350-601 · Question #265
An engineer configured an environment that contains the vPC and non-vPC switches. However, it was noticed that the downstream non-vPC switches do not receive the same STP bridge ID from the upstream…
The correct answer is B. Peer-switch. The vPC peer switch is introduced to address performance concerns around these STP convergence events. This feature allows a pair of Cisco Nexus 7000 Series devices to appear as a single STP root in the Layer 2 topology. In the vPC peer switch mode, STP BPDUs are sent from both…
Question
An engineer configured an environment that contains the vPC and non-vPC switches. However, it was noticed that the downstream non-vPC switches do not receive the same STP bridge ID from the upstream vPC switch peers. Which vPC feature must be implemented to ensure that vPC and non-vPC switches receive the same STP bridge ID from the upstream vPC switch peers?
Options
- ASystem-mac 0123.4567.89ab
- BPeer-switch
- CVPC local role-priority 4000
- DPeer-gateway
How the community answered
(23 responses)- A13% (3)
- B74% (17)
- C4% (1)
- D9% (2)
Explanation
The vPC peer switch is introduced to address performance concerns around these STP convergence events. This feature allows a pair of Cisco Nexus 7000 Series devices to appear as a single STP root in the Layer 2 topology. In the vPC peer switch mode, STP BPDUs are sent from both vPC peer devices. This behavior also avoids issues related to STP BPDU timeout on the downstream switches, which can cause traffic disruption. The vPC peer switch feature eliminates the need to pin the STP root to the vPC primary switch and improves vPC convergence if the vPC primary switch fails. It is important to note that the vPC peer switch is needed only when the STP root needs to be placed on the vPC pair of devices.
Topics
Community Discussion
No community discussion yet for this question.