Compaq AA-RHGWC-TE Uživatelský manuál

TruCluster ServerHardware ConfigurationPart Number: AA-RHGWC-TEAugust 2000Product Version: TruCluster Server Version 5.1Operating System and Version:

8.13.3.1ESL9326D Enterprise Library Robotic and Tape DriveRequired Firmware ...8–758.13.3.2Library Electronics a

Figure 4–1: KZPBA-CB Termination ResistorsInternal Wide DeviceConnector J2Internal Narrow DeviceConnector P2SCSI Bus TerminationResistors RM1-RM8ZK-14

5Setting Up the Memory Channel ClusterInterconnectThis chapter describes Memory Channel configuration restrictions, anddescribes how to set up the Mem

____________________ Note _____________________If you are installing SCSI or network adapters, you maywant to complete all hardware installation befor

Table 5–1: MC1 and MC1.5 Jumper Configuration (cont.)If hub mode is: Jumper: Example:Virtual: VH0 Pins 2 to 3123Virtual: VH1 None needed;store thejump

See the TruCluster Server Cluster Administration manual for moreinformation on failover pairs.The MC2 jumpers are described in Table 5–2.Table 5–2: MC

Table 5–2: MC2 Jumper Configuration (cont.)Jumper: Description: Example:J5: AlphaServer8x00 Mode8x00 mode selected:Pins 1 to 2a1238x00 mode not select

