Skip to main content
NetApp Knowledge Base

What is the logging behavior for cluster peer unavailable and available state transitions?

Views:
13
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • Cluster peering environment
  • SnapMirror replication

Answer

When the cpeer.unavailable alert is triggered in ONTAP, the following logging behavior applies:
  • Unavailable State Logging:
    • An EMS message is generated when a remote cluster transitions from available to unavailable:
      •  cpeer.unavailable:ALERT]: Peer cluster <cluster_name> is no longer available
  • Available State Logging:
    • No EMS message is generated when the remote cluster returns to available state
    • The transition to available is implicit between each cpeer.unavailable message
  • Recovery Time Identification:
    • There is no explicit log entry recording the recovery timestamp
    • No configuration option exists to enable additional logging for recovery events
    • Recovery time cannot be directly determined from ONTAP logs
  • Recommended Verification Commands:
    • After a cpeer.unavailable alert, verify cluster peer and object store health using:

::> cluster peer show

::> system health status show

::> snapmirror show-history

::> storage aggregate object-store show

    Note: When Availability displays as available in the output, the object store is accessible and functioning normally.

    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.