show class-of-service interface

Name of a physical interface.

Index of this interface or the internal index of this object.

(Enhanced subscriber management) Index values for dynamic CoS traffic control profiles and dynamic scheduler maps are larger for enhanced subscriber management than they are for legacy subscriber management.

Status of dedicated queues configured on an interface.

(Enhanced subscriber management) This field is not displayed for enhanced subscriber management.

Number of queues you can configure on the interface.

Maximum number of queues you can use.

Number of queues created in addition to the default queues.

(Enhanced subscriber management) This field is not displayed for enhanced subscriber management.

IEEE 802.1p code point (priority) rewrite value. Incoming traffic from the Fibre Channel (FC) SAN is classified into the forwarding class specified in the native FC interface (NP_Port) fixed classifier and uses the priority specified as the IEEE 802.1p rewrite value.

Maximum transmission rate on the physical interface. You can configure the shaping rate on the physical interface, or on the logical interface, but not on both. Therefore, the Shaping rate field is displayed for either the physical interface or the logical interface.

Name of the output scheduler map associated with this interface.

(Enhanced subscriber management) The name of the dynamic scheduler map object is associated with a generated UID (for example, SMAP-1_UID1002) instead of with a subscriber interface.

Name of the output fabric scheduler map associated with a QFabric system Interconnect device interface.

Maximum transmission rate on the input interface.

Name of the input scheduler map associated with this interface.

Name of the scheduler map associated with the packet forwarding component queues.

Name and type of the rewrite rules associated with this interface.

Name of the associated traffic control profile.

(Enhanced subscriber management) The name of the dynamic traffic control profile object is associated with a generated UID (for example, TC_PROF_100_199_SERIES_UID1006) instead of with a subscriber interface.

Name and type of classifiers associated with this interface.

Name of the forwarding map associated with this interface.

Congestion notification state, enabled or disabled.

Name of the dedicated buffer profile associated with the interface.

Name of a logical interface.

Category of an object: Classifier, Fragmentation-map (for LSQ interfaces only), Scheduler-map, Rewrite, Translation Table, or traffic-class-map.

Name of an object.

Type of an object: dscp, dscp-ipv6, exp, ieee-802.1, ip, inet-precedence, or ieee-802.1ad.

Encapsulation on the physical interface.

MTU size on the physical interface.

Speed at which the interface is running.

Whether loopback is enabled and the type of loopback.

Whether source filtering is enabled or disabled.

Whether flow control is enabled or disabled.

Whether autonegotiation is enabled or disabled.

Remote fault status.

• Online—Autonegotiation is manually configured as online.

• Offline—Autonegotiation is manually configured as offline.

The Device flags field provides information about the physical device and displays one or more of the following values:

• Down—Device has been administratively disabled.

• Hear-Own-Xmit—Device receives its own transmissions.

• Link-Layer-Down—The link-layer protocol has failed to connect with the remote endpoint.

• Loopback—Device is in physical loopback.

• Loop-Detected—The link layer has received frames that it sent, thereby detecting a physical loopback.

• No-Carrier—On media that support carrier recognition, no carrier is currently detected.

• No-Multicast—Device does not support multicast traffic.

• Present—Device is physically present and recognized.

• Promiscuous—Device is in promiscuous mode and recognizes frames addressed to all physical addresses on the media.

• Quench—Transmission on the device is quenched because the output buffer is overflowing.

• Recv-All-Multicasts—Device is in multicast promiscuous mode and therefore provides no multicast filtering.

• Running—Device is active and enabled.

The Interface flags field provides information about the physical interface and displays one or more of the following values:

• Admin-Test—Interface is in test mode and some sanity checking, such as loop detection, is disabled.

• Disabled—Interface is administratively disabled.

• Down—A hardware failure has occurred.

• Hardware-Down—Interface is nonfunctional or incorrectly connected.

• Link-Layer-Down—Interface keepalives have indicated that the link is incomplete.

• No-Multicast—Interface does not support multicast traffic.

• No-receive No-transmit—Passive monitor mode is configured on the interface.

• Point-To-Point—Interface is point-to-point.

• Pop all MPLS labels from packets of depth—MPLS labels are removed as packets arrive on an interface that has the pop-all-labels statement configured. The depth value can be one of the following:

  • 1—Takes effect for incoming packets with one label only.

  • 2—Takes effect for incoming packets with two labels only.

  • [ 1 2 ]—Takes effect for incoming packets with either one or two labels.

• Promiscuous—Interface is in promiscuous mode and recognizes frames addressed to all physical addresses.

• Recv-All-Multicasts—Interface is in multicast promiscuous mode and provides no multicast filtering.

