Interface commands (show interfaces

show interfaces

Use the show interfaces EXEC command to display statistics for all interfaces configured on the router or access server. The resulting output varies, depending on the network for which an interface has been configured.

show interfaces [type number] [first] [last] [accounting]
show interfaces [type slot/port] [accounting] (for Cisco 7200 series, and for the Cisco 7500
series with a Packet over SONET Interface Processor)
show interface [type slot/port-adapter/port] [ethernet | serial] (for ports on VIP cards in the
Cisco 7500 series routers)

Syntax Description

type	(Optional) Interface type. Allowed values for type include async, bri0, ethernet, fastethernet, fddi, hssi, loopback, null, serial, tokenring, and tunnel. For the Cisco 4000 series, type can be e1, ethernet, fastethernet, fddi, serial, t1, and token. For the Cisco 4500 series, type can also include atm. For the Cisco 7000 family, type can be atm, e1, ethernet, fastethernet, fddi, serial, t1, and tokenring. For the Cisco 7500 seriestype can also include posi.
number	(Optional) Port number on the selected interface.
first last	(Optional) For the Cisco 2500 and 3000 ISDN Basic Rate Interface (BRI) only. The argument first can be either 1 or 2. The argument last can only be 2, indicating B-channels 1 and 2. D-channel information is obtained by using the command without the optional arguments.
accounting	(Optional) Displays the number of packets of each protocol type that has been sent through the interface.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.
port -adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The show interfaces command displays statistics for the network interfaces. The resulting display on the Cisco 7200 series shows the interface processors in slot order. If you add interface processors after booting the system, they will appear at the end of the list, in the order in which they were inserted.

If you use the show interfaces command on the Cisco 7200 series without the slot/port arguments, information for all interface types will be shown. For example, if you type show interfaces ethernet you will receive information for all ethernet, serial, Token Ring, and FDDI interfaces. Only by adding the type slot/port argument can you specify a particular interface.

If you enter a show interfaces command for an interface type that has been removed from the router or access server, interface statistics will be displayed accompanied by the following text: "Hardware has been removed."

If you use the show interfaces command on a router or access server for which interfaces are configured to use weighted fair queueing through the fair-queue interface command, additional information is displayed. This information consists of the current and high-water mark number of flows.

You will use the show interfaces command frequently while configuring and monitoring devices. The various forms of the show interfaces commands are described in detail in the sections immediately following this command.

Sample Display

The following is sample output from the show interfaces command. Because your display will depend on the type and number of interface cards in your router or access server, only a portion of the display is shown.

Router# show interfaces
Ethernet 0 is up, line protocol is up
  Hardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)
  Internet address is 131.108.28.8, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 4:00:00
  Last input 0:00:00, output 0:00:00, output hang never
  Last clearing of "show interface" counters 0:00:00
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 2000 bits/sec, 4 packets/sec
     1127576 packets input, 447251251 bytes, 0 no buffer
     Received 354125 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5332142 packets output, 496316039 bytes, 0 underruns
     0 output errors, 432 collisions, 0 interface resets, 0 restarts
---More---

Sample Display with Custom Output Queuing

The following shows partial sample output when custom output queuing is enabled:

Last clearing of "show interface" counters 0:00:06
Input queue: 0/75/0 (size/max/drops); Total output drops: 21
Output queues: (queue #: size/max/drops)
     0: 14/20/14  1: 0/20/6  2: 0/20/0 3: 0/20/0 4: 0/20/0 5: 0/20/0 
     6: 0/20/0 7: 0/20/0  8: 0/20/0  9: 0/20/0  10: 0/20/0

When custom queuing is enabled, the drops accounted for in the output queues result from bandwidth limitation for the associated traffic and leads to queue length overflow. Total output drops include drops on all custom queues as well as the system queue. Fields are described with the Weighted Fair Queuing output in Table 43.

Sample Display Including Weighted-Fair-Queuing Output

For each interface on the router or access server configured to use weighted fair queuing, the show interfaces command displays the information beginning with Input queue: in the following display:

Router# show interfaces
Ethernet 0 is up, line protocol is up
  Hardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)
  Internet address is 131.108.28.8, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 4:00:00
  Last input 0:00:00, output 0:00:00, output hang never
  Last clearing of "show interface" counters 0:00:00
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 2000 bits/sec, 4 packets/sec
     1127576 packets input, 447251251 bytes, 0 no buffer
     Received 354125 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5332142 packets output, 496316039 bytes, 0 underruns
     0 output errors, 432 collisions, 0 interface resets, 0 restarts
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Output queue: 7/64/0 (size/threshold/drops)
				     Conversations 2/9 (active/max active)

Table 43 describes the input queue and output queue fields shown in this display.

**Table 43: Weighted-Fair-Queuing Output Fields**
Field	Description
Input queue:
size	Current size of the input queue.
max	Maximum size of the queue.
drops	Number of messages discarded in this interval.
Total output drops	Total number of messages discarded in this session.
Output queue:
size	Current size of the output queue.
threshold	Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped.
drops	Number of dropped messages.
Conversations: active	Number of currently active conversations.
Conversations: max active	Maximum number of concurrent conversations allowed.

Sample Display with Accounting Option

To display the number of packets of each protocol type that have been sent through all configured interfaces, use the show interfaces accounting EXEC command. When you use the accounting option, only the accounting statistics are displayed.

Note Except for protocols that are encapsulated inside other protocols, such as IP over X.25, the accounting option also shows the total of all bytes sent and received, including the MAC header. For example, it totals the size of the Ethernet packet or the size of a packet that includes HDLC encapsulation.

Table 44 lists the protocols for which per-packet accounting information is kept.

**Table 44: Per-Packet Counted Protocols (Continued)**
Protocol	Notes
Apollo	No note.
AppleTalk	No note.
ARP	For IP, Apollo, Frame Relay, SMDS.
CLNS	No note.
DEC MOP	The routers use MOP packets to advertise their existence to Digital Equipment Corporation machines that use the MOP protocol. A router periodically broadcasts MOP packets to identify itself as a MOP host. This results in MOP packets being counted, even when DECnet is not being actively used.
DECnet	No note.
HP Probe	No note.
IP	No note.
LAN Manager	LAN Network Manager and IBM Network Manager.
Novell	No note.
Serial Tunnel	SDLC.
Spanning Tree	No note.
SR Bridge	No note.
Transparent Bridge	No note.
VINES	No note.
XNS	No note.

Sample Show Interfaces Accounting Display

The following is sample output from the show interfaces accounting command:

Router# show interfaces accounting
Interface TokenRing0 is disabled
Ethernet0
                Protocol    Pkts In   Chars In   Pkts Out  Chars Out
                      IP     873171  735923409      34624    9644258
                  Novell     163849   12361626      57143    4272468
                 DEC MOP          0          0          1         77
                     ARP      69618    4177080       1529      91740
Interface Serial0 is disabled
Ethernet1
                Protocol    Pkts In   Chars In   Pkts Out  Chars Out
                      IP          0          0         37      11845
                  Novell          0          0       4591     275460
                 DEC MOP          0          0          1         77
                     ARP          0          0          7        420
Interface Serial1 is disabled
Interface Ethernet2 is disabled
Interface Serial2 is disabled
Interface Ethernet3 is disabled
Interface Serial3 is disabled
Interface Ethernet4 is disabled
Interface Ethernet5 is disabled
Interface Ethernet6 is disabled
Interface Ethernet7 is disabled
Interface Ethernet8 is disabled
Interface Ethernet9 is disabled
Fddi0
                Protocol    Pkts In   Chars In   Pkts Out  Chars Out
                  Novell          0          0        183      11163
                     ARP          1         49          0          0

When the output indicates an interface is "disabled," the router has received excessive errors (over 5000 in a keepalive period).

show interfaces ethernet

Use the show interfaces ethernet privileged EXEC command to display information about an Ethernet interface on the router.

show interfaces ethernet unit [accounting]
show interfaces ethernet [slot/port] [accounting] (for the Cisco 7200 series and Cisco 7500)
show interfaces ethernet [type slot/port-adapter/port] (for ports on VIP cards in the
Cisco 7500 series routers)

Syntax Description

unit	Must match a port number on the selected interface.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

If you do not provide values for the argument unit (or slot and port on the Cisco 7200 series or slot and port-adapter on the Cisco 7500 series), the command will display statistics for all network interfaces. The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.

Sample Display

The following is sample output from the show interfaces command for the Ethernet 0 interface:

Router# show interfaces ethernet 0
Ethernet 0 is up, line protocol is up
   Hardware is MCI Ethernet, address is aa00.0400.0134 (bia 0000.0c00.4369)
	   Internet address is 131.108.1.1, subnet mask is 255.255.255.0
	   MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
	   Encapsulation ARPA, loopback not set, keepalive set (10 sec)
   	ARP type: ARPA, PROBE, ARP Timeout 4:00:00
	   Last input 0:00:00, output 0:00:00, output hang never
	   Output queue 0/40, 0 drops; input queue 0/75, 2 drops
	   Five minute input rate 61000 bits/sec, 4 packets/sec
	   Five minute output rate 1000 bits/sec, 2 packets/sec
		       2295197 packets input, 305539992 bytes, 0 no buffer
		       Received 1925500 broadcasts, 0 runts, 0 giants
		       3 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
       0 input packets with dribble condition detected
		       3594664 packets output, 436549843 bytes, 0 underruns
		       8 output errors, 1790 collisions, 10 interface resets, 0 restarts

Table 45 describes significant fields shown in the display.

