Page 1: Trucluster Server
TruCluster Server Version 5.1 Operating System and Version: Tru64 UNIX Version 5.1 This manual describes how to configure the hardware for a TruCluster™ Server environment. TruCluster Server Version 5.1 runs on the Tru64™ UNIX operating system. Compaq Computer Corporation Houston, Texas...
Page 2 Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice.
Page 3: Table Of Contents
Contents About This Manual 1 Introduction The TruCluster Server Product ........1–1 Memory Requirements ..........1–2 Minimum Disk Requirements ..
Page 4 SCSI Signal Converters ..........2–10 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs ... 2–11 SCSI Cables .
Page 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 Commands .
Page 6 6.2.2.2 Fabric ............6–7 6.2.2.3 Arbitrated Loop Topology .
Page 7 6.6.2 Install the Tru64 UNIX Operating System ....6–51 6.6.3 Determining /dev/disk/dskn to Use for a Cluster Installation ............6–51 6.6.4 Label the Disks to Be Used to Create the Cluster .
Page 8 Cabling the Compaq 20/40 GB DLT Tape Drive .... . 8–11 Compaq 40/80-GB DLT Drive ........8–14 8.4.1...
Page 9 TL891 DLT MiniLibrary ....... 8–72 8.13 Compaq ESL9326D Enterprise Library ......8–73 8.13.1 General Overview ..
Page 10 8.13.3.1 ESL9326D Enterprise Library Robotic and Tape Drive Required Firmware ......... 8–75 8.13.3.2 Library Electronics and Tape Drive SCSI IDs .
Page 11 9.4.3.2 Cabling an HSZ20 in a Cluster Using External Termination ..........9–28 9.4.4 Cabling an HSZ40 or HSZ50 RAID Array Controller in a...
Page 12 5–1 Running the mc_cable Test ......... . 5–13 6–1 Determine HSG80 Connection Names ......6–31 6–2 Setting Up the Mirrorset .
Page 13 1–8 NSPOF Fibre Channel Cluster Using HSG80s in Multiple-Bus Failover Mode ............1–16 2–1 PCI Backplane Slot Layout .
Page 14 DS-TZ89N-VW SCSI ID Switches ........8–7 8–4 Compaq 20/40 GB DLT Tape Drive Rear Panel ....8–11 8–5 Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT Tape Drive ..
Page 15 9–15 TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller ............. . 9–31 10–1 KZPSA-BB Termination Resistors .
Page 16: Hardware Components Used In Configuration Shown In
8–9 TL894 Default SCSI ID Settings ........8–37 8–10 Hardware Components Used to Create the Configuration Shown in Figure 8–12 ..........8–42 8–11 TL895 Default SCSI ID Settings ..
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
TruCluster Server Version 5.1 product. You can find the latest version of the SPD and other TruCluster Server documentation at the following URL: http://www.tru64unix.compaq.com/faqs/publications/pub_page/cluster_list.html • Release Notes — Provides important information about TruCluster Server Version 5.1.
Page 19 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 • HSZ70 Array Controller HSOF Version 7.0 Configuration Manual •...
Page 20 • Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide • Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide • Compaq StorageWorks Fibre Channel SAN Switch 8-EL Installation and Hardware Guide • Compaq StorageWorks Fibre Channel SAN Switch Management Guide •...
Page 21 At this URL you will find links to individual system, storage, or cluster configurations. You can order the document through the Compaq Literature Order System (LOS) as order number EC-R026B-36. In addition, have available the following manuals from the Tru64 UNIX documentation set: •...
Page 22 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 • Internet electronic mail: readers_comment@zk3.dec.com A Reader’s Comment form is located on your system in the following location: /usr/doc/readers_comment.txt...
Page 23 Italic (slanted) type indicates variable values, file placeholders, and function argument names. A vertical ellipsis indicates that a portion of an example that would normally be present is not shown. A cross-reference to a reference page includes the appropriate section number in parentheses. For example, cat indicates that you can find information on the cat command in Section 1 of...
Page 25: 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 26: Memory Requirements
interconnect, you can more easily alter or expand your cluster’s hardware configuration as newer and faster technologies become available. 1.2 Memory Requirements Cluster members require a minimum of 128 MB of memory. 1.3 Minimum Disk Requirements This section provides an overview of the minimum file system or disk requirements for a two-node cluster.
Page 27: Clusterwide Disk(S)
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. See the TruCluster Server Cluster Administration manual for more information.
Page 28: Quorum Disk
partitions. You can move the swap partition off the member boot disk. See the TruCluster Server Cluster Administration manual for more information. 1.3.1.4 Quorum Disk The quorum disk allows greater availability for clusters consisting of two members. Its h partition contains cluster status and quorum information. See the TruCluster Server Cluster Administration manual for a discussion of how and when to use a quorum disk.
Page 29 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 30: 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 31: Two-Node Clusters Using An Ultrascsi Ba356 Storage Shelf And Minimum Disk Configurations
• 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.5.4). •...
Page 32: Minimum Two-Node Cluster With Ultrascsi Ba356 Storage Unit
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 33: 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. 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 34: Two-Node Cluster With Two Ultrascsi Ds-Ba356 Storage Units
UNIX Version 5.0, 16 devices are supported on a SCSI bus. Therefore, multiple BA356 storage units can be used on the same SCSI bus to 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 35: Two-Node Configurations With Ultrascsi Ba356 Storage Units And Dual Scsi Buses
file systems and the data disks across SCSI buses, removing the single SCSI bus as a single point of failure for these file systems. 1.5.3 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.
Page 36: 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 37: Cluster Configuration With Hsz70 Controllers In Transparent
instead of the HSZ70. The array controllers can be configured as a dual redundant pair. If you want the capability to fail over from one controller to another controller, you must install the second controller. Also, you must set the failover mode. Figure 1–6: Cluster Configuration with HSZ70 Controllers in Transparent Failover Mode Network...
Page 38: 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.5.5 Creating a NSPOF Cluster To create a no-single-point-of-failure (NSPOF) cluster: •...
Page 39: Nspof Cluster Using Hsz70S In Multiple-Bus Failover
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 40: 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 Memory Channel Interface Memory Memory Channel Channel KGPSA KGPSA KGPSA KGPSA Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A Port 1 Port 2 HSG 80 Controller B Port 2...
Page 41 Prepare the shared storage by installing disks and configuring any RAID controller subsystems (see Chapter 3, Chapter 6, and Chapter 9 and the documentation for the StorageWorks enclosure or RAID controller). Install signal converters in the StorageWorks enclosures, if applicable (see Chapter 3 and Chapter 9).
Page 43: Hardware Requirements And Restrictions
Y cables, and terminators. For the latest information about supported hardware see the AlphaServer options list for your system at the following URL: http://www.compaq.com/alphaserver/products/options.html 2.1 TruCluster Server Member System Requirements The requirements for member systems in a TruCluster Server cluster are as follows: •...
Page 44 arbitration enabled when connecting four-member systems to a common SCSI bus. • The following items pertain to the AlphaServer GS80/160/320 systems: – Hot swapping modules is not supported. – High power peripheral component interconnect (PCI) modules (approximately 25 watts or greater) must be placed in PCI slots with 1 inch module pitch;...
Page 45: Memory Channel Restrictions
2.2 Memory Channel Restrictions The Memory Channel interconnect is used for cluster communications between the member systems. There are currently three versions of the Memory Channel product; Memory Channel 1, Memory Channel 1.5, and Memory Channel 2. 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 46 • In an MC2 configuration, you can use a CCMFB optical converter in conjunction with the MC2 CCMAB module to increase the distance between systems. • The BN34R fiber optics cable, used to connect two CCMFB optical converters, is available in 10-meter (BN34R-10) and 31-meter (BN34R-31) lengths.
Page 47: Host Bus Adapter Restrictions
• The StorageWorks Modular Array 6000 (MA6000) is built with the new StorageWorks packaging, which consists of: – A Compaq StorageWorks enclosure Model 2100, which houses dual-redundant HSG60 controllers. – The 14-bay drive shelves (Compaq StorageWorks enclosure Model 4200).
Page 48 The StorageWorks Modular Array 8000 (MA8000) and Enterprise Modular Array 12000 (EMA12000) are also built with the new StorageWorks packaging, which consists of: – A Compaq StorageWorks enclosure Model 2200, which houses dual-redundant HSG80 controllers. – The 14-bay drive shelves (Compaq StorageWorks enclosure Model 4200).
Page 49 Model 4254 disk enclosures is 42. The Model 4214R and Model 4254 disk enclosures support only the new Compaq hot-pluggable wide-UltraSCSI low voltage differential (LVD) disk drives. For more information on configuring the MA8000/EMA12000, see the Compaq StorageWorks Modular Array Configuration Guide.
Page 50: Kzpsa-Bb Scsi Adapter Restrictions
• A maximum of three cascaded switches is supported, with a maximum of two hops between switches. The maximum hop length is 10 km longwave single-mode or 500 meters via shortwave multimode Fibre Channel cable. • Tru64 UNIX Version 5.1 limits the number of Fibre Channel targets to 126.
Page 51: Kzpba-Cb Scsi Bus Adapter Restrictions
AlphaServer 800, 1000, 1000A, 2000, 2100, or 2100A systems support the variable), you must set the bus_probe_algorithm console variable to new by entering the following command: >>> set bus_probe_algorithm new Use the show bus_probe_algorithm console command to determine if your system supports the variable. If the response is null or an error, there is no support for the variable.
Page 52: Scsi Signal Converters
RAID array controllers require the minimum Array Controller Software (ACS) shown in Table 2–1. Table 2–1: RAID Controller Minimum Required Array Controller Software RAID Controller Minimum Required Array Controller Software HSZ20 HSZ40 HSZ50 HSZ70 8.3-1 HSZ80 HSG60 HSG80 RAID controllers can be configured with the number of SCSI IDs as shown in Table 2–2.
Page 53: Ds-Dwzzh-03 And Ds-Dwzzh-05 Ultrascsi Hubs
______________________ Note _______________________ We could list the UltraSCSI hubs because they contain a DOC (DWZZA on a chip) chip, but they are discussed separately in Section 2.7. The restrictions for SCSI signal converters are as follows: • If you remove the cover from a standalone unit, be sure to replace the star washers on all four screws that hold the cover in place when you reattach the cover.
Page 54: Scsi Cables
SCSI bus length. Table 2–3 describes each supported cable and the context in which you would use the cable. Some Compaq equivalent 6-3 part numbers are not provided. 2–12 Hardware Requirements and Restrictions...
Page 55: Supported Scsi Cables
Connects two VHDCI trilinks to each other or an UltraSCSI hub to a VHDCI trilink on an HSZ70 or HSZ80 199629-002 or Two high 50-pin Connect a Compaq 20/40 GB DLT 189636-002 HD to Tape Drive to a DWZZB-AA 68-pin 146745-003 or Two high...
Page 56: 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 or High 68-pin Terminates an H885-AA trilink connector, 330563-001 BN21W-0B Y cable, or an ESL9326D Enterprise Library tape drive.
Page 57: 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 58: Shared Scsi Bus Configuration Requirements
This chapter discusses the following topics: • Shared SCSI bus configuration requirements (Section 3.1) • SCSI bus performance (Section 3.2) • SCSI bus device identification numbers (Section 3.3) • SCSI bus length (Section 3.4) • SCSI bus termination (Section 3.5) •...
Page 59: Scsi Bus Performance
storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storage arrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves are supported with UltraSCSI host adapters and host RAID controllers as long as they contain no UltraSCSI disks. • UltraSCSI drives and fast wide drives can be mixed together in an UltraSCSI BA356 shelf (see Chapter 9).
Page 60: Transmission Methods
cable or a backplane, and cable or backplane connectors. Each UltraSCSI bus segment must have a terminator at each end of the bus segment. Up to two UltraSCSI bus segments may be coupled together with UltraSCSI hubs or signal converters, increasing the total length of the UltraSCSI bus. 3.2.2 Transmission Methods Two transmission methods can be used in a SCSI bus: •...
Page 61: Data Path
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. The DS-BA35X-DA personality module contains a signal converter for the UltraSCSI BA356.
Page 62: Scsi Bus Length
______________________ 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). Use the following priority order to assign SCSI IDs to the SCSI bus adapters connected to a shared SCSI bus: 7-6-5-4-3-2-1-0-15-14-13-12-11-10-9-8 This order specifies that 7 is the highest priority, and 8 is the lowest priority.
Page 63: Terminating The Shared Scsi Bus When Using Ultrascsi Hubs
Because of the cable length limit, you must plan your hardware configuration carefully, and ensure that each SCSI bus meets the cable limit guidelines. In general, you must place systems and storage shelves as close together as possible and choose the shortest possible cables for the shared bus. 3.5 Terminating the Shared SCSI Bus When Using UltraSCSI Hubs You must properly connect devices to a shared SCSI bus.
Page 64: Ultrascsi Hubs
Figure 3–1 shows a VHDCI trilink connector (UltraSCSI), which you may attach to an HSZ70 or HSZ80. Figure 3–1: VHDCI Trilink Connector (H8861-AA) CXO5744A 3.6 UltraSCSI Hubs The DS-DWZZH series UltraSCSI hubs are UltraSCSI signal converters that provide radial connections of differential SCSI bus adapters and RAID array controllers.
Page 65: Ds-Dwzzh-03 Description
• Require that termination power (termpwr) be provided by the SCSI bus host adapters on each SCSI bus segment. _____________________ Note _____________________ The UltraSCSI hubs are designed to sense loss of termination power (such as a cable pull or termpwr not enabled on the host adapter) and shut down the applicable port to prevent corrupted signals on the remaining SCSI bus segments.
Page 66: Ds-Dwzzh-05 Description
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. 3.6.1.2 DS-DWZZH-05 Description The DS-DWZZH-05: • Is a 5.25-inch StorageWorks building block (SBB). • Has five Very High Density Cable Interconnect (VHDCI) differential SCSI bus connectors.
Page 67: Ds-Dwzzh Ultrascsi Hub Maximum Configurations
• The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks. A DS-DWZZH-05 UltraSCSI hub uses the storage shelf only to provide its power and mechanical support (it is not connected to the shelf internal SCSI bus).
Page 68: Ds-Dwzzh-05 Fair Arbitration
3.6.1.2.2 DS-DWZZH-05 Fair Arbitration Although each cluster member system and storage controller connected to an UltraSCSI hub are on separate SCSI bus segments, they all share a common SCSI bus and its bandwidth. As the number of systems accessing the storage controllers increases, it is likely that the adapter with the highest priority SCSI ID will obtain a higher proportion of the UltraSCSI bandwidth.
Page 69: Ds-Dwzzh-05 Address Configurations
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. With either addressing mode, if fair arbitration is enabled, each hub port is assigned a specific SCSI ID. This allows the fair arbitration logic in the hub to identify the SCSI ID of the device participating in the arbitration phase of the fair arbitration cycle.
Page 70 Figure 3–3: DS-DWZZH-05 Rear View ZK-1448U-AI 3–14 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware...
Page 71: 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 72: 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 73: 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 74: 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 75 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 76 Figure 3–5 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ70 RAID array controller configured for transparent failover. 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)
Page 77: 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 78: 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 79 Install H8861-AA VHDCI trilink connectors (with terminators) on: • HSZ70 controller A and controller B • HSZ80 controller A Port 1 (2) and controller B Port 1 (2) ___________________ Note ___________________ You must use the same port on each HSZ80 controller. 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)
Page 80: Failover Mode
Figure 3–7 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ70 configured for multiple-bus failover. Figure 3–7: TruCluster Server Configuration with HSZ70 in Multiple-Bus Failover Mode Network Member Member System Memory System Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6)
Page 81: Failover Mode
Figure 3–8 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ80 configured for multiple-bus failover. 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)
Page 83: 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 84: 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 85: 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 86: 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 software & drivers, then select All Products under the Alpha Systems heading. Select Alpha Firmware updates, then select the appropriate system.
Page 87: 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 88: 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 89: 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 90 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 91 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 92: Displaying Kzpba-Cb Adapters With The Show Console
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 93 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 94 Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.) Bus 02 Slot 02: DE500-AA Network Controller ewa0.0.0.2002.0 00-06-2B-00-0A-48 PCI Hose 01 Bus 00 Slot 07: DEC PCI FDDI fwa0.0.0.7.1 08-00-2B-B9-0D-5D Bus 00 Slot 08: DEC PCI MC Rev: 22, mca0 Bus 00 Slot 09: DEC PCI MC Rev: 22, mcb0...
Page 95: Displaying Configuration On An Alphaserver 8200
Example 4–3 shows the output from the show config console command entered on an AlphaServer 8200 system. Example 4–3: Displaying Configuration on an AlphaServer 8200 >>> show config Name Type Mnemonic TLSB KN7CC-AB 8014 0000 kn7cc-ab0 MS7CC 5000 0000 ms7cc0 KFTIA 2020 0000...
Page 96: 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 97: 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 98: 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 99: 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 100: 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 101: 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 102: Setting The Memory Channel Adapter Jumpers
____________________ Note _____________________ If you are installing SCSI or network adapters, you may want to complete all hardware installation before powering up the systems to run Memory Channel diagnostics. Section 5.7 provides procedures for upgrading from redundant MC1 interconnects to MC2 interconnects. 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 103: Mc2 Jumpers
Table 5–1: MC1 and MC1.5 Jumper Configuration (cont.) If hub mode is: Jumper: Example: Virtual: VH0 Pins 2 to 3 1 2 3 Virtual: VH1 None needed; store the jumper on pin 1 or 3 1 2 3 If you are upgrading from virtual hub mode to standard hub mode (or from standard hub mode to virtual hub mode), be sure to change the jumpers on all Memory Channel adapters on the rail.
Page 104: Mc2 Jumper Configuration
See the TruCluster Server Cluster Administration manual for more information on failover pairs. The MC2 jumpers are described in Table 5–2. Table 5–2: MC2 Jumper Configuration Jumper: Description: Example: J1: Hub Mode Standard: Pins 1 to 2 1 2 3 VH0: Pins 2 to 3 1 2 3 VH1: None needed;...
Page 105: Mc2 Linecard Jumper Configurations
Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: J5: AlphaServer 8x00 mode selected: 8x00 Mode Pins 1 to 2 1 2 3 8x00 mode not selected: Pins 2 to 3 1 2 3 J10 and J11: Fiber Fiber Off: Pins 1 to 2 Optics Mode Enable Fiber On: Pins 2 to 3 pins...
Page 106: Installing The Memory Channel Adapter
5.2 Installing the Memory Channel Adapter Install the Memory Channel adapter in an appropriate peripheral component interconnect (PCI) slot (see Section 2.2). Secure the module at the backplane. Ensure that the screw is tight to maintain proper grounding. The Memory Channel adapter comes with a straight extension plate. This fits most systems;...
Page 107: Installing The Memory Channel Hub
5.4 Installing the Memory Channel Hub You may use a hub in a two-node TruCluster Server cluster, but the hub is not required. When there are more than two systems in a cluster, you must use a Memory Channel hub as follows: •...
Page 108: Connecting Mc1 Or Mc1.5 Link Cables In Virtual Hub Mode
______________________ Note _______________________ Do not connect an MC1 or MC1.5 link cable to an MC2 module. 5.5.1.1 Connecting MC1 or MC1.5 Link Cables in Virtual Hub Mode For an MC1 virtual hub configuration (two nodes in the cluster), connect the BC12N-10 link cables between the Memory Channel adapters installed in each of the systems.
Page 109: Installing The Mc2 Cables
Figure 5–1 shows Memory Channel adapters connected to linecards that are in the same slot position in the Memory Channel hubs. Figure 5–1: Connecting Memory Channel Adapters to Hubs Memory Channel hub 1 System A Memory Channel Linecards hub 2 Memory Channel adapters...
Page 110: 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 111: 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 112 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 113: 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 114: Upgrading Memory Channel Adapters
5.7 Upgrading Memory Channel Adapters If you have a TruCluster Server configuration with redundant MC1 interconnects and want to upgrade to MC2 interconnects, you can do so without shutting down the entire cluster. When rolling from MC1 interconnects, which use 128 MB Memory Channel address space, to MC2, which uses either 128 or 512 MB Memory Channel address space, all Memory Channel adapters must be operating at 128 MB Memory Channel address space (the default) until the last adapter has been...
Page 115: Adding A Memory Channel Interconnect Or Rolling From A Dual, Redundant Mc1 Interconnect To Mc2 Interconnects
Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects Step Action Refer to: If desired, manually relocate all applications from the TruCluster cluster member that will be shut down using the cluster Server Cluster application availability (CAA) caa_relocate command.
Page 116 Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: ______________________ Note ______________________ If you set the J3 jumpers for 128 MB because the other interconnect is MC1, and then later on decide to upgrade to dual, redundant MC2 hardware using 512 MB address space, you will have to reset the jumpers.
Page 117 Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: Standard Hub Configuration: Remove the MC1 adapter and install the MC2 adapter in Figure 5–4, and one system, and on one rail at a time. Use a BN39B-10 Figure 5–5 link cable to connect the new MC2 adapter to the linecard in the MC2 hub that corresponds to the same linecard that...
Page 118 Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects (cont.) Step Action Refer to: On one member system, use the sysconfig command to reconfigure the Memory Channel kernel subsystem to initiate the use of 512 MB address space. The configuration change is propagated to the other cluster member systems: /sbin/sysconfig -r rm rm_use_512=1 ______________________...
Page 119 (dbx) p rm_adapters[1]->rmp_prail_va->rmc_size [0] 16384 [1] 0 [2] 16384 [3] 0 [4] 16384 [5] 0 [6] 0 [7] 0 Check the size of a logical rail. The logical rail is operating at 128 MB (16384 8-KB pages). Verify the jumper settings for the member systems on the. first physical rail.
Page 120: Mc1 To Mc2 Virtual Hub Rolling Upgrade
Figure 5–2 shows a dual, redundant virtual hub configuration using MC1 hardware being upgraded to MC2. Figure 5–2: MC1 to MC2 Virtual Hub Rolling Upgrade AlphaServer AlphaServer Member Member System 1 System 2 AlphaServer AlphaServer Member Member System 1 System 2 AlphaServer AlphaServer Member...
Page 121: Configuration
Figure 5–3 through Figure 5–8 show a three-node standard hub configuration being upgraded from MC1 to MC2. Figure 5–3: MC1 to MC2 Standard Hub Rolling Upgrade: Initial Configuration MC1 Hub AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 MC1 Hub ZK-1522U-AI...
Page 122: Module Replaced
Figure 5–4: MC1 to MC2 Standard Hub Rolling Upgrade: First MC1 Module Replaced MC1 Hub MC2 Hub 0/opto AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 MC1 Hub ZK-1523U-AI 5–22 Setting Up the Memory Channel Cluster Interconnect...
Page 123: Mc1 Adapter In Second System
Figure 5–5: MC1 to MC2 Standard Hub Rolling Upgrade: Replace First MC1 Adapter in Second System MC2 Hub opto 0/opto only AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 MC1 Hub ZK-1524U-AI Setting Up the Memory Channel Cluster Interconnect 5–23...
Page 124: System Memory Channel Adapters
Figure 5–6: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Third System Memory Channel Adapters MC2 Hub 1/opto opto only 0/opto AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 1/opto MC2 Hub MC1 Hub ZK-1525U-AI 5–24 Setting Up the Memory Channel Cluster Interconnect...
Page 125: Mc1 In Second System
Figure 5–7: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Second MC1 in Second System MC2 Hub 0/opto opto only 1/opto AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 1/opto opto only MC2 Hub ZK-1526U-AI Setting Up the Memory Channel Cluster Interconnect 5–25...
Page 126: Configuration
Figure 5–8: MC1 to MC2 Standard Hub Rolling Upgrade: Final Configuration MC2 Hub 1/opto opto only 0/opto AlphaServer AlphaServer Member Member System 2 System 1 AlphaServer Member System 3 0/opto opto 1/opto only MC2 Hub ZK-1527U-AI 5–26 Setting Up the Memory Channel Cluster Interconnect...
Page 127: 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.1 configuration. The information includes an example storageset configuration, 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...
Page 128: Procedure For Installation Using Fibre Channel Disks
• The steps necessary to install and configure the Fibre Channel hardware (Section 6.5). • The steps necessary to install the base operating system and cluster software using disks accessible over the Fibre Channel hardware (Section 6.6). • Changing the HSG80 from transparent to multiple-bus failover mode (Section 6.7).
Page 129 64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide • Compaq StorageWorks Fibre Channel Storage Switch User’s Guide • Compaq StorageWorks SAN Switch 8 Installation and Hardware Guide • Compaq StorageWorks SAN Switch 16 Installation and Hardware Guide • Compaq StorageWorks Fibre Channel SAN Switch 8-EL Installation and Hardware Guide •...
Page 130: Fibre Channel Overview
• Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide • MA6000 HSG60 Array Controller ACS Version 8.5 Solution Software for Compaq Tru64 UNIX Installation and Configuration Guide • Compaq StorageWorks HSG60/HSG80 Array Controller ACS Version 8.5 Maintenance and Service Guide •...
Page 131: Basic Fibre Channel Terminology
6.2.1 Basic Fibre Channel Terminology The following list describes the basic Fibre Channel terminology: Frame All data is transferred in a packet of information called a frame. A frame is limited to 2112 bytes. If the information consists of more than 2112 bytes, it is divided up into multiple frames.
Page 132: Fibre Channel Topologies
Link The physical connection between an N_Port and another N_Port or an N_Port and an F_Port. A link consists of two connections, one to transmit information and one to receive information. The transmit connection on one node is the receive connection on the node at the other end of the link.
Page 133: Fabric
Figure 6–1: Point-to-Point Topology Node 2 Node 1 Transmit Transmit N_Port N_Port Receive Receive ZK-1534U-AI 6.2.2.2 Fabric The fabric topology provides more connectivity than point-to-point topology. The fabric topology can connect up to 2 ports. The fabric examines the destination address in the frame header and routes the frame to the destination node.
Page 134: Arbitrated Loop Topology
Figure 6–2: Fabric Topology Node 1 Node 3 Transmit Transmit Transmit Transmit F_Port F_Port N_Port N_Port Receive Receive Receive Receive Fabric Node 2 Node 4 Transmit Transmit Transmit Transmit F_Port F_Port N_Port N_Port Receive Receive Receive Receive ZK-1536U-AI 6.2.2.3 Arbitrated Loop Topology In an arbitrated loop topology, frames are routed around a loop created by the links between the nodes.
Page 135: 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 Version 5.1 or TruCluster Server Version 5.1 products.
Page 136: Failover Mode
6.3.1 Fibre Channel Cluster Configurations for Transparent Failover Mode With transparent failover mode: • The hosts do not know a failover has taken place (failover is transparent to the hosts). • The units are divided between an HSG80 port 1 and port 2. •...
Page 137: Failover Mode
In transparent failover, units D00 through D99 are accessed through port 1 of both controllers. Units D100 through D199 are accessed through port 2 of both HSG80 controllers (with the limit of a total of 128 storage units). You cannot achieve a no-single-point-of-failure (NSPOF) configuration using transparent failover.
Page 138: Multiple-Bus Nspof Configuration Number 1
Therefore, you want to ensure that both HSG80 controllers start at the same time under all circumstances so that the controller sees its own preferred units. Figure 6–5, Figure 6–6, and Figure 6–7 show three different multiple-bus NSPOF cluster configurations. The only difference is the fiber-optic cable connection path between the switch and the HSG80 controller ports.
Page 139: Multiple-Bus Nspof Configuration Number 2
Figure 6–6: Multiple-Bus NSPOF Configuration Number 2 Member Member System System Memory Channel Interface Memory Memory Channel Channel KGPSA KGPSA KGPSA KGPSA Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A Port 1 Port 2 HSG 80 Controller B Port 1 Port 2 RA8000/ESA12000...
Page 140: Zoning
Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 Member Member System System Memory Channel Interface Memory Memory Channel Channel KGPSA KGPSA KGPSA KGPSA Fibre Channel Switch Fibre Channel Switch HSG 80 Controller A Port 1 Port 2 HSG 80 Controller B Port 2 Port 1 RA8000/ESA12000...
Page 141: Cascaded Switches
Figure 6–8: A Simple Zoned Configuration Memory Memory Memory Memory Channel Channel Channel Channel Cluster 1 Cluster 1 Cluster 2 Cluster 2 Member Member Member Member System 1 System 2 System 1 System 2 KGPSA KGPSA KGPSA KGPSA 8 10 12 14 Fibre Channel Switch 9 11 13 15...
Page 142: 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 to support Tru64 UNIX or a TruCluster Server configuration using Fibre Channel storage. 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 143: Installing The Switch
The DS-DSGGC-AA has a default IP address of 10.77.77.77. You may need to change this IP address before you connect the switch to the network. The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) or eight (DS-DSGGA-AB) plug-in interface modules. Each interface module in turn supports two Gigabit Interface Converter (GBIC) modules.
Page 144: Managing The Fibre Channel Switches
Compaq StorageWorks Fibre Channel SAN Switch 8-EL Installation and Hardware Guide For more information on managing a Fibre Channel switch, see the Compaq StorageWorks Fibre Channel SAN Switch Management Guide. For more information on the SAN switch fabric operating system, see the...
Page 145: Using The Switch Front Panel
6.5.1.2.1 Using the Switch Front Panel The switch front panel consists of a display and four buttons. The display is normally not active, but it lights up when any of the buttons are pressed. The display has a timer. After approximately 30 seconds of inactivity, the display will go out.
Page 146 ____________________ Note _____________________ Pressing the down button selects the next lower top-level menu. The top-level menus are: Configuration Menu Operation Menu Status Menu Test Menu 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.
Page 147: Setting The Ds-Dsggb-Aa And Ds-Dsggc-Aa
10. Use the Tab/Esc button to select Yes. Press Enter to reboot the switch and execute the POST tests. ____________________ Note _____________________ After changing any configuration menu settings, you must reboot the switch for the change to take effect. Refer to the switch documentation for information on other switch configuration settings.
Page 148: Logging In To The Switch With A Telnet Connection
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 149: Setting The Switch Name Via Telnet Session
______________________ Notes ______________________ Use Ctrl/H to correct typing errors. Use the logout command to log out from any telnet connection. 6.5.1.2.5 Setting the Switch Name via Telnet Session After you set the IP address and subnet mask, you can use a telnet session to log in to the switch to complete other switch management functions or monitor switch status.
Page 150: Setting The Kgpsa-Bc Or Kgpsa-Ca To Run On A Fabric
• 64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide _____________________ Caution _____________________ Static electricity can damage modules and electronic components. We recommend using a grounded antistatic wrist strap and a grounded work surface when handling modules. If necessary, install the mounting bracket on the KGPSA-BC module. Place the mounting bracket tabs on the component side of the board.
Page 151 AS8x00, GS60, GS60E, and GS140. Set the console to diagnostic mode as follows: P00>>> set mode diag Console is in diagnostic mode P00>>> The console remains in wwid manager mode (or diagnostic mode for the AS1200, AS4x00, AS8x00, GS60, GS60E, and GS140 systems), and you cannot boot until the system is re-initialized.
Page 152 The Link is down message indicates that one of the adapters is not available, probably due to its not being plugged into a switch. The warning message Nvram read failed indicates that the KGPSA NVRAM has not been initialized and formatted. The next topology will always be UNAVAIL for the host bus adapter that has an unformatted NVRAM.
Page 153: Obtaining The Worldwide Names Of Kgpsa Adapters
This display shows that the current topology for both KGPSA host bus adapters is LOOP, but will be FABRIC after the next initialization. A system initialization configures the KGPSAs to run on a fabric. 6.5.2.3 Obtaining the Worldwide Names of KGPSA Adapters A worldwide name is a unique number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by the manufacturer prior to shipping.
Page 154: Setting Up The Hsg80 Array Controller For Tru64 Unix
This section covers setting up the HSG80 controller for operation with Tru64 UNIX Version 5.1 and TruCluster Server Version 5.1. 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 155 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 156 Prevents the command line interpreter (CLI) from reporting a misconfiguration error resulting from not having a failover mode set. Puts the controller pair into multiple-bus failover mode. Ensure that you copy the configuration information from the controller known to have a good array configuration. __________________ Note ___________________...
Page 157: Determine Hsg80 Connection Names
Example 6–1: Determine HSG80 Connection Names HSG80 show connection Connection Unit Name Operating system Controller Port Address Status Offset !NEWCON49 TRU64_UNIX THIS 230813 OL this HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON50 TRU64_UNIX THIS 230813 OL this HOST_ID=1000-0000-C920-DA01 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON51 TRU64_UNIX THIS 230913 OL this HOST_ID=1000-0000-C920-EDEB ADAPTER_ID=1000-0000-C920-EDEB !NEWCON52...
Page 158 ____________________ Note _____________________ You can change the connection name with the HSG80 CLI RENAME command. For example, assume that member system pepicelli has two KGPSA Fibre Channel host bus adapters, and that the worldwide name for KGPSA pga is 1000-0000-C920-DA01. Example 6–1 shows that the connections for pga are !NEWCON49, !NEWCON50, !NEWCON54, and !NEWCON56.
Page 159: Obtaining The Worldwide Names Of Hsg80 Controller
____________________ Note _____________________ If the fiber-optic cables are not properly installed, there will be inconsistencies in the connections shown. 14. Set up the storage sets as required for the applications to be used. An example is provided in Section 6.6.1.1. 6.5.3.1 Obtaining the Worldwide Names of HSG80 Controller The RA8000 or ESA12000 is assigned a worldwide name when the unit is manufactured.
Page 160: Installing Tru64 Unix And Trucluster Server Software Using
– Controller B port 1 — 5000-1FE1-0000-0D63 – Controller B port 2 — 5000-1FE1-0000-0D64 Because the HSG80 controller’s configuration information and worldwide name is stored in nonvolatile random-access memory (NVRAM) on the controller, there are different procedures for replacing HSG80 controllers in an RA8000 or ESA12000: •...
Page 161 to each of those devices. For example, to boot from storage unit D1 as presented by the HSG80 controller, the AlphaServer console requires a device name such as dga133.1002.0.1.0 that identifies the storage unit. In addition, dga133.1002.0.1.0 must be reachable via a valid Fibre Channel connection.
Page 162: Before You Install
• Reset the bootdef_dev console environment variable to provide multiple boot paths (Section 6.6.6). • Add additional systems to the cluster Section 6.6.7). If you are installing the Tru64 UNIX operating system or TruCluster Server software, follow the procedure in Chapter 1. 6.6.1 Before You Install The following sections cover the preliminary steps that must be completed before you install Tru64 UNIX and TruCluster Server on Fibre Channel...
Page 163: Setting Up The Mirrorset
Table 6–2 contains the necessary information to convert from the HSG80 unit numbers to /dev/disk/dskn and device names for the example configuration. A blank table (Table A–1) is provided in Appendix A for use in an actual installation. One mirrorset, the BOOT-MIR mirrorset, will be used for the Tru64 UNIX and cluster member system boot disks.
Page 164 Example 6–2: Setting Up the Mirrorset (cont.) HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 HSG80> CREATE_PARTITION BOOT-MIR SIZE=25 HSG80> CREATE_PARTITION BOOT-MIR SIZE=LARGEST HSG80> CREATE_PARTITION CROOT-MIR SIZE=5 HSG80> CREATE_PARTITION CROOT-MIR SIZE=15 HSG80> CREATE_PARTITION CROOT-MIR SIZE=40 HSG80> CREATE_PARTITION CROOT-MIR SIZE=LARGEST HSG80> SHOW BOOT-MIR Name Storageset Uses Used by ---------------------------------------------------------------------...
Page 165 Create the BOOT-MIR mirrorset using disks 30200 and 30300 and the CROOT-MIR mirrorset using disks 40000 and 40100. Initialize the BOOT-MIR and CROOT-MIR mirrorsets. If you want to set any initialization switches, you must do so in this step. The BOOT-MIR mirrorset will be used for the Tru64 UNIX and cluster member system boot disks.
Page 166: Storagesets
6.6.1.2 Adding Units and Identifiers to the HSG80 Storagesets After you have created the storagesets (mirrorsets and partitions), assign a unit number to each partition and set a unique identifier as shown in Example 6–3. The steps performed in Example 6–3 include: •...
Page 167 Example 6–3: Adding Units and Identifiers to the HSG80 Storagesets (cont.) again enable the ones specified HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON68,!NEWCON74,!NEWCON76,!NEWCON77 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit. If you wish to enable ONLY the host(s) specified, disable all access paths (DISABLE_ACCESS=ALL), then again enable the ones specified HSG80>...
Page 168 Record the unit name of each partition with the intended use for that partition (see Table 6–2). Set an identifier for each storage unit. Use any number between 1 and 9999. To keep your storage naming as consistent and simple as possible, consider using the unit number of the unit as its UDID.
Page 169: Set The Device Unit Number
unwanted system. Record the identifier and worldwide name for later use. Table 6–2 is a sample table filled in for the example. Table A–1 in Appendix A is a blank table for your use in an actual installation. ____________________ Note _____________________ At this point, even though the table is filled in, we do not yet know the device names or dskn numbers.
Page 170 UNIX Version 5.1 installation disk or cluster member system boot disks. Setting the device unit number allows the installation scripts to recognize a Fibre Channel disk. To set the device unit number for a Fibre Channel device, follow these steps: Use the HSG80 show unit command to obtain the user defined identifier (UDID) for the HSG80 storageset to be used as the Tru64 UNIX Version 5.1 installation disk or cluster member system boot disks.
Page 171: To The Console
console command, it would not detect the Fibre Channel devices connected to the HSG80. Example 6–4: Displaying the UDID and Worldwide Names of Devices Known to the Console P00>>> wwidmgr -show wwid [0] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-0008 (ev:none) [1] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-0007 (ev:none) [2] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-0009 (ev:none) [3] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-000a (ev:none) [4] UDID:-1 WWID:01000010:6000-1fe1-0001-4770-0009-9171-3579-000b (ev:none)
Page 172 or wwidmgr -set command. In this example, none of the wwidn environment variables is set. Look through the wwidmgr -show wwid display (see Example 6–4) and locate the UDID for the Tru64 UNIX disk (133) and each member system boot disks (131, 132) to ensure the storage unit is seen. As a second check, compare the worldwide name values.
Page 173: Number
Example 6–5: Using the wwidmgr quickset Command to Set the Device Unit Number P00>>> wwidmgr -quickset -udid 133 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d60-0009-8080-0434-002e via adapter: via fc nport: connected: dga133.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 5000-1fe1-0000-0d63 dga133.1004.0.1.0 pga0.0.0.1.0...
Page 174: Displaying The Available Boot Devices
The disks are not reachable and you cannot boot until after the system is initialized. If you have not set the UDID, you cannot set the device unit number as shown in Example 6–5. You have to use the quickset command with the item number displayed by the wwidmgr -show wwid command (see Example 6–4).
Page 175: Set The Bootdef_Dev Console Environment Variable For Tru64 Unix Installation
$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 176 To set the bootdef_dev console environment variable for the Tru64 UNIX installation when booting from a Fibre Channel device, follow these steps: Obtain the device name for the Fibre Channel storage unit where you will install the Tru64 UNIX operating system. The device name shows up in the reachability display as shown in Example 6–5 with a Yes under the connected column.
Page 177: Install The Tru64 Unix Operating System
6.6.2 Install the Tru64 UNIX Operating System After reading the TruCluster Server Software Installation manual, and using the Tru64 UNIX Installation Guide as a reference, boot from the CD-ROM and install the Tru64 UNIX Version 5.1 operating system. When the installation procedure displays the list of disks available for operating system installation as shown here, look for the identifier in the Location column.
Page 178 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 179: Label The Disks To Be Used To Create The Cluster
Search the display for the UDIDs (or worldwide names) for each of the cluster installation disks and record the /dev/disk/dskn values. If you used the grep utility to search for a specific UDID, for example hwmgr -view dev | grep "IDENTIFIER=131" repeat the command to determine the /dev/disk/dskn for each of the remaining cluster disks.
Page 180 To reset the bootdef_dev console environment variable, follow these steps: Obtain the device name and worldwide name for the Fibre Channel unit from where you will boot cluster member system 1 (see Table 6–2). Check the reachability display (Example 6–5) provided by the wwidmgr -quickset or the wwidmgr -reachability commands for the device names that can access the storage unit from which you are booting.
Page 181: Add Additional Systems To The Cluster
or wwidmgr -show reachability). You must initialize the system to use any of the device names in the bootdef_dev variable as follows: P00>>> set bootdef_dev \ dga131.1001.0.1.0,dga131.1004.0.1.0,\ dgb131.1002.0.2.0,dgb131.1003.0.2.0 POO>>> init ______________________ Note _______________________ 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.
Page 182 Set the bootdef_dev console environment variable to one reachable path (Yes in the connected column of Example 6–7) to the member system boot disk: P00>>> set bootdef_dev dga132.1002.0.1.0 Boot genvmunix on the newly added cluster member system. Each installed subset will be configured and a new kernel will be built and installed.
Page 183: Converting The Hsg80 From Transparent To Multiple-Bus
dga132.1004.0.1.0 dgb132.1002.0.2.0 dgb132.1003.0.2.0 dga132.1001.0.1.0 Path from host bus adapter A to controller A port 1 Path from host bus adapter B to controller A port 2 Path from host bus adapter B to controller B port 1 Path from host bus adapter A to controller B port 2 Set the bootdef_dev console environment variable for member system 2 boot disk to a comma separated list of several of the boot path(s) that show up as connected in the reachability display...
Page 184: Overview
6.7.1 Overview The change in failover modes cannot be accomplished with a simple SET MULTIBUS COPY=THIS HSG80 CLI command because: • Unit offsets are not changed by the HSG80 SET MULTIBUS_FAILOVER COPY=THIS command. Each path between a Fibre Channel host bus adapter in a host computer and an active host port on an HSG80 controller is a connection.
Page 185: Procedure To Convert From Transparent To Multiple-Bus
6.7.2 Procedure to Convert from Transparent to Multiple-bus Failover Mode To change from transparent failover to multiple-bus failover mode by resetting the unit offsets and modifying the systems’ view of the storage units, follow these steps: Shut down the operating systems on all host systems that are accessing the HSG80 controllers you want to change from transparent failover to multiple-bus failover mode.
Page 186 HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON58 TRU64_UNIX OTHER offline HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON59 TRU64_UNIX THIS offline HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON60 TRU64_UNIX OTHER offline HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON61 TRU64_UNIX THIS 210513 OL this HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !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...
Page 187 __________________ Note ___________________ You must set the console to diagnostic mode to use the wwidmgr command for the following AlphaServer systems: AS1200, AS4x00, AS8x00, GS60, GS60E, and GS140. Set the console to diagnostic mode as follows: P00>>> set mode diag Console is in diagnostic mode P00>>>...
Page 188: Using The Emx Manager To Display Fibre Channel Adapter Information
wwid2 wwid3 50001fe100000d64 50001fe100000d62 50001fe100000d63 50001fe100000d61 P00>>> init Set the bootdef_dev console environment variable to the member system boot device. Use the paths shown in the reachability display of the wwidmgr -quickset command for the appropriate device (see Section 6.6.6). Repeat steps a through h on each system accessing devices on the HSG80.
Page 189 nodename 5000-1FE1-0000-0CB0 SCSI tgt id 5 : portname 1000-0000-C920-A7AE nodename 1000-0000-C920-A7AE SCSI tgt id 6 : portname 1000-0000-C920-CD9C nodename 1000-0000-C920-CD9C SCSI tgt id 7 : portname 1000-0000-C921-0D00 (emx0) nodename 1000-0000-C921-0D00 The previous example shows four Fibre Channel devices on this SCSI bus. The Fibre Channel adapter in question, emx0, at SCSI ID 7, is denoted by the presence of the emx0 designation.
Page 190 portname 2004-0060-6900-5A1B nodename 1000-0060-6900-5A1B Present, Logged in, F_PORT, Status of the emx1 link. The connection is a point-to-point fabric (switch) connection, and the link is up. The adapter is on SCSI bus 3 at SCSI ID 7. Both the port name and node name of the adapter (the worldwide name) are provided.
Page 191: Using The Emxmgr Utility Interactively
______________________ Note _______________________ You can use the emxmgr utility interactively to perform any of the previous functions. 6.8.2 Using the emxmgr Utility Interactively Start the emxmgr utility without any command-line options to enter the interactive mode to: • Display the presence of KGPSA Fibre Channel adapters •...
Page 192 Exit ----> 2 emx0 SCSI target id assignments: SCSI tgt id 0 : portname 5000-1FE1-0000-0CB2 nodename 5000-1FE1-0000-0CB0 SCSI tgt id 5 : portname 1000-0000-C920-A7AE nodename 1000-0000-C920-A7AE SCSI tgt id 6 : portname 1000-0000-C920-CD9C nodename 1000-0000-C920-CD9C SCSI tgt id 7 : portname 1000-0000-C921-0D00 (emx0) nodename 1000-0000-C921-0D00 Select Option (against "emx0"):...
Page 193: Using Gs80, Gs160, Or Gs320 Hard Partitions In A Trucluster Server Configuration
Using GS80, GS160, or GS320 Hard Partitions in a TruCluster Server Configuration This chapter contains information about using AlphaServer GS80/160/320 hard partitions in a TruCluster Server Version 5.1 configuration with Tru64 UNIX Version 5.1. 7.1 Overview An AlphaServer GS80/160/320 system provides the capability to define individual subsets of the system’s computing resources.
Page 194: Hardware Requirements For A Hard Partition In A Cluster
7.2 Hardware Requirements for a Hard Partition in a Cluster The TruCluster Server hardware requirements are the same for an AlphaServer GS80/160/320 hard partition as any other system in a cluster. You must have: • A supported host bus adapter connected to shared storage. This may be a KZPBA-CB for parallel SCSI, or a KGPSA-CA for Fibre Channel.
Page 195: Portion Of Qbb Showing I/O Riser Modules
Figure 7–1: Portion of QBB Showing I/O Riser Modules I/O Riser BN39B I/O Riser Cable ZK-1749U-AI ____________________ Notes ____________________ You can have up to two I/O riser modules in a QBB, but you cannot split them across partitions. Each I/O riser has two cable connections (Port 0 and Port 1). Ensure that both cables from one I/O riser are connected to the same PCI drawer (0-R and 1-R in Figure 2–1).
Page 196 We recommend that you connect I/O riser 0 (local I/O riser ports 0 and 1) to the primary PCI drawer that will be the master system control manager (SCM). The BA54A-AA PCI drawer (the bottom PCI drawer in Figure 7–2 and Figure 7–3) is a primary PCI drawer.
Page 197 1) that is higher than the master SCM. Both the master SCM and standby SCM must have the scm_csb_master_eligible SCM environment variable set. __________________ Note __________________ We recommend that you put the primary PCI drawers that contain the master and standby SCM in the power cabinet.
Page 198: Front View Of Expansion And Primary Pci Drawers
types of PCI drawers. It is harder to distinguish the type of PCI drawer from the rear, but slot 1 provides the key. The primary PCI drawer has a standard I/O module in slot 1, and the console and modem ports and USB connections are visible on the module.
Page 199: Configuring Partitioned Gs80, Gs160, Or Gs320 Systems In A Trucluster Configuration
Figure 7–3: Rear View of Expansion and Primary PCI Drawers I/O Riser 1 I/O Riser 0 Expansion PCI Drawer Console Serial Bus Node ID Module PCI Drawer Node ID CSB Connector Local Terminal/ Primary PCI Drawer COM1/Port PCI Drawer Node ID CSB Connector Console Serial Bus Node ID Module...
Page 200 equally well with any number of partitions (as supported by the system type) by modifying the amount and placement of hardware and the SCM environment variable values. ______________________ Notes ______________________ View each partition as a separate system. Ensure that the system comes up as a single partition the first time you turn power on.
Page 201 • Shared storage that is connected to KZPBA-CB (parallel SCSI) or KGPSA-CA (Fibre Channel) host bus adapters. • Network controllers. Install BN39B cables between the local I/O risers on the QBBs in the partition (see Figure 7–1) and the remote I/O risers in the primary and expansion PCI drawer (see Figure 2–1 and Figure 7–3).
Page 202: Defining Hard Partitions With Scm Environment Variables
____________________ Notes ____________________ If the OCP key switch is in the On or Secure position, the system will go through the power-up sequence. In this case, when the power-up sequence terminates, power down the system with the power off SCM command, then partition the system.
Page 203 Example 7–1: Defining Hard Partitions with SCM Environment Variables (cont.) HP_QBB_MASK5 HP_QBB_MASK6 HP_QBB_MASK7 SROM_MASK ff f XSROM_MASK ff ff ff ff ff ff ff ff ff 1 0 0 PRIMARY_CPU PRIMARY_QBB0 AUTO_QUIT_SCM FAULT_TO_SYS DIMM_READ_DIS SCM_CSB_MASTER_ELIGIBLE PERF_MON SCM_FORCE_FSL OCP_TEXT AS GS160 AUTO_FAULT_RESTART SCM_SIZING_TIME Set the number of hard partitions to two.
Page 204: Turning Partition Power On
scm_csb_master_eligible environment variable. The master and standby SCM must be connected to the OCP. The master SCM must have the lowest node ID. Use the node ID address obtained from the show csb SCM command (see Example 7–4). If multiple primary PCI drawers are eligible, the SCM on the PCI drawer with the lowest node ID is chosen as master.
Page 205 Turn on power to partition 1. Transfer control from the SCM firmware to the SRM firmware. ____________________ Note _____________________ If the auto_quit_scm SCM environment variable is set, control is passed to the SRM firmware automatically at the end of the power-up sequence. 12.
Page 206: Determining Alphaserver Gs80/160/320 System Configuration
7.4 Determining AlphaServer GS80/160/320 System Configuration You may be required to reconfigure an AlphaServer GS80/160/320 system that is not familiar to you. Before you start to reconfigure any system, you need to determine: • The number of partitions in the system •...
Page 207 QBB number and console serial bus (CSB) node ID. QBB 0 and 1 (CSB node IDs 30 and 31) are in partition 0. QBB 2 and 3 (CSB node IDs 32 and 33) are in partition 1. CPU module is present, powered up, and has passed self test (P). A dash (-) indicates an empty slot.
Page 208: Displaying Console Serial Bus Information
Console serial bus node ID for PCI drawers. In this example, the first PCI drawer has node ID 10. The second PCI drawer has node ID 11. Note that in this case, the node ID switches are set to 0 and 1. The status of each of the four PCI buses in a PCI drawer.
Page 209 Example 7–4: Displaying Console Serial Bus Information (cont.) CPU3/SROM V5.0-7 IOR0 IOR1 T05.4 (03.24/01:09) T4.0 (07.06) SrvSw: NORMAL XSROM T05.4 (03.24/02:10) CPU0/SROM V5.0-7 CPU1/SROM V5.0-7 CPU2/SROM V5.0-7 CPU3/SROM V5.0-7 T05.4 (03.24/01:09) T4.0 (07.06) SrvSw: NORMAL XSROM T05.4 (03.24/02:10) CPU0/SROM V5.0-7 CPU1/SROM V5.0-7 CPU2/SROM...
Page 210: Updating Gs80/160/320 Firmware
• SCM master: This PCI primary drawer has the master SCM. • SCM slave: The SCM on this PCI primary drawer is a slave and has not been designated as a backup to the master. • CPUn/SROM: Each CPU module has SROM firmware that is executed as part of the power-up sequence.
Page 211 – SCM: One on the standard I/O module of each primary PCI drawer – Power system manager (PSM): One on the PSM module in each QBB – PCI backplane manager (PBM): One on each PCI backplane – Hierarchical switch power manager (HPM): One on the H-switch •...
Page 212 Turn power on to the system to allow SRM firmware execution. The SRM code is copied to memory on the partition primary QBB during the power-up initialization sequence. SRM code is executed out of memory, not the SRM EEPROM on the standard I/O module. SCM_E0>...
Page 213 ___________________ Caution ___________________ Do not abort the update — doing so can cause a corrupt flash image in a firmware module. A complete firmware update takes a long time. The length of time increases proportionally to the number of PCI adapters you have.
Page 215: 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 216: 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 217: 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 218: Hardware Components Used To Create The Configuration
Figure 8–2 shows a TruCluster Server cluster with three shared SCSI buses. One shared bus has a BA350 with a TZ88N-VA at SCSI ID 3. Figure 8–2: Shared SCSI Buses with SBB Tape Drives Network Memory Member System 1 Channel Member System 2 Interface Memory Channel...
Page 219: Setting The Tz88N-Ta Scsi Id
Table 8–2: Hardware Components Used to Create the Configuration Shown in Figure 8–2 (cont.) Description Callout Number DWZZA-VA with H885-AA trilink connector DWZZB-VW with H885-AA trilink connector a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters.
Page 220: Preparing The Tz89 For Shared Scsi Usage
The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with BC19J cables as long as the SCSI bus maximum length is not exceeded. Ensure that the tape drive on the end of the bus is terminated with a H8574-A or H8890-AA terminator.
Page 221: Ds-Tz89N-Vw Scsi Id Switches
Figure 8–3: DS-TZ89N-VW SCSI ID Switches Backplane Interface Connector SCSI ID Switch Pack Snap−in Locking Handles DS−TZ89N−VW The SCSI ID is selected by switch positions, which must be selected before the tape drive is installed in the BA356. Table 8–3 shows the switch settings for the DS-TZ89N-VW.
Page 222: Cabling The Ds-Tz89N-Vw Tape Drives
Table 8–3: 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 223: 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 224: 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 225: 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 226 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 227: 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 228: Compaq 40/80-Gb Dlt Drive
Drive in more detail. 8.4.1 Setting the Compaq 40/80-GB DLT Drive SCSI ID As with any of the shared SCSI devices, the Compaq 40/80-GB DLT Drive SCSI ID must be set to ensure that no two SCSI devices on the shared SCSI bus have the same SCSI ID.
Page 229: Cabling The Compaq 40/80-Gb Dlt Drive
8.4.2 Cabling the Compaq 40/80-GB DLT Drive The Compaq 40/80-GB DLT Drive is connected to a single-ended segment of the shared SCSI bus. Figure 8–6 shows a configuration with a Compaq 40/80-GB DLT Drive for use on a shared SCSI bus.
Page 230: Drive
To achieve system performance capabilities, we recommend that you place no more than two Compaq 40/80-GB DLT Drives on a SCSI bus, and that you place no shared storage on the same SCSI bus with the tape drive. Figure 8–6: Cabling a Shared SCSI Bus with a Compaq 40/80-GB DLT Drive...
Page 231: Preparing The Tz885 For Shared Scsi Usage
Table 8–5: Hardware Components in the Configuration in Figure 8–6 (cont.) Description Callout Number H885-AA trilink connector 189646-001 (0.9 meter cable) or 189646-002 (1.8 meter cable) BN21K-01 or BN21L-01 (1 meter cable) BN21K-02 or BN21L-02 (2 meter cable) 152732-001 LVD terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters.
Page 232: Cabling The Tz885 Tape Drive
8.5.2 Cabling the TZ885 Tape Drive The TZ885 is connected to a single-ended segment of the shared SCSI bus. It is connected to a differential portion of the shared SCSI bus with a DWZZA-AA or DWZZB-AA. Figure 8–7 shows a configuration of a TZ885 for use on a shared SCSI bus.
Page 233: Cabling A Shared Scsi Bus With A Tz885
______________________ Note _______________________ Ensure that there is no conflict with tape drive and host bus adapter SCSI IDs. Figure 8–7: Cabling a Shared SCSI Bus with a TZ885 Network Member Member Memory System System Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) KZPBA-CB (ID 6)
Page 234: Preparing The Tz887 For Shared Scsi Bus Usage
Table 8–6: Hardware Components Used to Create the Configuration Shown in Figure 8–6 (cont.) Description Callout Number H885-AA trilink connector BN21M cable H8574-A terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters.
Page 235: Cabling The Tz887 Tape Drive
Figure 8–8: TZ887 DLT MiniLibrary Rear Panel SCSI ID SCSI ID Selector Switch TZ887 ZK-1461U-AI 8.6.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 236: Cabling A Shared Scsi Bus With A Tz887
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. You can add additional shared SCSI buses with TZ887 tape drives by adding additional DWZZB-AA/TZ887 combinations.
Page 237: Preparing The Tl891 And Tl892 Dlt Minilibraries For Shared Scsi Usage
8.7 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 238 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 239: 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 240 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 241 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 242: Buses
Figure 8–10: TruCluster Server Cluster with a TL892 on Two Shared SCSI Buses Network Memory Channel Member System 1 Member System 2 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) Library DLT1...
Page 243: Preparing The Tl890 Dlt Minilibrary Expansion Unit
8.8 Preparing the TL890 DLT MiniLibrary Expansion Unit The topics in this section provide information on preparing the TL890 DLT MiniLibrary expansion unit with the TL891 and TL892 DLT MiniLibraries 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, and also recommend that no shared storage be placed on the same SCSI...
Page 244: Cabling The Dlt Minilibraries
8.8.2.1 Cabling the DLT MiniLibraries You must make the following connections to render the DLT MiniLibrary system operational: • Expansion unit to the motor mechanism: The motor mechanism cable is about 1 meter long and has a DB-15 connector on each end. Connect it between the connector labeled Motor on the expansion unit to the motor on the pass-through mechanism.
Page 245 ____________________ Notes ____________________ Do not connect a SCSI bus to the SCSI connectors for the library connectors on the base modules. We recommend that no more than two TZ89 tape drives be on a SCSI bus. Figure 8–11 shows a MiniLibrary configuration with two TL892 DLT MiniLibraries and a TL890 DLT MiniLibrary expansion unit.
Page 246: Tl890 And Tl892 Dlt Minilibraries On Shared Scsi Buses
Figure 8–11: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses Network Member System 1 Memory 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) KZPBA-CB (ID 6) KZPBA-CB (ID 7)
Page 247: Configuring A Base Module As A Slave
Table 8–8: Hardware Components Used to Create the Configuration Shown in Figure 8–10 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 248: Powering Up The Dlt Minilibrary
After a series of power-on self-tests have executed, the default screen will be displayed on the base module control panel: DLT0 Idle DLT1 Idle Loader Idle 0> _ _ _ _ _ _ _ _ _ _ <9 The default screen shows the state of the tape drives, loader, and number of cartridges present for this base module.
Page 249: Setting The Tl890/Tl891/Tl892 Scsi Id
inventory of modules may be incorrect and the contents of some or all of the modules will be inaccessible to the system and to the host. When the expansion unit comes up, it will communicate with each base module through the expansion unit interface and inventory the number of base modules, tape drives, and cartridges present in each base module.
Page 250: Preparing The Tl894 Dlt Automated Tape Library For Shared
Press the down arrow button until the Configure Menu item is selected, and then press the Enter button to display the Configure submenu. Press the down arrow button until the Set SCSI item is selected and press the Enter button. Press the up or down arrow button to select the appropriate tape drive (DLT0 Bus ID:, DLT1 Bus ID:, DLT2 Bus ID:, and so on) or library robotics (Library Bus ID:) for which you wish to change the SCSI bus...
Page 251: Tl894 Robotic Controller Required Firmware
______________________ Note _______________________ To achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus segment. We also recommend that storage be placed on shared SCSI buses that do not have tape drives. The TL894 midrange automated DLT library contains a robotics controller and four differential TZ89 tape drives.
Page 252 Menu: Configuration Inquiry Press and release the up or down arrow buttons to locate the SCSI Address submenu, and verify that the following information is displayed in the SDA: Menu: Configuration SCSI Address .. Press and release the SELECT button to choose the SCSI Address submenu and verify that the following information is displayed in the SDA: Menu:...
Page 253: Tl894 Tape Library Internal Cabling
Press and release the SELECT button again to choose SCSI Address and verify that the following information is shown in the SDA: Menu: SCSI Address Robotics Use the down arrow button to bypass the Robotics submenu and verify that the following information is shown in the SDA: Menu: SCSI Address Drive 0...
Page 254: Tl894 Tape Library Four-Bus Configuration
Figure 8–12: TL894 Tape Library Four-Bus Configuration Robotics Controller *SCSI Address 0 Tape Drive SCSI Cable Interface PWA 1.5m Tape Drive 0 *SCSI Address 2 Internal SCSI Termination #1 Rear Panel Tape Drive 1 Host *SCSI Address 3 Connection #4 Internal SCSI Termination #2 SCSI Port 4...
Page 255: Connecting The Tl894 Tape Library To The Shared Scsi Bus
installing an HD68 SCSI bus terminator on the SCSI bus port connector on the cabinet exterior. This is not wrong, but by reconfiguring in this manner, the length of the SCSI bus is increased by 1.5 meters, and may cause problems if SCSI bus length is of concern.
Page 256: Shared Scsi Buses With Tl894 In Two-Bus Mode
In Figure 8–13, one bus is connected to port 1 (robotics controller and tape drives 0 and 1) and the other bus is connected to port 3 (tape drives 2 and 3). Ensure that the terminators are present on the tape drives 1 and 3. Figure 8–13: Shared SCSI Buses with TL894 in Two-Bus Mode Network Memory...
Page 257: Preparing The Tl895 Dlt Automated Tape Library For Shared
Table 8–10: Hardware Components Used to Create the Configuration Shown in Figure 8–12 (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 258: Tl895 Robotic Controller Required Firmware
The physical SCSI IDs should match the SCSI IDs set by the library electronics. Ensure that the SCSI ID set by the rotary switch and from the control panel do not conflict with any SCSI bus controller SCSI ID. The following sections describe how to prepare the TL895 for use on a shared SCSI bus in more detail.
Page 259: Tl895 Tape Library Internal Cabling
On the Operator screen, press the Configure Library button. The Configure Library screen displays the current library configuration. ____________________ Note _____________________ You can configure the library model number, number of storage bins, number of drives, library SCSI ID, and tape drive SCSI IDs from the Configure Library screen.
Page 260 You can reconfigure the tape drives and robotics controller to place multiple tape drives on the same SCSI bus with SCSI bus jumper (part number 6210567) included with the tape library. ______________________ Note _______________________ We recommend placing no more than two TZ89 drives on a SCSI bus segment.
Page 261: Upgrading A Tl895
Figure 8–14: TL895 Tape Library Internal Cabling Robotics Controller SCSI ID 0 Tape Drive 0 Terminator SCSI ID 1 PN 0415619 Tape Drive 1 SCSI ID 2 SCSI Jumper Cable SCSI Port 8 PN 6210567 Tape Drive 2 SCSI Port 7 SCSI ID 3 Terminator SCSI Port 6...
Page 262: Connecting The Tl895 Tape Library To The Shared Scsi Bus
electronic SCSI ID using the Configure menu from the control panel (see Section 8.10.2). The actual upgrade is beyond the scope of this manual. See the TL895 Drive Upgrade Instructions manual for upgrade instructions. 8.10.5 Connecting the TL895 Tape Library to the Shared SCSI Bus The TL895 tape library has up to 3 meters of internal SCSI cabling per SCSI bus.
Page 263 Each tape library comes configured with a robotic controller and bar code reader (to obtain quick and accurate tape inventories). The libraries have either three or six TZ89N-AV drives. The TL896, because it has a greater number of drives, has a lower capacity for tape cartridge storage.
Page 264: Communications With The Host Computer
These tape libraries each have a multi-unit controller (MUC) that serves two functions: • It is a SCSI adapter that allows the SCSI interface to control communications between the host and the tape library. • It permits the host to control up to five attached library units in a multi-unit configuration.
Page 265: Setting The Muc Scsi Id
Table 8–12: MUC Switch Functions (cont.) Function Switch 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. 8.11.3 Setting the MUC SCSI ID The multi-unit controller (MUC) SCSI ID is set with switch 1, 2, and 3, as shown in Table 8–13.
Page 266: Cabling
Table 8–15: TL896 Default SCSI IDs Device SCSI Port Default SCSI ID Drive 5 (top) Drive 4 Drive 3 Drive 2 Drive 1 Drive 0 (bottom) 8.11.5 TL893 and TL896 Automated Tape Library Internal Cabling The default internal cabling configurations for the TL893 and TL896 Automated Tape Libraries (ATLs) is as follows: •...
Page 267: Tl893 Three-Bus Configuration
Figure 8–15: TL893 Three-Bus Configuration 0415498 (50-Pin Micro-D Terminator) 0425031 (SCSI Diff Feed Through) 0425017 (Cable) SCSI Address 2 TZ89 Tape Drive SCSI Address 5 (top shelf) 0415619 (68-pin Micro-D Terminator) TZ89 Tape Drive SCSI Address 4 (middle shelf) 0415619 (68-pin Micro-D Terminator) TZ89 Tape Drive SCSI Address 3...
Page 268: Connecting The Tl893 And Tl896 Automated Tape Libraries To The Shared Scsi Bus
– The lower bay bottom shelf tape drive (tape drive 0, SCSI ID 3) is on SCSI Port C and is terminated on the tape drive. – The tape drive terminators are 68-pin differential terminators (part number 0415619). Figure 8–16: TL896 Six-Bus Configuration 0415498 (50-Pin Micro-D Terminator) 0425031 (SCSI Diff Feed Through) SCSI Address 2...
Page 269 on the shared SCSI bus. Each SCSI bus must be terminated internal to the tape library at the tape drive itself with the installed SCSI terminators. Therefore, TL893 and TL896 tape libraries must be on the end of the shared SCSI bus.
Page 270: Shared Scsi Buses With Tl896 In Three-Bus Mode
Figure 8–17: Shared SCSI Buses with TL896 in Three-Bus Mode Network Member System 1 Memory 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) KZPBA-CB (ID 6) KZPBA-CB (ID 7) DS-DWZZH-03...
Page 271: Preparing The Tl881 And Tl891 Dlt Minilibraries For Shared Bus Usage
8.12 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 272: Tl881 And Tl891 Minilibrary Rackmount Components
8.12.1.2 TL881 and TL891 MiniLibrary Rackmount Components A TL881 or TL891 base unit (which contains the tape drive(s)) can operate as an independent, standalone unit, or in concert with an expansion unit and multiple data units. A rackmount multiple-module configuration is expandable to up to six modules in a configuration.
Page 273: Tl881 And Tl891 Rackmount Scalability
• Data unit — This rackmount module contains a 16-cartridge magazine to provide additional capacity in a multi-module configuration. The data unit robotics works in conjunction with the robotics of the expansion unit and base units. It is under control of the expansion unit. The data unit works with either the TL881 or TL891 base unit.
Page 274: Dlt Minilibrary Part Numbers
Table 8–17: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary Configured Number of Number of Transfer Storage Transfer Storage Base Units Data Units Rate Rate Capacity Capacity Maximum: Performance 15 MB/sec 1.32 TB (66 50 MB/sec 2.31 TB (66 cartridges) (180...
Page 275: Standalone Shared Scsi Bus Usage
Table 8–18: DLT MiniLibrary Part Numbers (cont.) Number of Tape Part Number DLT Library Component Tabletop/Rackmount Drives 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 Rackmount 128670-B21 ______________________ Note...
Page 276: Setting The Standalone Minilibrary Tape Drive
For complete hardware installation instructions, see the TL881 MiniLibrary System User’s Guide or TL891 MiniLibrary System User’s Guide. 8.12.2.1.1 Setting the Standalone MiniLibrary Tape Drive SCSI ID The control panel on the front of the TL891 and TL892 MiniLibraries is used to display power-on self-test (POST) status, display messages, and to set up MiniLibrary functions.
Page 277: Cabling The Tl881 Or Tl891 Dlt Minilibrary
status until you exit the Menu Mode and the Ready light comes on once again. Depress the down arrow button until the Configure Menu item is selected, then press the Enter button to display the Configure submenu. ____________________ Note _____________________ The control panel up and down arrows have an auto-repeat feature.
Page 278 ______________________ 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–18).
Page 279 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 280: Tl891 Standalone Cluster Configuration
Figure 8–18: 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 281: Cabling The Rackmount Tl881 Or Tl891 Dlt Minilibrary
Table 8–19: 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 282 connector on the data unit and the female end to any Expansion Modules connector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector you connect to a base unit or a data unit. • 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 283: Expansion Unit
Figure 8–19: TL891 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 284: Shown In Figure 8–18
Table 8–20: 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 285: 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 286: 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 287: Compaq Esl9326D Enterprise Library
8.13.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 288: Esl9326D Enterprise Library Overview
146205-B28 You can upgrade a tape library 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 for more information. 8.13.3 Preparing the ESL9326D Enterprise Library for Shared SCSI...
Page 289: Esl9326D Enterprise Library Robotic And Tape Drive Required Firmware
Figure 8–20 shows the default robotics and tape drive SCSI IDs. 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.
Page 290: Esl9326D Internal Cabling
Figure 8–20: 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 291: Shared Scsi Bus
8.13.3.4 Connecting the ESL9326D Enterprise Library to the Shared SCSI Bus The ESL9326D Enterprise Library has 5 meters of internal SCSI bus cabling for each pair of tape drives. Because of the internal SCSI bus lengths, you cannot 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 292 ______________________ 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 you do not have enough host bus adapters and you want to place more than two tape drives on a...
Page 293: 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 294: 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 295: 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 296: 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 297: 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 298 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 299: 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 300: 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 301: 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 302: 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 303 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 304: 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 305: 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 306: 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 307: Preparing Ba350, Ba356, And Ultrascsi Ba356 Storage Shelves For An Externally Terminated Trucluster Server 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 308: Preparing A Ba356 Storage Shelf For Shared Scsi 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 309: 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 310 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 311: Ba350 And Ba356 Cabled For Shared Scsi Bus Usage
Figure 9–9 shows a two-member TruCluster Server configuration using a BA350 and a BA356 for storage. 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...
Page 312: 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 313: Two Ba356S Cabled For Shared Scsi Bus Usage
Figure 9–10 shows a two member TruCluster Server configuration using two BA356s for storage. 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...
Page 314 9.4.2.3 Connecting Two UltraSCSI BA356s for Shared SCSI Bus Usage When you use two UltraSCSI BA356 storage shelves on a shared SCSI bus in a TruCluster configuration, one storage shelf must be configured for SCSI IDs 0 through 6 and the other configured for SCSI IDs 8 through 14. 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.
Page 315: Two Ultrascsi Ba356S Cabled For Shared Scsi Bus Usage
Figure 9–11 shows a two member TruCluster Server configuration using two UltraSCSI BA356s for storage. 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...
Page 316: 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 317: 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 318: Raid Array Controllers
Figure 9–12 shows two AlphaServer systems in a TruCluster Server configuration with dual-redundant HSZ50 RAID controllers in the middle of the shared SCSI bus. Note that the SCSI bus adapters are KZPSA-BB PCI-to-SCSI adapters. They could be KZPBA-CB host bus adapters without changing any cables.
Page 319: Array Controllers At Bus End
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 320: Cabling An Hsz20 In A Cluster Using External Termination
9.4.3.2 Cabling an HSZ20 in a Cluster Using External Termination To connect a SWXRA-Z1 (HSZ20 controller) to a shared SCSI bus, follow these steps: Referring to the RAID Array 310 Deskside Subsystem (SWXRA-ZX) Hardware User’s Guide, open the SWXRA-Z1 cabinet, locate the SCSI bus converter board, and: •...
Page 321 Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H885-AA trilink connector to the other controller. Install a BN21K or BN21L cable between the H885-AA trilink connectors on the two controllers.
Page 322: Trucluster Server Cluster Using Ds-Dwzzh-03, Scsi Adapter With Terminators Installed, And Hsz50
Figure 9–14 shows a sample configuration with radial connection of KZPSA-BB PCI-to-SCSI adapters, DS-DWZZH-03 UltraSCSI hub, and an HSZ50 RAID array controller. Note that the KZPSA-BBs could be replaced with KZPBA-CB UltraSCSI adapters without any changes in cables. Figure 9–14: TruCluster Server Cluster Using DS-DWZZH-03, SCSI Adapter with Terminators Installed, and HSZ50 Network Member...
Page 323: Trucluster Server Cluster Using Kzpsa-Bb Scsi Adapters, A Ds-Dwzzh-05 Ultrascsi Hub, And An Hsz50 Raid Array Controller
Figure 9–15 shows a sample configuration that uses KZPSA-BB SCSI adapters, a DS-DWZZH-05 UltraSCSI hub, and an HSZ50 RAID array controller. Figure 9–15: TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller Network Member Member...
Page 325: 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 326: 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 327 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 328: 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.3.2. 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 329 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 330: 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 331: Termination
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 332 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.5 TZ887 Section 8.6 TL891/TL892 MiniLibrary Section 8.7 10–8 Configuring Systems for External Termination or Radial Connections...
Page 333: Show Console Commands
TL895 Section 8.10 TL893/TL896 Section 8.11 TL881/TL891 DLT MiniLibraries Section 8.12 Compaq ESL9326D Enterprise Library Section 8.13 _____________________ 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 334: 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 335: Displaying Configuration On An Alphaserver 8200
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 336: Displaying Devices On An Alphaserver 8200
Example 10–4: Displaying Devices on an AlphaServer 8200 >>> show device polling for units on isp0, slot0, bus0, hose0... polling for units on isp1, slot1, bus0, hose0... polling for units on isp2, slot4, bus0, hose0... polling for units on isp3, slot5, bus0, hose0... polling for units kzpaa0, slot0, bus0, hose1...
Page 337: Displaying Console Environment Variables And Setting The Kzpsa-Bb And Kzpba-Cb Scsi Id
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 338 Example 10–5: Displaying the pk* Console Environment Variables on an AlphaServer 4100 System (cont.) 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. Note that there are no pk* devices in either display. Example 10–2 shows: •...
Page 339: 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 340: 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 341: 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 342: 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 343 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 345: Quorum Disk
Worldwide ID-to-Disk Name Conversion Table Table A–1: Converting Storageset Unit Numbers to Disk Names WWID UDID Device Name dskn File System HSG80 or Disk Unit Tru64 UNIX disk Cluster root (/) /usr /var Member 1 boot disk Member 2 boot disk Member 3 boot disk...
Page 347 Index Numbers and Special , 3–10 DS-DWZZH-05 installed in Characters , 9–9, 9–12 jumper personality module address , 8–10 20/40 GB DLT Tape Drive , 9–11 switches , 8–11 cabling , 9–15, 9–17 preparing , 8–10 capacity preparing for shared SCSI usage , 8–10 cartridges 9–16...
Page 348 , 8–11 20/40 GB DLT Tape Drive SET FAILOVER COPY = , 8–15 40/80-GB DLT Drive , 1–13 THIS_CONTROLLER Compaq 20/40 GB DLT Tape Drive , 7–10 set hp_count 8–11 , 7–10 set hp_qbb_maskn , 8–15 Compaq 40/80-GB DLT Drive SET MULTIBUS_FAILOVER , 8–9...
Page 349 , 2–9 bus_probe_algorithm , 8–10 20/40 GB DLT Tape Drive , 7–4 , 8–14 40/80-GB DLT Drive , 7–5 nodes Compaq 20/40 GB DLT Tape Drive , 7–4 purpose 8–10 , 8–14 Compaq 40/80-GB DLT Drive , 8–17 TZ885 , 8–20...
Page 350 , 3–9 termpwr enterprise library , 2–12 ( See ESL9326D ) transfer rate , 3–8, 3–10 , 7–10 DS-DWZZH-05 environment variable , 3–10 , 6–50, 6–53, 6–56, bus connectors bootdef_dev , 2–12 6–57 bus isolation , 3–15 , 7–10 configurations hp_count , 2–12 , 7–10...
Page 351 , 6–4 Fibre Channel , 2–7, 6–17 GBIC , 6–8 arbitrated loop GigaBit Interface Converter , 6–4 data rates ( See GBIC ) , 6–4 distance Gigabit Link Module , 6–6 F_Port ( See GLM ) , 6–5, 6–7 fabric , 2–7 , 6–5 FL_Port...
Page 352 ( See KGPSA, KZPBA-CB, , 7–3, 7–9 cables KZPSA-BB ) , 7–3, 7–9 local , 7–5 , 7–3, 7–9 remote , 1–13 , 6–25, 6–48, 6–50, 6–55, HSG60 controller initialize , 2–5 6–57 , 2–8 , 3–16 configuring installation , 2–8 ( See also hardware port configuration , 2–8...
Page 353 , 2–9 restrictions MA8000 , 4–9t, 10–4t, , 2–8 termination resistors configuring 10–7t , 2–8 port configuration , 4–6, 10–2 , 2–8 use in cluster transparent failover mode KZPSA-BB , 2–8 unit configuration displaying device information , 5–12 mc_cable 10–5t, 10–7t , 5–12 mc_diag , 10–3...
Page 354: Ultrascsi Hub
multi-unit controller planning the hardware configuration ( See MUC ) 4–2 , 6–17 , 6–6 multimode fibre point-to-point , 1–14, 3–18, , 6–33 multiple-bus failover port name power system manager 3–22, 6–30 ( See PSM ) changing from transparent failover powering up 6–59 , 8–71...
Page 355 20/40 GB DLT Tape Drive number of devices supported , 8–14 40/80-GB DLT Drive SCSI bus with BA350 and BA356 9–18 Compaq 20/40 GB DLT Tape Drive 8–10 , 9–20 SCSI bus with Two BA356s , 8–14 Compaq 40/80-GB DLT Drive SCSI bus with two UltraSCSI BA356s , 8–9...
Page 356 , 8–51 , 9–2 creating differential bus , 8–72 , 9–2 TL881/891 DLT MiniLibrary differential I/O module , 8–23 , 9–3 TL891 differential termination , 8–23 TL892 DS-BA35X-DA personality module , 8–51 3–5, 9–4 TL893 , 8–37 TL894 extending differential bus length , 8–51 9–2 TL896...
Page 357: Mode
, 8–25, 8–36 system control manager default SCSI IDs ( See SCM ) , 8–24, 8–35 setting SCSI ID , 6–25, 6–48 , 8–23 system reset shared SCSI usage , 8–23 TL892 , 8–25, 8–30 cabling , 8–33 configuring as slave , 8–25, 8–36 , 6–58 default SCSI IDs...
Page 358 , 8–1 TZ88N-VA utility , 8–3 , 6–51 cabling hwmgr , 8–2 , 6–48, 6–54, 6–56 setting SCSI ID wwidmgr , 8–6 TZ89 , 6–27 /var/adm/messages UltraSCSI BA356 variable , 9–17 ( See environment variable ) disable termination Very High Density Cable Interconnect DS-BA35X-DA personality module ( See VHDCI ) 3–3...
Page 359 How to Order Tru64 UNIX Documentation To order Tru64 UNIX documentation in the United States and Canada, call 800-344-4825. In other countries, contact your local Compaq subsidiary. If you have access to Compaq’s intranet, you can place an order at the following Web site: http://asmorder.nqo.dec.com/...
Page 361 TruCluster Server Hardware Configuration AA-RHGWC-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 362 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-RHGWC-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 Using GS80, GS160, or GS320 Hard Partitions in a Trucluster Server Configuration

8 Configuring a Shared SCSI Bus for Tape Drive Use

Quick Links

TruCluster Server

Hardware Configuration

Related Manuals for Compaq TruCluster Server AA-RHGWC-TE

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