200-155 · Question #93
What link aggregation technology could be used when configuring port-channels for connecting an access switch to vPC Domain?
The correct answer is D. LACP mode active. When connecting an access switch to a vPC domain, LACP configured in 'active' mode is the required link aggregation technology for forming port-channels, ensuring proper negotiation and redundancy.
Question
What link aggregation technology could be used when configuring port-channels for connecting an access switch to vPC Domain?
Options
- ADot1q
- BLACP mode on
- CPort Aggregation Protocol (PAgP)
- DLACP mode active
- ENonegotiate mode
How the community answered
(28 responses)- B7% (2)
- C4% (1)
- D89% (25)
Why each option
When connecting an access switch to a vPC domain, LACP configured in 'active' mode is the required link aggregation technology for forming port-channels, ensuring proper negotiation and redundancy.
Dot1q is a VLAN tagging standard and not a link aggregation technology used for forming port-channels.
'LACP mode on' is not a standard LACP configuration mode; LACP typically uses 'active' or 'passive' modes for negotiation.
PAgP (Port Aggregation Protocol) is a Cisco proprietary link aggregation protocol that is not supported or recommended for vPC deployments, which strictly require LACP.
For vPC (Virtual Port-Channel) domains in Cisco Nexus environments, LACP (Link Aggregation Control Protocol) is the mandatory protocol for bundling links into port-channels. Specifically, configuring LACP in 'active' mode on the access switch side ensures it actively negotiates with the vPC peers, properly forming the port-channel and enabling load balancing and failover.
'Nonegotiate mode' or EtherChannel without negotiation is not compatible with vPC, as vPC relies on LACP negotiation to manage the multi-chassis EtherChannel.
Concept tested: vPC port-channel LACP configuration
Source: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/N5K-CLI-Fundamentals/vPC.html
Topics
Community Discussion
No community discussion yet for this question.