HP OpenVMS Cluster Systems
Previous Contents Index

8.4 Changing Computer Characteristics

As your processing needs change, you may want to add satellites to an existing OpenVMS Cluster, or you may want to change an OpenVMS Cluster that is based on one interconnect (such as the CI or DSSI interconnect, or HSC subsystem) to include several interconnects.

Table 8-8 describes the operations you can accomplish when you select the CHANGE option from the main menu of the cluster configuration command procedure.

Note: All operations except changing a satellite's LAN (Ethernet or FDDI) hardware address must be executed on the computer whose characteristics you want to change.

Table 8-8 CHANGE Options of the Cluster Configuration Procedure
Option Operation Performed
Enable the local computer as a disk server Loads the MSCP server by setting, in MODPARAMS.DAT, the value of the MSCP_LOAD parameter to 1 and the MSCP_SERVE_ALL parameter to 1 or 2.
Disable the local computer as a disk server Sets MSCP_LOAD to 0.
Enable the local computer as a boot server If you are setting up an OpenVMS Cluster that includes satellites, you must perform this operation once before you attempt to add satellites to the cluster. You thereby enable MOP service for the LAN adapter circuit that the computer uses to service operating system load requests from satellites. When you enable the computer as a boot server, it automatically becomes a disk server (if it is not one already) because it must serve its system disk to satellites.
Disable the local computer as a boot server Disables DECnet MOP service for the computer's adapter circuit.
Enable IP for cluster communications on the local computer Loads the port driver PEDRIVER by setting the value of the NISCS_LOAD_PEA0 parameter to 1 in MODPARAMS.DAT. Also, sets the value of NISCS_USE_UDP to 1 in MODPARAMS.DAT, which enables loading of the IP configuration files. Creates the cluster security database file, SYS$SYSTEM:[SYSEXE]CLUSTER_AUTHORIZE.DAT, on the local computer's system disk.
Disable IP for cluster communications on the local computer Sets NISCS_USE_UDP to 0.
Enable the LAN for cluster communications on the local computer Loads the port driver PEDRIVER by setting the value of the NISCS_LOAD_PEA0 parameter to 1 in MODPARAMS.DAT. Creates the cluster security database file, SYS$SYSTEM:[SYSEXE]CLUSTER_AUTHORIZE.DAT, on the local computer's system disk.

Caution: The VAXCLUSTER system parameter must be set to 2 if the NISCS_LOAD_PEA0 parameter is set to 1. This ensures coordinated access to shared resources in the cluster and prevents accidental data corruption.

Disable the LAN for cluster communications on the local computer Sets NISCS_LOAD_PEA0 to 0.
Enable a quorum disk on the local computer In MODPARAMS.DAT, sets the DISK_QUORUM system parameter to a device name; sets the value of QDSKVOTES to 1 (default value).
Disable a quorum disk on the local computer In MODPARAMS.DAT, sets a blank value for the DISK_QUORUM system parameter; sets the value of QDSKVOTES to 1.
Change a satellite's LAN hardware address Changes a satellite's hardware address if its LAN device needs replacement. Both the permanent and volatile network databases and NETNODE_UPDATE.COM are updated on the local computer.

Rule: You must perform this operation on each computer enabled as a boot server for the satellite.

