Cisco ACI Troubleshooting: Missing Directly Connected Leaf Switches

Troubleshooting Cisco ACI Environment: Fabric Membership Issue

Question

A Cisco ACI environment consists of three Cisco APICs, two spine switches, and four leaf switches.

The engineer erases and reboots all APICs first, then leaf and spine switches individually, and then completes the Initial Setup dialog on the APIC1 CIMC KVM console.

When the engineer logs in to the APIC1 web GUI, the engineer notices that there are no directly connected leaf switches being discovered under Fabric > Inventory > Fabric Membership.

What is the cause of the issue?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

In this scenario, the engineer erases and reboots all APICs first, then the leaf and spine switches individually, and finally completes the Initial Setup dialog on the APIC1 CIMC KVM console. However, when the engineer logs in to the APIC1 web GUI, they notice that there are no directly connected leaf switches being discovered under Fabric > Inventory > Fabric Membership.

The cause of the issue could be any of the following:

A. The leaf nodes were not erased properly, which caused a fabric parameters mismatch with the APIC1. If the leaf nodes were not erased properly, they might still contain the previous configuration, which could result in a fabric parameters mismatch with the APIC1. This could prevent the discovery of directly connected leaf switches under Fabric > Inventory > Fabric Membership.

B. Rebooting the APICs and the leaf and spine switches after wiping them is not required. Rebooting the APICs and the leaf and spine switches after wiping them is a standard procedure to ensure that the devices start with a clean slate. However, if this step was not required, it could still cause issues with the discovery of directly connected leaf switches.

C. The engineer did not enter the TEP Pool value during the Initial Setup dialog on APIC1. The TEP (Tunnel Endpoint) Pool is used for VXLAN traffic in a Cisco ACI environment. If the engineer did not enter the TEP Pool value during the Initial Setup dialog on APIC1, it could cause issues with the discovery of directly connected leaf switches.

D. The same Fabric Name value should be used before and after wiping all devices. The Fabric Name is used to identify the Cisco ACI fabric. If a different Fabric Name is used before and after wiping all devices, it could cause issues with the discovery of directly connected leaf switches.

To determine the cause of the issue, the engineer should check the fabric parameters on the APIC1 and the leaf switches. They should verify that the leaf switches have been properly erased and that the TEP Pool value was entered correctly during the Initial Setup dialog on APIC1. They should also verify that the same Fabric Name value was used before and after wiping all devices.