Skip to main content
NetApp Knowledge Base

MAUSO fails after MetroCluster IP site disaster

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

Applies to

  • MetroCluster IP
  • ONTAP 9
  • ONTAP Mediator

Issue

  • After a disaster at one of the MetroCluster sites, a MAUSO is initiated but fails

Mon Sep 25 11:52:58 +0200 [ClusterA-01: DR_heartbeat_thread: mcc.auso.trigFailed:EMERGENCY]: A trigger for Automatic Unplanned Switchover failed to issue the operation. Reason: Switchover job could not be started.
Mon Sep 25 11:52:58 +0200 [ClusterA-01: DR_heartbeat_thread: callhome.mcc.auso.trig.fail:EMERGENCY]: Call home for METROCLUSTER AUSO TRIGGER FAILED

  • One of the nodes at the surviving site loses it's Mediator iSCSI session

Sep 25 11:52:38 +0200 [ClusterA-02: kernel: iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting (destroy sim) for the target iqn.2012-05.local:mailbox.target.<uuid>:1 (type: mailbox, address: <IP>). Reason: session timed out 2 times waiting for iscsid(8).

  • The node then self-halts at the same time

Mon Sep 25 11:52:38 +0200 [ClusterA-02: fmmbx_instanceWorker: kern.shutdown.initiator:debug]: SK reboot was initiated by "maytag.ko::mia_mccip_local_write_partial_fail+568".

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.