EtherChannel - 1
EtherChannel - 1
EtherChannel is a technology developed by Cisco that allows you to bundle multiple physical Ethernet links
into a single logical link. This provides increased bandwidth and redundancy for network connections. If one
link in the bundle fails, traffic is automatically redistributed among the remaining links, ensuring continuous
connectivity.
1. Increased Bandwidth:
o Combines multiple physical links to act as one, providing higher throughput.
o For example, bundling four 1 Gbps links results in a theoretical 4 Gbps connection.
2. Redundancy:
o Ensures that if one link fails, the others in the bundle continue to handle traffic.
o Provides a fault-tolerant connection.
3. Load Balancing:
o Distributes traffic across the bundled links based on algorithms like source MAC, destination MAC, or
IP address.
4. Simplified Management:
o Treated as a single logical interface for configuration and monitoring.
5. Compatibility:
o Can be used in both Layer 2 (switches) and Layer 3 (routers) environments.
1. Connecting Switches:
o Increases bandwidth between switches in a LAN.
o Improves redundancy for uplinks.
2. Server Connections:
o Aggregates links between a switch and a server to enhance server performance.
3. Router Connections:
o Bundles links for higher throughput in WAN or inter-network connections.
Addressing Table
Background / Scenario
Link aggregation allows the creation of logical links that are comprised of two or more physical links. This provides
increased throughput beyond using only one physical link. Link aggregation also provides redundancy if one of the links
fails.
In this lab, you will configure EtherChannel, a form of link aggregation used in switched networks. You will configure
EtherChannel using Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP).
Note: PAgP is a Cisco-proprietary protocol that you can only run on Cisco switches and on switches that are licensed
vendors to support PAgP. LACP is a link aggregation protocol that is defined by IEEE 802.3ad, and it is not associated
with any specific vendor.
LACP allows Cisco switches to manage Ethernet channels between switches that conform to the 802.3ad protocol. You
can configure up to 16 ports to form a channel. Eight of the ports are in active mode and the other eight are in standby
mode. When any of the active ports fail, a standby port becomes active. Standby mode works only for LACP, not for
PAgP.
Note: The switches used with CCNA hands-on labs are Cisco Catalyst 2960s with Cisco IOS Release 15.0(2) (lanbasek9
image). Other switches and Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the
commands available and output produced might vary from what is shown in the labs.
Note: Make sure that the switches have been erased and have no startup configurations. If you are unsure, contact
your instructor.
Required Resources
• 3 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
• 3 PCs (Windows with terminal emulation program, such as Tera Term)
• Console cables to configure the Cisco IOS devices via the console ports
• Ethernet cables as shown in the topology
f. Assign cisco as the console and vty password and enable login.
g. Configure logging synchronous to prevent console message from interrupting command entry.
k. Configure the switch ports with attached hosts as access ports in VLAN 10.
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
The commands related to trunk configuration are the same. When the trunk commands were applied to the
EtherChannel, the commands also affected the individual links in the bundle.
b. Issue the show interfaces trunk and show spanning-tree commands on S1 and S3. What trunk port is listed? What
is the native VLAN? What is concluding result from the output?
___________________________________________________
The trunk port listed is Po1. The native VLAN is 99. After the links are bundled, only the aggregated interface is listed
in some show commands.
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32769
Address 0cd9.96e8.7400
Cost 12
Port 64 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0099
Spanning tree enabled protocol ieee
Root ID Priority 32867
Address 0cd9.96e8.7400
Cost 12
Port 64 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32769
Address 0cd9.96e8.7400
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0010
Spanning tree enabled protocol ieee
Root ID Priority 32778
Address 0cd9.96e8.7400
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0099
Spanning tree enabled protocol ieee
Root ID Priority 32867
Address 0cd9.96e8.7400
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
S1(config-if-range)# no shutdown
S2(config-if-range)# no shutdown
S3(config-if-range)# no shutdown
Reflection
What could prevent EtherChannels from forming?
___________________________________________________
Device Configs
Switch S1
S1# show vlan brief
Switch S2
Switch S3