show gt64010 (7200)

.

.

.

show history

terminal history size Enables the command history feature for the current terminal session, or changes the size of the command history buffer for the current terminal session.

show idprom

The module {slot | slot/subslot [clei]} syntax designates either the slot location alone of the SIP in the chassis (to show information for the SIP only), or the slot location of the SIP and the subslot location of a SPA installed within the SIP (to display information for a SPA only). Valid values for slot depend on the chassis model (2???13), and valid values for subslot depend on the SIP type (such as 0???3 for a Cisco 7600 SIP-200 and Cisco 7600 SIP-400). The optional clei keyword specifies display of the Common Language Equipment Identification (CLEI) information for the specified SIP or SPA.

Use the show idprom backplane command to display the chassis serial number.

Use the transceiver slot/subslot/port form of the command to display information for transceivers installed in a SPA, where slot designates the location of the SIP, subslot designates the location of the SPA, and port designates the interface number.

The interface interface slot keyword and arguments supported on GBIC security-enabled interfaces have been replaced by the transceiver keyword option.

To specify LAN Gigabit Ethernet interfaces, use the show idprom transceiver slot/subslot

GigabitEthernet form of the command.

???To specify WAN Gigabit Ethernet interfaces, use the show idprom transceiver slot/subslot

GigabitEthernetWAN form of the command.

show idprom

This example shows how to display IDPROM information for power supply 1:

Router# show idprom power-supply 1

IDPROM for power-supply #1

(FRU is '110/220v AC power supply, 1360 watt') OEM String = 'Cisco Systems, Inc.'

Product Number = 'WS-CAC-1300W' Serial Number = 'ACP03020001'

Manufacturing Assembly Number = '34-0918-01' Manufacturing Assembly Revision = 'A0' Hardware Revision = 1.0

Current supplied (+) or consumed (-) = 27.460A

This example shows how to display detailed IDPROM information for power supply 1:

Router# show idprom power-supply 1 detail

IDPROM for power-supply #1

IDPROM image:

(FRU is '110/220v AC power supply, 1360 watt')

show idprom

CISCO-STACK-MIB SNMP OID = 22 *** end of power supply block ***

End of IDPROM image

This example shows how to display IDPROM information for the backplane:

Router# show idprom backplane

IDPROM for backplane #0

(FRU is 'Catalyst 6000 9-slot backplane') OEM String = 'Cisco Systems'

Product Number = 'WS-C6009' Serial Number = 'SCA030900JA'

Manufacturing Assembly Number = '73-3046-04' Manufacturing Assembly Revision = 'A0' Hardware Revision = 1.0

Current supplied (+) or consumed (-) = 0.000A

The following example shows sample output for a Cisco 7600 SIP-400 installed in slot 3 of the router:

Router# show idprom module 3

IDPROM for module #3

(FRU is '4-subslot SPA Interface Processor-400') OEM String = 'Cisco Systems'

Product Number = '7600-SIP-400' Serial Number = 'JAB0851042X'

Manufacturing Assembly Number = '73-8404-10' Manufacturing Assembly Revision = '09' Hardware Revision = 0.95

Current supplied (+) or consumed (-) = -6.31A

The following example shows sample output for the clei form of the command on a Cisco 7600 SIP-200 installed in slot 2 of the router:

Router# show idprom module 2 clei

The following example shows sample output for the detail form of the command on a Cisco 7600 SIP-400 installed in slot 3 of the router:

Router# show idprom module 3 detail

IDPROM for module #3

IDPROM image:

(FRU is '4-subslot SPA Interface Processor-400')

IDPROM image block #0:

block-signature = 0xABAB, block-version = 3, block-length = 160, block-checksum = 4600

*** common-block ***

IDPROM capacity (bytes) = 512 IDPROM block-count = 2 FRU type = (0x6003,1103)

OEM String = 'Cisco Systems'

show idprom

IDPROM image block #1:

block-signature = 0x6003, block-version = 2, block-length = 103, block-checksum = 2556

*** linecard specific block ***

mac base = 0012.4310.D840 mac_len = 128 num_processors = 1 epld_num = 0

epld_versions = 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

port numbers:

pair #0: type=00, count=00

pair #1: type=00, count=00

pair #2: type=00, count=00

pair #3: type=00, count=00

pair #4: type=00, count=00

pair #5: type=00, count=00

pair #6: type=00, count=00

pair #7: type=00, count=00 sram_size = 0 sensor_thresholds =

sensor #0: critical = 75 oC, warning = 60 oC

sensor #1: critical = 70 oC, warning = 55 oC

sensor #2: critical = 80 oC, warning = 65 oC

sensor #3: critical = 75 oC, warning = 60 oC

sensor #4: critical = -128 oC (sensor not present), warning = -128 oC (sensor not present)

sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (sensor not present)

sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (sensor not present)

sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (sensor not present)

max_connector_power = 3600 cooling_requirement = 35 ambient_temp = 55

*** end of linecard specific block ***

End of IDPROM image

The following example shows sample output for a 4-Port OC-3c/STM-1 ATM SPA installed in subslot 0 of the SIP installed in slot 5 of the router:

Router# show idprom module 5/0

show idprom

The following example shows sample output for the clei form of the command for a 4-Port

OC-3c/STM-1 POS SPA installed in subslot 3 of the SIP installed in slot 2 of the router:

Router# show idprom module 2/3 clei

The following example shows sample output for the detail form of the command for a 4-Port OC-3c/STM-1 POS SPA installed in subslot 3 of the SIP installed in slot 2 of the router:

Router# show idprom module 2/3 detail

show inventory

NAME: ???PSslot 1???, DESCR: ???GSR 12008 AC Power Supply???

PID: FWR-GSR8-AC-B , VID: V01, SN: CAB041999CW

Table 89 describes the fields shown in the display.

show inventory

For diagnostic purposes, the show inventory command can be used with the raw keyword to display every RFC 2737 entity including those without a PID, UDI, or other physical identification.

Note The raw keyword option is primarily intended for troubleshooting problems with the show inventory command itself.

Enter the show inventory command with an entity argument value to display the UDI information for a specific type of Cisco entity installed in the networking device. In this example, a list of Cisco entities that match the sfslot argument string is displayed.

Router# show inventory sfslot

NAME: ???sfslot 1???, DESCR: ???GSR 12008 Switch Fabric Card???

You can request even more specific UDI information using the show inventory command with an entity argument value that is enclosed in quotation marks. In this example, only the details for the entity that exactly matches the sfslot 1 argument string are displayed.

Router# show inventory ???sfslot 1???

show logging

28 message lines logged,

0 message lines rate-limited,

0 message lines dropped-by-MD,

xml disabled, sequence number disabled filtering disabled

Logging to 172.25.126.15 (tcp port 1307, audit disabled, authentication disabled, encryption disabled, link up),

28 message lines logged,

0 message lines rate-limited,

0 message lines dropped-by-MD,

xml disabled, sequence number disabled, filtering disabled Logging to 172.20.1.1 (udp port 514, audit disabled,

authentication disabled, encryption disabled, link up), 28 message lines logged,

0 message lines rate-limited,

0 message lines dropped-by-MD,

xml disabled, sequence number disabled filtering disabled

Log Buffer (1000000 bytes):

Table 90 describes the significant fields shown in the output for the two preceding examples.

show logging

Table 90 show logging Field Descriptions (continued)

The following example shows that syslog messages from the system buffer are included, with time stamps. In this example, the software image does not support XML formatting or ESM filtering of syslog messages.

Router# show logging

Syslog logging:enabled (2 messages dropped, 0 flushes, 0 overruns)

Console logging:disabled

Monitor logging:level debugging, 0 messages logged

Buffer logging:level debugging, 4104 messages logged

Trap logging:level debugging, 4119 message lines logged

Logging to 192.168.111.14, 4119 message lines logged

Log Buffer (262144 bytes):

Jul 11 12:17:49 EDT:%BGP-4-MAXPFX:No. of prefix received from 209.165.200.225 (afi 0) reaches 24, max 24

!THE FOLLOWING LINE IS A DEBUG MESSAGE FROM NTP.

!NOTE THAT IT IS NOT PRECEEDED BY THE % SYMBOL. Jul 11 12:17:48 EDT: NTP: Maxslew = 213866

Jul 11 15:15:41 EDT:%SYS-5-CONFIG:Configured from tftp://host.com/addc5505-rsm.nyiix

.Jul 11 15:30:28 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Up

show logging

.Jul 11 15:31:34 EDT:%BGP-3-MAXPFXEXCEED:No. of prefix received from 209.165.200.226 (afi 0):16444 exceed limit 375

.Jul 11 15:31:34 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Down BGP Notification sent

.Jul 11 15:31:34 EDT:%BGP-3-NOTIFICATION:sent to neighbor 209.165.200.226 3/1 (update malformed) 0 bytes

.

.

.

The software clock keeps an ???authoritative??? flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the ???authoritative??? flag is set, the flag prevents peers from synchronizing to the software clock.

Table 91 describes the symbols that precede the timestamp.

The following is sample output from the show logging summary command for a Cisco 12012 router. A number in the column indicates that the syslog contains that many messages for the line card. For example, the line card in slot 9 has 1 error message, 4 warning messages, and 47 notification messages.

Note For similar log counting on other platforms, use the show logging count command.

show logging

Table 92 describes the logging level fields shown in the display.

show logging history

snmp-server enable traps The [no] snmp-server enable traps syslog form of this command controls (enables or disables) the sending of system-logging messages to a network management station.

show logging system

show logging system

To display the System Event Archive (SEA) logging system disk, use the show logging system command in privileged EXEC mode.

show logging system [disk | size]

The following example shows how to display the SEA logging system disk:

Router# show logging system disk

SEA log disk: sup-bootdisk:

The following example shows how to display the current size of the SEA:

Router# show logging system size

SEA log size: 33554432 bytes

Table 95 describes the significant fields shown in the display.

show logging system

show logging xml

<logging-exception size="8192 bytes"></logging-exception> <count-and-timestamp-logging status="disabled"></count-and-timestamp-logging> <trap-logging level="informational" messages-lines-logged="35"></trap-logging>

