3    Supported Hardware

This chapter describes the supported hardware for the TruCluster Server product. It also contains some specific requirements for some of the hardware components.

See the TruCluster Server Release Notes for the latest information about supported hardware and firmware revisions.

3.1    Member Systems

Table 3-1 lists the supported systems by product and the SCSI adapter used for shared SCSI buses on each system. Section 3.1.1 provides the specific requirements for member systems in a TruCluster Server cluster.

Table 3-1:  Supported Member Systems

System SCSI Adapter
AlphaServer 800 KZPSA
AlphaServer 1000 KZPSA
AlphaServer 1000A KZPSA
AlphaServer 1200 KZPSA
AlphaServer 2000 KZPSA
AlphaServer 2100 KZPSA
AlphaServer 2100A KZPSA
AlphaServer 4000 KZPSA
AlphaServer 4000A KZPSA
AlphaServer 4100 KZPSA or KZPBA-CB
AlphaServer 8200 and 8400 KZPSA or KZPBA-CB

3.1.1    TruCluster Server Member Requirements

The requirements for member systems in a TruCluster Server cluster are as follows:

3.2    Network Adapters

Ethernet and Asynchronous Transfer Mode (ATM) networks are supported by TruCluster Server. The following sections describe these adapters.

3.2.1    Supported Ethernet Adapters

The following Ethernet network adapters are supported:

3.2.2    Supported ATM Adapters

Asynchronous Transfer Mode (ATM) is a high-speed, connection-oriented, cell-switched technology. It meets the real-time networking requirements of multimedia applications, while providing increased bandwidth for current installations.

The TruCluster Server product supports the use of ATM Lan Emulation as a network for client access.

ATM is a cell-switching and multiplexing technology where the sender negotiates a path with the network for a connection to the destination.

Information to be sent, which may be data, voice, or video, is segmented into a 53-byte, fixed-length cell (48 bytes of actual information with a 5-byte header).

An ATM network consists of the following components:

The DGLPB-AB ATMworks 350 155 MB/sec multimode fiber optics PCI adapter is supported.

Any high-performance ATM switch with 155 MB/sec ports is supported. A minimum of one ATM switch is required for each ATM circuit.

3.3    SCSI Bus Adapter

To connect a member system to a shared SCSI bus, you must install a SCSI bus adapter in an I/O bus slot. Table 3-2 describes the supported SCSI adapters.

Table 3-2:  Supported SCSI Adapters

SCSI Bus Adapter Transmission Method
KZPBA-CB Differential UltraSCSI
KZPSA-BB UltraSCSI, Differential

The following sections describe the SCSI adapters in more detail.

3.3.1    KZPSA-BB SCSI Adapter Restrictions

KZPSA-BB SCSI adapters have the following restrictions:

3.3.2    KZPBA-CB System and Adapter Restrictions

Compaq's Tru64 UNIX operating system supports a maximum of 48 SCSI buses. Only 30 shared SCSI buses are supported in a TruCluster Server cluster.

Each system supporting the KZPBA-CB UltraSCSI host adapter limits the number of adapters that may be installed. The maximum number of KZPBA-CB UltraSCSI host adapters supported with the TruCluster Server product follow:

3.4    Memory Channel Hardware

Table 3-3 describes the supported Memory Channel hardware.

Table 3-3:  Supported Memory Channel Hardware

Memory Channel Hardware Component Designation Description
Memory Channel PCI adapter CCMAA-AA or CCMAA-BA Memory Channel PCI adapter used as the cluster interconnect.
Memory Channel hub CCMHA-AA PC-class enclosure that is populated with line cards and used to connect Memory Channel adapters. A hub is required if you have more than two member systems.
Line card CCMLA-AA Installed in a Memory Channel hub to allow connection of more than two systems.
Link cable BC12N-10 (10 meters) Connects a Memory Channel adapter to a hub or one Memory Channel adapter to another Memory Channel adapter (virtual hub).

The Memory Channel hardware restrictions are as follows:

3.5    Disk Devices

Table 3-4 lists the supported disk devices for shared SCSI buses and the data paths available for each disk type.

Table 3-4:  Supported Disk Devices

