Page 3 - Contents; About This Manual; Contents iii
Contents About This Manual 1 Introduction 1.1 The TruCluster Server Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 1.2 Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 1.3 Minimum Disk Require...
Page 4 - iv Contents
2.6 SCSI Signal Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10 2.7 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs . . . . . . . . . . . 2–11 2.8 SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 5 - Setting Up the Memory Channel Cluster Interconnect; Installing the MC2 Optical Converter in the Member System; Using Fibre Channel Storage; Contents v
4.3.1 Installation of a KZPBA-CB Using Internal Terminationfor a Radial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7 4.3.2 Displaying KZPBA-CB Adapters with the show ConsoleCommands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 6 - vi Contents
6.2.2.2 Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7 6.2.2.3 Arbitrated Loop Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8 6.3 Example Fibre Channel Configurations Supported byTruCluste...
Page 7 - Contents vii
6.6.2 Install the Tru64 UNIX Operating System . . . . . . . . . . . . . . . . . . 6–51 6.6.3 Determining /dev/disk/dskn to Use for a ClusterInstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–51 6.6.4 Label the Disks to Be Us...
Page 8 - viii Contents
8.2.2 Cabling the DS-TZ89N-VW Tape Drives . . . . . . . . . . . . . . . . . . . . . 8–8 8.2.3 Setting the DS-TZ89N-TA SCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9 8.2.4 Cabling the DS-TZ89N-TA Tape Drives . . . . . . . . . . . . . . . . . . . . . . 8–9 8.3 Compaq 20/40 GB DLT Ta...
Page 9 - Contents ix
8.10.5 Connecting the TL895 Tape Library to the Shared SCSIBus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48 8.11 Preparing the TL893 and TL896 Automated Tape Librariesfor Shared SCSI Bus Usage . . . . . . . . ....
Page 10 - to Non-UltraSCSI Devices; DWZZA and DWZZB Signal Converter Termination . .; x Contents
8.13.3.1 ESL9326D Enterprise Library Robotic and Tape DriveRequired Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–75 8.13.3.2 Library Electronics and Tape Drive SCSI IDs . . . . . . . . . . 8–75 8.13.3.3 ESL9326D Enterprise Library Internal Cabling . . ...
Page 11 - Contents xi
9.4.3.2 Cabling an HSZ20 in a Cluster Using ExternalTermination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–28 9.4.4 Cabling an HSZ40 or HSZ50 RAID Array Controller in aRadial Configuration with an UltraSCSI Hub . . . . . . . . . . . . . . 9–...
Page 12 - Figures; xii Contents
5–1 Running the mc_cable Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13 6–1 Determine HSG80 Connection Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–31 6–2 Setting Up the Mirrorset . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 13 - Contents xiii
1–8 NSPOF Fibre Channel Cluster Using HSG80s in Multiple-BusFailover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16 2–1 PCI Backplane Slot Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 14 - xiv Contents
8–1 TZ88N-VA SCSI ID Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2 8–2 Shared SCSI Buses with SBB Tape Drives . . . . . . . . . . . . . . . . . . . . . . . 8–4 8–3 DS-TZ89N-VW SCSI ID Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 15 - Tables; Contents xv
9–15 TruCluster Server Cluster Using KZPSA-BB SCSI Adapters,a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID ArrayController . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–31 10–1 KZPSA-BB Termination Resistors . . . . . . ...
Page 16 - xvi Contents
8–9 TL894 Default SCSI ID Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–37 8–10 Hardware Components Used to Create the ConfigurationShown in Figure 8–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42 8–11 TL895 ...
Page 17 - Audience; Describes hardware requirements and restrictions.
About This Manual This manual describes how to set up and maintain the hardwareconfiguration for a TruCluster™ Server cluster. Audience This manual is for system administrators who will set up and configure thehardware before installing the TruCluster Server software. The manualassumes that you are ...
Page 18 - Related Documents; Installation Guide; xviii About This Manual
Chapter 7 Describes the use of AlphaServer™ GS80, GS160, or GS320 hardwarepartitions in a TruCluster Server configuration. Chapter 8 Describes how to configure a shared SCSI bus for tape drive,tape loader, or tape library usage. Chapter 9 Describes the requirements for a shared SCSI bus using extern...
Page 19 - About This Manual xix
The StorageWorks™ UltraSCSI Configuration Guidelines documentprovides guidelines regarding UltraSCSI configurations. For information about setting up a RAID subsystem, see the followingmanuls as appropriate for your configuration: • DEC RAID Subsystem User ’s Guide • HS Family of Array Controllers U...
Page 20 - For information about the tape devices, see the following manuals:; xx About This Manual
• Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide • Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide • Compaq StorageWorks Fibre Channel SAN Switch 8-EL Installationand Hardware Guide • Compaq StorageWorks Fibre Channel SAN Switch Management Guide • Compaq StorageWo...
Page 21 - About This Manual xxi
• For more information on the ESL9326D Enterprise Library, seethe following Compaq StorageWorks ESL9000 Series Tape Librarydocumentation: – Unpacking and Installation Guide – Reference Guide – Maintenance and Service Guide – Tape Drive Upgrade Guide The Golden Eggs Visual Configuration Guide provide...
Page 22 - Reader’s Comments; You can send your comments in the following ways:; Conventions; The following typographical conventions are used in this manual:; cat; xxii About This Manual
Reader’s Comments Compaq welcomes any comments and suggestions you have on this andother Tru64 UNIX manuals. You can send your comments in the following ways: • Fax: 603-884-0120 Attn: UBPG Publications, ZKO3-3/Y32 • Internet electronic mail: [email protected] A Reader ’s Comment form is l...
Page 23 - cluster; About This Manual xxiii
file Italic (slanted) type indicates variable values,placeholders, and function argument names. .. . A vertical ellipsis indicates that a portion of anexample that would normally be present is notshown. cat (1) A cross-reference to a reference page includesthe appropriate section number in parenthes...
Page 25 - Introduction; The TruCluster Server Product; Introduction 1–1
1 Introduction This chapter introduces the TruCluster Server product and some basiccluster hardware configuration concepts. Subsequent chapters describe how to set up and maintain TruCluster Serverhardware configurations. See the TruCluster Server Software Installationmanual for information about so...
Page 26 - Memory Requirements; Cluster members require a minimum of 128 MB of memory.; Minimum Disk Requirements; You need to allocate disks for the following uses:; –2 Introduction
interconnect, you can more easily alter or expand your cluster ’s hardwareconfiguration as newer and faster technologies become available. 1.2 Memory Requirements Cluster members require a minimum of 128 MB of memory. 1.3 Minimum Disk Requirements This section provides an overview of the minimum fil...
Page 27 - root; first; Introduction 1–3
Because the Tru64 UNIX operating system will be available on the firstcluster member, in an emergency, after shutting down the cluster, you havethe option of booting the Tru64 UNIX operating system and attempting tofix the problem. See the TruCluster Server Cluster Administration manualfor more info...
Page 28 - –4 Introduction
partitions. You can move the swap partition off the member boot disk. Seethe TruCluster Server Cluster Administration manual for more information. 1.3.1.4 Quorum Disk The quorum disk allows greater availability for clusters consisting of twomembers. Its h partition contains cluster status and quorum...
Page 29 - Network; Introduction 1–5
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 disk • Member 2 boot disk A minimum configuration cluster may have reduced availability due to thelack of a quorum disk. As shown, with only two-me...
Page 30 - Growing a Cluster from Minimum Storage to a NSPOF; Adding a second SCSI bus allows the use of LSM to mirror the; –6 Introduction
Administration manual for a discussion of how and when to use a quorumdisk. Figure 1–2: Generic Two-Node Cluster with Minimum Disk Configurationand Quorum Disk Member System 1 Network Memory Channel Shared SCSI Bus PCI SCSI Adapter Member System 2 PCI SCSI Adapter Cluster File System root (/) /usr /...
Page 31 - Note; Two-Node Clusters Using an UltraSCSI BA356 Storage Shelf; Introduction 1–7
• Using a RAID array controller in transparent failover mode allows theuse of hardware RAID to mirror the disks. However, without a secondSCSI bus, second Memory Channel, and redundant networks, thisconfiguration is still not a NSPOF cluster (Section 1.5.4). • By using an HSZ70, HSZ80, or HSG80 with...
Page 32 - –8 Introduction
Figure 1–3: Minimum Two-Node Cluster with UltraSCSI BA356 Storage Unit ID 5 PWR SharedSCSIBus Clusterwide/, /usr, /var Member 1Boot Disk Member 2Boot Disk Quorum Disk UltraSCSI BA356 ID 4 Host Bus Adapter (ID 7) MemoryChannelInterface Memory Channel Host Bus Adapter (ID 6) Memory Channel MemberSyste...
Page 33 - Two-Node Clusters Using UltraSCSI BA356 Storage Units with; Introduction 1–9
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 TruCluster Server ClusterAdministration manual for a discussion of the cluster file system), theclusterwide root ( / ), /usr , and /var file systems ...
Page 34 - and
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 on the same bus. Figure 1–4 shows the configuration in Figure 1–3 with a second UltraSCSIBA356 storage unit that provides an additional seven disks f...
Page 35 - You cannot use LSM to mirror the clusterwide root (
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 Configurations with UltraSCSI BA356 Storage Units and Dual SCSI Buses By adding a second shared SCSI bus, you now have the capability to use theLogical S...
Page 36 - By using LSM to mirror the; Using Hardware RAID to Mirror the Clusterwide Root File
Figure 1–5: Two-Node Configurations with UltraSCSI BA356 Storage Unitsand Dual SCSI Buses Host Bus Adapter (ID 7) Network MemoryChannelInterface Memory Channel Memory Channel MemberSystem 2 MemberSystem 1 Tru64 UNIX Disk Host Bus Adapter (ID 6) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) ID 8 ID...
Page 37 - StorageWorks
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 toanother controller, you must install the second controller. Also, you mustset the failover mode. Figure 1–6: Cluster Configuration with HSZ70 Controlle...
Page 38 - Notes; SET MULTIBUS_FAILOVER
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 single shared SCSI bus is a single point of failure. 1.5.5 Creating a NSPOF Cluster To create a no-single-point-of-failure (NSPOF) cluster: • Use har...
Page 39 - Member System 1
Figure 1–7: NSPOF Cluster Using HSZ70s in Multiple-Bus Failover Mode Networks Host Bus Adapter (ID 7) Member System 1 Member System 2 Tru64 UNIX Disk Host Bus Adapter (ID 6) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) HSZ70 StorageWorks RAID Array 7000 HSZ70 ZK-1594U-AI MemoryChannelInterfaces M...
Page 40 - Fibre Channel Switch; Overview of Setting Up the TruCluster Server Hardware; Draw a diagram of your configuration.
Figure 1–8: NSPOF Fibre Channel Cluster Using HSG80s in Multiple-BusFailover Mode KGPSA Member System 2 KGPSA KGPSA Member System 1 KGPSA Memory Channel Memory Channel Memory Channel Interface ZK-1765U-AI Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B RA8000/ESA120...
Page 43 - Hardware Requirements and Restrictions; TruCluster Server Member System Requirements; Select; Hardware Requirements and Restrictions 2–1
2 Hardware Requirements and Restrictions This chapter describes the hardware requirements and restrictions fora TruCluster Server cluster. It includes lists of supported cables, trilinkconnectors, Y cables, and terminators. For the latest information about supported hardware see theAlphaServer optio...
Page 44 - Hot swapping modules is not supported.; –2 Hardware Requirements and Restrictions
arbitration enabled when connecting four-member systems to acommon SCSI bus. • The following items pertain to the AlphaServer GS80/160/320 systems: – Hot swapping modules is not supported. – High power peripheral component interconnect (PCI) modules(approximately 25 watts or greater) must be placed ...
Page 45 - Memory Channel Restrictions; The MC1 adapter cannot be cabled to a MC2 adapter.; Hardware Requirements and Restrictions 2–3
2.2 Memory Channel Restrictions The Memory Channel interconnect is used for cluster communicationsbetween the member systems. There are currently three versions of the Memory Channel product; MemoryChannel 1, Memory Channel 1.5, and Memory Channel 2. The MemoryChannel 1 and Memory Channel 1.5 produc...
Page 46 - examine; –4 Hardware Requirements and Restrictions
• In an MC2 configuration, you can use a CCMFB optical converter inconjunction with the MC2 CCMAB module to increase the distancebetween systems. • The BN34R fiber optics cable, used to connect two CCMFB opticalconverters, is available in 10-meter (BN34R-10) and 31-meter(BN34R-31) lengths. • Always ...
Page 47 - Host Bus Adapter Restrictions; Fibre Channel Requirements and Restrictions; Hardware Requirements and Restrictions 2–5
each Memory Channel adapter on one system must be connected to thesame linecard in each Memory Channel hub. 2.3 Host Bus Adapter Restrictions To connect a member system to a shared SCSI bus, you must install a hostbus adapter in an I/O bus slot. The Tru64 UNIX operating system supports a maximum of ...
Page 48 - –6 Hardware Requirements and Restrictions
____________________ Notes ____________________ The Model 4124R disk enclosure is a single-bus enclosure thathas slots for 14 drives, but only 12 drives are supported atthe present time. The maximum number of drives behind an HSG60 (singleor dual-redundant pair) using two single-bus Model 4214Rdisk ...
Page 49 - Hardware Requirements and Restrictions 2–7
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 Model 4254 disk enclosures supportonly the new Compaq hot-pluggable wide-UltraSCSI lowvoltage differential (LVD) disk drives. For more information on ...
Page 50 - –8 Hardware Requirements and Restrictions
• A maximum of three cascaded switches is supported, with a maximum oftwo hops between switches. The maximum hop length is 10 km longwavesingle-mode or 500 meters via shortwave multimode Fibre Channel cable. • Tru64 UNIX Version 5.1 limits the number of Fibre Channel targetsto 126. • Tru64 UNIX Vers...
Page 51 - Disk Device Restrictions; Hardware Requirements and Restrictions 2–9
AlphaServer 800, 1000, 1000A, 2000, 2100, or 2100A systems supportthe 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 suppo...
Page 52 - Table 2–2: RAID Controller SCSI IDs; RAID Controller; SCSI Signal Converters; –10 Hardware Requirements and Restrictions
RAID array controllers require the minimum Array Controller Software(ACS) shown in Table 2–1. Table 2–1: RAID Controller Minimum Required Array Controller Software RAID Controller Minimum Required Array ControllerSoftware HSZ20 3.4 HSZ40 3.7 HSZ50 5.7 HSZ70 7.7 HSZ80 8.3-1 HSG60 8.5 HSG80 8.5 RAID c...
Page 53 - The restrictions for SCSI signal converters are as follows:; Hardware Requirements and Restrictions 2–11
______________________ Note _______________________ We could list the UltraSCSI hubs because they contain a DOC(DWZZA on a chip) chip, but they are discussed separately inSection 2.7. The restrictions for SCSI signal converters are as follows: • If you remove the cover from a standalone unit, be sur...
Page 54 - Improves the reliability of the detection of cable faults.; –12 Hardware Requirements and Restrictions
• The lower righthand device slot of the BA370 shelf within the RA7000or ESA 10000 RAID array subsystems. This position minimizes cablelengths and interference with disks. • A wide BA356 which has been upgraded to the 180-watt power supplywith the DS-BA35X-HH option. A DS-DWZZH-03 or DS-DWZZH-05 Ult...
Page 55 - Table 2–3: Supported SCSI Cables; Cable; Three high; Hardware Requirements and Restrictions 2–13
Table 2–3: Supported SCSI Cables Cable ConnectorDensity Pins Configuration Use BN21W-0B Three high 68-pin A Y cable that can be attached to aKZPSA-BB or KZPBA-CB if thereis no room for a trilink connector.It can be used with a terminator toprovide external termination. BN21M One low, onehigh 50-pinL...
Page 56 - SCSI Terminators and Trilink Connectors; Table 2–4: Supported SCSI Terminators and Trilink Connectors; Pins; The requirements for trilink connectors are as follows:; –14 Hardware Requirements and Restrictions
2.9 SCSI Terminators and Trilink Connectors Table 2–4 describes the supported trilink connectors and SCSI terminatorsand the context in which you would use them. Table 2–4: Supported SCSI Terminators and Trilink Connectors TrilinkConnector orTerminator Den-sity Pins Configuration Use H885-AA Three 6...
Page 57 - Introduces SCSI bus configuration concepts; termpwr
3 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware A TruCluster Server cluster uses shared SCSI buses, external storageshelves or RAID controllers, and supports disk mirroring and fast file systemrecovery to provide high data availability and reliability. This chapter: • Intr...
Page 58 - This chapter discusses the following topics:; Shared SCSI Bus Configuration Requirements; A shared SCSI bus must adhere to the following requirements:
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.5) • UltraSCSI hubs (Section 3.6) • Co...
Page 59 - SCSI Bus Performance
storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storagearrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves aresupported with UltraSCSI host adapters and host RAID controllers aslong as they contain no UltraSCSI disks. • UltraSCSI drives and fast wide drives can be mixed together in ...
Page 60 - Two transmission methods can be used in a SCSI bus:
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 UltraSCSI bus segments may be coupled together with UltraSCSIhubs or signal converters, increasing the total length of the UltraSCSI bus. 3.2.2 Transmis...
Page 61 - There are two data paths for SCSI devices:; Table 3–1: SCSI Bus Speeds; SCSI Bus; SCSI; SCSI Bus Device Identification Numbers
You cannot use a DWZZA or DWZZB signal converter at UltraSCSI speedsfor TruCluster Server if there are any UltraSCSI disks on the bus, becausethe DWZZA or DWZZB will not operate correctly at UltraSCSI speed.The DS-BA35X-DA personality module contains a signal converter forthe UltraSCSI BA356. It is ...
Page 62 - meters
______________________ Note _______________________ If you are using a DS-DWZZH-05 UltraSCSI hub with fairarbitration enabled, SCSI ID numbering will change (seeSection 3.6.1.2). Use the following priority order to assign SCSI IDs to the SCSI bus adaptersconnected to a shared SCSI bus: 7-6-5-4-3-2-1...
Page 63 - There are two rules for SCSI bus termination:
Because of the cable length limit, you must plan your hardware configurationcarefully, and ensure that each SCSI bus meets the cable limit guidelines.In general, you must place systems and storage shelves as close together aspossible and choose the shortest possible cables for the shared bus. 3.5 Te...
Page 64 - Using a DWZZH UltraSCSI Hub in a Cluster Configuration
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) CXO5744A 3.6 UltraSCSI Hubs The DS-DWZZH series UltraSCSI hubs are UltraSCSI signal convertersthat provide radial connections of differential SCSI bus adap...
Page 67 - Disk Drives
• The lower righthand device slot of the BA370 shelf within the RA7000or ESA 10000 RAID array subsystems. This position minimizes cablelengths and interference with disks. A DS-DWZZH-05 UltraSCSI hub uses the storage shelf only to provide itspower and mechanical support (it is not connected to the s...
Page 69 - Caution
3.6.1.2.3 DS-DWZZH-05 Address Configurations The DS-DWZZH-05 has two addressing modes: wide addressing mode andnarrow addressing mode. With either addressing mode, if fair arbitration isenabled, each hub port is assigned a specific SCSI ID. This allows the fairarbitration logic in the hub to identif...
Page 72 - Fair; Preparing the UltraSCSI Storage Configuration
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-DWZZH-05 UltraSCSI hub in a UltraSCSI BA356,non-UltraSCSI BA356 (if it has the required 180-watt power supply), orBA370 storage shelf. 3.7 Preparing th...
Page 73 - ) to help achieve a NSPOF configuration if each host has
3.7.1 Configuring Radially Connected TruCluster Server Clusters with UltraSCSI Hardware Radial configurations with RAID array controllers allow you to takeadvantage of the benefits of hardware mirroring, and to achieve ano-single-point-of-failure (NSPOF) cluster. Typical RAID array storagesubsystems...
Page 74 - When using transparent failover mode:
or SCSI bus failure, the host can redistribute the load to the survivingcontroller. In case of a controller failure, the surviving controller will handleall units. ______________________ Notes ______________________ Multiple-bus failover does not support device partitioning withthe HSZ70 or HSZ80. P...
Page 77 - H8861-AA VHDCI trilink connector
Table 3–4: Hardware Components Used in Configuration Shown in Figure3–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 e...
Page 79 - HSZ70 controller A and controller B; You must use the same port on each HSZ80 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 B Port 1 (2) ___________________ Note ___________________ You must use the same port on each HSZ80 controller. 3. Install the DS-DWZZH-03 or DS-DWZ...
Page 81 - Member System 2
Figure 3–8 shows a two-member TruCluster Server configuration witha radially connected dual-redundant HSZ80 configured for multiple-busfailover. Figure 3–8: TruCluster Server Configuration with HSZ80 in Multiple-BusFailover Mode KZPBA-CB (ID 7) Networks MemoryChannelInterfaces KZPBA-CB (ID 6) Memory...
Page 83 - If you are using Fibre Channel storage, see Chapter 6.
4 TruCluster Server System Configuration Using UltraSCSI Hardware This chapter describes how to prepare systems for a TruCluster Servercluster, using UltraSCSI hardware and the preferred method of radialconfiguration, including how to connect devices to a shared SCSI bus forthe TruCluster Server pro...
Page 84 - Cluster interconnects
This is especially critical if you will install tape devices on the sharedSCSI bus. With the exception of the TZ885, TZ887, TL890, TL891, andTL892, tape devices can only be installed at the end of a shared SCSIbus. These tape devices are the only supported tape devices that canbe terminated external...
Page 85 - Table 4–1: Planning Your Configuration
• Number of shared SCSI buses and the storage on each shared bus Using shared SCSI buses increases storage availability. You can connect32 shared SCSI buses to a cluster member. You can use any combinationof KZPSA-BB, KZPBA-CB, or KGPSA-BC/CA host bus adapters. In addition, RAID array controllers al...
Page 86 - Obtaining the Firmware Release Notes; All Products
Table 4–1: Planning Your Configuration (cont.) To increase: You 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. 4.2 Obtaining the Firmware Release Notes...
Page 87 - Print the release notes.; TruCluster Server Hardware Installation
6. Copy the appropriate release notes to your system disk. In thisexample, obtain the firmware release notes for the AlphaServerDS20 from the Version 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. Print the release...
Page 88 - Step Action; Chapter 5
______________________ Note _______________________ The KZPSA-BB can be used in any configuration in place of theKZPBA-CB. The use of the KZPSA-BB is not mentioned in thischapter because it is not UltraSCSI hardware, and it cannotoperate at UltraSCSI speeds. The use of the KZPSA-BB (and the KZPBA-CB...
Page 89 - Installation of a KZPBA-CB Using Internal Termination for a; A DWZZH UltraSCSI hub can be installed in:
Table 4–2: Configuring TruCluster Server Hardware (cont.) Step Action Refer to: 4 Update the system SRM consolefirmware from the latest Alpha SystemsFirmware Update CD-ROM. Use the firmware update releasenotes (Section 4.2) ______________________ Note _____________________ The SRM console firmware i...
Page 92 - HSZ70 or HSZ80 in transparent failover mode; Commands; Example 4–1: Displaying Configuration on an AlphaServer DS20
Table 4–3: Installing the KZPBA-CB for Radial Connection to a DWZZHUltraSCSI Hub (cont.) Step Action Refer to: _____________________ Notes _____________________ Ensure that the SCSI ID that you use is distinct from all other SCSI IDson the same shared SCSI bus. If you do not remember the other SCSII...
Page 94 - Example 4–2: Displaying Devices on an AlphaServer DS20
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.0.0.7.1 08-00-2B-B9-0D-5D Bus 00 Slot 08: DEC PCI MC Rev: 22, mca0 Bus 00 Slot 09: DEC PCI MC Rev: 22, mcb0...
Page 95 - Example 4–3: Displaying Configuration on an AlphaServer 8200; Example 4–4: Displaying Devices on an AlphaServer 8200
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 Name Type Rev Mnemonic TLSB 4++ KN7CC-AB 8014 0000 kn7cc-ab0 5+ MS7CC 5000 0000 ms7cc0 8+ KFTIA 2020 0000 kft...
Page 96 - Displaying Console Environment Variables and Setting the; show
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......
Page 99 - Use the; Example 4–7: Setting the KZPBA-CB SCSI Bus ID
4.3.3.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBson the shared SCSI bus, use the set console command to set the SCSI ID. For a TruCluster Server cluster, you will most likely have to set theSCSI ID for all KZPBA-CB UltraSCSI adapters except ...
Page 100 - Figure 4–1: KZPBA-CB Termination Resistors
Figure 4–1: KZPBA-CB Termination Resistors Internal Wide DeviceConnector J2 Internal Narrow DeviceConnector P2 SCSI Bus TerminationResistors RM1-RM8 ZK-1451U-AI JA1 4–18 TruCluster Server System Configuration Using UltraSCSI Hardware
Page 101 - See Section 2.2 for a discussion on Memory Channel restrictions.; Setting Up the Memory Channel Cluster Interconnect 5–1
5 Setting Up the Memory Channel Cluster Interconnect This chapter describes Memory Channel configuration restrictions, anddescribes how to set up the Memory Channel cluster interconnect, includingsetting up a Memory Channel hub, Memory Channel optical converter (MC2only), and connecting link cables....
Page 102 - Setting the Memory Channel Adapter Jumpers; Table 5–1: MC1 and MC1.5 Jumper Configuration; Standard; –2 Setting Up the Memory Channel Cluster Interconnect
____________________ Note _____________________ If you are installing SCSI or network adapters, you maywant to complete all hardware installation before poweringup the systems to run Memory Channel diagnostics. Section 5.7 provides procedures for upgrading from redundant MC1interconnects to MC2 inte...
Page 103 - None needed store the jumper on pin 1 or 3; Most of the jumper settings are straightforward, but the; Setting Up the Memory Channel Cluster Interconnect 5–3
Table 5–1: MC1 and MC1.5 Jumper Configuration (cont.) If hub mode is: Jumper: Example: Virtual: VH0 Pins 2 to 3 1 2 3 Virtual: VH1 None needed; store the jumper on pin 1 or 3 1 2 3 If you are upgrading from virtual hub mode to standard hub mode (or fromstandard hub mode to virtual hub mode), be sure...
Page 104 - The MC2 jumpers are described in Table 5–2.; Table 5–2: MC2 Jumper Configuration; Standard: Pins 1 to 2; –4 Setting Up the Memory Channel Cluster Interconnect
See the TruCluster Server Cluster Administration manual for moreinformation on failover pairs. The MC2 jumpers are described in Table 5–2. Table 5–2: MC2 Jumper Configuration Jumper: Description: Example: J1: Hub Mode Standard: Pins 1 to 2 1 2 3 VH0: Pins 2 to 3 1 2 3 VH1: None needed;store the jump...
Page 105 - Fiber Off: Pins 1 to 2; Table 5–3: MC2 Linecard Jumper Configurations; Fiber Off: Pins 2 to 3; Setting Up the Memory Channel Cluster Interconnect 5–5
Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: J5: AlphaServer8x00 Mode 8x00 mode selected:Pins 1 to 2 a 1 2 3 8x00 mode not selected:Pins 2 to 3 1 2 3 J10 and J11: FiberOptics Mode Enable Fiber Off: Pins 1 to 2 3 2 1 Fiber On: Pins 2 to3 pins 3 2 1 a Increases the maximum...
Page 106 - Remove the bulkhead blanking plate for the desired PCI slot.; –6 Setting Up the Memory Channel Cluster Interconnect
5.2 Installing the Memory Channel Adapter Install the Memory Channel adapter in an appropriate peripheral componentinterconnect (PCI) slot (see Section 2.2). Secure the module at the backplane.Ensure that the screw is tight to maintain proper grounding. The Memory Channel adapter comes with a straig...
Page 107 - Installing the Memory Channel Hub; CCMLA linecards for the CCMHA MC1 hub; Installing the Memory Channel Cables; Setting Up the Memory Channel Cluster Interconnect 5–7
5.4 Installing the Memory Channel Hub You may use a hub in a two-node TruCluster Server cluster, but the hub isnot required. When there are more than two systems in a cluster, you mustuse a Memory Channel hub as follows: • For use with the MC1 or MC1.5 CCMAA adapter, you must install thehub within 3...
Page 108 - Do not connect an MC1 or MC1.5 link cable to an MC2 module.; in one; –8 Setting Up the Memory Channel Cluster Interconnect
______________________ 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 Virtual Hub Mode For an MC1 virtual hub configuration (two nodes in the cluster), connect theBC12N-10 link cables between the Memory Channel ...
Page 109 - Figure 5–1: Connecting Memory Channel Adapters to Hubs; Linecards; Setting Up the Memory Channel Cluster Interconnect 5–9
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 Memory Channel Adapters to Hubs Memory Channel hub 1 Memory Channel hub 2 System A MemoryChanneladapters Linecards ZK-1197U-AI 5.5.2 Installing the MC2...
Page 110 - You cannot install a CCMLB linecard in slot; –10 Setting Up the Memory Channel Cluster Interconnect
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 good ground contact. If you are setting up redundant interconnects, all Memory Channel adaptersin a system must have the same jumper setting, either VH...
Page 111 - Set the CCMLB linecard jumpers to support fiber optics; Fiber On; Running Memory Channel Diagnostics; Setting Up the Memory Channel Cluster Interconnect 5–11
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 module for each fiber optics link ______________________ Note _______________________ Remember, if you have m...
Page 112 - –12 Setting Up the Memory Channel Cluster Interconnect
There are two console level Memory Channel diagnostics, mc_diag and mc_cable : • The mc_diag diagnostic: – Tests the Memory Channel adapter(s) on the system running thediagnostic. – Runs as part of the initialization sequence when the system ispowered up. – Runs on a standalone system or while conne...
Page 113 - Setting Up the Memory Channel Cluster Interconnect 5–13
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 response from node 0 on mcb0 3 Response from node 0 on mca0 4 Response from node 0 on mcb0 5 mcb0 is offline...
Page 114 - Upgrading Memory Channel Adapters; –14 Setting Up the Memory Channel Cluster Interconnect
5.7 Upgrading Memory Channel Adapters If you have a TruCluster Server configuration with redundant MC1interconnects and want to upgrade to MC2 interconnects, you can do sowithout shutting down the entire cluster. When rolling from MC1 interconnects, which use 128 MB Memory Channeladdress space, to M...
Page 115 - set; Setting Up the Memory Channel Cluster Interconnect 5–15
Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 Interconnects Step Action Refer to: 1 If desired, manually relocate all applications from thecluster member that will be shut down using the clusterapplication availability (CAA) caa_relocate com...
Page 116 - J4 — Page size: Jumper pins 1 to 3 to select 8 KB; –16 Setting Up the Memory Channel Cluster Interconnect
Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual,Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: ______________________ Note ______________________ If you set the J3 jumpers for 128 MB because the other interconnectis MC1, and then later on decide ...
Page 117 - sysconfig; Setting Up the Memory Channel Cluster Interconnect 5–17
Table 5–4: Adding a Memory Channel Interconnect 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 inone system, and on one rail at a time. Use a BN39B-10link cable to con...
Page 118 - On one member system, use the; If you use the; If you have used the; –18 Setting Up the Memory Channel Cluster Interconnect
Table 5–4: Adding a Memory Channel Interconnect 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 toinitiate the use of 512 MB address space. The conf...
Page 119 - Check the size of a logical rail.; Setting Up the Memory Channel Cluster Interconnect 5–19
(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 Verify the jumper settings for the member systems on the. first physicalrai...
Page 120 - Figure 5–2: MC1 to MC2 Virtual Hub Rolling Upgrade; –20 Setting Up the Memory Channel Cluster Interconnect
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 Upgrade AlphaServer Member System 1 MC1 MC1 AlphaServer Member System 2 MC1 MC1 AlphaServer Member System 1 MC2 MC1 AlphaServer Member System 2 MC1 MC1 Alp...
Page 121 - Setting Up the Memory Channel Cluster Interconnect 5–21
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 Upgrade: InitialConfiguration AlphaServer Member System 1 MC1 MC1 AlphaServer Member System 2 MC1 MC1 MC1 Hub # 1 ZK-1522U-AI MC1 Hub # 2 AlphaServer ...
Page 122 - –22 Setting Up the Memory Channel Cluster Interconnect
Figure 5–4: MC1 to MC2 Standard Hub Rolling Upgrade: First MC1 ModuleReplaced AlphaServer Member System 1 MC2 MC1 AlphaServer Member System 2 MC1 MC1 MC1 Hub # 1 MC1 Hub # 2 AlphaServer Member System 3 MC1 MC1 MC2 Hub # 1 0/opto ZK-1523U-AI 5–22 Setting Up the Memory Channel Cluster Interconnect
Page 123 - Setting Up the Memory Channel Cluster Interconnect 5–23
Figure 5–5: MC1 to MC2 Standard Hub Rolling Upgrade: Replace First MC1Adapter in Second System AlphaServer Member System 1 MC2 MC1 AlphaServer Member System 2 MC2 MC1 MC2 Hub # 1 MC1 Hub # 2 AlphaServer Member System 3 MC1 MC1 0/opto opto only ZK-1524U-AI Setting Up the Memory Channel Cluster Interc...
Page 124 - –24 Setting Up the Memory Channel Cluster Interconnect
Figure 5–6: MC1 to MC2 Standard Hub Rolling Upgrade: Replace ThirdSystem Memory Channel Adapters AlphaServer Member System 1 MC2 MC1 AlphaServer Member System 2 MC2 MC1 MC2 Hub # 1 MC1 Hub # 2 AlphaServer Member System 3 MC2 MC2 MC2 Hub # 2 opto only 0/opto 1/opto 1/opto ZK-1525U-AI 5–24 Setting Up ...
Page 125 - Setting Up the Memory Channel Cluster Interconnect 5–25
Figure 5–7: MC1 to MC2 Standard Hub Rolling Upgrade: Replace SecondMC1 in Second System AlphaServer Member System 1 MC2 MC1 AlphaServer Member System 2 MC2 MC2 MC2 Hub # 1 MC2 Hub # 2 AlphaServer Member System 3 MC2 MC2 opto only opto only 1/opto 1/opto 0/opto ZK-1526U-AI Setting Up the Memory Chann...
Page 126 - –26 Setting Up the Memory Channel Cluster Interconnect
Figure 5–8: MC1 to MC2 Standard Hub Rolling Upgrade: FinalConfiguration AlphaServer Member System 1 MC2 MC2 AlphaServer Member System 2 MC2 MC2 MC2 Hub # 1 MC2 Hub # 2 AlphaServer Member System 3 MC2 MC2 opto only opto only 0/opto 0/opto 1/opto 1/opto ZK-1527U-AI 5–26 Setting Up the Memory Channel C...
Page 127 - value that corresponds to the Fibre; Using Fibre Channel Storage 6–1
6 Using Fibre Channel Storage This chapter provides an overview of Fibre Channel, Fibre Channelconfiguration examples, and information on Fibre Channel hardwareinstallation and configuration in a Tru64 UNIX or TruCluster Server Version5.1 configuration. The information includes an example storageset...
Page 128 - Procedure for Installation Using Fibre Channel Disks; wwidmgr; –2 Using Fibre Channel Storage
• The steps necessary to install and configure the Fibre Channel hardware(Section 6.5). • The steps necessary to install the base operating system and clustersoftware using disks accessible over the Fibre Channel hardware(Section 6.6). • Changing the HSG80 from transparent to multiple-bus failover m...
Page 129 - Using Fibre Channel Storage 6–3
8. See the Tru64 UNIX Installation Guide and install the base operatingsystem from the CD-ROM. The installation procedure will recognize thedisks for which you set the device unit number. Select the disk you havechosen as the Tru64 UNIX operating system installation disk from thelist of disks provid...
Page 130 - Fibre Channel Overview; Support for multiple protocols; –4 Using Fibre Channel Storage
• Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLIReference Guide • MA6000 HSG60 Array Controller ACS Version 8.5 Solution Software forCompaq Tru64 UNIX Installation and Configuration Guide • Compaq StorageWorks HSG60/HSG80 Array Controller ACS Version 8.5Maintenance and Service Guide ...
Page 131 - Using Fibre Channel Storage 6–5
6.2.1 Basic Fibre Channel Terminology The following list describes the basic Fibre Channel terminology: Frame All data is transferred in a packet of informationcalled a frame. A frame is limited to 2112 bytes. Ifthe information consists of more than 2112 bytes, itis divided up into multiple frames. ...
Page 132 - –6 Using Fibre Channel Storage
Link The physical connection between an N_Port andanother N_Port or an N_Port and an F_Port. Alink consists of two connections, one to transmitinformation and one to receive information. Thetransmit connection on one node is the receiveconnection on the node at the other end of the link.A link may b...
Page 133 - Figure 6–2 shows an example fabric topology.; Using Fibre Channel Storage 6–7
Figure 6–1: Point-to-Point Topology N_Port N_Port Transmit Receive Node 1 Node 2 Transmit Receive 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. The fabric examines the destination address in th...
Page 134 - Figure 6–2: Fabric Topology; Figure 6–3 shows an example arbitrated loop topology.; –8 Using Fibre Channel Storage
Figure 6–2: Fabric Topology N_Port Node 1 Node 2 Transmit Receive Transmit Receive Transmit Receive Transmit Receive Transmit Receive Transmit Receive Transmit Receive Transmit Receive F_Port Fabric Node 3 Node 4 F_Port F_Port F_Port N_Port N_Port N_Port ZK-1536U-AI 6.2.2.3 Arbitrated Loop Topology ...
Page 135 - Figure 6–3: Arbitrated Loop Topology; Hub; Example Fibre Channel Configurations Supported by; Using Fibre Channel Storage 6–9
Figure 6–3: Arbitrated Loop Topology NL_Port NL_Port Node 1 Node 2 NL_Port NL_Port Transmit Receive Transmit Receive Transmit Receive Transmit Receive Node 3 Node 4 Hub ZK-1535U-AI ______________________ Note _______________________ The arbitrated loop topology is not supported by the Tru64 UNIXVers...
Page 136 - Mode; With transparent failover mode:; Memory; –10 Using Fibre Channel Storage
6.3.1 Fibre Channel Cluster Configurations for Transparent Failover Mode With transparent failover mode: • The hosts do not know a failover has taken place (failover is transparentto the hosts). • The units are divided between an HSG80 port 1 and port 2. • If there are dual-redundant HSG80 controlle...
Page 137 - SET; Using Fibre Channel Storage 6–11
In transparent failover, units D00 through D99 are accessed through port 1of both controllers. Units D100 through D199 are accessed through port 2 ofboth HSG80 controllers (with the limit of a total of 128 storage units). You cannot achieve a no-single-point-of-failure (NSPOF) configuration usingtra...
Page 138 - –12 Using Fibre Channel Storage
Therefore, you want to ensure that both HSG80 controllersstart at the same time under all circumstances so that thecontroller sees its own preferred units. Figure 6–5, Figure 6–6, and Figure 6–7 show three different multiple-busNSPOF cluster configurations. The only difference is the fiber-optic cab...
Page 139 - Using Fibre Channel Storage 6–13
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 Memory Channel Interface Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B RA8000/ESA12000 Port 1 Port 2 Port 1 Port...
Page 140 - Zoning and Cascaded Switches; –14 Using Fibre Channel Storage
Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 KGPSA Member System 2 KGPSA KGPSA Member System 1 KGPSA Memory Channel Memory Channel Memory Channel Interface ZK-1765U-AI Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B RA8000/ESA12000 Port 1 Port 2 Port 1 Port...
Page 141 - Figure 6–8: A Simple Zoned Configuration; KGPSA; Using Fibre Channel Storage 6–15
Figure 6–8: A Simple Zoned Configuration KGPSA MemoryChannel KGPSA KGPSA KGPSA Fibre Channel Switch Cluster 1MemberSystem 1 Cluster 1MemberSystem 2 Cluster 2MemberSystem 2 Cluster 2MemberSystem 1 0 2 4 6 8 10 12 14 ZK-1709U-AI MemoryChannel MemoryChannel MemoryChannel HSG 80 Controller A HSG 80 Cont...
Page 142 - Installing and Configuring Fibre Channel Hardware; Installing and Setting Up the Fibre Channel Switch; Remotely using a telnet TCP/IP connection; –16 Using Fibre Channel Storage
6.5 Installing and Configuring Fibre Channel Hardware This section provides information about installing the Fibre Channelhardware needed to support Tru64 UNIX or a TruCluster Serverconfiguration using Fibre Channel storage. Ensure that the member systems, the Fibre Channel switches, and theHSG80 ar...
Page 143 - Place the switch or install it in the rack.; Using Fibre Channel Storage 6–17
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 switch has slots to accommodate up to four (DS-DSGGA-AA) oreight (DS-DSGGA-AB) plug-in interface modules. Each interface module inturn supports two Gi...
Page 144 - –18 Using Fibre Channel Storage
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-on self test (POST)tests. The DS-DSGGC-AA has no power switch; power is applied whenthe unit is plugged in. 7. Set the switch IP address and subne...
Page 145 - The four front panel buttons are:; Configuration Menu; Using Fibre Channel Storage 6–19
6.5.1.2.1 Using the Switch Front Panel The switch front panel consists of a display and four buttons. The display isnormally not active, but it lights up when any of the buttons are pressed.The display has a timer. After approximately 30 seconds of inactivity, thedisplay will go out. The four front ...
Page 146 - The underline cursor denotes the selected address field.; –20 Using Fibre Channel Storage
____________________ Note _____________________ Pressing the down button selects the next lower top-levelmenu. The top-level menus are: Configuration MenuOperation Menu Status Menu Test Menu 2. Press Enter to display the first submenu item in the configurationmenu, Ethernet IP address: Ethernet IP a...
Page 147 - Yes; admin; ipAddrSet; Return; logout
10. Use the Tab/Esc button to select Yes . Press Enter to reboot the switch and execute the POST tests. ____________________ Note _____________________ After changing any configuration menu settings, you mustreboot the switch for the change to take effect. Refer to the switch documentation for infor...
Page 148 - DSGGA; Allows you to execute commands ending in; passwd; –22 Using Fibre Channel Storage
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 Logging In to the Switch with a Telnet Connection Before you telnet to a Fibre Channel switch, you must set the Ethernet IPaddress and subnet mask. ______...
Page 149 - User; Passwd; Adapter Module; KGPSA-BC PCI-to-Optical Fibre Channel Host Adapter User Guide; Using Fibre Channel Storage 6–23
______________________ Notes ______________________ Use Ctrl/H to correct typing errors. Use the logout command to log out from any telnet connection. 6.5.1.2.5 Setting the Switch Name via Telnet Session After you set the IP address and subnet mask, you can use a telnet sessionto log in to the switc...
Page 150 - You must set the console to diagnostic mode to use the; –24 Using Fibre Channel Storage
• 64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide _____________________ Caution _____________________ Static electricity can damage modules and electronic components.We recommend using a grounded antistatic wrist strap and agrounded work surface when handling modules. 1. If necessary, instal...
Page 151 - Using Fibre Channel Storage 6–25
AS8x00, GS60, GS60E, and GS140. Set the console to diagnosticmode 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 GS140systems), and you cannot boot u...
Page 152 - Reformatting nvram; –26 Using Fibre Channel Storage
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 warningmessage 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 ada...
Page 153 - show dev; Using Fibre Channel Storage 6–27
This display shows that the current topology for both KGPSA host busadapters is LOOP , but will be FABRIC after the next initialization. A system initialization configures the KGPSAs to run on a fabric. 6.5.2.3 Obtaining the Worldwide Names of KGPSA Adapters A worldwide name is a unique number assig...
Page 154 - Install the fiber-optic cables between the KGPSA and the switch.; Install disks into storage shelves.; –28 Using Fibre Channel Storage
6.5.3 Setting Up the HSG80 Array Controller for Tru64 UNIX Installation This section covers setting up the HSG80 controller for operation with Tru64UNIX Version 5.1 and TruCluster Server Version 5.1. For more informationon installing the HSG80, see the Compaq StorageWorks HSG80 ArrayController ACS V...
Page 155 - show this; set nofailover
• 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 adapters must be cabled to the switch,with the system power applied before you turn power on tothe RA8000/ESA120...
Page 156 - clear cli; –30 Using Fibre Channel Storage
2 Prevents the command line interpreter (CLI) from reporting amisconfiguration error resulting from not having a failover modeset. 3 Puts the controller pair into multiple-bus failover mode. Ensurethat you copy the configuration information from the controllerknown to have a good array configuration...
Page 157 - Example 6–1: Determine HSG80 Connection Names; Using Fibre Channel Storage 6–31
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=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON50 TRU64_UNIX THIS 1 230813 OL this 0 HOST_ID...
Page 158 - restart other
____________________ Note _____________________ You can change the connection name with the HSG80 CLI RENAME command. For example, assume that member system pepicelli has two KGPSA Fibre Channel host bus adapters, and that the worldwide name for KGPSA pga is 1000-0000-C920-DA01. Example 6–1 shows th...
Page 159 - SHOW; Using Fibre Channel Storage 6–33
____________________ Note _____________________ If the fiber-optic cables are not properly installed, there willbe 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.6.1.1. 6.5.3.1 Obtaining the World...
Page 160 - Installing Tru64 UNIX and TruCluster Server Software; show unit; –34 Using Fibre Channel Storage
– Controller B port 1 — 5000-1FE1-0000-0D63 – Controller B port 2 — 5000-1FE1-0000-0D64 Because the HSG80 controller ’s configuration information and worldwidename is stored in nonvolatile random-access memory (NVRAM) on thecontroller, there are different procedures for replacing HSG80 controllersin...
Page 161 - Using Fibre Channel Storage 6–35
to each of those devices. For example, to boot from storage unit D1 as presented by the HSG80 controller, the AlphaServer console requires adevice 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. T...
Page 162 - –36 Using Fibre Channel Storage
• 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 Tru64 UNIX operating system or TruCluster Serversoftware, follow the procedure in Chapter 1. 6.6.1 Before You Install...
Page 163 - Example 6–2: Setting Up the Mirrorset; Using Fibre Channel Storage 6–37
Table 6–2 contains the necessary information to convert from the HSG80unit numbers to /dev/disk/dsk n and device names for the example configuration. A blank table (Table A–1) is provided in Appendix A for use inan actual installation. One mirrorset, the BOOT-MIR mirrorset, will be used for the Tru6...
Page 164 - –38 Using Fibre Channel Storage
Example 6–2: Setting Up the Mirrorset (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> CREATE_PARTITION CROOT-MIR SIZE=5 6 HSG80> CREATE_PARTITION CROOT-MIR SIZE=15 6 HSG80> CREATE_P...
Page 165 - Using Fibre Channel Storage 6–39
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 Tru64 UNIX...
Page 166 - Adding Units and Identifiers to the HSG80 Storagesets; Set an identifier for each storage unit.; Example 6–3: Adding Units and Identifiers to the HSG80 Storagesets; –40 Using Fibre Channel Storage
6.6.1.2 Adding Units and Identifiers to the HSG80 Storagesets After you have created the storagesets (mirrorsets and partitions), assigna unit number to each partition and set a unique identifier as shown inExample 6–3. The steps performed in Example 6–3 include: • Assign a unit number to each stora...
Page 167 - Using Fibre Channel Storage 6–41
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. If you wish to enable ...
Page 168 - –42 Using Fibre Channel Storage
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 number between 1 and9999. To keep your storage naming as consistent and simple as possible,consider using the unit number of the unit as its UDID. for in...
Page 169 - dsk; Table 6–2: Converting Storageset Unit Numbers to Disk Names; Worldwide Name; Quorum disk; Using Fibre Channel Storage 6–43
unwanted system. Record the identifier and worldwide name for lateruse. Table 6–2 is a sample table filled in for the example. Table A–1 inAppendix A is a blank table for your use in an actual installation. ____________________ Note _____________________ At this point, even though the table is fille...
Page 170 - –44 Using Fibre Channel Storage
UNIX Version 5.1 installation disk or cluster member system boot disks.Setting the device unit number allows the installation scripts to recognize aFibre Channel disk. To set the device unit number for a Fibre Channel device, follow these steps: 1. Use the HSG80 show unit command to obtain the user ...
Page 171 - Using Fibre Channel Storage 6–45
console command, it would not detect the Fibre Channel devicesconnected to the HSG80. Example 6–4: Displaying the UDID and Worldwide Names of DevicesKnown to the Console P00>>> wwidmgr -show wwid [0] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-0008 (ev:none) [1] UDID:-1 WWID:01...
Page 172 - –46 Using Fibre Channel Storage
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 Tru64 UNIX disk (133) and each membersystem boot disks (131, 132) to ensure the storage unit is seen. As asecond che...
Page 173 - The; Using Fibre Channel Storage 6–47
Example 6–5: Using the wwidmgr quickset Command to Set the DeviceUnit 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.1001.0.1.0 pga0.0.0.1.0 5000-1fe1-...
Page 174 - –48 Using Fibre Channel Storage
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 unitnumber as shown in Example 6–5. You have to use the quickset command with the item number displayed by the wwidmgr -show wwid command (see Example 6–4). F...
Page 175 - Example 6–6: Sample Fibre Channel Device Names; Installation; Using Fibre Channel Storage 6–49
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.0 $1$DGA133 HSG80 V8.5F dga133.1002.0.1.0 $1$DGA133 ...
Page 177 - Install the Tru64 UNIX Operating System; hwmgr; Using Fibre Channel Storage 6–51
6.6.2 Install the Tru64 UNIX Operating System After reading the TruCluster Server Software Installation manual, andusing the Tru64 UNIX Installation Guide as a reference, boot from theCD-ROM and install the Tru64 UNIX Version 5.1 operating system. When the installation procedure displays the list of...
Page 178 - –52 Using Fibre Channel Storage
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 -view dev | grep IDENTIFIER | grep 131 ____________________ Note _____________________ If you have no...
Page 179 - grep; Label the Disks to Be Used to Create the Cluster; Quorum; Install the TruCluster Server Software and Create the First; Using Fibre Channel Storage 6–53
2. Search the display for the UDIDs (or worldwide names) for each of thecluster installation disks and record the /dev/disk/dsk n values. If you used the grep utility to search for a specific UDID, for example hwmgr -view dev | grep "IDENTIFIER=131" repeat the command to determine the /dev/d...
Page 180 - –54 Using Fibre Channel Storage
To reset the bootdef_dev console environment variable, follow these steps: 1. Obtain the device name and worldwide name for the Fibre Channel unitfrom where you will boot cluster member system 1 (see Table 6–2). 2. Check the reachability display (Example 6–5) provided by the wwidmgr -quickset or the...
Page 181 - wwidmgr -show reachability; Add Additional Systems to the Cluster; Using Fibre Channel Storage 6–55
or wwidmgr -show reachability ). You must initialize the system to use any of the device names in the bootdef_dev variable as follows: P00>>> set bootdef_dev \ dga131.1001.0.1.0,dga131.1004.0.1.0,\ dgb131.1002.0.2.0,dgb131.1003.0.2.0 POO>>> init ______________________ Note ________...
Page 182 - –56 Using Fibre Channel Storage
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. Each installed subset will be configur...
Page 183 - Converting the HSG80 from Transparent to Multiple-Bus; Using Fibre Channel Storage 6–57
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. S...
Page 184 - –58 Using Fibre Channel Storage
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. Each path between a Fibre Channel host bus adapter in a host computerand an active h...
Page 185 - SET NOFAILOVER; Execute the; Using Fibre Channel Storage 6–59
6.7.2 Procedure to Convert from Transparent to Multiple-bus Failover Mode To change from transparent failover to multiple-bus failover mode byresetting the unit offsets and modifying the systems’ view of the storageunits, follow these steps: 1. Shut down the operating systems on all host systems tha...
Page 186 - –60 Using Fibre Channel Storage
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_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON60 TRU64_UNIX OTHER 2 offline 100 HOST_...
Page 187 - set mode diag; Console is in diagnostic mode; wwid
__________________ Note ___________________ You must set the console to diagnostic mode to usethe wwidmgr command for the following AlphaServer systems: AS1200, AS4x00, AS8x00, GS60, GS60E, andGS140. Set the console to diagnostic mode as follows: P00>>> set mode diag Console is in diagnosti...
Page 188 - Using the emx Manager to Display Fibre Channel; Using the emxmgr Utility to Display Fibre Channel Adapter; emx0 SCSI target id assignments:; –62 Using Fibre Channel Storage
wwid2 wwid3N1 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 displayof the wwidmgr -quickset command for the appropriate de...
Page 189 - Using Fibre Channel Storage 6–63
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 Chan...
Page 190 - Status of the; –64 Using Fibre Channel Storage
portname 2004-0060-6900-5A1B nodename 1000-0060-6900-5A1BPresent, 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 3at SCSI ID 7. Both the port name and node name of the adapter (theworldwide n...
Page 191 - Using the emxmgr Utility Interactively; emxmgr; View adapter’s current Topology; Using Fibre Channel Storage 6–65
______________________ Note _______________________ You can use the emxmgr utility interactively to perform any of the previous functions. 6.8.2 Using the emxmgr Utility Interactively Start the emxmgr utility without any command-line options to enter the interactive mode to: • Display the presence o...
Page 192 - –66 Using Fibre Channel Storage
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 SCSI tgt id 6 : portname 1000-0000-C920-CD9C nodename 1000-0000-C920-CD9C SCSI tgt id 7 : portname 1...
Page 194 - Hardware Requirements for a Hard Partition in a Cluster; One or more network connections.
7.2 Hardware Requirements for a Hard Partition in a Cluster The TruCluster Server hardware requirements are the same for anAlphaServer GS80/160/320 hard partition as any other system in a cluster.You must have: • A supported host bus adapter connected to shared storage. This may bea KZPBA-CB for par...
Page 195 - Figure 7–1: Portion of QBB Showing I/O Riser Modules; BN39B I/O Riser Cable
Figure 7–1: Portion of QBB Showing I/O Riser Modules I/O Riser BN39B I/O Riser Cable ZK-1749U-AI ____________________ Notes ____________________ You can have up to two I/O riser modules in a QBB, but youcannot split them across partitions. Each I/O riser has two cable connections (Port 0 and Port 1)...
Page 199 - Figure 7–3: Rear View of Expansion and Primary PCI Drawers; Expansion PCI Drawer; PCI Drawer Node ID; Systems in a TruCluster Configuration; as Two Partitions in a Cluster
Figure 7–3: Rear View of Expansion and Primary PCI Drawers ZK-1751U-AI Expansion PCI Drawer Primary PCI Drawer Console SerialBus Node ID Module Local Terminal/COM1/Port PCI Drawer Node ID CSB Connector PCI Drawer Node ID CSB ConnectorConsole SerialBus Node ID Module Standard I/O Module I/O Riser 0 I...
Page 200 - View each partition as a separate system.
equally well with any number of partitions (as supported by the systemtype) by modifying the amount and placement of hardware and the SCMenvironment variable values. ______________________ Notes ______________________ View each partition as a separate system. Ensure that the system comes up as a sin...
Page 202 - On; show nvr
____________________ 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, powerdown the system with the power off SCM command, then partition the system. If the auto_qu...
Page 203 - Esc Esc
Example 7–1: Defining Hard Partitions with SCM Environment Variables(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 ff PRIMARY_QBB0 ff AUTO_QUIT_SCM 1 6 FAULT_TO_SYS 0 DIMM_READ_DIS 0 SCM_CSB_MASTER_ELIGIBLE 1 7 PERF_MON 20 ...
Page 204 - show csb; Example 7–2: Turning Partition Power On; quit
scm_csb_master_eligible environment variable. The master and standby SCM must be connected to the OCP. The master SCM musthave the lowest node ID. Use the node ID address obtained from the show csb SCM command (see Example 7–4). If multiple primary PCI drawers are eligible, theSCM on the PCI drawer ...
Page 206 - Configuration; Example 7–3: Displaying AlphaServer GS160 System Information
7.4 Determining AlphaServer GS80/160/320 System Configuration You may be required to reconfigure an AlphaServer GS80/160/320 systemthat is not familiar to you. Before you start to reconfigure any system, youneed to determine: • The number of partitions in the system • Which QBBs are in each partitio...
Page 208 - Example 7–4: Displaying Console Serial Bus Information
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 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. An S indicates that a standard I/O mo...
Page 211 - power off
– 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 – Hierarchical switch power manager (HPM): One on the H-switch • PCI host bus adapter EEPROMS To update the AlphaS...
Page 212 - boot dqa0; list; update srm
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 initialization sequence. SRM code is executed out of memory,not the SRM EEPROM on the standard I/O module. SCM_E0> power on 6. Transfer control from the ...
Page 213 - After you update the firmware, use the; Set the hard partitions back to the original configuration:; power on; at the console of each partition, boot the operating system.
___________________ Caution ___________________ Do not abort the update — doing so can cause a corrupt flashimage in a firmware module. A complete firmware update takes a long time. The length oftime increases proportionally to the number of PCI adaptersyou have. 9. After you update the firmware, us...
Page 215 - Preparing the TZ88 for Shared Bus Usage; Configuring a Shared SCSI Bus for Tape Drive Use 8–1
8 Configuring a Shared SCSI Bus for Tape Drive Use The topics in this section provide information on preparing the various tapedevices for use on a shared SCSI bus with the TruCluster Server product. ______________________ Notes ______________________ Section 8.7 and Section 8.8 provide documentatio...
Page 216 - –2 Configuring a Shared SCSI Bus for Tape Drive Use
8.1.1 Setting the TZ88N-VA SCSI ID You must set the TZ88N-VA switches before the tape drive is installed intothe BA350 StorageWorks enclosure. The Automatic selection is normallyused. The TZ88N-VA takes up three backplane slot positions. The physicalconnection is in the lower of the three slots. For...
Page 217 - Configuring a Shared SCSI Bus for Tape Drive Use 8–3
Table 8–1: TZ88N-VA Switch Settings SCSI ID SCSI ID Selection Switches 1 2 3 4 5 6 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 On Off Off Off Off 4 Off Off On Off Off Off 5 On Off On Off Off Off 6 Off On On Off Off Off 7 On On On ...
Page 218 - Figure 8–2: Shared SCSI Buses with SBB Tape Drives; Callout Number; –4 Configuring a Shared SCSI Bus for Tape Drive Use
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 SCSI Buses with SBB Tape Drives KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Member System 1 D S - D W Z Z H - 0 3 T T T 2 ...
Page 219 - Configuring a Shared SCSI Bus for Tape Drive Use 8–5
Table 8–2: Hardware Components Used to Create the Configuration Shownin Figure 8–2 (cont.) Callout Number Description 8 DWZZA-VA 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 mete...
Page 220 - Preparing the TZ89 for Shared SCSI Usage; –6 Configuring a Shared SCSI Bus for Tape Drive Use
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 not exceeded. Ensure that the tape drive on the end of the bus isterminated with a H8574-A or H8890-AA terminator. You can add additional TZ88N-TA tape...
Page 222 - –8 Configuring a Shared SCSI Bus for Tape Drive Use
Table 8–3: DS-TZ89N-VW Switch Settings (cont.) SCSI ID SCSI ID Selection Switches 1 2 3 4 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 Off Off On Off Off Off Off 9 On Off Off On Off Off Off Off 10 Off On Off On Off Off Off Off 11 On On ...
Page 223 - Attach a trilink connector to the differential end of the DWZZB-AA.; Configuring a Shared SCSI Bus for Tape Drive Use 8–9
8.2.3 Setting the DS-TZ89N-TA SCSI ID The DS-TZ89N-TA has a push-button counter switch on the rear panel toselect the SCSI ID. It is preset at the factory to 15. Push the button abovethe counter to increment the SCSI ID (the maximum is 15); push the buttonbelow the switch to decrease the SCSI ID. 8....
Page 224 - –10 Configuring a Shared SCSI Bus for Tape Drive Use
8.3 Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is a Digital Linear Tape (DLT)tabletop cartridge tape drive capable of holding up to 40 GB of dataper Compactape IV cartridge using 2:1 compression. It is capable ofstoring/retrieving data at a rate of up to 10.8 GB per hour (usin...
Page 225 - Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel; Configuring a Shared SCSI Bus for Tape Drive Use 8–11
Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel + - 0 20/40 GB DLT Tape Drive S C S I I DS e l e c t o rS w i t c h S C S I I D + - 0 ZK-1603U-AI 8.3.2 Cabling the Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is connected to a single-endedsegment of the shared SCSI bus. A ...
Page 226 - –12 Configuring a Shared SCSI Bus for Tape Drive Use
cable). Ensure that the trilink or Y cable at both ends of the differentialsegment of the shared SCSI bus is terminated with an HD68 differentialterminator such as an H879-AA. The single-ended SCSI bus may be daisy chained from one single-endedtape drive to another with cable part number 146745-003 ...
Page 227 - Configuring a Shared SCSI Bus for Tape Drive Use 8–13
Figure 8–5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT TapeDrive KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 10 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T ...
Page 228 - –14 Configuring a Shared SCSI Bus for Tape Drive Use
Table 8–4: Hardware Components Used to Create the Configuration Shownin Figure 8–5 (cont.) Callout Number Description 9 199629-002 or 189636-002 (68-pin high density to 50-pinhigh density 1.8-meter cables) 10 341102-001 50-pin high density terminator a The maximum length of the BN38C (or BN38D) cabl...
Page 229 - Configuring a Shared SCSI Bus for Tape Drive Use 8–15
8.4.2 Cabling the Compaq 40/80-GB DLT Drive The Compaq 40/80-GB DLT Drive is connected to a single-ended segmentof the shared SCSI bus. Figure 8–6 shows a configuration with a Compaq40/80-GB DLT Drive for use on a shared SCSI bus. To configure the shared SCSI bus for use with a Compaq 40/80-GB DLTDr...
Page 230 - Figure 8–6: Cabling a Shared SCSI Bus with a Compaq 40/80-GB DLT Drive; Table 8–5: Hardware Components in the Configuration in Figure 8–6; –16 Configuring a Shared SCSI Bus for Tape Drive Use
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 shared storage on the same SCSI bus with the tape drive. Figure 8–6: Cabling a Shared SCSI Bus with a Compaq 40/80-GB DLT Drive KZPBA-CB (ID 7) Memor...
Page 231 - H885-AA trilink connector; Preparing the TZ885 for Shared SCSI Usage; SCSI ID SEL; Press the Display Mode push button again.; Configuring a Shared SCSI Bus for Tape Drive Use 8–17
Table 8–5: Hardware Components in the Configuration in Figure 8–6 (cont.) Callout Number Description 8 H885-AA trilink connector 9 189646-001 (0.9 meter cable) or 189646-002 (1.8 meter cable) d BN21K-01 or BN21L-01 (1 meter cable) d BN21K-02 or BN21L-02 (2 meter cable) d 10 152732-001 LVD terminator...
Page 232 - You will need one DWZZA-AA or DWZZB-AA for each TZ885 tape drive.; –18 Configuring a Shared SCSI Bus for Tape Drive Use
8.5.2 Cabling the TZ885 Tape Drive The TZ885 is connected to a single-ended segment of the shared SCSIbus. It is connected to a differential portion of the shared SCSI bus with aDWZZA-AA or DWZZB-AA. Figure 8–7 shows a configuration of a TZ885 foruse on a shared SCSI bus. To configure the shared SCS...
Page 233 - Configuring a Shared SCSI Bus for Tape Drive Use 8–19
______________________ Note _______________________ Ensure that there is no conflict with tape drive and host busadapter SCSI IDs. Figure 8–7: Cabling a Shared SCSI Bus with a TZ885 KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 D S...
Page 234 - Preparing the TZ887 for Shared SCSI Bus Usage; –20 Configuring a Shared SCSI Bus for Tape Drive Use
Table 8–6: Hardware Components Used to Create the Configuration Shownin 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. b The maximum le...
Page 235 - Figure 8–8: TZ887 DLT MiniLibrary Rear Panel; Configuring a Shared SCSI Bus for Tape Drive Use 8–21
Figure 8–8: TZ887 DLT MiniLibrary Rear Panel + - 0 T Z 8 8 7 Z K - 1 4 6 1 U - A I S C S I I D S C S I I DS e l e c t o rS w i t c h + - 0 8.6.2 Cabling the TZ887 Tape Drive The TZ887 is connected to a single-ended segment of the shared SCSIbus. It is connected to a differential portion of the share...
Page 236 - –22 Configuring a Shared SCSI Bus for Tape Drive Use
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 orH8890-AA terminator. You can add additional shared SCSI buses with TZ887 tape drives by addingadditional DWZZB-AA/TZ887 combinations. __________________...
Page 237 - DLT0 Idle; Configuring a Shared SCSI Bus for Tape Drive Use 8–23
8.7 Preparing the TL891 and TL892 DLT MiniLibraries for Shared SCSI Usage ______________________ Note _______________________ To achieve system performance capabilities, we recommendplacing no more than two TZ89 drives on a SCSI bus, and alsorecommend that no shared storage be placed on the same SCS...
Page 238 - –24 Configuring a Shared SCSI Bus for Tape Drive Use
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 robotics,and the fourth line is a map of the magazine, with the numbers from 0 to9 representing the cartridge slots. Rectangles present on this line indicate...
Page 239 - Repeat steps 4 and 5 to set other SCSI bus IDs as necessary.; Configuring a Shared SCSI Bus for Tape Drive Use 8–25
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 IDs are as follows: • Lib Bus ID: 0 • DLT0 Bus ID: 4 • DLT1 Bus ID: 5 Use the up or down arrow button to select the item for which you needto change ...
Page 240 - –26 Configuring a Shared SCSI Bus for Tape Drive Use
SCSI bus without stopping all ASE services that generate activityon the bus. For this reason, we recommend that tape devices be placed onseparate shared SCSI buses, and that there be no storage deviceson the SCSI bus. The cabling depends on whether or not there are one or two drives, and forthe two-...
Page 241 - Configuring a Shared SCSI Bus for Tape Drive Use 8–27
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 BN21K or BN21L between the last trilink connector on oneshared SCSI bus to the leftmost connector (as viewed from the rear) ofthe TL892. 2. Connect a B...
Page 242 - –28 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–10: TruCluster Server Cluster with a TL892 on Two Shared SCSIBuses KZPBA-CB (ID 7) Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Member System 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 6 7 K...
Page 243 - Preparing the TL890 DLT MiniLibrary Expansion Unit; TL890 DLT MiniLibrary Expansion Unit Hardware; Configuring a Shared SCSI Bus for Tape Drive Use 8–29
8.8 Preparing the TL890 DLT MiniLibrary Expansion Unit The topics in this section provide information on preparing the TL890 DLTMiniLibrary expansion unit with the TL891 and TL892 DLT MiniLibrariesfor use on a shared SCSI bus. ______________________ Note _______________________ To achieve system per...
Page 244 - –30 Configuring a Shared SCSI Bus for Tape Drive Use
8.8.2.1 Cabling the DLT MiniLibraries You must make the following connections to render the DLT MiniLibrarysystem operational: • Expansion unit to the motor mechanism: The motor mechanism cable isabout 1 meter long and has a DB-15 connector on each end. Connect itbetween the connector labeled Motor ...
Page 245 - Configuring a Shared SCSI Bus for Tape Drive Use 8–31
____________________ Notes ____________________ Do not connect a SCSI bus to the SCSI connectors for thelibrary connectors on the base modules. We recommend that no more than two TZ89 tape drives beon a SCSI bus. Figure 8–11 shows a MiniLibrary configuration with two TL892 DLTMiniLibraries and a TL8...
Page 246 - Figure 8–11: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses; –32 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–11: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses T L 8 9 2 T L 8 9 2 T L 8 9 0 L i b r a r y R o b o t i c s D L T 1 E x p a n s i o n M o d u l e s R o b o t i c s C o n t r o l c a b l e s D L T 2 L i b r a r y R o b o t i c s D L T 1 D L T 2 E x p a n s i o nU n i tI n t e r f ...
Page 247 - Configuring a Shared SCSI Bus for Tape Drive Use 8–33
Table 8–8: Hardware Components Used to Create the Configuration Shownin Figure 8–10 Callout Number Description 1 BN38C or BN38D cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator 5 BN21W-0B Y cable 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The m...
Page 248 - Loader Idle; –34 Configuring a Shared SCSI Bus for Tape Drive Use
After a series of power-on self-tests have executed, the default screenwill be displayed on the base module control panel: DLT0 IdleDLT1 Idle Loader Idle 0> _ _ _ _ _ _ _ _ _ _ <9 The default screen shows the state of the tape drives, loader, andnumber of cartridges present for this base modul...
Page 249 - Expansion unit: 0 through 15; DLT2 Idle; Configuring a Shared SCSI Bus for Tape Drive Use 8–35
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 expansion unit comes up, it will communicate with each basemodule through the expansion unit interface and inventory the number ofbase modules, tape drives...
Page 250 - until the Default window is displayed.; Preparing the TL894 DLT Automated Tape Library for; –36 Configuring a Shared SCSI Bus for Tape Drive Use
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 andpress the Enter button. 6. Press the up or down arrow button to select the appropriate tape...
Page 251 - TL894 Robotic Controller Required Firmware; Table 8–9: TL894 Default SCSI ID Settings; SCSI Device; Robotics Controller; Press and release SELECT to enter the menu mode.; Configuring a Shared SCSI Bus for Tape Drive Use 8–37
______________________ Note _______________________ To achieve system performance capabilities, we recommendplacing no more than two TZ89 drives on a SCSI bus segment.We also recommend that storage be placed on shared SCSI busesthat do not have tape drives. The TL894 midrange automated DLT library c...
Page 252 - –38 Configuring a Shared SCSI Bus for Tape Drive Use
Menu: Configuration Inquiry 6. Press and release the up or down arrow buttons to locate the SCSIAddress submenu, and verify that the following information is displayedin the SDA: Menu: Configuration SCSI Address .. 7. Press and release the SELECT button to choose the SCSI Addresssubmenu and verify t...
Page 253 - TL894 Tape Library Internal Cabling; Configuring a Shared SCSI Bus for Tape Drive Use 8–39
6. Press and release the SELECT button again to choose SCSI Addressand 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 verifythat the following information is shown in the SDA: Menu: SCSI Address D...
Page 254 - Figure 8–12: TL894 Tape Library Four-Bus Configuration; –40 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–12: TL894 Tape Library Four-Bus Configuration Robotics Controller*SCSI Address 0 Rear PanelHost 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 DriveInterface P...
Page 255 - Connecting the TL894 Tape Library to the Shared SCSI Bus; Configuring a Shared SCSI Bus for Tape Drive Use 8–41
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, thelength of the SCSI bus is increased by 1.5 meters, and may causeproblems if SCSI bus length is of concern. In a future revision of the previously m...
Page 256 - Figure 8–13: Shared SCSI Buses with TL894 in Two-Bus Mode; –42 Configuring a Shared SCSI Bus for Tape Drive Use
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 and 3).Ensure that the terminators are present on the tape drives 1 and 3. Figure 8–13: Shared SCSI Buses with TL894 in Two-Bus Mode KZPBA-CB (ID 7) Mem...
Page 257 - Preparing the TL895 DLT Automated Tape Library for; TL895 DLT Library Operator ’s Guide; Configuring a Shared SCSI Bus for Tape Drive Use 8–43
Table 8–10: Hardware Components Used to Create the ConfigurationShown 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. b The maximum lengt...
Page 258 - TL895 Robotic Controller Required Firmware; Table 8–11: TL895 Default SCSI ID Settings; At the control panel, press the Operator tab.; –44 Configuring a Shared SCSI Bus for Tape Drive Use
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 panel do not conflict with any SCSIbus controller SCSI ID. The following sections describe how to prepare the TL895 for use on a sharedSCSI bus in more ...
Page 259 - To change any of the configurations, press the Configure button.; Configuring a Shared SCSI Bus for Tape Drive Use 8–45
3. On the Operator screen, press the Configure Library button. TheConfigure Library screen displays the current library configuration. ____________________ Note _____________________ You can configure the library model number, number ofstorage bins, number of drives, library SCSI ID, and tapedrive S...
Page 260 - To reconfigure TL895 SCSI bus configuration, follow these steps:; –46 Configuring a Shared SCSI Bus for Tape Drive Use
You can reconfigure the tape drives and robotics controller to place multipletape drives on the same SCSI bus with SCSI bus jumper (part number6210567) included with the tape library. ______________________ Note _______________________ We recommend placing no more than two TZ89 drives on a SCSIbus s...
Page 261 - Figure 8–14: TL895 Tape Library Internal Cabling; Configuring a Shared SCSI Bus for Tape Drive Use 8–47
Figure 8–14: TL895 Tape 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 7 SCSI Port 6 SCSI Port 2 SCSI Port 1 Terminator Terminator Terminator Terminator PN 0415619 SCSI Jumper ...
Page 262 - Connecting the TL895 Tape Library to the Shared SCSI Bus; Libraries for Shared SCSI Bus Usage; –48 Configuring a Shared SCSI Bus for Tape Drive Use
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 TL895 DriveUpgrade Instructions manual for upgrade instructions. 8.10.5 Connecting the TL895 Tape Library to the Shared SCSI Bus The TL895 tape libra...
Page 263 - The tape library specifications are as follows:; Configuring a Shared SCSI Bus for Tape Drive Use 8–49
Each tape library comes configured with a robotic controller and bar codereader (to obtain quick and accurate tape inventories). The libraries have either three or six TZ89N-AV drives. The TL896, becauseit has a greater number of drives, has a lower capacity for tape cartridgestorage. Each tape libr...
Page 264 - Communications with the Host Computer; Switch 7 on the MUC switch pack must be down to select the SCSI bus.; Table 8–12: MUC Switch Functions; Switch; MUC SCSI ID if Switch 7 is down; –50 Configuring a Shared SCSI Bus for Tape Drive Use
These tape libraries each have a multi-unit controller (MUC) that servestwo functions: • It is a SCSI adapter that allows the SCSI interface to controlcommunications between the host and the tape library. • It permits the host to control up to five attached library units in amulti-unit configuration...
Page 265 - Table 8–13: MUC SCSI ID Selection; Configuring a Shared SCSI Bus for Tape Drive Use 8–51
Table 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 TruCluster Server cluster, switch 7 is down, allowing switches 1, 2, and 3 to select the MUC SCSI ID. 8.11.3 Setting the MUC SCSI ID The multi-unit c...
Page 266 - MUC; –52 Configuring a Shared SCSI Bus for Tape Drive Use
Table 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.11.5 TL893 and TL896 Automated Tape Library Internal Cabling The default internal cabling configurations for the TL893 and TL896Automated...
Page 267 - Figure 8–15: TL893 Three-Bus Configuration; Configuring a Shared SCSI Bus for Tape Drive Use 8–53
Figure 8–15: TL893 Three-Bus Configuration MUC SCSI Address 2 SCSI Port A SCSI Port B SCSI Port C TZ89 Tape DriveSCSI Address 5 (top shelf) TZ89 Tape DriveSCSI Address 4 (middle shelf) TZ89 Tape DriveSCSI Address 3 (bottom shelf) 0425031 (SCSI Diff Feed Through) Drive Housing 0415619(68-pin Micro-D ...
Page 268 - the Shared SCSI Bus; –54 Configuring a Shared SCSI Bus for Tape Drive Use
– 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 are 68-pin differential terminators (partnumber 0415619). Figure 8–16: TL896 Six-Bus Configuration MUC SCSI Address 2 SCSI Port D SCSI Port E SCSI Port...
Page 269 - Configuring a Shared SCSI Bus for Tape Drive Use 8–55
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.Therefore, TL893 and TL896 tape libraries must be on the end of the sharedSCSI bus. In a TruCluster Server cluster with TL893 or TL896 tape libraries, the...
Page 270 - Figure 8–17: Shared SCSI Buses with TL896 in Three-Bus Mode; –56 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–17: Shared SCSI Buses with TL896 in Three-Bus Mode KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 7 KZPBA-CB (ID 6) T T Network T Member ...
Page 271 - Shared Bus Usage; TL881 MiniLibrary System User ’s Guide; Configuring a Shared SCSI Bus for Tape Drive Use 8–57
Table 8–16: Hardware Components Used to Create the ConfigurationShown 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. b The maximum lengt...
Page 272 - The expansion unit works with either the TL881 or TL891 base unit.; –58 Configuring a Shared SCSI Bus for Tape Drive Use
8.12.1.2 TL881 and TL891 MiniLibrary Rackmount Components A TL881 or TL891 base unit (which contains the tape drive(s)) can operateas an independent, standalone unit, or in concert with an expansion unitand multiple data units. A rackmount multiple-module configuration is expandable to up to sixmodu...
Page 273 - The data unit works with either the TL881 or TL891 base unit.; Configuring a Shared SCSI Bus for Tape Drive Use 8–59
• Data unit — This rackmount module contains a 16-cartridge magazineto provide additional capacity in a multi-module configuration. The dataunit robotics works in conjunction with the robotics of the expansion unitand base units. It is under control of the expansion unit. The data unit works with ei...
Page 274 - Table 8–18: DLT MiniLibrary Part Numbers; DLT Library Component
Table 8–17: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary ConfiguredforMaximum: Number ofBase Units a b Number ofData Units c TransferRate d StorageCapacity e TransferRate f StorageCapacity g Performance 5 0 15 MB/sec(54GB/hour) 1.32 TB (66cartri...
Page 275 - Rackmount; Use; Bus Usage; Configuring a Shared SCSI Bus for Tape Drive Use 8–61
Table 8–18: DLT MiniLibrary Part Numbers (cont.) DLT Library Component Number of TapeDrives Tabletop/Rackmount Part Number TL891 DLT MiniLibraryBase Unit 2 Rackmount 120876-B22 Add-on DLT 35/70 drivefor TL891 1 N/A 120878-B21 MiniLibrary Expansion Unit N/A Rackmount 120877-B21 MiniLibrary Data Unit ...
Page 276 - –62 Configuring a Shared SCSI Bus for Tape Drive Use
For complete hardware installation instructions, see the TL881 MiniLibrarySystem User ’s Guide or TL891 MiniLibrary System User ’s Guide. 8.12.2.1.1 Setting the Standalone MiniLibrary Tape Drive SCSI ID The control panel on the front of the TL891 and TL892 MiniLibraries is usedto display power-on se...
Page 277 - Configuring a Shared SCSI Bus for Tape Drive Use 8–63
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, then press the Enter button to display the Configure submenu. ____________________ Note _____________________ The control panel up and down arrows ha...
Page 278 - –64 Configuring a Shared SCSI Bus for Tape Drive Use
______________________ Note _______________________ The tape drive SCSI connectors are labeled DLT1 (tape drive 1)and DLT2 (tape drive 2). The control panel designation for thedrives is DLT0 (tape drive 1) and DLT1 (tape drive 2). The default for the TL881 or TL891 DLT MiniLibrary is to place the ro...
Page 279 - Configuring a Shared SCSI Bus for Tape Drive Use 8–65
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 robotics and two drives to a single shared SCSI bus,follow these steps: 1. Connect a 328215-00X, BN21K, or BN21L between the last trilinkconnector on ...
Page 280 - Figure 8–18: TL891 Standalone Cluster Configuration; –66 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–18: TL891 Standalone Cluster Configuration KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 KZ...
Page 281 - Configuring a Shared SCSI Bus for Tape Drive Use 8–67
Table 8–19: Hardware Components Used to Create the ConfigurationShown 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. b The maximum lengt...
Page 282 - –68 Configuring a Shared SCSI Bus for Tape Drive Use
connector on the data unit and the female end to any Expansion Modulesconnector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector you connect toa base unit or a data unit. • SCSI bus connection to the expansion unit robotics: Connect...
Page 283 - Figure 8–19: TL891 DLT MiniLibrary Rackmount Configuration; Configuring a Shared SCSI Bus for Tape Drive Use 8–69
Figure 8–19: TL891 DLT MiniLibrary Rackmount Configuration KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Member System 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 7 KZPBA-CB (ID 6) T T Ne...
Page 284 - –70 Configuring a Shared SCSI Bus for Tape Drive Use
Table 8–20: Hardware Components Used to Create the ConfigurationShown in Figure 8–18 Callout Number Description 1 BN38C or BN38D cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator 5 BN21W-0B Y cable 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The ...
Page 285 - Configuring a Shared SCSI Bus for Tape Drive Use 8–71
DLT0 Idle DLT1 IdleLoader Idle 0> _ _ _ _ _ _ _ _ _ _ <9 The default screen shows the state of the tape drives, loader, andnumber of cartridges present for this base unit. A rectangle in place ofthe underscore indicates that a cartridge is present in that location. 2. Press the Enter button to...
Page 286 - –72 Configuring a Shared SCSI Bus for Tape Drive Use
When the expansion unit comes up, it will communicate with each base anddata unit through the expansion unit interface and inventory the numberof base units, tape drives, data units, and cartridges present in each baseand data unit. After the MiniLibrary configuration has been determined, theexpansi...
Page 287 - You do not have to cycle power to set the SCSI IDs.; Configuring a Shared SCSI Bus for Tape Drive Use 8–73
• DLT3 Bus ID: 4 • DLT4 Bus ID: 5 • DLT5 Bus ID: 6 7. Press Enter when you have the item selected for which you wish tochange the SCSI ID. 8. Use the up and down arrows to select the desired SCSI ID. Press theEnter button to save the new selection. 9. Press the Escape button once to return to the Se...
Page 288 - Order Number; Preparing the ESL9326D Enterprise Library for Shared SCSI; –74 Configuring a Shared SCSI Bus for Tape Drive Use
______________________ Note _______________________ These tape devices have been qualified for use on shared SCSIbuses with both the KZPSA-BB and KZPBA-CB host busadapters. 8.13.2 ESL9326D Enterprise Library Overview The ESL9326D Enterprise Library is an enterprise Digital Linear Tape(DLT) automated...
Page 289 - Configuring a Shared SCSI Bus for Tape Drive Use 8–75
______________________ Notes ______________________ The ESL9326D Enterprise Library is cabled internally for two35/70 DLT tape drives on each SCSI bus. It arrives with thelibrary electronics cabled to tape drives 0 and 1. Every otherpair of tape drives is cabled together (2 and 3, 4 and 5, 6 and7, a...
Page 290 - –76 Configuring a Shared SCSI Bus for Tape Drive Use
Figure 8–20: ESL9326D Internal Cabling T Tape Drive 0 Tape Drive 1 Tape Drive 2 Tape Drive 3 Tape Drive 4 Tape Drive 5 Tape Drive 6 Tape Drive 7 Tape Drive 8 Tape Drive 9 Tape Drive 10 Tape Drive 11 Tape Drive 12 Tape Drive 13 Tape Drive 14 Tape Drive 15 Robotics T T T T T T T A B C D E F G H P O N ...
Page 291 - Configuring a Shared SCSI Bus for Tape Drive Use 8–77
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 cablingfor each pair of tape drives. Because of the internal SCSI bus lengths, youcannot use a trilink connector or Y cable to terminate the SCSI bus externalt...
Page 292 - –78 Configuring a Shared SCSI Bus for Tape Drive Use
______________________ Notes ______________________ Each ESL9326D Enterprise Library arrives with one 330563-001HD68 terminator for each pair of tape drives (one SCSI bus). Thekit also includes at least one 330582-001 jumper cable to connectthe library electronics to tape drives 0 and 1. Tape librar...
Page 293 - Externally terminated TruCluster Server configurations; Non-UltraSCSI Devices 9–1
9 Configurations Using External Termination or Radial Connections to Non-UltraSCSI Devices This chapter describes the requirements for the shared SCSI bus using: • Externally terminated TruCluster Server configurations • Radial configurations with non-UltraSCSI RAID array controllers In addition to ...
Page 294 - Using SCSI Bus Signal Converters; DWZZA — 8-bit data path; Types of SCSI Bus Signal Converters
9.1 Using SCSI Bus Signal Converters A SCSI bus signal converter allows you to couple a differential bus segmentto a single-ended bus segment, allowing the mixing of differential andsingle-ended devices on the same SCSI bus to isolate bus segments formaintenance purposes. Each SCSI signal converter ...
Page 295 - Using the SCSI Bus Signal Converters; Non-UltraSCSI Devices 9–3
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 discuss the DWZZA and DWZZB signal convertersand the DS-BA35X-DA personality module. 9.1.2 Using the SCSI Bus Signal Converters The DWZZA and DWZZB sig...
Page 297 - Terminating the Shared SCSI Bus; Non-UltraSCSI Devices 9–5
______________________ Notes ______________________ S4-3 and S4-4 have no function on the DS-BA35X-DA personalitymodule. See Section 9.3.2.2 for information on how to select the deviceSCSI IDs in an UltraSCSI BA356. Figure 9–3 shows the relative positions of the two DS-BA35X-DA switchpacks. Figure 9...
Page 299 - Non-UltraSCSI Devices 9–7
connector at a later time without affecting bus termination. This allows youto expand your configuration without shutting down the cluster. Figure 9–4 shows a BN21W-0B Y cable, which you may attach to aKZPSA-BB or KZPBA-CB SCSI adapter that has had its onboard terminationremoved. You can also use th...
Page 300 - Overview of Disk Storage Shelves
Figure 9–5: HD68 Trilink Connector (H885-AA) FRONT VIEW REAR VIEW ZK-1140U-AI ______________________ Note _______________________ If you connect a trilink connector to a SCSI bus adapter, youmay block access to an adjacent PCI slot. If this occurs, use a Ycable instead of the trilink connector. This...
Page 301 - Non-UltraSCSI Devices 9–9
9.3.1 BA350 Storage Shelf Up to seven narrow (8-bit) single-ended StorageWorks building blocks(SBBs) can be installed in the BA350. Their SCSI IDs are based upon theslot they are installed in. For instance, a disk installed in BA350 slot 0 hasSCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1...
Page 302 - Figure 9–6: BA350 Internal SCSI Bus
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 TruCluster Server clusters:the BA356 (non-UltraSCSI BA356) and the UltraSCSI BA356. An example of the non-UltraSCSI BA356 is the BA356-KC, which...
Page 303 - Non-UltraSCSI Devices 9–11
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 moduleaddress 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. The jum...
Page 304 - Figure 9–7: BA356 Internal SCSI Bus
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 ofthe box when it is standing vertically). JB1, on the front of the module, isvisible. JA1 is on the left side of the personality module as you fa...
Page 305 - Non-UltraSCSI Devices 9–13
Figure 9–8: BA356 Jumper and Terminator Module Identification Pins Slot 6 Jumper Pin Slot 6 Terminator Pin Slot 1 Jumper Pin Slot 1 Terminator 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. The DS-BA35X-DA...
Page 307 - for an Externally Terminated TruCluster Server Configuration; Non-UltraSCSI Devices 9–15
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 Preparing BA350, BA356, and UltraSCSI BA356 Storage Shelves for an Externally Terminated TruCluster Server Configuration You may be using the BA350,...
Page 308 - Install the DWZZA-VA in slot 0 of the BA350.; Preparing a BA356 Storage Shelf for Shared SCSI Usage; Set the switches on the BA356 personality module as follows:
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 termination from the differential end by removing the five14-pin differential terminator resistor SIPs. 3. Attach an H885-AA trilink connector to the DWZZA...
Page 309 - If you are using a DWZZB-VW, install it in slot 0 of the BA356.; Connecting Storage Shelves Together; Non-UltraSCSI Devices 9–17
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.4.1.3 Preparing an UltraSCSI BA356 Storage Shelf for a TruCluster Configuration An UltraSCSI BA356 storage shelf is connected to a shared UltraSCSI...
Page 311 - Figure 9–9: BA350 and BA356 Cabled for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–19
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 Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 ID 14 orredundantpowersupply KZPSA-BB (ID 7) MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Chan...
Page 312 - Connect a BN21K or BN21L cable between the H885-AA trilinks.
Table 9–1: Hardware Components Used for Configuration Shown in Figure8–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. 9...
Page 313 - Figure 9–10: Two BA356s Cabled for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–21
Figure 9–10 shows a two member TruCluster Server configuration using twoBA356s for storage. Figure 9–10: Two BA356s Cabled for Shared SCSI Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 ID 14 orredundantpowersupply KZPSA-BB (ID 7) MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Channel MemberSy...
Page 314 - Connecting Two UltraSCSI BA356s for Shared SCSI Bus Usage
9.4.2.3 Connecting Two UltraSCSI BA356s for Shared SCSI Bus Usage When you use two UltraSCSI BA356 storage shelves on a shared SCSI busin a TruCluster configuration, one storage shelf must be configured for SCSIIDs 0 through 6 and the other configured for SCSI IDs 8 through 14. To prepare two UltraS...
Page 315 - Figure 9–11: Two UltraSCSI BA356s Cabled for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–23
Figure 9–11 shows a two member TruCluster Server configuration usingtwo UltraSCSI BA356s for storage. Figure 9–11: Two UltraSCSI BA356s Cabled for Shared SCSI Bus Usage ID 8 ID 9 ID 10 ID 11 ID 12 ID 13 PWR ID 5 PWR Clusterwide/, /usr, /var Member 1Boot Disk Member 2Boot Disk QuorumDisk UltraSCSI BA...
Page 316 - Terminated Shared SCSI Bus; KZPSA-BB host bus adapter
Table 9–2: Hardware Components Used for Configuration Shown in Figure9–11 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA HD68 terminator 3 BN38C (or BN38D) cable a 4 H8861-AA VHDCI trilink connector 5 BN37A cable a a The maximum combined length of the BN38C (or BN38D) and BN37A cables on on...
Page 317 - Non-UltraSCSI Devices 9–25
9.4.3.1 Cabling an HSZ40 or HSZ50 in a Cluster Using External Termination To connect an HSZ40 or HSZ50 controller to an externally terminated sharedSCSI bus, follow these steps: 1. If the HSZ40 or HSZ50 will be on the end of the shared SCSI bus, attachan H879-AA terminator to an H885-AA trilink conn...
Page 319 - Non-UltraSCSI Devices 9–27
Figure 9–13: Externally Terminated Shared SCSI Bus with HSZ50 RAIDArray Controllers at Bus End KZPSA-BB (ID 7) Network MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 2 1 1 2 T T 3 4 3 3 4 HSZ50 Controller A Controller B HSZ50 ZK-1597U-AI Table 9–3 ...
Page 320 - Cabling an HSZ20 in a Cluster Using External Termination; Remove the five differential terminator resistor SIPs.; Cabling an HSZ40 or HSZ50 RAID Array Controller in a Radial
9.4.3.2 Cabling an HSZ20 in a Cluster Using External Termination To connect a SWXRA-Z1 (HSZ20 controller) to a shared SCSI bus, followthese steps: 1. Referring to the RAID Array 310 Deskside Subsystem (SWXRA-ZX)Hardware User ’s Guide, open the SWXRA-Z1 cabinet, locate the SCSIbus converter board, an...
Page 321 - Non-UltraSCSI Devices 9–29
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 to the other controller. 3. Install a BN21K or BN21L cable between the H885-AA trilinkconnectors on the two controllers. The BN21L-0B is a 0.15-meter c...
Page 323 - Non-UltraSCSI Devices 9–31
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: TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, aDS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller KZPSA-BB (ID 5) Network Memory...
Page 325 - file; TruCluster Server Hardware Installation Using PCI; to Non-UltraSCSI Devices 10–1
10 Configuring Systems for External Termination or Radial Connections to Non-UltraSCSI Devices This chapter describes how to prepare the systems for a TruCluster Servercluster when there is a need for external termination or radial connection tonon-UltraSCSI RAID array controllers (HSZ40 and HSZ50)....
Page 326 - Termination
Follow the steps in Table 10–1 to start the TruCluster Server hardwareinstallation procedure. You can save time by installing the Memory Channeladapters, redundant network adapters (if applicable), and KZPSA-BB orKZPBA-CB SCSI adapters all at the same time. Follow the directions in the referenced do...
Page 327 - to Non-UltraSCSI Devices 10–3
The DWZZH-series UltraSCSI hubs are designed to allow more separationbetween member systems and shared storage. Using the UltraSCSI hub alsoimproves the reliability of the detection of cable faults. A side benefit is the ability to connect the member systems’ SCSI adapterdirectly to a hub port witho...
Page 328 - new; Step
_____________________ Note _____________________ You may have problems if the member system supports the bus_probe_algorithm console variable and it is not set to new . See Section 2.3.2. The KZPBA-CB UltraSCSI host adapter: • Is a high-performance PCI option connecting the PCI-based host systemto t...
Page 329 - to Non-UltraSCSI Devices 10–5
Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connectionto a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: 2 Power down the system. Install a KZPSA-BBPCI-to-SCSI adapter or KZPBA-CB UltraSCSI hostadapter in the PCI slot corresponding to the logicalbus to be used for the shared SCSI ...
Page 331 - to Non-UltraSCSI Devices 10–7
Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with ExternalTermination Step Action Refer to: 1 Remove the KZPSA-BB internal terminationresistors, Z1, Z2, Z3, Z4, and Z5. Section 10.1.4.4,Figure 10–1, and KZPSAPCI-to-SCSI StorageAdapter Installationand User ’s Guide Remove the eight KZPBA-CB ...
Page 333 - Compaq ESL9326D Enterprise Library; These tape libraries must be on the end of the shared SCSI bus.; Console Commands; Example 10–1: Displaying Configuration on an AlphaServer 4100
Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with ExternalTermination (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 DLT MiniLibraries Section 8.12 Compaq ESL9326D Enterprise Library Section 8.13 ___...
Page 334 - Example 10–2: Displaying Devices on an AlphaServer 4100
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 Bus 0 iod0 (PCI0) Slot Option Name Type Rev Name 1 PCEB 4828086 0005 pceb0 2 S3 Trio64/Trio32 88115333 00...
Page 335 - Example 10–3: Displaying Configuration on an AlphaServer 8200; to Non-UltraSCSI Devices 10–11
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.0.5.1 dke TPwr 1 Fast 1 Bus ID 7 L01 A11 dke100.1.0.5...
Page 336 - Example 10–4: Displaying Devices on an AlphaServer 8200
Example 10–4: Displaying Devices 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...polling for units kzpaa0...
Page 337 - Displaying Console Environment Variables and Setting the; Variables; diff; to Non-UltraSCSI Devices 10–13
10.1.4 Displaying Console Environment Variables 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. Use these ...
Page 339 - to Non-UltraSCSI Devices 10–15
Example 10–6: Displaying Console Variables for a KZPBA-CB on anAlphaServer 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 isp2_soft_term on isp3_host_id 7 isp3_soft_term on isp5_host_id 7 isp5_soft_term diff Both Example 10–3 an...
Page 340 - on; Example 10–8: Setting the KZPBA-CB SCSI Bus ID
Example 10–7: Displaying Console Variables for a KZPSA-BB on anAlphaServer 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-CBson the shared SCSI bus, use the set console command t...
Page 341 - set pk; set pk; Example 10–9: Setting KZPSA-BB SCSI Bus ID and Speed; to Non-UltraSCSI Devices 10–17
10.1.4.3 Setting KZPSA-BB SCSI Bus ID, Bus Speed, and Termination Power If the KZPSA-BB SCSI ID is not correct, or if it was reset to 7 by thefirmware update utility, or you need to change the KZPSA-BB speed, orenable termination power, use the set console command. ______________________ Note ______...
Page 342 - Figure 10–1: KZPSA-BB Termination Resistors; update
10.1.4.4 KZPSA-BB and KZPBA-CB Termination Resistors The KZPSA-BB internal termination is disabled by removing terminationresistors Z1 through Z5, as shown in Figure 10–1. Figure 10–1: KZPSA-BB Termination Resistors Z1 − Z5 TerminationResistor SIPs The KZPBA-CB internal termination is disabled by re...
Page 343 - update pkb0; verify; to Non-UltraSCSI Devices 10–19
The boot sequence provides firmware update overview information. UseReturn to scroll the text, or press Ctrl/C to skip the text. After the overview information has been displayed, the name of the defaultboot file is provided. If it is the correct boot file, press Return at the Bootfile: prompt. Othe...
Page 345 - Table; Table A–1: Converting Storageset Unit Numbers to Disk Names; WWID; Worldwide ID-to-Disk Name Conversion Table A–1
A Worldwide ID-to-Disk Name Conversion Table Table A–1: Converting Storageset Unit Numbers to Disk Names File Systemor Disk HSG80Unit WWID UDID Device Name dsk n Tru64 UNIXdisk Cluster root ( / ) /usr /var Member 1 bootdisk Member 2 bootdisk Member 3 bootdisk Member 4 bootdisk Quorum disk Worldwide ...
Page 347 - Index; Index–1
Index Numbers and SpecialCharacters 20/40 GB DLT Tape Drive , 8–10 cabling , 8–11 capacity , 8–10 cartridges , 8–10 connectors , 8–10 setting SCSI ID , 8–10 40/80-GB DLT Drive , 8–14 cabling , 8–15 capacity , 8–14 cartridges , 8–14 connectors , 8–14 setting SCSI ID , 8–14 A ACS V8.5 , 2–5 arbitrated...
Page 348 - Index–2
BN39B-04 , 5–7, 5–9 BN39B-10 , 2–3, 5–7, 5–9 ESL9326D , 8–77 supported , 2–12 cabling 20/40 GB DLT Tape Drive , 8–11 40/80-GB DLT Drive , 8–15 Compaq 20/40 GB DLT Tape Drive , 8–11 Compaq 40/80-GB DLT Drive , 8–15 DS-TZ89N-TA , 8–9 DS-TZ89N-VW , 8–8 ESL9326D , 8–74, 8–75, 8–77 TL881/891 DLT MiniLibr...
Page 349 - Index–3
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–9 terminal server , 7–9 console variable bus_probe_algorithm , 2–9 CSB , 7–4 nodes , 7–5 purpose , 7–4 D data path ...
Page 350 - Index–4
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 installed in , 3–10, 3–11 internal termination , 3–8, 3–9 radial disconnect , 2–12 SBB , 3–10 SCSI ID , 3–10 termpwr , 3–9 transfer r...
Page 351 - Index–5
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 point-to-point , 6–6 restrictions , 2–5 supported configurations , 6–9 switch installation , 6–16 terminology , 6–5 topology , 6–6, 6–64 F...
Page 352 - Index–6
( 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 HSG80 controller , 1–13 ACS , 2–5 changing failover modes , 6–59 configuring , 2–8, 6–28 multiple-bus failover , 6–30 obta...
Page 353 - Index–7
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 , 10–3 restrictions , 2–8 setting bus speed , 10–17 setting SCSI ID , 10–17 setting termination power , 10–17 termination resistors , 10–4t, 10–...
Page 354 - Index–8
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 NSPOF , 3–18 setting , 6–30, 6–59 N N_Port , 6–5 NL_Port , 6–5 node name , 6–33 non-Ultra BA356 storage shelf preparing , 9–...
Page 355 - Index–9
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 adapters , 2–8 Memory Channel interconnects , 2–3 SCSI bus adapters , 2–5 rolling upgrade MC1 to MC2 , 5–14 S SAVE_CONFIGURATION co...
Page 359 - How to Order Tru64 UNIX Documentation; Name
How to Order Tru64 UNIX Documentation To order Tru64 UNIX documentation in the United States and Canada, call800-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 followingWeb site: http://asmorder.nqo.dec.com/ ...
Page 362 - UBPG PUBLICATIONS MANAGER; Do Not Cut or Tear - Fold Here; FIRST CLASS MAIL PERMIT NO. 33 MAYNARD MA; COMPAQ COMPUTER CORPORATION; Cut on This Line
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. 33 MAYNARD MA POSTAGE WILL BE PAID BY ADDRESSEE Z K O 3 - 3 / Y 3 2110 SPIT BROOK RD COMPAQ COMPUTER CORPORATION NASHUA NH ...