Brown Belt 20 min

Port-Channels on Cisco IOS XE Routers

Routers use port-channels differently than switches. Instead of carrying switched VLANs, they carry routed traffic with 802.1Q subinterfaces. Learn how to configure LACP bundles on router interfaces.

Key Difference: Routers vs. Switches

When you use port-channels on a switch, the port-channel acts like a single trunk and carries multiple switched VLANs.

When you use port-channels on a router, the port-channel is a routed interface. It has its own IP address, and you create 802.1Q subinterfaces on the port-channel to route between VLANs.

  • Switch port-channel: carries multiple VLANs, forwards at L2.
  • Router port-channel: routes traffic at L3, uses subinterfaces for multiple subnets.

Router Port-Channel Configuration (IOS XE)

Create a port-channel on a Cisco IOS XE router bundling GigabitEthernet0/0/0 and GigabitEthernet0/0/1, then add subinterfaces for VLANs 10 and 20:

interface Port-channel1
 ip address 10.0.0.1 255.255.255.252
 description Link-to-Switch

interface Port-channel1.10
 encapsulation dot1Q 10
 ip address 10.10.0.1 255.255.255.0
 description VLAN10-Subnet

interface Port-channel1.20
 encapsulation dot1Q 20
 ip address 10.20.0.1 255.255.255.0
 description VLAN20-Subnet

interface range GigabitEthernet0/0/0 - 1
 no ip address
 channel-group 1 mode active
 no shutdown

Key points:

  • The base port-channel (Port-channel1) gets an IP for management or inter-router traffic.
  • Subinterfaces (Port-channel1.10, Port-channel1.20) define each VLAN's subnet and gateway IP.
  • Member physical interfaces have no IP address — they just belong to the port-channel.
  • Each subinterface uses encapsulation dot1Q VLAN-ID to tag frames for that VLAN.

Why No IP on Member Interfaces?

On a router, physical interfaces bundled into a port-channel must be unnumbered (no IP address). They act purely as a transport layer, forwarding all traffic to the port-channel, which then routes it based on subinterface configuration.

If you add an IP address to a member interface, the router treats it as a separate interface and load-balancing breaks.

Verify Router Port-Channel

show etherchannel summary

Shows:

  • Group 1, Port-channel: Po1
  • Protocol: LACP
  • Members: Gi0/0/0(P), Gi0/0/1(P)
show ip interface brief

Shows all configured IP addresses:

  • Port-channel1: 10.0.0.1
  • Port-channel1.10: 10.10.0.1
  • Port-channel1.20: 10.20.0.1
show lacp neighbor

Confirms the remote switch (or router) has agreed to the same channel group.

Load-Balancing on Routers

Set the load-balancing method globally (same as switches):

port-channel load-balance src-dst-ip

This balances traffic based on source and destination IP addresses. Multiple flows to different destinations will use different physical links in the bundle.

Topology Example

A typical setup:

  • Switch (with port-channel trunk carrying VLANs 10, 20) ↔ Router (with port-channel + subinterfaces for VLANs 10, 20)
  • Devices in VLAN 10 send traffic to the switch, which tags it as VLAN 10 and forwards to the router.
  • Router receives the tagged frame on port-channel1.10, routes it based on the destination IP, and sends it to VLAN 20.
  • Switch receives the VLAN 20-tagged frame from the router and forwards it to devices in VLAN 20.

Common Mistakes

1. Adding an IP to member interfaces: Always keep member physical interfaces unnumbered. The port-channel handles all IP addressing.
2. Forgetting encapsulation dot1Q on subinterfaces: Without it, the router won't tag or untag VLAN traffic on that subinterface.
3. Mismatching subinterface numbers and VLAN IDs: It's a convention to name subinterface 1.10 for VLAN 10, but you must match the VLAN ID in the encapsulation dot1Q command. If they differ, routing breaks.
4. Using no shutdown inconsistently: Ensure physical member interfaces and the port-channel are not shut down. Subinterfaces inherit the administrative state of the parent port-channel.

Summary

  • Router port-channels are routed interfaces, not trunks. They have their own IP and routing logic.
  • Create the port-channel with an IP, add 802.1Q subinterfaces for each VLAN with its own subnet.
  • Member physical interfaces must be unnumbered (no IP address).
  • Use encapsulation dot1Q VLAN-ID on each subinterface to tag frames for that VLAN.
  • Verify with show etherchannel summary and show ip interface brief.
  • Set load-balancing globally with port-channel load-balance.