This operation can be started automatically after you have finished creating an IP address resource hierarchy or from an existing IP address resource hierarchy as described in the section on extending resource hierarchies. The following additional data is required to extend an IP address resource hierarchy.
|Subnet Mask||Enter the subnet mask to use for the IP resource on the target server. LifeKeeper for Windows will, by default, offer the subnet mask used on the template server.|
|Network Connection||Select the network connection to use on the target server.|
|Target Restore Mode|| This feature applies to three-node LifeKeeper for Windows clusters where two nodes are on a LAN (same subnet) and the third node is on a WAN (different subnet). The restore mode of the IP resource would be enabled on the LAN nodes and disabled on the WAN node.
Select the appropriate Restore Mode for this IP resource on the target system. In some situations a protected IP address should not be used on a remote target system. For example, the remote target system may be connected to a different subnet than other systems in the cluster. In this situation the IP resource may be extended using the “Disable” Restore Mode. When using the “Disable” Restore Mode option, LifeKeeper for Windows will not configure the IP address on the target system when the resource is placed in-service there and monitoring for the IP resource will be disabled. In these situations, network redirection may be implemented some other way or by using a LifeKeeper for Windows DNS resource. You may use the IP resource properties page on the target system to change your selection at a later time. See Managing IP Resources.
|Target Local Recovery||Click Yes if you wish to enable IP Local Recovery on the target server; otherwise choose No.|
|Target Local Recovery Network Connection||If you answered Yes to Local Recovery, you must select a network connection to use as the backup interface. Specify the backup NIC if one exists; otherwise, specify the primary NIC.|