EtherChannel, also known as Port-Channel, is a technology that combines multiple physical switch ports into one logical interface. This bundling increases bandwidth while providing redundancy if one physical link fails. Configuration options include modes that automatically negotiate channels (such as LACP) or statically configure them. It is widely used between switches to ensure higher throughput and fault tolerance.
In this lab, we will configure an EtherChannel between Switch1 and Switch2 using LACP in active mode. The focus is on bundling interfaces Fa0/1 and Fa0/2 on each switch into Port-channel1, then verifying that the logical link is formed and operational.
Note: By default, creating a channel-group automatically generates the Port-Channel interface (e.g., Port-channel1). You can fine-tune it if needed.
On Switch1 and Switch2, after creating the channel group, you can configure additional parameters on the logical interface if desired (for example, forcing trunk mode). Below is a simple example on Switch1 (and similarly on Switch2, if needed):
Below are the key verification commands with explanation and actual console output one might see. (Outputs are typical and can vary slightly depending on IOS version.)
show etherchannel summary
Example Output:
show interfaces port-channel 1
Example Output:
Switch1# show interfaces port-channel 1
Port-channel1 is up, line protocol is up
Hardware is EtherChannel, address is 0001.6432.ab00 (bia 0001.6432.ab00)
MTU 1500 bytes, BW 2000000 Kbit/sec, DLY 10 usec
Full-duplex, 2000Mb/s, media type is SX
Member interfaces: Fa0/1, Fa0/2
Note: Bandwidth shown is aggregated logically, but depends on actual link speeds.
show run interface port-channel1
Example Output:
show run interface FastEthernet0/1
Example Output:
Mode/Protocol Mismatch
Symptom: Bundle doesn’t form; ports remain in stand-alone or suspended state.
Solution: Use compatible modes on both ends (e.g., LACP active↔active or active↔passive, or mode on↔mode on).
Interface Parameter Mismatches
Symptom: One or more member ports show as suspended in show etherchannel summary.
Causes:
Speed mismatch
Duplex mismatch
Switchport mode mismatch (access vs trunk)
VLAN mismatch (different access VLANs, or different trunk allowed VLAN lists)
Different native VLAN on trunk ports
STP setting mismatches (portfast, cost, priority, BPDU guard/filter)
Layer type mismatch (one side Layer 2, other Layer 3)
Solution: Ensure all member interfaces in the channel have identical Layer 1 and Layer 2 settings on both ends before adding them.
Add an Additional Interface to the Existing EtherChannel
Convert the Existing LACP Configuration to Static “On”