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

Figure 4 Multiple Providers per CLIM, Example Configuration
Using Multiple Providers
You can use multiple providers to customize network configurations to an application's needs,
while isolating that application's configuration from other applications in other providers. To
associate a CLIM and all of its interfaces with multiple providers, set the MULTIPROV attribute of
the CLIM object to ON using the ADD CLIM or ALTER CLIM command. See “ADD PROVIDER”
(page 228) and “ADD CLIM” (page 226).
Using Multiple SWAN Paths in a Single Provider
CIP supports configuring path A and path B in a SWAN configuration to run in the same Provider
only on a single CLIM. If you use two CLIMs in a SWAN configuration, you must use different
Providers.
Using Multiple Listeners with Round Robin Sockets
NonStop TCP/IPv6 had a limitation of one listening process per processor per port. CIP does not
have this limitation. There can be many listening processes per processor per port. The only limitation
is the amount of memory available to create sockets.
Routing in the CIP Subsystem
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) is associated with a 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 and so are associated with all of 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 then performs its own IP routing to select an interface
and the first hop in the external network.
34 Overview