An engineer is troubleshooting a routed (Layer 3) EtherChannel between Switch-A and Switch-B. The output of `show etherchannel summary` on Switch-A displays the following status:
text
Group Port-channel Protocol Ports
------+------------+----------+-----------------------------------
10 Po10(SD) LACP Gi0/1(I) Gi0/2(I)
Flags: S - Layer3, D - Down, I - Stand-alone
Switch-A's physical interfaces GigabitEthernet0/1 and GigabitEthernet0/2 are configured with `no switchport` and `channel-group 10 mode active` under interface configuration mode.
Which remote configuration on Switch-B explains why the physical member interfaces on Switch-A remain in a stand-alone (I) state and the port-channel is down (SD)?
- Switch-B has configured member interfaces with `channel-group 10 mode auto`.Answer
- BSwitch-B has configured member interfaces with `channel-group 10 mode passive`.
- CSwitch-B has a native VLAN mismatch configured on interface GigabitEthernet0/1.
- DSwitch-B has assigned an IP address directly to member interface GigabitEthernet0/1 while leaving interface Port-channel10 unnumbered.
Answer
Switch-B has configured member interfaces with `channel-group 10 mode auto`.
The option stating that Switch-B has configured member interfaces with `channel-group 10 mode auto` is correct because `mode auto` enables PAgP negotiation. PAgP and LACP are mutually incompatible protocols; an LACP active interface will never form an EtherChannel with a PAgP auto interface, leaving local ports in the stand-alone (I) state.
Step-by-Step Solution
Key Concept
LACP vs PAgP Protocol Compatibility and Operational State Verification