F.5 Configuring Virtual IP Addresses

After the appropriate virtual IP addresses and host masks have been determined as described in Section F.3, Planning a Virtual IP Network Implementation, you can enable virtual IP addresses in a business continuity cluster. A maximum of 256 virtual IP addresses can be bound. For every cluster resource in the business continuity cluster, you must modify the load and unload scripts to use the virtual IP address that you assign to that cluster resource.

For each cluster resource in the business continuity cluster, do the following:

  1. Before you begin, the routers in a virtual IP address configuration must be running the routing protocol.

    For information, see Section F.4, Configuring a Virtual Router with OSPF.

  2. In the cluster resource load script, add the command to bind a virtual IP address for the cluster resource.

    In iManager, use the Clusters plug-in to edit the resource load script to comment out the add_secondary_ipaddress line, and add the virtual IP address information for the dummy0 adapter.

    For example, the old and new lines are emphasized in the following sample load script:

    #!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=POOL1
exit_on_error ncpcon mount TVOL1=101

###exit_on_error add_secondary_ipaddress 10.10.0.101

exit_on_error ip addr add 10.50.0.101/32 dev dummy0

exit_on_error ncpcon bind --ncpservername=CL1-POOL1-VS --ipaddress=10.50.0.101
exit 0

  3. In the cluster resource unload script, add the command to unbind the virtual IP address to the cluster resource unload script.

    In iManager, use the Clusters plug-in to edit the resource unload script to comment out the del_secondary_ipaddress line, and add a line that deletes the virtual IP address information for the dummy0 adapter.

    For example, the old and new lines are emphasized in the following sample unload script:

    #!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error ncpcon unbind --ncpservername=CL1-POOL1-VS --ipaddress=10.50.0.101

###ignore_error del_secondary_ipaddress 10.10.0.101

ignore_error ip addr del 10.50.0.101/32 dev dummy0

ignore_error nss /pooldeact=POOL1
exit 0

  4. In iManager, use the Clusters plug-in to offline the cluster resource, then online the cluster resource.

    This activates the changes that you made to the cluster resource’s load and unload scripts.

  5. To verify that a virtual IP address is bound, enter display secondary ipaddress at a terminal console of the cluster node where the virtual IP address is assigned.

    This displays all bound virtual IP addresses.

  6. Repeat the previous steps for the remaining cluster resources.