4 Installing Fibre Channel Hardware

4.1 Installing and Configuring Fibre Channel Hardware

This chapter provides information about installing the Fibre Channel hardware needed to support Tru64 UNIX or a TruCluster Server configuration using Fibre Channel storage.

Ensure that the member systems, the Fibre Channel switches, and the HSG80 array controllers are placed within the lengths of the optical cables you will be using.

Note

The maximum length of the optical cable between the KGPSA and the switch or switch and the HSG80 array controller is 500 meters via shortwave multimode Fibre Channel cable. The maximum distance between switches in a cascaded switch configuration is 10 kilometers using longwave single-mode fiber.

4.1.1 Installing and Setting Up the Fibre Channel Switch

The Fibre Channel switches support up to 8 (DS-DSGGA-AA/DS-DSGGB-AA) or 16 (DS-DSGGA-AB/DS-DSGGB-AB) full-duplex 1.6025 Gbits/sec ports. Each switch port can be connected to a KGPSA-BC or KGPSA-CA PCI-to-Fibre Channel host bus adapter, an HSG80 array controller, or another switch.

Each switch, except the DS-DSGGB-AB, has a front panel display and four push buttons that you use to manage the switch. There are four menus that allow you to configure, operate, obtain status, or test the switch. The DS-DSGGB-AB is managed by way of a telnet session once the IP address has been set (from a PC or terminal).

All switches have a 10Base-T Ethernet (RJ45) port, and once the IP address is set, the Ethernet connection allows you to manage the switch:

Remotely using a telnet TCP/IP connection

With Simple Network Management Protocol (SNMP)

Using Web management tools

Note

You have to set the IP address and subnet mask from the front panel (or from a PC or terminal with the DS-DSGGB-AA) before you can manage the switch by way of a telnet session, SNMP, or the Web.

The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) or eight (DS-DSGGA-AB) plug-in interface modules. Each interface module in turn supports two Gigabit Interface Converter (GBIC) modules. The GBIC module is the electrical-to-optical converter.

The shortwave GBIC supports 50-micron multimode fiber (MMF) using the standard subscriber connector (SC) connector. The longwave GBIC supports 9-micron, single-mode fiber optical cables. Only the 50-micron MMF optical cable is supported between the host bus adapters and switches or switches and HSG80 controllers for the TruCluster Server product. Longwave single-mode fiber optical cables are supported between switches in a cascaded switch configuration.

Note

If you need to install additional interface modules, do so before placing the switch in a relatively inaccessible location because you have to remove the top cover to install the interface modules.

The DS-DSGGB switch accommodates up to 8 (DS-DSGGB-AA) or 16 (DS-DSBBG-AB) GBIC modules.

4.1.1.1 Installing the Switch

Place the switch within 500 meters of the member systems (with KGPSA PCI-to-Fibre Channel adapter) and the HSG80 array controllers.

You can mount the switches in a 48.7-cm (19-in) rackmount installation or place the switch on a flat solid surface.

When you plan the switch location, ensure that you provide access to the front of the switch. All cables plug into the front of the switch. Also, for those switches with a control panel, the display and switches are on the front of the switch.

For an installation, at a minimum, you have to:

Place the switch or install it in the rack.

Connect the Ethernet cable.

Connect the fiber-optic cables.

Connect power to the switch.

Turn on the power. The switch runs a series of power-on self test (POST) tests.

Set the switch IP address and subnet mask (see Section 4.1.1.2.2). You can also set the switch name if desired (see Section 4.1.1.2.5). The switch IP address and subnet mask must initially be set from the front panel, except for the DS-DSGGB-AA 8-port Fibre Channel switch. In this case you have to connect a PC or terminal to the switch. You must use a telnet session to set the switch name.

Reboot the switch to enable the change in IP address and subnet mask to take effect.

For more information on the individual switches, see the following documentation:

Compaq StorageWorks Fibre Channel Storage Switch User's Guide

Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide

Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide

For more information on the DSGGB command set, see the Compaq StorageWorks SAN Switch Fabric Operating System Management Guide.

4.1.1.2 Managing the Fibre Channel Switches

You can manage the DS-DSGGA-AA, DS-DSGGA-AB, and DS-DSGGB-AB switches, and obtain switch status from the front panel, by making a telnet connection or by accessing the Web. The DS-DSGGB-AA does not have a front panel, so you must use a telnet connection or use Web access.

