Modular QoS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

PDF

Modular QoS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

Egress feature capability

Updated: June 9, 2026

Want to summarize with AI?

Log in

Explains the egress traffic processing capability that enables supported egress QoS features.

Egress feature capability is a QoS traffic processing model that

  • applies traffic processing after the final egress interface is determined, and

  • introduces an additional egress processing stage for supported traffic flows.

Some Cisco 8000 platforms and line cards provide this capability by default. On other supported platforms, you must enable the capability before you configure dependent egress features.

On supported platforms, egress feature capability is enabled for the entire system. The configured mode applies to all physical interfaces and breakout ports after the router reloads.

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

Egress feature capability

Release 26.2.1

Introduced in this release on: Fixed Systems (8700 [ASIC: K100])(select variants only*)

You can now enable Egress feature capability on supported platforms to expand support for egress traffic management features. It uses an egress processing path to enable capabilities such as egress queuing, egress policing, and multicast QoS scheduling.

The feature introduces these changes:

CLI:

  • hw-module profile edge-mode

  • show hw-module profile edge-mode

*This feature is now supported on:

  • 8711-48Z-M

  • 8712-MOD-M

Benefits of egress feature capability

Traditional forwarding platforms apply most QoS operations before packets reach the egress interface. Because the final egress characteristics are not yet available during ingress processing, some egress features cannot be applied.

Egress traffic processing using egress feature capability introduces an additional processing stage after the forwarding destination is resolved. This additional processing stage provides visibility into the final egress interface and enables features that depend on egress-specific information.

Configure egress feature capability

Procedure

1.

Enable egress traffic processing.

Example:

Router(config)# hw-module profile edge-mode
Router(config)# commit

The router displays a message stating that the configuration change is activated only after a manual reload.
2.

Reload the router manually.

Example:

Router# reload
3.

Verify the configured and applied state of egress traffic processing.

Example:

Router# show hw-module profile edge-mode

When the capability is configured and active, the command displays this state:

--------------------------------------------------------------
Knob                          Status          Applied   Action
--------------------------------------------------------------
Edge mode                     Configured      Yes       None

If the configuration is committed but the router has not yet reloaded, the Action field displays Reload.
4.

Verify VOQ usage for the interfaces and system resources.

  • To display VOQ usage for a specific physical interface, use:

    Router# show controllers npu voq-usage interface <interface-name>

  • To display VOQ usage for all physical interfaces, use:

    Router# show controllers npu voq-usage interface all

  • To display global VOQ resource usage per interface group, use:

    Router# show controllers npu voq-usage resource-manager

  • To display local VOQ resource usage per interface group, use:

    Router# show controllers npu voq-usage resource-manager local

Egress traffic processing is active on all physical interfaces in the system. You can now configure supported features that depend on egress processing.