FAS and V-Series Storage Systems Discussions

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hi,

 

i just upgraded to Ontap 9.5P4 and got the same issus:

: vifmgr.cluscheck.crcerrors: Port e0b on node is reporting a high number of observed hardware errors, possibly CRC errors.

 

opened a support case and will update.

 

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hello @miller ,

thanks for your message. We already have a support case opened, in our environment the presence of CRC errors seems the cause of link flapping on multimode_lacp interface groups.

net.ifgrp.lacp.link.inactive: ifgrp a0a, port e0c has transitioned to an inactive state. The interface group is in a degraded state.

This happens also when almost there's no traffic (our 9.5P3 systems are not yet in production) and not happens with high traffic systems with 9.1 , where the number of CRC is higher... 

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hello @miller 

since I am working on the support case for @LORENZO_CONTI would you please be able to share your support case with me?

A PM will be fine as well!

 

Thanks in advance.

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hi All,

 

We had same issue our customer and they changed jumbo frames on switch and netapp after that this issue was fixed. 

 

(FAS9000 , Ontap9.5P5)

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hi @buraksenturk , could you please explain better? What do you mean with "changed jumbo frames" exactly?
Thank you

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Hi @LORENZO_CONTI 

 

port set to switches 9000 and also port set netapp 9000.

 

thats example from customer;

 

switch;

  TX

    1916130391 unicast packets  2666708 multicast packets  20843127 broadcast packets

    1939643557 output packets  136406204523 bytes

    3331 jumbo packets

    3331 output error  0 collision  0 deferred  0 late collision

    0 lost carrier  0 no carrier  0 babble  0 output discard

    0 Tx pause

 

netapp;

 

RECEIVE

Total frames:      551m | Frames/second:     197  | Total bytes:     36893m

Bytes/second:    13145  | Total errors:     3372  | Errors/minute:       0

 Total discards:      0  | Discards/minute:     0  | Multi/broadcast: 23737k

Non-primary u/c:     0  | CRC errors:       3370  | Runt frames:         2

 Long frames:         0  | Alignment errors:    0  | No buffer:           0

 Pause:               0  | Jumbo:              42  | Noproto:             0

 Bus overruns:        0  | LRO segments:      100  | LRO bytes:       11072

 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

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

We have same Error since 5 Month, NetApp does not find a solution.
The port we have problems with, is e0M (Management).
e0M can not be higher than MTU 1500, Switch is configured too on MTU 1500 and with 1000 Mbps.


Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

PKoza can you post your ifstat output for that port?

 

Highlighted

Re: CRC-Error Messages seen since Ontap Upgrade to 9.3P7

Here it is attached.

Check out the KB!
NetApp Insights To Action
All Community Forums