**Table 45: Show Interfaces Ethernet Field Descriptions (Continued)**
Field	Description
Ethernet ... is up ...is administratively down	Indicates whether the interface hardware is currently active and if it has been taken down by an administrator. "Disabled" indicates the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default.
line protocol is {up \| down \| administratively down}	Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful) or if it has been taken down by an administrator.
Hardware	Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.
Internet address	Internet address followed by subnet mask.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
ARP type:	Type of Address Resolution Protocol assigned.
loopback	Indicates whether loopback is set or not.
keepalive	Indicates whether keepalives are set or not.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate, Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic). The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffers	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
Received ... broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size. For example, any Ethernet packet that is greater than 1,518 bytes is considered a giant.
input error	Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
overrun	Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
input packets with dribble condition detected	Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times a Type 2 Ethernet controller was restarted because of errors.

Sample Display on Cisco 7500

The following sample output illustrates the show interfaces ethernet command on the Cisco 7500:

Router> show interfaces ethernet 4/2
Ethernet4/2 is up, line protocol is up
  Hardware is cxBus Ethernet, address is 0000.0c02.d0ce (bia 0000.0c02.d0ce)
  Internet address is 131.108.7.1, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 4:00:00
  Last input 0:00:00, output 0:00:09, output hang never
  Last clearing of "show interface" counters 0:56:40
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 3000 bits/sec, 4 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     4961 packets input, 715381 bytes, 0 no buffer
     Received 2014 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     567 packets output, 224914 bytes, 0 underruns
     0 output errors, 168 collisions, 0 interface resets, 0 restarts

Sample Display with Accounting Option

The following is sample output from the show interfaces ethernet command with the accounting option on the Cisco 7500:

Router# show interfaces ethernet 4/2 accounting
Ethernet4/2
       Protocol    Pkts In   Chars In   Pkts Out  Chars Out
             IP       7344    4787842       1803    1535774
      Appletalk      33345    4797459      12781    1089695
        DEC MOP          0          0        127       9779
            ARP          7        420         39       2340

show interfaces fastethernet

Use the show interface fastethernet EXEC command to display information about the FastEthernet interfaces.

show interfaces fastethernet [number] (Cisco 4500 and Cisco 4700)
show interfaces fastethernet [slot/port] ( Cisco 7200 series and Cisco 7500)
show interfaces fastethernet [slot/port-adapter/port] (Cisco 7500 series with a VIP card)

Syntax Description

number	(Optional) Port, connector, or interface card number. On a Cisco 4500 or Cisco 4700 router, specifies the NIM or NPM number. The numbers are assigned at the factory at the time of installation or when added to a system.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Sample Displays

The following is a sample display for the show interface fastethernet on a Cisco 4500 router:

c4500-1# show interfaces fastethernet 0
FastEthernet0 is up, line protocol is up 
  Hardware is DEC21140, address is 0000.0c0c.1111 (bia 0002.eaa3.5a60)
  Internet address is 11.0.0.1 255.0.0.0
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive not set, hdx, 100BaseTX
  ARP type: ARPA, ARP Timeout 4:00:00
  Last input never, output 0:00:16, output hang 0:28:01
  Last clearing of "show interface" counters 0:20:05
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 1786161921 ignored, 0 abort
     0 watchdog, 0 multicast
     0 input packets with dribble condition detected
     67 packets output, 8151 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets, 0 restarts
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

The following shows information specific to the first FEIP port in slot 0 on a Cisco 7500:

Router# show interface fastethernet 0/1
FastEthernet0/1 is administratively down, line protocol is down
  Hardware is cxBus FastEthernet, address is 0000.0c35.dc16 (bia 0000.0c35.dc16)
  Internet address is 1.1.0.64 255.255.0.0
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive not set, half-duplex, RJ45 (or MII)
  ARP type: ARPA, ARP Timeout 4:00:00
  Last input never, output 2:03:52, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/40, 0 drops; input queue 0/75, 1 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 watchdog, 0 multicast
     0 input packets with dribble condition detected
     5 packets output, 805 bytes, 0 underruns
     0 output errors, 0 collisions, 4 interface resets, 0 restarts
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Table 46 describes the fields in these displays.

**Table 46: Show Interfaces FastEthernet Field Descriptions**
Field	Description
FastEthernet0 is ... is up ...is administratively down	Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.
line protocol is	Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.
Hardware	Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.
Internet address	Internet address followed by subnet mask.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
ARP type:	Type of Address Resolution Protocol assigned.
loopback	Indicates whether loopback is set or not.
keepalive	Indicates whether keepalives are set or not.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate, 5 minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic). The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
Received ... broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size. For example, any Ethernet packet that is greater than 1,518 bytes is considered a giant.
input errors	Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
overrun	Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Number of packets whose receipt was aborted.
watchdog	Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048.
multicast	Number of multicast packets received.
input packets with dribble condition detected	Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times a Type 2 Ethernet controller was restarted because of errors.
babbles	The transmit jabber timer expired.
late collision	Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble.
deferred	Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
lost carrier	Number of times the carrier was lost during transmission.
no carrier	Number of times the carrier was not present during the transmission.
output buffer failures	Number of failed buffers and number of buffers swapped out.

show interfaces fddi

To display information about the FDDI interface, use the show interfaces fddi EXEC command.

show interfaces fddi number [accounting]
show interfaces fddi [slot/port] [accounting] (Cisco 7000 series and Cisco 7200 series)
show interfaces fddi [slot/port-adapter/port] [accounting] (Cisco 7500 series routers)

Syntax Description

number	Port number on the selected interface.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

This information was modified in Cisco IOS Release 11.3 to include sample output for FDDI full-duplex, single- and multimode port adapters (PA-F/FD-SM and PA-F/FD-MM).

Sample Displays

The following is a sample partial display of FDDI-specific data from the show interfaces fddi command on a Cisco 7500 series router:

Router> show interfaces fddi 3/0 
Fddi3/0 is up, line protocol is up
  Hardware is cxBus Fddi, address is 0000.0c02.adf1 (bia 0000.0c02.adf1)
  Internet address is 131.108.33.14, subnet mask is 255.255.255.0
  MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation SNAP, loopback not set, keepalive not set
  ARP type: SNAP, ARP Timeout 4:00:00
  Phy-A state is  active, neighbor is   B, cmt signal bits 008/20C, status ILS
  Phy-B state is  active, neighbor is   A, cmt signal bits 20C/008, status ILS
  ECM is in, CFM is thru, RMT is ring_op
  Token rotation 5000 usec, ring operational 21:32:34
  Upstream neighbor 0000.0c02.ba83, downstream neighbor 0000.0c02.ba83
  Last input 0:00:05, output 0:00:00, output hang never
  Last clearing of "show interface" counters 0:59:10
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 69000 bits/sec, 44 packets/sec
  Five minute output rate 0 bits/sec, 1 packets/sec
     113157 packets input, 21622582 bytes, 0 no buffer
     Received 276 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     4740 packets output, 487346 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets, 0 restarts
     0 transitions, 2 traces, 3 claims, 2 beacons

The following is a sample display of the show interfaces fddi command for the full-duplex FDDI port adapter on a Cisco 7500 series router:

Router# show interfaces fddi 0/1/0
Fddi0/1/0 is up, line protocol is up 
  Hardware is cxBus FDDI, address is 0060.3e33.3608 (bia 0060.3e33.3608)
  Internet address is 2.1.1.1/24
  MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation SNAP, loopback not set, keepalive not set
  ARP type: SNAP, ARP Timeout 04:00:00
  FDX supported, FDX enabled, FDX state is operation
  Phy-A state is maintenance, neighbor is Unknown, status HLS 
  Phy-B state is active, neighbor is A, status SILS
  ECM is in, CFM is c_wrap_b, RMT is ring_op,
  Requested token rotation 5000 usec, negotiated 4997 usec
  Configured tvx is 2500 usec
  LER for PortA = 0A, LER for PortB = 0A ring operational 00:02:45
  Upstream neighbor 0060.3e73.4600, downstream neighbor 0060.3e73.4600
  Last input 00:00:12, output 00:00:13, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     62 packets input, 6024 bytes, 0 no buffer
     Received 18 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     71 packets output, 4961 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 transitions, 0 traces,  100 claims, 0 beacon

Table 47 describes the show interfaces fddi display fields.

