TruCluster Server Cluster Hardware Configuration Technical Update for the MSA1000 February 2004 Product Version: TruCluster Server Version 5.1A and 5.1B Operating System and Version: Tru64 UNIX Version 5.1A and 5.1B This technical update describes how to configure the StorageWorks Modular Smart Array 1000 (MSA1000) Fibre Channel storage system in a TruCluster Server environment.
© Copyright 2004 Hewlett-Packard Development Company, L.P. Microsoft®, Windows®, and Windows NT® are trademarks of Microsoft Corporation in the U.S. and/or other countries. UNIX® and The Open Group™ are trademarks of The Open Group in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective owners. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.
Contents About This Technical Update 1 MSA1000 Fibre Channel Storage System 1.1 1.2 1.3 2 2.2 Supported AlphaServer Systems and Tru64 UNIX and TruCluster Server Software .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . General Requirements and Restrictions . .. . .. . .. . .. . . .. . .. . .. . .. . 2-1 2-2 TruCluster Server Configurations Using an MSA1000 for Storage 3.1 3.2 3.3 4 1-1 1-1 1-2 Requirements and Restrictions 2.1 3 General Overview . . .. . .. . .. . . .. . .. .
.9.1 Set the Device Unit Number .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.9.2 Displaying Valid Boot Devices . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.10 Installing the Software . . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.10.1 Install the Base Operating System . . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.10.2 Reset the bootdef_dev Console Environment Variable . . .. . 4.10.
4-19 4-20 4-21 4-22 4-23 4-24 Sample Fibre Channel Device Names .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Disks Available for Software Installation .. . .. . .. . .. . . .. . .. . .. . .. . Using the hwmgr to Display Devices with the Identifier Qualifier .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Using the hwmgr to Display Devices with the MSA1000 Qualifier .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . ..
About This Technical Update This technical update provides important information about using the StorageWorks Modular Smart Array 1000 (MSA1000) Fibre Channel storage system in a TruCluster Server configuration. Audience If you plan to use an MSA1000 Fibre Channel storage system in a TruCluster configuration, read this addendum to the TruCluster Server Cluster Hardware Configuration manual. Organization This manual is organized as follows: Chapter 1 Introduces the MSA1000 Fibre Channel storage system.
1 MSA1000 Fibre Channel Storage System This technical update to the TruCluster Server Cluster Hardware Configuration manual provides important information about support for the StorageWorks Modular Smart Array 1000 (MSA1000) Fibre Channel storage system designed for the entry-level to midrange storage area network (SAN). It has been qualified with the Tru64 UNIX and TruCluster Server Version 5.1A and 5.1B products in a TruCluster Server configuration.
1.3 MSA1000 Overview The MSA1000 Fibre Channel storage array provides 2-Gb connections to the host with support for 1-Gb Fibre Channel connections. The MSA1000 consists of a 4U (17.6 cm (7.0 inches)) rack mount controller shelf with an attached disk enclosure that holds up to 14 1-inch Ultra3 SCSI disk drives. The MSA1000 provides the following RAID support: • RAID0: Striping, no fault tolerance. See RAID1+0. • RAID1: Mirroring. See RAID1+0. • RAID1+0: Striping and Mirroring.
The MSA1000 provides Ultra3 SCSI connections to the Model 4314R or 4354R disk enclosures, which house universal 1-inch Ultra3 hard drives. There may be a maximum of four SCSI buses: two internal SCSI buses for the MSA1000 enclosure (SCSI buses 0 and 1), and two external SCSI buses in the disk enclosures served by the SCSI I/O module (SCSI buses 2 and 3). The MSA1000 drive enclosure has a split bus with two SCSI buses: SCSI bus 0 serves bays 1 through 7, and SCSI bus 1 serves bays 8 through 14.
Figure 1-3: SCSI Bus IDs for Model 4353R Disk Enclosure (Box 2) BAY 1 2 SCSI Bus SCSI ID 3 4 5 6 7 8 9 SCSI Bus 2 0 1 2 3 4 10 11 12 13 14 SCSI Bus 3 5 8 0 1 2 3 4 5 8 ZK-2009U-AI 1-4 MSA1000 Fibre Channel Storage System
2 Requirements and Restrictions This chapter describes the hardware requirements and restrictions for use of an MSA1000 Fibre Channel storage array in a TruCluster Server cluster. It includes lists of supported Tru64 UNIX operating system and TruCluster Server versions, AlphaServer systems, standard reference manual (SRM) firmware, Fibre Channel host bus adapters, and other general restrictions. 2.
• On the download patches page: - Select a server in your region. - Select the desired format for the download (zip, gzip, tar, or download a script that will ftp the patches). - Click on the download » button.
• TruCluster Server supports clusters with up to eight member systems. An MSA1000 may be connected to no more than four of these cluster member systems. • Fibre Channel arbitrated loop (FC-AL), including the MSA Hub 2/3, is not supported with the MSA1000 at this time. • The MSA Fabric Switch 6 (with five external and one internal ports) is not supported at this time. • If you install a second controller, you must also install a second Fibre Channel I/O module or MSA SAN Switch 2/8.
3 TruCluster Server Configurations Using an MSA1000 for Storage This chapter provides illustrations of TruCluster Server configurations using an MSA1000 Fibre Channel storage array. 3.1 A Single Controller MSA1000 Cluster Configuration A TruCluster Server configuration with a single-controller MSA1000 is shown in Figure 3-1.
Figure 3-1: Single-Point-of-Failure Configuration Using a Single Fibre Channel I/O Module Network Member System 1 Member System 2 Cluster Interconnect Fibre Channel Host Bus Adapter Fibre Channel Host Bus Adapter Fibre Channel Switch FC I/O Module SCSI I/O Module MSA1000 Model 4354R Disk Enclosure ZK-2011U-AI If a second MSA1000 controller and associated Fibre Channel I/O module is installed in the configuration shown in Figure 3-1, the Fibre Channel switch and single Fibre Channel host bus adapter
3.2 No-Single-Point-of-Failure Cluster Configurations Figure 3-2 is a no-single-point-of-failure (NSPOF) TruCluster Server configuration using two MSA1000 controllers. Each MSA1000 controller has a corresponding Fibre Channel I/O module. This configuration uses two Fibre Channel switches in a dual fabric to provide the input to the Fibre Channel I/O modules. A Model 4354R disk enclosure provide extra disk storage.
Figure 3-2: NSPOF TruCluster Server MSA1000 Configuration Using Fibre Channel Switches, Fibre Channel I/O Modules, and a Split-Bus Disk Enclosure Network Member System 1 Member System 2 Cluster Interconnect Fibre Channel Host Bus Adapter Fibre Channel Host Bus Adapter Fibre Channel Host Bus Adapter Fibre Channel Host Bus Adapter Fibre Channel Switches FC I/O Module FC I/O Module SCSI I/O Module MSA1000 Model 4354R Disk Enclosure ZK-2014U-AI 3-4 TruCluster Server Configurations Using an MSA1000 fo
Figure 3-3 is the same as Figure 3-2, except for the use of two single-bus Model 4314R disk enclosures for additional storage.
Figure 3-4 is an NSPOF TruCluster Server configuration using an MSA1000 with two controllers and MSA SAN Switch 2/8 Fibre Channel switches as inputs to the controllers. An MSA SAN Switch 2/8 is required for each controller.
3.3 Unsupported and Illegal Cluster Configurations Figure 3-5 shows a TruCluster Server configuration that is not supported. The MSA1000 controllers operate in active/passive mode; one controller is active while the other controller is passive. In the configuration shown in Figure 3-5, both cluster member systems try to make their controller active, creating a ping-pong effect. Both systems would receive many errors, and no useful I/O would be accomplished.
The configuration shown in Figure 3-6 is an illegal configuration. Tru64 UNIX requires that the Fibre Channel host bus adapter be connected to a Fibre Channel switch; the Fibre Channel host bus adapter cannot be connected directly to the array controller or Fibre Channel I/O module.
4 Preparing the MSA1000 for TruCluster Server Use The topics in this chapter provide information on how to prepare an MSA1000 Fibre Channel storage system and associated disks for Tru64 UNIX and TruCluster Server installation. The base operating system and TruCluster Server software will be installed on MSA1000 storage. To install Tru64 UNIX and TruCluster Server on MSA1000 disks, follow these steps: 1.
4.1 External Fibre Channel Switch Installation If the MSA1000 has an installed Fibre Channel I/O module, you must use external Fibre Channel switches. An NSPOF configuration requires redundant MSA1000 controllers and two Fibre Channel I/O modules. Ensure that the member systems, the Fibre Channel switches, and the MSA1000 are placed within the lengths of the optical cables that you will be using.
_____________________ 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. 1. Using the documentation that came with your Fibre Channel host bus adapter, install the Fibre Channel adapter in an open 64-bit PCI slot. 2. Set the Fibre Channel adapter to run on fabric (see Section 4.2.2) 3.
The display in Example 4-1 shows that both Fibre Channel 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). You may view the Nvram read failed message as an error, and may not like the fact that the next topology is Unavail.
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 as shown in Example 4-2. 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 [ 0] pga0.0.0.2.0 1000-0000-c922-4aac [ 1] pgb0.0.0.4.0 1000-0000-c924-4b7b [9999] All of the above. Cur.
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. 4.2.3 Obtain the Fibre Channel Adapter Worldwide Name A worldwide name (WWN) 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.
Obtain the Fibre Channel host bus adapter port WWN using the wwidmgr -show port command as follows: P00>>> wwidmgr -show port pga0.0.0.7.0 Link is down. pgb0.0.0.8.0 Link is down. [0] 1000-0000-c927-242e [1] 1000-0000-c927-2e67 ______________________ Note _______________________ Use the wwidmgr -show port command before connecting the Fibre Channel host bus adapters to the Fibre Channel switches.
4.3 Install and Set Up the MSA1000 Storage System If not already completed, install the MSA1000 in the rack, using the documentation that came with the MSA1000 and follow these steps: 1. If necessary, upgrade the MSA1000 firmware to the latest firmware version, which at the time this technical update was re-released, is v4.24. 2. Install additional disk enclosures. You can install two StorageWorks Model 4314R or one StorageWorks Model 4354R disk enclosure. 3. Install disks in the disk enclosures. 4.
If the MSA1000 has installed MSA SAN Switch 2/8s, install the fiber-optic cables as follows (see Figure 3-4): • Install an SC-to-LC or LC-to-LC fiber-optic cable between the first Fibre Channel host bus adapter of each member system and the leftmost MSA SAN Switch 2/8. • Install a second SC-to-LC or LC-to-LC fiber-optic cable between the second Fibre Channel host bus adapter of each member system and the rightmost MSA SAN Switch 2/8. 4.
• Flow Control: None After the terminal, or terminal emulator is set up, type an Enter or two to obtain the CLI> prompt. The MSA1000 accepts CLI commands in upper- or lowercase. All commands will be typed in uppercase in this document. See the hp StorageWorks modular SAN array 1000 user guide for more information on CLI commands than is provided in this technical update. ______________________ Note _______________________ MSA1000 commands must be typed completely; they cannot be abbreviated. 4.
To set up storage for a Tru64 UNIX and TruCluster Server configuration using storage as shown in Table 4-2, follow these steps: 1. Change the MSA1000 prompt if you want to. You can use up to 25 alphanumeric characters. The SET PROMPT command shown in Example 4-3 changes the MSA1000 prompt to MSA1000-1> .
Example 4-4: Displaying the MSA1000 Connections (cont.
Example 4-5: Changing the Connection Profile to Tru64 MSA1000-1> MSA1000-1> MSA1000-1> MSA1000-1> ADD ADD ADD ADD CONNECTION CONNECTION CONNECTION CONNECTION swiss-emx0 WWPN=10000000-C927242E PROFILE=Tru64 swiss-emx1 WWPN=10000000-C9272E67 PROFILE=Tru64 rye-emx0 WWPN=10000000-C92C2C81 PROFILE=Tru64 rye-emx1 WWPN=10000000-C92C2C10 PROFILE=Tru64 Use the SHOW CONNECTIONS command once again to verify that the connection name and profile has been changed, as shown in Example 4-6.
inherited an MSA1000 that was used previously. Use the SHOW UNIT command, as shown in Example 4-7, to determine if there are any existing LUNs. Example 4-7: Using the SHOW UNIT Command to Display Existing LUNs MSA1000-1> SHOW UNIT . . . If there are existing LUNs that you want to remove, delete one LUN at a time with the DELETE UNIT command, as shown in Example 4-8. ____________________ Note _____________________ If more than one LUN has been created, only the last LUN created may be deleted.
Example 4-9: Displaying the Installed Disks MSA1000-1> SHOW DISKS Disk List: (box,bay) (bus,ID) Disk101 (1,01) (0,00) Disk102 (1,02) (0,01) Disk103 (1,03) (0,02) Disk104 (1,04) (0,03) Disk105 (1,05) (0,04) Disk106 (1,06) (0,05) Disk107 (1,07) (0,08) Disk108 (1,08) (1,00) Disk109 (1,09) (1,01) Disk110 (1,10) (1,02) Disk111 (1,11) (1,03) Disk112 (1,12) (1,04) Disk113 (1,13) (1,05) Disk114 (1,14) (1,08) 6. Size 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.1GB 9.
Example 4-10: Creating the Storage Units (LUNs) (cont.) MSA1000-1> ADD UNIT 5 RAID_LEVEL=1 DATA="DISK101 DISK102 DISK108 DISK109" SIZE=1MB A unit cannot be smaller than 15MB. . . . 6 MSA1000-1> ADD UNIT 5 RAID_LEVEL=1 DATA="DISK101 DISK102 DISK108 DISK109" SIZE=15MB 6 MSA1000-1> ADD UNIT 6 RAID_LEVEL=1 DATA="DISK101 DISK102 DISK108 DISK109" SIZE=3GB 7 . . . MSA1000-1> ADD UNIT 7 RAID_LEVEL=1 DATA="DISK101 DISK102 DISK108 DISK109" SIZE=3GB . . . 1 8 Create the storage unit for the Tru64 UNIX disk.
7 Create the boot disk for member 1. 8 Create the boot disk for member 2. ____________________ Note _____________________ You should fill in Table A-2 as you progress. 7. If you want to, add a spare disk to protect against a failed disk. If you add a spare disk to storage unit 1, that spare is assigned to any other storage units that use the same disks as storage unit 1, in our case, disks 101, 102, 108, and 109. You can assign one disk drive to be a spare for several arrays of disks.
Example 4-12: Displaying Information About the Storage Unit (cont.) Disk103: Box 1, Bay 03, (SCSI bus 0, SCSI id 2) 9 Logical Volume Raid Level: MIRROR FAULT TOLERANCE (Raid 1) 10 stripe_size=128kB 11 Logical Volume Capacity : 2,047MB 12 MSA1000-1> SHOW UNIT 7 Unit 7: In PDLA mode, Unit 7 is Lun 8; In VSA mode, Unit 7 is Lun 7.
performed on the drive. Mirror status is not provided until after the first write. 8 Lists the disks used by this LUN. 9 A list of spare disks assigned to this LUN. 10 The RAID level. 11 The stripe size. 12 The total capacity of this logical volume 9. When you create the unit with the ADD UNIT command, the unit ID is automatically assigned to the LUN number as can be seen in Example 4-12.
Example 4-13: Changing a LUN Unit ID MSA1000-1> MSA1000-1> MSA1000-1> MSA1000-1> MSA1000-1> MSA1000-1> MSA1000-1> SET SET SET SET SET SET SET UNIT_ID UNIT_ID UNIT_ID UNIT_ID UNIT_ID UNIT_ID UNIT_ID 1 2 3 4 5 6 7 101 102 103 104 105 106 107 1 2 3 4 5 6 7 1 Change the unit ID of storage unit 1, LUN 2 to unit ID 101. 2 Change the unit ID of storage unit 2, LUN 3 to unit ID 102. 3 Change the unit ID of storage unit 3, LUN 4 to unit ID 103.
Example 4-14: Creating an Access Control List for TruCluster Server Storage Units MSA1000-1> ADD ACL CONNECTION=swiss-emx0 UNIT=1-7 1 Enabling ACL. Allowing 10000000-C927242E access to unit 1 2 3 4 5 6 7. 2 MSA1000-1> ADD ACL CONNECTION=swiss-emx1 UNIT=1-7 Enabling ACL. Allowing 10000000-C9272E67 access to unit 1 2 3 4 5 6 7. MSA1000-1> ADD ACL WWPN=10000000-C92C2C81 UNIT=1-7 3 Enabling ACL. Allowing 10000000-C92C2C81 access to unit 1 2 3 4 5 6 7.
4.9 Setting the Device Unit Number and Verifying Valid Boot Devices This section covers the remaining steps you must complete before you install the Tru64 UNIX and TruCluster Server software: 1. Set the device unit number of the disk where you will install the base operating system software, and set the device unit number of the first cluster member boot disk. Setting the device unit number allows the console and installation scripts to recognize the disks (see Section 4.9.1). 2.
P00>>> init . . . P00>>> wwidmgr -clear all P00>>> show wwid* wwid0 wwid1 wwid2 wwid3 P00>>> show n* N1 N2 N3 N4 ____________________ Note _____________________ The console only creates devices for which the wwidn console environment variable has been set, and that are accessible through an MSA1000 N_Port as specified by the Nn console environment variable also being set. These console environment variables are set with the wwidmgr -quickset or wwidmgr -set wwid commands.
Example 4-16: Setting the Device Unit Number for the BOS Installation Disk P00>>> wwidmgr -quickset -udid 101 Disk assignment and reachability after next initialization: 6008-05f3-0001-27e0-0000-0000-ca7b-0075 via adapter: dga101.1001.0.7.0 3 pga0.0.0.7.0 4 dga101.1002.0.7.0 pga0.0.0.7.0 dgb101.1001.0.8.0 dgb101.1002.0.8.0 pgb0.0.0.8.0 pgb0.0.0.8.
Example 4-17: Setting the Device Unit Number for the First Cluster Member Boot Disk (cont.) 6008-05F3-0001-27E0-0000-0000-B98B-007A via adapter: dga106.1001.0.7.0 pga0.0.0.7.0 dga106.1002.0.7.0 pga0.0.0.7.0 dgb106.1001.0.8.0 pgb0.0.0.8.0 dgb106.1002.0.8.0 pgb0.0.0.8.
n* command shows that the units are accessible through two controller N_Ports, as shown in Example 4-18.
4.10 Installing the Software This section covers the installation of the Tru64 UNIX and TruCluster Server software: 1. Install the base operating system (see Section 4.10.1). 2. If you are not installing the TruCluster Server software, set the bootdef_dev console environment variable to ensure that there is a path to the boot disk if the RAID array controllers have failed over (see Section 4.10.2).
Example 4-20: Disks Available for Software Installation (cont.) 9) dsk78 3.0 SCSI MSA1000 IDENTIFIER=106 Record the /dev/disk/dskn value for the Tru64 UNIX disk in Table A-2. For the example we are using, identifier 101 is dsk73 (see Example 4-20 and Table 4-2.) Complete the installation, following the instructions in the Tru64 UNIX Installation Guide for your version of the operating system.
If you have an NSPOF configuration, use device names for at least two host bus adapters. For example, to ensure that you have a connected boot path in case of a failed host bus adapter or controller failover, choose device names for multiple host bus adapters and each controller port.
For more information on using the ffauto and ffnext console environment variables, see the wwidmgr User’s Manual. 2. Set the bootdef_dev console environment variable for the base operating system boot disk to a comma-separated list of several of the boot paths that show up in the reachability display (wwidmgr -show reachability). You must initialize the system to use any of the device names in the bootdef_dev variable as follows: P00>>> set bootdef_dev \ dga101.1001.0.7.0, dga101.1002.0.7.0, \ dgb101.
Example 4-21: Using the hwmgr to Display Devices with the Identifier Qualifier # hwmgr view dev | grep IDENTIFIER HWID: Device Name Mfg Model Location -------------------------------------------------------------------85: /dev/disk/dsk11c DEC HSG80 IDENTIFIER=6 147: /dev/disk/dsk73c COMPAQ MSA1000 VOLUME IDENTIFIER=101 148: /dev/disk/dsk74c COMPAQ MSA1000 VOLUME IDENTIFIER=102 149: /dev/disk/dsk75c COMPAQ MSA1000 VOLUME IDENTIFIER=103 150: /dev/disk/dsk76c COMPAQ MSA1000 VOLUME IDENTIFIER=104 151: /dev/disk
______________________ Note _______________________ You must label the disks before you install cluster software. 4.10.4 Label the Disks to Be Used to Create the Cluster Before you run clu_create to create the first cluster member or clu_add_member to add subsequent cluster members, you must label the disks to be used for cluster software. On the system where you installed the Tru64 UNIX operating system, if you have not already done so, boot the system.
1. On the system where you installed the Tru64 UNIX operating system and TruCluster Server software, boot the system into the cluster as a single-member cluster. 2. Referring to the TruCluster Server Cluster Installation manual procedures, use clu_add_member to add a cluster member. Before you boot the system being added to the cluster, on the newly added cluster member: a.
If it is not set to multiple paths, enter the wwidmgr -show reachability command to determine the paths to the boot disk. An example of the reachability display is shown in Example 4-17. Set the bootdef_dev console environment variable, as shown in step 2 of Section 4.10.2.
A Worldwide Names, File System, Unit Number, Unit ID, Device Name, and Disk Name Table A-1: Fibre Channel Host Bus Adapter Worldwide Names Cluster Member Fibre Channel Adapter Port Worldwide Name emx0 Member 1 emx1 emx0 Member 2 emx1 emx0 Member 3 emx1 emx0 Member 4 emx1 Table A-2: Storage Allocation for TruCluster Server Installation File System or Disk Size Unit Number Unit ID Device Name dskn Tru64 UNIX disk Cluster root (/) Cluster /usr Cluster /var Quorum disk Member 1 boot disk Member 2 b
Index Numbers and Special Characters 164604-B21, 2-3, 4-8 259992-001, 4-9 341174-B21, 2-3, 4-8 341175-B21, 2-3, 4-8 3X-BC56J-02, 2-3, 4-8 3X-BC56J-03, 2-3, 4-8 3X-BC56J-04, 2-3, 4-8 A access control list ( See ACL ) ACL controlling access with, 4-20 setting, 4-20 verifying, 4-21 active/passive mode, 2-3, 3-7 add ACL command, 4-20 add connection command, 4-12 add spare command, 4-17 add unit command, 4-15 C CLI terminal setup, 4-9 CLI command add ACL, 4-20 add connection, 4-12 add spare, 4-17 add unit, 4-
disk enclosures model 4314R, 1-2 model 4354R, 1-2 disklabel command, 4-32 disks available for software installation, overview, 4-2 file /var/adm/messages, 4-7 H 4-27 hardware configuration Fibre Channel host bus adapter, maximum number, 1-2 number of, 1-2 4-3 verifying FCA topology, 4-3 hwmgr command -view dev, 4-30, 4-31 E Ethernet switch 10Base-T Ethernet connection, 4-2 F fabric mode, 4-3 failure to boot, 4-5 ffauto console environment variable, 4-29 ffnext console environment variable, 4-29 Fibr
creating storage units, 4-15 deleting a unit, 4-14 disk drive compatibility, 1-2 displaying installed disks, 4-14 displaying the storage unit, 4-17 FC I/O module, 1-2 Fibre Channel compatibility, 1-2 installing disk enclosure power cables, 4-9 installing fiber-optic cables, 4-8 installing SCSI cables, 4-8 MSA Hub 2/3, 1-2 MSA SAN switch 2/8, 1-2 setting the profile, 4-12 software support for, 1-1 supported Fibre Channel adapters, 2-2 supported Fibre Channel connections, 1-2 supported software versions, 2-1
Fibre Channel adapters, 2-2 software versions, 2-1 system boot problem, 4-5 system reset after using wwidmgr, 4-5 W WorldWide ID Manager ( See wwidmgr, wwidmgr command ) worldwide name ( See WWN ) T WWID topology, 4-3, 4-5 U Ultra3 SCSI, 1-3 V ( See WWN ) wwidmgr failure to boot, 4-5 unavailable, 4-5 wwidmgr command, 4-23 -clear, 4-22, 4-23 -quickset, 4-22, 4-23, 4-24, 4-25, 4-33 valid boot devices, 4-25 /var/adm/messages file, 4-7 variable ( See console environment variable ) volume set address