<logging-to><dest id="0" ipaddr="10.2.3.4" message-lines-logged="1"><xml>disabled</xml><dest></logging-to>

<logging-to><dest id="1" ipaddr="192.168.2.1" message-lines-logged="1"><xml>enabled</xml><dest></logging-to>

<log-xml-buffer size="44444 bytes"></log-xml-buffer>

<ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time> 00:04:20</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg> <ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time> 00:04:41</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg>

Router#

Table 96 describes the significant fields shown in the displays.

show logging history Displays the contents of the SNMP syslog history table.

show memory

Cisco IOS Software Modularity

No optional keywords or arguments are supported for the show memory command when a Software Modularity image is running. To display details about PSOIX and Cisco IOS style system memory information when Software Modularity images are running, use the show memory detailed command.

The following is sample output from the show memory free command:

Router# show memory free

show memory

The output of the show memory free command contains the same types of information as the show memory output, except that only free memory is displayed, and the information is ordered by free list.

The first section of the display includes summary statistics about the activities of the system memory allocator. Table 97 describes the significant fields shown in the first section of the display.

The second section of the display is a block-by-block listing of memory use. Table 98 describes the significant fields shown in the second section of the display.

The show memory io command displays the free I/O memory blocks. On the Cisco 4000 router, this command quickly shows how much unused I/O memory is available.

The following is sample output from the show memory io command:

Router# show memory io

show memory

The following example displays details of a memory block overflow correction when the exception memory ignore overflow global configuration command is configured:

Router# show memory overflow

The report includes the amount of time since the last correction was made and the name of the file that logged the memory block overflow details.

The show memory sram command displays the free SRAM memory blocks. For the Cisco 4000 router, this command supports the high-speed static RAM memory pool to make it easier for you to debug or diagnose problems with allocation or freeing of such memory.

The following is sample output from the show memory sram command:

Router# show memory sram

The following example of the show memory command used on the Cisco 4000 router includes information about SRAM memory and I/O memory:

Router# show memory

The show memory summary command displays a summary of all memory pools and memory usage per Alloc PC (address of the system call that allocated the block).

The following is a partial sample output from the show memory summary command. This output shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see Table 97 and Table 98.

Router# show memory summary

show memory

Cisco IOS Software Modularity

The following is sample output from the show memory command when a Cisco IOS Software Modularity image is running.

Router# show memory

System Memory: 262144K total, 116148K used, 145996K free 4000K kernel reserved

Table 99 describes the significant fields shown in the display.

show memory allocating-process

show memory allocating-process

Table 101 describes the significant fields shown in the display.

show processes memory Displays memory used per process.

show memory dead

Table 102 describes the significant fields shown in the display.

show memory debug incremental

Note All memory leak detection commands invoke normal mode memory leak detection, except when the low memory option is specifically invoked by use of the lowmem keyword. In normal mode, if memory leak detection determines that there is insufficient memory to proceed in normal mode, it will display an appropriate message and switch to low memory mode.

The following example shows output from the show memory debug incremental command when entered with the allocations keyword:

Router# show memory debug incremental allocations

show memory debug incremental leaks summary Command Example

The following example shows output from the show memory debug incremental command when entered with the leaks and summary keywords:

Router# show memory debug incremental leaks summary

Adding blocks for GD...

show memory debug incremental status Command Example

The following example shows output from the show memory debug incremental command entered with the status keyword:

Router# show memory debug incremental status

Incremental debugging is enabled

Time elapsed since start of incremental debugging: 00:00:10

show memory debug incremental

show memory debug leaks

Table 103 describes the significant fields shown in the display.

show memory debug leaks chunks Command Example

The following example shows output from the show memory debug leaks chunks command:

Router# show memory debug leaks chunks

Adding blocks for GD...

show memory debug leaks

Table 104 describes the significant fields shown in the display.

show memory debug leaks largest Command Example

The following example shows output from the show memory debug leaks largest command:

Router# show memory debug leaks largest

Adding blocks for GD...

show memory debug leaks

The following example shows output from the second invocation of the show memory debug leaks largest command:

Router# show memory debug leaks largest

Adding blocks for GD...

show memory debug leaks summary Command Example

The following example shows output from the show memory debug leaks summary command:

show memory debug leaks

Table 105 describes the significant fields shown in the display.

show memory debug references

Table 106 describes the significant fields shown in the displays.

show memory debug unused

Table 107 describes the significant fields shown in the display.

show memory ecc

Table 108 describes the significant fields shown in the first section of the display.

show memory fast

Router>

The following example shows sample output from the show memory fast allocating-process command,

followed by sample output from the show memory fast allocating-process totals command:

show memory fast

--More-- <Ctrl+z>

The following example shows sample output from the show memory fast dead command:

Router#show memory fast dead

Router#

show memory fragment

The following is sample output from the show memory processor fragment detail command:

show memory multibus

show memory pci

show memory processor

Table 112 show memory processor Field Descriptions (continued)

Table 113 describes the significant fields shown in the display.

show memory processor

659CF6B0 0000000024 659CF678 659CF6FC 000 6698FFC8 659CF86C 6078A2CC Init 659CF86C 0000000024 659CF710 659CF8B8 000 659CF6B0 65ADB53C 6078A2CC Init 65ADB53C 0000000024 65ADB504 65ADB588 000 659CF86C 65ADFC38 6078A2CC Init 65ADFC38 0000000024 65ADFC00 65ADFC84 000 65ADB53C 65B6C504 6078A2CC Init 65B6C504 0000000024 65B6C4B8 65B6C550 000 65ADFC38 6593E924 6078A2CC Init 6593E924 0000000028 6593E8E8 6593E974 000 65B6C504 65CCB054 6078A2CC Init 65CCB054 0000000024 65CCB01C 65CCB0A0 000 6593E924 65CCBD98 6078A2CC Init 65CCBD98 0000000028 65CCBD60 65CCBDE8 000 65CCB054 65CCFB70 6078A2CC Init 65CCFB70 0000000024 65CCFB38 65CCFBBC 000 65CCBD98 65D0BB58 6078A2CC Init 65D0BB58 0000000024 65D0BB20 65D0BBA4 000 65CCFB70 65D0C5F0 6078A2CC Init 65D0C5F0 0000000024 65D0C5B8 65D0C63C 000 65D0BB58 65CFF2F4 6078A2CC Init 65CFF2F4 0000000024 65CFF2BC 65CFF340 000 65D0C5F0 6609B7B8 6078A2CC Init 6609B7B8 0000000036 6609AFC8 6609B810 000 65CFF2F4 660A0BD4 6078A2CC Init

Table 114 describes the significant fields shown in the display.

Table 115 describes the significant fields shown in the display.

show memory processor

show memory scan

show memory statistics history table

Time: 10:44:24.342

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 09:38:53.038

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 08:33:35.154

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 07:28:05.987

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 06:35:22.878

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 05:42:14.286

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 04:41:53.486

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 03:48:47.891

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 02:46:32.391

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 01:54:27.931

Used(b): 20717804 Largest(b): 381064952 Free blocks :189

Time: 01:02:05.535

Used(b): 20717804 Largest(b): 381064952 Free blocks :189

Maximum memory users for this period

Time: 00:00:17.936

Used(b): 21011192 Largest(b): 381064952 Free blocks :186

Maximum memory users for this period

History for I/O memory

Time: 15:48:56.809

Used(b): 7455520 Largest(b): 59370080 Free blocks :164

Time: 13:37:26.920

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 12:39:44.424

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

show memory statistics history table

Time: 11:46:25.137

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 10:44:24.344

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 09:38:53.040

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 08:33:35.156

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 07:28:05.985

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 06:35:22.877

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 05:42:14.285

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 04:41:53.485

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 03:48:47.889

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 02:46:32.389

Used(b): 7297744 Largest(b): 59797664 Free blocks :25

Time: 01:54:27.929

Used(b): 7308336 Largest(b): 59797664 Free blocks :23

Time: 01:02:05.533

Used(b): 7308336 Largest(b): 59797664 Free blocks :23

show memory transient

show microcode

show mls statistics

This example shows how to display the MLS statistics for a specific module:

Router# show mls statistics module 1

Statistics for Earl in Module 1

show mls statistics

show module

7Bypass

8Bypass

9Bypass Router#

This example shows how to display information for a specific module:

Router# show module 2

Router#

This example shows how to display version information:

Router# show module version

Fw : 6.3(1)

Sw : 7.5(0.30)CFW11

Router#

This example shows how to display module provisioning information:

Router# show module provision

show module

Router#

show monitor event-trace

show monitor event-trace

To display event trace messages for Cisco IOS software subsystem components, use the show monitor event-trace command in privileged EXEC mode.

show monitor event-trace [all-traces] [component {all | back hour:minute | clock hour:minute | from-boot seconds | latest | parameters}]

show monitor event-trace

3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Fail -> Down (from LC)

3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Down -> Up (from LC)

To display trace information for all components configured for event tracing on the networking device, enter the show monitor event-trace all-traces command. In this example, separate output is provided for each event, and message numbers are interleaved between the events.

Router# show monitor event-trace all-traces

Test1 event trace:

3667: 6840.016:Message type:3 Data=0123456789

3669: 6841.016:Message type:4 Data=0123456789

3671: 6842.016:Message type:5 Data=0123456789

3673: 6843.016:Message type:6 Data=0123456789

Test2 event trace:

3668: 6840.016:Message type:3 Data=0123456789

3670: 6841.016:Message type:4 Data=0123456789

3672: 6842.016:Message type:5 Data=0123456789

3674: 6843.016:Message type:6 Data=0123456789

SPA Component Example

The following is sample output from the show monitor event-trace component latest command for the spa component:

Router# show monitor event-trace spa latest

00:01:15.364: subslot 2/3: 4xOC3 POS SPA, TSM Event:inserted New state:wait_psm _ready

spa type 0x440

00:02:02.308: subslot 2/0: not present, TSM Event:empty New state:remove spa type 0x0, fail code 0x0(none)

00:02:02.308: subslot 2/0: not present, TSM Event:remove_complete New state:idle

00:02:02.308: subslot 2/1: not present, TSM Event:empty New state:remove spa type 0x0, fail code 0x0(none)

