Table Of Contents

show interfaces

show interfaces analysis-module

show interfaces content-engine

show interfaces ctunnel

show interfaces ethernet

show interfaces fastethernet

show interfaces fddi

show interfaces gigabitethernet

show interfaces hssi

show interfaces loopback

show interfaces port-channel

show interfaces pos

show interfaces satellite

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 command in privileged EXEC mode. The resulting output varies, depending on the network for which an interface has been configured.

Cisco 2500 Series, Cisco 2600 Series, Cisco 4700 Series, and Cisco 7000 Series

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]

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 4500 series routers, type can be atm, e1, ethernet, fastethernet, fddi, serial, t1, and token.. 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 series routers, ISDN BRI only. The first argument can be either 1 or 2. The last argument 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 have been sent through the interface.
slot	(Optional) Slot number. Refer to the appropriate hardware manual for slot information.
/port	(Optional) Port number. Refer to the appropriate hardware manual for port information.
/port-adapter	(Optional) Port adapter number. 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

Display Interpretation

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.

Information About Specific Interfaces

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.

Removed Interfaces

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

Weighted Fair Queueing Information

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.

Accounting Information

The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.

Dialer Interfaces Configured for Binding

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.

Command Variations

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 that follow.

Examples

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.

---

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 10.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:

Router# show interfaces

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

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 10.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 
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 47 describes the input queue and output queue fields shown in the preceding two displays.

Table 47 Weighted-Fair-Queueing Output Field Descriptions 

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 High-Level Data Link Control (HDLC) encapsulation.

---

Per-packet accounting information is displayed for protocols. The following is an example of protocols for which accounting information is displayed. This list is not inclusive of all protocols and could vary among platforms.

•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

•IP

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

•Novell

•Serial Tunnel (SDLC)

•Spanning Tree

•SR Bridge

•Transparent Bridge

•VINES

•XNS

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

The following is sample output from the show interfaces accounting command when a switched packet is dropped:

Router# show interfaces accounting

FastEthernet0/2

       Protocol    Pkts In   Chars In   Pkts Out  Chars Out

          Other          0          0       9373      562380

             IP      37342   21789327        954       86850

        DEC MOP          0          0        158       12166

            ARP        882      52920         71        4260

Interface FastEthernet1/0 is disabled

Interface FastEthernet1/1 is disabled

       Protocol    Pkts In   Chars In   Pkts Out  Chars Out

No traffic sent or received on this interface

Table 48 describes the fields shown in the display.

Table 48 show interfaces accounting Field Descriptions

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.

Example with DWRED

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

Router# show interfaces hssi 0/0/0

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

  Hardware is cyBus HSSI

  Description: 45Mbps to R1

