Skip to main content
NetApp Knowledge Base

AFF or FAS system does not detect partner causing failover

  1. Last updated
  2. Save as PDF
Views:
597
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • FAS systems
  • AFF systems

Issue

  • Takeover with no PANIC or NMI reported.
  • No CORE file triggered.
  • EMS logs show takeover due to no heartbeat detected. Example:

[Nodeb: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
[Nodeb: kernel: netif.linkDown:info]: Ethernet e0b: Link down, check cable.
[Nodeb: wafl_exempt17: nvmm.mirror.aborting:debug]: mirror of sysid 1, partner_type HA Partner and mirror state NVMM_MIRROR_ONLINE is aborted because of reason NVMM_ERR_IO.
...[Nodeb: cf_main: cf.fsm.takeover.noHeartbeat:alert]: Failover monitor: Takeover initiated after no heartbeat was detected from the partner node.
[Nodeb: cf_takeover: cf.fm.takeoverStarted:notice]: Failover monitor: takeover started
...

  • No issues noticed after giveback.

 

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.