Compaq AA-RHGWB-TE - Manual

Page 3 - Contents; About This Manual; Overview of the TruCluster Server Hardware Configuration . .; Hardware Requirements and Restrictions; Contents iii

Contents About This Manual 1 Introduction 1.1 The TruCluster Server Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 1.2 Overview of the TruCluster Server Hardware Configuration . . 1–2 1.3 Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . ....

Page 4 - iv Contents

2.6 RAID Array Controller Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7 2.7 SCSI Signal Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8 2.8 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs . . . . . . . . . . . 2–9...

Page 5 - Setting Up the Memory Channel Cluster Interconnect; Installing the MC2 Optical Converter in the Member System; Using Fibre Channel Storage; Contents v

4.3 TruCluster Server Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . 4–5 4.3.1 Installation of a KZPBA-CB Using Internal Terminationfor a Radial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7 4.3.2 Displaying KZPBA-CB Adapters wit...

Page 6 - vi Contents

6.2.2.2 Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 6.2.2.3 Arbitrated Loop Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7 6.3 Example Fibre Channel Configurations Supported byTruCluste...

Page 7 - Contents vii

6.12 Using the emx Manager to Display Fibre Channel AdapterInformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–59 6.12.1 Using the emxmgr Utility to Display Fibre ChannelAdapter Information . . . . . . . . . . . . . . ...

Page 8 - TL881 and TL891 DLT MiniLibrary Tabletop Model . .; viii Contents

8.7.2.1 Cabling the DLT MiniLibraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24 8.7.2.2 Configuring a Base Module as a Slave . . . . . . . . . . . . . . . . . . . 8–26 8.7.2.3 Powering Up the DLT MiniLibrary . . . . . . . . . . . . . . . . . . . . . . . 8–28 8.7.2.4 Setting the TL89...

Page 9 - Powering Up the TL881/TL891 DLT MiniLibrary .; to Non-UltraSCSI Devices; DWZZA and DWZZB Signal Converter Termination . .; Contents ix

8.11.2.1.1 Setting the Standalone MiniLibrary Tape DriveSCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53 8.11.2.1.2 Cabling the TL881 or TL891 DLT MiniLibrary . . . . 8–54 8.11.2.2 Preparing a TL881 or TL891 Rackmount MiniLibraryfor Sha...

Page 10 - Connecting Two BA356s for Shared SCSI Bus Usage .; Configuring Systems for External Termination or Radial; x Contents

9.4.1 Preparing BA350, BA356, and UltraSCSI BA356 StorageShelves for an Externally Terminated TruCluster ServerConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15 9.4.1.1 Preparing a BA350 Storage Shelf for Shared SCSIUsage . ....

Page 11 - Contents xi

10.1.4.5 Updating the KZPSA-BB Adapter Firmware . . . . . . . . . . . 10–18 A Worldwide ID to Disk Name Conversion Table Index Examples 4–1 Displaying Configuration on an AlphaServer DS20 . . . . . . . . . . . . . 4–10 4–2 Displaying Devices on an AlphaServer DS20 . . . . . . . . . . . . . . . . . ....

Page 12 - NSPOF Cluster using HSZ70s in Multiple-Bus Failover Mode; xii Contents

1–2 Generic Two-Node Cluster with Minimum Disk Configurationand Quorum Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7 1–3 Minimum Two-Node Cluster with UltraSCSI BA356 StorageUnit . . . . . . . . . . . . . . . . . . . . . . . . . . ...

Page 13 - Tables; Contents xiii

8–6 Cabling a Shared SCSI Bus with a TZ885 . . . . . . . . . . . . . . . . . . . . . . . . 8–15 8–7 TZ887 DLT MiniLibrary Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16 8–8 Cabling a Shared SCSI Bus with a TZ887 . . . . . . . . . . . . . . . . . . . . . . . . 8–17 8–9 ...

Page 14 - xiv Contents

2–4 Supported SCSI Terminators and Trilink Connectors . . . . . . . . . . 2–11 3–1 SCSI Bus Speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5 3–2 SCSI Bus Segment Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....

Page 15 - Contents xv

9–4 Hardware Components Used in Configuration Shown inFigure 9–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–30 10–1 Configuring TruCluster Server Hardware for Use with a PCISCSI Adapter . . . . . . . . . . . . . . . . . ...

Page 17 - Audience; Describes hardware requirements and restrictions.

About This Manual This manual describes how to set up and maintain the hardwareconfiguration for a TruCluster Server cluster. Audience This manual is for system administrators who will set up and configure thehardware before installing the TruCluster Server software. The manualassumes that you are f...

Page 18 - Related Documents; DEC RAID Subsystem User ’s Guide; xviii About This Manual

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 busrequirements, and how to connect storage to a shared SCSI bus usingexternal termination or radial connections to non-Ul...

Page 19 - About This Manual xix

• HSZ70 Array Controller HSOF Version 7.0 Configuration Manual • HSZ80 Array Controller ACS Version 8.2 • Compaq StorageWorks HSG80 Array Controller ACS Version 8.5Configuration Guide • Compaq StorageWorks HSG80 Array Controller ACS Version 8.5 CLIReference Guide • Wwidmgr User ’s Manual For informa...

Page 20 - Reader’s Comments; You can send your comments in the following ways:; xx About This Manual

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 clusterconfigurations. You can order the document through the Compaq LiteratureOrder System (LOS) as o...

Page 21 - Conventions; cat; file; About This Manual xxi

UBPG Publications ManagerZKO3-3/Y32110 Spit Brook RoadNashua, 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 ...

Page 22 - cluster; xxii About This Manual

cluster Bold text indicates a term that is defined in theglossary. xxii About This Manual

Page 23 - Introduction; The TruCluster Server Product; Introduction 1–1

1 Introduction This chapter introduces the TruCluster Server product and some basiccluster hardware configuration concepts. Subsequent chapters describe how to set up and maintain TruCluster Serverhardware configurations. See the TruCluster Server Software Installationmanual for information about so...

