Because the GDS I/O Monitor Option assures the I/O response time, it is equiped with hang-up monitoring functions to monitor whether or not the GDS daemon or driver is hung-up.
The hang-up monitoring function monitors whether or not the sdxservd daemon and the sfdsk driver of the current node are hung-up, and if a hang-up is detected it panics the current node.
The hang-up monitoring function checks the status of the daemon and driver at a 46 seconds monitoring interval, if there is no response within the 23 second judgement time it will be determined to be hung-up.
If a value other than the default value is set for the I/O response time, change the monitoring interval and judgement time parameter of the hang-up monitoring function as follows:
Item | Parameter Name | Explanation |
---|---|---|
Monitoring Interval | SDX_HCHK_INTERVAL | The time interval (seconds) after monitoring has finished before the next monitoring start. |
Conclusion Time | SDX_HCHK_CRITERION | Time (seconds) after monitoring has been started before it is judged to be hung-up. |
Change the setting parameters in the GDS settings file /etc/opt/FJSVsdx/sdx.cf, or add parameter settings.
Example) If setting the monitoring time interval to 48 seconds and the judgement time to 24 seconds
SDX_HCHK_INTERVAL=48
SDX_HCHK_CRITERION=24
Restart the system. Or execute the following command.
# svcadm restart svc:/milestone/fjsvsdxhealth:default
After restarting the system or service with step 2, check that the service is operating.
# svcs svc:/milestone/fjsvsdxhealth:default
STATE STIME FMRI online 10:15:54 svc:/milestone/fjsvsdxhealth:default
Note
No monitoring is done in single user mode.