**Table 47: Show Interfaces FDDI Field Descriptions**
Field	Description
Fddi is {up \| down \| administratively down	Gives the interface processor unit number and tells whether the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
line protocol is {up \| down}	Indicates whether the software processes that handle the line protocol consider the interface usable.
Hardware	Provides the hardware type, followed by the hardware address.
Internet address	IP address, followed by subnet mask.
MTU	Maximum transmission unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether or not loopback is set.
keepalive	Indicates whether or not keepalives are set.
ARP type	Type of Address Resolution Protocol assigned.
FDX	Displays full-duplex information. Values are: not supported or supported. When the value is supported, the display indicates whether full-duplex is enabled or disabled. When enabled, the state of the FDX negotiation process is displayed. The negotiation states only relate to the full-duplex negotiation process. You must also ensure that the interface is up and working by looking at other fields in the show interfaces fddi command such as line protocol and RMT. Negotiation states are: idle--Interface is working but not in full-duplex mode yet. If persistent, it could mean that the interface did not meet all negotiation conditions (for example, there are more than two stations in the ring). request--Interface is working but not in full-duplex mode yet. If persistent, it could mean that the remote interface does not support full-duplex or full-duplex is not enabled on the interface. confirm--Transient state. operation--Negotiations completed successfully, and both stations are operating in full-duplex mode.
Phy-{A \| B}	Lists the state the Physical A or Physical B connection is in; one of the following: off, active, trace, connect, next, signal, join, verify, or break.
neighbor	State of the neighbor: A--Indicates that the connection management (CMT) process has established a connection with its neighbor. The bits received during the CMT signaling process indicate that the neighbor is a Physical A type dual attachment station (DAS) or concentrator that attaches to the primary ring IN and the secondary ring OUT when attaching to the dual ring. S--Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the neighbor is one Physical type in a single attachment station (SAS). B--Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the neighbor is a Physical B dual attachment station or concentrator that attaches to the secondary ring IN and the primary ring OUT when attaching to the dual ring. M--Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the router's neighbor is a Physical M-type concentrator serving as a Master to a connected station or concentrator. unk--Indicates that the network server has not completed the CMT process and, as a result, does not know about its neighbor. See the section "Setting Bit Control" for an explanation of the bit patterns.
cmt signal bits	Shows the transmitted/received CMT bits. The transmitted bits are 0x008 for a Physical A type and 0x20C for Physical B type. The number after the slash (/) is the received signal bits. If the connection is not active, the received bits are zero (0); see the line beginning Phy-B in the display. This applies to FIP interfaces only.
status	Status value displayed is the actual status on the fiber. The FDDI standard defines the following values: LSU--Line State Unknown, the criteria for entering or remaining in any other line state have not been met. NLS--Noise Line State is entered upon the occurrence of 16 potential noise events without satisfying the criteria for entry into another line state. MLS--Master Line State is entered upon the receipt of eight or nine consecutive HQ or QH symbol pairs. ILS--Idle Line State is entered upon receipt of four or five idle symbols. HLS--Halt Line State is entered upon the receipt of 16 or 17 consecutive H symbols. QLS--Quiet Line State is entered upon the receipt of 16 or 17 consecutive Q symbols or when carrier detect goes low. ALS--Active Line State is entered upon receipt of a JK symbol pair when carrier detect is high. OVUF--Elasticity buffer Overflow/Underflow. The normal states for a connected Physical type are ILS or ALS. If the report displays the QLS status, this indicates that the fiber is disconnected from Physical B, or that it is not connected to another Physical type, or that the other station is not running.
ECM is...	ECM is the SMT entity coordination management, which overlooks the operation of CFM and PCM. The ECM state can be one of the following: out--Router is isolated from the network. in--Router is actively connected to the network. This is the normal state for a connected router. trace--Router is trying to localize a stuck beacon condition. leave--Router is allowing time for all the connections to break before leaving the network. path_test--Router is testing its internal paths. insert--Router is allowing time for the optical bypass to insert. check--Router is making sure optical bypasses switched correctly. deinsert--Router is allowing time for the optical bypass to deinsert.
CFM is...	Contains information about the current state of the MAC connection. The Configuration Management state can be one of the following: isolated--MAC is not attached to any Physical type. wrap_a--MAC is attached to Physical A. Data is received on Physical A and transmitted on Physical A. wrap_b--MAC is attached to Physical B. Data is received on Physical B and transmitted on Physical B. wrap_s--MAC is attached to Physical S. Data is received on Physical S and transmitted on Physical S. This is the normal mode for a single attachment station (SAS). thru--MAC is attached to Physical A and B. Data is received on Physical A and transmitted on Physical B. This is the normal mode for a dual attachment station (DAS) with one MAC. The ring has been operational for 1 minute and 42 seconds.
RMT is...	RMT (Ring Management) is the SMT MAC-related state machine. The RMT state can be one of the following: isolated--MAC is not trying to participate in the ring. This is the initial state. non_op--MAC is participating in ring recovery, and ring is not operational. ring_op--MAC is participating in an operational ring. This is the normal state while the MAC is connected to the ring. detect--Ring has been nonoperational for longer than normal. Duplicate address conditions are being checked. non_op_dup--Indications have been received that the address of the MAC is a duplicate of another MAC on the ring. Ring is not operational. ring_op_dup--Indications have been received that the address of the MAC is a duplicate of another MAC on the ring. Ring is operational in this state. directed--MAC is sending beacon frames notifying the ring of the stuck condition. trace--Trace has been initiated by this MAC, and the RMT state machine is waiting for its completion before starting an internal path test.
token rotation	Token rotation value is the default or configured rotation value as determined by the fddi token-rotation-time command. This value is used by all stations on the ring. The default is 5000 microseconds. For FDDI full-duplex, this indicates the value in use prior to entering full-duplex operation.
negotiated	Actual (negotiated) target token rotation time.
ring operational	When the ring is operational, the displayed value will be the negotiated token rotation time of all stations on the ring. Operational times are displayed by the number of hours:minutes:seconds the ring has been up. If the ring is not operational, the message "ring not operational" is displayed.
Configured tvx	Transmission timer.
LER	Link error rate.
Upstream \| downstream neighbor	Displays the canonical MAC address of outgoing upstream and downstream neighbors. If the address is unknown, the value will be the FDDI unknown address (0x00 00 f8 00 00 00).
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Queueing strategy	First-in, first-out queuing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue, input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate 5 minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. The five-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
frame	Number of packets received incorrectly that have a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device. On an FDDI LAN, this also can be the result of a failing fiber (cracks) or a hardware malfunction.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of transmit aborts (when the router cannot feed the transmitter fast enough).
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, because some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
collisions	Because an FDDI ring cannot have collisions, this statistic is always zero.
interface resets	Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
restarts	Should always be zero for FDDI interfaces.
output buffer failures	Number of no resource errors received on the output.
output buffers swapped out	Number of packets swapped to DRAM.
transitions	The number of times the ring made a transition from ring operational to ring nonoperational, or vice versa. A large number of transitions indicates a problem with the ring or the interface.
traces	Trace count applies to both the FCI, FCIT, and FIP. Indicates the number of times this interface started a trace.
claims	Pertains to FCIT and FIP only. Indicates the number of times this interface has been in claim state.
beacons	Pertains to FCIT and FIP only. Indicates the number of times the interface has been in beacon state.

The following is an example that includes the accounting option. When you use the accounting option, only the accounting statistics are displayed.

Router> show interfaces fddi 3/0 accounting
Fddi3/0
       Protocol    Pkts In   Chars In   Pkts Out  Chars Out
             IP       7344    4787842       1803    1535774
      Appletalk      33345    4797459      12781    1089695
        DEC MOP          0          0        127       9779
            ARP          7        420         39       2340

Table 48 describes the show interfaces fddi display fields.

**Table 48: Show Interfaces FDDI Field Descriptions--Accounting**
Field	Description
Protocol	Protocol that is operating on the interface.
Pkts In	Number of packets received for that protocol.
Chars In	Number of characters received for that protocol.
Pkts Out	Number of packets transmitted for that protocol.
Chars Out	Number of characters transmitted for that protocol.

show interfaces hssi

Use the show interfaces hssi privileged EXEC command to display information about the HSSI interface.

show interfaces hssi unit [accounting]
show interfaces hssi [slot/port] [accounting] (for the Cisco 7500 series)

Syntax Description

unit	Must match a port number on the selected interface.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Displays

The following is sample output from the show interfaces hssi command when HSSI is enabled:

Router# show interfaces hssi 0
HSSI 0 is up, line protocol is up
	Hardware is cBus HSSI
	Internet address is 150.136.67.190, subnet mask is 255.255.255.0
	MTU 4470 bytes, BW 45045 Kbit, DLY 20000 usec, rely 255/255, load 1/255
	Encapsulation HDLC, loopback not set, keepalive set (10 sec)
	Last input 0:00:03, output 0:00:00, output hang never
	Output queue 0/40, 0 drops; input queue 0/75, 0 drops
	Five minute input rate 0 bits/sec, 0 packets/sec
	Five minute output rate 0 bits/sec, 0 packets/sec
    		0 packets input, 0 bytes, 0 no buffer
	    	Received 0 broadcasts, 0 runts, 0 giants
              0 parity, 0 rx disabled
	0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
	17 packets output, 994 bytes, 0 underruns
	0 output errors, 0 applique, 4 interface resets, 0 restarts
	2 carrier transitions

Table 49 describes significant fields shown in the display.

**Table 49: Show Interfaces HSSI Field Descriptions (Continued)**
Field	Description
HSSI is {up \| down \| administratively down}	Indicates whether the interface hardware is currently active (whether carrier detect is present) and if it has been taken down by an administrator. "Disabled" indicates the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default.
line protocol is {up \| down \| administratively down}	Indicates whether the software processes that handle the line protocol considers the line usable (that is, whether keepalives are successful).
Hardware	Specifies the hardware type.
Internet address	Lists the Internet address followed by subnet mask.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether loopback is set and type of loopback test.
keepalive	Indicates whether keepalives are set or not.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, drops Input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate, Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
parity	Report of the parity errors on the HSSI.
rx disabled	Indicates the HSSI could not find a free buffer on the ciscoBus controller to reserve for use for the HSSI receiver. When this happens, the HSSI shuts down its receiver and waits until a buffer is available. Data is not lost unless a packet comes in and overflows the HSSI FIFO. Usually, the receive disables are frequent but do not last for long, and the number of dropped packets is less than the count in the "rx disabled" field. A receive disabled condition can happen in systems that are under heavy traffic load and that have shorter packets. In this situation, the number of buffers available on the ciscoBus controller is at a premium. One way to alleviate this problem is to reduce the mtu on the HSSI interface from 4500 (FDDI size) to 1500 (Ethernet size). Doing so allows the software to take the fixed memory of the ciscoBus controller and divide it into a larger number of smaller buffers, rather than a small number of large buffers. Receive disables are not errors, so they are not included in any error counts.
input errors	Sum of all errors that prevented the receipt of datagrams on the interface being examined. This may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC errors are also reported when a far-end abort occurs, and when the idle flag pattern is corrupted. This makes it possible to get CRC errors even when there is no data traffic.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Number of packets whose receipt was aborted.
packets output	Total number of messages transmitted by the system.
bytes output	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
congestion drop	Number of messages discarded because the output queue on an interface grew too long. This can happen on a slow, congested serial link.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
applique	Indicates an unrecoverable error has occurred on the HSA applique. The system then invokes an interface reset.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times the controller was restarted because of errors.
carrier transitions	Number of times the carrier detect signal of the interface has changed state. Indicates modem or line problems if the carrier detect line is changing state often.
Protocol	Protocol that is operating on the interface.
Pkts In	Number of packets received for that protocol.
Chars In	Number of characters received for that protocol.
Pkts Out	Number of packets transmitted for that protocol.
Chars Out	Number of characters transmitted for that protocol.

The following is an example of the show interfaces hssi command on a Cisco 7500:

Router# show interfaces hssi 1/0
Hssi1/0 is up, line protocol is up
  Hardware is cxBus HSSI
  Internet address is 131.108.38.14, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 45045 Kbit, DLY 1000000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive set (10 sec)
  Last input 0:00:00, output 0:00:08, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 1000 bits/sec, 2 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     630573548 packets input, 2077237628 bytes, 0 no buffer
     Received 2832063 broadcasts, 0 runts, 0 giants
              0 parity, 1970 rx disabled
     113 input errors, 20 CRC, 93 frame, 0 overrun, 0 ignored, 0 abort
     629721628 packets output, 1934313295 bytes, 0 underruns
     0 output errors, 0 applique, 62 interface resets, 0 restarts
     309 carrier transitions

The following is an example of the show interfaces hssi command with the accounting option on a Cisco 7500:

Router# show interfaces hssi 1/0 accounting
HIP1/0
       Protocol    Pkts In   Chars In   Pkts Out  Chars Out
             IP       7344    4787842       1803    1535774
      Appletalk      33345    4797459      12781    1089695
        DEC MOP          0          0        127       9779
            ARP          7        420         39       2340

show interfaces ip-brief

To display a brief summary of an IP interface's information and status, use the show interfaces ip-brief EXEC command.

show interfaces ip-brief

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

The following is sample output from the show interfaces ip-brief command:

Router# show interfaces ip-brief
Any interface listed with OK? value "NO" does not have a valid configuration
Interface    IP-Address      OK?  Method     Status                 Protocol
Ethernet0    172.30.160.22   YES  NVRAM      up                     up

show interfaces lex

To display statistics about a LAN Extender interface, use the show interface lex EXEC command.

show interfaces lex number [ethernet | serial]

Syntax Description

number	Number of the LAN Extender interface that resides on the core router about which to display statistics.
ethernet	(Optional) Displays statistics about the Ethernet interface that resides on the LAN Extender chassis.
serial	(Optional) Displays statistics about the serial interface that resides on the LAN Extender chassis.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

To display statistics about the LAN Extender interface on the core router, use the show interfaces lex command without any keywords.

Administratively, the physical serial interface that connects the core router to the LAN Extender is completely hidden. The show interfaces serial command will show only that the serial interface is present. However, it will not report any statistics about the traffic passing over the physical line. All statistics are report by the show interfaces lex command.

Sample Displays

The following is sample output from the show interfaces lex command, showing the LAN Extender interface on the host router. Note the "Bound to ..." field, which is displayed only on a LAN Extender interface.

Router# show interfaces lex 0
Lex0 is up, line protocol is up
  Hardware is Lan Extender, address is 0204.0301.1526 (bia 0000.0000.0000)
  MTU 1500 bytes, BW 10000 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set
  ARP type: ARPA, ARP Timeout 4:00:00
  Bound to Serial3
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 1000 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     1022 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     2070 packets output, 23663 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets, 0 restarts

The following is sample output from the show interfaces lex command when you specify the ethernet keyword:

Router# show interfaces lex 0 ethernet
Lex0-Ethernet0 is up, line protocol is up
  Hardware is LAN-Extender, address is 0000.0c01.1526 (bia 0000.0c01.1526)
  Last input 6w3d, output 6w3d
  Last clearing of "show interface" counters 0:02:30
  Output queue 40/50, 60 drops; input queue 10/40, 2 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     3916 packets input, 960303 bytes, 3 no buffer
     Received 2 broadcasts, 3 runts, 3 giants
     2 input errors, 1 CRC, 1 frame, 1 overrun, 3 ignored, 2 abort
     2500 packets output, 128288 bytes, 1 underruns
     1 output errors, 1 collisions, 0 interface resets, 0 restarts

The following is sample output from the show interfaces lex command when you specify the serial keyword:

Router# show interfaces lex 0 serial
Lex0-Serial0 is up, line protocol is up
  Hardware is LAN-Extender
  Last input 6w3d, output 6w3d
  Last clearing of "show interface" counters 0:03:05
  Input queue: 5/15/4 (size/max/drops); Total output drops: 450
  Output queue: high 25/35/90, medium 70/80/180, normal 40/50/120, low 10/20/60
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     1939 packets input, 30998 bytes, 6 no buffer
     Received 4 broadcasts, 6 runts, 6 giants
     4 input errors, 2 CRC, 2 frame, 2 overrun, 6 ignored, 4 abort
     1939 packets output, 219535 bytes, 2 underruns
     2 output errors, 2 collisions, 0 interface resets, 0 restarts
     2 carrier transitions

Table 50 describes the fields shown in these displays.

**Table 50: Show Interfaces Lex Field Descriptions**
Field	Description
Lex0 is up, line protocol is up	Indicates whether the logical LAN Extender interface on the core router is currently active (that is, whether carrier detect is present), inactive, or has been taken down by an administrator.
Lex0-Ethernet0 is up, line protocol is up Lex0-Serial0 is up, line protocol is up	Indicates whether the physical Ethernet and serial interfaces on the LAN Extender chassis are currently active (that is, whether carrier detect is present) and if it has been taken down by an administrator.
Hardware is LAN-Extender	Hardware type of the interfaces on the LAN Extender.
address is...	Logical MAC address of the interface.
bia	Burned-in MAC address of the interface. The LAN Extender interface does not have a burned in address; hence it appears as all zeroes.
MTU	Maximum transmission unit size of the interface.
BW	Value of the bandwidth parameter that has been configured for the interface (in kilobits per second). The bandwidth parameter is used to compute IGRP metrics only. If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 for T1 and 56 for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
ARP type	Type of Address Resolution Protocol assigned.
ARP Timeout	Number of hours, minutes, and seconds an ARP cache entry will stay in the cache.
Bound to ...	Number of the serial interface to which the logical LAN Extender interface is bound.
Last input	Number of hours, minutes, and seconds (or never) since the last packet was successfully received by an interface. This is useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds (or never) since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing of "show interface" counters	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes	Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
Received ... broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
input packets with dribble condition detected	Does not apply to a LAN Extender interface.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This usually is the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). Some collisions are normal. However, if your collision rate climbs to around 4 or 5%, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds' time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times the controller was restarted because of errors.

