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

IPv6-over-IPv4 tunnel interfaces are not directly configured for failover; rather, they follow the
interface containing their configured local address. The interface name configured on the home
CLIM is used on the failover CLIM; therefore, tunnel interface names must not be the same on the
home and failover CLIMs.
Interface Status Control
The CLIMCMD utilities ifstart and ifstop are provided to bring interfaces up and down, respectively.
They coordinate with the CLIM software and host to start and stop the proper interface resources.
Failover is suppressed when an interface is brought down using ifstop.
The INTFALL option of the SCF ABORT CLIM command brings down all home interfaces on the
specified CLIM even if they have failed over to other CLIMs. Otherwise, failed-over interfaces are
not affected by ABORT CLIM. The INTFALL option can be used on CLIMs that have already been
aborted to bring down just the failed-over interfaces.
IPSec Configuration
IPSec is configured on the CLIM using the climconfig command tool (see “Climconfig (Man Pages)”
(page 301)). The IPSec configuration is not failed over and must be identical on the home and
failover CLIMs for addresses that can fail over between them.
Configuration Changes
When a configuration change is made using the climconfig command tool that affects failover,
such as changing interfaces, IP addresses, routes, or failover-interface names, the failover
configuration becomes invalid and failover does not occur until:
• The failover configuration is propagated to all CLIMs containing failover interfaces. This is
done automatically as long as the failover CLIMs are available on the dedicated service LAN.
• The home CLIM object is in the STARTED state, at least briefly, so the host can retrieve
information about the configuration change.
When an interface has failed over, changes made to its configuration do not take effect until the
interface is restored to its home interface.
Invalid Failover Configuration
Some invalid failover configurations cannot be detected until the affected CLIM objects become
STARTED. These invalid configurations include:
• Failover interface does not exist or is not allowed, such as a slave or tunnel interface
• Home and failover interfaces do not form a pair
• A configuration change has been made and the CLIM has not copied the new configuration
files to the failover CLIM
• A configuration change has been made and the home CLIM object never became STARTED
• A CLIM interface is specified that is configured on the system, but is not under the same
Provider.
When an invalid failover configuration is detected, an EMS message is issued and failover does
not occur either manually or automatically. When the condition is repaired, another EMS message
indicates that failover is now possible.
Internet Protocol Security (IPSec)
For background information about IPSec, see the NonStop Networking Overview Manual.
The CLIM has IPSec functionality enabled by default. The climconfig command tool allows
configuration of the IPSec security policies, security associations and dynamic internet key exchange
(IKE) functionality using racoon.
48 Overview