• SNMP-Traps—SNMP trap notifications are enabled.

• Up—Interface is enabled and operational.

The Logical interface flags field provides information about the logical interface and displays one or more of the following values:

• ACFC Encapsulation—Address control field Compression (ACFC) encapsulation is enabled (negotiated successfully with a peer).

• Device-down—Device has been administratively disabled.

• Disabled—Interface is administratively disabled.

• Down—A hardware failure has occurred.

• Clear-DF-Bit—GRE tunnel or IPsec tunnel is configured to clear the Don't Fragment (DF) bit.

• Hardware-Down—Interface protocol initialization failed to complete successfully.

• PFC—Protocol field compression is enabled for the PPP session.

• Point-To-Point—Interface is point-to-point.

• SNMP-Traps—SNMP trap notifications are enabled.

• Up—Interface is enabled and operational.

Encapsulation on the logical interface.

Administrative state of the interface (Up or Down)

Status of physical link (Up or Down).

Protocol configured on the interface.

Names of any firewall filters to be evaluated when packets are received on the interface, including any filters attached through activation of dynamic service.

Names of any firewall filters to be evaluated when packets are transmitted on the interface, including any filters attached through activation of dynamic service.

Provides information about the physical link and displays one or more of the following values:

• ACFC—Address control field compression is configured. The Point-to-Point Protocol (PPP) session negotiates the ACFC option.

• Give-Up—Link protocol does not continue connection attempts after repeated failures.

• Loose-LCP—PPP does not use the Link Control Protocol (LCP) to indicate whether the link protocol is operational.

• Loose-LMI—Frame Relay does not use the Local Management Interface (LMI) to indicate whether the link protocol is operational.

• Loose-NCP—PPP does not use the Network Control Protocol (NCP) to indicate whether the device is operational.

• Keepalives—Link protocol keepalives are enabled.

• No-Keepalives—Link protocol keepalives are disabled.

• PFC—Protocol field compression is configured. The PPP session negotiates the PFC option.

Current interface hold-time up and hold-time down, in milliseconds.

Number of CoS queues configured.

Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

Number and rate of bytes and packets received and transmitted on the physical interface.

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

Exclude the counting of overhead bytes from aggregate queue statistics.

• Disabled—Default configuration. Includes the counting of overhead bytes in aggregate queue statistics.

• Enabled—Excludes the counting of overhead bytes from aggregate queue statistics for just the physical interface.

• Enabled for hierarchy—Excludes the counting of overhead bytes from aggregate queue statistics for the physical interface as well as all child interfaces, including logical interfaces and interface sets.

Number of IPv6 transit bytes and packets received and transmitted on the logical interface if IPv6 statistics tracking is enabled.

Input errors on the interface. The labels are explained in the following list:

• Errors—Sum of the incoming frame terminations and FCS errors.

• Drops—Number of packets dropped by the input queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism.

• Framing errors—Number of packets received with an invalid frame checksum (FCS).

• Runts—Number of frames received that are smaller than the runt threshold.

• Giants—Number of frames received that are larger than the giant threshold.

• Bucket Drops—Drops resulting from the traffic load exceeding the interface transmit or receive leaky bucket configuration.

• Policed discards—Number of frames that the incoming packet match code discarded because they were not recognized or not of interest. Usually, this field reports protocols that Junos OS does not handle.

• L3 incompletes—Number of incoming packets discarded because they failed Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with less than 20 bytes of available IP header is discarded. Layer 3 incomplete errors can be ignored by configuring the ignore-l3-incompletes statement.

• L2 channel errors—Number of times the software did not find a valid logical interface for an incoming frame.

• L2 mismatch timeouts—Number of malformed or short packets that caused the incoming packet handler to discard the frame as unreadable.

• HS link CRC errors—Number of errors on the high-speed links between the ASICs responsible for handling the router interfaces.

• HS link FIFO overflows—Number of FIFO overflows on the high-speed links between the ASICs responsible for handling the router interfaces.

Output errors on the interface. The labels are explained in the following list:

• Carrier transitions—Number of times the interface has gone from down to up. This number does not normally increment quickly, increasing only when the cable is unplugged, the far-end system is powered down and up, or another problem occurs. If the number of carrier transitions increments quickly (perhaps once every 10 seconds), the cable, the far-end system, or the PIC is malfunctioning.

• Errors—Sum of the outgoing frame terminations and FCS errors.

• Drops—Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism.

• Aged packets—Number of packets that remained in shared packet SDRAM so long that the system automatically purged them. The value in this field should never increment. If it does, it is most likely a software bug or possibly malfunctioning hardware.

• HS link FIFO underflows—Number of FIFO underflows on the high-speed links between the ASICs responsible for handling the router interfaces.