00:02:02.308: subslot 2/1: not present, TSM Event:remove_complete New state:idle

00:02:02.308: subslot 2/2: not present, TSM Event:empty New state:remove spa type 0x0, fail code 0x0(none)

00:02:02.308: subslot 2/2: not present, TSM Event:remove_complete New state:idle

00:02:02.312: subslot 2/3: not present(plugin 4xOC3 POS SPA), TSM Event:empty New state:remove

spa type 0x0, fail code 0x0(none)

00:02:02.312: subslot 2/3: not present, TSM Event:remove_complete New state:idle

Cisco Express Forwarding Component Examples

If you select Cisco Express Forwarding as the component for which to display event messages, you can use the following additional arguments and keywords: show monitor event-trace cef [events | interface | ipv6 | ipv4][all].

The following example shows the IPv6 or IPv4 events related to the Cisco Express Forwarding component. Each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.

Router# show monitor event-trace cef ipv6 all

show monitor event-trace

In the following example, all event trace messages for the Cisco Express Forwarding component are displayed:

Router# show monitor event-trace cef events all

The following example shows Cisco Express Forwarding interface events:

Router# show monitor event-trace cef interface all

Cisco Express Forwarding Component Examples for Cisco 10000 Series Routers Only

The following example shows the IPv4 events related to the Cisco Express Forwarding component. Each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.

Router# show monitor event-trace cef ipv4 all

In the following example, all event trace message for the Cisco Express Forwarding component are displayed:

Router# show monitor event-trace cef events all

show monitor event-trace

The following examples show Cisco Express Forwarding interface events:

Router# show monitor event-trace cef interface all

CFD Component for Cisco IOS Release 12.4(9)T

To troubleshoot errors in an encryption datapath, enter the show monitor event-trace cfd all command. In this example, events are shown separately, each beginning with a time stamp, followed by data from the error trace buffer. Cisco Technical Assistence Center (TAC) engineers can use this information to diagnose the cause of the errors.

Note If no packets have been dropped, this command does not display any output.

Router# show monitor event-trace cfd all

00:00:42.452: 450000B4 00060000 FF33B306 02020203 02020204 32040000 F672999C 00000001 7A7690C2 A0A4F8BC E732985C D6FFDCC8 00000001 C0902BD0 A99127AE 8EAA22D4

00:00:44.452: 450000B4 00070000 FF33B305 02020203 02020204 32040000 F672999C 00000002 93C01218 2325B697 3C384CF1 D6FFDCC8 00000002 BFA13E8A D21053ED 0F62AB0E

00:00:46.452: 450000B4 00080000 FF33B304 02020203 02020204 32040000 F672999C 00000003 7D2E11B7 A0BA4110 CC62F91E D6FFDCC8 00000003 7236B930 3240CA8C 9EBB44FF

00:00:48.452: 450000B4 00090000 FF33B303 02020203 02020204 32040000 F672999C 00000004 FB6C80D9 1AADF938 CDE57ABA D6FFDCC8 00000004 E10D8028 6BBD748F 87F5E253

00:00:50.452: 450000B4 000A0000 FF33B302 02020203 02020204 32040000 F672999C 00000005 697C8D9D 35A8799A 2A67E97B D6FFDCC8 00000005 BC21669D 98B29FFF F32670F6

00:00:52.452: 450000B4 000B0000 FF33B301 02020203 02020204 32040000 F672999C 00000006 CA18CBC4 0F387FE0 9095C27C D6FFDCC8 00000006 87A54811 AE3A0517 F8AC4E64

show monitor session

show monitor session

To display information about the ERSPAN, SPAN and RSPAN sessions, use the show monitor session command in user EXEC mode.

show monitor session [range session-range | local | remote | all | session]

show monitor session [erspan-destination | erspan-source | egress replication-mode capability| detail]

show monitor session

show monitor session

-------------------------------------------------------

-------------------------------------------------------

Router#

This example shows how to display information about the destination ERSPAN sessions only:

Router# show monitor session erspan-destination

This example shows how to display detailed information about the destination ERSPAN sessions only:

Router# show monitor session erspan-destination detail

This example shows how to display information about the source ERSPAN sessions only:

Router# show monitor session erspan-source

Session 1

show monitor session

This example shows how to display detailed information about the source ERSPAN sessions only:

Router# show monitor session erspan-source detail

This example shows how to display the operational mode and configured mode of the session and module session capabilities:

Router# show monitor session egress replication-mode capability

Session 65 Type Local Session

show msfc

pair #6: type=00, count=00

pair #7: type=00, count=00 sram_size = 4096 sensor_thresholds =

r not present)

sensor #3: critical = -128 oC (sensor not present), warning = -128 oC (senso r not present)

sensor #4: critical = -128 oC (sensor not present), warning = -128 oC (senso r not present)

sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (senso r not present)

sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (senso r not present)

sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (senso r not present)

*** end of linecard specific block ***

End of IDPROM image

Router#

Router# show msfc fault

Router#

Router# show msfc netint

Network IO Interrupt Throttling: throttle count=0, timer count=0 active=0, configured=1

netint usec=3999, netint mask usec=400

show parser dump

redirection to a file using the | redirect URL syntax at the end of the command is highly recommended. (See the documentation for the show <command> redirect command for more information on using this command extension.)

Output for this command will show the syntax options for all commands available in the specified mode. The preceding number shows the privilege level associated with that command. For example, the line

15 type dhcp

indicates that the type dhcp command has a privilege level of 15 assigned to it. For information about privilege levels, see the ???Configuring Passwords and Privileges??? chapter in the Cisco IOS Security Configuration Guide.

Any given command-line string should indicate the full syntax needed to make the command complete and valid. In other words, the command line string ends where the carriage return (Enter) could be entered, as indicated in command-line help by the <cr> syntax. You will typically see multiple forms of a command, each showing a valid syntax combination. For example, each of the following syntax combinations, as seen in the output of the show parser dump rtr | include dhcp command, are valid commands:

type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id <string> type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id <string> type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask <ipmask>

type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> type dhcp dest-ipaddr <address> source-ipaddr <address>

type dhcp dest-ipaddr <address> type dhcp

Use of the show command extensions | begin, | include, and | exclude are recommended for this command, as these extensions allow you to filter the output to show only the commands you are interested in. The redirection extensions | redirect, | append, and | tee allow you to redirect the output of this command to local or remote storage as a file.

As with most show commands, you can typically exit from the --More-- prompt back to EXEC mode using Ctrl-Z. For some connections, Ctrl-Shift-6 (Ctrl^) or Ctrl-Shift-6-X should be used instead.

show parser dump

In the following example, only commands in RTR Configuration mode are shown:

show parser dump

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id <string>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id <string>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask <ipmask>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> 15 type dhcp dest-ipaddr <address> source-ipaddr <address>

15 type dhcp dest-ipaddr <address>

15 type dhcp

15 type dns target-addr <string> name-server <address> source-ipaddr <address> source-port <1-65535>

15 type dns target-addr <string> name-server <address> source-ipaddr <address> 15 type dns target-addr <string> name-server <address>

15 type pathEcho protocol ipIcmpEcho <address> source-ipaddr <address> 15 type pathEcho protocol ipIcmpEcho <address>

15 type pathJitter dest-ipaddr <address> source-ipaddr <address> 15 type pathJitter dest-ipaddr <address> num-packets <1-100>

15 type pathJitter dest-ipaddr <address> interval <1-1000> 15 type pathJitter dest-ipaddr <address> targetOnly

15 type pathJitter dest-ipaddr <address>

15 type slm frame-relay pvc

15 type slm controller T1 <controller>

15 type slm controller E1 <controller>

15 type slm controller T3 <controller>

15 type slm controller E3 <controller>

15 exit

In the following example, only those commands in RTR Configuration mode containing the keyword dhcp are shown:

Router# show parser dump rtr | include dhcp

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id <string>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id <string>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask <ipmask>

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> 15 type dhcp dest-ipaddr <address> source-ipaddr <address>

15 type dhcp dest-ipaddr <address>

15 type dhcp Router#

The following example shows how the extend keyword displays the syntax descriptions that match those shown using the ? command-line help:

Router# show parser dump rtr extend

Mode Name :rtr

15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>

dest-port : Destination Port

<1-65535> : Port Number

source-ipaddr : Source address

show parser dump

enable : Enable control packets exchange (default)

.

.

.

! Ctrl-Z used here to interrupt output and return to CLI prompt.

Router# config terminal

Enter configuration commands, one per line. End with CNTL/Z. Router(config)# rtr 1

Router(config-rtr)# type udpEcho ? dest-ipaddr Destination address

Router(config-rtr)# type udpEcho dest-ipaddr ?

Hostname or A.B.C.D IP address or hostname

Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME ? dest-port Destination Port

Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port ?

<1-65535> Port Number

Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port 1 ?

Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port 1 control ?

In the following example, show parser dump output is redirected to a file on a remote TFTP server:

show parser dump exec extend | redirect tftp://209.165.200.225/userdirectory/123-exec-commands.txt

show parser macro

switchport mode trunk switchport nonegotiate

#Configure qos to trust this interface auto qos voip trust

mls qos trust dscp

#Ensure fast access to the network when enabling the interface.

#Ensure that switch devices cannot become active on the interface. spanning-tree portfast

spanning-tree bpduguard enable

The following example shows how to list the Cisco-provided smart port macros:

Router# show parser macro brief | include default

show parser statistics

In the following example the show parser statistics command is used to compare the parse-time of a large configuration file with the Parser Cache feature disabled and enabled. In this example, a configuration file with 1484 access list commands is loaded into the running configuration.

Router# configure terminal

!parser cache is disabled Router(config)# no parser cache

!configuration file is loaded into the running configuration Router# copy slot0:acl_list running-config

.

.

.

Router# show parser statistics

Last configuration file parsed:Number of Commands:1484, Time:1272 ms

Parser cache:disabled, 0 hits, 2 misses

!the parser cache is reenabled Router(config)# parser cache

!configuration file is loaded into the running configuration Router# copy slot0:acl_list running-config

.

.

.

Router# show parser statistics