5.2 Installing the Memory Channel AdapterInstall the Memory Channel adapter in an appropriate peripheral componentinterconnect (PCI) slot (see Section

5.4 Installing the Memory Channel HubYou may use a hub in a two-node TruCluster Server cluster, but the hub isnot required. When there are more than t

______________________ 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 Cab

Figure 5–1 shows Memory Channel adapters connected to linecards that arein the same slot position in the Memory Channel hubs.Figure 5–1: Connecting Me

9.4.3.2Cabling an HSZ20 in a Cluster Using ExternalTermination ...9–289.4.4Cabling an HSZ40 or HSZ50 RA

Gently push the cable’s connector into the receptacle, and then use thescrews to pull the connector in tight. The connector must be tight to ensurea g

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• Ins

There are two console level Memory Channel diagnostics, mc_diag andmc_cable:• The mc_diag diagnostic:– Tests the Memory Channel adapter(s) on the syst

Example 5–1: Running the mc_cable Test>>> mc_cable 1To exit MC_CABLE, type <Ctrl/C>mca0 node id 1 is online2No response from node 0 on

5.7 Upgrading Memory Channel AdaptersIf you have a TruCluster Server configuration with redundant MC1interconnects and want to upgrade to MC2 intercon

Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 InterconnectsStepAction Refer to:1If desired,

Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 Interconnects (cont.)StepAction Refer to:____

Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 Interconnects (cont.)StepAction Refer to:Stan

Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 Interconnects (cont.)StepAction Refer to:On o

(dbx) p rm_adapters[1]->rmp_prail_va->rmc_size 5{[0] 163846[1] 0[2] 163846[3] 0[4] 163846[5] 0[6] 0[7] 0}1 Check the size of a logical rail.2 Th

5–1Running the mc_cable Test ...5–136–1Determine HSG80 Connection Names ...6–316–2Sett

Figure 5–2 shows a dual, redundant virtual hub configuration using MC1hardware being upgraded to MC2.Figure 5–2: MC1 to MC2 Virtual Hub Rolling Upgrad

Figure 5–3 through Figure 5–8 show a three-node standard hubconfiguration being upgraded from MC1 to MC2.Figure 5–3: MC1 to MC2 Standard Hub Rolling U

Figure 5–4: MC1 to MC2 Standard Hub Rolling Upgrade: First MC1 ModuleReplacedAlphaServer Member System 1MC2MC1AlphaServer Member System 2M

Figure 5–5: MC1 to MC2 Standard Hub Rolling Upgrade: Replace First MC1Adapter in Second SystemAlphaServer Member System 1MC2MC1AlphaServer Me

Figure 5–6: MC1 to MC2 Standard Hub Rolling Upgrade: Replace ThirdSystem Memory Channel AdaptersAlphaServer Member System 1MC2MC1AlphaServer

Figure 5–7: MC1 to MC2 Standard Hub Rolling Upgrade: Replace SecondMC1 in Second SystemAlphaServer Member System 1MC2MC1AlphaServer Member

Figure 5–8: MC1 to MC2 Standard Hub Rolling Upgrade: FinalConfigurationAlphaServer Member System 1MC2MC2AlphaServer Member System 2MC2MC2M

6Using Fibre Channel StorageThis chapter provides an overview of Fibre Channel, Fibre Channelconfiguration examples, and information on Fibre Channel

• The steps necessary to install and configure the Fibre Channel hardware(Section 6.5).• The steps necessary to install the base operating system and

8. See the Tru64 UNIX Installation Guide and install the base operatingsystem from the CD-ROM. The installation procedure will recognize thedisks for

1–8NSPOF Fibre Channel Cluster Using HSG80s in Multiple-BusFailover Mode ...1–162–1PCI Backplane

• Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLIReference Guide• MA6000 HSG60 Array Controller ACS Version 8.5 Solution Software forCo

6.2.1 Basic Fibre Channel TerminologyThe following list describes the basic Fibre Channel terminology:FrameAll data is transferred in a packet of info

LinkThe physical connection between an N_Port andanother N_Port or an N_Port and an F_Port. Alink consists of two connections, one to transmitinformat

Figure 6–1: Point-to-Point TopologyN_PortN_PortTransmitReceiveNode 1Node 2TransmitReceiveZK-1534U-AI6.2.2.2 FabricThe fabric topology provides more co

Figure 6–2: Fabric TopologyN_PortNode 1Node 2TransmitReceiveTransmitReceiveTransmitReceiveTransmitReceiveTransmitReceiveTransmitReceiveTransmitReceive

Figure 6–3: Arbitrated Loop TopologyNL_PortNL_PortNode 1Node 2NL_PortNL_PortTransmitReceiveTransmitReceiveTransmitReceiveTransmitReceiveNode 3Node 4Hu

6.3.1 Fibre Channel Cluster Configurations for Transparent FailoverModeWith transparent failover mode:• The hosts do not know a failover has taken pla

In transparent failover, units D00 through D99 are accessed through port 1of both controllers. Units D100 through D199 are accessed through port 2 ofb

Therefore, you want to ensure that both HSG80 controllersstart at the same time under all circumstances so that thecontroller sees its own preferred u

Figure 6–6: Multiple-Bus NSPOF Configuration Number 2ZK-1707U-AIKGPSAMemberSystem2KGPSAMemoryChannelKGPSAMemberSystem1KGPSAMemoryChannelMemory Channel

8–1TZ88N-VA SCSI ID Switches ...8–28–2Shared SCSI Buses with SBB Tape Drives ... 8–48–3DS-TZ89

Figure 6–7: Multiple-Bus NSPOF Configuration Number 3KGPSAMemberSystem2KGPSAKGPSAMemberSystem1KGPSAMemoryChannelMemoryChannelMemory ChannelInterfaceZK

Figure 6–8: A Simple Zoned ConfigurationKGPSAMemoryChannelKGPSAKGPSAKGPSAFibre Channel SwitchCluster 1MemberSystem 1Cluster 1MemberSystem 2Cluster 2Me

6.5 Installing and Configuring Fibre Channel HardwareThis section provides information about installing the Fibre Channelhardware needed to support Tr

The DS-DSGGC-AA has a default IP address of 10.77.77.77.You may need to change this IP address before you connect theswitch to the network.The DSGGA s

3. Connect the Ethernet cable.4. Connect the fiber-optic cables.5. Connect power to the switch.6. Turn on the power. The switch runs a series of power

6.5.1.2.1 Using the Switch Front PanelThe switch front panel consists of a display and four buttons. The display isnormally not active, but it lights

____________________ Note _____________________Pressing the down button selects the next lower top-levelmenu. The top-level menus are:Configuration Me

10. Use the Tab/Esc button to select Yes. Press Enter to reboot the switchand execute the POST tests.____________________ Note _____________________Af

When you have completed setting the IP address and subnet mask,disconnect the PC or terminal from the DS-DSGGB-AA or DS-DSGGC-AAswitch.6.5.1.2.4 Loggi

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

9–15TruCluster Server Cluster Using KZPSA-BB SCSI Adapters,a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID ArrayController ...

• 64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide_____________________ Caution _____________________Static electricity can damage modules and

AS8x00, GS60, GS60E, and GS140. Set the console to diagnosticmode as follows:P00>>> set mode diagConsole is in diagnostic modeP00>>>

The Link is down message indicates that one of the adapters is notavailable, probably due to its not being plugged into a switch. The warningmessage N

This display shows that the current topology for both KGPSA host busadapters is LOOP, but will be FABRIC after the next initialization.A system initia

6.5.3 Setting Up the HSG80 Array Controller for Tru64 UNIXInstallationThis section covers setting up the HSG80 controller for operation with Tru64UNIX

• 9600 BPS• 8 data bits• 1 stop bit• No parity8. Connect the RA8000 or ESA12000 to the power source and apply power.____________________ Note ________

2 Prevents the command line interpreter (CLI) from reporting amisconfiguration error resulting from not having a failover modeset.3 Puts the controlle

Example 6–1: Determine HSG80 Connection NamesHSG80 show connectionConnection UnitName Operating system Controller Port Address Status Offset!NEWCON49

____________________ Note _____________________You can change the connection name with the HSG80 CLIRENAME command. For example, assume that membersys

____________________ Note _____________________If the fiber-optic cables are not properly installed, there willbe inconsistencies in the connections s

8–9TL894 Default SCSI ID Settings ...8–378–10Hardware Components Used to Create the ConfigurationShown in Figure 8–12

– Controller B port 1 — 5000-1FE1-0000-0D63– Controller B port 2 — 5000-1FE1-0000-0D64Because the HSG80 controller’s configuration information and wor

to each of those devices. For example, to boot from storage unit D1 aspresented by the HSG80 controller, the AlphaServer console requires adevice name

• Reset the bootdef_dev console environment variable to providemultiple boot paths (Section 6.6.6).• Add additional systems to the cluster Section 6.6

Table 6–2 contains the necessary information to convert from the HSG80unit numbers to /dev/disk/dskn and device names for the exampleconfiguration. A

Example 6–2: Setting Up the Mirrorset (cont.)HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 5HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 5HSG80> CREAT

2 Create the BOOT-MIR mirrorset using disks 30200 and 30300 and theCROOT-MIR mirrorset using disks 40000 and 40100.3 Initialize the BOOT-MIR and CROOT

6.6.1.2 Adding Units and Identifiers to the HSG80 StoragesetsAfter you have created the storagesets (mirrorsets and partitions), assigna unit number t

Example 6–3: Adding Units and Identifiers to the HSG80 Storagesets(cont.)again enable the ones specifiedHSG80> set d144 ENABLE_ACCESS_PATH = !NEWCO

Record the unit name of each partition with the intended use for thatpartition (see Table 6–2).2 Set an identifier for each storage unit. Use any numb

unwanted system. Record the identifier and worldwide name for lateruse. Table 6–2 is a sample table filled in for the example. Table A–1inAppendix A i

About This ManualThis manual describes how to set up and maintain the hardwareconfiguration for a TruCluster™ Server cluster.AudienceThis manual is fo

UNIX Version 5.1 installation disk or cluster member system boot disks.Setting the device unit number allows the installation scripts to recognize aFi

console command, it would not detect the Fibre Channel devicesconnected to the HSG80.Example 6–4: Displaying the UDID and Worldwide Names of DevicesKn

or wwidmgr -set command. In this example, none of the wwidnenvironment variables is set.4. Look through the wwidmgr -show wwid display (see Example 6–

Example 6–5: Using the wwidmgr quickset Command to Set the DeviceUnit NumberP00>>> wwidmgr -quickset -udid 133Disk assignment and reachabilit

The disks are not reachable and you cannot boot until after thesystem is initialized.If you have not set the UDID, you cannot set the device unitnumbe

Example 6–6: Sample Fibre Channel Device NamesP00>>> show devdga131.1001.0.1.0 $1$DGA131 HSG80 V8.5Fdga131.1002.0.1.0 $1$DGA131 HSG80 V8.5Fdg

To set the bootdef_dev console environment variable for the Tru64 UNIXinstallation when booting from a Fibre Channel device, follow these steps:1. Obt

6.6.2 Install the Tru64 UNIX Operating SystemAfter reading the TruCluster Server Software Installation manual, andusing the Tru64 UNIX Installation Gu

67: /dev/disk/dsk20c DEC HSG80 IDENTIFIER=14368: /dev/disk/dsk21c DEC HSG80 IDENTIFIER=144If you know that you have set the UDID for a large number of

2. Search the display for the UDIDs (or worldwide names) for each of thecluster installation disks and record the /dev/disk/dskn values.If you used th

Chapter 7 Describes the use of AlphaServer™ GS80, GS160, or GS320 hardwarepartitions in a TruCluster Server configuration.Chapter 8 Describes how to c

To reset the bootdef_dev console environment variable, follow these steps:1. Obtain the device name and worldwide name for the Fibre Channel unitfrom

or wwidmgr -show reachability). You must initialize the system touse any of the device names in the bootdef_dev variable as follows:P00>>> se

b. Set the bootdef_dev console environment variable to onereachable path (Yes in the connected column of Example 6–7) tothe member system boot disk:P0

dga132.1004.0.1.0 1dgb132.1002.0.2.0 2dgb132.1003.0.2.0 3dga132.1001.0.1.0 41 Path from host bus adapter A to controller A port 12 Path from host bus

6.7.1 OverviewThe change in failover modes cannot be accomplished with a simple SETMULTIBUS COPY=THIS HSG80 CLI command because:• Unit offsets are not

6.7.2 Procedure to Convert from Transparent to Multiple-bus FailoverModeTo change from transparent failover to multiple-bus failover mode byresetting

HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7!NEWCON58 TRU64_UNIX OTHER 1 offline 0HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-

__________________ Note ___________________You must set the console to diagnostic mode to usethe wwidmgr command for the following AlphaServersystems:

wwid2wwid3N1 50001fe100000d64N2 50001fe100000d62N3 50001fe100000d63N4 50001fe100000d61P00>>> inith. Set the bootdef_dev console environment v

nodename 5000-1FE1-0000-0CB0SCSI tgt id 5 : portname 1000-0000-C920-A7AEnodename 1000-0000-C920-A7AESCSI tgt id 6 : portname 1000-0000-C920-CD9Cnodena

The StorageWorks™ UltraSCSI Configuration Guidelines documentprovides guidelines regarding UltraSCSI configurations.For information about setting up a

portname 2004-0060-6900-5A1Bnodename 1000-0060-6900-5A1BPresent, Logged in, F_PORT,1 Status of the emx1 link. The connection is a point-to-point fabri

______________________ Note _______________________You can use the emxmgr utility interactively to perform any ofthe previous functions.6.8.2 Using th

x. Exit----> 2emx0 SCSI target id assignments:SCSI tgt id 0 : portname 5000-1FE1-0000-0CB2nodename 5000-1FE1-0000-0CB0SCSI tgt id 5 : portname 1000

7Using GS80, GS160, or GS320 HardPartitions in a TruCluster ServerConfigurationThis chapter contains information about using AlphaServer GS80/160/320h

7.2 Hardware Requirements for a Hard Partition in a ClusterThe TruCluster Server hardware requirements are the same for anAlphaServer GS80/160/320 har

Figure 7–1: Portion of QBB Showing I/O Riser ModulesI/O RiserBN39B I/O Riser Cable ZK-1749U-AI____________________ Notes ____________________You can h

We recommend that you connect I/O riser 0 (local I/O riserports 0 and 1) to the primary PCI drawer that will be themaster system control manager (SCM)

1) that is higher than the master SCM. Both the master SCMand standby SCM must have the scm_csb_master_eligibleSCM environment variable set.__________

types of PCI drawers. It is harder to distinguish the type of PCI drawerfrom the rear, but slot 1 provides the key. The primary PCI drawer has astanda

Figure 7–3: Rear View of Expansion and Primary PCI DrawersZK-1751U-AIExpansion PCI DrawerPrimary PCI DrawerConsole SerialBus Node ID ModuleLocal Termi

© 2000 Compaq Computer CorporationCOMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, AlphaServer,StorageWorks, TruClust

• Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide• Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide• Compaq StorageW

equally well with any number of partitions (as supported by the systemtype) by modifying the amount and placement of hardware and the SCMenvironment v

• Shared storage that is connected to KZPBA-CB (parallel SCSI) orKGPSA-CA (Fibre Channel) host bus adapters.• Network controllers.3. Install BN39B cab

____________________ Notes ____________________If the OCP key switch is in the On or Secure position, thesystem will go through the power-up sequence.

Example 7–1: Defining Hard Partitions with SCM Environment Variables(cont.)HP_QBB_MASK5 0HP_QBB_MASK6 0HP_QBB_MASK7 0SROM_MASK ff fXSROM_MASK ff ff ff

scm_csb_master_eligible environment variable. The master andstandby SCM must be connected to the OCP. The master SCM musthave the lowest node ID.Use t

2 Turn on power to partition 1.3 Transfer control from the SCM firmware to the SRM firmware.____________________ Note _____________________If the auto

7.4 Determining AlphaServer GS80/160/320 SystemConfigurationYou may be required to reconfigure an AlphaServer GS80/160/320 systemthat is not familiar

2 QBB number and console serial bus (CSB) node ID. QBB 0 and 1 (CSBnode IDs 30 and 31) are in partition 0. QBB 2 and 3 (CSB node IDs 32and 33) are in

12 Console serial bus node ID for PCI drawers. In this example, the firstPCI drawer has node ID 10. The second PCI drawer has node ID 11.Note that in

Example 7–4: Displaying Console Serial Bus Information (cont.)C3 CPU3/SROM V5.0-7 ONC0 IOR0 ONC1 IOR1 ON31 PSM T05.4 (03.24/01:09) T4.0 (07.06) ON Srv

• For more information on the ESL9326D Enterprise Library, seethe following Compaq StorageWorks ESL9000 Series Tape Librarydocumentation:–Unpacking an

• SCM master: This PCI primary drawer has the master SCM.• SCM slave: The SCM on this PCI primary drawer is a slave and hasnot been designated as a ba

– 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

5. Turn power on to the system to allow SRM firmware execution. TheSRM code is copied to memory on the partition primary QBB during thepower-up initia

___________________ Caution ___________________Do not abort the update — doing so can cause a corrupt flashimage in a firmware module.A complete firmw

8Configuring a Shared SCSI Bus for TapeDrive UseThe topics in this section provide information on preparing the various tapedevices for use on a share

8.1.1 Setting the TZ88N-VA SCSI IDYou must set the TZ88N-VA switches before the tape drive is installed intothe BA350 StorageWorks enclosure. The Auto

Table 8–1: TZ88N-VA Switch SettingsSCSI ID SCSI ID Selection Switches123456AutomaticaOff Off Off On On On0Off Off Off Off Off Off1On Off Off Off Off O

Figure 8–2 shows a TruCluster Server cluster with three shared SCSI buses.One shared bus has a BA350 with a TZ88N-VA at SCSI ID 3.Figure 8–2: Shared S

Table 8–2: Hardware Components Used to Create the Configuration Shownin Figure 8–2 (cont.)Callout NumberDescription8DWZZA-VA with H885-AA trilink conn

Reader’s CommentsCompaq welcomes any comments and suggestions you have on this andother Tru64 UNIX manuals.You can send your comments in the following

The single-ended SCSI bus may be daisy chained from one single-endedtape drive to another with BC19J cables as long as the SCSI bus maximumlength is n

Figure 8–3: DS-TZ89N-VW SCSI ID SwitchesSnap−inLockingHandlesSCSI IDSwitch PackBackplaneInterfaceConnectorDS−TZ89N−VWThe SCSI ID is selected by switch

Table 8–3: DS-TZ89N-VW Switch Settings (cont.)SCSI ID SCSI ID Selection Switches123456785On Off On Off Off Off Off Off6Off On On Off Off Off Off Off7O

8.2.3 Setting the DS-TZ89N-TA SCSI IDThe DS-TZ89N-TA has a push-button counter switch on the rear panel toselect the SCSI ID. It is preset at the fact