• MTU errors—Number of packets whose size exceeds the MTU of the interface.

Total number of egress Maximum usable queues on the specified interface.

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.

SONET media-specific alarms and defects that prevent the interface from passing packets. When a defect persists for a certain period, it is promoted to an alarm. Based on the router configuration, an alarm can ring the red or yellow alarm bell on the router or light the red or yellow alarm LED on the craft interface. See these fields for possible alarms and defects: SONET PHY, SONET section, SONET line, and SONET path.

Counts of specific SONET errors with detailed information.

• Seconds—Number of seconds the defect has been active.

• Count—Number of times that the defect has gone from inactive to active.

• State—State of the error. A state other than OK indicates a problem.

The SONET PHY field has the following subfields:

• PLL Lock—Phase-locked loop

• PHY Light—Loss of optical signal

Counts of specific SONET errors with detailed information.

• Seconds—Number of seconds the defect has been active.

• Count—Number of times that the defect has gone from inactive to active.

• State—State of the error. A state other than OK indicates a problem.

The SONET section field has the following subfields:

• BIP-B1—Bit interleaved parity for SONET section overhead

• SEF—Severely errored framing

• LOS—Loss of signal

• LOF—Loss of frame

• ES-S—Errored seconds (section)

• SES-S—Severely errored seconds (section)

• SEFS-S—Severely errored framing seconds (section)

Active alarms and defects, plus counts of specific SONET errors with detailed information.

• Seconds—Number of seconds the defect has been active.

• Count—Number of times that the defect has gone from inactive to active.

• State—State of the error. A state other than OK indicates a problem.

The SONET line field has the following subfields:

• BIP-B2—Bit interleaved parity for SONET line overhead

• REI-L—Remote error indication (near-end line)

• RDI-L—Remote defect indication (near-end line)

• AIS-L—Alarm indication signal (near-end line)

• BERR-SF—Bit error rate fault (signal failure)

• BERR-SD—Bit error rate defect (signal degradation)

• ES-L—Errored seconds (near-end line)

• SES-L—Severely errored seconds (near-end line)

• UAS-L—Unavailable seconds (near-end line)

• ES-LFE—Errored seconds (far-end line)

• SES-LFE—Severely errored seconds (far-end line)

• UAS-LFE—Unavailable seconds (far-end line)

Active alarms and defects, plus counts of specific SONET errors with detailed information.

• Seconds—Number of seconds the defect has been active.

• Count—Number of times that the defect has gone from inactive to active.

• State—State of the error. A state other than OK indicates a problem.

The SONET path field has the following subfields:

• BIP-B3—Bit interleaved parity for SONET section overhead

• REI-P—Remote error indication

• LOP-P—Loss of pointer (path)

• AIS-P—Path alarm indication signal

• RDI-P—Path remote defect indication

• UNEQ-P—Path unequipped

• PLM-P—Path payload (signal) label mismatch

• ES-P—Errored seconds (near-end STS path)

• SES-P—Severely errored seconds (near-end STS path)

• UAS-P—Unavailable seconds (near-end STS path)

• ES-PFE—Errored seconds (far-end STS path)

• SES-PFE—Severely errored seconds (far-end STS path)

• UAS-PFE—Unavailable seconds (far-end STS path)

Values of the received and transmitted SONET overhead:

• C2—Signal label. Allocated to identify the construction and content of the STS-level SPE and for PDI-P.

• F1—Section user channel byte. This byte is set aside for the purposes of users.

• K1 and K2—These bytes are allocated for APS signaling for the protection of the multiplex section.

• J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N signal. Used to transmit a 1-byte fixed-length string or a 16-byte message so that a receiving terminal in a section can verify its continued connection to the intended transmitter.

• S1—Synchronization status. The S1 byte is located in the first STS-1 number of an STS-N signal.

• Z3 and Z4—Allocated for future use.

SONET/SDH interfaces allow path trace bytes to be sent inband across the SONET/SDH link. Juniper Networks and other router manufacturers use these bytes to help diagnose misconfigurations and network errors by setting the transmitted path trace message so that it contains the system hostname and name of the physical interface. The received path trace value is the message received from the router at the other end of the fiber. The transmitted path trace value is the message that this router transmits.

Information about the HDLC configuration.

• Policing bucket—Configured state of the receiving policer.

• Shaping bucket—Configured state of the transmitting shaper.

• Giant threshold—Giant threshold programmed into the hardware.

• Runt threshold—Runt threshold programmed into the hardware.

Information about the configuration of the Packet Forwarding Engine:

• Destination slot—FPC slot number.

• PLP byte—Packet Level Protocol byte.

