The secondary vradmind may appear hung and the vradmin commands may fail (3940842,3944301)

Last published : Sep 09, 2026
The secondary vradmind daemon may appear to be hung and the vradmin commands may fail, even if the replication is ON.
This issue is observed in cases where heavy I/Os are in progress.
To address the heavy I/Os, the secondary vradmind continues to perform certain IOCTLs and hence fails to respond to the heartbeat from the primary vradmind. As a result, the connection between the two vradmind is lost. This behavior continues during the next connection attempts too, due to which the vradmin commands fail and the secondary vradmind appears hung.
Workaround:
On both the sites, modify the /etc/vx/vras/vras_env file to resolve the issue. Make the following edits:
  • Uncomment the following commands:
    \#export VRAS_ENABLE_STATS
    \#VRAS_ENABLE_STATS=on
    and
    \#export IPM_HEARTBEAT_TIMEOUT
    \#IPM_HEARTBEAT_TIMEOUT=30
  • Set the VRAS_ENABLE_STATS to OFF
  • Increase the IPM_HEARTBEAT_TIMEOUT value
After you modify the files, restart the vradmind daemon on both the sites:
/usr/sbin/vxstart_vvr stop
/usr/sbin/vxstart_vvr start
Related information
Replication known issues