Table 147: show interfaces queue Output Fields (continued)
Field DescriptionField Name
Number of bytes dropped because of RED. The byte counts vary by interface hardware. For more
information, see Table 148 on page 2552.
• (M Series and T Series routers only) On M320 and M120 routers and the T Series routers, only the
total number of dropped bytes is displayed. On all other M Series routers, 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.
NOTE: Due to accounting space limitations on certain Type 3 FPCs (which are supported in M320
and T640 routers), this field does not always display the correct value for queue 6 or queue 7 for
interfaces on 10-port 1-Gigabit Ethernet PICs.
RED-dropped bytes
Displays queue-depth average, current, peak, and maximum values for RTP queues. Because
queue-depth values cannot be aggregated, displays the values for RTP queues regardless of whether
aggregate, remaining-traffic, or neither option is selected.
Queue-depth bytes
Displays queue-depth average, current, peak, and maximum values for RTP queues. Because
queue-depth values cannot be aggregated, displays the values for RTP queues regardless of whether
aggregate, remaining-traffic, or neither option is selected.
Queue-depth bytes
Starting with Junos OS Release 16.1, Last-packet enqueued output field is introduced. 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.
Last-packet enqueued
Byte counts vary by interface hardware. Table 148 on page 2552 shows how the byte counts
on the outbound interfaces vary depending on the interface hardware.
Table 148 on page 2552 is based on the assumption that outbound interfaces are sending
IP traffic with 478 bytes per packet.
2551Copyright © 2017, Juniper Networks, Inc.
Chapter 42: Operational Commands