show interfaces (Channelized STM1)
Syntax
show interfaces e1-fpc/pic/port:e1channel<brief | detail | extensive | terse><descriptions><media><snmp-indexsnmp-index><statistics>Release Information
Command introduced before JUNOS Release 7.4.
Description
(M-series and T-series routing platforms only) Display status information about the specified channelized STM1 interface.
Options
e1-fpc/pic/port:e1channel—Display 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-indexsnmp-index—(Optional) Display information for the specified SNMP index of the interface.
statistics—(Optional) Display static interface statistics.Required Privilege Level
List of Sample Output
show interfaces extensive (Channelized STM1, SDH)Output Fields
Table 84 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.
State of the interface. Possible values are described in Enabled Field.
Physical interface's index number, which reflects its initialization sequence.
Unique number for use by Juniper Networks technical support only.
Whether loopback is enabled and the type of loopback (
localorremote).Frame check sequence on the interface (either
16or32). The default is16bits.Physical layer framing format used on the link. It can be
G704,G704-NO-CRC4, orUnframed. The default isG704.(Channelized STM1 IQ interfaces only) Name and interface index of the interface to which a particular child interface belongs.
Noneindicates that this interface is the top level.Information about the physical device. Possible values are described in Device Flags.
Information about the interface. Possible values are described in Interface Flags.
Information about the link. Possible values are described in Link Flags.
Current interface hold-time up and hold-time down, in milliseconds.
(PPP and HDLC) Configured settings for keepalives.
intervalseconds—The time in seconds between successive keepalive requests. The range is10seconds through32,767seconds, with a default of10seconds.down-countnumber—The number of keepalive packets a destination must fail to receive before the network takes a link down. The range is1through255, with a default of3.up-countnumber—The number of keepalive packets a destination must receive to change a link's status from down to up. The range is1through255, with a default of1.(Frame Relay) Local Management Interface settings. The format is
(ANSI or ITU) LMI settings:value,value...xxseconds, wherevaluecan be:(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 isInput:nn(last seenhh:mm:ssago).Output—Number of packets sent out on the interface (nn) and how much time has passed since the last packet was sent. The format isOutput:nn(last senthh:mm:ssago).(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.(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.(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 forn392dteorn393dceintervals. (SeeLMI settings.)(Frame Relay, displayed only from the DTE) Number of DLCIs configured from the DCE.
(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.Date, time, and how long ago the interface went from down to up. The format is
Last flapped:year-month-day hour:minute:secondtimezone(hour:minute:secondago). For example,Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).Time when the statistics for the interface were last set to zero.
Number and rate of bytes and packets received and transmitted on the physical interface.
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.Invalid VCs—Number of cells that arrived for a nonexistent VC.Framing errors—Number of packets received with an invalid frame checksum (FCS).Bucket Drops—Drops caused by the traffic load exceeding the interface transmit/receive leaky bucket configuration. The default isoff.Giants—Number of frames received that are larger than the giant threshold.Runts—Number of frames received that are smaller than the runt threshold.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 software 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.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 fromdowntoup. 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.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.
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.
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 thanOKindicates a problem.The E1 media-specific error types can be:
AIS—Alarm indication signalBEE—Bit errorBES—Bit error secondsBPV—Bipolar violationCS—Carrier stateES—Errored secondsEXZ—Excessive zerosFEBE—Far-end block errorLCV—Line code violationLES—Line error secondsLOF—Loss of frameLOS—Loss of signalPCV—Pulse code violationSEF—Severely errored framingSEFS-S—Severely errored framing seconds (section)SES—Severely errored secondsUAS—Unavailable secondsYELLOW—Errors at the remote site receiverNames of the transmit queues and their associated statistics for each E1 channel on the Channelized STM1 to E1 PIC.
BERT (bit error rate test) checks the quality of the line. This output appears only when a BERT is run on the interface.
Active alarms and defects, plus counts of specific SDH
errors with detailed information.Active alarms and defects, plus counts of specific SDH errors with detailed information.
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 thanOKindicates a problem.
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)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 thanOKindicates a problem.
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 signalHP-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)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 thanOKindicates a problem.
TU-BIP-2—Bit interleaved parity for SONET line overheadTU-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)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.K1andK2—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 1of an STS-Nsignal. 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.Z3andZ4—Allocated for future use.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.
Information about the configuration of the Packet Forwarding Engine:
Destination slot—FPC slot number.PLP byte—Packet Level Protocol byte.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. Possible values arelowandhigh.Limit—Displayed if rate limiting is configured for the queue. Possible values arenoneandexact. Ifexactis configured, the queue transmits only up to the configured bandwidth, even if excess bandwidth is available. Ifnoneis configured, the queue transmits beyond the configured bandwidth if bandwidth is available.State of the interface. Possible values are described in Enabled Field.
Logical interface index number, which reflects its initialization sequence.
Information about the logical interface. Possible values are described in Logical Interface Flags.
Protocol family configured on the logical interface, such as
iso,inet6, ormpls.Unique number for use by Juniper Networks technical support only.
Routing table in which the logical interface address is located. For example,
0refers to the routing table inet.0.Information about the protocol family flags. Possible values are described in Family Flags.
Information about the address flags. Possible values are described in Addresses, Flags.
(Frame Relay) DLCI number of the logical interface. The following DLCI information is displayed:
Flags,Total down time,Last down, andTraffic statistics.Flagsis 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.(Frame Relay) Data-link connection identifier (DLCI) statistics.
show interfaces extensive
(Channelized STM1, SDH)user@host>show interfaces e1-1/0/0:1 extensivePhysical interface: e1-1/0/0:1, Enabled, Physical link is UpInterface index: 148, SNMP ifIndex: 285, Generation: 2915Link-level type: Frame-relay, MTU: 1504, SDH mode, Speed: E1, Loopback: None, FCS: 16, Framing: G704Device flags : Present RunningInterface flags: Point-To-Point SNMP-TrapsLink flags : Keepalives DTEANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 secondsLMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)DTE statistics:Enquiries sent : 43186Full enquiries sent : 8515Enquiry responses received : 43185Full enquiry responses received : 8515DCE statistics:Enquiries received : 0Full enquiries received : 0Enquiry responses sent : 0Full enquiry responses sent : 0Common statistics:Unknown messages received : 0Asynchronous updates received : 0Out-of-sequence packets received : 0Keepalive responses timedout : 0Nonmatching DCE-end DLCIs:2Hold-times : Up 0 ms, Down 0 msLast flapped : 2002-05-23 17:02:59 PDT (17:23:45 ago)Statistics last cleared: NeverTraffic statistics:Input bytes : 592 48 bpsOutput bytes : 644 48 bpsInput packets: 46 0 ppsOutput packets: 46 0 ppsInput errors:Errors: 0, Drops: 9, Framing errors: 0, Policed discards: 0,L3 incompletes: 0, L2 channel errors: 11, L2 mismatch timeouts: 0,HS link CRC errors: 0, SRAM errors: 0Output errors:Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0DS1 alarms : NoneDS1 defects : NoneSDH alarms : NoneSDH defects : NoneE1 media: Seconds Count StateSEF 0 0 OKBEE 0 0 OKAIS 124 1 OKLOF 124 1 OKLOS 0 0 OKYELLOW 0 0 OKBPV 0 0EXZ 0 0LCV 0 0PCV 0 0CS 0 0FEBE 0 0LES 124ES 125SES 124SEFS 124BES 0UAS 37Interface transmit queues:B/W WRR Packets Bytes Drops ErrorsQueue0 95 95 0 0 0 0Queue1 5 5 529 6348 0 0HDLC configuration:Giant threshold: 0, Runt threshold: 0Timeslots : All activeLine encoding: HDB3DS1 BERT configuration:BERT time period: 10 seconds, Elapsed: 0 secondsInduced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)SDH PHY: Seconds Count StatePLL Lock 0 0 OKPHY Light 0 0 OKSDH regenerator section:RS-BIP8 0 0OOF 125 1 OKLOS 125 1 OKLOF 125 1 OKRS-ES 125RS-SES 125RS-SEFS 125SDH multiplex section:MS-BIP24 0 0MS-FEBE 0 0MS-FERF 0 0 OKMS-AIS 125 1 OKBERR-SF 0 0 OKBERR-SD 0 0 OKMS-ES 125MS-SES 125MS-UAS 115MS-ES-FE 0MS-SES-FE 0MS-UAS-FE 0SDH path:HP-BIP8 0 0HP-FEBE 0 0HP-LOP 0 0 OKHP-AIS 125 1 OKHP-FERF 0 0 OKHP-UNEQ 0 0 OKHP-PLM 125 1 OKHP-ES 125HP-SES 125HP-UAS 115HP-ES-FE 0HP-SES-FE 0HP-UAS-FE 0SDH tu:TU-BIP2 0 0TU-FEBE 124 1TU-LOP 0 0 OKTU-AIS 124 1 OKTU-FERF 124 1 OKTU-UNEQ 0 0 OKTU-PLM 124 1 OKTU-ES 125TU-SES 125TU-UAS 115TU-ES-FE 0TU-SES-FE 0TU-UAS-FE 0Received SDH overhead:F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00S1 : 0x00, C2 : 0x02, C2(cmp) : 0x02, F2 : 0x00Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00, V5 : 0x02V5(cmp) : 0x02Transmitted SDH overhead:F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00S1 : 0x00, C2 : 0x02, F2 : 0x00, Z3 : 0x00Z4 : 0x00, V5 : 0x02Received path trace:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................Transmitted path trace:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................Packet Forwarding Engine configuration:Destination slot: 1, PLP byte: 2 (0x07)CoS transmit queue Bandwidth Buffer Priority Limit% bps % usec0 best-effort 95 1945600 95 0 low none3 network-control 5 102400 5 0 low noneLogical interface e1-1/0/0:1.0 (Index 10) (SNMP ifIndex 369) (Generation 496)Flags: Point-To-Point SNMP-Traps Encapsulation: PPPProtocol inet, MTU: 1500, Generation: 575, Route table: 0Flags: NoneAddresses, Flags: Is-Preferred Is-PrimaryDestination: 19.19.19.3, Local: 19.19.19.4, Broadcast: Unspecified,Generation: 975DLCI 100Flags: Active, Dce-configuredTotal down time: 0 sec, Last down: NeverTraffic statistics:Input bytes : 0Output bytes : 0Input packets: 0Output packets: 0DLCI statistics:Active DLCI :2 Inactive DLCI : 0