Disk Data Path
RZ26 Narrow
RZ26L Narrow and wide
RZ26N Narrow and wide
RZ28 Narrow and wide
RZ28B Narrow
RZ28D Narrow and wide
RZ28L Narrow and wide
RZ28M Narrow and wide
RZ29 Narrow and wide
RZ29B Narrow and wide
RZ29L Narrow and wide
RZ40 Narrow and wide
RZ40L Narrow and wide
RZ1BB Narrow and wide
RZ1CB Narrow and wide
RZ1DB Narrow and wide

The restrictions for disk devices are as follows:

3.6    Supported RAID Controllers

RAID controllers provide high performance, high availability, and high connectivity access to SCSI devices through a shared SCSI bus. The following RAID controllers are supported in a TruCluster Server cluster.

The HSZ40 controller can be configured with one to four SCSI IDs and with one to eight logical unit numbers (LUNs) for each SCSI ID. For any number of disks, having more SCSI IDs with fewer LUNs for each SCSI ID provides better performance than a configuration with fewer SCSI IDs and more LUNs.

Each RAID controller requires a specific minimum Hierarchical Storage Operating Firmware (HSOF) revision. See the TruCluster Server Release Notes for information about required HSOF revisions.

TruCluster Server supports single-controller, single-bus HSZ40 array configurations and dual-controller, single-bus HSZ40 configurations.

3.7    Disk Storage Shelves

Table 3-5 lists the supported disk storage shelves.

Table 3-5:  Supported Disk Storage Shelves

Storage Shelf Transmission Mode Data Path Internal SCSI Bus Length
BA350 Single-ended Narrow 0.9 Meter
BA353 Single-ended Narrow 0.9 Meter
BA356 Single-ended Wide 1.0 Meter
UltraSCSI BA356 UltraSCSI Single-ended Wide 1.0 Meter

Disk storage shelves have the following restrictions:

The following sections discuss these storage shelves in more detail.

3.7.1    BA350 Storage Shelf

Up to seven narrow (8-bit) StorageWorks building blocks (SBB) can be installed in the BA350. Their SCSI IDs are based upon the slot they are installed in. For instance, a disk installed in BA350 slot 0 has SCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1, and so forth.

The BA350 storage shelf contains internal SCSI bus termination and a SCSI bus jumper. There are occasions when the termination must be removed from the BA350 (for example, when daisy chaining two BA350s together). The jumper is not removed during normal operation.

The BA350 can be set up for two-bus operation, but that option is not very useful for a shared SCSI bus and is not covered in this manual.

Figure 3-1 shows the relative locations of the BA350 SCSI bus terminator and SCSI bus jumper. They are accessed from the rear of the box. For operation within a TruCluster Server cluster, you must install the J jumper.

Figure 3-1:  BA350 Internal SCSI Bus

3.7.2    BA353 Storage Shelf

The BA353 is probably of little use in TruCluster Server configurations; it only has three slots for shared disks.

The SCSI ID for disks installed in a BA353 is defined by device address switches on the back of the BA353. The switches are located to the left of the SCSI input and SCSI output connectors, as shown in Figure 3-2.

The switches are marked as Left (Slot 1), Center (Slot 2), and Right (Slot 3). Slot 1 is the leftmost slot when the BA353 is viewed from the front.

The On position of a switch generates a logic 1 in the device address, and switch one is the least significant bit (LSB) in the device address. The SCSI IDs shown in Figure 3-2 would be 0, 1, and 2, left, center, and right.

Figure 3-2:  BA353 Device Address Switches and SCSI Connectors

3.7.3    BA356 Storage Shelf

There are two variations of the BA356 used in TruCluster Server clusters: the UltraSCSI BA356 and the non-UltraSCSI BA356.

An example of the non-UltraSCSI BA356 is the BA356-KC, which has a wide, single-ended internal SCSI bus. It uses the BA35X-MH 16-bit personality module and has a 150-watt power supply.

The DS-BA356-JF (or DS-BA356-KH) has a single-ended, wide UltraSCSI bus. The DS-BA35X-DA personality module provides the interface between the internal, single-ended UltraSCSI bus and the shared, differential UltraSCSI bus. The UltraSCSI BA356 uses an 180-watt power supply.

