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

Table 2 Interface Type for Failover Behavior
FailoverCharacteristicsInterface Type
Exists in every CLIM so failover is not needed.
Cannot be configured for failover, but does
Loopback
• Reflects output back to its input
• Named lo
have an entry in the NonStop OS interface
table.
Can be configured for CLIM-to-CLIM failover.
The backup interface can be a physical or
bonded interface.
Physical (non-slave)
• Corresponds to a physical Ethernet
interface connected to a user network
• Reports link pulse from the physical
interface
• Named by the CLIM kernel: eth1, eth2, …
Not supported and cannot be configured on
data LAN interfaces.
Logical
• Adds an IP address to a physical interface
• Named by appending a colon (:) and
number to the physical interface name:
eth2:1
Can be configured for CLIM-to-CLIM failover.
If all its slave interfaces fail, the interface
Bonding
• Combines two or more physical interfaces
for fault tolerance
resources of the bonded interface are migrated.
• Each physical interface is called a slave
interface
The backup interface can be a physical or
bonded interface.
• Reports link pulse down only if down on
all slave interfaces
• Named by the user, must be either :
bond0 or bond1 (only two bonded
interfaces allowed on each CLIM)
Cannot be configured for failover and does
not have an entry in the NonStop OS interface
table.
• A physical interface that is combined into
a bonded interface
Slave
Follows the physical or bonded interface
associated with its local address. Cannot be
Static IPv6-over-IPv4
Tunnel
• Encapsulates IPv6 packets inside IPv4
packets.
individually configured for failover, but does
• Named by the user, typically: TUN0,
TUN1, TUN2, …
have an entry in the NonStop OS interface
table.
Cannot be configured for failover and does
not have an entry in the NonStop
operating-system interface table.
Maintenance Interface
• Corresponds to a physical Ethernet
interface eth0 connected to the dedicated
service LAN
• Used for CLIM access to the dedicated
service LAN
• Named by the CLIM kernel as eth0. (A
single wire from the eth0 interface to the
dedicated service LAN is used for both
eth0 and eth0:0.)
Cannot be configured for failover and does
not have an entry in the NonStop OS interface
Maintenance Provider
Interface
• Configured for maintenance Provider
• Used for NonStop OS access to the
dedicated service LAN
table for a data Provider. Does have an entry
in the NonStop OS interface table for the
maintenance Provider.
• Associated with maintenance interface
eth0
• Added at startup, named eth0:0
CLIM Bonded Interfaces
CIP supports failover of Ethernet interfaces within the same CLIM using the CLIM bonding driver.
The bonding driver groups multiple physical interfaces, called slave interfaces, into a single bonded
interface. The bonding driver transparently handles failure of a slave interface by switching traffic
42 Overview