Displaying subinterface queue resource allocation
Given the scale of the systems, not all subinterfaces can be enabled for subinterface queuing. To display subinterfaces that are configured for subinterface queuing but which are currently on the pending list because of a lack of available resources, use the qos interfaces interface output voq-set-pending and qos interfaces interface output voq-set-statistics-pending commands.
A retry mechanism ensures that if any voq-set or voq-set-statistics resources become available they are allocated to a pending subinterface.
.Display interfaces with pending VOQ set
--{ candidate shared default }--[ ]--
# info from state /qos interfaces interface ethernet-1/1.896 output voq-set-pending
voq-set-pending [
ethernet-1/1
]
Display interfaces with pending VOQ set statistics
--{ candidate shared default }--[ ]--
# info from state /qos interfaces interface ethernet-1/1.896 output voq-set-statistics-pending
voq-set-statistics-pending [
ethernet-1/1
]
Display VOQ connector sets per line-card
To display the status of voq-connector-sets per line card, forwarding complex, and core, use the info from state platform linecard forwarding-complex core command.--{ candidate shared default }--[ ]--
# info from state / platform linecard 1 forwarding-complex 0 core 1
qos {
resource voq-connector-set {
used 840
free 0
}
}
Display overal system resources for VOQ sets and statistics
To display the overall system resources for VOQ sets and VOQ statistics, use the info from state system utilization qos command.
--{ candidate shared default }--[ ]--
# info from state /system utilization qos
resource voq-set {
upper-threshold-set 90
upper-threshold-clear 70
used-percent 94
used-entries 6720
free-entries 448
used-high-watermark 6720
used-last-high-watermark-time "2026-06-09T04:02:35.675Z (6 minutes ago)"
used-upper-threshold-exceeded true
}
resource voq-set-statistics {
upper-threshold-set 90
upper-threshold-clear 70
used-percent 99
used-entries 1691
free-entries 9
used-high-watermark 1691
used-last-high-watermark-time "2026-06-09T04:04:15.009Z (5 minutes ago)"
used-upper-threshold-exceeded true
}