How to remove FAULT F0103 associated to the APIC eth2/1 and eth2/3 port being down?

In the Following case scenario, a customer’s APIC is reporting a Fault because the APIC port eth2/1 and eth2/3 is down. The Fault reported is “topology/pod-1/node-1/sys/cphys-[eth2/1] - Physical Interface eth2/1 on Node 1 is now down” and “topology/pod-1/node-1/sys/cphys-[eth2/3] - Physical Interface eth2/3 on Node 1 is now down”. This fault is commonly seen in ACI deployments since most installs do not utilize eth2/1 and eth2/3 port. Unfortunately, Fault F0103 is raised as a major fault.

APIC-PCIE-IQ10GC or UCSC-PCIE-IQ10GC can use any ports or any pair of ports to connect to a leaf node, but you must use eth2/2 for one cable and eth2/4 for another cable to the leaves, the eth2/1 and eth2/3 interfaces will remain in the admin up state and operationally down.

At this time, the only way to remove the fault is to change the “Administrative State” for the eth2/1 and eth2/3 port to “Down”. Unfortunately, a user can NOT disable the APIC eth2/1 and eth2/3 port from the admin APIC GUI. The following steps will show you how to show the port down manually using the APIC CLI.

APIC1# show faults code F0103 controller

Code??????: F0103

Severity????: major

Last Transition : 2023-02-14T11:51:22.942+00:00

Lifecycle????: soaking

DN???????: topology/pod-1/node-1/sys/cphys-[eth2/1]/fault-F0103

Description???: Physical Interface eth2/1 on Node 1 of fabric XXXX???

?????????with hostname APIC1 is now down????????????

Steps to Disable eth2/1 and eth2/3 port on an APIC using the CLI.?

The following note is written against Application Policy Infrastructure Controller Version: 5.2(x) The following information apply to earlier or later versions of Application Policy Infrastructure Controller firmware versions.?

1. Access the CLI of the APIC (use SSH or KVM console access)
2. Check to see if a FAULT F0103 is still present and associated with eth2/1 and eth2/3 port being down. Use the “show faults code F0103 controller” command.
3. Change directory to “/mit/topology/pod-1/node-1/sys/cphys-\[eth2--1\]”
4. Use the command “cat summary” to verify the “adminSt” is “up” and the “operSt” is “down” for eth2/1.
5. Use “MO” CLI commands to change the eth2/1 port’s “adminSt” to “down” (moset & moconfig).
6. Use the command “cat summary” to verify the “adminSt” is “down” and the “operSt” is “down” for eth2/1.
7. Check to see if FAULT F0103 has been cleared. Use the “show faults code F0103 controller” command. You may need repeat the command a couple times while the Fault is transitions states.

On APIC1:

cd /mit/topology/pod-1/node-1/sys/cphys-\[eth2--1\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

cd /mit/topology/pod-1/node-1/sys/cphys-\[eth2--3\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

On APIC2:

cd /mit/topology/pod-1/node-2/sys/cphys-\[eth2--1\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

cd /mit/topology/pod-1/node-2/sys/cphys-\[eth2--3\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

On APIC3:

cd /mit/topology/pod-1/node-3/sys/cphys-\[eth2--1\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

cd /mit/topology/pod-1/node-3/sys/cphys-\[eth2--3\]

cat summary

moset adminSt "down"

moconfig commit

cat summary

verify again the fault with "show faults code F0103 controller"

APIC1# show faults code F0103 controller

Code??????: F0103

Severity????: cleared

Last Transition : 2023-02-14T11:58:57.895+00:00

Lifecycle????: retaining

DN???????: topology/pod-1/node-1/sys/cphys-[eth2/1]/fault-F0103

Description???: Physical Interface eth2/1 on Node 1 of fabric XXX??

?????????with hostname APIC1 is now down?????