Document revision date: 15 July 2002

The AlphaServer console can be used to view the status of an FC interconnect. This allows you to confirm that the interconnect is set up properly before booting. If you plan to use an FC disk device for booting or dumping, you must perform some additional steps to set up those FC disk devices at the console. These topics are discussed in the next sections.

7.6.1 Viewing the FC Configuration from the Console

Console SHOW commands can be used to display information about the devices that the console detected when it last probed the system's I/O adapters. Unlike other interconnects, however, FC disk devices are not automatically included in the SHOW DEVICE output. This is because FC devices are identified by their WWIDs, and WWIDs are too large to be included in the SHOW DEVICE output. Instead, the console provides a command for managing WWIDs, named the wwidmgr command. This command enables you to display information about FC devices and to define appropriate device names for the FC devices that will be used for booting and dumping.

Note the following points about using the wwidmgr command:

• To use the wwidmgr command, if your system is an AlphaServer model 8x00, 4x00, or 1200, you must first enter diagnostic mode. On all other platforms, the wwidmgr command can be issued at any time.
• The changes made by the wwidmgr command do not take effect until after the next system initialization. After using the wwidmgr command, you must issue the initialize command.

Refer to the Wwidmgr Users' Manual for a complete description of the wwidmgr command. (The Wwidmgr Users' Manual is available in the [.DOC] directory of the Alpha Systems Firmware Update CD-ROM.)

The following examples, produced on an AlphaServer 4100 system, show some typical uses of the wwidmgr command. Other environments may require additional steps to be taken, and the output on other systems may vary slightly.

Note the following about Example 7-1:

• The wwidmgr -show wwid command displays a summary of the FC devices on the system. This command does not display information about device connectivity.
• There are two FC adapters and five disks. (All the disks are listed at the end, independent of the adapters to which they are connected.) In this example, each of the disks was assigned a device identifier at the HSG80 console. The console refers to this identifier as a user-assigned device identifier (UDID).

Example 7-1 Using wwidmgr -show wwid

P00>>>set mode diag Console is in diagnostic mode P00>>>wwidmgr -show wwid polling kgpsa0 (KGPSA-B) slot 2, bus 0 PCI, hose 1 kgpsaa0.0.0.2.1 PGA0 WWN 1000-0000-c920-a7db polling kgpsa1 (KGPSA-B) slot 3, bus 0 PCI, hose 1 kgpsab0.0.0.3.1 PGB0 WWN 1000-0000-c920-a694 [0] UDID:10 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 (ev:none) [1] UDID:50 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 (ev:none) [2] UDID:51 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 (ev:none) [3] UDID:60 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 (ev:none) [4] UDID:61 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 (ev:none)

Example 7-2 shows how the wwidmgr show wwid -full command displays information about FC devices and how they are connected. The display has two parts:

• The first part lists each path from an adapter to an FC port. Adapters are identified by console device names, such as KGPSAA. FC ports are identified by their WWID, such as 5000-1FE1-0000-0D14. If any FC disks are found on a path, they are listed after that path. FC disks are identified by their current console device name, followed by their WWID.
• The second part of the display lists all the FC disks and the paths through which they are reachable. In this part, which begins with [0] UDID:10... , you will see there are four paths to each disk with two paths through each adapter, KGPSAA and KGPSAB. Each path through an adapter goes to a different port on the HSG or HSV. The column titled Con indicates whether the FC disk unit is currently online to the HSG or HSV controller that this path uses.

Example 7-2 Using wwidmgr -show wwid -full