Page 24 - Note; The clusterwide root (; –2 Introduction

interconnect, you can more easily alter or expand your cluster ’s hardwareconfiguration 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 highlyspecific hardware component...

Page 25 - Memory Requirements; Cluster members require a minimum of 128 MB of memory.; Minimum Disk Requirements; You need to allocate disks for the following uses:; Introduction 1–3

contains up to eight linecards. The Memory Channel adapter in eachsystem in the cluster is connected to the Memory Channel hub. One or two Memory Channel adapters can be used with TruClusterServer. When dual Memory Channel adapters are installed, if theMemory Channel adapter being used for cluster c...

Page 26 - root; first; –4 Introduction

The operating system disk (Tru64 UNIX disk) cannot be used as aclusterwide disk, a member boot disk, or as the quorum disk. Because the Tru64 UNIX operating system will be available on the firstcluster member, in an emergency, after shutting down the cluster, you havethe option of booting the Tru64 ...

Page 27 - Introduction 1–5

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 requiredpartitions. You can move the swap partition off the member boot disk. Seethe TruCluster...

Page 28 - Network; –6 Introduction

Figure 1–1 shows a generic two-node cluster with the minimum numberof disks. • Tru64 UNIX disk • Clusterwide root ( / ), /usr , and /var • Member 1 boot disk • Member 2 boot disk A minimum configuration cluster may have reduced availability due to thelack of a quorum disk. As shown, with only two-me...

Page 29 - Growing a Cluster from Minimum Storage to a NSPOF; Adding a second SCSI bus allows the use of LSM to mirror the; Introduction 1–7

Administration manual for a discussion of how and when to use a quorumdisk. Figure 1–2: Generic Two-Node Cluster with Minimum Disk Configurationand Quorum Disk Member System 1 Network Memory Channel Shared SCSI Bus PCI SCSI Adapter Member System 2 PCI SCSI Adapter Cluster File System root (/) /usr /...

Page 30 - –8 Introduction

• Using a RAID array controller in transparent failover mode allows theuse of hardware RAID to mirror the disks. However, without a secondSCSI bus, second Memory Channel, and redundant networks, thisconfiguration is still not a NSPOF cluster (Section 1.6.4). • By using an HSZ70, HSZ80, or HSG80 with...

Page 31 - Introduction 1–9

Figure 1–3: Minimum Two-Node Cluster with UltraSCSI BA356 Storage Unit ID 5 PWR SharedSCSIBus Clusterwide/, /usr, /var Member 1Boot Disk Member 2Boot Disk Quorum Disk UltraSCSI BA356 ID 4 Host Bus Adapter (ID 7) MemoryChannelInterface Memory Channel Host Bus Adapter (ID 6) Memory Channel MemberSyste...

Page 32 - Two-Node Clusters Using UltraSCSI BA356 Storage Units with

this slot can be used for a second power supply to provide fullyredundant power to the storage shelf. Note that with the use of the cluster file system (See the TruCluster ServerCluster Administration manual for a discussion of the cluster file system),the clusterwide root ( / ), /usr , and /var fil...

Page 33 - and

multiple BA356 storage units can be used on the same SCSI bus to allowmore devices on the same bus. Figure 1–4 shows the configuration in Figure 1–3 with a second UltraSCSIBA356 storage unit that provides an additional seven disks for highlyavailable applications. Figure 1–4: Two-Node Cluster with T...

Page 34 - You cannot use LSM to mirror the clusterwide root (

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 theLogical Storage Manager (LSM) to mirror data disks, and the clusterwide /usr and /var file systems across SCSI buses. ______________________ ...

Page 35 - By using LSM to mirror the; Using Hardware RAID to Mirror the Clusterwide Root File

Figure 1–5: Two-Node Configurations with UltraSCSI BA356 Storage Unitsand Dual SCSI Buses Host Bus Adapter (ID 7) Network MemoryChannelInterface Memory Channel Memory Channel MemberSystem 2 MemberSystem 1 Tru64 UNIX Disk Host Bus Adapter (ID 6) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) ID 8 ID...

Page 36 - StorageWorks

HSZ70. The array controllers can be configured as a dual redundant pair. Ifyou want the capability to fail over from one controller to another controller,you must install the second controller. Also, you must set the failover mode. Figure 1–6: Cluster Configuration with HSZ70 Controllers in Transpar...

Page 37 - Notes

Note that in the configuration shown in Figure 1–6, there is only one sharedSCSI bus. Even by mirroring the clusterwide root and member boot disks,the single shared SCSI bus is a single point of failure. 1.6.5 Creating a NSPOF Cluster To create a no-single-point-of-failure (NSPOF) cluster: • Use har...

Page 38 - Member System 1

Figure 1–7: NSPOF Cluster using HSZ70s in Multiple-Bus Failover Mode Networks Host Bus Adapter (ID 7) Member System 1 Member System 2 Tru64 UNIX Disk Host Bus Adapter (ID 6) Host Bus Adapter (ID 6) Host Bus Adapter (ID 7) HSZ70 StorageWorks RAID Array 7000 HSZ70 ZK-1594U-AI MemoryChannelInterfaces M...

Page 39 - Overview of Setting up the TruCluster Server Hardware; Draw a diagram of your configuration.

Figure 1–8: NSPOF Fibre Channel Cluster using HSG80s in Multiple-BusFailover Mode KGPSA RA8000/ ESA12000 Member System 2 KGPSA KGPSA DSGGA DSGGA RA8000/ ESA12000 Member System 1 KGPSA HSG80 HSG80 HSG80 HSG80 ZK-1533U-AI 1.7 Overview of Setting up the TruCluster Server Hardware Configuration To set u...

Page 41 - TruCluster Server Member System Requirements; You can also obtain firmware information from the Web at; Memory Channel Restrictions; Hardware Requirements and Restrictions 2–1

2 Hardware Requirements and Restrictions This chapter describes the hardware requirements and restrictions fora TruCluster Server cluster. It includes lists of supported cables, trilinkconnectors, Y cables, and terminators. See the TruCluster Server Software Product Description (SPD) for the latesti...

Page 42 - –2 Hardware Requirements and Restrictions

There are currently three versions of the Memory Channel product; MemoryChannel 1, Memory Channel 1.5, and Memory Channel 2. The MemoryChannel 1 and Memory Channel 1.5 products are very similar (the PCIadapter for both versions is the CCMAA module) and are generally referredto as MC1 throughout this...

Page 43 - Fibre Channel Requirements and Restrictions; Hardware Requirements and Restrictions 2–3

• For AlphaServer 2000 systems, the B2111-AA module must be atRevision H or higher. For AlphaServer 2100 systems, the B2110-AA module must be atRevision L or higher. Use the examine console command to determine if these modules are at a supported revision as follows: P00>>> examine -b econf...

Page 44 - Table 2–1: AlphaServer Systems Supported for Fibre Channel; AlphaServer; Compaq AlphaServer DS10; A maximum of four member systems is supported.; –4 Hardware Requirements and Restrictions

Table 2–1: AlphaServer Systems Supported for Fibre Channel AlphaServer Number of KGPSA-BC AdaptersSupported 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 8400 a 32 (2...

Page 45 - Hardware Requirements and Restrictions 2–5

• The Fibre Channel RAID Array 8000 (RA8000) midrange departmentalstorage subsystem and Fibre Channel Enterprise Storage Array 12000(ESA12000) house two HSG80 dual-channel controllers. There areprovisions for six UltraSCSI channels. • Only disk devices attached to the HSG80 Fibre Channel to Six Chan...

Page 46 - SCSI Bus Adapter Restrictions; new; –6 Hardware Requirements and Restrictions

2.4 SCSI Bus Adapter Restrictions To connect a member system to a shared SCSI bus, you must install a SCSIbus 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-BBhost bus adapters, KZPB...

Page 47 - Disk Device Restrictions; The restrictions for disk devices are as follows:; RAID Array Controller Restrictions; Table 2–2: RAID Controller SCSI IDs; RAID Controller

– AlphaServer 8200, 8400, GS60, GS60E, GS140: 32 The KZPBA-CB is supported on the DWLPB only; it is not supportedon the DWLPA module. – AlphaServer DS10: 2 – AlphaServer DS20/DS20E: 4 – AlphaServer ES40: 5 • A maximum of four HSZ50, HSZ70, or HSZ80 RAID array controllers canbe placed on a single KZP...

Page 48 - SCSI Signal Converters; The restrictions for SCSI signal converters are as follows:; –8 Hardware Requirements and Restrictions

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 SCSIinterface in your cluster configuration, you must connect it to a SCSI signalconverter. SCSI sign...

Page 49 - Improves the reliability of the detection of cable faults.; Hardware Requirements and Restrictions 2–9

2.8 DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI Hubs The DS-DWZZH-03 and DS-DWZZH-05 series UltraSCSI hubs are the onlyhubs supported in a TruCluster Server configuration. They are SCSI-2-and draft SCSI-3-compliant SCSI 16-bit signal converters capable of datatransfer rates of up to 40 MB/sec. These hubs ...

Page 50 - Table 2–3: Supported SCSI Cables; Cable; Three high; –10 Hardware Requirements and Restrictions

In addition, each supported cable comes in various lengths. Use the shortestpossible cables to adhere to the limits on SCSI bus length. Table 2–3 describes each supported cable and the context in which you woulduse the cable. Note that there are cables with the Compaq 6-3 part numberthat are not lis...

Page 51 - SCSI Terminators and Trilink Connectors; Table 2–4: Supported SCSI Terminators and Trilink Connectors; Pins; The requirements for trilink connectors are as follows:; Hardware Requirements and Restrictions 2–11

2.10 SCSI Terminators and Trilink Connectors Table 2–4 describes the supported trilink connectors and SCSI terminatorsand the context in which you would use them. Table 2–4: Supported SCSI Terminators and Trilink Connectors TrilinkConnector orTerminator Den-sity Pins Configuration Use H885-AA Three ...

Page 53 - Introduces SCSI bus configuration concepts; termpwr

3 Shared SCSI Bus Requirements and Configurations Using UltraSCSI Hardware A TruCluster Server cluster uses shared SCSI buses, external storageshelves or RAID controllers, and supports disk mirroring and fast file systemrecovery to provide high data availability and reliability. This chapter: • Intr...

Page 54 - This chapter discusses the following topics:; Shared SCSI Bus Configuration Requirements; A shared SCSI bus must adhere to the following requirements:

termination and covers radial configurations with the DWZZH UltraSCSIhubs 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 (S...

Page 55 - SCSI Bus Performance; Transmission method

• All supported UltraSCSI host adapters support UltraSCSI disks atUltraSCSI speeds in UltraSCSI BA356 shelves, RA7000 or ESA10000storage arrays (HSZ70 and HSZ80), or RA8000 or ESA12000 storagearrays (HSZ80 and HSG80). Older, non-UltraSCSI BA356 shelves aresupported with UltraSCSI host adapters and h...

Page 56 - Two transmission methods can be used in a SCSI bus:

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 thatmay be in a cable or a backplane, and cable or backplane connectors. EachUltraSCSI bus segment must have a terminator at e...

Page 57 - There are two data paths for SCSI devices:; Table 3–1: SCSI Bus Speeds; SCSI Bus; SCSI; SCSI Bus Device Identification Numbers

connect devices that use different transmission methods, use a SCSI signalconverter between the devices. The DS-BA35X-DA personality module isdiscussed in Section 9.1.2.2. See Section 9.1 for information about using theDWZZ* series of SCSI signal converters. You cannot use a DWZZA or DWZZB signal co...

Page 59 - Table 3–2: SCSI Bus Segment Length; meters; Terminating the Shared SCSI Bus when Using UltraSCSI; There are two rules for SCSI bus termination:

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 meters a a The maximum separation between a host and the stor...

Page 61 - Using a DWZZH UltraSCSI Hub in a Cluster Configuration; Require that termination power (

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 aTruCluster Server cluster. They both provide radial connection of clustermember systems and storage, and are similar in the following ways: • Contain internal termination for...

Page 62 - Figure 3–2 shows a front view of the DS-DWZZH-03 UltraSCSI hub.

• DS-DWZZH-03 and DS-DWZZH-05 UltraSCSI hubs may be housedin the same storage shelf with disk drives. Table 3–3 provides thesupported 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 sy...

Page 63 - Disk Drives

_____________________ Note _____________________ Dual power supplies are recommended for any BA356 shelfcontaining a DS-DWZZH-05 UltraSCSI hub in order toprovide a higher level of availability between cluster membersystems and storage. • The lower righthand device slot of the BA370 shelf within the ...

Page 64 - Installed; Fair

Table 3–3: DS-DWZZH UltraSCSI Hub Maximum Configurations (cont.) DS-DWZZH-03 DS-DWZZH-05 Disk Drives a PersonalityModule b 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 notassociated with the DS-DWZZH UltraSCSI h...

Page 68 - Preparing the UltraSCSI Storage Configuration

2. If fair arbitration is to be used, ensure that the switch on the front ofthe DS-DWZZH-05 UltraSCSI hub is in the Fair position. 3. Install the DS-DWZZH-05 UltraSCSI hub in a UltraSCSI BA356,non-UltraSCSI BA356 (if it has the required 180-watt power supply), orBA370 storage shelf. 3.7 Preparing th...

Page 69 - ) to help achieve a NSPOF configuration if each host has

3.7.1 Configuring Radially Connected TruCluster Server Clusters with UltraSCSI Hardware Radial configurations with RAID array controllers allow you to takeadvantage of the benefits of hardware mirroring, and to achieve ano-single-point-of-failure (NSPOF) cluster. Typical RAID array storagesubsystems...

Page 70 - When using transparent failover mode:

or SCSI bus failure, the host can redistribute the load to the survivingcontroller. In case of a controller failure, the surviving controller will handleall units. ______________________ Notes ______________________ Multiple-bus failover does not support device partitioning withthe HSZ70 or HSZ80. P...

Page 73 - H8861-AA VHDCI trilink connector

Table 3–4: Hardware Components Used in Configuration Shown in Figure3–5 Through Figure 3–8 Callout Number Description 1 BN38C cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator b a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not e...

Page 75 - HSZ70 controller A and controller B; You must use the same port on each HSZ80 controller.

• 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 aDS-BA356, BA356 (with the required 180-watt ...

Page 77 - Member System 2

Figure 3–8: TruCluster Server Configuration with HSZ80 in Multiple-BusFailover Mode KZPBA-CB (ID 7) Networks MemoryChannelInterfaces KZPBA-CB (ID 6) Memory Channel (mca0) Member System 2 Member System 1 D S - D W Z Z H - 0 3 T T T 2 3 1 4 1 3 T KZPBA-CB (ID 6) KZPBA-CB (ID 7) D S - D W Z Z H - 0 3 T...

Page 79 - If you are using Fibre Channel storage, see Chapter 6.

4 TruCluster Server System Configuration Using UltraSCSI Hardware This chapter describes how to prepare systems for a TruCluster Servercluster, using UltraSCSI hardware and the preferred method of radialconfiguration, including how to connect devices to a shared SCSI bus forthe TruCluster Server pro...

Page 80 - Cluster interconnects

This is especially critical if you will install tape devices on the sharedSCSI bus. With the exception of the TZ885, TZ887, TL890, TL891, andTL892, tape devices can only be installed at the end of a shared SCSIbus. These tape devices are the only supported tape devices that canbe terminated external...

Page 81 - Table 4–1: Planning Your Configuration

• Number of shared SCSI buses and the storage on each shared bus Using shared SCSI buses increases storage availability. You can connect32 shared SCSI buses to a cluster member. You can use any combinationof KZPSA-BB, KZPBA-CB, or KGPSA-BC/CA host bus adapters. In addition, RAID array controllers al...

Page 82 - Obtaining the Firmware Release Notes; Alpha Systems

Table 4–1: Planning Your Configuration (cont.) To increase: You can: Disk availability Mirror disks across shared buses. Use a RAID array controller. Shared storage capacity Increase the number of shared buses. Use a RAID array controller. Increase disk size. 4.2 Obtaining the Firmware Release Notes...

Page 83 - Print the release notes.; TruCluster Server Hardware Installation

6. Copy the appropriate release notes to your system disk. In thisexample, obtain the firmware release notes for the AlphaServerDS20 from the Version 5.6 Alpha Firmware Update CD-ROM: # cp /mnt/doc/ds20_v56_fw_relnote.txt ds20-rel-notes 7. Unmount the CD-ROM drive: # umount /mnt 8. Print the release...

Page 84 - Step Action; Chapter 5

______________________ Note _______________________ The KZPSA-BB can be used in any configuration in place of theKZPBA-CB. The use of the KZPSA-BB is not mentioned in thischapter because it is not UltraSCSI hardware, and it cannotoperate at UltraSCSI speeds. The use of the KZPSA-BB (and the KZPBA-CB...

Page 85 - Installation of a KZPBA-CB Using Internal Termination for a; A DWZZH UltraSCSI hub can be installed in:

Table 4–2: Configuring TruCluster Server Hardware (cont.) Step Action Refer to: 4 Update the system SRM consolefirmware from the latest Alpha SystemsFirmware Update CD-ROM. Use the firmware update releasenotes (Section 4.2) ______________________ Note _____________________ The SRM console firmware i...

Page 88 - HSZ70 or HSZ80 in transparent failover mode; Commands; Example 4–1: Displaying Configuration on an AlphaServer DS20

Table 4–3: Installing the KZPBA-CB for Radial Connection to a DWZZHUltraSCSI Hub (cont.) Step Action Refer to: _____________________ Notes _____________________ Ensure that the SCSI ID that you use is distinct from all other SCSI IDson the same shared SCSI bus. If you do not remember the other SCSII...

Page 90 - Example 4–2: Displaying Devices on an AlphaServer DS20

Example 4–1: Displaying Configuration on an AlphaServer DS20 (cont.) Bus 02 Slot 02: DE500-AA Network Controller ewa0.0.0.2002.0 00-06-2B-00-0A-48 PCI Hose 01 Bus 00 Slot 07: DEC PCI FDDI fwa0.0.0.7.1 08-00-2B-B9-0D-5D Bus 00 Slot 08: DEC PCI MC Rev: 22, mca0 Bus 00 Slot 09: DEC PCI MC Rev: 22, mcb0...

Page 91 - Example 4–3: Displaying Configuration on an AlphaServer 8200; Example 4–4: Displaying Devices on an AlphaServer 8200

Example 4–3 shows the output from the show config console command entered on an AlphaServer 8200 system. Example 4–3: Displaying Configuration on an AlphaServer 8200 >>> show config Name Type Rev Mnemonic TLSB 4++ KN7CC-AB 8014 0000 kn7cc-ab0 5+ MS7CC 5000 0000 ms7cc0 8+ KFTIA 2020 0000 kft...

Page 92 - Displaying Console Environment Variables and Setting the; show

Example 4–4: Displaying Devices on an AlphaServer 8200 (cont.) dkf4.0.0.1.1 DKF4 HSZ70 V70Z dkf5.0.0.1.1 DKF5 HSZ70 V70Z dkf6.0.0.1.1 DKF6 HSZ70 V70Z dkf100.1.0.1.1 DKF100 RZ28M 0568 dkf200.2.0.1.1 DKF200 RZ28M 0568 dkf300.3.0.1.1 DKF300 RZ28 442D polling for units on kzpsa0, slot 2, bus 0, hose1......

Page 95 - Use the; Example 4–7: Setting the KZPBA-CB SCSI Bus ID

4.3.3.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBson the shared SCSI bus, use the set console command to set the SCSI ID. For a TruCluster Server cluster, you will most likely have to set theSCSI ID for all KZPBA-CB UltraSCSI adapters except ...

Page 96 - Figure 4–1: KZPBA-CB Termination Resistors

Figure 4–1: KZPBA-CB Termination Resistors Internal Wide DeviceConnector J2 Internal Narrow DeviceConnector P2 SCSI Bus TerminationResistors RM1-RM8 ZK-1451U-AI JA1 4–18 TruCluster Server System Configuration Using UltraSCSI Hardware

Page 97 - See Section 2.2 for a discussion on Memory Channel restrictions.; Setting Up the Memory Channel Cluster Interconnect 5–1

5 Setting Up the Memory Channel Cluster Interconnect This chapter describes Memory Channel configuration restrictions, anddescribes how to set up the Memory Channel cluster interconnect, includingsetting up a Memory Channel hub, Memory Channel optical converter (MC2only), and connecting link cables....

Page 98 - Setting the Memory Channel Adapter Jumpers; Table 5–1: MC1 and MC1.5 Jumper Configuration; Standard; –2 Setting Up the Memory Channel Cluster Interconnect

____________________ Note _____________________ If you are installing SCSI or network adapters, you may wishto complete all hardware installation before powering up thesystems to run Memory Channel diagnostics. 5.1 Setting the Memory Channel Adapter Jumpers The meaning of the Memory Channel adapter ...

Page 99 - Table 5–2: MC2 Jumper Configuration; Standard: Pins 1 to 2; Setting Up the Memory Channel Cluster Interconnect 5–3

If you are upgrading from virtual hub mode to standard hub mode (or fromstandard hub mode to virtual hub mode), be sure to change the jumpers onall Memory Channel adapters on the rail. 5.1.2 MC2 Jumpers The MC2 module (CCMAB) has multiple jumpers. They are numbered rightto left, starting with J1 in ...

Page 100 - –4 Setting Up the Memory Channel Cluster Interconnect

Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: VH0: Pins 2 to 3 1 2 3 VH1: None needed;store the jumper onpin 1 or pin 3 1 2 3 J3: Window Size 512 MB: Pins 2 to 3 1 2 3 128 MB: Pins 1 to 2 1 2 3 J4: Page Size 8-KB page size (UNIX):Pins 1 to 2 1 2 3 4-KB page size (notused)...

Page 101 - Fiber Off: Pins 1 to 2; Table 5–3: MC2 Linecard Jumper Configurations; Fiber Off: Pins 2 to 3; Installing the Memory Channel Adapter; Setting Up the Memory Channel Cluster Interconnect 5–5

Table 5–2: MC2 Jumper Configuration (cont.) Jumper: Description: Example: J10 and J11: FiberOptics Mode Enable Fiber Off: Pins 1 to 2 3 2 1 Fiber On: Pins 2 to3 pins 3 2 1 a Increases the maximum sustainable bandwidth for 8x00 systems. If the jumpers are in this position forother systems, the bandwi...

Page 102 - Remove the bulkhead blanking plate for the desired PCI slot.; Installing the Memory Channel Hub; –6 Setting Up the Memory Channel Cluster Interconnect

If you are setting up a redundant Memory Channel configuration, install thesecond Memory Channel adapter right after installing the first MemoryChannel adapter. Ensure that the jumpers are correct and are the sameon both modules. After you install the Memory Channel adapter(s), replace the system pa...

Page 103 - Installing the Memory Channel Cables; Do not connect an MC1 or MC1.5 link cable to an MC2 module.; Setting Up the Memory Channel Cluster Interconnect 5–7

For use with the MC2 CCMAB adapter, the hub must be placed within4 or 10 meters (the length of the BN39B link cables) of each system. Iffiber optics is used in conjunction with the MC2 adapter, the hub may beplaced up to 31 meters from the systems. • Ensure that the voltage selection switch on the b...

Page 104 - in one; –8 Setting Up the Memory Channel Cluster Interconnect

5.5.1.1 Connecting MC1 or MC1.5 Link Cables in Virtual Hub Mode For an MC1 virtual hub configuration (two nodes in the cluster), connect theBC12N-10 link cables between the Memory Channel adapters installed ineach of the systems. _____________________ Caution _____________________ Be very careful wh...

Page 105 - Figure 5–1: Connecting Memory Channel Adapters to Hubs; Linecards; Setting Up the Memory Channel Cluster Interconnect 5–9

Figure 5–1: Connecting Memory Channel Adapters to Hubs Memory Channel hub 1 Memory Channel hub 2 System A MemoryChanneladapters Linecards ZK-1197U-AI 5.5.2 Installing the MC2 Cables To set up an MC2 interconnect, use the BN39B-04 (4-meter) or BN39B-10(10-meter) link cables for virtual hub or standar...

Page 106 - You cannot install a CCMLB linecard in slot; –10 Setting Up the Memory Channel Cluster Interconnect

Gently push the cable’s connector into the receptacle, and then use thescrews to pull the connector in tight. The connector must be tight to ensurea good ground contact. If you are setting up redundant interconnects, all Memory Channel adaptersin a system must have the same jumper setting, either VH...

Page 107 - Set the CCMLB linecard jumpers to support fiber optics; Fiber On; Running Memory Channel Diagnostics; Setting Up the Memory Channel Cluster Interconnect 5–11

Now you need to: • Set the CCMLB linecard jumpers to support fiber optics • Connect the fiber optics cable to a CCMFB fiber optics converter module • Install the CCMFB fiber optics converter module for each fiber optics link ______________________ Note _______________________ Remember, if you have m...

Page 108 - Caution; –12 Setting Up the Memory Channel Cluster Interconnect

There are two console level Memory Channel diagnostics, mc_diag and mc_cable : • The mc_diag diagnostic: – Tests the Memory Channel adapter(s) on the system running thediagnostic. – Runs as part of the initialization sequence when the system ispowered up. – Runs on a standalone system or while conne...

Page 109 - Setting Up the Memory Channel Cluster Interconnect 5–13

Example 5–1: Running the mc_cable Test >>> mc_cable 1 To exit MC_CABLE, type <Ctrl/C> mca0 node id 1 is online 2 No response from node 0 on mca0 2 mcb0 node id 1 is online 3 No response from node 0 on mcb0 3 Response from node 0 on mca0 4 Response from node 0 on mcb0 5 mcb0 is offline...

Page 111 - The information includes how to determine the; Using Fibre Channel Storage 6–1

6 Using Fibre Channel Storage This chapter provides an overview of Fibre Channel, Fibre Channelconfiguration examples, and information on Fibre Channel hardwareinstallation and configuration in a Tru64 UNIX or TruCluster Server Version5.0A configuration. The information includes how to determine the...

Page 112 - Procedure for Installation Using Fibre Channel Disks; wwidmgr; –2 Using Fibre Channel Storage

• A discussion on how you can use the emx manager ( emxmgr ) to display the presence of Fibre Channel adapters, target ID mappings for a FibreChannel adapter, and the current Fibre Channel topology (Section 6.12). 6.1 Procedure for Installation Using Fibre Channel Disks Use the following procedure t...

Page 113 - Using Fibre Channel Storage 6–3

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...

Page 114 - Wwidmgr User ’s Manual; Fibre Channel Overview; Support for multiple protocols; Frame; –4 Using Fibre Channel Storage

• 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 Cha...

Page 115 - Using Fibre Channel Storage 6–5

is manufactured. An N_Port is connected directlyto another N_Port in a point-to-point topology. AnN_Port is connected to an F_Port in a fabric topology. NL_Port In an arbitrated loop topology, information is routedaround a loop. The information is repeated by eachintermediate port until it reaches i...

Page 116 - –6 Using Fibre Channel Storage

• Arbitrated loop (Section 6.2.2.3) ______________________ Note _______________________ Although it is possible to interconnect an arbitrated loop withfabric, hybrid configurations are not supported at the presenttime, and therefore not discussed in this manual. 6.2.2.1 Point-to-Point The point-to-p...

Page 117 - Figure 6–2 shows an example fabric topology.; Figure 6–2: Fabric Topology; Figure 6–3 shows an example arbitrated loop topology.; Using Fibre Channel Storage 6–7

connected by the fabric switching function, which routes the frame from oneF_Port to another F_Port within the switch. Communication between twoswitches is routed between two expansion ports (E_Ports). When an N_Port is connected to an F_Port, the fabric is responsible for theassignment of the Fibre...

Page 118 - Figure 6–3: Arbitrated Loop Topology; Hub; Example Fibre Channel Configurations Supported by; Mode; With transparent failover mode:; –8 Using Fibre Channel Storage

Figure 6–3: Arbitrated Loop Topology NL_Port NL_Port Node 1 Node 2 NL_Port NL_Port Transmit Receive Transmit Receive Transmit Receive Transmit Receive Node 3 Node 4 Hub ZK-1535U-AI ______________________ Note _______________________ The arbitrated loop topology is not supported by the Tru64 UNIXor T...

Page 119 - The units are divided between an HSG80 port 1 and port 2.; DSGGA; Using Fibre Channel Storage 6–9

• The units are divided between an HSG80 port 1 and port 2. • If there are dual-redundant HSG80 controllers, controller A port 1 andcontroller B port 2 are normally active; controller A port 1 and controllerB port 1 are normally passive. • If one controller fails, the other controller takes control ...

Page 120 - SET; –10 Using Fibre Channel Storage

You can, however, add the hardware for a second bus (another KGPSA,switch, and RA8000/ESA12000 with associated cabling) and use LSM tomirror across the buses. However, because you cannot use LSM to mirrorthe cluster root ( / ) file system, member boot partitions, the quorum disk, or swap partitions ...

Page 121 - Figure 6–5: Multiple-Bus NSPOF Configuration Number 1

If you consider the loss of a host bus adapter or switch, the configurations inFigure 6–6 and Figure 6–7 will provide better throughput than Figure 6–5because you still have access to both controllers. With Figure 6–5, if you losea host bus adapter or switch, you lose the use of a controller. Figure...

Page 122 - Figure 6–6: Multiple-Bus NSPOF Configuration Number 2

Figure 6–6: Multiple-Bus NSPOF Configuration Number 2 KGPSA Member System 2 KGPSA KGPSA DSGGA DSGGA Member System 1 KGPSA ZK-1707U-AI RA8000/ ESA12000 HSG80 HSG80 HSG80 1 1 2 2 A B 6–12 Using Fibre Channel Storage

Page 123 - Figure 6–7: Multiple-Bus NSPOF Configuration Number 3; Zoning and Cascaded Switches; Using Fibre Channel Storage 6–13

Figure 6–7: Multiple-Bus NSPOF Configuration Number 3 KGPSA Member System 2 KGPSA KGPSA DSGGA DSGGA Member System 1 KGPSA ZK-1708U-AI RA8000/ ESA12000 HSG80 HSG80 HSG80 1 1 2 2 A B 6.4 Zoning and Cascaded Switches This section provides a brief overview of zoning and cascaded switches. 6.4.1 Zoning A...

Page 124 - Figure 6–8: A Simple Zoned Configuration; KGPSA; DSGGA SWITCH; –14 Using Fibre Channel Storage

Figure 6–8: A Simple Zoned Configuration KGPSA KGPSA RA8000/ ESA12000 HSG80 HSG80 RA8000/ ESA12000 HSG80 HSG80 KGPSA KGPSA DSGGA SWITCH Cluster 1MemberSystem 1 Cluster 1MemberSystem 2 Cluster 2MemberSystem 2 Cluster 2MemberSystem 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ZK-1709U-AI _________________...

Page 125 - Installing and Configuring Fibre Channel Hardware; Installing and Setting Up the Fibre Channel Switch; Remotely using a telnet TCP/IP connection; Using Fibre Channel Storage 6–15

6.5 Installing and Configuring Fibre Channel Hardware This section provides information about installing the Fibre Channelhardware needed for a TruCluster Server configuration accessing storageover the Fibre Channel. Ensure that the member systems, the Fibre Channel switches, and theHSG80 array cont...

Page 126 - Place the switch or install it in the rack.; –16 Using Fibre Channel Storage

you can manage the switch by way of a telnet session, SNMP, orthe Web. The DSGGA switch has slots to accommodate up to four (DS-DSGGA-AA) oreight (DS-DSGGA-AB) plug-in interface modules. Each interface module inturn supports two Giga Bit Interface Converter modules (GBIC). The GBICmodule is the elec...

Page 127 - The four front panel buttons are:; Using Fibre Channel Storage 6–17

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). Youcan also set the switch name if desired (see Section 6.5.1.2.5). Theswitch IP address and subnet mask must initially be set from the frontpanel, ...

Page 128 - Configuration Menu; –18 Using Fibre Channel Storage

Down — Downward triangle: Scrolls the menu down (which effectivelymoves up the list of commands) or decreases the value being displayed. ______________________ Note _______________________ When the up or down buttons are used to increase or decreasea numerical display, the number changes slowly at f...

Page 129 - Yes; Using Fibre Channel Storage 6–19

2. Press Enter to display the first submenu item in the configurationmenu, 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...

Page 130 - PC or Terminal; admin; ipAddrSet; Return; logout; –20 Using Fibre Channel Storage

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 mustuse a connection to a Windows 95/98/NT PC or video terminal to set theEthernet IP address and subnet mask. To set the Ethernet IP address...

Page 131 - Allows you to execute commands ending in; passwd; Using Fibre Channel Storage 6–21

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 cha...

Page 132 - User; Passwd; switchName fcsw1; Adapter Module

# 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 willinclude the switch name, for example: fcsw1:A...

Page 133 - set mode diag; wwid; Using Fibre Channel Storage 6–23

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 opticalshortwave multimode Fibre Channel interface. 3. Install the KGPSA in an open 32- or 64-bit PCI slot. 4. Insert ...

Page 134 - –24 Using Fibre Channel Storage

P00>>> boot warning -- main memory zone is not freeP00>>> init . . . P00>>> boot If you have initialized and booted the system, then shut down thesystem and try to use the wwidmgr utility, you may be prevented from doing so. If you receive the following error, initialize t...

Page 135 - Reformatting nvram; Using Fibre Channel Storage 6–25

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...

Page 136 - show dev; You can use the; emx; Setting up the HSG80 Array Controller for Tru64 UNIX; Install the fibre-optic cables between the KGPSA and the switch.; –26 Using Fibre Channel Storage

P00>>> show dev . . . pga0.0.0.1.0 PGA0 WWN 1000-0000-c920-eda0 pgb0.0.0.2.0 PGB0 WWN 1000-0000-c920-da01 • You can use the wwidmgr -show adapter command as follows: P00>>> wwidmgr -show adapter item adapter WWN Cur. Topo Next Topo [ 0] pga0.0.0.4.1 1000-0000-c920-eda0 FABRIC FABRI...

Page 137 - Install disks into storage shelves.; Using Fibre Channel Storage 6–27

____________________ Note _____________________ Do not use PVA ID 1: With Port-Target-LUN (PTL) addressing, the PVA ID is usedto determine the target ID of the devices on ports 1 through6 (the LUN is always zero). Valid target ID numbers are 0through 15, excluding numbers 4 through 7. Target IDs 6an...

Page 138 - show this; set nofailover; clear cli; –28 Using Fibre Channel Storage

____________________ 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 StorageW...

Page 139 - Example 6–1: Determine HSG80 Connection Names; Using Fibre Channel Storage 6–29

5 Takes the ports off line and resets the topology to prevent an errormessage 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 tothe KGPSA host bus adapters....

Page 140 - –30 Using Fibre Channel Storage

Example 6–1: Determine HSG80 Connection Names (cont.) HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER 1 offline 0 HOST_ID=1000-0000-C921-0943 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER 1 210413 OL other 0 HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=100...

Page 141 - SHOW; Using Fibre Channel Storage 6–31

your cluster member systems. If the operating system and offsets areincorrect, set them, then restart both controllers as follows: HSG80> set !NEWCON49 unit_offset = 0 1 HSG80> set !NEWCON49 operating_system = TRU64_UNIX 2 HSG80> restart other 3 HSG80> restart this 3 . . . HSG80> show...

Page 142 - –32 Using Fibre Channel Storage

• In a subsystem with two controllers in transparent failover mode, thecontroller 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...

Page 143 - Preparing to Install Tru64 UNIX and TruCluster Server; Using Fibre Channel Storage 6–33

– 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 labelcontaining the...

Page 144 - Example 6–2: Setting up the Mirrorset; –34 Using Fibre Channel Storage

• 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 Tru64UNIX disk (and of course any disks for applications). This documentassumes that both the base operating system and cluster software a...

Page 145 - Using Fibre Channel Storage 6–35

Example 6–2: Setting up the Mirrorset (cont.) Config - Normal Termination HSG80> ADD MIRRORSET BOOT-MIR DISK 30200 40000 2 HSG80> ADD MIRRORSET CROOT-MIR DISK 30300 40100 2 HSG80> INITIALIZE BOOT-MIR 3 HSG80> INITIALIZE CROOT-MIR 3 HSG80> SHOW BOOT-MIR 4 Name Storageset Uses Used by -...

Page 146 - –36 Using Fibre Channel Storage

Example 6–2: Setting up the Mirrorset (cont.) HSG80> HSG80> SHOW CROOT-MIR 11 Name Storageset Uses Used by ------------------------------------------------------------------------------ CROOT-MIR mirrorset DISK30300 DISK40100 Switches: POLICY (for replacement) = BEST_PERFORMANCE COPY (priority...

Page 147 - Using Fibre Channel Storage 6–37

Example 6–2: Setting up the Mirrorset (cont.) HSG80> set d144 ENABLE_ACCESS_PATH = !NEWCON53,!NEWCON54,!NEWCON55,!NEWCON56 Warning 1000: Other host(s) in addition to the one(s) specified can still access this unit. If you wish to enable ONLY the host(s) specified, disable all access paths (DISABL...

Page 148 - –38 Using Fibre Channel Storage

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 di...

Page 149 - ADD UNIT; Using Fibre Channel Storage 6–39

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...

Page 150 - dsk; Table 6–2: Converting Storageset Unit Numbers to Disk Names; Worldwide Name; Quorum disk; –40 Using Fibre Channel Storage

that at this point, even though the table is filled in, we do not yet knowthe device names or dsk n numbers. Table 6–2: Converting Storageset Unit Numbers to Disk Names File Systemor Disk HSG80Unit Worldwide Name UserDefineIdentifier(UDID) Device Name dsk n Member 1 bootdisk D131 6000-1FE1-0000-0D60...

Page 151 - Using Fibre Channel Storage 6–41

disk is unit D133 with a UDID 133. The UDID for the cluster member 1boot 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 st...

Page 152 - –42 Using Fibre Channel Storage

[16] UDID:144 WWID:01000010:6000-1fe1-0000-0d60-0009-8080-0434-0028 (ev:none) [17] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002b (ev:none)[18] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002c (ev:none) [19] UDID:-1 WWID:01000010:6000-1fe1-0000-0ca0-0009-8090-0708-002d (e...

Page 153 - connected; Using Fibre Channel Storage 6–43

132 (cluster member 2). The device unit number is an alias for theworldwide 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 thro...

Page 154 - The; –44 Using Fibre Channel Storage

Example 6–3: Using the wwidmgr quickset Command to Set Device UnitNumber (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: via fc ...

Page 155 - Example 6–4: Sample Fibre Channel Device Names; Using Fibre Channel Storage 6–45

The disks are not reachable and you cannot boot until after thesystem is initialized. Note, that in the reachability portion of the display, the storagesets arereachable from KGPSA dga through two HSG80 ports and from KGPSA dgb through two HSG80 ports. Also note, that the device unit numbers, theali...

Page 156 - –46 Using Fibre Channel Storage

Example 6–4: Sample Fibre Channel Device Names (cont.) dgb132.1001.0.2.0 $1$DGA132 HSG80 V8.5F dgb132.1002.0.2.0 $1$DGA132 HSG80 V8.5F dgb132.1003.0.2.0 $1$DGA132 HSG80 V8.5F dgb132.1004.0.2.0 $1$DGA132 HSG80 V8.5F dgb133.1001.0.2.0 $1$DGA133 HSG80 V8.5F dgb133.1002.0.2.0 $1$DGA133 HSG80 V8.5F dgb13...

Page 157 - Using Fibre Channel Storage 6–47

• 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 clustermember, you r...

Page 158 - genvmunix; Install the Base Operating System; If that disk has a visible indicator light, it will; –48 Using Fibre Channel Storage

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 ...

Page 159 - Using Fibre Channel Storage 6–49

Device Size Controller Disk Name in GB Type Model Location 1) dsk0 4.0 SCSI RZ2CA-LA bus-0-targ-0-lun-0 2) dsk15 1.0 SCSI HSG80 IDENTIFIER=133 3) dsk16 1.0 SCSI HSG80 IDENTIFIER=132 4) dsk17 2.0 SCSI HSG80 IDENTIFIER=131 If you flash the light on a storage unit (logical disk) that is a mirrorset,str...

Page 160 - reachability

For example, to ensure that you have a connected boot pathin case of a failed host bus adapter or controller failover,choose device names for multiple host bus adapters and eachcontroller port. For example, if you use the reachabilitydisplay shown in Example 6–3, you could choose thefollowing device...

Page 161 - Installation; hwmgr; Using Fibre Channel Storage 6–51

• 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 guaranteesthat you can set th...

Page 162 - more; –52 Using Fibre Channel Storage

# 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 particulardisk in question. The following example shows the format ofthe command output: # hwmgr -get attribute -a name -a dev_base_name 1...

Page 163 - Installing the TruCluster Server Software; Quorum; Using Fibre Channel Storage 6–53

6.10 Installing the TruCluster Server Software This section covers the Fibre Channel specific procedures you need toexecute 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...

Page 164 - Changing the HSG80 from Transparent to Multiple-Bus; –54 Using Fibre Channel Storage

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.10...

Page 165 - Using Fibre Channel Storage 6–55

Each path between a Fibre Channel host bus adapter in a host computerand an active host port on an HSG80 controller is a connection. DuringFibre Channel initialization, when a controller becomes aware of aconnection to a host bus adapter through a switch, it adds the connectionto its table of known ...

Page 166 - SET NOFAILOVER; Execute the; –56 Using Fibre Channel Storage

2. At the HSG80, set multiple-bus failover as follows. Note that beforeputting the controllers in multiple-bus failover mode, you must removeany previous failover mode: HSG80> SET NOFAILOVER HSG80> SET MULTIBUS_FAILOVER COPY=THIS ____________________ Note _____________________ Use the controll...

Page 167 - Console is in diagnostic mode; Using Fibre Channel Storage 6–57

!NEWCON62 TRU64_UNIX OTHER 1 210513 OL other 0 HOST_ID=1000-0000-C921-086C ADAPTER_ID=1000-0000-C921-086C !NEWCON63 TRU64_UNIX OTHER 1 offline 0 HOST_ID=1000-0000-C921-0943 ADAPTER_ID=1000-0000-C921-0943 !NEWCON64 TRU64_UNIX OTHER 1 210413 OL other 0 HOST_ID=1000-0000-C920-EDA0 ADAPTER_ID=1000-0000-...

Page 168 - –58 Using Fibre Channel Storage

P00>>> b. For each wwid n line, record the unit number (131, 132, and 133) and worldwide name for the storage unit. The unit number is thefirst field in the display (after wwid n ). The N n value is the HSG80 port being used to access the storage units (controller B, port 2). c. Clear the w...

Page 169 - Using the emxmgr Utility to Display Fibre Channel Adapter; emx0 SCSI target id assignments:; Using Fibre Channel Storage 6–59

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 theHSG80. 6.12 Using the emx Manager to Display Fibre Channel Adapter Information The emx manager ( emxmgr ) utility was written for the TruCluster Software ...

Page 170 - emx1 state information:; Status of the; –60 Using Fibre Channel Storage

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 emx1 s...

Page 171 - Using the emxmgr Utility Interactively; emxmgr; Using Fibre Channel Storage 6–61

worldwide name) are provided. The Fibre Channel DID number is thephysical Fibre Channel address being used by the N_Port. 2 A list of all other Fibre Channel devices on this SCSI bus, with theirSCSI ID, port name, node name, physical Fibre Channel address andother items such as: • Present — The adap...

Page 173 - Using Fibre Channel Storage 6–63

2. View adapter’s Target Id Mappings 3. Change Target ID Mappings d. Display Attached Adapters a. Change targeted adapter x. Exit ----> x # Using Fibre Channel Storage 6–63

Page 175 - Preparing ATM Adapters; Preparing ATM Adapters 7–1

7 Preparing ATM Adapters The Compaq Tru64 UNIX operating system supports Asynchronous TransferMode (ATM). TruCluster Server supports the use of LAN emulation overATM for client access. This chapter provides an ATM overview, an example TruCluster Servercluster using ATM, an ATM adapter installation p...

Page 176 - –2 Preparing ATM Adapters

Most data traffic in existing customer networks is sent over Local AreaNetworks (LANs) such as Ethernet or Token Ring networks. The servicesprovided by the LANs differ from those of ATM, for example: • LAN messages are connectionless; ATM is a connection-orientedtechnology • Because a LAN is based o...

Page 177 - Figure 7–1: Emulated LAN Over an ATM Network; Installing ATM Adapters; Warning; Preparing ATM Adapters 7–3

– Broadcast and Unknown Server (BUS): A BUS handles broadcastdata sent by a LAN emulation client, all multicast data, and data sentby 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 Bare LECs on ELAN1. Hosts C, D, a...

Page 178 - To verify that the cables are connected correctly, see Section 7.3.; Verifying ATM Fiber Optic Cable Connectivity; –4 Preparing ATM Adapters

Use the following steps to install an ATMworks adapter. See the ATMworks350 Adapter Installation and Service guide for more information. Be sureto use the antistatic ground strap. 1. Remove the adapter extender bracket if the ATMworks 350 is to beinstalled in an AlphaServer 2100 system. 2. Remove th...

Page 180 - ATMworks Adapter LEDs; Table 7–1: ATMworks Adapter LEDs; Network LED

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 andrecheck the indicators. 6. If you still do not have a correct cable connection, you probably have abad cable. 7.4 ATMworks Adapter LEDs The ATMworks adapte...

Page 181 - Preparing the TZ88 for Shared Bus Usage; Configuring a Shared SCSI Bus for Tape Drive Use 8–1

8 Configuring a Shared SCSI Bus for Tape Drive Use The topics in this section provide information on preparing the various tapedevices for use on a shared SCSI bus with the TruCluster Server product. ______________________ Notes ______________________ Section 8.6 and Section 8.7 provide documentatio...

Page 182 - –2 Configuring a Shared SCSI Bus for Tape Drive Use

8.1.1 Setting the TZ88N-VA SCSI ID You must set the TZ88N-VA switches before the tape drive is installed intothe BA350 StorageWorks enclosure. The Automatic selection is normallyused. The TZ88N-VA takes up three backplane slot positions. The physicalconnection is in the lower of the three slots. For...

Page 183 - Configuring a Shared SCSI Bus for Tape Drive Use 8–3

Table 8–1: TZ88N-VA Switch Settings SCSI ID SCSI ID Selection Switches 1 2 3 4 5 6 Automatic a Off Off Off On On On 0 Off Off Off Off Off Off 1 On Off Off Off Off Off 2 Off On Off Off Off Off 3 On On Off Off Off Off 4 Off Off On Off Off Off 5 On Off On Off Off Off 6 Off On On Off Off Off 7 On On On ...

Page 184 - Figure 8–2: Shared SCSI Buses with SBB Tape Drives; –4 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–2: Shared SCSI Buses with SBB Tape Drives 1 2 4 5 D W Z Z B - V W , t r i l i n k c o n n e c t o r ,a n d H 8 7 9 t e r m i n a t o r D W Z Z A - V A ,t r i l i n k , a n d H 8 7 9 t e r m i n a t o r D W Z Z A - V Aa n d t r i l i n k A l p h a S e r v e r 2 1 0 0 A T B A 3 5 0 A l p h a ...

Page 185 - Preparing the TZ89 for Shared SCSI Usage; Configuring a Shared SCSI Bus for Tape Drive Use 8–5

Ensure that DWZZA jumper J2 or DWZZB jumpers W1 and W2 areinstalled to enable the single-ended termination. Remove the termination from the differential end by removing the five14-pin SIP resistors. 2. Attach a trilink connector to the differential end of the DWZZA orDWZZB. 3. Connect the single-end...

Page 187 - Configuring a Shared SCSI Bus for Tape Drive Use 8–7

Table 8–2: DS-TZ89N-VW Switch Settings (cont.) SCSI ID SCSI ID Selection Switches 2 Off On Off Off Off Off Off Off 3 On On Off Off Off Off Off Off 4 Off Off On Off Off Off Off Off 5 On Off On Off Off Off Off Off 6 Off On On Off Off Off Off Off 7 On On On Off Off Off Off Off 8 Off Off Off On Off Off ...

Page 188 - Attach a trilink connector to the differential end of the DWZZB-AA.; –8 Configuring a Shared SCSI Bus for Tape Drive Use

8.2.3 Setting the DS-TZ89N-TA SCSI ID The DS-TZ89N-TA has a push-button counter switch on the rear panel toselect the SCSI ID. It is preset at the factory to 15. Push the button abovethe counter to increment the SCSI ID (the maximum is 15); push the buttonbelow the switch to decrease the SCSI ID. 8....

Page 189 - Configuring a Shared SCSI Bus for Tape Drive Use 8–9

8.3 Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is a Digital Linear Tape (DLT)tabletop cartridge tape drive capable of holding up to 40 GB of dataper Compactape IV cartridge using 2:1 compression. It is capable ofstoring/retrieving data at a rate of up to 10.8 GB per hour (usin...

Page 190 - Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel; –10 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–4: Compaq 20/40 GB DLT Tape Drive Rear Panel + - 0 20/40 GB DLT Tape Drive S C S I I DS e l e c t o rS w i t c h S C S I I D + - 0 ZK-1603U-AI 8.3.2 Cabling the Compaq 20/40 GB DLT Tape Drive The Compaq 20/40 GB DLT Tape Drive is connected to a single-endedsegment of the shared SCSI bus. A ...

Page 191 - Configuring a Shared SCSI Bus for Tape Drive Use 8–11

cable). Ensure that the trilink or Y cable at both ends of the differentialsegment of the shared SCSI bus is terminated with an HD68 differentialterminator such as an H879-AA. The single-ended SCSI bus may be daisy chained from one single-endedtape drive to another with cable part number 146745-003 ...

Page 192 - Callout Number; –12 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–5: Cabling a Shared SCSI Bus with a Compaq 20/40 GB DLT TapeDrive KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 10 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T ...

Page 193 - Preparing the TZ885 for Shared SCSI Usage; SCSI ID SEL; Press the Display Mode push button again.; Configuring a Shared SCSI Bus for Tape Drive Use 8–13

Table 8–3: Hardware Components Used to Create the Configuration Shownin 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 ma...

Page 194 - You will need one DWZZA-AA or DWZZB-AA for each TZ885 tape drive.; –14 Configuring a Shared SCSI Bus for Tape Drive Use

for use on a shared SCSI bus. The TZ885 in this figure has had the SCSIID 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 areinst...

Page 195 - Figure 8–6: Cabling a Shared SCSI Bus with a TZ885; Preparing the TZ887 for Shared SCSI Bus Usage; Configuring a Shared SCSI Bus for Tape Drive Use 8–15

Figure 8–6: Cabling a Shared SCSI Bus with a TZ885 D W Z Z A - V A , t r i l i n k c o n n e c t o r ,a n d H 8 7 9 t e r m i n a t o r D W Z Z A - V Aa n d t r i l i n k c o n n e c t o r T r i l i n kc o n n e c t o ra n dH 8 7 9 - A At e r m i n a t o r A l p h a S e r v e r 2 1 0 0 A T B A 3 5 0...

Page 196 - Figure 8–7: TZ887 DLT MiniLibrary Rear Panel; –16 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–7: TZ887 DLT MiniLibrary Rear Panel + - 0 T Z 8 8 7 Z K - 1 4 6 1 U - A I S C S I I D S C S I I DS e l e c t o rS w i t c h + - 0 8.5.2 Cabling the TZ887 Tape Drive The TZ887 is connected to a single-ended segment of the shared SCSIbus. It is connected to a differential portion of the share...

Page 197 - Configuring a Shared SCSI Bus for Tape Drive Use 8–17

The single-ended SCSI bus may be daisy chained from one single-endedtape drive to another with BC19J cables, as long as the SCSI bus maximumlength is not exceeded and there are sufficient SCSI IDs available. Ensurethat the tape drive on the end of the bus is terminated with an H8574-A orH8890-AA ter...

Page 198 - DLT0 Idle; –18 Configuring a Shared SCSI Bus for Tape Drive Use

8.6 Preparing the TL891 and TL892 DLT MiniLibraries for Shared SCSI Usage ______________________ Note _______________________ To achieve system performance capabilities, we recommendplacing no more than two TZ89 drives on a SCSI bus, and alsorecommend that no shared storage be placed on the same SCS...

Page 199 - Configuring a Shared SCSI Bus for Tape Drive Use 8–19

The first and second lines of the default screen show the status of the twodrives (if present). The third line shows the status of the library robotics,and the fourth line is a map of the magazine, with the numbers from 0 to9 representing the cartridge slots. Rectangles present on this line indicate...

Page 200 - Repeat steps 4 and 5 to set other SCSI bus IDs as necessary.; –20 Configuring a Shared SCSI Bus for Tape Drive Use

4. Select the tape drive (DLT0 Bus ID: or DLT1 Bus ID:) or library robotics(LIB Bus ID:) for which you wish to change the SCSI bus ID. The defaultSCSI IDs are as follows: • Lib Bus ID: 0 • DLT0 Bus ID: 4 • DLT1 Bus ID: 5 Use the up or down arrow button to select the item for which you needto change ...

Page 201 - Configuring a Shared SCSI Bus for Tape Drive Use 8–21

SCSI bus without stopping all ASE services that generate activityon the bus. For this reason, we recommend that tape devices be placed onseparate shared SCSI buses, and that there be no storage deviceson the SCSI bus. The cabling depends on whether or not there are one or two drives, and forthe two-...

Page 202 - –22 Configuring a Shared SCSI Bus for Tape Drive Use

To connect the drive robotics and one drive to one shared SCSI bus and thesecond drive to a second shared SCSI bus, follow these steps: 1. Connect a BN21K or BN21L between the last trilink connector on oneshared SCSI bus to the leftmost connector (as viewed from the rear) ofthe TL892. 2. Connect a B...

Page 203 - Preparing the TL890 DLT MiniLibrary Expansion Unit; Configuring a Shared SCSI Bus for Tape Drive Use 8–23

Figure 8–9: TruCluster Server Cluster with a TL892 on Two Shared SCSIBuses D W Z Z A - V A , t r i l i n k c o n n e c t o r ,a n d H 8 7 9 t e r m i n a t o r D W Z Z A - V A , t r i l i n k c o n n e c t o r ,a n d H 8 7 9 t e r m i n a t o r L i b r a r yR o b o t i c s H 8 7 9 - A At e r m i n a...

Page 204 - –24 Configuring a Shared SCSI Bus for Tape Drive Use

8.7.1 TL890 DLT MiniLibrary Expansion Unit Hardware The TL890 expansion unit is installed above the TL891/TL892 DLTMiniLibrary base units in a SW500, SW800, or RETMA cabinet. Theexpansion unit integrates the robotics in the individual modules into asingle, coordinated library robotics system. The TL...

Page 205 - Configuring a Shared SCSI Bus for Tape Drive Use 8–25

• 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 femaleconnector on the other end. Connect the male end to the ExpansionUnit Interface connector on the base module and the female end to anyExpansion Modules connector ...

Page 206 - Figure 8–10: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses; A l p h a S e r v e r 2 1 0 0 A s; –26 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–10: TL890 and TL892 DLT MiniLibraries on Shared SCSI Buses T L 8 9 2 T L 8 9 2 T L 8 9 0 L i b r a r y R o b o t i c s D L T 1 E x p a n s i o n M o d u l e s R o b o t i c s C o n t r o l c a b l e s D i a g D L T 2 L i b r a r y R o b o t i c s D L T 1 D L T 2 H 8 7 9 - A At e r m i n a t...

Page 207 - Loader Idle; Configuring a Shared SCSI Bus for Tape Drive Use 8–27

unit will not have control over the base module robotics when you power upthe 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 DLTMiniLibrary expansion unit, perform the following procedure on each basemodule i...

Page 208 - Expansion unit: 0 through 15; DLT2 Idle; –28 Configuring a Shared SCSI Bus for Tape Drive Use

7. After the selection stops flashing and the control panel indicates thatthe change is not effective until a reboot, press the Enter button. 8. When the Special Configuration menu reappears, turn the power switchoff and then on to cycle the power. The base module is now reconfiguredas a slave to th...

Page 209 - Configuring a Shared SCSI Bus for Tape Drive Use 8–29

control functions are carried out from the expansion unit control panel. Thisincludes setting the SCSI ID for each of the tape drives present. To set the SCSI IDs for the tape drives in a MiniLibrary configured withTL890/TL891/TL892 hardware, follow these steps: 1. Apply power to the MiniLibrary, en...

Page 210 - until the Default window is displayed.; Preparing the TL894 DLT Automated Tape Library for; TL894 Robotic Controller Required Firmware; Table 8–4: TL894 Default SCSI ID Settings; SCSI Device; Robotics Controller; –30 Configuring a Shared SCSI Bus for Tape Drive Use

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 beconfigured. 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 De...

Page 211 - Tape Drive 2; Press and release SELECT to enter the menu mode.; Configuring a Shared SCSI Bus for Tape Drive Use 8–31

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 thatthe SDA (Status Display Area) shows System Off-line....

Page 212 - –32 Configuring a Shared SCSI Bus for Tape Drive Use

12. Press and release the up or down button and the SELECT button simultaneously, and verify that System On-line or System Off-line isdisplayed in the SDA. To set the SCSI ID for each tape drive if the desired SCSI IDs are differentfrom those shown in Table 8–4, follow these steps: 1. Press and rele...

Page 213 - Press and release the up or down button and the SELECT button; TL894 Tape Library Internal Cabling; Figure 8–11: TL894 Tape Library Four-Bus Configuration; Configuring a Shared SCSI Bus for Tape Drive Use 8–33

14. Press and release the up or down button and the SELECT button simultaneously and verify that System On-line or System Off-lineis displayed in the SDA. 8.8.3 TL894 Tape Library Internal Cabling The default internal cabling configuration for the TL894 tape library has therobotics controller and to...

Page 214 - Connecting the TL894 Tape Library to the Shared SCSI Bus; –34 Configuring a Shared SCSI Bus for Tape Drive Use

other drive to be daisy chained. Use the SCSI jumper cable to connect thetwo drives and place them on the same SCSI bus. ______________________ Notes ______________________ We recommend that you not place more than two TZ89 tapedrives on any one SCSI bus in these tape libraries. We alsorecommend tha...

Page 215 - Figure 8–12: Shared SCSI Buses with TL894 in Two-Bus Mode; Configuring a Shared SCSI Bus for Tape Drive Use 8–35

Figure 8–12 shows a sample TruCluster Server cluster using a TL894 tapelibrary. In the sample configuration, the tape library has been connected inthe two-bus mode by jumpering tape drive 0 to tape drive 1 and tape drive2 to tape drive 3 (See Section 8.8.3 and Figure 8–11). The two SCSI busesare lef...

Page 216 - –36 Configuring a Shared SCSI Bus for Tape Drive Use

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 DigitalLinear Tape (DLT) automated tape library for use on a shared SCSI bus. ______________________ Note _______________________ To achieve system perfo...

Page 217 - Table 8–5: TL895 Default SCSI ID Settings; At the control panel, press the Operator tab.; Configuring a Shared SCSI Bus for Tape Drive Use 8–37

8.9.1 TL895 Robotic Controller Required Firmware Robotic firmware version N2.20 is the minimum firmware revision supportedin a TruCluster Server cluster. For information on upgrading the roboticfirmware, see the Flash Download section of the TL895 DLT Tape LibraryDiagnostic Software User ’s Manual. ...

Page 218 - TL895 Tape Library Internal Cabling; –38 Configuring a Shared SCSI Bus for Tape Drive Use

4. To change any of the configurations, press the Configure button. 5. Press the Select button until the item you wish to configure ishighlighted. For the devices, select the desired device (library or drive)by scrolling through the devices with the arrow buttons. After thelibrary or selected drive ...

Page 219 - Figure 8–13: TL895 Tape Library Internal Cabling; Configuring a Shared SCSI Bus for Tape Drive Use 8–39

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 aterminator installed. 4. Inst...

Page 220 - Connecting the TL895 Tape Library to the Shared SCSI Bus; Libraries for Shared SCSI Bus Usage; –40 Configuring a Shared SCSI Bus for Tape Drive Use

8.9.4 Upgrading a TL895 The TL985 DLT automated tape library can be upgraded from two orfive tape drives to seven drives with multiple DS-TL89X-UA upgradekits. Besides the associated documentation, the upgrade kit contains oneTZ89N-AV tape drive, a SCSI bus terminator, a SCSI bus jumper (partnumber ...

Page 221 - The tape library specifications are as follows:; Configuring a Shared SCSI Bus for Tape Drive Use 8–41

______________________ Note _______________________ To achieve system performance capabilities, We recommendplacing no more than two TZ89 drives on a SCSI bus. The TL893 and TL896 Automated Tape Libraries (ATLs) are designed toprovide high-capacity storage and robotic access for the Digital Linear T...

Page 222 - Communications with the Host Computer; Switch 7 on the MUC switch pack must be down to select the SCSI bus.; –42 Configuring a Shared SCSI Bus for Tape Drive Use

on adding additional cabinets. Up to five cabinets are supported with theTruCluster Server. For TruCluster Server, the tape cartridges in all the cabinets are combinedinto one logical unit, with consecutive numbering from the first cabinet tothe last cabinet, by an upgrade from the multi-unit, multi...

Page 223 - Table 8–6: MUC Switch Functions; Switch; Table 8–7: MUC SCSI ID Selection; MUC SCSI ID; Configuring a Shared SCSI Bus for Tape Drive Use 8–43

Table 8–6: MUC Switch Functions Switch Function 1, 2, and 3 MUC SCSI ID if Switch 7 is down a 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 serial a 8 Must be down, reserved for testing a For a TruCluster Server clus...

Page 225 - Figure 8–14: TL893 Three-Bus Configuration; Configuring a Shared SCSI Bus for Tape Drive Use 8–45

– The bottom shelf tape drive (SCSI ID 3) is on SCSI Port A and isalso terminated on the drive with a 68-pin Micro-D terminator, partnumber 0415619. Figure 8–14: TL893 Three-Bus Configuration MUC SCSI Address 2 SCSI Port A SCSI Port B SCSI Port C TZ89 Tape DriveSCSI Address 5 (top shelf) TZ89 Tape D...

Page 226 - –46 Configuring a Shared SCSI Bus for Tape Drive Use

– The lower bay top shelf tape drive (tape drive 2, SCSI ID 5) is onSCSI Port A and is terminated on the tape drive. – The lower bay middle shelf tape drive (tape drive 1, SCSI ID 4) is onSCSI Port B and is terminated on the tape drive. – The lower bay bottom shelf tape drive (tape drive 0, SCSI ID ...

Page 227 - the Shared SCSI Bus; Configuring a Shared SCSI Bus for Tape Drive Use 8–47

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 3meters of internal SCSI cabling on each SCSI bus. Because of the internalSCSI cable lengths, it is not possible to use a trilink connector or Y cable ...

Page 228 - Figure 8–16: Shared SCSI Buses with TL896 in Three-Bus Mode; Shared Bus Usage; TL881 MiniLibrary System User ’s Guide; –48 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–16: Shared SCSI Buses with TL896 in Three-Bus Mode KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 7 KZPBA-CB (ID 6) T T Network T N O T E...

Page 229 - Configuring a Shared SCSI Bus for Tape Drive Use 8–49

• 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 offeredas standalone tabletop units or as expandable rackmount units. The following sections des...

Page 230 - The expansion unit works with either the TL881 or TL891 base unit.; The data unit works with either the TL881 or TL891 base unit.; –50 Configuring a Shared SCSI Bus for Tape Drive Use

device and only works as a slave to the expansion unit. To create amultimodule rackmount system, there must be one expansion unit andat least one base unit. The expansion unit has to be the top modulein the configuration. The expansion unit works with either the TL881 or TL891 base unit. • TL881 or ...

Page 231 - Table 8–11: DLT MiniLibrary Part Numbers; DLT Library Component

TL881 or TL891 MiniLibrary in configurations set up for either maximumperformance or maximum capacity. Table 8–10: TL881 and TL891 MiniLibrary Performance and Capacity Comparison TL881 MiniLibrary TL891 MiniLibrary ConfiguredforMaximum: Number ofBase Units a b Number ofData Units c TransferRate d St...

Page 232 - Use; Bus Usage; –52 Configuring a Shared SCSI Bus for Tape Drive Use

Table 8–11: DLT MiniLibrary Part Numbers (cont.) DLT Library Component Number of TapeDrives Tabletop/Rackmount Part Number TL891 DLT MiniLibraryBase Unit 1 Rackmount 120876-B21 TL891 DLT MiniLibraryBase Unit 2 Rackmount 120876-B22 Add-on DLT 35/70 drivefor TL891 1 N/A 120878-B21 MiniLibrary Expansio...

Page 233 - Configuring a Shared SCSI Bus for Tape Drive Use 8–53

The topics in this section provide information on preparing the TL881 orTL891 DLT MiniLibrary tabletop model or rackmount base unit for useon a shared SCSI bus. For complete hardware installation instructions, see the TL881 MiniLibrarySystem User ’s Guide or TL891 MiniLibrary System User ’s Guide. 8...

Page 234 - –54 Configuring a Shared SCSI Bus for Tape Drive Use

____________________ Note _____________________ When you enter the Menu Mode, the Ready light goes out,an indication that the module is off line, and all mediumchanger commands from the host return a SCSI "not ready"status until you exit the Menu Mode and the Ready lightcomes on once again. ...

Page 235 - Configuring a Shared SCSI Bus for Tape Drive Use 8–55

______________________ Note _______________________ The tape drive SCSI connectors are labeled DLT1 (tape drive 1)and DLT2 (tape drive 2). The control panel designation for thedrives is DLT0 (tape drive 1) and DLT1 (tape drive 2). The default for the TL881 or TL891 DLT MiniLibrary is to place the ro...

Page 236 - –56 Configuring a Shared SCSI Bus for Tape Drive Use

3. Install an HD68 differential terminator (such as an H879-AA) on theright DLT1 connector (the fourth connector from the left). To connect the drive robotics and two drives to a single shared SCSI bus,follow these steps: 1. Connect a 328215-00X, BN21K, or BN21L between the last trilinkconnector on ...

Page 237 - Figure 8–17: TL891 Standalone Cluster Configuration; Configuring a Shared SCSI Bus for Tape Drive Use 8–57

Figure 8–17: TL891 Standalone Cluster Configuration KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 KZ...

Page 238 - –58 Configuring a Shared SCSI Bus for Tape Drive Use

Table 8–12: Hardware Components Used to Create the ConfigurationShown in Figure 8–17 (cont.) Callout Number Description 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The maximum length of the BN38C (or BN38D) cable on one SCSI bus segment must not exceed 25 meters. b The maximum lengt...

Page 239 - Configuring a Shared SCSI Bus for Tape Drive Use 8–59

connector on the data unit and the female end to any Expansion Modulesconnector on the expansion unit. _____________________ Note _____________________ It does not matter which interface connector a base unit ordata unit is connected to. • SCSI bus connection to the expansion unit robotics: Connect ...

Page 240 - Figure 8–18: TL881 DLT MiniLibrary Rackmount Configuration; –60 Configuring a Shared SCSI Bus for Tape Drive Use

Figure 8–18: TL881 DLT MiniLibrary Rackmount Configuration KZPBA-CB (ID 7) MemoryChannelInterface Memory Channel KZPBA-CB (ID 6) Member System 1 D S - D W Z Z H - 0 3 T T T 2 1 4 1 3 StorageWorks RAID Array 7000 HSZ70 HSZ70 Controller B Controller A T KZPBA-CB (ID 7) 5 5 6 7 7 KZPBA-CB (ID 6) T T Ne...

Page 241 - Configuring a Shared SCSI Bus for Tape Drive Use 8–61

Table 8–13: Hardware Components Used to Create the ConfigurationShown in Figure 8–18 Callout Number Description 1 BN38C or BN38D cable a 2 BN37A cable b 3 H8861-AA VHDCI trilink connector 4 H8863-AA VHDCI terminator 5 BN21W-0B Y cable 6 H879-AA terminator 7 328215-00X, BN21K, or BN21L cable c a The ...

Page 242 - –62 Configuring a Shared SCSI Bus for Tape Drive Use

DLT0 Idle DLT1 IdleLoader Idle 0> _ _ _ _ _ _ _ _ _ _ <9 The default screen shows the state of the tape drives, loader, andnumber of cartridges present for this base unit. A rectangle in place ofthe underscore indicates that a cartridge is present in that location. 2. Press the Enter button to...

Page 243 - Configuring a Shared SCSI Bus for Tape Drive Use 8–63

When the expansion unit comes up, it will communicate with each base anddata unit through the expansion unit interface and inventory the numberof base units, tape drives, data units, and cartridges present in each baseand data unit. After the MiniLibrary configuration has been determined, theexpansi...

Page 244 - You do not have to cycle power to set the SCSI IDs.; –64 Configuring a Shared SCSI Bus for Tape Drive Use

• DLT3 Bus ID: 4 • DLT4 Bus ID: 5 • DLT5 Bus ID: 6 7. Press Enter when you have the item selected for which you wish tochange the SCSI ID. 8. Use the up and down arrows to select the desired SCSI ID. Press theEnter button to save the new selection. 9. Press the Escape button once to return to the Se...

Page 245 - Order Number; Preparing the ESL9326D Enterprise Library for Shared SCSI; Configuring a Shared SCSI Bus for Tape Drive Use 8–65

______________________ Note _______________________ These tape devices have been qualified for use on shared SCSIbuses with both the KZPSA-BB and KZPBA-CB host busadapters. 8.12.2 ESL9326D Enterprise Library Overview The ESL9326D Enterprise Library is an enterprise Digital Linear Tape(DLT) automated...

Page 246 - The 35/70 DLT tape drives require V80 or later firmware.; –66 Configuring a Shared SCSI Bus for Tape Drive Use

______________________ Notes ______________________ The ESL9326D Enterprise Library is cabled internally for two35/70 DLT tape drives on each SCSI bus. It arrives with thelibrary electronics cabled to tape drives 0 and 1. Every otherpair of tape drives is cabled together (2 and 3, 4 and 5, 6 and7, a...

Page 247 - Configuring a Shared SCSI Bus for Tape Drive Use 8–67

Figure 8–19: ESL9326D Internal Cabling T Tape Drive 0 Tape Drive 1 Tape Drive 2 Tape Drive 3 Tape Drive 4 Tape Drive 5 Tape Drive 6 Tape Drive 7 Tape Drive 8 Tape Drive 9 Tape Drive 10 Tape Drive 11 Tape Drive 12 Tape Drive 13 Tape Drive 14 Tape Drive 15 Robotics T T T T T T T A B C D E F G H P O N ...

Page 248 - –68 Configuring a Shared SCSI Bus for Tape Drive Use

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 cablingfor each pair of tape drives. Because of the internal SCSI bus lengths, itis not possible to use a trilink connector or Y cable to terminate the SCSIbus...

Page 249 - Configuring a Shared SCSI Bus for Tape Drive Use 8–69

______________________ Notes ______________________ Each ESL9326D Enterprise Library arrives with one 330563-001HD68 terminator for each pair of tape drives (one SCSI bus). Thekit also includes at least one 330582-001 jumper cable to connectthe library electronics to tape drives 0 and 1. Tape librar...

Page 251 - Externally terminated TruCluster Server configurations; Non-UltraSCSI Devices 9–1

9 Configurations Using External Termination or Radial Connections to Non-UltraSCSI Devices This chapter describes the requirements for the shared SCSI bus using: • Externally terminated TruCluster Server configurations • Radial configurations with non-UltraSCSI RAID array controllers In addition to ...

Page 252 - Using SCSI Bus Signal Converters; DWZZA — 8-bit data path; Types of SCSI Bus Signal Converters

9.1 Using SCSI Bus Signal Converters A SCSI bus signal converter allows you to couple a differential bus segmentto a single-ended bus segment, allowing the mixing of differential andsingle-ended devices on the same SCSI bus to isolate bus segments formaintenance purposes. Each SCSI signal converter ...

Page 253 - Using the SCSI Bus Signal Converters; Non-UltraSCSI Devices 9–3

but you would waste a disk slot and it would not work with a KZPBA-CB ifthere are any UltraSCSI disks in the storage shelves. The following sections discuss the DWZZA and DWZZB signal convertersand the DS-BA35X-DA personality module. 9.1.2 Using the SCSI Bus Signal Converters The DWZZA and DWZZB sig...

Page 255 - Terminating the Shared SCSI Bus; Non-UltraSCSI Devices 9–5

______________________ Notes ______________________ S4-3 and S4-4 have no function on the DS-BA35X-DA personalitymodule. See Section 9.3.2.2 for information on how to select the deviceSCSI IDs in an UltraSCSI BA356. Figure 9–3 shows the relative positions of the two DS-BA35X-DA switchpacks. Figure 9...

Page 257 - Non-UltraSCSI Devices 9–7

connector at a later time without affecting bus termination. This allows youto expand your configuration without shutting down the cluster. Figure 9–4 shows a BN21W-0B Y cable, which you may attach to aKZPSA-BB or KZPBA-CB SCSI adapter that has had its onboard terminationremoved. You can also use th...

Page 258 - Overview of Disk Storage Shelves

Figure 9–5: HD68 Trilink Connector (H885-AA) FRONT VIEW REAR VIEW ZK-1140U-AI ______________________ Note _______________________ If you connect a trilink connector to a SCSI bus adapter, youmay block access to an adjacent PCI slot. If this occurs, use a Ycable instead of the trilink connector. This...

Page 259 - Non-UltraSCSI Devices 9–9

9.3.1 BA350 Storage Shelf Up to seven narrow (8-bit) single-ended StorageWorks building blocks(SBBs) can be installed in the BA350. Their SCSI IDs are based upon theslot they are installed in. For instance, a disk installed in BA350 slot 0 hasSCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1...

Page 260 - Figure 9–6: BA350 Internal SCSI Bus

Figure 9–6: BA350 Internal SCSI Bus JA1 JB1 0 1 2 3 4 5 6 POWER (7) T J ZK-1338U-AI 9.3.2 BA356 Storage Shelf There are two variations of the BA356 used in TruCluster Server clusters:the BA356 (non-UltraSCSI BA356) and the UltraSCSI BA356. An example of the non-UltraSCSI BA356 is the BA356-KC, which...

Page 261 - Non-UltraSCSI Devices 9–11

select SCSI IDs 0 through 6, set the personality module address switches 1through 7 to off. To select SCSI IDs 8 through 14, set personality moduleaddress switches 1 through 3 to on and switches 4 through 7 to off. Figure 9–7 shows the relative location of the BA356 SCSI bus jumper,BA35X-MF. The jum...

Page 262 - Figure 9–7: BA356 Internal SCSI Bus

Figure 9–7: BA356 Internal SCSI Bus JA1 JB1 0 1 2 3 4 5 6 POWER (7) J ZK-1339U-AI Note that JA1 and JB1 are located on the personality module (in the top ofthe box when it is standing vertically). JB1, on the front of the module, isvisible. JA1 is on the left side of the personality module as you fa...

Page 263 - Non-UltraSCSI Devices 9–13

Figure 9–8: BA356 Jumper and Terminator Module Identification Pins Slot 6 Jumper Pin Slot 6 Terminator Pin Slot 1 Jumper Pin Slot 1 Terminator Pin ZK-1529U-AI 9.3.2.2 UltraSCSI BA356 Storage Shelf The UltraSCSI BA356 (DS-BA356-JF or DS-BA356-KH) has a single-ended,wide UltraSCSI bus. The DS-BA35X-DA...

Page 265 - for an Externally Terminated TruCluster Server Configuration; Non-UltraSCSI Devices 9–15

Later sections describe how to install cables to configure an HSZ20, HSZ40,or HSZ50 in a TruCluster Server configuration with two member systems. 9.4.1 Preparing BA350, BA356, and UltraSCSI BA356 Storage Shelves for an Externally Terminated TruCluster Server Configuration You may be using the BA350,...

Page 266 - Install the DWZZA-VA in slot 0 of the BA350.; Preparing a BA356 Storage Shelf for Shared SCSI Usage; Set the switches on the BA356 personality module as follows:

2. You will need a DWZZA-VA signal converter for the BA350. Ensurethat the DWZZA-VA single-ended termination jumper, J2, is installed.Remove the termination from the differential end by removing the five14-pin differential terminator resistor SIPs. 3. Attach an H885-AA trilink connector to the DWZZA...

Page 267 - If you are using a DWZZB-VW, install it in slot 0 of the BA356.; Connecting Storage Shelves Together; Non-UltraSCSI Devices 9–17

SCSI bus (cable and BA356) under the 3-meter limit to still allow highspeed operation. If you are using a DWZZB-VW, install it in slot 0 of the BA356. 9.4.1.3 Preparing an UltraSCSI BA356 Storage Shelf for a TruCluster Configuration An UltraSCSI BA356 storage shelf is connected to a shared UltraSCSI...

Page 269 - Figure 9–9: BA350 and BA356 Cabled for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–19

Figure 9–9: BA350 and BA356 Cabled for Shared SCSI Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 ID 14 orredundantpowersupply KZPSA-BB (ID 7) MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 ID 5 ID 4 ID 6 ID 3 ID 2 ID 1 Datadisk Do not use fordata disk. Ma...

Page 270 - H885-AA trilink connector; Connect a BN21K or BN21L cable between the H885-AA trilinks.

Table 9–1: Hardware Components Used for Configuration Shown in Figure8–9 and Figure 8–10 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA terminator 3 BN21K (or BN21L) cable a 4 H885-AA trilink connector a The maximum combined length of the BN21K (or BN21L) cables must not exceed 25 meters. 9...

Page 271 - Figure 9–10: Two BA356s Cabled for Shared SCSI Bus Usage; Connecting Two UltraSCSI BA356s for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–21

Figure 9–10: Two BA356s Cabled for Shared SCSI Bus Usage ID 9 ID 10 ID 11 ID 12 ID 13 ID 14 orredundantpowersupply KZPSA-BB (ID 7) MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 ID 5 ID 4 ID 6 ID 3 ID 2 ID 1 Datadisk Do not use fordata disk. Maybe ...

Page 273 - Figure 9–11: Two UltraSCSI BA356s Cabled for Shared SCSI Bus Usage; Non-UltraSCSI Devices 9–23

Figure 9–11: Two UltraSCSI BA356s Cabled for Shared SCSI Bus Usage ID 8 ID 9 ID 10 ID 11 ID 12 ID 13 PWR ID 5 PWR Clusterwide/, /usr, /var Member 1Boot Disk Member 2Boot Disk QuorumDisk UltraSCSI BA356 UltraSCSI BA356 ID 4 ID 14 orredundantpowersupply KZPBA-CB (ID 7) Network MemoryChannelInterface M...

Page 274 - Terminated Shared SCSI Bus; KZPSA-BB host bus adapter

Table 9–2: Hardware Components Used for Configuration Shown in Figure9–11 Callout Number Description 1 BN21W-0B Y cable 2 H879-AA HD68 terminator 3 BN38C (or BN38D) cable a 4 H8861-AA VHDCI trilink connector 5 BN37A cable a a The maximum combined length of the BN38C (or BN38D) and BN37A cables on on...

Page 275 - Non-UltraSCSI Devices 9–25

9.4.3.1 Cabling an HSZ40 or HSZ50 in a Cluster Using External Termination To connect an HSZ40 or HSZ50 controller to an externally terminated sharedSCSI bus, follow these steps: 1. If the HSZ40 or HSZ50 will be on the end of the shared SCSI bus, attachan H879-AA terminator to an H885-AA trilink conn...

Page 277 - Cabling an HSZ20 in a Cluster using External Termination; Remove the five differential terminator resistor SIPs.; Non-UltraSCSI Devices 9–27

Figure 9–13: Externally Terminated Shared SCSI Bus with HSZ50 RAIDArray Controllers at Bus End KZPSA-BB (ID 7) Network MemoryChannelInterface Memory Channel KZPSA-BB (ID 6) Memory Channel MemberSystem 2 MemberSystem 1 2 1 1 2 T T 3 4 3 3 4 HSZ50 Controller A Controller B HSZ50 ZK-1597U-AI Table 9–3 ...

Page 278 - Cabling an HSZ40 or HSZ50 RAID Array Controller in a Radial; Verify that the fair arbitration switch is in the

• Ensure that the W1 and W2 jumpers are installed to enable thesingle-ended termination on one end of the bus. ___________________ Note ___________________ The RAID Array 310 SCSI bus converter board is thesame logic board used in the DWZZB signal converter. 2. Attach an H885-AA trilink connector to...

Page 279 - Install the UltraSCSI hub in:; Non-UltraSCSI Devices 9–29

5. Install the UltraSCSI hub in: • A StorageWorks UltraSCSI BA356 shelf (which has the required180-watt power supply). • A non-UltraSCSI BA356 which has been upgraded to the 180-wattpower supply with the DS-BA35X-HH option. 6. If you are using a: • DS-DWZZH-03: Install a BN38C (or BN38D) HD to VHDCI...

Page 281 - Non-UltraSCSI Devices 9–31

Figure 9–15: TruCluster Server Cluster Using KZPSA-BB SCSI Adapters, aDS-DWZZH-05 UltraSCSI Hub, and an HSZ50 RAID Array Controller T T T T T T HSZ50 HSZ50 T 1 D S - D W Z Z H - 0 5 KZPSA-BB KZPSA-BB 1 1 1 AlphaServer Member System 2 T KZPSA-BB AlphaServer Member System 1 AlphaServer Member System 3...

Page 283 - TruCluster Server Hardware Installation Using PCI; to Non-UltraSCSI Devices 10–1

10 Configuring Systems for External Termination or Radial Connections to Non-UltraSCSI Devices This chapter describes how to prepare the systems for a TruCluster Servercluster when there is a need for external termination or radial connection tonon-UltraSCSI RAID array controllers (HSZ40 and HSZ50)....

Page 284 - Termination

Follow the steps in Table 10–1 to start the TruCluster Server hardwareinstallation procedure. You can save time by installing the Memory Channeladapters, redundant network adapters (if applicable), and KZPSA-BB orKZPBA-CB SCSI adapters all at the same time. Follow the directions in the referenced do...

Page 285 - to Non-UltraSCSI Devices 10–3

The DWZZH-series UltraSCSI hubs are designed to allow more separationbetween member systems and shared storage. Using the UltraSCSI hub alsoimproves the reliability of the detection of cable faults. A side benefit is the ability to connect the member systems’ SCSI adapterdirectly to a hub port witho...

Page 286 - Step

_____________________ Note _____________________ You may have problems if the member system supports the bus_probe_algorithm console variable and it is not set to new . See Section 2.4.1. The KZPBA-CB UltraSCSI host adapter: • Is a high-performance PCI option connecting the PCI-based host systemto t...

Page 287 - to Non-UltraSCSI Devices 10–5

Table 10–2: Installing the KZPSA-BB or KZPBA-CB for Radial Connectionto a DWZZH UltraSCSI Hub (cont.) Step Action Refer to: 2 Power down the system. Install a KZPSA-BBPCI-to-SCSI adapter or KZPBA-CB UltraSCSI hostadapter in the PCI slot corresponding to the logicalbus to be used for the shared SCSI ...

Page 289 - to Non-UltraSCSI Devices 10–7

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for use with ExternalTermination Step Action Refer to: 1 Remove the KZPSA-BB internal terminationresistors, Z1, Z2, Z3, Z4, and Z5. Section 10.1.4.4,Figure 10–1, and KZPSAPCI-to-SCSI StorageAdapter Installationand User ’s Guide Remove the eight KZPBA-CB ...

Page 290 - set

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for use with ExternalTermination (cont.) Step Action Refer to: 7 Use the show pk* or show isp* console commands to determine the status of theKZPSA-BB or KZPBA-CB console environmentvariables, and then use the set console command to set the KZPSA-BB bus ...

Page 291 - Compaq ESL9326D Enterprise Library; These tape libraries must be on the end of the shared SCSI bus.; Console Commands; Example 10–1: Displaying Configuration on an AlphaServer 4100

Table 10–3: Installing a KZPSA-BB or KZPBA-CB for use with ExternalTermination (cont.) Step Action Refer to: TL890 with TL891/TL892 Section 8.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 ____...

Page 292 - Example 10–2: Displaying Devices on an AlphaServer 4100

Example 10–1: Displaying Configuration on an AlphaServer 4100 (cont.) CPU (4MB Cache) 3 0000 cpu0 CPU (4MB Cache) 3 0000 cpu1 Bridge (IOD0/IOD1) 600 0021 iod0/iod1 PCI Motherboard 8 0000 saddle0 Bus 0 iod0 (PCI0) Slot Option Name Type Rev Name 1 PCEB 4828086 0005 pceb0 2 S3 Trio64/Trio32 88115333 00...

Page 293 - Example 10–3: Displaying Configuration on an AlphaServer 8200; to Non-UltraSCSI Devices 10–11

Example 10–2: Displaying Devices on an AlphaServer 4100 (cont.) dkd100.1.0.4.1 DKd100 RZ26N 0568 dkd200.1.0.4.1 DKd200 RZ26 392A dkd300.1.0.4.1 DKd300 RZ26N 0568 polling kzpsa0 (DEC KZPSA) slot 5, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 7 kzpsa0.7.0.5.1 dke TPwr 1 Fast 1 Bus ID 7 L01 A11 dke100.1.0.5...

Page 294 - Example 10–4: Displaying Devices on an AlphaServer 8200

Example 10–4: Displaying Devices on an AlphaServer 8200 >>> show device polling for units on isp0, slot0, bus0, hose0... polling for units on isp1, slot1, bus0, hose0... polling for units on isp2, slot4, bus0, hose0... polling for units on isp3, slot5, bus0, hose0...polling for units kzpaa0...

Page 295 - Displaying Console Environment Variables and Setting the; Variables; diff; to Non-UltraSCSI Devices 10–13

10.1.4 Displaying Console Environment Variables and Setting the KZPSA-BB and KZPBA-CB SCSI ID The following sections show how to use the show console command to display the pk* and isp* console environment variables and set the KZPSA-BB and KZPBA-CB SCSI ID on various AlphaServer systems. Use these ...

Page 297 - to Non-UltraSCSI Devices 10–15

Example 10–6: Displaying Console Variables for a KZPBA-CB on anAlphaServer 8x00 System P00>>> show isp* isp0_host_id 7 isp0_soft_term on isp1_host_id 7 isp1_soft_term on isp2_host_id 7 isp2_soft_term on isp3_host_id 7 isp3_soft_term on isp5_host_id 7 isp5_soft_term diff Both Example 10–3 an...

Page 298 - on; Example 10–8: Setting the KZPBA-CB SCSI Bus ID

Example 10–7: Displaying Console Variables for a KZPSA-BB on anAlphaServer 8x00 System (cont.) pkc0_fast 1 pkc0_host_id 7 pkc0_termpwr on 10.1.4.2 Setting the KZPBA-CB SCSI ID After you determine the console environment variables for the KZPBA-CBson the shared SCSI bus, use the set console command t...

Page 299 - set pk; set pk; Example 10–9: Setting KZPSA-BB SCSI Bus ID and Speed; to Non-UltraSCSI Devices 10–17

10.1.4.3 Setting KZPSA-BB SCSI Bus ID, Bus Speed, and Termination Power If the KZPSA-BB SCSI ID is not correct, or if it was reset to 7 by thefirmware update utility, or you need to change the KZPSA-BB speed, orenable termination power, use the set console command. ______________________ Note ______...

Page 300 - Figure 10–1: KZPSA-BB Termination Resistors; update

10.1.4.4 KZPSA-BB and KZPBA-CB Termination Resistors The KZPSA-BB internal termination is disabled by removing terminationresistors Z1 through Z5, as shown in Figure 10–1. Figure 10–1: KZPSA-BB Termination Resistors Z1 − Z5 TerminationResistor SIPs The KZPBA-CB internal termination is disabled by re...

Page 301 - update pkb0; verify; to Non-UltraSCSI Devices 10–19

The boot sequence provides firmware update overview information. UseReturn to scroll the text, or press Ctrl/C to skip the text. After the overview information has been displayed, the name of the defaultboot file is provided. If it is the correct boot file, press Return at the Bootfile: prompt. Othe...

Page 303 - Table A–1: Converting Storageset Unit Numbers to Disk Names; WWID; Worldwide ID to Disk Name Conversion Table A–1

A Worldwide ID to Disk Name Conversion Table Table A–1: Converting Storageset Unit Numbers to Disk Names File Systemor Disk HSG80Unit WWID UserDefineIden-tifier(UDID) Device Name dsk n Tru64 UNIXdisk Cluster root( / ) /usr /var Member 1boot disk Member 2boot disk Member 3boot disk Member 4boot disk ...

Page 305 - Index; Index–1

Index A ACS V8.5 , 2–4 arbitrated loop , 6–7 ATL TL893 , 8–40, 8–41 TL896 , 8–40, 8–41 ATM atmconfig command , 7–4 connecting cables , 7–4 installation , 7–1 LANE , 7–1 atmconfig command , 7–4 availability increasing , 4–3 B BA350 , 9–9 preparing , 9–15 preparing for shared SCSI usage , 9–15 termina...

Page 306 - Index–2

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 clusterwid...

Page 307 - Index–3

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...

Page 308 - Index–4

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...

Page 309 - Index–5

supported Y cables , 2–1 terminators , 2–11 trilink connectors , 2–11 host bus adapters ( 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 por...

Page 310 - Index–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–...

Page 311 - Index–7

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 po...

Page 312 - Index–8

( 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 sub...

Page 313 - Index–9

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...

Page 317 - How to Order Tru64 UNIX Documentation; Name

How to Order Tru64 UNIX Documentation You can order documentation for the Tru64 UNIX operating system and relatedproducts at the following Web site: http://www.businesslink.digital.com/ If you need help deciding which documentation best meets your needs, see theTru64 UNIX Documentation Overview or c...

Page 320 - UBPG PUBLICATIONS MANAGER; Do Not Cut or Tear - Fold Here; FIRST CLASS MAIL PERMIT NO. 33 MAYNARD MA; COMPAQ COMPUTER CORPORATION; Cut on This Line

UBPG PUBLICATIONS MANAGER Do Not Cut or Tear - Fold Here Do Not Cut or Tear - Fold Here and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES FIRST CLASS MAIL PERMIT NO. 33 MAYNARD MA POSTAGE WILL BE PAID BY ADDRESSEE Z K O 3 - 3 / Y 3 2110 SPIT BROOK RD COMPAQ COMPUTER CORPORATION NASHUA NH ...

Compaq AA-RHGWB-TE - Manual

Table of Contents:

Summary

Other Compaq Models