show interfaces loopback

Use the show interfaces loopback privileged EXEC command to display information about the loopback interface.

show interfaces loopback [number] [accounting]

Syntax Description

number	(Optional) Port number on the selected interface.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Displays

The following is sample output from the show interfaces loopback command:

Router# show interfaces loopback 0
Loopback0 is up, line protocol is up
  Hardware is Loopback
  MTU 1500 bytes, BW 1 Kbit, DLY 50 usec, rely 255/255, load 1/255
  Encapsulation UNKNOWN, loopback not set, keepalive set (10 sec)
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/0, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets, 0 restarts

The following is sample output when the accounting keyword is included:

Router# show interfaces loopback 0 accounting
Loopback0
                Protocol    Pkts In   Chars In   Pkts Out  Chars Out
No traffic sent or received on this interface.

Table 51 describes significant fields shown in the displays.

**Table 51: Show Interfaces Loopback Field Descriptions (Continued)**
Field	Description
Loopback is {up \| down \| administratively down}	Indicates whether the interface hardware is currently active (whether carrier detect is present), inactive, or has been taken down by an administrator.
line protocol is {up \| down \| administratively down}	Indicates whether the software processes that handle the line protocol considers the line usable (that is, whether keepalives are successful).
Hardware	Hardware is Loopback.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether loopback is set and type of loopback test.
keepalive	Indicates whether keepalives are set or not.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, drops Input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate, Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Sum of all errors that prevented the receipt of datagrams on the interface being examined. This may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC errors are also reported when a far-end abort occurs, and when the idle flag pattern is corrupted. This makes it possible to get CRC errors even when there is no data traffic.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Number of packets whose receipt was aborted.
packets output	Total number of messages transmitted by the system.
bytes output	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never happen (be reported) on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	A loopback interface does not have collisions.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times the controller was restarted because of errors.
Protocol	Protocol that is operating on the interface.
Pkts In	Number of packets received for that protocol.
Chars In	Number of characters received for that protocol.
Pkts Out	Number of packets transmitted for that protocol.
Chars Out	Number of characters transmitted for that protocol.

show interfaces pos

To display information about the Packet OC-3 interface in Cisco 7500 series routers, use the show interfaces pos EXEC command.

show interfaces pos [slot/port-adapter/port] (on VIP cards in Cisco 7000 series and Cisco 7500
series routers)

Syntax Description

slot	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.
port	Refer to the appropriate hardware manual for slot and port information.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

This command was modified in Cisco IOS Release 11.3 to change the show interface posi command to show interface pos and to update the sample output.

Sample Display

The following is sample output from the show interfaces pos command on a Cisco 7513 router with one Packet OC-3 Interface Processor (POSIP):

Router# show interfaces pos 2/0/0
POS2/0/0 is up, line protocol is up
  Hardware is cyBus Packet over Sonet
  Description: PRI-T1 net to zippy (4K) to Pac-Bell
  Internet address is 1.1.1.1/27
  MTU 4470 bytes, BW 1000 Kbit, DLY 40000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive set (3 sec)
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:23:09
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 1 packets/sec
  5 minute output rate 1000 bits/sec, 1 packets/sec
     1046 packets input, 54437 bytes, 0 no buffer
     Received 485 broadcasts, 0 runts, 0 giants, 0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     4013 packets output, 1357412 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Table 52 describes significant fields in this output.

**Table 52: Show Interfaces POS Field Descriptions**
Field	Description
POS2/0/0 is up, line protocol is up	Indicates whether the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
Hardware is cyBus Packet over Sonet	Hardware type.
Internet address is	Internet address and subnet mask.
MTU	Maximum transmission unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether loopbacks are set.
keepalive	Indicates whether keepalives are set.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
(Last) output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
(Last) output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Queueing strategy	First-in, first-out queuing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
5 minute input rate 5 minute output rate	Average number of bits and packets received or transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes (input)	Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
parity	Report of the parity errors on the interface.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
abort	Illegal sequence of one bits on the interface.
packets output	Total number of messages transmitted by the system.
bytes (output)	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
applique	Indicates an unrecoverable error has occurred on the POSIP applique. The system then invokes an interface reset.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
carrier transitions	Number of times the carrier detect signal of the interface has changed state.

Related Commands

You can use the master indexes or search online to find documentation of related commands.

interface pos

show interfaces serial

To display information about a serial interface, use the show interfaces serial privileged EXEC command.

show interfaces serial [number] [accounting]
show interfaces serial [number [:channel-group] [accounting]  (Cisco 4000 series)
show interfaces serial [slot/port [:channel-group]] [accounting]  (Cisco 7500 series)
show interfaces serial [type slot/port-adapter/port] [serial]  (ports on VIP cards in the
Cisco 7500 series)
show interfaces serial [type slot/port-adapter/port] [:t1-channel] [accounting | crb] (CT3IP in
Cisco 7500 series)

Syntax Description

number	(Optional) Port number.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
:channel-group	(Optional) On the Cisco 4000 series with an NPM or Cisco 7500 series with a MIP, specifies the T1 channel-group number in the range of 0 to 23 defined with the channel-group controller configuration command.
slot	Refer to the appropriate hardware manual for slot and port information.
port-	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.
:t1-channel	(Optional) For the CT3IP, the T1 channel is a number between 1 and 28. T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
crb	(Optional) Shows interface routing and bridging information.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0 for the Cisco 4000 series.
This command first appeared in Cisco IOS Release 11.0 for the Cisco 7000 series.

This command was modified in Cisco IOS Release 11.3 to include the CT3IP.

Sample Displays

The following is sample output from the show interfaces command for a synchronous serial interface:

Router# show interfaces serial
Serial 0 is up, line protocol is up
   Hardware is MCI Serial
   Internet address is 150.136.190.203, subnet mask is 255.255.255.0
   MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
   Encapsulation HDLC, loopback not set, keepalive set (10 sec)
   Last input 0:00:07, output 0:00:00, output hang never
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   Five minute input rate 0 bits/sec, 0 packets/sec
   Five minute output rate 0 bits/sec, 0 packets/sec
       16263 packets input, 1347238 bytes, 0 no buffer
       Received 13983 broadcasts, 0 runts, 0 giants
       2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
1 carrier transitions 
     22146 packets output, 2383680 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets, 0 restarts

Table 53 describes significant fields shown in the display.

**Table 53: Show Interfaces Serial Field Descriptions**
Field	Description
Serial... is {up \| down} ...is administratively down	Indicates whether the interface hardware is currently active (whether carrier detect is present) or if it has been taken down by an administrator.
line protocol is {up \| down}	Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful) or if it has been taken down by an administrator.
Hardware is	Specifies the hardware type.
Internet address is	Specifies the Internet address and subnet mask.
MTU	Maximum transmission unit of the interface.
BW	Indicates the value of the bandwidth parameter that has been configured for the interface (in kilobits per second). The bandwidth parameter is used to compute IGRP metrics only. If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 for T1 and 56 for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether loopback is set or not.
keepalive	Indicates whether keepalives are set or not.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate 5 minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes	Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
Received... broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
carrier transitions	Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.
packets output	Total number of messages transmitted by the system.
bytes output	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This usually is the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). Some collisions are normal. However, if your collision rate climbs to around 4 or 5%, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds' time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
restarts	Number of times the controller was restarted because of errors.
alarm indications, remote alarms, rx LOF, rx LOS	Number of CSU/DSU alarms, and number of occurrences of receive loss of frame and receive loss of signal.
BER inactive, NELR inactive, FELR inactive	Status of G.703-E1 counters for bit error rate (BER) alarm, near-end loop remote (NELR), and far-end loop remote (FELR). Note that you cannot set the NELR or FELR.

The following is sample output of the show interfaces serial command for the CT3IP serial interface:

Router# show interfaces serial 3/0/0:25
Serial3/0/0:25 is up, line protocol is up 
  Hardware is cyBus T3
  Internet address is 25.25.25.2/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 12/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 00:19:01, output 00:11:49, output hang never
  Last clearing of "show interface" counters 00:19:39
  Input queue: 0/75/0 (size/max/drops); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/64/0 (size/threshold/drops) 
     Conversations  0/1 (active/max active)
     Reserved Conversations 0/0 (allocated/max allocated)
  5 minute input rate 69000 bits/sec, 90 packets/sec
  5 minute output rate 71000 bits/sec, 90 packets/sec
     762350 packets input, 79284400 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     150 input errors, 0 CRC, 0 frame, 150 overrun, 0 ignored, 0 abort
     763213 packets output, 80900472 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions no alarm present
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 5
  non-inverted data

Most fields are described in Table 53. Fields relevant to the CT3IP are described in Table 54.

**Table 54: Show Interfaces Serial Field Descriptions--CT3IP**
Field	Description
Timeslot(s) Used	Number of timeslots assigned to the T1 channel.
Transmitter delay	Number of idle flags inserted between each HDLC frame.
transmit queue length	Number of packets allowed in the transmit queue.
non-inverted data	Whether or not the interface is configured for inverted data.

The following is sample output of the show interfaces serial command for the HDLC synchronous serial interface on a Cisco 7500:

Router# show interfaces serial 1/0
Serial1/0 is up, line protocol is up
  Hardware is cxBus Serial
  Internet address is 150.136.190.203, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive set (10 sec)
  Last input 0:00:07, output 0:00:00, output hang never
  Last clearing of "show interface" counters 2w4d
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     16263 packets input, 1347238 bytes, 0 no buffer
     Received 13983 broadcasts, 0 runts, 0 giants
     2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
     22146 packets output, 2383680 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets, 0 restarts
     1 carrier transitions

The following is sample output of the show interfaces serial command for a G.703 interface on which framing is enabled:

Router# show interfaces serial 2/3
Serial2/3 is up, line protocol is up
  Hardware is cxBus Serial
  Internet address is 5.4.4.1, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 0:00:21, output 0:00:21, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     53 packets input, 7810 bytes, 0 no buffer
     Received 53 broadcasts, 0 runts, 0 giants
     2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
     56 packets output, 8218 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets, 0 restarts
     1 carrier transitions
     2 alarm indications, 333 remote alarms, 332 rx LOF, 0 rx LOS
     RTS up, CTS up, DTR up, DCD up, DSR up
     BER inactive, NELR inactive, FELR inactive

Table 53 describes significant fields shown in the display.

Sample Display with Frame Relay Encapsulation

When using the Frame Relay encapsulation, use the show interfaces command to display information on the multicast DLCI, the DLCI of the interface, and the LMI DLCI used for the local management interface.

The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and the frame-relay local-dlci configuration commands, or provided through the local management interface. The status information is taken from the LMI, when active.

The following is sample output from the show interfaces serial command when using Frame Relay encapsulation:

Router# show interfaces serial
Serial 2 is up, line protocol is up
   Hardware type is MCI Serial
   Internet address is 131.108.122.1, subnet mask is 255.255.255.0
   MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
   Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)
   multicast DLCI 1022,  status defined, active
   source DLCI    20, status defined, active
   LMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2
   Last input 7:21:29, output 0:00:37, output hang never
   Output queue 0/100, 0 drops; input queue 0/75, 0 drops
   Five minute input rate 0 bits/sec, 0 packets/sec
   Five minute output rate 0 bits/sec, 0 packets/sec
       47 packets input, 2656 bytes, 0 no buffer
       Received 5 broadcasts, 0 runts, 0 giants
       5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 57 abort
       518 packets output, 391205 bytes
       0 output errors, 0 collisions, 0 interface resets, 0 restarts
       1 carrier transitions

In this display, the multicast DLCI has been changed to 1022 with the frame-relay multicast-dlci interface configuration command.

The display shows the statistics for the LMI are the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). See the Frame Relay Interface specification for additional explanations of this output.

Sample Display with ANSI LMI

For a serial interface with the ANSI LMI enabled, use the show interfaces command to determine the LMI type implemented.

The following is a sample display from the show interfaces output for a serial interface with the ANSI LMI enabled:

Router# show interfaces serial
Serial 1 is up, line protocol is up
   Hardware is MCI Serial
   Internet address is 131.108.121.1, subnet mask is 255.255.255.0
   MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
   Encapsulation FRAME-RELAY, loopback not set, keepalive set
   LMI DLCI    0, LMI sent 10, LMI stat recvd 10
   LMI type is ANSI Annex D
   Last input 0:00:00, output 0:00:00, output hang never
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   Five minute input rate 0 bits/sec, 1 packets/sec
   Five minute output rate 1000 bits/sec, 1 packets/sec
       261 packets input, 13212 bytes, 0 no buffer
       Received 33 broadcasts, 0 runts, 0 giants
       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
       238 packets output, 14751 bytes, 0 underruns
       0 output errors, 0 collisions, 0 interface resets, 0 restarts

Notice that the show interfaces output for a serial interface with ANSI LMI shown in this display is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. Table 55 describes the few differences that exist.

**Table 55: Show Interfaces Serial Field Description--With ANSI LMI**
Field	Description
LMI DLCI 0	Identifies the DLCI used by the LMI for this interface. Default: 1023.
LMI sent 10	Number of LMI packets the router sent.
LMI type is ANSI Annex D	Indicates that the interface is configured for the ANSI-adopted Frame Relay specification T1.617 Annex D.

