To create a resource instance from the primary server, complete the following steps:
- From the LifeKeeper GUI menu, select Edit, then Server. From the drop down menu, select Create Resource Hierarchy.
- A dialog box will appear with a dropdown list box menu listing all recognized recovery kits installed within the cluster. Select IP from the dropdown list and click Next.
- You will be prompted 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 the Cancel button at any time during the sequence of creating your hierarchy, LifeKeeper will cancel the entire creation process.
|This dictates how the IP instance will be switched back to this server when the server comes back up after a failover. You can choose either intelligent or automatic. Intelligent switchback requires administrative intervention to switch the instance back to the primary/original server. Automatic switchback means the switchback will occur as soon as the primary server comes back on line and reestablishes LifeKeeper communication paths. The switchback type can be changed later from the General tab of the Resource Properties dialog box.
|Select the Server where you want to place the IP Address (typically this is referred to as the primary or template server). All the servers in your cluster are included in the drop down list.
| Enter the virtual IP address to protect. This is the IP address or symbolic name that LifeKeeper will use for this resource.
Not only a virtual IP address but also an actual IP address which is allocated for a network interface can be protected. If you protect an actual IP address, enter ’0.0.0.0’. When you protect the actual IP, the IP address which is allocated for the network interface you will select later will be protected.
A client connects to the IP address via the network interface which is configured later. If you use a symbolic name, it must exist in the local /etc/hosts file or be accessible via a Domain Name Service (DNS). Alias names and domain names are acceptable as long as they meet the criteria listed above. No defaults are provided for this information field.
Note: If you choose to use a symbolic name, be advised that when you extend this resource, the actual IP address will appear in one of the dialog boxes as the IP resource designation.
Note: When the actual IP address is used, you must allocate it to the physical network interface. Only IP v4 is supported for the actual IP resource.
| Select or enter the network mask, Netmask, which your IP resource will use on the target server. Any standard netmask for the class of the specific IP resource address is valid.
If you specify the actual IP address protection (’0.0.0.0’) in the IP resource field, this Netmask field will not appear.
Note: The netmask you choose, combined with the IP address, determines the subnet that will be used by the IP resource and should be consistent with the network configuration.
|Select or enter the Network Interface where your IP resource will be placed under LifeKeeper protection. This is the physical Ethernet card that the IP address is interfacing with. Valid choices will depend on the existing network configuration and values chosen for the IP resource address and netmask. The default value is the interface within the set of valid choices which most closely matches the address and netmask values you have selected.
|IP Resource Tag
| Select or enter a unique IP Resource Tag name for the IP resource instance you are creating.This field is populated automatically with a default tag name as described below.
Virtual IP address：ip-<resource> (<resource> is the resource name or IP address.)
Actual IP address：realip-<network interface> (This is the value which is selected in the Network Interface field.)
This tag can be changed if necessary.
- Click Create. The Create Resource Wizard will then create your IP resource.
- At this point, an information box appears and LifeKeeper will validate that you have provided valid data to create your IP resource hierarchy. If LifeKeeper detects a problem, an ERROR will appear in the information box. If the validation is successful, your resource will be created. Click Next.
- Another information box will appear explaining that you have successfully created an IP resource hierarchy, and you must Extend that hierarchy to another server in your cluster in order to place it under LifeKeeper protection.
When you click Continue, LifeKeeper will launch the Pre-Extend configuration task. Refer to the Extending Your Hierarchy topic for details on how to extend your resource hierarchy to another server.
If you click Cancel now, another dialog box will appear alerting you that you’ll need to come back and extend your IP resource hierarchy to another server at some other time to put it under LifeKeeper protection.