Internet address is 10.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 serial interface 2 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 a Synchronous Data Link Control (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 49 shows the fields relevant to all SDLC connections.

Table 49 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 50 shows other data given for each SDLC secondary interface configured to be attached to this interface.

Table 50 SDLC Field Descriptions 

Field	Description
addr	Address of this secondary interface.
State	Current state of this connection. The possible values follow: •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.

Example with Flow-Based WRED

The following is sample output from the show interfaces command issued for the Serial interface 1 for which flow-based weighted RED (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 that the maximum number of possible flows configured for the interface is 16:

Router# show interfaces serial 1

Serial1 is up, line protocol is up 

  Hardware is HD64570

  Internet address is 10.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 distributed weighted fair queueing (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 10.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 10.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 that indicates the binding relationship. The output is shown here:

Router# show interfaces dialer0 

Dialer0 is up, line protocol is up 

  Hardware is Unknown

  Internet address is 10.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 the Dialer0 output, the show interfaces command is executed on each physical interface bound to it.

Example with BRI

In this 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 interfaces 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 analysis-module

To display status, traffic data, and configuration information about the analysis module interface, use the show interfaces analysis-module command in user EXEC or privileged EXEC mode.

show interfaces analysis-module slot/unit

Syntax Description

slot	Number of the router chassis slot for the network module.
/unit	Number of the daughter card on the network analysis module (NAM). For NAM, always use 0.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
12.3(4)XD	This command was introduced on the following platforms: Cisco 2600XM series, Cisco 2691, Cisco 3660, Cisco 3725, and Cisco 3745.
12.3(7)T	This command was integrated into Cisco IOS Release 12.3(7)T.
12.3(8)T4	This command was implemented on the following platforms: Cisco 2811, Cisco 2821, and Cisco 2851.
12.3(11)T	This command was implemented on the Cisco 3800 series.

Usage Guidelines

The analysis module interface is a Fast Ethernet interface on the router that connects to the internal interface on the Network Analysis Module (NM-NAM).

Examples

The command in the following example displays status, traffic data, and configuration information about the analysis module interface when the NM-NAM is installed in slot 2 of a Cisco 3745.

Router# show interfaces analysis-module 2/0 

Network-Analyzer2/0 is up, line protocol is up

  Hardware is I82559FE, address is 0001.a535.0920 (bia 0001.a535.0920)

  Internet address is 10.1.1.1/24

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 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:00, output hang never

  Last clearing of "show interface" counters never

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

  Queueing strategy: fifo

  Output queue: 0/60 (size/max)

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

  5 minute output rate 36000 bits/sec, 22 packets/sec

     905 packets input, 38190 bytes, 0 no buffer

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

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

     0 input packets with dribble condition detected

     671863 packets output, 96101624 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Table 51 describes the significant fields shown in the display.

Table 51 show interfaces analysis-module Field Descriptions 

Field	Description
Network-Analyzer	Indicates whether the analysis module interface hardware is currently active. The analysis module interface is the router-side interface for the internal Ethernet segment between the router and the NAM network module. If the analysis module interface hardware is operational, the output states that the "Network-Analyzer 1/0 is up." If the interface has been taken down by an administrator, the output states that the "Network-Analyzer 1/0 is administratively down."
line protocol is	Indicates whether the software processes that handle the line protocol consider the line usable or whether the line has been taken down by an administrator.
Hardware is...address is	Hardware type and address.
MTU	Maximum transmission unit (MTU) of the analysis module interface.
BW	Bandwidth of the interface, in kbps.
DLY	Delay of the interface, in microseconds.
reliability	Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
txload	Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
rxload	Receive 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 the interface.
loopback	Indicates whether or not loopback is set.
Keepalive	Indicates whether or not keepalives are set and the interval between keepalives if they have been set.
ARP type...ARP Timeout	Type of Address Resolution Protocol (ARP) assigned and length of timeout.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by the interface and processed locally on the router. This field is useful for detecting when a dead interface failed. Note This field is not updated by fast-switched traffic.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. This field is useful for detecting when a dead interface failed.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because a transmission 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. Asterisks (***) indicate that the elapsed time is too large to be displayed.
Input queue	Number of packets in the input queue. Each number is followed by a slash, the maximum size of the queue, the number of packets dropped because of a full queue, and the number of times that queued packets have been discarded.
Total output drops	Number of packets in the output queue that have been dropped because of a full queue.
Queueing strategy	Queueing strategy applied to the interface, which is configurable under the interface. The default is FIFO (first-in, first-out).
Output queue	Number of packets in the output queue, and the maximum size of the queue. Each number is followed by a slash.
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 that 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 2 percent of the instantaneous rate of a uniform stream of traffic over that period. Note The 5-minute period referenced in this output is a load interval that is configurable under the interface. The default value is 5 minutes.
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	Number of broadcasts received.
runts	Number of packets that are discarded because they are smaller than the minimum packet size of the medium. 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 maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
throttles	Number of times that the interface requested another interface within the router to slow down.
input errors	Errors that include runts, giants, no buffer, cyclic redundancy checksum (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	Errors created when the CRC 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 that is 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.
overrun	Number of times that 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 that were ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from system buffer space described. Broadcast storms and bursts of noise can cause the ignored count to increase.
input packets with dribble condition detected	Number of packets with dribble condition. 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 that have been transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, that have been transmitted by the system.
underruns	Number of times that the transmitter has run faster than the router could 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 that is being examined. Note that 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.
collisions	Number of messages that have been retransmitted because of 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 that were 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.
babbles	Count of frames greater than 1518 bytes that have been transmitted, indicating that the transmitter has been on the interface longer than the time necessary to transmit the largest frame.
late collision	Number of late collisions. A collision becomes a late collision when it occurs after the preamble has been transmitted.
deferred	Deferred indicates that the chip, while ready to transmit a frame, had to defer because the carrier was asserted.
lost carrier	Number of times that the carrier was lost during transmission.
no carrier	Number of times that the carrier was not present during the transmission.
output buffer failures, output buffers swapped out	Number of failed buffers and number of buffers swapped out.

Related Commands

Command	Description
show controllers analysis-module	Displays controller information for the analysis module interface.

show interfaces content-engine

To display basic interface configuration information for a content engine (CE) network module, use the show interfaces content-engine command in privileged EXEC mode.

show interfaces content-engine slot/unit

Syntax Description

slot	Number of the router chassis slot for the network module.
unit	Number of the daughter card on the network module. For CE network modules, always use 0.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(11)YT	This command was introduced.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

The output for this command contains the basic configuration for the interface, as well as the number of packets transmitted, output rate, and so forth.

Examples

The following example displays interface status and data for the CE network module in slot 1 for Cisco 2600 series routers (except the Cisco 2691). Note that the bandwidth is 10 Mbps.

Router# show interfaces content-engine 1/0

Content-Engine1/0 is up, line protocol is up 

  Hardware is I82559FE, address is 0006.280e.10b0 (bia 0006.280e.10b0)

  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

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

  Last input 00:00:50, output 00:00:04, output hang never

  Last clearing of "show interface" counters never

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

  Queueing strategy: fifo

  Output queue :0/40 (size/max)

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

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

     13 packets input, 5835 bytes, 0 no buffer

     Received 13 broadcasts, 0 runts, 0 giants, 0 throttles

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

     0 input packets with dribble condition detected

     71 packets output, 6285 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 buffer failures, 0 output buffers swapped out

The following example displays interface status and data for a CE network module in slot 3 of a Cisco 2691. This example shows the 100-Mbps bandwidth of a Cisco 2691 and all the other supported routers except the remainder of the Cisco 2600 series.

Router# show interfaces content-engine 3/0

Content-Engine3/0 is up, line protocol is up 

  Hardware is I82559FE, address is 0004.9a0b.4b30 (bia 0004.9a0b.4b30)

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, 

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

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

  Last input 00:00:41, output 00:00:04, output hang never

  Last clearing of "show interface" counters never

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

  Queueing strategy: fifo

  Output queue :0/40 (size/max)

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

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

     14 packets input, 6176 bytes, 0 no buffer

     Received 14 broadcasts, 0 runts, 0 giants, 0 throttles

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

     0 input packets with dribble condition detected

     109 packets output, 16881 bytes, 0 underruns

     0 output errors, 0 collisions, 1 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Table 52 describes the significant fields shown in the display.

Table 52 show interfaces content-engine Field Descriptions 

Field	Description
Content-Engine	Indicates whether the CE interface hardware is currently active. If the CE interface hardware is operational, the output states that "Content-Engine slot/port is up." If it has been taken down by an administrator, the output states that "Content-Engine slot/port is administratively down."
line protocol	Indicates whether the software processes that handle the line protocol consider the line usable or whether the line has been taken down by an administrator.
Hardware...address	Hardware type and address.
MTU	Maximum transmission unit (MTU) of the content engine interface.
BW	Bandwidth of the interface, in kilobits per second.
DLY	Delay of the interface, in microseconds.
reliability	Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
txload	Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
rxload	Receive 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 the interface.
loopback	Indicates whether loopback is set.
Keepalive	Indicates whether keepalives are set and the interval between keepalives if they have been set.
ARP type...Timeout	Type of Address Resolution Protocol (ARP) assigned and length of timeout.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by the interface and processed locally on the router. This field is useful for detecting when a dead interface failed. Note This field is not updated by fast-switched traffic.
output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. This field is useful for detecting when a dead interface failed.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because a transmission 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. Asterisks (***) indicate that the elapsed time is too large to be displayed. A time of all zeroes (0:00:00) indicates that the counters were cleared more than 231 ms (and less than 232 ms) ago.
Input queue	Number of packets in the input queue. Each number is followed by a slash, the maximum size of the queue, the number of packets dropped because of a full queue, and the number of times that queued packets have been discarded.
Total output drops	Number of packets in the output queue that have been dropped because of a full queue.
Queueing strategy	Queueing strategy applied to the inter