show interfaces (Channelized OC3 IQ)
Syntax
show interfaces (type-fpc/pic/port<:channel><:channel><:channel>)<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 OC3 IQ interface. (You can include wildcard characters in the interface name to display more than one channelized OC3 IQ interface. See Interface Types.)
Options
type-fpc/pic/port:channel:channel:channel—Interface type with optional corresponding channel levels. The interface type can be one of the following:
type-fpc/pic/port—For the physical interface,typeiscoc3.For the clear channel,typeisso(for OC3).type-fpc/pic/port:channel—At the first level of channelization,typecan becoc1 (channelized OC1),ct3(fromcoc1), ort3(fromcoc1).type-fpc/pic/port:channel:channel—At the second level of channelization,typecan bect1(fromcoc1orct3)ort1(fromcoc1orct3).type-fpc/pic/port:channel:channel:channel—At the third level of channelization,typecan beds(fromct1).
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 OC3 IQ) (Physical)show interfaces extensive (Channelized OC1 on Channelized OC3 IQ)show interfaces extensive (Channelized T1 on Channelized OC3 IQ)show interfaces extensive (DS0 on Channelized OC3 IQ)Output Fields
Table 76 lists the output fields for the
show interfaces(all Channelized OC 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.
SONET/SDH reference clock source. It can be
InternalorExternal. Clocking is configured and displayed only for channel 0.Whether loopback is enabled and the type of loopback (
localorremote).Whether loopback is enabled on a SONET/SDH interface, and the type of loopback (
localorremote).Frame check sequence on the interface (either
16or32). The default is16-bit.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.
(Frame Relay) Settings for Local Management Interface (LMI). 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) Number of DLCIs configured from the DCE, displayed only from the DTE.
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.
E1or T1 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.
Counts of T1 or E1 media-specific errors.
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.The T1 or E1 media-specific error types are:
SEF—Severely errored framingBEE—Bit errorAIS—Alarm indication signalLOF—Loss of frameLOS—Loss of signalYELLOW—Errors at the remote site receiverBPV—Bipolar violationEXZ—Excessive zerosLCV—Line code violationPCV—Pulse code violationCS—Carrier stateFEBE—Far-end block error (E1 only)LES—Line error secondsES—Errored secondsBES—Bit error secondsSES—Severely errored secondsSEFS—Severely errored framing secondsUAS—Unavailable secondsNumber 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.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 caused by traffic load exceeding the interface transmit/receive leaky bucket configuration. The default is off.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.HS link FIFO overflows—Number of FIFO overflows on the high-speed links between the ASICs responsible for handling the router interfaces.Resource errors—Sum of transmit drops.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.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.Resource errors—Sum of transmit drops.Total number of egress queues supported on the specified interface.
CoS queue number and its associated user-configured forwarding class name.
Defects that can prevent the interface from passing packets:
Media-specific defects that can prevent the interface from passing packets. When a defect persists for a certain amount of time, 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, andSONET path.SONET virtual-tributary (VT) alarms and defects:
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.
BIP-B2—Bit interleaved parity for SONET line overheadREI-V—Remote error indication (near-end VT)LOP-V—Loss of pointer (near-end VT)AIS-V—Alarm indication signal (near-end VT)RDI-V—Remote defect indication (near-end VT)UNEQ-V—Unequipped (near-end VT)PLM-V—Payload label mismatch (near-end VT)ES-V—Errored seconds (near-end VT)SES-V—Severely errored seconds (near-end VT)UAS-V—Unavailable seconds (near-end VT)ES-VFE—Errored seconds (far-end VT)SES-VFE—Severely errored seconds (far-end VT)UAS-VFE—Unavailable seconds (far-end VT)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 thanOKindicates a problem.
BIP-B2—Bit interleaved parity for SONET line overheadREI-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. State other thanOKindicates a problem.
BIP-B3—Bit interleaved parity for SONET section overheadREI-P—Remote error indicationLOP-P—Loss of pointer (path)AIS-P—Path alarm indication signalRDI-P—Path remote defect indicationUNEQ-P—Path unequippedPLM-P—Path payload label mismatchES-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/SDH overhead:
F1—Section user channel byte. This byte is set aside for the purposes of users.
S1—Synchronization Status (S1). The S1 byte is located in the first STS-1 of an STS-N. Bits 5 through 8 convey the synchronization status of the network element.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 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 sectionActive 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)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.
Counts of T3 media-specific errors. For detailed definitions of the T3 (DS-3) error events (BPV, EXZ, LCV, PCV, and CCV) and performance parameters (LES, PES, PSES, CES, CSES, SEFS, and UAS), see RFC 2496.
The DS3 or E3 media-specific error types can be:
PLL Lock—Phase-locked loop out of lockReframing—Frame alignment recovery timeAIS—Alarm indication signalLOF—Loss of frameLOS—Loss of signalIDLE—Idle code detectedYELLOW—Errors at the remote site receiverBPV—Bipolar violationEXZ—Excessive zerosLCV—Line code violationPCV—(DS3 only) Pulse code violationCCV—(DS3 only) C-bit coding violationFEBE—(DS3 only) Far-end block errorLES—Line error secondsPES—(DS3 only) P-bit errored secondsPSES—(DS3 only) P-bit errored seconds (section)CES—(DS3 only) C-bit errored secondsCSES—(DS3 only) C-bit severely errored secondsSEFS—Severely errored framing secondsUAS—Unavailable secondsInformation 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.Timeslots—Configured time slots for the interface.Line encoding—Line encoding used. It is alwaysHDB3.Byte encoding—(T1 only) Byte encoding used:Nx64KorNx56K.Line encoding—Line encoding used. For T1, the value can beB8ZSorAMI. For E1, the value isHDB3.Data inversion—HDLC data inversion setting:EnabledorDisabled.Idle cycle flag—Idle cycle flags.Start end flag—Start and end flag.Name of the transmit queues and their associated statistics for each DS3 channel on the Channelized OC12 PIC.
Information about the DSU configuration. The last three lines (
Bit count,Error bit count, andLOSinformation) are displayed only if a BERT has ever been run on the interface.
Compatibility mode—CSU/DSU compatibility mode. It can beNone,Larscom,Kentrox, orDigital-Link.Scrambling—Payload scrambling. It can beEnabledorDisabled.Subrate—Configured subrate setting. Applies only whenDigital-Linkcompatibility mode is used. It can beDisabledor display units in kbps.FEAC loopback—(T3) Whether a far-end alarm and control (FEAC) loopback isActiveorInactive. This feature is used to send alarm or status information from the far-end terminal back to the near-end terminal and to initiate T3 loopbacks at the far-end terminal from the near-end terminal.Response—Whether the FEAC signal isEnabledorDisabled.Count—Number of FEAC loopbacks.(DS interfaces) BERT (bit error rate test) checks the quality of the line. This output appears only when a BERT is run on the interface.
Information about the configuration of the Packet Forwarding Engine:
Destination slot—FPC slot number.PLP byte—Packet Level Protocol byte.CoS transmit queue—The 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.Logical interface index number, which reflects its initialization sequence.
Information about the logical interface. Possible values are described in Logical Interface Flags.
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 awhile (generally, less than 1 second) for this counter to stabilize.
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 awhile (generally, less than 1 second) for this counter to stabilize.
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 awhile (generally, less than 1 second) for this counter to stabilize.
Protocol family configured on the logical interface, such as
iso,inet6, ormpls.(If the logical interface is configured as part of a multilink bundle.) Interface name for the multilink bundle.
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 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 OC3 IQ) (Physical)user@host>show interfaces extensive coc3-0/0/0Physical interface: coc3-0/0/0, Enabled, Physical link is DownInterface index: 128, SNMP ifIndex: 22, Generation: 11Description: pink coc3-0/0/0Link-level type: Controller, Clocking: Internal, SONET mode, Speed: OC3, Loopback: None,Parent: NoneDevice flags : Present Running DownInterface flags: Hardware-Down Point-To-Point SNMP-Traps 16384Link flags : NoneHold-times : Up 0 ms, Down 0 msCoS queues : 4 supportedLast flapped : 2005-01-27 16:39:21 PST (1w0d 22:09 ago)Statistics last cleared: NeverSONET alarms : PLL, LOSSONET defects : PLL, LOF, LOS, SEF, AIS-LSONET PHY: Seconds Count StatePLL Lock 681767 1 PLL Lock ErrorPHY Light 0 0 OKSONET section:BIP-B1 0 0SEF 681767 1 Defect ActiveLOS 681767 1 Defect ActiveLOF 681767 1 Defect ActiveES-S 681767SES-S 681767SEFS-S 681767SONET line:BIP-B2 0 0REI-L 0 0RDI-L 0 0 OKAIS-L 681767 1 Defect ActiveBERR-SF 0 0 OKBERR-SD 0 0 OKES-L 681767SES-L 681767UAS-L 681757ES-LFE 0SES-LFE 0UAS-LFE 0Received SONET overhead:F1 : 0x00, J0 : 0x00, K1 : 0xff, K2 : 0xffS1 : 0xffTransmitted SONET overhead:F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00S1 : 0x00show interfaces extensive
(Channelized OC1 on Channelized OC3 IQ)user@host>show interfaces extensive coc1-0/0/0:1Physical interface: coc1-0/0/0:1, Enabled, Physical link is DownInterface index: 133, SNMP ifIndex: 27, Generation: 16Link-level type: Controller, Clocking: Internal, SONET mode, Speed: 51840kbps, Loopback: None,Parent: coc3-0/0/0Interface index 128Device flags : Present Running Down 16384Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384Link flags : NoneHold-times : Up 0 ms, Down 0 msCoS queues : 4 supportedLast flapped : 2005-02-04 14:51:07 PST (00:00:35 ago)Statistics last cleared: NeverSONET alarms : NoneSONET defects : AIS-PSONET path:BIP-B3 0 0REI-P 0 0LOP-P 0 0 OKAIS-P 36 1 Defect ActiveRDI-P 0 0 OKUNEQ-P 0 0 OKPLM-P 0 0 OKES-P 36SES-P 36UAS-P 26ES-PFE 0SES-PFE 0UAS-PFE 0Received SONET overhead:C2 : 0xff, C2(cmp) : 0x01, F2 : 0x00, Z3 : 0x00Z4 : 0x00, S1(cmp) : 0x00Transmitted SONET overhead:C2 : 0x01, F2 : 0x00, Z3 : 0x00, Z4 : 0x00Received path trace:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................Transmitted path trace: router-1 coc1-0/0/0:16b 61 76 65 72 69 20 63 6f 63 31 2d 30 2f 30 2f router-1 coc1-0/0/30 3a 31 00 00 00 00 00 00 00 00 00 00 00 00 00 0:1.............00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................Packet Forwarding Engine configuration:Destination slot: 0 (0x00)show interfaces extensive
(Channelized T1 on Channelized OC3 IQ)user@host>show interfaces extensive ct1-0/0/0:1:1Physical interface: ct1-0/0/0:1:1, Enabled, Physical link is DownInterface index: 134, SNMP ifIndex: 62, Generation: 17Link-level type: Controller, Clocking: Internal, Speed: T1, Loopback: None, Framing: ESF,Parent: coc1-0/0/0:1Interface index 133Device flags : Present Running Down 16384Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384Link flags : NoneHold-times : Up 0 ms, Down 0 msCoS queues : 4 supportedLast flapped : 2005-02-04 14:54:35 PST (00:00:18 ago)Statistics last cleared: NeverDS1 alarms : NoneDS1 defects : AIS, LOFT1 media: Seconds Count StateSEF 1 1 OKBEE 1 1 OKAIS 18 1 Defect ActiveLOF 18 1 Defect ActiveLOS 0 0 OKYELLOW 0 0 OKBPV 0 0EXZ 0 0LCV 0 0PCV 0 0CS 0 0LES 18ES 18SES 18SEFS 18BES 0UAS 14DS1 BERT configuration:BERT time period: 10 seconds, Elapsed: 0 secondsInduced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)SONET alarms : NoneSONET defects : NoneSONET vt:BIP-BIP2 0 0REI-V 0 0LOP-V 0 0 OKAIS-V 19 1 Defect ActiveRDI-V 19 1 Defect ActiveUNEQ-V 0 0 OKPLM-V 19 1 Defect ActiveES-V 19SES-V 19UAS-V 9ES-VFE 0SES-VFE 0UAS-VFE 0Received SONET overhead:V5 : 0x07, V5(cmp) : 0x02Transmitted SONET overhead:V5 : 0x02Packet Forwarding Engine configuration:Destination slot: 0 (0x00)show interfaces extensive (DS0 on Channelized OC3 IQ)
user@host>show interfaces extensive ds-0/0/0:1:1:1Physical interface: ds-0/0/0:1:1:1, Enabled, Physical link is DownInterface index: 135, SNMP ifIndex: 63, Generation: 18Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 320kbps,Loopback: None, FCS: 16,Parent: ct1-0/0/0:1:1Interface index 134Device flags : Present RunningInterface flags: Hardware-Down Point-To-Point SNMP-Traps 16384Link flags : KeepalivesHold-times : Up 0 ms, Down 0 msCoS queues : 4 supportedLast flapped : NeverStatistics last cleared: NeverTraffic statistics:Input bytes : 0 0 bpsOutput bytes : 0 0 bpsInput packets: 0 0 ppsOutput packets: 0 0 ppsInput errors:Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,L2 mismatch timeouts: 0, HS link CRC errors: 0, Resource errors: 0Output errors:Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0, Resource errors: 0Queue counters: Queued packets Transmitted packets Dropped packets0 best-effort 0 0 01 expedited-fo 0 0 02 assured-forw 0 0 03 network-cont 0 0 0HDLC configuration:Giant threshold: 1514, Runt threshold: 2Timeslots : 1-5Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags, Start end flag: sharedDS0 BERT configuration:BERT time period: 10 seconds, Elapsed: 0 secondsInduced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)Packet Forwarding Engine configuration:Destination slot: 0, PLP byte: 4 (0x00)