Before you can make a telnet connection or access the switch via the Web, you must assign an IP address and subnet mask to the Ethernet connection using the front panel or from a PC or terminal (DS-DSGGB-AA).

4.1.1.2.1 Using the Switch Front Panel

The switch front panel consists of a display and four buttons. The display is normally not active, but it lights up when any of the buttons are pressed. The display has a timer. After approximately 30 seconds of inactivity, the display will go out.

The four front panel buttons are:

Up -- Upward triangle: Scrolls the menu up (which effectively moves down the list of commands) or increases the value being displayed.

Down -- Downward triangle: Scrolls the menu down (which effectively moves up the list of commands) or decreases the value being displayed.

Note

When the up or down buttons are used to increase or decrease a numerical display, the number changes slowly at first, but changes to fast mode if the button is held down. The maximum number displayed is 255. An additional increment at a count of 255 resets the count to 0.

Tab/Esc -- Leftward triangle: Allows you to tab through multiple optional functions, for example, the fields in an IP address. You can use this button to abort an entry, which takes you to the previous menu item. If pressed repeatedly, the front panel display will turn off.

Enter -- Rightward triangle: Causes the switch to accept the input you have made and move to the next function.

4.1.1.2.2 Setting the Ethernet IP Address and Subnet Mask from the Front Panel

Before you telnet to the switch, you must connect the Ethernet cable and then set the Ethernet IP address and subnet mask.

To use the front panel to set the Ethernet address and subnet mask, follow these steps:

Press any of the switch front panel buttons to activate the display for the top-level menu. If the Configuration Menu is not displayed, press the down button repeatedly until it is displayed:
```
Select Menu:
Configuration Menu
 
```
Note

Pressing the down button selects the next lower top-level menu. The top-level menus are:
```
Configuration Menu
Operation Menu
Status Menu
Test Menu
 
```

Press Enter to display the first submenu item in the configuration menu, Ethernet IP address:
```
Ethernet IP address:
10.00.00.10
--
 
```
The underline cursor denotes the selected address field.
Use the up or down button to increase or decrease the displayed number. Use the Tab/Esc button to select the next field. Modify the address fields until you have the address set correctly.

Use Enter to accept the value and step to the next submenu item (Ethernet Submask), and then repeat step 2 to set the Ethernet subnet mask.

Press Enter to accept the Ethernet subnet mask.

Press the Tab/Esc button repeatedly to get back to the top-level menu.

Press the down button to select the Operation Menu:
```
Select Menu:
Operation Menu
 
```

If the switch is operational, place the switch off line before rebooting or you will lose any transmission in progress.
Press Enter to display the first submenu in the Operation Menu, Switch Offline:
```
Operation Menu:
Switch Offline
 
```

Press the down button until the Reboot submenu item is displayed:
```
Operation Menu:
Reboot
 
```

Press Enter. You can change your mind and not reboot:
```
Reboot
Accept?    Yes  No
 
```

Use the Tab/Esc button to select Yes. Press Enter to reboot the switch and execute the POST tests.

Note

After changing any configuration menu settings, you must reboot the switch for the change to take effect.

Refer to the switch documentation for information on other switch configuration settings.

4.1.1.2.3 Setting the DS-DSGGB-AA Ethernet IP Address and Subnet Mask from a PC or Terminal

For the DS-DSGGB-AA switch, which does not have a front panel, you must use a connection to a Windows 95/98/NT PC or video terminal to set the Ethernet IP address and subnet mask.

To set the Ethernet IP address and subnet mask for the DS-DSGGB-AA switch, follow these steps:

Connect the switch serial port to a terminal or PC COM port with a standard serial cable with a DB9 connector. Note that the serial port is only used for initial power-on self-test (POST) verification, IP address configuration, or for resetting the factory/default settings.

If you are using a PC, start a remote communication program, for example, HyperTerminal.

Set the port settings to 9600 bits per second, 8 bits per character, and no parity.

Turn on power to the switch. The switch automatically connects to the host and logs the user on to the switch as admin.

Enter the ipAddrSet command, then enter the IP address, subnet mask, and gateway address (if necessary). For example:

admin> ipAddrSet
Ethernet IP Address [10.77.77.77]: 16.142.72.54
Ethernet Subnetmask [255.255.255.0]: [Return]
Fibre Channel IP Address [none]: [Return]
Fibre Channel Subnetmask [none]: [Return]
Gateway Address [none]: [Return]
admin> logout

