Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.3Redundant Line Control Function

5.3.1 Monitoring resource status of standby node

In a userApplication for standby operation, it is possible to monitor standby node as well as a status of resource used in an operating node of GLS.

The following describes about monitoring GLS resource status of standby node.

5.3.1.1 Preface

Normally, a userApplication for standby operation does not monitor GLS resource status for standby node. In such case, even though a transfer path failure occurs in a standby node, the erroneous GLS resource remains to be unreleased and nothing is reported to the user. As a result, GLS resource error in standby node remains to be unsolved. To avoid this problem, GLS resource for standby node must be monitored with caution.

In order to monitor the GLS resource for a standby node, configure the "Standby Transition" when creating a userApplication.

Once the Standby Transition is successfully configured, it separates the erroneous GLS resource and reports the error to the user when a transfer failure occurs in a standby node. (This can be checked in "Cluster Admin" of Web-Based Admin View).

5.3.1.2 Configuration

Refer to "PRIMECLUSTER Installation and Administration Guide" for configuration of monitoring GLS resource status for a standby node.

5.3.1.3 Recovering from a resource failure in Standby node

See the following procedure for recovering GLS resource.

1) Recovering the transfer path failure

Restore the erroneous transfer path (Reconnecting the cable, restore the power of Switch/HUB, and replace the erroneous Switch/HUB)

2) Initializing GLS resource error

Clear the erroneous GLS resource status using "Cluster Admin" for Web-Based Admin View. (Use hvutil -c)
From this operation, GLS resource for standby node is reconfigured in a userApplication as a standby status.