TruCluster Server Hardware Configuration Part Number: AA-RHGWB-TE April 2000 Product Version: TruCluster Server Version 5.0A Operating System and Version: Tru64 UNIX Version 5.0A This manual describes how to configure the hardware for a TruCluster Server environment. TruCluster Server Version 5.0A runs on the Tru64™ UNIX® operating system.
© 2000 Compaq Computer Corporation COMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Office. TruCluster and Tru64 are trademarks of Compaq Information Technologies Group, L.P. Microsoft and Windows are trademarks of Microsoft Corporation. UNIX and The Open Group are trademarks of The Open Group. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies. Confidential computer software.
Contents About This Manual 1 Introduction 1.1 1.2 1.3 1.4 1.4.1 1.4.1.1 1.4.1.2 1.4.1.3 1.4.1.4 1.5 1.6 1.6.1 1.6.2 1.6.3 1.6.4 1.6.5 1.7 2 The TruCluster Server Product . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Overview of the TruCluster Server Hardware Configuration . . Memory Requirements . . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Minimum Disk Requirements .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
2.6 2.7 2.8 2.9 2.10 RAID Array Controller Restrictions . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . SCSI Signal Converters . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs . . .. . .. . .. . SCSI Cables . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . SCSI Terminators and Trilink Connectors . . .. . .. . .. . . .. . .. . .. . .. .
4.3 4.3.1 TruCluster Server Hardware Installation . . .. . .. . .. . . .. . .. . .. . .. . Installation of a KZPBA-CB Using Internal Termination for a Radial Configuration .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.3.2 Displaying KZPBA-CB Adapters with the show Console Commands . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 4.3.3 Displaying Console Environment Variables and Setting the KZPBA-CB SCSI ID . . .. . .. . .. . .. . . .. . ..
.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.12 Using the emx Manager to Display Fibre Channel Adapter Information . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.12.1 Using the emxmgr Utility to Display Fibre Channel Adapter Information .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.12.2 Using the emxmgr Utility Interactively .. . .. . .. . . .. . .. . .. . .. . 7 6–59 6–61 Preparing ATM Adapters 7.1 7.2 7.3 7.4 8 6–59 ATM Overview . . .. . .. . .. . .. .
.7.2.1 Cabling the DLT MiniLibraries . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.7.2.2 Configuring a Base Module as a Slave .. . .. . . .. . .. . .. . .. . 8.7.2.3 Powering Up the DLT MiniLibrary . .. . .. . .. . . .. . .. . .. . .. . 8.7.2.4 Setting the TL890/TL891/TL892 SCSI ID . . . .. . .. . .. . .. . 8.8 Preparing the TL894 DLT Automated Tape Library for Shared SCSI Bus Usage . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.8.
8.11.2.1.1 Setting the Standalone MiniLibrary Tape Drive SCSI ID . . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11.2.1.2 Cabling the TL881 or TL891 DLT MiniLibrary . .. . 8.11.2.2 Preparing a TL881 or TL891 Rackmount MiniLibrary for Shared SCSI Bus Usage .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11.2.2.1 Cabling the Rackmount TL881 or TL891 DLT MiniLibrary .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 8.11.2.2.
9.4.1 9.4.1.1 9.4.1.2 9.4.1.3 9.4.2 9.4.2.1 9.4.2.2 9.4.2.3 9.4.3 9.4.3.1 9.4.3.2 9.4.4 Preparing BA350, BA356, and UltraSCSI BA356 Storage Shelves for an Externally Terminated TruCluster Server Configuration . . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Preparing a BA350 Storage Shelf for Shared SCSI Usage .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Preparing a BA356 Storage Shelf for Shared SCSI Usage .. .
10.1.4.5 A Updating the KZPSA-BB Adapter Firmware . . .. . .. . .. . 10–18 Worldwide ID to Disk Name Conversion Table Index Examples 4–1 4–2 4–3 4–4 4–5 4–6 4–7 5–1 6–1 6–2 6–3 6–4 10–1 10–2 10–3 10–4 10–5 10–6 10–7 10–8 10–9 Displaying Configuration on an AlphaServer DS20 . .. . .. . .. . .. . Displaying Devices on an AlphaServer DS20 . .. . .. . . .. . .. . .. . .. . Displaying Configuration on an AlphaServer 8200 . . .. . .. . .. . .. . Displaying Devices on an AlphaServer 8200 . . .. . .. . . .. .
1–2 1–3 1–4 1–5 1–6 1–7 1–8 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 4–1 5–1 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 7–1 8–1 8–2 8–3 8–4 8–5 xii Contents Generic Two-Node Cluster with Minimum Disk Configuration and Quorum Disk . . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Minimum Two-Node Cluster with UltraSCSI BA356 Storage Unit . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
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 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 9–15 10–1 Cabling a Shared SCSI Bus with a TZ885 . . .. . .. . .. . . .. . .. . .. . .. . TZ887 DLT MiniLibrary Rear Panel . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Cabling a Shared SCSI Bus with a TZ887 . . .. . .. . .. . . .. . .. . .. . .. . TruCluster Server Cluster with a TL892 on Two Shared SCSI Buses . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . ..
2–4 3–1 3–2 3–3 3–4 4–1 4–2 4–3 5–1 5–2 5–3 6–1 6–2 7–1 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 9–1 9–2 9–3 xiv Contents Supported SCSI Terminators and Trilink Connectors . .. . .. . .. . SCSI Bus Speeds .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . SCSI Bus Segment Length . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . DS-DWZZH UltraSCSI Hub Maximum Configurations . . .. . .. .
9–4 10–1 10–2 10–3 A–1 Hardware Components Used in Configuration Shown in Figure 9–14 . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Configuring TruCluster Server Hardware for Use with a PCI SCSI Adapter .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Installing the KZPSA-BB or KZPBA-CB for Radial Connection to a DWZZH UltraSCSI Hub . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
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 ten chapters and an index.
Chapter 8 Describes how to configure a shared SCSI bus for tape drive, tape loader, or tape library usage. Chapter 9 Contains information about setting up a shared SCSI bus, SCSI bus requirements, and how to connect storage to a shared SCSI bus using external termination or radial connections to non-UltraSCSI devices.
• HSZ70 Array Controller HSOF Version 7.0 Configuration Manual • HSZ80 Array Controller ACS Version 8.2 • Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 Configuration Guide • Compaq StorageWorks HSG80 Array Controller ACS Version 8.
systems. It is available on line in PostScript and Portable Document Format (PDF) formats at: http://www.compaq.com/info/golden-eggs At this URL you will find links to individual system, storage, or cluster configurations. You can order the document through the Compaq Literature Order System (LOS) as order number EC-R026B-36.
UBPG Publications Manager ZKO3-3/Y32 110 Spit Brook Road Nashua, NH 03062-2698 A Reader’s Comment form is located in the back of each printed manual. The form is postage paid if you mail it in the United States. Please include the following information along with your comments: • The full title of the book and the order number. (The order number is printed on the title page of this book and on its back cover.) • The section numbers and page numbers of the information on which you are commenting.
cluster xxii About This Manual 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 Overview of the TruCluster Server Hardware Configuration A TruCluster Server hardware configuration consists of a number of highly specific hardware components: • TruCluster Server currently supports from one to eight member systems.
contains up to eight linecards. The Memory Channel adapter in each system in the cluster is connected to the Memory Channel hub. One or two Memory Channel adapters can be used with TruCluster Server. When dual Memory Channel adapters are installed, if the Memory Channel adapter being used for cluster communication fails, the communication will fail over to the other Memory Channel. 1.3 Memory Requirements Cluster members require a minimum of 128 MB of memory. 1.
The operating system disk (Tru64 UNIX disk) cannot be used as a clusterwide disk, a member boot disk, or as the quorum disk. Because the Tru64 UNIX operating system will be available on the first cluster member, in an emergency, after shutting down the cluster, you have the option of booting the Tru64 UNIX operating system and attempting to fix the problem. See the TruCluster Server Cluster Administration manual for more information. 1.4.1.
A member boot disk cannot contain one of the clusterwide root (/), /usr, and /var file systems. Also, a member boot disk cannot be used as the quorum disk. A member disk can contain more than the three required partitions. You can move the swap partition off the member boot disk. See the TruCluster Server Cluster Administration manual for more information. 1.4.1.4 Quorum Disk The quorum disk allows greater availability for clusters consisting of two members.
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.6.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 Tru64 UNIX Disk Memory Channel Interface Member System 2 Memory Channel Memory Channel Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) Shared SCSI Bus 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. Note that with the use of the cluster file system (See the TruCluster Server Cluster Administration manual for a discussion of the cluster file system), the clusterwide root (/), /usr, and /var file systems could be physically placed on a private bus of either of the member systems.
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.
1.6.3 Two-Node Configurations with UltraSCSI BA356 Storage Units and Dual SCSI Buses By adding a second shared SCSI bus, you now have the capability to use the Logical Storage Manager (LSM) to mirror data disks, and the clusterwide /usr and /var file systems across SCSI buses. ______________________ Note _______________________ You cannot use LSM to mirror the clusterwide root (/), member system boot, swap, or quorum disks, but you can use hardware RAID.
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
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.6.
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 Member System 2 KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA HSG80 HSG80 HSG80 HSG80 RA8000/ ESA12000 RA8000/ ESA12000 ZK-1533U-AI 1.7 Overview of Setting up the TruCluster Server Hardware Configuration To set up a TruCluster Server hardware configuration, follow these steps: 1. Plan your hardware configuration. (See Chapter 3, Chapter 4, Chapter 6, Chapter 9, and Chapter 10). 2.
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). For a Fibre Channel configuration, connect the HSG80 controllers to the switches. You want the HSG80 to recognize the connections to the systems when the systems are powered on. 8. 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. See the TruCluster Server Software Product Description (SPD) for the latest information about supported hardware. 2.
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.
• For AlphaServer 2000 systems, the B2111-AA module must be at Revision H or higher. For AlphaServer 2100 systems, the B2110-AA module must be at Revision L or higher. Use the examine console command to determine if these modules are at a supported revision as follows: P00>>> examine -b econfig:20008 econfig: 20008 04 P00>>> If a hexadecimal value of 04 or greater is returned, the I/O module supports Memory Channel.
Table 2–1: AlphaServer Systems Supported for Fibre Channel AlphaServer Number of KGPSA-BC Adapters Supported AlphaServer 800 2 AlphaServer 1200 4 AlphaServer 4000, 4000A, or 4100 4 Compaq AlphaServer DS10 1 Compaq AlphaServer DS20 and DS20E 2 Compaq AlphaServer ES40 4 AlphaServer 8200 or 8400a 32 (2 per DWLPB for throughput, 4 per DWLPB for connectivity) Compaq AlphaServer GS60, GS60E, and GS140a 32 (2 per DWLPB for throughput, 4 per DWLPB for connectivity) a The KGPSA-BC/CA PCI-to-Fibre C
• The Fibre Channel RAID Array 8000 (RA8000) midrange departmental storage subsystem and Fibre Channel Enterprise Storage Array 12000 (ESA12000) house two HSG80 dual-channel controllers. There are provisions for six UltraSCSI channels. • Only disk devices attached to the HSG80 Fibre Channel to Six Channel UltraSCSI Array controller are supported with the TruCluster Server product. • No tape devices are supported. • Tru64 UNIX Version 5.0A limits the number of Fibre Channel targets to 126.
2.4 SCSI Bus Adapter Restrictions To connect a member system to a shared SCSI bus, you must install a SCSI bus adapter in an I/O bus slot. The Tru64 UNIX operating system supports a maximum of 64 I/O buses. TruCluster Server supports a total of 32 shared I/O buses using KZPSA-BB host bus adapters, KZPBA-CB UltraSCSI host bus adapters, or KGPSA Fibre Channel host bus adapters. The following sections describe the SCSI adapter restrictions in more detail. 2.4.
– AlphaServer 8200, 8400, GS60, GS60E, GS140: 32 The KZPBA-CB is supported on the DWLPB only; it is not supported on the DWLPA module. – AlphaServer DS10: 2 – AlphaServer DS20/DS20E: 4 – AlphaServer ES40: 5 • A maximum of four HSZ50, HSZ70, or HSZ80 RAID array controllers can be placed on a single KZPBA-CB UltraSCSI bus. Only two redundant pairs of array controllers are allowed on one SCSI bus. • The KZPBA-CB requires ISP 1020/1040 firmware Version 5.
Table 2–2: RAID Controller SCSI IDs (cont.) RAID Controller Number of SCSI IDs Supported HSZ80 15 HSG80 N/A 2.7 SCSI Signal Converters If you are using a standalone storage shelf with a single-ended SCSI interface in your cluster configuration, you must connect it to a SCSI signal converter. SCSI signal converters convert wide, differential SCSI to narrow or wide, single-ended SCSI and vice versa.
2.8 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs The DS-DWZZH-03 and DS-DWZZH-05 series UltraSCSI hubs are the only hubs supported in a TruCluster Server configuration. They are SCSI-2and draft SCSI-3-compliant SCSI 16-bit signal converters capable of data transfer rates of up to 40 MB/sec. These hubs can be listed with the other SCSI bus signal converters, but as they are used differently in cluster configurations they will be discussed differently in this manual.
In addition, each supported cable comes in various lengths. Use the shortest possible cables to adhere to the limits on SCSI bus length. Table 2–3 describes each supported cable and the context in which you would use the cable. Note that there are cables with the Compaq 6-3 part number that are not listed, but are equivalent to the cables listed.
2.10 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.
termination and covers radial configurations with the DWZZH UltraSCSI hubs and non-UltraSCSI RAID array controllers. This chapter discusses the following topics: • Shared SCSI bus configuration requirements (Section 3.1) • SCSI bus performance (Section 3.2) • SCSI bus device identification numbers (Section 3.3) • 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.
• All supported UltraSCSI host adapters support UltraSCSI disks at UltraSCSI speeds in UltraSCSI BA356 shelves, RA7000 or ESA10000 storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storage arrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves are supported with UltraSCSI host adapters and host RAID controllers as long as they contain no UltraSCSI disks. • UltraSCSI drives and fast wide drives can be mixed together in an UltraSCSI BA356 shelf (see Chapter 9).
3.2.1 SCSI Bus Versus SCSI Bus Segments An UltraSCSI bus may be comprised of multiple UltraSCSI bus segments. Each UltraSCSI bus segment is comprised of electrical conductors that may be in a cable or a backplane, and cable or backplane connectors. Each UltraSCSI bus segment must have a terminator at each end of the bus segment. 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.
connect devices that use different transmission methods, use a SCSI signal converter between the devices. The DS-BA35X-DA personality module is discussed in Section 9.1.2.2. See Section 9.1 for information about using the DWZZ* series of SCSI signal converters. You cannot use a DWZZA or DWZZB signal converter at UltraSCSI speeds for TruCluster Server if there are any UltraSCSI disks on the bus, because the DWZZA or DWZZB will not operate correctly at UltraSCSI speed.
SCSI bus adapters have a default SCSI ID that you can change by using console commands or utilities. For example, a KZPSA adapter has an initial SCSI ID of 7. ______________________ Note _______________________ If you are using a DS-DWZZH-05 UltraSCSI hub with fair arbitration enabled, SCSI ID numbering will change (see Section 3.6.1.2).
Table 3–2: SCSI Bus Segment Length SCSI Bus Bus Speed Maximum Cable Length Narrow, single-ended 5 MB/sec 6 meters Narrow, single-ended fast 10 MB/sec 3 meters Wide differential, fast 20 MB/sec 25 meters Differential UltraSCSI 40 MB/sec 25 metersa a The maximum separation between a host and the storage in a TruCluster Server configuration is 50 meters: 25 meters between any host and the UltraSCSI hub and 25 meters between the UltraSCSI hub and the RAID array controller.
Most devices have internal termination. For example, the UltraSCSI KZPBA-CB and the fast and wide KZPSA-BB host bus adapters have internal termination. When using a KZPBA-CB or KZPSA-BB with an UltraSCSI hub, ensure that the onboard termination resistor SIPs have not been removed. You will need to provide termination at the storage end of one SCSI bus segment. You will install an H8863-AA trilink connector on the HSZ70 or HSZ80 at the bus end.
3.6.1 Using a DWZZH UltraSCSI Hub in a Cluster Configuration The DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI hubs are supported in a TruCluster Server cluster. They both provide radial connection of cluster member systems and storage, and are similar in the following ways: • Contain internal termination for each port; therefore, the hub end of each SCSI bus segment is terminated.
• DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI hubs may be housed in the same storage shelf with disk drives. Table 3–3 provides the supported configurations. Figure 3–2 shows a front view of the DS-DWZZH-03 UltraSCSI hub. Figure 3–2: DS-DWZZH-03 Front View Differential symbol ZK-1412U-AI The differential symbol (and the lack of a single-ended symbol) indicates that all three connectors are differential. 3.6.1.2 DS-DWZZH-05 Description The DS-DWZZH-05: • Is a 5.
_____________________ Note _____________________ Dual power supplies are recommended for any BA356 shelf containing a DS-DWZZH-05 UltraSCSI hub in order to provide a higher level of availability between cluster member systems and storage. • The lower righthand device slot of the BA370 shelf within the RA7000 or ESA 10000 RAID array subsystems. This position minimizes cable lengths and interference with disks.
Table 3–3: DS-DWZZH UltraSCSI Hub Maximum Configurations (cont.) DS-DWZZH-03 DS-DWZZH-05 Disk Drivesa Personality Moduleb c 1 1 2 Installed 0 1 3 Installed a DS-DWZZH UltraSCSI hubs and disk drives may coexist in a storage shelf. Installed disk drives are not associated with the DS-DWZZH UltraSCSI hub SCSI bus segments; they are on the SCSI bus connected to the personality module. b If the personality module is installed, you can install a maximum of four DS-DWZZH-03 UltraSCSI hubs.
______________________ Note _______________________ Host port SCSI ID assignments are not linked to the physical port when fair arbitration is disabled. The DS-DWZZH-05 reserves SCSI ID 7 regardless of whether fair arbitration is enabled or not. 3.6.1.2.3 DS-DWZZH-05 Address Configurations The DS-DWZZH-05 has two addressing modes: wide addressing mode and narrow addressing mode. With either addressing mode, if fair arbitration is enabled, each hub port is assigned a specific SCSI ID.
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: Shared SCSI Bus with HSZ70 Configured for Transparent Failover Network Member System 1 Member System 2 Memory Channel Interface Memory Channel KZPBA-CB (ID 6) Memory Channel T T KZPBA-CB (ID 7) 1 1 T DS-DWZZH-03 T T 2 3 2 3 4 T Controller A Controller B HSZ70 HSZ70 StorageWorks RAID Array 7000 ZK-1599U-AI Table 3–4 shows the components used to create the clusters shown in Figure 3–5, Figure 3–6, Figure 3–7, and Figure 3–8.
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.
• 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: TruCluster Server Configuration with HSZ70 in Multiple-Bus Failover Mode Network Member System 1 Member System 2 Memory Channel Interface Memory Channel KZPBA-CB (ID 6) T Memory Channel T T KZPBA-CB (ID 7) 1 1 1 1 T T DS-DWZZH-03 T DS-DWZZH-03 T T T 2 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 3 3 T 4 4 2 T Controller A Controller B HSZ70 HSZ70 StorageWorks RAID Array 7000 ZK-1601U-AI Table 3–4 shows the components used to create the cluster shown in Figure 3–7.
Figure 3–8: TruCluster Server Configuration with HSZ80 in Multiple-Bus Failover Mode Networks Memory Channel Interfaces Member System 1 Member System 2 Memory Channel (mca1) Memory Channel (mca1) Memory Channel (mca0) Memory Channel (mca0) KZPBA-CB (ID 6) T T KZPBA-CB (ID 7) KZPBA-CB (ID 6) T 1 1 T KZPBA-CB (ID 7) 1 1 T T DS-DWZZH-03 T DS-DWZZH-03 T T T 2 3 Port 1 4 4 T T Port 2 Controller A HSZ80 2 3 Port 1 Port 2 Controller B HSZ80 StorageWorks RAID Array 8000 ZK-1602
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 wish to complete all hardware installation before powering up the systems to run Memory Channel diagnostics. 5.1 Setting the Memory Channel Adapter Jumpers The meaning of the Memory Channel adapter module jumpers depends upon the version of the Memory Channel module. 5.1.1 MC1 and MC1.5 Jumpers The MC1 and MC1.
If you are upgrading from virtual hub mode to standard hub mode (or from standard hub mode to virtual hub mode), be sure to change the jumpers on all Memory Channel adapters on the rail. 5.1.2 MC2 Jumpers The MC2 module (CCMAB) has multiple jumpers. They are numbered right to left, starting with J1 in the upper righthand corner (as you view the jumper side of the module with the endplate in your left hand). The leftmost jumpers are J11 and J10. J11 is above J10.
Table 5–2: MC2 Jumper Configuration (cont.
Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: 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. The MC2 linecard (CCMLB) has two jumpers, J2 and J3, that are used to enable fiber optics mode.
If you are setting up a redundant Memory Channel configuration, install the second Memory Channel adapter right after installing the first Memory Channel adapter. Ensure that the jumpers are correct and are the same on both modules. After you install the Memory Channel adapter(s), replace the system panels unless you have more hardware to install. 5.
For use with the MC2 CCMAB adapter, the hub must be placed within 4 or 10 meters (the length of the BN39B link cables) of each system. If fiber optics is used in conjunction with the MC2 adapter, the hub may be placed up to 31 meters from the systems. • Ensure that the voltage selection switch on the back of the hub is set to select the correct voltage for your location (115V or 230V).
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. Gently push the cable’s connector into the receptacle, and then use the screws to pull the connector in tight.
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. If optical converters are used, use the BN39B-01 1-meter link cable and the BN34R-10 (10-meter) or BN34R-31 (31-meter) fiber optics cable. 5.5.2.
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.
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.0A configuration.
• A discussion on how you can use the emx manager (emxmgr) to display the presence of Fibre Channel adapters, target ID mappings for a Fibre Channel adapter, and the current Fibre Channel topology (Section 6.12). 6.1 Procedure for Installation Using Fibre Channel Disks Use the following procedure to install Tru64 UNIX Version 5.0A or TruCluster Server Version 5.0A using Fibre Channel disks. If you are only installing Tru64 UNIX Version 5.0A, complete the first eight steps.
10. Use the disklabel utility to label the disks used to create the cluster (Section 6.10). 11. Refer to the TruCluster Server Software Installation manual and install the TruCluster Server software subsets and run the clu_create command to create the first cluster member. Do not allow clu_create to boot the system. Shut down the system to the console prompt (Section 6.10). 12. Reset the bootdef_dev console environment variable to provide multiple boot paths (Section 6.8). Boot the first cluster member. 13.
• Wwidmgr User’s Manual 6.2 Fibre Channel Overview Fibre Channel supports multiple protocols over the same physical interface. Fibre Channel is primarily a protocol-independent transport medium; therefore, it is independent of the function that it is used for. The TruCluster Server uses the Fibre Channel Protocol (FCP) for SCSI to use Fibre Channel as the physical interface.
is manufactured. An N_Port is connected directly to another N_Port in a point-to-point topology. An N_Port is connected to an F_Port in a fabric topology. NL_Port In an arbitrated loop topology, information is routed around a loop. The information is repeated by each intermediate port until it reaches its destination. The N_Port that contains this additional loop functionality is an NL_Port.
• Arbitrated loop (Section 6.2.2.3) ______________________ Note _______________________ Although it is possible to interconnect an arbitrated loop with fabric, hybrid configurations are not supported at the present time, and therefore not discussed in this manual. 6.2.2.1 Point-to-Point The point-to-point topology is the simplest Fibre Channel topology. In a point-to-point topology, one N_Port is connected to another N_Port by a single link.
connected by the fabric switching function, which routes the frame from one F_Port to another F_Port within the switch. Communication between two switches is routed between two expansion ports (E_Ports). When an N_Port is connected to an F_Port, the fabric is responsible for the assignment of the Fibre Channel address to the N_Port attached to the fabric. The fabric is also responsible for selecting the route a frame will take, within the fabric, to be delivered to the destination.
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 or TruCluster Server products.
• 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. • If one controller fails, the other controller takes control and both its ports are active. Figure 6–4 shows a typical Fibre Channel cluster configuration using transparent failover mode.
You can, however, add the hardware for a second bus (another KGPSA, switch, and RA8000/ESA12000 with associated cabling) and use LSM to mirror across the buses. However, because you cannot use LSM to mirror the cluster root (/) file system, member boot partitions, the quorum disk, or swap partitions you cannot obtain an NSPOF transparent failover configuration, even though you have increased availability. 6.3.
If you consider the loss of a host bus adapter or switch, the configurations in Figure 6–6 and Figure 6–7 will provide better throughput than Figure 6–5 because you still have access to both controllers. With Figure 6–5, if you lose a host bus adapter or switch, you lose the use of a controller.
Figure 6–6: Multiple-Bus NSPOF Configuration Number 2 Member System 1 Member System 2 KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA HSG80 HSG80 HSG80 12 12 A B RA8000/ ESA12000 ZK-1707U-AI 6–12 Using Fibre Channel Storage
Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 Member System 1 Member System 2 KGPSA KGPSA KGPSA KGPSA DSGGA DSGGA HSG80 HSG80 HSG80 12 12 A B RA8000/ ESA12000 ZK-1708U-AI 6.4 Zoning and Cascaded Switches This section provides a brief overview of zoning and cascaded switches. 6.4.1 Zoning A zone is a logical subset of the Fibre Channel devices connected to the fabric. Zoning allows partitioning of resources for management and access control.
Figure 6–8: A Simple Zoned Configuration Cluster 1 Member System 1 KGPSA Cluster 2 Member System 1 KGPSA Cluster 1 Member System 2 KGPSA 1 2 3 4 5 6 7 Cluster 2 Member System 2 KGPSA 8 DSGGA SWITCH 9 10 11 12 13 14 15 16 HSG80 HSG80 HSG80 HSG80 RA8000/ ESA12000 RA8000/ ESA12000 ZK-1709U-AI ______________________ Note _______________________ Only static zoning is supported; zones can only be changed when all connected systems are shut down.
6.5 Installing and Configuring Fibre Channel Hardware This section provides information about installing the Fibre Channel hardware needed for a TruCluster Server configuration accessing storage over the Fibre Channel. Ensure that the member systems, the Fibre Channel switches, and the HSG80 array controllers are placed within the lengths of the optical cables you will be using.
you can manage the switch by way of a telnet session, SNMP, or the Web. The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) or eight (DS-DSGGA-AB) plug-in interface modules. Each interface module in turn supports two Giga Bit Interface Converter modules (GBIC). The GBIC module is the electrical-to-optical converter. The shortwave GBIC supports 50-micron multimode fibre (MMF) using the standard subscriber connector (SC) connector.
5. Turn on the power. The switch runs a series of power-on self test (POST) tests. 6. 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). The switch IP address and subnet mask must initially be set from the front panel, except for the DS-DSGGB-AA 8-port Fibre Channel switch. In this case you have to connect a PC or terminal to the switch. You must use a telnet session to set the switch name. 7.
Down — Downward triangle: Scrolls the menu down (which effectively moves up the list of commands) or decreases the value being displayed. ______________________ Note _______________________ When the up or down buttons are used to increase or decrease a numerical display, the number changes slowly at first, but changes to fast mode if the button is held down. The maximum number displayed is 255. An additional increment at a count of 255 resets the count to 0.
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. Modify the address fields until you have the address set correctly. 3.
6.5.1.2.3 Setting the DS-DSGGB-AA Ethernet IP Address and Subnet Mask from a PC or Terminal For the DS-DSGGB-AA switch, which does not have a front panel, you must use a connection to a Windows 95/98/NT PC or video terminal to set the Ethernet IP address and subnet mask. To set the Ethernet IP address and subnet mask for the DS-DSGGB-AA switch, follow these steps: 1. Connect the switch serial port to a terminal or PC COM port with a standard serial cable with a DB9 connector.
Table 6–1: Telnet Session Default User Names for Fibre Channel Switches DSGGA DSGGB Description other n/a Allows you to execute commands ending in Show, such as dateShow and portShow. user user Allows you to execute all commands ending in Show, plus any commands from the help menu that do not change the state of the switch, for example, version and errDump. You can change the passwords for all users up to and including the current user’s security level.
# telnet 132.25.47.146 Return User admin Return Passwd Return :Admin> switchName fcsw1 Return :Admin> switchName Return fcsw1 :Admin> ______________________ Note _______________________ When you telnet to the switch the next time, the prompt will include the switch name, for example: fcsw1:Admin> 6.5.2 Installing and Configuring the KGPSA PCI-to-Fibre Channel Adapter Module The following sections discuss KGPSA installation and configuration. 6.5.2.
GLM alignment pins, alignment tabs, and connector pins with the holes, oval openings, and board socket. Press the GLM into place. The KGPSA-CA does not use a GLM, it uses an embedded optical shortwave multimode Fibre Channel interface. 3. Install the KGPSA in an open 32- or 64-bit PCI slot. 4. Insert the optical cable SC connectors into the KGPSA-BC GLM or KGPSA-CA SC connectors. The SC connectors are keyed to prevent their being plugged in incorrectly. Do not use unnecessary force.
P00>>> boot warning -- main memory zone is not free P00>>> init . . . P00>>> boot If you have initialized and booted the system, then shut down the system and try to use the wwidmgr utility, you may be prevented from doing so. If you receive the following error, initialize the system and retry the wwidmgr command: P00>>> wwidmgr -show adapter wwidmgr available only prior to booting. Reinit system and try again. P00>>> init . . . P00>>> wwidmgr -show adapter . . .
If, however, the current topology is LOOP, you have to change the topology to FABRIC to operate in a fabric. You will never see the Nvram read failed message if the current topology is LOOP. The NVRAM has to have been formatted to change the current mode to LOOP. Consider the case where the KGPSA current topology is LOOP as follows: P00>>> wwidmgr -show adapter item adapter WWN [ 0] pga0.0.0.3.1 1000-0000-c920-eda0 [ 1] pgb0.0.0.4.0 1000-0000-c920-da01 [9999] All of the above. Cur.
P00>>> show dev . . . pga0.0.0.1.0 pgb0.0.0.2.0 • PGA0 PGB0 WWN 1000-0000-c920-eda0 WWN 1000-0000-c920-da01 You can use the wwidmgr -show adapter command as follows: P00>>> wwidmgr -show adapter item adapter WWN [ 0] pga0.0.0.4.1 1000-0000-c920-eda0 [ 1] pgb0.0.0.3.0 1000-0000-c920-da01 [9999] All of the above. • Cur.
____________________ Note _____________________ Do not use PVA ID 1: With Port-Target-LUN (PTL) addressing, the PVA ID is used to determine the target ID of the devices on ports 1 through 6 (the LUN is always zero). Valid target ID numbers are 0 through 15, excluding numbers 4 through 7. Target IDs 6 and 7 are reserved for the controller pair, and target IDs 4 and 5 are never used.
____________________ Note _____________________ Setting the controller variable CACHE_UPS for one controller sets it for both controllers. 10. From the maintenance terminal, use the show this and show other commands to verify that controllers have the current firmware version. See the Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLI Reference Guide for information on upgrading the firmware. 11.
5 Takes the ports off line and resets the topology to prevent an error message when setting the port topology. 6 Sets fabric as the switch topology. 12. Enter the show connection command as shown in Example 6–1 to determine the HSG80 connection names for the connections to the KGPSA host bus adapters.
Example 6–1: Determine HSG80 Connection Names (cont.
your cluster member systems. If the operating system and offsets are incorrect, set them, then restart both controllers as follows: HSG80> HSG80> HSG80> HSG80> set !NEWCON49 unit_offset = 0 set !NEWCON49 operating_system = TRU64_UNIX restart other restart this . . . 1 2 3 3 4 HSG80> show connection 1 Set the relative offset for LUN numbering to 0. You can set the unit_offset to nonzero values, but use caution. Make sure you understand the impact.
• In a subsystem with two controllers in transparent failover mode, the controller port IDs increment as follows: – Controller A and controller B, port 1 — worldwide name + 1 – Controller A and controller B, port 2 — worldwide name + 2 For example, using the worldwide name of 5000-1FE1-0000-0D60, the following port IDs are automatically assigned and shared between the ports as a REPORTED PORT_ID on each port: • – Controller A and controller B, port 1 — 5000-1FE1-0000-0D61 – Controller A and contro
– If the configuration has been saved to disk (with the INITIALIZE DISKnnnn SAVE_CONFIGURATION or INITIALIZE storageset-name SAVE_CONFIGURATION option), you can restore it from disk with the CONFIGURATION RESTORE command. – If you have not saved the configuration to disk, but the label containing the worldwide name and checksum is still intact, or you have recorded the worldwide name and checksum (Section 6.5.3.
• Cluster /var • Member boot disk (one for each cluster member system) • Quorum disk (if used) If you are installing only the operating system, you need only the Tru64 UNIX disk (and of course any disks for applications). This document assumes that both the base operating system and cluster software are to be installed on Fibre Channel disks. If you are installing a cluster, you need one or more disks to hold the Tru64 UNIX operating system.
Example 6–2: Setting up the Mirrorset (cont.
Example 6–2: Setting up the Mirrorset (cont.
Example 6–2: Setting up the Mirrorset (cont.) HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON53,!NEWCON54,!NEWCON55,!NEWCON56 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit.
1 Use the CONFIG utility to configure the devices on the device side buses and add them to the controller configuration. The CONFIG utility takes about two minutes to complete. You can use the ADD DISK command to add disk drives to the configuration manually. 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.
14 Partition for cluster /usr filesystem. 15 Partition for cluster /var filesystem. 16 Assign a unit number to each partition. When the unit is created by the ADD UNIT command, disable access to all hosts. This allows selective access in case there are other systems or clusters connected to the same switch as our cluster. Record the unit name of each partition with the intended use for that partition (see Table 6–2). 17 Set the identifier for each storage unit. Use any number between 1 and 9999.
that at this point, even though the table is filled in, we do not yet know the device names or dskn numbers. Table 6–2: Converting Storageset Unit Numbers to Disk Names File System or Disk HSG80 Unit Worldwide Name User Define Identifier (UDID) Device Name dskn Member 1 boot D131 disk 6000-1FE1-0000-0D60- 131 0009-8080-0434-002F dga131.1001.0.1.0 dsk17 Member2 boot disk D132 6000-1FE1-0000-0D60- 132 0009-8080-0434-0030 dga132.1001.0.1.
disk is unit D133 with a UDID 133. The UDID for the cluster member 1 boot disk is 131, and the cluster member 2 boot disk is 132. 2. Use the wwidmgr -clear all command to clear the stored Fibre Channel wwid1, wwid2, wwid3, wwid4, N1, N2, N3, and N4 console environment variables. You want to start with all wwid and N variables clear.
[16] [17] [18] [19] [20] 1 UDID:144 WWID:01000010:6000-1fe1-0000-0d60-0009-8080-0434-0028 (ev:none) UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002b (ev:none) UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002c (ev:none) UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002d (ev:none) UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002e (ev:none) 2 3 4 1 The number within the brackets ([ ]) is the item number of the device shown on any particular line.
132 (cluster member 2). The device unit number is an alias for the worldwide name for the storage unit. • The reachability part of the display provides the followng: – The worldwide name for the storage unit that is to be accessed – The new device name for the KGPSA – Whether access is available through a port – The HSG80 port (N_Port) that will be used to access the storage unit – The connected column indicates the HSG80 controller ports that will be used to access the storage units.
Example 6–3: Using the wwidmgr quickset Command to Set Device Unit Number (cont.) dgb131.1004.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d61 Yes P00>>> wwidmgr -quickset -udid 132 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.
The disks are not reachable and you cannot boot until after the system is initialized. Note, that in the reachability portion of the display, the storagesets are reachable from KGPSA dga through two HSG80 ports and from KGPSA dgb through two HSG80 ports. Also note, that the device unit numbers, the alias for the worldwide name of the disk device, has been set for the KGPSA for each HSG80 port. The device names have also been set for the cluster member boot disks. Record the device names.
Example 6–4: Sample Fibre Channel Device Names (cont.) dgb132.1001.0.2.0 dgb132.1002.0.2.0 dgb132.1003.0.2.0 dgb132.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.1 $1$DGA132 $1$DGA132 $1$DGA132 $1$DGA132 $1$DGA133 $1$DGA133 $1$DGA133 $1$DGA133 DKA0 DQA0 DVA0 EWA0 PGA0 PGB0 PKA0 ______________________ HSG80 V8.5F HSG80 V8.5F HSG80 V8.5F HSG80 V8.5F HSG80 V8.5F HSG80 V8.
• After a cluster member has been added to the cluster with clu_add_member (but before the member system is booted). _____________________ Note _____________________ You do not use this procedure after using clu_create to create the first cluster member. Before booting the first cluster member, you reset the bootdef_dev console environment variable to multiple boot paths. To set the bootdef_dev console environment variable when booting from a Fibre Channel device, follow these steps: 1.
2. Set the bootdef_dev console environment variable to one of the boot path(s) that show up as connected. Ensure that you set the bootdef_dev variable appropriately for the system and boot disk. For the example disk configuration, set bootdef_dev as follows: • On the system where you are installing the Tru64 UNIX operating system (which will also be the first cluster member): P00>>> set bootdef_dev dga133.1002.0.1.
1) 2) 3) 4) Device Name dsk0 dsk15 dsk16 dsk17 Size in GB 4.0 1.0 1.0 2.0 Controller Type SCSI SCSI SCSI SCSI Disk Model RZ2CA-LA HSG80 HSG80 HSG80 Location bus-0-targ-0-lun-0 IDENTIFIER=133 IDENTIFIER=132 IDENTIFIER=131 If you flash the light on a storage unit (logical disk) that is a mirrorset, stripeset, or RAIDset, the lights on all disks in the storageset will blink. Record the /dev/disk/dskn value (dsk15) for the Tru64 UNIX disk that matches the UDID (133) (Table 6–2).
For example, to ensure that you have a connected boot path in case of a failed host bus adapter or controller failover, choose device names for multiple host bus adapters and each controller port. For example, if you use the reachability display shown in Example 6–3, you could choose the following device names when setting the bootdef_dev console environment variable: dga133.1001.0.1.0 dga133.1004.0.1.0 dgb133.1002.0.2.0 dgb133.1003.0.2.
• For member system 2 boot disk: P00>>> set bootdef_dev \ dga132.1001.0.1.0,dga132.1002.0.2.0,\ dgb132.1001.0.1.0,dgb132.1002.0.2.0 POO>>> init . . . ______________________ Note _______________________ The console system reference manual (SRM) software guarantees that you can set the bootdef_dev console environment variable to a minimum of four device names. You may be able to set it to five, but four is all that is guaranteed. 6.
# hwmgr -get attribute -a name -a dev_base_name | more Use the more search utility (/) to search for the worldwide name of the storageset you have set up for the particular disk in question. The following example shows the format of the command output: # hwmgr -get attribute -a name -a dev_base_name 1: name = Compaq AlphaServer ES40 2: name = CPU0 . . .
6.10 Installing the TruCluster Server Software This section covers the Fibre Channel specific procedures you need to execute before running clu_create to create the first cluster member or clu_add_member to add subsequent cluster members. It also covers the procedure you need to execute after running clu_create or clu_add_member before you boot the new cluster member into the cluster.
P00>>> wwidmgr -quickset -udid 132 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d60-0009-8080-0434-0030 via adapter: via fc nport: connected: dga132.1001.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d64 No dga132.1002.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d62 Yes dga132.1003.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d63 No dga132.1004.0.1.0 pga0.0.0.1.0 5000-1fe1-0000-0d61 Yes dgb132.1001.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d64 No dgb132.1002.0.2.0 pgb0.0.0.2.0 5000-1fe1-0000-0d62 Yes dgb132.1003.
Each path between a Fibre Channel host bus adapter in a host computer and an active host port on an HSG80 controller is a connection. During Fibre Channel initialization, when a controller becomes aware of a connection to a host bus adapter through a switch, it adds the connection to its table of known connections. The unit offset for the connection depends on the failover mode in effect at the time the connection is discovered.
2. At the HSG80, set multiple-bus failover as follows. Note that before putting the controllers in multiple-bus failover mode, you must remove any previous failover mode: HSG80> SET NOFAILOVER HSG80> SET MULTIBUS_FAILOVER COPY=THIS ____________________ Note _____________________ Use the controller known to have the good configuration information. 3.
!NEWCON62 TRU64_UNIX OTHER HOST_ID=1000-0000-C921-086C 1 210513 OL other 0 ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER HOST_ID=1000-0000-C921-0943 1 offline 0 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER HOST_ID=1000-0000-C920-EDA0 1 210413 OL other 0 ADAPTER_ID=1000-0000-C920-EDA0 !NEWCON65 TRU64_UNIX OTHER HOST_ID=1000-0000-C921-086C 2 210513 OL other 100 ADAPTER_ID=1000-0000-C921-086C . . .
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). The Nn value is the HSG80 port being used to access the storage units (controller B, port 2). c. Clear the wwidn and Nn environment variables: P00>>> wwidmgr -clear all d. Initialize the console: P00>>> init e.
of the wwidmgr -quickset command for the appropriate device (see Section 6.8). i. Repeat steps a through h on each system accessing devices on the HSG80. 6.12 Using the emx Manager to Display Fibre Channel Adapter Information The emx manager (emxmgr) utility was written for the TruCluster Software Product Version 1.6 products to be used to modify and maintain emx driver worldwide name to target ID mappings. It is included with Tru64 UNIX Version 5.
The previous example shows four Fibre Channel devices on this SCSI bus. The Fibre Channel adapter in question, emx0, at SCSI ID 7, is denoted by the presence of the emx0 designation. Use the emxmgr -t command to display the Fibre Channel topology for the adapter. For example: # emxmgr -t emx1 1 emx1 state information: Link : connection is UP Point to Point Fabric attached FC DID 0x210413 Link is SCSI bus 3 (e.g.
worldwide name) are provided. The Fibre Channel DID number is the physical Fibre Channel address being used by the N_Port.
• Display the target ID mappings for a Fibre Channel adapter • Display the current Fibre Channel topology for a Fibre Channel adapter You have already seen how you can perform these functions from the command line. The same output is available using the interactive mode by selecting the appropriate option (shown in the following example). When you start the emxmgr utility with no command-line options, the default device used is the first Fibre Channel adapter it finds.
2. 3. View adapter’s Target Id Mappings Change Target ID Mappings d. a. x.
7 Preparing ATM Adapters The Compaq Tru64 UNIX operating system supports Asynchronous Transfer Mode (ATM). TruCluster Server supports the use of LAN emulation over ATM for client access. This chapter provides an ATM overview, an example TruCluster Server cluster using ATM, an ATM adapter installation procedure, and information about verifying proper installation of fiber optic cables. See the Tru64 UNIX Asynchronous Transfer Mode manual for information on configuring the ATM software. 7.
Most data traffic in existing customer networks is sent over Local Area Networks (LANs) such as Ethernet or Token Ring networks.
– Broadcast and Unknown Server (BUS): A BUS handles broadcast data sent by a LAN emulation client, all multicast data, and data sent by a LAN emulation client before the ATM address has been resolved. Figure 7–1 shows an ATM network with two emulated LANs. Hosts A and B are LECs on ELAN1. Hosts C, D, and E are LECs on ELAN2. The LECS, the LES, and the BUS are server functions resident on the ATM switch (even though they are shown separately).
Use the following steps to install an ATMworks adapter. See the ATMworks 350 Adapter Installation and Service guide for more information. Be sure to use the antistatic ground strap. 1. Remove the adapter extender bracket if the ATMworks 350 is to be installed in an AlphaServer 2100 system. 2. Remove the option slot cover from the appropriate PCI or TURBOchannel slot. 3. Install the adapter module. 4.
# /usr/sbin/setld -i | grep ATM • OSFATMBASE: ATM Commands • OSFATMBIN: ATM Kernel Modules Additionally, after the ATM subsets have been installed, verify that a new kernel has been built with the following kernel options selected (/sbin/sysconfig -q atm): 3. • Asynchronous Transfer Mode (ATM) • ATM UNI 3.0/3.
5. If you do not have an indication that confirms a correct cable connection, swap the transmit and receive connectors on one end of the cable and recheck the indicators. 6. If you still do not have a correct cable connection, you probably have a bad cable. 7.4 ATMworks Adapter LEDs The ATMworks adapter has two LEDS that indicate the status of the adapter and its connections to the network, the Network LED, and the Module LED. The Network LED is labeled with a number sign (#) under the LED.
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.6 and Section 8.7 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: Shared SCSI Buses with SBB Tape Drives KZPSA adapter, trilink connector, and H879 terminator BN21K or BN21L cables BN21K or BN21L cable DWZZA-VA and trilink T T T DWZZA-VA, trilink, and H879 terminator 1 TZ88N-VA 2 4 5 Memory Channel adapters Memory Channel link cable AlphaServer 2100A BA350 AlphaServer 2100A BA350 DWZZB-VW, trilink connector, and H879 terminator DWZZB-VW and trilink T 1 TZ89N-VW 3 4 5 BA356 BA356 ZK-1334U-AI 8.1.
Ensure that DWZZA jumper J2 or DWZZB jumpers W1 and W2 are installed to enable the single-ended termination. Remove the termination from the differential end by removing the five 14-pin SIP resistors. 2. Attach a trilink connector to the differential end of the DWZZA or DWZZB. 3. Connect the single-ended end of a DWZZA to the TZ88N-TA with a BC19J cable. Connect the single-ended end of a DWZZB to the TZ88N-TA with a BN21M cable. 4.
3, the SCSI ID is 2. If it is installed in slots 3, 4, and 5, the SCSI ID is 4. Figure 8–3 shows a view of the DS-TZ89N-VW showing the backplane interface connector and SCSI ID switch pack. Figure 8–3: DS-TZ89N-VW SCSI ID Switches Backplane Interface Connector 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–2 shows the switch settings for the DS-TZ89N-VW.
Table 8–2: 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 NOTE: This drawing is not to scale.
Table 8–3: Hardware Components Used to Create the Configuration Shown in Figure 8 — 5 (cont.) Callout Number Description 9 199629-002 or 189636-002 (1.8-meter cable) 10 341102-001 terminator a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum length of the BN37A cable must not exceed 25 meters. c The maximum combined length of these cables must not exceed 25 meters. 8.
for use on a shared SCSI bus. The TZ885 in this figure has had the SCSI ID set to 0 (zero). To configure the shared SCSI bus for use with a TZ885, follow these steps: 1. You will need one DWZZA-AA or DWZZB-AA for each TZ885 tape drive. Ensure that the DWZZA jumper J2 or DWZZB jumpers W1 and W2 are installed to enable the single-ended termination. Remove the termination from the differential end by removing the five 14-pin SIP resistors. 2.
Figure 8–6: Cabling a Shared SCSI Bus with a TZ885 KZPSA adapter, trilink connector, and H879 terminator BN21K or BN21L cables DWZZA-VA, trilink connector, and H879 terminator DWZZA-VA and trilink connector T T T Memory Channel link cable AlphaServer 2100A 1 1 2 3 2 3 4 5 4 5 Memory Channel adapters AlphaServer 2100A BN21K or BN21L cable BA350 BA350 BC19J T T DWZZA-AA TZ885 H8574-A terminator Trilink connector and H879-AA terminator ZK-1344U-AI 8.
Figure 8–7: TZ887 DLT MiniLibrary Rear Panel SCSI ID Selector Switch SCSI ID + + 0 0 - - TZ887 ZK-1461U-AI 8.5.2 Cabling the TZ887 Tape Drive The TZ887 is connected to a single-ended segment of the shared SCSI bus. It is connected to a differential portion of the shared SCSI bus with a DWZZB-AA. Figure 8–8 shows a configuration with a TZ887 for use on a shared SCSI bus. The TZ887 in this figure would have the SCSI ID set to 0.
The single-ended SCSI bus may be daisy chained from one single-ended tape drive to another with BC19J cables, as long as the SCSI bus maximum length is not exceeded and there are sufficient SCSI IDs available. Ensure that the tape drive on the end of the bus is terminated with an H8574-A or H8890-AA terminator. You can add additional shared SCSI buses with TZ887 tape drives by adding additional DWZZB-AA/TZ887 combinations.
8.6 Preparing the TL891 and TL892 DLT MiniLibraries for Shared SCSI Usage ______________________ Note _______________________ To achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus, and also recommend that no shared storage be placed on the same SCSI bus with a tape library. 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–9: TruCluster Server Cluster with a TL892 on Two Shared SCSI Buses KZPSA adapter, trilink connector, and H879 terminator BN21K or BN21L cables DWZZA-VA, trilink connector, and H879 terminator DWZZA-VA, trilink connector, and H879 terminator T T Memory Channel link cable AlphaServer 2100A T T 1 2 1 2 3 4 3 4 5 5 Memory Channel adapters AlphaServer 2100A BA350 Library Robotics BA350 DLT1 H879-AA terminators BN21K or BN21L cable DLT2 Expansion Unit Interface TL892 1 Ft SCSI Bu
8.7.1 TL890 DLT MiniLibrary Expansion Unit Hardware The TL890 expansion unit is installed above the TL891/TL892 DLT MiniLibrary base units in a SW500, SW800, or RETMA cabinet. The expansion unit integrates the robotics in the individual modules into a single, coordinated library robotics system. The TL890 assumes control of the media, maintaining an inventory of all media present in the system, and controls movement of all media.
• Robotics control cables from each base module to the expansion unit: These cables have a DB-9 male connector on one end and a DB-9 female connector on the other end. Connect the male end to the Expansion Unit Interface connector on the base module and the female end to any Expansion Modules connector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector a base module is connected to.
Figure 8–10: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses DWZZA-VA, trilink connector, and H879 terminator BN21K or BN21L cables T T T T T Memory Channel link cable T T 1 2 3 4 1 2 5 5 3 4 Memory Channel adapters BA350 AlphaServer 2100As BN21K or BN21L cables Diag SCSI TL890 Robotics Control cables BA350 Motor H879-AA terminator Expansion Modules Library Robotics DLT1 DLT2 H879-AA terminator 0.
unit will not have control over the base module robotics when you power up the MiniLibrary system if you do not reconfigure the base modules as a slave. To reconfigure a TL891/TL892 base module as a slave to the TL890 DLT MiniLibrary expansion unit, perform the following procedure on each base module in the system: 1. Turn on the power switch on the TL891/TL892 base module to be reconfigured. ____________________ Note _____________________ Do not power on the expansion unit.
7. After the selection stops flashing and the control panel indicates that the change is not effective until a reboot, press the Enter button. 8. When the Special Configuration menu reappears, turn the power switch off and then on to cycle the power. The base module is now reconfigured as a slave to the TL890 expansion unit. 9. Repeat the steps for each TL891/TL892 base module present that is to be a slave to the TL890 expansion unit. 8.7.2.
control functions are carried out from the expansion unit control panel. This includes setting the SCSI ID for each of the tape drives present. To set the SCSI IDs for the tape drives in a MiniLibrary configured with TL890/TL891/TL892 hardware, follow these steps: 1. Apply power to the MiniLibrary, ensuring that you power up the expansion unit after or at the same time as the base modules. 2.
10. If there are other items you wish to configure, press the Escape button until the Configure submenu is displayed, then select the item to be configured. Repeat this procedure for each item you wish to configure. 11. If there are no more items to be configured, press the Escape button until the Default window is displayed. 8.
Table 8–4: TL894 Default SCSI ID Settings (cont.) SCSI Device SCSI Address Tape Drive 2 4 Tape Drive 3 5 To set the SCSI ID for the TL894 robotics controller, follow these steps: 1. Press and release the Control Panel STANDBY button and verify that the SDA (Status Display Area) shows System Off-line. 2. Press and release SELECT to enter the menu mode. 3. Verify that the following information is displayed in the SDA: Menu: Configuration: 4.
12. Press and release the up or down button and the SELECT button simultaneously, and verify that System On-line or System Off-line is displayed in the SDA. To set the SCSI ID for each tape drive if the desired SCSI IDs are different from those shown in Table 8–4, follow these steps: 1. Press and release the Control Panel STANDBY button and verify that the SDA (Status Display Area) shows System Off-line. 2. Press and release SELECT to enter the menu mode. 3.
14. Press and release the up or down button and the SELECT button simultaneously and verify that System On-line or System Off-line is displayed in the SDA. 8.8.3 TL894 Tape Library Internal Cabling The default internal cabling configuration for the TL894 tape library has the robotics controller and top drive (drive 0) on SCSI bus port 1. Drive 1 is on SCSI bus port 2, drive 2 is on SCSI port 3, and drive 3 is on SCSI bus port 4.
other drive to be daisy chained. Use the SCSI jumper cable to connect the two drives and place them on the same SCSI bus. ______________________ Notes ______________________ We recommend that you not place more than two TZ89 tape drives on any one SCSI bus in these tape libraries. We also recommend that storage be placed on shared SCSI buses that do not have tape drives. Therefore, we do not recommend that you reconfigure the TL894 tape library into the one-bus configuration.
Figure 8–12 shows a sample TruCluster Server cluster using a TL894 tape library. In the sample configuration, the tape library has been connected in the two-bus mode by jumpering tape drive 0 to tape drive 1 and tape drive 2 to tape drive 3 (See Section 8.8.3 and Figure 8–11). The two SCSI buses are left at the default SCSI IDs and terminated at drives 1 and 3 with the installed terminators (part number 0415619).
8.9 Preparing the TL895 DLT Automated Tape Library for Shared SCSI Bus Usage The topics in this section provide information on preparing the TL895 Digital Linear Tape (DLT) automated tape library for use on a shared SCSI bus. ______________________ Note _______________________ To achieve system performance capabilities, we recommend placing no more than two TZ89 drives on a SCSI bus segment. We also recommend that storage be placed on shared SCSI buses that do not have tape drives.
8.9.1 TL895 Robotic Controller Required Firmware Robotic firmware version N2.20 is the minimum firmware revision supported in a TruCluster Server cluster. For information on upgrading the robotic firmware, see the Flash Download section of the TL895 DLT Tape Library Diagnostic Software User’s Manual. 8.9.2 Setting the TL895 Tape Library SCSI IDs The library and each tape drive must have the SCSI ID set (unless the default is sufficient). Table 8–5 lists the TL895 default SCSI IDs.
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. For the devices, select the desired device (library or drive) by scrolling through the devices with the arrow buttons. After the library or selected drive is selected, use the Select button to highlight the SCSI ID. 6. Use the arrow buttons to scroll through the setting choices until the desired setting appears. 7.
To reconfigure TL895 SCSI bus configuration, follow these steps: 1. Remove the SCSI bus cable from one drive to be daisy chained. 2. Remove the terminator from the other drive to be daisy chained. 3. Ensure that the drive that will be the last drive on the SCSI bus has a terminator installed. 4. Install a SCSI bus jumper cable (part number 6210567) on the open connectors of the two drives to be daisy chained.
8.9.4 Upgrading a TL895 The TL985 DLT automated tape library can be upgraded from two or five tape drives to seven drives with multiple DS-TL89X-UA upgrade kits. Besides the associated documentation, the upgrade kit contains one TZ89N-AV tape drive, a SCSI bus terminator, a SCSI bus jumper (part number 6210567) so you can place more than one drive on the same SCSI bus, and other associated hardware.
______________________ Note _______________________ To achieve system performance capabilities, We recommend placing no more than two TZ89 drives on a SCSI bus. The TL893 and TL896 Automated Tape Libraries (ATLs) are designed to provide high-capacity storage and robotic access for the Digital Linear Tape (DLT) series of tape drives. They are identical except in the number of tape drives and the maximum capacity for tape cartridges.
on adding additional cabinets. Up to five cabinets are supported with the TruCluster Server. For TruCluster Server, the tape cartridges in all the cabinets are combined into one logical unit, with consecutive numbering from the first cabinet to the last cabinet, by an upgrade from the multi-unit, multi-LUN (MUML) configuration to a multi-unit, single-LUN (MUSL) configuration. See the TL82X/TL89X MUML to MUSL Upgrade Instructions manual for information on the firmware upgrade.
Table 8–6: MUC Switch Functions Switch Function 1, 2, and 3 MUC SCSI ID if Switch 7 is downa 4 and 5 Must be down, reserved for testing 6 Default is up, disable bus reset on power up 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.10.
Table 8–8: TL893 Default SCSI IDs Device Default SCSI ID MUC 2 Drive 2 (top) 5 B Drive 1 (middle) 4 A Drive 0 (bottom) 3 SCSI Port C Table 8–9: 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.10.
– The bottom shelf tape drive (SCSI ID 3) is on SCSI Port A and is also terminated on the drive with a 68-pin Micro-D terminator, part number 0415619.
– The lower bay top shelf tape drive (tape drive 2, SCSI ID 5) is on SCSI Port A and is terminated on the tape drive. – The lower bay middle shelf tape drive (tape drive 1, SCSI ID 4) is on SCSI Port B and is terminated on the tape drive. – 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).
8.10.6 Connecting the TL893 and TL896 Automated Tape Libraries to the Shared SCSI Bus The TL893 and TL896 Automated Tape Libraries (ATLs) have up to 3 meters of internal SCSI cabling on each SCSI bus. Because of the internal SCSI cable lengths, it is not possible to use a trilink connector or Y cable to terminate the SCSI bus external to the library as is done with other devices on the shared SCSI bus.
Figure 8–16: 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 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 Controller B HSZ70 7 4 Controller A HSZ70 StorageWorks RAID Array 7000 TL896 A B C D E F SCSI Ports (3-bus mode) NOTE: This
• TL891 MiniLibrary System User’s Guide • TL881 MiniLibrary Drive Upgrade Procedure • Pass-Through Expansion Kit Installation Instructions The TL881 and TL891 Digital Linear Tape (DLT) MiniLibraries are offered as standalone tabletop units or as expandable rackmount units. The following sections describe these units in more detail. 8.11.1.
device and only works as a slave to the expansion unit. To create a multimodule rackmount system, there must be one expansion unit and at least one base unit. The expansion unit has to be the top module in the configuration. The expansion unit works with either the TL881 or TL891 base unit.
TL881 or TL891 MiniLibrary in configurations set up for either maximum performance or maximum capacity. Table 8–10: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary 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.
Table 8–11: DLT MiniLibrary Part Numbers (cont.
The topics in this section provide information on preparing the TL881 or TL891 DLT MiniLibrary tabletop model or rackmount base unit for use on a shared SCSI bus. For complete hardware installation instructions, see the TL881 MiniLibrary System User’s Guide or TL891 MiniLibrary System User’s Guide. 8.11.2.1.
____________________ Note _____________________ When you enter the Menu Mode, the Ready light goes out, an indication that the module is off line, and all medium changer commands from the host return a SCSI "not ready" status until you exit the Menu Mode and the Ready light comes on once again. 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 tape drive SCSI connectors are labeled DLT1 (tape drive 1) and DLT2 (tape drive 2). The control panel designation for the drives is DLT0 (tape drive 1) and DLT1 (tape drive 2). The default for the TL881 or TL891 DLT MiniLibrary is to place the robotics controller and tape drive 1 on the same SCSI bus (Figure 8–17). 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–17: TL891 Standalone Cluster Configuration Network Member System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPBA-CB (ID 6) T 6 T KZPBA-CB (ID 7) 5 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 1 1 T Library Robotics T 6 DLT1 T DS-DWZZH-03 7 2 3 T 4 DLT2 Controller B HSZ70 Controller A HSZ70 Expansion Unit Interface StorageWorks RAID Array 7000 TL891 NOTE: This drawing is not to scale. 0.
Table 8–12: 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.11.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 a base unit or data unit is connected to. • SCSI bus connection to the expansion unit robotics: Connect the shared SCSI bus that will control the robotics to one of the SCSI connectors on the expansion unit with a 328215-00X, BN21K, or BN21L cable.
Figure 8–18: TL881 DLT MiniLibrary Rackmount Configuration Network Memory Channel Interface Member System 1 Member System 2 Memory Channel Memory Channel T 6 KZPBA-CB (ID 6) T KZPBA-CB (ID 6) T KZPBA-CB (ID 7) 5 5 T KZPBA-CB (ID 7) KZPBA-CB (ID 6) 7 7 1 1 7 5 KZPBA-CB (ID 7) 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–13: 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.12.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–19: 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 T SCSI Bulkhead A B T C
8.12.3.4 Connecting the ESL9326D Enterprise Library to the Shared SCSI Bus The ESL9326D Enterprise Library has 5 meters of internal SCSI bus cabling for each pair of tape drives. Because of the internal SCSI bus lengths, it is not possible to use a trilink connector or Y cable to terminate the SCSI bus external to the tape library as is done with other devices on the shared SCSI bus. Each SCSI bus must be terminated 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: 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. May be used for redundant power supply.
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: 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.
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. Ensure that the personality module address switches on one UltraSCSI BA356 are set to select SCSI IDs 0 through 6 and the address switches on the other UltraSCSI BA356 personality module are set to select SCSI IDs 8 through 14. 2. You will need two H8861-AA VHDCI trilink connectors.
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: Externally Terminated Shared SCSI Bus with Mid-Bus HSZ50 RAID Array Controllers Network Member System 1 Member System 2 Memory Channel Interface Memory Channel Memory Channel KZPSA-BB (ID 6) KZPSA-BB (ID 7) T T 2 1 3 4 HSZ50 Controller A 3 4 3 1 2 HSZ50 Controller B ZK-1596U-AI Table 9–3 shows the components used to create the cluster shown in Figure 9–12 and Figure 9–13.
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.
• Ensure that the W1 and W2 jumpers are installed to enable the single-ended termination on one end of the bus. ___________________ Note ___________________ The RAID Array 310 SCSI bus converter board is the same logic board used in the DWZZB signal converter. 2. Attach an H885-AA trilink connector to the SCSI input connector (on the back of the cabinet). 3.
5. 6. Install the UltraSCSI hub in: • A StorageWorks UltraSCSI BA356 shelf (which has the required 180-watt power supply). • A non-UltraSCSI BA356 which has been upgraded to the 180-watt power supply with the DS-BA35X-HH option. If you are using a: • DS-DWZZH-03: Install a BN38C (or BN38D) HD to VHDCI cable between any DS-DWZZH-03 port and the open connector on the H885-AA trilink connector (on the RAID array controller).
Figure 9–14: TruCluster Server Cluster Using DS-DWZZH-03, SCSI Adapter with Terminators Installed, and HSZ50 1 KZPSA-BB DS-DWZZH-03 T T AlphaServer Member System 1 T 1 T HSZ50 2 1 4 KZPSA-BB T HSZ50 2 T AlphaServer Member System 2 3 ZK-1415U-AI Table 9–4 shows the components used to create the cluster shown in Figure 9–14.
Figure 9–15: TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, a DS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller AlphaServer Member System 1 T KZPSA-BB 1 1 KZPSA-BB DS-DWZZH-05 T T 1 T AlphaServer Member System 2 T T T 1 1 HSZ50 2 4 KZPSA-BB KZPSA-BB T T AlphaServer Member System 3 AlphaServer Member System 4 HSZ50 2 T 3 ZK-1449U-AI ______________________ Note _______________________ The systems shown in Figure 9–15 use KZPSA-BB SCSI adapters.
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.4.1. The KZPBA-CB UltraSCSI host adapter: • Is a high-performance PCI option connecting the PCI-based host system to the devices on a 16-bit, ultrawide differential SCSI bus. • 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.7 TL894 Section 8.8 TL895 Section 8.9 TL893/TL896 Section 8.10 TL881/TL891 DLT MiniLibraries Section 8.11 Compaq ESL9326D Enterprise Library Section 8.12 _____________________ Notes _____________________ If you install tape devices on the shared SCSI buses, ensure that you understand how the particular tape device(s) affect the shared SCSI bus.
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.) pke0_termpwr 1 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 User Define Identifier (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 A ACS V8.
TL892, 8–20, 8–24 TL893, 8–47 TL894, 8–34 TL895, 8–40 TL896, 8–47 TZ885, 8–13 TZ887, 8–16 TZ88N-TA, 8–4 TZ88N-VA, 8–3 changing HSG80 failover modes, 6–55 cluster expanding, 3–7, 9–6 increasing availability, 4–3 planning, 4–2 cluster interconnects increasing availability, 4–2 clusterwide file systems allocating a disk for, 1–4 command atmconfig, 7–4 CONFIGURATION RESTORE, 6–33 emxmgr, 6–59 emxmgr -d, 6–59 emxmgr -m, 6–59 emxmgr -t, 6–60 init, 6–24, 6–45, 6–48, 6–50 SAVE_CONFIGURATION, 6–33 set bootdef_dev,
clusterwide /usr, 1–10 clusterwide /var, 1–10 clusterwide root, 1–10 member boot, 1–10 quorum, 1–10 disklabel, 6–53 displaying device information KZPBA-CB, 4–9t, 10–5t, 10–7t KZPSA-BB, 10–5t, 10–7t DLT Compaq 20/40 GB DLT Tape Drive, 8–9 TZ885, 8–13 TZ887, 8–15 DLT MiniLibrary Configuring TL881/TL891 as slave, 8–61 Configuring TL891 as slave, 8–26 TL881, 8–48 TL891, 8–48 DS-BA356 DS-DWZZH-03 installed in, 2–9, 3–9, 4–7, 9–29, 10–3 DS-DWZZH-05 installed in, 3–10 DS-BA35X-DA personality module, 3–3, 3–5,
configuring, 2–5 port configuration, 2–5 replacing controllers of, 6–32 transparent failover mode, 2–5 unit configuration, 2–5 ESL9000 series tape library ( See ESL9326D ) ESL9326D cables, 8–68 cabling, 8–65, 8–68 capacity, 8–65 firmware, 8–66 internal cabling, 8–67 number of drives, 8–65 part numbers, 8–65 SCSI connectors, 8–68 setting SCSI IDs, 8–66 tape cartridges, 8–65 tape drives, 8–65 termination, 8–68 upgrading, 8–65 F F_Port, 6–5 fabric, 6–5 failover mode changing, 6–55 multiple-bus, 6–55 set nofa
supported Y cables, 2–1 terminators, 2–11 trilink connectors, 2–11 host bus adapters ( See also hardware configuration ) ATM adapter, 7–1 KGPSA, 6–22 KZPSA, 10–3 MC2, 5–10 MC2 cables, 5–9 Memory Channel, 5–5 ( See KGPSA, KZPBA-CB, KZPSA-BB ) HSG80 controller ACS, 2–4 changing failover modes, 6–55 configuring, 2–5, 6–26 multiple-bus failover, 6–28 obtaining the worldwide name of, 6–31 port configuration, 2–5 port_n_topology, 6–29 replacing, 6–32 resetting offsets, 6–55 setting controller values, 6–26, 6–
KZPSA-BB displaying device information, 10–5t, 10–7t installation, 10–3 restrictions, 2–6 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 LAN emulation ( See LANE ) LANE, 7–1 LFU, 10–18 booting, 10–18 starting, 10–18 updating firmware, 10–18 link cable installation, 5–7 Loadable Firmware Update utility ( See LFU ) Logical Storage Manager ( See LSM ) LSM mirroring across SCSI buses, 1–11
O optical cable, 6–16 optical converter cable connection, 5–6 installation, 5–6 P part numbers ESL9326D, 8–65 partitioned storagesets, 3–18 performance improving, 4–2 personality module, 3–3, 9–13 ( See also signal converters ) planning the hardware configuration, 4–2 point-to-point, 6–6 port name, 6–31 powering up TL881/891 DLT MiniLibrary, 8–62 preparing storage shelves BA350, 9–15 BA350 and BA356, 9–18 BA356, 9–16, 9–20 UltraSCSI BA356, 9–17, 9–21 Prestoserve cannot be used in a cluster, 4–3 Q quorum
( See cables ) requirement, 2–10 SCSI controllers bus speed for, 3–5 SCSI ID selection, 9–17 BA356, 9–16 SCSI IDs BA350, 9–9 BA350 storage shelves, 9–15 BA356, 9–11, 9–16 HSZ20 controller, 9–24 HSZ40 controller, 9–24 HSZ50 controller, 9–24 in BA356, 9–11 in UltraSCSI BA356, 9–13 RAID subsystem controllers, 9–24 requirement, 3–5 UltraSCSI BA356, 9–13, 9–17 SCSI targets number of, 2–5 SCSI terminators supported, 2–11 SCSI-2 bus, 3–5 SCSI-3, 6–4 selecting BA356 disk SCSI IDs, 9–11 selecting UltraSCSI BA356 dis
SBB, 9–2 single-ended termination, 9–3 standalone, 9–2 terminating, 9–2 termination, 9–3 single-ended SCSI buses description of, 3–4 single-ended transmission definition, 3–4 storage shelves, 9–8, 9–9, 9–13 attaching to shared SCSI bus, 9–8, 9–13 BA350, 9–9 BA356, 9–9 overview, 9–8, 9–13 setting up, 3–16, 9–14 subscriber connector, 6–16 switch 10Base-T Ethernet connection, 6–15 changing password, 6–21 changing user names, 6–21 front panel, 6–15, 6–18 GBIC, 6–16 installing, 6–15 interface module, 6–16 over
setting SCSI ID, 8–30 TL895 cabling, 8–40 TL896, 8–40, 8–41 cabling, 8–44, 8–47 MUC switch functions, 8–42 setting SCSI ID, 8–43 transparent failover, 1–14, 3–17 changing to multiple-bus failover, 6–55 trilink connectors connecting devices with, 9–6 requirement, 2–11 supported, 2–11 TZ88, 8–1 versions, 8–1 TZ885, 8–13 cabling, 8–13 setting SCSI ID, 8–13 TZ887, 8–15 cabling, 8–16 setting SCSI ID, 8–15 TZ88N-TA, 8–1 cabling, 8–4 setting SCSI ID, 8–4 TZ88N-VA, 8–1 cabling, 8–3 setting SCSI ID, 8–2 TZ89, 8–5
Y Y cables connecting devices with, 9–6 supported, 2–10 Index–11
How to Order Tru64 UNIX Documentation You can order documentation for the Tru64 UNIX operating system and related products at the following Web site: http://www.businesslink.digital.com/ If you need help deciding which documentation best meets your needs, see the Tru64 UNIX Documentation Overview or call 800-344-4825 in the United States and Canada. In Puerto Rico, call 787-781-0505. In other countries, contact your local Compaq subsidiary.
Reader’s Comments TruCluster Server Hardware Configuration AA-RHGWB-TE Compaq welcomes your comments and suggestions on this manual. Your input will help us to write documentation that meets your needs. Please send your suggestions using one of the following methods: • This postage-paid form • 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.
