Cisco IOS Interface and Hardware Component Command Reference
show hw-module slot tech-support through show interfaces vg-anylan

Table Of Contents

show hw-module slot tech-support

show hw-module subslot

show hw-module subslot fpd

show hw-module subslot oir

show hw-module subslot service-engine status

show hw-module subslot transceiver

show icc

show interface sdcc

show interfaces

show interfaces accounting

show interfaces analysis-module

show interfaces capabilities

show interfaces content-engine

show interfaces counters nonzero

show interfaces ctunnel

show interfaces debounce

show interfaces description

show interfaces ethernet

show interfaces fastethernet

show interfaces fddi

show interfaces flowcontrol

show interfaces gigabitethernet

show interfaces hssi

show interfaces integrated-service-engine

show interfaces ism

show interfaces lex

show interfaces loopback

show interfaces port-channel

show interfaces port-channel etherchannel

show interfaces pos

show interfaces private-vlan mapping

show interfaces satellite

show interfaces serial

show interfaces sm

show interfaces status

show interfaces summary

show interfaces switchport

show interfaces switchport backup

show interfaces tokenring

show interfaces transceiver

show interfaces trunk

show interfaces tunnel

show interfaces unidirectional

show interfaces vg-anylan


show hw-module slot tech-support

To display system information for a SPA interface processor (SIP) or other module to troubleshoot a problem, use the show hw-module slot tech-support command in privileged EXEC configuration mode.

show hw-module slot slot tech-support [cpu {0 | 1}]

Syntax Description

slot

Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

cpu {0 | 1}

(Optional) Number of the CPU (0 or 1) for which you want to display data.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(18)SXE

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Usage Guidelines

Use the show hw-module slot tech-support command to gather information about the SIP or other module to troubleshoot a problem. Certain error messages request that you gather this information and have it available when reporting a problem to Cisco Systems technical support personnel.

The show hw-module slot tech-support command runs a collection of different show commands to gather information about your system environment and configuration.

The number of CPUs available varies by the type of SIP. Although the Cisco 7600 SIP-200 has two CPUs, you can display alignment data for the first CPU (CPU 0) only.

Examples

The following example shows system information for the SIP installed in slot 5 of the router:

Router# show hw-module slot 5 tech-support

------------------ show version ------------------

Cisco Internetwork Operating System Software 
IOS (tm) cwlc Software (sip2-DW-M), Version 12.2(PIKESPEAK_INTEG_041013) INTERIM SOFTWARE
Synced to V122_18_S6, 12.2(18)S6 on v122_18_s_throttle, Weekly 12.2(18.6.4)SX
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Wed 13-Oct-04 06:55 by kchristi
Image text-base: 0x40010FC0, data-base: 0x40680000

ROM: System Bootstrap, Version 12.2(20040716:151531) [tawei-pike1 1.1dev(0.1)] DEVELOPMENT 
SOFTWARE
ROM: cwlc Software (sip2-DW-M), Version 12.2(PIKESPEAK_INTEG_041013) INTERIM SOFTWARE

SIP-400-5 uptime is 19 hours, 38 minutes
System returned to ROM by power-on
Running default software

cisco CWAN Modular Service Card (SIP-400) (SB-1) processor with 245760K/16383K bytes of 
memory.
SB-1 CPU at 400Mhz, Implementation 0x401, Rev 0.3, 256KB L2 Cache
Last reset from power-on
4 ATM network interface(s)

Configuration register is 0x0


------------------ show running-config ------------------


Building configuration...

Current configuration : 13 bytes
!
!
!
!
end


------------------ show stacks ------------------


Minimum process stacks:
 Free/Size   Name
 5080/6000   SCP Find Master process
 8448/12000  Init
 5528/6000   IPC Zone Manager
 5264/6000   SCP Hybrid Registration process
 4616/6000   IPC delayed init
 5056/6000   SIP2 FPD Process
 8120/12000  Exec
 6920/12000  console_rpc_server_action
 7536/12000  RFSS_server_action

Interrupt level stacks:
Level    Called Unused/Size  Name
  1           1   7896/9000  Level 1 Interrupt
  2      116555   6136/9000  Level 2 Interrupt
  3         289   7760/9000  Level 3 Interrupt
  4       24915   8392/9000  Level 4 Interrupt
  5          67   8424/9000  Level 5 Interrupt
  7    17683668   8568/9000  NMI Interrupt Handler

------------------ show interfaces ------------------


ATM5/0/0 is administratively down, line protocol is down 
  Hardware is SPA-4XOC3-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 0, BW 149760 Kbit, DLY 0 usec, 
     reliability 0/255, txload 1/255, rxload 1/255
  Encapsulation ATM, loopback not set
  Last input never, output never, 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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
ATM5/0/1 is administratively down, line protocol is down 
  Hardware is SPA-4XOC3-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 0, BW 149760 Kbit, DLY 0 usec, 
     reliability 0/255, txload 1/255, rxload 1/255
  Encapsulation ATM, loopback not set
  Last input never, output never, 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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
ATM5/0/2 is administratively down, line protocol is down 
  Hardware is SPA-4XOC3-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 0, BW 149760 Kbit, DLY 0 usec, 
     reliability 0/255, txload 1/255, rxload 1/255
  Encapsulation ATM, loopback not set
  Last input never, output never, 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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
ATM5/0/3 is administratively down, line protocol is down 
  Hardware is SPA-4XOC3-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 0, BW 149760 Kbit, DLY 0 usec, 
     reliability 0/255, txload 1/255, rxload 1/255
  Encapsulation ATM, loopback not set
  Last input never, output never, 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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out

------------------ show controllers ------------------

Shared Port Adapter SPA-4XOC3-ATM[5/0]
 4xOC3 ATM SPA revision 1
SAR is Azanda Katana SAR/TM, rev B, manf_id 0x1B2, base 0xB8300000
 object     0x43D9DF90, port      0x43A332E8, list_elems 0x43A3C7D0
 hash_tbl   0x41EEF0A0, vc_tbl    0x4276C2F0, fid_tbl    0x441145A0
 shp_prof   0x42996990
 vc_count 0/16384 (curr/max), fid_count 12/65536 (curr/max), max_bids 1048576 
 Device level stats:
  s4p3_abort                 0  s4p3_pty_errs              0
  cor_ecc_errs               0  lut_pty_errs               0
  uncor_ecc_errs             0  hdrap_pty_errs             0
  mem_bad_errs               0
  pfq2mem_rels               0  null_rel                   0
  mem2pfq_rels               0  null_dq                    0
  mem_nq                     0  pre_pfq_drops              0
  dbs_dq_cnt                 0  post_pfq_drops             0
  no_fid_drops               0  tot_free_bufs        1048575
  bid_nulls                  0  bufs_inuse                 0
  sch_cells                  0  sch_cells_out              0
  sch_blocked                0  sch_eop                    0
  sch_empty                  0  cbwfq_merge_in             0
  cbwfq_merge_out            0
Backpressure status:
 SEG input FIFO: not full
             LUT    RAS    PFQ    DBS
            lo hi  lo hi  lo hi  lo hi
 Port 0 RX  -  -   -  -   -  -   -  -
 Port 0 TX  -  -   -  -   -  -   -  -
 Port 1 RX  -  -   -  -   -  -   -  -
 Port 1 TX  -  -   -  -   -  -   -  -
 Port 2 RX  -  -   -  -   -  -   -  -
 Port 2 TX  1  1   -  -   -  -   -  -
 Port 3 RX  -  -   -  -   -  -   -  -
 Port 3 TX  1  1   -  -   -  -   -  -
 Port 0 Stats:
  rx_paks                    0  tx_paks                    0
  rx_cells                   0  tx_cells                   0
  rx_bytes                   0  tx_bytes                   0
  pm_rx_paks                 0  pm_tx_paks                 0
  pm_rx_bytes                0  pm_tx_bytes                0
  rx_wred_tail_dr            0  tx_wred_tail_dr            0
  rx_wred_prob_dr            0  tx_wred_prob_dr            0
  rx_buf_thr_lo          62260  tx_buf_thr_lo         186778
  rx_bufs_inuse_l            0  tx_bufs_inuse_l            0
  rx_buf_thr_hi           3276  tx_buf_thr_hi           9830
  rx_bufs_inuse_h            0  tx_bufs_inuse_h            0
  rx_crc32_errs              0  rx_crc10_errs              0
  rx_no_vcd                  0
 Port 1 Stats:
  rx_paks                    0  tx_paks                    0
  rx_cells                   0  tx_cells                   0
  rx_bytes                   0  tx_bytes                   0
  pm_rx_paks                 0  pm_tx_paks                 0
  pm_rx_bytes                0  pm_tx_bytes                0
  rx_wred_tail_dr            0  tx_wred_tail_dr            0
  rx_wred_prob_dr            0  tx_wred_prob_dr            0
  rx_buf_thr_lo          62260  tx_buf_thr_lo         186778
  rx_bufs_inuse_l            0  tx_bufs_inuse_l            0
  rx_buf_thr_hi           3276  tx_buf_thr_hi           9830
  rx_bufs_inuse_h            0  tx_bufs_inuse_h            0
  rx_crc32_errs              0  rx_crc10_errs              0
  rx_no_vcd                  0
 Port 2 Stats:
  rx_paks                    0  tx_paks                    0
  rx_cells                   0  tx_cells                   0
  rx_bytes                   0  tx_bytes                   0
  pm_rx_paks                 0  pm_tx_paks                 0
  pm_rx_bytes                0  pm_tx_bytes                0
  rx_wred_tail_dr            0  tx_wred_tail_dr            0
  rx_wred_prob_dr            0  tx_wred_prob_dr            0
  rx_buf_thr_lo          62260  tx_buf_thr_lo         186778
  rx_bufs_inuse_l            0  tx_bufs_inuse_l            0
  rx_buf_thr_hi           3276  tx_buf_thr_hi           9830
  rx_bufs_inuse_h            0  tx_bufs_inuse_h            0
  rx_crc32_errs              0  rx_crc10_errs              0
  rx_no_vcd                  0
 Port 3 Stats:
  rx_paks                    0  tx_paks                    0
  rx_cells                   0  tx_cells                   0
  rx_bytes                   0  tx_bytes                   0
  pm_rx_paks                 0  pm_tx_paks                 0
  pm_rx_bytes                0  pm_tx_bytes                0
  rx_wred_tail_dr            0  tx_wred_tail_dr            0
  rx_wred_prob_dr            0  tx_wred_prob_dr            0
  rx_buf_thr_lo          62260  tx_buf_thr_lo         186778
  rx_bufs_inuse_l            0  tx_bufs_inuse_l            0
  rx_buf_thr_hi           3276  tx_buf_thr_hi           9830
  rx_bufs_inuse_h            0  tx_bufs_inuse_h            0
  rx_crc32_errs              0  rx_crc10_errs              0
  rx_no_vcd                  0
 Flow utilization summary
           blks  unsh  t_rt  t_lb  t_lf  rt_lf  shap  root  drain | Total
  # free : 24568 0     1023  8184  0     8191  15355 8191   0     | 65512
flow                 int     red dfl    queue size         sent          packet drops
 id   vcd  gqid use  prt dir pro clr curr  avg     max     paks    bufm  giant to/ab 
pl/crc
0001     0 0000 shap  1  tx   18  4      0     1   35940        0      0     0     0     0
0002     0 0000 shap  3  tx   18  4      0     1   35940        0      0     0     0     0
0003     0 0000 shap  5  tx   18  4      0     1   35940        0      0     0     0     0
0004     0 0000 shap  7  tx   18  4      0     1   35940        0      0     0     0     0
FFF8     0 0000 unsh 11  rx   18  4      0     1   35940        0      0     0     0     0
FFF9     0 0000 unsh 13  rx   18  4      0     1   35940        0      0     0     0     0
FFFA     0 0000 unsh 15  rx   18  4      0     1   35940        0      0     0     0     0
FFFB     0 0000 unsh 17  rx   18  4      0     1   35940        0      0     0     0     0
FFFC     0 0000 unsh 10  rx   21  0      0     1       0        0      0     0     0     0
FFFD     0 0000 unsh 12  rx   21  0      0     1       0        0      0     0     0     0
FFFE     0 0000 unsh 14  rx   21  0      0     1       0        0      0     0     0     0
FFFF     0 0000 unsh 16  rx   21  0      0     1       0        0      0     0     0     0
KATM FPGA: rev 0.90, base 0xB8000000, obj 0x42994748
            packets                cells                errors
port     rx         tx         rx         tx         rx         tx
 0           0          0          0          0          0          0
 1           0          0          0          0          0          0
 2           0          0          0          0          0          0
 3           0          0          0          0          0          0
PM5379 ATM Framer: Type:0, Rev:1, base 0xB8100000, obj 0x41EEA2B0
                    Cells                   CRC errs
