The engineer configures port 1/2 on Leaf-101 and Leaf-102 to connect to a new server (SVR-12), which belongs to EPG-12 using VLAN-1212 encapsulation. The server is configured as a vPC member port and statically bound to EPG-12. The task is to ensure connectivity, indicating a missing configuration step.
Requirement Analysis
Static binding of a vPC member port to an EPG requires proper VLAN association and domain mapping.
vPC ensures redundancy, and the VLAN (1212) must be allocated and associated with the EPG via a domain (e.g., VMM or physical domain).
Option Evaluation
A. Create a VPC Explicit Protection Group for EPG-12 and VLAN-1212:
vPC Explicit Protection Groups are used for specific vPC configurations, but this is not a standard requirement for EPG binding and VLAN association.
[: Cisco ACI vPC Configuration Guide., B. Associate a domain with EPG-12 that is associated with VLAN-1212: , Associating a domain (e.g., VMM or physical domain) with EPG-12 and mapping VLAN-1212 ensures the VLAN is allocated and recognized by the fabric for the vPC ports. This is a critical step for static binding to work., Reference: Cisco APIC EPG Configuration Guide, "Domain and VLAN Association.", C. Select VLAN-1212 on the EPG-12 Interface Policy Group: , The Interface Policy Group defines port settings, but VLAN selection is managed via the domain association, not the policy group alone. This is insufficient., Reference: Cisco ACI Interface Policy Configuration Guide., D. Configure an LACP Interface Policy and apply it to EPG-12: , LACP is optional for vPC and not required for static EPG binding. The issue is VLAN/domain association, not link aggregation., Reference: Cisco ACI LACP Configuration Guide., Final Answer Justification, B is correct because associating a domain with EPG-12 and VLAN-1212 ensures the fabric recognizes the VLAN encapsulation and applies the EPG configuration to the vPC ports., Primary Cisco References: , Cisco APIC vPC Deployment Guide., Cisco ACI EPG and Domain Configuration Guide., , ]
Submit