What is the logging behavior for cluster peer unavailable and available state transitions?
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
-
- An EMS message is generated when a remote cluster transitions from available to unavailable:
- 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.unavailablemessage
- 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.
