Skip to main content
NetApp Knowledge Base

Metrocluster AUSO triggered due to node reboot

  1. Last updated
  2. Save as PDF
Views:
161
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • Stretch MetroCluster
  • Fabric MetroCluster
  • Automatic Unplanned Switch Over (AUSO)

Issue

  • Callhome autosupport event triggered:

notifyd: callhome.mcc.auso.complete:alert]: Call home for METROCLUSTER AUTOMATIC UNPLANNED SWITCHOVER COMPLETE

  • EMS reports:

[<nodename>: DR_heartbeat_thread: mcc.auso.triggered:notice]: The node has triggered an Automatic Unplanned Switchover of the DR partner. Reason: DR partner node rebooted. If Automatic Unplanned Switchover was triggered because of heartbeat loss, any ongoing dump on the partner may be aborted

  • AUDIT-MLOG-TXT.GZ shows:

admin :: system node reboot

 

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.