NonStop NS-Series Planning Guide (H06.05+)

Integrity NonStop NS14000 System Description
HP Integrity NonStop NS-Series Planning Guide—529567-008
8-22
P-Switch to NonStop S-Series I/O Enclosure Cabling
Processor Switch ServerNet Connections
Integrity NonStop NS14000 servers do not use p-switches. Instead, ServerNet cluster
connections connect to ServerNet switch boards in the IOAM enclosure.
Processor Switches to IOAM Enclosures
Integrity NonStop NS14000 servers do not use p-switches. Instead, LSUs in a NonStop
Blade Complex connect directly to 4PSEs installed in the IOAM enclosure.
FCSA to Fibre Channel Disk Modules
The Integrity NonStop NS14000 system implements cabling between FCSAs and
FCDMs (see NonStop Blade Elements to LSUs on page 6-8) similarly to the Integrity
NonStop NS16000 system, with these exceptions:
•
Only configurations with one IOAM enclosure are supported.
•
A maximum of 16 FCDMs can be connected in the Integrity NonStop NS14000
system because only one IOAM enclosure containing a maximum of four FCSAs is
supported.
See FCSA to Fibre Channel Disk Modules on page 6-16
FCSA to Tape Devices
The Integrity NonStop NS14000 system implements cabling connections between
FCSAs and tape devices in the same manner as the Integrity NonStop NS16000
server. For information on this topic, see FCSA to Tape Devices on page 6-16.
P-Switch to NonStop S-Series I/O Enclosure Cabling
The Integrity NonStop NS14000 system does not use p-switches or support
connections to NonStop S-series I/O enclosures.
IOAM Enclosure and Disk Storage Considerations
These considerations apply to an Integrity NonStop NS14000 system:
•
Only configurations with one IOAM enclosure are supported.
•
The group number for the IOAM enclosure is 100.
•
NonStop S-series I/O enclosures are not supported.
•
A maximum of 16 FCDMs can be connected in the Integrity NonStop NS14000
system because only one IOAM enclosure containing a maximum of four FCSAs is
supported.
•
Two G4SAs, one G4SA in each IOAM module, that connect to the ME are
necessary to enable the OSM Service Connection and OSM Notification Director.