Table Of Contents

show interfaces

show interfaces ethernet

show interfaces fastethernet

show interfaces fddi

show interfaces hssi

show interfaces lex

show interfaces loopback

show interfaces port-channel

show interfaces pos

show interfaces posi

show interfaces serial

show interfaces tokenring

show interfaces tunnel

show interfaces vg-anylan

show interfaces

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

show interfaces [type number] [first] [last] [accounting]

Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor

show interfaces [type slot/port] [accounting]

Cisco 7500 Series with Ports on VIPs

show interfaces [type slot/port-adapter/port] [ethernet | serial]

Syntax Description

type	(Optional) Interface type. Allowed values for type include async, bri0, dialer, ethernet, fastethernet, fddi, hssi, loopback, null, serial, tokenring, and tunnel. For the Cisco 4000 series routers, type can be e1, ethernet, fastethernet, fddi, serial, t1, and token. For the Cisco 4500 series routers, 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 series type can also include pos.
number	(Optional) Port number on the selected interface.
first last	(Optional) For the Cisco 2500 and 3000 series routers, 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	(Optional) Number of the slot being configured. Refer to the appropriate hardware manual for slot and port information.
port	(Optional) Number of the port being configured. Refer to the appropriate hardware manual for slot and port information.
port-adapter	(Optional) Number of the port-adapter being configured. Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.
12.0(3)T	This command was modified to include support for flow-based WRED.
12.0(4)T	This command was modified to include enhanced display information for dialer bound interfaces.
12.0(7)T	This command was modified to include dialer as an interface type, and to reflect the default behavior.

Usage Guidelines

The show interfaces command displays statistics for the network interfaces. The resulting display on the Cisco 7200 series routers 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 routers 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.

If you use the show interfaces command on dialer interfaces configured for binding, the display will report statistics on each physical interface bound to the dialer interface; see the following examples for more information.

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.

Examples

The following is an example 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.

---

Note If an asterisk (*) appears after the throttles counter value, it means that the interface was throttled at the time the command was run.

---

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, 57186* throttles

     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

...

Example with Custom Output Queueing

The following shows partial sample output when custom output queueing 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 queueing 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 Queueing output in Table 29.

Example including Weighted-Fair-Queueing Output

For each interface on the router or access server configured to use weighted fair queueing, 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 29 describes the input queue and output queue fields shown in the preceding display.

Table 29 Weighted-Fair-Queueing 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.

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

---

Per-packet accounting information is kept for the following protocols:

•Apollo

•AppleTalk

•ARP (for IP, Apollo, Frame Relay, SMDS)

•CLNS

•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

•HP Probe

•IP

•LAN Manager (LAN Network Manager and IBM Network Manager)

•Novell

•Serial Tunnel (SDLC)

•Spanning Tree

•SR Bridge

•Transparent Bridge

•VINES

•XNS

Example with DWRED

The following is sample output from the show interfaces command when DWRED is enabled on an interface. Notice that the packet drop strategy is listed as "VIP-based weighted RED."

Router# show interfaces hssi0/0/0

Hssi0/0/0 is up, line protocol is up

  Hardware is cyBus HSSI

  Description: 45Mbps to R1

Internet address is 200.200.14.250/30

MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 255/255, load 1/255

Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input 00:00:02, output 00:00:03, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

Packet Drop strategy: VIP-based weighted RED

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

1976 packets input, 131263 bytes, 0 no buffer

Received 1577 broadcasts, 0 runts, 0 giants

0 parity

4 input errors, 4 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

1939 packets output, 130910 bytes, 0 underruns

0 output errors, 0 applique, 3 interface resets

0 output buffers copied, 0 interrupts, 0 failures

Example with ALC

The following is sample output from the show interfaces command for the serial 2 interface when ALC is enabled:

Router# show interfaces serial 2

Serial2 is up, line protocol is up

Hardware is CD2430

MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation ALC, loopback not set

Full-duplex enabled.

     ascus in UP state: 42, 46

     ascus in DOWN state: 

     ascus DISABLED: 

Last input never, output never, 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

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, 3 interface resets

0 output buffer failures, 0 output buffers swapped out

DCD=down  DSR=down  DTR=down  RTS=down  CTS=down

Example with SDLC

The following is sample output from the show interfaces command for an SDLC primary interface supporting the SDLC 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 30 shows the fields relevant to all SDLC connections.

Table 30 show interfaces Field Descriptions When SDLC is Enabled 

Field	Description
Timers (msec)	List of timers in milliseconds.
poll pause, fair poll, Poll limit	Current values of these timers, as described in the individual commands in this chapter.
T1, N1, N2, K	Current values for these variables, as described in the individual commands in this chapter.

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

Table 31 SDLC Field Descriptions 

Field	Description
addr	Address of this secondary.
State	Current state of this connection. The possible values are: •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.
RCNT	Number of correctly sequenced I-frames received when the Cisco IOS software was in a state in which it is acceptable to receive I-frames.
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, 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 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).

Example with Flow-based WRED

