cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

1890
Views
10
Helpful
4
Replies
montgomerywr
Beginner

Cisco ACI F0546 Fault Code

Does anyone know of any way to remove the F0546 fault code by any other means than squelching all faults with this code?

 

F0546: fltEthpmIfPortDownNoInfra

Explanation: This fault occurs when a port goes down

Recommended Action: If you see this fault, take the following actions
  1. Check the port connectivity
  2. Administratively shut the port if the port is not in use
  3. For mcp-loop-err-disable, this could be due to a loop in the network. Check the config to resolve any loops
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

 

It appears that this fault is created when a cable is connected to an interface that does not have a configuration.  At that point, ACI learns (by discovery) that something is connected to the interface.  But when it is removed, the interface will forever have a health score <100.

 

During migration, technicians connected some cables to the wrong interfaces & then after they were correctly placed in the correct interfaces; we're left with this fault code.  I'm hesitant to squelch it completely as it may be helpful in the future if some techs get a little hasty with their work.

 

Any ideas?

 

4 REPLIES 4
Nik Noltenius
Beginner

Hi,

 

have you considered administravely shutting down the ports in question? This should clear the fault.

The fault will return when they are brought back up but then again there is no real reason to bring them back up unless something will connect to them.

We generally disable all unused ports at most of our ACI customers.

 

Regards,

Nik

Maurlai
Beginner

Hi montgomerywr,

   the way is to squelch it (with Ignore Fault right mouse button) and late delete the squelch raw under Fabric-Access Policies-Policies-Monitoring-default-Fault Severity Assignment Policies.

 

This procedure delete the entry for the discovery.

 

 

Hello Team,

squelching a fault is not the right way , any other ways to fix this fault ?

I opened a TAC case a while back, the answer from TAC is that you have to "call" TAC to clear this error for you, as they cannot release the tool to clients.
We upgraded to 4.1.1j which fixed this annoying problem.
Content for Community-Ad