Document revision date: 30 March 2001

This section describes the basic requirements for setting up an HSG for use with OpenVMS. Note that the steps for setting up an HSG60 and an HSG80 are the same, although the examples show the output for an HSG80. Refer to the HSG80 Array Controller ACS Version 8.4 Configuration and CLI Reference Guide for more information.

These are the steps you must perform to configure an HSG for OpenVMS:

1. If the HSG has dual controllers, set them to multibus failover mode ( Section 7.7.1).
2. Set the controller's SCSI version to SCSI-3 ( Section 7.7.2).

   Note You do not need to set the controller's allocation class value. This parameter is not used by OpenVMS with the HSG.

3. If you want to access the HSG Command Console LUN (CCL) from OpenVMS, assign it a device identifier ( Section 7.7.3).
   This will cause OpenVMS to configure the CCL as a generic SCSI device.

   Note In current versions of OpenVMS, you must assign a device identifier to the CCL. This requirement will be removed in a future update.

4. Set the parameters for the HSG FC ports ( Section 7.7.4).
   Each port must have its FC profile set to PLDA and its topology set to FABRIC.
5. Initialize and add logical units to the HSG configuration ( Section 7.7.5).
   In this step, you must assign a logical unit number and a device identifier to each logical unit.

   Note You do not need to set the logical unit's preferred path parameter. OpenVMS does not use this value in its path selection.

6. Configure the HSG host connection table ( Section 7.7.6).

To set a dual HSG to multibus failover mode, you can use the following commands at the HSG console:

• An initial SHOW command to show whether the dual controller is configured for failover.
• The SET command that puts the controllers into multibus mode. Notice that this causes the other controller to restart.
• A second SHOW command to show that the dual controller is configured for multibus failover.

The commands and output are shown in Example 7-5.

Example 7-5 Setting a Dual HSG to Multibus Failover Mode

HSG> SHOW THIS_CONTROLLER Controller: HSG80 ZG80900677 Software R024F-0, Hardware E01 NODE_ID = 5000-1FE1-0000-0D10 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-2 Not configured for dual-redundancy Controller misconfigured -- other controller present Device Port SCSI address 6 Time: NOT SET Command Console LUN is disabled Host PORT_1: Reported PORT_ID = 5000-1FE1-0000-0D11 PORT_1_PROFILE = SCC PORT_1_TOPOLOGY = OFFLINE (offline) Host PORT_2: Reported PORT_ID = 5000-1FE1-0000-0D12 PORT_2_PROFILE = SCC PORT_2_TOPOLOGY = OFFLINE (offline) NOREMOTE_COPY Cache: 128 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) Mirrored Cache: Not enabled Battery: FULLY CHARGED Expires: 27-APR-2000 NOCACHE_UPS %CER--HSG> --13-JAN-1946 04:32:49 (time not set)-- Controllers misconfigured. - Type SHOW THIS_CONTROLLER HSG> SET MULTIBUS_FAILOVER COPY = THIS_CONTROLLER %EVL--HSG> --13-JAN-1946 04:38:37 (time not set)-- Instance Code: 07050064 (not yet reported to host) Template: 5.(05) Power On Time: 0. Years, 284. Days, 5. Hours, 18. Minutes, 27. Seconds Controller Model: HSG80 Serial Number: ZG80900677 Hardware Version: E01(29) Software Version: R024F(FF) Informational Report Instance Code: 07050064 Last Failure Code: 08080000 (No Last Failure Parameters) %EVL--HSG> --13-JAN-1946 04:38:37 (time not set)-- Instance Code: 43010064 (not yet reported to host) Template: 4.(04) Power On Time: 0. Years, 284. Days, 5. Hours, 18. Minutes, 28. Seconds Controller Model: HSG80 Serial Number: ZG80900677 Hardware Version: E01(29) Software Version: R024F(FF) Informational Report Other Controller Serial Number: ZG80900641 Failed Controller Target Number: 0.(00) LUNs Taken By This Controller: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Instance Code: 43010064 ... %CER--HSG> --13-JAN-1946 04:38:37 (time not set)-- Received LAST GASP message- from other controller, Last Failure Code: 08080000 HSG> ... %CER--HSG> --13-JAN-1946 04:39:23 (time not set)-- Other controller restarted HSG> SHOW THIS_CONTROLLER Controller: HSG80 ZG80900677 Software R024F-0, Hardware E01 NODE_ID = 5000-1FE1-0000-0D10 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-2 Configured for MULTIBUS_FAILOVER with ZG80900641 In dual-redundant configuration Device Port SCSI address 6 Time: NOT SET Command Console LUN is disabled Host PORT_1: Reported PORT_ID = 5000-1FE1-0000-0D11 PORT_1_PROFILE = SCC PORT_1_TOPOLOGY = OFFLINE (offline) Host PORT_2: Reported PORT_ID = 5000-1FE1-0000-0D12 PORT_2_PROFILE = SCC PORT_2_TOPOLOGY = OFFLINE (offline) NOREMOTE_COPY Cache: 128 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) Mirrored Cache: Not enabled Battery: FULLY CHARGED Expires: 27-APR-2000 NOCACHE_UPS Other controller restarted

