Describes the diagnostic capability that isolates a detected stuck Virtual Output Queue condition to the ingress or egress network processing unit and line card and reports the affected side through operational show commands.
Stuck Virtual Output Queue (VOQ) isolation is a Modular QoS diagnostic capability that
-
determines whether a detected stuck VOQ condition originates on the ingress or egress network processing unit (NPU) line card
-
replaces the debug-shell workflow previously required to isolate the affected ingress or egress NPU line cards, and
-
displays the affected interface and VOQ information, diagnostic status, and recommended action.
A stuck VOQ has a queue depth that remains unchanged even when no traffic is present. The VOQ watchdog detects the condition and reports it in an Cisco IOS XR system message. Stuck VOQ isolation determines whether the detected condition is associated with the ingress or egress NPU line card.
|
Feature Name |
Release Information |
Feature Description |
|---|---|---|
|
Identify the source of a stuck VOQ |
Release 26.3.1 |
Introduced in this release on: Modular Systems (8800 [LC ASIC: Q100, Q200]) You can now determine whether a detected stuck VOQ condition originates on the ingress or egress NPU line card. Previously, isolating the affected side required debug-shell commands. The new operational commands display the affected VOQ and interface information, diagnostic status, and recommended action. The feature introduces these changes: CLI:
YANG Data Model:
*This feature is supported on:
|