port          rx               tx              rx
0             0                0               0
1             0                0               0
2             0                0               0
3             0                0               0

ATM5/0/0: 
        ID: SFP
        Extended ID: 4
        Xcvr Type: OC3 SR-1/STM1 MM (1)
        Connector: LC
        Vendor name: OCP             
        Product Identifier (PID): TRP-03BCS       
        State: Enabled

ATM5/0/0: 
Phased Initialization
        Phase Reached: 4
        Phase Exit Code: Success 0
        Phase Read Offset: 256

Socket Verification
        Compatibility: Compatibility passed
        Security: Security passed


------------------ show memory statistics ------------------


                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
Processor   4145B860   230311840   118715296   111596544   106212312    48534600
      I/O    F000000    16776736     3090304    13686432    13686432    13685880

------------------ show process memory ------------------


Total: 247088544, Used: 121805424, Free: 125283120
 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process
   0   0   17899632      57040   17017720          0          0 *Init*          
   0   0       1256     145000       1256          0          0 *Sched*         
   0   0          0          0          0          0          0 *Neutrino*      
   0   0    5233000    4617848     589152     606508          0 *Dead*          
   1   0          0          0       6968          0          0 Chunk Manager   
   2   0        192        192       3960          0          0 Load Meter      
   3   0          0          0       6960          0          0 SCP async: CWAN-
   4   0          0          0       6960          0          0 Check heaps     
   5   0      25984     169280       9584      15748      51748 Pool Manager    
   6   0        192        192       6960          0          0 Timers          
   7   0          0          0       6976          0          0 AAA_SERVER_DEADT
   8   0        192        192       6968          0          0 AAA high-capacit
   9   0        192        192       6960          0          0 Serial Backgroun
  10   0          0          0       6960          0          0 ENVM Background 
  11   0          0          0       6960          0          0 IPC Dynamic Cach
  12   0     145256        384      23968      31200          0 PROCMIB LC Proce
  13   0          0          0       6960          0          0 IPC BackPressure
  14   0       7040          0       6960          0          0 IPC Periodic Tim
  15   0          0          0       6968          0          0 IPC Deferred Por
  16   0     123536        352      25416      12756          0 IPC Seat Manager
  17   0          0          0       6960          0          0 SERIAL A'detect 
  18   0     992944     993024       6960          0          0 SMART           
  19   0          0          0       6960          0          0 Critical Bkgnd  
  20   0      14080          0      13120          0          0 Net Background  
  21   0        192        192      12960          0          0 Logger          
  22   0      26384        448       9960          0          0 TTY Background  
  23   0          0          0       6960          0          0 Per-Second Jobs 
  24   0          0          0       6960          0          0 Per-minute Jobs 
  25   0          0        152       6960          0          0 SCP Multicast   
  26   0          0          0       3960          0          0 Inode Table Dest
  27   0          0          0       6976          0          0 LC to RP  defere
  28   0        192        192       6960          0          0 CWLC IFCOM Proce
  29   0          0          0       6968          0          0 IPC RTTYC Messag
  30   0        192        192      12960          0          0 INTR MGR PROCESS
  31   0          0          0       6960          0          0 ixp_exmem_reuse_
  32   0      14456      14296       7120          0          0 spnpc_dowork    
  33   0          0          0       6960          0          0 Spi4 Timer      
  34   0          0          0       6968          0          0 LC interrupt, J1
  35   0          0          0       6976          0          0 SIP interrupt, P
  36   0          0          0      12960          0          0 SDCC Input      
  37   0        192        192      12960          0          0 SDCC Periodic   
  38   0        192        192      12960          0          0 SDCC IO         
  39   0          0          0       6960          0          0 CWAN LTL manager
  40   0          0          0       6960          0          0 msg_handler_proc
  41   0    2620112    2620112       6960          0          0 Cardmgr Periodic
  42   0          0          0       6960          0          0 SIP SWBus Sync P
  43   0          0          0       6960          0          0 NP doorbell proc
  44   0      10432       5344       6960       2268          0 CardMgr Events  
  45   0    1905448       3592    1787560          0          0 INP Reload      
  46   0          0          0       6960          0          0 ipc_handler_proc
  47   0          0          0       6960          0          0 NP doorbell proc
  48   0    2270440       2328    2158576       2268          0 ENP Reload      
  49   0          0          0       6960          0          0 ipc_handler_proc
  50   0          0          0       6960          0          0 SIP2 Bus Stall  
  51   0 1504729392 1504768488     200528          0          0 ifnpc_dowork    
  52   0          0          0       6960          0          0 hmi_dowork      
  53   0       7000       7000       6960          0          0 cwanlc_npc_dowor
  54   0          0          0       6968          0          0 VIP Encap IPC Ba
  55   0  554366168  457784816   96580296      12756          0 SPA OIR 5/0     
  56   0          0          0      12960          0          0 SPA OIR 5/1     
  57   0          0          0      12960          0          0 SPA OIR 5/2     
  58   0          0          0      12960          0          0 SPA OIR 5/3     
  59   0   27281752   27281752       6960          0          0 LC FPD Upgrade P
  60   0          0          0       6960          0          0 spa_env_monitor 
  61   0        192        192       6960          0          0 AAA Dictionary R
  62   0        192        192       6960          0          0 AAA Server      
  63   0          0          0       6960          0          0 AAA ACCT Proc   
  64   0          0          0       6960          0          0 ACCT Periodic Pr
  65   0        192        192       6960          0          0 ATMLS task      
  66   0          0          0       6968          0          0 AToM NP CLIENT B
  67   0          0          0       6968          0          0 TTFIB NP CLIENT 
  68   0          0          0       6960          0          0 SSA FABLINK Proc
  69   0          0          0       6968          0          0 HYP ACCU FAB COU
  70   0     327264          0     327264          0          0 CEF process     
  71   0        192        192       6960          0          0 CWTLC SSO Proces
  72   0        192        192       6960          0          0 SCP Hybrid proce
  73   0          0          0      12960          0          0 ATM NP CLIENT PR
  74   0          0          0      12968          0          0 BRIDGING NP CLIE
  75   0          0          0       6960          0          0 fr_npc_dowork   
  76   0        192        192       6968          0          0 fastblk backgrou
  77   0          0          0       6960          0          0 hnpc_dowork     
  78   0          0          0      12968          0          0 SIP2 BRIDGE PROC
  79   0        192        192      12960          0          0 QoS NP Client   
  80   0    2355016    1220392    2338776      12756          0 CEF LC IPC Backg
  81   0  112519984  111381200      72720          0          0 CEF LC Stats    
  82   0          0          0       6960          0          0 CEF MQC IPC Back
  83   0          0          0       6960          0          0 TFIB LC cleanup 
  84   0        192        192       6984          0          0 Any Transport ov
  85   0        192        192       6960          0          0 LOCAL AAA       
  86   0        192        192       6960          0          0 AAA Cached Serve
  87   0        192        192       6960          0          0 RADIUS TEST CMD 
  88   0        192        192       6960          0          0 AAA SEND STOP EV
  89   0        168          0       7128          0          0 CEF Scanner     
  90   0          0          0       6968          0          0 SIP ATM cmd hand
  91   0          0          0       6968          0          0 SONET alarm time
  92   0          0          0       6960          0          0 Net Input       
  93   0        192        192       6960          0          0 Compute load avg
  94   1      90632      89968      18392          0          0 console_rpc_serv
                                121804560 Total

------------------ show process cpu ------------------


CPU utilization for five seconds: 2%/0%; one minute: 2%; five minutes: 2%
 PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process 
   1           0         1          0  0.00%  0.00%  0.00%   0 Chunk Manager    
   2           4     14151          0  0.00%  0.00%  0.00%   0 Load Meter       
   3           0         1          0  0.00%  0.00%  0.00%   0 SCP async: CWAN- 
   4        9816      7180       1367  0.16%  0.01%  0.00%   0 Check heaps      
   5           0        23          0  0.00%  0.00%  0.00%   0 Pool Manager     
   6           0         2          0  0.00%  0.00%  0.00%   0 Timers           
   7           0         1          0  0.00%  0.00%  0.00%   0 AAA_SERVER_DEADT 
   8           0         2          0  0.00%  0.00%  0.00%   0 AAA high-capacit 
   9           0         2          0  0.00%  0.00%  0.00%   0 Serial Backgroun 
  10         840     14179         59  0.00%  0.00%  0.00%   0 ENVM Background  
  11           0      1180          0  0.00%  0.00%  0.00%   0 IPC Dynamic Cach 
  12          72      1182         60  0.00%  0.00%  0.00%   0 PROCMIB LC Proce 
  13           0         1          0  0.00%  0.00%  0.00%   0 IPC BackPressure 
  14          36     70728          0  0.00%  0.00%  0.00%   0 IPC Periodic Tim 
  15          44     70728          0  0.00%  0.00%  0.00%   0 IPC Deferred Por 
  16          12        19        631  0.00%  0.00%  0.00%   0 IPC Seat Manager 
  17           0         1          0  0.00%  0.00%  0.00%   0 SERIAL A'detect  
  18        2956        38      77789  0.00%  0.00%  0.00%   0 SMART            
  19           0         1          0  0.00%  0.00%  0.00%   0 Critical Bkgnd   
  20          36     14355          2  0.00%  0.00%  0.00%   0 Net Background   
  21           0        61          0  0.00%  0.00%  0.00%   0 Logger           
  22         240     70728          3  0.00%  0.00%  0.00%   0 TTY Background   
  23     1387988    138571      10016  2.04%  1.01%  1.04%   0 Per-Second Jobs  
  24        4808      1218       3947  0.00%  0.01%  0.00%   0 Per-minute Jobs  
  25           0         2          0  0.00%  0.00%  0.00%   0 SCP Multicast    
  26           0         1          0  0.00%  0.00%  0.00%   0 Inode Table Dest 
  27           0         3          0  0.00%  0.00%  0.00%   0 LC to RP  defere 
  28           0        26          0  0.00%  0.00%  0.00%   0 CWLC IFCOM Proce 
  29           0         1          0  0.00%  0.00%  0.00%   0 IPC RTTYC Messag 
  30           0         2          0  0.00%  0.00%  0.00%   0 INTR MGR PROCESS 
  31           0        11          0  0.00%  0.00%  0.00%   0 ixp_exmem_reuse_ 
  32           4        62         64  0.00%  0.00%  0.00%   0 spnpc_dowork     
  33           0         1          0  0.00%  0.00%  0.00%   0 Spi4 Timer       
  34           0         1          0  0.00%  0.00%  0.00%   0 LC interrupt, J1 
  35           0         1          0  0.00%  0.00%  0.00%   0 SIP interrupt, P 
  36           0         1          0  0.00%  0.00%  0.00%   0 SDCC Input       
  37           0         2          0  0.00%  0.00%  0.00%   0 SDCC Periodic    
  38           0         2          0  0.00%  0.00%  0.00%   0 SDCC IO          
  39           0         1          0  0.00%  0.00%  0.00%   0 CWAN LTL manager 
  40        1208     14154         85  0.00%  0.00%  0.00%   0 msg_handler_proc 
  41         148     70730          2  0.00%  0.00%  0.00%   0 Cardmgr Periodic 
  42           0         6          0  0.00%  0.00%  0.00%   0 SIP SWBus Sync P 
  43           0         5          0  0.00%  0.00%  0.00%   0 NP doorbell proc 
  44           0         5          0  0.00%  0.00%  0.00%   0 CardMgr Events   
  45        1400        26      53846  0.00%  0.00%  0.00%   0 INP Reload       
  46           0       379          0  0.00%  0.00%  0.00%   0 ipc_handler_proc 
  47           0         5          0  0.00%  0.00%  0.00%   0 NP doorbell proc 
  48        2224        25      88960  0.00%  0.00%  0.00%   0 ENP Reload       
  49          16      1200         13  0.00%  0.00%  0.00%   0 ipc_handler_proc 
  50           0         1          0  0.00%  0.00%  0.00%   0 SIP2 Bus Stall   
  51      214912     53129       4045  0.00%  0.00%  0.00%   0 ifnpc_dowork     
  52           0         4          0  0.00%  0.00%  0.00%   0 hmi_dowork       
  53           0        31          0  0.00%  0.00%  0.00%   0 cwanlc_npc_dowor 
  54           0         1          0  0.00%  0.00%  0.00%   0 VIP Encap IPC Ba 
  55       18532    487255         38  0.00%  0.00%  0.00%   0 SPA OIR 5/0      
  56          84      2372         35  0.00%  0.00%  0.00%   0 SPA OIR 5/1      
  57          80      2368         33  0.00%  0.00%  0.00%   0 SPA OIR 5/2      
  58          84      2368         35  0.00%  0.00%  0.00%   0 SPA OIR 5/3      
  59        2432        32      76000  0.00%  0.00%  0.00%   0 LC FPD Upgrade P 
  60        3112    138447         22  0.00%  0.00%  0.00%   0 spa_env_monitor  
  61           0         2          0  0.00%  0.00%  0.00%   0 AAA Dictionary R 
  62           0         2          0  0.00%  0.00%  0.00%   0 AAA Server       
  63           0         1          0  0.00%  0.00%  0.00%   0 AAA ACCT Proc    
  64           0         1          0  0.00%  0.00%  0.00%   0 ACCT Periodic Pr 
  65           0         2          0  0.00%  0.00%  0.00%   0 ATMLS task       
  66           0      7185          0  0.00%  0.00%  0.00%   0 AToM NP CLIENT B 
  67          16      7185          2  0.00%  0.00%  0.00%   0 TTFIB NP CLIENT  
  68           8    707134          0  0.00%  0.00%  0.00%   0 SSA FABLINK Proc 
  69           0     14150          0  0.00%  0.00%  0.00%   0 HYP ACCU FAB COU 
  70        7140    103916         68  0.00%  0.00%  0.00%   0 CEF process      
  71           0         2          0  0.00%  0.00%  0.00%   0 CWTLC SSO Proces 
  72         328      4423         74  0.00%  0.00%  0.00%   0 SCP Hybrid proce 
  73           4     77777          0  0.00%  0.00%  0.00%   0 ATM NP CLIENT PR 
  74         324     70733          4  0.00%  0.00%  0.00%   0 BRIDGING NP CLIE 
  75          12      7182          1  0.00%  0.00%  0.00%   0 fr_npc_dowork    
  76           4    707140          0  0.00%  0.00%  0.00%   0 fastblk backgrou 
  77          40         2      20000  0.00%  0.00%  0.00%   0 hnpc_dowork      
  78           0         1          0  0.00%  0.00%  0.00%   0 SIP2 BRIDGE PROC 
  79         416      7079         58  0.00%  0.00%  0.00%   0 QoS NP Client    
  80        3300    726380          4  0.00%  0.00%  0.00%   0 CEF LC IPC Backg 
  81         628     93426          6  0.00%  0.00%  0.00%   0 CEF LC Stats     
  82           0         1          0  0.00%  0.00%  0.00%   0 CEF MQC IPC Back 
  83           0         1          0  0.00%  0.00%  0.00%   0 TFIB LC cleanup  
  84           0         2          0  0.00%  0.00%  0.00%   0 Any Transport ov 
  85           0         2          0  0.00%  0.00%  0.00%   0 LOCAL AAA        
  86           0         2          0  0.00%  0.00%  0.00%   0 AAA Cached Serve 
  87           0         3          0  0.00%  0.00%  0.00%   0 RADIUS TEST CMD  
  88           0         2          0  0.00%  0.00%  0.00%   0 AAA SEND STOP EV 
  89         128      5003         25  0.00%  0.00%  0.00%   0 CEF Scanner      
  90           0         1          0  0.00%  0.00%  0.00%   0 SIP ATM cmd hand 
  91           0         1          0  0.00%  0.00%  0.00%   0 SONET alarm time 
  92           0         1          0  0.00%  0.00%  0.00%   0 Net Input        
  93          16     14775          1  0.00%  0.00%  0.00%   0 Compute load avg 
  94          92       502        183  0.00%  0.09%  0.02%   1 console_rpc_serv