7.7.2 Setting an HSG to SCSI-3 Mode

Example 7-6 shows how to set the HSG to SCSI-3 mode. Note that the other controller in a dual configuration is set automatically to the same mode. You must restart the controllers for this operation to take effect.

Example 7-6 Setting an HSG to SCSI-3 Mode

HSG> SET THIS_CONTROLLER SCSI_VERSION = SCSI-3 Warning 4030: Any units that would appear as unit 0 to a host will not be available when in SCSI-3 mode Warning 4020: A restart of both this and the other controller is required before all the parameters modified will take effect %CER--HSG> --13-JAN-1946 04:42:28 (time not set)-- Restart of this controller- required %CER--HSG> --13-JAN-1946 04:42:28 (time not set)-- Restart of the other- controller required Restart of this controller required Restart of the other controller required

7.7.3 Setting the Device Identifier for the CCL

If you choose to have OpenVMS configure the CCL, then you must assign an identifier to the controller pair. This identifier must be unique for all HSG controller pairs in the cluster.

The following command sets the device identifier for the CCL of the controller pair to 42. This will cause OpenVMS to configure the CCL as a generic SCSI device. The device name will be $1$GGA42. Use the SHOW THIS_CONTROLLER command to verify the setting.

HSG> SET THIS_CONTROLLER IDENTIFIER = 42

To set each HSG port's profile to PLDA and its topology to FABRIC, use the commands shown in Example 7-7. You can verify the settings with the SHOW THIS and SHOW OTHER commands.

Note that each port has a unique 64-bit identifier in the form 5000-1FE1-0000-0D11. These identifiers are displayed in the SHOW THIS and SHOW OTHER displays, next to the label Reported PORT_ID . These identifiers are used by OpenVMS to denote the multiple paths that may exist between the host and the logical unit.

Example 7-7 Setting the HSG Port Parameters

