5190/5194 Modular Tape Subsystem Manual

Installing the Modular Tape Subsystem
5190/5194 Modular Tape Subsystem Manual426878-002
3-5
Device IDs
Note the following guidelines for each controller or adapter type:
For NonStop Himalaya K-series servers:
°
The MFC supports one drive CRU for each controller. This drive CRU must
have a device ID of 5.
°
The 3216 tape controller supports up to two drive CRUs. If one drive CRU is
attached to the 3216 controller, it must have a device ID of 5. If two drive
CRUs are attached to the same 3216 controller and linked by a daisy-chain
cable, the device IDs must be 4 and 5.
For NonStop Himalaya S-series servers:
°
The ServerNet addressable controller (SAC), which is part of the PMF CRU or
IOMF CRU, supports one drive CRU. This drive CRU must have a device ID
of 5.
°
The 6760 ServerNet device adapter, connected by either a SCSI cable (S-PIC)
or a fiber-optic cable (F-PIC), can support one tape drive for each PIC. On an
S-PIC, the device ID can be 0 through 5. On an F-PIC, the device ID can be 4
or 5. On either, the default is 5.
See Table 3-3 for a summary of device IDs based on the controller or adapter type.
Table 3-3. Drive CRU Device IDs for Each Controller or Adapter
Controller
or Adapter Server
Number of Drive
CRUs Supported
Drive CRU
Device IDs
MFC NonStop Himalaya K-series
server
15
3216 NonStop Himalaya K-series
server
1 or 2* 5 and 4
SCSI SAC NonStop Himalaya S-series
server
15
6760 adapter
with 6761 F-PIC
NonStop Himalaya S-series
server
4
(1 per PIC)
5 or 4
6760 adapter
with 6762 S-PIC
NonStop Himalaya S-series
server
4
(1 per PIC)
0 through 5
* Two drive CRUs can be supported using daisy-chaining.