Skip to main content
NetApp Knowledge Base

metrocluster state show configuration-error

  1. Last updated
    Apr 14, 2025
  2. Save as PDF
Views:
43
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:
4/14/2025, 3:41:31 PM

Applies to

  • A300
  • ONTAP 9.7P6
  • MetroCluster IP

Issue

  • While replacing the motherboard of a node in the 4-node metrocluster, an issue occurred where all CNA ports were recognized as FC ports, causing the intercluster LIF composed of these CNA ports to be unable to communicate
  • After applying the following KB solution to change all FC ports back to CNA ports, the intercluster LIF has returned to normal
  • Although the intercluster LIF has returned to normal, the metrocluster status after replacing the motherboard are displayed as follows
Cluster_B::*> metrocluster show
 
Configuration: IP-fabric
 
Cluster                        Entry Name             State
------------------------------ ---------------------- ---------------------
Local: Cluster_B
Configuration State  configuration-error
Mode  -
AUSO Failure Domain  auso-on-cluster-disaster
Remote: Cluster_A
Configuration State  configuration-error
Mode  -
AUSO Failure Domain  auso-on-cluster-disaster
 
Cluster_B::*> metrocluster operation show
Operation: configure
State: failed
Start Time: 4/10/2025 13:40:09
End Time: 4/10/2025 13:40:11
Errors: Required mirrored non-root aggregates were not found in cluster "Cluster_B". MetroCluster configuration requires at least 2 mirrored non-root aggregates that are home, with at least 20GB of free space, in "online" state before running the configure command.
 
Cluster_B::*> metrocluster check node show
Cluster_B-02
node-reachable                       ok
metrocluster-ready                   ok
local-ha-partner                     ok
ha-mirroring-on                      ok
ha-mirroring-op-state                ok
symmetric-ha-relationship            ok
remote-dr-partner                    ok
dr-mirroring-on                      warning
dr-mirroring-op-state                warning
symmetric-dr-relationship            ok
remote-dr-auxiliary-partner          ok
symmetric-dr-auxiliary-relationship  ok
storage-failover-enabled             ok
has-intercluster-lif                 ok
node-object-limit                    ok
automatic-uso                        not-applicable
 
Cluster_B::*> metrocluster check node show -instance
 
Node Name: Cluster_B-02
Type of Check: dr-mirroring-on
Cluster Name: Cluster_B
Result of the Check: warning
Additional Information/Recovery Steps: Node's DR mirroring is not enabled. Check the RDMA Interconnect connectivity to its DR partner, run the "metrocluster node show" command to verify the node and its DR partner are up and normal, then enable the DR mirroring with the (privilege: diag) "metrocluster interconnect mirror modify -node <node> -partner-type DR -mirror-oper-status online" command.
 
Node Name: Cluster_B-02
Type of Check: dr-mirroring-op-state
Cluster Name: Cluster_B
Result of the Check: warning
Additional Information/Recovery Steps: Node's DR mirroring is not online. Check the RDMA connectivity to its DR partner, run the "metrocluster node show" command to verify the node and its DR partner are up and normal, then bring the DR mirroring online with the (privilege: diag) "metrocluster interconnect mirror modify -node <node> -partner-type DR -mirror-oper-status online" command.

 

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.