Creating a Resource Hierarchy
To create an LB Health Check resource, complete the following steps:
- Start the Create Resource Wizard as described in Creating Resource Hierarchies.
- Select LB Health Check as a Recovery Kit.
- Enter the following parameters.
| Field | Tips |
|---|---|
| Switchback Type | Specifies how the LB Health Check is switched back to this node when it recovers after a failover. You can select intelligent or automatic. |
| Server | Select the node on which you want to create a resource. All nodes in the cluster will appear in the drop-down list. |
| Reply daemon Port | Specify the port number that listens for connections from the load balancer. |
| Reply daemon Message | Specifies the reply string from the daemon (optional). |
| LB Health Check Resource Tag | Enter a unique tag name for the LB Health Check resource you are creating. The default tag name, lbhc-<port>, will automatically be populated in this field. <port> is the specified Reply daemon port. |
- Entering all parameters will start a daemon that listens for health check probes at the specified Port number to bring the LB Health Check resource ISP (In-Service, Protected). When LifeKeeper detects a problem, an error will appear in the information box or log file.
When the resource is created successfully, the Pre-Extend configuration task is started.
For details on extending the resource hierarchy to another node, see Extending Resource Hierarchies.
Delete a Resource Hierarchy
To delete a LB Health Check resource, refer to Deleting a Hierarchy from All Servers.
Extend the Resource Hierarchy
To extend the LB Health Check resource hierarchy, complete the following steps:
- Start the Extend Resource Hierarchy Wizard following the steps described in Extending Resource Hierarchies.
- Enter the following information in the Pre-Extend Wizard.
| Field | Tips |
|---|---|
| Switchback Type | Specifies how the LB Health Check resource is switched back to the destination node when it comes back after a failover. You can choose intelligent or automatic. |
| Template Priority | Enter the priority of the resource hierarchy for the source node. |
| Target Priority | Enter the priority of the resource hierarchy for the destination node. |
- CanExtend is run to verify that the extension requirements for the target LB Health Check resource are met.
- Enter the following parameter to extend the resource.
| Field | Tips |
|---|---|
| LB Health Check Resource Tag | Enter the LB Health Check resource tag. This is the resource tag name used by the LB Health Check resource being extended to the standby node. By default, the resource tag name on the source node is displayed. |
- To extend the same LB Health Check resource to another node in the cluster, click Next Server and repeat the process. Click Finish to confirm that the LB Health Check resource has been successfully extended.
Unextend the Resource Hierarchy
To unextend the LB Health Check resource, see Unextending a Hierarchy.
Change Resource Properties
The port number and response string of the LB Health Check resource can be changed later. First, take the LB Health Check resource to Out of Service, then change them for all servers in the [Resource Configuration] tab of the Properties Panel and bring the resource In Service. You can also change them with lkcli config following the same steps.
Post your comment on this topic.