P00>>>wwidmgr -show wwid -full kgpsaa0.0.0.2.1 - Port: 1000-0000-c920-a7db kgpsaa0.0.0.2.1 - Port: 2007-0060-6900-075b kgpsaa0.0.0.2.1 - Port: 20fc-0060-6900-075b kgpsaa0.0.0.2.1 - Port: 5000-1fe1-0000-0d14 - dga12274.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 - dga15346.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 - dga31539.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 - dga31155.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 - dga30963.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 kgpsaa0.0.0.2.1 - Port: 5000-1fe1-0000-0d11 - dga12274.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 - dga15346.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 - dga31539.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 - dga31155.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 - dga30963.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 kgpsab0.0.0.3.1 - Port: 1000-0000-c920-a694 kgpsab0.0.0.3.1 - Port: 2007-0060-6900-09b8 kgpsab0.0.0.3.1 - Port: 20fc-0060-6900-09b8 kgpsab0.0.0.3.1 - Port: 5000-1fe1-0000-0d13 - dgb12274.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 - dgb15346.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 - dgb31539.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 - dgb31155.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 - dgb30963.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 kgpsab0.0.0.3.1 - Port: 5000-1fe1-0000-0d12 - dgb12274.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 - dgb15346.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 - dgb31539.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 - dgb31155.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 - dgb30963.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 [0] UDID:10 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 (ev:none) - current_unit:12274 current_col: 0 default_unit:12274 via adapter via fc_nport Con DID Lun - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 10 - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 10 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 10 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 10 [1] UDID:50 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 (ev:none) - current_unit:15346 current_col: 0 default_unit:15346 via adapter via fc_nport Con DID Lun - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 50 - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 50 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 50 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 50 [2] UDID:51 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 (ev:none) - current_unit:31539 current_col: 0 default_unit:31539 via adapter via fc_nport Con DID Lun - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 51 - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 51 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 51 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 51 [3] UDID:60 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 (ev:none) - current_unit:31155 current_col: 0 default_unit:31155 via adapter via fc_nport Con DID Lun - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 60 - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 60 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 60 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 60 [4] UDID:61 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 (ev:none) - current_unit:30963 current_col: 0 default_unit:30963 via adapter via fc_nport Con DID Lun - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 61 - kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 61 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 61 - kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 61

7.6.2 Setting Up FC Disks for Booting and Dumping

You must use the wwidmgr command to set up each device that you will use for booting or dumping. Once a device is set up, the console retains the information it requires to access the device in nonvolatile memory. You only have to rerun the wwidmgr command if the system configuration changes and the nonvolatile information is no longer valid.

The console provides a simplified setup command, called wwidmgr -quickset . This command can be used in either of the following cases:

• You are setting up just one device.
• All the devices you are setting up are accessed through the same ports on the HSG or HSV.

If neither description applies to your configuration, refer to the Wwidmgr Users' Manual for additional instructions.

Example 7-3 illustrates the wwidmgr -quickset command. Note the following:

• The command wwidmgr -quickset -udid 10 sets up the FC disk whose HSG or HSV device identifier is equal to 10.
• The console device names are path dependent. Each path used to access an FC disk has a different name. In this example, the wwidmgr -quickset command establishes four console device names corresponding to the four paths from the host to the FC disk:
  • dga10.1001.0.2.1
  • dga10.1002.0.2.1
  • dgb10.1003.0.3.1
  • dgb10.1004.0.3.1
• The second command, wwidmgr -quickset -udid 50 , sets up the FC disk whose HSG or HSV identifier is equal to 50.
• The changes made by the wwidmgr command do not take effect until after the next system initialization, so the next step is to issue an initialize command.
• After the initialization, the console show device command displays each FC adapter, followed by the paths through that adapter to each of the defined FC disks. The path-independent OpenVMS device name for each FC disk is displayed in the second column.

Example 7-3 Using widmgr -quickset

