Skip to main content
NetApp Stage KB

MetroCluster stack ID conflict

Views:
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

 

Applies to

  • Fabric-attached MetroCluster
  • ONTAP 9

Issue

  • One or more nodes report a stackmon.stack.id.conflict error in the event logs:
[Node-A: stackmon_thread: stackmon.stack.id.conflict:error]: Stack ID of the Shelf 30 (S/N SHFXXXXXXXXXX89) on channel Node101swb:8 cannot be agreed on by all the nodes in the cluster.
[Node-A: stackmon_thread: stackmon.stack.id.conflict:error]: Stack ID of the Shelf 70 (S/N SHFXXXXXXXXXX79) on channel Node100swa:8 cannot be agreed on by all the nodes in the cluster.  
  • The stack IDs for shelves in different stacks report the same stack ID:

Cluster1::> storage shelf show -fields shelf, shelf-id, stack-id
node    shelf stack-id shelf-id
-------- ----- -------- --------
C1_N1     3.50  3        50     <<< Shelf in correct stack
C1_N1     3.51  3        51     <<< Shelf in correct stack
C1_N1     3.60  3        60     <<< Shelf in incorrect stack
C1_N1     3.61  3        61     <<< Shelf in incorrect stack
C1_N1     3.70  3        70     <<< Shelf in incorrect stack
C1_N1     3.71  3        71     <<< Shelf in incorrect stack

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.
7afa749d-3b92-4c58-83ed-e3714a73221a