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.
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).
Refer to "PRIMECLUSTER Installation and Administration Guide" for configuration of monitoring GLS resource status for a standby node.
See the following procedure for recovering from a Gls resource failure following a transfer path failure on the standby node.
1) Recovering the transfer path where a failure has occurred
Restore the failed transfer path to the normal status (perform necessary work such as reconnecting the cable, powering on the switch/HUB again, and replacing the failed switch/HUB).
2) Clearing the Gls resource failure status
Clear the Gls resource failure status back to the original status by using "Cluster Admin" in Web-Based Admin View.
From this operation, the Gls resource for the standby node is reconfigured in a userApplication as the standby status.
