TruCluster Server Hardware Configuration Part Number: AA-RHGWC-TE August 2000 Product Version: 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.
© 2000 Compaq Computer Corporation COMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, AlphaServer, StorageWorks, TruCluster, and Tru64 are trademarks of Compaq Information Technologies Group, L.P. Microsoft and Windows are trademarks of Microsoft Corporation. UNIX and The Open Group are trademarks of The Open Group. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.
Contents About This Manual 1 Introduction 1.1 1.2 1.3 1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.1.4 1.4 1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.6 2 The TruCluster Server Product . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Memory Requirements . . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Minimum Disk Requirements .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Disks Needed for Installation . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
2.6 2.7 2.8 2.9 SCSI Signal Converters . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs . . .. . .. . .. . SCSI Cables . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . SCSI Terminators and Trilink Connectors . . .. . .. . .. . . .. . .. . .. . .. . 2–10 2–11 2–12 2–14 3 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.
4.3.1 4.3.2 4.3.3 4.3.3.1 4.3.3.2 4.3.3.3 5 4–7 4–10 4–14 4–15 4–17 4–17 Setting Up the Memory Channel Cluster Interconnect 5.1 5.1.1 5.1.2 5.2 5.3 5.4 5.5 5.5.1 5.5.1.1 5.5.1.2 5.5.2 5.5.2.1 5.5.2.2 5.5.2.3 5.5.2.4 5.6 5.7 6 Installation of a KZPBA-CB Using Internal Termination for a Radial Configuration .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Displaying KZPBA-CB Adapters with the show Console Commands . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .
.2.2.2 Fabric . . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.2.2.3 Arbitrated Loop Topology . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.3 Example Fibre Channel Configurations Supported by TruCluster Server . . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.3.1 Fibre Channel Cluster Configurations for Transparent Failover Mode . . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. .
6.6.2 6.6.3 6.6.4 6.6.5 6.6.6 6.6.7 6.7 6.7.1 6.7.2 6.8 6.8.1 6.8.2 Install the Tru64 UNIX Operating System . . .. . . .. . .. . .. . .. . Determining /dev/disk/dskn to Use for a Cluster Installation . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Label the Disks to Be Used to Create the Cluster . .. . .. . .. . Install the TruCluster Server Software and Create the First Cluster Member . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
.2.2 8.2.3 8.2.4 8.3 8.3.1 8.3.2 8.4 8.4.1 8.4.2 8.5 8.5.1 8.5.2 8.6 8.6.1 8.6.2 8.7 8.7.1 8.7.2 8.8 8.8.1 8.8.2 8.8.2.1 8.8.2.2 8.8.2.3 8.8.2.4 8.9 8.9.1 8.9.2 8.9.3 8.9.4 8.10 8.10.1 8.10.2 8.10.3 8.10.4 viii Contents Cabling the DS-TZ89N-VW Tape Drives . . .. . .. . . .. . .. . .. . .. . Setting the DS-TZ89N-TA SCSI ID . . .. . .. . .. . .. . . .. . .. . .. . .. . Cabling the DS-TZ89N-TA Tape Drives .. . .. . .. . . .. . .. . .. . .. . Compaq 20/40 GB DLT Tape Drive .. . .. . . .. . .. . .. . .. . . .
8.10.5 Connecting the TL895 Tape Library to the Shared SCSI Bus . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11 Preparing the TL893 and TL896 Automated Tape Libraries for Shared SCSI Bus Usage .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11.1 Communications with the Host Computer .. . .. . . .. . .. . .. . .. . 8.11.2 MUC Switch Functions .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11.
8.13.3.1 8.13.3.2 8.13.3.3 8.13.3.4 ESL9326D Enterprise Library Robotic and Tape Drive Required Firmware .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Library Electronics and Tape Drive SCSI IDs . .. . .. . .. . ESL9326D Enterprise Library Internal Cabling . .. . .. . Connecting the ESL9326D Enterprise Library to the Shared SCSI Bus . . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
9.4.3.2 9.4.4 Cabling an HSZ20 in a Cluster Using External Termination . . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Cabling an HSZ40 or HSZ50 RAID Array Controller in a Radial Configuration with an UltraSCSI Hub . . .. . .. . .. . .. . 9–28 9–28 10 Configuring Systems for External Termination or Radial Connections to Non-UltraSCSI Devices 10.1 TruCluster Server Hardware Installation Using PCI SCSI Adapters .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
5–1 6–1 6–2 6–3 6–4 6–5 6–6 6–7 7–1 7–2 7–3 7–4 10–1 10–2 10–3 10–4 10–5 10–6 10–7 10–8 10–9 Running the mc_cable Test . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Determine HSG80 Connection Names . . . .. . .. . .. . .. . . .. . .. . .. . .. . Setting Up the Mirrorset . . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Adding Units and Identifiers to the HSG80 Storagesets . .. . .. . Displaying the UDID and Worldwide Names of Devices Known to the Console .
1–8 2–1 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 4–1 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 7–1 7–2 7–3 NSPOF Fibre Channel Cluster Using HSG80s in Multiple-Bus Failover Mode . . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . PCI Backplane Slot Layout . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . VHDCI Trilink Connector (H8861-AA) . . . .. . .. . .. . .. . . .. . .. . .. . .. . DS-DWZZH-03 Front View . .. . .. . .. . ..
8–1 8–2 8–3 8–4 8–5 8–6 8–7 8–8 8–9 8–10 8–11 8–12 8–13 8–14 8–15 8–16 8–17 8–18 8–19 8–20 9–1 9–2 9–3 9–4 9–5 9–6 9–7 9–8 9–9 9–10 9–11 9–12 9–13 9–14 xiv Contents TZ88N-VA SCSI ID Switches . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Shared SCSI Buses with SBB Tape Drives . .. . .. . .. . . .. . .. . .. . .. . DS-TZ89N-VW SCSI ID Switches . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Compaq 20/40 GB DLT Tape Drive Rear Panel . . .. . . .. . .. . .. . .. .
9–15 10–1 TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . KZPSA-BB Termination Resistors . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 9–31 10–18 Tables 2–1 2–2 2–3 2–4 3–1 3–2 3–3 3–4 4–1 4–2 4–3 5–1 5–2 5–3 5–4 6–1 6–2 8–1 8–2 8–3 8–4 8–5 8–6 8–7 8–8 RAID Controller Minimum Required Array Controller Software .. . ..
8–9 8–10 8–11 8–12 8–13 8–14 8–15 8–16 8–17 8–18 8–19 8–20 8–21 9–1 9–2 9–3 9–4 10–1 10–2 10–3 A–1 xvi Contents TL894 Default SCSI ID Settings .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Hardware Components Used to Create the Configuration Shown in Figure 8–12 .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . TL895 Default SCSI ID Settings .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . MUC Switch Functions . .. . . .. . .. . .. . .. . .. . . .. . .
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. Organization This manual contains 10 chapters, an appendix, and an index.
Chapter 7 Describes the use of AlphaServer™ GS80, GS160, or GS320 hardware partitions in a TruCluster Server configuration. Chapter 8 Describes how to configure a shared SCSI bus for tape drive, tape loader, or tape library usage. Chapter 9 Describes the requirements for a shared SCSI bus using externally terminated configurations and radial configurations using non-UltraSCSI RAID array controllers.
The StorageWorks™ UltraSCSI Configuration Guidelines document provides guidelines regarding UltraSCSI configurations. For information about setting up a RAID subsystem, see the following manuls as appropriate for your configuration: • DEC RAID Subsystem User’s Guide • HS Family of Array Controllers User’s Guide • RAID Array 310 Configuration and Maintenance Guide User’s Guide • Configuring Your StorageWorks Subsystem HSZ40 Array Controllers HSOF Version 3.0 • Getting Started RAID Array 450 V5.
• 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 • Compaq StorageWorks SAN Switch Fabric Operating System Management Guide • Fibre Channel Storage Hub 7 Installation Guide • Fibre Channel Storage Hub 7 Rack Mounting Installation Card For information about the tape
• For more information on the ESL9326D Enterprise Library, see the following Compaq StorageWorks ESL9000 Series Tape Library documentation: – Unpacking and Installation Guide – Reference Guide – Maintenance and Service Guide – Tape Drive Upgrade Guide The Golden Eggs Visual Configuration Guide provides configuration diagrams of workstations, servers, storage components, and clustered systems. It is available on line in PostScript and Portable Document Format (PDF) formats at: http://www.compaq.
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.
file Italic (slanted) type indicates variable values, placeholders, and function argument names. .. . A vertical ellipsis indicates that a portion of an example that would normally be present is not shown. cat(1) A cross-reference to a reference page includes the appropriate section number in parentheses. For example, cat(1) indicates that you can find information on the cat command in Section 1 of the reference pages. cluster Bold text indicates a term that is defined in the glossary.
1 Introduction This chapter introduces the TruCluster Server product and some basic cluster hardware configuration concepts. Subsequent chapters describe how to set up and maintain TruCluster Server hardware configurations. See the TruCluster Server Software Installation manual for information about software installation; see the TruCluster Server Cluster Administration manual for detailed information about setting up member systems and highly available applications. 1.
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. For more information on the amount of space required for each required cluster file system, see the TruCluster Server Software Installation manual. 1.3.
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. 1.3.1.2 Clusterwide Disk(s) When you create a cluster, the installation scripts copy the Tru64 UNIX root (/), /usr, and /var file systems from the Tru64 UNIX disk to the disk or disks you specify.
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.
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. As shown, with only two-member systems, both systems must be operational to achieve quorum and form a cluster. If only one system is operational, it will loop, waiting for the second system to boot before a cluster can be formed.
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 System 1 Memory Channel PCI SCSI Adapter Member System 2 PCI SCSI Adapter Tru64 UNIX Disk Shared SCSI Bus Cluster File System root (/) /usr /var Member 1 Member 1 root (/) swap root (/) swap Quorum ZK-1588U-AI 1.
• 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). • By using an HSZ70, HSZ80, or HSG80 with multiple-bus failover enabled you can use two shared SCSI buses to access the storage.
Figure 1–3: Minimum Two-Node Cluster with UltraSCSI BA356 Storage Unit Network Member System 1 Memory Channel Interface Memory Channel Memory Channel Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) Shared SCSI Bus Tru64 UNIX Disk Member System 2 UltraSCSI BA356 ID 0 Clusterwide /, /usr, /var ID 1 Member 1 Boot Disk ID 2 Member 2 Boot Disk ID 3 Quorum Disk ID 4 Shared SCSI Bus DS-BA35X-DA Personality Module Clusterwide Data Disks ID 5 ID 6 PWR Do not use for data disk.
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. But, if that member system was not available, the other member system(s) would not have access to the clusterwide file systems.
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.
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.
Figure 1–5: Two-Node Configurations with UltraSCSI BA356 Storage Units and Dual SCSI Buses Network Tru64 UNIX Disk Member System 1 Member System 2 Memory 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 BA356 UltraSCSI BA356 UltraSCSI BA356 UltraSCSI BA356 ID 0 Clusterwide /, /usr, /var Data Disk ID 0 Mirrored /usr, /var Mirrored Data Disk ID 8 ID 1 Member 1 Boot Disk Data Disk ID
instead of the HSZ70. The array controllers can be configured as a dual redundant pair. If you want the capability to fail over from one controller to another controller, you must install the second controller. Also, you must set the failover mode.
Note that in the configuration shown in Figure 1–6, there is only one shared SCSI bus. Even by mirroring the clusterwide root and member boot disks, the single shared SCSI bus is a single point of failure. 1.5.5 Creating a NSPOF Cluster To create a no-single-point-of-failure (NSPOF) cluster: • Use hardware RAID to mirror the clusterwide root (/), /usr, and /var file systems, the member boot disks, quorum disk (if present), and data disks.
Figure 1–7: NSPOF Cluster Using HSZ70s in Multiple-Bus Failover Mode Networks Tru64 UNIX Disk Memory Channel Interfaces Member System 1 Memory Channel (mca1) Member System 2 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) HSZ70 HSZ70 StorageWorks RAID Array 7000 ZK-1594U-AI Figure 1–8 shows a cluster configuration with dual-shared Fibre Channel SCSI buses and a storage array with d
Figure 1–8: NSPOF Fibre Channel Cluster Using HSG80s in Multiple-Bus Failover Mode Member System 1 Memory Channel KGPSA Memory Channel Interface Member System 2 Memory Channel KGPSA KGPSA KGPSA Fibre Channel Switch Fibre Channel Switch Port 1 Port 1 HSG 80 Controller A HSG 80 Controller B Port 2 Port 2 RA8000/ESA12000 ZK-1765U-AI 1.6 Overview of Setting Up the TruCluster Server Hardware Configuration To set up a TruCluster Server hardware configuration, follow these steps: 1.
5. Prepare the shared storage by installing disks and configuring any RAID controller subsystems (see Chapter 3, Chapter 6, and Chapter 9 and the documentation for the StorageWorks enclosure or RAID controller). 6. Install signal converters in the StorageWorks enclosures, if applicable (see Chapter 3 and Chapter 9). 7. Connect storage to the shared SCSI buses. Terminate each bus. Use Y cables or trilink connectors where necessary (see Chapter 3 and Chapter 9).
2 Hardware Requirements and Restrictions This chapter describes the hardware requirements and restrictions for a TruCluster Server cluster. It includes lists of supported cables, trilink connectors, 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.
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; any slot except 0-5, 0-6, 1-5, and 1-6.
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. The Memory Channel 2 product (CCMAB module) is referred to as MC2.
• 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. • Always check a Memory Channel link cable for bent or broken pins. Be sure that you do not bend or break any pins when you connect or disconnect a cable.
each Memory Channel adapter on one system must be connected to the same linecard in each Memory Channel hub. 2.3 Host Bus Adapter Restrictions To connect a member system to a shared SCSI bus, you must install a host bus adapter in an I/O bus slot. The Tru64 UNIX operating system supports a maximum of 64 I/O buses. TruCluster Server supports a total of 32 shared I/O buses using KZPSA-BB host bus adapters, KZPBA-CB UltraSCSI host bus adapters, or KGPSA Fibre Channel host bus adapters.
____________________ Notes ____________________ The Model 4124R disk enclosure is a single-bus enclosure that has slots for 14 drives, but only 12 drives are supported at the present time. The maximum number of drives behind an HSG60 (single or dual-redundant pair) using two single-bus Model 4214R disk enclosures is 24. The maximum number of drives behind an HSG60 (single or dual-redundant pair) using one dual-bus Model 4254 disk enclosures is 14.
The maximum number of drives behind an HSG80 (single or dual-redundant pair) using three dual-bus Model 4254 disk enclosures is 42. The Model 4214R and Model 4254 disk enclosures support only the new Compaq hot-pluggable wide-UltraSCSI low voltage differential (LVD) disk drives. For more information on configuring the MA8000/EMA12000, see the Compaq StorageWorks Modular Array Configuration Guide.
• 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. • Tru64 UNIX Version 5.1 allows up to 255 LUNs per target. • The HSG60 and HSG80 supports transparent and multiple-bus failover mode when used in a TruCluster Server Version 5.1 configuration.
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. If the response is anything other than new, you must set it to new.
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 3.4 HSZ40 3.7 HSZ50 5.7 HSZ70 7.7 HSZ80 8.3-1 HSG60 8.5 HSG80 8.5 RAID controllers can be configured with the number of SCSI IDs as shown in Table 2–2.
______________________ 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.
• The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks. • A wide BA356 which has been upgraded to the 180-watt power supply with the DS-BA35X-HH option. A DS-DWZZH-03 or DS-DWZZH-05 UltraSCSI hub: • Improves the reliability of the detection of cable faults. • Provides for bus isolation of cluster systems while allowing the remaining connections to continue to operate.
Table 2–3: Supported SCSI Cables Cable Connector Density Pins Configuration Use BN21W-0B Three high 68-pin A Y cable that can be attached to a KZPSA-BB or KZPBA-CB if there is no room for a trilink connector. It can be used with a terminator to provide external termination. BN21M One low, one high 50-pin LD to 68-pin HD Connects the single-ended end of a DWZZA-AA or DWZZB-AA to a TZ885 or TZ887.a BN21K, BN21L, or 328215-00X Two HD68 68-pin Connects BN21W Y cables or wide devices.
2.9 SCSI Terminators and Trilink Connectors Table 2–4 describes the supported trilink connectors and SCSI terminators and the context in which you would use them. Table 2–4: Supported SCSI Terminators and Trilink Connectors Trilink Connector or Terminator Density Pins Configuration Use H885-AA Three 68-pin Trilink connector that attaches to high-density, 68-pin cables or devices, such as a KZPSA-BB, KZPBA-CB, HSZ40, HSZ50, or the differential side of a SCSI signal converter.
3 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 discusses the following topics: • Shared SCSI bus configuration requirements (Section 3.1) • SCSI bus performance (Section 3.2) • SCSI bus device identification numbers (Section 3.3) • SCSI bus length (Section 3.4) • SCSI bus termination (Section 3.5) • UltraSCSI hubs (Section 3.6) • Configuring UltraSCSI hubs with RAID array controllers (Section 3.7) 3.
storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storage arrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves are supported with UltraSCSI host adapters and host RAID controllers as long as they contain no UltraSCSI disks. • UltraSCSI drives and fast wide drives can be mixed together in an UltraSCSI BA356 shelf (see Chapter 9).
cable or a backplane, and cable or backplane connectors. Each UltraSCSI bus segment must have a terminator at each end of the bus segment. Up to two UltraSCSI bus segments may be coupled together with UltraSCSI hubs or signal converters, increasing the total length of the UltraSCSI bus. 3.2.2 Transmission Methods Two transmission methods can be used in a SCSI bus: • • Single-ended — In a single-ended SCSI bus, one data lead and one ground lead are utilized for the data transmission.
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. It is the interface between the shared differential UltraSCSI bus and the UltraSCSI BA356 internal single-ended SCSI bus.
______________________ 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. When assigning SCSI IDs, use the highest priority ID for member systems (starting at 7).
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.
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. Each connection forms a SCSI bus segment with SCSI bus adapters or the storage unit. The hub provides termination for one end of the bus segment.
• 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. 3.6.1.1 DS-DWZZH-03 Description The DS-DWZZH-03: • Is a 3.5-inch StorageWorks building block (SBB).
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. • Uses SCSI ID 7 whether or not fair arbitration mode is enabled.
• The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks. A DS-DWZZH-05 UltraSCSI hub uses the storage shelf only to provide its power and mechanical support (it is not connected to the shelf internal SCSI bus).
3.6.1.2.2 DS-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.
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.
Figure 3–3: DS-DWZZH-05 Rear View W1 ZK-1448U-AI 3–14 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware
Figure 3–4: DS-DWZZH-05 Front View Fair Disable Controller Port SCSI ID 6-4 (6 - 0) Host Port SCSI ID 2 (14) Power Host Port SCSI ID 3 (15) Host Port SCSI ID 1 (13) Busy Host Port SCSI ID 0 (12) 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 on each end of the SCSI bus segment. If the host adapter is disconnected from the hub, the port is disabled.
2. If fair arbitration is to be used, ensure that the switch on the front of the DS-DWZZH-05 UltraSCSI hub is in the Fair position. 3. Install the DS-DWZZH-05 UltraSCSI hub in a UltraSCSI BA356, non-UltraSCSI BA356 (if it has the required 180-watt power supply), or BA370 storage shelf. 3.
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.
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.
2. Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H8861-AA VHDCI trilink connector to: • HSZ70 controller A and controller B • HSZ80 Port 1 (2) of controller A and Port 1 (2) of controller B ___________________ Note ___________________ You must use the same port on each HSZ80 controller. 3.
Figure 3–5 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ70 RAID array controller configured for transparent failover.
Table 3–4: Hardware Components Used in Configuration Shown in Figure 3–5 Through Figure 3–8 Callout Number Description 1 BN38C cablea 2 BN37A cableb 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminatorb 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.
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. If one host adapter or SCSI bus fails, the host(s) can move all storage to the other path.
2. Install H8861-AA VHDCI trilink connectors (with terminators) on: • HSZ70 controller A and controller B • HSZ80 controller A Port 1 (2) and controller B Port 1 (2) ___________________ Note ___________________ You must use the same port on each HSZ80 controller. 3. Install the DS-DWZZH-03 or DS-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) 4.
Figure 3–7 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ70 configured for multiple-bus failover.
Figure 3–8 shows a two-member TruCluster Server configuration with a radially connected dual-redundant HSZ80 configured for multiple-bus failover.
4 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. This chapter does not provide detailed information about installing devices; it describes only how to set up the hardware in the context of the TruCluster Server product.
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. • Place the devices as close together as possible and ensure that shared SCSI buses will be within length limitations.
• 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. Mirroring data across shared buses provides you with more reliable and available data.
Table 4–1: Planning Your Configuration (cont.) To increase: You can: Disk availability Mirror disks across shared buses. Use a RAID array controller. Shared storage capacity Increase the number of shared buses. Use a RAID array controller. Increase disk size. 4.2 Obtaining the Firmware Release Notes You may be required to update the system or SCSI controller firmware during a TruCluster Server installation, so you may need the firmware release notes.
6. 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 7. Unmount the CD-ROM drive: # umount /mnt 8. Print the release notes. 4.3 TruCluster Server Hardware Installation Member systems may be connected to a shared SCSI bus with a peripheral component interconnect (PCI) SCSI adapter.
______________________ 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.
Table 4–2: Configuring TruCluster Server Hardware (cont.) Step Action Refer to: 4 Use the firmware update release notes (Section 4.2) Update the system SRM console firmware from the latest Alpha Systems Firmware Update CD-ROM. ______________________ Note _____________________ The SRM console firmware includes the ISP1020/1040-based PCI option firmware, which includes the KZPBA-CB. When you update the SRM console firmware, you are enabling the KZPBA-CB firmware to be updated.
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. Power for the DWZZH termination (termpwr) is supplied by the host SCSI bus adapter or RAID array controller connected to the DWZZH port.
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 Refer to: 1 Ensure that the eight KZPBA-CB internal Section 4.3.1, Figure 4–1, termination resistor SIPs, RM1-RM8 are installed.
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. If you are using a DS-DWZZH-05, you cannot use SCSI ID 7 for a KZPBA-CB UltraSCSI adapter; SCSI ID 7 is reserved for DS-DWZZH-05 use.
Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.) Core Logic Cchip Dchip Pchip 0 Pchip 1 DECchip DECchip DECchip DECchip TIG Arbiter Rev 4.14 Rev 2.10 (0x1) MEMORY Array # ------0 Size ---------512 MB 21272-CA 21272-DA 21272-EA 21272-EA Rev Rev Rev Rev 2.1 2.0 2.2 2.2 Base Addr --------000000000 Total Bad Pages = 0 Total Good Memory = 512 MBytes PCI Hose 00 Bus 00 Slot 05/0: Cypress 82C693 Bus 00 Bridge to Bus 1, ISA Slot 05/1: Cypress 82C693 IDE dqa.0.0.105.
Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.) Bus 02 PCI Hose 01 Bus 00 Slot 02: DE500-AA Network Controller ewa0.0.0.2002.0 00-06-2B-00-0A-48 Slot 07: DEC PCI FDDI fwa0.0.0.7.
Example 4–3 shows the output from the show config console command entered on an AlphaServer 8200 system.
Example 4–4: Displaying Devices on an AlphaServer 8200 (cont.) dkf4.0.0.1.1 dkf5.0.0.1.1 dkf6.0.0.1.1 dkf100.1.0.1.1 dkf200.2.0.1.1 dkf300.3.0.1.1 DKF4 DKF5 DKF6 DKF100 DKF200 DKF300 HSZ70 HSZ70 HSZ70 RZ28M RZ28M RZ28 V70Z V70Z V70Z 0568 0568 442D polling for units kzpsa0.4.0.2.1 dkg0.0.0.2.1 dkg1.0.0.2.1 dkg2.0.0.2.1 dkg100.1.0.2.1 dkg200.2.0.2.1 dkg300.3.0.2.1 on kzpsa0, slot 2, bus 0, hose1...
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.
• 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. Therefore, the pk*0_soft_term environment variable has no meaning and it may be ignored. Example 4–6 shows the use of the show isp console command to display the console environment variables for KZPBA-CBs on an AlphaServer 8x00.
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. And, if you are using a DS-DWZZH-05, you will have to set the SCSI IDs for all KZPBA-CB UltraSCSI adapters.
Figure 4–1: KZPBA-CB Termination Resistors Internal Narrow Device Connector P2 Internal Wide Device Connector J2 JA1 SCSI Bus Termination Resistors RM1-RM8 ZK-1451U-AI 4–18 TruCluster Server System Configuration Using UltraSCSI Hardware
5 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; CCMAA and CCMAB (MC2). Two variations of the CCMAA PCI adapter are in use; CCMAA-AA (MC1) and CCMAA-AB (MC1.5).
____________________ 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. 5.1.1 MC1 and MC1.
Table 5–1: MC1 and MC1.5 Jumper Configuration (cont.) If hub mode is: Jumper: Virtual: VH0 Pins 2 to 3 Example: 12 3 Virtual: VH1 None needed; store the jumper on pin 1 or 3 12 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. 5.1.2 MC2 Jumpers The MC2 module (CCMAB) has multiple jumpers.
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 (cont.) Jumper: Description: J5: AlphaServer 8x00 Mode 8x00 mode selected: Pins 1 to 2a Example: 12 3 8x00 mode not selected: Pins 2 to 3 12 3 J10 and J11: Fiber Fiber Off: Pins 1 to 2 Optics Mode Enable 3 2 1 Fiber On: Pins 2 to 3 pins 3 2 1 a Increases the maximum sustainable bandwidth for 8x00 systems. If the jumpers are in this position for other systems, the bandwidth is decreased.
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.
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: • For use with the MC1 or MC1.5 CCMAA adapter, you must install the hub within 3 meters of each of the systems. For use with the MC2 CCMAB adapter, the hub must be placed within 4 or 10 meters (the length of the BN39B link cables) of each system.
______________________ 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. _____________________ Caution _____________________ Be very careful when installing the link cables. Insert the cables straight in.
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 hub 2 Linecards Memory Channel adapters ZK-1197U-AI 5.5.2 Installing the MC2 Cables To set up an MC2 interconnect, use the BN39B-04 (4-meter) or BN39B-10 (10-meter) link cables for virtual hub or standard hub configurations without optical converters.
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. 5.5.2.
Now you need to: • Set the CCMLB linecard jumpers to support fiber optics • Connect the fiber optics cable to a CCMFB fiber optics converter module • Install the CCMFB fiber optics converter module for each fiber optics link ______________________ Note _______________________ Remember, if you have more than four fiber optics links, you need two or more hubs. The CCMHB-BA hub has no linecards. To set the CCMLB jumpers and install CCMFB optics converter modules in an MC2 hub, follow these steps: 1.
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. – Runs on a standalone system or while connected to another system or a hub with the link cable. The mc_cable diagnostic: – Must be run on all systems in the cluster simultaneously (therefore, all systems must be at the console prompt).
Example 5–1: Running the mc_cable Test >>> mc_cable To exit MC_CABLE, type 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 Ctrl/C >>> 1 2 2 3 3 4 5 6 6 7 1 The mc_cable diagnostic is initiated on node 1. 2 Node 1 reports that mca0 is on line but has not communicated with the Memory Channel adapter on node 0.
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 changed.
Table 5–4: Adding a Memory Channel Interconnect or Rolling from a Dual, Redundant MC1 Interconnect to MC2 Interconnects Step Action Refer to: 1 If desired, manually relocate all applications from the cluster member that will be shut down using the cluster application availability (CAA) caa_relocate command. TruCluster Server Cluster Administration 2 On the system having an MC1 adapter installed or replaced, log in as the root user and execute the shutdown -h utility to halt the system.
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.
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 Figure 5–5 one system, and on one rail at a time. Use a BN39B-10 link cable to connect the new MC2 adapter to the linecard in the MC2 hub that corresponds to the same linecard that the MC1 module was connected to in the MC1 hub.
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.
(dbx) { p rm_adapters[1]->rmp_prail_va->rmc_size [0] [1] [2] [3] [4] [5] [6] [7] 16384 0 16384 0 16384 0 0 0 5 6 6 6 } 1 Check the size of a logical rail. 2 The logical rail is operating at 128 MB (16384 8-KB pages). 3 Verify the jumper settings for the member systems on the. first physical rail. 4 The J3 jumper is set at 512 MB for nodes 0, 2, and 4 on the first physical rail (65536 8-KB pages). 5 Verify the jumper settings for the member systems on the second physical rail.
Figure 5–2 shows a dual, redundant virtual hub configuration using MC1 hardware being upgraded to MC2.
Figure 5–3 through Figure 5–8 show a three-node standard hub configuration being upgraded from MC1 to MC2.
Figure 5–4: MC1 to MC2 Standard Hub Rolling Upgrade: First MC1 Module Replaced MC1 Hub #1 MC2 Hub #1 0/opto AlphaServer Member System 1 MC2 MC1 MC1 MC1 AlphaServer Member System 3 MC1 AlphaServer Member System 2 MC1 MC1 Hub #2 ZK-1523U-AI 5–22 Setting Up the Memory Channel Cluster Interconnect
Figure 5–5: MC1 to MC2 Standard Hub Rolling Upgrade: Replace First MC1 Adapter in Second System MC2 Hub #1 0/opto opto only AlphaServer Member System 1 MC2 MC2 MC1 MC1 AlphaServer Member System 3 MC1 AlphaServer Member System 2 MC1 MC1 Hub #2 ZK-1524U-AI Setting Up the Memory Channel Cluster Interconnect 5–23
Figure 5–6: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Third System Memory Channel Adapters MC2 Hub #1 1/opto opto 0/opto only AlphaServer Member System 1 MC2 MC2 MC1 MC1 AlphaServer Member System 3 MC2 AlphaServer Member System 2 MC2 1/opto MC2 Hub #2 MC1 Hub #2 ZK-1525U-AI 5–24 Setting Up the Memory Channel Cluster Interconnect
Figure 5–7: MC1 to MC2 Standard Hub Rolling Upgrade: Replace Second MC1 in Second System MC2 Hub #1 0/opto opto 1/opto only AlphaServer Member System 1 MC2 MC2 MC1 MC2 AlphaServer Member System 3 MC2 AlphaServer Member System 2 MC2 1/opto opto only MC2 Hub #2 ZK-1526U-AI Setting Up the Memory Channel Cluster Interconnect 5–25
Figure 5–8: MC1 to MC2 Standard Hub Rolling Upgrade: Final Configuration MC2 Hub #1 1/opto opto 0/opto only AlphaServer Member System 1 MC2 MC2 MC2 MC2 AlphaServer Member System 3 MC2 AlphaServer Member System 2 MC2 0/opto opto only 1/opto MC2 Hub #2 ZK-1527U-AI 5–26 Setting Up the Memory Channel Cluster Interconnect
6 Using Fibre Channel Storage This chapter provides an overview of Fibre Channel, Fibre Channel configuration examples, and information on Fibre Channel hardware installation and configuration in a Tru64 UNIX or TruCluster Server Version 5.1 configuration.
• The steps necessary to install and configure the Fibre Channel hardware (Section 6.5). • The steps necessary to install the base operating system and cluster software using disks accessible over the Fibre Channel hardware (Section 6.6). • Changing the HSG80 from transparent to multiple-bus failover mode (Section 6.7).
8. See the Tru64 UNIX Installation Guide and install the base operating system from the CD-ROM. The installation procedure will recognize the disks for which you set the device unit number. Select the disk you have chosen as the Tru64 UNIX operating system installation disk from the list of disks provided (Section 6.6.2). After the new kernel has booted to multi-user mode, complete the operating system installation. 9. Determine the /dev/disk/dskn values to be used for cluster installation (Section 6.6.
• 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 • MA6000 HSG60 Array Controller ACS Version 8.
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. Node The source and destination of a frame. A node may be a computer system, a redundant array of independent disks (RAID) array controller, or a disk device.
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. A link may be optical fiber, coaxial cable, or shielded twisted pair. E_Port An expansion port on a switch used to make a connection between two switches in the fabric. 6.2.
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 224 ports. The fabric examines the destination address in the frame header and routes the frame to the destination node. A fabric may consist of a single switch, or there may be several interconnected switches (up to three interconnected switches is supported).
Figure 6–2: Fabric Topology Node 1 Node 3 Transmit Transmit Transmit Transmit F_Port N_Port Receive F_Port N_Port Receive Receive Receive Fabric Node 2 Node 4 Transmit Transmit Transmit Transmit F_Port N_Port Receive Receive F_Port N_Port 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.
Figure 6–3: Arbitrated Loop Topology Node 3 Node 1 Receive Transmit NL_Port NL_Port Receive Transmit Hub 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.
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. • If there are dual-redundant HSG80 controllers, controller A port 1 and controller B port 2 are normally active; controller A port 1 and controller B port 1 are normally passive.
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. The host cannot initiate failover, and if you lose a host bus adapter, switch, or a cable, you lose the units behind at least one port.
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.
Figure 6–6: Multiple-Bus NSPOF Configuration Number 2 Member System 1 Memory Channel Memory Channel Interface Member System 2 Memory Channel KGPSA KGPSA KGPSA KGPSA Fibre Channel Switch Port 1 Port 1 Fibre Channel Switch HSG 80 Controller A HSG 80 Controller B Port 2 Port 2 RA8000/ESA12000 ZK-1707U-AI Using Fibre Channel Storage 6–13
Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 Member System 1 Memory Channel KGPSA Memory Channel Interface Member System 2 Memory Channel KGPSA KGPSA KGPSA Fibre Channel Switch Fibre Channel Switch Port 1 Port 1 HSG 80 Controller A HSG 80 Controller B Port 2 Port 2 RA8000/ESA12000 ZK-1765U-AI 6.4 Zoning and Cascaded Switches This section provides a brief overview of zoning and cascaded switches. 6.4.
Figure 6–8: A Simple Zoned Configuration Memory Channel Cluster 1 Member System 2 KGPSA Memory Channel Cluster 1 Member System 1 KGPSA 0 2 4 Memory Channel Cluster 2 Member System 1 KGPSA 6 Memory Channel Cluster 2 Member System 2 KGPSA 8 10 12 14 Fibre Channel Switch 1 Port 1 HSG 80 Controller A Port 1 HSG 80 Controller B 3 5 Port 2 Port 2 7 9 11 13 15 Port 1 HSG 80 Controller A Port 2 Port 1 HSG 80 Controller B Port 2 RA8000/ESA12000 RA8000/ESA12000 ZK-1709U-AI _______________
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.
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. The GBIC module is the electrical-to-optical converter.
3. Connect the Ethernet cable. 4. Connect the fiber-optic cables. 5. Connect power to the switch. 6. Turn on the power. The switch runs a series of power-on self test (POST) tests. The DS-DSGGC-AA has no power switch; power is applied when the unit is plugged in. 7. Set the switch IP address and subnet mask (see Section 6.5.1.2.2). You can also set the switch name if desired (see Section 6.5.1.2.5).
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. The four front panel buttons are: • Up — Upward triangle: Scrolls the menu up (which effectively moves down the list of commands) or increases the value being displayed.
____________________ Note _____________________ Pressing the down button selects the next lower top-level menu. The top-level menus are: Configuration Menu Operation Menu Status Menu Test Menu 2. Press Enter to display the first submenu item in the configuration menu, Ethernet IP address: Ethernet IP address: 10.00.00.10 -- The underline cursor denotes the selected address field. Use the up or down button to increase or decrease the displayed number. Use the Tab/Esc button to select the next field.
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. 6.5.1.2.
When you have completed setting the IP address and subnet mask, disconnect the PC or terminal from the DS-DSGGB-AA or DS-DSGGC-AA switch. 6.5.1.2.4 Logging In to the Switch with a Telnet Connection Before you telnet to a Fibre Channel switch, you must set the Ethernet IP address and subnet mask. ______________________ Note _______________________ A serial port connection and a telnet session cannot both be active (at the same time) with the DS-DSGGB-AA and DS-DSGGC-AA switch.
______________________ 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. For example, if a system’s /etc/hosts file contains an alias for the switch’s IP address, set the switch name to the alias.
• 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. 1. If necessary, install the mounting bracket on the KGPSA-BC module. Place the mounting bracket tabs on the component side of the board. Insert the screws from the solder side of the board. 2.
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. Use the init command or a system reset to re-initialize the system after you have completed using the wwid manager.
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. Both messages are benign and can be ignored for the fabric mode of operation. To correct the Nvram read failed situation, use the wwidmgr -set adapter command.
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. The worldwide name assigned to a subsystem never changes.
6.5.3 Setting Up the HSG80 Array Controller for Tru64 UNIX Installation 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. To set up an HSG80 for TruCluster Server operation, follow these steps: 1.
8. • 9600 BPS • 8 data bits • 1 stop bit • No parity Connect the RA8000 or ESA12000 to the power source and apply power. ____________________ Note _____________________ The KGPSA host bus adapters must be cabled to the switch, with the system power applied before you turn power on to the RA8000/ESA12000, in order for the HSG80 to see the connection to the KGPSAs. 9.
2 Prevents the command line interpreter (CLI) from reporting a misconfiguration error resulting from not having a failover mode set. 3 Puts the controller pair into multiple-bus failover mode. Ensure that you copy the configuration information from the controller known to have a good array configuration. __________________ Note ___________________ Use the command set failover copy = this_controller to set transparent failover mode.
Example 6–1: Determine HSG80 Connection Names HSG80 show connection Connection Name Operating system !NEWCON49 TRU64_UNIX HOST_ID=1000-0000-C920-DA01 Controller Port Address Status Unit Offset THIS 2 230813 OL this 0 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON50 TRU64_UNIX THIS HOST_ID=1000-0000-C920-DA01 1 230813 OL this 0 ADAPTER_ID=1000-0000-C920-DA01 !NEWCON51 TRU64_UNIX THIS HOST_ID=1000-0000-C920-EDEB 2 230913 OL this 0 ADAPTER_ID=1000-0000-C920-EDEB !NEWCON52 TRU64_UNIX THIS HOST_ID=1000-0
____________________ 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.
____________________ 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.
– 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: • If you replace one controller of a dual-redundant pair, the NVRAM from the remaining controller retains the configuration information (including worldwide name).
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. This section describes how to perform the following tasks: • Configure HSG80 storagesets — In this document, example storagesets are configured for both Tru64 UNIX and TruCluster Server on Fibre Channel storage.
• Reset the bootdef_dev console environment variable to provide multiple boot paths (Section 6.6.6). • Add additional systems to the cluster Section 6.6.7). If you are installing the Tru64 UNIX operating system or TruCluster 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 disks. 6.6.1.
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. The other mirrorset, CROOT-MIR, will be used for the cluster root (/), cluster /usr, cluster /var, and quorum disks.
Example 6–2: Setting Up the Mirrorset (cont.
2 Create the BOOT-MIR mirrorset using disks 30200 and 30300 and the CROOT-MIR mirrorset using disks 40000 and 40100. 3 Initialize the BOOT-MIR and CROOT-MIR mirrorsets. If you want to set any initialization switches, you must do so in this step. The BOOT-MIR mirrorset will be used for the Tru64 UNIX and cluster member system boot disks. The CROOT-MIR mirrorset will be used for the cluster root (/), cluster /usr and cluster /var file systems, and the quorum disk.
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: • Assign a unit number to each storage unit and disable all access to the storage unit. • Set an identifier for each storage unit. • Enable selective access to the storage unit.
Example 6–3: Adding Units and Identifiers to the HSG80 Storagesets (cont.) again enable the ones specified HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON68,!NEWCON74,!NEWCON76,!NEWCON77 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit.
Record the unit name of each partition with the intended use for that partition (see Table 6–2). 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. for instance, if the unit number is D133, use 133 as the UDID. Note, however, that the identifier must be unique.
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.
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: 1. 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. Record the UDIDs.
console command, it would not detect the Fibre Channel devices connected to the HSG80.
or wwidmgr -set command. In this example, none of the wwidn environment variables is set. 4. Look through the wwidmgr -show wwid display (see Example 6–4) and locate the UDID for the Tru64 UNIX disk (133) and each member system boot disks (131, 132) to ensure the storage unit is seen. As a second check, compare the worldwide name values. 5. Use the wwidmgr command with the -quickset option to set a device unit number for the Tru64 UNIX Version 5.
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: dga133.1001.0.1.0 pga0.0.0.1.0 dga133.1002.0.1.0 pga0.0.0.1.0 dga133.1003.0.1.0 pga0.0.0.1.0 dga133.1004.0.1.0 pga0.0.0.1.0 dgb133.1001.0.2.0 pgb0.0.0.2.0 dgb133.1002.0.2.0 pgb0.0.0.2.0 dgb133.1003.0.2.0 pgb0.0.0.2.0 dgb133.1004.0.2.0 pgb0.0.0.2.
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).
Example 6–6: Sample Fibre Channel Device Names P00>>> show dev dga131.1001.0.1.0 dga131.1002.0.1.0 dga131.1003.0.1.0 dga131.1004.0.1.0 dga133.1001.0.1.0 dga133.1002.0.1.0 dga133.1003.0.1.0 dga133.1004.0.1.0 dgb131.1001.0.2.0 dgb131.1002.0.2.0 dgb131.1003.0.2.0 dgb131.1004.0.2.0 dgb133.1001.0.2.0 dgb133.1002.0.2.0 dgb133.1003.0.2.0 dgb133.1004.0.2.0 dka0.0.0.1.1 dqa0.0.0.15.0 dva0.0.0.1000.0 ewa0.0.0.5.1 pga0.0.0.1.0 pgb0.0.0.2.0 pka0.7.0.1.
To set the bootdef_dev console environment variable for the Tru64 UNIX installation when booting from a Fibre Channel device, follow these steps: 1. Obtain the device name for the Fibre Channel storage unit where you will install the 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. You can also use the wwidmgr -show reachability command to determine reachability.
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. Verify the identifier from the table you have been preparing (see Table 6–2).
67: /dev/disk/dsk20c 68: /dev/disk/dsk21c DEC DEC HSG80 HSG80 IDENTIFIER=143 IDENTIFIER=144 If you know that you have set the UDID for a large number of disks, you can also grep for the UDID: # hwmgr -view dev | grep IDENTIFIER | grep 131 ____________________ Note _____________________ If you have not set the UDID, you can use hwmgr to determine the /dev/disk/dskn name by using the hardware manager to display device attributes and searching for the storage unit worldwide name as follows: # hwmgr -ge
2. 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. Record the information for use when you install the cluster software. You must label the disks before you install cluster software. 6.6.
To reset the bootdef_dev console environment variable, follow these steps: 1. Obtain the device name and worldwide name for the Fibre Channel unit from where you will boot cluster member system 1 (see Table 6–2). 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.
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.
b. Set the bootdef_dev console environment variable to one reachable path (Yes in the connected column of Example 6–7) to the member system boot disk: P00>>> set bootdef_dev dga132.1002.0.1.0 c. 2. Boot genvmunix on the newly added cluster member system. Each installed subset will be configured and a new kernel will be built and installed. After the new kernel is built, do not reboot the new cluster member system.
dga132.1004.0.1.0 dgb132.1002.0.2.0 dgb132.1003.0.2.0 dga132.1001.0.1.0 1 2 3 4 1 Path from host bus adapter A to controller A port 1 2 Path from host bus adapter B to controller A port 2 3 Path from host bus adapter B to controller B port 1 4 Path from host bus adapter A to controller B port 2 c.
6.7.1 Overview The change in failover modes cannot be accomplished with a simple SET MULTIBUS COPY=THIS HSG80 CLI command because: • Unit offsets are not changed by the HSG80 SET MULTIBUS_FAILOVER COPY=THIS command. 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.
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: 1. 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. 2. At the HSG80, set multiple-bus failover as follows.
HOST_ID=1000-0000-C921-09F7 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON58 TRU64_UNIX OTHER HOST_ID=1000-0000-C921-09F7 1 offline 0 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON59 TRU64_UNIX THIS HOST_ID=1000-0000-C921-09F7 1 offline 0 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON60 TRU64_UNIX OTHER HOST_ID=1000-0000-C921-09F7 2 offline 100 ADAPTER_ID=1000-0000-C921-09F7 !NEWCON61 TRU64_UNIX THIS HOST_ID=1000-0000-C921-086C 2 210513 OL this 100 ADAPTER_ID=1000-0000-C921-086C !NEWCON62 TRU64_UNIX OTHER HOST_ID=10
__________________ 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>>> b. For each wwidn line, record the unit number (131, 132, and 133) and worldwide name for the storage unit. The unit number is the first field in the display (after wwidn).
wwid2 wwid3 N1 50001fe100000d64 N2 50001fe100000d62 N3 50001fe100000d63 N4 50001fe100000d61 P00>>> init h. Set the bootdef_dev console environment variable to the member system boot device. Use the paths shown in the reachability display of the wwidmgr -quickset command for the appropriate device (see Section 6.6.6). i. Repeat steps a through h on each system accessing devices on the HSG80. 6.
SCSI tgt id SCSI tgt id SCSI tgt id nodename 5 : portname nodename 6 : portname nodename 7 : portname nodename 5000-1FE1-0000-0CB0 1000-0000-C920-A7AE 1000-0000-C920-A7AE 1000-0000-C920-CD9C 1000-0000-C920-CD9C 1000-0000-C921-0D00 1000-0000-C921-0D00 (emx0) 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.
portname 2004-0060-6900-5A1B nodename 1000-0060-6900-5A1B Present, Logged in, F_PORT, 1 Status of the emx1 link. The connection is a point-to-point fabric (switch) connection, and the link is up. The adapter is on SCSI bus 3 at SCSI ID 7. Both the port name and node name of the adapter (the worldwide name) are provided. The Fibre Channel DID number is the physical Fibre Channel address being used by the N_Port.
______________________ Note _______________________ You can use the emxmgr utility interactively to perform any of the previous functions. 6.8.
x. Exit ----> 2 emx0 SCSI target id assignments: SCSI tgt id 0 : portname 5000-1FE1-0000-0CB2 nodename 5000-1FE1-0000-0CB0 SCSI tgt id 5 : portname 1000-0000-C920-A7AE nodename 1000-0000-C920-A7AE SCSI tgt id 6 : portname 1000-0000-C920-CD9C nodename 1000-0000-C920-CD9C SCSI tgt id 7 : portname 1000-0000-C921-0D00 nodename 1000-0000-C921-0D00 Select Option (against "emx0"): 1. 2. 3. View adapter’s current Topology View adapter’s Target Id Mappings Change Target ID Mappings d. a. x.
7 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. Each subset is capable of running an operating system. The Tru64 UNIX Version 5.
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. • One or more network connections. • A Memory Channel interface. The AlphaServer GS80/160/320 system supports only the MC2 products.
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). A QBB I/O riser (local) is connected to a PCI I/O riser (remote) by BN39B cables.
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. See Figure 2–1 for PCI drawer slot layout. A primary PCI drawer contains: – A standard I/O module in slot 0-0/1 that has EEPROMs for the system control manager (SCM) and system reference manual (SRM) firmware.
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. They both must be connected to the OCP.
types of PCI drawers. It is harder to distinguish the type of PCI drawer from the rear, but slot 1 provides the key. The primary PCI drawer has a standard I/O module in slot 1, and the console and modem ports and USB connections are visible on the module.
Figure 7–3: Rear View of Expansion and Primary PCI Drawers I/O Riser 1 I/O Riser 0 Expansion PCI Drawer Console Serial Bus Node ID Module PCI Drawer Node ID CSB Connector Primary PCI Drawer Local Terminal/ COM1/Port PCI Drawer Node ID Standard I/O Module CSB Connector Console Serial Bus Node ID Module ZK-1751U-AI 7.3 Configuring Partitioned GS80, GS160, or GS320 Systems in a TruCluster Configuration An AlphaServer GS80/160/320 system can be a member of a TruCluster Server configuration.
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. Do not turn the key switch on. Only turn on the AC circuit breakers.
3. • 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). Use BN39B-01 cables (1-meter) for a PCI drawer in the GS80 RETMA cabinet. Use BN39B-04 cables (4-meter) if the PCI drawer is in a GS160 or GS320 power cabinet.
____________________ 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. If the auto_quit_scm SCM environment variable is set (equal 1), control will be passed to the SRM firmware at the end of the power-up sequence. Use the escape sequence (Esc Esc scm) to transfer control to the SCM firmware.
Example 7–1: Defining Hard Partitions with SCM Environment Variables (cont.) HP_QBB_MASK5 HP_QBB_MASK6 HP_QBB_MASK7 SROM_MASK XSROM_MASK PRIMARY_CPU PRIMARY_QBB0 AUTO_QUIT_SCM FAULT_TO_SYS DIMM_READ_DIS SCM_CSB_MASTER_ELIGIBLE PERF_MON SCM_FORCE_FSL OCP_TEXT AUTO_FAULT_RESTART SCM_SIZING_TIME 0 0 0 ff f ff ff ff ff ff ff ff ff ff 1 0 0 ff ff 6 1 0 0 1 7 20 0 AS GS160 1 c 1 Set the number of hard partitions to two. 2 Set bits 0 and 1 of the mask (0011) to select QBB 0 and QBB 1 for hard partition 0.
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. The other SCM will be a standby in case of a problem with the master SCM. If the node ID switch is set to zero, the CSB node ID will be 10 (Example 7–4).
2 Turn on power to partition 1. 3 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. Obtain a copy of the latest firmware release notes for the AlphaServer system (see Section 7.5).
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.
2 QBB number and console serial bus (CSB) node ID. QBB 0 and 1 (CSB node IDs 30 and 31) are in partition 0. QBB 2 and 3 (CSB node IDs 32 and 33) are in partition 1. 3 CPU module is present, powered up, and has passed self test (P). A dash (-) indicates an empty slot. An F indicates a self test failure. In this example, each QBB contains four CPU modules, each of which has passed self test. 4 Memory module is present, powered up, and has passed self test (P). A dash (-) indicates an empty slot.
12 Console serial bus node ID for PCI drawers. In this example, the first PCI drawer has node ID 10. The second PCI drawer has node ID 11. Note that in this case, the node ID switches are set to 0 and 1. 13 The status of each of the four PCI buses in a PCI drawer. An S indicates that a standard I/O module is present.
Example 7–4: Displaying Console Serial Bus Information (cont.) C3 C0 C1 31 31 C4 C5 C6 C7 32 32 C8 C9 CA CB C8 C9 33 33 CC CD CE CF 40 E0 E1 1 2 CPU3/SROM IOR0 IOR1 PSM XSROM CPU0/SROM CPU1/SROM CPU2/SROM CPU3/SROM PSM XSROM CPU0/SROM CPU1/SROM CPU2/SROM CPU3/SROM IOR0 IOR1 PSM XSROM CPU0/SROM CPU1/SROM CPU2/SROM CPU3/SROM HPM SCM MASTER SCM SLAVE V5.0-7 T05.4 T05.4 V5.0-7 V5.0-7 V5.0-7 V5.0-7 T05.4 T05.4 V5.0-7 V5.0-7 V5.0-7 V5.0-7 (03.24/01:09) (03.24/02:10) T05.4 T05.4 V5.0-7 V5.0-7 V5.0-7 V5.
• SCM master: This PCI primary drawer has the master SCM. • SCM slave: The SCM on this PCI primary drawer is a slave and has not been designated as a backup to the master. • CPUn/SROM: Each CPU module has SROM firmware that is executed as part of the power-up sequence. • XROM: Each CPU executes this extended SROM firmware on the PSM module after executing the SROM firmware. 3 The revision of the firmware and compilation date. 4 The revision of the fail-safe loader (FSL) firmware.
• – SCM: One on the standard I/O module of each primary PCI drawer – Power system manager (PSM): One on the PSM module in each QBB – PCI backplane manager (PBM): One on each PCI backplane – Hierarchical switch power manager (HPM): One on the H-switch PCI host bus adapter EEPROMS To update the AlphaServer GS80/160/320 firmware with the LFU utility, follow these steps: 1. At the console for each partition, shut down the operating system. 2.
5. 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> power on 6. Transfer control from the SCM to SRM firmware (if the auto_quit_scm SCM environment variable is not set): SCM_E0> quit P00>>> 7. Use the console show device command to determine which device is the CD-ROM. 8.
___________________ 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. 9. After you update the firmware, use the verify command to verify the firmware update, then transfer control back to the SCM and reset the system: P00>>> Esc Esc scm SCM_E0> reset 10.
8 Configuring a Shared SCSI Bus for Tape Drive Use The topics in this section provide information on preparing the various tape devices for use on a shared SCSI bus with the TruCluster Server product. ______________________ Notes ______________________ Section 8.7 and Section 8.8 provide documentation for the TL890/TL891/TL892 MiniLibrary family as sold with the DS-TL891-NE/NG, DS-TL891-NT, DS-TL892-UA, DS-TL890-NE/NG part numbers.
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.
Table 8–1: TZ88N-VA Switch Settings SCSI ID SCSI ID Selection Switches 1 2 3 4 5 6 Automatica Off Off Off On On On 0 Off Off Off Off Off Off 1 On Off Off Off Off Off 2 Off On Off Off Off Off 3 On On Off Off Off Off 4 Off Off On Off Off Off 5 On Off On Off Off Off 6 Off On On Off Off Off 7 On On On Off Off Off a SBB tape drive SCSI ID is determined by the SBB physical slot. 8.1.
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.
Table 8–2: Hardware Components Used to Create the Configuration Shown in Figure 8–2 (cont.) Callout Number Description 8 DWZZA-VA with H885-AA trilink connector 9 DWZZB-VW with H885-AA trilink connector a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters. c The maximum combined length of these cables must not exceed 25 meters. 8.1.
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. You can add additional TZ88N-TA tape drives to the differential shared SCSI bus by adding additional DWZZA or DWZZB/TZ88N-TA combinations.
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.
Table 8–3: DS-TZ89N-VW Switch Settings (cont.
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. 8.2.4 Cabling the DS-TZ89N-TA Tape Drives You must connect the DS-TZ89N-TA tabletop model to a single-ended segment of the shared SCSI bus.
8.3 Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is a Digital Linear Tape (DLT) tabletop cartridge tape drive capable of holding up to 40 GB of data per Compactape IV cartridge using 2:1 compression. It is capable of storing/retrieving data at a rate of up to 10.8 GB per hour (using 2:1 compression). The Compaq 20/40 GB DLT Tape Drive uses CompacTape III, CompacTape IIIXT, or CompacTape IV media. It is a narrow, single-ended SCSI device, and uses 50-pin, high-density connectors.
Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel SCSI ID SCSI ID Selector Switch + 0 + 0 - - 20/40 GB DLT Tape Drive ZK-1603U-AI 8.3.2 Cabling the Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is connected to a single-ended segment of the shared 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.
cable). Ensure that the trilink or Y cable at both ends of the differential segment of the shared SCSI bus is terminated with an HD68 differential terminator such as an H879-AA. The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with cable part number 146745-003 or 146776-003 (0.9-meter cables) as long as the SCSI bus maximum length of 3 meters (fast SCSI) is not exceeded.
Figure 8–5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT Tape Drive Network Member System 1 Memory Channel T KZPBA-CB (ID 6) T Member System 2 Memory Channel Interface 7 Memory Channel 6 KZPBA-CB (ID 7) 5 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 1 1 + 0 T - DS-DWZZH-03 T T T 10 T 9 2 3 T Controller B HSZ70 20/40 GB DLT Tape Drive 4 6 8 DWZZB-AA Controller A HSZ70 StorageWorks RAID Array 7000 ZK-1604U-AI Table 8–4 shows the components used to create the cluster shown in
Table 8–4: Hardware Components Used to Create the Configuration Shown in Figure 8–5 (cont.) Callout Number Description 9 199629-002 or 189636-002 (68-pin high density to 50-pin high density 1.8-meter cables) 10 341102-001 50-pin high density 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. c The maximum combined length of these cables must not exceed 25 meters. 8.
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. To configure the shared SCSI bus for use with a Compaq 40/80-GB DLT Drive, follow these steps: 1. You need one DWZZB-AA for each shared SCSI bus with a Compaq 40/80-GB DLT Drive. Ensure that the DWZZB-AA jumpers W1 and W2 are installed to enable the single-ended termination.
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.
Table 8–5: Hardware Components in the Configuration in Figure 8–6 (cont.) Callout Number Description 8 H885-AA trilink connector 9 189646-001 (0.9 meter cable) or 189646-002 (1.8 meter cable)d BN21K-01 or BN21L-01 (1 meter cable)d BN21K-02 or BN21L-02 (2 meter cable)d 10 152732-001 LVD terminator 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.
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. To configure the shared SCSI bus for use with a TZ885, follow these steps: 1. You will need one DWZZA-AA or DWZZB-AA for each TZ885 tape drive.
______________________ Note _______________________ Ensure that there is no conflict with tape drive and host bus adapter SCSI IDs.
Table 8–6: Hardware Components Used to Create the Configuration Shown in Figure 8–6 (cont.) Callout Number Description 8 H885-AA trilink connector 9 BN21M cable 10 H8574-A terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters. c The maximum combined length of these cables must not exceed 25 meters. 8.
Figure 8–8: TZ887 DLT MiniLibrary Rear Panel SCSI ID Selector Switch SCSI ID + 0 + 0 - - 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. Figure 8–9 shows a configuration with a TZ887 for use on a shared SCSI bus. To configure the shared SCSI bus for use with a TZ887, follow these steps: 1.
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. ______________________ Note _______________________ Ensure that there is no conflict with tape drive and host bus adapter SCSI IDs.
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. The TL891 and TL892 MiniLibraries use one (TL891) or two (TL892) TZ89N-AV differential tape drives and a robotics controller, which access cartridges in a 10-cartridge magazine.
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. Rectangles present on this line indicate cartridges present in the corresponding slot of the magazine. For example, this fourth line (0> X X _ _ _ _ _ _ _ <9, where X represents rectangles) indicates that cartridges are installed in slots 0 and 1.
4. Select the tape drive (DLT0 Bus ID: or DLT1 Bus ID:) or library robotics (LIB Bus ID:) for which you wish to change the SCSI bus ID. The default SCSI IDs are as follows: • Lib Bus ID: 0 • DLT0 Bus ID: 4 • DLT1 Bus ID: 5 Use the up or down arrow button to select the item for which you need to change the SCSI ID. Press the Enter button. 5. Use the up or down arrow button to scroll through the possible SCSI ID settings. Press the Enter button when the desired SCSI ID is displayed. 6.
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. ______________________ Note _______________________ It is assumed that the library robotics is on the same SCSI bus as tape drive 1.
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: 1. Connect a BN21K or BN21L between the last trilink connector on one shared SCSI bus to the leftmost connector (as viewed from the rear) of the TL892. 2. Connect a BN21K or BN21L between the last trilink connector on the second shared SCSI bus to the left DLT2 connector (the fifth connector from the left). 3. Install a 0.
Figure 8–10: TruCluster Server Cluster with a TL892 on Two Shared SCSI Buses Network Memory Channel Interface Member System 1 Member System 2 T 6 KZPBA-CB (ID 6) KZPBA-CB (ID 7) 5 7 5 KZPBA-CB (ID 7) 5 T KZPBA-CB (ID 6) T 7 Memory Channel Memory Channel 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 7 1 1 T DS-DWZZH-03 T Library Robotics DLT1 T 6 2 3 T Controller B HSZ70 4 DLT2 Expansion Unit Interface Controller A HSZ70 StorageWorks RAID Array 7000 TL892 1 Ft SCSI Bus Jumper ZK-1
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 bus with a tape library. 8.8.
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.
____________________ 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. The TL890 library robotics is on one shared SCSI bus, and the two TZ89 tape drives in each TL892 are on separate, shared SCSI buses.
Figure 8–11: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses Network Memory Channel Interface Member System 1 T Memory Channel 6 7 Member System 2 7 Memory Channel 6 KZPBA-CB (ID 6) KZPBA-CB (ID 6) KZPBA-CB (ID 6) T 5 T 5 5 KZPBA-CB (ID 7) KZPBA-CB (ID 7) 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 1 1 5 KZPBA-CB (ID 7) T 6 5 T DS-DWZZH-03 T T 2 7 3 T 7 4 Diag Controller B HSZ70 Controller A HSZ70 StorageWorks RAID Array 7000 Motor 6 SCSI TL890 Robotics Control cabl
Table 8–8: Hardware Components Used to Create the Configuration Shown in Figure 8–10 Callout Number Description 1 BN38C or BN38D cablea 2 BN37A cableb 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator 5 BN21W-0B Y cable 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cablec 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.
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. A rectangle in place of the underscore indicates that a cartridge is present in that location. 2. Press the Enter button to enter the Menu Mode, displaying the Main Menu. 3.
inventory of modules may be incorrect and the contents of some or all of the modules will be inaccessible to the system and to the host. When the expansion unit comes up, it will communicate with each base module through the expansion unit interface and inventory the number of base modules, tape drives, and cartridges present in each base module.
4. Press the down arrow button until the Configure Menu item is selected, and then press the Enter button to display the Configure submenu. 5. Press the down arrow button until the Set SCSI item is selected and press the Enter button. 6. 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 ID.
______________________ 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. The following sections describe how to prepare the TL894 in more detail. 8.9.
Menu: Configuration Inquiry 6. Press and release the up or down arrow buttons to locate the SCSI Address submenu, and verify that the following information is displayed in the SDA: Menu: Configuration SCSI Address .. 7. Press and release the SELECT button to choose the SCSI Address submenu and verify that the following information is displayed in the SDA: Menu: Configuration Robotics 8.
6. Press and release the SELECT button again to choose SCSI Address and verify that the following information is shown in the SDA: Menu: SCSI Address Robotics 7. Use the down arrow button to bypass the Robotics submenu and verify that the following information is shown in the SDA: Menu: SCSI Address Drive 0 8. Use the up and down arrow buttons to select the drive number to set or change. 9.
Figure 8–12: TL894 Tape Library Four-Bus Configuration Robotics Controller *SCSI Address 0 Tape Drive Interface PWA SCSI Cable 1.
installing an HD68 SCSI bus terminator on the SCSI bus port connector on the cabinet exterior. This is not wrong, but by reconfiguring in this manner, the length of the SCSI bus is increased by 1.5 meters, and may cause problems if SCSI bus length is of concern. In a future revision of the previously mentioned guide, the bus configuration figures will be modified to show all SCSI buses terminated at the tape drives. 8.9.
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.
Table 8–10: Hardware Components Used to Create the Configuration Shown in Figure 8–12 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cablec 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. c The maximum combined length of these cables must not exceed 25 meters. 8.
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. 8.10.1 TL895 Robotic Controller Required Firmware Robotic firmware version N2.20 is the minimum firmware revision supported in a TruCluster Server cluster.
3. 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. 4. To change any of the configurations, press the Configure button. 5. Press the Select button until the item you wish to configure is highlighted.
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. We also recommend that storage be placed on shared SCSI buses that do not have tape drives. To reconfigure TL895 SCSI bus configuration, follow these steps: 1.
Figure 8–14: TL895 Tape Library Internal Cabling Robotics Controller SCSI ID 0 Tape Drive 0 SCSI ID 1 Tape Drive 1 SCSI ID 2 Terminator PN 0415619 SCSI Jumper Cable PN 6210567 Tape Drive 2 SCSI ID 3 SCSI Port 8 SCSI Port 7 Terminator SCSI Port 6 Tape Drive 3 SCSI ID 4 SCSI Port 5 Jumper Cable Tape Drive 4 SCSI ID 5 SCSI Port 4 Terminator SCSI Port 3 Tape Drive 5 SCSI ID 1 SCSI Port 2 Jumper Cable SCSI Port 1 Tape Drive 6 SCSI ID 2 Terminator ZK-1397U-AI 8.10.
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.
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. Each tape library utilizes bulk loading of bin packs, with each bin pack containing a maximum of 11 cartridges. Bin packs are arranged on an eight-sided carousel that provides either two or three bin packs per face.
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. Multi-unit configurations are not discussed in this manual.
Table 8–12: MUC Switch Functions (cont.) Switch Function 7 Host selection: Down for SCSI, up for seriala 8 Must be down, reserved for testing a For a TruCluster Server cluster, switch 7 is down, allowing switches 1, 2, and 3 to select the MUC SCSI ID. 8.11.3 Setting the MUC SCSI ID The multi-unit controller (MUC) SCSI ID is set with switch 1, 2, and 3, as shown in Table 8–13. Note that switch 7 must be down to select the SCSI bus and enable switches 1, 2, and 3 to select the MUC SCSI ID.
Table 8–15: TL896 Default SCSI IDs Device Default SCSI ID MUC 2 Drive 5 (top) 5 E Drive 4 4 F Drive 3 3 A Drive 2 5 B Drive 1 4 C Drive 0 (bottom) 3 SCSI Port D 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: • The SCSI input for the TL893 is high-density, 68-pin differential.
; Figure 8–15: TL893 Three-Bus Configuration 0415498 (50-Pin Micro-D Terminator) 0425031 (SCSI Diff Feed Through) MUC SCSI Address 2 TZ89 Tape Drive SCSI Address 5 (top shelf) TZ89 Tape Drive SCSI Address 4 (middle shelf) TZ89 Tape Drive SCSI Address 3 (bottom shelf) 0425017 (Cable) 9-01 409 6 20 62 1 99-0 040 9-01 409 6 20 0415619 (68-pin Micro-D Terminator) 0415619 (68-pin Micro-D Terminator) Drive Housing SCSI Port A SCSI Port B SCSI Port C (Rear Connector Panel) ZK-1326U-AI • The SCSI
;; – The lower bay bottom shelf tape drive (tape drive 0, SCSI ID 3) is on SCSI Port C and is terminated on the tape drive. – The tape drive terminators are 68-pin differential terminators (part number 0415619).
on the shared SCSI bus. Each SCSI bus must be terminated internal to the tape library at the tape drive itself with the installed SCSI terminators. Therefore, TL893 and TL896 tape libraries must be on the end of the shared SCSI bus. In a TruCluster Server cluster with TL893 or TL896 tape libraries, the member systems and StorageWorks enclosures or RAID subsystems may be isolated from the shared SCSI bus because they use trilink connectors or Y cables.
Figure 8–17: Shared SCSI Buses with TL896 in Three-Bus Mode Network Memory Channel Interface Member System 1 T Memory Channel 6 7 Member System 2 7 Memory Channel 6 KZPBA-CB (ID 6) KZPBA-CB (ID 6) KZPBA-CB (ID 6) T 5 T 5 KZPBA-CB (ID 7) KZPBA-CB (ID 7) 5 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 1 1 5 KZPBA-CB (ID 7) T 6 5 T DS-DWZZH-03 T T 2 7 3 T Controller B HSZ70 7 4 Controller A HSZ70 StorageWorks RAID Array 7000 TL896 A B C D E F SCSI Ports (3-bus mode) ZK-1626U-A
Table 8–16: Hardware Components Used to Create the Configuration Shown in Figure 8–16 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cablec 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. c The maximum combined length of these cables must not exceed 25 meters. 8.
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. The configuration must contain at least one expansion unit and one base unit.
• 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.
Table 8–17: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary Configured for Maximum: Number of Number of Transfer Base Unitsa b Data Unitsc Rated Storage Capacitye Performance 5 0 15 MB/sec (54 GB/hour) 1.32 TB (66 50 MB/sec cartridges) (180 GB/hour) 2.31 TB (66 cartridges) Capacity 1 4 3 MB/sec (10.8 GB/hour) 1.8 TB (90 10 MB/sec cartridges) (36 GB/hour) 3.
Table 8–18: DLT MiniLibrary Part Numbers (cont.) DLT Library Component Number of Tape Drives Tabletop/Rackmount Part Number TL891 DLT MiniLibrary Base Unit 2 Rackmount 120876-B22 Add-on DLT 35/70 drive for TL891 1 N/A 120878-B21 MiniLibrary Expansion Unit N/A Rackmount 120877-B21 MiniLibrary Data Unit N/A Rackmount 128670-B21 ______________________ Note _______________________ The TL881 DLT MiniLibrary tabletop model is available as fast, wide differential or fast, wide single-ended.
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. When power is first applied to a MiniLibrary, a series of POST diagnostics are performed.
status until you exit the Menu Mode and the Ready light comes on once again. 2. Depress the down arrow button until the Configure Menu item is selected, then press the Enter button to display the Configure submenu. ____________________ Note _____________________ The control panel up and down arrows have an auto-repeat feature. When you press either button for more than one-half second, the control panel behaves as if you were pressing the button about four times per second.
______________________ 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). A 0.3-meter SCSI jumper cable is provided with the unit.
3. 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: 1. 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. 2. Install a 0.
Figure 8–18: TL891 Standalone Cluster Configuration Network Member System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) T KZPBA-CB (ID 7) 5 6 T 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 1 1 T Library Robotics T DLT1 6 T DS-DWZZH-03 7 2 3 T 4 DLT2 Controller B HSZ70 Controller A HSZ70 StorageWorks RAID Array 7000 Expansion Unit Interface TL891 0.
Table 8–19: Hardware Components Used to Create the Configuration Shown in Figure 8–17 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cablec 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. c The maximum combined length of these cables must not exceed 25 meters. 8.12.2.
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.
Figure 8–19: TL891 DLT MiniLibrary Rackmount Configuration Network Memory Channel Interface Member System 1 Memory Channel Memory Channel T 6 KZPBA-CB (ID 6) 5 KZPBA-CB (ID 7) 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 7 1 1 7 5 KZPBA-CB (ID 7) T KZPBA-CB (ID 6) T Member System 2 T DS-DWZZH-03 T T Diag Motor 2 3 T 4 Expansion Unit 6 SCSI Controller B HSZ70 Controller A HSZ70 StorageWorks RAID Array 7000 Expansion Modules Robotics Control cables Library Robotics DLT2 6 TL891
Table 8–20: Hardware Components Used to Create the Configuration Shown in Figure 8–18 Callout Number Description 1 BN38C or BN38D cablea 2 BN37A cableb 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator 5 BN21W-0B Y cable 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cablec 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.
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. 2. Press the Enter button to enter the Menu Mode, displaying the Main Menu. 3. Depress the down arrow button until the Configure Menu item is selected, then press the Enter button.
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.
• DLT3 Bus ID: 4 • DLT4 Bus ID: 5 • DLT5 Bus ID: 6 7. Press Enter when you have the item selected for which you wish to change the SCSI ID. 8. Use the up and down arrows to select the desired SCSI ID. Press the Enter button to save the new selection. 9. Press the Escape button once to return to the Set SCSI Submenu to select another tape drive or the library robotics, and then repeat steps 6, 7, and 8 to set the SCSI ID. 10.
______________________ Note _______________________ These tape devices have been qualified for use on shared SCSI buses with both the KZPSA-BB and KZPBA-CB host bus adapters. 8.13.2 ESL9326D Enterprise Library Overview The ESL9326D Enterprise Library is an enterprise Digital Linear Tape (DLT) automated tape library with from 6 to 16 fast-wide, differential tape drives. This tape library uses the 35/70 DLT (DS-TZ89N-AV) differential tape drives. The SCSI bus connectors are 68-pin, high-density.
______________________ Notes ______________________ The ESL9326D Enterprise Library is cabled internally for two 35/70 DLT tape drives on each SCSI bus. It arrives with the library electronics cabled to tape drives 0 and 1. Every other pair of tape drives is cabled together (2 and 3, 4 and 5, 6 and 7, and so on).
Figure 8–20: ESL9326D Internal Cabling Tape Drive 8 SCSI ID 2 Tape Drive 0 SCSI ID 2 Tape Drive 9 SCSI ID 3 Tape Drive 1 SCSI ID 3 Tape Drive 10 SCSI ID 4 Tape Drive 2 SCSI ID 4 Tape Drive 11 SCSI ID 5 Tape Drive 3 SCSI ID 5 Tape Drive 12 SCSI ID 2 Tape Drive 4 SCSI ID 2 Tape Drive 13 SCSI ID 3 Tape Drive 5 SCSI ID 3 Tape Drive 14 SCSI ID 4 Tape Drive 6 SCSI ID 4 Tape Drive 15 SCSI ID 5 Tape Drive 7 SCSI ID 5 Robotics SCSI ID 0 P T O N M L T T K J I Q R SCSI Bulkhead A T B T C
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. You must terminate each SCSI bus at the end of the SCSI bus by installing a terminator on the SCSI bulkhead SCSI connector.
______________________ Notes ______________________ Each ESL9326D Enterprise Library arrives with one 330563-001 HD68 terminator for each pair of tape drives (one SCSI bus). The kit also includes at least one 330582-001 jumper cable to connect the library electronics to tape drives 0 and 1.
9 Configurations Using External 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.
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.
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. They have removable termination. The DS-BA35X-DA personality module is used in the UltraSCSI BA356.
Figure 9–1: Standalone SCSI Signal Converter T T Single-ended side Differential side with trilink 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 T T Single-ended side Differential side with trilink attached ZK-1576U-AI 9.1.2.
______________________ 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. Figure 9–3: DS-BA35X-DA Personality Module Switches OFF ON 1 2 3 4 SCSI Bus Termination Switch S4 ON OFF 1 2 3 4 5 6 7 SCSI Bus Address Switch S3 ZK-1411U-AI 9.
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.
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. You can also use the BN21W-0B Y cable with a HSZ40 or HSZ50 controller or the unterminated differential side of a SCSI signal converter.
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. This is the case with the KZPBA-CB and KZPSA-BB SCSI adapters on some AlphaServer systems. Use the H879-AA terminator to terminate one leg of a BN21W-0B Y cable or H885-AA trilink.
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. ______________________ Note _______________________ Do not install disks in the slots corresponding to the host SCSI IDs (usually SCSI ID 6 and 7 for a two-node cluster).
Figure 9–6: BA350 Internal SCSI Bus JA1 JB1 0 T 1 2 3 4 J 5 6 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. It has a BA35X-MH 16-bit personality module (only used for SCSI ID selection) and a 150-watt power supply.
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. The jumper is accessed from the rear of the box. For operation within a TruCluster Server cluster, you must install the J jumper in the normal position, behind slot 6.
Figure 9–7: BA356 Internal SCSI Bus JA1 JB1 0 1 2 3 4 5 J 6 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.
Figure 9–8: BA356 Jumper and Terminator Module Identification Pins Slot 6 Jumper Pin Slot 1 Jumper Pin Slot 6 Terminator Pin Slot 1 Terminator Pin ZK-1529U-AI 9.3.2.2 UltraSCSI BA356 Storage Shelf The UltraSCSI BA356 (DS-BA356-JF or DS-BA356-KH) has a single-ended, wide UltraSCSI bus. The DS-BA35X-DA personality module provides the interface between the internal, single-ended UltraSCSI bus segment and the shared, wide, differential UltraSCSI bus. The UltraSCSI BA356 uses a 180-watt power supply.
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. DS-BA35X-DA termination is discussed in Section 9.1.2.2. 9.
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.
2. 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. 3. Attach an H885-AA trilink connector to the DWZZA-VA 68-pin high-density connector. 4. Install the DWZZA-VA in slot 0 of the BA350. 9.4.1.
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. The interface between the buses is the DS-BA35X-DA personality module installed in the UltraSCSI BA356.
must be used with a BA356 or UltraSCSI BA356 if more than five disks are required. The following sections provide the steps needed to connect two storage shelves and two member systems on a shared SCSI bus: • BA350 and BA356 (Section 9.4.2.1) • Two BA356s (Section 9.4.2.2) • Two UltraSCSI BA356s (Section 9.4.2.3) 9.4.2.
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 System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) T KZPSA-BB (ID 7) 2 T 2 1 1 3 3 BA356 BA350 3 4 DWZZB-VW DWZZA-VA ID 1 ID 9 Member 1 Boot Disk ID 2 ID 10 Member 2 Boot Disk ID 3 Quorum Disk ID 4 Data disk Do not use for data disk.
Table 9–1: Hardware Components Used for Configuration Shown in Figure 8–9 and Figure 8–10 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA terminator 3 BN21K (or BN21L) cablea 4 H885-AA trilink connector a The maximum combined length of the BN21K (or BN21L) cables must not exceed 25 meters. 9.4.2.
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 System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) T KZPSA-BB (ID 7) 2 T 2 1 1 3 3 BA356 BA356 3 4 Do not use for data disk. May be used for redundant power supply.
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: 1. Complete the steps of Section 9.4.1.3 for each UltraSCSI BA356.
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 System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) KZPBA-CB (ID 7) 1 T Tru64 UNIX Disk T 3 2 UltraSCSI BA356 2 4 UltraSCSI BA356 5 4 Data disks Do not use for data disk. May be used for redundant power supply.
Table 9–2: Hardware Components Used for Configuration Shown in Figure 9–11 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA HD68 terminator 3 BN38C (or BN38D) cablea 4 H8861-AA VHDCI trilink connector 5 BN37A cablea a The maximum combined length of the BN38C (or BN38D) and BN37A cables on one SCSI bus segment must not exceed 25 meters. 9.4.
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: 1. If the HSZ40 or HSZ50 will be on the end of the shared SCSI bus, attach an H879-AA terminator to an H885-AA trilink connector. 2. Attach an H885-AA trilink connector to each RAID controller port. Attach the H885-AA trilink connector with the terminator to the controller that will be on the end of the shared SCSI bus. 3.
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.
Figure 9–13: Externally Terminated Shared SCSI Bus with HSZ50 RAID Array Controllers at Bus End Network Member System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) 3 T 2 1 4 2 3 4 1 3 T HSZ50 Controller A HSZ50 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.
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: 1. 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: • Remove the five differential terminator resistor SIPs. • Ensure that the W1 and W2 jumpers are installed to enable the single-ended termination on one end of the bus.
2. Attach the trilink with the terminator to the controller that you want to be on the end of the shared SCSI bus. Attach an H885-AA trilink connector to the other controller. 3. Install a BN21K or BN21L cable between the H885-AA trilink connectors on the two controllers. The BN21L-0B is a 0.15-meter cable. 4. If you are using a DS-DWZZH-05: 5. 6. • Verify that the fair arbitration switch is in the Fair position to enable fair arbitration (see Section 3.6.1.2.
Figure 9–14 shows a sample configuration with radial connection of KZPSA-BB PCI-to-SCSI adapters, DS-DWZZH-03 UltraSCSI hub, and an HSZ50 RAID array controller. Note that the KZPSA-BBs could be replaced with KZPBA-CB UltraSCSI adapters without any changes in cables.
Figure 9–15 shows a sample configuration that uses KZPSA-BB SCSI adapters, a DS-DWZZH-05 UltraSCSI hub, and an HSZ50 RAID array controller.
10 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; it describes only how to set up the hardware in the context of the TruCluster Server product.
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.
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. This simplifies the configuration by reducing the number of cable connections.
_____________________ 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. • Is a single-channel, ultrawide differential adapter.
Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: 2 Power down the system. Install a KZPSA-BB PCI-to-SCSI adapter or KZPBA-CB UltraSCSI host adapter in the PCI slot corresponding to the logical bus to be used for the shared SCSI bus. Ensure that the number of adapters are within limits for the system, and that the placement is acceptable.
Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: 6 Section 10.1.4.1 through Section 10.1.4.3 and Example 10–6 through Example 10–9 Use the show pk* or show isp* console commands to determine the status of the KZPSA-BB or KZPBA-CB console environment variables, and then use the set console command to set the KZPSA-BB bus speed to fast, termination power to on, and the KZPSA or KZPBA-CB SCSI bus ID.
Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with External Termination Step Action Refer to: 1 Section 10.1.4.4, Figure 10–1, and KZPSA PCI-to-SCSI Storage Adapter Installation and User’s Guide Remove the KZPSA-BB internal termination resistors, Z1, Z2, Z3, Z4, and Z5. Remove the eight KZPBA-CB internal termination Section 4.3.3.3, resistor SIPs, RM1-RM8. Figure 4–1, and KZPBA-CB PCI-to-Ultra SCSI Differential Host Adapter User’s Guide 2 Power down the member system.
Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with External Termination (cont.) Step Action Refer to: 7 Section 10.1.4.1 through Section 10.1.4.3 and Example 10–6 through Example 10–9 Use the show pk* or show isp* console commands to determine the status of the KZPSA-BB or KZPBA-CB console environment variables, and then use the set console command to set the KZPSA-BB bus speed to fast, termination power to on, and the KZPSA or KZPBA-CB SCSI bus ID.
Table 10–3: Installing a KZPSA-BB or KZPBA-CB for Use with External Termination (cont.) Step Action Refer to: TL890 with TL891/TL892 Section 8.8 TL894 Section 8.9 TL895 Section 8.10 TL893/TL896 Section 8.11 TL881/TL891 DLT MiniLibraries Section 8.12 Compaq ESL9326D Enterprise Library Section 8.13 _____________________ 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.
Example 10–1: Displaying Configuration on an AlphaServer 4100 (cont.
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 RZ28 442D dke200.2.0.5.1 DKe200 RZ26 392A dke300.3.0.5.1 DKe300 RZ26L 442D polling floppy0 (FLOPPY) pceb IBUS hose 0 dva0.0.0.1000.
Example 10–4: Displaying Devices on an AlphaServer 8200 >>> show device polling for units polling for units polling for units polling for units polling for units pke0.7.0.0.1 dke0.0.0.0.1 dke200.2.0.0.1 dke400.4.0.0.1 on isp0, slot0, bus0, hose0... on isp1, slot1, bus0, hose0... on isp2, slot4, bus0, hose0... on isp3, slot5, bus0, hose0... kzpaa0, slot0, bus0, hose1... kzpaa4 SCSI Bus ID 7 DKE0 RZ28 442D DKE200 RZ28 442D DKE400 RRD43 0064 polling for units dkf0.0.0.1.1 dkf1.0.0.1.1 dkf2.0.0.1.1 dkf3.0.0.
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. Note that the console environment variables used for the SCSI options vary from system to system.
Example 10–5: Displaying the pk* Console Environment Variables on an AlphaServer 4100 System (cont.) pkf0_fast pkf0_host_id pkf0_termpwr 1 7 1 Compare the show pk* command display in Example 10–5 with the show config command in Example 10–1 and the show dev command in Example 10–2. Note that there are no pk* devices in either display.
Example 10–6: Displaying Console Variables for a KZPBA-CB on an AlphaServer 8x00 System P00>>> show isp* isp0_host_id isp0_soft_term 7 on isp1_host_id isp1_soft_term 7 on isp2_host_id isp2_soft_term 7 on isp3_host_id isp3_soft_term 7 on isp5_host_id isp5_soft_term 7 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.
Example 10–7: Displaying Console Variables for a KZPSA-BB on an AlphaServer 8x00 System (cont.) pkc0_fast pkc0_host_id pkc0_termpwr 1 7 on 10.1.4.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBs on the shared SCSI bus, use the set console command to set the SCSI ID. For a TruCluster Server cluster, you will most likely have to set the SCSI ID for all KZPBA-CB UltraSCSI adapters except one.
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. ______________________ Note _______________________ All KZPSA-BB host bus adapters should be enabled to generate termination power.
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. 10.1.4.5 Updating the KZPSA-BB Adapter Firmware You must check, and update as necessary, the system and host bus adapter firmware.
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. Otherwise, enter the name of the file you wish to boot from.
A Worldwide ID-to-Disk Name Conversion Table Table A–1: Converting Storageset Unit Numbers to Disk Names File System or Disk HSG80 Unit WWID UDID Device Name dskn Tru64 UNIX disk Cluster root (/) /usr /var Member 1 boot disk Member 2 boot disk Member 3 boot disk Member 4 boot disk Quorum disk Worldwide ID-to-Disk Name Conversion Table A–1
Index Numbers and Special Characters 20/40 GB DLT Tape Drive, 8–10 cabling, 8–11 capacity, 8–10 cartridges, 8–10 connectors, 8–10 setting SCSI ID, 8–10 40/80-GB DLT Drive, 8–14 cabling, 8–15 capacity, 8–14 cartridges, 8–14 connectors, 8–14 setting SCSI ID, 8–14 A ACS V8.
BN39B-04, 5–7, 5–9 BN39B-10, 2–3, 5–7, 5–9 ESL9326D, 8–77 supported, 2–12 cabling 20/40 GB DLT Tape Drive, 8–11 40/80-GB DLT Drive, 8–15 Compaq 20/40 GB DLT Tape Drive, 8–11 Compaq 40/80-GB DLT Drive, 8–15 DS-TZ89N-TA, 8–9 DS-TZ89N-VW, 8–8 ESL9326D, 8–74, 8–75, 8–77 TL881/891 DLT MiniLibrary, 8–63, 8–67 TL890, 8–30 TL891, 8–25, 8–30 TL892, 8–25, 8–30 TL893, 8–55 TL894, 8–41 TL895, 8–48 TL896, 8–55 TZ885, 8–18 TZ887, 8–21 TZ88N-TA, 8–5 TZ88N-VA, 8–3 changing HSG80 failover modes, 6–59 clu_create, 6–53 clus
configuring base unit as slave, 8–33, 8–70 connections to HSG80, 6–58 connectors supported, 2–14 console serial bus ( See CSB ) console terminal need for, 7–9 terminal emulator, 7–9 terminal server, 7–9 console variable bus_probe_algorithm, 2–9 CSB, 7–4 nodes, 7–5 purpose, 7–4 D data path for buses, 3–5 default SCSI IDs ESL9326D, 8–75 TL881/TL891, 8–62 TL890, 8–36 TL891, 8–36 TL892, 8–36 TL893, 8–51 TL894, 8–37 TL895, 8–44 TL896, 8–51 device name, 6–44 device unit number, 6–44 setting, 6–44 diagnostics M
termpwr, 3–9 transfer rate, 2–12 DS-DWZZH-05, 3–8, 3–10 bus connectors, 3–10 bus isolation, 2–12 configurations, 3–15 description, 2–12 fair arbitration, 3–10 installed in, 3–10, 3–11 internal termination, 3–8, 3–9 radial disconnect, 2–12 SBB, 3–10 SCSI ID, 3–10 termpwr, 3–9 transfer rate, 2–12 DS-TZ89N-TA cabling, 8–9 setting SCSI ID, 8–9 DS-TZ89N-VW cabling, 8–8 setting SCSI ID, 8–6 dual-redundant controllers, 1–13 DWZZA incorrect hardware revision, 2–11 termination, 9–3, 9–16 upgrade, 2–11 DWZZB terminat
FCP, 6–4 Fibre Channel arbitrated loop, 6–8 data rates, 6–4 distance, 6–4 F_Port, 6–6 fabric, 6–5, 6–7 FL_Port, 6–5 frame, 6–5 N_Port, 6–5 NL_Port, 6–5 point-to-point, 6–6 restrictions, 2–5 supported configurations, 6–9 switch installation, 6–16 terminology, 6–5 topology, 6–6, 6–64 Fibre Channel Protocol ( See FCP ) file /var/adm/messages, 6–27 firmware 35/70 DLT tape drives, 8–75 ESL9326D, 8–75 fail-safe loader, 7–18 HSG80, 6–29 KZPBA-CB, 2–9, 4–7, 7–13, 10–5 KZPSA, 10–18 KZPSA-BB, 2–8, 2–9, 10–5t, 10–18
( See KGPSA, KZPBA-CB, KZPSA-BB ) HPM, 7–5 HSG60 controller, 1–13 ACS, 2–5 configuring, 2–8 port configuration, 2–8 transparent failover mode, 2–8 unit configuration, 2–8 HSG80 controller, 1–13 ACS, 2–5 changing failover modes, 6–59 configuring, 2–8, 6–28 multiple-bus failover, 6–30 obtaining the worldwide name of, 6–33 port configuration, 2–8 port_n_topology, 6–30 replacing, 6–34 resetting offsets, 6–59 setting controller values, 6–28, 6–29 transparent failover mode, 2–8 unit configuration, 2–8 HSZ failo
restrictions, 2–9 termination resistors, 4–9t, 10–4t, 10–7t use in cluster, 4–6, 10–2 KZPSA-BB displaying device information, 10–5t, 10–7t installation, 10–3 restrictions, 2–8 setting bus speed, 10–17 setting SCSI ID, 10–17 setting termination power, 10–17 termination resistors, 10–4t, 10–7t updating firmware, 10–18 use in cluster, 10–2 L MA8000 configuring, 2–8 port configuration, 2–8 transparent failover mode, 2–8 unit configuration, 2–8 mc_cable, 5–12 mc_diag, 5–12 member systems improving performanc
multi-unit controller planning the hardware configuration, ( See MUC ) multimode fibre, 6–17 multiple-bus failover, 1–14, 3–18, 3–22, 6–30 4–2 point-to-point, 6–6 port name, 6–33 power system manager ( See PSM ) changing from transparent failover, 6–59 example configurations, 6–12 NSPOF, 3–18 setting, 6–30, 6–59 N N_Port, 6–5 NL_Port, 6–5 node name, 6–33 non-Ultra BA356 storage shelf preparing, 9–15 NSPOF, 1–12, 3–18 O optical cable, 6–17 optical converter cable connection, 5–6 installation, 5–6 P
HSG80 controller, 6–34 requirements SCSI bus, 3–1, 9–1 reset, 6–25, 6–48 resetting offsets, 6–59 restrictions, 2–8 disk devices, 2–9 KZPBA-CB adapters, 2–9 KZPSA adapters, 2–8 Memory Channel interconnects, 2–3 SCSI bus adapters, 2–5 rolling upgrade MC1 to MC2, 5–14 S SAVE_CONFIGURATION command, 6–34 SC connector ( See subscriber connector ) SCM, 7–4 master, 7–5 master-designate, 7–5 powered by, 7–4 purpose, 7–4 slave, 7–5 SCM command power on, 7–12 set hp_count, 7–10 set hp_qbb_mask, 7–10 show nvr, 7–10
MUC, 8–51 TL881/891 DLT MiniLibrary, 8–72 TL891, 8–23 TL892, 8–23 TL893, 8–51 TL894, 8–37 TL896, 8–51 TZ885, 8–17 TZ887, 8–20 TZ88N-TA, 8–5 TZ88N-VA, 8–2 setting SCSI IDs ESL9326D, 8–75 setting the SCSI ID TL881/891 DLT MiniLibrary, 8–62 shared SCSI buses, 4–3 adding devices, 9–6 assigning SCSI IDs, 3–6 cable length restrictions, 3–6 connecting devices, 3–7, 9–6 device addresses, 3–5 differential, 3–4 number of, 2–5, 4–3 requirements, 3–2 single-ended, 3–4 using trilink connectors, 9–6 using Y cables, 9–6 s
system control manager ( See SCM ) system reset, 6–25, 6–48 T table of connections, 6–58 terminal emulator, 7–9 terminal server, 7–9 termination, 9–13 BA356, 9–11 DWZZA, 9–16 DWZZB, 9–16 ESL9326D, 8–77 terminating the shared bus, 3–7, 9–5 UltraSCSI BA356, 9–14 termination resistors KZPBA-CB, 4–9t, 10–4t, 10–7t KZPSA, 10–4t, 10–7t KZPSA-BB, 10–7t terminators supported, 2–14 TL881, 8–57 TL881/891 DLT MiniLibrary cabling, 8–63, 8–67 capacity, 8–57, 8–59 components, 8–58 configuring base unit as slave, 8–70
TZ88N-VA, 8–1 cabling, 8–3 setting SCSI ID, 8–2 TZ89, 8–6 utility hwmgr, 6–51 wwidmgr, 6–48, 6–54, 6–56 V U UltraSCSI BA356 disable termination, 9–17 DS-BA35X-DA personality module, /var/adm/messages, 6–27 variable ( See environment variable ) Very High Density Cable Interconnect ( See VHDCI ) 3–3 fast narrow SCSI drives, 3–3 fast wide SCSI drives, 3–3 jumper, 9–14 personality module address switches, 9–13 power supply, 3–3 preparing, 9–15, 9–17 preparing for shared SCSI usage, 9–17 SCSI ID selectio
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.
Reader’s Comments 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 • Internet electronic mail: readers_comment@zk3.dec.
Do Not Cut or Tear - Fold Here and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES FIRST CLASS MAIL PERMIT NO.