Last configuration file parsed:Number of Commands:1484, Time:820 ms

Parser cache:enabled, 1460 hits, 26 misses

show parser statistics

These results show an improvement to the load time for the same configuration file from

1272 milliseconds (ms) to 820 ms when the Parser Cache feature was enabled. As indicated in the ???hits??? field of the show command output, 1460 commands were able to be parsed more efficiently by the parser cache.

show pci

(0x08): cfccid = 0x06040002

(0x0C): cfpmlt = 0x00011810

(0x18): cfsmlt = 0x18000100

(0x1C): cfsis = 0x02809050

(0x20): cfmla = 0x4AF04880

(0x24): cfpmla = 0x4BF04B00

(0x40): cfseed = 0x00100000

(0x44): cfstwt = 0x00008020

.

.

.

show pci hardware

show platform

show platform

To display platform information, use the show platform command privileged EXEC mode.

show platform {buffers | copp rate-limit {arp | dhcp | atm-oam | ethernet-oam | pppoe-discovery | all} | np copp [ifnum] [detail] | eeprom | fault | hardware capacity | hardware pfc mode | internal-vlan | netint | software ipv6-multicast connected | tech-support ipmulticast group-ip-addr src-ip-addr | tlb}

show platform

Router#

Cisco 7600 Series Routers with Cisco 7600 SIP-400

This example shows how to display the list of interfaces on which a rate limiter is active for Address Resolution Protocol (ARP), along with the count of confirmed and exceeded packets for the rate limiter.

Router# show platform copp rate-limit arp

Rate limiter Information for Protocol arp:

show platform

Table 120 describes the significant fields shown in the display.

Table 120 show platform copp rate-limit Field Descriptions

This example shows how to display CPU EEPROM information:

Router# show platform eeprom

MSFC CPU IDPROM:

IDPROM image:

show platform

mac base = 0005.9A3A.7E9C mac_len = 0 num_processors = 2 epld_num = 2

epld_versions = 0001 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

show platform

This example shows how to display fault-date information:

Router# show platform fault

Fault History Buffer:

s72033_rp Software (s72033_rp-JSV-M), Experimental Version 12.2(20030331:071521) [kkuttuva-CSCea55513-const2 120]

Compiled Mon 31-Mar-03 21:58 by kkuttuva

This example shows how to display the PFC-operating mode:

Router# show platform hardware pfc mode

PFC operating mode : PFC3A

Router#

This example shows how to display platform net-interrupt information:

Router# show platform netint

Network IO Interrupt Throttling: throttle count=0, timer count=0 active=0, configured=1

netint usec=3999, netint mask usec=800 inband_throttle_mask_hi = 0x0 inband_throttle_mask_lo = 0x800000 Router#

This example shows how to display TLB-register information:

Router# show platform tlb

show platform hardware capacity

The show platform hardware capacity cpu command displays the following information:

???CPU utilization for the last 5 seconds (busy time and interrupt time), the percentage of the last 1-minute average busy time, and the percentage of the last 5-minute average busy time.

???Processor memory total available bytes, used bytes, and percentage used.

???I/O memory total available bytes, used bytes, and percentage used.

The show platform hardware capacity eobc command displays the following information:

???Transmit and receive rate

???Packets received and packets sent

???Dropped received packets and dropped transmitted packets

The show platform hardware capacity forwarding command displays the following information:

???The total available entries, used entries, and used percentage for the MAC tables.

???The total available entries, used entries, and used percentage for the FIB TCAM tables. The display is done per protocol base.

???The total available entries, used entries, and used percentage for the adjacency tables. The display is done for each region in which the adjacency table is divided.

???The created entries, failures, and resource usage percentage for the NetFlow TCAM and ICAM tables.

???The total available entries and mask, used entries and mask, reserved entries and mask, and entries and mask used percentage for the ACL/QoS TCAM tables. The output displays the available, used, reserved, and used percentage of the labels. The output displays the resource of other hardware resources that are related to the ACL/QoS TCAMs (such as available, used, reserved, and used percentage of the LOU, ANDOR, and ORAND).

???The available, used, reserved, and used percentage for the CPU rate limiters.

The show platform hardware capacity interface command displays the following information:

???Tx/Rx drops???Displays the sum of transmit and receive drop counters on each online module (aggregate for all ports) and provides the port number that has the highest drop count on the module.

???Tx/Rx per port buffer size???Summarizes the port-buffer size on a per-module basis for modules where there is a consistent buffer size across the module.

The show platform hardware capacity monitor command displays the following SPAN information:

???The maximum local SPAN sessions, maximum RSPAN sessions, maximum ERSPAN sessions, and maximum service module sessions.

???The local SPAN sessions used/available, RSPAN sessions used/available, ERSPAN sessions used/available, and service module sessions used/available.

The show platform hardware capacity multicast command displays the following information:

???Multicast Replication Mode: ingress and egress IPv4 and IPv6 modes.

???The MET table usage that indicates the total used and the percentage used for each module in the system.

???The bidirectional PIM DF table usage that indicates the total used and the percentage used.

The show platform hardware capacity system command displays the following information:

???PFC operating mode (PFC Version: PFC3A, PFC3B, unknown, and so forth)

???Supervisor redundancy mode (RPR, RPR+, SSO, none, and so forth)

show platform hardware capacity

???Module-specific switching information, including the following information:

???Part number (WS-SUP720-BASE, WS-X6548-RJ-45, and so forth)

???Series (supervisor engine, fabric, CEF720, CEF256, dCEF256, or classic)

???CEF Mode (central CEF, dCEF)

The show platform hardware capacity vlan command displays the following VLAN information:

???Total VLANs

???VTP VLANs that are used

???External VLANs that are used

???Internal VLANs that are used

???Free VLANs

This example shows how to display EOBC-related statistics for the route processor, the switch processor, and the DFCs in the Cisco 7600 series router:

Router# show platform hardware capacity eobc

This example shows how to display the current and peak switching utilization:

Router# show platform hardware capacity fabric

Switch Fabric Resources

show platform hardware capacity

Router#

This example shows how to display information about the total capacity, the bytes used, and the percentage that is used for the Flash/NVRAM resources present in the system:

Router# show platform hardware capacity flash

This example shows how to display the capacity and utilization of the EARLs present in the system:

Router# show platform hardware capacity forwarding

show platform hardware capacity

Router#

This example shows how to display the interface resources:

Router# show platform hardware capacity interface

This example shows how to display SPAN information:

Router# show platform hardware capacity monitor

This example shows how to display the capacity and utilization of resources for Layer 3 multicast functionality:

Router# show platform hardware capacity multicast

show platform hardware capacity

IPv6 replication mode: ingress

Bi-directional PIM Designated Forwarder Table usage: 4 total, 0 (0%) used

Router#

This example shows how to display information about the system power capacities and utilizations:

Router# show platform hardware capacity power

Power Resources

Power supply redundancy mode: administratively combined

operationally combined System power: 1922W, 0W (0%) inline, 1289W (67%) total allocated

Powered devices: 0 total Router#

This example shows how to display the capacity and utilization of QoS policer resources per EARL in the Cisco 7600 series router:

Router# show platform hardware capacity qos

Router#

This example shows how to display information about the key system resources:

Router# show platform hardware capacity system

System Resources

PFC operating mode: PFC3BXL

Supervisor redundancy mode: administratively rpr-plus, operationally rpr-plus

This example shows how to display VLAN information:

Router# show platform hardware capacity vlan

VLAN Resources

VLANs: 4094 total, 10 VTP, 0 extended, 0 internal, 4084 free

Router#

show platform software filesystem

14096 Apr 01 2008 13:34:30 +00:00 /bootflash/

216384 Dec 04 2007 04:32:46 +00:00 /bootflash/lost+found

34096 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh

4963 Dec 04 2007 06:06:16 +00:00 /bootflash/.ssh/ssh_host_key

5627 Dec 04 2007 06:06:16 +00:00 /bootflash/.ssh/ssh_host_key.pub

61675 Dec 04 2007 06:06:18 +00:00 /bootflash/.ssh/ssh_host_rsa_key

7382 Dec 04 2007 06:06:18 +00:00 /bootflash/.ssh/ssh_host_rsa_key.pub

8668 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh/ssh_host_dsa_key

9590 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh/ssh_host_dsa_key.pub

104096 Dec 04 2007 06:06:36 +00:00 /bootflash/.rollback_timer

114096 Mar 18 2008 17:31:17 +00:00 /bootflash/.prst_sync

124096 Dec 04 2007 04:34:45 +00:00 /bootflash/.installer

13205951180 Mar 18 2008 17:23:03 +00:00 /bootflash/asr1000rp1-advipservicesk

1446858444 Mar 18 2008 17:28:55 +00:00 /bootflash/asr1000rp1-espbase.02.01.

1520318412 Mar 18 2008 17:28:56 +00:00 /bootflash/asr1000rp1-rpaccess-k9.02

1622266060 Mar 18 2008 17:28:57 +00:00 /bootflash/asr1000rp1-rpbase.02.01.0

1721659852 Mar 18 2008 17:28:57 +00:00 /bootflash/asr1000rp1-rpcontrol.02.0

1845934796 Mar 18 2008 17:28:58 +00:00 /bootflash/asr1000rp1-rpios-advipser

1934169036 Mar 18 2008 17:28:59 +00:00 /bootflash/asr1000rp1-sipbase.02.01.

2022067404 Mar 18 2008 17:29:00 +00:00 /bootflash/asr1000rp1-sipspa.02.01.0

217180 Mar 18 2008 17:29:00 +00:00 /bootflash/packages.conf

461897728 bytes available (419782656 bytes used)

The following example displays information only about the bootflash file system itself, such as file system type and access permissions:

Router# show platform software filesystem bootflash: details

Filesystem: bootflash

Filesystem Path: /bootflash

Filesystem Type: ext2

Mounted: Read/Write

Table 121 describes the significant fields shown in the displays of file system information.

Table 121 show platform software filesystem Field Descriptions

show platform software filesystem

show platform software memory

show platform software memory

To display memory information for the specified process, use the show platform software memory command in privileged EXEC or diagnostic mode.

