5190/5194 Modular Tape Subsystem Manual

Installing the Modular Tape Subsystem
5190/5194 Modular Tape Subsystem Manual—426878-002
3-12
Migrating a Tape Drive to a NonStop Himalaya
S-Series Server
Migrating a Tape Drive to a NonStop Himalaya S-Series Server
If you wish to migrate a 5190 or 5194 tape drive to a NonStop Himalaya S-series
server, ask your service provider to provide version level information for your tape drive
hardware.
Tape Drive Configurations
The installation procedure for a modular tape subsystem depends on the controller or
adapter, cable type, and the number of tape drives (one or two) in each tape drive
module.
MFC (NonStop Himalaya K-Series Servers)
An MFC supports one tape drive (see Figure 3-4). For a module containing two drives,
you must attach the drives to separate MFCs. The MFC uses SCSI cable for
attachment and does not require a back-end board (BEB).
3216 Controller (NonStop Himalaya K-Series Servers)
A 3216 controller can support one tape drive (see Figure 3-5) or two tape drives (see
Figure 3-6). In the two-drive configuration, a daisy-chained SCSI cable passes
commands and information between the drives. The daisy-chain cable and the SCSI
terminator required to terminate the unused receptacle are installed at the factory.
The 3216 controller attaches to the drive CRU using fiber-optic cable and requires a
back-end board (BEB) to translate fiber-optic signals into SCSI data. You must install
the BEB by plugging it into the SCSI port and securing the wing nut (see Installing the
BEB (Fiber-Optic Cables Only) on page 3-25). With a daisy-chain cable, one BEB can
support two drives.
Figure 3-4. MFC Drive Configuration
Tape
Drive
Device ID 5
ACL
Drive CRU
Copper Cable
(3.1 m or 7.7 m)
MFC Logic Board RS-232/SCSI
BIC
SCSI
Terminator
VST011.vsd