VCS does not honour the value for VCS_GAB_RMTIMEOUT variable in VCS 5.1

book

Article ID: 100025328

calendar_today

Updated On:

Description

Error Message

2011/07/14 10:00:23 VCS NOTICE V-16-1-11057 GAB registration monitoring timeout set to 200000 ms

Cause

The value of VCS_GAB_RMTIMEOUT is specified in milliseconds, and minimum value of VCS_GAB_RMTIMEOUT is 200000 milliseconds (200 seconds). If VCS_GAB_RMTIMEOUT is less than the minimum value of VCS_GAB_RMTIMEOUT then VCS overrides and set it to 200000 milliseconds (200 seconds).

It is not reflected correctly in the documentation (VCS Administrator's Guide, formerly called VCS User's Guide).

Resolution

Specify the value in milliseconds. To set the value of VCS_GAB_RMTIMEOUT to 900 seconds (900000 milliseconds), set the following in /opt/VRTSvcs/bin/vcsenv file and restart the cluster.


# grep VCS_GAB_RMTIMEOUT "/opt/VRTSvcs/bin/vcsenv"
VCS_GAB_RMTIMEOUT=900000  
#  

 Once this is set and VCS engine restarted on the node, engine_A.log shows the correct value.
 

2011/07/14 15:53:50 VCS NOTICE V-16-1-11057 GAB registration monitoring timeout set to 900000 ms  
 

Applies To

All system running VCS 5.1 (and above)

Issue/Introduction

Veritas Cluster Server (VCS) refers to the value of VCS_GAB_RMTIMEOUT variable to set the Timeout (in milliseconds) for High Availability Daemon (HAD) to register with GAB. VCS does not honour the value for VCS_GAB_RMTIMEOUT variable in VCS 5.1. In spite of setting a new value for VCS_GAB_RMTIMEOUT variable in /opt/VRTSvcs/bin/vcsenv file and restarting the cluster, VCS still sets this value to the default value of 200 seconds (200000 ms).

Additional Information

ETrack: 2435437 ETrack: 2444653