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

attribute of the SUBNET object to specify which interface the TCP/IP transport-provider process
would use to send and receive data.
In CIP, there is no underlying subsystem that you have to ensure is running.
In CIP, you can associate a transport-provider process (CIPSAM) with a CLIM but not with a single
interface on a CLIM. You associate a network CLIM with a Provider by using the PROVIDER attribute
of the CLIM object. (A maintenance Provider can be associated with a CLIM but there is no CLIM
attribute for IP data Providers. See “ADD PROVIDER” (page 228) and “ADD ROUTE” (page 230).)
Network Partitioning Differences
In conventional TCP/IP, you can have multiple TCP/IP processes, each having one or more interfaces
uniquely associated with it. In NonStop TCP/IPv6, you can configure the environment to use
logical-network partitioning, each partition having one or more interfaces uniquely associated with
it.
In CIP, with the MULTIPROV option OFF, you can use the SCF PROVIDER object for network
partitioning but you can only restrict a whole CLIM to a Provider (partition). You cannot restrict
individual interfaces to a Provider. If you must associate an application with a specific IP address,
bind the application to that IP address. Alternatively, you can use one interface or set of interfaces
on a CLIM by just adding a subset of the possible physical interfaces (for example, eth1 and eth2).
In CIP, with the MULTIPROV option ON, you can use the SCF PROVIDER object for network
partitioning, with each PROVIDER having one or more interfaces on one or more CLIMs uniquely
associated with it.
Confining Applications that Bind to INADDR_ANY
Server applications that are not configured with a specific IP address to accept incoming TCP/IP
requests probably bind to INADDR_ANY. This allows the applications to accept requests on all IP
addresses in the partition. You might be using network partitioning to confine such applications to
a subset of the addresses on the system. However, many third-party applications can be configured
to bind to a specific address so that they accept connections only to that address, much like binding
to INADDR_ANY on a partition with one interface, as shown in this diagram:
For example, the TCP/IP parameters used by the iTP Secure WebServer are configured in the
Accept command. If this command has no address option, the WebServer binds to INADDR_ANY.
However, if you add an address option with an IP address, the WebServer binds just to that
address.
Routing Differences
The SCF ROUTE object plays a different role in the CIP environment than it did in the previous
subsystem environments. In the CIP subsystem, the ROUTE object allows you to prioritize the CLIM(s)
to use when no specific route matching the destination is configured on any CLIM in the Provider.
In the previous subsystems, the ROUTE object allowed you to specify a route for the first hop on
182 IP CIP Migration, Compatibility and Operational Differences