show platform software memory [database | messaging] {chassis-manager slot | cpp-control-process process | cpp-driver process | cpp-ha-server process | cpp-service-process process | forwarding-manager slot | host-manager slot | interface-manager slot | ios slot | logger slot | pluggable-services slot | shell-manager slot}

process values are:

??? cpp active???Active CPPDriver process

??? cpp standby???Standby CPP Driver process

The information displayed is for internal debugging purposes only.

show platform software memory

forwarding-manager Displays memory information for the Forwarding Manager process in the

show platform software memory

interface-manager slot Displays memory information for the Interface Manager process in the specified slot. Possible slot values are:

show platform software memory

The following example displays abbreviated (brief keyword) memory information for the Chassis Manager process for Cisco ASR 1000 Series ESP slot 0:

Router# show platform software memory chassis-manager f0 brief

moduleallocated requested allocs frees

------------------------------------------------------------------------

show platform software memory

Table 123 describes the significant fields shown in the brief keyword display.

Table 123 show platform software memory brief Field Descriptions

show platform software mount

Users may be requested to execute this command to collect information about the underlying configuration of the platform software.

The RP output can differ depending on how the router was booted, and whether there are USB devices inserted.

The SIP and ESP output can differ depending on whether the chassis is a dual or single RP.

The following example displays mounted file systems for the Cisco ASR 1000 Series ESP in ESP slot 0:

The following example displays mounted file systems for the active Cisco ASR 1000 Series RP:

show platform software mount

Table 124 describes the significant fields shown in the SIP slot (0, 1, or 2) displays.

Table 124 show platform software mount SIP slot Field Descriptions

The following example displays abbreviated (brief keyword) mounted file system information for Cisco ASR 1000 Series SIP slot 0:

Mount point: /dev/mtdblock1

show platform software mount

Mount point: automount(pid3199)

Location : /misc1

Options : rw,fd=5,pgrp=3199,timeout=60,minproto=2,maxproto=4,indirect

Table 125 describes the significant fields shown in the brief keyword display.

Table 125 show platform software mount brief Field Descriptions

show platform software process list

Table 126 describes the significant fields shown in the display.

Table 126 show platform software process list Field Descriptions

show platform software process list

Table 126 show platform software process list Field Descriptions (continued)

The following example displays information about a specific named process for Cisco ASR 1000 Series SIP slot 0:

Router# show platform software process list 0 name sleep

Name: sleep

The following example displays information about a specific process identifier for Cisco ASR 1000 Series SIP slot 0:

Router# show platform software process list 0 process-id 1

Table 127 describes the significant fields shown in the name and process-id keyword displays.

Table 127 show platform software process list name and process-id Field Descriptions

show platform software process list

Table 127 show platform software process list name and process-id Field Descriptions (continued)

The following example displays process summary information for Cisco ASR 1000 Series SIP slot 0:

Router# show platform software process list 0 summary

Total number of processes: 54

Table 128 describes the significant fields shown in the summary keyword display.

Table 128 show platform software process list summary Field Descriptions

show platform software process list

Table 128 show platform software process list summary Field Descriptions (continued)

show platform software process list

Table 128 show platform software process list summary Field Descriptions (continued)

show platform software tech-support

The following example creates a technical support information tar file for the boot flash memory file system on the active RP:

Router# show platform software tech-support file bootflash:tech_support_output.tgz

Running tech support command set; please wait...

Creating file 'bootflash:target_support_output.tgz.tgz' ...

File 'bootflash:target_support_output.tgz.tgz' created successfully

The following example creates a technical support information tar file for the hard disk file system on the active RP:

Router# show platform software tech-support file harddisk:tech_support_output.tgz

Running tech support command set; please wait...

Creating file 'harddisk:tech_support_ouput.tgz.tgz' ...

File 'harddisk:tech_support_ouput.tgz.tgz' created successfully

show power

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

Valid values for vlan-id are from 1 to 4094.

The Inline power field in the show power output displays the inline power that is consumed by the modules. For example, this example shows that module 9 has consumed 0.300 A of inline power:

show power

exceeded)

Router>

This example shows how to display the power status for all FRU types:

Router# show power status all

This example shows how to display the power status for a specific module:

Router# show power status module 1

This example shows how to display the power status for a specific power supply:

Router# show power status power-supply 1

This example displays information about the high-capacity power supplies:

Router# show power status power-supply 2

Router#

This example shows how to display the total power that is available from the power supplies:

Router# show power total

system power total = 27.460A Router#

This example shows how to display the total power that is budgeted for powered-on items:

Router# show power used

system power used = -6.990A Router#

This command shows how to display the inline power status on the interfaces:

Router# show power inline

show power

. <Output truncated>

This command shows how to display the inline power status for a specific module:

Router# show power inline mod 7

show processes

CPU utilization for five seconds: 21%/0%; one minute: 2%; five minutes: 2%

Table 129 describes the fields shown in the display.

show processes

Note Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after a large number of invocations or a reasonable, measured run time.

For a list of process descriptions, see http://www.cisco.com/warp/public/63/showproc_cpu.html.

The following is sample output from the show processes history command:

Router# show processes history

PID Exectime(ms) Caller PC Process Name 312 0x0 Exec

160 0x603F4DEC GraphIt

210 0x603CFEF4 TTY Background

220 0x6042FD7C Per-Second Jobs

670 0x6015CD38 SMT input

390 0x60178804 FBM Timer

160 0x603F4DEC GraphIt

210 0x603CFEF4 TTY Background

220 0x6042FD7C Per-Second Jobs

160 0x603F4DEC GraphIt

210 0x603CFEF4 TTY Background

220 0x6042FD7C Per-Second Jobs

670 0x6015CD38 SMT input

390 0x60178804 FBM Timer

240 0x60425070 Compute load avgs

110 0x605210A8 ARP Input

--More--

Table 130 describes the significant fields shown in the display.

The following is sample output from the show processes process-id command:

show processes

Age: 662314 msec, Runtime: 3841 msec

State: Running, Priority: Normal

Table 131 describes the fields shown in the display.

Cisco IOS Software Modularity

The following is sample output from the show processes command when a Cisco IOS Software Modularity image is running:

Router# show processes

show processes

Table 132 describes the significant fields shown in the display.

show processes memory Displays amount of system memory used per system process.

show processes cpu

The following is sample output of the one-hour portion of the output. The Y-axis of the graph is the CPU utilization. The X-axis of the graph is the increment within the time period displayed in the graph. This example shows the individual minutes during the previous hour. The most recent measurement is on the left of the X-axis.

Router# show processes cpu history

!--- One minute output omitted

6665776865756676676666667667677676766666766767767666566667

6378016198993513709771991443732358689932740858269643922613

100

show processes cpu

!--- 72-hour output omitted

The top two rows, read vertically, display the highest percentage of CPU utilization recorded during the time increment. In this example, the CPU utilization for the last minute recorded is 66 percent. The device may have reached 66 percent only once during that minute, or it may have reached 66 percent multiple times. The device records only the peak reached during the time increment and the average over the course of that increment.

The following is sample output from the show processes cpu command that shows an ARP probe process:

Router# show processes cpu | include ARP

show processes cpu

Note Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after several invocations or a reasonable, measured run time.

Cisco IOS Software Modularity

The following is sample output from the show processes cpu command when a Software Modularity image is running:

Router# show processes cpu

Total CPU utilization for 5 seconds: 99.6%; 1 minute: 98.5%; 5 minutes: 85.3%

Table 134 describes the significant fields shown in the display.

show processes cpu

Table 134 show processes cpu (Software Modularity) Field Descriptions

The following is partial sample output from the show processes cpu command with the detailed keyword when a Software Modularity image is running:

Router# show processes cpu detailed

show processes cpu

.

.

Table 135 describes the significant fields shown in the display.

show processes cpu

show processes interrupt mask buffer

show processes interrupt mask detail

show processes memory

show processes memory

show processes memory

Cisco IOS Software Modularity

The system memory followed by a one-line summary of memory information about each Software Modularity process is displayed.

show processes memory

show processes memory

???show processes memory Command for Releases Prior to 12.3(11)T, 12.2(28)S, and 12.0(30)S

???show processes memory Command for Cisco IOS Software Modularity

show processes memory Command for Releases Prior to 12.3(7)T, 12.2(22)S, and 12.0(28)S

The following is sample output from the show processes memory command:

Router# show processes memory

Table 136 describes the significant fields shown in the display.

show processes memory

The following is sample output from the show processes memory command when the sorted keyword is used. In this case, the output is sorted by the ???Holding??? column, from largest to smallest.

Router# show processes memory sorted

--More--

The following is sample output from the show processes memory command when a Process ID (process-id) is specified:

Router# show processes memory 1

Process ID: 1

Process Name: Chunk Manager

Total Memory Held: 8428 bytes

show processes memory

I/O memory holding = 0 bytes

show processes memory Command for Releases Prior to 12.3(11)T, 12.2(28)S, and 12.0(30)S