P00>>>wwidmgr -quickset -udid 10 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d10-0009-8090-0677-0016 via adapter: via fc nport: connected: dga10.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes dga10.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No dgb10.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes dgb10.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No P00>>>wwidmgr -quickset -udid 50 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d10-0009-8090-0677-0016 via adapter: via fc nport: connected: dga10.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes dga10.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No dgb10.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes dgb10.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 6000-1fe1-0000-0d10-0009-8090-0677-0026 via adapter: via fc nport: connected: dga50.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes dga50.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No dgb50.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes dgb50.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No P00>>>initialize Initializing... P00>>>show device polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7 dka500.5.0.1.1 DKA500 RRD45 1645 polling kgpsa0 (KGPSA-B) slot 2, bus 0 PCI, hose 1 kgpsaa0.0.0.2.1 PGA0 WWN 1000-0000-c920-a7db dga10.1001.0.2.1 $1$DGA10 HSG80 R024 dga50.1001.0.2.1 $1$DGA50 HSG80 R024 dga10.1002.0.2.1 $1$DGA10 HSG80 R024 dga50.1002.0.2.1 $1$DGA50 HSG80 R024 polling kgpsa1 (KGPSA-B) slot 3, bus 0 PCI, hose 1 kgpsab0.0.0.3.1 PGB0 WWN 1000-0000-c920-a694 dgb10.1003.0.3.1 $1$DGA10 HSG80 R024 dgb50.1003.0.3.1 $1$DGA50 HSG80 R024 dgb10.1004.0.3.1 $1$DGA10 HSG80 R024 dgb50.1004.0.3.1 $1$DGA50 HSG80 R024 polling isp0 (QLogic ISP1020) slot 4, bus 0 PCI, hose 1 SCSI Bus ID 15 dkb0.0.0.4.1 DKB0 RZ1CB-CS 0844 dkb100.1.0.4.1 DKB100 RZ1CB-CS 0844 polling floppy0 (FLOPPY) PCEB - XBUS hose 0 dva0.0.0.1000.0 DVA0 RX23 polling ncr1 (NCR 53C810) slot 4, bus 0 PCI, hose 0 SCSI Bus ID 7 dkc0.0.0.4.0 DKC0 RZ29B 0007 polling tulip0 (DECchip 21040-AA) slot 3, bus 0 PCI, hose 0 ewa0.0.0.3.0 00-00-F8-21-09-74 Auto-Sensing

Example 7-4 shows a boot sequence from an FC system disk. Note the following:

• The boot device is $1$DGA50 . The user has elected to enter all four paths to the device in the bootdef_dev string. This ensures that the system will be able to boot even if a path has failed.
• The first path on the boot command string, dga50.1002.0.2.1 , is not currently connected (that is, the disk is not on line to the HSG80 on that path). The console indicates this fact, retries a few times, then moves on to the next path in the bootdef_dev string. This path is currently connected, and the boot succeeds.
• After booting, the OpenVMS SHOW DEVICE command confirms that OpenVMS has configured all five of the FC devices that were displayed by the wwidmgr -show wwid command, not only the two FC disks that were set up using the console wwidmgr -quickset command. The OpenVMS SHOW DEV/MULTIPATH command confirms that OpenVMS has configured all four paths to each disk.

Example 7-4 Boot Sequence from an FC System Disk

P00>>>set bootdef_dev dga50.1002.0.2.1,dga50.1001.0.2.1,dgb50.1003.0.3.1, dgb50.1004.0.3.1 P00>>>b (boot dga50.1002.0.2.1 -flags 0,0) dga50.1002.0.2.1 is not connected dga50.1002.0.2.1 is not connected dga50.1002.0.2.1 is not connected dga50.1002.0.2.1 is not connected failed to open dga50.1002.0.2.1 (boot dga50.1001.0.2.1 -flags 0,0) block 0 of dga50.1001.0.2.1 is a valid boot block reading 919 blocks from dga50.1001.0.2.1 bootstrap code read in Building FRU table base = 200000, image_start = 0, image_bytes = 72e00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OpenVMS (TM) Alpha Operating System, Version V7.2 ... $ SHOW DEVICE Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $1$DGA10: (FCNOD1) Online 0 $1$DGA50: (FCNOD1) Mounted 0 V72_SSB 4734189 303 1 $1$DGA51: (FCNOD1) Online 0 $1$DGA60: (FCNOD1) Online 0 $1$DGA61: (FCNOD1) Online 0 $ SHOW LOGICAL SYS$SYSDEVICE "SYS$SYSDEVICE" = "$1$DGA50:" (LNM$SYSTEM_TABLE) $ SHO DEV/MULTI Device Device Error Current Name Status Count Paths path $1$DGA10: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11 $1$DGA50: (FCNOD1) Mounted 0 4/ 4 PGA0.5000-1FE1-0000-0D12 $1$DGA51: (FCNOD1) Online 0 4/ 4 PGA0.5000-1FE1-0000-0D13 $1$DGA60: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D14 $1$DGA61: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11 Device Device Error Current Name Status Count Paths path $1$GGA42: Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11

7.7 Setting Up a Storage Controller for Use with OpenVMS

The Compaq storage array controllers and the manuals that provide specific information for configuring them for use with OpenVMS follow:

• HSG60/80
  HSG80 ACS Solution Software Version 8.6 for Compaq OpenVMS, order number AA-RH4BD-TE.
  This manual is available at the following location:

  ftp://ftp.compaq.com/pub/products/storageworks/techdoc/raidstorage/AA-RH4BD-TE.pdf

