Skip to main content
NetApp Knowledge Base

How to increase the TCP receive window buffer size for Inter-Cluster and IntraCluster Volume SnapMirror

Last Updated:

Applies to

  • ONTAP 9
  • Clustered Data ONTAP 8


Inter-Cluster and IntraCluster SnapMirror uses the network service named ctlopcp

  • The ctlopcp service has a tunable TCP receive buffer window for Inter-Cluster and IntraCluster connections.
    • The Inter-Cluster TCP receive buffer window defaults to 2 MB, the IntraCluster TCP receive buffer window defaults to 256 KB.
    • The TCP receive buffer windows can be increased up to 7 MB, and can be decreased to 256 KB.
  • Increasing the Inter-Cluster TCP receive buffer window can increase the effective throughput when working with high-capacity WAN connections.
    • However, this may not be necessary due to the increased number of active TCP streams used for replication.
    • For more information, see Section 2.4 "Network Connections for Inter-Cluster SnapMirror" in TR-4015.
  • Inter-Cluster TCP receives buffer windows auto-tune by default.
    • These start at 64KB per TCP stream and grow to a maximum of the configured value (default 2MB) to accommodate InterCluster replications.
    • Once grown, the receive buffer window does not shrink as long as the TCP stream remains open.


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.