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

replicated in all the CLIMs. If the socket is used for an outgoing connection or for sending a packet,
the host must choose one of the CLIMs to send it. This process uses the destination address and is
similar to IP routing, but is used only to select a CLIM within a Provider. With either type of binding,
the sending CLIM performs its own IP routing to select an interface and the first hop in the external
network. See “ROUTE Object” and for more information about routing in CIP.
The HOSTNAME and HOSTID attributes give the name returned by gethostname() and the
number returned by the gethostid() socket library calls when the provider is selected.
A PROVIDER can be in one of either the STARTED, STARTING, or STOPPED state. (For definitions
of these states, see “Summary States” (page 222).) If an application tries to create a socket when
the Provider is not in the STARTED state, the application programmatic interface (API) returns an
error. Aborting a Provider that has open sockets also causes the API to return an error on the next
or pending operation.
For more information about the Provider object, see “ADD PROVIDER” (page 228).
ROUTE Object
The ROUTE object specifies which CLIM to use for default routing when there is no non-default
routing specified on any CLIM that can be used for routing to the specified destination and the
connection is not already tied to a specific CLIM. The ROUTE object is a method of selecting a
CLIM for default routing when all other routing methods have failed (for example, no specific route
or rule exists that would cause a specific CLIM to be picked). The route used in the external TCP/IP
network is then determined by the configuration of network routes on the selected CLIM. See
“Climconfig (Man Pages)” (page 301) for information about configuring network routes by using
the CLIMCMD climconfig tool. See “Routing in the CIP Subsystem” (page 34) for more information
about routing in CIP. Multiple CLIMs can define different default routes, however, and the ROUTE
object on the NonStop host system controls which CLIM to select by assigning a PRIORITY attribute
to each CLIM.
The ROUTE is subordinate to the Provider object and requires a unique name. There are no reserved
names.
SUBNET Object
An object represents the interface in the CIP subsystem. It is provided for backward compatibility
and its fully qualified name is of the format: $ZZCIP.#subnet-name. The subnet name can be a
maximum of eight alphanumeric characters. SUBNET names are generated by CIPSAM, not the
user, and are always #SNnnnn, where nnnn is a unique number for each interface. The INFO
SUBNET command displays the association between SUBNET names and CLIM interfaces.
Naming Convention Summary
Table 26: Object Naming Convention Summary and Reserved Names summarizes the reserved
names for each object type and the naming convention rules.
Table 26 Object Naming Convention Summary and Reserved Names
Character LimitNaming
Recommendation
First Character
Requirement
Starting Symbol
(Required)
Reserved NamesObject Type
5MON names are
assigned
automatically.
N/ANoneZCMnnMON (CIPMON)
N/AN/AN/AN/AN/Anull
5The name is
always $ZZCIP.
N/A$$ZZCIPPROCESS
(CIPMAN)
220 SCF Reference for CIP