Skip to main content
NetApp Knowledge Base

Ethernet Link flapping on ONTAP node

  1. Last updated
  2. Save as PDF
Views:
7,310
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS systems
  • AFF systems
  • ONTAP 9

Issue

  • Port keeps going from up to down on the node:
[Node1: kernel: netif.linkUp:info]: Ethernet e0f: Link up.
[Node1: kernel: netif.linkDown:info]: Ethernet e0f: Link down, check cable.
  • If the port is a part of an ifgroup, then the ifgroup will be degraded with the message:

[Node1: intr: net.ifgrp.lacp.link.inactive:error]: ifgrp a0a, port e0f has transitioned to an inactive state. The interface group is in a degraded state.

  • EMS log reports the events:

[Node1: vifmgr: vifmgr.port.monitor.failed:error]: The "link_flapping" health check for port e0f (node Node1) has failed. The port is operating in a degraded state.
[Node1: vifmgr: vifmgr.port.monitor.passed:notice]: The "link_flapping" health check for port e0f (node Node1) has passed.
[Node1: vifmgr: vifmgr.portHealthy:notice]: The health status of port e0f (node Node1) has changed from degraded to healthy. This port can now be used for hosting LIFs.

  • The connected switch port will also show link flaps at the same time as the controller port

 

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.