• HSV110 (Enterprise Virtual Array)
  OpenVMS Kit V1.0 for Enterprise Virtual Array Installation and Configuration Guide, order number AA-RR03A-TE.
  This manual is available at the following location:

  ftp://ftp.compaq.com/pub/products/storageworks/techdoc/enterprise/AA-RR03A-TE.pdf

Defining a unique device identifier for the Command Console LUN (CCL) of the HSG and HSV is not required by OpenVMS, but it may be required by some management tools. OpenVMS suggests that you always define a unique device identifier since this identifier causes the creation of a CCL device visible using the SHOW DEVICE command. Although this device is not directly controllable on OpenVMS, you can display the multiple paths to the storage controller using the SHOW DEVICE/FULL command, and diagnose failed paths, as shown in the following example for $1$GGA3, where one of the two paths has failed.

Paver> sh dev gg /mul Device Device Error Current Name Status Count Paths path $1$GGA1: Online 0 2/ 2 PGA0.5000-1FE1-0011-AF08 $1$GGA3: Online 0 1/ 2 PGA0.5000-1FE1-0011-B158 $1$GGA4: Online 0 2/ 2 PGA0.5000-1FE1-0015-2C58 $1$GGA5: Online 0 2/ 2 PGA0.5000-1FE1-0015-22A8 $1$GGA6: Online 0 2/ 2 PGA0.5000-1FE1-0015-2D18 $1$GGA7: Online 0 2/ 2 PGA0.5000-1FE1-0015-2D08 $1$GGA9: Online 0 2/ 2 PGA0.5000-1FE1-0007-04E3 Paver> show dev /full $1$gga9: Device $1$GGA9:, device type Generic SCSI device, is online, shareable, device has multiple I/O paths. Error count 0 Operations completed 0 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL Reference count 0 Default buffer size 0 WWID 02000008:5000-1FE1-0007-04E0 I/O paths to device 2 Path PGA0.5000-1FE1-0007-04E3 (PAVER), primary path, current path. Error count 0 Operations completed 0 Path PGA0.5000-1FE1-0007-04E1 (PAVER). Error count 0 Operations completed 0

7.7.2 Setting Up the Device Identifier for Disk Devices

The device identifier for disks is appended to the string $1$DGA to form the complete device name. It is essential that all disks have unique device identifiers within a cluster. Device identifiers can be between 0 and 32767, except a device identifier of 0 is not valid on the HSV. Device identifiers greater than 9999 cannot be MSCP served to other systems.

7.8 Creating a Cluster with a Shared FC System Disk

To configure nodes in an OpenVMS Cluster system, you must execute the CLUSTER_CONFIG.COM (or CLUSTER_CONFIG_LAN.COM) command procedure. (You can run either the full version, which provides more information about most prompts, or the brief version.)

For the purposes of CLUSTER_CONFIG, a shared Fibre Channel (FC) bus is treated like a shared SCSI bus, except that the allocation class parameters do not apply to FC. The rules for setting node allocation class and port allocation class values remain in effect when parallel SCSI storage devices are present in a configuration that includes FC storage devices.

To configure a new OpenVMS Cluster system, you must first enable clustering on a single, or standalone, system. Then you can add additional nodes to the cluster.

Example 7-5 shows how to enable clustering using brief version of CLUSTER_CONFIG_LAN.COM on a standalone node called FCNOD1. At the end of the procedure, FCNOD1 reboots and forms a one-node cluster.

Example 7-6 shows how to run the brief version of CLUSTER_CONFIG_LAN.COM on FCNOD1 to add a second node, called FCNOD2, to form a two-node cluster. At the end of the procedure, the cluster is configured to allow FCNOD2 to boot off the same FC system disk as FCNOD1.

The following steps are common to both examples:

1. Select the default option [1] for ADD.
2. Answer Yes when CLUSTER_CONFIG_LAN.COM asks whether there will be a shared SCSI bus. SCSI in this context refers to FC as well as to parallel SCSI.
   The allocation class parameters are not affected by the presence of FC.
3. Answer No when the procedure asks whether the node will be a satellite.

Example 7-5 Enabling Clustering on a Standalone FC Node