The following is sample output from the show interfaces command issued for the Serial1 interface for which flow-based WRED is enabled. The output shows that there are 8 active flow-based WRED flows, that the maximum number of flows active at any time is 9, and the maximum number of possible flows configured for the interface is 16:

Router# show interfaces serial1

Serial1 is up, line protocol is up 

  Hardware is HD64570

  Internet address is 190.1.2.1/24

  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

Reliability 255/255, txload 237/255, rxload 1/255

  Encapsulation HDLC, loopback not set

  Keepalive not set

  Last input 00:00:22, output 00:00:00, output hang never

  Last clearing of "show interface" counters 00:17:58

  Input queue: 0/75/0 (size/max/drops); Total output drops: 2479

  Queueing strategy: random early detection(RED)

    flows (active/max active/max): 8/9/16

    mean queue depth: 27

    drops: class  random   tail     min-th   max-th   mark-prob 

           0      946      0        20       40       1/10

           1      488      0        22       40       1/10

           2      429      0        24       40       1/10

           3      341      0        26       40       1/10

           4      235      0        28       40       1/10

           5      40       0        31       40       1/10

           6      0        0        33       40       1/10

           7      0        0        35       40       1/10

           rsvp   0        0        37       40       1/10

  30 second input rate 1000 bits/sec, 2 packets/sec

  30 second output rate 119000 bits/sec, 126 packets/sec

     1346 packets input, 83808 bytes, 0 no buffer

     Received 12 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     84543 packets output, 9977642 bytes, 0 underruns

     0 output errors, 0 collisions, 6 interface resets

     0 output buffer failures, 0 output buffers swapped out

     0 carrier transitions

     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

Example with DWFQ

The following is sample output from the show interfaces command when DWFQ is enabled on an interface. Notice that the queueing strategy is listed as "VIP-based fair queueing."

Router# show interfaces fastethernet 1/1/0

Fast Ethernet 1/1/0 is up, line protocol is up

  Hardware is cyBus Fast Ethernet Interface, address is 0007.f618.4448 (bia 00e0)

  Description: pkt input i/f for WRL tests (to pagent)

  Internet address is 80.0.2.70/24

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255

  Encapsulation ARPA, loopback not set, keepalive not set, fdx, 100BaseTX/FX

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input never, output 01:11:01, output hang never

  Last clearing of "show interface" counters 01:12:31

  Queueing strategy: VIP-based fair queueing

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  30 second input rate 0 bits/sec, 0 packets/sec

  30 second 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

     1 packets output, 60 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffers copied, 0 interrupts, 0 failures

Example with DNIS Binding

When the show interfaces command is issued on an unbound dialer interface, the output looks as follows:

Router# show interfaces dialer0 

Dialer0 is up (spoofing), line protocol is up (spoofing)

  Hardware is Unknown

  Internet address is 21.1.1.2/8

  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 3/255

  Encapsulation PPP, loopback not set

  DTR is pulsed for 1 seconds on reset

  Last input 00:00:34, output never, output hang never

  Last clearing of "show interface" counters 00:05:09

  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 1000 bits/sec, 0 packets/sec

     18 packets input, 2579 bytes

     14 packets output, 5328 bytes

But when the show interfaces command is issued on a bound dialer interface, you will get an additional report indicating the binding relationship. The output looks as follows:

Router# show interfaces dialer0 

Dialer0 is up, line protocol is up 

  Hardware is Unknown

  Internet address is 21.1.1.2/8

  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255

  Encapsulation PPP, loopback not set

  DTR is pulsed for 1 seconds on reset

  Interface is bound to BRI0:1

  Last input 00:00:38, output never, output hang never

  Last clearing of "show interface" counters 00:05:36

  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

     38 packets input, 4659 bytes

     34 packets output, 9952 bytes

Bound to:

BRI0:1 is up, line protocol is up 

  Hardware is BRI

  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255

  Encapsulation PPP, loopback not set, keepalive not set

  Interface is bound to Dialer0 (Encapsulation PPP)

  LCP Open, multilink Open

  Last input 00:00:39, output 00:00:11, 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

     78 packets input, 9317 bytes, 0 no buffer

     Received 65 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     93 packets output, 9864 bytes, 0 underruns

     0 output errors, 0 collisions, 7 interface resets

     0 output buffer failures, 0 output buffers swapped out

     4 carrier transitions

At the end of Dialer0 output, the show interfaces command is executed on each physical interface bound to it.

In the next example, the physical interface is the B1 channel of the BRI0 link. This example also illustrates that the output under the B channel keeps all hardware counts that are not displayed under any logical or virtual access interface. The line in the report that states "Interface is bound to Dialer0 (Encapsulation LAPB)" indicates that this B interface is bound to Dialer0 and the encapsulation running over this connection is LAPB, not PPP, which is the encapsulation configured on the D interface and inherited by the B channel.

Router# show interface bri0:1 

