Skip to main content
NetApp Knowledge Base

Cluster Peer availability Pending after upgrade to ONTAP 9.5 and higher

Views:
2,074
Visibility:
Public
Votes:
1
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • Cluster peering

Issue

  • Immediately following ONTAP upgrade to 9.5 or higher cluster peer availability state is Pending.

:*> cluster peer show
Peer Cluster Name         Cluster Serial Number Availability   Authentication
------------------------- --------------------- -------------- --------------
< cluster name >           < serial >           Pending        ok  

  • In a Metrocluster the ability to switchover will not work without a healthy peer relationship.

::*> metrocluster show

Cluster                        Entry Name             State
------------------------------ ---------------------- ---------------------
Local: < cluster name >
                                 Configuration State  configured
                                                Mode  normal
                                 AUSO Failure Domain  auso-on-cluster-disaster
Remote: < cluster name >
                                 Configuration State  not-reachable
                                                Mode  -
                                 AUSO Failure Domain  not-reachable

 

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.