------------------ show process cpu history ------------------

     2222222223333322222222222222222222111112222222222222222222
100                                                            
 90                                                            
 80                                                            
 70                                                            
 60                                                            
 50                                                            
 40                                                            
 30                                                            
 20                                                            
 10                                                            
    0....5....1....1....2....2....3....3....4....4....5....5....
              0    5    0    5    0    5    0    5    0    5    

               CPU% per second (last 60 seconds)

                1           1 1  1                             
     2222222222332222222222242432432222222222222222222222222222
100                                                            
 90                                                            
 80                                                            
 70                                                            
 60                                                            
 50                                                            
 40                                                            
 30                                                            
 20                                                            
 10             *           * *  *                             
    0....5....1....1....2....2....3....3....4....4....5....5....
              0    5    0    5    0    5    0    5    0    5    

               CPU% per minute (last 60 minutes)
              * = maximum CPU%   # = average CPU%

     1                 9                                                   
     4222222222222222229                                                   
100                    *                                                   
 90                    *                                                   
 80                    *                                                   
 70                    *                                                   
 60                    *                                                   
 50                    *                                                   
 40                    *                                                   
 30                    *                                                   
 20                    *                                                   
 10  *                 *                                                   
    0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
              0    5    0    5    0    5    0    5    0    5    0    5    0 

                   CPU% per hour (last 72 hours)
                  * = maximum CPU%   # = average CPU%



------------------ show file systems ------------------


File Systems:

     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -    opaque     rw   system:
           -           -    opaque     rw   null:
           -           -    opaque     ro   tar:
*   64097280    40606720      disk     rw   disk0:


------------------ show disk0: all ------------------

-#- --length-- -----date/time------ path

 number of file 8

 inode path is 1 idprom-oc12-atm-superspa 

 fullpath is disk0:/idprom-oc12-atm-superspa 
1         1152 Jun 09 2004 13:03:38 idprom-oc12-atm-superspa

 inode path is 2 idprom-4oc3-atm-superspa 

 fullpath is disk0:/idprom-4oc3-atm-superspa 
2         1152 Jun 09 2004 05:51:34 idprom-4oc3-atm-superspa

 inode path is 3 bonham_brd_rev2_rev19.hex 

 fullpath is disk0:/bonham_brd_rev2_rev19.hex 
3      2626407 Aug 24 2004 11:04:42 bonham_brd_rev2_rev19.hex

 inode path is 4 sip2-dw-mz.b2-testt 

 fullpath is disk0:/sip2-dw-mz.b2-testt 
4      5895640 Aug 26 2004 05:09:08 sip2-dw-mz.b2-testt

 inode path is 5 sip2-dw-mz.hp-depth 

 fullpath is disk0:/sip2-dw-mz.hp-depth 
5      5897476 Aug 12 2004 04:40:38 sip2-dw-mz.hp-depth

 inode path is 6 viking1.jbc 

 fullpath is disk0:/viking1.jbc 
6      2678150 Jun 09 2004 12:48:32 viking1.jbc

 inode path is 7 sip2-dw-mz.hpd 

 fullpath is disk0:/sip2-dw-mz.hpd 
7      5916716 Aug 25 2004 10:25:14 sip2-dw-mz.hpd

 inode path is 8 sip2iofpga_promlatest_rev78.hex 

 fullpath is disk0:/sip2iofpga_promlatest_rev78.hex 
8       468975 Aug 24 2004 10:56:54 sip2iofpga_promlatest_rev78.hex

40606720 bytes available (23490560 bytes used)

******** ATA Flash Card Geometry/Format Info ********

ATA CARD GEOMETRY
   Number of Heads:       4     
   Number of Cylinders    984   
   Sectors per Cylinder   32    
   Sector Size            512   
   Total Sectors          125952

ATA CARD FORMAT
   Number of FAT Sectors  246   
   Sectors Per Cluster    2     
   Number of Clusters     62595 
   Number of Data Sectors 125817
   Base Root Sector       595   
   Base FAT Sector        103   
   Base Data Sector       627   


------------------ show scp status ------------------


Rx 29169,  Tx 29165,  Sap 3  scp_my_addr 0x4
Id Sap      Channel name    current/peak/retry/dropped/total  time(queue/process/ack)
-- ---- ------------------- --------------------------------  ----------------------
0  0    SCP Unsolicited:0       0/    2/    0/      0/ 4421      0/   0/  76
1  23   SCP async: CWAN-NMP     0/    0/    0/      0/    0      0/   0/   0

------------------ show inventory ------------------



------------------ show region ------------------


Region Manager:

      Start         End     Size(b)  Class  Media  Name
 0x0F000000  0x0FFFFDFF    16776704  Iomem  R/W    iomem
 0x40000000  0x4EFFFFFF   251658240  Local  R/W    main
 0x40010FC0  0x4067FFE7     6746152  IText  R/O    main:text
 0x40680000  0x40CE977F     6723456  IData  R/W    main:data
 0x40CE9780  0x4145B85F     7807200  IBss   R/W    main:bss
 0x4145B860  0x4EFFFFFF   230311840  Local  R/W    main:heap
 0x80000000  0x8EFFFFFF   251658240  Local  R/W    main:(main_k0)
 0xA0000000  0xAEFFFFFF   251658240  Local  R/W    main:(main_k1)



------------------ show buffers ------------------


Buffer elements:
     500 in free list (500 max allowed)
     595460 hits, 0 misses, 0 created

Public buffer pools:
Small buffers, 104 bytes (total 37, permanent 25, peak 39 @ 19:39:17):
     35 in free list (20 min, 60 max allowed)
     310581 hits, 48 misses, 110 trims, 122 created
     0 failures (0 no memory)
Middle buffers, 600 bytes (total 15, permanent 15, peak 21 @ 19:39:19):
     14 in free list (10 min, 30 max allowed)
     20386 hits, 2 misses, 6 trims, 6 created
     0 failures (0 no memory)
Big buffers, 1536 bytes (total 6, permanent 5, peak 8 @ 19:39:21):
     6 in free list (5 min, 10 max allowed)
     16375 hits, 1 misses, 11 trims, 12 created
     0 failures (0 no memory)