3.7.3.1    Non-UltraSCSI BA356 Storage Shelf

The non-UltraSCSI BA356, like the BA350 can hold up to seven StorageWorks building blocks (SBBs). However, unlike the BA350, these SBBs are wide devices. Also, like the BA350, the SBB SCSI IDs are based upon the slot they are installed in, but the switches on the personality module (BA35X-MH) have to be set to off, the default switch positions. Verify that the personality module switches are all off.

Figure 3-3 shows the relative location of the BA356 SCSI bus jumper, BA35X-MF. The jumper is accessed from the rear of the box. For operation within a TruCluster Server cluster, you must install the J jumper in the normal position, behind slot 6. Note that the SCSI bus jumper is not in the same position in the BA356 as in the BA350.

Termination for the BA356 single-ended bus is on the personality module, and is active unless a cable is installed on JB1 to daisy chain two BA356s together. In this case, when the cable is connected to JB1, the personality module terminator is disabled.

Like the BA350, you can set up the BA356 for two-bus operation by installing a SCSI bus terminator (BA35X-ME) in place of the SCSI bus jumper. However, like the BA350, two-bus operation in the BA356 is not very useful for a TruCluster Server cluster.

You can use the position behind slot 1 to store the SCSI bus terminator or jumper.

Figure 3-3 shows the relative locations of the BA356 SCSI bus jumper and the position for storing the SCSI bus jumper, if you do install the terminator. For operation within a TruCluster Server cluster, you must install the J jumper.

Figure 3-3:  BA356 Internal SCSI Bus

Note that JA1 and JB1 are located on the personality module (in the top of the box when it is standing vertically). JB1, on the front of the module, is visible. JA1 is on the left side of the personality module as you face the front of the BA356, and is hidden from the normal view.

To determine if a jumper module or terminator module is installed in a BA356, remove the devices from slots 1 and 6 and note the following pin locations (see Figure 3-4):

Figure 3-4:  BA356 Jumper and Terminator Module Identification Pins

3.7.3.2    UltraSCSI BA356 Storage Shelf

The UltraSCSI BA356 can also hold up to seven StorageWorks building blocks (SBBs). These SBBs are UltraSCSI single-ended wide devices. The SBB SCSI IDs are based upon the slot they are installed in, but the SCSI bus address switches (S3-1 through S3-7) on the personality module (BA35X-DA) have to be set to OFF, the default switch positions. Verify that the personality module SCSI bus address switches are all OFF.

The jumper module is positioned behind slot 6 as with the non-UltraSCSI BA356 shown in Figure 3-3. For operation within a TruCluster Server cluster, you must install the J jumper. You verify the presence or absence of the jumper or terminator modules the same as for the non-UltraSCSI BA356, as shown in Figure 3-4.

Termination for both ends of the UltraSCSI BA356 internal, single-ended bus is on the personality module, and is always active. Termination for the differential UltraSCSI bus is also on the personality module, and is controlled by the SCSI bus termination switches, switch pack S4. For normal cluster operations, S4-1 and S4-2 should normally be ON. Section 4.5.2.2 discusses these switches in more detail.

3.8    SCSI Signal Converters

If you are using a storage shelf with a single-ended SCSI interface in your TruCluster Server hardware configuration, you must connect it to a SCSI signal converter. SCSI signal converters convert narrow or wide, single-ended SCSI to wide, differential SCSI. Some signal converters are standalone desktop units and some are StorageWorks building blocks (SBBs) that you install in storage shelves disk slots.

Note

The UltraSCSI hubs could probably be listed here, but they are covered separately.

Table 3-6 lists the supported SCSI signal converters.

Table 3-6:  Supported SCSI Signal Converters

Device Description
DWZZA-AA Standalone unit
  Converts single-ended, narrow SCSI to differential, wide SCSI. Use with a BA350 or BA353 storage shelf.
DWZZA-VA SBB
  Converts single-ended, narrow SCSI to differential, wide SCSI. Install in a BA350 or BA353 storage shelf.
DWZZB-AA Standalone unit
  Converts single-ended, wide SCSI to differential, wide SCSI. Use with a BA356 storage shelf.
