A network engineer checks EtherChannel status on a switch and sees the following output:
Group Port-channel Protocol Ports ------+-------------+---------+----------------------------- 1 Po1(SD) LACP Gi1/0/1(s) Gi1/0/2(I)
What is the most likely reason the EtherChannel is not forwarding traffic?
Trap 1: The member interfaces have mismatched speed or duplex settings
Speed or duplex mismatches can definitely break an EtherChannel, which makes this option tempting. The problem is that the exhibit does not specifically prove that speed or duplex is the issue. It only proves that the links are not bundling correctly. On exam-style questions, choose the conclusion directly supported by the output before jumping to one of several possible hidden causes.
Trap 2: The port channel is Layer 3 instead of Layer 2
A Layer 3 port-channel can work perfectly well when intentionally configured that way, so the phrase 'Layer 3' does not explain the failure on its own. The real problem shown here is that the member interfaces are not joining the logical channel correctly. The status flags point to a bundle formation problem, not simply to the channel being Layer 3 or Layer 2.
Trap 3: LACP requires exactly four links to form a bundle
LACP does not require four links. Two-link EtherChannels are extremely common, and LACP can negotiate bundles with fewer than four member interfaces. The issue is not link count. The issue is that the displayed interfaces are not in a healthy bundled state.
- A
The member interfaces have mismatched speed or duplex settings
Why it fails: Speed or duplex mismatches can definitely break an EtherChannel, which makes this option tempting. The problem is that the exhibit does not specifically prove that speed or duplex is the issue. It only proves that the links are not bundling correctly. On exam-style questions, choose the conclusion directly supported by the output before jumping to one of several possible hidden causes.
- B
The port channel is Layer 3 instead of Layer 2
Why it fails: A Layer 3 port-channel can work perfectly well when intentionally configured that way, so the phrase 'Layer 3' does not explain the failure on its own. The real problem shown here is that the member interfaces are not joining the logical channel correctly. The status flags point to a bundle formation problem, not simply to the channel being Layer 3 or Layer 2.
- C
At least one member interface is not bundled correctly, so the logical channel is down
Correct. This is correct. The logical EtherChannel is down because the physical members are not properly bundled. The status display is telling you that the switch did not build a working aggregated link, so the port-channel cannot carry traffic as intended.
- D
LACP requires exactly four links to form a bundle
Why it fails: LACP does not require four links. Two-link EtherChannels are extremely common, and LACP can negotiate bundles with fewer than four member interfaces. The issue is not link count. The issue is that the displayed interfaces are not in a healthy bundled state.