InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - AIX

MultiNICA and IPMultiNIC

In the following example, two systems, sysa and sysb, each have a pair of network interfaces, en0 and en1. In this example, the two interfaces, en0 and en1, have the same base, or physical, IP address. Note the lines beginning Device@sysa and Device@sysb; the use of different physical addresses shows how to localize an attribute for a particular host.

The MultiNICA resource fails over the IP addresses to the backup interface in the event of a failure of the active interface. The resources ip1 and ip2, shown in the following example, have the Address attribute that contains the virtual IP address. In the event of an interface failure on sysa, the physical IP address and the two virtual IP addresses fail over from en0 to en1.

However, if both the interfaces on sysa are disconnected, the MultiNICA and IPMultiNIC resources work in tandem to fault the group on sysa. The entire group now fails over to sysb.

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

group grp1 (
SystemList = { sysa = 0 , sysb = 1 }
AutoStartList = { sysa }
)
MultiNICA mnic (
Device@sysa = { en0 = "10.128.8.42", en1 = "10.128.8.42" }
Device@sysb = { en0 = "10.128.8.43", en1 = "10.128.8.43" }
NetMask = "255.255.0.0"
Gateway = "10.128.1.1"
BroadcastAddr = "10.128.255.255"
Options = "mtu 1500"
)
IPMultiNIC ip1 (
Address = "10.128.10.14"
NetMask = "255.255.0.0"
MultiNICAResName = mnic
Options = "mtu 1500"
)
ip1 requires mnic
group grp2 (
SystemList = { sysa = 0 , sysb = 1 }
AutoStartList = { sysa }
)
IPMultiNIC ip2 (
Address = "10.128.9.4"
NetMask = "255.255.0.0"
MultiNICAResName = mnic
Options = "mtu 1500"
)
Proxy proxy (
TargetResName = mnic
)
ip2 requires proxy