Jabber errors on ethernet port
Applies to
- FAS / AFF Systems
- ONTAP 9
Issue
- EMS report hardware errors on a physical and/or logical port.
[Node-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e2a on node Node-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[Node-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e2c on node Node-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[Node-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port a0a on node Node-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
- ifstat output show Jabber errors if ONTAP is receiving the errors.
-- interface  e2a  (104 days, 14 hours, 16 minutes, 20 seconds) --
RECEIVE
 Total frames:     2233m | Frames/second:     247  | Total bytes:       571g
 Bytes/second:    63198  | Total errors:    11352k | Errors/minute:      75 
 Total discards:      0  | Discards/minute:     0  | Multi/broadcast:  1962m
 Non-primary u/c:     0  | Errored frames:      0  | Unsupported Op:      0 
 CRC errors:          0  | Runt frames:         0  | Fragment:            0 
 Long frames:      4601  | Jabber:          11347k | Length errors:       0 
