VVR: VxVM 6.2.1 VVR nmcom_max_connections setting is not maintained after disconnect/reconnect of rlink

book

Article ID: 100046135

calendar_today

Updated On:

Description

Error Message

There are no error messages. The tunables settings would revert to the original values if the RLINK reconnects.

 

Cause

VVR 6.2.1 does not have a setting to force the nmcom_max_connections to be used during rlink disconnect/reconnect operations.  After a rlink disconnect, VVR in 6.2.1 reverts back to auto-tuning the number of TCP connections during the reconnect operation.

Resolution

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. 

Use these steps to set the 2 tunable values:

  1. Set nmcom_max_connections to the desired value.
    1. example:  vxtune nmcom_max_connections 16
  2. Set vol_vvr_force_connections to 1 to enable force of max tcp connections.
    1. example:  vxtune vol_vvr_force_connections 1

To disable the force max tcp connections tunable, set vol_vvr_force_connections to 0.

Note: the Hotfix are currently available for RHEL6 and RHEL7.

 

Issue/Introduction

The VVR (Veritas Volume Replicator) Primary node does not maintain the number of TCP connections set in the nmcom_max_connections setting after the rlink does disconnect-reconnect of the RLINK

Error Message

There are no error messages. The tunables settings would revert to the original values if the RLINK reconnects.
Powered by Wolken Software