Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show interfaces (Channelized STM1)

 

Syntax

Release Information

Command introduced before Junos OS Release 7.4.

Description

(M Series and T Series routers only) Display status information about the specified channelized STM1 interface.

Options

e1-fpc/pic/port:e1channelDisplay standard status information about the specified channelized STM1 interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege Level

view

List of Sample Output

show interfaces extensive (Channelized STM1, SDH)

Output Fields

Table 1 lists the output fields for the show interfaces (all Channelized STM1 interfaces) command. Output fields are listed in the approximate order in which they appear.

Table 1: Channelized STM1 show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface 

Physical interface

Name of the physical interface.

All levels

Enabled

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

All levels

Interface index

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

detail extensive none

SNMP ifIndex

SNMP index number for the physical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

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

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Framing

Physical layer framing format used on the link. It can be G704, G704-NO-CRC4, or Unframed. The default is G704.

All levels

Parent

(Channelized STM1 IQ interfaces only) Name and interface index of the interface to which a particular child interface belongs. None indicates that this interface is the top level.

All levels

Device flags

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

All levels

Interface flags

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

All levels

Link flags

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

All levels

Hold-times

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

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

  • intervalseconds—The time in seconds between successive keepalive requests. The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

  • down-count number—The number of keepalive packets a destination must fail to receive before the network takes a link down. The range is1 through 255, with a default of 3.

  • up-count number—The number of keepalive packets a destination must receive to change a link’s status from down to up. The range is 1 through 255, with a default of 1.

detail extensive none

Keepalive statistics

(PPP and HDLC) Information about keepalive packets.

  • Input—Number of keepalive packets received by PPP.

    • (last seen 00:00:00 ago)—Time since the last keepalive packet was received, in the formathh:mm:ss.

  • Output—Number of keepalive packets sent by PPP and how long ago the last keepalive packets were sent and received.

    • (last seen 00:00:00 ago)—Time since the last keepalive packet was sent, in the format hh:mm:ss.

detail extensive none

ANSI LMI settingsor ITU LMI settings

(Frame Relay) Local Management Interface settings. The format is (ANSI or ITU) LMI settings: value, value... xx seconds, where value can be:

  • n391dte—DTE full status polling interval (1- 255)

  • n392dce—DCE error threshold (1-10)

  • n392dte—DTE error threshold (1-10)

  • n393dce—DCE monitored event count (1-10)

  • n393dte—DTE monitored event count (1-10)

  • t391dte—DTE polling timer (5-30 seconds)

  • t392dce—DCE polling verification timer (5-30 seconds)

detail extensive none

LMI

(Frame Relay) Statistics about the link management.

  • Input—Number of packets coming in on the interface (nn) and how much time has passed since the last packet arrived. The format is Input: nn (last seen hh:mm:ss ago).

  • Output—Number of packets sent out on the interface (nn) and how much time has passed since the last packet was sent. The format is Output: nn (last seen hh:mm:ss ago).

detail extensive none

DTE statistics

(Frame Relay) Statistics about messages transmitted from the data terminal equipment (DTE) to the data circuit-terminating equipment (DCE):

  • Enquiries sent—Number of link status enquiries sent from the DTE to the DCE.

  • Full enquiries sent—Number of full enquiries sent from the DTE to the DCE.

  • Enquiry responses received—Number of enquiry responses received by the DTE from the DCE.

  • Full enquiry responses received—Number of full enquiry responses sent from the DTE to the DCE.

detail extensive none

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

  • Enquiries received—Number of enquiries received by the DCE from the DTE.

  • Full enquiries received—Number of full enquiries received by the DCE from the DTE.

  • Enquiry responses sent—Number of enquiry responses sent from the DCE to the DTE.

  • Full enquiry responses sent—Number of full enquiry responses sent from the DCE to the DTE.

detail extensive none

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

  • Unknown messages received—Number of received packets that do not fall into any category.

  • Asynchronous updates received—Number of link status peer changes received.

  • Out-of-sequence packets received—Number of packets for which the sequence of the packets received is different from the expected sequence.

  • Keepalive responses timedout—Number of keepalive responses that timed out when no LMI packet was reported for n392dte or n393dce intervals. (See LMI settings.)

detail extensive none

Nonmatching DCE-end DLCIs

(Frame Relay, displayed only from the DTE) Number of DLCIs configured from the DCE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

  • Conf-ack-received—Acknowledgment was received.

  • Conf-ack-sent—Acknowledgment was sent.

  • Conf-req-sent—Request was sent.

  • Down—LCP negotiation is incomplete (not yet completed or has failed).

  • Not-configured—LCP is not configured on the interface.

  • Opened—LCP negotiation is successful.

detail extensive none

NCP state

(PPP) Network Control Protocol state.

  • Conf-ack-received—Acknowledgment was received.

  • Conf-ack-sent—Acknowledgment was sent.

  • Conf-req-sent—Request was sent.

  • Down—NCP negotiation is incomplete (not yet completed or has failed).

  • Not-configured—NCP is not configured on the interface.

  • Opened—NCP negotiation is successful.

detail extensive none

CHAP state

(PPP) Displays the state of the Challenge Handshake Authentication Protocol (CHAP) during its transaction.

  • Chap-Chal-received—Challenge was received but response not yet sent.

  • Chap-Chal-sent—Challenge was sent.

  • Chap-Resp-received—Response was received for the challenge sent, but CHAP has not yet moved into the Success state. (Most likely with RADIUS authentication.)

  • Chap-Resp-sent—Response was sent for the challenge received.

  • Closed—CHAP authentication is incomplete.

  • Failure—CHAP authentication failed.

  • Not-configured—CHAP is not configured on the interface.

  • Success—CHAP authentication was successful.

detail extensive none

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

detail extensive none

Statistics last cleared

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

detail extensive

Traffic statistics

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.

detail extensive

Input errors

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

  • Errors—Sum of the incoming frame aborts 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).

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

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

  • SRAM errors—Number of hardware errors that occurred in the static RAM (SRAM) on the PIC. If the value of this field increments, the PIC is malfunctioning.

extensive

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 then 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 aborts 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.

extensive

DS1 alarms

DS1 defects

E1 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 turn on the red or yellow alarm LED on the craft interface. The following lists all possible alarms and defects. For complete explanations of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.

  • LOS—Loss of signal.

  • LOF—Loss of frame.

  • AIS—Alarm indication signal.

  • YLW—Yellow alarm. Indicates errors at the remote site receiver.

detail extensive none

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.

Note: For controller-based SONET PICs, the SDH alarms and SDH defects output in the show interface cstm1 extensive command output only shows the section and line level defects. The path level defects can be found under the SONET (so) interface output.

All levels

E1 media

Active alarms and defects, plus counts of specific E1 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.

Error types can be:

  • AIS—Alarm indication signal

  • BEE—Bit error

  • BES—Bit error seconds

  • BPV—Bipolar violation

  • CS—Carrier state

  • ES—Errored seconds

  • EXZ—Excessive zeros

  • FEBE—Far-end block error

  • LCV—Line code violation

  • LES—Line error seconds

  • LOF—Loss of frame

  • LOS—Loss of signal

  • PCV—Pulse code violation

  • SEF—Severely errored framing

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

  • SES—Severely errored seconds

  • UAS—Unavailable seconds

  • YELLOW—Errors at the remote site receiver

extensive

Interface transmit queues

Names of the transmit queues and their associated statistics for each E1 channel on the Channelized STM1-to-E1 PIC.

  • B/W—Queue bandwidth as a percentage of the total interface bandwidth.

  • WRR—Weighted round-robin (in percent).

  • Packets—Number of packets transmitted.

  • Bytes—Number of bytes transmitted.

  • Drops—Number of packets dropped.

  • Errors—Number of packet errors.

extensive

HDLC configuration

Information about the HDLC configuration.

  • Giant threshold—Giant threshold programmed into the hardware.

  • Runt threshold—Runt threshold programmed into the hardware.

  • Timeslots—Configured time slots for the interface.

  • Line encoding—Line encoding used. It is always HDB3.

extensive

DS1 BERT configuration

BERT (bit error rate test) checks the quality of the line. This output appears only when a BERT is run on the interface.

  • BERT time period—Configured total time period that the BERT is to run.

  • Elapsed—Actual time elapsed since the start of the BERT (in seconds).

  • Induced error rate—Configured rate at which the bit errors are induced in the BERT pattern.

  • Algorithm—Type of algorithm selected for the BERT.

detail extensive none

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

extensive

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)

extensive

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)

extensive

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)

extensive

SDH tu

Active alarms and defects, plus counts of specific SDH tributary unit (TU) 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:

  • TU-BIP-2—Bit interleaved parity for SONET line overhead

  • TU-FEBE—(near-end TU)

  • TU-LOP—Loss of pointer (near-end TU)

  • TU-AIS—Alarm indication signal (near-end TU)

  • TU-FERF—(near-end TU)

  • TU-UNEQ—Unequipped (near-end TU)

  • TU-PLM—Payload label mismatch (near-end TU)

  • TU-ES—Errored seconds (near-end TU)

  • TU-SES—Severely errored seconds (near-end TU)

  • TU-UAS—Unavailable seconds (near-end TU)

  • TU-ES-FE—Errored seconds (far-end TU)

  • TU-SES-FE—Severely errored seconds (far-end TU)

  • TU-UAS-FE—Unavailable seconds (far-end TU)

extensive

Received SDH overhead

Transmitted SDH 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 signal.

  • Z3 and Z4—Allocated for future use.

extensive

Received path trace

Transmitted path trace

Channelized OC12 interfaces allow path trace bytes to be sent inband across the SONET/SDH link. 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. This information is specific to each of the 12 channelized OC12 interfaces.

extensive

Packet Forwarding Engine configuration

Information about the configuration of the Packet Forwarding Engine:

  • Destination slot—FPC slot number.

  • PLP byte—Packet Level Protocol byte.

extensive

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.

extensive

Logical Interface 

Logical interface

Name of the logical interface.

All levels

Enabled

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

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Flags

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

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

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

detail extensive

Flags

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

detail extensive none

Addresses, Flags

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

detail extensive none

Destination

IP address of the remote side of the connection.

detail extensive none

Local

IP address of the logical interface.

detail extensive none

Broadcast

Broadcast address.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI information is displayed: Flags, Total down time, Last down, and Traffic statistics. Flags is one or more of the following:

  • Active—Set when the link is active and the DTE and DCE are exchanging information.

  • Down—Set when the link is active, but no information is received from the DCE.

  • Unconfigured—Set when the corresponding DLCI in the DCE is not configured.

  • Configured—Set when the corresponding DLCI in the DCE is configured.

  • Dce-configured—Displayed when the command is issued from the DTE.

detail extensive none

DLCI statistics

(Frame Relay) Data-link connection identifier (DLCI) statistics.

  • Active DLCI—Number of active DLCIs.

  • Inactive DLCI—Number of inactive DLCIs.

detail extensive none

Sample Output

show interfaces extensive (Channelized STM1, SDH)

user@host> show interfaces e1-1/0/0:1 extensive