Ifstat output reports long frames

Applies to

• All ONTAP versions
• All 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 

2. 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.