Skip to main content
NetApp Knowledge Base

Ifstat output reports long frames

Views:
2,245
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP
  • FAS/AFF platforms

Issue

  1. Long frames can be seen in the output of ifstat
-- interface  e1d  (5 days, 13 hours, 44 minutes, 30 seconds) --

RECEIVE
 Total frames:      438k | Frames/second:       1  | Total bytes:     32232k
 Bytes/second:       67  | Total errors:    32047  | Errors/minute:       4 
 Total discards:      0  | Discards/minute:     0  | Multi/broadcast:   561k
 Non-primary u/c:     0  | CRC errors:          0  | Runt frames:         0 
 Long frames:     32047  | Length errors:       0  | Alignment errors:    0 
 No buffer:           0  | Pause:               0  | Jumbo:               0 
 Noproto:             0  | Bus overruns:        0  | LRO segments:        0 
 LRO bytes:           0  | LRO6 segments:       0  | LRO6 bytes:          0 
 Bad UDP cksum:       0  | Bad UDP6 cksum:      0  | Bad TCP cksum:       0 
 Bad TCP6 cksum:      0  | Mcast v6 solicit:    0 
  1. Either of the below events can be logged in EMS, depending on the ONTAP version
    • [Node1: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1d on node Node1 is reporting a high number of observed CRC errors.
    • [Node1: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1d on node Node1 is reporting a high number of observed hardware errors, possibly CRC errors.
 

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support