Arctera

Handle planned change of secondary logowner (4114764)

To ensure proper hostname binding in VVR, vradmind on the primary logowner must be manually restarted when there is a planned change of the secondary logowner.

To avoid the manual restarting of vradmind service whenever the secondary logowner is changed, perform the following steps on all cluster nodes in both the VVR primary and secondary sites:

Add the following lines to /etc/vx/vras/vras_env and restart vradmind:

  • export VRAS_ENABLE_FBSL
  • VRAS_ENABLE_FBSL=on
Handle planned change of secondary logowner (4114764)

In this article