In a userApplication for standby operation, it is possible to monitor an operating node as well as a status of resource used in standby 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).
Note
When using GS/SURE linkage mode on a cluster system, the virtual interface for standby side is inactive so that the standby side stops monitoring the remote system. Due to this, it cannot monitor GLS resources on the standby node. Therefore, it is not necessary to configure "StandbyTransition" attribute while creating userApplication in GS/SURE linkage mode.
Refer to "6.6.2 Creating UserApplications" in "PRIMECLUSTER Installation and Administration Guide 4.1" for configuration of monitoring GLS resource status for a 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. (Use hvutil -c)
From this operation, GLS resource for standby node is reconfigured in a userApplication as a standby status.
