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

NOTE: The physical interface eth0 connects each CLIM to the dedicated service LAN. Only IP
and Telco CLIMs can have the logical interface eth0:0 and the associated maintenance Providers.
NOTE: In this manual, unless stated explicitly otherwise, “Provider” refers to an IPDATA Provider.
Maintenance Provider Restrictions
There is no failover support for the maintenance Provider. However, HP recommends configuring
two maintenance Providers running on different CLIMs with different IP addresses. OSM can
then switch to a different maintenance Provider if one of them fails.
The maintenance Provider supports only IPv4 addresses.
The maintenance Provider does not support the IP loopback address (127.0.0.1), 127.*.*.*,
class D, or class E IP addresses.
There is a limit of one maintenance Provider interface and one maintenance Provider IP address
for each CLIM.
CLIM Object Name and Hostname
The CLIM object name on the NonStop system must be the same as the host name on the CLIM
itself for the CLIM to be brought to the STARTED state. You assign the name. Host names on CLIMs
on different systems can be the same as long as the combination of the system name and the host
name on the CLIM are unique across the dedicated service LAN. For example, if you have two
systems named \A and \B, you can have a CLIM with a host name of CLIM1 on each system,
since the combination of system name and CLIM name are unique.
Neither the CLIM object name nor the host name on the CLIM can be changed while the CLIM
object is in the STARTED state. The CLIM object is configured by using SCF. The host name on the
CLIM is configured by using the climconfig tool.
CIP CLIM Software Overview
The CLIM runs the Linux operating system offering many of the open source networking features
and providing an intelligent device for storage applications. The CIP software on the CLIM uses
Linux tools to configure and control TCP/IP and IPSec, SNMP agents for health monitoring, HP
Integrated Lights Out (iLO) Management for low-level diagnostics, and the syslog and evlog event
mechanism for event reporting.
When using CIP, you do not need to use Linux commands directly on the CLIM and in fact very
few Linux commands are supported. Instead, use the CLIMCMD command line interface from the
TACL prompt on the NonStop host system. The CLIMCMD CLI provides persistence and failover
for the configuration and also offers only Linux commands that are safe to execute on the CLIM.
CLIM Management
A combination of OSM, the CLIMCMD tool, I/O Essentials, and an integrated Lights Out
Management (iLO) interface are the management tools for the CLIM.
CLIMCMD Tool
The CLIMCMD tool provides a pass-through for commands issued from the NonStop host system
to the CLIM. This mechanism uses a Secure Shell (SSH) server accepting SSH requests from the
NonStop host system. This tool provides support for both Storage and IP CIP.
The CLIMCMD tool with the climconfig command is used to configure networking attributes, SNMP
(for both IP and storage) and the LUN manager on the CLIM. The CLIMCMD tool is also used for
other commands. See Chapter 3 (page 69) for a complete list of CLIMCMD utilities.
You run the CLIMCMD tool on the NonStop host system from the TACL prompt.
CIP CLIM Software Overview 29