One Parallel service group will have a MultiNICA resource with a Phantom resource while the rest of the Failover service groups with IPMultiNIC resource will have a proxy resource monitoring the MultiNICA resource status. Each of the other service groups will have an IPMultiNIC resource controlling the virtual IP address for that application.

1.  Create one Parallel group that has the MultiNICA resource that will monitor the devices.

2.  In the same group,  create a Phantom agent so the group will report the correct status. This is needed when a service group's only resources do not online or offline.  Also change the Parallel attribute to1, so that the group can be in the ONLINE status on all nodes at the same time.

3.  In each of the other Failover groups,  the IPMultiNIC resources will use the TargetResName of the original MultiNICA resource from the first service group for the Proxy. This will attach the additional virtual IPs on the same device for all the service groups.  

4.  The Proxy resource in each additional group will replicate the state of the resource it is representing. That way there is no additional monitoring which could cause additional system load.

5.  Linking the Proxy resource with the IPMultiNIC resource in each of the groups will ensure that if there is a fault on the MulitNICA resource from the first group, the Proxy resource representing it will also fault. This will then affect the behavior of the group to offline resources and possibly failover if appropriate.

Example of a main.cf file:

group grp1(
SystemList = { camcs3, camcs4 }
AutoStartList = { camcs3, camcs4 }
Parallel =1
               )

MultiNICA MultiNICA1(
Device @camcs3 = { hme0 ="152.48.56.3", qfe2 = "152.48.56.3"}
Device @camcs4 = { hme0 ="152.48.56.4", qfe2 = "152.48.56.4"}
                               )
                               
Phantom grp1phantom(

                                 )


groupgrp2 (
SystemList = { camcs3, camcs4 }
AutoStartList = { camcs4, camcs3 }
            )

IPMultiNIC IPMulti2 (
Address ="152.48.56.5"
MultiNICResName =MultiNICA1
)

Proxy MultiNICproxy (
TargetResName =MultiNICA1
)

IPMulti2 requires MultiNICproxy

The commands to do this are:

1.  Open the Cluster Server configuration to allow changes:

2.  Create the service groups:
 

 

 

3.  Add the systems that will run this service group to the SystemList:
 

4.  Modify the AutoStartList to have the group autostart on the nodes in the SystemList:
 

5.  Change the "Parallel" attribute to 1 in order for all the nodes to online the group at the same time:
 

6. Create the MultiNICA resource for grp1:
 

7. Change the "Device" attribute from global to local allowing each system to have differing entries:
 

8.  Populate the "Device" attribute for both systems:

 

9. Set the "Enabled" attribute for the resource so that Cluster Server can control and monitor the resource:
 

10. Create the "Phantom" resource for grp1:
 

11. Enable the resource by setting the Enable flag to 1:
 

12. Add the "IPMultiNIC" resource to grp2:
 

 

13. Add the virtual IP address to the address attribute for the IPMulti2 resource:
 

14. Add the name of the MultiNICA resource to which the virtual IP address will be assigned; notice that it is the MultiNICA resource from grp1:

 

15. Enable the group by setting the Enabled attribute to 1:
 

16. Create the "Proxy" resource (see article 201640 for more information):
 

17.  Add the name of the resource whose state the Proxy resource will be replicating.  In this case it is the MultiNICA resource from grp1:
 

18. Enable the resource by setting the Enabled attribute to 1:
 

19.  Create a dependency between the IPMultiNIC resource and the Proxy resource:

20.  Close the Cluster Server configuration and dump the changes in the main.cf file: