Using vxrlink to diagnose buffer space-related network issues

  • Modified Date:
  • Article ID:000066015


Using vxrlink to diagnose buffer space-related network issues

The amount of buffer space available for requests coming in to the Secondary over the network is determined by the Veritas Volume Replicator (VVR) tunable, vol_max_nmpool_sz, which defaults to 16 megabytes. VVR allocates separate buffer space for each Secondary RVG, the size of which is equal to the value of the tunable vol_max_nmpool_sz. The buffer space on the Secondary must be large enough to prevent slowing the network transfers excessively. If the buffer space on the Secondary is too small, the replicated data is discarded and memory errors are returned back to the Primary.

While replication is active at the peak rate, run the vxrlink stats command and make sure there are no memory errors and the number of timeout errors is small:

# vxrlink -g dg1 -i5 stats rlink1

See Using vxrlink to diagnose network issues

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)