Enable the local computer as a tape server Loads the TMSCP server by setting, in MODPARAMS.DAT, the value of the TMSCP_LOAD parameter to 1 and the TMSCP_SERVE_ALL parameter to 1 or 2.
Disable the local computer as a tape server Sets TMSCP_LOAD to zero.
Change the local computer's node allocation class value Sets a value for the computer's ALLOCLASS parameter in MODPARAMS.DAT.
Change the local computer's tape allocation class value Sets a value from 1 to 255 for the computer's TAPE_ALLOCLASS parameter in MODPARAMS.DAT. The default value is zero. You must specify a nonzero tape allocation class parameter if this node is locally connected to a dual-ported tape, or if it will be serving any multiple-host tapes (for example, TF nn or HSC connected tapes) to other cluster members. Satellites usually have TAPE_ALLOCLASS set to zero.
Change the local computer's port allocation class value Sets a value for the computer's ALLOCLASS parameter in MODPARAMS.DAT for all devices attached to it.
Enable MEMORY CHANNEL Sets MC_SERVICES_P2 to 1 to load the PMDRIVER (PMA0) cluster driver. This system parameter enables MEMORY CHANNEL on the local computer for node-to-node cluster communications.
Disable MEMORY CHANNEL Sets MC_SERVICES_P2 to 0 so that the PMDRIVER (PMA0) cluster driver is not loaded. The setting of 0 disables MEMORY CHANNEL on the local computer as the node-to-node cluster communications interconnect.

8.4.1 Preparation

You usually need to perform a number of steps before using the cluster configuration command procedure to change the configuration of your existing cluster.

Table 8-9 suggests several typical configuration changes and describes the procedures required to make them.

Table 8-9 Tasks Involved in Changing OpenVMS Cluster Configurations
Task Procedure
Add satellite nodes Perform these operations on the computer that will be enabled as a cluster boot server:
  1. Execute the CHANGE function to enable the first installed computer as a boot server (see Example 8-9).
  2. Execute the ADD function to add the satellite (as described in Section 8.2).
  3. Reconfigure the cluster according to the postconfiguration instructions in Section 8.6.
Change an existing CI or DSSI cluster to include satellite nodes To enable cluster communications over the LAN (Ethernet or FDDI) on all computers, and to enable one or more computers as boot servers, proceed as follows:
  1. Log in as system manager on each computer, invoke either CLUSTER_CONFIG_LAN.COM or CLUSTER_CONFIG.COM, and execute the CHANGE function to enable LAN communications.

    Rule: You must perform this operation on all computers.

    Note: You must establish a cluster group number and password on all system disks in the OpenVMS Cluster before you can successfully add a satellite node using the CHANGE function of the cluster configuration procedure.

  2. Execute the CHANGE function to enable one or more computers as boot servers.
  3. Reconfigure the cluster according to the postconfiguration instructions in Section 8.6.
Change an existing LAN-based cluster to include CI and DSSI interconnects Before performing the operations described here, be sure that the computers and HSC subsystems or RF disks you intend to include in your new configuration are correctly installed and checked for proper operation.

The method you use to include CI and DSSI interconnects with an existing LAN-based cluster configuration depends on whether your current boot server is capable of being configured as a CI or DSSI computer.

Note: The following procedures assume that the system disk containing satellite roots will reside on an HSC disk (for CI configurations) or an RF disk (for DSSI configurations).

  • If the boot server can be configured as a CI or DSSI computer, proceed as follows:
    1. Log in as system manager on the boot server and perform an image backup operation to back up the current system disk to a disk on an HSC subsystem or RF storage device. (For more information about backup operations, refer to the HP OpenVMS System Management Utilities Reference Manual.)
    2. Modify the computer's default bootstrap command procedure to boot the computer from the HSC or RF disk, according to the instructions in the appropriate system-specific installation and operations guide.
    3. Shut down the cluster. Shut down the satellites first, and then shut down the boot server.
    4. Boot the boot server from the newly created system disk on the HSC or RF storage subsystem.
    5. Reboot the satellites.
  • If your current boot server cannot be configured as a CI or a DSSI computer, proceed as follows:
    1. Shut down the old local area cluster. Shut down the satellites first, and then shut down the boot server.
    2. Install the OpenVMS operating system on the new CI computer's HSC system disk or on the new DSSI computer's RF disk, as appropriate. When the installation procedure asks whether you want to enable the LAN for cluster communications, answer YES.
    3. When the installation completes, log in as system manager, and configure and start the DECnet for OpenVMS network as described in Chapter 4.
    4. Execute the CHANGE function of either CLUSTER_CONFIG_LAN.COM or CLUSTER_CONFIG.COM to enable the computer as a boot server.
    5. Log in as system manager on the newly added computer and execute the ADD function of either CLUSTER_CONFIG_LAN.COM or CLUSTER_CONFIG.COM to add the former LAN cluster members (including the former boot server) as satellites.
  • Reconfigure the cluster according to the postconfiguration instructions in Section 8.6.