HSG> SET THIS_CONTROLLER PORT_1_PROFILE = PLDA Warning 4000: A restart of this controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:24:09-- Restart of this controller required Restart of this controller required HSG> SET THIS_CONTROLLER PORT_1_TOPOLOGY = FABRIC Warning 4000: A restart of this controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:25:02-- Restart of this controller required Restart of this controller required HSG> SET THIS_CONTROLLER PORT_2_PROFILE = PLDA Warning 4000: A restart of this controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:25:26-- Restart of this controller required Restart of this controller required HSG> SET THIS_CONTROLLER PORT_2_TOPOLOGY = FABRIC Warning 4000: A restart of this controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:25:39-- Restart of this controller required Restart of this controller required HSG> SHOW THIS_CONTROLLER Controller: HSG80 ZG80900677 Software R024F-0, Hardware E01 NODE_ID = 5000-1FE1-0000-0D10 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 Configured for MULTIBUS_FAILOVER with ZG80900641 In dual-redundant configuration Device Port SCSI address 6 Time: 17-MAR-1999 12:25:55 Command Console LUN is lun 0 (IDENTIFIER = 42) Host PORT_1: Reported PORT_ID = 5000-1FE1-0000-0D11 PORT_1_PROFILE = PLDA PORT_1_TOPOLOGY = FABRIC (offline) Host PORT_2: Reported PORT_ID = 5000-1FE1-0000-0D12 PORT_2_PROFILE = PLDA PORT_2_TOPOLOGY = FABRIC (offline) NOREMOTE_COPY Cache: 128 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) Mirrored Cache: Not enabled Battery: FULLY CHARGED Expires: 27-APR-2000 NOCACHE_UPS HSG> SET OTHER_CONTROLLER PORT_1_PROFILE = PLDA Warning 4010: A restart of the other controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:26:46-- Restart of the other controller required Restart of the other controller required HSG> SET OTHER_CONTROLLER PORT_1_TOPOLOGY = FABRIC Warning 4010: A restart of the other controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:26:59-- Restart of the other controller required Restart of the other controller required HSG> SET OTHER_CONTROLLER PORT_2_PROFILE = PLDA Warning 4010: A restart of the other controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:27:08-- Restart of the other controller required Restart of the other controller required HSG> SET OTHER_CONTROLLER PORT_2_TOPOLOGY = FABRIC Warning 4010: A restart of the other controller is required before all the parameters modified will take effect %CER--HSG> --17-MAR-1999 12:27:15-- Restart of the other controller required Restart of the other controller required HSG> SHOW OTHER_CONTROLLER Controller: HSG80 ZG80900641 Software R024F-0, Hardware E01 NODE_ID = 5000-1FE1-0000-0D10 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 Configured for MULTIBUS_FAILOVER with ZG80900677 In dual-redundant configuration Device Port SCSI address 7 Time: 17-MAR-1999 12:27:31 Command Console LUN is lun 0 (IDENTIFIER = 42) Host PORT_1: Reported PORT_ID = 5000-1FE1-0000-0D13 PORT_1_PROFILE = PLDA PORT_1_TOPOLOGY = FABRIC (offline) Host PORT_2: Reported PORT_ID = 5000-1FE1-0000-0D14 PORT_2_PROFILE = PLDA PORT_2_TOPOLOGY = FABRIC (offline) NOREMOTE_COPY Cache: 128 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = DEFAULT (10 seconds) Mirrored Cache: Not enabled Battery: FULLY CHARGED Expires: 27-APR-2000 NOCACHE_UPS

7.7.5 Setting Up Logical Units on the HSG

Setting up logical units on the HSG consists of the following steps, as shown in Example 7-8:

1. Configure all the physical disk devices on the HSG with the CONFIG command.
2. Configure each disk device as a logical unit as follows:
   1. Use the INITIALIZE command to initialize the disk.
   2. Use the ADD command to add the initialized disk as a host-visible logical unit.
      Choose a logical unit number that is unique for the HSG storage subsystem. The value chosen in Example 7-8 is 20, which results in a logical unit name of D20.
   3. Use the SET command to set a device identifier that will serve as the basis for the OpenVMS device name.
      This device identifier must be unique for all FC disks in the OpenVMS Cluster. The value chosen in Example 7-8 is 32020, which results in an OpenVMS device name of $1$DGA32020 for the logical unit.
      Note: This device identifier is limited to 9999, if the FC device is MSCP served. This restriction will be removed in a future release.

Example 7-8 Setting Up Logical Units on the HSG

