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

CIPSAM Object
The CIPSAM process object represents a transport-service provider process. In CIP, the CIPSAM
object can be used only to display and control the CIPSAM process itself. The CIPSAM process is
started by the persistence manager. For specific information about adding and starting the CIPSAM
process, see “Starting CIP on the NonStop Host System” (page 100). For general information about
configuring generic processes (to be started and restarted as necessary by the persistence manager),
see the SCF Reference Manual for the Kernel Subsystem
MON Object
The MON object represents the CIPMON process and is used to query the subsystem on a processor
or replace CIPMON and the CIP library. It is referenced in SCF commands as ZCMnn (no leading
$ or # character), where nn is the two-digit processor number. The MON object can be in one of
either the STOPPED, STARTING, STARTED, or STOPPING states. (For definitions of these states,
see “Summary States” (page 222).)
CIPMONs are started using the persistence manager. MON objects are added or deleted
automatically by CIPMAN to match the running processors. A MON object state of STARTED
indicates that CIPMON is running on the processor and CIPMAN has established communication
with it. An individual CIPMON process can be manually stopped for online replacement or software
reset by issuing a STOP or ABORT command to its MON object; the persistence manager then
automatically restarts the CIPMON process. When the MON process is stopped, the operation of
CIP on its processor is halted and existing sockets are closed.
For specific information about adding and starting the CIPMON process, see “Configuring CIP
Processes for Persistence” (page 73). For general information about configuring generic processes
(to be started and restarted as necessary by the persistence manager), see the SCF Reference
Manual for the Kernel Subsystem.
CLIM Object
The CLIM object on the NonStop host system represents the NonStop host system interface to a
CLIM; it does not really represent the CLIM itself. The CLIM itself starts operating as soon as it boots
the CLIM software, but the NonStop host system gains access to the CLIM by starting the CLIM
object. A CLIM object can be in one of either the STOPPED, STARTING, or STARTED state. (For
definitions of these states, see “Summary States” (page 222).)
The LOCATION attribute gives the group, module, slot, port, and fiber of the ServerNet switch to
which the actual CLIM is connected. If the specified location does not reference an operational
CLIM, then the CLIM object cannot enter the STARTED state.
PROVIDER Object
The PROVIDER object represents a transport-service provider and directs socket requests to a specific
CLIM. Each Provider must have a corresponding CIPSAM process. You associate the Provider with
the CIPSAM process when you add the Provider object. (See “ADD PROVIDER” (page 228).) When
a socket is created, the socket is associated with the CIPSAM process that is set as the environment’s
transport service provider for the session.
The PROVIDER attribute of the CLIM specifies the IPDATA Provider object with which the CLIM is
associated. Multiple CLIMs can be associated with each Provider. This feature allows socket
applications to treat the set of CLIMs associated with the same Provider object as a single
multi-homed host. The sockets created by socket applications can be on any of the CLIMs associated
with the Provider depending on the local IP address associated with each socket. In a Provider
comprising multiple CLIMs, a socket that is bound to a specific local IP address other than a
loopback address (IPv4 127.0.0.1 or IPv6 ::1) exists only in the CLIM containing that address. An
outgoing connection or packet for these kinds of sockets is sent through that CLIM. However, sockets
not yet bound, bound to INADDR_ANY, or bound to a loopback address might be used to listen
for incoming connections or packets on addresses that exist in all the CLIMs of a Provider, so are
Object Types 219