01-25-2017 02:30 AM - edited 03-01-2019 05:08 AM
Hi,
The error F1549 is currently occurring on our ACI platform. The file attached summarizes all the information I have collected.
But unfortunately, I can't find the cause of this issue
How to deal with this kind of error ? Any ideas to find out the root cause ?
APIC running version : 2.1(1h).
Thank you.
Ju
Solved! Go to Solution.
01-25-2017 08:52 AM
Any atomic counter stats are going to be unreliable for EX based switches. We have multiple bugs opened to track this (CSCvb89753 is a customer visible one). 2.1(1h) fixed some (not all) of these faults (or at least suppressed them). We verify that this isn’t causing problems in a couple of different ways:
-Verify that no drops are being seen on spine uplink ports
-Capture traffic on both source and dest of a flow and verify that everything is being received (provided there are performance complaints)
Until we get a complete fix for atomic counter reporting the only thing that we can suggest at this point is to squelch these faults. You won’t lose any functionality in doing this because atomic counters can’t be trusted as a reliable source of information at this point with EX switches.
01-25-2017 03:59 AM
Hi Ju
Is this a stretched fabric? If yes, these faults are kind of normal behavior:
Regards
Marcel
01-25-2017 08:48 AM
01-25-2017 07:26 AM
Are these EX series switches?
01-25-2017 08:37 AM
Yes Joseph. We have the following devices
LEAF101 - N9K-C93180YC-EX
LEAF102 - N9K-C93180YC-EX
SPINE201 - N9K-C9336PQ
SPINE202 - N9K-C9336PQ
Ju
01-25-2017 08:52 AM
Any atomic counter stats are going to be unreliable for EX based switches. We have multiple bugs opened to track this (CSCvb89753 is a customer visible one). 2.1(1h) fixed some (not all) of these faults (or at least suppressed them). We verify that this isn’t causing problems in a couple of different ways:
-Verify that no drops are being seen on spine uplink ports
-Capture traffic on both source and dest of a flow and verify that everything is being received (provided there are performance complaints)
Until we get a complete fix for atomic counter reporting the only thing that we can suggest at this point is to squelch these faults. You won’t lose any functionality in doing this because atomic counters can’t be trusted as a reliable source of information at this point with EX switches.
01-26-2017 12:28 AM
Hi Joseph,
I don't have any drops on spine uplink ports, hence I can wait the bug has been fixed.
Thank you for your explanation.
Regards,
Ju
06-28-2018 06:50 AM
I hate to dredge up an old thread, but is the atomic counters still an issue under the 3.1 and 3.2 trains? Thanks!
09-24-2018 04:37 AM
10-17-2018 01:30 AM
This is not clear to me, however I have seen these at least on 3.1.1x
Would be great to have an official statement here from Cisco.
12-22-2020 10:36 PM - edited 12-22-2020 10:38 PM
We are experiencing this same fault and we have FX switches. We already squelched the faults but it still keeps on reoccurring. Are atomic counters unreliable for FX switches as well ?
Could you share the link for the documentation on this?
We are running ACI 5.1(2e).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide