Delayed response to VCS commands observed on nodes with several resources and system has high CPU usage or high swap usage

Last published : Sep 23, 2026
You may experience a delay of several minutes in the VCS response to commands if you configure large number of resources for monitoring on a VCS node and if the CPU usage is close to 100 percent or swap usage is very high.
Some of the commands are mentioned below:
  • # hares -online
  • # hares -offline
  • # hagrp -online
  • # hagrp -offline
  • # hares -switch
The delay occurs as the related VCS agent does not get enough CPU bandwidth to process your command. The agent may also be busy processing large number of pending internal commands (such as periodic monitoring of each resource).
Workaround: Change the values of some VCS agent type attributes which are facing the issue and restore the original attribute values after the system returns to the normal CPU load.
  1. Back up the original values of attributes such as MonitorInterval, OfflineMonitorInterval, and MonitorFreq of IMF attribute.
  2. If the agent does not support Intelligent Monitoring Framework (IMF), increase the value of MonitorInterval and OfflineMonitorInterval attributes.
    \# haconf -makerw
    \# hatype -modify <TypeName> MonitorInterval <value>
    \# hatype -modify <TypeName> OfflineMonitorInterval <value>
    \# haconf -dump -makero
    Where <TypeName> is the name of the agent with which you are facing delays and <value> is any numerical value appropriate for your environment.
    1. If the agent supports IMF, increase the value of MonitorFreq attribute of IMF.
    \# haconf -makerw
    \# hatype -modify \<TypeName\> IMF -update MonitorFreq \<value\>
    \# haconf -dump -makero
Where \&lt;value\> is any numerical value appropriate for your environment.
  1. Wait for several minutes to ensure that VCS has executed all pending commands, and then execute any new VCS command.
  2. If the delay persists, repeat step 2 or 3 as appropriate.
  3. If the CPU usage returns to normal limits, revert the attribute changes to the backed up values to avoid the delay in detecting the resource fault.