Question 200
A data center administrator identifies the following risk: Two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list. Which root cause best explains this behavior?
Explanation
Correct Answer
The technical cause is The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The appropriate response is: Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms. Confirm successful repair: The host VLAN remains reachable through either peer after a simulated downstream member failure.
Incorrect Answers
The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” would address that alternative cause, not the condition in this question: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.
“Configure a matching supported LACP mode and port-channel membership across the two endpoints” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms”, so the alternative does not meet the stated condition.
The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” applies to that separate problem. The observed case is two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list; choosing this alternative would address the wrong failure mode.