Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

1
Slot 1: ServerNet PCIe card
Four ServerNet ports, from left to right: XB, YB, XA, YA
2
Slot 2 (empty)
3
Slot 3 (empty)
4
Slot 4: Two InfiniBand ports, from left to right: ib1, ib0
5
Slot 5 (empty)
6
Slot 6 (empty)
7
LAN 4: eth3 customer-usable interface
8
LAN 3: eth2 customer-usable interface
9
ILO: Maintenance LAN interface
10
LAN 2: eth1 customer-usable interface
11
LAN 1: Maintenance LAN interface. Eth0 and eth0:0 interface
NOTE: The Informatica software which is part of the Low Latency Solution uses only one InfiniBand
interface on the IB CLIM. HP recommends connecting to the ib0 InfiniBand interface for ease of
manageability.
The CIP Subsystem for Storage I/O (Storage CIP) and the Storage
Subsystem
To find out of your system supports Storage CLIMs, see the planning guide for your system or the
NonStop Networking Overview.
Storage CIP provides the NonStop host system storage subsystem an industry-standard server (the
CLIM). User applications, SQL, and DP2, can access Storage CLIMs without any changes.
Storage CIP uses mostly the same CLIM hardware as IP CIP with some additional storage specific
hardware such as storage-controller adapters and disk storage.
Storage CIP interfaces with the NonStop host system storage subsystem with these restrictions:
NOTE: For the remainder of this manual, Storage CIP refers to the Storage CIP subsystem ($ZZCIP)
and storage subsystem refers to the NonStop host system storage subsystem ($ZZSTO).
• Storage CIP requires a CLIM object to be configured within the CIP subsystem before a CLIM
can be accessed by the storage subsystem. The storage subsystem cannot use a CLIM object
that is configured for IP. A CLIM object that is in use by the storage subsystem cannot be
removed from the CIP subsystem.
• Some management and status information provided by the CIP subsystem is essential for
management of CLIMs by OSM and I/O Essentials. The CLIM object must be in the STARTED
state within the CIP subsystem in order for the CIP subsystem to provide some of this information
(mostly through the STATUS CLIM command).
• CLIM hardware event reporting is provided using a common mechanism for both IP and
Storage CIP. Syslog and evlog events generated in the CLIM are sent to EMS and I/O
Essentials. The CLIM object must be in the STARTED state within the CIP subsystem for this
event reporting functionality to work.
The CIP subsystem allows you to configure and monitor the CLIM as a storage I/O device. To
configure storage features, such as disk paths, use the SCF interface for the storage subsystem.
See the SCF Reference Manual for the Storage Subsystem. Storage CIP commands include:
• Adding a CLIM
• Deleting a CLIM
• Monitoring events from a CLIM
• Obtaining information and various statistics about the CLIM
The CIP Subsystem for Storage I/O (Storage CIP) and the Storage Subsystem 57