Ethernet Link flapping on ONTAP node
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.
-
[vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node1, port e0h [vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a0b on node Node1 is reporting a high number of observed hardware errors, possibly CRC errors. [vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a0b-4000 on node Node1 is reporting a high number of observed hardware errors, possibly CRC errors. [vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a0b-13 on node Node1 is reporting a high number of observed hardware errors, possibly CRC errors.
-
- The connected switch port will also show link flaps at the same time as the controller port