Refer to the exhibit. After an engineer configures an EtherChannel between switch SW1 and switch SW2, this error message is logged on switch SW2. Based on the output from SW1 and the log message recei

Question

Exhibits

Options

• AConfigure the same protocol on the EtherChannel on switch SW1 and SW2.
• BConnect the configuration error on interface Gi0/1 on switch SW1.
• CDefine the correct port members on the EtherChannel on switch SW1.
• DCorrect the configuration error on interface Gi0/0 switch SW1.

• A
  73% (11)
• C
  20% (3)
• D
  7% (1)

Explanation

EtherChannel Protocol Mismatch Explanation

Option A is correct because the error message logged on SW2 indicates an EtherChannel protocol mismatch - one switch is likely configured with LACP (IEEE 802.3ad) while the other is configured with PAgP (Cisco proprietary) or set to a static/incompatible mode. Both switches must use the same negotiation protocol (or both set to "on") for the EtherChannel bundle to form successfully.

Why the distractors are wrong:

• Option B is incorrect because the error is a protocol mismatch, not an interface-level configuration error on Gi0/1 specifically - and "connect" makes no logical sense in this context.
• Option C is incorrect because the port members are not the root cause; the ports can be correctly assigned to the channel group while still having a protocol conflict.
• Option D is incorrect for the same reason as B - the error is about protocol negotiation, not a misconfiguration isolated to interface Gi0/0.

Memory Tip

Think "same language, same conversation" - LACP and PAgP cannot negotiate with each other, just like two people speaking different languages. If SW1 speaks PAgP and SW2 speaks LACP, the EtherChannel will never form. Always verify protocol consistency on both ends.

No community discussion yet for this question.