Sample Display with LAPB Encapsulation

Use the show interfaces command to display operation statistics for an interface using LAPB encapsulation.

The following is sample output from the show interfaces command for a serial interface using LAPB encapsulation:

Router# show interfaces
LAPB state is DISCONNECT, T1 3000, N1 12000, N2 20, K7, TH 3000
Window is closed
IFRAMEs 12/28 RNRs 0/1 REJs 13/1 SABMs 1/13 FRMRs 3/0 DISCs 0/11

Table 56 shows the fields relevant to all LAPB connections.

**Table 56: Show Interfaces Serial Field Descriptions--With LAPB Enabled**
Parameter	Description
LAPB state is DISCONNECT	State of the LAPB protocol.
T1 3000, N1 12000,...	Current parameter settings.
Window is closed	Indicates that no more frames can be transmitted until some outstanding frames have been acknowledged.
IFRAMEs 12/28 RNRs 0/1...	Count of the different types of frames in the form of sent/received.

Show Interfaces Serial with PPP

An interface configured for synchronous PPP encapsulation differs from the standard show interface serial output. An interface configured for PPP might include the following information:

  lcp state = OPEN
  ncp ipcp state = OPEN   ncp osicp state = NOT NEGOTIATED
  ncp ipxcp state = NOT NEGOTIATED   ncp xnscp state = NOT NEGOTIATED
  ncp vinescp state = NOT NEGOTIATED   ncp deccp state = NOT NEGOTIATED
  ncp bridgecp state = NOT NEGOTIATED   ncp atalkcp state = NOT NEGOTIATED

Table 57 show the fields relevant to PPP connections.

**Table 57: Show Interfaces Serial Field Descriptions--With PPP Encapsulation**
Field	Description
lcp state	Link Control Protocol
ncp ipcp state	Network Control Protocol Internet Protocol Control Protocol
ncp osicp state	Network Control Protocol OSI (CLNS) Control Protocol
ncp ipxcp state	Network Control Protocol IPX (Novell) Control Protocol
ncp xnscp state	Network Control Protocol XNS Control Protocol
ncp vinescp state	Network Control Protocol VINES Control Protocol
ncp deccp state	Network Control Protocol DECnet Control Protocol
ncp bridgecp state	Network Control Protocol Bridging Control Protocol
ncp atalkcp state	Network Control Protocol AppleTalk Control Protocol

Sample Display with SDLC Connections

Use the show interfaces command to display the SDLC information for a given SDLC interface. The following is sample output from the show interfaces command for an SDLC primary interface supporting the SDLLC function:

Router# show interfaces
Serial 0 is up, line protocol is up
Hardware is MCI Serial
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC-PRIMARY, loopback not set
    Timers (msec): poll pause 100 fair poll 500. Poll limit 1
    [T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
    SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
             largest token ring frame 2052]
SDLC addr C1 state is CONNECT
     VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
     Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
     Poll: clear, Poll count: 0, chain: p: C1 n: C1
     SDLLC [largest SDLC frame: 265, XID: disabled]
 Last input 00:00:02, output 00:00:01, output hang never
 Output queue 0/40, 0 drops; input queue 0/75, 0 drops
 Five minute input rate 517 bits/sec, 30 packets/sec
 Five minute output rate 672 bits/sec, 20 packets/sec
     357 packets input, 28382 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     926 packets output, 77274 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets, 0 restarts
     2 carrier transitions

Table 58 shows the fields relevant to all SDLC connections.

**Table 58: Show Interfaces Serial Field Descriptions--With SDLC Enabled**
Field	Description
Timers (msec): poll pause, fair poll, Poll limit	Current values of these timers, as described in the configuration section, for this interface.
T1, N1, N2, K	Values for these parameters, as described in the configuration section, for this interface.

Table 59 shows other data given for each SDLC secondary configured to be attached to this interface.

**Table 59: SDLC Secondary Descriptions**
SDLC Secondary	Description
addr	Address of this secondary.
state is	Current state of this connection, which is one of the following: DISCONNECT--No communication is being attempted to this secondary. CONNECT--A normal connect state exists between this router and this secondary. DISCSENT--This router has sent a disconnect request to this secondary and is awaiting its response. SNRMSENT--This router has sent a connect request (SNRM) to this secondary and is awaiting its response. THEMBUSY--This secondary has told this router that it is temporarily unable to receive any more information frames. USBUSY--This router has told this secondary that it is temporarily unable to receive any more information frames. BOTHBUSY--Both sides have told each other that they are temporarily unable to receive any more information frames. ERROR--This router has detected an error and is waiting for a response from the secondary acknowledging this.
VS	Sequence number of the next information frame this station sends.
VR	Sequence number of the next information frame from this secondary that this station expects to receive.
Remote VR	Last frame transmitted by this station that has been acknowledged by the other station.
Current retransmit count:	Number of times the current I-frame or sequence of I-frames has been retransmitted.
Hold Queue	Number of frames in hold queue/Maximum size of hold queue.
IFRAMEs, RNRs, SNRMs, DISCs	Sent/received count for these frames.
Poll	"Set" if this router has a poll outstanding to the secondary; "clear" if it does not.
Poll Count	Number of polls in a row that have been given to this secondary at this time.
Chain	Shows the previous (p) and next (n) secondary address on this interface in the round robin loop of polled devices.

Sample Display with SDLLC

Use the show interfaces serial command to display the SDLLC statistics for SDLLC configured interfaces.

The following is sample output from the show interfaces serial command for an a serial interface configured for SDLLC:

Router# show interfaces serial
Serial 0 is up, line protocol is up
   Hardware is MCI Serial
   MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
   Encapsulation SDLC-PRIMARY, loopback not set
       Timers (msec): poll pause 100 fair poll 500. Poll limit 1
       [T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
       SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
             largest token ring frame 2052]
   SDLC addr C1 state is CONNECT
       VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
       Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
       Poll: clear, Poll count: 0, chain: p: C1 n: C1
       SDLLC [largest SDLC frame: 265, XID: disabled]
   Last input 00:00:02, output 00:00:01, output hang never
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   Five minute input rate 517 bits/sec, 30 packets/sec
   Five minute output rate 672 bits/sec, 20 packets/sec
       357 packets input, 28382 bytes, 0 no buffer
       Received 0 broadcasts, 0 runts, 0 giants
       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
       926 packets output, 77274 bytes, 0 underruns
       0 output errors, 0 collisions, 0 interface resets, 0 restarts
       6608 Last polled device: none
       SDLLC [ma: 0000.0C01.14--, ring: 7 brid2 carrier transitions

Most of the output shown in the display is generic to all SDLC encapsulated interfaces and is described in the "LLC2 and SDLC Commands" chapter in the Bridging and IBM Networking Command Reference. Table 60 shows the parameters specific to SDLLC.

**Table 60: SDLLC Parameter Descriptions**
Field	Description
SDLLC ma	Lists the MAC address configured for this interface. The last byte is shown as "--" to indicate that it is filled in with the SDLC address of the connection.
ring, bridge, target ring	Lists the parameters as configured by the sdllc traddr command.
largest token ring frame	Shows the largest Token Ring frame that is accepted on the LLC2 side of the connection.
largest SDLC frame	Shows the largest SDLC frame that is accepted and will be generated on the SDLC side of the connection.
XID	Enabled or disabled: Shows whether XID processing is enabled on the SDLC side of the connection. If enabled, it will show the XID value for this address.

Sample Display with Accounting Option

The following example illustrates the show interfaces serial command with the accounting option on a Cisco 7500:

Router# show interfaces serial 1/0 accounting
Serial1/0
       Protocol    Pkts In   Chars In   Pkts Out  Chars Out
             IP       7344    4787842       1803    1535774
      Appletalk      33345    4797459      12781    1089695
        DEC MOP          0          0        127       9779
            ARP          7        420         39       2340

show interfaces tokenring

Use the show interfaces tokenring privileged EXEC command to display information about the Token Ring interface and the state of source route bridging.

show interfaces tokenring unit [accounting]
show interfaces tokenring slot/port [accounting] (for the Cisco 7500 series and Cisco 7200 series)
show interfaces tokenring [slot/port-adapter/port] (for ports on VIP cards in the Cisco 7500 series routers)

Syntax Description

unit	Must match the interface port line number.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
slot	Refer to the appropriate hardware manual for slot and port information.
port	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The command description was modified in Cisco IOS Release 11.3 to account for support on new full-duplex token-ring port adapters.

If you do not provide values for the parameters slot and port, the command will display statistics for all the network interfaces. The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.

Sample Displays

The following is sample output from the show interfaces tokenring command:

Router# show interfaces tokenring
TokenRing 0 is up, line protocol is up
Hardware is 16/4 Token Ring, address is 5500.2000.dc27 (bia 0000.3000.072b)
   	Internet address is 150.136.230.203, subnet mask is 255.255.255.0
	   MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
   	Encapsulation SNAP, loopback not set, keepalive set (10 sec)
	   ARP type: SNAP, ARP Timeout 4:00:00
	   Ring speed: 16 Mbps
	   Single ring node, Source Route Bridge capable
	   Group Address: 0x00000000, Functional Address: 0x60840000
   	Last input 0:00:01, output 0:00:01, output hang never
   	Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   	Five minute input rate 0 bits/sec, 0 packets/sec
   	Five minute output rate 0 bits/sec, 0 packets/sec
	   16339 packets input, 1496515 bytes, 0 no buffer
		        Received 9895 broadcasts, 0 runts, 0 giants
		        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     32648 packets output, 9738303 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
     5 transitions

Table 61 describes significant fields shown in the display.

**Table 61: Show Interfaces Tokenring Field Descriptions (Continued)**
Field	Description
Token Ring is { up \| down }	Interface is either currently active and inserted into ring (up) or inactive and not inserted (down). On the Cisco 7500 series, gives the interface processor type, slot number, and port number.
Token Ring is Reset	Hardware error has occurred.
Token Ring is Initializing	Hardware is up, in the process of inserting the ring.
Token Ring is Administratively Down	Hardware has been taken down by an administrator.
line protocol is {up \| down \| administratively down}	Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful).
Hardware	Hardware type. "Hardware is Token Ring" indicates that the board is a CSC-R board. "Hardware is 16/4 Token Ring" indicates that the board is a CSC-R16 board. Also shows the address of the interface.
Internet address	Lists the Internet address followed by subnet mask.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether loopback is set or not.
keepalive	Indicates whether keepalives are set or not.
ARP type:	Type of Address Resolution Protocol assigned.
Ring speed:	Speed of Token Ring--4 or 16 Mbps.
{Single ring \|multiring node}	Indicates whether a node is enabled to collect and use source routing information (RIF) for routable Token Ring protocols.
Group Address:	Interface's group address, if any. The group address is a multicast address; any number of interfaces on the ring may share the same group address. Each interface may have at most one group address.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, drops Input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate, Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of a station transmitting bad data.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
packets output	Total number of messages transmitted by the system.
bytes output	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Since a Token Ring cannot have collisions, this statistic is nonzero only if an unusual event occurred when frames were being queued or dequeued by the system software.
interface resets	Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
restarts	Should always be zero for Token Ring interfaces.
transitions	Number of times the ring made a transition from up to down, or vice versa. A large number of transitions indicates a problem with the ring or the interface.

The following is sample output from the show interfaces tokenring command on a Cisco 7500:

Router# show interfaces tokenring 2/0
TokenRing2/0 is administratively down, line protocol is down
  Hardware is cxBus Token Ring, address is 0000.3040.8b4a (bia 0000.3040.8b4a)
  MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
  Encapsulation SNAP, loopback not set, keepalive set (10 sec)
  ARP type: SNAP, ARP Timeout 4:00:00
  Ring speed: 0 Mbps
  Single ring node, Source Route Transparent Bridge capable
  Ethernet Transit OUI: 0x0000F8
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets, 0 restarts
     1 transitions

The following example on the Cisco 7500 includes the accounting option.When you use the accounting option, only the accounting statistics are displayed.

Router# show interfaces tokenring 2/0 accounting
TokenRing2/0
       Protocol    Pkts In   Chars In   Pkts Out  Chars Out
             IP       7344    4787842       1803    1535774
      Appletalk      33345    4797459      12781    1089695
        DEC MOP          0          0        127       9779
            ARP          7        420         39       2340

show interfaces tunnel

To list tunnel interface information, use the show interfaces tunnel privileged EXEC command.

show interfaces tunnel number [accounting]

Syntax Description

number	Port line number.
accounting	(Optional) Displays the number of packets of each protocol type that have been sent through the interface.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

The following is sample output from the show interface tunnel command:

Router# show interfaces tunnel 4
Tunnel4 is up, line protocol is down
  Hardware is Routing Tunnel
  MTU 1500 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
  Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
  Tunnel source 0.0.0.0, destination 0.0.0.0
  Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Output queue 0/0, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 0 bits/sec, 0 packets/sec
  Five minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets, 0 restarts

Table 62 describes significant fields shown in the display.

**Table 62: Show Interfaces Tunnel Field Descriptions**
Field	Description
Tunnel is {up \| down}	Interface is currently active and inserted into ring (up) or inactive and not inserted (down). On the Cisco 7500 series, gives the interface processor type, slot number, and port number.
line protocol is {up \| down \| administratively down}	Shows line protocol up if a valid route is available to the tunnel destination. Shows line protocol down if no route is available, or if the route would be recursive.
Hardware	Specifies the hardware type.
MTU	Maximum Transmission Unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation	Encapsulation method is always TUNNEL for tunnels.
loopback	Indicates whether loopback is set or not.
keepalive	Indicates whether keepalives are set or not.
Tunnel source	IP address used as the source address for packets in the tunnel.
destination	IP address of the host destination.
Tunnel protocol	Tunnel transport protocol (the protocol the tunnel is using). This is based on the tunnel mode command, which defaults to GRE.
key	ID key for the tunnel interface, unless disabled.
sequencing	Indicates whether the tunnel interface drops datagrams that arrive out of order. Can be disabled.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
Output queue, drops Input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
Five minute input rate, Five minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes. The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input	Total number of error-free packets received by the system.
bytes	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of a station transmitting bad data.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
abort	Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This usually is the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). Some collisions are normal. However, if your collision rate climbs to around 4 or 5%, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
restarts	Number of times the controller was restarted because of errors.

Related Commands

You can use the master indexes or search online to find documentation of related commands.

show interfaces
show ip route
show route

show interfaces vg-anylan

Use the show interfaces vg-anylan EXEC command to display the information about the 100VG-AnyLAN port adapter on Cisco 7200 series routers, Cisco 7500 series routers.

show interfaces vg-anylan [slot/port-adapter/port] (on VIP cards in Cisco 7500 series)
show interfaces vg-anylan [slot/port] (Cisco 7200 series)

Syntax Description

slot	Refer to the appropriate hardware manual for slot and port information.
port-adapter	Refer to the appropriate hardware manual for information about port adapter compatibility.
port	Refer to the appropriate hardware manual for slot and port information.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3.

Sample Display

The following is sample output from the show interfaces vg-anylan command:

Router# show interfaces vg-anylan 3/0/0
VG-AnyLAN3/0/0 is up, line protocol is up 
  Hardware is cyBus VG-AnyLAN Interface
  Frame type is 802.3, address is 0060.3e64.2460 (bia 0060.3e64.2460)
  Internet address is 10.1.1.5/16
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:26, output 00:00:09, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     5316 packets input, 857349 bytes, 0 no buffer
     Received 5310 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 input packets with dribble condition detected
     7920 packets output, 754259 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 vg alignment error, 0 vg balance error
     0 vg invalid ipm  error, 0 vg symbol error
     0 vg skew error, 0 vg frame delimit error
     0 vg high priority packets, 0 vg high priority octets

Table 63 describes significant fields in this output.

**Table 63: Show Interfaces VG-AnyLAN Field Descriptions**
Field	Description
VG-AnyLAN3/0/0 is up, line protocol is up	Indicates if the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
Hardware is cyBus VG-AnyLAN	Hardware type.
Frame type is 803.2	Currently the frame type supported is 803.2.
Internet address	Internet address and subnet mask.
MTU	Maximum transmission unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
Encapsulation	Encapsulation method assigned to the interface.
loopback	Indicates if loopbacks are set.
keepalive	Indicates if keepalives are set.
ARA type	ARP type on the interface.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
last clearing	Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less then 232ms) ago.
Queueing strategy	First-in, first-out queuing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
5 minute input rate 5 minute output rate	Average number of bits and packets received or transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes (input)	Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
abort	Illegal sequence of one bits on the interface.
input packets with dribble condition detected	Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
packets output	Total number of messages transmitted by the system.
bytes (output)	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
collisions	Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
output buffer failures	Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory.
output buffers swapped out	Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty.
vg alignment error	Number of non-octets received.
vg balance error	Number of incorrect balanced symbols received.
vg invalid ipm error	Number of packets received with an invalid packet marker (IPM).
vg symbol error	Number of symbols received that were not correctly decoded.
vg skew error	Number of skews between four pairs of twisted-pair wire that exceeded the allowable skew.
vg frame delimit error	Number of start-of-frame errors or false-start errors received.
vg high priority packets	Number of high-priority packets received.
vg high priority octets	Number of high-priority octets received.

Related Commands

You can use the master indexes or search online to find documentation of related commands.

interface vg-anylan

show ip interface

To list a summary of an interface's IP information and status, use the show ip interface privileged EXEC command.

show ip interface [brief] [type] [number]

Syntax Description

brief	(Optional) Displays a brief summary of IP status and configuration.
type	(Optional) Specifies that information be displayed about that interface type only. The possible value depends on the type of interfaces the system has. For example, it could be ethernet, null, serial, tokenring, and so forth.
number	(Optional) Interface number.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Displays

The following is sample output from the show ip interface command:

Router# show ip interface
Ethernet0 is administratively down, line protocol is down
  Internet address is 1.0.46.10, subnet mask is 255.0.0.0
  Broadcast address is 255.255.255.255
  Address determined by setup command
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is enabled
  Multicast groups joined: 224.0.0.1 224.0.0.2
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent
  ICMP mask replies are never sent
  IP fast switching is enabled
  IP fast switching on the same interface is disabled
  IP SSE switching is disabled
  Router Discovery is disabled
  IP accounting is disabled
  TCP/IP header compression is disabled
  Probe proxy name replies are disabled
  Gateway Discovery is disabled
PCbus0 is administratively down, line protocol is down
  Internet address is 198.135.1.43, subnet mask is 255.255.255.0
  Broadcast address is 255.255.255.255
  Address determined by setup command
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is enabled
  Multicast groups joined: 224.0.0.1 224.0.0.2
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent
  ICMP mask replies are never sent
  IP fast switching is enabled
  IP fast switching on the same interface is disabled
  IP SSE switching is disabled
  Router Discovery is disabled
  IP accounting is disabled
  TCP/IP header compression is disabled
  Probe proxy name replies are disabled
  Gateway Discovery is disabled
Serial0 is administratively down, line protocol is down
  Internet address is 198.135.2.49, subnet mask is 255.255.255.0
  Broadcast address is 255.255.255.255
  Address determined by setup command
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is enabled
  Multicast groups joined: 224.0.0.1 224.0.0.2
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent
  ICMP mask replies are never sent
  IP fast switching is enabled
  IP fast switching on the same interface is disabled
  IP SSE switching is disabled
  Router Discovery is disabled
  IP accounting is disabled
  TCP/IP header compression is disabled
  Probe proxy name replies are disabled
  Gateway Discovery is disabled

The following is sample output from the show ip interface brief command:

Router# show ip interface brief
Interface    IP-Address      OK?  Method     Status                 Protocol
Ethernet0    1.0.46.10       YES  manual     administratively down  down    
PCbus0       198.135.1.43    YES  manual     administratively down  down    
Serial0      198.135.2.49    YES  manual     administratively down  down

The following is sample output from the show ip interface brief pcbus 0 command:

Router# show ip interface brief pcbus 0
Interface    IP-Address      OK?  Method     Status                 Protocol
PCbus0       198.135.1.43    YES  manual     administratively down  down

Related Commands

You can use the master indexes or search online to find documentation of related commands.

show interfaces

show rif

Use the show rif EXEC command to display the current contents of the RIF cache.

show rif

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

The following is sample output from the show rif command:

Router# show rif
Codes: * interface, - static, + remote
Hardware Addr  How   Idle (min)  Routing Information Field
5C02.0001.4322 rg5           -   0630.0053.00B0
5A00.0000.2333 TR0           3   08B0.0101.2201.0FF0
5B01.0000.4444 -             -   -
0000.1403.4800 TR1           0   -
0000.2805.4C00 TR0           *   -
0000.2807.4C00 TR1           *   -
0000.28A8.4800 TR0           0   -
0077.2201.0001 rg5          10   0830.0052.2201.0FF0

In the display, entries marked with an asterisk (*) are the router/bridge's interface addresses. Entries marked with a dash (-) are static entries. Entries with a number are cached entries. If the RIF timeout is set to something other than the default of 15 minutes, the timeout is displayed at the top of the display.

Table 64 describes significant fields shown in the display.

**Table 64: Show RIF Cache Display Field Descriptions**
Field	Description
Hardware Addr	Lists the MAC-level addresses.
How	Describes how the RIF has been learned. Possible values include a ring group (rg), or interface (TR).
Idle (min)	Indicates how long, in minutes, since the last response was received directly from this node.
Routing Information Field	Lists the RIF.

show service-module serial

To display the performance report for an integrated CSU/DSU, use the show service-module serial privileged EXEC command.

show service-module serial number [performance-statistics [interval-range]]

Syntax Description

number	Interface number 0 or 1.
performance-statistics	(Optional) Displays the CSU/DSU performance statistics for the past 24 hours. This keyword applies only to the fractional T1/T1 module.
interval-range	(Optional) Specifies the number of 15-minute intervals displayed. You can choose a range from 1 to 96, where each value represents the CSU/DSU activity performed in that 15-minute interval. For example, a range of 2-3 displays the performance statistics for the intervals two and three.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

This command applies to the 2- and 4-wire 56/64-kbps CSU/DSU module and FT1/T1 CSU/DSU module. The performance-statistics keyword applies only to the FT1/T1 CSU/DSU module.

Sample Displays

The following example shows CSU/DSU performance statistics on a Cisco 2524 or Cisco 2525 router for intervals 30 to 32. Each interval is 15 minutes long. All the data is zero because no errors were discovered on the T1 line:

Router# show service-module serial 1 performance-statistics 30-32
Total Data (last 58 15 minute intervals):
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in current interval (131 seconds elapsed):
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 30:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 31:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 32:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

The following example is sample output from the show service-module serial command:

Router1# show service-module serial 0
Module type is T1/fractional
    Hardware revision is B, Software revision is 1.1 ,
    Image checksum is 0x2160B7C, Protocol revision is 1.1
Receiver has AIS alarm,
Unit is currently in test mode:
    line loopback is in progress
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536 Kbits/sec.
Last user loopback performed:
    remote loopback
    Failed to loopup remote
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:05:50
    loss of signal        :    1, last occurred 0:01:50
    loss of frame         :    0,
    AIS alarm             :    1, current duration 0:00:49
    Remote alarm          :    0,
    Module access errors  :    0,
Total Data (last 0 15 minute intervals):
Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in current interval (351 seconds elapsed):
    1466 Line Code Violations, 0 Path Code Violations
    25 Slip Secs, 49 Fr Loss Secs, 40 Line Err Secs, 1 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 49 Unavail Secs
Router1# show service-module serial 1
Module type is 4-wire Switched 56
    Hardware revision is B, Software revision is 1.00,
    Image checksum is 0x44453634, Protocol revision is 1.0
Connection state: active,
Receiver has loss of signal, loss of sealing current,
Unit is currently in test mode:
    line loopback is in progress
Current line rate is 56 Kbits/sec
Last user loopback performed:
    dte loopback
    duration 00:00:58
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:13:54
    oos/oof               :    3, last occurred 0:00:24
    loss of signal        :    3, current duration 0:00:24
    loss of sealing curren:    2, current duration 0:04:39
    loss of frame         :    0,
    rate adaption attempts:    0,

The following example shows sample output from the show service-module serial command issued on a Cisco 3640 modular access router:

router# show service-module serial 0/1
Module type is 4-wire Switched 56
    Hardware revision is B, Software revision is 1.00,
    Image checksum is 0x42364436, Protocol revision is 1.0
Connection state: Idle
Receiver has no alarms.
CSU/DSU Alarm mask is 0
Current line rate is 56 Kbits/sec
Last module self-test (done at startup): Passed
Last clearing of alarm counters 4d02h
    oos/oof               :    0,
    loss of signal        :    0,
    loss of sealing curren:    0,
    loss of frame         :    0,
    rate adaptation attemp:    0,

The following example shows sample output from the show service-module serial command issued on a Cisco 1605 router:

router# show service-module serial 0
Module type is 4-wire Switched 56
    Hardware revision is B, Software revision is 1.00,
    Image checksum is 0x42364436, Protocol revision is 1.0
Receiver has oos/oof, loss of signal,
CSU/DSU Alarm mask is 4
Current line rate is 56 Kbits/sec
Last module self-test (done at startup): Passed
Last clearing of alarm counters 1d02h
    oos/oof               :    1, current duration 1d02h
    loss of signal        :    1, current duration 1d02h
    loss of frame         :    0,
    rate adaptation attemp:    0,

Table 65 describes the fields displayed by the show service-module serial command.

**Table 65: Show Service-Module Output Field Descriptions**
Field	Description
Module type	The CSU/DSU module installed in the router. The possible modules are T1/fractional, 2-wire switched 56-kbps, and 4-wire 56/64-kbps.
Receiver has AIS alarm	Alarms detected by the FT1/T1 CSU/DSU module or 2- and 4-wire 56/64-kbps CSU/DSU modules. Possible T1 alarms are as follows: Transmitter is sending remote alarm. Transmitter is sending AIS. Receiver has loss of signal. Receiver has loss of frame. Receiver has remote alarm. Receiver has no alarms. Possible switched 56k alarms are as follows: Receiver has loss of signal Receiver has loss of sealing current Receiver has loss of frame Receiver has rate adaptation attempts
		Unit is currently in test mode	Loopback tests are in progress.
		Framing is ESF	Indicates frame type used on the line. Can be extended super frame or super frame.
		Line Code is B8ZS	Indicated line-code type configured. Can be alternate mark inversion (AMI) or binary 8-zero substitution (B8ZS).
		Current clock source is line	Clock source configured on the line, which can be supplied by the service provider (line) or the integrated CSU/DSU module (internal).
		Fraction has 24 timeslots	Number of timeslots defined for the FT1/T1 module, which can range from 1 to 24.
		Net bandwidth	Total bandwidth of the line (for example, 24 timeslots multiplied by 64 kbps equals a bandwidth of 1536 kbps).
		Last user loopback performed	Type and outcome of the last performed loopback.
		Last module self-test (done at startup): Passed	Status of the last self test performed on an integrated CSU/DSU module.
Last clearing of alarm counters	List of network alarms that were detected and cleared on the CSU/DSU module.
Total Data Data in current interval	Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer.
Line Code Violations	Indicates the occurrence of either a bipolar violation or excessive zeroes error event.
Path Code Violations	Indicates a frame synchronization bit error in the D4 and E1-no CRC formats or a CRC error in the ESF and E1-CRC formats.
Slip Secs	Indicates the replication or detection of the payload bits of a DS1 frame. A slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal.
Fr Loss Secs	Indicates the number of seconds an out of frame error is detected.
Line Err Secs	Line errored seconds is a second in which one or more line code violation errors are detected.
Errored Secs	In ESF and E1-CRC links, an errored second is a second in which one of the following is detected: one or more path code violations; one or more out of frame defects; one or more controlled slip events; a detected AIS defect. For D4 and E1-no CRC links, the presence of bipolar violation also triggers an errored second.
Bursty Err Secs	A second with fewer than 320 and more than 1 path coding violation errors. No severely errored frame defects or incoming AIS defects are detected. Controlled slips are not included in this parameter.
Severely Err Secs	For ESF signals, a second with one of the following errors: 320 or more path code violation errors; one or more out of frame defects; a detected AIS defect. For D4 signals, a count of 1-second intervals with framing errors, or an out of frame defect, or 1544 line code violations.
Unavail Secs	Total time the line was out of service.

Related Commands

You can use the master indexes or search online to find documentation of related commands.

clear service-module

Table of Contents

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Sample Display with Custom Output Queuing

Sample Display Including Weighted-Fair-Queuing Output

Sample Display with Accounting Option

Sample Show Interfaces Accounting Display

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Sample Display on Cisco 7500

Sample Display with Accounting Option

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Related Commands

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Sample Display with Frame Relay Encapsulation

Sample Display with ANSI LMI

Sample Display with LAPB Encapsulation

Sample Display with SDLC Connections

Sample Display with SDLLC

Sample Display with Accounting Option

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Related Commands

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Related Commands

Syntax Description

Command Mode

Usage Guidelines

Sample Displays

Related Commands

Syntax Description

Command Mode

Usage Guidelines

Sample Display

Syntax Description

Command Mode

Usage Guidelines