8.3 Compaq 20/40 GB DLT Tape DriveThe Compaq 20/40 GB DLT Tape Drive is a Digital Linear Tape (DLT)tabletop cartridge tape drive capable of holding up

Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel+-020/40 GB DLT Tape DriveSCSI IDSelectorSwitchSCSI ID+-0ZK-1603U-AI8.3.2 Cabling the Compaq 20/4

cable). Ensure that the trilink or Y cable at both ends of the differentialsegment of the shared SCSI bus is terminated with an HD68 differentialtermi

Figure 8–5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT TapeDriveKZPBA-CB (ID 7)MemoryChannelInterfaceMemory ChannelKZPBA-CB (ID 6)Memory Cha

Table 8–4: Hardware Components Used to Create the Configuration Shownin Figure 8–5 (cont.)Callout NumberDescription9199629-002 or 189636-002 (68-pin h

8.4.2 Cabling the Compaq 40/80-GB DLT DriveThe Compaq 40/80-GB DLT Drive is connected to a single-ended segmentof the shared SCSI bus. Figure 8–6 show

fileItalic (slanted) type indicates variable values,placeholders, and function argument names...A vertical ellipsis indicates that a portion of anexa

To achieve system performance capabilities, we recommend that you placeno more than two Compaq 40/80-GB DLT Drives on a SCSI bus, and thatyou place no

Table 8–5: Hardware Components in the Configuration in Figure 8–6 (cont.)Callout NumberDescription8H885-AA trilink connector9189646-001 (0.9 meter cab

8.5.2 Cabling the TZ885 Tape DriveThe TZ885 is connected to a single-ended segment of the shared SCSIbus. It is connected to a differential portion of

______________________ Note _______________________Ensure that there is no conflict with tape drive and host busadapter SCSI IDs.Figure 8–7: Cabling a

Table 8–6: Hardware Components Used to Create the Configuration Shownin Figure 8–6 (cont.)Callout NumberDescription8H885-AA trilink connector9BN21M ca

Figure 8–8: TZ887 DLT MiniLibrary Rear Panel+-0TZ887ZK-1461U-AISCSI IDSCSI IDSelectorSwitch+-08.6.2 Cabling the TZ887 Tape DriveThe TZ887 is connected

length is not exceeded and there are sufficient SCSI IDs available. Ensurethat the tape drive on the end of the bus is terminated with an H8574-A orH8

8.7 Preparing the TL891 and TL892 DLT MiniLibraries forShared SCSI Usage______________________ Note _______________________To achieve system performan

The first and second lines of the default screen show the status of the twodrives (if present). The third line shows the status of the library robotic

4. Select the tape drive (DLT0 Bus ID: or DLT1 Bus ID:) or library robotics(LIB Bus ID:) for which you wish to change the SCSI bus ID. The defaultSCSI

SCSI bus without stopping all ASE services that generate activityon the bus.For this reason, we recommend that tape devices be placed onseparate share

To connect the drive robotics and one drive to one shared SCSI bus and thesecond drive to a second shared SCSI bus, follow these steps:1. Connect a BN

Figure 8–10: TruCluster Server Cluster with a TL892 on Two Shared SCSIBusesKZPBA-CB (ID 7)MemoryChannelInterfaceMemory ChannelKZPBA-CB (ID 6)Member Sy

8.8 Preparing the TL890 DLT MiniLibrary Expansion UnitThe topics in this section provide information on preparing the TL890 DLTMiniLibrary expansion u

8.8.2.1 Cabling the DLT MiniLibrariesYou must make the following connections to render the DLT MiniLibrarysystem operational:• Expansion unit to the m

____________________ Notes ____________________Do not connect a SCSI bus to the SCSI connectors for thelibrary connectors on the base modules.We recom

Figure 8–11: TL890 and TL892 DLT MiniLibraries on Shared SCSI BusesTL892TL892TL890LibraryRoboticsDLT1Expansion ModulesRoboticsControlcablesDLT2Library

Table 8–8: Hardware Components Used to Create the Configuration Shownin Figure 8–10Callout NumberDescription1BN38C or BN38D cablea2BN37A cableb3H8861-

After a series of power-on self-tests have executed, the default screenwill be displayed on the base module control panel:DLT0 IdleDLT1 IdleLoader Idl

inventory of modules may be incorrect and the contents of some or all of themodules will be inaccessible to the system and to the host.When the expans

1IntroductionThis chapter introduces the TruCluster Server product and some basiccluster hardware configuration concepts.Subsequent chapters describe

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

______________________ Note _______________________To achieve system performance capabilities, we recommendplacing no more than two TZ89 drives on a S

Menu: ConfigurationInquiry6. Press and release the up or down arrow buttons to locate the SCSIAddress submenu, and verify that the following informati

6. Press and release the SELECT button again to choose SCSI Addressand verify that the following information is shown in the SDA:Menu: SCSI AddressRob

Figure 8–12: TL894 Tape Library Four-Bus ConfigurationRobotics Controller*SCSI Address 0Rear PanelHost Connection #1SCSI Port 1SCSI Port 2SCSI Port 3S

installing an HD68 SCSI bus terminator on the SCSI bus portconnector on the cabinet exterior.This is not wrong, but by reconfiguring in this manner, t

In Figure 8–13, one bus is connected to port 1 (robotics controller and tapedrives 0 and 1) and the other bus is connected to port 3 (tape drives 2 an

Table 8–10: Hardware Components Used to Create the ConfigurationShown in Figure 8–12 (cont.)Callout NumberDescription6H879-AA terminator7328215-00X, B

The physical SCSI IDs should match the SCSI IDs set by thelibrary electronics. Ensure that the SCSI ID set by the rotaryswitch and from the control pa

3. On the Operator screen, press the Configure Library button. TheConfigure Library screen displays the current library configuration.________________

interconnect, you can more easily alter or expand your cluster’s hardwareconfiguration as newer and faster technologies become available.1.2 Memory Re

You can reconfigure the tape drives and robotics controller to place multipletape drives on the same SCSI bus with SCSI bus jumper (part number6210567

Figure 8–14: TL895 Tape Library Internal CablingRoboticsControllerSCSI ID 0SCSI Port 5SCSI Port 4SCSI Port 3 Tape Drive 0SCSI ID 1 Tape Drive 1SCSI

electronic SCSI ID using the Configure menu from the control panel (seeSection 8.10.2).The actual upgrade is beyond the scope of this manual. See the

Each tape library comes configured with a robotic controller and bar codereader (to obtain quick and accurate tape inventories).The libraries have eit

These tape libraries each have a multi-unit controller (MUC) that servestwo functions:• It is a SCSI adapter that allows the SCSI interface to control

Table 8–12: MUC Switch Functions (cont.)SwitchFunction7Host selection: Down for SCSI, up for seriala8Must be down, reserved for testingaFor a TruClust

Table 8–15: TL896 Default SCSI IDsSCSI PortDeviceDefault SCSI IDMUC2DDrive 5 (top)5E Drive 44F Drive 33A Drive 25B Drive 14C Drive 0 (bottom)38.11.5 T

Figure 8–15: TL893 Three-Bus ConfigurationMUCSCSI Address 2SCSI Port A SCSI Port B SCSI Port CTZ89 Tape DriveSCSI Address 5 (top shelf)TZ89 Tape Dr

– The lower bay bottom shelf tape drive (tape drive 0, SCSI ID 3) is onSCSI Port C and is terminated on the tape drive.– The tape drive terminators ar

on the shared SCSI bus. Each SCSI bus must be terminated internal to thetape library at the tape drive itself with the installed SCSI terminators.Ther

Because the Tru64 UNIX operating system will be available on the firstcluster member, in an emergency, after shutting down the cluster, you havethe op

Figure 8–17: Shared SCSI Buses with TL896 in Three-Bus ModeKZPBA-CB (ID 7)MemoryChannelInterfaceMemory ChannelKZPBA-CB (ID 6)DS-DWZZH-03TTT21413Storag

Table 8–16: Hardware Components Used to Create the ConfigurationShown in Figure 8–16 (cont.)Callout NumberDescription6H879-AA terminator7328215-00X, B

8.12.1.2 TL881 and TL891 MiniLibrary Rackmount ComponentsA TL881 or TL891 base unit (which contains the tape drive(s)) can operateas an independent, s

• Data unit — This rackmount module contains a 16-cartridge magazineto provide additional capacity in a multi-module configuration. The dataunit robot

Table 8–17: TL881 and TL891 MiniLibrary Performance and Capacity ComparisonTL881 MiniLibrary TL891 MiniLibraryConfiguredforMaximum:Number ofBase Units

Table 8–18: DLT MiniLibrary Part Numbers (cont.)DLT Library ComponentNumber of TapeDrivesTabletop/RackmountPart NumberTL891 DLT MiniLibraryBase Unit2R

For complete hardware installation instructions, see the TL881 MiniLibrarySystem User’s Guide or TL891 MiniLibrary System User’s Guide.8.12.2.1.1 Sett

status until you exit the Menu Mode and the Ready lightcomes on once again.2. Depress the down arrow button until the Configure Menu item isselected,

______________________ Note _______________________The tape drive SCSI connectors are labeled DLT1 (tape drive 1)and DLT2 (tape drive 2). The control

3. Install an HD68 differential terminator (such as an H879-AA) on theright DLT1 connector (the fourth connector from the left).To connect the drive r

partitions. You can move the swap partition off the member boot disk. Seethe TruCluster Server Cluster Administration manual for more information.1.3.

Figure 8–18: TL891 Standalone Cluster ConfigurationKZPBA-CB (ID 7)MemoryChannelInterfaceMemory ChannelKZPBA-CB (ID 6)Memory ChannelMemberSystem 2

Table 8–19: Hardware Components Used to Create the ConfigurationShown in Figure 8–17 (cont.)Callout NumberDescription6H879-AA terminator7328215-00X, B

connector on the data unit and the female end to any Expansion Modulesconnector on the expansion unit._____________________ Note _____________________

Figure 8–19: TL891 DLT MiniLibrary Rackmount ConfigurationKZPBA-CB (ID 7)MemoryChannelInterfaceMemory ChannelKZPBA-CB (ID 6)Member System 1DS-DWZZH-03

Table 8–20: Hardware Components Used to Create the ConfigurationShown in Figure 8–18Callout NumberDescription1BN38C or BN38D cablea2BN37A cableb3H8861

DLT0 IdleDLT1 IdleLoader Idle0>__________<9The default screen shows the state of the tape drives, loader, andnumber of cartridges present for th

When the expansion unit comes up, it will communicate with each base anddata unit through the expansion unit interface and inventory the numberof base

• DLT3 Bus ID: 4• DLT4 Bus ID: 5• DLT5 Bus ID: 67. Press Enter when you have the item selected for which you wish tochange the SCSI ID.8. Use the up a

______________________ Note _______________________These tape devices have been qualified for use on shared SCSIbuses with both the KZPSA-BB and KZPBA

______________________ Notes ______________________The ESL9326D Enterprise Library is cabled internally for two35/70 DLT tape drives on each SCSI bus.

Figure 1–1 shows a generic two-node cluster with the minimum numberof disks.• Tru64 UNIX disk• Clusterwide root (/), /usr, and /var• Member 1 boot dis

Figure 8–20: ESL9326D Internal CablingTTape Drive 0Tape Drive 1Tape Drive 2Tape Drive 3Tape Drive 4Tape Drive 5Tape Drive 6Tape Drive 7Tape Drive 8Tap

8.13.3.4 Connecting the ESL9326D Enterprise Library to the Shared SCSI BusThe ESL9326D Enterprise Library has 5 meters of internal SCSI bus cablingfor

______________________ Notes ______________________Each ESL9326D Enterprise Library arrives with one 330563-001HD68 terminator for each pair of tape d

9Configurations Using ExternalTermination or Radial Connectionsto Non-UltraSCSI DevicesThis chapter describes the requirements for the shared SCSI bus

9.1 Using SCSI Bus Signal ConvertersA SCSI bus signal converter allows you to couple a differential bus segmentto a single-ended bus segment, allowing

but you would waste a disk slot and it would not work with a KZPBA-CB ifthere are any UltraSCSI disks in the storage shelves.The following sections di

Figure 9–1: Standalone SCSI Signal ConverterZK-1050U-AITTSingle-ended Differential side with trilinkattachedsideFigure 9–2 shows the status of interna

______________________ Notes ______________________S4-3 and S4-4 have no function on the DS-BA35X-DA personalitymodule.See Section 9.3.2.2 for informa

Whenever possible, connect devices to a shared bus so that they can beisolated from the bus. This allows you to disconnect devices from the busfor mai

connector at a later time without affecting bus termination. This allows youto expand your configuration without shutting down the cluster.Figure 9–4

ContentsAbout This Manual1 Introduction1.1The TruCluster Server Product ... 1–11.2Memory Requirements ...

Administration manual for a discussion of how and when to use a quorumdisk.Figure 1–2: Generic Two-Node Cluster with Minimum Disk Configurationand Quo

Figure 9–5: HD68 Trilink Connector (H885-AA)FRONT VIEWREAR VIEWZK-1140U-AI______________________ Note _______________________If you connect a trilink

9.3.1 BA350 Storage ShelfUp to seven narrow (8-bit) single-ended StorageWorks building blocks(SBBs) can be installed in the BA350. Their SCSI IDs are

Figure 9–6: BA350 Internal SCSI BusJA1JB10123456POWER (7)TJZK-1338U-AI9.3.2 BA356 Storage ShelfThere are two variations of the BA356 used in TruCluste

select SCSI IDs 0 through 6, set the personality module address switches 1through 7 to off. To select SCSI IDs 8 through 14, set personality moduleadd

Figure 9–7: BA356 Internal SCSI BusJA1JB10123456POWER (7)JZK-1339U-AINote that JA1 and JB1 are located on the personality module (in the top ofthe box

Figure 9–8: BA356 Jumper and Terminator Module Identification PinsSlot 6JumperPinSlot 6TerminatorPinSlot 1JumperPinSlot 1TerminatorPinZK-1529U-AI9.3.2

BA356, as shown in Figure 9–8. With proper lighting you will be able to seea J or T near the hole where the pin sticks through.Termination for both en

Later sections describe how to install cables to configure an HSZ20, HSZ40,or HSZ50 in a TruCluster Server configuration with two member systems.9.4.1

2. You will need a DWZZA-VA signal converter for the BA350. Ensurethat the DWZZA-VA single-ended termination jumper, J2, is installed.Remove the termi

SCSI bus (cable and BA356) under the 3-meter limit to still allow highspeed operation.If you are using a DWZZB-VW, install it in slot 0 of the BA356.9

• Using a RAID array controller in transparent failover mode allows theuse of hardware RAID to mirror the disks. However, without a secondSCSI bus, se

must be used with a BA356 or UltraSCSI BA356 if more thanfive disks are required.The following sections provide the steps needed to connect two storag

Figure 9–9 shows a two-member TruCluster Server configuration usinga BA350 and a BA356 for storage.Figure 9–9: BA350 and BA356 Cabled for Shared SCSI

Table 9–1: Hardware Components Used for Configuration Shown in Figure8–9 and Figure 8–10Callout NumberDescription1BN21W-0B Y cable2H879-AA terminator3

Figure 9–10 shows a two member TruCluster Server configuration using twoBA356s for storage.Figure 9–10: Two BA356s Cabled for Shared SCSI Bus UsageID

9.4.2.3 Connecting Two UltraSCSI BA356s for Shared SCSI Bus UsageWhen you use two UltraSCSI BA356 storage shelves on a shared SCSI busin a TruCluster

Figure 9–11 shows a two member TruCluster Server configuration usingtwo UltraSCSI BA356s for storage.Figure 9–11: Two UltraSCSI BA356s Cabled for Shar

Table 9–2: Hardware Components Used for Configuration Shown in Figure9–11Callout NumberDescription1BN21W-0B Y cable2H879-AA HD68 terminator3BN38C (or

9.4.3.1 Cabling an HSZ40 or HSZ50 in a Cluster Using External TerminationTo connect an HSZ40 or HSZ50 controller to an externally terminated sharedSCS

Figure 9–12 shows two AlphaServer systems in a TruCluster Serverconfiguration with dual-redundant HSZ50 RAID controllers in the middleof the shared SC

Figure 9–13: Externally Terminated Shared SCSI Bus with HSZ50 RAIDArray Controllers at Bus EndKZPSA-BB (ID 7)NetworkMemoryChannelInterfaceMemory Chann

Figure 1–3: Minimum Two-Node Cluster with UltraSCSI BA356 Storage UnitID 5PWRSharedSCSIBusClusterwide/, /usr, /varMember 1Boot DiskMember 2Boot DiskQu

9.4.3.2 Cabling an HSZ20 in a Cluster Using External TerminationTo connect a SWXRA-Z1 (HSZ20 controller) to a shared SCSI bus, followthese steps:1. Re

2. Attach the trilink with the terminator to the controller that you wantto be on the end of the shared SCSI bus. Attach an H885-AA trilinkconnector t

Figure 9–14 shows a sample configuration with radial connection ofKZPSA-BB PCI-to-SCSI adapters, DS-DWZZH-03 UltraSCSI hub, and anHSZ50 RAID array con

Figure 9–15 shows a sample configuration that uses KZPSA-BB SCSIadapters, a DS-DWZZH-05 UltraSCSI hub, and an HSZ50 RAID arraycontroller.Figure 9–15:

10Configuring Systems for ExternalTermination or Radial Connections toNon-UltraSCSI DevicesThis chapter describes how to prepare the systems for a Tru

Follow the steps in Table 10–1 to start the TruCluster Server hardwareinstallation procedure. You can save time by installing the Memory Channeladapte

The DWZZH-series UltraSCSI hubs are designed to allow more separationbetween member systems and shared storage. Using the UltraSCSI hub alsoimproves t

_____________________ Note _____________________You may have problems if the member system supports thebus_probe_algorithm console variable and it is

Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connectionto a DWZZH UltraSCSI Hub (cont.)StepAction Refer to:2Power down the system. Insta

this slot can be used for a second power supply to provide fullyredundant power to the storage shelf.With the use of the cluster file system (see the

Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connectionto a DWZZH UltraSCSI Hub (cont.)StepAction Refer to:6Use the show pk* or show isp

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with ExternalTerminationStepAction Refer to:1Remove the KZPSA-BB internal terminationresistors,

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with ExternalTermination (cont.)StepAction Refer to:7Use the show pk* or show isp* consolecomman

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with ExternalTermination (cont.)StepAction Refer to:TL890 with TL891/TL892 Section 8.8TL894 Sect

Example 10–1: Displaying Configuration on an AlphaServer 4100 (cont.)CPU (4MB Cache) 3 0000 cpu0CPU (4MB Cache) 3 0000 cpu1Bridge (IOD0/IOD1) 600 0021

Example 10–2: Displaying Devices on an AlphaServer 4100 (cont.)dkd100.1.0.4.1 DKd100 RZ26N 0568dkd200.1.0.4.1 DKd200 RZ26 392Adkd300.1.0.4.1 DKd300 RZ

Example 10–4: Displaying Devices on an AlphaServer 8200>>> show devicepolling for units on isp0, slot0, bus0, hose0...polling for units on is

10.1.4 Displaying Console Environment Variables and Setting theKZPSA-BB and KZPBA-CB SCSI IDThe following sections show how to use the show console co

Example 10–5: Displaying the pk* Console Environment Variables on anAlphaServer 4100 System (cont.)pkf0_fast 1pkf0_host_id 7pkf0_termpwr 1Compare the

Example 10–6: Displaying Console Variables for a KZPBA-CB on anAlphaServer 8x00 SystemP00>>> show isp*isp0_host_id 7isp0_soft_term onisp1_hos

UNIX Version 5.0, 16 devices are supported on a SCSI bus. Therefore,multiple BA356 storage units can be used on the same SCSI bus to allowmore devices

Example 10–7: Displaying Console Variables for a KZPSA-BB on anAlphaServer 8x00 System (cont.)pkc0_fast 1pkc0_host_id 7pkc0_termpwr on10.1.4.2 Setting

10.1.4.3 Setting KZPSA-BB SCSI Bus ID, Bus Speed, and Termination PowerIf the KZPSA-BB SCSI ID is not correct, or if it was reset to 7 by thefirmware

10.1.4.4 KZPSA-BB and KZPBA-CB Termination ResistorsThe KZPSA-BB internal termination is disabled by removing terminationresistors Z1 through Z5, as s

The boot sequence provides firmware update overview information. UseReturn to scroll the text, or press Ctrl/C to skip the text.After the overview inf

AWorldwide ID-to-Disk Name ConversionTableTable A–1: Converting Storageset Unit Numbers to Disk NamesFile Systemor DiskHSG80UnitWWID UDID Device Name

IndexNumbers and SpecialCharacters20/40 GB DLT Tape Drive,8–10cabling,8–11capacity,8–10cartridges,8–10connectors,8–10setting SCSI ID,8–1040/80-GB DLT

BN39B-04,5–7, 5–9BN39B-10,2–3, 5–7, 5–9ESL9326D,8–77supported,2–12cabling20/40 GB DLT Tape Drive,8–1140/80-GB DLT Drive,8–15Compaq 20/40 GB DLT Tape D

configuring base unit as slave,8–33,8–70connections to HSG80,6–58connectorssupported,2–14console serial bus( See CSB )console terminalneed for,7–9term

file systems and the data disks across SCSI buses, removing the single SCSIbus as a single point of failure for these file systems.1.5.3 Two-Node Conf

termpwr,3–9transfer rate,2–12DS-DWZZH-05,3–8, 3–10bus connectors,3–10bus isolation,2–12configurations,3–15description,2–12fair arbitration,3–10install

FCP,6–4Fibre Channelarbitrated loop,6–8data rates,6–4distance,6–4F_Port,6–6fabric,6–5, 6–7FL_Port,6–5frame,6–5N_Port,6–5NL_Port,6–5point-to-point,6–6r

( See KGPSA, KZPBA-CB,KZPSA-BB )HPM,7–5HSG60 controller,1–13ACS,2–5configuring,2–8port configuration,2–8transparent failover mode,2–8unit configuratio

restrictions,2–9termination resistors,4–9t, 10–4t,10–7tuse in cluster,4–6, 10–2KZPSA-BBdisplaying device information,10–5t, 10–7tinstallation,10–3rest

multi-unit controller( See MUC )multimode fibre,6–17multiple-bus failover,1–14, 3–18,3–22, 6–30changing from transparent failover,6–59example configur

HSG80 controller,6–34requirementsSCSI bus,3–1, 9–1reset,6–25, 6–48resetting offsets,6–59restrictions,2–8disk devices,2–9KZPBA-CB adapters,2–9KZPSA ada

MUC,8–51TL881/891 DLT MiniLibrary,8–72TL891,8–23TL892,8–23TL893,8–51TL894,8–37TL896,8–51TZ885,8–17TZ887,8–20TZ88N-TA,8–5TZ88N-VA,8–2setting SCSI IDsES

system control manager( See SCM )system reset,6–25, 6–48Ttable of connections,6–58terminal emulator,7–9terminal server,7–9termination,9–13BA356,9–11DW

TZ88N-VA,8–1cabling,8–3setting SCSI ID,8–2TZ89,8–6UUltraSCSI BA356disable termination,9–17DS-BA35X-DA personality module,3–3fast narrow SCSI drives,3–

How to Order Tru64 UNIX DocumentationTo order Tru64 UNIX documentation in the United States and Canada, call800-344-4825. In other countries, contact

Figure 1–5: Two-Node Configurations with UltraSCSI BA356 Storage Unitsand Dual SCSI BusesHost Bus Adapter (ID 7)NetworkMemoryChannelInterfaceMemory Ch

Reader’s CommentsTruCluster ServerHardware ConfigurationAA-RHGWC-TECompaq welcomes your comments and suggestions on this manual. Your input will help

UBPG PUBLICATIONS MANAGER Do Not Cut or Tear - Fold Here Do Not Cut or Tear - Fold Here and Tape NO POSTAGENECESSARY IFMAILED IN THEUNITE

instead of the HSZ70. The array controllers can be configured as a dualredundant pair. If you want the capability to fail over from one controller toa

Note that in the configuration shown in Figure 1–6, there is only one sharedSCSI bus. Even by mirroring the clusterwide root and member boot disks,the

Figure 1–7: NSPOF Cluster Using HSZ70s in Multiple-Bus Failover ModeNetworksHost Bus Adapter (ID 7)Member System 1 Member System 2Tru64UNIXDiskHost Bu

2.6SCSI Signal Converters ...2–102.7DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs ... 2–112.8SCSI Cabl

Figure 1–8: NSPOF Fibre Channel Cluster Using HSG80s in Multiple-BusFailover ModeKGPSAMemberSystem2KGPSAKGPSAMemberSystem1KGPSAMemoryChannelMemoryChan

5. Prepare the shared storage by installing disks and configuring any RAIDcontroller subsystems (see Chapter 3, Chapter 6, and Chapter 9 and thedocume

2Hardware Requirements and RestrictionsThis chapter describes the hardware requirements and restrictions fora TruCluster Server cluster. It includes l

arbitration enabled when connecting four-member systems to acommon SCSI bus.• The following items pertain to the AlphaServer GS80/160/320 systems:– Ho

2.2 Memory Channel RestrictionsThe Memory Channel interconnect is used for cluster communicationsbetween the member systems.There are currently three

• In an MC2 configuration, you can use a CCMFB optical converter inconjunction with the MC2 CCMAB module to increase the distancebetween systems.• The

each Memory Channel adapter on one system must be connected to thesame linecard in each Memory Channel hub.2.3 Host Bus Adapter RestrictionsTo connect

____________________ Notes ____________________The Model 4124R disk enclosure is a single-bus enclosure thathas slots for 14 drives, but only 12 drive

The maximum number of drives behind an HSG80 (single ordual-redundant pair) using three dual-bus Model 4254 diskenclosures is 42.The Model 4214R and M

4.3.1Installation of a KZPBA-CB Using Internal Terminationfor a Radial Configuration ...4–74.3.2Displaying KZPBA-CB

• A maximum of three cascaded switches is supported, with a maximum oftwo hops between switches. The maximum hop length is 10 km longwavesingle-mode o

AlphaServer 800, 1000, 1000A, 2000, 2100, or 2100A systems supportthe variable), you must set the bus_probe_algorithm console variableto new by enteri

RAID array controllers require the minimum Array Controller Software(ACS) shown in Table 2–1.Table 2–1: RAID Controller Minimum Required Array Control

______________________ Note _______________________We could list the UltraSCSI hubs because they contain a DOC(DWZZA on a chip) chip, but they are dis

• The lower righthand device slot of the BA370 shelf within the RA7000or ESA 10000 RAID array subsystems. This position minimizes cablelengths and int

Table 2–3: Supported SCSI CablesCable ConnectorDensityPinsConfiguration UseBN21W-0B Three high 68-pin A Y cable that can be attached to aKZPSA-BB or K

2.9 SCSI Terminators and Trilink ConnectorsTable 2–4 describes the supported trilink connectors and SCSI terminatorsand the context in which you would

3Shared SCSI Bus Requirements andConfigurations Using UltraSCSI HardwareA TruCluster Server cluster uses shared SCSI buses, external storageshelves or

This chapter discusses the following topics:• Shared SCSI bus configuration requirements (Section 3.1)• SCSI bus performance (Section 3.2)• SCSI bus d

storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storagearrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves aresupported with UltraSCS

6.2.2.2Fabric ...6–76.2.2.3Arbitrated Loop Topology ...6–86.3Exam

cable or a backplane, and cable or backplane connectors. Each UltraSCSIbus segment must have a terminator at each end of the bus segment.Up to two Ult

You cannot use a DWZZA or DWZZB signal converter at UltraSCSI speedsfor TruCluster Server if there are any UltraSCSI disks on the bus, becausethe DWZZ

______________________ Note _______________________If you are using a DS-DWZZH-05 UltraSCSI hub with fairarbitration enabled, SCSI ID numbering will c

Because of the cable length limit, youmust plan your hardware configurationcarefully, and ensure that each SCSI bus meets the cable limit guidelines.I

Figure 3–1 shows a VHDCI trilink connector (UltraSCSI), which you mayattach to an HSZ70 or HSZ80.Figure 3–1: VHDCI Trilink Connector (H8861-AA)CXO5744

• Require that termination power (termpwr) be provided by the SCSI bushost adapters on each SCSI bus segment._____________________ Note ______________

Figure 3–2: DS-DWZZH-03 Front ViewDifferential symbolZK-1412U-AIThe differential symbol (and the lack of a single-ended symbol) indicatesthat all thre

• The lower righthand device slot of the BA370 shelf within the RA7000or ESA 10000 RAID array subsystems. This position minimizes cablelengths and int

3.6.1.2.2 DS-DWZZH-05 Fair ArbitrationAlthough each cluster member system and storage controller connected to anUltraSCSI hub are on separate SCSI bus

3.6.1.2.3 DS-DWZZH-05 Address ConfigurationsThe DS-DWZZH-05 has two addressing modes: wide addressing mode andnarrow addressing mode. With either addr

6.6.2Install the Tru64 UNIX Operating System ... 6–516.6.3Determining /dev/disk/dskn to Use for a ClusterInstallation ...

Figure 3–3: DS-DWZZH-05 Rear ViewW1ZK-1448U-AI3–14 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware

Figure 3–4: DS-DWZZH-05 Front ViewFair DisableHost PortSCSI ID1(13)Host PortSCSI ID3(15)ControllerPortSCSI ID6 - 4(6 - 0)Busy02ZK-1447U-AIHost PortHos

2. If fair arbitration is to be used, ensure that the switch on the front ofthe DS-DWZZH-05 UltraSCSI hub is in the Fair position.3. Install the DS-DW

3.7.1 Configuring Radially Connected TruCluster Server Clusterswith UltraSCSI HardwareRadial configurations with RAID array controllers allow you to t

or SCSI bus failure, the host can redistribute the load to the survivingcontroller. In case of a controller failure, the surviving controller will han

2. Attach the trilink with the terminator to the controller that you wantto be on the end of the shared SCSI bus. Attach an H8861-AA VHDCItrilink conn

Figure 3–5 shows a two-member TruCluster Server configuration with aradially connected dual-redundant HSZ70 RAID array controller configuredfor transp

Table 3–4: Hardware Components Used in Configuration Shown in Figure3–5 Through Figure 3–8Callout NumberDescription1BN38C cablea2BN37A cableb3H8861-AA

3.7.1.2 Preparing a Dual-Redundant HSZ70 or HSZ80 for a Shared SCSI Bus UsingMultiple-Bus FailoverMultiple-bus failover is a dual-redundant controller

2. Install H8861-AA VHDCI trilink connectors (with terminators) on:• HSZ70 controller A and controller B• HSZ80 controller A Port 1 (2) and controller

8.2.2Cabling the DS-TZ89N-VW Tape Drives ... 8–88.2.3Setting the DS-TZ89N-TA SCSI ID ... 8–98.2.4Cabling the

Figure 3–7 shows a two-member TruCluster Server configuration witha radially connected dual-redundant HSZ70 configured for multiple-busfailover.Figure

Figure 3–8 shows a two-member TruCluster Server configuration witha radially connected dual-redundant HSZ80 configured for multiple-busfailover.Figure

4TruCluster Server System ConfigurationUsing UltraSCSI HardwareThis chapter describes how to prepare systems for a TruCluster Servercluster, using Ult

This is especially critical if you will install tape devices on the sharedSCSI bus. With the exception of the TZ885, TZ887, TL890, TL891, andTL892, ta

• Number of shared SCSI buses and the storage on each shared busUsing shared SCSI buses increases storage availability. You can connect32 shared SCSI

Table 4–1: Planning Your Configuration (cont.)To increase: You can:Disk availability Mirror disks across shared buses.Use a RAID array controller.Shar

6. Copy the appropriate release notes to your system disk. In thisexample, obtain the firmware release notes for the AlphaServerDS20 from the Version

______________________ Note _______________________The KZPSA-BB can be used in any configuration in place of theKZPBA-CB. The use of the KZPSA-BB is n

Table 4–2: Configuring TruCluster Server Hardware (cont.)StepAction Refer to:4Update the system SRM consolefirmware from the latest Alpha SystemsFirmw

8.10.5Connecting the TL895 Tape Library to the Shared SCSIBus ...8–488.11Preparing the T

The DWZZH contains a differential to single-ended signal converter for eachhub port (sometimes referred to as a DWZZA on a chip, or DOC chip). Thesing

Your storage shelves or RAID array subsystems should be set up beforecompleting this portion of an installation.Use the steps in Table 4–3 to set up a

Table 4–3: Installing the KZPBA-CB for Radial Connection to a DWZZHUltraSCSI Hub (cont.)StepAction Refer to:_____________________ Notes ______________

Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.)Core LogicCchip DECchip 21272-CA Rev 2.1Dchip DECchip 21272-DA Rev 2.0Pchip 0 DECc

Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.)Bus 02 Slot 02: DE500-AA Network Controllerewa0.0.0.2002.0 00-06-2B-00-0A-48PCI Ho

Example 4–3 shows the output from the show config console commandentered on an AlphaServer 8200 system.Example 4–3: Displaying Configuration on an Alp

Example 4–4: Displaying Devices on an AlphaServer 8200 (cont.)dkf4.0.0.1.1 DKF4 HSZ70 V70Zdkf5.0.0.1.1 DKF5 HSZ70 V70Zdkf6.0.0.1.1 DKF6 HSZ70 V70Zdkf1

4.3.3.1 Displaying KZPBA-CB pk* or isp* Console Environment VariablesTo determine the console environment variables to use, execute the showpk* and sh

• on — Turns on both low 8 bits and high 8 bits• diff — Places the bus in differential modeThe KZPBA-CB is a Qlogic ISP1040 module, and its terminatio

4.3.3.2 Setting the KZPBA-CB SCSI IDAfter you determine the console environment variables for the KZPBA-CBson the shared SCSI bus, use the set console