Skip to main content
NetApp Knowledge Base

MetroCluster sync-destination SVM missing export-policy configuration

  1. Last updated
  2. Save as PDF
Views:
69
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster
  • SVM DR
  • NFS export-policy

Issue

  • The same export policy has a different RO, RW & SuperUser ID on the sync-source & sync-destination SVMs

Example:

  • Sync-source:

B::> export-policy rule show -vserver svm_B_1 -policyname nfs -fields rorule,rwrule,superuser

vserver    policyname ruleindex rorule rwrule superuser
-------    ---------- --------- ------ ------ ---------
svm_B_1    nfs        1         any    any    any
 

  • Sync-destination:

A::> export-policy rule show -vserver svm_B_1-mc -policyname nfs -fields rorule,rwrule,superuser

vserver    policyname ruleindex rorule rwrule superuser
-------    ---------- --------- ------ ------ ---------
svm_B_1-mc nfs        1         none   never  none
 

  • No errors reported by metrocluster switchover -simulate true
  • Switchover completes and an outage occurs due to the policy misconfiguration

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.