Information about the CoS queue for the physical interface.

• CoS transmit queue—Queue number and its associated user-configured forwarding class name.

• Bandwidth %—Percentage of bandwidth allocated to the queue.

• Bandwidth bps—Bandwidth allocated to the queue (in bps).

• Buffer %—Percentage of buffer space allocated to the queue.

• Buffer usec—Amount of buffer space allocated to the queue, in microseconds. This value is nonzero only if the buffer size is configured in terms of time.

• Priority—Queue priority: low or high.

• Limit—Displayed if rate limiting is configured for the queue. Possible values are none and exact. If exact is configured, the queue transmits only up to the configured bandwidth, even if excess bandwidth is available. If none is configured, the queue transmits beyond the configured bandwidth if bandwidth is available.

Total number of forwarding classes supported on the specified interface.

Total number of egress Maximum usable queues on the specified interface.

Queue number.

Forwarding class name.

Number of packets queued to this queue.

Number of bytes queued to this queue. The byte counts vary by PIC type.

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.

Number of bytes transmitted by this queue. The byte counts vary by PIC type.

Number of packets dropped because of tail drop.

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

• (M Series and T Series routers only) On M320 and M120 routers and the T Series routers, the total number of dropped packets is displayed. On all other M Series routers, the output classifies dropped packets into the following categories:

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

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

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

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

• (MX Series routers with enhanced DPCs, and T Series routers with enhanced FPCs only) 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.

Number of bytes dropped because of RED. The byte counts vary by PIC type.

• (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.

Configured transmit rate of the scheduler. The rate is a percentage of the total interface bandwidth.

Rate limiting configuration of the queue. Possible values are :

• None—No rate limit.

• exact—Queue transmits at the configured rate.

Delay buffer size in the queue.

Scheduling priority configured as low or high.

Priority of the excess bandwidth traffic on a scheduler: low, medium-low, medium-high, high, or none.

Display the assignment of drop profiles.

• Loss priority—Packet loss priority for drop profile assignment.

• Protocol—Transport protocol for drop profile assignment.

• Index—Index of the indicated object. Objects that have indexes in this output include schedulers and drop profiles.

• Name—Name of the drop profile.

• Type—Type of the drop profile: discrete or interpolated.

• Fill Level—Percentage fullness of a queue.

• Drop probability—Drop probability at this fill level.

Priority of the excess bandwidth traffic on a scheduler.

Display the assignment of drop profiles.

• Loss priority—Packet loss priority for drop profile assignment.

• Protocol—Transport protocol for drop profile assignment.

• Index—Index of the indicated object. Objects that have indexes in this output include schedulers and drop profiles.

• Name—Name of the drop profile.

• Type—Type of the drop profile: discrete or interpolated.

• Fill Level—Percentage fullness of a queue.

• Drop probability—Drop probability at this fill level.

Display the assignment of shaping-rate adjustments on a scheduler node or queue.

• Adjusting application—Application that is performing the shaping-rate adjustment.

  • The adjusting application can appear as ancp LS-0, which is the Junos OS Access Node Control Profile process (ancpd) that performs shaping-rate adjustments on schedule nodes.

  • The adjusting application can appear as DHCP, which adjusts the shaping-rate and overhead-accounting class-of-service attributes based on DSL Forum VSA conveyed in DHCP option 82, suboption 9 (Vendor Specific Information). The shaping rate is based on the actual-data-rate-downstream attribute. The overhead accounting value is based on the access-loop-encapsulation attribute and specifies whether the access loop uses Ethernet (frame mode) or ATM (cell mode).

  • The adjusting application can also appear as pppoe, which adjusts the shaping-rate and overhead-accounting class-of-service attributes on dynamic subscriber interfaces in a broadband access network based on access line parameters in Point-to-Point Protocol over Ethernet (PPPoE) Tags [TR-101]. The shaping rate is based on the actual-data-rate-downstream attribute. The overhead accounting value is based on the access-loop-encapsulation attribute and specifies whether the access loop uses Ethernet (frame mode) or ATM (cell mode).

• Adjustment type—Type of adjustment: absolute or delta.

• Configured shaping rate—Shaping rate configured for the scheduler node or queue.

• Adjustment value—Value of adjusted shaping rate.

• Adjustment target—Level of shaping-rate adjustment performed: node or queue.

• Adjustment overhead-accounting mode—Configured shaping mode: frame or cell.

• Adjustment overhead bytes—Number of bytes that the ANCP agent adds to or subtracts from the actual downstream frame overhead before reporting the adjusted values to CoS.

• Adjustment target—Level of shaping-rate adjustment performed: node or queue.

• Adjustment multicast index—