4.1.1.2.4 Logging In to the Switch with a Telnet Connection

Before you telnet to a Fibre Channel switch, you must set the Ethernet IP address and subnet mask.

Note

A serial port connection and a telnet session cannot both be active (at the same time) with the DS-DSGGB-AA switch. The telnet session takes precedence and the serial port session is aborted when the telnet session is started.

You can use a telnet session to log in to the switch at one of three security levels. The default user names, shown from lowest security level to highest security level, are shown in Table 4-1.

Table 4-1: Telnet Session Default User Names for Fibre Channel Switches

DSGGA	DSGGB	Description
`other`	n/a	Allows you to execute commands ending in `Show`, such as `dateShow` and `portShow`.
`user`	`user`	Allows you to execute all commands ending in `Show`, plus any commands from the help menu that do not change the state of the switch, for example, `version` and `errDump`. You can change the passwords for all users up to and including the current user's security level.
`admin`	`admin`	Provides access to all the commands that show up in the help menu. Most switch administration is done when logged in as `admin`.
`n/a`	`root`	Gives users access to an extensive command set that can significantly alter system performance. Root commands should only be used at the request of Compaq customer service.

You can set the user names and passwords for users at or below the security level of the present login level by executing the passwd command. Enter a new user name (if desired) and a new password for the user.

Notes

Use Ctrl/H to correct typing errors.
Use the logout command to log out from any telnet connection.

4.1.1.2.5 Setting the Switch Name via Telnet Session

After you set the IP address and subnet mask, you can use a telnet session to log in to the switch to complete other switch management functions or monitor switch status. For example, if a system's /etc/hosts file contains an alias for the switch's IP address, set the switch name to the alias. This allows you to telnet to the switch name from that system. Telnet from a system that has the IP address in its /etc/hosts file and set the switch address as follows:

# telnet 132.25.47.146  [Return]
User admin [Return]
Passwd        [Return]
:Admin> switchName fcsw1 [Return]
:Admin> switchName [Return]
fcsw1
:Admin>

Note

When you telnet to the switch the next time, the prompt will include the switch name, for example:
fcsw1:Admin>

4.1.2 Installing and Configuring the KGPSA PCI-to-Fibre Channel Adapter Module

The following sections discuss KGPSA installation and configuration.
4.1.2.1    Installing the KGPSA PCI-to-Fibre Channel Adapter Module

To install the KGPSA-BC or KGPSA-CA PCI-to-Fibre Channel adapter modules follow these steps. For more information, see the following documentation:

KGPSA-BC PCI-to-Optical Fibre Channel Host Adapter User Guide

64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide

Caution

Static electricity can damage modules and electronic components. We recommend using a grounded antistatic wrist strap and a grounded work surface when handling modules.

If necessary, install the mounting bracket on the KGPSA-BC module. Place the mounting bracket tabs on the component side of the board. Insert the screws from the solder side of the board.

The KGPSA-BC should arrive with the gigabit link module (GLM) installed. If not, close the GLM ejector mechanism. Then, align the GLM alignment pins, alignment tabs, and connector pins with the holes, oval openings, and board socket. Press the GLM into place.
The KGPSA-CA does not use a GLM, it uses an embedded optical shortwave multimode Fibre Channel interface.

Install the KGPSA in an open 32- or 64-bit PCI slot.

Insert the optical cable SC connectors into the KGPSA-BC GLM or KGPSA-CA SC connectors. The SC connectors are keyed to prevent their being plugged in incorrectly. Do not use unnecessary force. Do not forget to remove the transparent plastic covering on the extremities of the optical cable.

Connect the fiber-optic cables to the shortwave Gigabit Interface Converter modules (GBICs) in the DSGGA or DSGGB Fibre Channel switch.

4.1.2.2    Setting the KGPSA-BC or KGPSA-CA to Run on a Fabric

The KGPSA host bus adapter defaults to the fabric mode, and can be used in a fabric without taking any action. However, if you install a KGPSA that has been used in the loop mode on another system, you will need to reformat the KGPSA nonvolatile RAM (NVRAM) and configure it to run on a Fibre Channel fabric configuration.
Use the wwidmgr utility to determine the mode of operation of the KGPSA host bus adapter, and to set the mode if it needs changing (for example from loop to fabric).

Notes

