Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May I know if there is any actual network performance impact to affected port even though the alert is a bug? Thanks.
Solved! See The Solution
1 ACCEPTED SOLUTION
georgewong2424 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi there,
In my experience, it doesn't. I was investigating this 3weeks ago for my environment because we noticed similar errors in VLAN level but not on ports or ifgrp level. If you run ifstat on port and ifgrp no errors but on lif (VLAN) there will be.
Hope that helps
2 REPLIES 2
georgewong2424 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi there,
In my experience, it doesn't. I was investigating this 3weeks ago for my environment because we noticed similar errors in VLAN level but not on ports or ifgrp level. If you run ifstat on port and ifgrp no errors but on lif (VLAN) there will be.
Hope that helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hello:
The bug ID is as follows in the link
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-Issues/CONTAP-86456
Generally speaking, this won't affect the network traffic. Use this command "system node run -node * -command ifstat -a" to observe whether the CRC error and Total errors are still increasing. If they are still increasing, clear the error message and it is recommended to replace the module of the faulty port.
i hope to help you.
Best regards.