Convert a standalone computer to an OpenVMS Cluster computer Execute either CLUSTER_CONFIG_LAN.COM or CLUSTER_CONFIG.COM on a standalone computer to perform either of the following operations:
  • Add the standalone computer with its own system disk to an existing cluster.
  • Set up the standalone computer to form a new cluster if the computer was not set up as a cluster computer during installation of the operating system.
  • Reconfigure the cluster according to the postconfiguration instructions in Section 8.6.

See Example 8-13, which illustrates the use of CLUSTER_CONFIG.COM on standalone computer PLUTO to convert PLUTO to a cluster boot server.

If your cluster uses DECdtm services, you must create a transaction log for the computer when you have configured it into your cluster. For step-by-step instructions on how to do this, see the chapter on DECdtm services in the HP OpenVMS System Manager's Manual.

Enable or disable disk-serving or tape-serving functions After invoking either CLUSTER_CONFIG_LAN.COM or CLUSTER_CONFIG.COM to enable or disable the disk or tape serving functions, run AUTOGEN with the REBOOT option to reboot the local computer (see Section 8.6.1).

Note: When the cluster configuration command procedure sets or changes values in MODPARAMS.DAT, the new values are always appended at the end of the file so that they override earlier values. You may want to edit the file occasionally and delete lines that specify earlier values.

8.4.2 Examples

Examples 8-7 through 8-13 illustrate the use of CLUSTER_CONFIG_LAN.COM to perform the following operations:

Example 8-7 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Disk Server 

$ @CLUSTER_CONFIG_LAN.COM
              Cluster/IPCI Configuration Procedure 
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 5 
 
Enter a value for BHAGAT's ALLOCLASS parameter [1]: 
    The configuration procedure has completed successfully. 
 
    BHAGAT has been enabled as a disk server. In MODPARAMS.DAT: 
 
           MSCP_LOAD has been set to 1 
           MSCP_SERVE_ALL has been set to 2 
 
    Please run AUTOGEN to reboot BHAGAT: 
 
           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 
 
    If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the 
    cluster, using the procedure described in the OpenVMS Cluster Systems manual.

Example 8-8 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change the Local Computer's ALLOCLASS Value 

$ @CLUSTER_CONFIG_LAN.COM
               Cluster/IPCI Configuration Procedure 
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 7 
 
Enter a value for BHAGAT's ALLOCLASS parameter [1]: 2 
    The configuration procedure has completed successfully. 
 
    Since you have changed BHAGAT's ALLOCLASS value, you must reconfigure 
    the cluster, using the procedure described in the "OpenVMS Cluster 
    Systems" manual. This includes running AUTOGEN for BHAGAT as 
    shown below, before rebooting the cluster: 
 
           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 
                 
    If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the 
    cluster, using the procedure described in the OpenVMS Cluster Systems manual.

Example 8-9 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Boot Server 

$ @CLUSTER_CONFIG_LAN.COM
              Cluster/IPCI Configuration Procedure
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 1 
 
Enter a value for BHAGAT's ALLOCLASS parameter [1]: [Return]
    The configuration procedure has completed successfully. 
 
    BHAGAT has been enabled as a boot server. Disk serving and 
    LAN capabilities are enabled automatically. If BHAGAT was 
    not previously set up as a disk server, please run AUTOGEN 
    to reboot BHAGAT: 
 
           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 
 
    If you have changed BHAGAT's ALLOCLASS value, you must reconfigure the 
    cluster, using the procedure described in the OpenVMS Cluster Systems manual.

