|
|
|
|
|
In the following example, two systems, sysa and sysb, each have a pair of network interfaces, lan0 and lan3. In this example, the two interfaces, lan0 and lan3, 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 only the physical IP address to the backup NIC during a failure. The logical IP addresses are configured by the IPMultiNIC agent. The resources ip1 and ip2, shown in the following example, have the Address attribute which contains the logical IP address. If a NIC fails on sysa, the physical IP address and the two logical IP addresses fails over from lan0 to lan3. If lan3 fails, the address fails back to lan0 if lan0 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 now fails over to sysb.
If you have more than one group using the MultiNICA resource, the second group can use a Proxy resource to point to the MultiNICA resource in the first group. This prevents redundant monitoring of the NICs on the same system. The IPMultiNIC resource is always made dependent on the MultiNICA resource. See the IPMultiNIC agent for more information.
Device@sysa = { lan0 = "192.205.8.42", lan3 = "192.205.8.42" }
Device@sysb = { lan0 = "192.205.8.43", lan3 = "192.205.8.43" }
Options = "broadcast 192.203.15.255"
Options = "broadcast 192.203.15.255"
Options = "broadcast 192.203.15.255"