show interfaces (for Channelized E1 Interfaces)
Syntax
show interfaces ds-fpc/pic/port:ds-0 channel<brief | detail | extensive> <interface-name> <interval><destination-classdestination-class-name> <source-classsource-class-name>
show interfaces ds-fpc/pic/port:ds-0 channel<brief | detail | extensive> <media>
show interfaces ds-fpc/pic/port:ds-0 channel<brief | detail | extensive> <statistics>Description
Display status information about Channelized E1 router interfaces.
Options
none—Display information about all interfaces.
brief—(Optional) Display brief interface information.
detail—(Optional) Display detailed interface information.
extensive—(Optional) Display very detailed interface information.
destination-classdestination-class-name—(Optional) Name of a logical grouping of prefixes that count packets having the destination address matching those prefixes. Whenever a destination class is specified, you must also specify a particular logical interface, not all interfaces.
ds-fpc/pic/port:ds0 channel—Name of an interface.
interval—(Optional) Display Channel Service Unit (CSU) interface alarm and error count in 15-minute intervals for the past 24 hours. If the system has been up for less than 24 hours, the maximum number of intervals available is displayed.
media—(Optional) Display media-specific information about network interfaces.
source-classsource-class-name—(Optional) Name of a logical grouping of prefixes that count packets having the source address matching those prefixes. Whenever a source class is specified, you must also specify a particular logical interface, not all interfaces.
statistics—(Optional) Display static interface statistics.Required Privilege Level
Sample Output
show interfaces (standard) (for Channelized E1 Interfaces)show interfaces brief (for Channelized E1 Interfaces)show interfaces detail (for Channelized E1 Interfaces)show interfaces extensive (for Channelized E1 Interfaces)show interfaces interval (for Channelized E1 Interfaces)show interfaces media (for Channelized E1 Interfaces)show interfaces statistics (for Channelized E1 Interfaces)Output Fields at a Glance
Table 11 summarizes the information included in the output fields of each
show interfacescommand option for Channelized E1 interfaces. In this table, output fields are listed in alphabetical order. In Table 12, the output fields are listed in more detail in the order in which they are displayed.
Table 12:
State of the interface. Possible values are described in Enabled. Information about the physical device. Possible values are described in Device Flags. Information about the link. Possible values are described in Link Flags. (Extensive output only) Settings for link management can be either ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The format is (ANSI or ITU) LMI settings:value,value...xxseconds, wherevaluecan 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)
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).
intervalseconds—The time in seconds between successive keepalive requests. The range is10 secondsthrough32767 seconds, with a default of10 seconds.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.
Not-configured—CHAP was not configured on the interface.Success—CHAP authentication was successful.Fail—CHAP authentication failed.Chap-Resp-received—Received response for the challenge sent, but not yet moved into the Success state. (Most likely with RADIUS authentication.)Chap-Resp-sent—Response sent for the challenge received.Chap-Chal-sent—Challenge sent.Chap-Chal-received—Challenge received but response not yet sent. (Extensive output only) Input errors on the interface. The following paragraphs explain the nonobvious counters:
Errors—Sum of the incoming 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.Invalid VCs—Number of cells that arrived for a nonexistent VC.Framing errors—Sum of AAL5 packets that have FCS errors, AAL5 packets that have reassembly timeout errors, and AAL5 packets that have length errors.Bucket Drops—Drops due to traffic load exceeding the interface transmit/receive leaky bucket configuration. The default is off.Giants—Frames received that are larger than the giant threshold.Runts—Frames received that are smaller than the runt threshold.Policed discards—Frames that the incoming packet match code discarded because they were not recognized or of interest. Usually, this field reports protocols that the JUNOS software does not handle, such as CDP.L3 incompletes—Increments when the incoming packet fails Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with less than 20 bytes of available IP header would be discarded and this counter would increment.L2 channel errors—This counter increments when the software could not find a valid logical interface for an incoming frame.L2 mismatch timeouts—Count of malformed or short packets that cause the incoming packet handler to discard the frame as unreadable.SRAM errors—This counter increments when a hardware error has occurred in the SRAM on the PIC. The value in this field should always be 0. If it increments, the PIC is broken.HS link FCS errors—Number of errors on the high-speed links between the ASICs responsible for handling the router interfaces. (Extensive output only) Output errors on the interface. The following paragraphs explain the nonobvious counters:
Carrier transitions—Number of times the interface has gone from down to up. This number should not increment quickly, increasing only when the cable is unplugged, the far-end system is powered down and up, or a similar problem occurs. If it increments quickly (perhaps once every 10 seconds), then either the cable, the far-end system, or the PIC is broken.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 for 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 broken hardware. E1 media-specific defects that can render the interface unable to pass 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 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. (Extensive output only) 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.
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 FrameSEFS-S—Severely Errored Framing Seconds (section)SES—Severely Errored SecondsUAS—Unavailable SecondsYELLOW—Errors at the remote site receiver
Policing bucket—Configured state of the Rx policer.Shaping bucket—Configured state of the Tx 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. BERT (Bit Error Rate Testing) checks the quality of the line. This output only appears when BERT is run on the interface (see test interface bert-start).
Destination slot—FPC slot number.PLP byte—Packet Level Protocol byte.Stream number—Stream used by the ASIC on the FPC.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 Bytes—Number of bytes allocated to the queue. This value is only nonzero 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 will only transmit up to the configured bandwidth, even if there is excess bandwidth available. Ifnoneis configured, the queue will transmit beyond the configured bandwidth if there is bandwidth available. 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 a while (generally, less than 1 second) for this counter to stabilize. Information about the protocol family flags. Possible values are described in Family Flags. Information about the address flags. Possible values are described in Address Flags.
Channelized E1 Show Interfaces Output Field Summary in Order of Appearance