Skip to main content
NetApp Knowledge Base

Is it possible to bind FlexCache or SnapMirror traffic to a specific intercluster LIF within the same cluster peer?

Views:
164
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • FlexCache
  • SnapMirror

Answer

No. There is impossible to bind FlexCache or SnapMirror traffic to a specific intercluster LIF within the same cluster peer.

Additional Information

  • See the following best practices for more details:
  • SnapMirror configuration and best practices guide for ONTAP 9 
    • Intercluster networks are used by SnapMirror and other data protection solutions within the ONTAP environment.
    • All intercluster LIFs for a given SnapMirror relationship must be in the same IPspace. Different IPspaces can be used to peer with different clusters by using different intercluster LIFs.

Note: It is not possible to select a specific LIF pair to use for a replication event. All session management is performed automatically by the ONTAP session manager.

  • FlexCache in ONTAP :
    • The Remote Access Layer (RAL) is the function FlexCache software uses to enable loading and manipulation of content from any volume inside or outside of the cluster to the origin. 
    • When the RAL function is invoked, any operations that are ready to be forwarded to the origin are then redirected over the cluster interconnect LIFs between the nodes. 

 

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.