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

Routes
Static routes configured for an interface are migrated during failover. They are copied to the failover
CLIM from the home CLIM as part of the interface configuration and are added when the failover
logical interface is started.
Dynamic routes were created as the result of information received from routers in the external
network and are not failed over. The failover CLIM has or obtains similar information when it starts
taking over the workload of the failed interface.
TCP and SCTP Connections
TCP and SCTP connections are not migrated during CLIM-to-CLIM failover. An ECONNRESET error
is returned to the local application instead. For TCP connections, the failover CLIM attempts to reset
the connections that were using the failed interface so the remote application can be quickly
informed that the connection is gone. SCTP connections are not reset.
Clients are expected to handle error recovery by attempting to re-establish connections on a new
socket.
IPv6-over-IPv4 Tunnels
Static IPv6-over-IPv4 tunnel interfaces configured with a local address are migrated during failover
of that address. Their configuration is copied to the failover CLIM from the home CLIM as part of
the interface configuration and the interface is added when other failover resources are added.
IPSec Configuration
IPSec parameters are not migrated during failover. It is expected that the IPSec configuration on
the home and failover CLIMs is identical for addresses that can fail over between them. IPSec SAs
that were negotiated between the CLIM containing the failed interface and the remote endpoint
cannot be failed over. They must be renegotiated with the failover CLIM. The remote endpoint sees
an unexpected request for renegotiation, which it must allow.
Failover Configuration
Failover is configured on the CLIMs using the climconfig tool. See “Climconfig (Man Pages)”
(page 301) for command syntax.
CLIM Interface Configuration
Interfaces are configured on their home CLIM using the climconfig tool. Loopback, physical, and
IPv6-over-IPv4 tunnel interfaces can be configured. Intra-CLIM failover is configured by creating a
bonded interface and adding slave interfaces to it. Logical interfaces cannot be configured. Static
routes and ARP entries can be associated with interfaces.
The interface configurations are kept in standard CLIM files on the home CLIM and are copied to
a mirror file sub-tree on their failover CLIMs. Subsequent configuration changes trigger a copy of
the configuration again.
Failover Configuration
A non-slave physical or bonded interface can have a failover interface name associated with it. If
it does not, its interface resources do not fail over if the interface fails, loses link pulse, or the CLIM
fails. If it does, the failover interface name specifies the CLIM and interface to use for failover. The
failover CLIM must be different from the one on which the interface is configured; the failover
interface must be a non-slave physical or bonded interface on the failover CLIM. If an interface
and its failover interface both use failover, they must be configured to use each other. Even if an
interface is not configured for failover, that interface can be used as a failover interface by only
one other interface. The interfaces configured on a CLIM can specify failover interfaces on differing
CLIMs.
Both IPv4 and IPv6 addresses, if configured, are failed over. IPv4 resources include IPv4 addresses,
sockets, and routes. IPv6 resources are IPv6 addresses, sockets, routes, and tunnels.
The CIP Subsystem for Internet Protocols (IP CIP) 47