Information about Per-Tunnel QoS
Overview of Per-Tunnel QoS
Use the Per-tunnel QoS feature to configure a Cisco vEdge device as a spoke and apply a quality of service (QoS) policy on a hub on a per-spoke instance in the egress direction. Only Cisco IOS XE SD-WAN devices can be configured as hubs but both Cisco IOS XE SD-WAN devices and Cisco vEdge device can be configured as spokes.
Per-tunnel QoS can only be applied on hub-to-spoke network topologies. Per-tunnel QoS on a hub lets you shape tunnel traffic to individual spokes. It also differentiates individual data flows going through the tunnel or the spoke for policing.
Benefits of Per-Tunnel QoS
Before the introduction of Per-tunnel QoS feature on Cisco SD-WAN, QoS on a hub could be configured to measure only the aggregate outbound traffic for all spokes. Per-tunnel QoS for Cisco SD-WAN provides the following benefits.
-
A QoS policy is configurable on the basis of session groups, thus providing the capability of regulating traffic from hub to spokes at a per-spoke level.
-
The hub cannot send excessive traffic to a small spoke and overrun it.
-
The maximum outbound bandwidth and QoS queue are set up automatically when each spoke registers with an Overlay Management Protocol (OMP) message.
-
The amount of outbound hub bandwidth that a “greedy” spoke can consume can be limited; therefore, the traffic can’t monopolize a hub’s resources and starve other spokes.
-
Multiple policies (MPoL) are supported. This enables underlay and TLOC extension traffic to coexist with the overlay tunnel traffic.
Supported Platforms
Per-Tunnel QoS for Hub
The following series of platforms can be configured as hubs for the per-tunnel QoS in Cisco SD-WAN.
-
Cisco 1000 Series Aggregation Services Routers
-
Cisco 1000 Series Integrated Services Routers
-
Cisco ISR 1100 and ISR 1100X Series Integrated Services Routers
-
Cisco 4000 Series Integrated Services Routers
-
Cisco Cloud Services Router 1000V Series
-
Cisco Catalyst 8000 Edge Platforms Family
Per-Tunnel QoS for Spokes
The following series of IOS XE SD-WAN devices can be configured as spokes for per-tunnel QoS in Cisco SD-WAN.
-
Cisco 1000 Series Aggregation Services Routers
-
Cisco 1000 Series Integrated Services Routers
-
Cisco ISR 1100 and ISR 1100X Series Integrated Services Routers
-
Cisco 4000 Series Integrated Services Routers
-
Cisco Cloud Services Router 1000V Series
-
Cisco Catalyst 8000 Edge Platforms Family
Additionally, all Cisco vEdge devices can be configured as spokes for per-tunnel QoS in Cisco SD-WAN.
-
vEdge 100
-
vEdge 100b
-
vEdge 100m
-
vEdge 100wm
-
vEdge1000
-
vEdge 2000
-
vEdge 5000
-
vEdge Cloud Router
-
Cisco 1000 Series Integrated Services Routers (ISRs)
-
ISR1100-4G
-
ISR1100-6G
-
ISR1100-4GLTENA and ISR1100-4GLTEGB
-
Restrictions for Per-Tunnel QoS
The following restrictions apply to the Per-tunnel QoS feature in Cisco SD-WAN.
-
Only hub-to-spoke network topology is supported for configuring per-tunnel QoS. Spoke-to-spoke network topology isn't supported.
-
Only Cisco IOS XE SD-WAN devices are supported as hubs for per-tunnel QoS. However, both Cisco IOS XE SD-WAN devices and Cisco vEdge devices are supported as spokes in the hub-to-spoke topology supported for per-tunnel QoS.
-
In Cisco IOS XE Release 17.2.1r, per-tunnel QoS can only be configured using the Cisco VPN Interface Ethernet template in Cisco vManage 20.1.1.
-
Per-tunnel QoS with loopback WAN for non-binding mode isn’t supported on the hub.