show interfaces (ATM)

Physical 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.

Description

Configured interface description.

Interface index

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

SNMP ifIndex

SNMP index number for the physical interface.

Generation

Unique number for use by Juniper Networks technical support only.

Link-level type

Encapsulation being used on the physical interface:

• ATM-CCC-CELL-RELAY—ATM cell relay for CCC.

• ATM-CCC-VC-MUX—ATM virtual circuit (VC) for CCC.

• ATM-CISCO-NLPID—Cisco-compatible ATM NLPID encapsulation.

• ATM-MIPP-LLC—ATM MLPPP over ATM Adaptation Layer 5 (AAL5)/logical link control (LLC).

• ATM-NLPID—ATM NLPID encapsulation.

• ATM-PPP-LLC—ATM PPP over AAL5/LLC.

• ATM-PPP-VC-MUX—ATM PPP over raw AAL5.

• ATM-PVC—ATM permanent virtual circuits.

• ATM-SNAP—ATM LLC/SNAP encapsulation.

• ATM-TCC-SNAP—ATM LLC/SNAP for translational cross-connection.

• ATM-TCC-VC-MUX—ATM VC for translational cross-connection.

• ATM-VC-MUX—ATM VC multiplexing.

• ETHER-OVER-ATM-LLC—Ethernet over ATM (LLC/SNAP) encapsulation.

• ETHER-VPLS-OVER-ATM-LLC—Ethernet VPLS over ATM (bridging) encapsulation.

MTU

MTU size on the physical interface.

Clocking

Reference clock source: Internal or External.

framing Mode

Framing mode: SONET or SDH.

Speed

Speed at which the interface is running as represented by the interface type (for example, OC3, ADSL2+, and SHDSL(2-wire).

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

Payload scrambler

Whether payload scrambling is enabled.

Device flags

Information about the physical device. Possible values are described in the “Device Flags” section under Common Output Fields Description.

Link flags

Information about the link. Possible values are described in the “Link Flags” section under Common Output Fields Description.

CoS queues

Number of CoS queues configured.

Hold-times

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

Current address

Ethernet MAC address for this interface for Ethernet over ATM encapsulation.

Last flapped

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).

Input Rate

Input rate in bits per second (bps) and packets per second (pps).

Output Rate

Output rate in bps and pps.

Statistics last cleared

Time when the statistics for the interface were last set to zero.

Traffic statistics

Statistics for traffic on the 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.

Input errors

Input errors on the interface whose definitions are as follows:

• Errors—Sum of the incoming frame terminations and frame check sequence (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 random early detection (RED) mechanism.

• Invalid VCs—Number of cells that arrived for a nonexistent VC.

• Framing errors—Sum of AAL5 packets that have FCS errors, reassembly timeout errors, and length errors.

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

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

• Resource errors—Sum of transmit drops.

Output errors

Output errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious:

• 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, increasing only when the cable is unplugged, the far-end system is powered down and then up, or another problem occurs. If it increments quickly (perhaps once every 10 seconds), the cable, the far-end system, or the PIC or PIM 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 so long in shared packet SDRAM 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.

• MTU errors—Number of packets larger than the MTU threshold.

• Resource errors—Sum of transmit drops.

Egress queues

Total number of egress queues supported on the specified interface.

Queue counters

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 alarms

SONET defects

SONET media-specific 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.

SONET PHY

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. State other than OK indicates a problem.

Subfields are:

• PLL Lock—Phase-locked loop

• PHY Light—Loss of optical signal

SONET section

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. State other than OK indicates a problem.

Subfields are:

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

• SEF—Severely errored framing

• LOL—Loss of light

• LOF—Loss of frame

• ES-S—Errored seconds (section)

• SES-S—Severely errored seconds (section)

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

SONET 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. State other than OK indicates a problem.

Subfields are:

• 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)

SONET path

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. State other than OK indicates a problem.

Subfields are:

• 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)

Received SONET overhead

Transmitted SONET overhead

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 of an STS-N.

• Z3 and Z4—Allocated for future use.

SDH alarms

SDH defects

SDH media-specific defects that can 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: SDH PHY, SDH regenerator section, SDH multiplex section, and SDH path.

SDH PHY

Active alarms and defects, plus counts of specific SDH 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. State other than OK indicates a problem.

Subfields are:

• PLL Lock—Phase-locked loop

• PHY Light—Loss of optical signal

SDH regenerator section

Active alarms and defects, plus counts of specific SDH 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. State other than OK indicates a problem.

Subfields are:

• RS-BIP8—24-bit BIP for multiplex section overhead (B2 bytes)

• OOF—Out of frame

• LOS—Loss of signal

• LOF—Loss of frame

• RS-ES—Errored seconds (near-end regenerator section)

• RS-SES—Severely errored seconds (near-end regenerator section)