You must set the console to diagnostic mode to use the wwidmgr utility for the following AlphaServer systems: AS1200, AS4x00, AS8x00, GS60, GS60E, and GS140. Set the console to diagnostic mode as follows:
P00>>> set mode diag Console is in diagnostic mode P00>>>

The console remains in wwid manager mode (or diagnostic mode for the AS1200, AS4x00, AS8x00, GS60, GS60E, and GS140 systems), and you cannot boot until the system is re-initialized. Use the init command or a system reset to re-initialize the system after you have completed using the wwid manager.
If you try to boot the system and receive the following error, initialize the console to get out of WWID manager mode, then reboot:
P00>>> boot warning -- main memory zone is not free P00>>> init
.
.
.
P00>>> boot

If you have initialized and booted the system, then shut down the system and try to use the wwidmgr utility, you may be prevented from doing so. If you receive the following error, initialize the system and retry the wwidmgr command:
P00>>> wwidmgr -show adapter wwidmgr available only prior to booting. Reinit system and try again. P00>>> init
.
.
.
P00>>> wwidmgr -show adapter
.
.
.

For more information on the wwidmgr utility, see the Wwidmgr User's Manual, which is on the Alpha Systems Firmware Update CD-ROM in the DOC directory.

Use the worldwide ID manager to show all KGPSA adapters:
P00>>> wwidmgr -show adapter Link is down. item adapter WWN Cur. Topo Next Topo pga0.0.0.3.1 - Nvram read failed [ 0] pga0.0.0.3.1 1000-0000-c920-eda0 FABRIC UNAVAIL pgb0.0.0.4.0 - Nvram read failed [ 1] pgb0.0.0.4.0 1000-0000-c920-da01 FABRIC UNAVAIL pgc0.0.0.5.1 - Nvram read failed. [ 2] pgc0.0.0.5.1 1000-0000-c920-cd9c FABRIC UNAVAIL [9999] All of the above.

The Link is down message indicates that one of the adapters is not available, probably due to its not being plugged into a switch. The warning message Nvram read failed indicates that the KGPSA NVRAM has not been initialized and formatted. The next topology will always be UNAVAIL for the host bus adapter that has an unformatted NVRAM. Both messages are benign and can be ignored for the fabric mode of operation. To correct the Nvram read failed situation, use the wwidmgr -set adapter command.
The previous display shows that all three KGPSA host bus adapters are set for fabric topology as the current topology, the default. When operating in a fabric, if the current topology is FABRIC, it does not matter if the next topology is Unavail, or that the NVRAM is not formatted (Nvram read failed).
If, however, the current topology is LOOP, you have to change the topology to FABRIC to operate in a fabric. You will never see the Nvram read failed message if the current topology is LOOP. The NVRAM has to have been formatted to change the current mode to LOOP.
Consider the case where the KGPSA current topology is LOOP as follows:
P00>>> wwidmgr -show adapter item adapter WWN Cur. Topo Next Topo [ 0] pga0.0.0.3.1 1000-0000-c920-eda0 LOOP LOOP [ 1] pgb0.0.0.4.0 1000-0000-c920-da01 LOOP LOOP [9999] All of the above.

If the current topology for an adapter is LOOP, set an individual adapter to FABRIC by using the item number for that adapter (for example, 0 or 1). Use 9999 to set all adapters:
P00>>> wwidmgr -set adapter -item 9999 -topo fabric Reformatting nvram Reformatting nvram

Note

The qualifier in the previous command is -topo and not -topology. You will get an error if you use -topology.

Displaying the adapter information again will show the topology that the adapters will assume after the next console initialization:
P00>>> wwidmgr -show adapter item adapter WWN Cur. Topo Next Topo [ 0] pga0.0.0.4.1 1000-0000-c920-eda0 LOOP FABRIC [ 1] pgb0.0.0.3.0 1000-0000-c920-da01 LOOP FABRIC [9999] All of the above.

This display shows that the current topology for both KGPSA host bus adapters is LOOP, but will be FABRIC after the next initialization.
A system initialization configures the KGPSAs to run on a fabric.
4.1.2.3    Obtaining the Worldwide Names of KGPSA Adapters

A worldwide name is a unique number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by the manufacturer prior to shipping. The worldwide name assigned to a subsystem never changes. You should obtain and record the worldwide names of Fibre Channel components in case you need to verify their target ID mappings in the operating system.
Fibre Channel devices have both a node name and a port name worldwide name, both of which are 64-bit numbers. Most commands you use with Fibre Channel only show the port name.
There are multiple ways to obtain the KGPSA port name worldwide name:

