Skip to main content
NetApp Knowledge Base

IFGRP Tx 'Lagg drops' count increasing during its member port link flapping

  1. Last updated
  2. Save as PDF
Views:
371
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9.7
  • IFGRP

Issue

  • Ifgrp's physical member port link flapping:

Wed May 24 13:38:22 +0900 [nodename: intr: pvif.lacp.outofsync:alert]: ifgrp a1a, port e0e cannot synchronize with the LACP aggregate.
Wed May 24 13:39:48 +0900 [nodename: intr: net.ifgrp.lacp.link.active:notice]: ifgrp a1a, port e0e has transitioned to the active state.
Wed May 24 13:43:19 +0900 [nodename: intr: net.ifgrp.lacp.link.inactive:error]: ifgrp a1a, port e0e has transitioned to an inactive state. The interface group is in a degraded state.
Wed May 24 13:43:35 +0900 [nodename: intr: net.ifgrp.lacp.link.active:notice]: ifgrp a1a, port e0e has transitioned to the active state.

  • Ifgrp a1a and it's vlan ports raised EMS event vifmgr.cluscheck.crcerrors:alert:

Wed May 24 13:45:17 +0900 [nodename: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a1a on node nodename is reporting a high number of observed hardware errors, possibly CRC errors.
Wed May 24 13:45:17 +0900 [nodename: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a1a-65 on node nodename is reporting a high number of observed hardware errors, possibly CRC errors.
Wed May 24 13:45:17 +0900 [nodename: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a1a-928 on node nodename is reporting a high number of observed hardware errors, possibly CRC errors.
Wed May 24 13:45:17 +0900 [nodename: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a1a-130 on node nodename is reporting a high number of observed hardware errors, possibly CRC errors.
Wed May 24 13:45:17 +0900 [nodename: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port a1a-623 on node nodename is reporting a high number of observed hardware errors, possibly CRC errors.

  • IFSTAT-A shows Ifgrp a1a Transmit side  Lagg drops  count increased:

-- interface  a1a  (0 hours, 4 minutes, 42 seconds) --
TRANSMIT
 Total frames:      100  | Frames/second:       0  | Total bytes:     14380
 Bytes/second:       51  | Total errors:        5  | Errors/minute:       1
 Total discards:      0  | Queue overflow:      0  | Multi/broadcast:    82
...
 Mcast v6 solicit:    0  | Lagg drops:          5  | Lagg no buffer:      0
 Lagg no entries:     0
DEVICE
 Mcast addresses:     0  | Rx MBuf Sz:          0
LINK INFO
 Speed:              n/a | Duplex:             n/a | Flowcontrol:        n/a
 Media state:     active | Up to downs:          1 | HW assist:        5654

  • Lagg drops  count stop increase after port link status getting stable.

 

 

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.