Creating an IP Address Resource Hierarchy

SIOS Protection Suite provides the ability to monitor local switchable IP addresses and moves them to another network adapter in the same system when a failure is detected. This can avoid an entire resource hierarchy failing over to a backup server.

IP Local Recovery imposes requirements and limitations on the system configuration.

Requirements for IP Local Recovery

IP local recovery allows you to specify a single backup network interface for each SIOS Protection Suite-protected IP address on a server. In order for the backup interface to work properly, it must be attached to the same physical network as the primary interface. The system administrator is expected to ensure that a valid interface is being chosen. Note that it is reasonable and valid to specify a backup interface on one server but not on another within the cluster (i.e., the chosen backup interface on one server has no impact on the choice of a backup on any other server).

The backup adapter, also known as the Local Recovery Adapter where the switchable address will become active after a failure of the primary adapter,must be configured in the following way:

• Both adapters must be connected to the same physical subnet.

• For routing purposes, all addresses on the Local Recovery Adapter must be on a different logical subnet than any permanent addresses on the Primary adapter. They must also be on a different logical subnet than any SIOS Protection Suite-protected switchable addresses that are configured on the Primary adapter.

• The IP Local Recovery feature requires that a network gateway exist on the network. Specifically, the default gateway field in the TCP/IP configuration for the system must contain the address of a network gateway. In addition, the local recovery adapter must also be configured with the same network gateway.

• IP Local Recovery can only be enabled at the time the IP resource is created. Local Recovery can not be added to an IP resource by modifying its resource attributes after the resource has been created.

• IP Local Recovery may be disabled for an IP resource by using the “ins_setlocalrecovery” command line utility. This utility is located in the LifeKeeper \bin directory (C:\LK\bin by default). From a command prompt, type “ins_setlocalrecovery” for the usage and switch options.

Before you create and use IP Address resources in SIOS Protection Suite hierarchies, your network should be configured and tested as described in the Verifying Network Configuration topic.

Also verify that the switchable IP address you plan to use is unique using the ping command. The switchable IP address does not need to be created as a prerequisite; it is created when you create the IP address hierarchy.

To create an IP address resource hierarchy from the primary server, you should complete the following steps:

1. Select the server, and then select Create Resource Hierarchy from the server context menu or server context toolbar.

2. A dialog entitled Application to Protect will appear with a list of all recognized recovery kits installed within the cluster. Select IP Address and click Next.

3. The Wizard will prompt you to enter the following information. When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is especially helpful should you encounter an error that might require you to correct previously entered information. If you click Cancel at any time during the sequence of creating your hierarchy, SIOS Protection Suite will cancel the entire creation process.

4. After all of the data is entered, click Next and SIOS Protection Suite will create and validate your resource hierarchy.

5. After receiving the message that the resource hierarchy has been created successfully, click Next to continue. If SIOS Protection Suite has detected a problem, an ERROR will appear in the information box, the partially created resource hierarchy will be removed, and the Next button will be disabled. In that case, click Cancel to exit the Wizard.

*Note: If using teaming software or if network cards are changed after creating a switchable IP resource, the switchable IP resource should be deleted and recreated as the associated index number for the card can change.