BRI0:1 is up, line protocol is up 

  Hardware is BRI

  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255

  Encapsulation PPP, loopback not set, keepalive not set

  Interface is bound to Dialer0 (Encapsulation LAPB)

  LCP Open, multilink Open

  Last input 00:00:31, output 00:00:03, 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, 1 packets/sec

  5 minute output rate 0 bits/sec, 1 packets/sec

     110 packets input, 13994 bytes, 0 no buffer

     Received 91 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     135 packets output, 14175 bytes, 0 underruns

     0 output errors, 0 collisions, 12 interface resets

     0 output buffer failures, 0 output buffers swapped out

     8 carrier transitions

Any protocol configuration and states should be displayed from the Dialer0 interface.

show interfaces ethernet

To display information about an Ethernet interface on the router, use the show interfaces ethernet privileged EXEC command.

show interfaces ethernet unit [accounting]

Cisco 7200 and 7500 Series

show interfaces ethernet [slot/port] [accounting]

Cisco 7500 Series with Ports on VIPs

show interfaces ethernet [type slot/port-adapter/port]

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	(Optional) Number of the slot being configured. Refer to the appropriate hardware manual for slot and port information.
port	(Optional) Number of the port being configured. Refer to the appropriate hardware manual for slot and port information.
type	(Optional) Type of interface.
port-adapter	(Optional) Number of the port-adapter being configured. Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

If you do not provide values for the argument unit (or slot and port on the Cisco 7200 series routers or slot and port adapter on the Cisco 7500 series routers), the command displays 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.

Examples

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

Router# show interfaces ethernet 0

Ethernet0 is up, line protocol is up 

  Hardware is Lance, address is 0060.3ef1.702b (bia 0060.3ef1.702b)

  Internet address is 172.21.102.33/24

  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 04:00:00

  Last input 00:00:20, output 00:00:06, 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

     115331 packets input, 27282407 bytes, 0 no buffer

     Received 93567 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     0 input packets with dribble condition detected

     143782 packets output, 14482169 bytes, 0 underruns

     0 output errors, 1 collisions, 5 interface resets

     0 babbles, 0 late collision, 7 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Table 32 describes significant fields shown in the display.

Table 32 show interfaces ethernet Field Descriptions 

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 percent 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 and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.
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 231 ms (and less than 232 ms) 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 1518 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 transmitted due to an Ethernet collision. 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. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
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.

Example on Cisco 7500 Series Routers

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

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

     0 babbles, 2 late collision, 7 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Example with Accounting Option

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

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

To display information about the Fast Ethernet interfaces, use the show interface fastethernet EXEC command.

Cisco 4500 and 4700 Series

show interfaces fastethernet [number]

Cisco 7200 and 7500 Series

show interfaces fastethernet [slot/port]

Cisco 7500 Series with a VIP

show interfaces fastethernet [slot/port-adapter/port]

Syntax Description

number	(Optional) Port, connector, or interface card number. On a Cisco 4500 or Cisco 4700 series routers, 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	(Optional) Number of the slot being configured. Refer to the appropriate hardware manual for slot and port information.
port	(Optional) Number of the port being configured. Refer to the appropriate hardware manual for slot and port information.
port-adapter	(Optional) Number of the port-adapter being configured. Refer to the appropriate hardware manual for information about port adapter compatibility.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Examples

The following is an example for the show interface fastethernet on a Cisco 4500 series routers:

c4500-1# show interfaces fastethernet 0

Fast Ethernet0 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 is an example for the show interface fastethernet on a Cisco AS5300 access server:

as5300# show interface fastethernet 0

Fast Ethernet0 is up, line protocol is up

  Hardware is DEC21140AD, address is 00e0.1e3e.c179 (bia 00e0.1e3e.c179)

  Internet address is 1.17.30.4/16

  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255

  Encapsulation ARPA, loopback not set, keepalive set (10 sec)

  Half-duplex, 10Mb/s, 100BaseTX/FX

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output 00:00:03, output hang never

  Last clearing of "show interface" counters never

  Queueing strategy: fifo

  Output queue 0/40, 0 drops; input queue 0/120, 8 drops

  5 minute input rate 2000 bits/sec, 3 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     158773 packets input, 17362631 bytes, 4 no buffer

     Received 158781 broadcasts, 0 runts, 0 giants, 7 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     0 watchdog, 0 multicast

     0 input packets with dribble condition detected

     6299 packets output, 622530 bytes, 0 underruns

     1 output errors, 0 collisions, 3 interface resets

     0 babbles, 0 late collision, 0 deferred

     1 lost carrier, 1 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 series routers:

Router# show interface fastethernet 0/1

Fast Ethernet0/1 is administratively down, line protocol is down

  Hardware is cxBus Fast Ethernet, 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 33 describes the fields in these displays.

Table 33 show interfaces fastethernet Field Descriptions—FEIP 

Field	Description
Fast Ethernet0 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 percent 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 and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.
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. This counter is updated only when packets are process switched, not when packets are fast switched.
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 231 ms (and less than 232 ms) 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 1518 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 transmit