An EtherChannel bundles multiple physical links into a single logical interface, called a port channel.
You already built EtherChannels in the EtherChannel module of the CCNA path.
This module is about what happens when a bundle breaks, and how to fix it.
Before that, let's rebuild the foundation in one lesson.The Problem with Parallel Links
Plugging two cables between your switches should double the bandwidth.
It doesn't.Spanning Tree Protocol sees a Layer 2 loop between the switches and blocks the redundant link.

Figure 1 – Parallel links without EtherChannel
One link forwards, the other sits idle.
You pay for two links and use one.Answer the question below
Which protocol blocks the redundant link?
One Logical Interface
With EtherChannel, STP no longer sees two physical links.
It operates on one logical interface, so there is nothing to block.
Figure 2 – EtherChannel logical bundling
All member links forward at the same time, and your traffic is load balanced across them.
Failures behave differently too.
When a member link fails, the port channel stays up.
No STP recalculation, no topology change.
The bundle keeps forwarding on the remaining links.Answer the question below
Does STP operate on the physical links or the logical interface?
A port channel can be assembled statically or negotiated by a protocol.
You know all three from CCNA.Static Mode (On)
With static mode, your switch bundles the ports without asking the neighbor anything.

Figure 3 – Static EtherChannel (mode on)
No negotiation also means no health check.
If the other side is misconfigured, the static side bundles anyway.
It causes most of the failures you will troubleshoot in the next lesson.Answer the question below
Does static mode perform any health check with the neighbor?
PAgP: Desirable and Auto
PAgP (Port Aggregation Protocol) is Cisco proprietary.

Figure 4 – PAgP modes (desirable and auto)
An interface in desirable mode actively sends PAgP packets to negotiate the bundle.
An interface in auto mode stays quiet and only replies if the neighbor speaks first.
Answer the question below
Which PAgP mode initiates the negotiation?
LACP: Active and Passive
LACP (Link Aggregation Control Protocol) is the open standard, originally defined in IEEE 802.3ad and now maintained in IEEE 802.1AX.

Figure 5 – LACP modes (active and passive)
Active mode initiates the negotiation
Passive mode waits for it
LACP is the preferred choice today, even between Cisco switches, because it works across vendors.
Answer the question below
Which negotiation protocol is Cisco proprietary?
Two sides form an EtherChannel only if their channel-group modes are compatible.
Memorize these combinations.They are the first thing to check on a broken bundle.
PAgP Combinations
SW1's mode is on the left, SW2's mode on top:
SW1 / SW2
desirable
auto
desirable
✓
✓
auto
✓
✗
Table 1 – PAgP mode compatibility
Both sides in auto never form a bundle.
Nobody sends the first PAgP packet.Answer the question below
How many PAgP combinations form a working bundle?
LACP Combinations
Same logic, different names:
SW1 / SW2
active
passive
active
✓
✓
passive
✓
✗
Table 2 – LACP mode compatibility
Same trap with both sides in passive.
Nobody sends the first LACPDU.Answer the question below
In LACP, which mode waits for the negotiation?
Static and Mixed Protocols
Static mode has no matrix to learn.
On only works with on!And never mix the methods between the two sides:
on + any dynamic mode → the static side ignores the negotiation entirely
PAgP on one side, LACP on the other → two different languages, no agreement
The pattern is simple.
Same protocol on both sides, and at least one side initiates.Answer the question below
Do two interfaces in LACP passive mode form an EtherChannel?
You manage two switches, SW1 and SW2, connected through g0/0 and g0/1.
Your objective: bundle both links with LACP, carry VLAN 50 over the trunk, and verify the result.
This working bundle is your reference point for the whole module.
Figure 6 – LACP baseline lab topology
Building the Bundle
Start on SW1.
Assign the physical interfaces to channel group 1 in active mode.
Then configure the trunk on the port-channel interface.SW1# configure terminal SW1(config)# interface range g0/0-1 SW1(config-if-range)# channel-group 1 mode active Creating a port-channel interface Port-channel 1 SW1(config-if-range)# exit SW1(config)# interface po1 SW1(config-if)# switchport trunk encapsulation dot1q SW1(config-if)# switchport mode trunk SW1(config-if)# switchport trunk allowed vlan 50 SW1(config-if)# end %EC-5-L3DONTBNDL2: Gi0/0 suspended: LACP currently not enabled on the remote port. %EC-5-L3DONTBNDL2: Gi0/1 suspended: LACP currently not enabled on the remote port.Notice the message: the switch automatically creates the logical interface Port-channel 1 the moment you assign the first member.
All trunk settings go on the port channel, not on the member ports.The members inherit them.
Both members go suspended, and that is expected.
SW1 sends LACPDUs, but SW2 does not speak LACP yet.The ports wait in a suspended state until the other side answers.
Now configure SW2 as the passive side.
SW2# configure terminal SW2(config)# interface range g0/0-1 SW2(config-if-range)# channel-group 1 mode passive Creating a port-channel interface Port-channel 1 %LINK-3-UPDOWN: Interface Port-channel1, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up SW2(config-if-range)# exit SW2(config)# interface po1 SW2(config-if)# switchport trunk encapsulation dot1q SW2(config-if)# switchport mode trunk SW2(config-if)# switchport trunk allowed vlan 50 SW2(config-if)# endThe port channel comes up as soon as SW2 starts answering SW1's LACPDUs.
Active plus passive: a valid combination from Table 2.Reading a Healthy Summary
Now check the result.
Run show etherchannel summary on SW1.
SW1# show etherchannel summary Flags: D - down P - bundled in port-channel I - stand-alone s - suspended H - Hot-standby (LACP only) R - Layer3 S - Layer2 U - in use f - failed to allocate aggregator M - not in use, minimum links not met u - unsuitable for bundling w - waiting to be aggregated d - default port A - formed by Auto LAG Number of channel-groups in use: 1 Number of aggregators: 1 Group Port-channel Protocol Ports ------+-------------+-----------+----------------------------------------------- 1 Po1(SU) LACP Gi0/0(P) Gi0/1(P)Three things to check, in order:
S → the port channel runs in Layer 2 mode
U → the logical interface is in use and forwarding
(P) on each member → the port is bundled in the port channel
SU on the port channel, P on every member.
That is the signature of a healthy EtherChannel.Anything else (a D, an I, an s) means something went wrong.
Decoding those flags and fixing their causes is where the next lesson begins.Answer the question below
Which flag combination indicates a healthy Layer 2 port channel?