09-29-2016 10:39 AM - edited 03-01-2019 05:03 AM
During migration from Legacy to ACI fabric I have a ton of interfaces configured but not yet in use. This is resulting in some pretty bad health scores.
I can accept this during our transitional phase, but there will always be down ports in our production fabric. Dell Equallogics for instance physically down their stand-by interfaces and will always appear 'down' by the network gear.
Is there a way to have down ports ignored for health score calculation?
Thanks
Solved! Go to Solution.
09-29-2016 11:13 AM
The reason that fault code F0546 raises is due to a non-configured port or port not associated with EPG/Infra once had a neighboring device plugged in but was later unplugged. The switch is looking for a neighboring device since it previously had one. You could follow one of the two options to prevent F0546 from impacting the health score.
Option 1: Squelching fault code F0546. This should work on any ACI code release.
Log into the APIC GUI
Click on Fabric
Click on Access Policies
Click on Monitoring Policies
Click on default
Select Fault Severity Assignment Policies
Click on Edit icon
Select Physical Interface Runtime State (ethpm) (ethpm.PhysIf)
Submit
Click on Monitoring Object
Select Physical Interface Runtime State (ethpm) (ethpm.PhysIf)
Click Create
Select Code as F0546 [fltEthpmIfPortDownNoInfra]
Select Initial Severity as Squelched
Select Target Severity as Inherit
Click Update
Any future (non-configured) ports that go up/down will no longer raise the fault at all. Any F0546 code that is currently raised will require further action. You need to plug a device into the faulted port to clear it out. Unplugging the port (after the fault clears) should not raise the fault again. Reboot the leaf may actually clear the current faults too.
Option 2: Allow acknowledged faults to not have any weight on health score. This may require ACI code releases 1.2(2) and later.
2a. Log in to the APIC GUI and navigate to Fabric > Fabric Policies > Monitoring Policies > Common Policy > Health Score Evaluation Policies > Health Score Evaluation Policy
2b. In the properties pane, you will see “Ignore Acknowledged Faults”. Enable this setting.
2c. Go to the fault and check the “acknowledge” box.
The fault will still raise; however acknowledging the fault (and acknowledging any fault) will prevent the fault from weighing down the health score.
09-29-2016 10:43 AM
There are multiple fault codes for down interfaces. Could you provide the specific fault code that you see for the down interface?
Jason
09-29-2016 10:49 AM
Code F0546
Port is down, reason:notconnect(connected), used by:Discovery
|
09-29-2016 10:53 AM
Also F0532
Port is down, reason:notconnect(connected), used by:EPG
|
09-29-2016 11:13 AM
The reason that fault code F0546 raises is due to a non-configured port or port not associated with EPG/Infra once had a neighboring device plugged in but was later unplugged. The switch is looking for a neighboring device since it previously had one. You could follow one of the two options to prevent F0546 from impacting the health score.
Option 1: Squelching fault code F0546. This should work on any ACI code release.
Log into the APIC GUI
Click on Fabric
Click on Access Policies
Click on Monitoring Policies
Click on default
Select Fault Severity Assignment Policies
Click on Edit icon
Select Physical Interface Runtime State (ethpm) (ethpm.PhysIf)
Submit
Click on Monitoring Object
Select Physical Interface Runtime State (ethpm) (ethpm.PhysIf)
Click Create
Select Code as F0546 [fltEthpmIfPortDownNoInfra]
Select Initial Severity as Squelched
Select Target Severity as Inherit
Click Update
Any future (non-configured) ports that go up/down will no longer raise the fault at all. Any F0546 code that is currently raised will require further action. You need to plug a device into the faulted port to clear it out. Unplugging the port (after the fault clears) should not raise the fault again. Reboot the leaf may actually clear the current faults too.
Option 2: Allow acknowledged faults to not have any weight on health score. This may require ACI code releases 1.2(2) and later.
2a. Log in to the APIC GUI and navigate to Fabric > Fabric Policies > Monitoring Policies > Common Policy > Health Score Evaluation Policies > Health Score Evaluation Policy
2b. In the properties pane, you will see “Ignore Acknowledged Faults”. Enable this setting.
2c. Go to the fault and check the “acknowledge” box.
The fault will still raise; however acknowledging the fault (and acknowledging any fault) will prevent the fault from weighing down the health score.
09-29-2016 11:52 AM
F A N T A S T I C !
Thanks!
11-15-2017 02:06 PM
Would this squelch a Leaf to Spine port if that disconnected? That would be bad if you did not get the alert for a link like that dropping. What if a APIC dropped a link to a Leaf, would that be squelched as well?
11-15-2017 02:48 PM
In short, No.
This fault only pertains to interfaces which are not connected to spines, leafs, APICs
and
( have no access policies configured
or
have access policies configured but the interface does not have any EPG association).
If a link were to go down between spine and leaf, then fault below would raise.
-JW
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