Configuration to affect HealthScore with CRC errors

HealthScores a good way to monitor faults in ACI. But in certain cases, such as CRC errors the interface does not change state (up/down) therefore no fault is generated and consequently the HealthScore is not affected. In this case we can use the below steps to have the errors such as CRC, FCS affect the HealthScore.

Goto Fabric > Fabric Policies > Monitoring Policies > default > Stats Collection Policies

Then select “Layer 1Physical Interface Configuration” and then select “Ingress Drop Packets” (as shown below).

Stats-Collection-Policies

Click on the “Config Thresholds” + symbol and at the new pop-up wizard, edit the thresholds for “Ingress Errors Drop Packets rate”

Thresholds-For-Collection-5-Minute

Modify the values as needed for Rising

Edit-Stats-Threshold.jpg

This will count the packets drop (CRC) in a 5 min interval and raise a Fault when the threshold is hit and will affect the Health Score accordingly.

In the figure above, if there are 10 CRC errors in a 5 minute interval then a fault of Warning will be raised, if the count increases over 500 then a Minor fault will be raised and so on. You can change the counts as per your environment.

 


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.