Skip to main content
NetApp Knowledge Base

Why are some LIFs are admin-up but operationally-down in a MetroCluster?

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

Applies to

  • MetroCluster
  • ONTAP 9

Answer

  • When a MetroCluster is operating normally, all of the LIFs hosted on a MetroCluster sync-destination vserver (denoted by the suffix '-mc' on the vserver name) are configured as admin-up, but operationally-down (up/down).
Example:
A LIF in up/down status:
ClusterA::> network interface show -status-oper down
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
svm1-mc
            nas_lif    up/down    1.2.3.4/24         ClusterA-01   e10a    true

 
Verifying that the vserver is a sync-destination vserver
ClusterA::> vserver show -vserver svm1-mc
                               Admin      Operational Root
Vserver     Type    Subtype    State      State       Volume     Aggregate
----------- ------- ---------- ---------- ----------- ---------- ----------
svm1-mc     data    sync-destination      stopped     svm1_root  aggr1
                               running                          
Note: The vserver is in the same state as the LIF (Admin State 'running', Operational State 'stopped')
  • This happens because the vserver and the LIFs are not brought up Operationally unless there is a metrocluster switchover operation.
  • This is normal and by design, there is no cause for concern.

Additional Information

If the LIFs in this state are not associated with a sync-destination vserver:

Please contact NetApp Technical Support or log into the NetApp Support Site to create a case. Reference this article for assistance with the solution. 

  • The solution requires Diagnostic-level recovery. 
  • The use of Diagnostic commands and recovery steps is potentially disruptive and should only be used with guidance from NetApp 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.