The following example shows the output of the show processes memory command before the changes to the summary information were made. Note that the ???Total:??? in the show processes summary command indicates total memory for all memory pools; in this example, the show processes memory Total of 35423840 can be obtained by adding the Processor and I/O totals shown in the output of the show memory summary command. Note also that the show processes memory sorted command lists the Total Processor Memory (matches the show memory summary Processor Total, but the show processes memory command (without the sorted keyword) lists the Total for all memory pools (Processor plus I/O memory).

Router# show version | include IOS

Cisco IOS Software, 3600 Software (C3660-BIN-M), Version 12.3(9)

Router# show memory summary

.

.

.

Router# show processes memory

Router# show processes memory sorted

Router# show version | include IOS

Cisco IOS Software, 3600 Software (c3660-p-mz), Version 12.0(29)S,

Router# show memory summary

show processes memory

show processes memory Command for Cisco IOS Software Modularity

The following is sample output from the show processes memory command when a Cisco IOS Software Modularity image is running:

Router# show processes memory

System Memory : 262144K total, 113672K used, 148472K free

show processes memory

Table 137 describes the significant fields shown in the display.

The following is sample output from the show processes memory command with details about the memory of the process named cdp2.iosproc:

Router# show processes memory detailed cdp2.iosproc

System Memory : 262144K total, 113460K used, 148684K free

Process sbin/cdp2.iosproc, type IOS, PID = 12329

640K total, 4K text, 4K data, 32K stack, 600K dynamic

Memory Summary for TaskID = 1

Holding = 10032

The following is sample output from the show processes memory command with details about the memory of process 12322 and the task with the ID of 1:

Router# show processes memory detailed 12322 taskid 1

System Memory : 262144K total, 113456K used, 148688K free

Process sbin/c7200-p-blob, type IOS, PID = 12322

show processes memory

0x74175060 160 1

Table 138 describes the significant fields shown in the display that are different from Table 137 on page 855.

The following is sample output from the show processes memory command with details about the memory of POSIX process ID 234567 with summary process memory usage per allocator:

Router# show processes memory detailed 234567 alloc-summary

System Memory : 262144K total, 113672K used, 148472K free

Allocated Blocks

Address Usize Size Caller 0x0806C358 0x00000478 0x000004D0 0x721C7290 0x0806D1E0 0x00000128 0x00000130 0x72B90248 0x0806D318 0x00003678 0x000036E0 0x72B9820C 0x0806D700 0x000002A0 0x000002C0 0x72B8EB58 0x0806D770 0x00000058 0x00000060 0x72BA5488 0x0806D7D8 0x000000A0 0x000000B0 0x72B8D228 0x0806D8A8 0x00000200 0x00000208 0x721A728C 0x0806FF78 0x00000068 0x00000070 0x72BA78EC 0x08071438 0x0000005C 0x00000068 0x72B908A8 0x08071508 0x0000010E 0x00000120 0x72BA7AFC 0x08072840 0x000000A8 0x000000C0 0x7270A060 0x08072910 0x0000010C 0x00000118 0x7273A898 0x08072A30 0x000000E4 0x000000F0 0x72749074 0x08072B28 0x000000B0 0x000000B8 0x7276E87C 0x08072BE8 0x0000006C 0x00000078 0x727367A4 0x08072C68 0x000000B8 0x000000C0 0x7271E2A4 0x08072D30 0x000000D0 0x000000D8 0x7273834C 0x08072E10 0x00000250 0x00000258 0x72718A70 0x08073070 0x000002F4 0x00000300 0x72726484 0x08073378 0x000006A8 0x000006B0 0x73EA4DC4 0x08073A30 0x00000060 0x00000068 0x7352A9F8 0x08073B38 0x00000068 0x00000070 0x72B92008 0x08073BB0 0x00000058 0x00000060 0x72B9201C 0x08073EB8 0x00002FB4 0x000031C0 0x08026FEC 0x08074028 0x000020B8 0x000020C0 0x72709C9C 0x08077400 0x000000A0 0x000000A8 0x721DED94 0x08078028 0x000022B8 0x000022C0 0x727446B8 0x0807C028 0x00002320 0x00002328 0x72B907C4

Free Blocks

show processes memory

show region

show region

To display valid memory regions (memory mapping) in use on your system, use the show region command in Privileged EXEC mode.

show region [address hex-address]

To use the show region command to troubleshoot a bus error, note the memory location address from the show version command, the show context command, or from the system error message that alerted you to the bus error. The show region command can then be used to determine if that address is a valid memory location.

For example, in the output of the show version command after a system restart casued by a bus error, you will see output similar to ???System restarted by bus error at PC 0x30EE546, address 0xBB4C4.??? In this case, the memory location that the router tried to access is 0xBB4C4. If the address falls within one of the ranges in the show region output, it means that the router was accessing a valid memory address, but the hardware corresponding to that address is not responding properly. This indicates a hardware problem.

show region

If the address reported by the bus error does not fall within the ranges displayed in the show region output, this means that the router was trying to access an address that is not valid. This indicates that it is a Cisco IOS software problem.

More detailed information is available on Cisco.com in Tech Note #7949, Troubleshooting Bus Error Crashes.

show registry

show registry

To display the function registry information when Cisco IOS or Cisco IOS Software Modularity images are running, use the show registry command in user EXEC or privileged EXEC mode.

Cisco IOS Software

show registry

--

Registry 23: ATM Registry Service 23/0:

Service 23/1:

Service 23/2:

Service 23/3:

Service 23/4:

Service 23/5:

Service 23/6:

Service 23/7:

Service 23/8:

Service 23/9:

Service 23/10:

Service 23/11:

Service 23/12:

Service 23/13:

Service 23/14:

.

.

.

Registry 25: ATM routing Registry Service 25/0:

Table 140 describes the significant fields shown in the display.

Table 140 show registry brief (Cisco IOS) Field Descriptions

show registry

Cisco IOS Software Modularity

The following is partial sample output from the show registry command when running a software Modularity image:

Router# show registry

Registry information for ios-base:1:

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

Table 141 describes the significant fields shown in the display.

show rom-monitor

to both the Cisco 7200 VXR and Cisco 7301 routers, displays both ROMMON images and verifies that the Upgrade ROMMON image is running:

Router> show rom-monitor

ReadOnly ROMMON version:

System Bootstrap, Version 12.2(20031011:151758)

Copyright (c) 2004 by Cisco Systems, Inc.

Upgrade ROMMON version:

System Bootstrap, Version 12.2(20031011:151758)

Copyright (c) 2004 by Cisco Systems, Inc.

Currently running ROMMON from Upgrade region

ROMMON from Upgrade region is selected for next boot

In the following example, the ROMmon image in RP 0 of a Cisco ASR 1006 Router is verified using the show rom-monitor command:

Router# show rom-monitor r0

System Bootstrap, Version 12.2(33r)XN1, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 2007 by cisco Systems, Inc.

show rom-monitor slot

show running-config

show running-config

To display the contents of the current running configuration file or the configuration for a specific module, Layer 2 VLAN, class map, interface, map class, policy map, or virtual circuit (VC) class, use the show running-config command in user EXEC or privileged EXEC mode.

show running-config [options]

show running-config

???The show running-config command does not display this value.

???The show running-config all displays this output: cdp holdtime 180.

If the Cisco Discovery Protocol holdtime is changed to a nondefault value (for example, 100), the output of the show running-config and show running-config all commands is the same; that is, the configured parameter is displayed.

Current configuration : 104 bytes 1 : !

2 : interface Ethernet0/0

3 : ip address 10.4.2.63 255.255.255.0

4: no ip route-cache

5: no ip mroute-cache

6: end

show running-config

The following example shows how to set line numbers in the command output and then use the output modifier to start the display at line 10:

Router# show running-config linenum | begin 10

10: boot-start-marker

11: boot-end-marker

12: !

13: no logging buffered

14: enable password #####

15: !

16: spe 1/0 1/7

17: firmware location bootflash:mica-modem-pw.172.16.0.0.bin

18: !

19: !

20: resource-pool disable

21: !

22: no aaa new-model

23: ip subnet-zero

24: ip domain name cisco.com

25: ip name-server 172.16.11.48

26: ip name-server 172.16.2.133

27: !

28: !

29: isdn switch-type primary-5ess

30: !

.

.

.

126 : end

The following example shows how to display the module and status configuration for all modules on a Cisco 7600 series router:

Router# show running-config

Building configuration...

Current configuration:

!

version 12.0

service timestamps debug datetime localtime service timestamps log datetime localtime no service password-encryption

!

hostname Router

!

boot buffersize 126968

boot system flash slot0:7600r

boot bootldr bootflash:c6msfc-boot-mz.120-6.5T.XE1.0.83.bin enable password lab

!

clock timezone Pacific -8

clock summer-time Daylight recurring redundancy

main-cpu

auto-sync standard

show running-config

mls flow ip destination mls flow ipx destination cns event-service server

!

spanning-tree portfast bpdu-guard spanning-tree uplinkfast

spanning-tree vlan 200 forward-time 21 port-channel load-balance sdip

!

!

!

shutdown

!

!

.

.

.

In the following sample output from the show running-config command, the shape average command indicates that traffic shaping overhead accounting for ATM is enabled. The BRAS-DSLAM encapsulation type is qinq and the subscriber line encapsulation type is snap-rbe based on the AAL5 service.

Router# show running-config

.

.

.

subscriber policy recording rules limit 64

no mpls traffic-eng auto-bw timers frequency 0 call rsvp-sync

!

controller T1 2/0 framing sf linecode ami

!

controller T1 2/1 framing sf linecode ami

!

!

policy-map unit-test class class-default

shape average percent 10 account qinq aal5 snap-rbe

!

show running-config

show policy-map Displays the configuration of all classes for a specified service policy map or all classes for all existing policy maps, and displays ATM overhead accounting information, if configured.

show startup-config Displays the contents of NVRAM (if present and valid) or displays the configuration file pointed to by the CONFIG_FILE environment variable. (Command alias for the more:nvram startup-config command.)

show running-config map-class

Building configuration...

Current configuration:

!

map-class frame-relay cir60 frame-relay bc 16000

frame-relay adaptive-shaping becn

!

map-class frame-relay cir70

no frame-relay adaptive-shaping frame-relay priority-group 2

!

map-class atm vc100 atm aal5mux

!

map-class dialer dialer1 dialer idle-timeout 10

end

All Frame Relay Map Classes Example

The following example displays all Frame Relay map classes on the router:

Router# show running-config map-class frame-relay

Building configuration...

Current configuration:

!

map-class frame-relay cir60 frame-relay bc 16000

frame-relay adaptive-shaping becn

!

map-class frame-relay cir70

no frame-relay adaptive-shaping frame-relay priority-group 2

end

A Specific Map Class and Display of Line Numbers Example

The following example displays a specific map class called class1. Line numbers are displayed in the output.

Router# show running-config map-class frame-relay class1 linenum

Building configuration...

Current configuration: 1 : !

2: map-class frame-relay boy

3: no frame-relay adaptive-shaping

4: frame-relay cir 1000

5: end

show running-config map-class

show running-config partition

In the following example, only the main configuration partition associated with the interface configuration is queried, and only the configuration commands associated with FastEthernet interface 0/1 are displayed.

Router# show running-config partition interface fastethernet0/1

Building configuration...

Current configuration : 213 bytes

!

Configuration of Partition interface FastEthernet0/1

!

!

interface FastEthernet0/1

ip address 10.4.2.39 255.255.255.0 no ip route-cache cef

no ip route-cache duplex half

ipv6 enable no cdp enable

!

!

end

show scp

show scp

To display Switch-Module Configuration Protocol (SCP) information, use the show scp in privileged EXEC mode on the Switch Processor.

show scp {accounting | counters | linecards [details] | mcast {group group-id | inst} | process id

show scp

1Pass

2Pass

3Pass

5Pass

6Pass

Router# attach 5

Trying Switch ...

Entering CONSOLE for Switch

Type "^C^C^C" to end this session

Switch-sp# show scp process

Sap Pid Name

=== === ====

0 180 CWAN-RP SCP Input Process

18 42 itasca

20 3 Exec

21 3 Exec

22 180 CWAN-RP SCP Input Process Total number of SAP registered = 5 Router#

show slot

show slot

The following example show the flash detailed directory.

Router# show slot detailed

The following example shows the flash chip erase and write retries.

Router# show slot err

The following example shows the flash partition summary.

The following example shows flash chip information.

The following example show the flash detailed directory.

Router# show slot0: detailed

show slot0:

The following example shows the flash chip erase and write retries.

Router# show slot0: err

The following example shows the flash partition summary.

show slot1:

The following example shows flash chip information.

The following example show the flash detailed directory.

Router# show slot1: detailed

PCMCIA Slot0 flash directory:

show slot1:

The following example shows the flash chip erase and write retries.

Router# show slot1: err

The following example shows the flash partition summary.

show stacks

show startup-config

show startup-config

The more nvram:startup-config command has been replaced by the show startup-config command.

See the description of the more command in the ???Cisco IOS File System Commands??? chapter for more information.

show subsys

Table 142 describes the fields shown in the display.

show sup-bootflash

******** Intel SCS Status/Register Dump ********

COMMON MEMORY REGISTERS: Bank 0

Intelligent ID Code : 890089

Compatible Status Reg: 800080

Queued Erase Supported : No

Router#

This example shows how to display information about the Flash chip:

Router# show sup-bootflash chips

******** Intel SCS Status/Register Dump ********

COMMON MEMORY REGISTERS: Bank 0

Intelligent ID Code : 890089

Compatible Status Reg: 800080

Queued Erase Supported : No

Router#

This example shows how to display information about the file system:

show sup-bootflash

Router#

show tech-support

show tech-support

To display general information about the router when it reports a problem, use the show tech-support command in privileged EXEC mode.

show tech-support [page] [password] [cef | ipc | ipmulticast [vrf vrf-name] | isis | mpls | ospf [process-id | detail] | rsvp]

Cisco 7600 Series

show tech-support [cef | ipmulticast [vrf vrf-name] | isis | password [page] | platform | page | rsvp]

show tech-support

The output of the show tech-support ipmulticast vrf command was changed to include the output from these commands:

??? show mls ip multicast rp-mapping gm-cache

??? show mmls gc process

??? show mmls msc rpdf-cache

The output of the show tech-support ipmulticast command (without the vrf vrf-name keyword and argument) was changed to include the output from these commands:

??? show ip pim int df

??? show ip pim mdt

??? show ip pim mdt bgp

??? show ip pim rp metric

Support to interrupt and terminate the show tech-support output was added.

show tech-support

Usage Guidelines To interrupt and terminate the show tech-support output, simultaneously press and release the CTRL, ALT, and 6 keys.

Press the Return key to display the next line of output, or press the Spacebar to display the next page of information. If you do not enter the page keyword, the output scrolls (that is, it does not stop for page breaks).

If you do not enter the password keyword, passwords and other security-sensitive information in the output are replaced with the label ???<removed>.???

The show tech-support command is useful for collecting a large amount of information about your routing device for troubleshooting purposes. The output of this command can be provided to technical support representatives when reporting a problem.

Note This command can generate a very large amount of output. You may want to redirect the output to a file using the show inventory | redirect url command syntax extension. Redirecting the output to a file also makes sending this output to your technical support representative easier. See the command documentation for show <command> | redirect for more information on this option.

The show tech-support command displays the output of a number of show commands at once. The output from this command varies depending on your platform and configuration. For example, access servers display voice-related show command output. Additionally, the show protocol traffic commands are displayed for only the protocols enabled on your device. For a sample display of the output of the show tech-support command, see the individual show command listed.

If you enter the show tech-support command without arguments, the output displays, but is not limited to, the equivalent of these show commands:

???show appletalk traffic

???show bootflash

???show bootvar

???show buffers

???show cdp neighbors

???show cef

???show clns traffic

???show context

???show controllers

???show decnet traffic

???show disk0: all

???show dmvpn details

show tech-support

???show environment

???show fabric channel-counters

???show file systems

???show interfaces

???show interfaces switchport

???show interfaces trunk

???show ip interface

???show ip traffic

???show logging

???show mac-address-table

???show module

???show power

???show processes cpu

???show processes memory

???show running-config

???show spanning-tree

???show stacks

???show version

???show vlan

Note Crypto information is not duplicated by the show dmvpn details command output.

Use of the optional cef, ipc, ipmulticast, isis, mpls, ospf, or rsvp keywords provides a way to display a number of show commands specific to a particular protocol or process in addition to the show commands listed previously.

For example, if your Technical Assistance Center (TAC) support representative suspects that you may have a problem in your Cisco Express Forwarding (CEF) configuration, you may be asked to provide the output of the show tech-support cef command. The show tech-support [page] [password] cef command will display the output from the following commands in addition to the output for the standard show tech-support command:

???show adjacency summary

???show cef drop

???show cef events

???show cef interface

???show cef not-cef-switched

???show cef timers

???show interfaces stats

???show ip cef events summary

???show ip cef inconsistency records detail

???show ip cef summary

show tech-support

show tech-support

show usb device

Configuration:

Number:1

Number of Interfaces:1

Description:

Attributes:None

Max Power:140 mA

Interface:

Number:0

Description:

Class Code:8

Subclass:6

Protocol:80

Number of Endpoints:2

Endpoint:

Number:1

Transfer Type:BULK

Transfer Direction:Device to Host

Max Packet:64

Interval:0

Endpoint:

Number:2

Transfer Type:BULK

Transfer Direction:Host to Device

Max Packet:64

Interval:0

Host Controller:1

Address:0x11

Device Configured:YES

Device Supported:YES

Description:eToken Pro 4254

Manufacturer:AKS

Version:1.0

Serial Number:

Device Handle:0x1010000

USB Version Compliance:1.0

Class Code:0xFF

Subclass Code:0x0

Protocol:0x0

Vendor ID:0x529

Product ID:0x514

Max. Packet Size of Endpoint Zero:8

Number of Configurations:1

Speed:Low

Selected Configuration:1

Selected Interface:0

Configuration:

Number:1

Number of Interfaces:1

Description:

Attributes:None

Max Power:60 mA

Interface:

Number:0

Description:

Class Code:255

Subclass:0

Protocol:0

Number of Endpoints:0

show usb device

Table 143 describes the significant fields shown in the display.

Table 143 show usb device Field Descriptions

show usb driver

Subclass Code:0x6249BD58

Protocol:0x2

Interface Class Code:0x5DC0

Interface Subclass Code:0x5

Interface Protocol Code:0xFFFFFFFF

Product ID:0x2

Vendor ID:0x1

Attached Devices:

None

Index:3

Owner Mask:0x10

Class Code:0x0

Subclass Code:0x0

Protocol:0x0

Interface Class Code:0x0

Interface Subclass Code:0x0

Interface Protocol Code:0x0

Product ID:0x0

Vendor ID:0x0

Attached Devices:

None

Table 144 describes the significant field shown in the display.

show usbtoken

Table 145 show usbtoken Field Descriptions (continued)

show version

Usage Guidelines This command displays information about the Cisco IOS software version currently running on a routing device, the ROM Monitor and Bootflash software versions, and information about the hardware configuration, including the amount of system memory. Because this command displays both software and hardware information, the output of this command is the same as the output of the show hardware command. (The show hardware command is a command alias for the show version command.)

Specifically, the show version command provides the following information:

???Software information

???Main Cisco IOS image version

???Main Cisco IOS image capabilities (feature set)

???Location and name of bootfile in ROM

???Bootflash image version (depending on platform)

???Device-specific information

???Device name

???System uptime

???System reload reason

???Config-register setting

???Config-register settings for after the next reload (depending on platform)

???Hardware information

???Platform type

???Processor type

???Processor hardware revision

???Amount of main (processor) memory installed

???Amount I/O memory installed

???Amount of Flash memory installed on different types (depending on platform)

???Processor board ID

The output of this command uses the following format:

Cisco IOS Software, <platform> Software (<image-id>), Version <software-version>, <software-type>

Technical Support: http://www.cisco.com/techsupport

Copyright (c) <date-range> by Cisco Systems, Inc.

Compiled <day> <date> <time> by <compiler-id>

show version

show version

2 FastEthernet interfaces

4 Serial interfaces

DRAM configuration is 64 bits wide with parity disabled. 125K bytes of NVRAM.

16384K bytes of processor board System flash (Read/Write)

Flash card inserted. Reading filesystem...done.

20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)

Configuration register is 0x2102

Cisco 7200 Router

The following is sample output from the show version command issued on a Cisco 7200 router running Cisco IOS Release 12.4(4)T. This output shows the total bandwidth capacity and the bandwith capacity that is configured on the Cisco 7200. Displaying bandwidth capacity is available in Cisco IOS Release 12.2 and later releases.

Router# show version

Cisco IOS Software, 7200 Software (C7200-JS-M), Version 12.4(4)T, RELEASE SOFTW)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2005 by Cisco Systems, Inc.

Compiled Thu 27-Oct-05 05:58 by ccai

ROM: System Bootstrap, Version 12.1(20000710:044039) [nlaw-121E_npeb 117], DEVEE

BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.3(16), RELEASE SOFTWARE (fc4)

router uptime is 5 days, 18 hours, 2 minutes

System returned to ROM by reload at 02:45:12 UTC Tue Feb 14 2006 System image file is "disk0:c7200-js-mz.124-4.T"

Last reload reason: Reload Command

Cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of memo. Processor board ID 26793934

R7000 CPU at 350MHz, Implementation 39, Rev 3.2, 256KB L2 Cache 6 slot VXR midplane, Version 2.6

Last reset from power-on

PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.

Current configuration on bus mb0_mb1 has a total of 440 bandwidth points.

This configuration is within the PCI bus capacity and is supported.

PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.

Current configuration on bus mb2 has a total of 390 bandwidth points

This configuration is within the PCI bus capacity and is supported.

Please refer to the following document "Cisco 7200 Series Port Adaptor Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com> for c7200 bandwidth points oversubscription and usage guidelines.

4 Ethernet interfaces

2 FastEthernet interfaces

2 ATM interfaces

125K bytes of NVRAM.

62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes). 125952K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2002

show version

Router#

For information about PCI buses and bandwidth calculation, go to http://www.cisco.com/univercd/cc/td/doc/product/core/7206/port_adp/config/3875in.htm#wp1057192.

