The rlink disconnects because of temporary network glitch

  • Article ID:100026279
  • Modified Date:
  • Product(s):


The rlink  disconnects because of temporary network glitch


VVR uses a heartbeat mechanism to detect communication failures between the Primary and the Secondary hosts. The RLINKs connect after the heartbeats are exchanged between the Primary and the Secondary. The RLINK remains connected while the heartbeats continue to be acknowledged by the remote host. The maximum interval during which heartbeats can remain unacknowledged is known as the heartbeat timeout value. If the heartbeat is not acknowledged within the specified timeout value, VVR disconnects the RLINK.

The tunable vol_nm_hb_timeout enables you to specify the heartbeat timeout value. The default is 10 seconds. For a high latency network, increasing the default value of the tunable vol_nm_hb_timeout prevents the RLINKs from experiencing false disconnects.

The maximum value that you can set would be 60 seconds.

To display the current value of a tunable that is used by VxVM, use the following commands with the /proc file system:

# cat < /proc/sys/vxvm/vxio/vol_nm_hb_timeout


To change the value of a VxVM tunable, specify the new value using the vxvoltune command:

# vxvoltune vxvm_tunable value

eg.# vxvoltune vol_nm_hb_timeout 60

You must then shut down and reboot the system for the change to take effect. The new value persists across system reboots until it is next changed.

The vxvoltune utility modifies the tunable values stored in the /etc/vx/vxvm_tunables file. We recommend that you use the vxvoltune command to change the values stored in this file. Do not edit this file directly.

You can use the vxvoltune command to display the current values of a tunable parameter that is set in the vxvm_tunables file:

# vxvoltune vxvm_tunable


Was this content helpful?

Get Support