nerdexam
Cisco

300-620 · Question #177

Refer to the exhibit. The Cisco ACI fabric has an egress L3Out from Leaf-101 and Leaf-102 to CORE-1. VLAN 102 is used to form the OSPF adjacency. The workloads must be migrated into EPG-101, and the s

The correct answer is D. Prune VLAN 101 from the VLAN pool that is used by the egress L3Out.. An MCP fault indicates a VLAN ID conflict, specifically when VLAN 101 is used for both an EPG's static binding and is also included in the VLAN pool associated with an L3Out.

External Network Connectivity

Question

Refer to the exhibit. The Cisco ACI fabric has an egress L3Out from Leaf-101 and Leaf-102 to CORE-1. VLAN 102 is used to form the OSPF adjacency. The workloads must be migrated into EPG-101, and the static port binding is configured to Leaf-103 e1/1 with encap VLAN 101. An engineer completes the port binding and receives an MCP fault. Which action clears the fault?

Exhibit

300-620 question #177 exhibit

Options

  • AUse VLAN 101 for OSPF adjacency on the egress L3Out.
  • BUse VLAN 102 as the encap VLAN on the EPG-101 static port binding.
  • CAdd VLAN 102 to the VLAN pool that is used by the static port binding.
  • DPrune VLAN 101 from the VLAN pool that is used by the egress L3Out.

How the community answered

(55 responses)
  • A
    15% (8)
  • B
    7% (4)
  • C
    35% (19)
  • D
    44% (24)

Why each option

An MCP fault indicates a VLAN ID conflict, specifically when VLAN 101 is used for both an EPG's static binding and is also included in the VLAN pool associated with an L3Out.

AUse VLAN 101 for OSPF adjacency on the egress L3Out.

Using VLAN 101 for OSPF adjacency on the L3Out would exacerbate the conflict, as VLAN 101 is already assigned to the EPG's static port binding.

BUse VLAN 102 as the encap VLAN on the EPG-101 static port binding.

Changing the EPG's encap VLAN to 102 would avoid the conflict by moving the EPG to a different VLAN, but it changes the EPG's intended VLAN and does not address the underlying configuration conflict.

CAdd VLAN 102 to the VLAN pool that is used by the static port binding.

Adding VLAN 102 to the VLAN pool used by the static port binding does not resolve the existing conflict involving VLAN 101.

DPrune VLAN 101 from the VLAN pool that is used by the egress L3Out.Correct

An MCP (Mis-Cabling Protocol) fault often arises from VLAN ID reuse or conflicts. If VLAN 101 is statically bound to EPG-101 and also present in the VLAN pool used by the egress L3Out, it creates an overlap causing the MCP fault. Pruning VLAN 101 from the L3Out's VLAN pool ensures its exclusive use by the EPG, resolving the conflict.

Concept tested: Cisco ACI VLAN ID conflict and MCP fault

Source: https://www.cisco.com/c/en/us/support/docs/data-center-virtualization/application-centric-infrastructure/212626-troubleshoot-aci-mcp-faults.html

Topics

#MCP fault#VLAN conflict#L3Out#EPG static binding#troubleshooting

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice