Manuale d’uso / di manutenzione del prodotto AA-RHGWC-TE del fabbricante Compaq
Vai alla pagina of 362
T ruCluster Ser v er Hardware Configur ation Part Number: AA-RHGWC-TE August 2000 Product V er sion: T ruCluster Server V ersion 5.1 Operating System and V ersion: T ru64 UNIX V ersion 5.1 This manual describes how to configure the hardware for a T ruCluster™ Server environment.
© 2000 Compaq Computer Corporation COMP AQ and the Compaq logo Registered in U.S. Patent and T rademark Office. Alpha, AlphaServer , StorageW orks, T ruCluster , and T ru64 are trademarks of Compaq Information T echnologies Group, L.P . Microsoft and Windows are trademarks of Microsoft Corporation.
Contents About This Manual 1 Introduction 1.1 The T ruCluster Server Product . . . . . . . . . ....... ...... ....... ...... .. 1–1 1.2 Memory Requirements . . . ....... ...... ....... ...... ....... ...... ..... 1–2 1.3 Minimum Disk Requirements .
2.6 SCSI Signal Converters . . ....... ...... ....... ...... ....... ...... ..... 2 – 10 2.7 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs . . . . . . . . . . . 2 – 11 2.8 SCSI Cables . . . .... ...... ....... ...... ...... ....... ...... ....... ...
4.3.1 Installation of a KZPBA-CB Using Internal T ermination for a Radial Configuration . . . . . . . . . . ....... ...... ....... ...... .. 4 – 7 4.3.2 Displaying KZPBA-CB Adapters with the show Console Commands . . . . . . . . . . . . .......... .
6.2.2.2 Fabric ....... ...... ....... ...... ....... ...... ....... ...... ..... 6 – 7 6.2.2.3 Arbitrated Loop T opology . . . . . . ....... ...... ....... ...... .. 6 – 8 6.3 Example Fibre Channel Configurations Supported by T ruCluster Server . .
6.6.2 Install the T ru64 UNIX Operating System . . . ....... ...... .. 6 – 51 6.6.3 Determining /dev/disk/dskn to Use for a Cluster Installation . . . . . . . . . . . . .......... ...... ....... ...... ....... ...... .. 6 – 51 6.6.4 Label the Disks to Be Used to Create the Cluster .
8.2.2 Cabling the DS-TZ89N-VW T ape Drives . . . . . . ....... ...... .. 8 – 8 8.2.3 Setting the DS-TZ89N-T A SCSI ID . . . . . . . . . . . . .... ...... ..... 8 – 9 8.2.4 Cabling the DS-TZ89N-T A T ape Drives . . . . . . . ....... ...... .. 8 – 9 8.
8.10.5 Connecting the TL895 T ape Library to the Shared SCSI B u s .. ...... .......... ....... ...... ...... ....... ...... ....... ...... .. 8 – 48 8.11 Preparing the TL893 and TL896 Automated T ape Libraries for Shared SCSI Bus Usage . . . . . . .
8.13.3.1 ESL9326D Enterprise Library Robotic and T ape Drive Required Firmware . . . . . . . . . . . . . ....... ...... ....... ...... .. 8 – 75 8.13.3.2 Library Electronics and T ape Drive SCSI IDs . . . . . . . . . . 8 – 75 8.13.3.3 ESL9326D Enterprise Library Internal Cabling .
9.4.3.2 Cabling an HSZ20 in a Cluster Using External T ermination . . . . . . ....... ...... ....... ...... ....... ...... ..... 9 – 28 9.4.4 Cabling an HSZ40 or HSZ50 RAID Array Controller in a Radial Configuration with an UltraSCSI Hub . . . . . .
5 – 1 Running the mc_cable T est . . . . . . . . . . . . . . ....... ...... ....... ...... .. 5 – 13 6 – 1 Determine HSG80 Connection Names ....... ...... ....... ...... .. 6 – 31 6 – 2 Setting Up the Mirrorset ....... ...... ....... ...... .
1 – 8 NSPOF Fibre Channel Cluster Using HSG80s in Multiple-Bus Failover Mode ....... ...... ....... ...... ....... ...... ....... ...... ..... 1 – 16 2 – 1 PCI Backplane Slot Layout . . . . . . . . . . . . . . ....... ...... ....... ...... .. 2 – 2 3 – 1 VHDCI T rilink Connector (H8861-AA) .
8 – 1 TZ88N-V A SCSI ID Switches . . . . . . . . . . . ....... ...... ....... ...... .. 8 – 2 8 – 2 Shared SCSI Buses with SBB T ape Drives . . . . . . . . ....... ...... .. 8 – 4 8 – 3 DS-TZ89N-VW SCSI ID Switches . . . . . . ....... ......
9 – 15 T ruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller . . . . . ....... ...... ....... ...... ....... ...... ....... ...... ..... 9 – 31 10 – 1 KZPSA-BB T ermination Resistors .
8 – 9 TL894 Default SCSI ID Settings . . . . . . . ....... ...... ....... ...... .. 8 – 37 8 – 10 Hardware Components Used to Create the Configuration Shown in Figure 8 – 1 2 .... ....... ...... ....... ...... ....... ...... ..... 8 – 42 8 – 11 TL895 Default SCSI ID Settings .
About This Manual This manual describes how to set up and maintain the hardware configuration for a T ruCluster ™ Server cluster . A udience This manual is for system administrators who will set up and configure the hardware before installing the T ruCluster Server software.
Chapter 7 Describes the use of AlphaServer ™ GS80, GS160, or GS320 hardware partitions in a T ruCluster Server configuration. Chapter 8 Describes how to configure a shared SCSI bus for tape drive, tape loader , or tape library usage.
The StorageW orks ™ UltraSCSI Configuration Guidelines document provides guidelines regarding UltraSCSI configurations. For information about setting up a RAID subsystem, see the following manuls as.
• Compaq StorageW orks SAN Switch 8 Installation and Hardware Guide • Compaq StorageW orks SAN Switch 16 Installation and Hardware Guide • Compaq StorageW orks Fibre Channel SAN Switch 8-EL Inst.
• For more information on the ESL9326D Enterprise Library , see the following Compaq StorageW orks ESL9000 Series T ape Library documentation: – Unpacking and Installation Guide – Reference Guid.
Reader’s Comments Compaq welcomes any comments and suggestions you have on this and other T ru64 UNIX manuals. Y ou can send your comments in the following ways: • Fax: 603-884-0120 Attn: UBPG Publications, ZKO3-3/Y32 • Internet electronic mail: readers_comment@zk3.
file Italic (slanted) type indicates variable values, placeholders, and function argument names. . . . A vertical ellipsis indicates that a portion of an example that would normally be present is not shown. cat (1) A cross-reference to a reference page includes the appropriate section number in parentheses.
.
1 Introduction This chapter introduces the T ruCluster Server product and some basic cluster hardware configuration concepts. Subsequent chapters describe how to set up and maintain T ruCluster Server hardware configurations.
interconnect, you can more easily alter or expand your cluster ’ s hardware configuration as newer and faster technologies become available. 1.2 Memor y Requirements Cluster members require a minimum of 128 MB of memory .
Because the T ru64 UNIX operating system will be available on the first cluster member , in an emergency , after shutting down the cluster , you have the option of booting the T ru64 UNIX operating system and attempting to fix the problem. See the T ruCluster Server Cluster Administration manual for more information.
partitions. Y ou can move the swap partition off the member boot disk. See the T ruCluster Server Cluster Administration manual for more information. 1.3.1.4 Quorum Disk The quorum disk allows greater availability for clusters consisting of two members.
Figure 1 – 1 shows a generic two-node cluster with the minimum number of disks. • T ru64 UNIX disk • Clusterwide root ( / ), /usr , and /var • Member 1 boot disk • Member 2 boot disk A minimum configuration cluster may have reduced availability due to the lack of a quorum disk.
Administration manual for a discussion of how and when to use a quorum disk. Figure 1 – 2: Generic T wo-Node Cluster with Minimum Disk Configuration and Quorum Disk Member System 1 Network Memory Ch.
• Using a RAID array controller in transparent failover mode allows the use of hardware RAID to mirror the disks. However , without a second SCSI bus, second Memory Channel, and redundant networks, this configuration is still not a NSPOF cluster (Section 1.
Figure 1 – 3: Minim um T wo-Node Cluster with UltraSCSI B A356 Storage Unit ID 5 PWR Shared SCSI Bus Clusterwide /, /usr , /var Member 1 Boot Disk Member 2 Boot Disk Quorum Disk UltraSCSI BA356 ID 4.
this slot can be used for a second power supply to provide fully redundant power to the storage shelf. W ith the use of the cluster file system (see the T ruCluster Server Cluster Administration manua.
UNIX V ersion 5.0, 16 devices are supported on a SCSI bus. Therefore, multiple BA356 storage units can be used on the same SCSI bus to allow more devices on the same bus. Figure 1 – 4 shows the configuration in Figure 1 – 3 with a second UltraSCSI BA356 storage unit that provides an additional seven disks for highly available applications.
file systems and the data disks across SCSI buses, removing the single SCSI bus as a single point of failure for these file systems. 1.5.3 T w o-Node Configurations with UltraSCSI BA356 Storage Units .
Figure 1 – 5: T wo-Node Configurations with UltraSCSI BA356 Storage Units and Dual SCSI Buses Host Bus Adapter (ID 7) Network Memory Channel Interface Memory Channel Memory Channel Member System 2 M.
instead of the HSZ70. The array controllers can be configured as a dual redundant pair . If you want the capability to fail over from one controller to another controller , you must install the second controller . Also, you must set the failover mode.
Note that in the configuration shown in Figure 1 – 6, there is only one shared SCSI bus. Even by mirroring the clusterwide root and member boot disks, the single shared SCSI bus is a single point of failure.
Figure 1 – 7: NSPOF Cluster Using HSZ70s in Multiple-Bus Failo ver Mode Networks Host Bus Adapter (ID 7) Member System 1 Member System 2 T ru64 UNIX Disk Host Bus Adapter (ID 6) Host Bus Adapter (ID.
Figure 1 – 8: NSPOF Fibre Channel Cluster Using HSG80s in Multiple-Bus Failo ver Mode KGPSA Member System 2 KGPSA KGPSA Member System 1 KGPSA Memory Channel Memory Channel Memor y Channel Interf ace ZK-1765U-AI Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B RA8000/ESA12000 Po r t 1 Po r t 2 Po r t 1 Po r t 2 1.
5. Prepare the shared storage by installing disks and configuring any RAID controller subsystems (see Chapter 3, Chapter 6, and Chapter 9 and the documentation for the StorageW orks enclosure or RAID controller). 6. Install signal converters in the StorageW orks enclosures, if applicable (see Chapter 3 and Chapter 9).
.
2 Hard ware Requirements and Restrictions This chapter describes the hardware requirements and restrictions for a T ruCluster Server cluster . It includes lists of supported cables, trilink connectors, Y cables, and terminators.
arbitration enabled when connecting four-member systems to a common SCSI bus. • The following items pertain to the AlphaServer GS80/160/320 systems: – Hot swapping modules is not supported.
2.2 Memor y Channel Restrictions The Memory Channel interconnect is used for cluster communications between the member systems. There are currently three versions of the Memory Channel product; Memory Channel 1, Memory Channel 1.5, and Memory Channel 2.
• In an MC2 configuration, you can use a CCMFB optical converter in conjunction with the MC2 CCMAB module to increase the distance between systems. • The BN34R fiber optics cable, used to connect two CCMFB optical converters, is available in 10-meter (BN34R-10) and 31-meter (BN34R-31) lengths.
each Memory Channel adapter on one system must be connected to the same linecard in each Memory Channel hub. 2.3 Host Bus Adapter Restrictions T o connect a member system to a shared SCSI bus, you must install a host bus adapter in an I/O bus slot. The T ru64 UNIX operating system supports a maximum of 64 I/O buses.
____________________ Notes ____________________ The Model 4124R disk enclosure is a single-bus enclosure that has slots for 14 drives, but only 12 drives are supported at the present time. The maximum number of drives behind an HSG60 (single or dual-redundant pair) using two single-bus Model 4214R disk enclosures is 24.
The maximum number of drives behind an HSG80 (single or dual-redundant pair) using three dual-bus Model 4254 disk enclosures is 42. The Model 4214R and Model 4254 disk enclosures support only the new Compaq hot-pluggable wide-UltraSCSI low voltage differential (L VD) disk drives.
• A maximum of three cascaded switches is supported, with a maximum of two hops between switches. The maximum hop length is 10 km longwave single-mode or 500 meters via shortwave multimode Fibre Channel cable. • T ru64 UNIX V ersion 5.1 limits the number of Fibre Channel targets to 126.
AlphaServer 800, 1000, 1000A, 2000, 2100, or 2100A systems support the variable), you must set the bus_probe_algorithm console variable to new by entering the following command: >>> set bus_probe_algorithm new Use the show bus_probe_algorithm console command to determine if your system supports the variable.
RAID array controllers require the minimum Array Controller Software (ACS) shown in T able 2 – 1. T able 2 – 1: RAID Controller Minimum Required Arra y Controller Software RAID Controller Minimum Required Arra y Controller Software HSZ20 3.4 HSZ40 3.
______________________ Note _______________________ W e could list the UltraSCSI hubs because they contain a DOC (DWZZA on a chip) chip, but they are discussed separately in Section 2.
• The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks. • A wide BA356 which has been upgraded to the 180-watt power supply with the DS-BA35X-HH option.
T able 2 – 3: Suppor ted SCSI Cables Cable Connector Density Pins Configuration Use BN21W-0B Three high 68-pin A Y cable that can be attached to a KZPSA-BB or KZPBA-CB if there is no room for a trilink connector . It can be used with a terminator to provide external termination.
2.9 SCSI T erminator s and T rilink Connectors T able 2 – 4 describes the supported trilink connectors and SCSI terminators and the context in which you would use them.
3 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hard ware A T ruCluster Server cluster uses shared SCSI buses, external storage shelves or RAID controllers, and supports disk mirroring and fast file system recovery to provide high data availability and reliability .
This chapter discusses the following topics: • Shared SCSI bus configuration requirements (Section 3.1) • SCSI bus performance (Section 3.2) • SCSI bus device identification numbers (Section 3.3) • SCSI bus length (Section 3.4) • SCSI bus termination (Section 3.
storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storage arrays (HSZ80 and HSG80). Older , non-UltraSCSI BA356 shelves are supported with UltraSCSI host adapters and host RAID controllers as long as they contain no UltraSCSI disks. • UltraSCSI drives and fast wide drives can be mixed together in an UltraSCSI BA356 shelf (see Chapter 9).
cable or a backplane, and cable or backplane connectors. Each UltraSCSI bus segment must have a terminator at each end of the bus segment. Up to two UltraSCSI bus segments may be coupled together with UltraSCSI hubs or signal converters, increasing the total length of the UltraSCSI bus.
Y ou cannot use a DWZZA or DWZZB signal converter at UltraSCSI speeds for T ruCluster Server if there are any UltraSCSI disks on the bus, because the DWZZA or DWZZB will not operate correctly at UltraSCSI speed. The DS-BA35X-DA personality module contains a signal converter for the UltraSCSI BA356.
______________________ Note _______________________ If you are using a DS-DWZZH-05 UltraSCSI hub with fair arbitration enabled, SCSI ID numbering will change (see Section 3.
Because of the cable length limit, you must plan your hardware configuration carefully , and ensure that each SCSI bus meets the cable limit guidelines. In general, you must place systems and storage shelves as close together as possible and choose the shortest possible cables for the shared bus.
Figure 3 – 1 shows a VHDCI trilink connector (UltraSCSI), which you may attach to an HSZ70 or HSZ80. Figure 3 – 1: VHDCI T rilink Connector (H8861-AA) CXO5744A 3.6 UltraSCSI Hubs The DS-DWZZH series UltraSCSI hubs are UltraSCSI signal converters that provide radial connections of differential SCSI bus adapters and RAID array controllers.
• Require that termination power ( termpwr ) be provided by the SCSI bus host adapters on each SCSI bus segment. _____________________ Note _____________________ The UltraSCSI hubs are designed to s.
Figure 3 – 2: DS-D WZZH-03 Front Vie w Differential symbol ZK-1412U-AI The differential symbol (and the lack of a single-ended symbol) indicates that all three connectors are differential. 3.6.1.2 DS-D WZZH-05 Description The DS-DWZZH-05: • Is a 5.
• The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks. A DS-DWZZH-05 UltraSCSI hub uses the storage shelf only to provide its power and mechanical support (it is not connected to the shelf internal SCSI bus).
3.6.1.2.2 DS-D WZZH-05 Fair Arbitration Although each cluster member system and storage controller connected to an UltraSCSI hub are on separate SCSI bus segments, they all share a common SCSI bus and its bandwidth.
3.6.1.2.3 DS-D WZZH-05 Address Configurations The DS-DWZZH-05 has two addressing modes: wide addressing mode and narrow addressing mode. W ith either addressing mode, if fair arbitration is enabled, each hub port is assigned a specific SCSI ID.
Figure 3 – 3: DS-D WZZH-05 Rear View W1 ZK-1448U-AI 3 – 14 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware.
Figure 3 – 4: DS-D WZZH-05 Front Vie w Fair Disable Host Port SCSI ID 1 (13) Host Port SCSI ID 3 (15) Controller Port SCSI ID 6 - 4 (6 - 0) Busy 0 2 ZK-1447U-AI Host Port Host Port SCSI ID SCSI ID (14) Power (12) 3.
2. If fair arbitration is to be used, ensure that the switch on the front of the DS-DWZZH-05 UltraSCSI hub is in the Fair position. 3. Install the DS-DWZZH-05 UltraSCSI hub in a UltraSCSI BA356, non-UltraSCSI BA356 (if it has the required 180-watt power supply), or BA370 storage shelf.
3.7.1 Configuring Radially Connected T ruCluster Server Clusters with UltraSCSI Hard ware Radial configurations with RAID array controllers allow you to take advantage of the benefits of hardware mirroring, and to achieve a no-single-point-of-failure (NSPOF) cluster .
or SCSI bus failure, the host can redistribute the load to the surviving controller . In case of a controller failure, the surviving controller will handle all units. ______________________ Notes ______________________ Multiple-bus failover does not support device partitioning with the HSZ70 or HSZ80.
2. Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H8861-AA VHDCI trilink connector to: • HSZ70 controller A and controller .
Figure 3 – 5 shows a two-member T ruCluster Server configuration with a radially connected dual-redundant HSZ70 RAID array controller configured for transparent failover .
T able 3 – 4: Hard ware Components Used in Configuration Shown in Figure 3 – 5 Through Figure 3 – 8 Callout Number Description 1 BN38C cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator b a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
3.7.1.2 Preparing a Dual-Redundant HSZ70 or HSZ80 f or a Shared SCSI Bus Using Multiple-Bus Failo ver Multiple-bus failover is a dual-redundant controller configuration in which each host has two paths (two shared SCSI buses) to the array controller subsystem.
2. Install H8861-AA VHDCI trilink connectors (with terminators) on: • HSZ70 controller A and controller B • HSZ80 controller A Port 1 (2) and controller B Port 1 (2) ___________________ Note ___________________ Y ou must use the same port on each HSZ80 controller .
Figure 3 – 7 shows a two-member T ruCluster Server configuration with a radially connected dual-redundant HSZ70 configured for multiple-bus failover .
Figure 3 – 8 shows a two-member T ruCluster Server configuration with a radially connected dual-redundant HSZ80 configured for multiple-bus failover .
.
4 T ruCluster Ser ver System Configuration Using UltraSCSI Hard ware This chapter describes how to prepare systems for a T ruCluster Server cluster , using UltraSCSI hardware and the preferred method of radial configuration, including how to connect devices to a shared SCSI bus for the T ruCluster Server product.
This is especially critical if you will install tape devices on the shared SCSI bus. W ith the exception of the TZ885, TZ887, TL890, TL891, and TL892, tape devices can only be installed at the end of a shared SCSI bus. These tape devices are the only supported tape devices that can be terminated externally .
• Number of shared SCSI buses and the storage on each shared bus Using shared SCSI buses increases storage availability . Y ou can connect 32 shared SCSI buses to a cluster member . Y ou can use any combination of KZPSA-BB, KZPBA-CB, or KGPSA-BC/CA host bus adapters.
T able 4 – 1: Planning Y our Configuration (cont.) T o increase: Y ou can: Disk availability Mirror disks across shared buses. Use a RAID array controller . Shared storage capacity Increase the number of shared buses. Use a RAID array controller . Increase disk size.
6. Copy the appropriate release notes to your system disk. In this example, obtain the firmware release notes for the AlphaServer DS20 from the V ersion 5.6 Alpha Firmware Update CD-ROM: # cp /mnt/doc/ds20_v56_fw_relnote.txt ds20-rel-notes 7. Unmount the CD-ROM drive: # umount /mnt 8.
______________________ Note _______________________ The KZPSA-BB can be used in any configuration in place of the KZPBA-CB. The use of the KZPSA-BB is not mentioned in this chapter because it is not UltraSCSI hardware, and it cannot operate at UltraSCSI speeds.
T able 4 – 2: Configuring T ruCluster Server Hard ware (cont.) Step Action Refer to: 4 Update the system SRM console firmware from the latest Alpha Systems Firmware Update CD-ROM.
The DWZZH contains a differential to single-ended signal converter for each hub port (sometimes referred to as a DWZZA on a chip, or DOC chip). The single-ended sides are connected together to form an internal single-ended SCSI bus segment.
Y our storage shelves or RAID array subsystems should be set up before completing this portion of an installation. Use the steps in T able 4 – 3 to set up a KZPBA-CB for a T ruCluster Server cluster that uses radial connection to a DWZZH UltraSCSI hub.
T able 4 – 3: Installing the KZPBA-CB f or Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: _____________________ Notes _____________________ Ensure that the SCSI ID that you use is distinct from all other SCSI IDs on the same shared SCSI bus.
Example 4 – 1: Displaying Configuration on an AlphaServer DS20 (cont.) Core Logic Cchip DECchip 21272-CA Rev 2.1 Dchip DECchip 21272-DA Rev 2.0 Pchip 0 DECchip 21272-EA Rev 2.
Example 4 – 1: Displaying Configuration on an AlphaServer DS20 (cont.) Bus 02 Slot 02: DE500-AA Network Controller ewa0.0.0.2002.0 00-06-2B-00-0A-48 PCI Hose 01 Bus 00 Slot 07: DEC PCI FDDI fwa0.
Example 4 – 3 shows the output from the show config console command entered on an AlphaServer 8200 system. Example 4 – 3: Displaying Configuration on an AlphaServer 8200 >>> show config N.
Example 4 – 4: Displaying Devices on an AlphaServer 8200 (cont.) dkf4.0.0.1.1 DKF4 HSZ70 V70Z dkf5.0.0.1.1 DKF5 HSZ70 V70Z dkf6.0.0.1.1 DKF6 HSZ70 V70Z dkf100.1.0.1.1 DKF100 RZ28M 0568 dkf200.2.0.1.1 DKF200 RZ28M 0568 dkf300.3.0.1.1 DKF300 RZ28 442D polling for units on kzpsa0, slot 2, bus 0, hose1.
4.3.3.1 Displaying KZPBA-CB pk* or isp* Console En vironment V ariables T o determine the console environment variables to use, execute the show pk* and show isp* console commands. Example 4 – 5 shows the pk console environment variables for an AlphaServer DS20.
• on — T urns on both low 8 bits and high 8 bits • diff — Places the bus in differential mode The KZPBA-CB is a Qlogic ISP1040 module, and its termination is determined by the presence or absence of internal termination resistor SIPs RM1-RM8. Therefore, the pk*0_soft_term environment variable has no meaning and it may be ignored.
4.3.3.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBs on the shared SCSI bus, use the set console command to set the SCSI ID. For a T ruCluster Server cluster , you will most likely have to set the SCSI ID for all KZPBA-CB UltraSCSI adapters except one.
Figure 4 – 1: KZPBA-CB T ermination Resistor s Internal Wide Device Connector J2 Internal Narrow Device Connector P2 SCSI Bus Termination Resistors RM1-RM8 ZK-1451U-AI JA1 4 – 18 T r uCluster Serv.
5 Setting Up the Memor y Channel Cluster Interconnect This chapter describes Memory Channel configuration restrictions, and describes how to set up the Memory Channel cluster interconnect, including setting up a Memory Channel hub, Memory Channel optical converter (MC2 only), and connecting link cables.
____________________ Note _____________________ If you are installing SCSI or network adapters, you may want to complete all hardware installation before powering up the systems to run Memory Channel diagnostics. Section 5.7 provides procedures for upgrading from redundant MC1 interconnects to MC2 interconnects.
T able 5 – 1: MC1 and MC1.5 Jumper Configuration (cont.) If hub mode is: J umper: Example: V irtual: VH0 Pins 2 to 3 12 3 V irtual: VH1 None needed; store the jumper on pin 1 or 3 12 3 If you are up.
See the T ruCluster Server Cluster Administration manual for more information on failover pairs. The MC2 jumpers are described in T able 5 – 2. T able 5 – 2: MC2 Jumper Configuration Jumper: Descr.
T able 5 – 2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: J5: AlphaServer 8x00 Mode 8x00 mode selected: Pins 1 to 2 a 12 3 8x00 mode not selected: Pins 2 to 3 12 3 J10 and J11: Fiber Optics Mode Enable Fiber Off: Pins 1 to 2 3 2 1 Fiber On: Pins 2 to 3 pins 3 2 1 a Increases the maximum sustainable bandwidth for 8x00 systems.
5.2 Installing the Memor y Channel Adapter Install the Memory Channel adapter in an appropriate peripheral component interconnect (PCI) slot (see Section 2.2). Secure the module at the backplane. Ensure that the screw is tight to maintain proper grounding.
5.4 Installing the Memory Channel Hub Y ou may use a hub in a two-node T ruCluster Server cluster , but the hub is not required. When there are more than two systems in a cluster , you must use a Memory Channel hub as follows: • For use with the MC1 or MC1.
______________________ Note _______________________ Do not connect an MC1 or MC1.5 link cable to an MC2 module. 5.5.1.1 Connecting MC1 or MC1.5 Link Cables in Vir tual Hub Mode For an MC1 virtual hub configuration (two nodes in the cluster), connect the BC12N-10 link cables between the Memory Channel adapters installed in each of the systems.
Figure 5 – 1 shows Memory Channel adapters connected to linecards that are in the same slot position in the Memory Channel hubs. Figure 5 – 1: Connecting Memory Channel Adapters to Hubs Memory Channel hub 1 Memory Channel hub 2 System A Memory Channel adapters Linecards ZK-1197U-AI 5.
Gently push the cable ’ s connector into the receptacle, and then use the screws to pull the connector in tight. The connector must be tight to ensure a good ground contact. If you are setting up redundant interconnects, all Memory Channel adapters in a system must have the same jumper setting, either VH0 or VH1.
Now you need to: • Set the CCMLB linecard jumpers to support fiber optics • Connect the fiber optics cable to a CCMFB fiber optics converter module • Install the CCMFB fiber optics converter mod.
There are two console level Memory Channel diagnostics, mc_diag and mc_cable : • The mc_diag diagnostic: – T ests the Memory Channel adapter(s) on the system running the diagnostic. – Runs as part of the initialization sequence when the system is powered up.
Example 5 – 1: Running the mc_cable Test >>> mc_cable 1 To exit MC_CABLE, type <Ctrl/C> mca0 node id 1 is online 2 No response from node 0 on mca0 2 mcb0 node id 1 is online 3 No resp.
5.7 Upgrading Memor y Channel Adapters If you have a T ruCluster Server configuration with redundant MC1 interconnects and want to upgrade to MC2 interconnects, you can do so without shutting down the entire cluster .
T able 5 – 4: Adding a Memory Channel Inter connect or Rolling from a Dual, Redundant MC1 Inter connect to MC2 Interconnects Step Action Refer to: 1 If desired, manually relocate all applications from the cluster member that will be shut down using the cluster application availability (CAA) caa_relocate command.
T able 5 – 4: Adding a Memory Channel Inter connect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: ______________________ Note ________________.
T able 5 – 4: Adding a Memory Channel Inter connect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: Standard Hub Configuration: Remove the MC1 adapter and install the MC2 adapter in one system, and on one rail at a time.
T able 5 – 4: Adding a Memory Channel Inter connect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: On one member system, use the sysconfig command to reconfigure the Memory Channel kernel subsystem to initiate the use of 512 MB address space.
(dbx) p rm_adapters[1]->rmp_prail_va->rmc_size 5 { [0] 16384 6 [1] 0 [2] 16384 6 [3] 0 [4] 16384 6 [5] 0 [6] 0 [7] 0 } 1 Check the size of a logical rail. 2 The logical rail is operating at 128 MB (16384 8-KB pages). 3 V erify the jumper settings for the member systems on the.
Figure 5 – 2 shows a dual, redundant virtual hub configuration using MC1 hardware being upgraded to MC2. Figure 5 – 2: MC1 to MC2 Virtual Hub Rolling Upgrade AlphaSer v er Member System 1 MC1 MC1 .
Figure 5 – 3 through Figure 5 – 8 show a three-node standard hub configuration being upgraded from MC1 to MC2. Figure 5 – 3: MC1 to MC2 Standard Hub Rolling Upgrade: Initial Configuration AlphaS.
Figure 5 – 4: MC1 to MC2 Standar d Hub Rolling Upgrade: First MC1 Module Replaced AlphaSer v er Member System 1 MC2 MC1 AlphaSer v er Member System 2 MC1 MC1 MC1 Hub # 1 MC1 Hub # 2 AlphaSer v er Me.
Figure 5 – 5: MC1 to MC2 Standard Hub Rolling Upgrade: Replace First MC1 Adapter in Second System AlphaSer v er Member System 1 MC2 MC1 AlphaSer v er Member System 2 MC2 MC1 MC2 Hub # 1 MC1 Hub # 2 .
Figure 5 – 6: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Third System Memory Channel Adapters AlphaSer v er Member System 1 MC2 MC1 AlphaSer v er Member System 2 MC2 MC1 MC2 Hub # 1 MC1 Hub # .
Figure 5 – 7: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Second MC1 in Second System AlphaSer v er Member System 1 MC2 MC1 AlphaSer v er Member System 2 MC2 MC2 MC2 Hub # 1 MC2 Hub # 2 AlphaSe.
Figure 5 – 8: MC1 to MC2 Standard Hub Rolling Upgrade: Final Configuration AlphaSer v er Member System 1 MC2 MC2 AlphaSer v er Member System 2 MC2 MC2 MC2 Hub # 1 MC2 Hub # 2 AlphaSer v er Member Sy.
6 Using Fibre Channel Storage This chapter provides an overview of Fibre Channel, Fibre Channel configuration examples, and information on Fibre Channel hardware installation and configuration in a T ru64 UNIX or T ruCluster Server V ersion 5.1 configuration.
• The steps necessary to install and configure the Fibre Channel hardware (Section 6.5). • The steps necessary to install the base operating system and cluster software using disks accessible over the Fibre Channel hardware (Section 6.6). • Changing the HSG80 from transparent to multiple-bus failover mode (Section 6.
8. See the T ru64 UNIX Installation Guide and install the base operating system from the CD-ROM. The installation procedure will recognize the disks for which you set the device unit number . Select the disk you have chosen as the T ru64 UNIX operating system installation disk from the list of disks provided (Section 6.
• Compaq StorageW orks HSG80 Array Controller ACS V ersion 8.5 CLI Reference Guide • MA6000 HSG60 Array Controller ACS V ersion 8.5 Solution Software for Compaq T ru64 UNIX Installation and Configuration Guide • Compaq StorageW orks HSG60/HSG80 Array Controller ACS V ersion 8.
6.2.1 Basic Fibre Channel T erminology The following list describes the basic Fibre Channel terminology: Frame All data is transferred in a packet of information called a frame. A frame is limited to 2112 bytes. If the information consists of more than 2112 bytes, it is divided up into multiple frames.
Link The physical connection between an N_Port and another N_Port or an N_Port and an F_Port. A link consists of two connections, one to transmit information and one to receive information. The transmit connection on one node is the receive connection on the node at the other end of the link.
Figure 6 – 1: P oint-to-P oint T opology N_P or t N_P or t T ransmit Receive Node 1 Node 2 T ransmit Receiv e ZK-1534U-AI 6.2.2.2 Fabric The fabric topology provides more connectivity than point-to-point topology . The fabric topology can connect up to 2 24 ports.
Figure 6 – 2: Fabric T opology N_P or t Node 1 Node 2 T ransmit Receive T ransmit Receive T ransmit Receive T ransmit Receive T ransmit Receive T ransmit Receive T ransmit Receive T ransmit Receive F_P or t F abric Node 3 Node 4 F_P or t F_P or t F_P or t N_P or t N_P or t N_P or t ZK-1536U-AI 6.
Figure 6 – 3: Arbitrated Loop T opology NL_P or t NL_P or t Node 1 Node 2 NL_P or t NL_P or t T ransmit Receiv e T ransmit Receiv e T ransmit Receiv e T ransmit Receiv e Node 3 Node 4 Hub ZK-1535U-AI ______________________ Note _______________________ The arbitrated loop topology is not supported by the T ru64 UNIX V ersion 5.
6.3.1 Fibre Channel Cluster Configurations for T ransparent Failo ver Mode W ith transparent failover mode: • The hosts do not know a failover has taken place (failover is transparent to the hosts). • The units are divided between an HSG80 port 1 and port 2.
In transparent failover , units D00 through D99 are accessed through port 1 of both controllers. Units D100 through D199 are accessed through port 2 of both HSG80 controllers (with the limit of a total of 128 storage units). Y ou cannot achieve a no-single-point-of-failure (NSPOF) configuration using transparent failover .
Therefore, you want to ensure that both HSG80 controllers start at the same time under all circumstances so that the controller sees its own preferred units. Figure 6 – 5, Figure 6 – 6, and Figure 6 – 7 show three different multiple-bus NSPOF cluster configurations.
Figure 6 – 6: Multiple-Bus NSPOF Configuration Number 2 ZK-1707U-AI KGPSA Member System 2 KGPSA Memory Channel KGPSA Member System 1 KGPSA Memory Channel Memor y Channel Interf ace Fibre Channel Swi.
Figure 6 – 7: Multiple-Bus NSPOF Configuration Number 3 KGPSA Member System 2 KGPSA KGPSA Member System 1 KGPSA Memory Channel Memory Channel Memor y Channel Interf ace ZK-1765U-AI Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B RA8000/ESA12000 Po r t 1 Po r t 2 Po r t 1 Po r t 2 6.
Figure 6 – 8: A Simple Zoned Configuration KGPSA Memory Channel KGPSA KGPSA KGPSA Fibre Channel Switch Cluster 1 Member System 1 Cluster 1 Member System 2 Cluster 2 Member System 2 Cluster 2 Member .
6.5 Installing and Configuring Fibre Channel Hard ware This section provides information about installing the Fibre Channel hardware needed to support T ru64 UNIX or a T ruCluster Server configuration using Fibre Channel storage.
The DS-DSGGC-AA has a default IP address of 10.77.77.77. Y ou may need to change this IP address before you connect the switch to the network. The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) or eight (DS-DSGGA-AB) plug-in interface modules.
3. Connect the Ethernet cable. 4. Connect the fiber-optic cables. 5. Connect power to the switch. 6. T urn on the power . The switch runs a series of power-on self test (POST) tests. The DS-DSGGC-AA has no power switch; power is applied when the unit is plugged in.
6.5.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.
____________________ 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 2. Press Enter to display the first submenu item in the configuration menu, Ethernet IP address: Ethernet IP address: 10.
10. Use the T ab/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.
When you have completed setting the IP address and subnet mask, disconnect the PC or terminal from the DS-DSGGB-AA or DS-DSGGC-AA switch. 6.5.1.2.4 Logging In to the Switch with a T elnet Connection Before you telnet to a Fibre Channel switch, you must set the Ethernet IP address and subnet mask.
______________________ Notes ______________________ Use Ctrl/H to correct typing errors. Use the logout command to log out from any telnet connection. 6.
• 64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide _____________________ Caution _____________________ Static electricity can damage modules and electronic components. W e recommend using a grounded antistatic wrist strap and a grounded work surface when handling modules.
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.
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.
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.
6.5.3 Setting Up the HSG80 Arra y Contr oller f or T ru64 UNIX Installation This section covers setting up the HSG80 controller for operation with T ru64 UNIX V ersion 5.1 and T ruCluster Server V ersion 5.1. For more information on installing the HSG80, see the Compaq StorageW orks HSG80 Array Controller ACS V ersion 8.
• 9600 BPS • 8 data bits • 1 stop bit • No parity 8. Connect the RA8000 or ESA12000 to the power source and apply power . ____________________ Note _____________________ The KGPSA host bus ada.
2 Prevents the command line interpreter (CLI) from reporting a misconfiguration error resulting from not having a failover mode set. 3 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.
Example 6 – 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.
____________________ Note _____________________ Y ou 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.
____________________ Note _____________________ If the fiber-optic cables are not properly installed, there will be inconsistencies in the connections shown. 14. Set up the storage sets as required for the applications to be used. An example is provided in Section 6.
– 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.
to each of those devices. For example, to boot from storage unit D1 as presented by the HSG80 controller , the AlphaServer console requires a device name such as dga133.1002.0.1.0 that identifies the storage unit. In addition, dga133.1002.0.1.0 must be reachable via a valid Fibre Channel connection.
• Reset the bootdef_dev console environment variable to provide multiple boot paths (Section 6.6.6). • Add additional systems to the cluster Section 6.6.7). If you are installing the T ru64 UNIX operating system or T ruCluster Server software, follow the procedure in Chapter 1.
T able 6 – 2 contains the necessary information to convert from the HSG80 unit numbers to /dev/disk/dsk n and device names for the example configuration.
Example 6 – 2: Setting Up the Mirror set (cont.) HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 5 HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 5 HSG80> CREATE_PARTITION BOOT-MIR SIZE=LARGEST 5 HSG80&.
2 Create the BOOT-MIR mirrorset using disks 30200 and 30300 and the CROOT-MIR mirrorset using disks 40000 and 40100. 3 Initialize the BOOT-MIR and CROOT-MIR mirrorsets. If you want to set any initialization switches, you must do so in this step. The BOOT-MIR mirrorset will be used for the T ru64 UNIX and cluster member system boot disks.
6.6.1.2 Adding Units and Identifiers to the HSG80 Storagesets After you have created the storagesets (mirrorsets and partitions), assign a unit number to each partition and set a unique identifier as shown in Example 6 – 3.
Example 6 – 3: Adding Units and Identifiers to the HSG80 Storagesets (cont.) again enable the ones specified HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON68,!NEWCON74,!NEWCON76,!NEWCON77 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit.
Record the unit name of each partition with the intended use for that partition (see T able 6 – 2). 2 Set an identifier for each storage unit. Use any number between 1 and 9999. T o keep your storage naming as consistent and simple as possible, consider using the unit number of the unit as its UDID.
unwanted system. Record the identifier and worldwide name for later use. T able 6 – 2 is a sample table filled in for the example. T able A – 1i n Appendix A is a blank table for your use in an actual installation.
UNIX V ersion 5.1 installation disk or cluster member system boot disks. Setting the device unit number allows the installation scripts to recognize a Fibre Channel disk. T o set the device unit number for a Fibre Channel device, follow these steps: 1.
console command, it would not detect the Fibre Channel devices connected to the HSG80. Example 6 – 4: Displaying the UDID and W orldwide Names of Devices Known to the Console P00>>> wwidmgr.
or wwidmgr -set command. In this example, none of the wwid n environment variables is set. 4. Look through the wwidmgr -show wwid display (see Example 6 – 4) and locate the UDID for the T ru64 UNIX disk (133) and each member system boot disks (131, 132) to ensure the storage unit is seen.
Example 6 – 5: Using the wwidmgr quickset Command to Set the Device Unit Number P00>>> wwidmgr -quickset -udid 133 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d60-0009-8080-0434-002e via adapter: via fc nport: connected: dga133.
The disks are not reachable and you cannot boot until after the system is initialized. If you have not set the UDID, you cannot set the device unit number as shown in Example 6 – 5. Y ou have to use the quickset command with the item number displayed by the wwidmgr -show wwid command (see Example 6 – 4).
Example 6 – 6: Sample Fibre Channel Device Names P00>>> show dev dga131.1001.0.1.0 $1$DGA131 HSG80 V8.5F dga131.1002.0.1.0 $1$DGA131 HSG80 V8.5F dga131.1003.0.1.0 $1$DGA131 HSG80 V8.5F dga131.1004.0.1.0 $1$DGA131 HSG80 V8.5F dga133.1001.0.1.
T o set the bootdef_dev console environment variable for the T ru64 UNIX installation when booting from a Fibre Channel device, follow these steps: 1. Obtain the device name for the Fibre Channel storage unit where you will install the T ru64 UNIX operating system.
6.6.2 Install the T ru64 UNIX Operating System After reading the T ruCluster Server Software Installation manual, and using the T ru64 UNIX Installation Guide as a reference, boot from the CD-ROM and install the T ru64 UNIX V ersion 5.1 operating system.
67: /dev/disk/dsk20c DEC HSG80 IDENTIFIER=143 68: /dev/disk/dsk21c DEC HSG80 IDENTIFIER=144 If you know that you have set the UDID for a large number of disks, you can also grep for the UDID: # hwmgr .
2. Search the display for the UDIDs (or worldwide names) for each of the cluster installation disks and record the /dev/disk/dsk n values. If you used the grep utility to search for a specific UDID, f.
T o reset the bootdef_dev console environment variable, follow these steps: 1. Obtain the device name and worldwide name for the Fibre Channel unit from where you will boot cluster member system 1 (see T able 6 – 2).
or wwidmgr -show reachability ). Y ou must initialize the system to use any of the device names in the bootdef_dev variable as follows: P00>>> set bootdef_dev dga131.
b. Set the bootdef_dev console environment variable to one reachable path ( Yes in the connected column of Example 6 – 7) to the member system boot disk: P00>>> set bootdef_dev dga132.1002.0.1.0 c. Boot genvmunix on the newly added cluster member system.
dga132.1004.0.1.0 1 dgb132.1002.0.2.0 2 dgb132.1003.0.2.0 3 dga132.1001.0.1.0 4 1 Path from host bus adapter A to controller A port 1 2 Path from host bus adapter B to controller A port 2 3 Path from host bus adapter B to controller B port 1 4 Path from host bus adapter A to controller B port 2 c.
6.7.1 Overview The change in failover modes cannot be accomplished with a simple SET MULTIBUS COPY=THIS HSG80 CLI command because: • Unit offsets are not changed by the HSG80 SET MULTIBUS_FAILOVER COPY=THIS command.
6.7.2 Procedure to Con vert from T ransparent to Multiple-bus F ailover Mode T o change from transparent failover to multiple-bus failover mode by resetting the unit offsets and modifying the systems ’ view of the storage units, follow these steps: 1.
HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON58 TRU64_UNIX OTHER 1 offline 0 HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON59 TRU64_UNIX THIS 1 offline 0 HOST_.
__________________ Note ___________________ Y ou must set the console to diagnostic mode to use the wwidmgr command 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>>> b.
wwid2 wwid3 N1 50001fe100000d64 N2 50001fe100000d62 N3 50001fe100000d63 N4 50001fe100000d61 P00>>> init h. Set the bootdef_dev console environment variable to the member system boot device. Use the paths shown in the reachability display of the wwidmgr -quickset command for the appropriate device (see Section 6.
nodename 5000-1FE1-0000-0CB0 SCSI tgt id 5 : portname 1000-0000-C920-A7AE nodename 1000-0000-C920-A7AE SCSI tgt id 6 : portname 1000-0000-C920-CD9C nodename 1000-0000-C920-CD9C SCSI tgt id 7 : portname 1000-0000-C921-0D00 (emx0) nodename 1000-0000-C921-0D00 The previous example shows four Fibre Channel devices on this SCSI bus.
portname 2004-0060-6900-5A1B nodename 1000-0060-6900-5A1B Present, Logged in, F_PORT, 1 Status of the emx1 link. The connection is a point-to-point fabric (switch) connection, and the link is up. The adapter is on SCSI bus 3 at SCSI ID 7. Both the port name and node name of the adapter (the worldwide name) are provided.
______________________ Note _______________________ Y ou can use the emxmgr utility interactively to perform any of the previous functions. 6.8.2 Using the emxmgr Utility Interactivel y Start the emxm.
x. Exit ----> 2 emx0 SCSI target id assignments: SCSI tgt id 0 : portname 5000-1FE1-0000-0CB2 nodename 5000-1FE1-0000-0CB0 SCSI tgt id 5 : portname 1000-0000-C920-A7AE nodename 1000-0000-C920-A7AE .
7 Using GS80, GS160, or GS320 Hard P artitions in a T ruCluster Ser ver Configuration This chapter contains information about using AlphaServer GS80/160/320 hard partitions in a T ruCluster Server V ersion 5.1 configuration with T ru64 UNIX V ersion 5.
7.2 Hard ware Requirements f or a Hard P ar tition in a Cluster The T ruCluster Server hardware requirements are the same for an AlphaServer GS80/160/320 hard partition as any other system in a cluster . Y ou must have: • A supported host bus adapter connected to shared storage.
Figure 7 – 1: P or tion of QBB Showing I/O Riser Modules I/O Riser BN39B I/O Riser Cable ZK-1749U-AI ____________________ Notes ____________________ Y ou can have up to two I/O riser modules in a QBB, but you cannot split them across partitions. Each I/O riser has two cable connections (Port 0 and Port 1).
W e recommend that you connect I/O riser 0 (local I/O riser ports 0 and 1) to the primary PCI drawer that will be the master system control manager (SCM). The BA54A-AA PCI drawer (the bottom PCI drawer in Figure 7 – 2 and Figure 7 – 3) is a primary PCI drawer .
1) that is higher than the master SCM. Both the master SCM and standby SCM must have the scm_csb_master_eligible SCM environment variable set. __________________ Note __________________ W e recommend that you put the primary PCI drawers that contain the master and standby SCM in the power cabinet.
types of PCI drawers. It is harder to distinguish the type of PCI drawer from the rear , but slot 1 provides the key . The primary PCI drawer has a standard I/O module in slot 1, and the console and modem ports and USB connections are visible on the module.
Figure 7 – 3: Rear View of Expansion and Primary PCI Drawer s ZK-1751U-AI Expansion PCI Drawer Primary PCI Drawer Console Serial Bus Node ID Module Local T er minal/ COM1/P or t PCI Dra wer Node ID CSB Connector PCI Dra wer Node ID CSB Connector Console Serial Bus Node ID Module Standard I/O Module I/O Riser 0 I/O Riser 1 7.
equally well with any number of partitions (as supported by the system type) by modifying the amount and placement of hardware and the SCM environment variable values. ______________________ Notes ______________________ V iew each partition as a separate system.
• Shared storage that is connected to KZPBA-CB (parallel SCSI) or KGPSA-CA (Fibre Channel) host bus adapters. • Network controllers. 3. Install BN39B cables between the local I/O risers on the QBBs in the partition (see Figure 7 – 1) and the remote I/O risers in the primary and expansion PCI drawer (see Figure 2 – 1 and Figure 7 – 3).
____________________ Notes ____________________ If the OCP key switch is in the On or Secure position, the system will go through the power-up sequence. In this case, when the power-up sequence terminates, power down the system with the power off SCM command, then partition the system.
Example 7 – 1: Defining Hard P ar titions with SCM En vironment V ariables (cont.) HP_QBB_MASK5 0 HP_QBB_MASK6 0 HP_QBB_MASK7 0 SROM_MASK ff f XSROM_MASK ff ff ff ff ff ff ff ff ff 1 0 0 PRIMARY_CPU.
scm_csb_master_eligible environment variable. The master and standby SCM must be connected to the OCP . The master SCM must have the lowest node ID. Use the node ID address obtained from the show csb SCM command (see Example 7 – 4).
2 T urn on power to partition 1. 3 T ransfer control from the SCM firmware to the SRM firmware. ____________________ Note _____________________ If the auto_quit_scm SCM environment variable is set, control is passed to the SRM firmware automatically at the end of the power-up sequence.
7.4 Determining AlphaSer ver GS80/160/320 System Configuration Y ou may be required to reconfigure an AlphaServer GS80/160/320 system that is not familiar to you.
2 QBB number and console serial bus (CSB) node ID. QBB 0 and 1 (CSB node IDs 30 and 31) are in partition 0. QBB 2 and 3 (CSB node IDs 32 and 33) are in partition 1. 3 CPU module is present, powered up, and has passed self test ( P ). A dash (-) indicates an empty slot.
12 Console serial bus node ID for PCI drawers. In this example, the first PCI drawer has node ID 10. The second PCI drawer has node ID 11. Note that in this case, the node ID switches are set to 0 and 1. 13 The status of each of the four PCI buses in a PCI drawer .
Example 7 – 4: Displaying Console Serial Bus Information (cont.) C3 CPU3/SROM V5.0-7 ON C0 IOR0 ON C1 IOR1 ON 31 PSM T05.4 (03.24/01:09) T4.0 (07.06) ON SrvSw: NORMAL 31 XSROM T05.4 (03.24/02:10) C4 CPU0/SROM V5.0-7 ON C5 CPU1/SROM V5.0-7 ON C6 CPU2/SROM V5.
• SCM master: This PCI primary drawer has the master SCM. • SCM slave: The SCM on this PCI primary drawer is a slave and has not been designated as a backup to the master . • CPU n /SROM: Each CPU module has SROM firmware that is executed as part of the power-up sequence.
– SCM: One on the standard I/O module of each primary PCI drawer – Power system manager (PSM): One on the PSM module in each QBB – PCI backplane manager (PBM): One on each PCI backplane – Hier.
5. T urn power on to the system to allow SRM firmware execution. The SRM code is copied to memory on the partition primary QBB during the power-up initialization sequence. SRM code is executed out of memory , not the SRM EEPROM on the standard I/O module.
___________________ Caution ___________________ Do not abort the update — doing so can cause a corrupt flash image in a firmware module. A complete firmware update takes a long time. The length of time increases proportionally to the number of PCI adapters you have.
.
8 Configuring a Shared SCSI Bus for T ape Drive Use The topics in this section provide information on preparing the various tape devices for use on a shared SCSI bus with the T ruCluster Server product. ______________________ Notes ______________________ Section 8.
8.1.1 Setting the TZ88N-V A SCSI ID Y ou must set the TZ88N-V A switches before the tape drive is installed into the BA350 StorageW orks enclosure. The Automatic selection is normally used. The TZ88N-V A takes up three backplane slot positions. The physical connection is in the lower of the three slots.
T able 8 – 1: TZ88N-V A Switch Settings SCSI ID SCSI ID Selection Switches 1234 56 Automatic a Off Off Off On On On 0 Off Off Off Off Off Off 1 On Off Off Off Off Off 2 Off On Off Off Off Off 3 On O.
Figure 8 – 2 shows a T ruCluster Server cluster with three shared SCSI buses. One shared bus has a BA350 with a TZ88N-V A at SCSI ID 3. Figure 8 – 2: Shared SCSI Buses with SBB T ape Drives KZPBA-.
T able 8 – 2: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 2 (cont.) Callout Number Description 8 DWZZA-V A with H885-AA trilink connector 9 DWZZB-VW with H885-AA trilink connector a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with BC19J cables as long as the SCSI bus maximum length is not exceeded. Ensure that the tape drive on the end of the bus is terminated with a H8574-A or H8890-AA terminator .
Figure 8 – 3: DS-TZ89N-VW SCSI ID Switches Snap − in Locking Handles SCSI ID Switch Pack Backplane Interface Connector DS − TZ89N − VW The SCSI ID is selected by switch positions, which must be selected before the tape drive is installed in the BA356.
T able 8 – 3: DS-TZ89N-VW Switch Settings (cont.) SCSI ID SCSI ID Selection Switches 1234 5 6 7 8 5 On Off On Off Off Off Off Off 6 Off On On Off Off Off Off Off 7 On On On Off Off Off Off Off 8 Off.
8.2.3 Setting the DS-TZ89N-T A SCSI ID The DS-TZ89N-T A has a push-button counter switch on the rear panel to select the SCSI ID. It is preset at the factory to 15. Push the button above the counter to increment the SCSI ID (the maximum is 15); push the button below the switch to decrease the SCSI ID.
8.3 Compaq 20/40 GB DL T T ape Drive The Compaq 20/40 GB DL T T ape Drive is a Digital Linear T ape (DL T) tabletop cartridge tape drive capable of holding up to 40 GB of data per Compactape IV cartridge using 2:1 compression. It is capable of storing/retrieving data at a rate of up to 10.
Figure 8 – 4: Compaq 20/40 GB DL T T ape Drive Rear Panel + - 0 20/40 GB DL T T ape Drive SCSI ID Selector Switch SCSI ID + - 0 ZK-1603U-AI 8.3.2 Cabling the Compaq 20/40 GB DL T T ape Drive The Compaq 20/40 GB DL T T ape Drive is connected to a single-ended segment of the shared SCSI bus.
cable). Ensure that the trilink or Y cable at both ends of the differential segment of the shared SCSI bus is terminated with an HD68 differential terminator such as an H879-AA. The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with cable part number 146745-003 or 146776-003 (0.
Figure 8 – 5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DL T T ape Drive KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Memory Channel Member System 2 Member System 1.
T able 8 – 4: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 5 (cont.) Callout Number Description 9 199629-002 or 189636-002 (68-pin high density to 50-pin high density 1.
8.4.2 Cabling the Compaq 40/80-GB DL T Drive The Compaq 40/80-GB DL T Drive is connected to a single-ended segment of the shared SCSI bus. Figure 8 – 6 shows a configuration with a Compaq 40/80-GB DL T Drive for use on a shared SCSI bus. T o configure the shared SCSI bus for use with a Compaq 40/80-GB DL T Drive, follow these steps: 1.
T o achieve system performance capabilities, we recommend that you place no more than two Compaq 40/80-GB DL T Drives on a SCSI bus, and that you place no shared storage on the same SCSI bus with the tape drive.
T able 8 – 5: Hard ware Components in the Configuration in Figure 8 – 6 (cont.) Callout Number Description 8 H885-AA trilink connector 9 189646-001 (0.
8.5.2 Cabling the TZ885 T ape Drive The TZ885 is connected to a single-ended segment of the shared SCSI bus. It is connected to a differential portion of the shared SCSI bus with a DWZZA-AA or DWZZB-AA. Figure 8 – 7 shows a configuration of a TZ885 for use on a shared SCSI bus.
______________________ Note _______________________ Ensure that there is no conflict with tape drive and host bus adapter SCSI IDs. Figure 8 – 7: Cabling a Shared SCSI Bus with a TZ885 KZPBA-CB (ID .
T able 8 – 6: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 6 (cont.) Callout Number Description 8 H885-AA trilink connector 9 BN21M cable 10 H8574-A terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
Figure 8 – 8: TZ887 DL T MiniLibrary Rear Panel + - 0 TZ887 ZK-1461U-AI SCSI ID SCSI ID Selector Switch + - 0 8.6.2 Cabling the TZ887 T ape Drive The TZ887 is connected to a single-ended segment of the shared SCSI bus. It is connected to a differential portion of the shared SCSI bus with a DWZZB-AA.
length is not exceeded and there are sufficient SCSI IDs available. Ensure that the tape drive on the end of the bus is terminated with an H8574-A or H8890-AA terminator . Y ou can add additional shared SCSI buses with TZ887 tape drives by adding additional DWZZB-AA/TZ887 combinations.
8.7 Preparing the TL891 and TL892 DL T MiniLibraries for Shared SCSI Usage ______________________ Note _______________________ T o achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus, and also recommend that no shared storage be placed on the same SCSI bus with a tape library .
The first and second lines of the default screen show the status of the two drives (if present). The third line shows the status of the library robotics, and the fourth line is a map of the magazine, with the numbers from 0 to 9 representing the cartridge slots.
4. Select the tape drive (DL T0 Bus ID: or DL T1 Bus ID:) or library robotics (LIB Bus ID:) for which you wish to change the SCSI bus ID. The default SCSI IDs are as follows: • Lib Bus ID: 0 • DL T0 Bus ID: 4 • DL T1 Bus ID: 5 Use the up or down arrow button to select the item for which you need to change the SCSI ID.
SCSI bus without stopping all ASE services that generate activity on the bus. For this reason, we recommend that tape devices be placed on separate shared SCSI buses, and that there be no storage devices on the SCSI bus.
T o connect the drive robotics and one drive to one shared SCSI bus and the second drive to a second shared SCSI bus, follow these steps: 1. Connect a BN21K or BN21L between the last trilink connector on one shared SCSI bus to the leftmost connector (as viewed from the rear) of the TL892.
Figure 8 – 10: T ruCluster Server Cluster with a TL892 on T wo Shared SCSI Buses KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Member System 1 DS-DWZZH-03 T T T 2 1 4 1 3 S.
8.8 Preparing the TL890 DL T MiniLibrar y Expansion Unit The topics in this section provide information on preparing the TL890 DL T MiniLibrary expansion unit with the TL891 and TL892 DL T MiniLibraries for use on a shared SCSI bus.
8.8.2.1 Cabling the DL T MiniLibraries Y ou must make the following connections to render the DL T MiniLibrary system operational: • Expansion unit to the motor mechanism: The motor mechanism cable is about 1 meter long and has a DB-15 connector on each end.
____________________ Notes ____________________ Do not connect a SCSI bus to the SCSI connectors for the library connectors on the base modules. W e recommend that no more than two TZ89 tape drives be on a SCSI bus. Figure 8 – 11 shows a MiniLibrary configuration with two TL892 DL T MiniLibraries and a TL890 DL T MiniLibrary expansion unit.
Figure 8 – 11: TL890 and TL892 DL T MiniLibraries on Shared SCSI Buses TL892 TL892 TL890 Library Robotics DLT1 Expansion Modules Robotics Control cables DLT2 Library Robotics DLT1 DLT2 Expansion Uni.
T able 8 – 8: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 10 Callout Number Description 1 BN38C or BN38D cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 .
After a series of power-on self-tests have executed, the default screen will be displayed on the base module control panel: DLT0 Idle DLT1 Idle Loader Idle 0 >____ ______< 9 The default screen shows the state of the tape drives, loader , and number of cartridges present for this base module.
inventory of modules may be incorrect and the contents of some or all of the modules will be inaccessible to the system and to the host. When the expansion unit comes up, it will communicate with each base module through the expansion unit interface and inventory the number of base modules, tape drives, and cartridges present in each base module.
4. Press the down arrow button until the Configure Menu item is selected, and then press the Enter button to display the Configure submenu. 5. Press the down arrow button until the Set SCSI item is selected and press the Enter button.
______________________ Note _______________________ T o achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus segment. W e also recommend that storage be placed on shared SCSI buses that do not have tape drives.
Menu: Configuration Inquiry 6. Press and release the up or down arrow buttons to locate the SCSI Address submenu, and verify that the following information is displayed in the SDA: Menu: Configuration SCSI Address .
6. Press and release the SELECT button again to choose SCSI Address and verify that the following information is shown in the SDA: Menu: SCSI Address Robotics 7. Use the down arrow button to bypass the Robotics submenu and verify that the following information is shown in the SDA: Menu: SCSI Address Drive 0 8.
Figure 8 – 12: TL894 T ape Library Four-Bus Configuration Robotics Controller *SCSI Address 0 Rear Panel Host Connection #1 SCSI Port 1 SCSI Port 2 SCSI Port 3 SCSI Port 4 Tape Drive 0 *SCSI Address 2 Tape Drive 1 *SCSI Address 3 Tape Drive 2 *SCSI Address 4 Tape Drive 3 *SCSI Address 5 Tape Drive Interface PWA SCSI Cable 1.
installing an HD68 SCSI bus terminator on the SCSI bus port connector on the cabinet exterior . This is not wrong, but by reconfiguring in this manner , the length of the SCSI bus is increased by 1.5 meters, and may cause problems if SCSI bus length is of concern.
In Figure 8 – 13, one bus is connected to port 1 (robotics controller and tape drives 0 and 1) and the other bus is connected to port 3 (tape drives 2 and 3).
T able 8 – 10: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 12 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
The physical SCSI IDs should match the SCSI IDs set by the library electronics. Ensure that the SCSI ID set by the rotary switch and from the control panel do not conflict with any SCSI bus controller SCSI ID. The following sections describe how to prepare the TL895 for use on a shared SCSI bus in more detail.
3. On the Operator screen, press the Configure Library button. The Configure Library screen displays the current library configuration. ____________________ Note _____________________ Y ou can configure the library model number , number of storage bins, number of drives, library SCSI ID, and tape drive SCSI IDs from the Configure Library screen.
Y ou can reconfigure the tape drives and robotics controller to place multiple tape drives on the same SCSI bus with SCSI bus jumper (part number 6210567) included with the tape library . ______________________ Note _______________________ W e recommend placing no more than two TZ89 drives on a SCSI bus segment.
Figure 8 – 14: TL895 T ape Library Internal Cabling Robotics Controller SCSI ID 0 SCSI Port 5 SCSI Port 4 SCSI Port 3 Tape Drive 0 SCSI ID 1 Tape Drive 1 SCSI ID 2 ZK-1397U-AI SCSI Port 8 SCSI Port .
electronic SCSI ID using the Configure menu from the control panel (see Section 8.10.2). The actual upgrade is beyond the scope of this manual. See the TL895 Drive Upgrade Instructions manual for upgrade instructions.
Each tape library comes configured with a robotic controller and bar code reader (to obtain quick and accurate tape inventories). The libraries have either three or six TZ89N-A V drives. The TL896, because it has a greater number of drives, has a lower capacity for tape cartridge storage.
These tape libraries each have a multi-unit controller (MUC) that serves two functions: • It is a SCSI adapter that allows the SCSI interface to control communications between the host and the tape library . • It permits the host to control up to five attached library units in a multi-unit configuration.
T able 8 – 12: MUC Switch Functions (cont.) Switch Function 7 Host selection: Down for SCSI, up for serial a 8 Must be down, reserved for testing a For a T ruCluster Server cluster , switch 7 is down, allowing switches 1, 2, and 3 to select the MUC SCSI ID.
T able 8 – 15: TL896 Default SCSI IDs SCSI Port Device Default SCSI ID MUC 2 D Drive 5 (top) 5 E Drive 4 4 F Drive 3 3 A Drive 2 5 B Drive 1 4 C Drive 0 (bottom) 3 8.
Figure 8 – 15: TL893 Three-Bus Configuration MUC SCSI Address 2 SCSI Port A SCSI Port B SCSI Port C TZ89 Tape Drive SCSI Address 5 (top shelf) TZ89 Tape Drive SCSI Address 4 (middle shelf) TZ89 Tape.
– The lower bay bottom shelf tape drive (tape drive 0, SCSI ID 3) is on SCSI Port C and is terminated on the tape drive. – The tape drive terminators are 68-pin differential terminators (part number 0415619).
on the shared SCSI bus. Each SCSI bus must be terminated internal to the tape library at the tape drive itself with the installed SCSI terminators. Therefore, TL893 and TL896 tape libraries must be on the end of the shared SCSI bus.
Figure 8 – 17: Shared SCSI Buses with TL896 in Three-Bus Mode KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) DS-DWZZH-03 T T T 2 1 4 1 3 StorageW or ks RAID Arra y 7000 HSZ7.
T able 8 – 16: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 16 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
8.12.1.2 TL881 and TL891 MiniLibrary Rackmount Components A TL881 or TL891 base unit (which contains the tape drive(s)) can operate as an independent, standalone unit, or in concert with an expansion unit and multiple data units. A rackmount multiple-module configuration is expandable to up to six modules in a configuration.
• Data unit — This rackmount module contains a 16-cartridge magazine to provide additional capacity in a multi-module configuration. The data unit robotics works in conjunction with the robotics of the expansion unit and base units. It is under control of the expansion unit.
T able 8 – 17: TL881 and TL891 MiniLibrary Perf ormance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary Configured for Maximum: Number of Base Units ab Number of Data Units c T ransfer Rate d Storage Capacity e T ransfer Rate f Storage Capacity g Performance 50 15 MB/sec (54 GB/hour) 1.
T able 8 – 18: DL T MiniLibrary Part Numbers (cont.) DL T Library Component Number of T ape Drives T abletop/Rackmount P ar t Number TL891 DL T MiniLibrary Base Unit 2 Rackmount 120876-B22 Add-on DL.
For complete hardware installation instructions, see the TL881 MiniLibrary System User ’ s Guide or TL891 MiniLibrary System User ’ s Guide . 8.12.
status until you exit the Menu Mode and the Ready light comes on once again. 2. Depress the down arrow button until the Configure Menu item is selected, then press the Enter button to display the Configure submenu. ____________________ Note _____________________ The control panel up and down arrows have an auto-repeat feature.
______________________ Note _______________________ The tape drive SCSI connectors are labeled DL T1 (tape drive 1) and DL T2 (tape drive 2). The control panel designation for the drives is DL T0 (tape drive 1) and DL T1 (tape drive 2).
3. Install an HD68 differential terminator (such as an H879-AA) on the right DL T1 connector (the fourth connector from the left). T o connect the drive robotics and two drives to a single shared SCSI bus, follow these steps: 1.
Figure 8 – 18: TL891 Standalone Cluster Configuration KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Memory Channel Member System 2 Member System 1 DS-DWZZH-03 T T T 2 1 4 1.
T able 8 – 19: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 17 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
connector on the data unit and the female end to any Expansion Modules connector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector you connect to a base unit or a data unit.
Figure 8 – 19: TL891 DL T MiniLibrary Rackmount Configuration KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Member System 1 DS-DWZZH-03 T T T 2 1 4 1 3 StorageW or ks RAID .
T able 8 – 20: Hard ware Components Used to Create the Configuration Shown in Figure 8 – 18 Callout Number Description 1 BN38C or BN38D cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4.
DLT0 Idle DLT1 Idle Loader Idle 0 >____ ______< 9 The default screen shows the state of the tape drives, loader , and number of cartridges present for this base unit. A rectangle in place of the underscore indicates that a cartridge is present in that location.
When the expansion unit comes up, it will communicate with each base and data unit through the expansion unit interface and inventory the number of base units, tape drives, data units, and cartridges present in each base and data unit.
• DL T3 Bus ID: 4 • DL T4 Bus ID: 5 • DL T5 Bus ID: 6 7. Press Enter when you have the item selected for which you wish to change the SCSI ID. 8. Use the up and down arrows to select the desired SCSI ID. Press the Enter button to save the new selection.
______________________ Note _______________________ These tape devices have been qualified for use on shared SCSI buses with both the KZPSA-BB and KZPBA-CB host bus adapters.
______________________ Notes ______________________ The ESL9326D Enterprise Library is cabled internally for two 35/70 DL T tape drives on each SCSI bus. It arrives with the library electronics cabled to tape drives 0 and 1. Every other pair of tape drives is cabled together (2 and 3, 4 and 5, 6 and 7, and so on).
Figure 8 – 20: ESL9326D Internal Cabling T T ape Drive 0 T ape Drive 1 T ape Drive 2 T ape Drive 3 T ape Drive 4 T ape Drive 5 T ape Drive 6 T ape Drive 7 T ape Drive 8 T ape Drive 9 T ape Drive 10 .
8.13.3.4 Connecting the ESL9326D Enterprise Library to the Shared SCSI Bus The ESL9326D Enterprise Library has 5 meters of internal SCSI bus cabling for each pair of tape drives.
______________________ Notes ______________________ Each ESL9326D Enterprise Library arrives with one 330563-001 HD68 terminator for each pair of tape drives (one SCSI bus). The kit also includes at least one 330582-001 jumper cable to connect the library electronics to tape drives 0 and 1.
9 Configurations Using External T ermination or Radial Connections to Non-UltraSCSI De vices This chapter describes the requirements for the shared SCSI bus using: • Externally terminated T ruCluste.
9.1 Using SCSI Bus Signal Con ver ter s A SCSI bus signal converter allows you to couple a differential bus segment to a single-ended bus segment, allowing the mixing of differential and single-ended devices on the same SCSI bus to isolate bus segments for maintenance purposes.
but you would waste a disk slot and it would not work with a KZPBA-CB if there are any UltraSCSI disks in the storage shelves. The following sections discuss the DWZZA and DWZZB signal converters and the DS-BA35X-DA personality module.
Figure 9 – 1: Standalone SCSI Signal Con ver ter ZK-1050U-AI T T Single-ended Differential side with trilink attached side Figure 9 – 2 shows the status of internal termination for an SBB SCSI signal converter that has a trilink connector attached to the differential side.
______________________ Notes ______________________ S4-3 and S4-4 have no function on the DS-BA35X-DA personality module. See Section 9.3.2.2 for information on how to select the device SCSI IDs in an UltraSCSI BA356. Figure 9 – 3 shows the relative positions of the two DS-BA35X-DA switch packs.
Whenever possible, connect devices to a shared bus so that they can be isolated from the bus. This allows you to disconnect devices from the bus for maintenance purposes without affecting bus termination and cluster operation.
connector at a later time without affecting bus termination. This allows you to expand your configuration without shutting down the cluster . Figure 9 – 4 shows a BN21W-0B Y cable, which you may attach to a KZPSA-BB or KZPBA-CB SCSI adapter that has had its onboard termination removed.
Figure 9 – 5: HD68 T rilink Connector (H885-AA) FRONT VIEW REAR VIEW ZK-1140U-AI ______________________ Note _______________________ If you connect a trilink connector to a SCSI bus adapter , you may block access to an adjacent PCI slot. If this occurs, use a Y cable instead of the trilink connector .
9.3.1 BA350 Storage Shelf Up to seven narrow (8-bit) single-ended StorageW orks building blocks (SBBs) can be installed in the BA350. Their SCSI IDs are based upon the slot they are installed in. For instance, a disk installed in BA350 slot 0 has SCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1, and so forth.
Figure 9 – 6: BA350 Internal SCSI Bus JA1 JB1 0 1 2 3 4 5 6 POWER (7) T J ZK-1338U-AI 9.3.2 BA356 Storage Shelf There are two variations of the BA356 used in T ruCluster Server clusters: the BA356 (non-UltraSCSI BA356) and the UltraSCSI BA356. An example of the non-UltraSCSI BA356 is the BA356-KC, which has a wide, single-ended internal SCSI bus.
select SCSI IDs 0 through 6, set the personality module address switches 1 through 7 to off. T o select SCSI IDs 8 through 14, set personality module address switches 1 through 3 to on and switches 4 through 7 to off. Figure 9 – 7 shows the relative location of the BA356 SCSI bus jumper , BA35X-MF .
Figure 9 – 7: BA356 Internal SCSI Bus JA1 JB1 0 1 2 3 4 5 6 POWER (7) J ZK-1339U-AI Note that JA1 and JB1 are located on the personality module (in the top of the box when it is standing vertically).
Figure 9 – 8: BA356 Jumper and T erminator Module Identification Pins Slot 6 Jumper Pin Slot 6 T er minator Pin Slot 1 Jumper Pin Slot 1 T er minator Pin ZK-1529U-AI 9.3.2.2 UltraSCSI BA356 Storage Shelf The UltraSCSI BA356 (DS-BA356-JF or DS-BA356-KH) has a single-ended, wide UltraSCSI bus.
BA356, as shown in Figure 9 – 8. W ith proper lighting you will be able to see a J or T near the hole where the pin sticks through. T ermination for both ends of the UltraSCSI BA356 internal, single-ended bus is on the personality module, and is always active.
Later sections describe how to install cables to configure an HSZ20, HSZ40, or HSZ50 in a T ruCluster Server configuration with two member systems. 9.4.
2. Y ou will need a DWZZA-V A signal converter for the BA350. Ensure that the DWZZA-V A single-ended termination jumper , J2, is installed. Remove the termination from the differential end by removing the five 14-pin differential terminator resistor SIPs.
SCSI bus (cable and BA356) under the 3-meter limit to still allow high speed operation. If you are using a DWZZB-VW , install it in slot 0 of the BA356.
must be used with a BA356 or UltraSCSI BA356 if more than five disks are required. The following sections provide the steps needed to connect two storage shelves and two member systems on a shared SCSI bus: • BA350 and BA356 (Section 9.4.2.1) • T wo BA356s (Section 9.
Figure 9 – 9 shows a two-member T ruCluster Server configuration using a BA350 and a BA356 for storage. Figure 9 – 9: BA350 and BA356 Cabled for Shared SCSI Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 .
T able 9 – 1: Hard ware Components Used for Configuration Shown in Figure 8 – 9 and Figure 8 – 10 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA terminator 3 BN21K (or BN21L) cable a 4 H885-AA trilink connector a The maximum combined length of the BN21K (or BN21L) cables must not exceed 25 meters.
Figure 9 – 10 shows a two member T ruCluster Server configuration using two BA356s for storage. Figure 9 – 10: T wo B A356s Cabled for Shared SCSI Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 ID 14 or r.
9.4.2.3 Connecting T wo UltraSCSI BA356s for Shared SCSI Bus Usage When you use two UltraSCSI BA356 storage shelves on a shared SCSI bus in a T ruCluster configuration, one storage shelf must be configured for SCSI IDs 0 through 6 and the other configured for SCSI IDs 8 through 14.
Figure 9 – 11 shows a two member T ruCluster Server configuration using two UltraSCSI BA356s for storage. Figure 9 – 11: T wo UltraSCSI BA356s Cabled for Shared SCSI Bus Usage ID 8 ID 9 ID 10 ID 1.
T able 9 – 2: Hard ware Components Used for Configuration Shown in Figure 9 – 11 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA HD68 terminator 3 BN38C (or BN38D) cable a 4 H8861-AA VHDCI.
9.4.3.1 Cabling an HSZ40 or HSZ50 in a Cluster Using External T ermination T o connect an HSZ40 or HSZ50 controller to an externally terminated shared SCSI bus, follow these steps: 1. If the HSZ40 or HSZ50 will be on the end of the shared SCSI bus, attach an H879-AA terminator to an H885-AA trilink connector .
Figure 9 – 12 shows two AlphaServer systems in a T ruCluster Server configuration with dual-redundant HSZ50 RAID controllers in the middle of the shared SCSI bus. Note that the SCSI bus adapters are KZPSA-BB PCI-to-SCSI adapters. They could be KZPBA-CB host bus adapters without changing any cables.
Figure 9 – 13: Externally T erminated Shared SCSI Bus with HSZ50 RAID Array Contr ollers at Bus End KZPSA-BB (ID 7) Network Memory Channel Interface Memory Channel KZPSA-BB (ID 6) Memory Channel Mem.
9.4.3.2 Cabling an HSZ20 in a Cluster Using External Termination T o connect a SWXRA-Z1 (HSZ20 controller) to a shared SCSI bus, follow these steps: 1.
2. Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H885-AA trilink connector to the other controller . 3. Install a BN21K or BN21L cable between the H885-AA trilink connectors on the two controllers.
Figure 9 – 14 shows a sample configuration with radial connection of KZPSA-BB PCI-to-SCSI adapters, DS-DWZZH-03 UltraSCSI hub, and an HSZ50 RAID array controller . Note that the KZPSA-BBs could be replaced with KZPBA-CB UltraSCSI adapters without any changes in cables.
Figure 9 – 15 shows a sample configuration that uses KZPSA-BB SCSI adapters, a DS-DWZZH-05 UltraSCSI hub, and an HSZ50 RAID array controller . Figure 9 – 15: T ruCluster Server Cluster Using KZPSA.
.
10 Configuring Systems f or External T ermination or Radial Connections to Non-UltraSCSI Devices This chapter describes how to prepare the systems for a T ruCluster Server cluster when there is a need for external termination or radial connection to non-UltraSCSI RAID array controllers (HSZ40 and HSZ50).
Follow the steps in T able 10 – 1 to start the T ruCluster Server hardware installation procedure. Y ou can save time by installing the Memory Channel adapters, redundant network adapters (if applicable), and KZPSA-BB or KZPBA-CB SCSI adapters all at the same time.
The DWZZH-series UltraSCSI hubs are designed to allow more separation between member systems and shared storage. Using the UltraSCSI hub also improves the reliability of the detection of cable faults. A side benefit is the ability to connect the member systems ’ SCSI adapter directly to a hub port without external termination.
_____________________ Note _____________________ Y ou may have problems if the member system supports the bus_probe_algorithm console variable and it is not set to new .
T able 10 – 2: Installing the KZPSA-BB or KZPBA-CB f or Radial Connection to a D WZZH UltraSCSI Hub (cont.) Step Action Refer to: 2 Power down the system. Install a KZPSA-BB PCI-to-SCSI adapter or KZPBA-CB UltraSCSI host adapter in the PCI slot corresponding to the logical bus to be used for the shared SCSI bus.
T able 10 – 2: Installing the KZPSA-BB or KZPBA-CB f or Radial Connection to a D WZZH UltraSCSI Hub (cont.) Step Action Refer to: 6 Use the show pk* or show isp* console commands to determine the st.
T able 10 – 3: Installing a KZPSA-BB or KZPBA-CB f or Use with External T ermination Step Action Refer to: 1 Remove the KZPSA-BB internal termination resistors, Z1, Z2, Z3, Z4, and Z5.
T able 10 – 3: Installing a KZPSA-BB or KZPBA-CB f or Use with External T ermination (cont.) Step Action Refer to: 7 Use the show pk* or show isp* console commands to determine the status of the KZP.
T able 10 – 3: Installing a KZPSA-BB or KZPBA-CB f or Use with External T ermination (cont.) Step Action Refer to: TL890 with TL891/TL892 Section 8.8 TL894 Section 8.9 TL895 Section 8.10 TL893/TL896 Section 8.11 TL881/TL891 DL T MiniLibraries Section 8.
Example 10 – 1: Displaying Configuration on an AlphaServer 4100 (cont.) CPU (4MB Cache) 3 0000 cpu0 CPU (4MB Cache) 3 0000 cpu1 Bridge (IOD0/IOD1) 600 0021 iod0/iod1 PCI Motherboard 8 0000 saddle0 B.
Example 10 – 2: Displaying Devices on an AlphaServer 4100 (cont.) dkd100.1.0.4.1 DKd100 RZ26N 0568 dkd200.1.0.4.1 DKd200 RZ26 392A dkd300.1.0.4.1 DKd300 RZ26N 0568 polling kzpsa0 (DEC KZPSA) slot 5, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 7 kzpsa0.7.
Example 10 – 4: Displaying De vices on an AlphaServer 8200 >>> show device polling for units on isp0, slot0, bus0, hose0... polling for units on isp1, slot1, bus0, hose0... polling for units on isp2, slot4, bus0, hose0... polling for units on isp3, slot5, bus0, hose0.
10.1.4 Displa ying Console En vir onment V ariables and Setting the KZPSA-BB and KZPBA-CB SCSI ID The following sections show how to use the show console command to display the pk* and isp* console environment variables and set the KZPSA-BB and KZPBA-CB SCSI ID on various AlphaServer systems.
Example 10 – 5: Displaying the pk* Console En vironment V ariables on an AlphaServer 4100 System (cont.) pkf0_fast 1 pkf0_host_id 7 pkf0_termpwr 1 Compare the show pk* command display in Example 10 – 5 with the show config command in Example 10 – 1 and the show dev command in Example 10 – 2.
Example 10 – 6: Displa ying Console V ariables for a KZPBA-CB on an AlphaServer 8x00 System P00>>> show isp* isp0_host_id 7 isp0_soft_term on isp1_host_id 7 isp1_soft_term on isp2_host_id 7.
Example 10 – 7: Displa ying Console V ariables for a KZPSA-BB on an AlphaServer 8x00 System (cont.) pkc0_fast 1 pkc0_host_id 7 pkc0_termpwr on 10.1.4.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBs on the shared SCSI bus, use the set console command to set the SCSI ID.
10.1.4.3 Setting KZPSA-BB SCSI Bus ID, Bus Speed, and T ermination P o wer If the KZPSA-BB SCSI ID is not correct, or if it was reset to 7 by the firmware update utility , or you need to change the KZPSA-BB speed, or enable termination power , use the set console command.
10.1.4.4 KZPSA-BB and KZPBA-CB T ermination Resistors The KZPSA-BB internal termination is disabled by removing termination resistors Z1 through Z5, as shown in Figure 10 – 1.
The boot sequence provides firmware update overview information. Use Return to scroll the text, or press Ctrl/C to skip the text. After the overview information has been displayed, the name of the default boot file is provided. If it is the correct boot file, press Return at the Bootfile: prompt.
.
A W orldwide ID-to-Disk Name Con ver sion Ta b l e T able A – 1: Con ver ting Storageset Unit Numbers to Disk Names File System or Disk HSG80 Unit WWID UDID Device Name dsk n T ru64 UNIX disk Cluste.
.
Index Numbers and Special Characters 20/40 GB DL T T ape Drive ,8 – 10 cabling ,8 – 11 capacity ,8 – 10 cartridges ,8 – 10 connectors ,8 – 10 setting SCSI ID ,8 – 10 40/80-GB DL T Drive ,8 – 14 cabling ,8 – 15 capacity ,8 – 14 cartridges ,8 – 14 connectors ,8 – 14 setting SCSI ID ,8 – 14 A ACS V8.
BN39B-04 ,5 – 7, 5 – 9 BN39B-10 ,2 – 3, 5 – 7, 5 – 9 ESL9326D ,8 – 77 supported ,2 – 12 cabling 20/40 GB DL T T ape Drive ,8 – 11 40/80-GB DL T Drive ,8 – 15 Compaq 20/40 GB DL T T a.
configuring base unit as slave ,8 – 33, 8 – 70 connections to HSG80 ,6 – 58 connectors supported ,2 – 14 console serial bus ( See CSB ) console terminal need for ,7 – 9 terminal emulator ,7 .
termpwr ,3 – 9 transfer rate ,2 – 12 DS-DWZZH-05 ,3 – 8, 3 – 10 bus connectors ,3 – 10 bus isolation ,2 – 12 configurations ,3 – 15 description ,2 – 12 fair arbitration ,3 – 10 insta.
FCP ,6 – 4 Fibre Channel arbitrated loop ,6 – 8 data rates ,6 – 4 distance ,6 – 4 F_Port ,6 – 6 fabric ,6 – 5, 6 – 7 FL_Port ,6 – 5 frame ,6 – 5 N_Port ,6 – 5 NL_Port ,6 – 5 poin.
( See KGPSA, KZPBA-CB, KZPSA-BB ) HPM ,7 – 5 HSG60 controller ,1 – 13 ACS ,2 – 5 configuring ,2 – 8 port configuration ,2 – 8 transparent failover mode ,2 – 8 unit configuration ,2 – 8 H.
restrictions ,2 – 9 termination resistors ,4 – 9t, 10 – 4t, 10 – 7t use in cluster ,4 – 6, 10 – 2 KZPSA-BB displaying device information , 10 – 5t, 10 – 7t installation ,1 0 – 3 rest.
multi-unit controller ( See MUC ) multimode fibre ,6 – 17 multiple-bus failover ,1 – 14, 3 – 18, 3 – 22, 6 – 30 changing from transparent failover , 6 – 59 example configurations ,6 – 12.
HSG80 controller ,6 – 34 requirements SCSI bus ,3 – 1, 9 – 1 reset ,6 – 25, 6 – 48 resetting offsets ,6 – 59 restrictions ,2 – 8 disk devices ,2 – 9 KZPBA-CB adapters ,2 – 9 KZPSA ad.
MUC ,8 – 51 TL881/891 DL T MiniLibrary ,8 – 72 TL891 ,8 – 23 TL892 ,8 – 23 TL893 ,8 – 51 TL894 ,8 – 37 TL896 ,8 – 51 TZ885 ,8 – 17 TZ887 ,8 – 20 TZ88N-T A ,8 – 5 TZ88N-V A ,8 – 2.
system control manager ( See SCM ) system reset ,6 – 25, 6 – 48 T table of connections ,6 – 58 terminal emulator ,7 – 9 terminal server ,7 – 9 termination ,9 – 13 BA356 ,9 – 11 DWZZA ,9 .
TZ88N-V A ,8 – 1 cabling ,8 – 3 setting SCSI ID ,8 – 2 TZ89 ,8 – 6 U UltraSCSI BA356 disable termination ,9 – 17 DS-BA35X-DA personality module , 3 – 3 fast narrow SCSI drives ,3 – 3 fas.
How to Order T ru64 UNIX Documentation T o order T ru64 UNIX documentation in the United States and Canada, call 800-344-4825 . In other countries, contact your local Compaq subsidiary . If you have access to Compaq ’ s intranet, you can place an order at the following W eb site: http://asmorder.
.
Reader ’ s Comments T ruCluster Server Hardware Configuration AA-RHGWC-TE Compaq welcomes your comments and suggestions on this manual. Y our input will help us to write documentation that meets your needs.
UBPG PUBLICATIONS MANAGER Do Not Cut or Tear - Fold Here Do Not Cut or Tear - Fold Here and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES FIRST CLASS MAIL PERMIT NO.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Compaq AA-RHGWC-TE è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Compaq AA-RHGWC-TE - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Compaq AA-RHGWC-TE imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Compaq AA-RHGWC-TE ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Compaq AA-RHGWC-TE, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Compaq AA-RHGWC-TE.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Compaq AA-RHGWC-TE. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Compaq AA-RHGWC-TE insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
