Aggregate EtherChannel Quality of Service

Updated: April 24, 2026

Want to summarize with AI?

Introduces Aggregate EtherChannel QoS concepts, listing prerequisites, restrictions, configuration steps using CLI templates, and commands for verification to ensure optimal service quality on aggregated links.

The Aggregate EtherChannel Quality of Service (QoS) is a EtherChannel-related feature that

improves quality of service on a port channel main interface or subinterface,
effectively manages network parameters such as delay, jitter, bandwidth, and packet loss, and
allows the application of an aggregate egress-queuing policy-map on the main or sub-interface of a port channel.

The Aggregate EtherChannel QoS facilitates QoS support on the aggregate port channel's main interface on Cisco IOS XE Catalyst SD-WAN device.

Prerequisites for Aggregate EtherChannel Quality of Service

Identify aggregate port channel interfaces before creating them using the platform qos port-channel-aggregate command.
In a port channel, all member links must be of the same speed.

Restrictions for Aggregate EtherChannel Quality of Service

Aggregate port channel member and interface limits

The aggregate port channel can support four member links and eight aggregate port channel interfaces.

QoS policy application restrictions on aggregate port channels

You can apply a policy map to the aggregate a port channel's main interface or sub-interface only. Member link QoS is not supported.

Limitations of aggregate port channel conversion

You cannot spontaneously convert port channels to and from the aggregate status. You must delete the interface port-channel from the configurations before adding or removing the matching platform qos port-channel-aggregate command.

Unsupported QoS applications on port channel member links

QoS applications which are used to manage, prioritize and control the behavior of data transmission over a network are not supported on port channel member links.

QoS policies applied to aggregate port channel main interfaces and port channel sub-interfaces are not supported.

Channel group modification process with aggregate QoS enabled

When you enable aggregate QoS, it is not possible to directly modify a channel group on a member link. To make changes, the old channel group needs to be removed and the new one must be added. First push one template to remove the old member link and port channel configuration, then another template to add the new configuration.

Configure Aggregate EtherChannel Quality of Service using CLI Template

Configure aggregate EtherChannel Quality of Service using a CLI template.

In SD-WAN Manager, you can configure aggregate EtherChannel QoS using the CLI templates to manage bandwidth and prioritize traffic across bundled links.

Before you begin

For more informationabout using CLI templates, see CLI add-on feature templates and CLI templates for Cisco IOS XE Catalyst SD-WAN devices.

Note

By default, CLI templates execute commands in global config mode.

Follow these steps to configure aggregate EtherChannel QoS using a CLI template.

Procedure

	1.	Create the aggregated port channel. `platform qos port-channel-aggregate port-channel-number interface Port-channel channel-number no shutdown ip address ip-address mask`
	2.	Assign member links to port channel. `interface GigabitEthernet slot/subslot/port no negotiation auto channel-group channel-group-number mode {active passive} exit`
	3.	Configure tunnels. `interface Tunnel tunnel-number no shutdown ip unnumbered port-channel-interface tunnel source port-channel-interface tunnel mode sdwan` `sdwan interfacechannel-group-number tunnel-interface encapsulation ipsec color public-internet`
	4.	Configure QoS. `interface channel-group-number service-policy output pre-defined qos policy-map`

Here's the complete configuration example for configuring aggregate EtherChannel QoS.

!
class-map match-any Best-Effort
 match qos-group 2
!
class-map match-any Bulk
 match qos-group 3
!
class-map match-any Business
 match qos-group 1
!
class-map match-any Critical
 match qos-group 0
!
policy-map qos_template
 class Critical
  police rate percent 15
  !
  priority level 1
 !
 class Business
  bandwidth remaining percent 55
 !
 class Best-Effort
  bandwidth remaining percent 10
 !
 class Bulk
  bandwidth remaining percent 20
 !
!
policy-map shape_Port-channel1
 class class-default
  service-policy qos_template
  shape average 100000000
 !
!
interface TenGigabitEthernet0/1/6
 no shutdown
 no negotiation auto
 channel-group 1 mode active
 lacp rate fast
exit
interface TenGigabitEthernet0/1/7
 no shutdown
 no negotiation auto
 channel-group 1 mode active
 lacp rate fast
exit
interface Port-channel1
 no shutdown
 ip address 10.1.15.15 255.255.255.0
 ipv6 nd ra suppress all
 service-policy output shape_Port-channel1
exit
interface Tunnel1
 no shutdown
 ip unnumbered Port-channel1
 tunnel source Port-channel1
 tunnel mode sdwan
exit
!
sdwan
 interface Port-channel1
  tunnel-interface
   encapsulation ipsec
   color lte
   no allow-service bgp
   allow-service dhcp
   allow-service dns
   allow-service icmp
   no allow-service sshd
   no allow-service netconf
   no allow-service ntp
   no allow-service ospf
   no allow-service stun
   allow-service https
   no allow-service snmp
   no allow-service bfd
  exit
 exit

What to do next

Verify aggregate EtherChannel QoS.

Verify Aggregate EtherChannel Quality of Service

To view QoS issues on a port channel interface, use the show policy-map interface Port-channel command.

Device# show policy-map interface Port-channel 1
Port-channel1

  Service-policy output: shape_Port-channel1

    Class-map: class-default (match-any)  
      121 packets, 20797 bytes
      5 minute offered rate 2000 bps, drop rate 0000 bps
      Match: any 
      Queueing
      queue limit 416 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 121/20797
      shape (average) cir 100000000, bc 400000, be 400000
      target shape rate 100000000

      Service-policy : qos_template

        queue stats for all priority classes:
          Queueing
          priority level 1
          queue limit 512 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 121/20797

        Class-map: Critical (match-any)  
          121 packets, 20797 bytes
          5 minute offered rate 2000 bps, drop rate 0000 bps
          Match: qos-group 0
          police:
              rate 15 %
              rate 15000000 bps, burst 468750 bytes
            conformed 121 packets, 20797 bytes; actions:
              transmit 
            exceeded 0 packets, 0 bytes; actions:
              drop 
            conformed 2000 bps, exceeded 0000 bps
          Priority: Strict, b/w exceed drops: 0
          
          Priority Level: 1 

        Class-map: Business (match-any)  
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: qos-group 1
          Queueing
          queue limit 416 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth remaining 55%

        Class-map: Best-Effort (match-any)  
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: qos-group 2
          Queueing
          queue limit 416 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth remaining 10%

        Class-map: Bulk (match-any)  
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: qos-group 3
          Queueing
          queue limit 416 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth remaining 20%

        Class-map: class-default (match-any)  
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: any 
          
          queue limit 416 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.