Cluster Server 7.3.1 Bundled Agents Reference Guide - Linux

MultiNICA and IPMultiNIC Performance Mode configuration

In this example, two systems (sysA and sysB) each have a pair of network interfaces (eth0 and eth1, eth0 and eth2). These interfaces have different physical IP addresses and the agent behaves in Performance Mode (PM).

The MultiNICA resource fails over only the logical IP address to the backup NIC in the event of a failure. The resource ip1 has the Address attribute, which contains the logical IP address. In the event of a NIC failure on sysA, the logical IP address fails over from eth0 to eth1. In the event that eth1 fails - the address fails back to eth0 - as long as eth0 is reconnected.

However, if both the NICs on sysA are disconnected, the MultiNICA and IPMultiNIC resources work in tandem to fault the group on sysA. The entire group fails over to sysB.

If you have more than one service group using the MultiNICA resource, the second service group can use a Proxy resource. The Proxy resource points to the MultiNICA resource of the first service group. This resource prevents redundant monitoring of the NICs on the same system. The IPMultiNIC resource is always made dependent on the MultiNICA resource.

cluster foo (
    UserNames = { admin = "cDRpdxPmHpzS." }
    CounterInterval = 5
    )

    system sysA (
    )
    system sysB (
    )

group grp1 (
    SystemList = { sysA = 1, sysB = 2 }
    )

IPMultiNIC ip1 (
    Address = "192.123.10.177"
    MultiNICAResName = mnic
    NetMask = "255.255.248.0"
    )

MultiNICA mnic (
    Device @sysA = { eth0 = "192.123.10.127", eth1 = 
    "192.123.11.128" }
    Device @sysB = { eth0 = "192.123.10.129", eth2 =
    "192.123.11.130" }
    NetMask = "255.255.248.0"
    NetworkHosts = { "192.123.10.1", "192.123.10.2" }
    )

ip1 requires mnic
    // resource dependency tree
    // 
    // group grp1 
    //          { 
    // IPMultiNIC ip1 
    //          { 
    //          MultiNICA mnic 
    //          } 
    //     }
)