Support of vPC on the Cisco Nexus 5000 access switch enables various new design options for the data center Access layer, including which of the following?

Question

Options

• AThe vPC peer link is not required for Access layer control traffic, and can instead be used to span
• BA single switch can associate per-interface with more than one vPC domain
• CvPC can be used on both sides of the MEC, allowing a unique 16-link EtherChannel to be built
• DAllows an EtherChannel between a server and a access switch while still maintaining the level of

• A
  3% (2)
• B
  5% (3)
• C
  80% (47)
• D
  12% (7)

Explanation

Answer C is correct. Virtual Port Channel (vPC) allows two Nexus switches to appear as a single logical switch to downstream devices. When vPC is used on both ends of a Multi-chassis EtherChannel (MEC) link - both at the server/access side and at the aggregation side - the result is a very large EtherChannel (theoretically up to 16 links) that spans across two physical switches on each side, significantly increasing bandwidth and redundancy. Option A is incorrect because the vPC peer link is required for control traffic (it carries BPDUs, IGMP, and other control plane information). Option B is wrong because a single switch can only belong to one vPC domain. Option D partially describes vPC's benefit but is not the specific new design option that vPC on Nexus 5000 uniquely enables.

No community discussion yet for this question.