Example 8-10 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change a Satellite's Hardware Address 

$ @CLUSTER_CONFIG_LAN.COM
             Cluster/IPCI Configuration Procedure 
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 11 
 
What is the node's SCS node name? gomthi 
    Note: The current hardware address entry for GOMTHI is 00-30-6E-4C-BB-1A. 
What is GOMTHI's new LAN adapter hardware address? 00-30-6E-4C-BA-2A 
    The configuration procedure has completed successfully.

Example 8-11 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Tape Server 

$ @CLUSTER_CONFIG_LAN.COM                
              Cluster/IPCI Configuration Procedure
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 8 
 
Enter a value for BHAGAT's TAPE_ALLOCLASS parameter [0]: [Return]
Should BHAGAT serve any tapes it sees, local and remote [Y]? [Return]
 
    BHAGAT has been enabled as a tape server. In MODPARAMS.DAT, 
        TMSCP_LOAD has been set to 1 
        TMSCP_SERVE_ALL has been set to 1 
 
    Please run AUTOGEN to reboot BHAGAT: 
 
           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 
 
    If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure 
    the cluster, using the procedure described in the "OpenVMS Cluster 
    Systems" manual.

Example 8-12 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change the Local Computer's TAPE_ALLOCLASS Value 

$ @CLUSTER_CONFIG_LAN.COM
              Cluster/IPCI Configuration Procedure 
                   CLUSTER_CONFIG_LAN Version V2.84 
                     Executing on an IA64 System 
 
    DECnet-Plus is installed on this node. 
    IA64 satellites will use TCP/IP BOOTP and TFTP services for downline loading. 
    TCP/IP is installed and running on this node. 
 
        Enter a "?" for help at any prompt.  If you are familiar with 
        the execution of this procedure, you may want to mute extra notes 
        and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF". 
 
    BHAGAT is an IA64 system and currently a member of a cluster 
    so the following functions can be performed: 
 
MAIN Menu 
 
   1. ADD an IA64 node to the cluster. 
   2. REMOVE a node from the cluster. 
   3. CHANGE a cluster member's characteristics. 
   4. CREATE a duplicate system disk for BHAGAT. 
   5. MAKE a directory structure for a new root on a system disk. 
   6. DELETE a root from a system disk. 
   7. EXIT from this procedure. 
 
Enter choice [7]: 3 
 
CHANGE Menu 
 
   1. Enable BHAGAT as a boot server. 
   2. Disable BHAGAT as a boot server. 
   3. Enable a quorum disk for BHAGAT. 
   4. Disable a quorum disk for BHAGAT. 
   5. Enable BHAGAT as a disk server. 
   6. Disable BHAGAT as a disk server. 
   7. Change BHAGAT's ALLOCLASS value. 
   8. Enable BHAGAT as a tape server. 
   9. Disable BHAGAT as a tape server. 
  10. Change BHAGAT's TAPE_ALLOCLASS value. 
  11. Change an IA64 satellite node's LAN adapter hardware address. 
  12. Enable Cluster Communication using IP on BHAGAT. 
  13. Disable Cluster Communication using IP on BHAGAT. 
  14. Change BHAGAT's shared SCSI port allocation class value. 
  15. Reset an IA64 satellite node's boot environment file protections. 
  16. Return to MAIN menu. 
 
Enter choice [16]: 10 
 
Enter a value for BHAGAT's TAPE_ALLOCLASS parameter [0]: 1 
 
    If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure 
    the cluster, using the procedure described in the "OpenVMS Cluster 
    Systems" Manual. This includes running AUTOGEN for BHAGAT as 
    shown below, before rebooting the cluster: 
 
           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 
 
    If you have changed BHAGAT's TAPE_ALLOCLASS value, you must reconfigure 
    the cluster, using the procedure described in the OpenVMS Cluster Systems 
    manual.

Previous Next Contents Index