Lab-PT2a - 6.2.4 - Configure EtherChannel
Lab-PT2a - 6.2.4 - Configure EtherChannel
Objectives
Part 1: Configure Basic Switch Settings
Part 2: Configure an EtherChannel with Cisco PAgP
Part 3: Configure an 802.3ad LACP EtherChannel
Part 4: Configure a Redundant EtherChannel Link
Background
Three switches have just been installed. There are redundant uplinks between the switches.
As configured, only one of these links can be used; otherwise, a bridging loop might occur.
However, using only one link utilizes only half of the available bandwidth. EtherChannel
allows up to eight redundant links to be bundled together into one logical link. In this lab,
you will configure Port Aggregation Protocol (PAgP), a Cisco EtherChannel protocol, and
Link Aggregation Control Protocol (LACP), an IEEE 802.3ad open standard version of
EtherChannel.
Before beginning the configuration, review the EtherChannel Configuration Guidelines and
Restrictions listed at the end of this activity.
Instructions
Note: If the ports are configured with DTP dynamic auto mode, and you do not set the
mode of the ports to trunk, the links do not form trunks and remain access ports. The
default mode on a 2960 switch is for DTP to be enabled and set to dynamic auto. DTP
can be disabled on interfaces with the switchport nonegotiate command.
b. Use the show interfaces trunk command to ensure that you have an active trunk link
for those two links, and the native VLAN on both links is the same.
S1# show interfaces trunk
Port Mode Encapsulation Status Native vlan
F0/21 on 802.1q trunking 1
F0/22 on 802.1q trunking 1
G0/1 on 802.1q trunking 1
G0/2 on 802.1q trunking 1
<output omitted>
c. On S1 and S3, add ports F0/21 and F0/22 to Port Channel 1 with the channel-group 1
mode desirable command. The mode desirable option enables the switch to actively
negotiate to form a PAgP link. Note: Interfaces must be shutdown before adding them
to the channel group.
S1(config)# interface range f0/21 – 22
S1(config-if-range)# shutdown
S1(config-if-range)# channel-group 1 mode desirable
S1(config-if-range)# no shutdown
S3(config)# interface range f0/21 - 22
S3(config-if-range)# shutdown
S3(config-if-range)# channel-group 1 mode desirable
S3(config-if-range)# no shutdown
The message “Creating a port-channel interface Port-channel 1” should appear on both
switches when the channel-group is configured. This interface designation will appear
as Po1 in command output.
d. Configure the logical interface to become a trunk by first entering the interface port-
channel number command and then the switchport mode trunk command. Add this
configuration to both switches.
S1(config)# interface port-channel 1
S1(config-if)# switchport mode trunk
S3(config)# interface port-channel 1
S3(config-if)# switchport mode trunk
a. On switch S2, add ports F0/23 and F0/24 to Port Channel 3 with the channel-group 3
mode passive command. The passive option indicates that you want the switch to use
LACP only if another LACP device is detected. Statically configure Port Channel 3 as a
trunk interface.
S2(config)# interface range f0/23 - 24
S2(config-if-range)# shutdown
S2(config-if-range)# channel-group 3 mode passive
S2(config-if-range)# no shutdown
S2(config-if-range)# interface port-channel 3
S2(config-if)# switchport mode trunk
b. On S3, add ports F0/23 and F0/24 to Port Channel 3 with the channel-group 3 mode
active command. The active option indicates that you want the switch to use LACP
unconditionally. Statically configure Port Channel 3 as a trunk interface.
Port Channel 2 is not operative because Spanning Tree Protocol placed some ports into
blocking mode. Unfortunately, those ports were the Gigabit ports. In this topology, you
can restore these ports by configuring S1 to be primary root for VLAN 1. You could
also set the priority to 24576.
S1(config)# spanning-tree vlan 1 root primary
or
S1(config)# spanning-tree vlan 1 priority 24576
Close configuration window
You may have to wait for STP to recalculate the tree topology. Press fast-forward if
necessary. Use the show spanning-tree active command to verify that the Gigabit
ports are now in the forwarding state.
EtherChannel Configuration Guidelines and Restrictions
EtherChannel has some specific guidelines that must be followed in order to avoid
configuration problems.
1) All Ethernet interfaces support EtherChannel up to a maximum of eight interfaces
with no requirement that the interfaces be on the same interface module.
2) All interfaces within an EtherChannel must operate at the same speed and duplex.
3) EtherChannel links can function as either single VLAN access ports or as trunk links
between switches.
4) All interfaces in a Layer 2 EtherChannel must be members of the same VLAN or be
configured as trunks.
5) If configured as trunk links, Layer 2 EtherChannel must have the same native VLAN
and have the same VLANs allowed on both switches connected to the trunk.
6) When configuring EtherChannel links, all interfaces should be shutdown prior to
beginning the EtherChannel configuration. When configuration is complete, the links
can be re-enabled.
7) After configuring the EtherChannel, verify that all interfaces are in the up/up state.
8) It is possible to configure an EtherChannel as static, or for it to use either PAgP or
LACP to negotiate the EtherChannel connection. The determination of how an
EtherChannel is setup is the value of the channel-group number mode command.
Valid values are:
active LACP is enabled unconditionally
passive LACP is enabled only if another LACP-capable device is connected.
desirable PAgP is enabled unconditionally
auto PAgP is enabled only if another PAgP-capable device is connected.
on EtherChannel is enabled, but without either LACP or PAgP.
9) LAN ports can form an EtherChannel using PAgP if the modes are compatible.
Compatible PAgP modes are:
desirable => desirable
desirable => auto
If both interfaces are in auto mode, an Etherchannel cannot form.
10) LAN ports can form an EtherChannel using LACP if the modes are compatible.
Compatible LACP modes are:
active => active
active => passive
If both interfaces are in passive mode, an EtherChannel cannot form using
LACP.
11) Channel-group numbers are local to the individual switch. Although this activity
uses the same Channel-group number on either end of the EtherChannel
connection, it is not a requirement. Channel-group 1 (interface po1) on one switch
can form an EtherChannel with Channel-group 5 (interface po5) on another switch.