Skip to main content
NetApp Knowledge Base

Increasing Fragment errors on an ethernet port

Views:
157
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
network
Last Updated:

Applies to

ONTAP 9

Issue

  • ONTAP reports the following message in event logs:

Thu Jul 08 00:17:37 PDT [node1: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0M on node node1 is reporting a high number of observed hardware errors, possibly CRC errors.

  • Ifstat output shows the Fragment error counters increasing.

cluster1::> system node run node1 -command ifstat e0M

-- interface  e0M  (17 hours, 44 minutes, 20 seconds) --

RECEIVE
 Total frames:    86428  | Frames/second:       1  | Total bytes:      6852k
 Bytes/second:      107  | Total errors:     1847  | Errors/minute:       2 
 Total discards:      0  | Discards/minute:     0  | Multi/broadcast: 65563 
 Non-primary u/c:     0  | CRC errors:          0  | Runt frames:         0 
 Fragment:         1847  | Long frames:         0  | Jabber:              0

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device