$ @CLUSTER_CONFIG_LAN BRIEF Cluster Configuration Procedure Executing on an Alpha System DECnet Phase IV is installed on this node. The LAN, not DECnet, will be used for MOP downline loading. This Alpha node is not currently a cluster member MAIN MENU 1. ADD FCNOD1 to existing cluster, or form a new cluster. 2. MAKE a directory structure for a new root on a system disk. 3. DELETE a root from a system disk. 4. EXIT from this procedure. Enter choice [1]: 1 Is the node to be a clustered node with a shared SCSI or Fibre Channel bus (Y/N)? Y Note: Every cluster node must have a direct connection to every other node in the cluster. Since FCNOD1 will be a clustered node with a shared SCSI or FC bus, and Memory Channel, CI, and DSSI are not present, the LAN will be used for cluster communication. Enter this cluster's group number: 511 Enter this cluster's password: Re-enter this cluster's password for verification: Will FCNOD1 be a boot server [Y]? Y Verifying LAN adapters in LANACP database... Updating LANACP LAN server process volatile and permanent databases... Note: The LANACP LAN server process will be used by FCNOD1 for boot serving satellites. The following LAN devices have been found: Verifying LAN adapters in LANACP database... LAN TYPE ADAPTER NAME SERVICE STATUS ======== ============ ============== Ethernet EWA0 ENABLED CAUTION: If you do not define port allocation classes later in this procedure for shared SCSI buses, all nodes sharing a SCSI bus must have the same non-zero ALLOCLASS value. If multiple nodes connect to a shared SCSI bus without the same allocation class for the bus, system booting will halt due to the error or IO AUTOCONFIGURE after boot will keep the bus offline. Enter a value for FCNOD1's ALLOCLASS parameter [0]: 5 Does this cluster contain a quorum disk [N]? N Each shared SCSI bus must have a positive allocation class value. A shared bus uses a PK adapter. A private bus may use: PK, DR, DV. When adding a node with SCSI-based cluster communications, the shared SCSI port allocation classes may be established in SYS$DEVICES.DAT. Otherwise, the system's disk allocation class will apply. A private SCSI bus need not have an entry in SYS$DEVICES.DAT. If it has an entry, its entry may assign any legitimate port allocation class value: n where n = a positive integer, 1 to 32767 inclusive 0 no port allocation class and disk allocation class does not apply -1 system's disk allocation class applies (system parameter ALLOCLASS) When modifying port allocation classes, SYS$DEVICES.DAT must be updated for all affected nodes, and then all affected nodes must be rebooted. The following dialog will update SYS$DEVICES.DAT on FCNOD1. There are currently no entries in SYS$DEVICES.DAT for FCNOD1. After the next boot, any SCSI controller on FCNOD1 will use FCNOD1's disk allocation class. Assign port allocation class to which adapter [RETURN for none]: PKA Port allocation class for PKA0: 10 Port Alloclass 10 Adapter FCNOD1$PKA Assign port allocation class to which adapter [RETURN for none]: PKB Port allocation class for PKB0: 20 Port Alloclass 10 Adapter FCNOD1$PKA Port Alloclass 20 Adapter FCNOD1$PKB WARNING: FCNOD1 will be a voting cluster member. EXPECTED_VOTES for this and every other cluster member should be adjusted at a convenient time before a reboot. For complete instructions, check the section on configuring a cluster in the "OpenVMS Cluster Systems" manual. Execute AUTOGEN to compute the SYSGEN parameters for your configuration and reboot FCNOD1 with the new parameters. This is necessary before FCNOD1 can become a cluster member. Do you want to run AUTOGEN now [Y]? Y Running AUTOGEN -- Please wait. The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the upgrade will be complete.

Example 7-6 Adding a Node to a Cluster with a Shared FC System Disk

