Refer to the exhibit. An engineer is configuring an EtherChannel between Switch1 and Switch2 and notices the console message on Switch2. Based on the output, which action resolves this issue?

Question

Exhibits

Options

• AConfigure less member ports on Switch2.
• BConfigure the same port channel interface number on both switches
• CConfigure the same EtherChannel protocol on both switches
• DConfigure more member ports on Switch1.

• A
  3% (1)
• B
  6% (2)
• C
  88% (29)
• D
  3% (1)

Explanation

EtherChannel Protocol Mismatch Explanation

When the console message on Switch2 indicates an EtherChannel compatibility error, it typically signals a protocol mismatch - one switch is configured with LACP (802.3ad) while the other uses PAgP, or one is set to "on" (static) while the other uses a negotiation protocol. Configuring the same EtherChannel protocol on both switches (C) resolves this because both ends must agree on how to negotiate and form the bundle, whether that's LACP, PAgP, or static mode.

Why the distractors are wrong:

• A (fewer ports on Switch2): The number of ports isn't the issue; a protocol mismatch will prevent the channel from forming regardless of port count.
• B (same port channel number): The port-channel interface number is locally significant only - Switch1 can use Po1 and Switch2 can use Po2 and still form a working EtherChannel.
• D (more ports on Switch1): Adding ports doesn't address a protocol incompatibility and won't resolve the console error.

Memory Tip: Think of EtherChannel protocols like languages - if Switch1 speaks "LACP" and Switch2 speaks "PAgP," they simply cannot communicate. Both switches must speak the same language (protocol) to form the channel successfully.

No community discussion yet for this question.