• RS-SEFS—Severely errored framing seconds (regenerator section)

SDH multiplex section

Active alarms and defects, plus counts of specific SDH 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. State other than OK indicates a problem.

Subfields are:

• MS-BIP24—8-bit BIP for high-order path overhead (B3 byte)

• MS-FEBE—Far-end block error (multiplex section)

• MS-FERF—Far-end remote fail (multiplex section)

• MS-AIS—Alarm indication signal (multiplex section)

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

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

• MS-ES—Errored seconds (near-end multiplex section)

• MS-SES—Severely errored seconds (near-end multiplex section)

• MS-UAS—Unavailable seconds (near-end multiplex section)

• MS-ES-FE—Errored seconds (far-end multiplex section)

• MS-SES-FE—Severely errored seconds (far-end multiplex section)

• MS-UAS-FE—Unavailable seconds (far-end multiplex section)

SDH path

Active alarms and defects, plus counts of specific SDH 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. State other than OK indicates a problem.

Subfields are:

• HP-BIP8—8-bit BIP for regenerator section overhead (B1 byte)

• HP-FEBE—Far-end block error (high-order path)

• HP-LOP—Loss of pointer (high-order path)

• HP-AIS—High-order-path alarm indication signal

• HP-FERF—Far-end remote fail (high-order path)

• HP-UNEQ—Unequipped (high-order path)

• HP-PLM—Payload label mismatch (high-order path)

• HP-ES—Errored seconds (near-end high-order path)

• HP-SES—Severely errored seconds (near-end high-order path)

• HP-UAS—Unavailable seconds (near-end high-order path)

• HP-ES-FE—Errored seconds (far-end high-order path)

• HP-SES-FE—Severely errored seconds (far-end high-order path)

• HP-UAS-FE—Unavailable seconds (far-end high-order path)

Received SDH overhead

Transmitted SDH overhead

Values of the received and transmitted SONET overhead:

• C2—Signal label. This byte is 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. This bye is 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 of an STS-N.

• Z3 and Z4—These bytes are allocated for future use.

Received path trace

Transmitted path trace

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.

ATM Status

ATM state information:

• HCS State—Status of the header check sequence. ATM uses the HCS field in the cell header in the cell delineation process to frame ATM cell boundaries. The HCS is an FCS-8 calculation over the first four octets of the ATM cell header.

• LOC—Current loss of cell (LOC) delineation state. OK means that no LOC is currently asserted.

ATM Statistics

ATM statistics for the interface:

• Uncorrectable HCS errors—Number of cells dropped because the cell delineation failed. These errors most likely indicate that a SONET/SDH layer problem has occurred.

• Correctable HCS errors—Number of correctable HCS errors that occurred. The cell delineation process can recover from these errors and locate the ATM cell boundary, although the framing process is not quite stable. The ATM cell is not dropped. This counter increases when the cell delineation process changes its state from present to sync (for example, when a cable is plugged into the interface).

The following error statistics are from the framer:

• Tx cell FIFO overruns—Number of overruns in the transmit FIFO.

• Rx cell FIFO overruns—Number of overruns in the receive FIFO.

• Rx cell FIFO underruns—Number of underruns in the receive FIFO.

• Input cell count—Number of ATM cells received by the interface (not including idle cells).

• Output cell count—Number of ATM cells transmitted by the interface (including idle cells).

• Output idle cell count—Number of idle cells sent by the port. When ATM has nothing to send, it sends idle cells to fill the time slot.

• Output VC queue drops—Number of packets dropped by a port on the PIC. Packets are dropped because of queue limits on the VCs.

The following error statistics are from the SAR:

• Input no buffers—Number of AAL5 packets dropped because no channel blocks or buffers were available to handle them.

• Input length errors—Number of AAL5 packets dropped because their length was incorrect. Usually, these errors occur because a cell has been corrupted or lost, or because the length field was corrupted. They can also mean the AAL5 length field was zero.

• Input timeouts—Number of AAL5 packets dropped because of a reassembly timeout.

• Input invalid VCs—Number of AAL5 packets dropped because the header was unrecognized (because the VC was not correct or not configured).

• Input bad CRCs—Number of AAL5 packets dropped because of frame check sequence errors.

• Input OAM cell no buffers—Number of received OAM cells or raw cells dropped because no buffers were available to handle them.

• L2 circuit out-of-sequence packets—(Layer 2 AAL5 mode) Number of AAL5 packets that are out of sequential order.

• Denied packets count—The number of packets dropped due to VLAN priority deny packets or due to an error forwarding configuration that might cause a negative frame length, that is, the stripping size is larger than the packet size.

Packet Forwarding Engine configuration

Information about the configuration of the Packet Forwarding Engine:

• Destination slot—FPC slot number.

CoS information

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.