HSG> RUN CONFIG Config Local Program Invoked Config is building its tables and determining what devices exist on the subsystem. Please be patient. add disk DISK10000 1 0 0 add disk DISK10100 1 1 0 add disk DISK10200 1 2 0 add disk DISK20000 2 0 0 Config - Normal Termination HSG> SHOW DISK FULL Name Type Port Targ Lun Used by ------------------------------------------------------------------------------ ... DISK20000 disk 2 0 0 DEC RZ1CD-CS (C) DEC 0306 Switches: NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 20.00 MHZ negotiated) Size: 8378028 blocks HSG> SHOW UNITS No LUNs HSG> INITIALIZE DISK20000 HSG> ADD UNIT D20 DISK20000 HSG> SET D20 IDENTIFIER = 32020 HSG> SHOW UNITS FULL LUN Uses Used by ------------------------------------------------------------------------------ D20 DISK20000 LUN ID: 6000-1FE1-0000-0D10-0009-8090-0677-0024 IDENTIFIER = 32020 Switches: RUN NOWRITE_PROTECT READ_CACHE READAHEAD_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 32 Access: ALL State: ONLINE to this controller Not reserved NOPREFERRED_PATH Size: 8378028 blocks Geometry (C/H/S): ( 3708 / 20 / 113 )

7.7.6 Configuring the HSG Host Connections

You can allow the HSG to create default host-connection information automatically, or you can set host connection information manually, as described in the HSG80 Array Controller ACS Version 8.4 Configuration and CLI Reference Guide. If you use the automatic method, you will need to make some changes to the default settings.

Initially, the HSG has no host connections. Then, when hosts are connected to the FC interconnect and powered up, the HSG detects them and creates default connection information for them, as shown in Example 7-9. After this default information is created, you may want to rename the connections to values that have meaning in your environment, as shown in Example 7-9.

Then, you must:

• Set the operating system name to VMS for each connection, as shown in Example 7-9.
• Check that the unit offset value is set to zero (0) for each connection. If not, set to zero.

Example 7-9 Configuring the HSG Host Connections

HSG> SHOW CONNECTIONS No Connections HSG> SHOW CONNECTIONS Connection Unit Name Operating system Controller Port Address Status Offset !NEWCON44 WINNT THIS 2 210713 OL this 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB !NEWCON45 WINNT OTHER 2 210713 OL other 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB !NEWCON46 WINNT THIS 1 210713 OL this 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694 !NEWCON47 WINNT OTHER 1 210713 OL other 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694 HSG> RENAME !NEWCON44 FCNOD1A_T HSG> RENAME !NEWCON45 FCNOD1A_O HSG> RENAME !NEWCON46 FCNOD1B_T HSG> RENAME !NEWCON47 FCNOD1B_O HSG> SHOW CONNECTIONS Connection Unit Name Operating system Controller Port Address Status Offset FCNOD1A_O WINNT OTHER 2 210713 OL other 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB FCNOD1A_T WINNT THIS 2 210713 OL this 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB FCNOD1B_O WINNT OTHER 1 210713 OL other 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694 FCNOD1B_T WINNT THIS 1 210713 OL this 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694 HSG> SET FCNOD1A_O OPERATING_SYSTEM = VMS HSG> SET FCNOD1A_T OPERATING_SYSTEM = VMS HSG> SET FCNOD1B_O OPERATING_SYSTEM = VMS HSG> SET FCNOD1B_T OPERATING_SYSTEM = VMS HSG> SHOW CONNECTIONS Connection Unit Name Operating system Controller Port Address Status Offset FCNOD1A_O VMS OTHER 2 210713 OL other 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB FCNOD1A_T VMS THIS 2 210713 OL this 0 HOST_ID=1000-0000-C920-A7DB ADAPTER_ID=1000-0000-C920-A7DB FCNOD1B_O VMS OTHER 1 210713 OL other 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694 FCNOD1B_T VMS THIS 1 210713 OL this 0 HOST_ID=1000-0000-C920-A694 ADAPTER_ID=1000-0000-C920-A694

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-10 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-11 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-10 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-11 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