You can obtain the worldwide name from a label on the KGPSA module before you install it.

You can use the show dev command as follows:
P00>>> show dev
.
.
.
pga0.0.0.1.0 PGA0 WWN 1000-0000-c920-eda0 pgb0.0.0.2.0 PGB0 WWN 1000-0000-c920-da01

You can use the wwidmgr -show adapter command as follows:
P00>>> wwidmgr -show adapter item adapter WWN Cur. Topo Next Topo [ 0] pga0.0.0.4.1 1000-0000-c920-eda0 FABRIC FABRIC [ 1] pgb0.0.0.3.0 1000-0000-c920-da01 FABRIC FABRIC [9999] All of the above.

If the operating system is installed, the worldwide name of a KGPSA adapter is also displayed in the boot messages generated when the emx driver attaches to the adapter when the adapter's host system boots. Or, you can use the grep utility and obtain the worldwide name from the /var/adm/messages file as follows:

# grep wwn /var/adm/messages F/W Rev 2.20X2(1.12): wwn 1000-0000-c920-eda0 F/W Rev 2.20X2(1.12): wwn 1000-0000-c920-eda0 F/W Rev 2.20X2(1.12): wwn 1000-0000-c920-eda0
.
.
.

Record the worldwide name of each KGPSA adapter for later use.
4.1.3    Setting up the HSG80 Array Controller for Tru64 UNIX Installation

This section covers setting up the HSG80 controller for operation with Tru64 UNIX Version 5.0A and TruCluster Server Version 5.0A. For more information on installing the HSG80, see the Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 Configuration Guide or Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide.
To set up an HSG80 for TruCluster Server operation, follow these steps:

If not already installed, install the HSG80 controller(s) into the RA8000 or ESA12000 storage arrays.

If used, ensure that the external cache battery (ECB) is connected to the controller cache module(s).

Install the fiber-optic cables between the KGPSA and the switch.

Set the power verification and addressing (PVA) ID. Use PVA ID 0 for the enclosure that contains the HSG80 controller(s). Set the PVA ID to 2 and 3 on expansion enclosures (if present).

Note

Do not use PVA ID 1.
With Port-Target-LUN (PTL) addressing, the PVA ID is used to determine the target ID of the devices on ports 1 through 6 (the LUN is always zero). Valid target ID numbers are 0 through 15, excluding numbers 4 through 7. Target IDs 6 and 7 are reserved for the controller pair, and target IDs 4 and 5 are never used.
The enclosure with PVA ID 0 will contain devices with target IDs 0 through 3; with PVA ID 2, target IDs 8 through 11; with PVA ID 3, target IDs 12 through 15. Setting a PVA ID of an enclosure to 1 would set target IDs to 4 through 7, generating a conflict with the target IDs of the controllers.

Remove the program card ESD cover and insert the controller's program card. Replace the ESD cover.

Install disks into storage shelves.

Connect a terminal to the maintenance port on one of the HSG80 controllers. You need a local connection to configure the controller for the first time. The maintenance port supports serial communication with the following default values:

9600 BPS

8 data bits

1 stop bit

No parity

Connect the RA8000 or ESA12000 to the power source and apply power.

Note

The KGPSA host bus adapters must be cabled to the switch, with the system power applied before you turn power on to the RA8000/ESA12000, in order for the HSG80 to see the connection to the KGPSAs.

If an uninterruptible power supply (UPS) is used instead of the external cache battery, to prevent the controller from periodically checking the cache batteries after power is applied, enter the following command:
> set this CACHE_UPS

Note

Setting the controller variable CACHE_UPS for one controller sets it for both controllers.

From the maintenance terminal, use the show this and show other commands to verify that controllers have the current firmware version. See the Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide for information on upgrading the firmware.

To ensure proper operation of the HSG80 with Tru64 UNIX and TruCluster Server, set the the controller values as follows:
set nofailover [1] clear cli [2] set multibus copy = this [3] clear cli [4] set this port_1_topology = offline [5] set this port_2_topology = offline [5] set other port_1_topology = offline [5] set other port_2_topology = offline [5] set this port_1_topology = fabric [6] set this port_2_topology = fabric [6] set other port_1_topology = fabric [6] set other port_2_topology = fabric [6]