VPI

(ATM2) Virtual path identifier information:

• Flags—VPI flags can be one or more of the following:

  • Active (virtual path is up)

  • OAM (operation and maintenance is enabled)

  • Shaping (shaping is configured)

• CBR, Peak

• OAM, Period—Interval at which OAM F4 loopback cells are sent.

• Up count—Number of F4 OAM cells required to consider the virtual path up; the range is 1 through 255.

• Down count—Number of F4 OAM cells required to consider the virtual path down; the range is 1 through 255.

• Total down time—Total number of seconds the VPI has been down since it was opened, using the format Total down time: hh:mm:ss or Never.

• Last down—Time of last Down transition, using the format Last down: hh:mm:ss ago or Never.

• OAM F4 cell statistics—(Nonpromiscuous mode) OAM F4 statistics:

  • Total received—Number of OAM F4 cells received.

  • Total sent—Number of OAM F4 cells sent.

  • Loopback received—Number of OAM F4 loopback cells received.

  • Loopback sent—Number of OAM F4 loopback cells sent.

  • Last received—Time at which the last OAM F4 cell was received.

  • Last sent—Time at which the last OAM F4 cell was sent.

  • RDI received—Number of OAM F4 cells received with the remote defect indication bit set.

  • RDI sent—Number of OAM F4 cells sent with the RDI bit set.

  • AIS received—Number of OAM F4 cells received with the alarm indication signal bit set.

  • AIS sent—Number of OAM F4 cells sent with the AIS bit set.

Traffic statistics:

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

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

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

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

Logical interface

Name of the logical interface.

Index

Logical interface index number, which reflects its initialization sequence.

SNMP ifIndex

Logical interface SNMP interface index number.

Generation

Unique number for use by Juniper Networks technical support only.

Flags

Information about the logical interface. Possible values are described in the “Logical Interface Flags” section under Common Output Fields Description.

Input packets

Number of packets received on the logical interface.

Output packets

Number of packets transmitted on the logical interface.

Encapsulation

Encapsulation on the logical interface.

Traffic statistics

Total number of bytes and packets received and transmitted on the logical interface. These statistics are the sum of the local and transit statistics. When a burst of traffic is received, the value in the output packet rate field might briefly exceed the peak cell rate. It takes a while (generally, less than 1 second) for this counter to stabilize.

Local statistics

Statistics for traffic received from and transmitted to the Routing Engine. When a burst of traffic is received, the value in the output packet rate field might briefly exceed the peak cell rate. It takes a while (generally, less than 1 second) for this counter to stabilize.

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the value in the output packet rate field might briefly exceed the peak cell rate. It takes a while (generally, less than 1 second) for this counter to stabilize.

Input packets

Number of packets received on the logical interface.

Output packets

Number of packets transmitted on the logical interface.

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP address of the interface is also displayed.

Protocol

Protocol family configured on the logical interface.

MTU

MTU size on the logical interface.

Generation

Unique number for use by Juniper Networks technical support only.

Route table

Routing table in which the logical interface address is located. For example, 0 refers to the routing table inet.0.

Flags

Information about the protocol family flags. Possible values are described in the “Family Flags” section under Common Output Fields Description.

Addresses, Flags

Information about the address flags. Possible values are described in the “Addresses Flags” section under Common Output Fields Description.

Destination

IP address of the remote side of the connection.

Local

IP address of the logical interface.

Broadcast

Broadcast address.

Generation

Unique number for use by Juniper Networks technical support only.

VCI

Virtual circuit identifier number and information:

• Flags—VCI flags:

  • Active—VCI is up and in working condition.

  • CCC down—VCI CCC is not in working condition.

  • Closed—VCI is closed because the user disabled the logical or physical interface from the CLI.

  • Configured—VCI is configured.

  • Down—VCI is not in working condition. The VCI might have alarms, defects, F5 AIS/RDI, or no response to OAM loopback cells.

  • ILMI—VCI is up and in working condition.

  • OAM—OAM loopback is enabled.

  • Multicast—VCI is a multicast VCI or DLCI.

  • Multipoint destination—VCI is configured as a multipoint destination.

  • None—No VCI flags.

  • Passive-OAM—Passive OAM is enabled.

  • Shaping—Shaping is enabled.

  • Sustained—Shaping rate is set to Sustained.

  • Unconfigured—VCI is not configured.

• Total down time—Total number of seconds the VCI has been down, using the format Total down time: hh:mm:ss orNever.

• Last down—Time of last Down transition, using the format Last down: hh:mm:ss.

• EPD threshold—(ATM2 only) Threshold at which a packet is dropped when the queue size (in number of cells) exceeds the early packet-discard (EPD) value.

VCI (continued)

IMA group properties

IMA group alarms

IMA group defects

IMA Group state

IMA group media