$ @CLUSTER_CONFIG_LAN BRIEF Cluster Configuration Procedure Executing on an Alpha System DECnet Phase IV is installed on this node. The LAN, not DECnet, will be used for MOP downline loading. FCNOD1 is an Alpha system and currently a member of a cluster so the following functions can be performed: MAIN MENU 1. ADD an Alpha 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 FCNOD1. 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 [1]: 1 This ADD function will add a new Alpha node to the cluster. WARNING: If the node being added is a voting member, EXPECTED_VOTES for every cluster member must be adjusted. For complete instructions check the section on configuring a cluster in the "OpenVMS Cluster Systems" manual. CAUTION: If this cluster is running with multiple system disks and common system files will be used, please, do not proceed unless appropriate logical names are defined for cluster common files in SYLOGICALS.COM. For instructions, refer to the "OpenVMS Cluster Systems" manual. Is the node to be a clustered node with a shared SCSI or Fibre Channel bus (Y/N)? Y Will the node be a satellite [Y]? N What is the node's SCS node name? FCNOD2 What is the node's SCSSYSTEMID number? 19.111 NOTE: 19.111 equates to an SCSSYSTEMID of 19567 Will FCNOD2 be a boot server [Y]? Y What is the device name for FCNOD2's system root [default DISK$V72_SSB:]? Y What is the name of FCNOD2's system root [SYS10]? Creating directory tree SYS10 ... System root SYS10 created CAUTION: If you do not define port allocation classes later in this procedure for shared SCSI buses, all nodes sharing a SCSI bus must have the same non-zero ALLOCLASS value. If multiple nodes connect to a shared SCSI bus without the same allocation class for the bus, system booting will halt due to the error or IO AUTOCONFIGURE after boot will keep the bus offline. Enter a value for FCNOD2's ALLOCLASS parameter [5]: Does this cluster contain a quorum disk [N]? N Size of pagefile for FCNOD2 [RETURN for AUTOGEN sizing]? A temporary pagefile will be created until resizing by AUTOGEN. The default size below is arbitrary and may or may not be appropriate. Size of temporary pagefile [10000]? Size of swap file for FCNOD2 [RETURN for AUTOGEN sizing]? A temporary swap file will be created until resizing by AUTOGEN. The default size below is arbitrary and may or may not be appropriate. Size of temporary swap file [8000]? Each shared SCSI bus must have a positive allocation class value. A shared bus uses a PK adapter. A private bus may use: PK, DR, DV. When adding a node with SCSI-based cluster communications, the shared SCSI port allocation classes may be established in SYS$DEVICES.DAT. Otherwise, the system's disk allocation class will apply. A private SCSI bus need not have an entry in SYS$DEVICES.DAT. If it has an entry, its entry may assign any legitimate port allocation class value: n where n = a positive integer, 1 to 32767 inclusive 0 no port allocation class and disk allocation class does not apply -1 system's disk allocation class applies (system parameter ALLOCLASS) When modifying port allocation classes, SYS$DEVICES.DAT must be updated for all affected nodes, and then all affected nodes must be rebooted. The following dialog will update SYS$DEVICES.DAT on FCNOD2. Enter [RETURN] to continue: $20$DKA400:<VMS$COMMON.SYSEXE>SYS$DEVICES.DAT;1 contains port allocation classes for FCNOD2. After the next boot, any SCSI controller not assigned in SYS$DEVICES.DAT will use FCNOD2's disk allocation class. Assign port allocation class to which adapter [RETURN for none]: PKA Port allocation class for PKA0: 11 Port Alloclass 11 Adapter FCNOD2$PKA Assign port allocation class to which adapter [RETURN for none]: PKB Port allocation class for PKB0: 20 Port Alloclass 11 Adapter FCNOD2$PKA Port Alloclass 20 Adapter FCNOD2$PKB Assign port allocation class to which adapter [RETURN for none]: WARNING: FCNOD2 must be rebooted to make port allocation class specifications in SYS$DEVICES.DAT take effect. Will a disk local only to FCNOD2 (and not accessible at this time to FCNOD1) be used for paging and swapping (Y/N)? N If you specify a device other than DISK$V72_SSB: for FCNOD2's page and swap files, this procedure will create PAGEFILE_FCNOD2.SYS and SWAPFILE_FCNOD2.SYS in the [SYSEXE] directory on the device you specify. What is the device name for the page and swap files [DISK$V72_SSB:]? %SYSGEN-I-CREATED, $20$DKA400:[SYS10.SYSEXE]PAGEFILE.SYS;1 created %SYSGEN-I-CREATED, $20$DKA400:[SYS10.SYSEXE]SWAPFILE.SYS;1 created The configuration procedure has completed successfully. FCNOD2 has been configured to join the cluster. The first time FCNOD2 boots, NETCONFIG.COM and AUTOGEN.COM will run automatically.

	privacy and legal statement
6318PRO_011.HTML