Remove any failover mode that may have been previously configured. [Return to example]

Prevents the command line interpreter (CLI) from reporting a misconfiguration error resulting from not having a failover mode set. [Return to example]

Puts the controller pair into multiple-bus failover mode. Ensure that you copy the configuration information from the controller known to have a good array configuration.

Note

Use the command set failover copy = this_controller to set transparent failover mode.
[Return to example]

When the command is entered to set multiple-bus failover and copy the configuration information to the other controller, the other controller will restart. The restart may set off the audible alarm (which is silenced by pressing the button on the EMU). The CLI will display an event report, and continue reporting the condition until cleared with the clear cli command. [Return to example]

Takes the ports off line and resets the topology to prevent an error message when setting the port topology. [Return to example]

Sets fabric as the switch topology. [Return to example]

Enter the show connection command as shown in Example 4-1 to determine the HSG80 connection names for the connections to the KGPSA host bus adapters. For an RA8000/ESA12000 with dual-redundant HSG80s in multiple-bus failover mode, there will be four connections for each KGPSA in the cluster (as long as all four HSG80 ports are connected to the same fabric).
For example, in a two-node cluster with two KGPSAs in each member system, and an RA8000 or ESA12000 with dual-redundant HSG80s, there will be 16 connections for the cluster. If you have other systems or clusters connected to the switches in the fabric, there will be other connections for the other systems. In Example 4-1, note that the ! (exclamation mark) is part of the connection name. The HOST_ID is the KGPSA host name worldwide name and the ADAPTER_ID is the port name worldwide name.

Example 4-1:  Determine HSG80 Connection Names

HSG80 show connection Connection Unit Name Operating system Controller Port Address Status Offset !NEWCON49 TRU64_UNIX THIS 2 230813 OL this 0 HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON50 TRU64_UNIX THIS 1 230813 OL this 0 HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON51 TRU64_UNIX THIS 2 230913 OL this 0 HOST_ID=1000-0000-C920-EDEB ADAPTER_ID=1000-0000-C920-EDEB !NEWCON52 TRU64_UNIX THIS 1 230913 OL this 0 HOST_ID=1000-0000-C920-EDEB ADAPTER_ID=1000-0000-C920-EDEB !NEWCON53 TRU64_UNIX OTHER 1 230913 OL other 0 HOST_ID=1000-0000-C920-EDEB ADAPTER_ID=1000-0000-C920-EDEB !NEWCON54 TRU64_UNIX OTHER 1 230813 OL other 0 HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON55 TRU64_UNIX OTHER 2 230913 OL other 0 HOST_ID=1000-0000-C920-EDEB ADAPTER_ID=1000-0000-C920-EDEB !NEWCON56 TRU64_UNIX OTHER 2 230813 OL other 0 HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01
.
.
.
!NEWCON61 TRU64_UNIX THIS 2 210513 OL this 0 HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON62 TRU64_UNIX OTHER 1 210513 OL other 0 HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER 1 offline 0 HOST_ID=1000-0000-C921-0943 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER 1 210413 OL other 0 HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON65 TRU64_UNIX OTHER 2 210513 OL other 0 HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C
.
.
.
!NEWCON74 TRU64_UNIX THIS 2 210413 OL this 0 HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON75 TRU64_UNIX THIS 2 offline 0 HOST_ID=1000-0000-C921-0A75 ADAPTER_ID=1000-0000-C921-0A75 !NEWCON76 TRU64_UNIX THIS 1 210413 OL this 0 HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON77 TRU64_UNIX THIS 1 210513 OL this 0 HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON78 TRU64_UNIX THIS 2 offline 0 HOST_ID=1000-0000-C920-CB77 ADAPTER_ID=1000-0000-C920-CB77 !NEWCON79 TRU64_UNIX OTHER 1 offline 0 HOST_ID=1000-0000-C920-CB77 ADAPTER_ID=1000-0000-C920-CB77
.
.
.

Note

You can change the connection name with the HSG80 CLI RENAME command. For example, assume that member system pepicelli has two KGPSA Fibre Channel host bus adapters, and that the worldwide name for KGPSA pga is 1000-0000-C920-DA01. Example 4-1 shows that the connections for pga are !NEWCON49, !NEWCON50, !NEWCON54, and !NEWCON56. You could change the name of !NEWCON49 to indicate that it is the first connection (of four) to pga on member system pepicelli as follows:
HSG80> rename !NEWCON49 pep_pga_1

