Page 1: Trucluster Server
TruCluster Server Version 5.0A Operating System and Version: Tru64 UNIX Version 5.0A This manual describes how to configure the hardware for a TruCluster Server environment. TruCluster Server Version 5.0A runs on the Tru64™ ® UNIX operating system. Compaq Computer Corporation Houston, Texas...
Page 2 © 2000 Compaq Computer Corporation COMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Office. TruCluster and Tru64 are trademarks of Compaq Information Technologies Group, L.P. Microsoft and Windows are trademarks of Microsoft Corporation. UNIX and The Open Group are trademarks of The Open Group.
Page 3: Table Of Contents
Contents About This Manual 1 Introduction The TruCluster Server Product ........1–1 Overview of the TruCluster Server Hardware Configuration . . 1–2 Memory Requirements .
Page 4 RAID Array Controller Restrictions ....... 2–7 SCSI Signal Converters ..........2–8 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs .
Page 5 TruCluster Server Hardware Installation ......4–5 4.3.1 Installation of a KZPBA-CB Using Internal Termination for a Radial Configuration ........4–7 4.3.2 Displaying KZPBA-CB Adapters with the show Console...
Page 6 6.2.2.2 Fabric ............6–6 6.2.2.3 Arbitrated Loop Topology .
Page 7 Cabling the DS-TZ89N-TA Tape Drives ..... . 8–8 Compaq 20/40 GB DLT Tape Drive ....... . 8–9 8.3.1...
Page 8 8.7.2.1 Cabling the DLT MiniLibraries ......8–24 8.7.2.2 Configuring a Base Module as a Slave ....8–26 8.7.2.3 Powering Up the DLT MiniLibrary .
Page 9 TL891 DLT MiniLibrary ....... 8–63 8.12 Compaq ESL9326D Enterprise Library ......8–64 8.12.1 General Overview ..
Page 10 9.4.1 Preparing BA350, BA356, and UltraSCSI BA356 Storage Shelves for an Externally Terminated TruCluster Server Configuration ............ . 9–15 9.4.1.1 Preparing a BA350 Storage Shelf for Shared SCSI...
Page 11 10.1.4.5 Updating the KZPSA-BB Adapter Firmware ... 10–18 A Worldwide ID to Disk Name Conversion Table Index Examples 4–1 Displaying Configuration on an AlphaServer DS20 .... . 4–10 4–2 Displaying Devices on an AlphaServer DS20 .
Page 12 DS-TZ89N-VW SCSI ID Switches ........8–6 8–4 Compaq 20/40 GB DLT Tape Drive Rear Panel ....8–10 8–5 Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT Tape Drive ..
Page 13 8–6 Cabling a Shared SCSI Bus with a TZ885 ......8–15 8–7 TZ887 DLT MiniLibrary Rear Panel ....... 8–16 8–8 Cabling a Shared SCSI Bus with a TZ887 .
Page 14 2–4 Supported SCSI Terminators and Trilink Connectors ..2–11 3–1 SCSI Bus Speeds ............3–5 3–2 SCSI Bus Segment Length .
Page 15 9–4 Hardware Components Used in Configuration Shown in Figure 9–14 ............9–30 10–1 Configuring TruCluster Server Hardware for Use with a PCI...
Page 17: About This Manual
About This Manual This manual describes how to set up and maintain the hardware configuration for a TruCluster Server cluster. Audience This manual is for system administrators who will set up and configure the hardware before installing the TruCluster Server software. The manual assumes that you are familiar with the tools and methods needed to maintain your hardware, operating system, and network.
Page 18: Related Documents
HS Family of Array Controllers User’s Guide • RAID Array 310 Configuration and Maintenance Guide User’s Guide • Configuring Your StorageWorks Subsystem HSZ40 Array Controllers HSOF Version 3.0 • Getting Started RAID Array 450 V5.4 for Compaq Tru64 UNIX Installation Guide xviii About This Manual...
Page 19 HSZ80 Array Controller ACS Version 8.2 • Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 Configuration Guide • Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide • Wwidmgr User’s Manual For information about the tape devices, see the following documentation: •...
Page 20 Advanced File System (AdvFS) Utilities • Performance Manager Reader’s Comments Compaq welcomes any comments and suggestions you have on this and other Tru64 UNIX manuals. You can send your comments in the following ways: • Fax: 603-884-0120 Attn: UBPG Publications, ZKO3-3/Y32 •...
Page 21 The Tru64 UNIX Publications group cannot respond to system problems or technical support inquiries. Please address technical questions to your local system vendor or to the appropriate Compaq technical support office. Information provided with the software media explains how to send problem reports to Compaq.
Page 22 cluster Bold text indicates a term that is defined in the glossary. xxii About This Manual...
Page 23: Introduction
1.1 The TruCluster Server Product TruCluster Server, the newest addition to the Compaq Tru64 UNIX TruCluster Software products family, extends single-system management capabilities to clusters. It provides a clusterwide namespace for files and directories, including a single root file system that all cluster members share.
Page 24: Overview Of The Trucluster Server Hardware Configuration
interconnect, you can more easily alter or expand your cluster’s hardware configuration as newer and faster technologies become available. 1.2 Overview of the TruCluster Server Hardware Configuration A TruCluster Server hardware configuration consists of a number of highly specific hardware components: •...
Page 25: Memory Requirements
contains up to eight linecards. The Memory Channel adapter in each system in the cluster is connected to the Memory Channel hub. One or two Memory Channel adapters can be used with TruCluster Server. When dual Memory Channel adapters are installed, if the Memory Channel adapter being used for cluster communication fails, the communication will fail over to the other Memory Channel.
Page 26: Clusterwide Disk(S)
The operating system disk (Tru64 UNIX disk) cannot be used as a clusterwide disk, a member boot disk, or as the quorum disk. Because the Tru64 UNIX operating system will be available on the first cluster member, in an emergency, after shutting down the cluster, you have the option of booting the Tru64 UNIX operating system and attempting to fix the problem.
Page 27: Quorum Disk
A member boot disk cannot contain one of the clusterwide root (/), /usr, and /var file systems. Also, a member boot disk cannot be used as the quorum disk. A member disk can contain more than the three required partitions. You can move the swap partition off the member boot disk. See the TruCluster Server Cluster Administration manual for more information.
Page 28: Two-Node Cluster With Minimum Disk Configuration And No
Figure 1–1 shows a generic two-node cluster with the minimum number of 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 the lack of a quorum disk.
Page 29: Growing A Cluster From Minimum Storage To A Nspof Cluster
Administration manual for a discussion of how and when to use a quorum disk. Figure 1–2: Generic Two-Node Cluster with Minimum Disk Configuration and Quorum Disk Network Member Member Memory Channel System System PCI SCSI PCI SCSI Adapter Adapter Tru64 UNIX Disk Shared SCSI Bus...
Page 30: Unit
• Using a RAID array controller in transparent failover mode allows the use of hardware RAID to mirror the disks. However, without a second SCSI bus, second Memory Channel, and redundant networks, this configuration is still not a NSPOF cluster (Section 1.6.4). •...
Page 31 Figure 1–3: Minimum Two-Node Cluster with UltraSCSI BA356 Storage Unit Network Member Member System System Memory Channel Interface Memory Channel Memory Channel Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) UltraSCSI Shared Shared BA356 SCSI SCSI Tru64 UNIX Disk Clusterwide ID 0...
Page 32: Two-Node Clusters Using Ultrascsi Ba356 Storage Units With Increased Disk Configurations
this slot can be used for a second power supply to provide fully redundant power to the storage shelf. Note that with the use of the cluster file system (See the TruCluster Server Cluster Administration manual for a discussion of the cluster file system), the clusterwide root (/), /usr, and /var file systems could be physically placed on a private bus of either of the member systems.
Page 33 multiple BA356 storage units can be used on the same SCSI bus to allow more devices on the same bus. Figure 1–4 shows the configuration in Figure 1–3 with a second UltraSCSI BA356 storage unit that provides an additional seven disks for highly available applications.
Page 34: Two-Node Configurations With Ultrascsi Ba356 Storage Units And Dual Scsi Buses
1.6.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 the Logical Storage Manager (LSM) to mirror data disks, and the clusterwide /usr and /var file systems across SCSI buses. ______________________ Note _______________________...
Page 35: Using Hardware Raid To Mirror The Clusterwide Root File System And Member System Boot Disks
Figure 1–5: Two-Node Configurations with UltraSCSI BA356 Storage Units and Dual SCSI Buses Network Tru64 UNIX Disk Member Member Memory System System Channel Interface Memory Channel Memory Channel Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) UltraSCSI UltraSCSI...
Page 36: Failover Mode
HSZ70. The array controllers can be configured as a dual redundant pair. If you want the capability to fail over from one controller to another controller, you must install the second controller. Also, you must set the failover mode. Figure 1–6: Cluster Configuration with HSZ70 Controllers in Transparent Failover Mode Network Member...
Page 37: Creating A Nspof Cluster
Note that in the configuration shown in Figure 1–6, there is only one shared SCSI bus. Even by mirroring the clusterwide root and member boot disks, the single shared SCSI bus is a single point of failure. 1.6.5 Creating a NSPOF Cluster To create a no-single-point-of-failure (NSPOF) cluster: •...
Page 38: Nspof Cluster Using Hsz70S In Multiple-Bus Failover Mode
Figure 1–7: NSPOF Cluster using HSZ70s in Multiple-Bus Failover Mode Networks Tru64 UNIX Memory Disk Member System 1 Channel Member System 2 Interfaces Memory Channel (mca1) Memory Channel (mca1) Memory Channel (mca0) Memory Channel (mca0) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7)
Page 39: Overview Of Setting Up The Trucluster Server Hardware Configuration
Figure 1–8: NSPOF Fibre Channel Cluster using HSG80s in Multiple-Bus Failover Mode Member Member System System KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA RA8000/ RA8000/ ESA12000 ESA12000 ZK-1533U-AI 1.7 Overview of Setting up the TruCluster Server Hardware Configuration To set up a TruCluster Server hardware configuration, follow these steps: Plan your hardware configuration.
Page 40 Install signal converters in the StorageWorks enclosures, if applicable (see Chapter 3 and Chapter 9). Connect storage to the shared SCSI buses. Terminate each bus. Use Y cables or trilink connectors where necessary (see Chapter 3 and Chapter 9). For a Fibre Channel configuration, connect the HSG80 controllers to the switches.
Page 41: Hardware Requirements And Restrictions
See the Release Notes Overview supplied with the Alpha Systems Firmware Update CD-ROM. You can also obtain firmware information from the Web at http://www.compaq.com/support/. Select Alpha Systems from the downloadable drivers & utilities menu. Check the release notes for the appropriate system type to determine the firmware version required.
Page 42 There are currently three versions of the Memory Channel product; Memory Channel 1, Memory Channel 1.5, and Memory Channel 2. The Memory Channel 1 and Memory Channel 1.5 products are very similar (the PCI adapter for both versions is the CCMAA module) and are generally referred to as MC1 throughout this manual.
Page 43: Fibre Channel Requirements And Restrictions
• For AlphaServer 2000 systems, the B2111-AA module must be at Revision H or higher. For AlphaServer 2100 systems, the B2110-AA module must be at Revision L or higher. Use the examine console command to determine if these modules are at a supported revision as follows: P00>>>...
Page 44: Alphaserver Systems Supported For Fibre Channel
Supported AlphaServer 800 AlphaServer 1200 AlphaServer 4000, 4000A, or 4100 Compaq AlphaServer DS10 Compaq AlphaServer DS20 and DS20E Compaq AlphaServer ES40 AlphaServer 8200 or 8400 32 (2 per DWLPB for throughput, 4 per DWLPB for connectivity) Compaq AlphaServer GS60, GS60E,...
Page 45 • The Fibre Channel RAID Array 8000 (RA8000) midrange departmental storage subsystem and Fibre Channel Enterprise Storage Array 12000 (ESA12000) house two HSG80 dual-channel controllers. There are provisions for six UltraSCSI channels. • Only disk devices attached to the HSG80 Fibre Channel to Six Channel UltraSCSI Array controller are supported with the TruCluster Server product.
Page 46: Scsi Bus Adapter Restrictions
2.4 SCSI Bus Adapter Restrictions To connect a member system to a shared SCSI bus, you must install a SCSI bus adapter in an I/O bus slot. The Tru64 UNIX operating system supports a maximum of 64 I/O buses. TruCluster Server supports a total of 32 shared I/O buses using KZPSA-BB host bus adapters, KZPBA-CB UltraSCSI host bus adapters, or KGPSA Fibre Channel host bus adapters.
Page 47: Disk Device Restrictions
– AlphaServer 8200, 8400, GS60, GS60E, GS140: 32 The KZPBA-CB is supported on the DWLPB only; it is not supported on the DWLPA module. – AlphaServer DS10: 2 – AlphaServer DS20/DS20E: 4 – AlphaServer ES40: 5 • A maximum of four HSZ50, HSZ70, or HSZ80 RAID array controllers can be placed on a single KZPBA-CB UltraSCSI bus.
Page 48: Scsi Signal Converters
Table 2–2: RAID Controller SCSI IDs (cont.) RAID Controller Number of SCSI IDs Supported HSZ80 HSG80 2.7 SCSI Signal Converters If you are using a standalone storage shelf with a single-ended SCSI interface in your cluster configuration, you must connect it to a SCSI signal converter.
Page 49: Ds-Dwzzh-03 And Ds-Dwzzh-05 Ultrascsi Hubs
2.8 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs The DS-DWZZH-03 and DS-DWZZH-05 series UltraSCSI hubs are the only hubs supported in a TruCluster Server configuration. They are SCSI-2- and draft SCSI-3-compliant SCSI 16-bit signal converters capable of data transfer rates of up to 40 MB/sec. These hubs can be listed with the other SCSI bus signal converters, but as they are used differently in cluster configurations they will be discussed differently in this manual.
Page 50: Supported Scsi Cables
SCSI bus length. Table 2–3 describes each supported cable and the context in which you would use the cable. Note that there are cables with the Compaq 6-3 part number that are not listed, but are equivalent to the cables listed.
Page 51: Scsi Terminators And Trilink Connectors
H8574-A or 50-pin Terminates a TZ885 or TZ887 tape drive. H8860-AA 341102-001 High 50-pin Terminates a Compaq 20/40 GB DLT Tape Drive H879-AA High 68-pin Terminates an H885-AA trilink connector or BN21W-0B Y cable. H8861-AA VHDCI 68-pin...
Page 53: Shared Scsi Bus Requirements And Configurations Using Ultrascsi Hardware
Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware A TruCluster Server cluster uses shared SCSI buses, external storage shelves or RAID controllers, and supports disk mirroring and fast file system recovery to provide high data availability and reliability. This chapter: •...
Page 54: Shared Scsi Bus Configuration Requirements
termination and covers radial configurations with the DWZZH UltraSCSI hubs and non-UltraSCSI RAID array controllers. 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) •...
Page 55: Scsi Bus Performance
• All supported UltraSCSI host adapters support UltraSCSI disks at UltraSCSI speeds in UltraSCSI BA356 shelves, RA7000 or ESA10000 storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storage arrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves are supported with UltraSCSI host adapters and host RAID controllers as long as they contain no UltraSCSI disks.
Page 56: Scsi Bus Versus Scsi Bus Segments
3.2.1 SCSI Bus Versus SCSI Bus Segments An UltraSCSI bus may be comprised of multiple UltraSCSI bus segments. Each UltraSCSI bus segment is comprised of electrical conductors that may be in a cable or a backplane, and cable or backplane connectors. Each UltraSCSI bus segment must have a terminator at each end of the bus segment.
Page 57: Data Path
connect devices that use different transmission methods, use a SCSI signal converter between the devices. The DS-BA35X-DA personality module is discussed in Section 9.1.2.2. See Section 9.1 for information about using the DWZZ* series of SCSI signal converters. You cannot use a DWZZA or DWZZB signal converter at UltraSCSI speeds for TruCluster Server if there are any UltraSCSI disks on the bus, because the DWZZA or DWZZB will not operate correctly at UltraSCSI speed.
Page 58: Scsi Bus Length
SCSI bus adapters have a default SCSI ID that you can change by using console commands or utilities. For example, a KZPSA adapter has an initial SCSI ID of 7. ______________________ Note _______________________ If you are using a DS-DWZZH-05 UltraSCSI hub with fair arbitration enabled, SCSI ID numbering will change (see Section 3.6.1.2).
Page 59: Terminating The Shared Scsi Bus When Using Ultrascsi Hubs
Table 3–2: SCSI Bus Segment Length SCSI Bus Bus Speed Maximum Cable Length 6 meters Narrow, single-ended 5 MB/sec Narrow, single-ended fast 10 MB/sec 3 meters 25 meters Wide differential, fast 20 MB/sec 25 meters Differential UltraSCSI 40 MB/sec a The maximum separation between a host and the storage in a TruCluster Server configuration is 50 meters: 25 meters between any host and the UltraSCSI hub and 25 meters between the UltraSCSI hub and the RAID array controller.
Page 60: Ultrascsi Hubs
Most devices have internal termination. For example, the UltraSCSI KZPBA-CB and the fast and wide KZPSA-BB host bus adapters have internal termination. When using a KZPBA-CB or KZPSA-BB with an UltraSCSI hub, ensure that the onboard termination resistor SIPs have not been removed.
Page 61: Using A Dwzzh Ultrascsi Hub In A Cluster Configuration
3.6.1 Using a DWZZH UltraSCSI Hub in a Cluster Configuration The DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI hubs are supported in a TruCluster Server cluster. They both provide radial connection of cluster member systems and storage, and are similar in the following ways: •...
Page 62: Ds-Dwzzh-05 Description
• DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI hubs may be housed in the same storage shelf with disk drives. Table 3–3 provides the supported configurations. Figure 3–2 shows a front view of the DS-DWZZH-03 UltraSCSI hub. Figure 3–2: DS-DWZZH-03 Front View Differential symbol ZK-1412U-AI The differential symbol (and the lack of a single-ended symbol) indicates that all three connectors are differential.
Page 63: Ds-Dwzzh Ultrascsi Hub Maximum Configurations
_____________________ Note _____________________ Dual power supplies are recommended for any BA356 shelf containing a DS-DWZZH-05 UltraSCSI hub in order to provide a higher level of availability between cluster member systems and storage. • The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems.
Page 64: Ds-Dwzzh-05 Fair Arbitration
Table 3–3: DS-DWZZH UltraSCSI Hub Maximum Configurations (cont.) Disk Drives Personality DS-DWZZH-03 DS-DWZZH-05 Module Installed Installed a DS-DWZZH UltraSCSI hubs and disk drives may coexist in a storage shelf. Installed disk drives are not associated with the DS-DWZZH UltraSCSI hub SCSI bus segments; they are on the SCSI bus connected to the personality module.
Page 65: Ds-Dwzzh-05 Address Configurations
______________________ Note _______________________ Host port SCSI ID assignments are not linked to the physical port when fair arbitration is disabled. The DS-DWZZH-05 reserves SCSI ID 7 regardless of whether fair arbitration is enabled or not. 3.6.1.2.3 DS-DWZZH-05 Address Configurations The DS-DWZZH-05 has two addressing modes: wide addressing mode and narrow addressing mode.
Page 66: Ds-Dwzzh-05 Rear View
Figure 3–3: DS-DWZZH-05 Rear View ZK-1448U-AI 3–14 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware...
Page 67: Scsi Bus Termination Power
Figure 3–4: DS-DWZZH-05 Front View Fair Disable Controller Host Port Port SCSI ID SCSI ID 6 - 4 (6 - 0) (14) Power Host Port SCSI ID Busy (15) Host Port Host Port SCSI ID SCSI ID (12) (13) ZK-1447U-AI 3.6.1.2.4 SCSI Bus Termination Power Each host adapter connected to a DS-DWZZH-05 UltraSCSI hub port must supply termination power (termpwr) to enable the termination resistors...
Page 68: Preparing The Ultrascsi Storage Configuration
If fair arbitration is to be used, ensure that the switch on the front of the DS-DWZZH-05 UltraSCSI hub is in the Fair position. Install the DS-DWZZH-05 UltraSCSI hub in a UltraSCSI BA356, non-UltraSCSI BA356 (if it has the required 180-watt power supply), or BA370 storage shelf.
Page 69: Configuring Radially Connected Trucluster Server Clusters With Ultrascsi Hardware
3.7.1 Configuring Radially Connected TruCluster Server Clusters with UltraSCSI Hardware Radial configurations with RAID array controllers allow you to take advantage of the benefits of hardware mirroring, and to achieve a no-single-point-of-failure (NSPOF) cluster. Typical RAID array storage subsystems used in TruCluster Server cluster configurations are: •...
Page 70: Preparing An Hsz70 Or Hsz80 For A Shared Scsi Bus Using Transparent Failover Mode
or SCSI bus failure, the host can redistribute the load to the surviving controller. In case of a controller failure, the surviving controller will handle all units. ______________________ Notes ______________________ Multiple-bus failover does not support device partitioning with the HSZ70 or HSZ80. Partioned storagesets and partitioned single-disk units cannot function in multiple-bus failover dual-redundant configurations.
Page 71 Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H8861-AA VHDCI trilink connector to: • HSZ70 controller A and controller B • HSZ80 Port 1 (2) of controller A and Port 1 (2) of controller B ___________________ Note ___________________...
Page 72: Shared Scsi Bus With Hsz70 Configured For Transparent
Figure 3–5: Shared SCSI Bus with HSZ70 Configured for Transparent Failover Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03 Controller A Controller B HSZ70 HSZ70 StorageWorks RAID Array 7000 ZK-1599U-AI Table 3–4 shows the components used to create the clusters shown in Figure 3–5, Figure 3–6, Figure 3–7, and Figure 3–8.
Page 73: Figure 3–5 Through Figure 3–8
Table 3–4: Hardware Components Used in Configuration Shown in Figure 3–5 Through Figure 3–8 Description Callout Number BN38C cable BN37A cable H8861-AA VHDCI trilink connector H8863-AA VHDCI terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum combined length of the BN37A cables must not exceed 25 meters.
Page 74: Preparing A Dual-Redundant Hsz70 Or Hsz80 For A Shared Scsi Bus Using Multiple-Bus Failover
3.7.1.2 Preparing a Dual-Redundant HSZ70 or HSZ80 for a Shared SCSI Bus Using Multiple-Bus Failover Multiple-bus failover is a dual-redundant controller configuration in which each host has two paths (two shared SCSI buses) to the array controller subsystem. The host(s) have the capability to move LUNs from one controller (shared SCSI bus) to the other.
Page 75 • 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. Install the DS-DWZZH-03 or DS-DWZZH-05 UltraSCSI hub in a DS-BA356, BA356 (with the required 180-watt power supply), or BA370 storage shelf (see Section 3.6.1.1 or Section 3.6.1.2) If you are using a:...
Page 76: Failover
Figure 3–7: TruCluster Server Configuration with HSZ70 in Multiple-Bus Failover Mode Network Member Member Memory System System Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03 DS-DWZZH-03 Controller A Controller B HSZ70 HSZ70 StorageWorks...
Page 77: Failover Mode
Figure 3–8: TruCluster Server Configuration with HSZ80 in Multiple-Bus Failover Mode Networks Memory Member System 2 Member System 1 Channel Interfaces Memory Channel (mca1) Memory Channel (mca1) Memory Channel (mca0) Memory Channel (mca0) KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03 DS-DWZZH-03...
Page 79: Trucluster Server System Configuration Using Ultrascsi Hardware
TruCluster Server System Configuration Using UltraSCSI Hardware This chapter describes how to prepare systems for a TruCluster Server cluster, using UltraSCSI hardware and the preferred method of radial configuration, including how to connect devices to a shared SCSI bus for the TruCluster Server product.
Page 80: Planning Your Trucluster Server Hardware Configuration
This is especially critical if you will install tape devices on the shared SCSI bus. With the exception of the TZ885, TZ887, TL890, TL891, and TL892, tape devices can only be installed at the end of a shared SCSI bus. These tape devices are the only supported tape devices that can be terminated externally.
Page 81: Planning Your Configuration
• Number of shared SCSI buses and the storage on each shared bus Using shared SCSI buses increases storage availability. You can connect 32 shared SCSI buses to a cluster member. You can use any combination of KZPSA-BB, KZPBA-CB, or KGPSA-BC/CA host bus adapters. In addition, RAID array controllers allow you to increase your storage capacity and protect against disk, controller, host bus adapter, and SCSI bus failures.
Page 82: Obtaining The Firmware Release Notes
You can obtain the firmware release notes from: • The Web at the following URL: http://www.compaq.com/support/ Select Alpha Systems from the downloadable drivers & utilities menu. Then select the appropriate system. • The current Alpha Systems Firmware Update CD-ROM.
Page 83: Trucluster Server Hardware Installation
Copy the appropriate release notes to your system disk. In this example, obtain the firmware release notes for the AlphaServer DS20 from the Version 5.6 Alpha Firmware Update CD-ROM: # cp /mnt/doc/ds20_v56_fw_relnote.txt ds20-rel-notes Unmount the CD-ROM drive: # umount /mnt Print the release notes.
Page 84: Configuring Trucluster Server Hardware
______________________ Note _______________________ The KZPSA-BB can be used in any configuration in place of the KZPBA-CB. The use of the KZPSA-BB is not mentioned in this chapter because it is not UltraSCSI hardware, and it cannot operate at UltraSCSI speeds. The use of the KZPSA-BB (and the KZPBA-CB) with external termination is covered in Chapter 10.
Page 85: Installation Of A Kzpba-Cb Using Internal Termination For A Radial Configuration
Table 4–2: Configuring TruCluster Server Hardware (cont.) Step Action Refer to: Update the system SRM console Use the firmware update release firmware from the latest Alpha Systems notes (Section 4.2) Firmware Update CD-ROM. ______________________ Note _____________________ The SRM console firmware includes the ISP1020/1040-based PCI option firmware, which includes the KZPBA-CB.
Page 86 The DWZZH contains a differential to single-ended signal converter for each hub port (sometimes referred to as a DWZZA on a chip, or DOC chip). The single-ended sides are connected together to form an internal single-ended SCSI bus segment. Each differential SCSI bus port is terminated internal to the DWZZH with terminators that cannot be disabled or removed.
Page 87: Ultrascsi Hub
Your storage shelves or RAID array subsystems should be set up before completing this portion of an installation. Use the steps in Table 4–3 to set up a KZPBA-CB for a TruCluster Server cluster that uses radial connection to a DWZZH UltraSCSI hub. Table 4–3: Installing the KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub Step Action...
Page 88: Displaying Kzpba-Cb Adapters With The Show Console Commands
Table 4–3: Installing the KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: _____________________ Notes _____________________ Ensure that the SCSI ID that you use is distinct from all other SCSI IDs on the same shared SCSI bus. If you do not remember the other SCSI IDs, or do not have them recorded, you must determine these SCSI IDs.
Page 89 Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.) Core Logic Cchip DECchip 21272-CA Rev 2.1 Dchip DECchip 21272-DA Rev 2.0 Pchip 0 DECchip 21272-EA Rev 2.2 Pchip 1 DECchip 21272-EA Rev 2.2 Rev 4.14 Arbiter Rev 2.10 (0x1) MEMORY Array # Size Base Addr...
Page 90 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 91 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 Mnemonic TLSB KN7CC-AB 8014 0000 kn7cc-ab0 MS7CC 5000 0000 ms7cc0 KFTIA 2020 0000...
Page 92: The Kzpba-Cb Scsi Id
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... kzpsa0.4.0.2.1 TPwr 1 Fast 1 Bus ID 7 L01 A11...
Page 93: Displaying Kzpba-Cb Pk* Or Isp* Console Environment Variables
4.3.3.1 Displaying KZPBA-CB pk* or isp* Console Environment Variables To determine the console environment variables to use, execute the show pk* and show isp* console commands. Example 4–5 shows the pk console environment variables for an AlphaServer DS20. Example 4–5: Displaying the pk* Console Environment Variables on an AlphaServer DS20 System P00>>>show pk* pka0_disconnect...
Page 94: Alphaserver 8X00 System
• on — Turns on both low 8 bits and high 8 bits • diff — Places the bus in differential mode The KZPBA-CB is a Qlogic ISP1040 module, and its termination is determined by the presence or absence of internal termination resistor SIPs RM1-RM8.
Page 95: Setting The Kzpba-Cb Scsi Id
4.3.3.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBs on the shared SCSI bus, use the set console command to set the SCSI ID. For a TruCluster Server cluster, you will most likely have to set the SCSI ID for all KZPBA-CB UltraSCSI adapters except one.
Page 96: Kzpba-Cb Termination Resistors
Figure 4–1: KZPBA-CB Termination Resistors Internal Narrow Device Internal Wide Device Connector P2 Connector J2 SCSI Bus Termination Resistors RM1-RM8 ZK-1451U-AI 4–18 TruCluster Server System Configuration Using UltraSCSI Hardware...
Page 97: Setting Up The Memory Channel Cluster Interconnect
Setting Up the Memory Channel Cluster Interconnect This chapter describes Memory Channel configuration restrictions, and describes how to set up the Memory Channel cluster interconnect, including setting up a Memory Channel hub, Memory Channel optical converter (MC2 only), and connecting link cables. Two versions of the Memory Channel PCI adapter are available;...
Page 98: Setting The Memory Channel Adapter Jumpers
____________________ Note _____________________ If you are installing SCSI or network adapters, you may wish to complete all hardware installation before powering up the systems to run Memory Channel diagnostics. 5.1 Setting the Memory Channel Adapter Jumpers The meaning of the Memory Channel adapter module jumpers depends upon the version of the Memory Channel module.
Page 99: Mc2 Jumpers
If you are upgrading from virtual hub mode to standard hub mode (or from standard hub mode to virtual hub mode), be sure to change the jumpers on all Memory Channel adapters on the rail. 5.1.2 MC2 Jumpers The MC2 module (CCMAB) has multiple jumpers. They are numbered right to left, starting with J1 in the upper righthand corner (as you view the jumper side of the module with the endplate in your left hand).
Page 100 Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: VH0: Pins 2 to 3 1 2 3 VH1: None needed; store the jumper on pin 1 or pin 3 1 2 3 J3: Window Size 512 MB: Pins 2 to 3 1 2 3 128 MB: Pins 1 to 2 1 2 3...
Page 101: Installing The Memory Channel Adapter
Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: J10 and J11: Fiber Fiber Off: Pins 1 to 2 Optics Mode Enable Fiber On: Pins 2 to 3 pins a Increases the maximum sustainable bandwidth for 8x00 systems. If the jumpers are in this position for other systems, the bandwidth is decreased.
Page 102: Installing The Mc2 Optical Converter In The Member System
If you are setting up a redundant Memory Channel configuration, install the second Memory Channel adapter right after installing the first Memory Channel adapter. Ensure that the jumpers are correct and are the same on both modules. After you install the Memory Channel adapter(s), replace the system panels unless you have more hardware to install.
Page 103: Installing The Memory Channel Cables
For use with the MC2 CCMAB adapter, the hub must be placed within 4 or 10 meters (the length of the BN39B link cables) of each system. If fiber optics is used in conjunction with the MC2 adapter, the hub may be placed up to 31 meters from the systems.
Page 104: Connecting Mc1 Or Mc1.5 Link Cables In Virtual Hub Mode
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 the BC12N-10 link cables between the Memory Channel adapters installed in each of the systems. _____________________ Caution _____________________ Be very careful when installing the link cables.
Page 105: Installing The Mc2 Cables
Figure 5–1: Connecting Memory Channel Adapters to Hubs Memory Channel hub 1 System A Memory Channel Linecards hub 2 Memory Channel adapters ZK-1197U-AI 5.5.2 Installing the MC2 Cables To set up an MC2 interconnect, use the BN39B-04 (4-meter) or BN39B-10 (10-meter) link cables for virtual hub or standard hub configurations without optical converters.
Page 106: Connecting Mc2 Link Cables In Standard Hub Mode (No Fiber Optics)
Gently push the cable’s connector into the receptacle, and then use the screws to pull the connector in tight. The connector must be tight to ensure a good ground contact. If you are setting up redundant interconnects, all Memory Channel adapters in a system must have the same jumper setting, either VH0 or VH1.
Page 107: Running Memory Channel Diagnostics
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 _______________________...
Page 108 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 the diagnostic. – Runs as part of the initialization sequence when the system is powered up. –...
Page 109: Running The Mc_Cable Test
Example 5–1: Running the mc_cable Test >>> mc_cable To exit MC_CABLE, type <Ctrl/C> mca0 node id 1 is online No response from node 0 on mca0 mcb0 node id 1 is online No response from node 0 on mcb0 Response from node 0 on mca0 Response from node 0 on mcb0 mcb0 is offline mca0 is offline...
Page 111: Using Fibre Channel Storage
Using Fibre Channel Storage This chapter provides an overview of Fibre Channel, Fibre Channel configuration examples, and information on Fibre Channel hardware installation and configuration in a Tru64 UNIX or TruCluster Server Version 5.0A configuration. The information includes how to determine the /dev/disk/dskn value that corresponds to the Fibre Channel storagesets that have been set up as the Tru64 UNIX boot disk, cluster root (/), cluster /usr, cluster /var, cluster member boot, and quorum disks, and how to set up the bootdef_dev...
Page 112: Procedure For Installation Using Fibre Channel Disks
• A discussion on how you can use the emx manager (emxmgr) to display the presence of Fibre Channel adapters, target ID mappings for a Fibre Channel adapter, and the current Fibre Channel topology (Section 6.12). 6.1 Procedure for Installation Using Fibre Channel Disks Use the following procedure to install Tru64 UNIX Version 5.0A or TruCluster Server Version 5.0A using Fibre Channel disks.
Page 113 KGPSA-BC PCI-to-Optical Fibre Channel Host Adapter User Guide (AA-RF2JB-TE) • Compaq StorageWorks Fibre Channel Storage Switch User’s Guide (AA-RHBYA-TE) • Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide (EK-BCP24-IA/161355-001) • Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide (EK-BCP28-IA/161356-001) •...
Page 114: Fibre Channel Overview
• Wwidmgr User’s Manual 6.2 Fibre Channel Overview Fibre Channel supports multiple protocols over the same physical interface. Fibre Channel is primarily a protocol-independent transport medium; therefore, it is independent of the function that it is used for. The TruCluster Server uses the Fibre Channel Protocol (FCP) for SCSI to use Fibre Channel as the physical interface.
Page 115: Fibre Channel Topologies
is manufactured. An N_Port is connected directly to another N_Port in a point-to-point topology. An N_Port is connected to an F_Port in a fabric topology. NL_Port In an arbitrated loop topology, information is routed around a loop. The information is repeated by each intermediate port until it reaches its destination.
Page 116: Point-To-Point
• Arbitrated loop (Section 6.2.2.3) ______________________ Note _______________________ Although it is possible to interconnect an arbitrated loop with fabric, hybrid configurations are not supported at the present time, and therefore not discussed in this manual. 6.2.2.1 Point-to-Point The point-to-point topology is the simplest Fibre Channel topology. In a point-to-point topology, one N_Port is connected to another N_Port by a single link.
Page 117: Arbitrated Loop Topology
connected by the fabric switching function, which routes the frame from one F_Port to another F_Port within the switch. Communication between two switches is routed between two expansion ports (E_Ports). When an N_Port is connected to an F_Port, the fabric is responsible for the assignment of the Fibre Channel address to the N_Port attached to the fabric.
Page 118: Trucluster Server
Figure 6–3: Arbitrated Loop Topology Node 3 Node 1 Transmit Receive NL_Port NL_Port Receive Transmit Node 4 Node 2 Transmit Receive NL_Port NL_Port Receive Transmit ZK-1535U-AI ______________________ Note _______________________ The arbitrated loop topology is not supported by the Tru64 UNIX or TruCluster Server products.
Page 119: Fibre Channel Single Switch Transparent Failover
• The units are divided between an HSG80 port 1 and port 2. • If there are dual-redundant HSG80 controllers, controller A port 1 and controller B port 2 are normally active; controller A port 1 and controller B port 1 are normally passive. •...
Page 120: Fibre Channel Cluster Configurations For Multiple-Bus
You can, however, add the hardware for a second bus (another KGPSA, switch, and RA8000/ESA12000 with associated cabling) and use LSM to mirror across the buses. However, because you cannot use LSM to mirror the cluster root (/) file system, member boot partitions, the quorum disk, or swap partitions you cannot obtain an NSPOF transparent failover configuration, even though you have increased availability.
Page 121: Multiple-Bus Nspof Configuration Number 1
If you consider the loss of a host bus adapter or switch, the configurations in Figure 6–6 and Figure 6–7 will provide better throughput than Figure 6–5 because you still have access to both controllers. With Figure 6–5, if you lose a host bus adapter or switch, you lose the use of a controller.
Page 122: Multiple-Bus Nspof Configuration Number 2
Figure 6–6: Multiple-Bus NSPOF Configuration Number 2 Member Member System System KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA RA8000/ ESA12000 ZK-1707U-AI 6–12 Using Fibre Channel Storage...
Page 123: Zoning And Cascaded Switches
Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 Member Member System System KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA RA8000/ ESA12000 ZK-1708U-AI 6.4 Zoning and Cascaded Switches This section provides a brief overview of zoning and cascaded switches. 6.4.1 Zoning A zone is a logical subset of the Fibre Channel devices connected to the fabric.
Page 124: Cascaded Switches
Figure 6–8: A Simple Zoned Configuration Cluster 1 Cluster 2 Cluster 1 Cluster 2 Member Member Member Member System 1 System 1 System 2 System 2 KGPSA KGPSA KGPSA KGPSA DSGGA SWITCH 9 10 11 12 13 14 15 16 RA8000/ RA8000/ ESA12000...
Page 125: Installing And Configuring Fibre Channel Hardware
6.5 Installing and Configuring Fibre Channel Hardware This section provides information about installing the Fibre Channel hardware needed for a TruCluster Server configuration accessing storage over the Fibre Channel. Ensure that the member systems, the Fibre Channel switches, and the HSG80 array controllers are placed within the lengths of the optical cables you will be using.
Page 126: Installing The Switch
you can manage the switch by way of a telnet session, SNMP, or the Web. The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) or eight (DS-DSGGA-AB) plug-in interface modules. Each interface module in turn supports two Giga Bit Interface Converter modules (GBIC). The GBIC module is the electrical-to-optical converter.
Page 127: Managing The Fibre Channel Switches
(EK-BCP24-IA/161355-001) • Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide (EK-BCP28-IA/161356-001) For more information on the DSGGB command set, see the Compaq StorageWorks SAN Switch Fabric Operating System Management Guide (EK-P20FF-GA/161358-001). 6.5.1.2 Managing the Fibre Channel Switches You can manage the DS-DSGGA-AA, DS-DSGGA-AB, and DS-DSGGB-AB switches, and obtain switch status from the front panel, by making a telnet connection or by accessing the Web.
Page 128: From The Front Panel
Down — Downward triangle: Scrolls the menu down (which effectively moves up the list of commands) or decreases the value being displayed. ______________________ Note _______________________ When the up or down buttons are used to increase or decrease a numerical display, the number changes slowly at first, but changes to fast mode if the button is held down.
Page 129 Press Enter to display the first submenu item in the configuration menu, Ethernet IP address: Ethernet IP address: 10.00.00.10 The underline cursor denotes the selected address field. Use the up or down button to increase or decrease the displayed number. Use the Tab/Esc button to select the next field.
Page 130: Setting The Ds-Dsggb-Aa Ethernet Ip Address And Subnet Mask From A Pc Or Terminal
6.5.1.2.3 Setting the DS-DSGGB-AA Ethernet IP Address and Subnet Mask from a PC or Terminal For the DS-DSGGB-AA switch, which does not have a front panel, you must use a connection to a Windows 95/98/NT PC or video terminal to set the Ethernet IP address and subnet mask.
Page 131: Setting The Switch Name Via Telnet Session
Root commands should only be used at the request of Compaq customer service. You can set the user names and passwords for users at or below the security level of the present login level by executing the passwd command. Enter a new user name (if desired) and a new password for the user.
Page 132: Installing And Configuring The Kgpsa Pci-To-Fibre Channel Adapter Module
Return # telnet 132.25.47.146 Return User admin Return Passwd Return :Admin> switchName fcsw1 Return :Admin> switchName fcsw1 :Admin> ______________________ Note _______________________ When you telnet to the switch the next time, the prompt will include the switch name, for example: fcsw1:Admin> 6.5.2 Installing and Configuring the KGPSA PCI-to-Fibre Channel Adapter Module The following sections discuss KGPSA installation and configuration.
Page 133: Setting The Kgpsa-Bc Or Kgpsa-Ca To Run On A Fabric
GLM alignment pins, alignment tabs, and connector pins with the holes, oval openings, and board socket. Press the GLM into place. The KGPSA-CA does not use a GLM, it uses an embedded optical shortwave multimode Fibre Channel interface. Install the KGPSA in an open 32- or 64-bit PCI slot. Insert the optical cable SC connectors into the KGPSA-BC GLM or KGPSA-CA SC connectors.
Page 134 P00>>> boot warning -- main memory zone is not free P00>>> init P00>>> boot If you have initialized and booted the system, then shut down the system and try to use the wwidmgr utility, you may be prevented from doing so. If you receive the following error, initialize the system and retry the wwidmgr command: P00>>>...
Page 135: Obtaining The Worldwide Names Of Kgpsa Adapters
If, however, the current topology is LOOP, you have to change the topology to FABRIC to operate in a fabric. You will never see the Nvram read failed message if the current topology is LOOP. The NVRAM has to have been formatted to change the current mode to LOOP.
Page 136: Setting Up The Hsg80 Array Controller For Tru64 Unix Installation
Tru64 UNIX Version 5.0A and TruCluster Server Version 5.0A. For more information on installing the HSG80, see the Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 Configuration Guide or Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide.
Page 137 ____________________ Note _____________________ Do not use PVA ID 1: With Port-Target-LUN (PTL) addressing, the PVA ID is used to determine the target ID of the devices on ports 1 through 6 (the LUN is always zero). Valid target ID numbers are 0 through 15, excluding numbers 4 through 7.
Page 138 10. From the maintenance terminal, use the show this and show other commands to verify that controllers have the current firmware version. See the Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide for information on upgrading the firmware.
Page 139: Determine Hsg80 Connection Names
Takes the ports off line and resets the topology to prevent an error message when setting the port topology. Sets fabric as the switch topology. 12. Enter the show connection command as shown in Example 6–1 to determine the HSG80 connection names for the connections to the KGPSA host bus adapters.
Page 140 Example 6–1: Determine HSG80 Connection Names (cont.) HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER offline HOST_ID=1000-0000-C921-0943 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER 210413 OL other HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON65 TRU64_UNIX OTHER 210513 OL other HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON74 TRU64_UNIX THIS 210413 OL this HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON75 TRU64_UNIX THIS offline...
Page 141: Obtaining The Worldwide Names Of Hsg80 Controller
your cluster member systems. If the operating system and offsets are incorrect, set them, then restart both controllers as follows: HSG80> set !NEWCON49 unit_offset = 0 HSG80> set !NEWCON49 operating_system = TRU64_UNIX HSG80> restart other HSG80> restart this HSG80> show connection Set the relative offset for LUN numbering to 0.
Page 142 • In a subsystem with two controllers in transparent failover mode, the controller port IDs increment as follows: – Controller A and controller B, port 1 — worldwide name + 1 – Controller A and controller B, port 2 — worldwide name + 2 For example, using the worldwide name of 5000-1FE1-0000-0D60, the following port IDs are automatically assigned and shared between the ports as a REPORTED PORT_ID on each port:...
Page 143: Preparing To Install Tru64 Unix And Trucluster Server On
– If the configuration has been saved to disk (with the INITIALIZE DISKnnnn SAVE_CONFIGURATION or INITIALIZE storageset-name SAVE_CONFIGURATION option), you can restore it from disk with the CONFIGURATION RESTORE command. – If you have not saved the configuration to disk, but the label containing the worldwide name and checksum is still intact, or you have recorded the worldwide name and checksum (Section 6.5.3.1) and other configuration information, you can use the command-line...
Page 144: Setting Up The Mirrorset
• Cluster /var • Member boot disk (one for each cluster member system) • Quorum disk (if used) If you are installing only the operating system, you need only the Tru64 UNIX disk (and of course any disks for applications). This document assumes that both the base operating system and cluster software are to be installed on Fibre Channel disks.
Page 145 Example 6–2: Setting up the Mirrorset (cont.) Config - Normal Termination HSG80> ADD MIRRORSET BOOT-MIR DISK 30200 40000 HSG80> ADD MIRRORSET CROOT-MIR DISK 30300 40100 HSG80> INITIALIZE BOOT-MIR HSG80> INITIALIZE CROOT-MIR HSG80> SHOW BOOT-MIR Name Storageset Uses Used by -------------------------------------------------------------------- BOOT-MIR mirrorset DISK30200...
Page 146 Example 6–2: Setting up the Mirrorset (cont.) HSG80> HSG80> SHOW CROOT-MIR Name Storageset Uses Used by ------------------------------------------------------------------------------ CROOT-MIR mirrorset DISK30300 DISK40100 Switches: POLICY (for replacement) = BEST_PERFORMANCE COPY (priority) = NORMAL READ_SOURCE = LEAST_BUSY MEMBERSHIP = 2, 2 members present State: UNKNOWN -- State only available when configured as a unit Size:...
Page 147 Example 6–2: Setting up the Mirrorset (cont.) HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON53,!NEWCON54,!NEWCON55,!NEWCON56 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit. If you wish to enable ONLY the host(s) specified, disable all access paths (DISABLE_ACCESS=ALL), then again enable the ones specified HSG80>...
Page 148 Use the CONFIG utility to configure the devices on the device side buses and add them to the controller configuration. The CONFIG utility takes about two minutes to complete. You can use the ADD DISK command to add disk drives to the configuration manually. Create the BOOT-MIR mirrorset using disks 30200 and 30300 and the CROOT-MIR mirrorset using disks 40000 and 40100.
Page 149 Partition for cluster /usr filesystem. Partition for cluster /var filesystem. Assign a unit number to each partition. When the unit is created by the ADD UNIT command, disable access to all hosts. This allows selective access in case there are other systems or clusters connected to the same switch as our cluster.
Page 150: Setting The Device Unit Number
that at this point, even though the table is filled in, we do not yet know the device names or dskn numbers. Table 6–2: Converting Storageset Unit Numbers to Disk Names File System HSG80 Worldwide Name User Device Name dskn or Disk Unit Define...
Page 151 disk is unit D133 with a UDID 133. The UDID for the cluster member 1 boot disk is 131, and the cluster member 2 boot disk is 132. Use the wwidmgr -clear all command to clear the stored Fibre Channel wwid1, wwid2, wwid3, wwid4, N1, N2, N3, and N4 console environment variables.
Page 152 [16] UDID:144 WWID:01000010:6000-1fe1-0000-0d60-0009-8080-0434-0028 (ev:none) [17] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002b (ev:none) [18] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002c (ev:none) [19] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002d (ev:none) [20] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002e (ev:none) The number within the brackets ([ ]) is the item number of the device shown on any particular line. The UDID is assigned at the HSG80 with the set Dn IDENTIFIER = xxx command, and is not used by the Tru64 UNIX operating system, but may be set (as we have done with the SET D131 IDENTIFIER=131 group of commands).
Page 153: Number
132 (cluster member 2). The device unit number is an alias for the worldwide name for the storage unit. • The reachability part of the display provides the followng: – The worldwide name for the storage unit that is to be accessed –...
Page 154 Example 6–3: Using the wwidmgr quickset Command to Set Device Unit Number (cont.) dgb131.1004.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d61 P00>>> wwidmgr -quickset -udid 132 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-0000-0d64 dga133.1002.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d62 dga133.1003.0.1.0 pga0.0.0.1.0...
Page 155: Sample Fibre Channel Device Names
The disks are not reachable and you cannot boot until after the system is initialized. Note, that in the reachability portion of the display, the storagesets are reachable from KGPSA dga through two HSG80 ports and from KGPSA dgb through two HSG80 ports. Also note, that the device unit numbers, the alias for the worldwide name of the disk device, has been set for the KGPSA for each HSG80 port.
Page 156: Setting The Bootdef_Dev Console Environment Variable
$1$DGA133 HSG80 V8.5F dgb133.1002.0.2.0 $1$DGA133 HSG80 V8.5F dgb133.1003.0.2.0 $1$DGA133 HSG80 V8.5F dgb133.1004.0.2.0 $1$DGA133 HSG80 V8.5F dka0.0.0.1.1 DKA0 COMPAQ BB00911CA0 3B05 dqa0.0.0.15.0 DQA0 COMPAQ CDR-8435 0013 dva0.0.0.1000.0 DVA0 ewa0.0.0.5.1 EWA0 08-00-2B-C4-61-11 pga0.0.0.1.0 PGA0 WWN 1000-0000-c920-eda0 pgb0.0.0.2.0 PGB0 WWN 1000-0000-c920-da01 pka0.7.0.1.1...
Page 157 • After a cluster member has been added to the cluster with clu_add_member (but before the member system is booted). _____________________ Note _____________________ You do not use this procedure after using clu_create to create the first cluster member. Before booting the first cluster member, you reset the bootdef_dev console environment variable to multiple boot paths.
Page 158: Install The Base Operating System
Set the bootdef_dev console environment variable to one of the boot path(s) that show up as connected. Ensure that you set the bootdef_dev variable appropriately for the system and boot disk. For the example disk configuration, set bootdef_dev as follows: •...
Page 159: Resetting The Bootdef_Dev Console Environment Variable
Device Size Controller Disk Name in GB Type Model Location dsk0 SCSI RZ2CA-LA bus-0-targ-0-lun-0 dsk15 SCSI HSG80 IDENTIFIER=133 dsk16 SCSI HSG80 IDENTIFIER=132 dsk17 SCSI HSG80 IDENTIFIER=131 If you flash the light on a storage unit (logical disk) that is a mirrorset, stripeset, or RAIDset, the lights on all disks in the storageset will blink.
Page 160 For example, to ensure that you have a connected boot path in case of a failed host bus adapter or controller failover, choose device names for multiple host bus adapters and each controller port. For example, if you use the reachability display shown in Example 6–3, you could choose the following device names when setting the bootdef_dev console environment variable:...
Page 161: Determining /Dev/Disk/Dskn To Use For A Cluster Installation
• For member system 2 boot disk: P00>>> set bootdef_dev \ dga132.1001.0.1.0,dga132.1002.0.2.0,\ dgb132.1001.0.1.0,dgb132.1002.0.2.0 POO>>> init ______________________ Note _______________________ The console system reference manual (SRM) software guarantees that you can set the bootdef_dev console environment variable to a minimum of four device names. You may be able to set it to five, but four is all that is guaranteed.
Page 162 The following example shows the format of the command output: # hwmgr -get attribute -a name -a dev_base_name name = Compaq AlphaServer ES40 name = CPU0 name = SCSI-WWID:01000010:6000-1fe1-0000-0d60-0009-8080-0434-002e dev_base_name = dsk15...
Page 163: Installing The Trucluster Server Software
6.10 Installing the TruCluster Server Software This section covers the Fibre Channel specific procedures you need to execute before running clu_create to create the first cluster member or clu_add_member to add subsequent cluster members. It also covers the procedure you need to execute after running clu_create or clu_add_member before you boot the new cluster member into the cluster.
Page 164: Changing The Hsg80 From Transparent To Multiple-Bus
P00>>> wwidmgr -quickset -udid 132 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d60-0009-8080-0434-0030 via adapter: via fc nport: connected: dga132.1001.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d64 dga132.1002.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d62 dga132.1003.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d63 dga132.1004.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d61 dgb132.1001.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d64 dgb132.1002.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d62 dgb132.1003.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d63 dgb132.1004.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d61...
Page 165 Each path between a Fibre Channel host bus adapter in a host computer and an active host port on an HSG80 controller is a connection. During Fibre Channel initialization, when a controller becomes aware of a connection to a host bus adapter through a switch, it adds the connection to its table of known connections.
Page 166 At the HSG80, set multiple-bus failover as follows. Note that before putting the controllers in multiple-bus failover mode, you must remove any previous failover mode: HSG80> SET NOFAILOVER HSG80> SET MULTIBUS_FAILOVER COPY=THIS ____________________ Note _____________________ Use the controller known to have the good configuration information.
Page 167 !NEWCON62 TRU64_UNIX OTHER 210513 OL other HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER offline HOST_ID=1000-0000-C921-0943 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER 210413 OL other HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON65 TRU64_UNIX OTHER 210513 OL other HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C The following connections are shown to have nonzero offsets: !NEWCON49, !NEWCON51, !NEWCON55, !NEWCON56, !NEWCON57, !NEWCON60, !NEWCON61, and !NEWCON65 Set the unit offset to 0 for each connection that has a nonzero unit offset: HSG80>...
Page 168 P00>>> For each wwidn line, record the unit number (131, 132, and 133) and worldwide name for the storage unit. The unit number is the first field in the display (after wwidn). The Nn value is the HSG80 port being used to access the storage units (controller B, port 2). Clear the wwidn and Nn environment variables: P00>>>...
Page 169: Using The Emx Manager To Display Fibre Channel Adapter Information
of the wwidmgr -quickset command for the appropriate device (see Section 6.8). Repeat steps a through h on each system accessing devices on the HSG80. 6.12 Using the emx Manager to Display Fibre Channel Adapter Information The emx manager (emxmgr) utility was written for the TruCluster Software Product Version 1.6 products to be used to modify and maintain emx driver worldwide name to target ID mappings.
Page 170 The previous example shows four Fibre Channel devices on this SCSI bus. The Fibre Channel adapter in question, emx0, at SCSI ID 7, is denoted by the presence of the emx0 designation. Use the emxmgr -t command to display the Fibre Channel topology for the adapter.
Page 171: Using The Emxmgr Utility Interactively
worldwide name) are provided. The Fibre Channel DID number is the physical Fibre Channel address being used by the N_Port. A list of all other Fibre Channel devices on this SCSI bus, with their SCSI ID, port name, node name, physical Fibre Channel address and other items such as: •...
Page 172 • Display the target ID mappings for a Fibre Channel adapter • Display the current Fibre Channel topology for a Fibre Channel adapter You have already seen how you can perform these functions from the command line. The same output is available using the interactive mode by selecting the appropriate option (shown in the following example).
Page 173 View adapter’s Target Id Mappings Change Target ID Mappings Display Attached Adapters Change targeted adapter Exit ----> x Using Fibre Channel Storage 6–63...
Page 175: Preparing Atm Adapters
Preparing ATM Adapters The Compaq Tru64 UNIX operating system supports Asynchronous Transfer Mode (ATM). TruCluster Server supports the use of LAN emulation over ATM for client access. This chapter provides an ATM overview, an example TruCluster Server cluster using ATM, an ATM adapter installation procedure, and information about verifying proper installation of fiber optic cables.
Page 176 Most data traffic in existing customer networks is sent over Local Area Networks (LANs) such as Ethernet or Token Ring networks. The services provided by the LANs differ from those of ATM, for example: • LAN messages are connectionless; ATM is a connection-oriented technology •...
Page 177: Installing Atm Adapters
– Broadcast and Unknown Server (BUS): A BUS handles broadcast data sent by a LAN emulation client, all multicast data, and data sent by a LAN emulation client before the ATM address has been resolved. Figure 7–1 shows an ATM network with two emulated LANs. Hosts A and B are LECs on ELAN1.
Page 178: Verifying Atm Fiber Optic Cable Connectivity
Use the following steps to install an ATMworks adapter. See the ATMworks 350 Adapter Installation and Service guide for more information. Be sure to use the antistatic ground strap. Remove the adapter extender bracket if the ATMworks 350 is to be installed in an AlphaServer 2100 system.
Page 179 ATM Switch Indicator Comments Compaq GIGAswitch Illuminated green LED indicates that the switch is receiving idle cells from the ATM adapter. ®...
Page 180: Atmworks Adapter Leds
If you do not have an indication that confirms a correct cable connection, swap the transmit and receive connectors on one end of the cable and recheck the indicators. If you still do not have a correct cable connection, you probably have a bad cable.
Page 181: Configuring A Shared Scsi Bus For Tape Drive Use
The TL881, with a Compaq 6-3 part number was recently qualified in cluster configurations. The TL891 rackmount base unit has been provided with a Compaq 6-3 part number. The TL881 and TL891 only differ in the type of tape drive they use.
Page 182: Setting The Tz88N-Va Scsi Id
8.1.1 Setting the TZ88N-VA SCSI ID You must set the TZ88N-VA switches before the tape drive is installed into the BA350 StorageWorks enclosure. The Automatic selection is normally used. The TZ88N-VA takes up three backplane slot positions. The physical connection is in the lower of the three slots. For example, if the tape drive is installed in slots 1, 2, and 3 with the switches in Automatic, the SCSI ID is 3.
Page 183: Cabling The Tz88N-Va
Table 8–1: TZ88N-VA Switch Settings SCSI ID SCSI ID Selection Switches Automatic a SBB tape drive SCSI ID is determined by the SBB physical slot. 8.1.2 Cabling the TZ88N-VA There are no special cabling restrictions specific to the TZ88N-VA; it is installed in a BA350 StorageWorks enclosure.
Page 184: Setting The Tz88N-Ta Scsi Id
Figure 8–2: Shared SCSI Buses with SBB Tape Drives KZPSA adapter, trilink connector, BN21K or BN21L cable DWZZA-VA and H879 terminator and trilink BN21K or BN21L cables DWZZA-VA, trilink, and H879 terminator TZ88N-VA Memory Memory Channel link cable Channel adapters BA350 BA350 AlphaServer 2100A...
Page 185: Preparing The Tz89 For Shared Scsi Usage
Ensure that DWZZA jumper J2 or DWZZB jumpers W1 and W2 are installed to enable the single-ended termination. Remove the termination from the differential end by removing the five 14-pin SIP resistors. Attach a trilink connector to the differential end of the DWZZA or DWZZB.
Page 186: Ds-Tz89N-Vw Scsi Id Switches
3, the SCSI ID is 2. If it is installed in slots 3, 4, and 5, the SCSI ID is 4. Figure 8–3 shows a view of the DS-TZ89N-VW showing the backplane interface connector and SCSI ID switch pack. Figure 8–3: DS-TZ89N-VW SCSI ID Switches Backplane Interface Connector...
Page 187: Cabling The Ds-Tz89N-Vw Tape Drives
Table 8–2: DS-TZ89N-VW Switch Settings (cont.) SCSI ID SCSI ID Selection Switches a SBB tape drive SCSI ID is determined by the SBB physical slot. 8.2.2 Cabling the DS-TZ89N-VW Tape Drives No special cabling is involved with the DS-TZ89N-VW as it is installed in a BA356 StorageWorks enclosure.
Page 188: Setting The Ds-Tz89N-Ta Scsi Id
8.2.3 Setting the DS-TZ89N-TA SCSI ID The DS-TZ89N-TA has a push-button counter switch on the rear panel to select the SCSI ID. It is preset at the factory to 15. Push the button above the counter to increment the SCSI ID (the maximum is 15); push the button below the switch to decrease the SCSI ID.
Page 189: Compaq 20/40 Gb Dlt Tape Drive
8.3.1 Setting the Compaq 20/40 GB DLT Tape Drive SCSI ID As with any of the shared SCSI devices, the Compaq 20/40 GB DLT Tape Drive SCSI ID must be set to ensure that no two SCSI devices on the shared SCSI bus have the same SCSI ID.
Page 190: Cabling The Compaq 20/40 Gb Dlt Tape Drive
SCSI bus. A DWZZB-AA signal converter is required to convert the differential shared SCSI bus to single-ended. Figure 8–5 shows a configuration with a Compaq 20/40 GB DLT Tape Drive on a shared SCSI bus. To configure the shared SCSI bus for use with a Compaq 20/40 GB DLT...
Page 191 SCSI) is not exceeded. Ensure that the tape drive on the end of the bus is terminated with terminator part number 341102-001. You can add additional shared SCSI buses with Compaq 20/40 GB DLT Tape Drives by adding additional DWZZB-AA/Compaq 20/40 GB DLT Tape Drive combinations.
Page 192: Tape Drive
Figure 8–5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT Tape Drive Network Member Member Memory System System Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03...
Page 193: Preparing The Tz885 For Shared Scsi Usage
Table 8–3: Hardware Components Used to Create the Configuration Shown in Figure 8 — 5 (cont.) Description Callout Number 199629-002 or 189636-002 (1.8-meter cable) 341102-001 terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters.
Page 194 for use on a shared SCSI bus. The TZ885 in this figure has had the SCSI ID set to 0 (zero). To configure the shared SCSI bus for use with a TZ885, follow these steps: You will need one DWZZA-AA or DWZZB-AA for each TZ885 tape drive. Ensure that the DWZZA jumper J2 or DWZZB jumpers W1 and W2 are installed to enable the single-ended termination.
Page 195: Preparing The Tz887 For Shared Scsi Bus Usage
Figure 8–6: Cabling a Shared SCSI Bus with a TZ885 KZPSA adapter, DWZZA-VA, trilink connector, trilink connector, DWZZA-VA and H879 terminator and H879 terminator and trilink connector BN21K or BN21L cables Memory BN21K Memory Channel link cable Channel adapters BN21L cable BA350 BA350...
Page 196: Cabling The Tz887 Tape Drive
Figure 8–7: TZ887 DLT MiniLibrary Rear Panel SCSI ID SCSI ID Selector Switch TZ887 ZK-1461U-AI 8.5.2 Cabling the TZ887 Tape Drive The TZ887 is connected to a single-ended segment of the shared SCSI bus. It is connected to a differential portion of the shared SCSI bus with a DWZZB-AA.
Page 197: Cabling A Shared Scsi Bus With A Tz887
The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with BC19J cables, as long as the SCSI bus maximum length is not exceeded and there are sufficient SCSI IDs available. Ensure that the tape drive on the end of the bus is terminated with an H8574-A or H8890-AA terminator.
Page 198: Preparing The Tl891 And Tl892 Dlt Minilibraries For Shared Scsi Usage
8.6 Preparing the TL891 and TL892 DLT MiniLibraries for Shared SCSI Usage ______________________ Note _______________________ To achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus, and also recommend that no shared storage be placed on the same SCSI bus with a tape library.
Page 199 The first and second lines of the default screen show the status of the two drives (if present). The third line shows the status of the library robotics, and the fourth line is a map of the magazine, with the numbers from 0 to 9 representing the cartridge slots.
Page 200: Cabling The Tl891 Or Tl892 Minilibraries
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 default SCSI IDs are as follows: • Lib Bus ID: 0 • DLT0 Bus ID: 4 •...
Page 201 SCSI bus without stopping all ASE services that generate activity on the bus. For this reason, we recommend that tape devices be placed on separate shared SCSI buses, and that there be no storage devices on the SCSI bus. The cabling depends on whether or not there are one or two drives, and for the two-drive configuration, if each drive is on a separate SCSI bus.
Page 202 To connect the drive robotics and one drive to one shared SCSI bus and the second drive to a second shared SCSI bus, follow these steps: Connect a BN21K or BN21L between the last trilink connector on one shared SCSI bus to the leftmost connector (as viewed from the rear) of the TL892.
Page 203: Preparing The Tl890 Dlt Minilibrary Expansion Unit
Figure 8–9: TruCluster Server Cluster with a TL892 on Two Shared SCSI Buses KZPSA adapter, DWZZA-VA, DWZZA-VA, trilink connector, trilink connector, trilink connector, and H879 terminator BN21K or BN21L cables and H879 terminator and H879 terminator Memory Channel Memory Channel link cable adapters BA350 BA350...
Page 204: Tl890 Dlt Minilibrary Expansion Unit Hardware
8.7.1 TL890 DLT MiniLibrary Expansion Unit Hardware The TL890 expansion unit is installed above the TL891/TL892 DLT MiniLibrary base units in a SW500, SW800, or RETMA cabinet. The expansion unit integrates the robotics in the individual modules into a single, coordinated library robotics system. The TL890 assumes control of the media, maintaining an inventory of all media present in the system, and controls movement of all media.
Page 205 • Robotics control cables from each base module to the expansion unit: These cables have a DB-9 male connector on one end and a DB-9 female connector on the other end. Connect the male end to the Expansion Unit Interface connector on the base module and the female end to any Expansion Modules connector on the expansion unit.
Page 206: Configuring A Base Module As A Slave
Figure 8–10: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses DWZZA-VA, trilink connector, BN21K or BN21L cables and H879 terminator Memory Channel Memory Channel link cable adapters BA350 BA350 AlphaServer 2100As BN21K or BN21L cables Diag Motor H879-AA terminator SCSI Expansion Modules TL890...
Page 207 unit will not have control over the base module robotics when you power up the MiniLibrary system if you do not reconfigure the base modules as a slave. To reconfigure a TL891/TL892 base module as a slave to the TL890 DLT MiniLibrary expansion unit, perform the following procedure on each base module in the system: Turn on the power switch on the TL891/TL892 base module to be...
Page 208: Powering Up The Dlt Minilibrary
After the selection stops flashing and the control panel indicates that the change is not effective until a reboot, press the Enter button. When the Special Configuration menu reappears, turn the power switch off and then on to cycle the power. The base module is now reconfigured as a slave to the TL890 expansion unit.
Page 209 control functions are carried out from the expansion unit control panel. This includes setting the SCSI ID for each of the tape drives present. To set the SCSI IDs for the tape drives in a MiniLibrary configured with TL890/TL891/TL892 hardware, follow these steps: Apply power to the MiniLibrary, ensuring that you power up the expansion unit after or at the same time as the base modules.
Page 210: Preparing The Tl894 Dlt Automated Tape Library For Shared
10. If there are other items you wish to configure, press the Escape button until the Configure submenu is displayed, then select the item to be configured. Repeat this procedure for each item you wish to configure. 11. If there are no more items to be configured, press the Escape button until the Default window is displayed.
Page 211 Table 8–4: TL894 Default SCSI ID Settings (cont.) SCSI Device SCSI Address Tape Drive 2 Tape Drive 3 To set the SCSI ID for the TL894 robotics controller, follow these steps: Press and release the Control Panel STANDBY button and verify that the SDA (Status Display Area) shows System Off-line.
Page 212 12. Press and release the up or down button and the SELECT button simultaneously, and verify that System On-line or System Off-line is displayed in the SDA. To set the SCSI ID for each tape drive if the desired SCSI IDs are different from those shown in Table 8–4, follow these steps: Press and release the Control Panel STANDBY button and verify that the SDA (Status Display Area) shows System Off-line.
Page 213: Tl894 Tape Library Internal Cabling
14. Press and release the up or down button and the SELECT button simultaneously and verify that System On-line or System Off-line is displayed in the SDA. 8.8.3 TL894 Tape Library Internal Cabling The default internal cabling configuration for the TL894 tape library has the robotics controller and top drive (drive 0) on SCSI bus port 1.
Page 214: Connecting The Tl894 Tape Library To The Shared Scsi Bus
other drive to be daisy chained. Use the SCSI jumper cable to connect the two drives and place them on the same SCSI bus. ______________________ Notes ______________________ We recommend that you not place more than two TZ89 tape drives on any one SCSI bus in these tape libraries. We also recommend that storage be placed on shared SCSI buses that do not have tape drives.
Page 215: Shared Scsi Buses With Tl894 In Two-Bus Mode
Figure 8–12 shows a sample TruCluster Server cluster using a TL894 tape library. In the sample configuration, the tape library has been connected in the two-bus mode by jumpering tape drive 0 to tape drive 1 and tape drive 2 to tape drive 3 (See Section 8.8.3 and Figure 8–11). The two SCSI buses are left at the default SCSI IDs and terminated at drives 1 and 3 with the installed terminators (part number 0415619).
Page 216: Preparing The Tl895 Dlt Automated Tape Library For Shared
8.9 Preparing the TL895 DLT Automated Tape Library for Shared SCSI Bus Usage The topics in this section provide information on preparing the TL895 Digital Linear Tape (DLT) automated tape library for use on a shared SCSI bus. ______________________ Note _______________________ To achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus segment.
Page 217: Tl895 Robotic Controller Required Firmware
8.9.1 TL895 Robotic Controller Required Firmware Robotic firmware version N2.20 is the minimum firmware revision supported in a TruCluster Server cluster. For information on upgrading the robotic firmware, see the Flash Download section of the TL895 DLT Tape Library Diagnostic Software User’s Manual. 8.9.2 Setting the TL895 Tape Library SCSI IDs The library and each tape drive must have the SCSI ID set (unless the default is sufficient).
Page 218: Tl895 Tape Library Internal Cabling
To change any of the configurations, press the Configure button. Press the Select button until the item you wish to configure is highlighted. For the devices, select the desired device (library or drive) by scrolling through the devices with the arrow buttons. After the library or selected drive is selected, use the Select button to highlight the SCSI ID.
Page 219: Tl895 Tape Library Internal Cabling
To reconfigure TL895 SCSI bus configuration, follow these steps: Remove the SCSI bus cable from one drive to be daisy chained. Remove the terminator from the other drive to be daisy chained. Ensure that the drive that will be the last drive on the SCSI bus has a terminator installed.
Page 220: Upgrading A Tl895
8.9.4 Upgrading a TL895 The TL985 DLT automated tape library can be upgraded from two or five tape drives to seven drives with multiple DS-TL89X-UA upgrade kits. Besides the associated documentation, the upgrade kit contains one TZ89N-AV tape drive, a SCSI bus terminator, a SCSI bus jumper (part number 6210567) so you can place more than one drive on the same SCSI bus, and other associated hardware.
Page 221 ______________________ Note _______________________ To achieve system performance capabilities, We recommend placing no more than two TZ89 drives on a SCSI bus. The TL893 and TL896 Automated Tape Libraries (ATLs) are designed to provide high-capacity storage and robotic access for the Digital Linear Tape (DLT) series of tape drives.
Page 222: Communications With The Host Computer
on adding additional cabinets. Up to five cabinets are supported with the TruCluster Server. For TruCluster Server, the tape cartridges in all the cabinets are combined into one logical unit, with consecutive numbering from the first cabinet to the last cabinet, by an upgrade from the multi-unit, multi-LUN (MUML) configuration to a multi-unit, single-LUN (MUSL) configuration.
Page 223: Setting The Muc Scsi Id
Table 8–6: MUC Switch Functions Function Switch 1, 2, and 3 MUC SCSI ID if Switch 7 is down 4 and 5 Must be down, reserved for testing Default is up, disable bus reset on power up Host selection: Down for SCSI, up for serial 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.
Page 224: Tl893 And Tl896 Automated Tape Library Internal Cabling
Table 8–8: TL893 Default SCSI IDs Device SCSI Port Default SCSI ID Drive 2 (top) Drive 1 (middle) Drive 0 (bottom) Table 8–9: TL896 Default SCSI IDs SCSI Port Device Default SCSI ID Drive 5 (top) Drive 4 Drive 3 Drive 2 Drive 1 Drive 0 (bottom)
Page 225: Tl893 Three-Bus Configuration
– The bottom shelf tape drive (SCSI ID 3) is on SCSI Port A and is also terminated on the drive with a 68-pin Micro-D terminator, part number 0415619. Figure 8–14: TL893 Three-Bus Configuration 0415498 (50-Pin Micro-D Terminator) 0425031 (SCSI Diff Feed Through) 0425017 (Cable) SCSI Address 2 TZ89 Tape Drive...
Page 226: Tl896 Six-Bus Configuration
– The lower bay top shelf tape drive (tape drive 2, SCSI ID 5) is on SCSI Port A and is terminated on the tape drive. – The lower bay middle shelf tape drive (tape drive 1, SCSI ID 4) is on SCSI Port B and is terminated on the tape drive.
Page 227: Connecting The Tl893 And Tl896 Automated Tape Libraries To The Shared Scsi Bus
8.10.6 Connecting the TL893 and TL896 Automated Tape Libraries to the Shared SCSI Bus The TL893 and TL896 Automated Tape Libraries (ATLs) have up to 3 meters of internal SCSI cabling on each SCSI bus. Because of the internal SCSI cable lengths, it is not possible to use a trilink connector or Y cable to terminate the SCSI bus external to the library as is done with other devices on the shared SCSI bus.
Page 228: Preparing The Tl881 And Tl891 Dlt Minilibraries For Shared Bus Usage
8.11 Preparing the TL881 and TL891 DLT MiniLibraries for Shared Bus Usage The topics in this section provide an overview of the Compaq StorageWorks TL881 and TL891 Digital Linear Tape (DLT) MiniLibraries and hardware configuration information for preparing the TL881 or TL891 DLT MiniLibrary for use on a shared SCSI bus.
Page 229: Tl881 And Tl891 Dlt Minilibrary Tabletop Model
• TL891 MiniLibrary System User’s Guide • TL881 MiniLibrary Drive Upgrade Procedure • Pass-Through Expansion Kit Installation Instructions The TL881 and TL891 Digital Linear Tape (DLT) MiniLibraries are offered as standalone tabletop units or as expandable rackmount units. The following sections describe these units in more detail. 8.11.1.1 TL881 and TL891 DLT MiniLibrary Tabletop Model The TL881 and TL891 DLT MiniLibrary tabletop model consists of one unit with a removable 10-cartridge magazine, integral bar code reader, and either...
Page 230: Tl881 And Tl891 Rackmount Scalability
device and only works as a slave to the expansion unit. To create a multimodule rackmount system, there must be one expansion unit and at least one base unit. The expansion unit has to be the top module in the configuration. The expansion unit works with either the TL881 or TL891 base unit.
Page 231: Dlt Minilibrary Part Numbers
TL881 or TL891 MiniLibrary in configurations set up for either maximum performance or maximum capacity. Table 8–10: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary Number of Number of Transfer Transfer Configured Storage Storage Base Units Data Units Rate Rate...
Page 232: Preparing A Tabletop Model Or Base Unit For Standalone Shared Scsi Bus Usage
Table 8–11: DLT MiniLibrary Part Numbers (cont.) Number of Tape Part Number DLT Library Component Tabletop/Rackmount Drives TL891 DLT MiniLibrary Rackmount 120876-B21 Base Unit TL891 DLT MiniLibrary Rackmount 120876-B22 Base Unit Add-on DLT 35/70 drive 120878-B21 for TL891 MiniLibrary Expansion Unit Rackmount 120877-B21 MiniLibrary Data Unit...
Page 233: Setting The Standalone Minilibrary Tape Drive
The topics in this section provide information on preparing the TL881 or TL891 DLT MiniLibrary tabletop model or rackmount base unit for use on a shared SCSI bus. For complete hardware installation instructions, see the TL881 MiniLibrary System User’s Guide or TL891 MiniLibrary System User’s Guide. 8.11.2.1.1 Setting the Standalone MiniLibrary Tape Drive SCSI ID The control panel on the front of the TL891 and TL892 MiniLibraries is used to display power-on self-test (POST) status, display messages, and to set...
Page 234: Cabling The Tl881 Or Tl891 Dlt Minilibrary
____________________ Note _____________________ When you enter the Menu Mode, the Ready light goes out, an indication that the module is off line, and all medium changer commands from the host return a SCSI "not ready" status until you exit the Menu Mode and the Ready light comes on once again.
Page 235 ______________________ Note _______________________ The tape drive SCSI connectors are labeled DLT1 (tape drive 1) and DLT2 (tape drive 2). The control panel designation for the drives is DLT0 (tape drive 1) and DLT1 (tape drive 2). The default for the TL881 or TL891 DLT MiniLibrary is to place the robotics controller and tape drive 1 on the same SCSI bus (Figure 8–17).
Page 236 Install an HD68 differential terminator (such as an H879-AA) on the right 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: Connect a 328215-00X, BN21K, or BN21L between the last trilink connector on the bus to the leftmost connector (as viewed from the rear) of the MiniLibrary.
Page 237: Tl891 Standalone Cluster Configuration
Figure 8–17: TL891 Standalone Cluster Configuration Network Member Member Memory System System Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) Library DLT1 Robotics DS-DWZZH-03 DLT2 Controller B Controller A Expansion Unit HSZ70 HSZ70...
Page 238: For Shared Scsi Bus Usage
Table 8–12: Hardware Components Used to Create the Configuration Shown in Figure 8–17 (cont.) Description Callout Number H879-AA terminator 328215-00X, BN21K, or BN21L cable a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters.
Page 239 connector on the data unit and the female end to any Expansion Modules connector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector a base unit or data unit is connected to. • SCSI bus connection to the expansion unit robotics: Connect the shared SCSI bus that will control the robotics to one of the SCSI connectors on the expansion unit with a 328215-00X, BN21K, or BN21L cable.
Page 240: Expansion Unit
Figure 8–18: TL881 DLT MiniLibrary Rackmount Configuration Network Memory Member System 1 Member System 2 Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03 Diag Motor Expansion...
Page 241: Shown In Figure 8–18
Table 8–13: Hardware Components Used to Create the Configuration Shown in Figure 8–18 Description Callout Number BN38C or BN38D cable BN37A cable H8861-AA VHDCI trilink connector H8863-AA VHDCI terminator BN21W-0B Y cable H879-AA terminator 328215-00X, BN21K, or BN21L cable a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters.
Page 242: Powering Up The Tl881/Tl891 Dlt Minilibrary
DLT0 Idle DLT1 Idle Loader Idle 0> _ _ _ _ _ _ _ _ _ _ <9 The default screen shows the state of the tape drives, loader, and number of cartridges present for this base unit. A rectangle in place of the underscore indicates that a cartridge is present in that location.
Page 243: Setting The Scsi Ids For A Rackmount Tl881 Or Tl891 Dlt Minilibrary
When the expansion unit comes up, it will communicate with each base and data unit through the expansion unit interface and inventory the number of base units, tape drives, data units, and cartridges present in each base and data unit. After the MiniLibrary configuration has been determined, the expansion unit will communicate with each base and data unit and indicate to the modules which cartridge group that base or data unit contains.
Page 244: Compaq Esl9326D Enterprise Library
8.12.1 General Overview The Compaq StorageWorks ESL9326D Enterprise Library is the first building block of the Compaq ESL 9000 series tape library. For more information on the ESL9326D Enterprise Library, see the following Compaq StorageWorks ESL9000 Series Tape Library documentation: •...
Page 245: Esl9326D Enterprise Library Overview
A tape library with a capacity for additional tape drives may be upgraded with part number 146209-B21, which adds a 35/70 DLT tape drive. See the Compaq StorageWorks ESL9000 Series Tape Library Tape Drive Upgrade Guide (146582-001) for more information.
Page 246: Esl9326D Enterprise Library Robotic And Tape Drive Required Firmware
The default robotics and tape drive SCSI IDs are shown in Figure 8–19. If these SCSI IDs are not acceptable for your configuration and you need to change them, follow the steps in the Compaq StorageWorks ESL9000 Series Tape Library Reference Guide (146583-001).
Page 247: Esl9326D Internal Cabling
Figure 8–19: ESL9326D Internal Cabling Tape Drive 8 Tape Drive 0 SCSI ID 2 SCSI ID 2 Tape Drive 1 Tape Drive 9 SCSI ID 3 SCSI ID 3 Tape Drive 2 Tape Drive 10 SCSI ID 4 SCSI ID 4 Tape Drive 11 Tape Drive 3 SCSI ID 5...
Page 248: Shared Scsi Bus
8.12.3.4 Connecting the ESL9326D Enterprise Library to the Shared SCSI Bus The ESL9326D Enterprise Library has 5 meters of internal SCSI bus cabling for each pair of tape drives. Because of the internal SCSI bus lengths, it is not possible to use a trilink connector or Y cable to terminate the SCSI bus external to the tape library as is done with other devices on the shared SCSI bus.
Page 249 ______________________ Notes ______________________ Each ESL9326D Enterprise Library arrives with one 330563-001 HD68 terminator for each pair of tape drives (one SCSI bus). The kit also includes at least one 330582-001 jumper cable to connect the library electronics to tape drives 0 and 1. Tape libraries with more than six tape drives include extra 330582-01 jumper cables in case the customer is short on host bus adapters and wants to place more than two tape drives on a single...
Page 251: Configurations Using External Termination Or Radial Connections To Non-Ultrascsi Devices
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 using only the supported hardware, adhering to the requirements described in this chapter will ensure that your cluster operates correctly.
Page 252: Using Scsi Bus Signal Converters
9.1 Using SCSI Bus Signal Converters A SCSI bus signal converter allows you to couple a differential bus segment to a single-ended bus segment, allowing the mixing of differential and single-ended devices on the same SCSI bus to isolate bus segments for maintenance purposes.
Page 253: Using The Scsi Bus Signal Converters
but you would waste a disk slot and it would not work with a KZPBA-CB if there are any UltraSCSI disks in the storage shelves. The following sections discuss the DWZZA and DWZZB signal converters and the DS-BA35X-DA personality module. 9.1.2 Using the SCSI Bus Signal Converters The DWZZA and DWZZB signal converters are used in the BA350 and BA356 storage shelves.
Page 254: Ds-Ba35X-Da Termination
Figure 9–1: Standalone SCSI Signal Converter Single-ended Differential side with trilink side attached ZK-1050U-AI Figure 9–2 shows the status of internal termination for an SBB SCSI signal converter that has a trilink connector attached to the differential side. Figure 9–2: SBB SCSI Signal Converter Single-ended side Differential side with trilink...
Page 255: Terminating The Shared Scsi Bus
______________________ Notes ______________________ S4-3 and S4-4 have no function on the DS-BA35X-DA personality module. See Section 9.3.2.2 for information on how to select the device SCSI IDs in an UltraSCSI BA356. Figure 9–3 shows the relative positions of the two DS-BA35X-DA switch packs.
Page 256 Whenever possible, connect devices to a shared bus so that they can be isolated from the bus. This allows you to disconnect devices from the bus for maintenance purposes without affecting bus termination and cluster operation. You also can set up a shared SCSI bus so that you can connect additional devices at a later time without affecting bus termination.
Page 257: Bn21W-0B Y Cable
connector at a later time without affecting bus termination. This allows you to expand your configuration without shutting down the cluster. Figure 9–4 shows a BN21W-0B Y cable, which you may attach to a KZPSA-BB or KZPBA-CB SCSI adapter that has had its onboard termination removed.
Page 258: Overview Of Disk Storage Shelves
Figure 9–5: HD68 Trilink Connector (H885-AA) REAR VIEW FRONT VIEW ZK-1140U-AI ______________________ Note _______________________ If you connect a trilink connector to a SCSI bus adapter, you may block access to an adjacent PCI slot. If this occurs, use a Y cable instead of the trilink connector.
Page 259: Ba350 Storage Shelf
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 the slot they are installed in. For instance, a disk installed in BA350 slot 0 has SCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1, and so forth.
Page 260: Ba356 Storage Shelf
Figure 9–6: BA350 Internal SCSI Bus POWER (7) 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 has a wide, single-ended internal SCSI bus.
Page 261 select SCSI IDs 0 through 6, set the personality module address switches 1 through 7 to off. To select SCSI IDs 8 through 14, set personality module address switches 1 through 3 to on and switches 4 through 7 to off. Figure 9–7 shows the relative location of the BA356 SCSI bus jumper, BA35X-MF.
Page 262: Ba356 Internal Scsi Bus
Figure 9–7: BA356 Internal SCSI Bus POWER (7) ZK-1339U-AI Note that JA1 and JB1 are located on the personality module (in the top of the box when it is standing vertically). JB1, on the front of the module, is visible. JA1 is on the left side of the personality module as you face the front of the BA356, and is hidden from the normal view.
Page 263: Ultrascsi Ba356 Storage Shelf
Figure 9–8: BA356 Jumper and Terminator Module Identification Pins Slot 6 Slot 1 Jumper Jumper Slot 6 Slot 1 Terminator Terminator 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 personality module provides the interface between the internal, single-ended UltraSCSI bus segment and the shared, wide, differential UltraSCSI bus.
Page 264: Preparing The Storage For Configurations Using External Termination
BA356, as shown in Figure 9–8. With proper lighting you will be able to see a J or T near the hole where the pin sticks through. Termination for both ends of the UltraSCSI BA356 internal, single-ended bus is on the personality module, and is always active. Termination for the differential UltraSCSI bus is also on the personality module, and is controlled by the SCSI bus termination switches, switch pack S4.
Page 265: Configuration
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, BA356, or UltraSCSI BA356 storage shelves in your TruCluster Server configuration as follows: •...
Page 266: Usage
You will need a DWZZA-VA signal converter for the BA350. Ensure that the DWZZA-VA single-ended termination jumper, J2, is installed. Remove the termination from the differential end by removing the five 14-pin differential terminator resistor SIPs. Attach an H885-AA trilink connector to the DWZZA-VA 68-pin high-density connector.
Page 267: Preparing An Ultrascsi Ba356 Storage Shelf For A Trucluster Configuration
SCSI bus (cable and BA356) under the 3-meter limit to still allow high speed operation. If you are using a DWZZB-VW, install it in slot 0 of the BA356. 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 bus, and provides access to UltraSCSI devices on the internal, single-ended and wide UltraSCSI bus.
Page 268: Bus Usage
must be used with a BA356 or UltraSCSI BA356 if more than five disks are required. The following sections provide the steps needed to connect two storage shelves and two member systems on a shared SCSI bus: • BA350 and BA356 (Section 9.4.2.1) •...
Page 269: Ba350 And Ba356 Cabled For Shared Scsi Bus Usage
Figure 9–9: BA350 and BA356 Cabled for Shared SCSI Bus Usage Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) BA356 BA350 DWZZB-VW DWZZA-VA Clusterwide ID 9 ID 1 /, /usr, /var Member 1 ID 2 ID 10...
Page 270: Connecting Two Ba356S For Shared Scsi Bus Usage
Table 9–1: Hardware Components Used for Configuration Shown in Figure 8–9 and Figure 8–10 Description Callout Number BN21W-0B Y cable H879-AA terminator BN21K (or BN21L) cable H885-AA trilink connector a The maximum combined length of the BN21K (or BN21L) cables must not exceed 25 meters. 9.4.2.2 Connecting Two BA356s for Shared SCSI Bus Usage When you use two BA356 storage shelves on a shared SCSI bus in a TruCluster configuration, one BA356 must be configured for SCSI IDs 0...
Page 271: Two Ba356S Cabled For Shared Scsi Bus Usage
Figure 9–10: Two BA356s Cabled for Shared SCSI Bus Usage Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) BA356 BA356 DWZZB-VW DWZZB-VW Clusterwide ID 9 ID 1 /, /usr, /var Member 1 ID 2 ID 10...
Page 272 To prepare two UltraSCSI BA356 storage shelves for shared SCSI bus usage, (see Figure 9–11) follow these steps: Complete the steps of Section 9.4.1.3 for each UltraSCSI BA356. Ensure that the personality module address switches on one UltraSCSI BA356 are set to select SCSI IDs 0 through 6 and the address switches on the other UltraSCSI BA356 personality module are set to select SCSI IDs 8 through 14.
Page 273: Two Ultrascsi Ba356S Cabled For Shared Scsi Bus Usage
Figure 9–11: Two UltraSCSI BA356s Cabled for Shared SCSI Bus Usage Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) Tru64 UNIX UltraSCSI UltraSCSI Disk BA356 BA356 Clusterwide ID 8 ID 0 /, /usr, /var Member 1 ID 9...
Page 274: Cabling A Non-Ultrascsi Raid Array Controller To An Externally Terminated Shared Scsi Bus
Table 9–2: Hardware Components Used for Configuration Shown in Figure 9–11 Description Callout Number BN21W-0B Y cable H879-AA HD68 terminator BN38C (or BN38D) cable H8861-AA VHDCI trilink connector BN37A cable a The maximum combined length of the BN38C (or BN38D) and BN37A cables on one SCSI bus segment must not exceed 25 meters.
Page 275: Cabling An Hsz40 Or Hsz50 In A Cluster Using External Termination
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 shared SCSI bus, follow these steps: If the HSZ40 or HSZ50 will be on the end of the shared SCSI bus, attach an H879-AA terminator to an H885-AA trilink connector.
Page 276: Externally Terminated Shared Scsi Bus With Mid-Bus Hsz50
Figure 9–12: Externally Terminated Shared SCSI Bus with Mid-Bus HSZ50 RAID Array Controllers Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) HSZ50 HSZ50 Controller A Controller B ZK-1596U-AI Table 9–3 shows the components used to create the cluster shown in Figure 9–12 and Figure 9–13.
Page 277: Cabling An Hsz20 In A Cluster Using External Termination
Figure 9–13: Externally Terminated Shared SCSI Bus with HSZ50 RAID Array Controllers at Bus End Network Member Member System System Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) HSZ50 HSZ50 Controller A Controller B ZK-1597U-AI Table 9–3 shows the components used to create the cluster shown in Figure 9–12 and Figure 9–13.
Page 278: Cabling An Hsz40 Or Hsz50 Raid Array Controller In A Radial Configuration With An Ultrascsi Hub
• Ensure that the W1 and W2 jumpers are installed to enable the single-ended termination on one end of the bus. ___________________ Note ___________________ The RAID Array 310 SCSI bus converter board is the same logic board used in the DWZZB signal converter. Attach an H885-AA trilink connector to the SCSI input connector (on the back of the cabinet).
Page 279 Install the UltraSCSI hub in: • A StorageWorks UltraSCSI BA356 shelf (which has the required 180-watt power supply). • A non-UltraSCSI BA356 which has been upgraded to the 180-watt power supply with the DS-BA35X-HH option. If you are using a: •...
Page 280: Trucluster Server Cluster Using Ds-Dwzzh-03, Scsi Adapter With Terminators Installed, And Hsz50
Figure 9–14: TruCluster Server Cluster Using DS-DWZZH-03, SCSI Adapter with Terminators Installed, and HSZ50 KZPSA-BB DS-DWZZH-03 AlphaServer Member System 1 HSZ50 KZPSA-BB HSZ50 AlphaServer Member System 2 ZK-1415U-AI Table 9–4 shows the components used to create the cluster shown in Figure 9–14.
Page 281: Trucluster Server Cluster Using Kzpsa-Bb Scsi Adapters, A Ds-Dwzzh-05 Ultrascsi Hub, And An Hsz50 Raid Array Controller
Figure 9–15: TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller AlphaServer Member System 1 KZPSA-BB KZPSA-BB DS-DWZZH-05 AlphaServer Member System 2 HSZ50 KZPSA-BB KZPSA-BB HSZ50 AlphaServer AlphaServer Member Member System 3 System 4 ZK-1449U-AI ______________________...
Page 283: Configuring Systems For External Termination Or Radial Connections To Non-Ultrascsi Devices
Configuring Systems for External Termination or Radial Connections to Non-UltraSCSI Devices This chapter describes how to prepare the systems for a TruCluster Server cluster when there is a need for external termination or radial connection to non-UltraSCSI RAID array controllers (HSZ40 and HSZ50). This chapter does not provide detailed information about installing devices;...
Page 284: Internal Termination
Follow the steps in Table 10–1 to start the TruCluster Server hardware installation procedure. You can save time by installing the Memory Channel adapters, redundant network adapters (if applicable), and KZPSA-BB or KZPBA-CB SCSI adapters all at the same time. Follow the directions in the referenced documentation, or the steps in the referenced tables for the particular SCSI host bus adapter, returning to the appropriate table when you have completed the steps in the referenced table.
Page 285 The DWZZH-series UltraSCSI hubs are designed to allow more separation between member systems and shared storage. Using the UltraSCSI hub also improves the reliability of the detection of cable faults. A side benefit is the ability to connect the member systems’ SCSI adapter directly to a hub port without external termination.
Page 286: To A Dwzzh Ultrascsi Hub
_____________________ 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.4.1. The KZPBA-CB UltraSCSI host adapter: • Is a high-performance PCI option connecting the PCI-based host system to the devices on a 16-bit, ultrawide differential SCSI bus.
Page 287 Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: Power down the system. Install a KZPSA-BB KZPSA PCI-to-SCSI PCI-to-SCSI adapter or KZPBA-CB UltraSCSI host Storage Adapter adapter in the PCI slot corresponding to the logical Installation and User’s bus to be used for the shared SCSI bus.
Page 288: Installing A Kzpsa-Bb Or Kzpba-Cb Using External Termination
Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: Use the show pk* or show isp* console Section 10.1.4.1 through commands to determine the status of the Section 10.1.4.3 and KZPSA-BB or KZPBA-CB console environment Example 10–6 through variables, and then use the set console...
Page 289 Table 10–3: Installing a KZPSA-BB or KZPBA-CB for use with External Termination Step Action Refer to: Remove the KZPSA-BB internal termination Section 10.1.4.4, resistors, Z1, Z2, Z3, Z4, and Z5. Figure 10–1, and KZPSA PCI-to-SCSI Storage Adapter Installation and User’s Guide Remove the eight KZPBA-CB internal termination Section 4.3.3.3, resistor SIPs, RM1-RM8.
Page 290 Install the tape device hardware and cables Chapter 8 on the shared SCSI bus as follows: TZ88 Section 8.1 TZ89 Section 8.2 Compaq 20/40 GB DLT Tape Drive Section 8.3 TZ885 Section 8.4 TZ887 Section 8.5 TL891/TL892 MiniLibrary Section 8.6 10–8 Configuring Systems for External Termination or Radial Connections...
Page 291: Show Console Commands
TL895 Section 8.9 TL893/TL896 Section 8.10 TL881/TL891 DLT MiniLibraries Section 8.11 Compaq ESL9326D Enterprise Library Section 8.12 _____________________ Notes _____________________ If you install tape devices on the shared SCSI buses, ensure that you understand how the particular tape device(s) affect the shared SCSI bus.
Page 292: Displaying Devices On An Alphaserver 4100
Example 10–1: Displaying Configuration on an AlphaServer 4100 (cont.) CPU (4MB Cache) 0000 cpu0 CPU (4MB Cache) 0000 cpu1 Bridge (IOD0/IOD1) 0021 iod0/iod1 PCI Motherboard 0000 saddle0 Bus 0 iod0 (PCI0) Slot Option Name Type Name PCEB 4828086 0005 pceb0 S3 Trio64/Trio32 88115333 0000 vga0...
Page 293 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.1 DKe100...
Page 294 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, slot0, bus0, hose1...
Page 295: Displaying Console Environment Variables And Setting
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 examples as guides for your system.
Page 296 Example 10–5: Displaying the pk* Console Environment Variables on an AlphaServer 4100 System (cont.) pke0_termpwr pkf0_fast pkf0_host_id pkf0_termpwr Compare the show pk* command display in Example 10–5 with the show config command in Example 10–1 and the show dev command in Example 10–2.
Page 297: Alphaserver 8X00 System
Example 10–6: Displaying Console Variables for a KZPBA-CB on an AlphaServer 8x00 System P00>>> show isp* isp0_host_id isp0_soft_term isp1_host_id isp1_soft_term isp2_host_id isp2_soft_term isp3_host_id isp3_soft_term isp5_host_id isp5_soft_term diff Both Example 10–3 and Example 10–4 show five isp devices; isp0, isp1, isp2, isp3, and isp4. In Example 10–6, the show isp* console command shows isp0, isp1, isp2, isp3, and isp5.
Page 298: Setting The Kzpba-Cb Scsi Id
Example 10–7: Displaying Console Variables for a KZPSA-BB on an AlphaServer 8x00 System (cont.) pkc0_fast pkc0_host_id pkc0_termpwr 10.1.4.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBs on the shared SCSI bus, use the set console command to set the SCSI ID. For a TruCluster Server cluster, you will most likely have to set the SCSI ID for all KZPBA-CB UltraSCSI adapters except one.
Page 299: Termination Power
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 the firmware update utility, or you need to change the KZPSA-BB speed, or enable termination power, use the set console command.
Page 300: Kzpsa-Bb And Kzpba-Cb Termination Resistors
10.1.4.4 KZPSA-BB and KZPBA-CB Termination Resistors The KZPSA-BB internal termination is disabled by removing termination resistors Z1 through Z5, as shown in Figure 10–1. Figure 10–1: KZPSA-BB Termination Resistors Z1 − Z5 Termination Resistor SIPs The KZPBA-CB internal termination is disabled by removing the termination resistors RM1-RM8 as shown in Figure 4–1.
Page 301 The boot sequence provides firmware update overview information. Use Return to scroll the text, or press Ctrl/C to skip the text. After the overview information has been displayed, the name of the default boot file is provided. If it is the correct boot file, press Return at the Bootfile: prompt.
Page 303: A Worldwide Id To Disk Name Conversion Table
Worldwide ID to Disk Name Conversion Table Table A–1: Converting Storageset Unit Numbers to Disk Names WWID User Device Name dskn File System HSG80 or Disk Unit Define Iden- tifier (UDID) Tru64 UNIX disk Cluster root /usr /var Member 1 boot disk Member 2 boot disk...
Page 305 ESL9326D , 2–9, DS-DWZZH-03 installed in , 2–10 supported 3–9, 4–7, 9–29, 10–3 cabling , 3–10 DS-DWZZH-05 installed in Compaq 20/40 GB DLT Tape Drive , 9–9, 9–12 jumper 8–10 personality module address , 8–8 DS-TZ89N-TA , 9–11 switches , 8–7 DS-TZ89N-VW , 9–15, 9–17...
Page 306 , 6–40 wwidmgr , 3–4 definition , 6–41 wwidmgr -clear disk devices , 6–42 wwidmgr -quickset , 2–7 restrictions , 6–24, 6–42, 6–45 wwidmgr -show , 3–16, 9–14 setting up Compaq 20/40 GB DLT Tape Drive disk placement 8–9 Index–2...
Page 307 , 4–9t, 10–5t, 10–7t KZPBA-CB , 3–10 SCSI ID , 10–5t, 10–7t KZPSA-BB , 3–9 termpwr , 2–9 transfer rate Compaq 20/40 GB DLT Tape Drive DS-TZ89N-TA 8–9 , 8–8 cabling , 8–13 TZ885 , 8–8 setting SCSI ID , 8–15...
Page 308 , 2–5 , 6–8 configuring supported configurations , 2–5 , 6–15 port configuration switch installation , 6–32 , 6–4 replacing controllers of terminology , 2–5 , 6–5, 6–61 transparent failover mode topology file , 2–5 unit configuration , 6–26 ESL9000 series tape library /var/adm/messages ( See ESL9326D ) firmware...
Page 309 , 2–1 ( See also hardware supported Y cables , 2–11 configuration ) terminators , 2–11 , 7–1 trilink connectors ATM adapter host bus adapters , 6–22 KGPSA ( See KGPSA, KZPBA-CB, , 10–3 KZPSA KZPSA-BB ) , 5–10 HSG80 controller , 5–9 MC2 cables , 2–4...
Page 310 , 5–12 KZPSA-BB diagnostics , 5–2, 5–5 displaying device information installation 10–5t, 10–7t , 2–3 interconnect , 10–3 , 5–2 installation jumpers , 2–6 , 2–2 restrictions versions , 10–17 Memory Channel diagnostics setting bus speed , 5–12 , 10–17 mc_cable setting SCSI ID , 5–12...
Page 311 , 6–32 replacing controllers of , 2–5 transparent failover mode , 6–16 optical cable , 2–5 unit configuration optical converter radial connection , 5–6 cable connection , 3–8 bus termination , 5–6 installation , 3–8 UltraSCSI hub , 1–13 RAID RAID array controllers , 3–17 advantages of use...
Page 312 , 6–23 shortwave , 10–17 KZPSA SHOW THIS_CONTROLLER setting SCSI ID , 6–31 command Compaq 20/40 GB DLT Tape Drive , 9–2 signal converters 8–9 , 9–2 creating differential bus , 8–8 DS-TZ89N-TA , 9–2 differential I/O module , 8–5...
Page 313 , 9–2 , 3–7, terminating the shared bus , 9–3 9–5 single-ended termination , 9–2 , 9–14 standalone UltraSCSI BA356 termination resistors , 9–2 terminating , 4–9t, 10–4t, 10–7t KZPBA-CB , 9–3 termination , 10–4t, 10–7t single-ended SCSI buses KZPSA , 3–4 , 10–7t description of...
Page 314 , 8–30 setting SCSI ID preparing for shared SCSI usage TL895 9–17 , 8–40 cabling , 9–17 SCSI ID selection , 8–40, 8–41 TL896 , 9–13 selecting SCSI IDs , 8–44, 8–47 cabling , 9–14 termination , 8–42 MUC switch functions UltraSCSI host adapter , 8–43 , 3–3...
Page 315 , 9–6 connecting devices with , 2–10 supported Y cables Index–11...
Page 317 Tru64 UNIX Documentation Overview or call 800-344-4825 in the United States and Canada. In Puerto Rico, call 787-781-0505. In other countries, contact your local Compaq subsidiary. If you have access to Compaq’s intranet, you can place an order at the following Web site: http://asmorder.nqo.dec.com/ The following table provides the order numbers for the Tru64 UNIX operating system documentation kits.
Page 319 TruCluster Server Hardware Configuration AA-RHGWB-TE Compaq welcomes your comments and suggestions on this manual. Your input will help us to write documentation that meets your needs. Please send your suggestions using one of the following methods: • This postage-paid form •...
Page 320 NECESSARY IF MAILED IN THE UNITED STATES FIRST CLASS MAIL PERMIT NO. 33 MAYNARD MA POSTAGE WILL BE PAID BY ADDRESSEE COMPAQ COMPUTER CORPORATION UBPG PUBLICATIONS MANAGER ZKO3-3/Y32 110 SPIT BROOK RD NASHUA NH 03062-2698 Do Not Cut or Tear - Fold Here...

Compaq TruCluster Server AA-RHGWB-TE Manual

About this Manual

1 Introduction

2 Hardware Requirements and Restrictions

3 Shared SCSI Bus Requirements and Configurations Using Ultrascsi Hardware

4 Trucluster Server System Configuration Using Ultrascsi Hardware

5 Setting up the Memory Channel Cluster Interconnect

6 Using Fibre Channel Storage

7 Preparing ATM Adapters

8 Configuring a Shared SCSI Bus for Tape Drive Use

9 Configurations Using External Termination or Radial Connections to Non-Ultrascsi Devices

Quick Links

TruCluster Server

Hardware Configuration

Need help?

Questions and answers

Related Manuals for Compaq TruCluster Server AA-RHGWB-TE

Summary of Contents for Compaq TruCluster Server AA-RHGWB-TE