Table 146 describes the significant fields shown in the display.

show version

Table 146 show version Field Descriptions (continued)

show version

Table 146 show version Field Descriptions (continued)

show version

Table 146 show version Field Descriptions (continued)

Catalyst 6500 Series Switches and Cisco 7600 Series Routers

This example shows how to display the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images:

Router# show version

Cisco Internetwork Operating System Software

IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1 (nightly.E020626) NIG

HTLY BUILD

Copyright (c) 1986-2002 by cisco Systems, Inc.

Compiled Wed 26-Jun-02 06:20 by

Image text-base: 0x40008BF0, data-base: 0x419BA000

ROM: System Bootstrap, Version 12.1(11r)E1, RELEASE SOFTWARE (fc1)

Router uptime is 2 weeks, 8 hours, 48 minutes

Time since Router switched to active is 1 minute

System returned to ROM by power-on (SP by power-on)

System image file is "sup-bootflash:c6sup22-jsv-mz"

cisco Catalyst 6000 (R7000) processor with 112640K/18432K bytes of memory. Processor board ID SAD06210067

R7000 CPU at 300Mhz, Implementation 39, Rev 3.3, 256KB L2, 1024KB L3 Cache Last reset from power-on

Bridging software.

X.25 software, Version 3.0.0.

SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software.

3 Virtual Ethernet/IEEE 802.3 interface(s)

48 FastEthernet/IEEE 802.3 interface(s)

381K bytes of non-volatile configuration memory.

16384K bytes of Flash internal SIMM (Sector size 512K).

show version

Configuration register is 0x2102

Router#

Table 147 describes the fields that are shown in the example.

show version

Copyright (c) 1986-2000 by cisco Systems, Inc.

Compiled Wed 02-Feb-00 16:49 by ccai

Image text-base:0x60008900, data-base:0x61192000

ROM:System Bootstrap, Version 12.0(15)SC, RELEASE SOFTWARE

VXR1 uptime is 2 days, 1 hour, 24 minutes

System returned to ROM by power-on at 10:54:38 PST Sat Feb 5 2000

System restarted at 11:01:08 PST Sat Feb 5 2000

System image file is "slot1:ubr7200-p-mz.121-0.8.T"

cisco uBR7246VXR (NPE300) processor (revision B) with 122880K/40960K bytes of memory. Processor board ID SAB0329005N

R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache 6 slot VXR midplane, Version 2.0

Last reset from power-on

X.25 software, Version 3.0.0. National clock card with T1 controller 1 FastEthernet/IEEE 802.3 interface(s) 2 Cable Modem network interface(s)

125K bytes of non-volatile configuration memory.

16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K). 4096K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x0

Router#

Table 148 describes significant fields shown in these displays.

Table 148 show version Field Descriptions

The output of the show version command can also provide certain messages, such as bus error messages. If such error messages appear, report the complete text of this message to your technical support specialist.

show version

Cisco uBR10012 Router

The following example shows sample output from the show version command on a Cisco uBR10012 universal broadband router running Cisco IOS Release 12.3(17b)BC4:

Router> show version

Cisco Internetwork Operating System Software

IOS (tm) 10000 Software (UBR10K2-K9P6U2-M), Version 12.3(17b)BC4, RELEASE SOFTWA

RE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2006 by cisco Systems, Inc.

Compiled Wed 22-Nov-06 11:41 by tinhuang

Image text-base: 0x60010F0C, data-base: 0x62480000

ROM: System Bootstrap, Version 12.0(20020314:211744) [REL-pulsar_sx.ios-rommon 1

12], DEVELOPMENT SOFTWARE

ubr10k uptime is 2 days, 22 hours, 13 minutes

System returned to ROM by reload at 01:34:58 UTC Sun Jun 8 2008 System image file is "disk0:ubr10k2-k9p6u2-mz.123-17b.BC4" Last reload reason: Reload command

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to export@cisco.com.

cisco uBR10000 (PRE2-RP) processor with 946175K/98304K bytes of memory. Processor board ID TBA05380380

R7000 CPU at 500MHz, Implementation 39, Rev 4.1, 256KB L2, 8192KB L3 Cache Backplane version 1.1, 8 slot

Last reset from register reset PXF processor tmc0 is running. PXF processor tmc1 is running. PXF processor tmc2 is running. PXF processor tmc3 is running. 1 TCCplus card(s)

1 FastEthernet/IEEE 802.3 interface(s)

3 Gigabit Ethernet/IEEE 802.3 interface(s)

24 Cable Modem network interface(s)

2045K bytes of non-volatile configuration memory.

125440K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes). 125440K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes). 65536K bytes of Flash internal SIMM (Sector size 512KB).

Secondary is up.

Secondary has 1044480K bytes of memory.

Configuration register is 0x2102

show version

Cisco ASR 1000 Series Routers

In the following example, the show version installed command is entered on a Cisco ASR 1000 Series Router in diagnostic mode. Note that the output shows what every file that can be found in the consolidated package is or is not currently running (provisioning file, RP Access, RP Base, RP Control, RP IOS, ESP Base, SIP Base, SIP SPA).

Router#show version installed

Package: Provisioning File, version: n/a, status: active

File: bootflash:packages.conf, on: RP0

Built: n/a, by: n/a

File SHA1 checksum: 0b9f2c7c3d81d8455a918f285c078463c04a0cab

Package: rpbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 193c4810becc2a6097645f0b68f5684004bd3ab3

Package: rpaccess-k9, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 328c3d1e10f006304ce9543ab68e914b43c41b1e

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: active File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpbase, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg, on: RP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 193c4810becc2a6097645f0b68f5684004bd3ab3

Package: rpaccess-k9, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg, on: RP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 328c3d1e10f006304ce9543ab68e914b43c41b1e

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP1/0

Built: 2007-11-11_17.16, by: mcpre

show version

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: espbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle.pkg, on: FP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: b1c004ed151cf60f0ce250f6ea710f43707fb010

Package: espbase, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle.pkg, on: FP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: b1c004ed151cf60f0ce250f6ea710f43707fb010

Package: sipbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg, on: CC0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: bd34a8a23d001f9cefcac8853a31b62ffd8272a4

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/3

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg, on: CC1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: bd34a8a23d001f9cefcac8853a31b62ffd8272a4

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

show version

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/3

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipbase, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg, on: CC2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: bd34a8a23d001f9cefcac8853a31b62ffd8272a4

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC2/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC2/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC2/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC2/3

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Router#

In the following example, the show version provisioned command is entered to gather information on which sub-packages are provisioning which components on the router.

Router#show version provisioned

Package: Provisioning File, version: n/a, status: active

File: bootflash:packages.conf, on: RP0

Built: n/a, by: n/a

File SHA1 checksum: 0b9f2c7c3d81d8455a918f285c078463c04a0cab

Package: rpbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 193c4810becc2a6097645f0b68f5684004bd3ab3

Package: rpaccess-k9, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 328c3d1e10f006304ce9543ab68e914b43c41b1e

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: active File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP0/0

Built: 2007-11-11_17.16, by: mcpre

show version

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpbase, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg, on: RP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 193c4810becc2a6097645f0b68f5684004bd3ab3

Package: rpaccess-k9, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg, on: RP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 328c3d1e10f006304ce9543ab68e914b43c41b1e

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: inactive

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: inactive File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: FP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: FP1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

show version

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC0/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: CC0/3

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: active

File: unknown, on: CC1/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: CC1/3

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: CC2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: CC2/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

File: unknown, on: CC2/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: unknown

Package: rpios-advipservicesk9, version: unknown, status: inactive

show version

File SHA1 checksum: unknown

Router#

In the following example, the show version running command is entered to view which sub-packages are active on which hardware elements on the router.

Router#show version running

Package: Provisioning File, version: n/a, status: active

File: bootflash:packages.conf, on: RP0

Built: n/a, by: n/a

File SHA1 checksum: 0b9f2c7c3d81d8455a918f285c078463c04a0cab

Package: rpbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 193c4810becc2a6097645f0b68f5684004bd3ab3

Package: rpaccess-k9, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg, on: RP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 328c3d1e10f006304ce9543ab68e914b43c41b1e

Package: rpcontrol, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg, on: RP0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: e4152b7fe3c2b8aca07ce1e8ad6d5a54d6d20689

Package: rpios-advipservicesk9, version: v122_33_xn_asr_rls0_throttle, status: active File: bootflash:asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg, on:

RP0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 7f7f87f2c198c38e7b58214478c5b28ee3c7b567

Package: espbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle.pkg, on: FP0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: b1c004ed151cf60f0ce250f6ea710f43707fb010

Package: sipbase, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg, on: CC0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: bd34a8a23d001f9cefcac8853a31b62ffd8272a4

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC0/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

show version

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/0

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/1

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Package: sipspa, version: v122_33_xn_asr_rls0_throttle, status: active

File: bootflash:asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg, on: CC1/2

Built: 2007-11-11_17.16, by: mcpre

File SHA1 checksum: 6ad199569dad7d8b35beac2c8a72b080f9662897

Router#

showmon