Skip to main content
NetApp Knowledge Base

Why does cpeer.unavailable:alert occur even peering status is interface_reachable?

  1. Last updated
  2. Save as PDF
Views:
1,042
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.x
  • SnapMirror
  • Cluster peering

Answer

  • cluster peer ping and cluster peer health show are tools that show the current status 
  • This error can indicate a non-persistent network issue, Packet traces can reveal more details on the health of the Network
    • An example of a network issue is that older switch hardware may not be capable of handling the default amount of traffic from the NetApp InterCluster LIFs
    • Setting a snapmirror global replication throttle possibly may help with the over-saturated link, if older equipment has not or cannot be replaced
  • Note: Packet traces should capture an instance of the cpeer.unavailable:alert message from both source and destination clusters to be helpful in troubleshooting

Additional Information

 

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.