VeryBig buffers, 4520 bytes (total 50, permanent 50):
     50 in free list (40 min, 300 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
     0 failures (0 no memory)
Large buffers, 5024 bytes (total 0, permanent 0):
     0 in free list (0 min, 5 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
     0 failures (0 no memory)
Huge buffers, 18024 bytes (total 1, permanent 1):
     1 in free list (0 min, 2 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
     0 failures (0 no memory)

Interface buffer pools:
IPC buffers, 4096 bytes (total 85, permanent 16, peak 85 @ 00:00:36):
     12 in free list (10 min, 30 max allowed)
     251678 hits, 23 fallbacks, 0 trims, 69 created
     0 failures (0 no memory)

Header pools:
SDCC Packet Header buffers, 0 bytes (total 2048, permanent 2048):
     0 in free list (2048 min, 2048 max allowed)
     2048 hits, 0 misses
     2048 max cache size, 2048 in cache
     0 hits in cache, 0 misses in cache

Particle Clones:
     2048 clones, 0 hits, 0 misses

Public particle pools:
GLOBAL buffers, 512 bytes (total 862, permanent 862):
     0 in free list (0 min, 862 max allowed)
     862 hits, 0 misses
     862 max cache size, 862 in cache
     0 hits in cache, 0 misses in cache
COMM buffers, 512 bytes (total 32, permanent 32):
     0 in free list (0 min, 32 max allowed)
     32 hits, 0 misses
     32 max cache size, 32 in cache
     0 hits in cache, 0 misses in cache

Private particle pools:
SB-FIFO5/0/1 buffers, 512 bytes (total 1000, permanent 1000):
     0 in free list (0 min, 1000 max allowed)
     1000 hits, 0 fallbacks
     1000 max cache size, 744 in cache
     261 hits in cache, 0 misses in cache
     14 buffer threshold, 0 threshold transitions
EOBC0/0 buffers, 512 bytes (total 2000, permanent 2000):
     0 in free list (0 min, 2000 max allowed)
     2000 hits, 0 misses
     2000 max cache size, 1744 in cache
     79803 hits in cache, 0 misses in cache
     14 buffer threshold, 0 threshold transitions
Ingress ESF Engine buffers, 1028 bytes (total 21, permanent 21):
     0 in free list (21 min, 21 max allowed)
     21 hits, 0 misses
     21 max cache size, 0 in cache
     21 hits in cache, 0 misses in cache
Egress ESF Engine buffers, 1028 bytes (total 21, permanent 21):
     0 in free list (21 min, 21 max allowed)
     21 hits, 0 misses
     21 max cache size, 0 in cache
     21 hits in cache, 0 misses in cache



------------------ show platform hardware version ------------------


        Product Number: '7600-MSC-400'
        Baseboard Serial Number: 'SAD073101T6'
        Manufacturing Assembly Revision: 'A01'
        Baseboard Revision: 0.14
        Daughtercard Serial Number: ''
        CPU Manufacturer: 0x4 (Broadcom)
        CPU SOC Type: BCM1125H 400 Mhz rev 0x21 wafer 0x1
        CPU Revision: 0.3
        Super Santa Ana: 0x0
        PM PLD: 0x5
        IOFPGA version: 0x00051
               type:    0x0 format 0x2 loaded from Upgrade (C1) region
        ROMMON (major.minor.dev.build) = 1.1.0.1
        Bonham version: 0x019
               type:    rev2-or-higher-bb
        Gldfgr version: 0x10014
        Oddjob version: 0x10010
        Hyperion: 0x2
        Config PLD: 0x6
        Ingress ESF Engine          : Type 0.0 rev 0.2, 1400 MHz
                                      SRAM clocks: 140/200/200/200 MHz
                                      DRAM clock: 400 MHz
        Egress ESF Engine           : Type 0.0 rev 0.2, 1400 MHz
                                      SRAM clocks: 200/200/140/200 MHz
                                      DRAM clock: 400 MHz

------------------ show platform hardware iofpga ------------------


CPU base address:       0xB1000000
0000: type_and_version: 0x00000251
0004: global_intr_en:   0x100D1021
0008: global_intr_stat: 0x00000008
000C: reset_reason_reg: 0x00000001
0010: cpu_resets:       0x00000000
0014: device_reset:     0x00000040
0018: watchdog:         0x00003D96
001C: who_am_i:         0x00002200
0020: rommon_sel:       0x00000001
0024: led_reg:          0x0000001F
0028: iofpga_ctrl:      0x00000400
002C: earl_control:     0x0000000F
0030: iobus_intr_en:    0x0000000F
0034: iobus_intr_stat:  0x00000000
0038: iobus_deadman:    0x00000015
003C: iobus_last_addr:  0x00000000
0040: iobus_last_data:  0x00000000
0044: iobus_tran_stat:  0x00000000
0048: test_pins_reg:    0x00000000
0058: pld_jtag:         0xCAFEBABE

SIP2 base addr:   0xB1000400
0000: spa_ctrl:         0x00000923
0004: spa_intr_en:      0x7E07222F
0008: spa_intr_stat:    0x01000000
000C: spa_stat:         0x0000222C
0010: spabus_deadman:   0x0000002A
0014: spabus_tran_stat: 0x0800021C
0018: spabus_last_read: 0x00070001
001C: spabus_last_par:  0x00003531
0020: spa_test:         0xAB2B2B29
0024: spd_ctrl:         0x00000007
0028: scratchpad:       0x00000000
002C: ha_state:         0x00000001
0030: spa0_debounce:    0x0000000A
0034: spa1_debounce:    0x0000000A
0038: spa2_debounce:    0x0000000A
003C: spa3_debounce:    0x0000000A
0044: ha_sanity:        0x00000007
0040: spa_sonet_clk:    0x200AD500
0048: spa_sonet_clk_ie: 0x00000000
004C: spa_sonet_clk_is: 0x1FFFFFFC
0050: spa_sonet_clk_div[0]: 0x0000097E
0054: spa_sonet_clk_div[1]: 0x0000097E
0058: spa_sonet_clk_div[2]: 0x0000097E
005C: spa_sonet_clk_div[3]: 0x0000097E

show hw-module subslot

To display diagnostic information about internal hardware devices for a SPA, use the show hw-module subslot command in privileged EXEC configuration mode.

show hw-module subslot [slot/subslot] {brief | config | counters| errors| registers | status} device port

Syntax Description

slot

(Optional) Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot

(Optional) Secondary slot number on a SIP where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

{brief | config | counters | errors | registers | status}

Specifies the display of diagnostic and register information related to the following areas:

brief—Reserved for future.

config—Displays information related to configuration of the specified internal hardware device.

counters—Displays statistics related to the processing by the specified internal hardware device.

errors—Reserved for future.

registers—Displays register information for the specified internal hardware device.

status—Displays status information for the specified internal hardware device.

device

Specifies the internal hardware device or path on the SPA for which you want to display diagnostic information, including the field programmable gate array (FPGA) device, MAC device, PHY device, or System Packet Interface Level 4 (SPI4) path from the MSC to the FPGA device.

port

(Optional) Port or interface number.

Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(20)S2

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.


Usage Guidelines

Use the show hw-module subslot command to obtain diagnostic information about an interface on the SPA.

The counters keyword displays a subset of the statistics that are also provided by the show controllers fastethernet command for the specified SPA device.

Examples

The following examples provide sample output for several versions of the show hw-module subslot command for a 4-Port 10/100 Fast Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:

show hw-module subslot config fpga Example

show hw-module subslot config phy Example

show hw-module subslot counters fpga Example

show hw-module subslot status mac Example

show hw-module subslot status phy Example

show hw-module subslot config fpga Example

The following shows sample output from the show hw-module subslot config command for the FPGA device on the first interface (port 0):

Router# show hw-module subslot 4/0 config fpga 0

FPGA RX Config
  RX FIFO parity select is even
  RX CRC check is  enabled
  RX SHIM header insertion is  disabled
  RX Flow control is enabled
  RX CRC strip is  enabled
  RX TCAM LKUP is enabled
FPGA TX Config
  TX FIFO parity select is even
  TX CRC generation is enabled
  TX Padding is enabled

show hw-module subslot config phy Example

The following shows sample output from the show hw-module subslot config command for the PHY device on the first interface (port 0):

Router# show hw-module subslot 4/0 config phy 0

  PHY version: identifier1 = 0x141, identifier2 = 0xCD2
  PHY Configuration:
  control (reg 0) = 0x3100
    PHY state: not in reset, not powered down, not isoloated
    speed: 100 Mbps, duplex: full
    auto-negotiation enabled, loopback disabled, collision test disabled
  phy specific control (reg 16) = 0x78
    force link good: no
    MDI cross-over mode: automatic crossover
    Tx FIFO depth: +/- 16 bits, Rx FIFO depth: +/- 16 bits
    never assert CRS on transmit, energy detect: off
    enable extended distance: no, 125 clock: low
    MAC interface power: always up, SQE test: disabled
    polarity reversal: enabled, jabber function: enabled
  extended phy specific control (reg 20) = 0xCE2
    line loopback: disabled, detect lost lock: no, enabled RCLK
    master downshift counter: 4, slave downshift counter: 0
    default MAC interface speed: 1000 Mbps
    fiber auto-negotiation disabled
    add delay to RX_CLK for RXD outputs: yes
    add delay to GTX_CLK for TXD latching: yes
  auto-negotiation advertisement for 10/100 (reg 4) = 0xDE1
    10Base-Tx half-duplex: yes, full-duplex: yes
    100Base-Tx half-duplex: yes, full-duplex: yes
    pause frame support: yes, asymmetric pause: yes
    set remote fault bit: no, advertise next page: no

show hw-module subslot counters fpga Example

The following shows sample output from the show hw-module subslot counters command for the FPGA device on the first interface (port 0):


Note This information is also available using the show controllers fastethernet command.


Router# show hw-module subslot 4/0 counters fpga 0

Input: Total (good & bad) packets: 5734
         TCAM drops: 4908
         Satisfy (host-backpressure) drops: 0
         CRC drops: 0
         PL3 RERRs: 0
  Output: EOP (SPI4) errors: 0

show hw-module subslot status mac Example

The following shows sample output from the show hw-module subslot command for MAC device status on the first interface (port 0):

Router# show hw-module subslot 4/0 status mac 0

  Status registers:
    speed = 100 Mbps, duplex = full, interface mode = copper
    spi3 side loopback is disabled, line side loopback is disabled
    padding is disabled, crc add is disabled
    force duplex is enabled
  Rx FIFO status:
    Read pointer = 0xCDE, Write pointer = 0xCDE
    Occupancy of FIFO in 8 byte locations = 0
    Reset is not set
    Overflow event did not occur
  Tx FIFO status:
    Read pointer = 0x498, Write pointer = 0x498
    Occupancy of FIFO in 8 byte locations = 0
    Overflow event did not occur
    Underflow event did not occur
    Out of sequence event did not occur

show hw-module subslot status phy Example

The following shows sample output from the show hw-module subslot command for PHY device status on the first interface (port 0):

Router# show hw-module subslot 4/0 status phy 0

  PHY Status:
  status (reg 1) = 0x7949
    link is down, auto-negotiation is not complete
    remote fault not detected, jabber not detected
  phy specific status (reg 17) = 0x4100
    link is down (real-time), speed/duplex not resolved
    speed: 100 Mbps, duplex: half
    page not received, cable length is 80 - 110m
    MDI cross-over status: MDI, downshift status: no
    energy detect status: active
    transmit pause: disabled, receive pause: disabled
    polarity: normal, jabber: no
  phy specific extended status (reg 27) = 0x848B
    Fiber/ copper auto selection disabled, copper link
    Serial interface auto-negotiation bypass disabled
    Serial interface auto-negotiation bypass status:
      Link came up because regular fiber autoneg completed
    Interrupt polarity is active low
  receive error count: 0x0

show hw-module subslot fpd

To display the current versions of all field-programmable devices (FPDs) for a particular SPA or all of the active SPAs on a router, use the show hw-module subslot fpd command in privileged EXEC mode.

Cisco 7304 Router

show hw-module subslot [slot/subslot] fpd

Cisco 7600 Series Routers, Catalyst 6500 Series Switches, and Cisco 12000 Series Routers

show hw-module subslot {slot/subslot | all} fpd

Syntax Description

slot

Chassis slot number.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot

Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

all

Specifies display of FPD information for all SPAs in the system.

Note The all keyword is not supported for SPAs on the Cisco 7304 router.


Defaults

For the Cisco 7304 router, if no location is specified, the output for this command will show information for all supported card types on the router.

For the Cisco 7600 series routers, Catalyst 6500 series switches, and Cisco 12000 series routers, there is no default behavior or values.

For more information about FPD upgrades on shared port adapters (SPAs), refer to the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(20)S2

This command was introduced.

12.2(18)SXE

The all keyword was added in Cisco IOS Release 12.2(18)SXE on the Cisco 7600 series routers and Catalyst 6500 series switches.

12.0(31)S

This command was integrated into Cisco IOS Release 12.0(31)S and introduced on Cisco 12000 series routers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Usage Guidelines

Other than the FPD version information, the output for this command may also contain useful FPD-related notes.

Cisco 7304 Router

The all keyword is not supported on the Cisco 7304 router. The slot/subslot arguments are optional, and if you do not specify them, the command displays FPD information for all supported card types on the router.

Cisco 7600 Series Routers, Catalyst 6500 Series Switches, and 12000 Series Routers

If you do not use the all keyword, then you must specify the slot/subslot arguments to select the location of a particular card. There is no default behavior for this command on the Cisco 7600 series routers.

Examples

Displaying FPD Information for a Particular SPA Example

This example shows the output when using the slot/subslot arguments to identify a particular SPA. This SPA meets the minimum FPD requirements with that particular Cisco IOS release:

Router# show hw-module subslot 4/0 fpd

==== ====================== ====== =============================================
                             H/W   Field Programmable   Current   Min. Required
Slot Card Description        Ver.  Device: "ID-Name"    Version      Version
==== ====================== ====== ================== =========== ==============
4/0 SPA-4XOC3-ATM           1.0   1-I/O FPGA             0.121       0.121    
==== ====================== ====== =============================================

Displaying FPD Information for all SPAs in the System Example

This example shows FPD image file versions for all SPAs in the system:

Router# show hw-module subslot all fpd

==== ====================== ====== =============================================
                             H/W   Field Programmable   Current   Min. Required
Slot Card Type               Ver.  Device: "ID-Name"    Version      Version
==== ====================== ====== ================== =========== ==============
 4/0 SPA-4XOC3-ATM           1.0   1-I/O FPGA             0.121       0.121    
---- ---------------------- ------ ------------------ ----------- --------------
 4/1 SPA-8XT1/E1             0.143 1-ROMMON               2.12        2.12     
                                   2-I/O FPGA             0.22        0.22     
---- ---------------------- ------ ------------------ ----------- --------------
 4/3 SPA-4XOC3-POS           0.100 1-I/O FPGA             3.4         3.4      
---- ---------------------- ------ ------------------ ----------- --------------
 7/0 SPA-8XCHT1/E1           0.117 1-ROMMON               2.12        2.12     
                                   2-I/O FPGA             0.22        0.22     
---- ---------------------- ------ ------------------ ----------- --------------
 7/1 SPA-4XOC3-ATM           0.205 1-I/O FPGA             0.121       0.121    
==== ====================== ====== =============================================

Displaying Information for all SPAs in the System Example (Cisco 7304 only)

The all keyword is not supported on the Cisco 7304 router.

To display all FPD image file versions for all SPAs on a Cisco 7304 router, enter the show hw-module subslot fpd command without specifying a slot and subslot. The following example shows all FPD image file versions on a Cisco 7304 router:

Router# show hw-module subslot fpd

==== ====================== ====== =============================================
                             H/W   Field Programmable   Current   Min. Required
Slot Card Description        Ver.  Device:"ID-Name"     Version      Version
==== ====================== ====== ================== =========== ==============
 2/0 SPA-4FE-7304            0.32  1-Data & I/O FPGA      4.13        4.13     
---- ---------------------- ------ ------------------ ----------- --------------
 2/1 SPA-2GE-7304            0.15  1-Data & I/O FPGA      4.13        4.13     

==== ====================== ====== =============================================

Related Commands

Command
Description

show hw-module all fpd

Displays the current versions of all FPDs for all of the supported card types on a router.

show hw-module slot fpd

Displays the current versions of all FPDs for a SIP in the specified slot location on a router, and for all of the SPAs installed in that SIP.


show hw-module subslot oir

To display the operational status of a shared port adapter (SPA), use the show hw-module subslot oir command in privileged EXEC configuration mode.

show hw-module subslot {slot/subslot | all} oir [internal]

Syntax Description

slot

Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot

Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

all

Displays OIR status for all supported card types in the system.

internal

(Optional) Displays detailed diagnostic information. This option is intended for internal diagnostic use with Cisco Systems technical support personnel.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(25)S3

This command was introduced.

12.2(18)SXE

This command was integrated into Cisco IOS Release 12.2(18)SXE.

12.0(31)S

This command was integrated into Cisco IOS Release 12.0(31)S.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Usage Guidelines

Use the show hw-module subslot oir command to obtain operational status information about one or all SPAs. To display information for a specific SPA, specify the slot number of the SIP and the subslot number of the SPA about which you want information.

To display information for all SPAs in the router, do not specify the slot/subslot arguments and use the all keyword. If no location is specified, the output for this command will show information for all SPAs in the router.

The optional internal keyword displays detailed diagnostic information that is recommended only for use with Cisco Systems technical support personnel.

Examples

The following example shows the operational status of all of the SPAs installed in a router where two of the SPAs are in an out-of-service condition:

Router# show hw-module subslot all oir

Module         Model              Operational Status
-------------- ------------------ -------------------------
subslot 4/0    SPA-4XOC3-POS      booting
subslot 4/1    SPA-4XOC3-ATM      out of service(FPD upgrade failed)
subslot 4/2    SPA-4XOC3-POS      ok
subslot 4/3    SPA-1XTENGE-XFP    out of service(SPA unrecognized)

Table 1 describes the possible values for the Operational Status field in the output.


Note The following status descriptions are not applicable to every SPA and can be platform-specific.


Table 1 Operational Status Field Descriptions 

Operational Status
Description

admin down

SPA is administratively disabled by the hw-module subslot shutdown global configuration command.

booting

SPA is initializing.

missing

SPA is not present in the SIP subslot.

ok

SPA is operational.

out of service (reason)

The SPA is out of service for one of the following reasons:

Note The following reasons are not applicable to every SPA and can be platform-specific.

Analyze failed—Failed to create a SPA data structure, most likely due to a memory allocation problem.

Authentication failed—A SPA has failed hardware validation.

Data structure create error—Failed to create a SPA data structure, most likely due to a memory allocation problem.

Event corrupt—A SPA online insertion and removal (OIR) event has been corrupted. This could be caused by a corrupted message between the SIP and the Route Processor (RP) or some other software or hardware problem.

Event sequence error—A SPA OIR event was received out of sequence. This could be caused by a corrupted message between the SIP and the Route Processor (RP) or some other software or hardware problem.

Fail code not set—Failure code could not be read from a SPA OIR event message. This could be caused by a corrupted message between the SIP and the RP or some other software or hardware problem.

Failed too many times—A SPA is disabled because it has failed more than the allowable limit on the platform.

 

FPD upgrade failed—A field-programmable device, such as the Field-Programmable Gate Array (FPGA), failed to automatically upgrade.

H/W signal deasserted—The SPA_OK or PWR_OK hardware signal indicating that the SPA is accessible is no longer asserted.

Heartbeat failed—Occurs when intelligent SPAs encounter heartbeat failures.

Incompatible FPD—An FPGA version mismatch with the Cisco IOS software has been detected for the SPA.

Init timeout—Time limit has been reached during initialization of a SPA.

Read SPA type failed—A read from the hardware for the SPA type failed.

Reload request—A SPA reload is in progress from the hw-module subslot reload command.

SPA h/w error—The SPA software driver has detected a hardware error.

SPA ready timeout—A timeout ocurred on the RP while waiting for the SPA to become operational.

SPA type mismatch—Occurs when you have preconfigured a SPA of one type, but have inserted a SPA of a different type.

Note This reason code only applies to those platforms that support pre-configuration. This is not applicable to a Cisco 7600 series router or Catalyst 6500 series switch.

SPA unrecognized—SPA is not supported by the Cisco IOS software release.

Start failed—Failed to start interfaces on SPA.

Unexpected inserted event—The SPA OIR software has received a SPA insertion event when the OIR software considered the SPA already present.

Wait h/w ok timeout—A timeout occurred while waiting for the SPA_OK and PWR_OK hardware signals to be asserted.

Wait start timeout—A timeout occurred on the SIP while waiting for permission from the RP to bring up the SPA.

stopped

SPA has been gracefully deactivated using the hw-module subslot stop privileged EXEC command on the Cisco 7304 router.


The following example shows the operational status of all of the SPAs installed in a router where all SPAs are running successfully:

Router# show hw-module subslot all oir 

Module        Model                Operational Status
------------- -------------------- ------------------------
subslot 1/1   SPA-2XOC3-ATM        ok
subslot 4/0   SPA-2XT3/E3          ok
subslot 4/1   SPA-4XOC3-POS        ok
subslot 4/2   SPA-8XCHT1/E1        ok

The following example shows sample output when using the optional internal keyword:

Router# show hw-module subslot 4/0 oir internal

WARNING: This command is not intended for production use
and should only be used under the supervision of
Cisco Systems technical support personnel.

sm(spa_oir_tsm subslot 4/0 TSM), running yes, state ready
Admin Status: admin enabled,  Operational Status: ok(1)
Last reset Reason: manual
TSM Context:
    configured_spa_type 0x483
    soft remove fail code 0x0(none)
    last_fail_code 0x110E(SPA unrecognized)
    fail_count 0
    timed_fail_count 0, failed_spa_type 0x483
    recovery_action 6
    associated_fail_code 0x110E(SPA unrecognized)
    sequence numbers: next from tsm 4, last to tsm 2
    flags 0x0
Subslot:
    spa type 0x483, active spa type 0x483
    subslot flags 0x0, plugin flags 0x0
TSM Parameters:
    wait_psm_ready_timeout 360000 ms, init_timeout 240000 ms
    short_recovery_delay 5000 ms, long_recovery_delay 120000 ms
    ok_up_time 1200000 ms, bad_fail_count 10
    fail_time_period 600000 ms, max_fail_count 5
    does not support pre-configuration
SPA OIR state machine audit statistics
                In-sync poll-count  qry-fail resp-fail  restarts fail-count
subslot 4/0         yes          1         0         0         0          0

Related Commands

Command
Description

hw-module subslot reload

Restarts a SPA and its interfaces.

hw-module subslot shutdown

Shuts down a SPA with or without power.


show hw-module subslot service-engine status

To display the Cisco WebEx Node SPA application status on a Cisco ASR 1000 Series Router, use the show hw-module subslot service-engine status command in privileged EXEC mode.

show hw-module subslot slot/subslot service-engine status

Syntax Description

slot

Specifies the chassis slot number for the Cisco ASR 1000 Series Router SIP.

/subslot

Specifies the secondary subslot number on a Cisco ASR 1000 Series Router SIP where a SPA is installed.


Command Default

No default behavior or values.

Command Modes

Privileged EXEC (#)

Command History

Release
Modification

IOS XE Release 2.4

This command was introduced.


Usage Guidelines

Use the show hw-module subslot service-engine status command to obtain information about the Cisco WebEx Node SPA application status. This includes configuration information sent from the Route Processor (RP) and the operation status of the application.

Examples

The following example provides sample output for the show hw-module subslot service-engine status command for a Cisco WebEX Node SPA located in the top subslot (0) of the SIP that is installed in slot 0 on a Cisco ASR 1000 Series Router:

Service Engine is Cisco SPA-WMA-K9
Service Engine state: Steady (0x300)
Service Engine OS Version: 1.0.0, Application Version: 1.0.0
Application: WebEx Node (Web Conferencing)
Application Status: Online
Configuration:
  Int ip address: 10.200.72.18 ,  mask: 255.255.255.252
  GW ip address: 10.200.72.17
  Nameserver 1: 10.100.4.10 ,  Nameserver 2: 10.100.4.20
  Hostname: spawma1, Domain name: cisco.com
  WMA URL - https://wmabts.webex.com/wmams
  WMA Token - 45484b3e-8ea5-41e5-b050-49409006d14e
  WMA Passcode Name - cisco_test, key:0552055C271A4B5C4D5D424A5B5E007F

show hw-module subslot transceiver

To display the information about an optical transceiver installed in a shared port adapter (SPA), use the show hw-module subslot transceiver command in privileged EXEC configuration mode.

show hw-module subslot slot/subslot transceiver port {idprom [brief | detail | dump] | status}

Syntax Description

slot

Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot

Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

port

Port or interface number.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

idprom

Displays detailed hardware information for the specified transceiver.

brief

(Optional) Displays summary hardware information for the specified transceiver.

detail

(Optional) Displays detailed hardware information for the specified transceiver.

dump

(Optional) Displays register information for the specified transceiver.

status

Displays operational status for the specified transceiver.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(18)SXE

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Usage Guidelines

Use the show hw-module subslot transceiver command to obtain hardware information or operational status for optical devices installed in a SPA.

Cisco Systems qualifies the small form-factor pluggable (SFP) optics modules that can be used with SPAs.


Note The SPAs will only accept the SFP modules listed as supported in this document. An SFP check is run every time an SFP module is inserted into a SPA and only SFP modules that pass this check will be usable.


If a transceiver has not been qualified by Cisco Systems for use with a SPA, the show hw-module subslot transceiver status command reports the following message:

The transceiver in slot 4 subslot 0 port 2
  is not a Cisco supplied component. In the current configuration
  third party transceivers are not serviced.

If a transceiver has not been qualified by Cisco Systems for use with a SPA, the show hw-module subslot transceiver idprom command reports the following message:

Transceiver is not a Cisco supplied part: the system cannot read the IDPROM

Examples

Example of the show hw-module subslot transceiver idprom Command for an OC-3 Transceiver

The following example shows hardware IDPROM information for an OC-3, short reach, multimode transceiver installed in the first interface port (0) of the SPA located in subslot 2 of the SIP installed in chassis slot 7:

Router# show hw-module subslot 7/2 transceiver 0 idprom 
IDPROM for transceiver POS7/2/0:
  Description                               = SFP optics (type 3)
  Transceiver Type:                         = OC3 SR-1/STM1 MM (1)
  Product Indentifier (PID)                 = TRP-03BCS       
  Vendor Revision                           =   
  Serial Number (SN)                        = 2169298         
  Vendor Name                               = OCP             
  Vendor OUI (IEEE company ID)              = 00.00.00 (0)
  Device State                              = Enabled.
  CLEI code                                 = ^@^@^Cc#}0^Ll5
  Cisco part number                         = hc?z^B<@^E^R^@
  Date code (yy/mm/dd)                      = 03/04/21
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              4b5b
                                              NRZ
  Nominal bitrate                           = OC3/STM1 (200 Mbits/s)
  Minimum bit rate as % of nominal bit rate = 68 % of 200 Mbits/s
  Maximum bit rate as % of nominal bit rate = 71 % of 200 Mbits/s

Example of the show hw-module subslot transceiver idprom Command for an OC-12 Transceiver

The following example shows hardware IDPROM information for an OC-12, short reach, multimode transceiver installed in the first interface port (0) of the SPA located in subslot 0 of the SIP installed in chassis slot 7:

Router# show hw-module subslot 7/0 transceiver 0 idprom 
IDPROM for transceiver POS7/0/0:
  Description                               = SFP optics (type 3)
  Transceiver Type:                         = OC12 SR-1/STM4 MM (8)
  Product Indentifier (PID)                 = TRP-12BCS       
  Vendor Revision                           =   
  Serial Number (SN)                        = 2177091         
  Vendor Name                               = OCP             
  Vendor OUI (IEEE company ID)              = 00.00.00 (0)
  Device State                              = Enabled.
  CLEI code                                 = ^@^@^CdZ+{N^\^X
  Cisco part number                         = pk:c^F^K^@
  Date code (yy/mm/dd)                      = 03/05/07
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              4b5b
                                              NRZ
  Nominal bitrate                           = OC12/STM4 (600 Mbits/s)
  Minimum bit rate as % of nominal bit rate = 92 % of 600 Mbits/s
  Maximum bit rate as % of nominal bit rate = 13 % of 600 Mbits/s

Example of the show hw-module subslot transceiver idprom brief Command

The following example shows the operational status of the transceiver installed in the first interface port (0) of the SPA located in subslot 2 of the SIP installed in chassis slot 3:

Router# show hw-module subslot 3/2 transceiver 0 idprom brief
IDPROM for transceiver POS3/2/0:
  Description                               = SFP optics (type 3)
  Transceiver Type:                         = OC12 SR-1/STM4 MM (8)
  Product Indentifier (PID)                 = TRP-12BCS       
  Vendor Revision                           =   
  Serial Number (SN)                        = 2569567         
  Vendor Name                               = CISCO-OCP       
  Vendor OUI (IEEE company ID)              = 00.00.00 (0)
  Device State                              = Enabled.
  CLEI code                                 = ^@^@^C4]  ^@T(.
  Cisco part number                         = T^W;L^YkcQ7^@
  Date code (yy/mm/dd)                      = 04/03/24
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              4b5b
                                              NRZ
  Nominal bitrate                           = OC12/STM4 (600 Mbits/s)
  Minimum bit rate as % of nominal bit rate = 92 % of 600 Mbits/s
  Maximum bit rate as % of nominal bit rate = 13 % of 600 Mbits/s

Example of the show hw-module subslot transceiver idprom detail Command

The following example shows the detail form of the command for the transceiver installed in the sixth interface port (5) of the SPA located in subslot 0 of the SIP installed in chassis slot 4:

Router# show hw-module subslot 4/0 transceiver 5 idprom detail 
IDPROM for transceiver GigabitEthernet4/0/6:
  Description                               = SFP optics (type 3)
  Transceiver Type:                         = GE SX (19)
  Product Indentifier (PID)                 = FTRJ8519P1BNL-C3
  Vendor Revision                           = A1
  Serial Number (SN)                        = FNS0821K2J5     
  Vendor Name                               = CISCO-FINISAR   
  Vendor OUI (IEEE company ID)              = 00.90.65 (36965)
  CLEI code                                 = CNUIAAMAAA
  Cisco part number                         = 10-1954-01
  Device State                              = Enabled.
  Date code (yy/mm/dd)                      = 04/05/19
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              NRZ
  Nominal bitrate                           = 2xFC (2100 Mbits/s)
  Minimum bit rate as % of nominal bit rate = not specified
  Maximum bit rate as % of nominal bit rate = not specified
  Link reach for 9u fiber (km)              = SX(550/270m) (0)
                                              1xFC-MM(500/300m) (0)
                                              2xFC-MM(300/150m) (0)
                                              ESCON-MM(2km) (0)
  Link reach for 9u fiber (m)               = SX(550/270m) (0)
                                              1xFC-MM(500/300m) (0)
                                              2xFC-MM(300/150m) (0)
                                              ESCON-MM(2km) (0)
  Link reach for 50u fiber (m)              = 2xFC-MM(300/150m) (30)
  Link reach for 62.5u fiber (m)            = 2xFC-MM(300/150m) (15)
  Nominal laser wavelength                  = 850 nm.
  DWDM wavelength fraction                  = 850.0  nm.
  Supported options                         = Tx disable
                                              Tx fault signal
                                              Loss of signal (standard implementation)
  Supported enhanced options                = Alarms for monitored parameters
  Diagnostic monitoring                     = Digital diagnostics supported
                                              Diagnostics are externally calibrated
                                              Rx power measured is "Averagepower"
  Transceiver temperature operating range   = -5 C to 85 C (extended)
  Minimum operating temperature             = -20 C
  Maximum operating temperature             = 90 C
  High temperature alarm threshold          = +109.000 C
  High temperature warning threshold        = +103.000 C
  Low temperature warning threshold         =  -13.000 C
  Low temperature  alarm threshold          =  -29.000 C
  High voltage alarm threshold              = 3.9000 Volts
  High voltage warning threshold            = 3.7000 Volts
  Low voltage warning threshold             = 2.9000 Volts
  Low voltage alarm threshold               = 2.7000 Volts
  High laser bias current alarm threshold   = 15.000 mAmps
  High laser bias current warning threshold = 12.000 mAmps
  Low laser bias current warning threshold  = 2.000 mAmps
  Low laser bias current alarm threshold    = 1.000 mAmps
  High transmit power alarm threshold       = 0.7424 mWatts
  High transmit power warning threshold     = 0.7424 mWatts
  Low transmit power warning threshold      = 0.959 mWatts
  Low transmit power alarm threshold        = 0.619 mWatts
  High receive power alarm threshold        = 5.9324 mWatts
  High receive power warning threshold      = 3.7416 mWatts
  Low receive power warning threshold       = 0.751 mWatts
  Low receive power alarm threshold         = 0.478 mWatts
  External Calibration constant: Rx power4  = 0.000
  External Calibration constant: Rx power3  = 0.000
  External Calibration constant: Rx power2  = 0.000
  External Calibration constant: Rx power1  = 0.212
  External Calibration constant: Rx power0  = -1.4294966868
  External Calibration: bias current slope  = 1.000
  External Calibration: bias current offset = 0

Example of the show hw-module subslot transceiver status Command

The following example shows the operational status of the transceiver installed in the third interface port (2) of the SPA located in subslot 0 of the SIP installed in chassis slot 4:

Router# show hw-module subslot 4/0 transceiver 2 status 
The Transceiver in slot 4 subslot 0 port 2 is enabled.
  Module temperature                = +41.617 C
  Transceiver Tx supply voltage     = 3292.0 uVolts
  Transceiver Tx bias current       = 4840 uAmps
  Transceiver Tx power              = 349.2 uWatts
  Transceiver Rx optical power      = 0.5 uWatts

show icc

To display the information about the interface controller card (ICC) counter and status, use the show icc command in user EXEC or privileged EXEC mode.

show icc {counters | flowcontrol | mcast | status}

Syntax Description

counters

Displays the counter information.

flowcontrol

Displays the flow control information.

mcast

Displays the multicast information.

status

Displays the status information.


Defaults

This command has no default settings.

Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Examples

This example shows how to display the information about the ICC counter:

Router> show icc counters

total tx RPC packets to slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   2 =0            7 =0            8 =0            10=0           
   11=0            12=0            14=0            17=0           
   18=0            19=0            20=0           
total rx RPC packets from slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   2 =5            7 =7            8 =11           10=4           
   11=1            12=2            14=1            17=67          
   18=7            19=159          20=29
total tx MCAST-SP packets to slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   6 =0            7 =0            8 =0            9 =0           
   12=0            14=0           
total rx MCAST-SP packets from slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   6 =1            7 =1            8 =1            9 =1           
   12=41           14=67          
total tx L3-MGR packets to slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   1 =0            2 =0            3 =0           
total rx L3-MGR packets from slot 1 LCP = 0
  detail by request id: (<request-id>=<number-of-packets>)
   1 =1            2 =2            3 =1
Router#

This example shows how to display the information about the ICC status:

Router> show icc status

Class Name             Msgs Pending  Max Pending  Total Sent
----- ---------------- ------------  -----------  ----------
    2 RPC                         0            3         403
    3 MSC                         0            1           1
    5 L3-MGR                      0            4        4173
   13 TCAM-API                    0           10          26
Router#

Related Commands

Command
Description

show interfaces

Displays the status and statistics for the interfaces in the chassis.


show interface sdcc

To display configuration information and statistics for a sections data communications channel (SDCC) interface, use the show interface sdcc command in privileged EXEC mode.

show interface sdcc slot/subslot/port

Syntax Description

slot

Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot

Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

/port

(Optional) Port or interface number.

Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(11)BC3

This command was introduced.

12.2(25)S3

This command was integrated into Cisco IOS Release 12.2(25)S3 to support POS SPAs on the Cisco 7304 router.

12.2(18)SXE

This command was integrated into Cisco IOS Release 12.2(18)SXE to support POS SPAs on the Cisco 7600 series routers and Catalyst 6500 series switches.

12.0(31)S

This command was integrated into Cisco IOS Release 12.0(31)S to support POS SPAs on the Cisco 12000 series routers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Examples

Cisco 7600 Series Router and Catalyst 6500 Series Switch Example

The following command displays configuration information and statistics for SDCC interface 7/0/0:

Router# show interface sdcc 7/0/0

SDCC7/0/0 is up, line protocol is up
  Hardware is SDCC
  Internet address is 10.11.11.10/8
  MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive not set
  Last input 00:00:38, output 00:00:38, output hang never
  Last clearing of "show interface" counters 00:00:48
  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
     5 packets input, 520 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5 packets output, 520 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Cisco 12000 Series Router Example

The following is sample output from the show interface sdcc command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):

Router# show interface sdcc 1/1/0 

SDCC1/1/0 is administratively down, line protocol is down
  Hardware is SDCC
  MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, crc 32, loopback not set
  Keepalive set (10 sec)
  Last input never, output never, output hang never
  Last clearing of "show interface" counters 00:01:55
  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 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Table 2 describes the significant fields shown in these displays.

Table 2 show interface sdcc Field Descriptions 

Field
Description

SDCCx/y/z is up, line protocol is up

Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.

Hardware is. . .

Hardware type:

SDCC— Section Data Communications Channel

Internet address is

Internet address and subnet mask.

MTU

Maximum transmission unit of the interface.

BW

Bandwidth of the interface, in kilobits per second.

DLY

Delay of the interface, in microseconds.

rely

Reliability of the interface as a fraction of 255 (255/255 is 100 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. The calculation uses the value from the bandwidth interface configuration command.

Encapsulation

Encapsulation method assigned to interface.

crc

Cyclic redundancy check size (16 or 32 bits).

Loopback

Indicates whether loopback is set.

Keepalive

Indicates whether keepalives are set.

Last input

Number of hours, minutes, and seconds since the last packet was successfully received by an interface 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.

(Last) output

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.

(Last) output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Last clearing

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.

Queueing strategy

First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Output queue, drops
input queue, drops

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.

5 minute input rate
5 minute output rate

Average number of bits and packets received or transmitted per second in the last 5 minutes.

packets input

Total number of error-free packets received by the system.

bytes (input)

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.

broadcasts

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the minimum packet size of the medium.

giants

Number of packets that are discarded because they exceed the maximum packet size of the medium.

throttles

Not supported for POS interfaces.

parity

Report of the parity errors on the interface.

input errors

Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.

CRC

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.

frame

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.

overrun

Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.

abort

Illegal sequence of one bits on the interface.

packets output

Total number of messages transmitted by the system.

bytes (output)

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

underruns

Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.

collisions

Not supported for POS interfaces.

interface resets

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.

output buffer failures

Not supported for POS interfaces.

output buffers swapped out

Not supported for POS interfaces.

carrier transitions

Number of times the carrier detect signal of the interface has changed state.


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 interface-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]

Cisco 7600 Series

show interfaces [type interface-number | null interface-number | vlan vlan-id]

Channelized T3 Shared Port Adapters

show interfaces serial [slot/subslot/port/t1-num:channel-group]

Shared Port Adapters

show interfaces type [slot/subslot/port[/sub-int]]

Syntax Description

type

(Optional) Interface type. Allowed values for type can be 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 be pos.

For the Cisco 7600 series routers, type can be ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, and port-channel, atm, and ge-wan.

For shared port adapters, type can be fastethernet, gigabitethernet, pos, sdcc, serial, and tengigabitethernet, depending on the type of SPA supported on the router.

interface-number

(Optional) Port number on the selected interface.

first last

(Optional) For 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.

null interface-number

(Optional) Specifies the null interface; the valid value is 0.

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.

[slot/subslot/port/t1-num:channel-group]

(Optional) Channelized T3 Shared Port Adapters

Number of the chassis slot that contains the channelized T3 SPA (for example 5/0/0:23), where:

slot—(Optional) Chassis slot number.

For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot—(Optional) Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

/port—(Optional) Port or interface number.

For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.

/t1-num—(Optional) T1 time slot in the T3 line. The value can be from 1 to 28.

:channel-group—(Optional) Number 0-23 of the DS0 link on the T1 channel.

[slot/subslot/port[/sub-int]]

(Optional) Shared Port Adapters

Number of the chassis slot that contains the SPA interface (for example 4/3/0), where:

slot—(Optional) Chassis slot number.

For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.

/subslot—(Optional) Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.

/port—(Optional) Port or interface number.

For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.

/sub-int(Optional ) Subinterface number (for those SPAs that support subinterface configuration).

vlan vlan-id

(Optional) Specifies the VLAN ID; valid values are from 1 to 4094.


Defaults

No default behavior or values

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.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(20)S2

This command was integrated into Cisco IOS Release 12.2(20)S2 and introduced a new address format and output for SPA interfaces on the Cisco 7304 router. The subslot argument was introduced.

12.2(25)S3

This command was integrated into Cisco IOS Release 12.2(25)S3.

12.2(14)SX

Support for this command was added for the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to the 12.2SX release. The uplink dual-mode port information was updated.

12.2(18)SXE

This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers and Catalyst 6500 series switches.

12.0(31)S

This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers, and the tengigabitethernet interface type was added. 10-Gigabit Ethernet interfaces were introduced with the release of the 1-Port 10-Gigabit Ethernet SPA.

12.2(18)SXF

This command was integrated into Cisco IOS Release 12.2(18)SXF.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SRB1

This command was updated to display operational status for Gigabit Ethernet interfaces that are configured as primary and backup interfaces (Cisco 7600 series routers).


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

The interface-number argument designates the module and port number. 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 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.

Cisco 7600 Series Routers

Valid values for interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.

The port channels from 257 to 282 are internally allocated and are supported on the CSM and the FWSM only.

Statistics are collected on a per-VLAN basis for Layer 2-switched packets and Layer 3-switched packets. Statistics are available for both unicast and multicast traffic. The Layer 3-switched packet counts are available for both ingress and egress directions. The per-VLAN statistics are updated every 5 seconds.

In some cases, you might see a difference in the duplex mode that is displayed between the show interfaces command and the show running-config commands. In this case, the duplex mode that is displayed in the show interfaces command is the actual duplex mode that the interface is running. The show interfaces command shows the operating mode for an interface, while the show running-config command shows the configured mode for an interface.

If you do not enter any keywords, all counters for all modules are displayed.

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.

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.

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.

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

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

Table 3 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 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 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 kept for the following protocols:

AppleTalk

ARP (for IP, 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

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 4 shows the fields relevant to all SDLC connections.

Table 4 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.

T1, N1, N2, K

Current values for these variables.


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

Table 5 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 and 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 that 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 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.

Example with a Fast Ethernet SPA on a Cisco 7304 Router

The following is sample output from the show interfaces fastethernet command for the second interface (port 1) in a 4-Port 10/100 Fast Ethernet SPA located in the bottom subslot (1) of the MSC that is installed in slot 2 on a Cisco 7304 router:

Router# show interfaces fastethernet 2/1/1

FastEthernet2/1/1 is up, line protocol is up 
  Hardware is SPA-4FE-7304, address is 00b0.64ff.5d80 (bia 00b0.64ff.5d80)
  Internet address is 192.168.50.1/24
  MTU 9216 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)
  Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:22, output 00:00:02, 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
     5 packets input, 320 bytes
     Received 1 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog
     0 input packets with dribble condition detected
     8 packets output, 529 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 babbles, 0 late collision, 0 deferred
     2 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Example for an Interface with an Asymmetric Receiver and Transmitter Rates

Router# show interfaces e4/0

Ethernet4/0 is up, line protocol is up
  Hardware is AmdP2, address is 000b.bf30.f470 (bia 000b.bf30.f470)
  Internet address is 10.1.1.9/24
  MTU 1500 bytes, BW 10000 Kbit, RxBW 5000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 254/255 
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:01, output hang never
  Last clearing of "show interface" counters 00:03:36
  Input queue: 34/75/0/819 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  30 second input rate 7138000 bits/sec, 14870 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     3109298 packets input, 186557880 bytes, 0 no buffer
     Received 217 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
     22 packets output, 1320 bytes, 0 underruns
     11 output errors, 26 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

Table 6 describes the fields shown in the display.

Table 6 show interfaces fastethernet Field Descriptions—Fast Ethernet SPA 

Field
Description

Fast Ethernet...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, SPA-4FE-7304) and MAC address.

Description

Alphanumeric string identifying the interface. This only appears if the description interface configuration command has been configured on the interface.

Internet address

Internet address followed by subnet mask.

MTU

Maximum transmission unit of the interface. The default is 1500 bytes for the 4-Port 10/100 Fast Ethernet SPA.

BW

Bandwidth of the interface in kilobits per second.

RxBW

Receiver bandwidth of the interface, in kilobits per second. This value is displayed only when an interface has asymmetric receiver and transmitter rates.

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, rxload

Load on the interface (in the transmit "tx" and receive "rx" directions) 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 time interval.

Half-duplex, Full-duplex

Indicates the duplex mode for the interface.

100Mb/s, 10Mb/s

Speed of the interface in megabits per second.

100BaseTX/FX

Media protocol standard.

ARP type:

Type of Address Resolution Protocol (ARP) assigned and the timeout period.

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 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. Useful for knowing when a dead interface failed.

output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is displayed. If that field overflows, asterisks are printed.

Note This field does not apply to SPA interfaces.

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.

A series of asterisks (***) 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.

Input queue (size/max/drops/flushes)

Packet statistics on the input queue reported as:

Size—Number of packets in the input queue.

Max—Maximum size of the queue.

Drops—Number of packets dropped because of a full input queue.

Flushes—Number of packets dropped as part of selective packet discard (SPD). SPD implements a selective packet drop policy on the router's IP process queue. Therefore, it only applies to process-switched traffic.

Total output drops

Total number of packets dropped because of a full output queue.

Queueing strategy

Type of Layer 3 queueing active on this interface. The default is first-in, first-out (FIFO).

Output queue (size/max)

Number of packets in the output queue (size), and the maximum size of the queue (max).

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.

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 minimum packet size of the medium. For instance, any Ethernet packet that is smaller 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 larger than 1536 bytes is considered a giant.

Note For the 4-Port 10/100 Fast Ethernet SPA, the default is that a giant is any packet greater than 1536 bytes. However, if you modify the maximum transmission unit (MTU) for the interface, this counter increments when you exceed the specified MTU for the interface.

throttles

Number of times the receiver on the port was disabled, possibly because of buffer or processor overload.

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 check 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. Broadcast storms and bursts of noise can cause the ignored count to be increased.

watchdog

Number of times the watchdog receive timer expired. Expiration happens when receiving a packet with a length greater than 2048 bytes.

input packets with dribble condition detected

Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented for informational purposes only; 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.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.

collisions

Number of messages retransmitted 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 queued for transmission were not sent within several seconds. Interface resets can occur when an interface is looped back or shut down.

babbles

Transmit jabber timer expired.

late collision

Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble.

deferred

Number of times that the interface 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.

Note This field does not apply to SPA interfaces.

output buffer failures, output buffers swapped out

These counters are not used by the 4-Port 10/100 Fast Ethernet SPA on the Cisco 7304 router.


Example with a Gigabit Ethernet SPA on a Cisco 7304 Router


Example with Gigabit Ethernet SPAs Configured as Primary and Backup Interfaces on a Cisco 7600 Router

The following examples show the additional lines included in the display when the command is issued on two Gigabit Ethernet interfaces that are configured as a primary interface (gi3/0/0) and as a backup interface (gi3/0/11) for the primary:

Router# show interfaces gigabitEthernet 3/0/0 
GigabitEthernet3/0/0 is up, line protocol is up (connected)
  Hardware is GigEther SPA, address is 0005.dc57.8800 (bia 0005.dc57.8800)
  Backup interface GigabitEthernet3/0/11, failure delay 0 sec, secondary disable delay 0 
sec, 
  .
  .
  .

Router# show interfaces gigabitEthernet 3/0/11 
GigabitEthernet3/0/11 is standby mode, line protocol is down (disabled)
  .
  .
  .

Example with a POS SPA on a Cisco 7600 Series Router and Catalyst 6500 Series Switch

The following is sample output from the show interfaces pos command on a Cisco 7600 series router or Catalyst 6500 series switch for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot 4):

Router# show interfaces pos 4/3/0 

POS4/3/0 is up, line protocol is up  (APS working - active)
  Hardware is Packet over SONET
  Internet address is 10.0.0.1/8
  MTU 4470 bytes, BW 622000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive not set
  Scramble disabled
  Last input 00:00:34, output 04:09: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
        Available Bandwidth 622000 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     782 packets input, 226563 bytes, 0 no buffer
     Received 0 broadcasts, 1 runts, 0 giants, 0 throttles
              0 parity
     1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     271 packets output, 28140 bytes, 0 underruns
     0 output errors, 0 applique, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     2 carrier transitions

Table 2 describes the significant fields shown in this display.

Example with a POS SPA on a Cisco 12000 Series Router

The following is sample output from the show interfaces pos command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):

Router# show interfaces pos 1/1/0 

POS1/1/0 is up, line protocol is up
  Hardware is Packet over SONET
  Internet address is 10.41.41.2/24
  MTU 4470 bytes, BW 9952000 Kbit, DLY 100 usec, rely 255/255, load 1/255
  Encapsulation HDLC, crc 32, loopback not set
  Keepalive not set
  Scramble enabled
  Last input 00:00:59, output 00:00:11, output hang never
  Last clearing of "show interface" counters 00:00:14
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
        Available Bandwidth 9582482 kilobits/sec
  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 throttles
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     1 packets output, 314 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Table 7 describes the significant fields shown in this display.

Table 7 show interfaces pos Field Descriptions—POS SPA 

Field
Description

POSx/y/z is up, line protocol is up

Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.

Hardware is. . .

Hardware type:

For POSIP—cyBus Packet over Sonet

For POS SPAs—Packet over SONET

Internet address is

Internet address and subnet mask.

MTU

Maximum transmission unit of the interface.

BW

Bandwidth of the interface, in kilobits per second.

DLY

Delay of the interface, in microseconds.

rely

Reliability of the interface as a fraction of 255 (255/255 is 100 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. The calculation uses the value from the bandwidth interface configuration command.

Encapsulation

Encapsulation method assigned to interface.

Loopback

Indicates whether loopbacks are set.

Keepalive

Indicates whether keepalives are set.

Scramble

Indicates whether or not SONET payload scrambling is enabled. SONET scrambling is disabled by default. For the POS SPAs on the Cisco 12000 series routers, scrambling is enabled by default.

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.

(Last) output

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.

(Last) output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Last clearing

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.

Queueing strategy

First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Output queue, drops
input queue, drops

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.

5 minute input rate
5 minute output rate

Average number of bits and packets received or transmitted per second in the last 5 minutes.

packets input

Total number of error-free packets received by the system.

bytes (input)

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.

broadcasts

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the minimum packet size of the medium.

giants

Number of packets that are discarded because they exceed the maximum packet size of the medium.

throttles

Not supported for POS interfaces.

parity

Report of the parity errors on the interface.

input errors

Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.

CRC

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.

frame

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.

overrun

Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.

abort

Illegal sequence of one bits on the interface.

packets output

Total number of messages transmitted by the system.

bytes (output)

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

underruns

Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.

applique

Indicates an unrecoverable error has occurred on the POSIP applique. The system then invokes an interface reset.

interface resets

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.

output buffer failures

Not supported for POS interfaces.

output buffers swapped out

Not supported for POS interfaces.

carrier transitions

Number of times the carrier detect signal of the interface has changed state.


Example with a POS SPA SDCC Interface on a Cisco 12000 Series Router

The following is sample output from the show interfaces sdcc command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):

Router# show interfaces sdcc 1/1/0 

SDCC1/1/0 is administratively down, line protocol is down
  Hardware is SDCC
  MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, crc 32, loopback not set
  Keepalive set (10 sec)
  Last input never, output never, output hang never
  Last clearing of "show interface" counters 00:01:55
  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 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Table 8 describes the significant fields shown in these displays.

Table 8 show interfaces sdcc Field Descriptions—POS SPA 

Field
Description

SDCCx/y/z is up, line protocol is up

Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.

Hardware is. . .

Hardware type is SDCC—Section Data Communications Channel.

Internet address is

Internet address and subnet mask.

MTU

Maximum transmission unit of the interface.

BW

Bandwidth of the interface, in kilobits per second.

DLY

Delay of the interface, in microseconds.

rely

Reliability of the interface as a fraction of 255 (255/255 is 100 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. The calculation uses the value from the bandwidth interface configuration command.

Encapsulation

Encapsulation method assigned to interface.

crc

Cyclic redundancy check size (16 or 32 bits).

Loopback

Indicates whether loopback is set.

Keepalive

Indicates whether keepalives are set.

Last input

Number of hours, minutes, and seconds since the last packet was successfully received by an interface 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.

(Last) output

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.

(Last) output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Last clearing

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.

Queueing strategy

First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Output queue, drops
input queue, drops

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.

5 minute input rate
5 minute output rate

Average number of bits and packets received or transmitted per second in the last 5 minutes.

packets input

Total number of error-free packets received by the system.

bytes (input)

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.

broadcasts

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the minimum packet size of the medium.

giants

Number of packets that are discarded because they exceed the maximum packet size of the medium.

throttles

Not supported for POS interfaces.

parity

Report of the parity errors on the interface.

input errors

Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.

CRC

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.

frame

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.

overrun

Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.

abort

Illegal sequence of one bits on the interface.

packets output

Total number of messages transmitted by the system.

bytes (output)

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

underruns

Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.

collisions

Not supported for POS interfaces.

interface resets

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.

output buffer failures

Not supported for POS interfaces.

output buffers swapped out

Not supported for POS interfaces.

carrier transitions

Number of times the carrier detect signal of the interface has changed state.


Example with a T3/E3 Shared Port Adapter

The following example shows the interface serial statistics on the first port of a T3/E3 SPA installed in subslot 0 of the SIP located in chassis slot 5.

Router# show interfaces serial 5/0/0

Serial5/0/0 is up, line protocol is up 
  Hardware is SPA-4T3E3
  Internet address is 10.1.1.2/24
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, 
     reliability 255/255, txload 234/255, rxload 234/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input 00:00:05, 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: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 40685000 bits/sec, 115624 packets/sec
  5 minute output rate 40685000 bits/sec, 115627 packets/sec
     4653081241 packets input, 204735493724 bytes, 0 no buffer
     Received 4044 broadcasts (0 IP multicast)
     0 runts, 0 giants, 0 throttles
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     4652915555 packets output, 204728203520 bytes, 0 underruns
     0 output errors, 0 applique, 4 interface resets
     0 output buffer failures, 0 output buffers swapped out
	2 carrier transitions

Table 9 describes the fields shown in the show interfaces serial output for a T3/E3 SPA.


Note The fields appearing in the ouput will vary depending on card type, interface configuration, and the status of the interface.


Table 9 show interfaces serial Field Descriptions—T3/E3 SPA 

Field
Description

Serial

Name of the serial interface.

line protocol is

If the line protocol is up, the local router has received keepalive packets from the remote router. If the line protocol is down, the local router has not received keepalive packets form the remote router.

Hardware is

Designates the specific hardware type of the interface.

Internet address is

The IP address of the interface.

MTU

The maximum packet size set for the interface.

BW

Bandwidth in kilobits per second.

DLY

Interface delay 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.

crc

CRC size in bits.

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.

Last 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 of show interface counters

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.

Input queue

Packet statistics on the input queue reported as:

size—Current size of the input queue.

max—Maximum size of the input queue.

drops—Packets dropped because the queue was full.

flushes—Number of times that data on queue has been discarded.

Total output drops

Total number of dropped packets.

Queueing strategy

First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Output queue

Number of packets in the output queue (size), and the maximum size of the queue (max).

5-minute input rate

Average number of bits and packets received 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.

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.


Example with a 1-Port 10-Gigabit Ethernet SPA on a Cisco 12000 Series Router

Router# show interfaces tengigabitethernet 7/0/0

TenGigabitEthernet7/0/0 is up, line protocol is up (connected)
  Hardware is TenGigEther SPA, address is 0000.0c00.0102 (bia 000f.342f.c340)
  Internet address is 10.1.1.2/24
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not supported
  Full-duplex, 10Gb/s
  input flow-control is on, output flow-control is on 
ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:10, output hang never
  Last clearing of "show interface" counters 20:24:30
  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
  L2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
  L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast
  L3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes
     237450882 packets input, 15340005588 bytes, 0 no buffer
     Received 25 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     1676 packets output, 198290 bytes, 0 underruns
     0 output errors, 0 collisions, 4 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Displaying Traffic for a Specific Interface Example

This example shows how to display traffic for a specific interface:

Router# show interfaces GigabitEthernet9/5 

GigabitEthernet9/5 is up, line protocol is up 
Hardware is C6k 1000Mb 802.3, address is 0001.64f8.3fa5 (bia 0001.64f8.3fa5)
Internet address is 172.20.20.20/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s 
Dual-mode port configured as RJ45
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, 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 1000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
L2 Switched: ucast: 8199 pkt, 1362060 bytes - mcast: 6980 pkt, 371952 bytes
L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes 
300114 packets input, 27301436 bytes, 0 no buffer
Received 43458 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
15181 packets output, 1955836 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Router#

This example shows how to display traffic for a FlexWAN module:

Router# show interfaces pos 6/1/0.1 

POS6/1/0.1 is up, line protocol is up 
  Hardware is Packet over Sonet
  Internet address is 10.1.2.2/24
  MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY <<<+++ no packets info after this line
Arches#sh mod 6            
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  6    0  2 port adapter FlexWAN                 WS-X6182-2PA       SAD04340JY3

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  6  0001.6412.a234 to 0001.6412.a273   1.3   12.2(2004022 12.2(2004022 Ok

Mod Online Diag Status 
--- -------------------
  6 Pass
Router#

Related Commands

Command
Description

interface

Configures an interface type and enters interface configuration mode.

show controllers fastethernet

Displays Fast Ethernet interface information, transmission statistics and errors, and applicable MAC destination address and VLAN filtering tables.

show controllers gigabitethernet

Displays Gigabit Ethernet interface information, transmission statistics and errors, and applicable MAC destination address and VLAN filtering tables.

show controllers pos

Displays information about the POS controllers.

show controllers serial

Displays controller statistics.


show interfaces accounting

To display the number of packets of each protocol type that have been sent through all configured interfaces, use the show interfaces accounting command in user EXEC or privileged EXEC mode.

show interfaces [type number | null interface-number | vlan vlan-id] accounting

Syntax Description

null interface-number

(Optional) Specifies the null interface; the valid value is 0.

number

(Optional) Module and port number; see the "Usage Guidelines" section for valid values.

type

(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, port-channel, atm, and ge-wan.

vlan vlan-id

(Optional) Specifies the VLAN ID; valid values are from 1 to 4094.


Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History

Release
Modification

12.2(17a)SX1

This command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

This command was implemented on the Supervisor Engine 2.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SRC

Support for IPv6 was added.

12.2(33)SB

This command was integrated into Cisco IOS Release 12.2(33)SB.

Cisco IOS XE Release 2.1

This command was implemented on Cisco ASR 1000 Series Routers.


Usage Guidelines


Note The Pkts Out field for IP displays the number of IPv4 software and hardware switched packets transmitted for the specified protocol. The Pkts Out field for IPv6 displays the number of IPv6 software and hardware switched packets transmitted for the specified protocol. The Chars Out field for IP displays the number of IPv4 software and hardware switched characters transmitted for the specified protocol. The Chars Out field for IPv6 displays the number of IPv6 software and hardware switched characters transmitted for the specified protocol. The Pkts In and Chars In fields display both IPv4 and IPv6 packet counts, except for tunnel interfaces. For tunnel interfaces, the IPv6 input packets are counted as IPv6 packets only.


In the Cisco 7600 and Catalyst 6000 series platform, due to hardware limitations on the ASIC, PFC IPv4 and IPv6 packets cannot be differentiated. The Pkts In and Chars In fields for IP count IPv6 and IPv4 packets are hardware-forwarded. The Pkts In and Chars In fields for IPv6 count only the software-forwarded packets. The IP Pkts Out and Chars Out fields show IPv4 packets, and the IPv6 Pkts Out and Chars Out fields show IPv6 packets.

The number argument designates the module and port number. Valid values for number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.

The port channels from 257 to 282 are internally allocated and are supported on the CSM and the FWSM only.

If you do not enter any keywords, all counters for all modules are displayed.

Examples

This example shows how to display the number of packets of each protocol type that have been sent through all configured interfaces:

Router# show interfaces gigabitethernet 5/2 accounting 

GigabitEthernet5/2 
Protocol Pkts In Chars In Pkts Out Chars Out 
IP       50521   50521000 0        0 
DEC MOP  0       0        1        129 
CDP      0       0        1        592 
IPv6     11      834      96       131658

Table 10 describes the significant fields shown in the display.

Table 10 show interfaces accounting Descriptions 

Field
Description

Protocol

Protocol that is operating on the interface.

Pkts In

For IP, it is the number of IPv4 software-switched, IPv4 and IPv6 hardware-switched packets received for the specified protocol.

For IPv6, it is the number of IPv6 software-switched packets received for the specified protocol.

Chars In

For IP, it is the number of IPv4 software-switched, IPv4 and IPv6 hardware-switched characters received for the specified protocol.

For IPv6, it is the number of IPv6 software-switched characters received for the specified protocol.

Pkts Out

For IP, it is the number of IPv4 software-switched and hardware-switched packets transmitted for the specified protocol.

For IPv6, it is the number of IPv6 software-switched and hardware-switched packets transmitted for the specified protocol.

Chars Out

For IP, it is the number of IPv4 software-switched and hardware-switched characters transmitted for the specified protocol.

For IPv6, it is the number of IPv6 software-switched and hardware-switched characters transmitted for the specified protocol.


Related Commands

Command
Description

show interfaces

Displays the status and statistics for the interfaces in the chassis.


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 11 describes the significant fields shown in the display.

Table 11 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 capabilities

To display the interface capabilities for a module, an interface, or all interfaces, use the show interfaces capabilities command in user EXEC or privileged EXEC mode.

show interfaces [interface interface-number] capabilities [module number]

Syntax Description

interface

(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and port-channel, and ge-wan.

interface-number

Module and port number; see the "Usage Guidelines" section for valid values.

module number

(Optional) Specifies the module number; see the "Usage Guidelines" section for valid values.


Defaults

This command has no default settings.

Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.

12.2(18)SXE

This output was changed to include information about the following on the Supervisor Engine 720 only:

Port security

dot1x

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.


Usage Guidelines

The pos, atm, and ge-wan keywords are supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

The interface-number argument designates the module and port number. Valid values for interface-number depend on the chassis and module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the slot number are from 2 to 13 and valid values for the port number are from 1 to 48.

The port-channel values are from 0 to 282; values from 257 to 282 are supported on the CSM and the FWSM only.

Examples

This example shows how to display the interface capabilities for a module:

Router> show interfaces capabilities module 6 

FastEthernet6/1 
Dot1x: yes 
Model: WS-X6248-RJ-45 
Type: 10/100BaseTX 
Speed: 10,100,auto 
Duplex: half,full 
Trunk encap. type: 802.1Q,ISL 
Trunk mode: on,off,desirable,nonegotiate 
Channel: yes 
Broadcast suppression: percentage(0-100) 
Flowcontrol: rx-(off,on),tx-(none) 
Membership: static 
Fast Start: yes 
QOS scheduling: rx-(1q4t), tx-(2q2t) 
CoS rewrite: yes 
ToS rewrite: yes 
Inline power: no 
SPAN: source/destination 
UDLD yes 
Link Debounce: yes 
Link Debounce Time: no 
Ports on ASIC: 1-12 
Port-Security: yes 
Router# 

This example shows how to display the interface capabilities for an interface:

Router? show interfaces fastethernet 4/1 capabilities 

FastEthernet4/1 
Model: WS-X6348-RJ-45 
Type: 10/100BaseTX 
Speed: 10,100,auto 
Duplex: half,full 
Trunk encap. type: 802.1Q,ISL 
Trunk mode: on,off,desirable,nonegotiate 
Channel: yes 
Broadcast suppression: percentage(0-100) 
Flowcontrol: rx-(off,on),tx-(none) 
Fast Start: yes 
QOS scheduling: rx-(1q4t), tx-(2q2t) 
CoS rewrite: yes 
ToS rewrite: yes 
Inline power: no 
SPAN: source/destination 

This example shows how to display the port-channel interface capabilities:

Router> show interfaces port-channel 12 capabilities

Port-channel12
  Model:                 NO IDPROM
  Type:                  unknown
  Speed:                 10,100,1000,auto
  Duplex:                half,full
  Trunk encap. type:     802.1Q,ISL
  Trunk mode:            on,off,desirable,nonegotiate
  Channel:               yes
  Broadcast suppression: percentage(0-100)
  Flowcontrol:           rx-(off,on),tx-(none)
  Fast Start:            yes
  QOS scheduling:        rx-(1q4t), tx-(1q4t)
  CoS rewrite:           yes
  ToS rewrite:           yes
  Inline power:          no
  SPAN:                  source/destination
Router# 

Related Commands

Command
Description

show interfaces

Displays the status and statistics for the interfaces in the chassis.


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 12 describes the significant fields shown in the display.

Table 12 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 interface, which is configurable under the interface. The default is FIFO.

Output queue

Number of packets in the output queue. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of 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 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 check (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 non integer 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 content engine 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

interface content-engine

Configures an interface for a CE network module and enters interface configuration mode.

show controllers content-engine

Displays controller information for CE network modules.


show interfaces counters nonzero

To get the counter information for ports which have non zero values, use the show interfaces counters nonzero command in user EXEC or privileged EXEC mode.

show interfaces counters nonzero [module number]

Syntax Description

module

(Optional) Limits display to interfaces on module.

number

The module number has a range from 1 to 6.


Command Default

This command has no default settings.

Command Modes

EXEC (>)
Privileged EXEC (#)

Command History

Release
Modification

12.2(18)SXF

This command was introduced for Cisco IOS Release 12.2(18)SXF.

12.2(32)SX

This command was integrated into Cisco IOS Release 12.2(32)SX.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(32)XJC

This command was integrated into Cisco IOS Release 12.2(32)XJC.


Usage Guidelines

Use the show interfaces counters nonzero command to get the counter information for ports which have non zero values.

Examples

The following example shows the output of show interfaces counters nonzero command. The output is displayed only if any one of the counters is non zero. The counters are checked for all the ports present in the router.

Router#sh interfaces counters nonzero