DWZZB-VW SBB
  Converts single-ended, wide SCSI to differential, wide SCSI. Install in a BA356 storage shelf.

The restrictions for SCSI signal converters are as follows:

3.9    UltraSCSI Hubs

The DS-DWZZH series UltraSCSI hubs are SCSI-2 and draft SCSI-3 compliant SCSI 16-bit signal converters capable of data transfer rates of up to 40 MB per second.

They could be listed with the other SCSI bus signal converters, but as they are used differently in TruCluster Server clusters, they will be handled differently in this document.

A DS-DWZZH UltraSCSI hub is installed in a StorageWorks DS-BA356 shelf (which has the required 180-watt power supply). Cluster member systems and HSZ50 or HSZ70 RAID array controllers are radially connected to the hub ports.

A DS-DWZZH UltraSCSI hub:

The DS-DWZZH-03 and the DS-DWZZH-05 UltraSCSI hubs are supported in a TruCluster Server cluster.

3.10    SCSI Cables

If you are using shared SCSI buses, you must determine if you need cables with connectors that are low-density 50-pins, high-density 50-pins, high-density 68-pins (HD68), or Very High Density Cable Interconnect (VHDCI) 68-pins (UltraSCSI). You also have the choice of straight or right-angle connectors. In addition, each supported cable comes in various lengths. Use the shortest possible cables to adhere to the limits on SCSI bus length.

Table 3-7 describes each supported cable and the context in which you would use the cable.

Table 3-7:  Supported SCSI Cables

Cable Connector Density Pins Configuration Use
BN21V-0B One high, two low 50-pin This Y cable attaches to a PMAZC and can be terminated if necessary.
BN21W-0B Three high 68-pin A Y cable that attaches to a KZPSA, HSZ40, HSZ50, or the differential side of a signal converter. It can be terminated if necessary.
BN21R or BN23G One high, one low 50-pin Connects narrow devices such as the BA350, or BA353 to the single-ended side of a DWZZA signal converter. (Replaces the BC09D cable.)
BN21H or BN21J Two high 50-pin Connects narrow devices, such as a BA350 or a BA353.
BC19J or BC06P [Footnote 2] Two low 50-pin Connects BN21V-0B Y cables to each other or the single-ended end of a DWZZA to a TZ885 or TZ887.
BN21M One low, one high 50-pin LD to 68-pin HD Connects the single-ended end of a DWZZB-AA to a TZ885 or TZ887.
BN21K or BN21L Two HD68 68-pin Connects BN21W Y cables or wide devices. For example, connects HSZ40s, the differential sides of two SCSI signal converters, or a DWZZB-AA to a BA356.
BN38C or BN38D One HD68, one VHDCI VHDCI to HD68 Connect a high-density (HD68) Y cable (BN21W-0B) to a VHDCI trilink.
BN37A Two VHDCI VHDCI to VHDCI Connect two VHDCI trilinks to each other.

The requirement for SCSI cables is as follows:

3.11    SCSI Terminators and Trilink Connectors

Table 3-8 describes the supported SCSI terminators and the context in which you would use them.

Table 3-8:  Supported SCSI Terminators

Terminator Density Pins Configuration Use
H879-AA High 68-pin Terminates an H885-AA trilink connector or BN21W-0B Y cable.
12-37004-04 High 50-pin Terminates a BA353 input connector.
H8863-AA VHDCI 68-pin Terminate a VHDCI trilink connector.

Table 3-9 describes the supported trilink connectors and the context in which you would use them.

Table 3-9:  Supported Trilink Connectors

Trilink Connector Number of Connectors Pins Density Configuration Use
H885-AA Three 68-pin High Attaches to high-density, 68-pin cables or devices, such as a KZPSA, HSZ40, HSZ50, or the differential side of a SCSI signal converter. Can be terminated with an H879-AA terminator if necessary.
H8861-AA Three 68-pin VHDCI Attaches to VHDCI 68-pin cables, UltraSCSI BA356 JA1, HSZ70 RAID controllers. Can be terminated with an H8863-AA terminator if necessary.

The requirement for trilink connectors is as follows:

3.12    Supported Tape Devices

The following tape devices are supported by the TruCluster Server; product: