Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

show interfaces queue

Syntax

Description

Display class-of-service (CoS) queue information for physical interfaces.

Options

Note:

This topic lists all possible options for the show interfaces queue command. The options that appear vary depending on the platform, software release, and operating system (Junos OS or Junos OS Evolved).
none

Show detailed CoS queue statistics for all physical interfaces.
aggregate

Display the aggregated queuing statistics of all logical interfaces that have traffic-control profiles configured.
both-ingress-egress

Display both ingress and egress queue statistics.
buffer-occupancy

Displays the peak buffer occupancy for each queue while buffer-monitor-enable is enabled at the [edit chassis fpc slot-number traffic-manager] hierarchy level.
egress

Display egress queue statistics.
forwarding-class forwarding-class

Forwarding class name for this queue. Shows detailed CoS statistics for the queue associated with the specified forwarding class.
ingress

Display ingress queue statistics.
interface-name

Show detailed CoS queue statistics for the specified interface. The other listed options are available for the specified interface.
l2-statistics

Display Layer 2 statistics for MLPPP, FRF.15, and FRF.16 bundles
remaining-traffic

Display the queuing statistics of all logical interfaces that do not have traffic-control profiles configured.
slice slice-name | detail | summary slice-name displays the detailed hierarchical CoS statistics on the interface for the specified slice. detail displays the same statistics for all slices on the interface. summary displays a summary of the statistics for each slice on the interface. Both the detail and summary provide additional options, such as forwarding-class class-name, to filter the command results.

Overhead for Layer 2 Statistics

Transmitted packets and transmitted byte counts are displayed for the Layer 2 level with the addition of encapsulation overheads applied for fragmentation, as shown in Table 1. Others counters, such as packets and bytes queued (input) and drop counters, are displayed at the Layer 3 level. In the case of link fragmentation and interleaving (LFI) for which fragmentation is not applied, corresponding Layer 2 overheads are added, as shown in Table 1.

Table 1: Layer 2 Overhead and Transmitted Packets or Byte Counts

Protocol

Fragmentation

LFI
 

First fragmentation

Second to n fragmentations

  
 

Bytes

Bytes

  

MLPPP (Long)

13

12

8

MLPPP (short)

11

10

8

MLFR (FRF15)

12

10

8

MFR (FRF16)

10

8

-

MCMLPPP(Long)

13

12

-

MCMLPPP(Short)

11

10

-

Layer 2 Statistics—Fragmentation Overhead Calculation

Overhead with LFI

The following examples show overhead for different cases:

  • A 1000-byte packet is sent to a mlppp bundle without any fragmentation. At the Layer 2 level, bytes transmitted is 1013 in 1 packet. This overhead is for MLPPP long sequence encap.

  • A 1000-byte packet is sent to a mlppp bundle with a fragment threshold of 250byte. At the Layer 2 level, bytes transmitted is 1061 bytes in 5 packets.

  • A 1000-byte LFI packet is sent to an mlppp bundle. At the Layer 2 level, bytes transmitted is 1008 in 1 packet.

Additional Information

For rate-limited interfaces hosted on Modular Interface Cards (MICs), Modular Port Concentrators (MPCs), or Enhanced Queuing DPCs, rate-limit packet-drop operations occur before packets are queued for transmission scheduling. For such interfaces, the statistics for queued traffic do not include the packets that have already been dropped due to rate limiting, and consequently the displayed statistics for queued traffic are the same as the displayed statistics for transmitted traffic.

Note:

For rate-limited interfaces hosted on other types of hardware, rate-limit packet-drop operations occur after packets are queued for transmission scheduling. For these other interface types, the statistics for queued traffic include the packets that are later dropped due to rate limiting, and consequently the displayed statistics for queued traffic equals the sum of the statistics for transmitted and rate-limited traffic.

Statistics for an aggregated interface are the summation of the queue statistics of the child links of that aggregated interface. You can view the statistics for a child interface by using the show interfaces statistics command for that child interface.

When fragmentation occurs on the egress interface, the first set of packet counters shows the postfragmentation values. The second set of packet counters (under the Packet Forwarding Engine Chassis Queues field) shows the prefragmentation values.

The behavior of the egress queues for the Routing Engine-Generated Traffic is not same as the configured queue for MLPPP and MFR configurations.

For related CoS operational mode commands, see the CLI Explorer.

Required Privilege Level

view

Output Fields

Table 2 lists the output fields for the show interfaces queue command. Output fields are listed in the approximate order in which they appear. The output fields that appear vary depending on the platform, software release, and operating system (Junos OS or Junos OS Evolved).

Table 2: show interfaces queue Output Fields

Field Name

Field Description

Physical/Anchor interface

Name of the physical interface.

Enabled

State of the interface. Possible values are described in the “Enabled Field” section under Common Output Fields Description.

Interface index

Physical interface's index number, which reflects its initialization sequence.

SNMP ifIndex

SNMP index number for the interface.

Slice

Name of the slice.

Slice index

Slice's index number, which reflects its initialization sequence.

Forwarding classes supported

Total number of forwarding classes supported on the specified interface.

Forwarding classes in use

Total number of forwarding classes in use on the specified interface.

Ingress queues supported

Total number of ingress queues supported on the specified interface.

Ingress queues in use

Total number of ingress queues in use on the specified interface.

Output queues supported

Total number of output queues supported on the specified interface.

Output queues in use

Total number of output queues in use on the specified interface.

Egress queues supported

Total number of egress queues supported on the specified interface.

Egress queues in use

Total number of egress queues in use on the specified interface.

Queue counters (Ingress)

CoS queue number and its associated user-configured forwarding class name.

  • Queued packets—Number of queued packets.

  • Transmitted packets—Number of transmitted packets.

  • Dropped packets—Number of packets dropped by the ASIC's RED mechanism.

Burst size

Maximum number of bytes up to which the logical interface can burst. The burst size is based on the shaping rate applied to the interface.

The following output fields are applicable to both interface component and Packet Forwarding component in the show interfaces queue command:

Queue

Queue number.

Forwarding classes

Forwarding class name.

Queued Packets

Number of packets queued to this queue.

For rate-limited interfaces hosted on MICs or MPCs only, this statistic does not include traffic dropped due to rate limiting. For more information, see Additional Information.

Queued Bytes

Number of bytes queued to this queue. The byte counts vary by interface hardware. For more information, see Table 3.

For rate-limited interfaces hosted on MICs or MPCs only, this statistic does not include traffic dropped due to rate limiting. For more information, see Additional Information.

Transmitted Packets

Number of packets transmitted by this queue. When fragmentation occurs on the egress interface, the first set of packet counters shows the postfragmentation values. The second set of packet counters (displayed under the Packet Forwarding Engine Chassis Queues field) shows the prefragmentation values.

Note:

For Layer 2 statistics, see Overhead for Layer 2 Statistics

Transmitted Bytes

Number of bytes transmitted by this queue. The byte counts vary by interface hardware. For more information, see Table 3.

Note:

On MX Series routers, this number can be inaccurate when you issue the command for a physical interface repeatedly and in quick succession, because the statistics for the child nodes are collected infrequently. Wait ten seconds between successive iterations to avoid this situation.
Note:

For Layer 2 statistics, see Overhead for Layer 2 Statistics

Tail-dropped packets

Number of packets dropped because of tail drop.

RL-dropped packets

Number of packets dropped due to rate limiting.

For rate-limited interfaces hosted on MICs, MPCs, and Enhanced Queuing DPCs only, this statistic is not included in the queued traffic statistics. For more information, see Additional Information.

RL-dropped bytes

Number of bytes dropped due to rate limiting.

For rate-limited interfaces hosted on MICs, MPCs, and Enhanced Queuing DPCs only, this statistic is not included in the queued traffic statistics. For more information, see Additional Information.

RED-dropped packets

Number of packets dropped because of random early detection (RED).

  • The output classifies dropped packets into the following categories:

    • Low—Number of low-loss priority packets dropped because of RED.

    • Medium-low—Number of medium-low loss priority packets dropped because of RED.

    • Medium-high—Number of medium-high loss priority packets dropped because of RED.

    • High—Number of high-loss priority packets dropped because of RED.

RED-dropped bytes

Number of bytes dropped because of RED. The byte counts vary by interface hardware. For more information, see Table 3.

  • The output classifies dropped bytes into the following categories:

    • Low, non-TCP—Number of low-loss priority non-TCP bytes dropped because of RED.

    • Low, TCP—Number of low-loss priority TCP bytes dropped because of RED.

    • High, non-TCP—Number of high-loss priority non-TCP bytes dropped because of RED.

    • High, TCP—Number of high-loss priority TCP bytes dropped because of RED.

Queue Buffer Usage:

  • Reserved buffer—The size of the memory buffer that is allocated for storing packets

  • Current—The amount of buffer memory that is currently in use on this queue.

Queue-depth bytes

Displays the amount of queue buffer that is in occupation at this instance. This is an indicator of the amount of data that is present in a queue at that point in time. The amount of data present is in the units of bytes.

Peak

Diplays the peak buffer occupancy for the queue while buffer-monitor-enable is enabled at the [edit chassis fpc slot-number traffic-manager] hierarchy level.

Last-packet enqueued

If packet-timestamp is enabled for an FPC, shows the day, date, time, and year in the format day-of-the-week month day-date hh:mm:ss yyyy when a packet was enqueued in the CoS queue. When the timestamp is aggregated across all active Packet Forwarding Engines, the latest timestamp for each CoS queue is reported.

Byte counts vary by interface hardware. Table 3 shows how the byte counts on the outbound interfaces vary depending on the interface hardware. Table 3 is based on the assumption that outbound interfaces are sending IP traffic with 478 bytes per packet.

Table 3: Byte Count by Interface Hardware

Interface Hardware

Output Level

Byte Count Includes

Comments

Gigabit Ethernet IQ and IQE PICs

Interface

Queued: 490 bytes per packet, representing 478 bytes of Layer 3 packet + 12 bytes

Transmitted: 490 bytes per packet, representing 478 bytes of Layer 3 packet + 12 bytes

RED dropped: 496 bytes per packet representing 478 bytes of Layer 3 packet + 18 bytes

The 12 additional bytes include 6 bytes for the destination MAC address + 4 bytes for the VLAN + 2 bytes for the Ethernet type.

For RED dropped, 6 bytes are added for the source MAC address.

Packet forwarding component

Queued: 478 bytes per packet, representing 478 bytes of Layer 3 packet

Transmitted: 478 bytes per packet, representing 478 bytes of Layer 3 packet

–

Non-IQ PIC

Interface

T Series, TX Series, T1600, and MX Series routers:

  • Queued: 478 bytes of Layer 3 packet.

  • Transmitted: 478 bytes of Layer 3 packet.

T4000 routers with Type 5 FPCs :

  • Queued: 478 bytes of Layer 3 packet + the full Layer 2 overhead including 4 bytes CRC + the full Layer 1 overhead 8 bytes preamble + 12 bytes Inter frame Gap.

  • Transmitted: 478 bytes of Layer 3 packet + the full Layer 2 overhead including 4 bytes CRC + the full Layer 1 overhead 8 bytes preamble + 12 bytes Interframe Gap.

M Series routers:

  • Queued: 478 bytes of Layer 3 packet.

  • Transmitted: 478 bytes of Layer 3 packet + the full Layer 2 overhead.

PTX Series Packet Transport Routers:

  • Queued: The sum of the transmitted bytes and the RED dropped bytes.

  • Transmitted: Full Layer 2 overhead (including all L2 encapsulation and CRC) + 12 inter-packet gap + 8 for the preamble.

  • RED dropped: Full Layer 2 overhead (including all L2 encapsulation and CRC) + 12 inter-packet gap + 8 for the preamble (does not include the VLAN header or MPLS pushed bytes).

The Layer 2 overhead is 14 bytes for non-VLAN traffic and 18 bytes for VLAN traffic.

IQ and IQE PICs with a SONET/SDH interface

Interface

Queued: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes

Transmitted: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes

RED dropped: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes

The additional 4 bytes are for the Layer 2 Point-to-Point Protocol (PPP) header.

Packet forwarding component

Queued: 478 bytes per packet, representing 478 bytes of Layer 3 packet

Transmitted: 486 bytes per packet, representing 478 bytes of Layer 3 packet + 8 bytes

For transmitted packets, the additional 8 bytes includes 4 bytes for the PPP header and 4 bytes for a cookie.

Non-IQ PIC with a SONET/SDH interface

Interface

T Series, TX Series, T1600, and MX Series routers:

  • Queued: 478 bytes of Layer 3 packet.

  • Transmitted: 478 bytes of Layer 3 packet.

M Series routers:

  • Queued: 478 bytes of Layer 3 packet.

  • Transmitted: 483 bytes per packet, representing 478 bytes of Layer 3 packet + 5 bytes

  • RED dropped: 478 bytes per packet, representing 478 bytes of Layer 3 packet

For transmitted packets, the additional 5 bytes includes 4 bytes for the PPP header and 1 byte for the packet loss priority (PLP).

Interfaces configured with Frame Relay Encapsulation

Interface

The default Frame Relay overhead is 7 bytes. If you configure the Frame Check Sequence (FCS) to 4 bytes, then the overhead increases to 10 bytes.

1-port 10-Gigabit Ethernet IQ2 and IQ2–E PICs

4-port 1G IQ2 and IQ2-E PICs

8-port 1G IQ2 and IQ2-E PICs

Interface

Queued: 478 bytes of Layer 3 packet + the full Layer 2 overhead including CRC.

Transmitted: 478 bytes of Layer 3 packet + the full Layer 2 overhead including CRC.

The Layer 2 overhead is 18 bytes for non-VLAN traffic and 22 bytes for VLAN traffic.

Packet forwarding component

Queued: 478 bytes of Layer 3 packet.

Transmitted: 478 bytes of Layer 3 packet.

–

Sample Output

show interfaces queue (Rate-Limited Interface on a Gigabit Ethernet MIC in an MPC)

The following example shows queue information for the rate-limited interface ge-4/2/0 on a Gigabit Ethernet MIC in an MPC. For rate-limited queues for interfaces hosted on MICs or MPCs, rate-limit packet drops occur prior to packet output queuing. In the command output, the nonzero statistics displayed in the RL-dropped packets and RL-dropped bytes fields quantify the traffic dropped to rate-limit queue 0 output to 10 percent of 1 gigabyte (100 megabits) per second. Because the RL-dropped traffic is not included in the Queued statistics, the statistics displayed for queued traffic are the same as the statistics for transmitted traffic.

show interfaces queue (Aggregated Ethernet on a T320 Router)

The following example shows that the aggregated Ethernet interface, ae1, has traffic on queues af1 and af12:

show interfaces queue (Gigabit Ethernet on a T640 Router)

show interfaces queue aggregate (Gigabit Ethernet Enhanced DPC)

show interfaces queue (Gigabit Ethernet IQ2 PIC)

show interfaces queue both-ingress-egress (Gigabit Ethernet IQ2 PIC)

show interfaces queue ingress (Gigabit Ethernet IQ2 PIC)

show interfaces queue egress (Gigabit Ethernet IQ2 PIC)

show interfaces queue remaining-traffic (Gigabit Ethernet Enhanced DPC)

show interfaces queue (Channelized OC12 IQE Type 3 PIC in SONET Mode)

show interfaces queue (QFX Series)

show interfaces queue l2-statistics (lsq interface)

show interfaces queue lsq (lsq-ifd)

show interfaces queue (Aggregated Ethernet on a MX series Router)

show interfaces queue ge-0/0/0 (EX2200 Switch)

show interfaces queue xe-0/0/2 buffer-occupancy (QFX5000 Series switch)

show interfaces queue xe-3/0/3 slice slice1

Note:

show interfaces queue xe-3/0/3 slice detail shows the same level of information as below for all slices on the xe-3/0/3 interface.

show interfaces queue xe-4/0/5 slice summary

This sample shows two network slices, slice1 and slice2, which are anchored on xe-4/0/5. The counters here are the sum of corresponding counters across all queues of each slice on this physical interface. For example, the queued packets counter of slice2 on xe-4/0/5 here is the sum of queued packets across all the queues/forwarding-classes of slice2 on xe-4/0/5.

show interfaces queue xe-4/0/5 slice detail forwarding-class assured-forwarding

This sample shows two network slices, slice1 and slice2, which are anchored on xe-4/0/5. The counters here are for the assured-forwarding forwarding class of each slice on this physical interface.

show interfaces queue (vSRX Virtual Firewall)

The following truncated example shows the CoS queue sizes for queues 0, 1, and 3. Queue 1 has a queue buffer size (guaranteed allocated memory) of 9192 bytes.

Release Information

Command introduced before Junos OS Release 7.4.

both-ingress-egress, egress, and ingress options introduced in Junos OS Release 7.6.

l2-statistics option introduced in Junos OS Release 12.1.

buffer-occupancy statement introduced in Junos OS Release 19.1R1.

Related Documentation

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
22.3R1
Starting with Junos OS 24.2R1, the slice summary and slice detail options are supported on MX Series Routers.
22.3R1
Starting with Junos OS 22.3R1, the slice slice-name option is supported on MX Series Routers.
18.3R1
Starting with Junos OS 18.3R1, the Tail-dropped packets counter is supported on PTX Series Packet Transport Routers.
16.1
Starting with Junos OS Release 16.1, Last-packet enqueued output field is introduced.