For each connection to your cluster, verify that the operating system is TRU64_UNIX and the unit offset is 0. Search the show connection display for the worldwide name of each of the KGPSA adapters in your cluster member systems. If the operating system and offsets are incorrect, set them, then restart both controllers as follows:
HSG80> set !NEWCON49 unit_offset = 0 [1] HSG80> set !NEWCON49 operating_system = TRU64_UNIX [2] HSG80> restart other [3] HSG80> restart this [3]
.
.
.
HSG80> show connection [4]

Set the relative offset for LUN numbering to 0. You can set the unit_offset to nonzero values, but use caution. Make sure you understand the impact. [Return to example]

Specify that the host environment connected to the Fibre Channel port is TRU64_UNIX. You must change each connection to TRU64_UNIX. This is very important. Failure to set this to TRU64_UNIX will prevent your system from booting correctly, recovering from run-time errors, or from booting at all. The default operating system is Windows NT, and NT uses a different SCSI dialect to talk to the HSG80 controller. [Return to example]

Restart both controllers to cause all changes to take effect. [Return to example]

Enter the show connection command once more and verify that all connections have the offsets set to 0 and the operating system is set to TRU64_UNIX. [Return to example]

Note

If the fiber-optic cables are not properly installed, there will be inconsistencies in the connections shown.

Set up the storage sets as required for the applications to be used. An example is provided in Section 5.1.1.

4.1.3.1    Obtaining the Worldwide Names of HSG80 Controller

The RA8000 or ESA12000 is assigned a worldwide name when the unit is manufactured. The worldwide name (and checksum) of the unit appears on a sticker placed above the controllers. The worldwide name ends in zero (0), for example, 5000-1FE1-0000-0D60. You can also use the SHOW THIS_CONTROLLER Array Controller Software (ACS) command.
For HSG80 controllers, the controller port IDs are derived from the RA8000/ESA12000 worldwide name as follows:

In a subsystem with two controllers in transparent failover mode, the controller port IDs increment as follows:

Controller A and controller B, port 1 -- worldwide name + 1

Controller A and controller B, port 2 -- worldwide name + 2

For example, using the worldwide name of 5000-1FE1-0000-0D60, the following port IDs are automatically assigned and shared between the ports as a REPORTED PORT_ID on each port:

Controller A and controller B, port 1 -- 5000-1FE1-0000-0D61

Controller A and controller B, port 2 -- 5000-1FE1-0000-0D62

In a configuration with dual-redundant controllers in multiple-bus failover mode, the controller port IDs increment as follows:

Controller A port 1 -- worldwide name + 1

Controller A port 2 -- worldwide name + 2

Controller B port 1 -- worldwide name + 3

Controller B port 2 -- worldwide name + 4

For example, using the worldwide name of 5000-1FE1-0000-0D60, the following port IDs are automatically assigned and shared between the ports as a REPORTED PORT_ID on each port:

Controller A port 1 -- 5000-1FE1-0000-0D61

Controller A port 2 -- 5000-1FE1-0000-0D62

Controller B port 1 -- 5000-1FE1-0000-0D63

Controller B port 2 -- 5000-1FE1-0000-0D64

Because the HSG80 controller's configuration information and worldwide name is stored in nonvolatile random-access memory (NVRAM) on the controller, there are different procedures for replacing HSG80 controllers in an RA8000 or ESA12000:

If you replace one controller of a dual-redundant pair, the NVRAM from the remaining controller retains the configuration information (including worldwide name). When you install the replacement controller, the existing controller transfers configuration information to the replacement controller.

If you have to replace the HSG80 controller in a single controller configuration, or if you must replace both HSG80 controllers in a dual-redundant configuration simultaneously, you have two options:

If the configuration has been saved to disk (with the INITIALIZE DISKnnnn SAVE_CONFIGURATION or INITIALIZE storageset-name SAVE_CONFIGURATION option), you can restore it from disk with the CONFIGURATION RESTORE command.

If you have not saved the configuration to disk, but the label containing the worldwide name and checksum is still intact, or you have recorded the worldwide name and checksum (Section 4.1.3.1) and other configuration information, you can use the command-line interface (CLI) commands to configure the new controller and set the worldwide name. Set the worldwide name as follows:
SET THIS NODEID=nnnn-nnnn-nnnn-nnnn checksum