Cisco IOS Configuration Fundamentals Command Reference PDF
Cisco IOS Configuration Fundamentals Command Reference PDF
Command Reference
Americas Headquarters
CONTENTS
Introduction 1
Cisco IOS IFS Command Syntax 2
Obtaining Documentation Obtaining Support and Security Guidelines 4
A through B 5
activation-character 6
alias 7
archive 11
archive config 13
archive log config persistent save 16
archive tar 18
async-bootp 21
attach 24
autobaud 27
auto-sync 28
autoupgrade disk-cleanup 31
autoupgrade ida url 33
autoupgrade status email 35
banner exec 37
banner incoming 40
banner login 43
banner motd 46
banner slip-ppp 49
boot 52
boot bootldr 57
boot bootstrap 59
boot config 62
boot host 65
boot network 68
boot system 71
Contents
boot-end-marker 78
boot-start-marker 81
C commands 85
cd 87
clear archive log config 89
clear catalyst6000 traffic-meter 91
clear configuration lock 92
clear diagnostic event-log 94
clear ip http client cache 96
clear logging 98
clear logging system 100
clear logging xml 102
clear memory low-water-mark 104
clear mls statistics 105
clear parser cache 107
clear parser statistics 109
clear platform netint 111
clear processes interrupt mask 112
clear scp accounting 114
clear tcp 115
clear vlan counters 117
clock 118
clock initialize nvram 120
config-register 121
configure check syntax 123
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the
M train.) 124
configure confirm 131
configure memory 133
configure network 135
configure overwrite-network 136
configure replace 137
configure revert 142
configure terminal 144
confreg 147
Contents
Contents
downward-compatible-config 248
editing 250
enable 254
enable last-resort 258
end 259
environment-monitor shutdown temperature 261
environment temperature-controlled 262
erase 264
erase bootflash 268
errdisable detect cause 269
errdisable recovery 271
escape-character 274
exec 277
exec-banner 278
exec-character-bits 280
exec-timeout 282
execute-on 284
exit (EXEC) 289
exit (global) 291
F through K 293
file prompt 294
file verify auto 295
format 297
fsck 301
full-help 307
help 309
hidekeys 311
history 313
history size 315
hold-character 317
hostname 319
hw-module reset 321
hw-module shutdown 322
insecure 323
international 324
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Contents
state-machine 1365
stopbits 1367
storm-control level 1369
sync-restart-delay 1371
systat 1373
system flowcontrol bus 1374
system jumbomtu 1376
tdm clock priority 1378
terminal databits 1381
terminal data-character-bits 1383
terminal dispatch-character 1385
terminal dispatch-timeout 1386
terminal download 1388
terminal editing 1389
terminal escape-character 1390
terminal exec-character-bits 1392
terminal flowcontrol 1394
terminal full-help 1396
terminal history 1398
terminal history size 1400
terminal hold-character 1403
terminal international 1405
terminal keymap-type 1407
terminal length 1408
terminal monitor 1410
terminal notify 1411
terminal padding 1412
terminal parity 1414
terminal rxspeed 1416
terminal special-character-bits 1418
terminal speed 1420
terminal start-character 1421
terminal stopbits 1422
terminal stop-character 1423
terminal telnet break-on-ip 1424
Contents
Contents
vtp 1503
warm-reboot 1507
where 1509
width 1511
write core 1513
write erase 1515
write memory 1516
write mib-data 1517
write network 1519
write terminal 1521
xmodem 1522
ASCII Character Set and Hexadecimal Values 1525
Introduction
The Cisco IOS Configuration Fundamentals Command Reference provides command documentation
associated with the following tasks:
The basics of filesystem use and Cisco IOS softwares filesystem infrastructure
Configuring Basic File Transfer Services
For further information about performing these tasks, refer to the Cisco IOS Configuration Fundamentals
Configuration Guide for your release.
Note
Some commands previously documented in this Command Reference have been moved to other books:
Commands related to system management and network monitoring can be found in the Cisco IOS
Network Management Command Reference . Command reference documentation for the Cisco IOS
software feature Service Assurance Agent (SAA) can be found in the the Cisco IOS IP SLAs Command
Reference
Introduction
Cisco IOS IFS Command Syntax
Prefix
Description
ftp:
rcp:
tftp:
The following table lists the available suffix options (file indentification suffixes) for the URL prefixes
used in the previous table.
Table 2
Prefix
Suffix Options
ftp:
[[//[username[:password]@]location]/directory]/
filename
For example:
ftp://network-config (prefix ://filename )
ftp://user1:[email protected]/configfiles
rcp:
rcp:[[//[username@]location]/directory]/filename
tftp:
tftp:[[//location]/directory]/filename
The following table lists common URL prefixes used to indicate memory locations on the system.
Table 3
Prefix
Description
bootflash:
disk0:
Introduction
Cisco IOS IFS Command Syntax
Prefix
Description
flash: partition-number
flh:
null:
nvram:
slavebootflash:
slavenvram:
slaveslot0:
slaveslot1:
slot0:
slot1:
xmodem:
ymodem:
For details about the Cisco IOS IFS, and for IFS configuration tasks, refer to the Using the Cisco IOS
Integrated File System (IFS) chapter in the latest Cisco IOS Configuration Fundamentals Configuration
Guide appropriate for your release version.
Introduction
Obtaining Documentation Obtaining Support and Security Guidelines
A through B
activation-character, page 6
alias, page 7
archive, page 11
archive config, page 13
archive log config persistent save, page 16
archive tar, page 18
async-bootp, page 21
attach, page 24
autobaud, page 27
auto-sync, page 28
autoupgrade disk-cleanup, page 31
autoupgrade ida url, page 33
autoupgrade status email, page 35
banner exec, page 37
banner incoming, page 40
banner login, page 43
banner motd, page 46
banner slip-ppp, page 49
boot, page 52
boot bootldr, page 57
boot bootstrap, page 59
boot config, page 62
boot host, page 65
boot network, page 68
boot system, page 71
boot-end-marker, page 78
boot-start-marker, page 81
A through B
activation-character
activation-character
To define the character you ent er at a vacant terminal to begin a terminal session, use the activationcharacter command in line configuration mode. To make any character activate a terminal, use the no
form of this command.
activation-character ascii-number
no activation-character
Syntax Description
ascii-number
Command Default
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
See the ASCII Character Set and Hexadecimal Values document for a list of ASCII characters.
If you are using the autoselect function, set the activation character to the default, Return, and execcharacter-bits to 7. If you change these defaults, the application will not recognize the activation request.
The following example shows how to set the activation character for the console to Delete, which is
decimal character 127:
Router(config)# line console
Router(config-line)# activation-character 127
A through B
alias
alias
To create a command alias, use the alias command in global configuration mode. To delete all aliases in a
command mode or to delete a specific alias, and to revert to the original command syntax, use the no form
of this command.
alias mode command-alias original-command
no alias mode [command-alias]
Syntax Description
mode
command-alias
Command alias.
original-command
Command Default
A set of six basic EXEC mode aliases are enabled by default. See the Usage Guidelines section of this
command for a list of default aliases.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
15.0M
Command Alias
Original Command
help
A through B
alias
Command Alias
Original Command
lo
logout
ping
resume
show
where
The default aliases in the table above are predefined. These default aliases can be disabled with the no alias
exec command.
Common keyword aliases (which cannot be disabled) include running-config (keyword alias for
system:running-config) and startup-config (keyword alias for nvram:startup-config). See the
description of the copy command for more information about these keyword aliases.
Note that aliases can be configured for keywords instead of entire commands. You can create, for example,
an alias for the first part of any command and still enter the additional keywords and arguments as normal.
To determine the value for the mode argument, enter the command mode in which you would issue the
original command (and in which you will issue the alias) and enter the ? command. The name of the
command mode should appear at the top of the list of commands. For example, the second line in the
following sample output shows the name of the command mode as Interface configuration:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface e0
Router(config-if)# ?
Interface configuration commands:
access-expression
Build a bridge boolean access expression
.
.
.
To match the name of the command mode to the acceptable mode keyword for the alias command, issue
the alias ? command. As shown in the following sample output, the keyword needed to create a command
alias for the access-expression command is interface:
Router(config)# alias ?
accept-dialin
VPDN group accept dialin configuration mode
accept-dialout
VPDN group accept dialout configuration mode
address-family
Address Family configuration mode
call-discriminator
Call Discriminator Configuration
cascustom
Cas custom configuration mode
clid-group
CLID group configuration mode
configure
Global configuration mode
congestion
Frame Relay congestion configuration mode
controller
Controller configuration mode
cptone-set
custom call progress tone configuration mode
customer-profile
customer profile configuration mode
dhcp
DHCP pool configuration mode
dnis-group
DNIS group configuration mode
exec
Exec mode
flow-cache
Flow aggregation cache config mode
fr-fr
FR/FR connection configuration mode
interface
Interface configuration mode
.
.
.
Router(config)# alias interface express access-expression
A through B
alias
When you use online help, command aliases are indicated by an asterisk (*), and displayed in the following
format:
*command-alias =original-command
For example, the lo command alias is shown here along with other EXEC mode commands that start with
lo:
Router# lo?
*lo=logout lock
login
logout
When you use online help, aliases that contain multiple keyword elements separated by spaces are
displayed in quotes, as shown here:
Router(config)#alias exec device-mail telnet device.cisco.com 25
Router(config)#end
Router#device-mail?
*device-mail=telnet device.cisco.com 25"
To list only commands and omit aliases, begin your input line with a space. In the following example, the
alias td is not shown, because there is a space before the t?command line.
Router(config)#alias exec td telnet device
Router(config)#end
Router# t?
telnet terminal test tn3270 trace
To circumvent command aliases, use a space before entering the command. In the following example, the
command alias express is not recognized because a space is used before the command.
Router(config-if)#exp?
*express=access-expression
Router(config-if)# express ?
% Unrecognized command
As with commands, you can use online help to display the arguments and keywords that can follow a
command alias. In the following example,the alias td is created to represent the command telnet device.
The /debugand /lineswitchescan be added to telnet device to modify the command:
Router(config)#alias exec td telnet device
Router(config)#end
Router#td ?
/debug
Enable telnet debugging mode
/line
Enable telnet line mode
...
whois
Whois port
<cr>
Router# telnet device
You must enter the complete syntax for the command alias. Partial syntax for aliases is not accepted. In the
following example, the parser does not recognize the command t as indicating the alias td:
Router# t
% Ambiguous command: t
Examples
In the following example, the alias fixmyrtis configured for the clear iproute 192.168.116.16 EXEC mode
command:
Router(config)#alias exec fixmyrt clear ip route 192.168.116.16
A through B
alias
In the following example, the alias express is configured for the first part of the access-expression
interface configuration command:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface e0
Router(config-if)#?
Interface configuration commands:
access-expression
Build a bridge boolean access expression
.
.
.
Router(config-if)#exit
Router(config)#alias ?
accept-dialin
VPDN group accept dialin configuration mode
accept-dialout
VPDN group accept dialout configuration mode
address-family
Address Family configuration mode
call-discriminator
Call Discriminator Configuration
cascustom
Cas custom configuration mode
clid-group
CLID group configuration mode
configure
Global configuration mode
congestion
Frame Relay congestion configuration mode
controller
Controller configuration mode
cptone-set
custom call progress tone configuration mode
customer-profile
customer profile configuration mode
dhcp
DHCP pool configuration mode
dnis-group
DNIS group configuration mode
exec
Exec mode
flow-cache
Flow aggregation cache config mode
fr-fr
FR/FR connection configuration mode
interface
Interface configuration mode
.
.
.
Router(config)#alias interface express access-expression
Router(config)#int e0
Router(config-if)#exp?
*express=access-expression
Router(config-if)#express ?
input
Filter input packets
output
Filter output packets
!Note that the true form of the command/keyword alias appears on the screen after issuing
!the express ? command.
Router(config-if)#access-expression ?
input
Filter input packets
output Filter output packets
Router(config-if)#ex?
*express=access-expression exit
!Note that in the following line, a space is used before the ex? command
!so the alias is not displayed.
Router(config-if)# ex?
exit
!Note that in the following line, the alias cannot be recognized because
!a space is used before the command.
Router#(config-if)# express ?
% Unrecognized command
Router(config-if)# end
Router# show alias interface
Interface configuration mode aliases:
express
access-expression
Related Commands
Command
Description
show aliases
A through B
archive
archive
To enter archive configuration mode, use the archive command in global configuration mode.
archive
Syntax Description
Command Default
None
Command Modes
Global configuration
Command History
Examples
Release
Modification
12.3(4)T
12.2(25)S
12.2(33)SRA
12.2(33)SB
The following example shows how to place the router in archive configuration mode:
Router# configure terminal
!
Router(config)# archive
Router(config-archive)#
Related Commands
Command
Description
log config
logging enable
A through B
archive
Command
Description
maximum
path
time-period
A through B
archive config
archive config
To save a copy of the current running configuration to the Cisco IOS configuration archive, use the archive
config command in privileged EXEC mode.
archive config
Syntax Description
Command Modes
Command History
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SB
Usage Guidelines
Note
Before using this command, you must configure the path command in order to specify the location and
filename prefix for the files in the Cisco IOS configuration archive.
The Cisco IOS configuration archive is intended to provide a mechanism to store, organize, and manage an
archive of Cisco IOS configuration files to enhance the configuration rollback capability provided by the
configure replace command. Before this feature was introduced, you could save copies of the running
configuration using the copy running-config destination-url command, storing the target file either locally
or remotely. However, this method lacked any automated file management. On the other hand, the
A through B
archive config
Configuration Replace and Configuration Rollback feature provides the capability to automatically save
copies of the running configuration to the Cisco IOS configuration archive. These archived files serve as
checkpoint configuration references and can be used by the configure replace command to revert to
previous configuration states.
The archive config command allows you to save Cisco IOS configurations in the configuration archive
using a standard location and filename prefix that is automatically appended with an incremental version
number (and optional time stamp) as each consecutive file is saved. This functionality provides a means for
consistent identification of saved Cisco IOS configuration files. You can specify how many versions of the
running configuration are kept in the archive. After the maximum number of files has been saved in the
archive, the oldest file is automatically deleted when the next, most recent file is saved. The show archive
command displays information for all configuration files saved in the Cisco IOS configuration archive.
Examples
The following example shows how to save the current running configuration to the Cisco IOS configuration
archive using the archive config command. Before using the archive config command, you must configure
the path command to specify the location and filename prefix for the files in the Cisco IOS configuration
archive. In this example, the location and filename prefix are specified as disk0:myconfig as follows:
configure terminal
!
archive
path disk0:myconfig
end
You then save the current running configuration in the configuration archive, as follows:
archive config
The show archive command displays information on the files saved in the configuration archive as shown
in the following sample output:
Router# show archive
There are currently 1 archive configurations saved.
The next archive file will be named disk0:myconfig-2
Archive # Name
0
1
disk0:myconfig-1 <- Most Recent
2
3
4
5
6
7
8
9
10
Related Commands
Command
Description
archive
configure confirm
A through B
archive config
Command
Description
configure replace
maximum
path
show archive
time-period
A through B
archive log config persistent save
Syntax Description
Command Default
If this command is not entered, the persisted configuration commands in the archive log are not saved to the
Cisco IOS secure file system.
Command Modes
Command History
Release
Modification
12.2(33)SRA
12.4(11)T
12.2(33)SXH
12.2(33)SB
Usage Guidelines
If the router is in the persistent periodic mode, the persistent timer is restarted.
Examples
The following example saves the persisted commands in the archive log to the Cisco IOS secure file
system:
Router# archive log config persistent save
A through B
archive log config persistent save
Related Commands
Command
Description
log config
logging enable
logging persistent
A through B
archive tar
archive tar
To create a TAR file, to list files in a TAR file, or to extract the files from a TAR file, use the archive tar
command in privileged EXEC mode.
archive tar {/create destination-urlflash:/file-url | /table source-url | /xtract source-urlflash:/fileurl [dir/file...]}
Syntax Description
A through B
archive tar
/table source-url
Command Default
Command Modes
Command History
Release
Modification
12.1(13)AY
12.2(33)SXH
A through B
archive tar
Usage Guidelines
Release
Modification
12.4(22)YB
12.4(24)T
Examples
The following example shows how to create a TAR file. The command writes the contents of the newconfigs directory on the local flash device to a file named saved.tar on the TFTP server at 172.20.136.9.
Switch# archive tar /create tftp:172.20.136.9/saved.tar flash:/new-configs
The following example shows how to display the contents of the c2940-tv0-m.tar file that is in flash
memory. The contents of the TAR file appear on the screen.
Switch# archive tar /table flash:c2940-tv0-m.tar
info (219 bytes)
c2940-tv0-mz-121/ (directory)
c2940-tv0-mz-121/html/ (directory)
c2940-tv0-mz-121/html/foo.html (0 bytes)
c2940-tv0-mz-121/vegas-tv0-mz-121.bin (610856 bytes)
c2940-tv0-mz-121/info (219 bytes)
info.ver (219 bytes)
The following example shows how to extract the contents of a TAR file on the TFTP server at
172.20.10.30. This command extracts only the new-configs directory into the root directory on the local
flash file system. The remaining files in the saved.tar file are ignored.
Switch# archive tar /xtract tftp:/172.20.10.30/saved.tar flash:/ new-configs
A through B
async-bootp
async-bootp
To configure extended BOOTP requests for asynchronous interfaces as defined in RFC 1084, use the
async-bootp command in global configuration mode. To restore the default, use the noform of this
command.
async-bootp tag [:hostname] data
no async-bootp
Syntax Description
tag
: hostname
data
Table 5
Keyword
Description
bootfile
subnet-mask mask
time-offset offset
gateway address
time-server address
IEN116-server address
nbns-server address
A through B
async-bootp
Keyword
Description
DNS-server address
log-server address
quote-server address
lpr-server address
impress-server address
rlp-server address
hostname name
bootfile-size value
A two-octet value specifying the number of 512octet (byte) blocks in the default boot file.
Command Default
If no extended BOOTP commands are entered, the Cisco IOS software generates a gateway and subnet
mask appropriate for the local network.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Use the show async-bootp EXEC command to list the configured parameters. Use the no async-bootp
command to clear the list.
A through B
async-bootp
Examples
The following example illustrates how to specify different boot files: one for a PC, and one for a
Macintosh. With this configuration, a BOOTP request from the host on 172.30.1.1 results in a reply listing
the boot filename as pcboot. A BOOTP request from the host named mac results in a reply listing the
boot filename as macboot.
async-bootp bootfile :172.30.1.1 pcboot
async-bootp bootfile :mac macboot
The following example specifies a negative time offset of the local subnetwork of 3600 seconds:
async-bootp time-offset -3600
Related Commands
Command
Description
A through B
attach
attach
To connect to a specific line card or module from a remote location for the purpose of executing
monitoring and maintenance commands on that line card or module, use the attach command in privileged
EXEC mode. To exit from the Cisco IOS software image on the line card and return to the Cisco IOS
image on the main (Supervisor) module, use the exit command.
Cisco 12000 Series
attach slot-number
Cisco 7600 Series and Catalyst 6500 Series
attach module-number
Syntax Description
slot-number
module-number
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2GS
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
A through B
attach
Usage Guidelines
Note
Do not execute the configEXEC command from the Cisco IOS software image on the line card.
Cisco 7600 Series and Catalyst 6500 Series
Caution
After you enter the attach or remote login command to access another console from your switch, if you
enter global or interface configuration mode commands, the switch might reset.
Th e v alid values for the module-number argument depend on the chassis that is used. For example, if you
have a 13-slot chassis, valid values for the module number are from 1 to 13.
This command is supported on Distributed Forwarding Card (DFC)-equipped modules, FlexWan modules,
and the supervisor engine only.
When you execute the attach module-number command, the prompt changes to Router-dfcx# or Switchsp#, depending on the type of module to which you are connecting.
The behavior of the attach command is identical to that of the remote login module numcommand.
There are two ways to end this session:
Router-dfc3# exit
[Connection to Switch closed by foreign host]
Router#
Router-dfc3# ^C
Router-dfc3# ^C
Router-dfc3# ^C
Terminate remote login session? [confirm] y
[Connection to Switch closed by local host]
Router#
Examples
In the following example, the user connects to the Cisco IOS image running on the line card in slot 9, gets a
list of valid show commands, and returns the Cisco IOS image running on the GRP:
Router# attach 9
Entering Console for 4 Port Packet Over SONET OC-3c/STM-1 in Slot: 9
Type exit to end this session
Press RETURN to get started!
A through B
attach
LC-Slot9# show ?
cef
Cisco Express Forwarding
clock
Display the system clock
context
Show context information about recent crash(s)
history
Display the session command history
hosts
IP domain-name, lookup style, nameservers, and host table
ipc
Interprocess communications commands
location Display the system location
sessions Information about Telnet connections
terminal Display terminal configuration parameters
users
Display information about terminal lines
version
System hardware and software status
LC-Slot9# exit
Disconnecting from slot 9.
Connection Duration: 00:01:04
Router#
Note
Because not all statistics are maintained on line cards, the output from some of show commands may be
inconsistent.
The following example shows how to log in remotely to the DFC-equipped module:
Console#
attach 3
Trying Switch ...
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
Router-dfc3#
Related Commands
Command
Description
attach shelf
execute-on slot
remote login
A through B
autobaud
autobaud
To set the line for automatic baud rate detection (autobaud), use the autobaudcommand in line
configuration mode. To disable automatic baud detection, use the noform of this command.
autobaud
no autobaud
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Note
Examples
Release
Modification
10.0
12.2(33)SRA
The autobaud detection supports a range from 300 to 19200 baud. A line set for autobaud cannot be used
for outgoing connections, nor can you set autobaud capability on a line using 19200 baud when the parity
bit is set (because of hardware limitations).
Automatic baud detection must be disabled by using the no autobaud command prior to setting the txspeed,
rxspeed, or speed commands.
In the following example, the auxiliary port is configured for autobaud detection:
Router(config)# line aux
Router(config-line)# autobaud
A through B
auto-sync
auto-sync
To enable automatic synchronization of the configuration files in NVRAM, use the auto-sync command in
main-cpu redundancy configuration mode. To disable automatic synchronization, use the no form of this
command.
auto-sync {startup-config | config-register | bootvar | running-config | standard}
no auto-sync {startup-config | config-register | bootvar | standard}
Syntax Description
startup-config
config-register
bootvar
Command Default
running-config
standard
For the Performance Routing Engines (PREs) on the Cisco uBR10012 universal broadband router, the
system defaults to synchronizing all system files on the (auto-sync standard).
For the Supervisor Engines on the Cisco 7600 series routers, the system defaults to synchronizing the
running configuration. (running-config).
At the Cisco RF Gateway 10 chassis level, all the system files are synchronized by default.
Redundancy configuration (config-r)
Command Modes
A through B
auto-sync
Command History
Usage Guidelines
Release
Modification
12.2(4)XF1
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.3BC
12.2(33)SCA
12.2(44)SQ
Examples
A through B
auto-sync
Router (config-r)#
main-cpu
Router (config-r-mc)#
no auto-sync standard
Router (config-r-mc)#
auto-sync config-register
The following example shows how to configure the system to synchronize all system files except for the
startup configuration file. This typically is done when the two PRE1 (or PRE2) modules are running
different software images.
router(config)# redundancy
router(config-r)# main-cpu
router(config-r-mc)# no auto-sync startup-config
router(config-r-mc)# auto-sync config-register
router(config-r-mc)# auto-sync bootvar
router(config-r-mc)# exit
router(config-r)# exit
Cisco RF Gateway 10
The following example shows the synchronization of all system files on the Cisco RFGW-10 chassis:
Router#configure terminal
Router(config)#redundancy
Router(config-red)#main-cpu
Router(config-r-mc)#auto-sync standard
Router(config-r-mc)#exit
Router(config-red)#exit
Related Commands
Command
Description
redundancy
main-cpu
A through B
autoupgrade disk-cleanup
autoupgrade disk-cleanup
To configure the Cisco IOS Auto-Upgrade Manager disk cleanup utility, use the autoupgrade diskcleanup command in global configuration mode. To disable this configuration, use the no form of this
command.
autoupgrade disk-cleanup [crashinfo | core | image | irrecoverable]
no autoupgrade disk-cleanup [crashinfo | core | image | irrecoverable]
Syntax Description
crashinfo
core
image
irrecoverable
(Optional) Deletes files irretrievably (in a filesystem that supports the undelete operation) during
disk-cleanup before an image is downloaded.
Command Default
By default, the crashinfo files, the core files, and the Cisco IOS software images are deleted by the Cisco
IOS Auto-Upgrade Manager disk cleanup utility, and the filesystems that support the undelete operation are
not cleaned up.
Command Modes
Command History
Examples
Release
Modification
12.4(15)T
The following example shows how to clean-up filesystems that support undelete operation:
Router(config)# autoupgrade disk-cleanup irrecoverable
The following example shows how to avoid deleting the Cisco IOS software images:
Router(config)# no autoupgrade disk-cleanup image
A through B
autoupgrade disk-cleanup
Related Commands
Command
Description
A through B
autoupgrade ida url
Syntax Description
url
Command Default
Command Modes
Command History
Release
Modification
12.4(15)T
Usage Guidelines
Use the autoupgrade ida url command to configure a new URL for the IDA server, if it is not present in
the default location.
Examples
The following example shows how to configure the URL for the IDA server:
Router(config)# autoupgrade ida url https://www.cisco.com/cgi-bin/ida/locator/locator.pl
Related Commands
Command
Description
autoupgrade disk-cleanup
A through B
autoupgrade ida url
Command
Description
A through B
autoupgrade status email
Syntax Description
recipient
smtp-server
email-address
Command Default
Status email is not sent unless the address is configured. The recipient email address and SMTP server have
to be configured in order to receive AUM status email.
Command Modes
Command History
Release
Modification
12.4(15)T
Usage Guidelines
Use this command to configure the email-address where AUM status email can be sent.
Examples
The following example shows how to configure the address to which status email is to be sent:
Router(config)# autoupgrade status email recipient [email protected]
Router(config)# autoupgrade status email smtp-server smtpserver.abc.com
A through B
autoupgrade status email
Related Commands
Command
Description
autoupgrade disk-cleanup
A through B
banner exec
banner exec
To specify and enable a message to be displayed when an EXEC process is created (an EXEC banner), use
the banner exec command in global configuration mode. To delete the existing EXEC banner, use the no
form of this command.
banner exec d message d
no banner exec
Syntax Description
message
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
11.3(7.5)AA
12.0(3)T
12.2(33)SRA
This command specifies a message to be displayed when an EXEC process is created (a line is activated, or
an incoming connection is made to a vty). Follow this command with one or more blank spaces and a
delimiting character of your choice. Then enter one or more lines of text, terminating the message with the
second occurrence of the delimiting character.
When a user connects to a router, the message-of-the-day (MOTD) banner appears first, followed by the
login banner and prompts. After the user logs in to the router, the EXEC banner or incoming banner will be
A through B
banner exec
displayed, depending on the type of connection. For a reverse Telnet login, the incoming banner will be
displayed. For all other connections, the router will display the EXEC banner.
To disable the EXEC banner on a particular line or lines, use the no exec-banner line configuration
command.
To customize the banner, use tokens in the form $(token ) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are described
in the table below.
Table 6
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example sets an EXEC banner that uses tokens. The percent sign (%) is used as a delimiting
character. Notice that the $(token ) syntax is replaced by the corresponding configuration variable.
Router(config)# banner exec %
Enter TEXT message. End with the character '%'.
Session activated on line $(line), $(line-desc). Enter commands at the prompt.
%
Related Commands
Command
Description
banner incoming
banner login
banner motd
banner slip-ppp
A through B
banner exec
Command
Description
exec-banner
A through B
banner incoming
banner incoming
To define and enable a banner to be displayed when there is an incoming connection to a terminal line from
a host on the network, use the banner incoming command in global configuration mode. To delete the
incoming connection banner, use the no form of this command.
banner incoming d message d
no banner incoming
Syntax Description
message
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
11.3(7.5)AA
12.0(3)T
12.2(33)SRA
Follow the banner incomingcommand with one or more blank spaces and a delimiting character of your
choice. Then enter one or more lines of text, terminating the message with the second occurrence of the
delimiting character.
An incoming connection is one initiated from the network side of the router. Incoming connections are also
called reverse Telnet sessions. These sessions can display MOTD banners and incoming banners, but they
A through B
banner incoming
do not display EXEC banners. Use the no motd-banner line configuration command to disable the MOTD
banner for reverse Telnet sessions on asynchronous lines.
When a user connects to the router, the message-of-the-day (MOTD) banner (if configured) appears first,
before the login prompt. After the user successfully logs in to the router, the EXEC banner or incoming
banner will be displayed, depending on the type of connection. For a reverse Telnet login, the incoming
banner will be displayed. For all other connections, the router will display the EXEC banner.
Incoming banners cannot be suppressed. If you do not want the incoming banner to appear, you must delete
it with the no banner incoming command.
To customize the banner, use tokens in the form $(token ) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are described
in the table below.
Table 7
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example sets an incoming connection banner. The pound sign (#) is used as a delimiting
character.
Router(config)# banner incoming #
This is the Reuses router.
#
The following example sets an incoming connection banner that uses several tokens. The percent sign (%)
is used as a delimiting character.
darkstar(config)# banner incoming %
Enter TEXT message. End with the character '%'.
You have entered $(hostname).$(domain) on line $(line) ($(line-desc)) %
When the incoming connection banner is executed, the user will see the following banner. Notice that the $
(token ) syntax is replaced by the corresponding configuration variable.
You have entered darkstar.ourdomain.com on line 5 (Dialin Modem)
Related Commands
Command
Description
banner exec
A through B
banner incoming
Command
Description
banner login
banner motd
banner slip-ppp
A through B
banner login
banner login
To define and enable a customized banner to be displayed before the username and password login
prompts, use the banner login command in global configuration mode. To disable the login banner, use no
form of this command.
banner login d message d
no banner login
Syntax Description
message
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
11.3(7.5)AA
12.0(3)T
12.2(14)SX
12.2(33)SRA
Follow the banner login command with one or more blank spaces and a delimiting character of your
choice. Then enter one or more lines of text, terminating the message with the second occurrence of the
delimiting character.
A through B
banner login
When a user connects to the router, the message-of-the-day (MOTD) banner (if configured) appears first,
followed by the login banner and prompts. After the user successfully logs in to the router, the EXEC
banner or incoming banner will be displayed, depending on the type of connection. For a reverse Telnet
login, the incoming banner will be displayed. For all other connections, the router will display the EXEC
banner.
To customize the banner, use tokens in the form $(token ) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are described
in the table below.
Table 8
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example sets a login banner. Double quotes (") are used as the delimiting character.
Router# banner login " Access for authorized users only. Please enter your username and
password. "
The following example sets a login banner that uses several tokens. The percent sign (%) is used as the
delimiting character.
darkstar(config)# banner login %
Enter TEXT message. End with the character '%'.
You have entered $(hostname).$(domain) on line $(line) ($(line-desc)) %
When the login banner is executed, the user will see the following banner. Notice that the $(token) syntax
is replaced by the corresponding configuration variable.
You have entered darkstar.ourdomain.com on line 5 (Dialin Modem)
Related Commands
Command
Description
banner exec
banner incoming
banner motd
A through B
banner login
Command
Description
banner slip-ppp
A through B
banner motd
banner motd
To define and enable a message-of-the-day (MOTD) banner, use the banner motd command in global
configuration mode. To delete the MOTD banner, use the no form of this command.
banner motd d message d
no banner motd
Syntax Description
message
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
11.3(7.5)AA
12.0(3)T
12.2(33)SRA
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter
one or more lines of text, terminating the message with the second occurrence of the delimiting character.
This MOTD banner is displayed to all terminals connected and is useful for sending messages that affect all
users (such as impending system shutdowns). Use the no exec-banner or no motd-banner command to
disable the MOTD banner on a line. The no exec-banner command also disables the EXEC banner on the
line.
When a user connects to the router, the MOTD banner appears before the login prompt. After the user logs
in to the router, the EXEC banner or incoming banner will be displayed, depending on the type of
A through B
banner motd
connection. For a reverse Telnet login, the incoming banner will be displayed. For all other connections,
the router will display the EXEC banner.
To customize the banner, use tokens in the form $(token ) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are described
in the table below.
Table 9
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example configures an MOTD banner. The pound sign (#) is used as a delimiting character.
Router# banner motd # Building power will be off from 7:00 AM until 9:00 AM this coming
Tuesday.
The following example configures an MOTD banner with a token. The percent sign (%) is used as a
delimiting character.
darkstar(config)# banner motd %
Enter TEXT message. End with the character '%'.
Notice: all routers in $(domain) will be upgraded beginning April 20
%
When the MOTD banner is executed, the user will see the following. Notice that the $(token ) syntax is
replaced by the corresponding configuration variable.
Notice: all routers in ourdomain.com will be upgraded beginning April 20
Related Commands
Command
Description
banner exec
banner incoming
banner login
A through B
banner motd
Command
Description
banner slip-ppp
exec-banner
motd-banner
A through B
banner slip-ppp
banner slip-ppp
To customize the banner that is displayed when a Serial Line Internet Protocol (SLIP) or PPP connection is
made, use the banner slip-ppp command in global configuration mode. To restore the default SLIP or PPP
banner, use the no form of this command.
banner slip-ppp d message d
no banner slip-ppp
Syntax Description
Command Default
message
The banner message when using the service old-slip-prompt command is:
Entering encapsulation mode.
Your IP address is 10.100.0.0 MTU is 1500 bytes
Command Modes
Command History
Usage Guidelines
Global configuration
Release
Modification
12.0(3)T
12.2(33)SRA
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter
one or more lines of text, terminating the message with the second occurrence of the delimiting character.
A through B
banner slip-ppp
Use this command to define a custom SLIP or PPP connection message. This is useful when legacy client
applications require a specialized connection string. To customize the banner, use tokens in the form $
(token ) in the message text. Tokens will display current Cisco IOS configuration variables, such as the
routers host name, IP address, encapsulation type, and Maximum Transfer Unit (MTU) size. The banner
tokens are described in the table below.
Table 10
Examples
Token
$(hostname)
$(domain)
$(peer-ip)
$(gate-ip)
$(encap)
$(encap-alt)
$(mtu)
The following example sets the SLIP/PPP banner using several tokens and the percent sign (%) as the
delimiting character:
Router(config)# banner slip-ppp %
Enter TEXT message. End with the character '%'.
Starting $(encap) connection from $(gate-ip) to $(peer-ip) using a maximum packet size of
$(mtu) bytes... %
The new SLIP/PPP banner will now be displayed when the slip EXEC command is used. Notice that the $
(token ) syntax is replaced by the corresponding configuration variable.
Router# slip
Starting SLIP connection from 172.16.69.96 to 192.168.1.200 using a maximum packet size
of 1500 bytes...
Related Commands
Command
Description
banner exec
banner incoming
A through B
banner slip-ppp
Command
Description
banner motd
ppp
slip
A through B
boot
boot
To boot the router manually, use the bootcommand in ROM monitor mode. The syntax of this command
varies according to the platform and ROM monitor version.
boot
boot file-url
boot filename [tftp-ip-address]
boot flash [flash-fs:] [partition-number:] [filename]
Cisco 7000 Series, 7200 Series, 7500 Series Routers
boot flash-fs : [filename]
Cisco 1600 and Cisco 3600 Series Routers
boot [flash-fs:] [partition-number:] [filename]
Cisco 1800 Series, 2800 Series, and 3800 Series Routers
boot usbflash0 [:filename]
Syntax Description
file-url
A through B
boot
filename
tftp-ip-address
flash
usbflash0
A through B
boot
flash-fs :
partition-number :
Command Default
For most platforms, if you enter the boot command and press Enter, the router boots from ROM by default.
However, for some platforms, such as the Cisco 3600 series routers, if you enter the boot command and
press Enter, the router boots the first image in Flash memory. Refer to the documentation for your platform
for information about the default image.
Command Modes
ROM monitor
Command History
Usage Guidelines
Release
Modification
10.3
12.3(14)T
12.2(33)SRA
To determine which form of this command to use, refer to the documentation for your platform or use the
CLI help (?) feature.
Use this command only when your router cannot find the boot configuration information needed in
NVRAM. To enter ROM monitor mode, use one of the following methods:
Enter the reload EXEC command, then press the Break key during the first 60 seconds of startup.
A through B
boot
Set the configuration register bits 0 to 3 to zero (for example, set the configuration register to 0x0) and
enter the reload command.
The ROM Monitor prompt is either > or, for newer platforms, rommon x >. Enter only lowercase
commands.
These commands work only if there is a valid image to boot. Also, from the ROM monitor prompt, issuing
a prior reset command is necessary for the boot to be consistently successful.
In Cisco IOS Release 12.3(4)T, MONLIB was modified to search in media for a valid Cisco IOS image.
This change prevents boot failures that result when the first file read in disk or flash is not a valid Cisco
IOS image.
Refer to your hardware documentation for information on correct jumper settings for your platform.
Note
Examples
For some platforms the flash keyword is now required. If your attempts to use the boot command are
failing using the older boot flash:x:[filename ] syntax, try using the boot flash flash:x:[filename ] syntax.
In the following example, a router boots the file named routertest from a network server with the IP address
172.16.15.112 using the file-url syntax:
> boot tftp://172.16.15.112/routertest
F3
(ROM Monitor copyrights)
The following example shows the boot flash command without the filename argument. The first valid file
in Flash memory is loaded.
> boot flash
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
The following example boots from Flash memory using the file named gs7-k:
> boot flash gs7-k
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
A through B
boot
In the following example, the boot flash flash: command boots the relocatable image file named igs-bpx-l
from partition 2 in Flash memory:
> boot flash flash:2:igs-bpx-l
F3: 3562264+98228+303632 at 0x30000B4
(ROM Monitor copyrights)
In the following command, the Cisco 7000 family router accepts the flash keyword for compatibility but
ignores it, and boots from slot 0:
> boot flash slot0:gs7-k-mz.103-9
F3: 8468+3980384+165008 at 0x1000
In the following example, the command did not function because it must be entered in lowercase:
rommon 10 > BOOT
command BOOT not found
The following example boots the first file in the first partition of internal Flash memory of a Cisco 3600
series router:
> boot flash:
The following example boots the first image file in the first partition of the Flash memory card in slot 0 of a
Cisco 3600 series router:
> boot slot0:
The following example shows the ROM monitor booting the first file in the first Flash memory partition on
a Cisco 1600 series router:
> boot flash:
Related Commands
Command
Description
continue
A through B
boot bootldr
boot bootldr
To specify the location of the boot image that ROM uses for booting, use the boot bootldr command in
global configuration mode. To remove this boot image specification, use the no form of this command.
boot bootldr file-url boot bootldr command
no boot bootldr
Syntax Description
file-url
Command Default
Refer to your platform documentation for the location of the default boot image.
Command Modes
Command History
Usage Guidelines
Release
Modification
11.0
12.2(33)SRA
The boot bootldr command sets the BOOTLDR variable in the current running configuration. You must
specify both the Flash file system and the filename.
Note
When you use this global configuration command, you affect only the running configuration. You must
save the variable setting to your startup configuration to place the information under ROM monitor control
and to have the variable function as expected. Use the copy system:running-config nvram:startup-config
command to save the variable from your running configuration to your startup configuration.
Note
The default length of the bootstring filename is 64 characters. Depending on the platform a longer
bootstring filename can be used and supported.
The no form of the command sets the BOOTLDR variable to a null string. On the Cisco 7000 family
routers , a null string causes the first image file in boot Flash memory to be used as the boot image that
ROM uses for booting.
Use the show boot command to display the current value for the BOOTLDR variable.
A through B
boot bootldr
Examples
In the following example, the internal Flash memory contains the boot image:
boot bootldr bootflash:boot-image
The following example specifies that the Flash memory card inserted in slot 0 contains the boot image:
boot bootldr slot0:boot-image
Related Commands
Command
Description
show bootvar
A through B
boot bootstrap
boot bootstrap
To configure the filename that is used to boot a secondary bootstrap image, use the boot bootstrap
command in global configuration mode. To disable booting from a secondary bootstrap image, use the no
form of this command.
boot bootstrap file-url
no boot bootstrap file-url
boot bootstrap flash [filename]
no boot bootstrap flash [filename]
boot bootstrap [tftp] filename [ip-address]
no boot bootstrap [tftp] filename [ip-address]
boot bootstrap mop filename [interface-type interface-number]
no boot bootstrap mop filename [interface-type interface-number]
Syntax Description
file-url
flash
filename
tftp
ip-address
mop
interface-type
interface-number
A through B
boot bootstrap
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
15.0(1)M
12.2(33)SXI
The boot bootstrap command causes the router to load a secondary bootstrap image from the specied
URL, such as from a remote server. After the bootstrap image is loaded, the bootstrap image loads the
specified system image file. See the appropriate hardware installation guide for details on setting the
configuration register and secondary bootstrap filename.
Use this command when you have attempted to load a system image but have run out of memory even after
compressing the system image. Secondary bootstrap images allows you to load a larger system image
through a smaller secondary image.
Examples
The following example shows how to load the system image file named sysimage-2 by using a secondary
bootstrap image:
Router# configure terminal
Router(config)# boot bootstrap bootflash:sysimage-2
Related Commands
Command
Description
boot
A through B
boot bootstrap
Command
Description
boot system
A through B
boot config
boot config
To s pecify the device and filename of the configuration file from which the system configures itself during
initialization (startup), use the boot config command in global configuration mode. To return to the default
location for the configuration file, use the no form of this command.
Platforms Other than Cisco 7600 Series Router
boot config file-system-prefix : [directory/] filename [nvbypass]
no boot config
Cisco 7600 Series Router
boot config device : filename [nvbypass]
no boot config
Syntax Description
file-system-prefix :
directory/
filename
device :
nvbypass
Command Default
Command Modes
Command History
Release
Modification
12.2(33)SRA
A through B
boot config
Release
Modification
12.2(14)SX
12.2(17d)SXB
11.0
12.3(14)T
For systems that are configured with a Supervisor Engine 2, the valid values are bootflash:,
const_nvram:, flash:, nvram:, slot0:, sup-slot0:, and sup-bootflash:
For systems that are configured with a Supervisor Engine 720, the valid values are disk0: and disk1:
The configuration file must be an ASCII file that is located in the specified file system.
The disk0: and disk1: keywords are for Class C file systems.
The bootflash:, slot0:, and sup-bootflash: keywords are for Class A file systems.
For Class A flash file systems, the CONFIG_FILE environment variable specifies the file system and
filename of the configuration file to use for initialization (startup). You set the CONFIG_FILE environment
variable in the current running memory when you use the boot config command. This variable specifies the
configuration file used for initialization (startup).
All Supported Platforms
When you use the boot config command, you affect only the running configuration. You must save the
environment variable setting to your startup configuration to place the information under ROM monitor
control and to have the environment variable function as expected. Use the copy system:running-config
nvram:startup-config command to save the environment variable from your running configuration to your
startup configuration.
The software displays an error message and does not update the CONFIG_FILE environment variable in
the following situations:
You specify nvram: as the file system, and it contains only a distilled version of the configuration. (A
distilled configuration is one that does not contain access lists.)
You specify a configuration file in the filename argument that does not exist or is not valid.
A through B
boot config
The router uses the NVRAM configuration during initialization when the CONFIG_FILE environment
variable does not exist or when it is null (such as at first-time startup). If the software detects a problem
with NVRAM or the configuration it contains, the device enters setup mode.
When you use the no form of this command, the router returns to using the default NVRAM configuration
file as the startup configuration.
You can display the contents of the BOOT, BOOTLDR, and the CONFIG_FILE environment variables
using the show bootvar command. This command displays the settings for these variables as they exist in
the startup configuration and in the running configuration if a running configuration setting differs from a
startup configuration setting.
When the boot config command is used, the distilled configuration is written into NVRAM and the system
configuration is written into the file specified by the boot config command. If the distilled configuration
exceeds the size of NVRAM, the system configuration gets truncated. Use the nvbypass keyword to
prevent the system configuration from being truncated when the distilled configuration is larger than the
size of NVRAM.
Examples
The following example shows how to set the configuration file that is located in internal flash memory to
configure itself during initialization. The third line copies the specification to the startup configuration,
ensuring that this specification will take effect upon the next reload.
Router(config)# boot config flash:router-config
Router(config)# end
Router# copy system:running-config nvram:startup-config
The following example instructs a Cisco 7500 series router to use the configuration file named routerconfig located on the flash memory card inserted in the second Personal Computer Memory Card Industry
Association (PCMCIA) slot of the Route Switch Processor (RSP) card during initialization. The third line
copies the specification to the startup configuration, ensuring that this specification will take effect upon
the next reload.
Router (config)# boot config slot1:router-config
Router (config)# end
Router# copy system:running-config nvram:startup-config
Related Commands
Command
Description
show bootvar
A through B
boot host
boot host
To specify the host-specific configuration file to be used at the next system startup, use the boot host
command in global configuration mode. To restore the host configuration filename to the default, use the
no form of this command.
boot host commandboot host remote-url
no boot host remote-url
Syntax Description
remote-url
Command Default
If you do not specify a filename using this command, the router uses its configured host name to request a
configuration file from a remote server. To form the configuration filename, the router converts its name to
all lowercase letters, removes all domain information, and appends -confg or -config.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This command instructs the system to Boot using host-specific configuration file x , where x is the
filename specified in the remote-url argument. In other words, this command specifies the remote location
and filename of the host-specific configuration file to be used at the next system startup, as well as the
protocol to be used to obtain the file.
Before using the boot host command, use the service config global configuration command to enable the
loading of the specified configuration file at reboot time. Without this command, the router ignores the
boot host command and uses the configuration information in NVRAM. If the configuration information in
NVRAM is invalid or missing, the service config command is enabled automatically.
A through B
boot host
The network server will attempt to load two configuration files from remote hosts. The first is the network
configuration file containing commands that apply to all network servers on a network. Use the boot
network command to identify the network configuration file. The second is the host configuration file
containing commands that apply to one network server in particular. Use the boot host command to
identify the host configuration file.
Note
Usually, the service config command is used in conjunction with the boot host or boot network command.
You must enter the service config command to enable the router to automatically configure the system
from the file specified by the boot host or boot network command. With IOS software versions 12.3(2)T ,
12.3(1)B, and later, you no longer have to specify the service config command for the boot host or boot
network command to be active. If you specify both the no service config command and the boot host
command, the router attempts to find the specified host configuration file. The service config command can
also be used without the boot host or boot network command. If you do not specify host or network
configuration filenames, the router uses the default configuration files. The default network configuration
file is network-confg. The default host configuration file is host-confg, where host is the hostname of the
router. If the Cisco IOS software cannot resolve its hostname, the default host configuration file is routerconfg.
Loading a Configuration File Using rcp
The rcp software requires that a client send the remote username on each rcp request to the network server.
If the server has a directory structure (such as UNIX systems), the rcp implementation searches for the
configuration files starting in the directory associated with the remote username.
When you load a configuration file from a server using rcp, the Cisco IOS software sends the first valid
username in the following list:
1 The username specified in the file-URL, if a username is specified.
2 The username set by the ip rcmd remote-username command, if the command is configured.
3 The router host name.
Note
An account for the username must be defined on the destination server. If the network administrator of the
destination server did not establish an account for the username, this command will not execute
successfully.
Loading a Configuration File Using FTP
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. The username and password must be associated with an account on the FTP server. If the server has
a directory structure, the configuration file or image copied from the directory is associated with the
username on the server. Refer to the documentation for your FTP server for more details.
When you load a configuration file from a server using FTP, the Cisco IOS software sends the first valid
username in the following list:
1 The username specified in the boot host command, if a username is specified.
2 The username set by the ip ftp username command, if the command is configured.
3 Anonymous.
The router sends the first valid password in the following list:
1 The password specified in the boot host command, if a password is specified.
2 The password set by the ip ftp password command, if the command is configured.
A through B
boot host
3 The router forms a password username @routername .domain . The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain
of the router.
Examples
The following example sets the host filename to wilma-confg at address 192.168.7.19:
Router(config)# boot host tftp://192.168.7.19/usr/local/tftpdir/wilma-confg
Router(config)# service config
Related Commands
Command
Description
boot network
service config
A through B
boot network
boot network
To change the default name of the network configuration file from which to load configuration commands,
use the boot network command in global configuration mode. To restore the network configuration
filename to the default, use the no form of this command.
boot network remote-url
no boot network remote-url
Syntax Description
remote-url
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This command instructs the system to Boot using network configuration file x , where x is the filename
specified in the remote-url argument. This command specifies the remote location and filename of the
network configuration file to be used at the next system startup, as well as the protocol to be used to obtain
the file.
When booting from a network server, routers ignore routing information, static IP routes, and bridging
information. As a result, intermediate routers are responsible for handling FTP, rcp, or TFTP requests.
Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time.
Without this command, the router ignores the boot network command and uses the configuration
A through B
boot network
information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service
config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network
configuration file containing commands that apply to all network servers on a network. Use the boot
network command to identify the network configuration file. The second is the host configuration file
containing commands that apply to one network server in particular. Use the boot host command to
identify the host configuration file.
Note
Usually, the service config command is used in conjunction with the boot host or boot network command.
You must enter the service config command to enable the router to automatically configure the system
from the file specified by the boot host or boot network command. With IOS software versions 12.3(2)T ,
12.3(1)B, and later, you no longer have to specify the service config command for the boot host or boot
network command to be active. If you specify both the no service config command and the boot host
command, the router attempts to find the specified host configuration file. The service config command can
also be used without the boot host or boot network command. If you do not specify host or network
configuration filenames, the router uses the default configuration files. The default network configuration
file is network-confg. The default host configuration file is host-confg, where host is the hostname of the
router. If the Cisco IOS software cannot resolve its hostname, the default host configuration file is routerconfg.
Loading a Configuration File Using rcp
The rcp software requires that a client send the remote username on each rcp request to the network server.
If the server has a directory structure (such as UNIX systems), the rcp implementation searches for the
configuration files starting in the directory associated with the remote username.
When you load a configuration file from a server using rcp, the Cisco IOS software sends the first valid
username in the following list:
1 The username specified in the file-URL, if a username is specified.
2 The username set by the ip rcmd remote-username command, if the command is configured.
3 The router host name.
Note
An account for the username must be defined on the destination server. If the network administrator of the
destination server did not establish an account for the username, this command will not execute
successfully.
Loading a Configuration File Using FTP
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. The username and password must be associated with an account on the FTP server. If the server has
a directory structure, the configuration file or image copied from the directory associated with the username
on the server. Refer to the documentation for your FTP server for more details.
When you load a configuration file from a server using FTP, the Cisco IOS software sends the first valid
username in the following list:
1 The username specified in the boot network command, if a username is specified.
2 The username set by the ip ftp username command, if the command is configured.
3 Anonymous.
A through B
boot network
The router sends the first valid password in the following list:
1 The password specified in the boot network command, if a password is specified.
2 The password set by the ip ftp password command, if the command is configured.
3 The router forms a password username @routername .domain . The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain
of the router.
Examples
The following example changes the network configuration filename to bridge_9.1 and uses the default
broadcast address:
Router(config)# boot network tftp:bridge_9.1
Router(config)# service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be
used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which the
network configuration file resides:
Router(config)# service config
Router(config)# boot network rcp://172.16.1.111/bridge_9.1
Related Commands
Command
Description
boot host
service config
A through B
boot system
boot system
To specify the system image that the router loads at startup, use one of the following boot system
command in global configuration mode. To remove the startup system image specification, use the no form
of this command.
Loading System Image from a URL or a TFTP File
boot system {file-url | filename}
no boot system {file-url | filename}
Booting from a System Image in Internal Flash
boot system flash [flash-fs:] [partition-number:] [filename]
no boot system flash [flash-fs:] [partition-number:] [filename]
Booting from a MOP Server
boot system mop filename [mac-address] [interface]
no boot system mop filename [mac-address] [interface]
Booting from ROM
boot system rom
no boot system rom
Booting a System Image from a Network, TFTP, or FTP Server
boot system {rcp | tftp | ftp} filename [ip-address]
no boot system {rcp | tftp | ftp} filename [ip-address]
Syntax Description
file-url
filename
A through B
boot system
flash
flash-fs :
A through B
boot system
filename
mop
mac-address
interface
rom
rcp
tftp
ftp
ip-address
A through B
boot system
Command Default
If you configure the router to boot from a network server but do not specify a system image file with the
boot system command, the router uses the configuration register settings to determine the default system
image filename. The router forms the default boot filename by starting with the word cisco and then
appending the octal equivalent of the boot field number in the configuration register, followed by a hyphen
(-) and the processor type name (cisconn-cpu). Refer to the appropriate hardware installation guide for
details on the configuration register and default filename. See also the config-register or confreg
command.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
For this command to work, the config-register command must be set properly.
Create a comma-delimited list of several boot system commands to provide a fail-safe method for booting
your router. The router stores and executes the boot system commands in the order in which you enter
them in the configuration file. If you enter multiple boot commands of the same type--for example, if you
enter two commands that instruct the router to boot from different network servers--the router tries them in
the order in which they appear in the configuration file. If a boot system command entry in the list
specifies an invalid device, the router omits that entry. Use the boot system rom command to specify use
of the ROM system image as a backup to other boot system commands in the configuration.
Note
After a list of several images are specified with the boot system command, running the command again
results in the list being appended, not removed.
For some platforms, the boot image must be loaded before the system image is loaded. However, on many
platforms, the boot image is loaded only if the router is booting from a network server or if the flash file
system is not specified. If the file system is specified, the router will boot faster because it need not load the
boot image first.
A through B
boot system
Note
If you want to rearrange the order of the entries in the configuration file, you must first issue the no boot
system command and then redefine the list.
Booting Compressed Images
You can boot the router from a compressed image on a network server. When a network server boots
software, both the image being booted and the running image must be able to fit into memory. Use
compressed images to ensure that enough memory is available to boot the router. You can compress a
software image on any UNIX platform using the compress command. Refer to your UNIX platforms
documentation for the exact usage of the compress command. (You can also uncompress data with the
UNIX uncompress command.)
Understanding rcp
The rcp requires that a client send the remote username in an rcp request to a server. When the router
executes the boot system rcp command, the Cisco IOS software sends the hostname as both the remote
and local usernames by default. Before the rcp can execute properly, an account must be defined on the
network server for the remote username configured on the router.
If the server has a directory structure, the rcp software searches for the system image to boot from the
remote server relative to the directory of the remote username.
By default, the router software sends the hostname as the remote username. You can override the default
remote username by using the ip rcmd remote-username command. For example, if the system image
resides in the home directory of a user on the server, you can specify that users name as the remote
username.
Understanding TFTP
You need a TFTP server running to retrieve the router image from the host.
Understanding FTP
A through B
boot system
You need an FTP server running to retrieve the router image from the host. You also need an account on
the server or anonymous file access to the server.
Stopping Booting and Entering ROM Monitor Mode
During the first 60 seconds of startup, you can force the router to stop booting by pressing the Break key.
The router will enter ROM monitor mode, where you can change the configuration register value or boot
the router manually.
Cisco 1600 Series, Cisco 3600 Series, Cisco 7000 Family, and Cisco 7600 Series Router Notes
For the Cisco 3600 series and Cisco 7000 family, the boot system command modifies the BOOT variable
in the running configuration. The BOOT variable specifies a list of bootable images on various devices.
Note
When you use the boot system command on the Cisco 1600 series, Cisco 3600 series, Cisco 7000 family,
and Cisco 7600 series, you affect only the running configuration. You must save the BOOT variable
settings to your startup configuration to place the information under ROM monitor control and to have the
variable function as expected. Use the copy system:running-config nvram:startup-config privileged
EXEC command to save the variable from your running configuration to your startup configuration.
To display the contents of the BOOT variable, use the show bootvar EXEC command.
Examples
The following example illustrates a configuration that specifies two possible internetwork locations for a
system image, with the ROM software being used as a backup:
Router(config)# boot system tftp://192.168.7.24/cs3-rx.90-1
Router(config)# boot system tftp://192.168.7.19/cs3-rx.83-2
Router(config)# boot system rom
The following example boots the system boot relocatable image file named igs-bpx-l from partition 2 of the
flash device:
Router(config)# boot system flash:2:igs-bpx-l
The following example instructs the router to boot from an image located on the flash memory card
inserted in slot 0:
Router(config)# boot system slot0:new-config
The following example specifies the file named new-ios-image as the system image for a Cisco 3600 series
router to load at startup. This file is located in the fourth partition of the flash memory card in slot 0.
Router(config)# boot system slot0:4:dirt/images/new-ios-image
This example boots from the image fi le named c1600-y-l in part ition 2 of flash memory of a Cisco 1600
series router:
Router(config)# boot system flash:2:c1600-y-l
A through B
boot system
Related Commands
Command
Description
boot
config-register
confreg
copy
show bootvar
A through B
boot-end-marker
boot-end-marker
The boot-start-marker and boot-end-marker flags, which can be seen in Cisco IOS software
configuration files, are not CLI commands. These markers are written to configuration files automatically
to flag the beginning and end of the boot commands (boot statements). By flagging boot statements, these
markers allow the router to more reliably load Cisco IOS images during bootup.
A boot statement is one or more lines in a configuration file that tells the router which software image to
load after a powercycling (reboot). The boot-start-marker and boot-end-marker flags will appear around
any boot commands, including:
boot bootstrap
boot config
boot host
boot network
boot system
Note, however, that these markers will always appear in the output of the show running-configor more
system:running-config commands, regardless of whether any actual boot commands have been entered.
This means that no boot commands will appear between the markers if no boot commands have been
entered, or if all boot commands have been removed from the configuration, as shown in the Examples
section.
The boot-start-marker and boot-end-markerflags cannot be removed or modified using the CLI. These
markers are written to the startup configuration file whenever a copy running-config startup-config
command is issued.
These flags were also introduced to circumvent errors in the configuration file, such as a leading space
before a boot command (such as those sometimes introduced by manually edited configuration files), or the
use of text strings that include the word boot in banners or other user-specified text.
If the boot start-marker flag is not found in the configuration file, the system will use the traditional
method to identify the boot commands. However, if you are manually creating configuration files, or
copying from older Cisco IOS software releases, the addition of these markers is recommended.
Command History
Examples
Release
Modification
In the following example, a boot command is entered, and the boot-start-marker and boot-end-marker flags
are shown in the context of the startup configuration file:
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# boot system slot0:
Router(config)# end
Router# copy running-config startup-config
Router# show startup-config
A through B
boot-end-marker
In the following example, the boot-start-marker and boot-end-marker flags appear in the configuration file
even though no boot commands have been entered:
Router# show running-configuration
Current configuration :3055 bytes
!
! No configuration change since last restart
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
.
.
.
Related Commands
Command
Description
boot bootstrap
boot config
boot host
Specifies a remote host location for the hostspecific (router-specific) configuration file to be
used at the next system startup.
boot network
boot system
A through B
boot-end-marker
A through B
boot-start-marker
boot-start-marker
The boot-start-marker and boot-end-marker flags, which can be seen in Cisco IOS software
configuration files, are not CLI commands. These markers are written to configuration files automatically
to flag the beginning and end of the boot commands (boot statements). By flagging boot statements, these
markers allow the router to more reliably load Cisco IOS images during bootup.
A boot statement is one or more lines in a configuration file that tells the router which software image to
load after a powercycling (reboot). The boot-start-marker and boot-end-marker flags will appear around
any boot commands, including:
boot bootstrap
boot config
boot host
boot network
boot system
Note, however, that these markers will always appear in the output of the show running-configor more
system:running-config commands, regardless of whether any actual boot commands have been entered.
This means that no boot commands will appear between the markers if no boot commands have been
entered, or if all boot commands have been removed from the configuration, as shown in the Examples
section.
The boot-start-marker and boot-end-markerflags cannot be removed or modified using the CLI. These
markers are written to the startup configuration file whenever a copy running-config startup-config
command is issued.
These flags were also introduced to circumvent errors in the configuration file, such as a leading space
before a boot command (such as those sometimes introduced by manually edited configuration files), or the
use of text strings that include the word boot in banners or other user-specified text.
If the boot start-marker flag is not found in the configuration file, the system will use the traditional
method to identify the boot commands. However, if you are manually creating configuration files, or
copying from older Cisco IOS software releases, the addition of these markers is recommended.
Command History
Modification
Release
Examples
In the following example, a boot command is entered, and the boot-start-marker and boot-end-marker flags
are shown in the context of the startup configuration file:
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# boot system slot0:
Router(config)# end
Router# copy running-config startup-config
Router# show startup-config
A through B
boot-start-marker
In the following example, the boot-start-marker and boot-end-marker flags appear in the configuration file
even though no boot commands have been entered:
Router# show running-configuration
Current configuration :3055 bytes
!
! No configuration change since last restart
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
.
.
.
Related Commands
Command
Description
boot bootstrap
boot config
boot host
Specifies a remote host location for the hostspecific (router-specific) configuration file to be
used at the next system startup.
boot network
boot system
A through B
boot-start-marker
A through B
boot-start-marker
C commands
cd, page 87
clear archive log config, page 89
clear catalyst6000 traffic-meter, page 91
clear configuration lock, page 92
clear diagnostic event-log, page 94
clear ip http client cache, page 96
clear logging, page 98
clear logging system, page 100
clear logging xml, page 102
clear memory low-water-mark, page 104
clear mls statistics, page 105
clear parser cache, page 107
clear parser statistics, page 109
clear platform netint, page 111
clear processes interrupt mask, page 112
clear scp accounting, page 114
clear tcp, page 115
clear vlan counters, page 117
clock, page 118
clock initialize nvram, page 120
config-register, page 121
configure check syntax, page 123
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M
train.), page 124
configure confirm, page 131
configure memory, page 133
configure network, page 135
configure overwrite-network, page 136
configure replace, page 137
configure revert, page 142
configure terminal, page 144
confreg, page 147
continue (ROM monitor), page 149
copy, page 151
copy erase flash, page 170
C commands
C commands
cd
cd
To change the default directory or file system, use the cd command in user EXEC or privileged EXEC
mode.
cd [filesystem:] [directory]
Syntax Description
Command Default
filesystem :
directory
The initial default file system is flash:. For platforms that do not have a physical device named flash:, the
keyword flash: is aliased to the default Flash device.
For the Supervisor Engine, the initial default file system is disk0 :
If you do not specify a directory on a file system, the default is the root directory on that file system.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
11.0
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
For systems that are configured with a Supervisor Engine 2, valid values are bootflash:,
const_nvram:, disk0:, flash:, nvram:, slot0:, sup-slot0:, and sup-bootflash:
For systems that are configured with a Supervisor Engine 720, valid values are disk0: and disk1:
For all EXEC commands that have an optional filesystemargument, the system uses the file system
specified by the cd command when you omit the optional filesystemargument. For example, the
C commands
cd
dircommand, which displays a list of files on a file system, contains an optional filesystemargument. When
you omit this argument, the system lists the files on the file system specified by the cd command.
If you do not specify a directory on a file system, the default is the root directory on that file system.
Examples
In the following example, the cd command is used to set the default file system to the Flash memory card
inserted in slot 0:
Router# pwd
bootflash:/
Router# cd slot0:
Router#
pwd
slot0:/
Related Commands
Command
Description
copy
delete
dir
mkdir disk0:
pwd
undelete
C commands
clear archive log config
Syntax Description
force
persistent
Command Default
If this command is not used, the database entries accumulate in the archive log.
Command Modes
Command History
Release
Modification
12.2(33)SRA
12.4(11)T
12.2(33)SXH
12.2(33)SB
Usage Guidelines
When the clear archive log configcommand is entered, only the entries in the configuration logging
database file are deleted. The file itself is not deleted; it will be used in the future to log new entries as they
occur.
Examples
The following example clears the database entries that have been saved to the config log without asking
you to confirm the action before the entries are cleared:
Router# clear archive log config force
C commands
clear archive log config
Related Commands
Command
Description
C commands
clear catalyst6000 traffic-meter
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(17a)SX
12.2(17d)SXB
12.2(33)SRA
C commands
clear configuration lock
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(25)S
12.3(14)T
12.0(31)S
12.2(28)SB
12.2(33)SRA
12.2(33)SXH
The following is sample output from the clear configuration lockcommand when the running
configuration file is not locked by the configure replace command:
Router# clear configuration lock
Parser Config not locked.
The following is sample output from the clear configuration lockcommand when the running
configuration file is locked by the configure replace command:
Router# clear configuration lock
Process <3> is holding the EXCLUSIVE lock !
Do you want to clear the lock?[confirm] y
C commands
clear configuration lock
The following example shows how to use the clear configuration lock command to display the owner or
process ID of the lock and prompt the user for confirmation:
Router# clear configuration lock
Process <46> is holding the EXCLUSIVE lock.
Do you want to clear the lock?[confirm] y
After the lock is cleared, a message will be sent to the terminal if the owner of the lock is a TTY user:
Router(config)# The configuration lock was cleared by user <steve> from terminal <5>
Related Commands
Command
Description
C commands
clear diagnostic event-log
Syntax Description
event-type error
event-type info
event-type warning
module all
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SXH
The clear diagnostic event-log command clears all the events for all the modules.
The clear diagnostic event-log module num command clears events only for a specific module.
The clear diagnostic event-log event-typecommand clears only specific event types such as error,
informative, or warning events.
Examples
C commands
clear diagnostic event-log
This example shows how to clear error event logs on all the modules:
Router# clear diagnostic event-log module all
Related Commands
Command
Description
C commands
clear ip http client cache
Syntax Description
cache all
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(31)SB2
Usage Guidelines
Use this command to clear entries from the HTTP client cache pool: all the entries, all the entries owned by
a specific session, or only the entry associated with a specific request from an HTTP server.
Examples
The following example clears all entries in the HTTP client cache:
Router# clear ip http client cache all
The following example removes HTTP client cache entries that belong to the HTTP Client File System
(CFS) application:
Router# clear ip http client cache session HTTP CFS
C commands
clear ip http client cache
The following example removes HTTP client cache entries at the location http://myrouter.cisco.com/flash:/:
Router# clear ip http client cache url http://myrouter.cisco.com/flash:/
Related Commands
Command
Description
ip http path
C commands
clear logging
clear logging
To clear messages from the logging buffer, use the clear logging command in privileged EXEC mode.
clear logging [persistent [url filesystem:/directory]]
Syntax Description
Command Modes
Command History
persistent
url
filesystem:
/directory
Release
Modification
11.2
12.2(33)SRA
Usage Guidelines
The clear logging persistent command is used to remove stored audit records. This action can be
performed by the audit administrator only. The clear logging persistentcommand clears only log files
stored in the directory but does not remove the directory itself. If no log URL is not specified for logging,
this command clears files from the location as specified in the logging persistent command.
Examples
C commands
clear logging
The following example shows how to clear persistent logging files from a specific directory:
Router# clear logging persistent url harddisk:/log-persistant
Delete persistent logging files from harddisk:/log-persistent ? [confirm]
Router# dir harddisk:/log-persistant
Directory of harddisk:////log-persistent/
No files in directory
Related Commands
Command
Description
logging buffered
logging persistent
show logging
C commands
clear logging system
Syntax Description
disk name
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SXH
12.2(33)SCC
SEA is supported on switches that have a Supervisor Engine 32 or Supervisor Engine 720 with a compact
flash adapter and a Compact Flash card (WS-CF-UPG= for Supervisor Engine 720).
Cisco Universal Broadband Router 10012
The SEA feature is used to address debug trace and system console constraints. SEA is a logging feature
that allows the modules in the system to report major and critical events to the route processor (RP). The
events occurring on the line card or jacket card are also sent to the RP using Inter-Process Communication
(IPC) capability. Use the clear logging system command to clear the event records stored in the SEA log
file.
Note
To store the system event logs, the SEA requires either the PCMCIA ATA disk or Compact Flash Disk in
compact flash adapter for PRE2.
C commands
clear logging system
Examples
Related Commands
logging system
C commands
clear logging xml
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(15)T
12.2(28)SB
12.2(33)SRE
Usage Guidelines
This command clears the contents of the XML-formatted logging buffer, but does not clear the contents of
the standard logging buffer. The system will prompt you to confirm the action before clearing the buffer.
Examples
Related Commands
Command
Description
C commands
clear logging xml
Command
Description
C commands
clear memory low-water-mark
Syntax Description
Command Modes
Command History
Release
Modification
15.0(1)M
12.2(33)SRB
12.2(33)SXI
Usage Guidelines
This command clears all processor threshold values and the input/output memory threshold values, if any.
Examples
Related Commands
Command
Description
C commands
clear mls statistics
Syntax Description
module num
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.(17d)SXB1
12.2(17d)SXB5
12.2(33)SRA
Usage Guidelines
This command replaces the clear mls stats command, which was introduced on the Supervisor Engine 720
in Cisco IOS Release 12.2(17a)SX, and on the Supervisor Engine 2 in Cisco IOS Release 12.2(17d)SXB.
Examples
This example shows how to reset the MLS statistics counters for all modules:
Router#
clear mls statistics
Router#
This example shows how to reset the MLS statistics counters for a specific module:
Router#
clear mls statistics module 5
Router#
C commands
clear mls statistics
Related Commands
Command
Description
C commands
clear parser cache
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.1(5)T
12.2(33)SRA
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
The clear parser cache command will free the system memory used by the Parser Cache feature and will
erase the hit/miss statistics stored for the output of the show parser statistics EXEC command. This
command is only effective when the Parser Cache feature is enabled.
Examples
C commands
clear parser cache
Related Commands
Command
Description
parser cache
C commands
clear parser statistics
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
15.0S
Usage Guidelines
The clear parser statistics command will free the system memory used for recording parser performance
statistics stored for the output of the show parser statistics EXEC command..
Examples
C commands
clear parser statistics
Bootup hits:125
Bootup misses:43
Bootup clear parser cache:0
Router# clear parser statistics
func=E01730, duration=0 cmd= clear parser statistics
Router# show parser statistics
Last configuration file parsed: Number of Commands: 0, Time: 0 ms
Parser cache: enabled, 130 hits, 47 misses
Active startup time: 0
Standby startup time: 0
Copy to running-config time:0
Bulksync time:0
Top 10 slowest command:
Function
Time (ms) Command
Parser last bootup cache hits:
Bootup hits:0
Bootup misses:0
Bootup clear parser cache:0
Related Commands
Command
Description
parser cache
C commands
clear platform netint
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
This example shows how to clear the interrupt-throttling counters for the platform:
Router#
clear platform netint
Router#
Related Commands
Command
Description
C commands
clear processes interrupt mask
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
12.4(2)T
Usage Guidelines
See the documentation of the scheduler interrupt mask commands (listed in the Related Commands
table) for further details on process interrupt mask profiling.
Examples
The following example demonstrates how to the clear interrupt mask statistics from system memory for all
processes:
Router# clear processes interrupt mask detail
Related Commands
Command
Description
C commands
clear processes interrupt mask
Command
Description
C commands
clear scp accounting
Syntax Description
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SXI
The following example shows how to clear the SCP accounting information:
Router# clear scp accounting
Related Commands
Command
Description
show scp
C commands
clear tcp
clear tcp
To clear a TCP connection, use the clear tcpcommand in privileged EXEC mode.
clear tcp {line line-number | local hostname port remote hostname port | tcb address}
Syntax Description
Command Modes
Command History
Usage Guidelines
line line-number
tcb address
Privileged EXEC
Release
Modification
11.1
12.2(33)SRA
The clear tcp command is particularly useful for clearing hung TCP connections.
The clear tcp line line-numbercommand terminates the TCP connection on the specified tty line.
Additionally, all TCP sessions initiated from that tty line are terminated.
The clear tcp local hostname port remote hostname portcommand terminates the specific TCP connection
identified by the host name and port pair of the local and remote router.
The clear tcp tcb address command terminates the specific TCP connection identified by the TCB address.
Examples
The following example clears a TCP connection using its tty line number. The show tcp command displays
the line number (tty2) that is used in the clear tcp command.
Router# show tcp
tty2, virtual tty from host router20.cisco.com
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 171.69.233.7, Local port: 23
Foreign host: 171.69.61.75, Foreign port: 1058
C commands
clear tcp
snduna: 4151109752
rcvnxt: 1249472032
Next
0x0
0x0
0x0
0x0
0x0
0x0
0x0
sndnxt: 4151109752
rcvwnd:
4258
sndwnd:
delrcvwnd:
24576
30
SRTT: 710 ms, RTTO: 4442 ms, RTV: 1511 ms, KRTT: 0 ms
minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms
Router# clear tcp line 2
[confirm]
[OK]
The following example clears a TCP connection by specifying its local router host name and port and its
remote router host name and port. The show tcp brief command displays the local (Local Address) and
remote (Foreign Address) host names and ports to use in the clear tcp command.
Router# show tcp brief
TCB
Local Address
Foreign Address
(state)
60A34E9C router1.cisco.com.23
router20.cisco.1055 ESTAB
Router# clear tcp local router1 23 remote router20 1055
[confirm]
[OK]
The following example clears a TCP connection using its TCB address. The show tcp brief command
displays the TCB address to use in the clear tcp command.
Router# show tcp brief
TCB
Local Address
60B75E48 router1.cisco.com.23
Foreign Address
router20.cisco.1054
(state)
ESTAB
Related Commands
Command
Description
show tcp
C commands
clear vlan counters
Syntax Description
vlan-id
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
If you do not specify a vlan-id; the software-cached counter values for all existing VLANs are cleared.
Examples
This example shows how to clear the software-cached counter values for a specific VLAN:
Router# clear vlan 10 counters
Clear "show vlan" counters on this vlan [confirm]y
Router#
Related Commands
Command
Description
C commands
clock
clock
To configure the port clocking mode for the 1000BASE-T transceivers, use the clock command in interface
configuration mode. To return to the default settings,use the no form of this command.
clock {auto | active [prefer] | passive [prefer]}
no clock
Syntax Description
auto
active
prefer
passive
Command Default
auto
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
12.2(17a)SX
12.2(33)SRA
auto --Auto negotiates with the far end of the link but preference is given to the active-clock switch.
active --Uses a local clock to determine transmitter-operation timing.
C commands
clock
passive --Recovers the clock from the received signal and uses the recovered clock to determine
transmitter-operation timing.
active prefer --Auto negotiates with the far end of the link but preference is given to the active-clock
switch.
passive prefer --Auto negotiates with the far end of the link but preference is given to the passiveclock switch.
Enter the show running-config interface command to display the current clock mode.
Enter the show interfaces command to display the clock mode that is negotiated by the firmware.
Examples
Related Commands
Command
Description
show interfaces
C commands
clock initialize nvram
Syntax Description
Command Default
By default, the system clock is set to restart from the last known system clock value for platforms that have
no hardware calendar.
Command Modes
Command History
Release
Modification
12.3(4)T
Usage Guidelines
For platforms that have hardware calendars, the clock initialize nvram command is not available. When
the no form of the command is configured, the system clock gets initialized to default standard values. The
default values can be either 1MAR1993 or 1MAR2002.
Examples
The following example shows how to set the system clock to restart from the last known system clock
value:
Router(config)# clock initialize nvram
C commands
config-register
config-register
To change the configuration register settings, use the config-register command in global configuration
mode.
config-register value
Syntax Description
value
Command Default
Refer to the documentation for your platform for the default configuration register value. For many newer
platforms, the default is 0x2102, which causes the router to boot from Flash memory and the Break key to
be ignored.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
This command applies only to platforms that use a software configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field
determines if the router boots manually, from ROM, or from Flash or the network.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
If you set the configuration register boot field value to 0x0, you must boot the operating system
manually with the boot command.
C commands
config-register
If you set the configuration register boot field value to 0x1, the router boots using the default ROM
software.
If you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot
field value to form a default boot filename for booting from a network server.
For more information about the configuration register bit settings and default filenames, refer to the
appropriate router hardware installation guide.
Note
Examples
In a virtual switch application, If you have configured your config-register with a value that would skip file
parsing during the bootup process, your change to either a standalone or virtual switch will not take place
until you reconfigure your config-register. The config-register must be allowed to parse files in order to
ensure the conversion from either a standalone or virtual switch.
In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x2102
Related Commands
Command
Description
boot system
confreg
show version
C commands
configure check syntax
Syntax Description
source-location
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SRB
The following example shows how to check the syntax configuration using the configure check syntax
command:
Router# configure check syntax revrcsf:
Related Commands
Command
Description
configure revert
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
Effective with Cisco IOS XE Release 3.1S, the configuration mode exclusive command is replaced by the
parser command serializer command. See the parser command serializer command for more
information.
To enable single-user (exclusive) access functionality for the Cisco IOS command-line interface (CLI), use
the configuration mode exclusive command in global configuration mode. To disable the single-user
access (configuration locking) feature, use the no form of this command.
configuration mode exclusive {auto | manual} [expire seconds] [lock-show] [interleave]
[terminate] [config-wait seconds] [retry-wait seconds]
no configuration mode exclusive
Syntax Description
auto
manual
expire seconds
lock-show
interleave
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
config-wait seconds
retry-wait seconds
Command Default
Command Modes
Command History
Release
Modification
12.3(14)T
12.0(31)S
12.2(33)SRA
12.2(33)SB
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
Release
Modification
12.2(33)SXI
15.0(1)S
Usage Guidelines
Note
As of the 15.0 release, the configuration mode exclusive command is no longer available on the S and T
trains.
The configuration mode exclusive command enables the exclusive configuration lock feature. The
exclusive configuration lock allows single-user access to configuration modes using single-user
configuration mode. While the device configuration is locked, no other users can enter configuration
commands.
Users accessing the device using the state-full, session-based transports (telnet, Secure Shell (SSH) are able
to enter single-user configuration mode. The user enters single-user configuration mode by acquiring the
exclusive configuration lock using the configure terminal lock privileged EXEC mode command. The
configuration lock is released when the user exits configuration mode by using the end or exit command,
or by pressing Ctrl-Z. While a user is in single-user configuration mode, no other users can configure the
device. Users accessing Command Line Interface (CLI) options through stateless protocols (that is, the
HTTP web-based user interface) cannot access single-user configuration mode. (However, an Application
Programming Interface (API) allows the stateless transports to lock the configuration mode, complete its
operations, and release the lock.)
Examples
The following example shows how to configure the configuration file for single-user autoconfiguration
mode by using the configuration mode exclusive auto command. Use the configuration terminal
command to enter global configuration mode and lock the configuration mode exclusively. After the Cisco
IOS configuration mode is locked exclusively, you can verify this configuration by entering the show
configuration lockcommand.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# configuration mode exclusive auto
Router(config)# end
Router# show running-configuration
| include config
Building configuration...
Current configuration : 2296 bytes
configuration mode exclusive auto <========== auto policy
Router# configure terminal ?
<======== lock option not displayed when in auto policy
Router# configure terminal
<======= acquires the lock
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
The configuration mode is locked exclusively. The lock is cleared after you exit from configuration mode
by entering the end or exitcommand.
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Router(config)# show configuration lock
Parser Configure Lock
--------------------Owner PID : 3
User : unknown
TTY : 0
Type : EXCLUSIVE
State : LOCKED
Class : EXPOSED
Count : 1
Pending Requests : 0
User debug info : configure terminal
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 6
Lock Expiration timer (in Sec) : 593
Router(config)#
Router(config)# end
<========= releases the lock
Router#
Router# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 0
Lock Expiration timer (in Sec) : 0
The following example shows how to enable the exclusive locking feature in manual mode by using the
configuration mode exclusive manual command. Once you have configured manual exclusive mode, you
can lock the configuration mode by using the configure terminal lock command. In this mode, the
configure terminal command does not automatically lock the parser configuration mode. The lock is
cleared after you exit from configuration mode by entering the end or exit command.
Router# configure terminal
Configuration mode locked exclusively. The lock will be cleared once you exit out of
configuration mode using end/exit
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# configuration mode exclusive manual
Router(config)# end
Router#
Router# show running-configuration
| include configuration
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
Building configuration...
Current configuration : 2298 bytes
configuration mode exclusive manual <==== 'manual' policy
Router# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 0
Lock Expiration timer (in Sec) : 0
Router#
Router# configure terminal ?
lock Lock configuration mode <========= 'lock' option displayed in 'manual' policy
Router# configure terminal <============ configure terminal won't acquire lock
automatically
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 0
Lock Expiration timer (in Sec) : 0
Router(config)# end
Router# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 0
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
Configuration mode is locked exclusively. The lock is cleared after you exit from configuration mode by
entering the end or exit command. Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# show configuration lock
Parser Configure Lock
--------------------Owner PID : 3
User : unknown
TTY : 0
Type : EXCLUSIVE
State : LOCKED
Class : EXPOSED
Count : 1
Pending Requests : 0
User debug info : configure terminal lock
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 5
Lock Expiration timer (in Sec) : 594
Router(config)# end
<================ 'end' releases exclusive configuration lock
Router# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 0
Lock Expiration timer (in Sec) : 0
Router#
Related Commands
Command
Description
configure terminal
C commands
configuration mode exclusive (Deprecated as of the 15.0S and T releases. It's still available on the M train.)
Command
Description
C commands
configure confirm
configure confirm
To confirm replacement of the current running configuration with a saved Cisco IOS configuration file, use
the configure confirm command in privileged EXEC mode.
configure confirm
Syntax Description
Command Modes
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(33)SXH
12.2(33)SB
12.2(33)SXI
The configure confirm command is used only if the time seconds keyword and argument of the configure
replace command are specified. If the configure confirm command is not entered within the specified
time limit, the configuration replace operation is automatically reversed (in other words, the current
running configuration file is restored to the configuration state that existed prior to entering the configure
replace command).
C commands
configure confirm
Examples
The following example shows the use of the configure replace command with the time seconds keyword
and argument. You must enter the configure confirm command within the specified time limit to confirm
replacement of the current running configuration file:
Router# configure replace nvram:startup-config time 120
This will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
configuration. Enter Y if you are sure you want to proceed. ? [no]: Y
Total number of passes: 1
Rollback Done
Router# configure confirm
Related Commands
Command
Description
archive config
configure replace
maximum
path (config-archive)
show archive
time-period
C commands
configure memory
configure memory
To configure the system from the system memory, use the configure memory command in privileged
EXEC mode.
configure memory
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
On all platforms except Class A Flash file system platforms, this command executes the commands located
in the configuration file in NVRAM (the startup configuration file).
On Class A Flash file system platforms, if you specify the configure memory command, the router
executes the commands pointed to by the CONFIG_FILE environment variable. The CONFIG_FILE
environment variable specifies the location of the configuration file that the router uses to configure itself
during initialization. The file can be located in NVRAM or any of the Flash file systems supported by the
platform.
When the CONFIG_FILE environment variable specifies NVRAM, the router executes the NVRAM
configuration only if it is an entire configuration, not a distilled version. A distilled configuration is one that
does not contain access lists.
To view the contents of the CONFIG_FILE environment variable, use the show bootvar EXEC command.
To modify the CONFIG_FILE environment variable, use the boot config command and then save your
changes by issuing the copy system:running-config nvram:startup-config command.
Examples
In the following example, a router is configured from the configuration file in the memory location pointed
to by the CONFIG_FILE environment variable:
Router# configure memory
C commands
configure memory
Related Commands
Command
Description
boot config
show bootvar
C commands
configure network
configure network
The configure network command was replaced by the copy{rcp| tftp} running-config command in Cisco
IOS Release 11.0. To maintain backward compatibility, the configure network command continues to
function in Cisco IOS Release 12.2(11)T for most systems, but support for this command may be removed
in a future release.
The copy{rcp| tftp} running-config command was replaced by the copy {ftp: | rcp: | tftp:}[filename]
system: running-config command in Cisco IOS Release 12.1.
The copy {ftp: | rcp: | tftp:}[filename] system: running-config command specifies that a configuration
file should be copied from a FTP, rcp, or TFTP source to the running configuration. See the description of
the copy command in this chapter for more information.
C commands
configure overwrite-network
configure overwrite-network
The configure overwrite-network has been replaced by the copy {ftp-url | rcp-url | tftp-url
nvram:startup-config command. See the description of the copycommand in the Cisco IOS File System
Commands chapter for more information.
C commands
configure replace
configure replace
To replace the current running configuration with a saved Cisco IOS configuration file, use the configure
replace command in privileged EXEC mode.
configure replace target-url [nolock] list force ignorecase [revert trigger [error] [timer minutes] |
time minutes]
Syntax Description
target-url
nolock
list
force
ignorecase
revert trigger
C commands
configure replace
time minutes
Command Modes
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SXI
12.4(20)T
12.2(33)SRC
12.2(33)SB
When configuring more than one keyword option, the following rules apply:
The list keyword must be entered before the force and time keywords.
The force keyword must be entered before the time keyword.
C commands
configure replace
If the current running configuration is replaced with a saved Cisco IOS configuration file that contains
commands unaccepted by the Cisco IOS software parser, an error message is displayed listing the
commands that were unaccepted. The total number of passes performed in the configuration replace
operation is also displayed.
In Cisco IOS Release 12.2(25)S, a locking feature for the configuration replace operation was introduced.
When the configure replace command is enabled, the Cisco IOS running configuration file is locked by
default for the duration of the configuration replace operation. This locking mechanism prevents other users
from changing the running configuration while the replace operation is taking place, which might otherwise
cause the replace operation to terminate unsuccessfully. You can disable the locking of the running
configuration using the configure replace nolock command.
The running configuration lock is automatically cleared at the end of the configuration replace operation. It
is not expected that you should need to clear the lock manually during the replace operation, but as a
protection against any unforeseen circumstances, you can manually clear the lock using the clear
configuration lock command. You can also display any locks that may be currently applied to the running
configuration using the show configuration lock command.
Examples
configure replace,
configure replace,
configure replace,
configure replace,
page 137
page 137
page 137
page 137
Replacing the Current Running Configuration with a Saved Cisco IOS Configuration File
The following example shows how to replace the current running configuration with a saved Cisco IOS
configuration file named disk0:myconfig. Note that the configure replace command interactively prompts
you to confirm the operation.
Router# configure replace disk0:myconfig
This will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
configuration. Enter Y if you are sure you want to proceed. ? [no]: Y
Total number of passes: 1
Rollback Done
In the following example, the list keyword is specified to display the command lines that were applied
during the configuration replace operation:
Router# configure replace disk0:myconfig list
This will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
configuration. Enter Y if you are sure you want to proceed. ? [no]: Y
!Pass 1
!List of Commands:
no snmp-server community public ro
snmp-server community mystring
ro
end
Total number of passes: 1
Rollback Done
C commands
configure replace
Note
The path command must be configured before using the archive config command.
You first save the current running configuration in the configuration archive as follows:
Router# archive config
After making changes to the running configuration file, you might want to roll back these changes and
revert to the configuration that existed before the changes were made. The show archive command is used
to verify the version of the configuration to be used as a target file. The configure replace command is
then used to revert to the target configuration file as shown in the following example:
Router# show archive
There are currently 1 archive configurations saved.
The next archive file will be named disk0:myconfig-2
Archive # Name
0
C commands
configure replace
1
disk0:myconfig-1 <- Most Recent
2
3
4
5
6
7
8
9
10
Router# configure replace disk0:myconfig-1
Total number of passes: 1
Rollback Done
Related Commands
Command
Description
archive config
configure confirm
maximum
path
show archive
time-period
C commands
configure revert
configure revert
To cancel the timed rollback and trigger the rollback immediately, or to reset parameters for the timed
rollback, use the configure revertcommand in privileged EXEC mode.
configure revert {now | timer {minutes | idle minutes}}
Syntax Description
Command Modes
Command History
Usage Guidelines
now
timer
minutes
idle minutes
Release
Modification
12.2(33)SRC
12.2(33)SB
12.4(20)T
12.2(33)SXI
In order to use the configure revert command to configure a timed rollback, the Configuration Archive
functionality must be enable first. The Configuration Archive APIs are used to store the current
configuration before applying any changes or rolling back to the previous configuration.
In case of multi-user environments, only the user who enabled the timed rollback functionality will have
the permission to perform the following operations:
C commands
configure revert
Examples
The following example shows how to cancel the timed rollback and revert to the saved configuration
immediately:
Rourter(config)# archive
Router(config-archive)# path disk0:abc
Router# configure revert now
Related Commands
Command
Description
archive config
configure replace
maximum
path (config-archive)
show archive
time-period
C commands
configure terminal
configure terminal
To enter global configuration mode, use the configure terminal command in privileged EXEC mode.
configure terminal
Cisco IOS Releases 12.3(14)T and Subsequent Releases:
configure terminal [lock]
Cisco IOS Releases 12.2(33)SRC and Subsequent Releases:
configure terminal [revert {timer minutes | idle minutes}]
Syntax Description
Command Modes
Command History
lock
revert
timer minutes
idle minutes
Release
Modification
10.0
12.3(14)T
12.0(31)S
12.2(33)SRA
C commands
configure terminal
Usage Guidelines
Release
Modification
12.4(20)T
12.2(33)SB
12.2(33)SXI
Use this command to enter global configuration mode. Note that commands in this mode are written to the
running configuration file as soon as you enter them (using the Enter key/Carriage Return).
After you enter the configure terminalcommand, the system prompt changes from <router-name># to
<router-name>(config)# , indicating that the router is in global configuration mode. To leave global
configuration mode and return to privileged EXEC mode, type exit or press Ctrl-Z.
To view the changes to the configuration you have made, use the more system:running-config command
or show running-config command in user EXEC or privileged EXEC mode.
Configuration Locking
The first user to enter the configure terminal lockcommand acquires the configuration lock (exclusive
configuration mode).
Examples
The following example shows how to enter global configuration mode and lock the Cisco IOS software in
exclusive mode:
Router(config)# configure terminal lock
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Related Commands
Command
Description
boot config
or
copy system:running-config nvram:startupconfig
C commands
configure terminal
Command
Description
show running-config
or
more system:running-config
C commands
confreg
confreg
To change the configuration register settings while in ROM monitor mode, use the confreg command in
ROM monitor mode.
confreg [value]
Syntax Description
value
Command Default
Refer to your platform documentation for the default configuration register value.
Command Modes
ROM monitor
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Not all versions in the ROM monitor support this command. Refer to your platform documentation for
more information on ROM monitor mode.
If you use this command without specifying the configuration register value, the router prompts for each bit
of the configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field
determines if the router boots manually, from ROM, or from Flash or the network.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
If you set the configuration register boot field value to 0x0, you must boot the operating system
manually with the boot command.
If you set the configuration register boot field value to 0x1, the router boots using the default ROM
software.
If you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot
field value to form a default boot filename for booting from a network server.
For more information about the configuration register bit settings and default filenames, refer to the
appropriate router hardware installation guide.
C commands
confreg
Examples
In the following example, the configuration register is set to boot the system image from Flash memory:
confreg 0x210F
In the following example, no configuration value is entered, so the system prompts for each bit in the
register:
rommon 7 > confreg
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = the boot helper image
2-15 = boot system
[0]: 0
[0]:
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
You must reset or power cycle for new config to take effect.
rommon 8>
C commands
continue (ROM monitor)
Syntax Description
Command Default
Command Modes
ROM monitor
Command History
Usage Guidelines
Caution
Examples
Release
Modification
11.0
12.2(33)SRA
Use this command to return to EXEC mode from ROM monitor mode, to use the system image instead of
reloading. On older platforms, the angle bracket (< >) indicates that the router is in ROM monitor mode.
On newer platforms, rommon number> is the default ROM monitor prompt. Typically, the router is in
ROM monitor mode when you manually load a system image or perform diagnostic tests. Otherwise, the
router will most likely never be in this mode.
While in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a reset or
the continue command.
In the following example, the continue command switches the router from ROM monitor to EXEC mode:
> continue
Router#
C commands
continue (ROM monitor)
Related Commands
Command
Description
boot
C commands
copy
copy
To copy any file from a source to a destination, use the copy command in privileged EXEC or diagnostic
mode.
copy [/erase] [/verify | /noverify] source-url destination-url
Syntax Description
/erase
/noverify
destination-url
The exact format of the source and destination URLs varies according to the file or directory location. You
may enter either an alias keyword for a particular file or a filename that follows the standard Cisco IOS file
system syntax (filesystem :[/filepath ][/filename ]).
The table below shows two keyword shortcuts to URLs.
C commands
copy
Table 11
Keyword
Source or Destination
running-config
(Optional) Keyword alias for the system:runningconfig URL. The system:running-config keyword
represents the current running configuration file.
This keyword does not work in more and show file
EXEC command syntaxes.
startup-config
The following tables list URL prefix keywords by file system type. The available file systems will vary by
platform. If you do not specify a URL prefix keyword, the router looks for a file in the current directory.
The table below lists URL prefix keywords for Special (opaque) file systems.
Table 12
Keyword
Source or Destination
cns:
flh:
logging
modem:
null:
nvram:
obfl:
stby-nvram:
C commands
copy
Keyword
Source or Destination
stby-obfl:
system:
tar:
tmpsys:
xmodem:
ymodem:
The table belows lists URL prefix keywords for remote file systems.
Table 13
Keyword
Source or Destination
ftp:
http://
https://
rcp:
scp:
C commands
copy
Keyword
Source or Destination
tftp:
The table below lists URL prefix keywords for local writable storage file systems.
Table 14
Alias
Source or Destination
bootflash:
flash:
harddisk:
slavebootflash:
slaveram:
slaveslot0:
slaveslot1:
slot0:
slot1:
stby-bootflash:
stby-harddisk:
C commands
copy
Command Modes
Alias
Source or Destination
stby-usb [ 0-1 ] :
usb [ 0-1 ] :
usbflash 0 9 :
usbtoken [0 9] :
Command History
Release
Modification
11.3T
12.3(2)T
12.2(14)S
12.2(18)S
12.0(26)S
12.3(4)T
12.3(7)T
12.3(14)T
C commands
copy
Usage Guidelines
Release
Modification
12.2(28)SB
12.2(25)SG
12.4(11)T
12.2(33)SXH
The fundamental function of the copy command is to allow you to copy a file (such as a system image or
configuration file) from one location to another location. The source and destination for the file is specified
using a Cisco IOS File System URL, which allows you to specify any supported local or remote file
location. The file system being used (such as a local memory source, or a remote server) dictates the syntax
used in the command.
You can enter on the command line all necessary source- and destination-URL information and the
username and password to use, or you can enter the copy command and have the router prompt you for any
missing information.
For local file systems, two commonly used aliases exist for the system:running-config and
nvram:startup-config files; these aliases are running-config and startup-config, respectively.
Timesaver
Aliases are used to reduce the amount of typing you need to perform. For example, it is easier to type copy
run start (the abbreviated form of the copy running-config startup-config command) than it is to type
copy system:r nvram:s (the abbreviated form of the copy system:running-config nvram:startupconfigcommand). These aliases also allow you to continue using some of the common commands used in
previous versions of Cisco IOS software.
The entire copying process may take several minutes and differs from protocol to protocol and from
network to network.
The colon is required after the file system URL prefix keywords (such as flash). In some cases, file system
prefixes that did not require colons in earlier software releases are allowed for backwards compatibility, but
use of the colon is recommended.
In the URL syntax for ftp:, http:, https:, rcp:, scp: and tftp:, the location is either an IP address or a host
name. The filename is specified relative to the directory used for file transfers.
The following sections contain usage guidelines for the following topics:
Understanding Invalid Combinations of Source and Destination
Some invalid combinations of source and destination exist. Specifically, you cannot copy:
C commands
copy
Character
Description
Understanding Partitions
You cannot copy an image or configuration file to a flash partition from which you are currently running.
For example, if partition 1 is running the current system image, copy the configuration file or image to
partition 2. Otherwise, the copy operation will fail.
You can identify the available flash partitions by entering the show file system EXECcommand.
Using rcp
The rcp requires a client to send a remote username upon each rcp request to a server. When you copy a
configuration file or image between the router and a server using rcp, the Cisco IOS software sends the first
valid username it encounters in the following sequence:
1 The remote username specified in the copy command, if a username is specified.
2 The username set by the ip rcmd remote-username global configuration command, if the command is
configured.
3 The remote username associated with the current tty (terminal) process. For example, if the user is
connected to the router through Telnet and was authenticated through the username command, the
router software sends the Telnet username as the remote username.
4 The router host name.
For the rcp copy request to process, an account must be defined on the network server for the remote
username. If the network administrator of the destination server did not establish an account for the remote
C commands
copy
username, this command will not run. If the server has a directory structure, the configuration file or image
is written to or copied from the directory associated with the remote username on the server. For example,
if the system image resides in the home directory of a user on the server, specify that username as the
remote username.
If you are writing to the server, the rcp server must be properly configured to accept the rcp write request
from the user on the router. For UNIX systems, add an entry to the .rhosts file for the remote user on the
rcp server. Suppose the router contains the following configuration lines:
hostname Rtr1
ip rcmd remote-username User0
If the router IP address translates to Router1.company.com, then the .rhosts file for User0 on the rcp server
should contain the following line:
Router1.company.com Rtr1
Refer to the documentation for your rcp server for more details.
If you are using a personal computer as a file server, the computer must support the remote shell protocol
(rsh).
Using FTP
The FTP protocol requires a client to send a username and password with each FTP request to a remote
FTP server. Use the ip ftp username and ip ftp password global configuration commands to specify a
default username and password for all copy operations to or from an FTP server. Include the username in
the copy command syntax if you want to specify a username for that copy operation only.
When you copy a file from the router to a server using FTP, the Cisco IOS software sends the first valid
username that it encounters in the following sequence:
1 The username specified in the copy command, if a username is specified.
2 The username set by the ip ftp username command, if the command is configured.
3 Anonymous.
The router sends the first valid password in the following list:
1 The password specified in the copy command, if a password is specified.
2 The password set by the ip ftp password command, if the command is configured.
3 The router forms a password [email protected]. The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain
of the router.
The username and password must be associated with an account on the FTP server. If you are writing to the
server, the FTP server must be properly configured to accept the FTP write request from the user on the
router.
Note
The Syslog message will display 'xxxx' in place of the password entered in the syntax of the copy {ftp:}
command.
If the server has a directory structure, the configuration file or image is written to or copied from the
directory associated with the username on the server. For example, if the system image resides in the home
directory of a user on the server, specify that username as the remote username.
Refer to the documentation for your FTP server for details on setting up the server.
Using HTTP or HTTPS
C commands
copy
Copying a file to or from a remote HTTP or HTTPS server, to or from a local file system, is performed
using the embedded Secure HTTP client that is integrated in Cisco IOS software. The HTTP client is
enabled by default.
Downloading files from a remote HTTP or HTTPS server is performed using the HTTP client integrated in
Cisco IOS software.
If a username and password are not specified in the copy command syntax, the system uses the default
HTTP client username and password, if configured.
When you copy a file from a remote HTTP or HTTPS server, the Cisco IOS software sends the first valid
username that it encounters in the following sequence:
1 The username specified in the copy command, if a username is specified.
2 The username set by the ip http client username command, if the command is configured.
3 Anonymous.
The router sends the first valid password in the following list:
1 The password specified in the copy command, if a password is specified.
2 The password set by the ip http client password command, if the command is configured.
3 The router forms the password [email protected]. The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain
of the router.
Storing Images on Servers
Use the copy flash: destination-urlcommand (for example, copy flash: tftp:) to copy a system image or
boot image from flash memory to a network server. You can use the copy of the image as a backup copy.
Also, you can also use the image backup file to verify that the image in flash memory is the same as that in
the original file.
Copying from a Server to Flash Memory
Use the copy destination-url flash: command (for example, copy tftp: flash:) to copy an image from a
server to flash memory.
On Class B file system platforms, the system provides an option to erase existing flash memory before
writing onto it.
Note
Depending on the destination file system type, a checksum for the image file may be displayed when
the copy command completes. You can verify this checksum by comparing it to the checksum value
provided for your image file on Cisco.com.
C commands
copy
Caution
If the checksum values do not match, do not reboot the router. Instead, reissue the copycommand and
compare the checksums again. If the checksum is repeatedly wrong, copy the original image back into flash
memory beforeyou reboot the router from flash memory. If you have a corrupted image in flash memory
and try to boot from flash memory, the router will start the system image contained in ROM (assuming
booting from a network server is not configured). If ROM does not contain a fully functional system image,
the router might not function and will need to be reconfigured through a direct console port connection.
C commands
copy
Note
Some specific commands might not get saved to NVRAM. You will need to enter these commands again if
you reboot the machine. These commands are noted in the documentation. We recommend that you keep a
listing of these settings so you can quickly reconfigure your router after rebooting.
If you issue the copy system:running-config nvram:startup-configcommand from a bootstrap system
image, a warning will instruct you to indicate whether you want your previous NVRAM configuration to be
overwritten and configuration commands to be lost. This warning does not appear if NVRAM contains an
invalid configuration or if the previous configuration in NVRAM was generated by a bootstrap system
image.
On all platforms except Class A file system platforms, the copy system:running-config nvram:startupconfig command copies the currently running configuration to NVRAM.
On the Class A flash file system platforms, the copy system:running-config nvram:startup-config
command copies the currently running configuration to the location specified by the CONFIG_FILE
environment variable. This variable specifies the device and configuration file used for initialization. When
the CONFIG_FILE environment variable points to NVRAM or when this variable does not exist (such as at
first-time startup), the software writes the current configuration to NVRAM. If the current configuration is
too large for NVRAM, the software displays a message and stops executing the command.
When the CONFIG_FILE environment variable specifies a valid device other than nvram: (that is, flash:,
bootflash:, slot0:, or slot1:), the software writes the current configuration to the specified device and
filename, and stores a distilled version of the configuration in NVRAM. A distilled version is one that does
not contain access list information. If NVRAM already contains a copy of a complete configuration, the
router prompts you to confirm the copy.
Using CONFIG_FILE, BOOT, and BOOTLDR Environment Variables
For the Class A flash file system platforms, specifications are as follows:
The CONFIG_FILE environment variable specifies the configuration file used during router
initialization.
The BOOT environment variable specifies a list of bootable images on various devices.
The BOOTLDR environment variable specifies the flash device and filename containing the rxboot
image that ROM uses for booting.
Cisco 3600 routers do not use a dedicated boot helper image (rxboot), which many other routers use to
help with the boot process. Instead, the BOOTLDR ROM monitor environment variable identifies the
flash memory device and filename that are used as the boot helper; the default is the first system image
in flash memory.
To view the contents of environment variables, use the show bootvar EXEC command. To modify the
CONFIG_FILE environment variable, use the boot config global configuration command. To modify the
BOOTLDR environment variable, use the boot bootldr global configuration command. To modify the
BOOT environment variable, use the boot system global configuration command. To save your
modifications, use the copy system:running-config nvram:startup-configcommand.
When the destination of a copy command is specified by the CONFIG_FILE or BOOTLDR environment
variable, the router prompts you for confirmation before proceeding with the copy. When the destination is
the only valid image in the BOOT environment variable, the router also prompts you for confirmation
before proceeding with the copy.
Using the Copy Command with the Dual RSP Feature
The Dual RSP feature allows you to install two Route Switch Processor (RSP) cards in a single router on
the Cisco 7507 and Cisco 7513 platforms.
C commands
copy
On a Cisco 7507 or Cisco 7513 router configured for Dual RSPs, if you copy a file to nvram:startupconfiguration with automatic synchronization disabled, the system prompts whether you also want to copy
the file to the slave startup configuration. The default answer is yes. If automatic synchronization is
enabled, the system automatically copies the file to the slave startup configuration each time you use a
copy command with nvram:startup-configuration as the destination.
Using the copy command with the ASR1000 Series Routers
The copy command is available in both privileged EXEC and diagnostic mode on the Cisco ASR1000
series routers. Because the copycommand is available in diagnostic mode, it can be used to copy all types
of files between directories and remote locations even in the event of an IOS failure.
Examples
C commands
copy
Copying an Image from a Server to a Flash Memory Using Flash Load Helper Example
The following example copies a system image into a partition of flash memory. The system will prompt for
a partition number only if there are two or more read/write partitions or one read-only and one read/write
partition and dual flash bank support in boot ROMs. If the partition entered is not valid, the process
terminates. You can enter a partition number, a question mark (?) for a directory display of all partitions, or
a question mark and a number (? number) for directory display of a particular partition. The default is the
first read/write partition. In this case, the partition is read-only and has dual flash bank support in boot
ROM, so the system uses flash Load Helper.
Router# copy tftp: flash:
System flash partition information:
Partition
Size
Used
Free
Bank-Size
State
Copy-Mode
1
4096K
2048K
2048K
2048K
Read Only
RXBOOT-FLH
2
4096K
2048K
2048K
2048K
Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 2]
**** NOTICE ****
Flash load helper v1.0
This process will accept the copy options and then terminate
the current system image to use the ROM based image for the copy.
Routing functionality will not be available during that time.
If you are logged in via telnet, this connection will terminate.
Users with console access can see the results of the copy operation.
---- ******** ---Proceed? [confirm]
System flash directory, partition 1:
File Length
Name/status
1
3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 172.16.1.1
Source file name? master/igs-bfpx-100.4.3
Destination file name [default = source name]?
Loading master/igs-bfpx.100-4.3 from 172.16.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
C commands
copy
Copy an Image from Flash Memory to an SSH Server Using scp Example
The following example shows how to use scp to copy a system image from flash memory to a server that
supports SSH:
Router# copy flash:c4500-ik2s-mz.scp scp://user1@host1/
Address or name of remote host [host1]?
Destination username [user1]?
Destination filename [c4500-ik2s-mz.scp]?
Writing c4500-ik2s-mz.scp
Password:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you can use the server-side functionality, SSH, authentication, and authorization must be properly
configured so the router can determine whether a user is at the right privilege level. The scp server-side
functionality is configured with the ip scp server enable command.
Copy an Image from a Partition of Flash Memory to a Server Example
The following example copies an image from a particular partition of flash memory to an rcp server using a
remote username of netadmin1.
C commands
copy
The system will prompt if there are two or more partitions. If the partition entered is not valid, the process
terminates. You have the option to enter a partition number, a question mark (?) for a directory display of
all partitions, or a question mark and a number (? number) for a directory display of a particular partition.
The default is the first partition.
Router# configure terminal
Router# ip rcmd remote-username netadmin1
Router# end
Router# copy flash: rcp:
System flash partition information:
Partition
Size
Used
Free
Bank-Size
State
Copy-Mode
1
4096K
2048K
2048K
2048K
Read Only
RXBOOT-FLH
2
4096K
2048K
2048K
2048K
Read/Write Direct
[Type ?<number> for partition directory; ? for full directory; q to abort]
Which partition? [1] 2
System flash directory, partition 2:
File Length
Name/status
1
3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [ABC.CISCO.COM]?
Source file name? master/igs-bfpx.100-4.3
Destination file name [master/igs-bfpx.100-4.3]?
Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK
Copy 'master/igs-bfpx.100-4.3' from Flash to server
as 'master/igs-bfpx.100-4.3'? [yes/no] yes
!!!!...
Upload to server done
Flash copy took 0:00:00 [hh:mm:ss]
Copying an Image from a Flash Memory File System to an FTP Server Example
The following example copies the file c3600-i-mz from partition 1 of the flash memory card in slot 0 to an
FTP server at IP address 172.23.1.129:
Router# show slot0: partition 1
PCMCIA Slot0 flash directory, partition 1:
File Length
Name/status
1
1711088 c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Router# copy slot0:1:c3600-i-mz ftp://myuser:[email protected]/c3600-i-mz
Verifying checksum for '/tftpboot/cisco_rules/c3600-i-mz' (file # 1)... OK
Copy '/tftpboot/cisco_rules/c3600-i-mz' from Flash to server
as 'c3700-i-mz'? [yes/no] yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:23 [hh:mm:ss]
C commands
copy
C commands
copy
The following example shows the warning that the system provides if you try to save configuration
information from bootstrap into the system:
Router(boot)# copy system:running-config nvram:startup-config
Warning: Attempting to overwrite an NVRAM configuration written
by a full system image. This bootstrap software does not support
the full configuration command set. If you perform this command now,
some configuration commands may be lost.
Overwrite the previous NVRAM configuration?[confirm]
C commands
copy
In the following example, a default username and password for HTTP Client communications is
configured, and then the file sample.scr is copied from a secure HTTP server using HTTPS:
Router# configure terminal
Router(config)# ip http client username joeuser
Router(config)# ip http client password letmein
Router(config)# end
Router# copy https://www.example_secure.com/scripts/sample.scr flash:
In the following example, an HTTP proxy server is specified before using the copy http:// command:
Router# configure terminal
Router(config)# ip http client proxy-server edge2 proxy-port 29
Router(config)# end
Router# copy
http://
www.example.com/configs/config3 flash:/configs/config3
C commands
copy
Copying an Image from the Master RSP Card to the Slave RSP Card Example
The following example copies the router-image file from the flash memory card inserted in slot 1 of the
master RSP card to slot 0 of the slave RSP card in the same router:
Router# copy slot1:router-image slaveslot0:
Related Commands
Command
Description
boot config
boot system
cd
delete
dir
erase
ip rcmd remote-username
reload
show bootvar
verify bootflash:
C commands
copy erase flash
C commands
copy http
copy http
The copy http:// command is documented as part of the copy command.
C commands
copy https
copy https
The copy https:// command is documented as part of the copy command.
C commands
copy logging system
Syntax Description
target :
filename
Command Default
Command Modes
Command History
bootflash:
disk0:
disk1:
ftp:
http:
https:
rcp:
slavebootflash:
slavedisk0:
slavedisk1:
slavesup-bootdisk:
slavesup-bootflash:
sup-bootdisk:
sup-bootflash:
tftp:
Release
Modification
12.2(33)SXH
C commands
copy logging system
Usage Guidelines
Release
Modification
12.2(33)SCC
System Event Archive (SEA) is supported on switches that have a Supervisor Engine 32 or Supervisor
Engine 720 with a compact flash adapter and a Compact Flash card (WS-CF-UPG= for Supervisor Engine
720).
Cisco Universal Broadband Router 10012
The System Event Archive (SEA) feature is used to address the debug trace and system console constraints.
Use the copy logging systemcommand to copy the major and critical events stored in the sea_log.dat file,
to the destination file system.
Note
To store the system event logs, the SEA requires either the PCMCIA ATA disk or Compact Flash Disk in
compact flash adapter for PRE2.
The following example shows how to copy the SEA to the file system of disk0:
Router# copy logging system disk0:
Destination filename [sea_log.dat]?
The following example shows how to copy the SEA using the remote file copy function (rcp):
Router# copy logging system rcp:
Address or name of remote host []? 192.0.2.1
Destination username [Router]? username1
Destination filename [sea_log.dat]? /auto/tftpboot-users/username1/sea_log.dat
Related Commands
logging system
C commands
copy xmodem
copy xmodem
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX
workstation) to Flash memory on a Cisco 3600 series router using the Xmodem protocol, use the copy
xmodem: command in EXEC mode.
copy xmodem: flashfilesystem:
Syntax Description
Command Modes
Command History
Usage Guidelines
flash-filesystem :
EXEC
Release
Modification
11.2 P
12.2(15)T
12.2(33)SRA
This command is a form of the copy command. The copy xmodem: and copy xmodem commands are
identical. See the description of the copy command for more information.
Copying a file using FTP, rcp, or TFTP is much faster than copying a file using Xmodem. Use the copy
xmodem: command only if you do not have access to an FTP, TFTP, or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports
hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered
command to log all router messages sent to the console port during the file transfer.
Examples
The following example initiates a file transfer from a local or remote computer to the routers internal Flash
memory using the Xmodem protocol:
copy xmodem: flash:
C commands
copy xmodem
Related Commands
Command
Description
copy
copy ymodem:
C commands
copy ymodem
copy ymodem
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX
workstation) to Flash memory on a Cisco 3600 series router using the Ymodem protocol, use the copy
ymodem: command in EXEC mode.
copy ymodem: flashfilesystem:
Syntax Description
Command Modes
Command History
Usage Guidelines
flash-filesystem :
EXEC
Release
Modification
11.2 P
12.2(15)T
12.2(33)SRA
The copy ymodem: and copy ymodem commands are identical. See the description of the copycommand
for more information.
Copying a file using FTP, rcp, or TFTP is much faster than copying a file using Ymodem. Use the copy
ymodem: command only if you do not have access to an FTP, rcp, or TFTP server.
This copy operation is performed through the console or AUX port. The AUX port, which supports
hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered
command to log all router messages sent to the console port during the file transfer.
Examples
The following example initiates a file transfer from a local or remote computer to the routers internal Flash
memory using the Ymodem protocol:
copy ymodem: flash:
C commands
copy ymodem
Related Commands
Command
Description
copy xmodem:
C commands
copy noverify
copy noverify
To disable the automatic image verification for the current copy operation, use the copy /
noverifycommand.
copy /noverify source-url destination-url
Syntax Description
source-url
destination-url
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
The exact format of the source and destination URLs varies according to the file or directory location. You
may enter either an alias keyword for a particular file or an alias keyword for a file system type (not a file
within a type).
C commands
copy noverify
Timesaver
Aliases are used to cut down on the amount of typing that you need to perform. For example, it is easier to
type copy run start (the abbreviated form of the copy running-config startup-config command) than it is
to type copy system:r nvram:s (the abbreviated form of the copy system:running-config nvram:startupconfigcommand). These aliases allow you to continue using some of the common commands that are used
in previous versions of Cisco IOS software.
The table below shows two keyword shortcuts to URLs.
Table 16
Keyword
Source or Destination
running-config
startup-config
The following tables list aliases by file system type. If you do not specify an alias, the system looks for a
file in the current directory.
The table below lists the URL prefix aliases for special (opaque) file systems.
Table 17
Alias
Source or Destination
flh:
nvram:
null:
system:
xmodem:
ymodem:
C commands
copy noverify
The table below lists the URL prefix aliases for network file systems.
Table 18
Alias
Source or Destination
ftp:
rcp:
tftp:
The table below lists the URL prefix aliases for local writable storage file systems.
Table 19
Alias
Source or Destination
bootflash:
flash:
slavebootflash:
slaveram:
slavedisk0:
slavedisk1:
C commands
copy noverify
Alias
Source or Destination
slaveslot0:
slaveslot1:
slot0:
slot1:
You can enter on the command line all necessary source- and destination-URL information and the
username and password to use, or you can enter the copy command and have the switch prompt you for
any missing information.
If you enter information, choose one of the following three options: running-config, startup-config, or a
file system alias (see the tables above). The location of a file system dictates the format of the source or
destination URL.
The colon is required after the alias. However, earlier commands that do not require a colon remain
supported but are unavailable in context-sensitive help.
The entire copying process may take several minutes and differs from protocol to protocol and from
network to network.
In the alias syntax for ftp:, rcp:, and tftp:, the location is either an IP address or a hostname. The filename
is specified for the directory that is used for file transfers.
Enter the file verify autocommand to set up verification globally.
Examples
This example shows how to disable the automatic image verification for the current copy operation:
Router# copy /noverify tftp: sup-bootflash:
.................................................
[OK - 24301348 bytes]
24301348 bytes copied in 157.328 secs (154463 bytes/sec)
Router#
Related Commands
Command
Description
C commands
copy noverify
Command
Description
verify
C commands
copy noverify
D through E
D through E
D through E
databits
databits
To set the number of data bits per character that are interpreted and generated by the router hardware, use
the databitscommand in line configuration mode. To restore the default value, use the no form of the
command.
databits {5 | 6 | 7 | 8}
no databits
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The databits line configuration command can be used to mask the high bit on input from devices that
generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity
generation is in effect, specify 8 data bits per character. The other keywords are supplied for compatibility
with older devices and generally are not used.
Examples
The following example sets the number of data bits per character to seven on line 4:
Router(config)# line 4
Router(config-line)# databits 7
D through E
databits
Related Commands
Command
Description
data-character-bits
terminal databits
terminal data-character-bits
D through E
data-character-bits
data-character-bits
To set the number of data bits per character that are interpreted and generated by the Cisco IOS software,
use the data-character-bitscommand in line configuration mode. To restore the default value, use the no
form of this command.
data-character-bits {7 | 8}
no data-character-bits
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The data-character-bits line configuration command is used primarily to strip parity from X.25
connections on routers with the protocol translation software option. The data-character-bits line
configuration command does not work on hard-wired lines.
Examples
The following example sets the number of data bits per character to seven on virtual terminal line (vty) 1:
Router(config)# line vty 1
Router(config-line)# data-character-bits 7
D through E
data-character-bits
Related Commands
Command
Description
terminal data-character-bits
D through E
default-value data-character-bits
default-value data-character-bits
To configure the number of data bits per character that are generated and interpreted by Cisco software to
either 7 bits or 8 bits, use the default-value data-character-bitscommand in global configuration mode.
To disable the configured size, use the no form of this command.
default-value data-character-bits {7 | 8}
no default-value data-character-bits
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SRB
12.2(33)SXI
The following example shows how to set the default number of data character bits to 8:
Router# configure terminal
Router(config)# default-value data-character-bits 8
D through E
default-value data-character-bits
Related Commands
Command
Description
default-value exec-character-bits
default-value modem-signal
default-value special-character-bits
Configures the flow control default value from a 7bit width to an 8-bit width.
D through E
default-value exec-character-bits
default-value exec-character-bits
To define the EXEC character width for either 7 bits or 8 bits, use the default-value exec-character-bits
command in global configuration mode. To restore the default value, use the no form of this command.
default-value exec-character-bits {7 | 8}
no default-value exec-character-bits
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Configuring the EXEC character width to 8 bits allows you to add graphical and international characters in
banners, prompts, and so on. However, setting the EXEC character width to 8 bits can also cause failures. If
a user on a terminal that is sending parity enters the help command, an unrecognized command message
appears because the system is reading all 8 bits, although the eighth bit is not needed for the helpcommand.
Examples
The following example selects the full 8-bit ASCII character set for EXEC banners and prompts:
Router(config)# default-value exec-character-bits 8
D through E
default-value exec-character-bits
Related Commands
Command
Description
default-value special-character-bits
Configures the flow control default value from a 7bit width to an 8-bit width.
exec-character-bits
length
terminal exec-character-bits
terminal special-character-bits
D through E
default-value modem-interval
default-value modem-interval
To configure the default frequency time to scan modem signals, use the default-value modemintervalcommand in global configuration mode. To disable the configured frequency, use the no form of
this command.
default-value modem-interval milliseconds
no default-value modem-interval
Syntax Description
milliseconds
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to set the default time to scan the modem signal to 345 ms:
Router# configure terminal
Router(config)# default-value modem-signal 345
Related Commands
Command
Description
default-value data-character-bits
default-value exec-character-bits
default-value special-character-bits
Configures the flow control default value from a 7bit width to an 8-bit width.
D through E
default-value special-character-bits
default-value special-character-bits
To configure the flow control default value from a 7-bit width to an 8-bit width, use the default-value
special-character-bits command in global configuration mode. To restore the default value, use the no
form of this command.
default-value special-character-bits commanddefault-value special-character-bits {7 | 8}
no default-value special-character-bits
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Configuring the special character width to 8 bits allows you to add graphical and international characters in
banners, prompts, and so on.
Examples
The following example selects the full 8-bit special character set:
Router(config)# default-value special-character-bits 8
Related Commands
Command
Description
default-value exec-character-bits
D through E
default-value special-character-bits
Command
Description
exec-character-bits
length
terminal exec-character-bits
terminal special-character-bits
D through E
define interface-range
define interface-range
To create an interface-range macro, use the define interface-range command in global configuration
mode. To remove an interface-range macro, use the no form of this command.
define interface-range macro-name interface-range
Syntax Description
macro-name
interface-range
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
The define interface-range command applies a particular configuration on multiple interfaces and
creates multiple logical, and sub interfaces.
An interface range macro name can comprise up to 32 characters.
An interface range for a macro can accept a maximum of five ranges. However, the subinterface range
for a macro accepts only one range.
An interface range cannot span slots.
Use the interface-type slot/first-interface last-interface format to enter the interface range.
Valid values for the interface-type argument are as follows:
atm Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
ethernet
fastethernet
D through E
define interface-range
Examples
ge-wan Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
gigabitethernet
loopback
port-channel interface-number Valid values are from 1 to 256
pos Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
tengigabitethernet
tunnel
vlan vlan-id Valid values are from 1 to 4094
Related Commands
Command
Description
interface range
D through E
delete
delete
To delete a file on a Flash memory device or NVRAM, use the delete command in EXEC, privileged
EXEC, or diagnostic mode.
delete url [/force | /recursive]
Syntax Description
url
/force
Command Modes
EXEC (>)
Privileged EXEC (#)
Diagnostic (diag)
Command History
Release
Modification
11.0
12.3(14)T
12.2(33)SRA
D through E
delete
Release
Modification
Usage Guidelines
If you attempt to delete the configuration file or image specified by the CONFIG_FILE or BOOTLDR
environment variable, the system prompts you to confirm the deletion. Also, if you attempt to delete the
last valid system image specified in the BOOT environment variable, the system prompts you to confirm
the deletion. To accept the change, you may enter y, Y, or simply hit the Enter key. Entering ? will emit a
help prompt.
When you delete a file in Flash memory, the software simply marks the file as deleted, but it does not erase
the file. To later recover a deleted file in Flash memory, use the undeleteEXECcommand. You can
delete and undelete a file up to 15 times.
To permanently delete all files marked deleted on a linear Flash memory device, use the squeeze EXEC
command.
The table below contains a list of Cisco IOS File System URLs.
Table 20
Prefix
Filesystem
bootflash:
flash:
harddisk:
nvram:
obfl:
slot0:
stby-bootflash:
D through E
delete
Examples
Prefix
Filesystem
stby-harddisk:
stby-nvram:
stby-obfl:
stby-usb [ 0 - 1 ]:
usb [ 0 - 1 ];
usbflash 0 9 :
usbtoken 0 9 :
The following example deletes the file named test from the Flash card inserted in slot 0:
Router# delete slot0:test
Delete slot0:test? [confirm]
Related Commands
Command
Description
cd
dir
show bootvar
squeeze
undelete
D through E
diag
diag
To perform field diagnostics on a line card, on the Gigabit Route Processor (GRP), on the Switch Fabric
Cards (SFCs), and on the Clock Scheduler Card (CSC) in Cisco 12000 series Gigabit Switch Routers
(GSRs), use the diag command in privileged EXEC mode. To disable field diagnostics on a line card, use
the no form of this command.
diag command diag slot-number [halt | previous | post | verbose [wait] | wait]
no diag slot-number
Syntax Description
Command Default
slot-number
halt
previous
post
verbose [wait
wait
D through E
diag
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
11.2 GS
12.2(33)SRA
The diag command must be executed from the GRP main console port.
Perform diagnostics on the CSC only if a redundant CSC is in the router.
Diagnostics will stop and ask you for confirmation before altering the routers configuration. For example,
running diagnostics on a SFC or CSC will cause the fabric to go from full bandwidth to one-fourth
bandwidth. Bandwidth is not affected by GRP or line card diagnostics.
The field diagnostic software image is bundled with the Cisco IOS software and is downloaded
automatically from the GRP to the target line card prior to testing.
Caution
Performing field diagnostics on a line card stops all activity on the line card. Before the diag EXEC
command begins running diagnostics, you are prompted to confirm the request to perform field diagnostics
on the line card.
In normal mode, if a test fails, the title of the failed test is displayed on the console. However, not all tests
that are performed are displayed. To view all the tests that are performed, use the verbose keyword.
After all diagnostic tests are completed on the line card, a PASSED or TEST FAILURE message is
displayed. If the line card sends a PASSED message, the Cisco IOS software image on the line card is
automatically reloaded unless the wait keyword is specified. If the line card sends a TEST FAILURE
message, the Cisco IOS software image on the line card is not automatically reloaded.
If you want to reload the line card after it fails diagnostic testing, use the microcode reload slot global
configuration command.
Note
When you stop the field diagnostic test, the line card remains down (that is, in an unbooted state). In most
cases, you stopped the testing because you need to remove the line card or replace the line card. If that is
not the case, and you want to bring the line card back up (that is, online), you must use the microcode
reload global configuration command or power cycle the line card.
If the line card fails the test, the line card is defective and should be replaced. In future releases this might
not be the case because DRAM and SDRAM SIMM modules might be field replaceable units. For
example, if the DRAM test failed you might only need to replace the DRAM on the line card.
For more information, refer to the Cisco 12000 series installation and configuration guides.
D through E
diag
Examples
In the following example, a user is shown the output when field diagnostics are performed on the line card
in slot 3. After the line card passes all field diagnostic tests, the Cisco IOS software is automatically
reloaded on the card. Before starting the diagnostic tests, you must confirm the request to perform these
tests on the line card because all activity on the line card is halted. The total/indiv. timeout set to 600/220
sec. message indicates that 600 seconds are allowed to perform all field diagnostics tests, and that no single
test should exceed 220 seconds to complete.
Router# diag 3
Running Diags will halt ALL activity on the requested slot. [confirm]
Router#
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Board will reload
.
.
.
Router#
In the following example, a user is shown the output when field diagnostics are performed on the line card
in slot 3 in verbose mode:
Router# diag 3 verbose
Running Diags will halt ALL activity on the requested slot. [confirm]
Router#
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache
FDIAG_STAT_PASS test_num 1
FDIAG_STAT_IN_PROGRESS: test #2 Sunblock Ordering
FDIAG_STAT_PASS test_num 2
FDIAG_STAT_IN_PROGRESS: test #3 Dram Datapins
FDIAG_STAT_PASS test_num 3
.
.
.
Field Diags: FDIAG_STAT_DONE
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Board will reload
.
.
.
Router#
D through E
diag
Related Commands
Command
Description
microcode reload
D through E
diagnostic bootup level
Syntax Description
minimal
complete
Command Default
minimal
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(33)SCC
Setting the diagnostic level determines the level of testing that occurs when the system or module is reset.
The two levels are as follows:
D through E
diagnostic bootup level
Note
Although the default is minimal, you can set the diagnostic level to complete for troubleshooting hardware
problems.
In certain circumstances, you might want to skip the bootup online diagnostics completely. For example,
you might skip the bootup online diagnostics to verify that a port is as bad as online diagnostics reports. To
skip online diagnostic testing completely, use the no diagnostic bootup level command.
For information on the diagnostic test types, use the show diagnosticcommand.
The new level takes effect at the next reload or the next time that an online insertion and removal is
performed.
Examples
The following example shows how to set the diagnostic bootup level:
Router(config)#
diagnostic bootup level complete
Related Commands
Command
Description
D through E
diagnostic cns
diagnostic cns
To configure the Cisco Networking Services (CNS) diagnostics, use the diagnostic cns command in global
configuration mode. To disable sending diagnostic results to the CNS event bus., use the no form of this
command.
diagnostic cns {publish | subscribe} [subject]
no diagnostic cns {publish | subscribe} [subject]
Syntax Description
Command Default
publish
subscribe
subject
Command Modes
Command History
Usage Guidelines
Global configuration
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
The online diagnostics receive events by subscribing to an event subject name. The subject is the event that
you subscribe (receive) or publish (generate) through the CNS bus.
D through E
diagnostic cns
The diagnostic cns publish command sends diagnostic results to a remote network application to make
decisions and take corrective actions that are based on the diagnostic results.
The diagnostic cns subscribe command receives messages from remote network applications to perform
diagnostic tests or retrieve diagnostic results.
Examples
This example shows how to receive messages from remote network applications to perform diagnostic tests
or retrieve diagnostic results:
Router(config)#
diagnostic cns subscribe my.cns.subscribe
Router(config)#
Related Commands
Command
Description
D through E
diagnostic event-log size
Syntax Description
size
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA.
12.2(33)SCC
D through E
diagnostic event-log size
Examples
The following example shows how to set the diagnostic event-log size:
Router(config)#
diagnostic event-log size 600
Related Commands
Command
Description
D through E
diagnostic level
diagnostic level
To turn on power-on diagnostic tests for the network service engines (NSEs) installed in a Cisco 7300
series router, use the diagnostic level command in privileged EXEC configuration mode. There is no no
form of this command.
diagnostic level {power-on | bypass}
Syntax Description
power-on
bypass
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.1(10)EX2
12.2(18)S
12.2(33)SRA
12.2SX
Use this command to enable power-on diagnostic tests to run on the installed NSEs of a Cisco 7300 series
router when the system is booted. It is recommended that you issue this command only if you are
experiencing problems with an NSE and are planning on rebooting the router. Issuing this command causes
an increase in the boot time.
D through E
diagnostic level
Examples
The following sample output shows the output that is displayed upon system bootup after a power cycle or
router crash:
.
.
.
System Power On Diagnostics
DRAM Size ....................128 MB
Testing DRAM..................Passed
Level2 Cache .................Present
Testing Level2 Cache (256 KB)Passed
Level3 Cache .................Present
Testing Level3 Cache (1024 KB)Passed
System Power On Diagnostics Complete
Note
Related Commands
This output is displayed when the system is booting, not when the command is issued.
Command
Description
debug redundancy
show c7300
D through E
diagnostic monitor
diagnostic monitor
To configure health-monitoring diagnostic testing, use the diagnostic monitor command in global
configuration mode. To disable testing, use the no form of this command.
diagnostic monitor intervalmodule number test {test-id | test-id-range | all} hh:mm:ss milliseconds
days
diagnostic monitor syslog
diagnostic monitor module num test {test-id | test-id-range | all}
no diagnostic monitor {interval | syslog}
Cisco UBR10012 Router
diagnostic monitor {bay slot/bay | slot slot number | subslot slot/subslot} test {test-id | test-idrange | all}
diagnostic monitor interval{bay slot/bay | slot slot-no | subslot slot/subslot} test {test-id | test-idrange | all} hh:mm:ss milliseconds days
diagnostic monitor syslog
diagnostic monitor threshold {bay slot/bay | slot slot-no | subslot slot/subslot} test {test-id | testid-range | all} failure count failures [{runs | days | hours | minutes | seconds | milliseconds}
window_size]
Syntax Description
interval
module number
test
test-id
test-id-range
all
hour hh
min mm
D through E
diagnostic monitor
second ss
millisec ms
syslog
bay slot/bay
slot slotnumber
subslot slot/subslot
threshold
hh:mm:ss
milliseconds
days
runs window_size
days window_size
hours window_size
minutes window_size
D through E
diagnostic monitor
Command Default
seconds window_size
milliseconds window_size
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(33)SCC
test-id -- Enter the show diagnostic content command to display the test ID list .
test-id-range -- Enter the show diagnostic content command to display the test ID list . Enter the range
as integers separated by a comma and a hyphen (for example, 1,3-6 specifies test IDs 1, 3, 4, 5, and 6).
hh-- Enter the hours from 1 to 24.
mm-- Enter the minutes from 1 to 60.
days-- Enter the number of days between tests.
ss-- Enter the seconds from 1 to 60.
ms-- Enter the milliseconds from 1 to 1000.
Enter the [no] diagnostic monitor test {test-id | test-id-range | all} command to enable or disable the
specified health monitoring test.
D through E
diagnostic monitor
When entering the diagnostic monitor module number test {test-id | test-id-range | all} command,
observe the following:
Required
Isolate network traffic by disabling all connected ports and do not pump test packets during the
test.
Remove all modules for testing FIB TCAM and SSRAM memory on the PFC of the supervisor
engine.
Reset the system or the test module before putting the system back into the normal operating
mode.
Recommended
If the DFC module is present, remove all modules, and then reboot the system before starting the
memory test on the central PFC3B of the supervisor engine.
Turn off all background health-monitoring tests on the supervisor engine and the modules using
the no diagnostic monitor module number test {test-id | test-id-range | all} command.
The FIB TCAM test for central PFC3BXL or PFC3B (on the supervisor engine) takes approximately 4
hours and 30 minutes.
The FIB TCAM test for the distributed PFC3BXL or PFC3B (on the DFC module) takes approximately 16
hours.
You can run the FIB TCAM test on multiple DFC3BX modules simultaneously.
Cisco UBR10012 Router
The command syntax to refer a line card or SPAs is different on Cisco UBR10012 Router. The keyword is
slot x for a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.
To monitor a diagnostic test periodically, you first need to configure the hours, minutes, and seconds
interval to run the diagnostic test using the diagnostic monitor intervalcommand. An error message is
displayed, if the interval is not configured before enabling the monitoring.
To store log details for failed tests, execute the diagnostic monitor syslogcommand. A threshold value to
specify the maximum count for allowed failures is configured using the diagnostic monitor
thresholdcommand. The failed test results can be viewed using the show diagnostic resultscommand,
after the number of failed test reaches the maximum number of allowed failures configured using the
diagnostic monitor thresholdcommand.
Examples
The following example shows how to run the specified test every 3 days:
Router(config)# diagnostic monitor interval module 5 test 7 09:07:05 45 3
The following example shows how to enable the generation of a syslog message when any healthmonitoring test fails:
Router(config)#
diagnostic monitor syslog
D through E
diagnostic monitor
The following example shows how to enable logging of failed messages to syslog:
Router(config)# diangostic monitor syslog
The following example shows how to configure the failure threshold value after which the failed test results
are displayed in the command output for show diagnostic results:
Router(config)# diagnostic monitor threshold bay 1/0 test 2 failure count 10
Related Commands
Command
Description
D through E
diagnostic ondemand
diagnostic ondemand
To configure the on-demand diagnostics, use the diagnostic ondemand command in privileged EXEC
mode.
diagnostic ondemand {iteration iteration-count | action-on-failure {continue error-count | stop}}
Syntax Description
Command Default
iteration iteration-count
action-on-failure
continue
stop
error-count
Command Modes
Command History
iteration-count is 1
action-on-error is continue
error-count is 0
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
D through E
diagnostic ondemand
Release
Modification
12.2(33)SCC
Usage Guidelines
Entering 0 for the error-count sets the number of errors that are allowed to unlimited.
Examples
The following example shows how to set the ondemand testing iteration count:
Router#
diagnostic ondemand iteration 4
Router#
The following example shows how to set the execution action when an error is detected:
Router#
diagnostic ondemand action-on-failure continue 2
Router#
Related Commands
Command
Description
D through E
diagnostic schedule module
Syntax Description
module-number
slot / subslot
test
test-id
all
complete
minimal
non-disruptive
per-port
port
interface-port- number
port-number-list
all
on month dd yyyy hh : mm
daily hh : mm
D through E
diagnostic schedule module
weekly day-of-week hh : mm
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
12.2(33)SRE
test-id -- Enter the show diagnostic content command to display the test ID list .
month-- Spell out the month such as january, february ... december (either uppercase or lowercase
characters).
dd-- Enter the day as a two-digit number.
yyyy-- Enter the year as a four-digit number.
hh : mm-- Enter the time as a two-digit number (for a 24-hour clock) for hours:minutes; the colon (:) is
required.
day-of-week-- Spell out the day of the week, such as monday, tuesday... sunday (either uppercase or
lowercase characters).
per-port is not supported when specifying a scheduled switchover.
You can use the diagnostic schedule module slot / subslot test test-id command to schedule a switchover
from the active supervisor engine to the standby supervisor engine.
Enter the show diagnostic content module slot / subslot command to display the test ID list and look for
the test ID in the ScheduleSwitchover field.
D through E
diagnostic schedule module
You can specify a periodic switchover (daily or weekly) or a single switchover occurrence at a specific
time using these commands:
Note
Examples
To avoid system downtime in the event that the standby supervisor engine cannot switch over the system,
Cisco recommends that you schedule a switchover from the standby supervisor engine to the active
supervisor engine 10 minutes after the switchover occurs.
The following example shows how to schedule the diagnostic testing on a specific month, date and time for
a specific module:
Router(config)# diagnostic schedule module 1 test 5 on may 27 2010 10:30
The following example shows how to schedule the diagnostic testing to occur daily at a certain time for a
specific module:
Router(config)# diagnostic schedule module 1 test 5 daily 12:25
The following example shows how to schedule the diagnostic testing to occur weekly on a certain day for a
specific module:
Router(config)# diagnostic schedule module 1 test 5 weekly friday 09:23
Related Commands
Command
Description
D through E
diagnostic start
diagnostic start
To run the specified diagnostic test, use the diagnostic startcommand in privileged EXEC mode.
diagnostic start module num test {test-id | test-id-range | minimal | complete | basic | per-port |
non-disruptive | all} [port{num | port#-range | all}]
diagnostic start system test all
Cisco UBR10012 Universal Broadband Router
diagnostic start {bay slot/bay | slot slot-no} test {test-id | test-id-range | all | complete | minimal |
non-disruptive}
diagnostic start subslot slot/subslot test {test-id | test-id-range | all | complete | minimal | nondisruptive | [per-port [port{num | port#-range | all}]]}
Syntax Description
module num
test
test-id
test-id-range
minimal
complete
basic
per-port
non-disruptive
all
port num
port all
D through E
diagnostic start
bay slot/bay
slot slot-no
subslot slot/sub-slot
Command Default
None
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17a)SX
12.2(17d)SXB
12.2(33)SRA
12.2.(33)SXH
D through E
diagnostic start
Release
Modification
12.2(33)SCC
Usage Guidelines
Note
Note
Running all online diagnostic tests disrupts normal system operation. Reset the system after the diagnostic
start system test all command has completed. Do not insert, remove, or power down line cards or the
supervisor while the system test is running. Do not issue any diagnostic command other than the diagnostic
stop system test all command while the system test is running. Make sure no traffic is running in
background.
Do not enter the diagnostic start module x test all command on systems that are configured with a
DFC3A because this command causes the TCAM test to fail.
Enter the show diagnostic content command to display the test ID list .
Enter the test-id-range or port# range as integers separated by a comma and a hyphen (for example, 1,3-6
specifies test IDs 1, 3, 4, 5, and 6).
Use diagnostic stop command to stop the testing process.
Cisco UBR10012 Router
The command syntax to refer a line card or SPAs is different on Cisco UBR10012 Router. The keyword is
slot x for a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.
Note
To start a diagnostic test on the Cisco UBR10012 Router execute the command diagnostic stopwith the
bay, slot or subslot keyword respectively.
The GOLD test cases used to poll for system errors in Cisco IOS Software Release 12.2(33)SCC are Low
Latency Queueing (LLQ) drop, Cable Line Card (CLC) memory leak, and Guardian index leak tests.
Examples
The following example shows how to run the specified diagnostic test at the specified slot:
Router# diagnostic start module 1 test 5
Module 1:Running test(s) 5 may disrupt normal system operation
Do you want to run disruptive tests? [no] yes
00:48:14:Running OnDemand Diagnostics [Iteration #1] ...
00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ...
00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully
00:48:14:Running OnDemand Diagnostics [Iteration #2] ...
00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ...
00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully
Router#
D through E
diagnostic start
Related Commands
Command
Description
diagnostic schedule
diagnostic stop
diagnostic monitor
diagnostic ondemand
D through E
diagnostic start
Command
Description
D through E
diagnostic stop
diagnostic stop
To stop the testing process, use the diagnostic stop command in privileged EXEC mode.
diagnostic stop module num
Cisco UBR10012 Universal Broadband Router
diagnostic stop {bay slot/bay | slot slot-no | subslot slot/subslot}
Syntax Description
module num
Module number.
bay slot/bay
slot slot-no
subslot slot/subslot
Command Default
None
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
D through E
diagnostic stop
Usage Guidelines
Release
Modification
12.2(33)SRA
12.2(33)SCC
Note
To stop a diagnostic test on the Cisco UBR10012 Router execute the command diagnostic stopwith the
bay, slot or subslot keyword respectively.
The GOLD test cases used to poll for system errors in Cisco IOS Software Release 12.2(33)SCC are Low
Latency Queueing (LLQ) drop, Cable Line Card (CLC) memory leak, and line card index leak tests.
Examples
This example shows how to stop the diagnostic test process for subslot 5/0 on the Cisco UBR10012
Universal Broadband Router:
Router# diagnostic stop subslot 5/0
Router#
Related Commands
Command
Description
diagnostic schedule
diagnostic start
D through E
diagnostic stop
Command
Description
diagnostic monitor
diagnostic ondemand
D through E
dir
dir
To display a list of files on a file system, use the dircommand in EXEC, privileged EXEC, or diagnostic
mode.
dir [/all] [/recursive] [all-filesystems] [filesystem:] [file-url]
Syntax Description
/all
/recursive
all-filesystems
filesystem:
file-url
Command Default
When you omit the /all keyword, the Cisco IOS software displays only undeleted files.
Command Modes
Command History
Release
Modification
11.0
12.3
12.3(14)T
12.2(33)SRA
D through E
dir
Release
Modification
12.4(11)T
Usage Guidelines
Note
15.0(1)M
15.0(01)XO
Use the show file systemscommand to display more details about the files in a particular file system.
As of release 15.0(01)XO, on cat4000 series routers, the show(flash file system) and dirwill display
slightly different byte count and usage information for the same file system. This is due to slight difference
in how IOS computes these figures for this platform.
You can use the Cisco IOS software output modifiers to filter the output of the dir command, to display
only those lines you are interested in.
The output modifier feature is invoked by using the pipe symbol (|). To use this feature, enter the dir
command as normal but add a space and the pipe symbol at the end of the command line. Then add one of
the keywords shown in the table below.
Table 21
Command
Purpose
D through E
dir
Note
Examples
Command
Purpose
The append, redirect and tee keywords do not support rcp in the display.
The table below describes the significant fields shown in the displays.
Table 22
Field
Description
-rw-
d--directory
r--readable
w--writable
x--executable
D through E
dir
Field
Description
4720148
-08:00
hampton/nitro/c7200-j-mz
The following example shows how to use the output modifier feature with the exclude keyword and regular
expression. The table above describes the significant fields shown in the output.
Routwe# dir | exclude asr
Directory of bootflash:/
12 drwx
4096
Jan 5
59265 drwx
4096 Apr 20
14817 drwx
4096 Apr 20
88897 drwx
4096
Jan 7
Related Commands
01:34:50
01:51:10
01:54:37
22:13:26
+00:00
+00:00
+00:00
+00:00
lost+found
.installer
.ssh
.prst_sync
Command
Description
cd
delete
undelete
2005
2004
2004
2005
D through E
disable
disable
To exit privileged EXEC mode and return to user EXEC mode, or to exit to a lower privilege level, enter
the disable command in EXEC, privileged EXEC, or diagnostic mode.
disable [privilege-level]
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
Examples
privilege-level
Release
Modification
10.0
12.2(33)SRA
Up to 16 security levels can be configured using Cisco IOS software. If such levels are configured on a
system, using this command with the privilege-level option allows you to exit to a lower security level. If a
level is not specified, the user will exit to the user EXEC mode, which is the default.
Five EXEC commands are associated with privilege level 0: disable, enable, exit, help, and logout. If you
configure a privilege level greater than 0, these five commands will not be included in the command set for
that privilege level.
In the following example, the user enters privileged EXEC mode using the enable command, then exits
back to user EXEC mode using the disable command. Note that the prompt for user EXEC mode is >, and
the prompt for privileged EXEC mode is #.
Router> enable
Password: <letmein>
Router# disable
Router>
D through E
disable
Related Commands
Command
Description
enable
D through E
disconnect-character
disconnect-character
To define a character to disconnect a session, use the disconnect-character command in line configuration
mode. To remove the disconnect character, use the no form of this command.
disconnect-character ascii-number
no disconnect-character
Syntax Description
ascii-number
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters.
The Break character is represented by zero; NULL cannot be represented.
To use the session-disconnect character in normal communications, precede it with the escape character.
Examples
The following example defines the disconnect character for virtual terminal line 4 as Escape, which is
decimal character 27:
Router(config)# line vty 4
Router(config-line)# disconnect-character 27
D through E
dispatch-character
dispatch-character
To define a character that causes a packet to be sent, use the dispatch-charactercommand in line
configuration mode. To remove the definition of the specified dispatch character, usethe noform of this
command.
dispatch-character ascii-number1 [ascii-number2...]
no dispatch-character ascii-number1 [ascii-number2...]
Syntax Description
ascii-number1
ascii-number2 . . .
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters.
The dispatch-character command defines one or more dispatch characters that cause a packet to be sent
even if the dispatch timer has not expired. Use of a dispatch character causes the Cisco IOS software to
attempt to buffer characters into larger-sized packets for transmission to the remote host.
Enable the dispatch-character command from the session that initiates the connection, not from the
incoming side of a streaming Telnet session.
This command can take multiple arguments, so you can define any number of characters as dispatch
characters.
D through E
dispatch-character
Examples
The following example defines the Return character (decimal 13) as the dispatch character for virtual
terminal line (vty) line 4:
Router(config)# line vty 4
Router(config-line)# dispatch-character 13
Related Commands
Command
Description
dispatch-machine
dispatch-timeout
state-machine
terminal dispatch-character
D through E
dispatch-machine
dispatch-machine
To specify an identifier for a TCP packet dispatch state machine on a particular line, use the dispatchmachine command in line configuration mode. To disable a state machine on a particular line, use the no
form of this command.
dispatch-machine name
no dispatch-machine
Syntax Description
name
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
When the dispatch-timeout command is specified, a packet being built will be sent when the timer expires,
and the state will be reset to zero.
Any dispatch characters specified using the dispatch-character command are ignored when a state
machine is also specified.
If a packet becomes full, it will be sent regardless of the current state, but the state will not be reset. The
packet size depends on the traffic level on the asynchronous line and the dispatch-timeout value. There is
always room for 60 data bytes. If the dispatch-timeout value is greater than or equal to 100 milliseconds, a
packet size of 536 (data bytes) is allocated.
Examples
The following example specifies the name linefeedfor the state machine:
Router(config)# state-machine linefeed 0 0 9 0
Router(config)# state-machine linefeed 0 11 255 0
Router(config)# state-machine linefeed 0 10 10 transmit
D through E
dispatch-machine
Router(config)# line 1
Router(config-line)# dispatch-machine linefeed
Related Commands
Command
Description
dispatch-character
dispatch-timeout
state-machine
D through E
dispatch-timeout
dispatch-timeout
To set the character dispatch timer, use the dispatch-timeoutcommand in line configuration mode. To
remove the timeout definition, use the noform of this command.
dispatch-timeout milliseconds
no dispatch-timeout
Syntax Description
milliseconds
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Use this command to increase the processing efficiency for the remote host.
The dispatch-timeout line configuration command causes the software to buffer characters into packets for
transmission to the remote host. The Cisco IOS software sends a packet a specified amount of time after the
first character is put into the buffer. You can use the dispatch-timeoutand dispatch-character line
configuration commands together. In this case, the software dispatches a packet each time the dispatch
character is entered, or after the specified dispatch timeout interval, depending on which condition is met
first.
D through E
dispatch-timeout
Note
Examples
The system response time might appear intermittent if the timeout interval is greater than 100 milliseconds
and remote echoing is used. For lines with a reverse-Telnet connection, use a dispatch-timeout value less
than 10 milliseconds.
The following example sets the dispatch timer to 80 milliseconds for virtual terminal line (vty) lines 0
through 4:
Router(config)# line vty 0 4
Router(config-line)# dispatch-timeout 80
Related Commands
Command
Description
buffer-length
dispatch-character
dispatch-machine
state-machine
terminal dispatch-timeout
D through E
do
do
To execute user EXEC or privileged EXEC commands from global configuration mode or other
configuration modes or submodes, use the docommand in any configuration mode.
do command
Syntax Description
command
Command Default
A user EXEC or privileged EXEC command is not executed from a configuration mode.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(8)T
12.2(14)S
12.2(14)SX
12.2(17a)SX
12.2(17d)SXB
12.2(33)SRA
15.1(3)T
Use this command to execute user EXEC or privileged EXEC commands (such as show, clear, and debug
commands) while configuring your routing device. After the EXEC command is executed, the system will
return to the configuration mode you were using.
D through E
do
Tip
This command can be useful for saving your configuration to the startup-config file without having to
return to the user EXEC mode or privileged EXEC mode (do copy running-config startup-config) or for
checking the status of a feature (using a do show command) while configuring the feature.
Caution
Do not enter the do command in user EXEC mode or privileged EXEC mode. Interruption of service might
occur.
You cannot use the do command to execute the configure terminal c ommand because entering the
configure terminal command changes the user EXEC mode or privileged EXEC mode to the global
configuration mode.
You cannot use the do command to execute copy or write c ommands in the global configuration or any
other configuration mode or submode.
Examples
The following example shows how to enter the show interfaces serial privileged EXEC command from
within global configuration mode:
Router(config)# do show interfaces serial 3/0
Serial3/0 is up, line protocol is up
Hardware is M8T-RS232
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input never, output 1d17h, output hang never
Last clearing of show interface counters never
.
.
.
The following example shows how to enter the clear vpdn tunnel user EXEC or privileged EXEC
command from within VPDN configuration mode:
Router(config-vpdn)# do clear vpdn tunnel
Related Commands
Command
Description
configure terminal
copy
show interfaces
write core
D through E
downward-compatible-config
downward-compatible-config
To generate a configuration that is compatible with an earlier Cisco IOS release, use the downwardcompatible-configcommand in global configuration mode. To disable this function, use the no form of this
command.
downward-compatible-config version
no downward-compatible-config
Syntax Description
version
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
11.1
12.2(33)SRA
12.2(33)SXI
In Cisco IOS Release 10.3, IP access lists changed format. Use the downward-compatibleconfigcommand to regenerate a configuration in a format prior to Release 10.3 if you will downgrade from
your software version to version 10.2 or 10.3. The earliest version value this command accepts is 10.2.
When this command is configured, the router attempts to generate a configuration that is compatible with
the specified version. Note that this command affects only IP access lists.
Under some circumstances, the software might not be able to generate a fully backward-compatible
configuration. In such a case, the software issues a warning message.
D through E
downward-compatible-config
Examples
The following example shows how to generate a configuration file compatible with Cisco IOS Release 10.2
access lists:
Router(config)# downward-compatible-config 10.2
Related Commands
Command
Description
access-list (extended)
access-list (standard)
D through E
editing
editing
To reen able Cisco IOS enhanced editing features for a particular line after they have been disabled, use the
editing command in line configuration mode. To disable these features, use the no form of this command.
editing
no editing
Syntax Description
Command Default
Enabled
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Enhanced editing features are enabled by default. However, there may be situations in which you need to
disable these features. The no form of this command disables these enhanced editing features, and the plain
form of the command can be used to reenable these features.
The table below provides a description of the keys used to enter and edit commands when the editing
features are enabled. Ctrl indicates the Control key, which must be pressed simultaneously with its
associated letter key. Esc indicates the Escape key, which must be pressed first, followed by its associated
letter key. A comma is used in the following table to indicate a key sequence (the comma key should not be
pressed). Keys are not case sensitive. Many letters used for CLI navigation and editing were chosen to
provide an easy way of remembering their functions. In the following table, characters are bolded in the
Function Summary column to indicate the relation between the letter used and the function.
D through E
editing
Table 23
Keys
Function Summary
Function Details
Tab
Complete command
Execute
Continue
Continue
Delete or Backspace
Backspace
B ack character
F orward character
Esc, B
B ack word
Esc, F
F orward word
D through E
editing
Keys
Function Summary
Function Details
Ctrl-A
Beginning of line
Ctrl-E
E nd of line
Ctrl-D
D elete character
Esc, D
Ctrl-W
Ctrl-K
Ctrl-U or Ctrl-X
Ctrl-T
T ranspose characters
Ctrl-R or Ctrl-L
R edisplay line
Ctrl-V or Esc, Q
Ignore editing
Up Arrow1 or Ctrl-P
P revious command
N ext command
D through E
editing
Examples
Keys
Function Summary
Function Details
Ctrl-Y
Esc, Y
Esc, C
C apitalize word
Esc, U
Esc, L
Related Commands
Command
Description
terminal editing
D through E
enable
enable
To change the privilege level for a CLI session or to use a CLI view for a CLI session, use the enable
command in either user EXEC, privileged EXEC, or diagnostic mode.
enable [privilege-level] [view [view-name]]
Syntax Description
privilege-level
view
Command Default
Command Modes
Command History
Release
Modification
10.0
12.3(7)T
12.2(33)SRA
12.2(33)SRB
12.2SX
D through E
enable
Usage Guidelines
Release
Modification
12.2(33)SB
By default, using the enable command without the privilege-level argument in user EXEC mode causes the
router to enter privileged EXEC mode (privilege-level 15).
Entering privileged EXEC mode enables the use of privileged commands. Because many of the privileged
commands set operating parameters, privileged access should be password-protected to prevent
unauthorized use. If the system administrator has set a password with the enable password global
configuration command, you are prompted to enter the password before being allowed access to privileged
EXEC mode. The password is case sensitive.
If an enable password has not been set, only enable mode can be accessed through the console connection.
Security levels can be set by an administrator using the enable password and privilege level commands.
Up to 16 privilege levels can be specified, using the numbers 0 through 15. Using these privilege levels, the
administrator can allow or deny access to specific commands. Privilege level 0 is associated with user
EXEC mode, and privilege level 15 is associated with privileged EXEC mode.
For more information on defined privilege levels, see the Cisco IOSSecurity Configuration Guide and the
Cisco IOS Security Command Reference publications.
If a level is not specified when entering the enable command, the user will enter the default mode of
privileged EXEC (level 15).
Accessing a CLI View
CLI views restrict user access to specified CLI and configuration information. To configure and access CLI
views, users must first enter into root view, which is accomplished via the enable view command (without
the view-name argument). Thereafter, users are prompted for a password, which is the same password as
the privilege level 15 password.
The view-name argument is used to switch from one view to another view.
To prevent dictionary attacks, a user is prompted for a password even if an incorrect view name is given.
The user is denied access only after an incorrect view name and password are given.
Examples
In the following example, the user enters privileged EXEC mode (changes to privilege-level 15) by using
the enable command without a privilege-level argument. The system prompts the user for a password
before allowing access to the privileged EXEC mode. The password is not printed to the screen. The user
then exits back to user EXEC mode using the disable command. Note that the prompt for user EXEC mode
is the greater than symbol (>), and the prompt for privileged EXEC mode is the number sign (#).
Router> enable
Password: <letmein>
Router# disable
Router>
D through E
enable
The following example shows which commands are available inside the CLI view first after the user has
logged into this view:
Router# enable view first
Password:
00:28:23:%PARSER-6-VIEW_SWITCH:successfully set to view 'first'.
Router# ?
Exec commands:
configure Enter configuration mode
enable
Turn on privileged commands
exit
Exit from the EXEC
show
Show running system information
Router# show ?
ip
IP information
parser
Display parser information
version System hardware and software status
Router# show ip ?
access-lists
accounting
aliases
arp
as-path-access-list
bgp
cache
casa
cef
community-list
dfp
dhcp
drp
dvmrp
eigrp
extcommunity-list
flow
helper-address
http
igmp
irdp
.
.
The following example shows how to use the enable view command to switch from the root view to the
CLI view first:
Router# enable view
Router#
01:08:16:%PARSER-6-VIEW_SWITCH:successfully set to view 'root'.
Router#
! Enable the show parser view command from the root view
Router# show parser view
Current view is 'root'
! Enable the show parser view command from the root view to display all views
Router# show parser view all
Views Present in System:
View Name:
first
View Name:
second
! Switch to the CLI view first.
Router# enable view first
Router#
01:08:09:%PARSER-6-VIEW_SWITCH:successfully set to view 'first'.
! Enable the show parser view command from the CLI view first.
Router# show parser view
Current view is 'first'
D through E
enable
Related Commands
Command
Description
disable
enable password
D through E
enable last-resort
enable last-resort
To enable password parameters as the last resort without specifying the local enable password if no
TACACS servers respond, use the enable last-resort command in global configuration mode. To disable
the password parameters, use the no form of this command.
no enable last-resort {password | succeed}
no enable last-resort
Syntax Description
password
succeed
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to enable password parameters as the last resort without specifying the
local enable password if no TACACS servers respond:
Router> enable
Router# configure terminal
Router(config)# enable last-resort succeed
Related Commands
Command
Description
show tacacs
D through E
end
end
To en d the current configuration session and return to privileged EXEC mode, use the end command in
global configuration mode.
end
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
This command will bring you back to privileged EXEC mode regardless of what configuration mode or
configuration submode you are in.
Examples
In the following example, the end command is used to exit from ALPS ASCU configuration mode and
return to privileged EXEC mode. A show command is used in privileged EXEC mode to verify the
configuration.
Router# configure terminal
Router(config)# interface serial 1:1
Router(config-if)# alps ascu 4B
Router(config-alps-ascu)# end
Router# show interface serial 1:1
D through E
end
Related Commands
Command
Description
exit (global)
D through E
environment-monitor shutdown temperature
Syntax Description
rommon
powerdown
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
12.2(14)SX
12.2(18)SXF17
12.2(33)SXH6
This example shows how to place the supervisor engine in ROMMON when a major active alarm occurs:
Router(config)#
environment-monitor shutdown temperature rommon
Router(config)#
This example shows how to power down the supervisor engine when a major active alarm occurs:
Router(config)#
environment-monitor shutdown temperature powerdown
Router(config)#
D through E
environment temperature-controlled
environment temperature-controlled
To enable the ambient temperature control, use the environment temperature-controlled command in
global configuration mode. To disable the ambient temperature control, use the no form of this command.
environment temperature-controlled
no environment temperature-controlled
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This command does not affect temperature monitoring and alarm thresholds; it only affects whether a
module may be powered on. The software does not validate the inlet temperature.
If you enter the no form of this command and the cooling capacity is reduced below the module cooling
requirement, a syslog warning (and SNMP alarm) is generated. This module status does not change, and an
environmental alarm is not raised when you enter the no form of this command.
Examples
D through E
environment temperature-controlled
no environment temperature-controlled
Router(config)#
D through E
erase
erase
To erase a file system or all files available on a file system, use the erasecommand in privileged EXEC or
diagnostic mode.
erase {/all nvram: | /no-squeeze-reserve-space filesystem: | filesystem: | startup-config}
Cisco 7600 Series Routers and Cisco ASR 1000 Series Routers
erase {/all nvram: | filesystem: | startup-config}
Syntax Description
/all
nvram:
file-system:
Command Modes
Command History
/no-squeeze-reserve-space
startup-config
Release
Modification
11.0
12.2(11)T
12.2(14)SX
12.2(33)SRA
D through E
erase
Usage Guidelines
Caution
Release
Modification
15.0(1)M
The erase nvram: command replaces the write erase command and the erase startup-config command.
When you use the erase command to erase a file system, you cannot recover the files in the file system.
The word help feature is disabled for the erase command. You must enter the complete command name to
enable the command. The parser does not complete the command name if you enter partial syntax of the
command and press the Tab key. For more information on the word help feature, refer to the Using the
Cisco IOS Command-Line Interface feature guide.
The erasecommand can be used on Class B and Class C flash file systems only.
Class A flash file systems cannot be erased. You can delete individual files using the delete command and
then reclaim the space using the squeeze command. You can use the formatcommand to format the flash
file system. The format command when used on ATA disk clears the File Allocation Table (FAT) and root
directory entries only. The data is not erased.
The erase nvram: command erases NVRAM. On Class A file system platforms, if the CONFIG_FILE
variable specifies a file in flash memory, the specified file will be marked deleted.
The erase /all nvram: command erases all files on NVRAM, including private NVRAM.
The /no-squeeze-reserve-space keyword is available on systems with small amounts of flash memory in
order to conserve memory. When a squeeze operation is performed, the last two erase sectors are
permanently reserved for the squeeze logs and squeeze buffer. The /no-squeeze-reserve-spacekeyword
prevents the reservation of space that guarantees the ability to run the squeeze command. Disabling the
squeeze operation keeps these memory sectors free. If any sectors using squeeze data are detected, they will
be erased when the /no-squeeze-reserve-space keyword is used. The /no-squeeze-reserve-space keyword
increases the available amount of usable flash space, but you may not be able to run the squeeze command.
This is typically fine if the file system (such as flash) is used to store a single, large file. For example, an
IOS image.
On Class C flash file systems, space is dynamically reclaimed when you use the delete command. You can
also use either the format or erase command to reinitialize a Class C flash file system.
Note
Use the context-sensitive help to determine which file systems can be used for the erase command. The
output will vary based on the platform.
D through E
erase
Examples
The following example shows how to erase the NVRAM, including the startup configuration located there:
Router# erase nvram:
The following example shows how to erase all of partition 2 in internal flash memory:
Router# erase flash:2
System flash directory, partition 2:
File Length
Name/status
1
1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
Erase flash device, partition 2? [confirm]
Are you sure? [yes/no]:
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
The following example shows how to erase flash memory when flash is partitioned, but no partition is
specified in the command:
Router# erase flash:
System flash partition information:
Partition
Size
Used
Free
1
4096K
2048K
2048K
2
4096K
2048K
2048K
[Type ?<no> for partition directory;
Which partition? [default = 2]
Bank-Size
State
2048K
Read Only
2048K
Read/Write
? for full directory; q
Copy-Mode
RXBOOT-FLH
Direct
to abort]
The system will prompt only if there are two or more read/write partitions. If the partition entered is not
valid or is the read-only partition, the process terminates. You can enter a partition number, a question
mark (?) for a directory display of all partitions, or a question mark and a number (? number) for directory
display of a particular partition. The default is the first read/write partition.
System flash directory, partition 2:
File Length
Name/status
1
3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Erase flash device, partition 2? [confirm] <Return>
Related Commands
Command
Description
boot config
delete
more nvram:startup-config
show bootvar
D through E
erase
Command
Description
squeeze
undelete
write erase
D through E
erase bootflash
erase bootflash
The erase bootflash: and erase bootflash commands have identical functions. See the description of the
erasecommand in this chapter for more information.
D through E
errdisable detect cause
Syntax Description
all
bpduguard
dtp-flap
l2ptguard
link-flap
packet-buffer-error
pagp-flap
rootguard
udld
Command Default
Command Modes
D through E
errdisable detect cause
Command History
Release
Modification
15.0(1)M
12.2(14)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
Note
Entering the no errdisable detect cause packet-buffer-error command allows you to detect the fault that
triggers a power cycle of the affected module.
A cause (bpduguard, dtp-flap, link-flap, pagp-flap, root-guard, udld) is defined as the reason why the errordisable state occurred. When a cause is detected on an interface, the interface is placed in an error-disable
state (an operational state that is similiar to the link-down state).
You must enter the shutdown and then the no shutdown commands to recover an interface manually from
the error-disable state.
Examples
The following example shows how to enable error-disable detection for the Layer 2 protocol-tunnel guard
error-disable cause:
Router(config)#
errdisable detect cause l2ptguard
Related Commands
Command
Description
shutdown
Disables an interface.
D through E
errdisable recovery
errdisable recovery
To configure recovery mechanism variables, use the errdisable recovery command in global configuration
mode. To return to the default state, use the no form of this command.
errdisable recovery {cause {all | arp-inspection | bpduguard | channel-misconfig | dhcp-ratelimit | dtp-flap | gbic-invalid | l2ptguard | link-flap | pagp-flap | psecure-violation | securityviolation | rootguard | udld | unicast-flood} | interval seconds}
no errdisable recovery {cause {all | arp-inspection | bpduguard | channel-misconfig | dhcp-ratelimit | dtp-flap | gbic-invalid | l2ptguard | link-flap | pagp-flap | psecure-violation | securityviolation | rootguard | udld | unicast-flood} | interval seconds}
Syntax Description
cause
all
arp-inspection
bpduguard
channel-misconfig
dhcp-rate-limit
dtp-flap
gbic-invalid
l2ptguard
link-flap
pagp-flap
psecure-violation
D through E
errdisable recovery
security-violation
rootguard
udld
unicast-flood
interval seconds
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.2(33)SRA
A cause (bpduguard, channel-misconfig, dhcp-rate-limit, dtp-flap, l2ptguard, link-flap, pagp-flap, psecureviolation, security-violation, rootguard, udld, or unicast-flood) is defined as the reason why the errordisable state occurred. When a cause is detected on an interface, the interface is placed in an error-disable
state (an operational state that is similar to the link-down state). If you do not enable error-disable recovery
for the cause, the interface stays in the error-disable state until a shutdown and no shutdown occur. If you
enable recovery for a cause, the interface is brought out of the error-disable state and allowed to retry
operation once all the causes have timed out.
D through E
errdisable recovery
You must enter the shutdown command and then the no shutdown command to manually recover an
interface from the error-disable state.
Note
Examples
A separate line is required each time you want to enter the errdisable recovery cause command to add a
new reason for recovery; each new reason does not get appended to the original single line. This means you
must enter each new reason separately.
This example shows how to enable the recovery timer for the BPDU-guard error-disable cause:
Router(config)#
errdisable recovery cause bpduguard
This example shows how to set the recovery timer to 300 seconds:
Router(config)#
errdisable recovery interval 300
Related Commands
Command
Description
shutdown
Disables an interface.
D through E
escape-character
escape-character
To define a system escape character, use the escape-character command in line configuration mode. To
set the escape character to Break, use the noor defaultform of this command.
escape-character {break | char | default | none | soft}
no escape-character [soft]
default escape-character [soft]
Syntax Description
break
char
default
none
soft
Command Default
The default escape key sequence is Ctrl-Shift-6 (Ctrl-^) or Ctrl-Shift-6, X (^^X). The X is generally only
required for modem connections.
The default escape-character command sets the escape character to Break (the default setting for Break is
Ctrl-C).
Command Modes
Line configuration
Command History
Release
Modification
10.0
11.3
12.2(33)SRA
D through E
escape-character
Usage Guidelines
See the "ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters.
The escape character (or key sequence) suspends any actively running processes and returns you to
privileged EXEC mode or, if a menu is being used, to the system menu interface. The escape character is
used for interrupting or aborting a process started by previously executed command. Examples of processes
from which you can escape include Domain-Name lookup, ping, trace, and Telnet sessions initiated from
the device to which you are connected.
To view the current setting of the escape sequence for a line, use the show line command followed by the
specific line identifier (for example, show line 0, or show line console). The default escape sequence for a
line is often displayed as ^^X . The first caret symbol represents the Control (Ctrl) key, the second caret
symbol is literal (Shift-6), and the X is literal (for most systems, the X is not required).
To set the escape key for the active terminal line session, use the terminal escape-character command.
The Break key cannot be used as an escape character on a console terminal because the Cisco IOS software
interprets Break as an instruction to halt the system. Depending upon the configuration register setting,
break commands issued from the console line either will be ignored or cause the server to shut down.
To send an escape sequence over a Telnet connection, press Ctrl-Shift-6 twice.
The escape-character soft form of this command defines a character or character sequence that will cause
the system to wait until pending input is processed before suspending the current session. This option
allows you to program a key sequence to perform multiple actions, such as using the F1 key to execute a
command, then execute the escape function after the first command is executed.
The following restrictions apply when using the soft keyword:
Examples
The following example sets the escape character for the console line to the keyboard entry Ctrl-P, which is
represented by the ASCII decimal value of 16:
Router(config)# line console
Router(config-line)# escape-character 16
The following example sets the escape character for line 1 to !, which is represented in the configuration
file as the ASCII number 33:
Router(config)# line 1
Router(config-line)# escape-character !
Router(config-line)# end
Router# show running-config
Building configuration...
.
.
.
line 1
autoselect during-login
autoselect ppp
modem InOut
transport preferred none
transport output telnet
escape-character 33
D through E
escape-character
Related Commands
Command
Description
show line
terminal escape-character
D through E
exec
exec
To allow an EXEC process on a line, use the exec command in line configuration mode. To turn off the
EXEC process for the specified line, use the no form of this command.
exec
no exec
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
When you want to allow only an outgoing connection on a line, use the no exec command.
The no exec command allows you to disable the EXEC process for connections which may attempt to send
unsolicited data to the router. (For example, the control port of a rack of modems attached to an auxiliary
port of router.) When certain types of data are sent to a line connection, an EXEC process can start, which
makes the line unavailable.
When a user tries to Telnet to a line with the EXEC process disabled, the user will get no response when
attempting to log on.
Examples
D through E
exec-banner
exec-banner
To reenable the display of EXEC and message-of-the-day (MOTD) banners on the specified line or lines,
use the exec-banner command in line configuration mode. To suppress the banners on the specified line or
lines, use the no form of this command.
exec-banner
no exec-banner
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This command determines whether the router will display the EXEC banner and the message-of-the-day
(MOTD) banner when an EXEC session is created. These banners are defined with the banner exec and
banner motdglobal configurationcommands. By default, these banner are enabled on all lines. Disable the
EXEC and MOTD banners using the no exec-banner command.
This command has no effect on the incoming banner, which is controlled by the banner incoming
command.
The MOTD banners can also be disabled by the no motd-banner line configuration command, which
disables MOTD banners on a line. If the no exec-banner command is configured on a line, the MOTD
banner will be disabled regardless of whether the motd-bannercommand is enabled or disabled. The table
below summarizes the effects of the exec-banner command and the motd-banner command.
D through E
exec-banner
Table 24
motd-banner (default)
exec-banner (default)
no exec-banner
MOTD banner
None
EXEC banner
no motd-banner
EXEC banner
None
For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is
displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner
command or no motd-banner command is configured. The table below summarizes the effects of the
exec-banner command and the motd-banner command for reverse Telnet connections.
Table 25
Banners Displayed Based On exec-banner and motd-banner Combinations for Reverse Telnet
Sessions to Async Lines
motd-banner (default)
exec-banner (default)
no exec-banner
MOTD banner
Incoming banner
Incoming banner
no motd-banner
Examples
Incoming banner
Incoming banner
The following example suppresses the EXEC and MOTD banners on virtual terminal lines 0 to 4:
Router(config)# line vty 0 4
Router(config-line)# no exec-banner
Related Commands
Command
Description
banner exec
banner incoming
banner motd
motd-banner
D through E
exec-character-bits
exec-character-bits
To configure the character widths of EXEC and configuration command characters, use the execcharacter-bits command in line configuration mode. To restore the default value, use the no form of this
command.
exec-character-bits {7 | 8}
no exec-character-bits
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
Setting the EXEC character width to 8 allows you to use special graphical and international characters in
banners, prompts, and so on. However, setting the EXEC character width to 8 bits can cause failures. If a
user on a terminal that is sending parity enters the help command, an unrecognized command message
appears because the system is reading all 8 bits, and the eighth bit is not needed for the help command.
If you are using the autoselect function, set the activation character to the default (Return) and the value for
exec-character-bits to 7. If you change these defaults, the application will not recognize the activation
request.
D through E
exec-character-bits
Examples
The following example enables full 8-bit international character sets, except for the console, which is an
ASCII terminal. It illustrates use of the default-value exec-character-bits global configuration command
and the exec-character-bits line configuration command.
Router(config)# default-value exec-character-bits 8
Router(config)# line 0
Router(config-line)# exec-character-bits 7
Related Commands
Command
Description
default-value exec-character-bits
default-value special-character-bits
Configures the flow control default value from a 7bit width to an 8-bit width.
length
terminal exec-character-bits
terminal special-character-bits
D through E
exec-timeout
exec-timeout
To set the interval that the EXEC command interpreter waits until user input is detected, use the exectimeout command in line configuration mode. To remove the timeout definition, use the no form of this
command.
exec-timeout minutes [seconds]
no exec-timeout
Syntax Description
minutes
seconds
Command Default
10 minutes
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
15.0(1)SY2
If no input is detected during the interval, the EXEC facility resumes the current connection. If no
connections exist, the EXEC facility returns the terminal to the idle state and disconnects the incoming
session.
To specify no timeout, enter the no form of this command.
Examples
D through E
exec-timeout
D through E
execute-on
execute-on
To execute commands on a line card, use the execute-on command in privileged EXEC mode.
execute-on {slot slot-number | all | master} command
Syntax Description
slot slot-number
Command Modes
Command History
all
master
command
Privileged EXEC
Release
Modification
11.2 GS
11.3(2)AA
12.2(33)SRA
12.2(33)SRE
D through E
execute-on
Usage Guidelines
Use this command to execute a command on one or all line cards to monitor and maintain information on
one or more line cards (for example, a line card in a specified slot on a dial shelf). This allows you to issue
commands remotely; that is, to issue commands without needing to log in to the line card directly. The all
form of the command allows you to issue commands to all the line cards without having to log in to each in
turn.
Though this command does not have a no form, note that it is possible to use the no form of the remotely
executed commands used in this command.
Tip
This command is useful when used with show EXEC commands (such as show version), because you can
verify and troubleshoot the features found only on a specific line card. Please note, however, that because
not all statistics are maintained on the line cards, the output from some of the show commands might not be
consistent.
Cisco 12000 GSR Guidelines and Restrictions
You can use the execute-on privileged EXEC command only from Cisco IOS software running on the GRP
card.
Timesaver
Though you can use the attachprivileged EXEC command to execute commands on a specific line card,
using the execute-on slotcommand saves you some steps. For example, first you must use the attach
command to connect to the Cisco IOS software running on the line card. Next you must issue the
command. Finally you must disconnect from the line card to return to the Cisco IOS software running on
the GRP card. With the execute-on slot command, you can perform three steps with one command. In
addition, the execute-on allcommand allows you to perform the same command on all line cards
simultaneously.
Cisco c7600 Sup Guidelines and Restrictions
Beginning with the 12.2(33)SRE Cisco IOS release, all pipe '|" options can now be used with show option
in the execute-on command on SUP and SAMI consoles.
Cisco AS5800 Guidelines and Restrictions
The purpose of the command is to conveniently enable certain commands to be remotely executed on the
dial shelf cards from the router without connecting to each line card. This is the recommended procedure,
because it avoids the possibility of adversely affecting a good configuration of a line card in the process.
The execute-oncommand does not give access to every Cisco IOS command available on the Cisco
AS5800 access server. In general, the purpose of the execute-on command is to provide access to statistical
reports from line cards without directly connecting to the dial shelf line cards.
Caution
Do not use this command to change configurations on dial shelf cards, because such changes will not be
reflected in the router shelf.
Using this command makes it possible to accumulate inputs for inclusion in the show techsupportcommand.
The master form of the command can run a designated command remotely on the router from the DSC
card. However, using the console on the DSC is not recommended. It is used for technical support
troubleshooting only.
D through E
execute-on
The show tech-supportcommand for each dial shelf card is bundled into the router shelf's show techsupport command via the execute-on facility.
The execute-on command also support interactive commands such as the following:
router: execute-on slave slot
slot
ping
The execute-on command has the same limitations and restrictions as a vty telnet client has; that is, it
cannot reload DSC using the following command:
router: execute-on slave slot
slot
reload
You can use the execute-on command to enable remote execution of the commands included in the
following partial list:
Examples
In the following example, the user executes the show controllers command on the line card in slot 4 of a
Cisco 12000 series GSR:
Router# execute-on slot 4 show controllers
========= Line Card (Slot 4) =======
Interface POS0
Hardware is BFLC POS
lcpos_instance struct
6033A6E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
SUNI rsop intr status
00
CRC16 enabled, HDLC enc, int clock
no loop
Interface POS1
Hardware is BFLC POS
lcpos_instance struct
6033CEC0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
Interface POS2
Hardware is BFLC POS
lcpos_instance struct
6033F6A0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000800
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
D through E
execute-on
Interface POS3
Hardware is BFLC POS
lcpos_instance struct
60341E80
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000A00
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, ext clock
no loop
Router#
In the following example, the user executes the show version command on the line card in slot 2 and 3 of a
Cisco c7600 Sup series device:
Example for c7600 SUP Router#execute-on 2 3 show
WORD Command to be executed
|
Output modifiers
<cr>
Router#execute-on 2 3 show version
| ?
append
Append redirected output to URL (URLs supporting append operation
only)
begin
Begin with the line that matches
exclude
Exclude lines that match
format
Format the output using the specified spec file
include
Include lines that match
redirect Redirect output to URL
section
Filter a section of output
tee
Copy output to URL
Router#execute-on 2 3 execute-on 4 show version
?
WORD Command to be executed
|
Output modifiers
<cr>
Router#execute-on 2 3 execute-on 4 show version
| redirect
?
bootflash:
Uniform Resource Locator
const_nvram:
Uniform Resource Locator
disk0:
Uniform Resource Locator
disk1:
Uniform Resource Locator
nvram:
Uniform Resource Locator
sami#2-fs:
Uniform Resource Locator
sami#3-fs:
Uniform Resource Locator
slavebootflash:
Uniform Resource Locator
slaveconst_nvram:
Uniform Resource Locator
slavedisk0:
Uniform Resource Locator
slavedisk1:
Uniform Resource Locator
slavenvram:
Uniform Resource Locator
slavercsf:
Uniform Resource Locator
slavesup-bootdisk:
Uniform Resource Locator
slavesup-bootflash: Uniform Resource Locator
sup-bootdisk:
Uniform Resource Locator
sup-bootflash:
Uniform Resource Locator
In the following example, the user executes the show command on the line card in slot 4 of a Cisco c7600
SAMI series device:
Router#execute-on 4 show
?
WORD Command to be executed
|
Output modifiers
<cr>
Router#execute-on 4 show
| ?
append
Append redirected output to URL (URLs supporting append operation
only)
begin
Begin with the line that matches
exclude
Exclude lines that match
include
Include lines that match
D through E
execute-on
redirect
section
tee
Related Commands
Command
Description
attach
D through E
exit (EXEC)
exit (EXEC)
To close an active terminal session by logging off the router, use the exit command in EXEC mode.
exit
Syntax Description
Command Default
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Use the exit command in EXEC mode to exit the active session (log off the device). This command can be
used in any EXEC mode (such as User EXEC mode or Privileged EXEC mode) to exit from the EXEC
process.
Examples
In the following example, the exit (global) command is used to move from global configuration mode to
privileged EXEC mode, the disable command is used to move from privileged EXEC mode to user EXEC
mode, and the exit (EXEC) command is used to log off (exit the active session):
Router(config)# exit
Router# disable
Router> exit
Related Commands
Command
Description
disconnect
Disconnects a line.
end
D through E
exit (EXEC)
Command
Description
exit (global)
logout
D through E
exit (global)
exit (global)
To exit any configuration mode to the next highest mode in the CLI mode hierarchy, use the exit command
in any configuration mode.
exit
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The exit command is used in the Cisco IOS CLI to exit from the current command mode to the next highest
command mode in the CLI mode hierarchy.
For example, use the exit command in global configuration mode to return to privileged EXEC mode. Use
the exit command in interface, line, or router configuration mode to return to global configuration mode.
Use the exit command in subinterface configuration mode to return to interface configuration mode. At the
highest level, EXEC mode, the exit command will exit the EXEC mode and disconnect from the router
interface (see the description of the exit (EXEC) command for details).
Examples
The following example shows how to exit from the subinterface configuration mode and to return to the
interface configuration mode:
Router(config-subif)# exit
Router(config-if)#
The following example displays an exit from the interface configuration mode to return to
the global configuration mode:
Router(config-if)# exit
Router(config)#
D through E
exit (global)
Related Commands
Command
Description
disconnect
Disconnects a line.
end
exit (EXEC)
F through K
F through K
file prompt
file prompt
To specify the level of prompting, use the file promptcommand in global configuration mode.
file prompt prompt [alert | noisy | quiet]
Syntax Description
alert
noisy
quiet
Command Default
alert
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.0
12.2(33)SRA
Use this command to change the amount of confirmation needed for different file operations.
This command affects only prompts for confirmation of operations. The router will always prompt for
missing information.
Examples
The following example configures confirmation prompting for all file operations:
Router(config)# file prompt noisy
F through K
file verify auto
Syntax Description
Command Default
Image verification is not automatically applied to all images that are copied or reloaded onto a router.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.2(18)S
12.0(26)S
12.2(14)SX
12.2(17d)SXB
12.3(4)T
12.2(33)SRA
Image verification is accomplished by verifying the compressed Cisco IOS image checksum.
Image verification allows users to automatically verify the integrity of all Cisco IOS images. Thus, users
can be sure that the image is protected from accidental corruption, which can occur at any time during
transit, starting from the moment the files are generated by Cisco until they reach the user.
The file verify auto command enables image verification globally; that is, all images that are to be copied
(via the copy command) or reloaded (via the reload command) are automatically verified. Although both
the copy and reload commands have a /verify keyword that enables image verification, you must issue the
F through K
file verify auto
keyword each time you want to copy or reload an image. The file verify auto command enables image
verification by default so you no longer have to specify image verification multiple times.
If you have enabled image verification by default but prefer to disable verification for a specific image
copy or reload, the /noverify keyword along with either the copy or the reload command will override the
file verify auto command.
Examples
Related Commands
Command
Description
copy
copy/noverify
reload
verify
F through K
format
format
To format a Class A, Class B, or Class C flash memory file system, use the format command in privileged
EXEC or diagnostic mode.
Class B and Class C Flash File Systems
format filesystem1:
Class A Flash File System
format [spare spare-number] filesystem1 : [[filesystem2:][monlib-filename]]
Syntax Description
spare
spare-number
filesystem1 :
filesystem2 :
monlib-filename
F through K
format
Command Default
Command Modes
Command History
Release
Modification
11.0
12.2(14)SX
12.2(17d)SXB
12.3(14)T
12.2(33)SRA
12.2YST
Usage Guidelines
Reserve a certain number of memory sectors as spares, so that if some sectors fail, most of the flash
memory card can still be used. Otherwise, you must reformat the flash card after some of the sectors fail.
Use this command to format Class A, B, or C flash memory file systems. The Cisco 7600 series router
supports only Class A and Class C flash file systems.
In some cases, you might need to insert a new Personal Computer Memory Card Industry Association
(PCMCIA) flash memory or flash PC card and load images or backup configuration files onto it. Before
you can use a new flash memory or flash PC card, you must format it.
Sectors in flash memory or flash PC cards can fail. Reserve certain flash memory or flash PC sectors as
spares by using the optional spare-number argument on the format command to specify 0 to 16 sectors
F through K
format
as spares. If you reserve a small number of spare sectors for emergencies, you can still use most of the flash
memory or flash PC card. If you specify 0 spare sectors and some sectors fail, you must reformat the flash
memory or flash PC card, thereby erasing all existing data.
The monlib file is the ROM monitor library. The ROM monitor uses this file to access files in the flash file
system. The Cisco IOS system software contains a monlib file. Use the show disk0: allcommand to display
monlib file details.
When this command is used with HSA and you do not specify the monlib-filename argument, the system
takes the ROM monitor library file from the slave image bundle. If you specify the monlib-filename
argument, the system assumes that the files reside on the slave devices.
In the command syntax, the filesystem1 :argumentspecifies the device to format and the
filesystem2 :argumentspecifies the optional device containing the monlib file used to format the
filesystem1 :argument. The device determines which monlib file to use, as follows:
Note
If you omit the optional filesystem2 : and monlib-filename arguments, the system formats the
filesystem1 : argument using the monlib file already bundled with the system software.
If you omit only theoptional filesystem2 : argument, the system formats the filesystem1 :
argumentusing the monlib file from the device you specified with the cd command.
If you omit only the optional monlib-filename argument, the system formats filesystem1 : using the
filesystem2 : monlib file.
When you specify both arguments--filesystem2 : and monlib-filename-- the system formats the
filesystem1 : argumentusing the monlib file from the specified device.
You can specify the filesystem1 :argumentss own monlib file in this argument. If the system cannot
find a monlib file, it terminates its formatting.
Most platforms do not support booting from images stored on flash memory cards . You should reboot your
device only from integrated memory locations, such as NVRAM.
Cisco 7600 Series Router Notes
The bootflash:, slot0:, sup-slot0:, and sup-bootflash: keywords are supported on Cisco 7600 series
routers that are configured with a Supervisor Engine 2.
Use the format command to format Class A or C flash memory file systems.
The disk0: and disk1: keywords are for Class C file systems.
The bootflash:, slot0:, sup-slot0:, and sup-bootflash: keywords are for Class A file systems.
The disk0: keyword is supported on Cisco 7600 series routers that are configured with a Supervisor Engine
2 only.
Cisco ASR 1000 Series Routers Notes
This command is available in both privileged EXEC and diagnostic mode on the Cisco ASR 1000 Series
Routers.
Examples
The following example shows how to format a flash memory card that is inserted in slot 0:
Router# format slot0:
Running config file on this device, proceed? [confirm] y
All sectors will be erased, proceed? [confirm] y
Enter volume id (up to 31 characters): <Return>
F through K
format
When the console returns to the privileged EXEC prompt, the new flash memory card is formatted and
ready for use.
This following example shows how to format a CompactFlash PC card that is inserted in slot 0:
Router# format disk0:
Running config file on this device, proceed? [confirm] y
All sectors will be erased, proceed? [confirm] y
Enter volume id (up to 31 characters): <Return>
Formatting sector 1 (erasing)
Format device disk0 completed
When the console returns to the EXEC prompt, the new CompactFlash PC card is formatted
and ready for use.
This follwing example shows how a format operation cleans up the disk and writes the monitor library on
the disk filesystem:
Router# format formatdisk:
Format operation may take a while. Continue? [confirm]
Format operation will destroy all data in "bootdisk:".
Hash Computation:
100%Done!
Computed Hash
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Embedded Hash
Continue? [confirm]
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Related Commands
Command
Description
cd
copy
delete
squeeze
undelete
F through K
fsck
fsck
To check a File Allocation Table (FAT)-based disk, a flash file system, or a Class C file system for damage
and to repair any problems, use the fsckcommand in privileged EXEC or diagnostic mode.
Supported Platforms Other than the Cisco 7600 Series and Cisco ASR1000 Series Routers
fsck [/nocrc] [/automatic] [/all] [/force] [filesystem:]
Cisco 7600 Series Routers
fsck [/automatic] [/all] [/force] [filesystem:]
Cisco ASR 1000 Series Routers
fsck [/all] [/force] [filesystem:]
Syntax Description
/nocrc
/automatic
Command Default
/ all
/force
filesystem :
A FAT-based disk, flash file system, or Class C file system is not checked for damage and repaired. If you
do not enter the /automatic keyword, command-line interface (CLI) prompts for actions are issued. For the
Cisco 7600 series router, if you do not specify the disk0: keyword, the current file system is checked.
F through K
fsck
This command is available in both privileged EXEC and diagnostic mode on the Cisco ASR1000 series
routers.
Command Modes
Command History
Release
Modification
11.3 AA
12.0(22)S
12.2(13)T
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
15.0(1)M
Usage Guidelines
F through K
fsck
This command performs all steps necessary to remove corrupted files and reclaim unused disk space.
Changes include checking for incorrect file sizes, cluster loops, and so on. The default form of this
command issues multiple prompts to confirm each of the changes. However, you can skip these prompts by
using the /automatic keyword when issuing the command.
When you use the /automatickeyword you are prompted to confirm that you want the automatic option.
Prompts for actions will be skipped, but all actions performed are displayed to the terminal (see the
example below).
This command works with ATA Personal Computer Memory Card Industry Association (PCMCIA) cards
formatted in Disk Operating System (DOS), or for Class C flash file systems.
Note
Only one partition (the active partition) is checked in the ATA disk.
Cisco 7600 Series Router
The disk0: or slavedisk0: file systems are the only file systems in the Cisco 7600 series routers on which
you can run the File-System-Check ( fsck) utility. The slavedisk0: file system appears in redundant
supervisor engine systems only.
This command is valid only on Class C flash file systems and only on PCMCIA ATA flash disks and
CompactFlash disks.
The output for the fsck slavedisk0: command is similar to the fsck disk0: command output.
If you do not enter any arguments, the current file system is used. Use the pwd command to display the
current file system.
If you enter the disk0: or slavedisk0: keyword, the fsck utility checks the selected file system for
problems. If a problem is detected, a prompt is displayed asking if you want the problem fixed.
If you enter the /automatic keyword, you are prompted to confirm that you want the automatic mode. In
automatic mode, problems are fixed automatically and you are not prompted to confirm.
If you do not specify the /forcekeyword, any simultaneous file operations on the same device are not
terminated. Instead, an error message stating files are open for read or write access appears. If you specify
the /force keyword, the fsck utility terminates files that are open for read or write access and continues to
check for problems.
The table below lists the checks and actions that are performed by the fsck utility.
Table 26
Checks
Actions
Checks the boot sector and the partition table and reports the
errors.
No action.
Validates the media with the signature in the last 2 bytes of the
first sector (0x55 and 0xaa, respectively).
No action.
No action.
Checks the number of FATs field (correct values are 1 and 2).
No action.
F through K
fsck
Checks
Actions
No action.
If directories are found with nonzero size fields, the size is reset
to zero.
If unused cluster chains are found, new files are created and
linked to that file with the name fsck-start cluster
The table below lists the valid cluster numbers. Numbers other than those listed in the table below are
invalid numbers.
Table 27
Cluster
FAT-12
FAT-16
2-FEF
2-FFEF
F through K
fsck
Cluster
FAT-12
FAT-16
FF8-FFF
FFF8-FFFF
Available cluster
Bad Cluster
FF7
FFF7
Examples
Supported Platforms Other than the Cisco 7600 Series Router
The following example shows sample output from the fsck command in automatic mode:
Router# fsck /automatic disk1:
Proceed with the automatic mode? [yes] y
Checking the boot sector and partition table...
Checking FAT, Files and Directories...
Start cluster of file disk1:/file1 is invalid, removing file
File disk1:/file2 has a free/bad cluster, truncating...
File disk1:/file2 truncated.
File disk1:/file3 has a free/bad cluster, truncating...
File disk1:/file3 truncated.
File disk1:/file4 has a invalid cluster, truncating...
File disk1:/file4 truncated.
File disk1:/file5 has a invalid cluster, truncating...
File disk1:/file5 truncated.
File disk1:/file6 has a invalid cluster, truncating...
File disk1:/file6 truncated.
File size of disk1:/file7 is not correct, correcting it
File disk1:/file8 cluster chain has a loop, truncating it
File disk1:/file8 truncated.
File disk1:/file9 cluster chain has a loop, truncating it
File disk1:/file9 truncated.
File disk1:/file16 has a free/bad cluster, truncating...
File disk1:/file16 truncated.
File disk1:/file20 has a free/bad cluster, truncating...
File disk1:/file20 truncated.
Reclaiming unused space...
Created file disk1:/fsck-4 for an unused cluster chain
Created file disk1:/fsck-41 for an unused cluster chain
Created file disk1:/fsck-73 for an unused cluster chain
Created file disk1:/fsck-106 for an unused cluster chain
Created file disk1:/fsck-121 for an unused cluster chain
Created file disk1:/fsck-132 for an unused cluster chain
Created file disk1:/fsck-140 for an unused cluster chain
Created file disk1:/fsck-156 for an unused cluster chain
Created file disk1:/fsck-171 for an unused cluster chain
Created file disk1:/fsck-186 for an unused cluster chain
Created file disk1:/fsck-196 for an unused cluster chain
Created file disk1:/fsck-235 for an unused cluster chain
Created file disk1:/fsck-239 for an unused cluster chain
Updating FAT...
fsck of disk1: complete
F through K
fsck
Related Commands
character to ignore[confirm] 1
character to ignore[confirm] i
with the rest of the check...
unused
unused
unused
unused
unused
unused
unused
unused
unused
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
chain
chain
chain
chain
chain
chain
chain
chain
chain
Command
Description
cd
pwd
character to ignore[confirm] q
with the rest of the check...
F through K
full-help
full-help
To get help f or the full set of user-level commands, use the full-help command in line configuration mode.
full-help
Syntax Description
Command Default
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The full-help command enables (or disables) an unprivileged user to see all of the help messages available.
It is used with the show ? command.
Examples
In the following example, the show ? command is used first with full-help disabled. Then full-help is
enabled for the line, and the show ? command is used again to demonstrate the additional help output that
is displayed.
Router> show
bootflash
calendar
clock
context
dialer
history
hosts
isdn
kerberos
modemcap
ppp
rmon
sessions
snmp
terminal
users
version
?
Boot Flash information
Display the hardware calendar
Display the system clock
Show context information
Dialer parameters and statistics
Display the session command history
IP domain-name, lookup style, nameservers, and host table
ISDN information
Show Kerberos Values
Show Modem Capabilities database
PPP parameters and statistics
rmon statistics
Information about Telnet connections
snmp statistics
Display terminal configuration parameters
Display information about terminal lines
System hardware and software status
F through K
full-help
Router> enable
Password:<letmein>
Router#
%SYS-5-CONFIG_I: Configured from console by console
Router# disable
Router> show ?
access-expression List access expression
access-lists
List access lists
aliases
Display alias commands
apollo
Apollo network information
appletalk
AppleTalk information
arp
ARP table
async
Information on terminal lines used as router interfaces
bootflash
Boot Flash information
bridge
Bridge Forwarding/Filtering Database [verbose]
bsc
BSC interface information
bstun
BSTUN interface information
buffers
Buffer pool statistics
calendar
Display the hardware calendar
.
.
.
translate
Protocol translation information
ttycap
Terminal capability tables
users
Display information about terminal lines
version
System hardware and software status
vines
VINES information
vlans
Virtual LANs Information
whoami
Info on current tty line
x25
X.25 information
xns
XNS information
xremote
XRemote statistics
Related Commands
Command
Description
help
F through K
help
help
To display a brief description of the help system, use the help command in any command mode.
help
Syntax Description
Command Default
Command Modes
User EXEC
Privileged EXEC
All configuration modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The help command provides a brief description of the context-sensitive help system, which functions as
follows:
Examples
To list all commands available for a particular command mode, enter a question mark (?) at the system
prompt.
To obtain a list of commands that begin with a particular character string, enter the abbreviated
command entry immediately followed by a question mark (?). This form of help is called word help ,
because it lists only the keywords or arguments that begin with the abbreviation you entered.
To list the keywords and arguments associated with a command, enter a question mark (?) in place of a
keyword or argument on the command line. This form of help is called command syntax help , because
it lists the keywords or arguments that apply based on the command, keywords, and arguments you
have already entered.
In the following example, the help command is used to display a brief description of the help system:
Router#
help
Help may be requested at any point in a command by entering
F through K
help
The following example shows how to use word help to display all the privileged EXEC commands that
begin with the letters co. The letters entered before the question mark are reprinted on the next command
line to allow the user to continue entering the command.
Router# co?
configure connect
Router# co
copy
The following example shows how to use command syntax help to display the next argument of a partially
complete access-list command. One option is to add a wildcard mask. The <cr> symbol indicates that the
other option is to press Enter to execute the command without adding any more keywords or arguments.
The characters entered before the question mark are reprinted on the next command line to allow the user to
continue entering the command or to execute that command as it is.
Router(config)# access-list 99 deny 131.108.134.234 ?
A.B.C.D Mask of bits to ignore
<cr>
Router(config)# access-list 99 deny 131.108.134.234
Related Commands
Command
Description
full-help
F through K
hidekeys
hidekeys
To suppress the display of password information in configuration log files, use the hidekeys command in
configuration change logger configuration mode. To allow the display of password information in
configuration log files, use the no form of this command.
hidekeys
no hidekeys
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
Usage Guidelines
Enabling the hidekeys command increases security by preventing password information from being
displayed in configuration log files.
Examples
The following example shows how to prevent password information from being displayed in configuration
log files:
Router# configure terminal
!
F through K
hidekeys
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)# hidekey
s
Router(config-archive-log-config)# end
Related Commands
Command
Description
archive
log config
logging enable
logging size
notify syslog
F through K
history
history
To enable the command history function, use the history command in line configuration mode. To disable
the command history function, use the no form of this command.
history
no history
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The command history function provides a record of EXEC commands that you have entered. This function
is particularly useful for recalling long or complex commands or entries, including access lists.
To change the number of command lines that the system will record in its history buffer, use the history
size line configuration command.
The history command enables the history function with the last buffer size specified or, if there was not a
prior setting, with the default of ten lines. The no history command disables the history function.
The show history EXEC command will list the commands you have entered, but you can also use your
keyboard to display individual commands. The table below lists the keys you can use to recall commands
from the command history buffer.
F through K
history
Table 28
Examples
History Keys
Key(s)
Functions
Ctrl-P or Up Arrow2
Related Commands
Command
Description
history size
show history
terminal history
F through K
history size
history size
To change the command history buffer size for a particular line, use the history size command in line
configuration mode. To reset the command history buffer size to ten lines, use the no form of this
command.
history size number-of-lines
no history size
Syntax Description
number-of-lines
Command Default
10 command lines
Command Modes
Line configuration
Command History
Usage Guidelines
Note
Examples
Release
Modification
10.0
12.2(33)SRA
The history size command should be used in conjunction with the history and show history commands.
The history command enables or disables the command history function. The show history command lists
the commands you have entered in the current EXEC session. The number of commands that the history
buffer will show is set by the history size command.
The history size command only sets the size of the buffer; it does not reenable the history function. If the
no history command is used, the history command must be used to reenable this function.
The following example displays line 4 configured with a history buffer size of 35 lines:
Router(config)# line 4
Router(config-line)# history size 35
F through K
history size
Related Commands
Command
Description
history
show history
F through K
hold-character
hold-character
To define the local hold character used to pause output to the terminal screen, use the hold-character
command in line configuration mode. To restore the default, use the no form of this command.
hold-character ascii-number
no hold-character
Syntax Description
ascii-number
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The Break character is represented by zero; NULL cannot be represented. To continue the output, enter any
character after the hold character. To use the hold character in normal communications, precede it with the
escape character. See the ASCII Character Set appendix for a list of ASCII characters.
Examples
The following example sets the hold character to Ctrl-S, which is ASCII decimal character 19:
Router(config)# line 8
Router(config-line)# hold-character 19
Related Commands
Command
Description
terminal hold-character
F through K
hold-character
F through K
hostname
hostname
To specify or modify the hostname for the network server, use the hostname command in global
configuration mode.
hostname name
Syntax Description
name
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
12.2(33)SB
12.2(33)SXI
15.0(1)M4
F through K
hostname
or fewer. Creating an all numeric hostname is not recommended but the name will be accepted after an
error is returned.
Router(config)#hostname 123
% Hostname contains one or more illegal characters.
123(config)#
A hostname of less than 10 characters is recommended. For more information, refer to RFC 1035, Domain
Names--Implementation and Specification .
On most systems, a field of 30 characters is used for the hostname and the prompt in the CLI. Note that the
length of your hostname may cause longer configuration mode prompts to be truncated. For example, the
full prompt for service profile configuration mode is:
(config-service-profile)#
However, if you are using the hostname of Router, you will only see the following prompt (on most
systems):
Router(config-service-profil)#
If the hostname is longer, you will see even less of the prompt:
Basement-rtr2(config-service)#
Keep this behavior in mind when assigning a name to your system (using the hostname global
configuration command). If you expect that users will be relying on mode prompts as a CLI navigation aid,
you should assign hostnames of no more than nine characters.
The use of a special character such as '\'(backslash) and a three or more digit number for the character
setting like hostname, results in incorrect translation:
Router(config)#
Router(config)#hostname \99
% Hostname contains one or more illegal characters.
Examples
Related Commands
Command
Description
setup
F through K
hw-module reset
hw-module reset
To reset a module by turning the power off and then on, use the hw-module reset command in privileged
EXEC mode.
hw-module module num reset
Syntax Description
module num
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(31)SB2
Usage Guidelines
The num argument designates the module number. Valid values depend on the chassis that is used. For
example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
F through K
hw-module shutdown
hw-module shutdown
To shut down the module, use the hw-module shutdown command in privileged EXEC mode.
hw-module module num shutdown
Syntax Description
module num
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This command is supported on the SSL Services Module and the NAM.
If you enter the hw-module shutdowncommand to shut down the module, you will have to enter the no
power enable module command and the power enable module command to restart (power down and then
power up) the module.
Examples
This example shows how to shut down and restart the module:
Router# hw-module module 3 shutdown
Router# no power enable module 3
Router# power enable module 3
F through K
insecure
insecure
To configure a line as insecure, use the insecure command in line configuration mode. To disable this
function, use the no form of this command.
insecure
no insecure
Syntax Description
Command Default
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Use this command to identify a modem line as insecure for DEC local area transport (LAT) classification.
Examples
F through K
international
international
If you are using Telnet to access a Cisco IOS platform and you want to display 8-bit and multibyte
international characters (for example, Kanji) and print the Escape character as a single character instead of
as the caret and bracket symbols (^[), use the international command in line configuration mode. To
display characters in 7-bit format, use the no form of this command.
international
no international
Syntax Description
Command Default
Disabled
Command Modes
Line configuration
Command History
Release
Modification
11.3
12.2(33)SRA
Usage Guidelines
If you are configuring a Cisco IOS platform using the Cisco web browser user interface (UI), this function
is enabled automatically when you enable the Cisco web browser UI using the ip http server global
configuration command.
Examples
The following example enables a Cisco IOS platform to display 8-bit and multibyte characters and print the
Escape character as a single character instead of as the caret and bracket symbols (^[) when you are using
Telnet to access the platform:
line vty 4
international
F through K
international
Related Commands
Command
Description
terminal international
F through K
ip bootp server
ip bootp server
To enable the Bootstrap Protocol (BOOTP) service on your routing device, use the ip bootp server
command in global configuration mode. To disable BOOTP services, use the no form of the command.
ip bootp server
no ip bootp server
Syntax Description
Command Default
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.2
12.0(1)T
12.2(8)T
12.2(33)SRA
By default, the BOOTP service is enabled. When disabled, the no ip bootp server command will appear in
the configuration file.
The integrated Dynamic Host Configuration Protocol (DHCP) server was introduced in Cisco IOS Release
12.0(1)T. Because DHCP is based on BOOTP, both of these services share the well-known UDP server
port of 67 (per RFC 951, RFC 1534, and RFC 2131; the client port is 68). To disable DHCP services
(DHCP relay and DHCP server), use the no service dhcp command. To disable BOOTP services (in
releases 12.2(8)T and later), but leave DHCP services enabled, use the ip dhcp bootp ignore command.
If both the BOOTP server and DHCP server are disabled, ICMP port unreachable messages will be sent
in response to incoming requests on port 67, and the original incoming packet will be discarded. If DHCP
is enabled, using the no ip bootp server command by itself will not stop the router from listening on UDP
port 67.
F through K
ip bootp server
Note
Examples
As with all minor services, the async line BOOTP service should be disabled on your system if you do not
have a need for it in your network. Any network device that has User Data Protocol (UDP), TCP, BOOTP,
DHCP, or Finger services should be protected by a firewall or have the services disabled to protect against
Denial of Service attacks.
In the following example, BOOTP and DHCP services are disabled on the router:
Router(config)# no ip bootp server
Router(config)# no service dhcp
Related Commands
Command
Description
service dhcp
F through K
ip finger
ip finger
To configure a system to accept Finger protocol requests (defined in RFC 742), use the ip finger command
in global configuration mode. To disable this service, use the noform of this command.
ip finger [rfc-compliant]
no ip finger
Syntax Description
rfc-compliant
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.3
12.1(5), 12.1(5)T
12.2(33)SRA
The Finger service allows remote users to view the output equivalent to the show users [wide] command.
When ip finger is configured, the router will respond to a telnet a.b.c.d finger command from a remote
host by immediately displaying the output of the show userscommand and then closing the connection.
When the ip finger rfc-compliantcommandis configured, the router will wait for input before displaying
anything (as required by RFC 1288). The remote user can then enter the Return key to display the output of
the show users EXEC command, or enter /W to display the output of the show users wide EXEC
command. After this information is displayed, the connection is closed.
F through K
ip finger
Note
As with all minor services, the Finger service should be disabled on your system if you do not have a need
for it in your network. Any network device that has UDP, TCP, BOOTP, or Finger services should be
protected by a firewall or have the services disabled to protect against Denial of Service attacks.
Because of the potential for hung lines, the rfc-compliantform of this command should not be configured
for devices with more than 20 simultaneous users.
Examples
F through K
ip ftp passive
ip ftp passive
To configure the router to use only passive FTP connections, use the ip ftp passivecommand in global
configuration mode . To allow all types of FTP connections, use the noform of this command.
ip ftp passive
no ip ftp passive
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.3
12.2(33)SRA
In the following example, the router is configured to use only passive FTP connections:
Router(config)# ip ftp passive
Related Commands
Command
Description
ip ftp password
ip ftp source-interface
ip ftp username
F through K
ip ftp password
ip ftp password
To specify the password to be used for File Transfer Protocol (FTP) connections, use the ip ftp
passwordcommand in global configuration mode. To return the password to its default, use the no form of
this command.
ip ftp password [type] password
no ip ftp password
Syntax Description
type
password
Command Default
The router forms a password [email protected]. The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain of
the router.
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.3
12.2(33)SRA
The following example configures the router to use the username red and the password blue for FTP
connections:
Router(config)# ip ftp username red
Router(config)# ip ftp password blue
F through K
ip ftp password
Related Commands
Command
Description
ip ftp password
ip ftp source-interface
ip ftp username
F through K
ip ftp source-interface
ip ftp source-interface
To specify the source IP address for File Transfer Protocol (FTP) connections, use the ip ftp sourceinterfacecommand in global configuration mode. To use the address of the interface where the connection
is made, use the no form of this command.
ip ftp source-interface interface-type interface-number
no ip ftp source-interface
Syntax Description
interface-type interface-number
Command Default
The FTP source address is the IP address of the interface that the FTP packets use to leave the router.
Command Modes
Command History
Usage Guidelines
Release
Modification
10.3
12.3(6)
12.3(8)T
12.2(33)SRA
Use this command to set the same source address for all FTP connections.
In Cisco IOS 12.3(6) and later releases, FTP is VRF-aware, which means that FTP transfer is supported
across an interface within a VRF instance. To specify a VRF as a source for FTP connections, the VRF
must be associated with the same interface that you configure with the ip ftp source-interface command.
In this configuration, FTP looks for the destination IP address for file transfer in the specified VRF table. If
the specified source interface is not up, Cisco IOS software selects the address of the interface closest to the
destination as the source address.
F through K
ip ftp source-interface
Examples
The following example shows how to configure the router to use the IP address associated with Ethernet
interface 0 as the source address on all FTP packets, regardless of which interface is actually used to send
the packet:
Router> enable
Router# configure terminal
Router(config)# ip ftp source-interface ethernet 0
The following example shows how to configure the router to use the VRF table named vpn1 to look for the
destination IP address for the transfer of FTP packets:
Router# configure terminal
Router(config)# ip ftp source-interface ethernet 0
Router(config)# ip vrf vpn1
Router(config-vrf)# rd 200:1
Router(config-vrf)# route-target both 200:1
Router(config-vrf)# interface ethernet 0
Router(config-if)# ip vrf forwarding vpn1
Router(config-if)# end
Related Commands
Command
Description
ip ftp passive
ip ftp password
ip ftp username
F through K
ip ftp username
ip ftp username
To configure the username for File Transfer Protocol (FTP) connections, use the ip ftp usernamecommand
in global configuration mode . To configure the router to attempt anonymous FTP, use the noform of this
command.
ip ftp username username
no ip ftp username
Syntax Description
username
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.3
12.2(33)SRA
Usage Guidelines
The remote username must be associated with an account on the destination server.
Examples
In the following example, the router is configured to use the username red and the password bluefor
FTP connections:
Router(config)# ip ftp username red
Router(config)# ip ftp password blue
Related Commands
Command
Description
ip ftp passive
F through K
ip ftp username
Command
Description
ip ftp password
ip ftp source-interface
F through K
ip rarp-server
ip rarp-server
To enable the router to act as a Reverse Address Resolution Protocol (RARP) server, use the ip rarpserver command in interface configuration mode. To restore the interface to the default of no RARP server
support, use the noform of this command.
ip rarp-server ip-address
no ip rarp-server ip-address
Syntax Description
ip-address
Command Default
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This feature makes diskless booting of clients possible between network subnets where the client and server
are on separate subnets.
RARP server support is configurable on a per-interface basis, so that the router does not interfere with
RARP traffic on subnets that need no RARP assistance.
The Cisco IOS software answers incoming RARP requests only if both of the following two conditions are
met:
The ip rarp-server command has been configured for the interface on which the request was received.
A static entry is found in the IP ARP table that maps the MAC address contained in the RARP request
to an IP address.
Use the show ip arp EXEC command to display the contents of the IP ARP cache.
Sun Microsystems, Inc. makes use of RARP and UDP-based network services to facilitate network-based
booting of SunOS on its workstations. By bridging RARP packets and using both the ip helper-address
F through K
ip rarp-server
interface configuration command and the ip forward-protocol global configuration command, the Cisco
IOS software shouldbe able to perform the necessary packet switching to enable booting of Sun
workstations across subnets. Unfortunately, some Sun workstations assume that the sender of the RARP
response, in this case the router, is the host that the client can contact to TFTP load the bootstrap image.
This causes the workstations to fail to boot.
By using the ip rarp-server command, the Cisco IOS software can be configured to answer these RARP
requests, and the client machine should be able to reach its server by having its TFTP requests forwarded
through the router that acts as the RARP server.
In the case of RARP responses to Sun workstations attempting to diskless boot, the IP address specified in
the ip rarp-server interface configuration command should be the IP address of the TFTP server. In
addition to configuring RARP service, the Cisco IOS software must be configured to forward UDP-based
Sun portmapper requests to completely support diskless booting of Sun workstations. This can be
accomplished using configuration commands of the following form:
ip forward-protocol udp 111
interface
interface name
ip helper-address
target-address
Examples
The following partial example configures a router to act as a RARP server. The router is configured to use
the primary address of the specified interface in its RARP responses.
arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
ip address 172.30.3.100 255.255.255.0
ip rarp-server 172.30.3.100
In the following example, a router is configured to act as a RARP server, with TFTP and portmapper
requests forwarded to the Sun server:
! Allow the router to forward broadcast portmapper requests
ip forward-protocol udp 111
! Provide the router with the IP address of the diskless sun
arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
! Configure the router to act as a RARP server, using the Sun Server's IP
! address in the RARP response packet.
ip rarp-server 172.30.3.100
! Portmapper broadcasts from this interface are sent to the Sun Server.
ip helper-address 172.30.3.100
Related Commands
Command
Description
ip forward-protocol
ip helper-address
F through K
ip rcmd domain-lookup
ip rcmd domain-lookup
To reena ble the basic Domain Name Service (DNS) security check for rcp and rsh, use the ip rcmd
domain-lookupcommand in global configuration mode. T o disable the basic DNS security check for
remote copy protocol (rcp) and remote shell protoco (rsh), use the no form of this command.
ip rcmd domain-lookup
no ip rcmd domain-lookup
Syntax Description
Command Default
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
The abbreviation RCMD (remote command) is used to indicate both rsh and rcp.
DNS lookup for RCMD is enabled by default (provided general DNS services are enabled on the system
using the ip domain-lookupcommand).
The no ip rcmd domain-lookup command is used to disable the DNS lookup for RCMD. The ip rcmd
domain-lookup command is used to reenable the DNS lookup for RCMD.
DNS lookup for RCMD is performed as a basic security check. This check is performed using a host
authentication process. When enabled, the system records the address of the requesting client. That address
is mapped to a host name using DNS. Then a DNS request is made for the IP address for that host name.
The IP address received is then checked against the original requesting address. If the address does not
match with any of the addresses received from DNS, the RCMD request will not be serviced.
This reverse lookup is intended to help protect against spoofing. However, please note that the process only
confirms that the IP address is a valid routable address; it is still possible for a hacker to spoof the valid
IP address of a known host.
The DNS lookup is done after the TCP handshake but before the router (which is acting as a rsh/rcp server)
sends any data to the remote client.
The no ip rcmd domain-lookup will turn off DNS lookups for rsh and rcp only. The no ip domainlookup command takes precedence over the ip rcmd domain-lookupcommand. This means that if the no
F through K
ip rcmd domain-lookup
ip domain-lookup command is in the current configuration, DNS will be bypassed for rcp and rsh even if
the ip rcmd domain-lookup command is enabled.
Examples
In the following example, the DNS security check is disabled for RCMD (rsh/rcp):
Router(config)# no ip rcmd domain-lookup
Related Commands
Command
Description
ip domain-lookup
F through K
ip rcmd rcp-enable
ip rcmd rcp-enable
To configure the Cisco IOS software to allow remote users to copy files to and from the router using
remote copy protocol (rcp), use the ip rcmd rcp-enable command in global configuration mode. To
disable rcp on the device, use the no form of this command.
ip rcmd rcp-enable
no ip rcmd rcp-enable
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.3
12.2(33)SRA
Usage Guidelines
To allow a remote user to execute rcp commands on the router, you must also create an entry for the remote
user in the local authentication database using the ip rcmd remote-host command.
The no ip rcmd rcp-enable command does not prohibit a local user from using rcp to copy system images
and configuration files to and from the router.
To protect against unauthorized users copying the system image or configuration files, the router is not
enabled for rcp by default.
Examples
In the following example, the rcp service is enabled on the system, the IP address assigned to the
Loopback0 interface is used as the source address for outbound rcp and rsh packets, and access is granted
to the user netadmin3on the remote host 172.16.101.101:
Router(config)# ip rcmd rcp-enable
Router(config)# ip rcmd source-interface Loopback0
Router(config)# ip rcmd remote-host router1 172.16.101.101 netadmin3
F through K
ip rcmd rcp-enable
Related Commands
Command
Description
ip rcmd remote-host
F through K
ip rcmd remote-host
ip rcmd remote-host
To create an entry for the remote user in a local authentication database so that remote users can execute
commands on the router using remote shell protocol (rsh) or remote copy protocol (rcp), use the ip rcmd
remote-host command in global configuration mode. To remove an entry for a remote user from the local
authentication database, use the no form of this command.
ip rcmd remote-host local-username {ip-address | host-name} remote-username [enable [level]]
no ip rcmd remote-host local-username {ip-address | host-name} remote-username [enable [level]]
Syntax Description
local-username
ip-address
host-name
remote-username
enable [level]
Command Default
Command Modes
Global configuration
F through K
ip rcmd remote-host
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
A TCP connection to a router is established using an IP address. Using the host name is valid only when
you are initiating an rcp or rsh command from a local router. The host name is converted to an IP address
using DNS or host-name aliasing.
To allow a remote user to execute rcp or rsh commands on a local router, you must create an entry for the
remote user in the local authentication database. You must also enable the router to act as an rsh or rcp
server.
To enable the router to act as an rsh server, issue the ip rcmd rsh-enable command. To enable the router to
act as an rcp server, issue the ip rcmd rcp-enable command.The router cannot act as a server for either of
these protocols unless you explicitly enable the capacity.
A local authentication database, which is similar to a UNIX .rhosts file, is used to enforce security on the
router through access control. Each entry that you configure in the authentication database identifies the
local user, the remote host, and the remote user. To permit a remote user of rsh to execute commands in
privileged EXEC mode or to permit a remote user of rcp to copy files to the router, specify the enable
keyword and level. For information on the enable level, refer to the privilege level global configuration
command in the Release 12.2 Cisco IOS Security Command Reference.
An entry that you configure in the authentication database differs from an entry in a UNIX .rhostsfile in the
following aspect. Because the .rhosts file on a UNIX system resides in the home directory of a local user
account, an entry in a UNIX .rhosts file need not include the local username; the local username is
determined from the user account. To provide equivalent support on a router, specify the local username
along with the remote host and remote username in each authentication database entry that you configure.
For a remote user to be able to execute commands on the router in its capacity as a server, the local
username, host address or name, and remote username sent with the remote client request must match
values configured in an entry in the local authentication file.
A remote client host should be registered with DNS. The Cisco IOS software uses DNS to authenticate the
remote hosts name and address. Because DNS can return several valid IP addresses for a host name, the
Cisco IOS software checks the address of the requesting client against all of the IP addresses for the named
host returned by DNS. If the address sent by the requester is considered invalid, that is, it does not match
any address listed with DNS for the host name, then the software will reject the remote-command execution
request.
Note that if no DNS servers are configured for the router, then that device cannot authenticate the host in
this manner. In this case, the Cisco IOS software sends a broadcast request to attempt to gain access to
DNS services on another server. If DNS services are not available, you must use the no ip domain-lookup
command to disable the attempt to gain access to a DNS server by sending a broadcast request.
If DNS services are not available and, therefore, you bypass the DNS security check, the software will
accept the request to remotely execute a command only if all three values sent with the request match
exactly the values configured for an entry in the local authentication file.
F through K
ip rcmd remote-host
Examples
The following example allows the remote user named netadmin3 on a remote host with the IP address
172.16.101.101 to execute commands on router1 using the rsh or rcp protocol. User netadmin3 is allowed
to execute commands in privileged EXEC mode.
Router(config)# ip rcmd remote-host router1 172.16.101.101 netadmin3 enable
Related Commands
Command
Description
ip rcmd rcp-enable
ip domain-lookup
ip rcmd rsh-enable
F through K
ip rcmd remote-username
ip rcmd remote-username
To configure the remote username to be used when requesting a remote copy using remote copy protocol
(rcp), use the ip rcmd remote-usernamecommand in global configuration mode . To remove from the
configuration the remote username, use the noform of this command.
ip rcmd remote-username username
no ip rcmd remote-username username
Syntax Description
Command Default
Note
username
If you do not issue this command, the Cisco IOS software sends the remote username associated with the
current tty process, if that name is valid, for rcp copy commands. For example, if the user is connected to
the router through Telnet and the user was authenticated through the usernamecommand, then the software
sends that username as the remote username.
The remote username must be associated with an account on the destination server.
If the username for the current tty process is not valid, the Cisco IOS software sends the host name as the
remote username. For rcp boot commands, the Cisco IOS software sends the access server host name by
default.
Note
Command Modes
Command History
For Cisco, tty lines are commonly used for access services. The concept of tty originated with UNIX. For
UNIX systems, each physical device is represented in the file system. Terminals are called tty devices (tty
stands for teletype, the original UNIX terminal).
Global configuration
Release
Modification
10.3
F through K
ip rcmd remote-username
Usage Guidelines
Note
Examples
Release
Modification
12.2(33)SRA
The rcp protocol requires that a client send the remote username on an rcp request to the server. Use this
command to specify the remote username to be sent to the server for an rcp copy request. If the server has a
directory structure, as do UNIX systems, all files and images to be copied are searched for or written
relative to the directory of the remote users account.
Cisco IOS Release 10.3 added the ip keyword to rcmd commands. If you are upgrading from Release 10.2
to Release 10.3 or a later release, this keyword is automatically added to any rcmd commands you have in
your Release 10.2 configuration files.
Related Commands
Command
Description
bridge acquire
copy
F through K
ip rcmd rsh-enable
ip rcmd rsh-enable
To configure the router to allow remote users to execute commands on it using remote shell protocol (rsh),
use the ip rcmd rsh-enable command in global configuration mode. To disable a router that is enabled for
rsh, use the no form of this command.
ip rcmd rsh-enable
no ip rcmd rsh-enable
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
rsh, used as a client process, gives users the ability to remotely get router information (such as status)
without the need to connect into the router and then disconnect. This is valuable when looking at many
statistics on many different routers.
Use this command to enable the router to receive rsh requests from remote users. In addition to issuing this
command, you must create an entry for the remote user in the local authentication database to allow a
remote user to execute rsh commands on the router.
The no ip rcmd rsh-enable command does not prohibit a local user of the router from executing a
command on other routers and UNIX hosts on the network using rsh. The no form of this command only
disables remote access to rsh on the router.
Examples
F through K
ip rcmd rsh-enable
Related Commands
Command
Description
ip rcmd remote-host
F through K
ip rcmd source-interface
ip rcmd source-interface
To force remote copy protocol (rcp) or remote shell protocol (rsh) to use the IP address of a specified
interface for all outgoing rcp/rsh communication packets, use the ip rcmd source-interface command in
global configuration mode. To disable a previously configured ip rcmd source-interface command, use
the no form of this command.
ip rcmd source-interface interface-id
no ip rcmd source-interface interface-id
Syntax Description
interface-id
Command Default
The address of the interface closest to the destination is used as the source interface for rcp/rsh
communications.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.3
12.2(33)SRA
If this command is not used, or if the interface specified in this command is not available (not up), the
Cisco IOS software uses the address of the interface closest to the destination as the source address.
Use this command to force the system to tag all outgoing rcp/rsh packets with the IP address associated
with the specified interface. This address is used as the source address as long as the interface is in the up
state.
This command is especially useful in cases where the router has many interfaces, and you want to ensure
that all rcp and/or rsh packets from this router have the same source IP address. A consistent address is
preferred so that the other end of the connection (the rcp/rsh server or client) can maintain a single session.
The other benefit of a consistent address is that an access list can be configured on the remote device.
The specified interface must have an IP address associated with it. If the specified interface does not have
an IP address or is in a down state, then rcp/rsh reverts to the default. To avoid this, add an IP address to the
subinterface or bring the interface to the up state.
F through K
ip rcmd source-interface
Examples
In the following example, Loopback interface 0 is assigned an IP address of 220.144.159.200, and the ip
rcmd source-interface command is used to specify that the source IP address for all rcp/rsh packets will be
the IP address assigned to the Loopback0 interface:
interface Loopback0
description Loopback interface
ip address 220.144.159.200 255.255.255.255
no ip directed-broadcast
!
.
.
.
clock timezone GMT 0
ip subnet-zero
no ip source-route
no ip finger
ip rcmd source-interface Loopback0
ip telnet source-interface Loopback0
ip tftp source-interface Loopback0
ip ftp source-interface Loopback0
ip ftp username cisco
ip ftp password shhhhsecret
no ip bootp server
ip domain-name net.galaxy
ip name-server 220.144.159.1
ip name-server 220.144.159.2
ip name-server 219.10.2.1
!
.
.
.
Related Commands
Command
Description
ip rcmd remote-host
F through K
ip telnet source-interface
ip telnet source-interface
To specify the IP address of an interface as the source address for Telnet connections, use the ip telnet
source-interface command in global configuration mode. To reset the source address to the default for
each connection, use the no form of this command.
ip telnet source-interface interface
no ip telnet source-interface
Syntax Description
interface
Command Default
The address of the closest interface to the destination is the source address.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.1
12.2(33)SRA
Use this command to set the IP address of an interface as the source for all Telnet connections.
If the specified interface is not up, the Cisco IOS software selects the address of the interface closest to the
destination as the source address.
Examples
The following example forces the IP address for Ethernet interface 1 as the source address for Telnet
connections :
Router(config)# ip telnet source-interface Ethernet1
F through K
ip telnet source-interface
Related Commands
Command
Description
ip radius source-interface
F through K
ip tftp blocksize
ip tftp blocksize
To negotiate a transfer TFTP blocksize, use the ip tftp blocksizecommand in global configuration mode.
To disable this configuration, use the no form of this command.
ip tftp blocksize bytes
no ip tftp blocksize
Syntax Description
bytes
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2S
15.1(1)SG
The following example shows how to set a 1024 byte TFTP blocksize:
Router> enable
Router# configure terminal
Router(config)# ip tftp bblocksize 1024
Related Commands
Command
Description
ip tftp min-timeout
F through K
ip tftp boot-interface
ip tftp boot-interface
To use an interface for TFTP booting, use the ip tftp boot-interfacecommand in global configuration
mode. To disable this configuration, use the no form of this command.
ip tftp boot-interface type number
no ip tftp boot-interface
Syntax Description
type
number
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to ensure that an interface is used for TFTP booting:
Router> enable
Router# configure terminal
Router(config)# ip tftp boot-interface
Related Commands
Command
Description
ip tftp min-timeout
F through K
ip tftp min-timeout
ip tftp min-timeout
To specify the minimum timeout period for retransmission of data using TFTP, use the ip tftp mintimeoutcommand in global configuration mode. To disable, use the no form of this command.
ip tftp min-timeout seconds
no ip tftp min-timeout
Syntax Description
seconds
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to specify the minimum timeout period for retransmission of data as 5
seconds:
Router> enable
Router# configure terminal
Router(config)# ip tftp min-timeout 5
Related Commands
Command
Description
ip tftp boot-interface
F through K
ip tftp source-interface
ip tftp source-interface
To specify the IP address of an interface as the source address for TFTP connections, use the ip tftp
source-interface command in global configuration mode. To return to the default, use the no form of this
command.
ip tftp source-interface interface-type interface-number
no ip tftp source-interface
Syntax Description
interface-type interface-number
Command Default
The address of the closest interface to the destination is selected as the source address.
Command Modes
Command History
Usage Guidelines
Release
Modification
11.1
12.3(6)
12.3(8)T
12.2(33)SRA
Use this command to set the IP address of an interface as the source for all TFTP connections.
If the specified interface is not up, the Cisco IOS software selects the address of the interface closest to the
destination as the source address.
In Cisco IOS 12.3(6) and later releases, TFTP is VRF-aware, which means that TFTP transfer is supported
across an interface within a Virtual Private Network (VPN) routing and forwarding (VRF) instance. To
specify a VRF as a source for TFTP connections, the VRF must be associated with the same interface that
you configure with the ip tftp source-interface command. In this configuration, TFTP looks for the
destination IP address for file transfer in the specified VRF table.
F through K
ip tftp source-interface
Examples
The following example shows how to configure the router to use the IP address associated with loopback
interface 0 as the source address for TFTP connections :
Router# configure terminal
Router(config)# ip tftp source-interface loopback0
The following example shows how to configure the router to use the VRF table named vpn1 to look for the
destination IP address for TFTP connections. In this example, file transfer using TFTP is accomplished
across an interface within a VRF (VRF vpn1) link.
Router# configure terminal
Router(config)# ip tftp source-interface ethernet 1/0
Router(config)# ip vrf vpn1
Router(config-vrf)# rd 100:1
Router(config-vrf)# route-target both 100:1
Router(config-vrf)# interface ethernet 1/0
Router(config-if)# ip vrf forwarding vpn1
Router(config-if)# end
Related Commands
Command
Description
ip ftp source-interface
ip radius source-interface
F through K
ip wccp web-cache accelerated
Syntax Description
group-address group-address
redirect-list access-list
group-list access-list
password password
Command Default
When this command is not configured, hardware acceleration for WCCPv1 is not enabled.
Command Modes
Command History
Release
Modification
12.2(17d)SXB
F through K
ip wccp web-cache accelerated
Usage Guidelines
Release
Modification
12.2(18)SXD1
12.2(33)SRA
The group-address group-address option requires a multicast address that is used by the router to
determine which cache engine should receive redirected messages. This option instructs the router to use
the specified multicast IP address to coalesce the I See You responses for the Here I Am messages that
it has received on this group address. In addition, the response is sent to the group address. The default is
for no group-address to be configured, so that all Here I Am messages are responded to with a unicast
reply.
The redirect-list access-list option instructs the router to use an access list to control the traffic that is
redirected to the cache engines of the service group that is specified by the service-name given. The accesslist argument specifies either a number from 1 to 99 to represent a standard or extended access list number,
or a name to represent a named standard or extended access list. The access list itself specifies the traffic
that is permitted to be redirected. The default is for no redirect-list to be configured (all traffic is
redirected).
The group-list access-list option instructs the router to use an access list to control the cache engines that
are allowed to participate in the specified service group. The access-list argument specifies either a number
from 1 to 99 to represent a standard access list number, or a name to represent a named standard access list.
The access list specifies which cache engines are permitted to participate in the service group. The default
is for no group-list to be configured, so that all cache engines may participate in the service group.
The password can be up to seven characters. When you designate a password, the messages that are not
accepted by the authentication are discarded. The password name is combined with the HMAC MD5 value
to create security for the connection between the router and the cache engine.
Examples
The following example shows how to enable the hardware acceleration for WCCP version 1:
Router(config)# ip wccp web-cache accelerated
Related Commands
Command
Description
ip wccp version
L through mode
L through mode
L through mode
length
length
To set the terminal screen length, use the length command in line configuration mode. To restore the
default value, use the no form of this command.
length screen-length
no length
Syntax Description
screen-length
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The Cisco IOS software uses the value of this command to determine when to pause during multiple-screen
output. Not all commands recognize the configured screen length. For example, the show terminal
command assumes a screen length of 24 lines or more.
Examples
In the following example, the terminal type is specified and the screen pause function is disabled for the
terminal connection on line 6:
Router(config)# line 6
Router(config-line)# terminal-type VT220
Router(config-line)# length 0
L through mode
length
Related Commands
Command
Description
terminal length
L through mode
load-interval
load-interval
To change the length of time for which data is used to compute load statistics, use the load-interval
command in interface configuration mode or Frame Relay DLCI configuration mode. To revert to the
default setting, use the noform of this command.
load-interval seconds
no load-interval seconds
Syntax Description
seconds
Command Default
Enabled
Command Modes
Command History
Usage Guidelines
Release
Modification
10.3
12.2(4)T
12.2(18)SXF
12.2(28)SB
12.2(33)SRA
To make computations more reactive to short bursts of traffic, you can shorten the length of time over
which load averages are computed.
If the load interval is set to 30 seconds, new data is used for load calculations over a 30-second period. This
data is used to compute load statistics, including the input rate in bits and packets per second, the output
rate in bits and packets per second, the load, and reliability.
L through mode
load-interval
Load data is gathered every five seconds. This data is used for a weighted-average calculation in which
recent load data has more weight in the computation than older load data. If the load interval is set to 30
seconds, the average is computed for the last 30 seconds of load data.
If you change the calculation interval from the default of five minutes to a shorter period of time, the input
and output statistics that are displayed by the show interface command or the show frame-relay pvc
command will be more current and will be based on more nearly instantaneous data, rather than reflecting
the average load over a longer period of time.
This command is often used for dial backup purposes to increase or decrease the likelihood of
implementation of a backup interface, but it can be used on any interface.
Examples
Interface Example
In the following example, the default average of five minutes is changed to a 30-second average. A burst in
traffic that would not trigger a dial backup for an interface configured with the default five-minute interval
might trigger a dial backup for this interface, which is set for the shorter 30-second interval.
Router(config)# interface serial 0
Router(config-if)# load-interval 30
Related Commands
Command
Description
show interfaces
L through mode
location
location
To provide a description of the location of a serial device, use the location command in line configuration
mode. To remove the description, use the no form of this command.
location text
no location
Syntax Description
text
Command Default
Command Modes
Command History
Location description.
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The location command enters information about the device location and status. Use the show users all
EXEC command to display the location information.
Examples
In the following example, the location description for the console line is given as Building 3, Basement:
Router(config)# line console
Router(config-line)# location Building 3, Basement
Related Commands
Command
Description
show users
L through mode
lock
lock
To configure a temporary password on a line, use the lockcommand in EXEC mode.
lock
Syntax Description
Command Default
Not locked
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
You can prevent access to your session while keeping your connection open by setting up a temporary
password. To lock access to the terminal, perform the following steps:
1 Enter the lock command. The system prompts you for a password.
2 Enter a password, which can be any arbitrary string. The system will prompt you to confirm the
password. The screen then clears and displays the message Locked.
3 To regain access to your sessions, reenter the password.
The Cisco IOS software honors session timeouts on a locked lines. You must clear the line to remove this
feature. The system administrator must set the line up to allow use of the temporary locking feature by
using the lockable line configuration command.
Examples
The following example shows configuring the router as lockable, saving the configuration, and then
locking the current session for the user:
Router(config-line)# lockable
Router(config-line)# ^Z
Router# copy system:running-config nvram:startup-config
Building configuration...
OK
Router# lock
L through mode
lock
Password: <password>
Again: <password>
Locked
Password: <password>
Router#
Related Commands
Command
Description
lockable
login (EXEC)
L through mode
lockable
lockable
To enable use of the lock EXEC command, use the lockablecommand in line configuration mode. To
reinstate the default (the terminal session cannot be locked), use the noform of this command.
lockable
no lockable
Syntax Description
Command Default
Sessions on the line are not lockable (the lock EXEC command has no effect).
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command enables use of temporary terminal locking, which is executed using the lock EXEC
command. Terminal locking allows a user keep the current session open while preventing access by other
users.
Examples
In the following example, the terminal connection is configured as lockable, then the current connection is
locked:
Router# configure terminal
Router(config)# line console 0
Router(config-line)# lockable
Router(config)# ^Z
Router# lock
Password: <password>
Again: <password>
Locked
Password: <password>
Router#
L through mode
lockable
Related Commands
Command
Description
lock
L through mode
log config
log config
To enter configuration change logger configuration mode, use the log configcommand in archive
configuration mode.
log config
Syntax Description
Command Default
None
Command Modes
Archive configuration
Command History
Examples
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
The following example shows how to place the router in configuration change logger configuration mode:
Router# configure terminal
!
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)#
L through mode
log config
Related Commands
Command
Description
archive
hidekeys
logging enable
logging size
notify syslog
L through mode
logging buginf
logging buginf
To allow debug messages to be generated for the standard system logging buffer, use the logging
buginfcommand in global configuration mode. To disable the logging for debugging functionality, use the
no form of this command.
logging buginf
no logging buginf
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
Usage Guidelines
The no logging buginfcommand is used to avoid a situation where a large amount of debug messages
might overload the processor (CPU hog condition). This condition differs from the use of the undebug
allcommand wherein all debugging calls are disabled in the Cisco IOS software. No debug reporting is
available, even if debugging is enabled. Note that even though debugging has been completely disabled in
the system, other message reporting, including error reporting, is still available.
Examples
The following example shows how to enable buginf logging for debugging:
Router# configure terminal
Router(config)# logging buginf
L through mode
logging buginf
Related Commands
Command
Description
show logging
L through mode
logging enable
logging enable
To enable the logging of configuration changes, use the logging enablecommand in configuration change
logger configuration mode. To disable the logging of configuration changes, use the no form of this
command.
logging enable
no logging enable
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
Usage Guidelines
Use this command if you want to log configuration changes. If you disable configuration logging, all
configuration log records that were collected are purged.
Examples
L through mode
logging enable
The following example shows how to clear the configuration log by disabling and then reenabling the
configuration log:
Router# configure terminal
!
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)# no logging enable
Router(config-archive-log-config)# logging enable
Router(config-archive-log-config)# end
Related Commands
Command
Description
archive
hidekeys
log config
logging size
notify syslog
L through mode
logging esm config
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
Usage Guidelines
You can use the no logging esm config command to disallow configuration changes from ESM filters.
Examples
L through mode
logging esm config
Related Commands
Command
Description
logging filter
L through mode
logging event bundle-status
Syntax Description
default
boot
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
The logging event bundle-status command is not applicable on Port Channel or Ether-Channel interfaces.
Examples
This example shows how to enable the system logging of the interface state-change events on all interfaces
in the system:
Router(config)# logging event bundle-status
Router(config)# end
Router # show logging event bundle-status
*Aug 4 17:36:48.240 UTC: %EC-SP-5-UNBUNDLE: Interface FastEthernet9/23 left the port-
L through mode
logging event bundle-status
channel Port-channel2
*Aug 4 17:36:48.256 UTC: %LINK-SP-5-CHANGED: Interface FastEthernet9/23, changed state to
administratively down
*Aug 4 17:36:47.865 UTC: %EC-SPSTBY-5-UNBUNDLE: Interface FastEthernet9/23 left the portchannel Port-channel2
Router # show logging event bundle-status
*Aug 4 17:37:35.845 UTC: %EC-SP-5-BUNDLE: Interface FastEthernet9/23 joined port-channel
Port-channel2
*Aug 4 17:37:35.533 UTC: %EC-SPSTBY-5-BUNDLE: Interface FastEthernet9/23 joined portchannel Port-channel2
Related Commands
Command
Description
show running-config
L through mode
logging event link-status (global configuration)
Syntax Description
default
boot
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
You do not have to enter the logging event link-status boot command to enable link-status messaging
during system initialization. The logging event link-status default command logs system messages even
during system initialization.
If you enter both the logging event link-status default and the no logging event link-status
bootcommands, the interface state-change events are logged after all modules in the Cisco 7600 series
router come online after system initialization. The logging event link-status default and the no logging
event link-status boot commands are saved and retained in the running configuration of the system.
L through mode
logging event link-status (global configuration)
When both the logging event link-status default and the no logging event link-status bootcommands are
present in the running configuration and you want to display the interface state-change messages during
system initialization, enter the logging event link-status boot command.
Examples
This example shows how to enable the system logging of the interface state-change events on all interfaces
in the system:
Router(config)# logging event link-status default
Router(config)#
This example shows how to enable the system logging of interface state-change events on all interfaces
during system initialization:
Router(config)# logging event link-status boot
Router(config)#
This example shows how to disable the system logging of interface state-change events on all interfaces:
Router(config)# no logging event link-status default
Router(config)#
This example shows how to disable the system logging of interface state-change events during system
initialization:
Router(config)# no logging event link-status boot
Router(config)#
Related Commands
Command
Description
show running-config
L through mode
logging event link-status (interface configuration)
Syntax Description
bchan
dchan
nfas
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
To enable system logging of interface state-change events on a specific interface, enter the logging event
link-status command.
L through mode
logging event link-status (interface configuration)
Examples
The following example shows how to enable link-status event messaging on an interface:
Router(config-if)# logging event link-status
L through mode
logging event subif-link-status
Syntax Description
Command Default
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
12.2(17d)SXB
12.2(33)SRA
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine
720.
To enable system logging of interface state-change events on a specific subinterface, enter the logging
event subif-link-status command.
To enable system logging of interface state-change events on a specific interface, enter the logging event
link-status command.
To enable system logging of interface state-change events on all interfaces in the system, enter the logging
event link-status command.
Examples
This example shows how to enable the system logging of the interface state-change events on a
subinterface:
Router(config-if)# logging event subif-link-status
Router(config-if)#
L through mode
logging event subif-link-status
This example shows how to disable the system logging of the interface state-change events on a
subinterface:
Router(config-if)# no logging event subif-link-status
Router(config-if)#
Related Commands
Command
Description
show running-config
L through mode
logging event trunk-status
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
Usage Guidelines
The logging event bundle-status command is not applicable on Port Channel or Ether-Channel interfaces.
Examples
This example shows how to enable the trunk status messaging on physical ports:
Router(config)# logging event trunk-status
Router(config)# end
Router# show logging event trunk-status
*Aug 4 17:27:01.404 UTC: %DTP-SPSTBY-5-NONTRUNKPORTON: Port Gi3/3 has become non-trunk
*Aug 4 17:27:00.773 UTC: %DTP-SP-5-NONTRUNKPORTON: Port Gi3/3 has become non-trunk
Router#
L through mode
logging reload
logging reload
To set the reload logging level, use the logging reloadcommand in global configuration mode. To disable
the reload logging, use the no form of this command.
logging reload [message-limit number] [severity-level | alerts | critical | debugging | emergencies |
errors | informational | notifications | warnings]
no logging reload
Syntax Description
message-limit
number
severity-level
alerts
critical
debugging
emergencies
errors
informational
notifications
warnings
Command Default
Command Modes
L through mode
logging reload
Command History
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
Usage Guidelines
The default setting is recommended. Setting the message-limit too low may result in losing important
messages during reload. If the logging reload command is not enabled, logging is turned off during reload.
Examples
The following example shows how to set the limit on number of messages that can be logged during reload
to 100:
Router# configure terminal
Router(config)# logging reload message-limit 100
Related Commands
Command
Description
show logging
L through mode
logging ip access-list cache (global configuration)
Syntax Description
entries entries
interval seconds
rate-limit pps
threshold packets
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.2(17d)SXB
12.2(33)SRA
L through mode
logging ip access-list cache (global configuration)
Usage Guidelines
This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 720
only.
OAL is supported on IPv4 unicast traffic only.
You cannot configure OAL and VACL capture on the same chassis. OAL and VACL capture are
incompatible. With OAL configured, use SPAN to capture traffic.
If the entry is inactive for the duration that is specified in the update-interval seconds command, th e entry
is removed from the cache.
If you enter the no logging ip access-list cache command without keywords, all the parameters are
returned to the default values.
You must set ICMP unreachable rate limiting to 0 if the OAL is configured to log denied packets.
When enabling the IP "too short" check using the mls verify ip length minimum command, valid IP packets
with with an IP protocol field of ICMP(1), IGMP(2), IP(4), TCP(6), UDP(17), IPv6(41), GRE(47), or
SIPP-ESP(50) will be hardware switched. All other IP protocol fields are software switched.
Caution
Examples
Using optimized access-list logging (OAL) and the mls verify ip length minimum command together can
cause routing protocol neighbor flapping as they are incompatible
This example shows how to specify the maximum number of log entries that are cached in the software:
Router(config)#
logging ip access-list cache entries 200
This example shows how to specify the maximum time interval before an entry is sent to the system log:
Router(config)#
logging ip access-list cache interval 350
This example shows how to specify the number of packets that are logged per second in the software:
Router(config)#
logging ip access-list cache rate-limit 100
This example shows how to specify the number of packet matches before an entry is sent to the system log:
Router(config)#
logging ip access-list cache threshold 125
Related Commands
Command
Description
Clears all the entries from the OAL cache and sends
them to the syslog.
L through mode
logging ip access-list cache (global configuration)
Command
Description
update-interval seconds
L through mode
logging ip access-list cache (interface configuration)
Syntax Description
in
out
Command Default
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
12.2(17d)SXB
12.2(33)SRA
This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 720
only.
This command is supported on traffic that matches the log keyword in the applied ACL. You must set
ICMP unreachable rate limiting to 0 if the OAL is configured to log denied packets.
On systems that are configured with a PFC3A, support for the egress direction on tunnel interfaces is not
supported.
OAL is supported on IPv4 unicast traffic only.
You cannot configure OAL and VACL capture on the same chassis. OAL and VACL capture are
incompatible. With OAL configured, use SPAN to capture traffic.
If the entry is inactive for the duration that is specified in the update-interval seconds command, th e entry
is removed from the cache.
If you enter the no logging ip access-list cache command without keywords, all the parameters are
returned to the default values.
L through mode
logging ip access-list cache (interface configuration)
When enabling the IP "too short" check using the mls verify ip length minimum command, valid IP packets
with with an IP protocol field of ICMP(1), IGMP(2), IP(4), TCP(6), UDP(17), IPv6(41), GRE(47), or
SIPP-ESP(50) will be hardware switched. All other IP protocol fields are software switched.
Caution
Examples
Using optimized access-list logging (OAL) and the mls verify ip length minimum command together can
cause routing protocol neighbor flapping as they are incompatible
Related Commands
Command
Description
Clears all the entries from the OAL cache and sends
them to the syslog.
update-interval seconds
L through mode
logging persistent (config-archive-log-cfg)
Syntax Description
auto
manual
Command Default
The configuration commands are not saved to the Cisco IOS secure file system.
Command Modes
Command History
Release
Modification
12.0(26)S
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.4(11)T
12.2(33)SXH
12.2(33)SB
L through mode
logging persistent (config-archive-log-cfg)
Usage Guidelines
When you use the manualkeyword, you must save each configuration command manually to the Cisco IOS
secure file system. To do this, you must use the archive log config persistent save command.
Examples
The following example automatically saves the configuration commands to the Cisco IOS secure file
system:
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-cfg)# logging enable
Router(config-archive-log-cfg)# logging persistent auto
Related Commands
Command
Description
L through mode
logging persistent reload (config-archive-log-cfg)
Syntax Description
Command Default
The configuration commands saved in the configuration logger database are not applied to the runningconfig file.
Command Modes
Archive config mode; log config (configuration change logger) submode (config-archive-log-cfg)#
Command History
Release
Modification
12.2(33)SRA
12.4(11)T
12.2(33)SXH
12.2(33)SB
Usage Guidelines
Use the logging persistent reload command when you want changed configuration commands to take
effect on the next reload of the router.
Examples
The following example applies the configuration commands in the configuration logger database to the
running-config file after the next reload:
Router(config-archive-log-cfg)# logging persistent reload
L through mode
logging persistent reload (config-archive-log-cfg)
Related Commands
Command
Description
logging persistent
L through mode
logging size
logging size
To specify the maximum number of entries retained in the configuration log, use the logging sizecommand
in configuration change logger configuration mode. To reset the default value, use the no form of this
command.
logging size entries
no logging size
Syntax Description
entries
Command Default
100 entries
Command Modes
Command History
Usage Guidelines
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
When the configuration log is full, the oldest log entry will be removed every time a new entry is added.
L through mode
logging size
Note
Examples
If a new log size is specified that is smaller than the current log size, the oldest entries will be immediately
purged until the new log size is satisfied, regardless of the age of the log entries.
The following example shows how to specify that the configuration log may have a maximum of 200
entries:
Router(config-archive-log-config)# logging size 200
The following example shows how to clear the configuration log by reducing the log size to 1, then
resetting the log size to the desired value. Only the most recent configuration log file will be saved.
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)# logging size 1
Router(config-archive-log-config)# logging size 200
Related Commands
Command
Description
archive
hidekeys
log config
logging enable
notify syslog
L through mode
logging synchronous
logging synchronous
To synchronize unsolicited messages and debug output with solicited Cisco IOS software output and
prompts for a specific console port line, auxiliary port line, or vty, use the logging synchronous command
in line configuration mode. To disable synchronization of unsolicited messages and debug output, use the
no form of this command.
logging synchronous [level severity-level | all] [limit number-of-lines]
no logging synchronous [level severity-level | all] [limit number-of-lines]
Syntax Description
level severity-level
all
limit number-of-lines
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
12.2SX
L through mode
logging synchronous
Usage Guidelines
Tip
When synchronous logging of unsolicited messages and debug output is turned on, unsolicited Cisco IOS
software output is displayed on the console or printed after solicited Cisco IOS software output is displayed
or printed. This keeps unsolicited messages and debug output from being interspersed with solicited
software output and prompts.
This command is useful for keeping system messages from interrupting your typing. By default, messages
will appear immediately when they are processed by the system, and the CLI cursor will appear at the end
of the displayed message. For example, the line Configured by console from console may be printed to
the screen, interrupting whatever command you are currently typing. The logging synchronous command
allows you to avoid these potentially annoying interruptions without have to turn off logging to the console
entirely.
When this command is enabled, unsolicited messages and debug output are displayed on a separate line
than user input. After the unsolicited messages are displayed, the CLI returns to the user prompt.
Note
This command is also useful for allowing you to continue typing when debugging is enabled.
When specifying a severity level number, consider that for the logging system, low numbers indicate
greater severity and high numbers indicate lesser severity.
When a message queue limit of a terminal line is reached, new messages are dropped from the line,
although these messages might be displayed on other lines. If messages are dropped, the notice %SYS-3MSGLOST number-of-messages due to overflow follows any messages that are displayed. This notice is
displayed only on the terminal that lost the messages. It is not sent to any other lines, any logging servers,
or the logging buffer.
Caution
Examples
By configuring abnormally large message queue limits and setting the terminal to terminal monitor on a
terminal that is accessible to intruders, you expose yourself to denial of service attacks. An intruder could
carry out the attack by putting the terminal in synchronous output mode, making a Telnet connection to a
remote host, and leaving the connection idle. This could cause large numbers of messages to be generated
and queued, and these messages could consume all available RAM. You should guard against this type of
attack through proper configuration.
In the following example, a system message appears in the middle of typing the show running-config
command:
Router(config-line)# end
Router# show ru
2w1d: %SYS-5-CONFIG_I: Configured from console by consolenning-config
.
.
.
The user then enables synchronous logging for the current line (indicated by the * symbol in the show line
command), after which the system displays the system message on a separate line, and returns the user to
the prompt to allow the user to finish typing the command on a single line:
Router# show line
L through mode
logging synchronous
Tty Typ
Tx/Rx
A Modem Roty AccO AccI
Uses
Noise
*
0 CTY
0
3
.
.
.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# line 0
Router(config-line)# logging syn
<tab>
Router(config-line)# logging synchronous
Overruns
0/0
Int
-
Router(config-line)# end
Router# show ru
2w1d: %SYS-5-CONFIG_I: Configured from console by console
Router# show running-config
In the following example, synchronous logging for line 4 is enabled with a severity level of 6. Then
synchronous logging for line 2 is enabled with a severity level of 7 and is specified with a maximum
number of buffer lines of 1,000.
Router(config)# line
Router(config-line)#
Router(config-line)#
Router(config)# line
Router(config-line)#
Router(config-line)#
Router#
Related Commands
4
logging synchronous level 6
exit
2
logging synchronous level 7 limit 1000
end
Command
Description
line
logging on
L through mode
logging system
logging system
To enable System Event Archive (SEA) logging, use the logging systemcommand in global configuration
mode. To disable SEA logging, use the no form of this command.
logging system [disk name]
no logging system
Syntax Description
disk name
Command Default
By default, SEA logging feature is enabled, and the events are logged to a file on a persistent storage device
(bootflash: or disk:).
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SXH
12.2(33)SCC
SEA is supported on switches that have a Supervisor Engine 32 or Supervisor Engine 720 with a compact
flash adapter and a Compact Flash card (WS-CF-UPG= for Supervisor Engine 720).
To stop SEA logging to a specified disk, use the default logging system command.
For documentation of the configuration tasks associated with this feature, see the chapter Configuring the
System Event Archive in the Catalyst 6500 Release 12.2SX Software Configuration Guide .
Cisco Universal Broadband Router 100112
The SEA feature is used to address the deficiencies of the debug trace and system console. Support for SEA
feature was introduced on Cisco uBR10012 Router in the Cisco IOS Release 12.2(33)SCC. Use the logging
system disk command to change the location of the disk used to store the sea_log.dat file.
L through mode
logging system
Note
Examples
To store the system event logs, the SEA requires either PCMCIA ATA disk or Compact Flash disk in
compact flash adapter for PRE2.
The following example shows how to specify that the SEA log file should be written to the disk disk1::
Router(config)# logging system disk disk1:
Router(config)# end
Related Commands
L through mode
logout
logout
To close an active terminal session by logging off the router, use the logout command in user EXEC mode.
logout
Syntax Description
Command Default
Command Modes
User EXEC
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
In the following example, the exit (global) command is used to move from global configuration mode to
privileged EXEC mode, the disable command is used to move from privileged EXEC mode to user EXEC
mode, and the logout command is used to log off (exit from the active session):
Router(config)# exit
Router# disable
Router> logout
L through mode
logout-warning
logout-warning
To warn users of an impending forced timeout, use the logout-warningcommand in line configuration
mode. To restore the default, use the no form of this command.
logout-warning [seconds]
logout-warning
Syntax Description
seconds
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.3
12.2(33)SRA
Usage Guidelines
This command notifies the user of an impending forced timeout (set using the absolute-timeout
command).
Examples
In the following example, a logout warning is configured on line 5 with a countdown value of 30 seconds:
Router(config)# line 5
Router(config-line)# logout-warning 30
Related Commands
Command
Description
absolute-timeout
L through mode
logout-warning
Command
Description
session-timeout
L through mode
macro (global configuration)
Syntax Description
global
apply macro-name
description text
trace macro-name
keyword-to-value
value-first-keyword
value-second-keyword
value-third-keyword
name macro-name
Command Default
Command Modes
Command History
Release
Modification
12.2(33)SXH
15.0(1)M
L through mode
macro (global configuration)
Usage Guidelines
You can enter up to three keyword pairs using the macro global trace command.
You can enter the macro global descriptioncommand on the switch stack or on a standalone switch.
Use the description textkeyword and argument to associate the comment text, or the macro name with a
switch. When multiple macros are applied on a switch, the description text is used from the last applied
macro. You can verify the global description settings by using the show parser macro description
command.
To find the syntax or configuration errors, enter the macro global trace macro-name command to apply
and debug the macro.
To display a list of any keyword-value pairs defined in the macro, enter the macro global apply macroname ? command.
You can delete a global macro-applied configuration on a switch only by entering the no version of each
command that is in the macro.
Keyword matching is case sensitive.
When a macro is applied on the commands, all matching occurrences of keywords are replaced with the
corresponding values.
The no form of the macro name command deletes only the macro definition. It does not affect the
configuration of the interfaces on which the macro is already applied.
Examples
The following example shows how to apply the macro called snmp to set the hostname address to testserver and to set the IP precedence value to 7:
Router(config)# macro global apply snmp ADDRESS test-server VALUE 7
The following example shows how to debug the macro called snmp by using the macro global trace
command to find the syntax or configuration errors in the macro when it is applied to a switch:
Router(config)# macro global trace snmp VALUE 7 VALUE 8 VALUE 9
Applying command...`snmp-server enable traps port-security'
Applying command...`snmp-server enable traps linkup'
Applying command...`snmp-server enable traps linkdown'
Applying command...`snmp-server host'
%Error Unknown error.
Applying command...`snmp-server ip precedence 7'
Router(config)#
Related Commands
Command
Description
L through mode
macro (interface configuration)
Syntax Description
apply macro-name
description text
trace macro-name
keyword-to-value
value-first-keyword
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SXH
You can enter up to three keyword changes using the macro trace command.
You can enter the macro description command on the switch stack or on a standalone switch.
Use the description text keyword and argument to associate comment text, or the macro name, with a
switch. When multiple macros are applied on a switch, the description text will be from the last applied
macro. You can verify the description settings by entering the show parser macro description command.
To find any syntax or configuration errors, enter the macro trace macro-name command to apply and
debug the macro.
L through mode
macro (interface configuration)
To display a list of any keyword-value pairs defined in the macro, enter the macro apply macro-name ?
command.
To successfully apply the macro, you must enter any required keyword-value pairs.
Keyword matching is case sensitive.
In the commands that the macro applies, all matching occurrences of keywords are replaced with the
corresponding values.
You can delete all configuration on an interface by entering the default interface interfaceinterface
configuration command.
Examples
The following example shows how to apply the user-created macro called desktop-config and to verify the
configuration:
Router(config)# interface fastethernet1/2
Router(config-if)# macro apply desktop-config
The following example shows how to apply the user-created macro called desktop-config and to replace all
occurrences of vlan with VLAN ID 25:
Router(config-if)# macro apply desktop-config vlan 25
Related Commands
Command
Description
L through mode
maximum
maximum
To set the maximum number of archive files of the running configuration to be saved in the Cisco IOS
configuration archive, use the maximum command in archive configuration mode. To reset this command
to its default, use the no form of this command.
maximum number
no maximum number
Syntax Description
number
Command Default
By default, a maximum of 10 archive files of the running configuration are saved in the Cisco IOS
configuration archive.
Command Modes
Command History
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SB
L through mode
maximum
Usage Guidelines
Note
Before using this command, you must configure the path command to specify the location and filename
prefix for the files in the Cisco IOS configuration archive.
After the maximum number of files are saved in the Cisco IOS configuration archive, the oldest file is
automatically deleted when the next, most recent file is saved.
Note
Examples
This command should only be used when a local writable file system is specified in the url argument of the
path command. Network file systems may not support deletion of previously saved files.
In the following example, a value of 5 is set as the maximum number of archive files of the running
configuration to be saved in the Cisco IOS configuration archive:
configure terminal
!
archive
path disk0:myconfig
maximum 5
end
Related Commands
Command
Description
archive config
configure confirm
configure replace
path
show archive
time-period
L through mode
memory cache error-recovery
Syntax Description
L1
L2
L3
data
inst
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SXI
The following example shows how to enable the memory cache error-recovery command:
Router> enable
Router# configure terminal
Router(config)# memory cache error-recovery
L through mode
memory cache error-recovery
Related Commands
Command
Description
L through mode
memory cache error-recovery options
Syntax Description
abort-if-same-content
blocking-mode
max-recoveries value
nvram-report
parity-check
window seconds
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SXI
The following example shows how to enable the memory cache error-recovery optionscommand:
Router> enable
L through mode
memory cache error-recovery options
Related Commands
Command
Description
L through mode
memory free low-watermark
Syntax Description
processor threshold
io threshold
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.2(18)S
12.0(26)S
12.3(4)T
12.2(27)SBC
12.2(33)SRA
L through mode
memory free low-watermark
Usage Guidelines
Using this command, you can configure a router to issue a system logging message each time available free
memory falls below a specified threshold (low-watermark). Once available free memory rises to 5
percent above the threshold, another notification message is generated.
Examples
The following example specifies a free processor memory notification threshold of 20000 KB:
Router(config)# memory free low-watermark processor 200000
If available free processor memory falls below this threshold, the router sends a notification message like
this one:
000029: *Aug 12 22:31:19.559: %SYS-4-FREEMEMLOW: Free Memory has dropped below 20000k
Pool: Processor Free: 66814056 freemem_lwm: 204800000
Once available free processor memory rises to a point 5 percent above the threshold, another notification
message like this is sent:
000032: *Aug 12 22:33:29.411: %SYS-5-FREEMEMRECOVER: Free Memory has recovered 20000k
Pool: Processor Free: 66813960 freemem_lwm: 0
Related Commands
Command
Description
L through mode
memory lite
memory lite
To enable the memory allocation lite (malloc_lite) feature, use the memory lite command in global
configuration mode. To disable this feature, use the no form of this command.
memory lite
no memory lite
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.3(11)T
The malloc_lite feature was implemented to avoid excessive memory allocation overhead for situations
where less than 128 bytes were required. This feature is supported for processor memory pools only.
The malloc_lite feature is enabled by default. If the malloc_lite feature is disabled using the no memory
litecommand, you can re-enable the feature by entering the memory lite command.
Examples
Related Commands
Command
Description
L through mode
memory reserve
memory reserve
To reserve a specified amount of memory in kilobytes for console access and critical notifications, use the
memory reserve command in global configuration mode. To disable the configuration, use the no form of
this command.
Syntax for Releases 15.0(1)M and 12.2(33)SRC and Later Releases
memory reserve {console size | critical [total-size]}
no memory reserve {console | critical}
Syntax for Releases 12.2(33)SXI, Cisco IOS XE Release 2.1 and Later Releases
memory reserve critical [total-size]
no memory reserve critical
Syntax Description
console
size
critical
total-size
Command Modes
Command Default
256 KB is reserved for console memory access. 100 KB is reserved for cricial memory access.
Command History
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
L through mode
memory reserve
Usage Guidelines
Release
Modification
The memory reserve console command reserves enough memory to ensure console access to a Cisco IOS
device for administrative and troubleshooting purposes. This feature is especially beneficial when the
device runs low on memory.
The memory reserve critical command reserves the specified amount of memory in kilobytes so that the
router can issue critical notifications. The amount of memory reserved for critical notifications cannot
exceed 25 percent of the total available memory.
Examples
The following example shows how to reserve a specified amount of memory in kilobytes for console
access:
Router# configure terminal
Router(config)# memory reserve console 2
Related Commands
Command
Description
L through mode
memory reserve critical
Effective with Cisco IOS Release 12.4(15)T1, the memory reserve critical command is replaced by the
memory reserve command. See the memory reserve command for more information.
To configure the size of the memory region to be used for critical notifications (system logging messages),
use the memory reserve criticalcommand in global configuration mode. To disable the reservation of
memory for critical notifications, use the no form of this command.
memory reserve critical kilobytes
no memory reserve critical
Syntax Description
kilobytes
Command Default
Command Modes
Command History
Release
Modification
12.2(18)S
12.0(26)S
12.3(4)T
12.2(27)SBC
12.2(33)SRA
12.4(15)T1
L through mode
memory reserve critical
Usage Guidelines
Note
Examples
This command reserves a region of memory on the router so that, when system resources are overloaded,
the router retains enough memory to issue critical system logging messages.
Once the size of the reserved memory region is specified, any change to the specified value takes effect
only after the current configuration is saved and the system has been reloaded.
The following example shows how to reserve 1,000 KB of system memory for logging messages at the
next system restart:
Router(config)# memory reserve critical 1000
Related Commands
Command
Description
L through mode
memory sanity
memory sanity
To perform a sanity check for corruption in buffers and queues, use the memory sanity command in
global configuration mode. To disable this feature, use the no form of this command.
memory sanity [buffer | queue | all]
no memory sanity
Syntax Description
buffer
queue
all
Command Default
This command is not enabled by default. If the buffer or queue keyword is not specified, a sanity check
will be performed on all buffers and queues.
Command Modes
Global configuration
Command History
Release
Modification
12.2(15)T
Usage Guidelines
When the memory sanity buffer command is enabled, a sanity check is performed on buffers when a
packet buffer is allocated or when a packet buffer is returned to the buffer pool. This command also timestamps the buffer, which may be useful when tracking the age of a buffer.
The memory sanity command can be saved in the startup configuration file and, therefore, it is not
necessary to reconfigure this command each time the router is reloaded. Like the scheduler heapcheck
process memory command, the memory sanity command can check for corruption in the I/O memory
block.
Enabling the memory sanity command may result in slight router performance degradation.
Examples
The following example shows how to perform a sanity check for corruption in all buffers and queues:
memory sanity all
L through mode
memory sanity
Related Commands
Command
Description
L through mode
memory scan
memory scan
To enable the Memory Scan feature, use the memory scan command in global configuration mode. To
restore the router configuration to the default, use the no form of this command.
memory scan
no memory scan
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.0(4)XE
12.0(7)T
12.2(33)SRA
Usage Guidelines
The Memory Scan feature adds a low-priority background process that searches all installed dynamic
random-access memory (DRAM) for possible parity errors. If errors are found in memory areas that are not
in use, this feature attempts to scrub (remove) the errors. The time to complete one memory scan and scrub
cycle can range from 10 minutes to several hours, depending on the amount of installed memory. The
impact of the Memory Scan feature on the central processing unit (CPU) is minimal. To view the status of
the memory scan feature on your router, use the show memory scan command in EXEC mode.
Examples
The following example enables the Memory Scan feature on a Cisco 7500 series router:
Router(config)# memory scan
L through mode
memory scan
Related Commands
Command
Description
L through mode
memory-size iomem
memory-size iomem
To reallocate the percentage of DRAM to use for I/O memory and processor memory, use the memory-size
iomem command in global configuration mode. To revert to the default memory allocation, use the no
form of this command.
memory-size iomem i/o-memory-percentage
no memory-size iomem
Syntax Description
Command Default
Note
Command Modes
Command History
Usage Guidelines
i/o-memory-percentage
The default memory allocation is 25 percent of the DRAM to I/O memory and 75 percent of the DRAM to
processor memory.
If thesmartinitprocess has been enabled, the default memory allocation of 25 percent to the I/O memory
does not apply. Instead, smartinitexamines the network modules, and then calculates the memory
allocation for the I/O memory.
Release
Modification
11.2 P
12.2(33)SRA
12.4(15)T1
When you specify the percentage of I/O memory in the command line, the processor memory automatically
acquires the remaining percentage of the DRAM memory.
L through mode
memory-size iomem
Examples
The following example allocates 40 percent of the DRAM memory to I/O memory and the remaining 60
percent to the processor memory:
Router#
configure terminal
Router(config)#
memory-size iomem 40
Smart-init will be disabled and new I/O memory size will take effect upon reload.
L through mode
menu (EXEC)
menu (EXEC)
To display a preconfigured user menu, use the menu command in user EXEC or privileged EXEC mode.
menu menu-name
Syntax Description
Command Modes
menu-name
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
A user menu is a type of user interface where text descriptions of actions to be performed are displayed to
the user. The user can use the menu to select services and functions without having to know the details of
command-line interface (CLI) commands.
Menus can be created for users in global configuration mode, using the commands listed in the Related
Commands section.
A menu can be invoked at either the user or privileged EXEC level, but if an item in the menu contains a
privileged EXEC command, the user must be logged in at the privileged level for the command to succeed.
Examples
1
2
3
6
9
L through mode
menu (EXEC)
Related Commands
Command
Description
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
menu text
menu title
no menu
L through mode
menu menu-name single-space
Syntax Description
menu-name
Command Default
Enabled for menus with more than nine items; disabled for menus with nine or fewer items.
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
When more than nine menu items are defined, the menu is displayed single-spaced. To configure the menus
with nine or fewer items to display single-spaced, use this command.
Examples
In the following example, single-spaced menu items are displayed for the menu named Access1:
menu Access1 single-space
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
L through mode
menu menu-name single-space
Command
Description
menu default
menu line-mode
menu options
menu prompt
menu status-line
menu text
menu title
L through mode
menu clear-screen
menu clear-screen
To clear the terminal screen before displaying a menu, use the menu clear-screen command in global
configuration mode.
menu clear-screen menu-name clear-screen
Syntax Description
menu-name
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command uses a terminal-independent mechanism based on termcap entries defined in the router and
the configured terminal type for the user. This command allows the same menu to be used on multiple
types of terminals instead of having terminal-specific strings embedded within menu titles. If the termcap
entry does not contain a clear string, the menu system enters 24 new lines, causing all existing text to scroll
off the top of the terminal screen.
Examples
In the following example, the terminal screen is cleared before displaying the menu named Access1:
Router(config)# menu Access1 clear-screen
Related Commands
Command
Description
menu (EXEC)
menu command
L through mode
menu clear-screen
Command
Description
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
menu text
menu title
no menu
L through mode
menu command
menu command
To specify underlying commands for user menus, use the menu command command in global
configuration mode.
menu command menu menu-name command menu-item {command | menu-exit}
Syntax Description
menu-name
menu-item
command
menu-exit
Provides a way for menu users to return to a higherlevel menu or exit the menu system.
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Use this command to assign actions to items in a menu. Use the menu text global configuration command
to assign text to items. These commands must use the same menu name and menu selection key.
The menu command command has a special keyword for the command argument, menu-exit, that is
available only within menus. It is used to exit a submenu and return to the previous menu level, or to exit
the menu altogether and return to the EXEC command prompt.
You can create submenus that are opened by selecting entries in another menu. Use the menu EXEC
command as the command for the submenu item.
L through mode
menu command
Note
If you nest too many levels of menus, the system prints an error message on the terminal and returns to the
previous menu level.
When a menu allows connections (their normal use), the command for an entry activating the connection
should contain a resume command, or the line should be configured to prevent users from escaping their
sessions with the escape-char none command. Otherwise, when they escape from a connection and return
to the menu, there will be no way to resume the session and it will sit idle until the user logs out.
Specifying the resume command as the action that is performed for a selected menu entry permits a user to
resume a named connection or connect using the specified name, if there is no active connection by that
name. As an option, you can also supply the connect string needed to connect initially. When you do not
supply this connect string, the command uses the specified connection name.
You can also use the resume/next command, which resumes the next connection in the users list of
connections. This function allows you to create a single menu entry that steps through all of the users
connections.
Note
A menu should not contain any exit paths that leave users in an unfamiliar interface environment.
When a particular line should always display a menu, that line can be configured with an autocommand
line configuration command. Menus can be run on a per-user basis by defining a similar
autocommandcommand for that local username. For more information about the autocommand
command, refer to the Cisco IOS Dial Technologies Configuration Guide.
Examples
In the following example, the commands to be issued when the menu user selects option 1, 2, or 3 are
specified for the menu named Access1:
menu Access1 command 1 tn3270 vms.cisco.com
menu Access1 command 2 rlogin unix.cisco.com
menu Access1 command 3 menu-exit
The following example allows a menu user to exit a menu by entering Exit at the menu prompt:
menu Access1 text Exit Exit
Related Commands
Command
Description
autocommand
menu (EXEC)
menu clear-screen
L through mode
menu command
Command
Description
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
menu text
menu title
L through mode
menu default
menu default
To specify the menu item to use as the default, use the menu default command in global configuration
mode.
menu menu-name default menu-item
Syntax Description
menu-name
menu-item
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Use this command to specify which menu entry is used when the user presses Enter without specifying an
item. The menu entries are defined by the menu command and menu text global configuration commands.
Examples
In the following example, the menu user exits the menu when pressing Enter without selecting an item:
menu Access1 9 text Exit the menu
menu Access1 9 command menu-exit
menu Access1 default
9
L through mode
menu default
Related Commands
Command
Description
menu (EXEC)
menu command
menu prompt
menu text
menu title
L through mode
menu line-mode
menu line-mode
To require the user to press Enter after specifying an item, use the menu line-mode command in global
configuration mode.
menu menu-name line-mode
Syntax Description
menu-name
Command Default
Enabled for menus with more than nine items. Disabled for menus with nine or fewer items.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
In a menu of nine or fewer items, you ordinarily select a menu item by entering the item number. In line
mode, you select a menu entry by entering the item number and pressing Enter. Line mode allows you to
backspace over the selected number and enter another number before pressing Enter to issue the command.
This option is activated automatically when more than nine menu items are defined but also can be
configured explicitly for menus of nine or fewer items.
In order to use strings as keys for items, the menu line-mode command must be configured.
Examples
In the following example, the line-mode option is enabled for the menu named Access1:
menu Access1 line-mode
L through mode
menu line-mode
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu options
menu prompt
menu single-space
menu status-line
menu text
L through mode
menu options
menu options
To set options for items in user menus, use the menu options command in global configuration mode.
Cisco IOS Release 10.0, 12.2(33)SRA, 12.2(33)SXI , and Later Releases
menu menu-name options menu-item [login] [pause]
Cisco IOS XE Release 3.1S and Later Releases
menu menu-name options menu-item {login | pause}
Syntax Description
menu-name
menu-item
login
pause
Command Default
Command Modes
Command History
Release
Modification
10.0
12.2(33)SRA
12.2(33)SXI
L through mode
menu options
Usage Guidelines
Use the menu command and menu text commands to define a menu entry.
Examples
The following example shows how to configure the router to request a login before issuing the command
specified by menu entry 3 of the menu named Access1:
Router(config)#
menu Access1 options 3 login
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu prompt
menu single-space
menu status-line
menu text
menu title
L through mode
menu prompt
menu prompt
To specify the prompt for a user menu, use the menu prompt command in global configuration mode.
menu menu-name prompt d prompt d
Syntax Description
menu-name
prompt
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Press Enter after entering the first delimiter. The router will prompt you for the text of the prompt. Enter the
text followed by the delimiter, and press Enter.
Use the menu command and menu text commands to define the menu selections.
Examples
In the following example, the prompt for the menu named Access1 is configured as Select an item.:
Router(config)# menu Access1 prompt /
Enter TEXT message. End with the character '/'.
Select an item. /
Router(config)#
L through mode
menu prompt
Related Commands
Command
Description
menu (EXEC)
menu command
menu default
menu text
menu title
L through mode
menu status-line
menu status-line
To display a line of status information about the current user at the top of a menu, use the menu status-line
command in global configuration mode.
menu menu-name status-line
Syntax Description
menu-name
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command displays the status information at the top of the screen before the menu title is displayed.
This status line includes the routers host name, the users line number, and the current terminal type and
keymap type (if any).
Examples
In the following example, status information is enabled for the menu named Access1:
menu Access1 status-line
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
L through mode
menu status-line
Command
Description
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu text
menu title
L through mode
menu text
menu text
To specify th e text of a menu item in a user menu, use the menu text command in global configuration
mode.
menu menu-name text menu-item menu-text
Syntax Description
menu-name
menu-item
menu-text
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Use this command to assign text to items in a menu. Use the menu command command to assign actions
to items. These commands must use the same menu name and menu selection key.
You can specify a maximum of 18 items in a menu.
Examples
In the following example, the descriptive text for the three entries is specified for options 1, 2, and 3 in the
menu named Access1:
menu Access1 text 1 IBM Information Systems
L through mode
menu text
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
menu title
L through mode
menu title
menu title
To create a t itle (banner) for a user menu, use the menu title command in global configuration mode.
menu menu-name title d menu-title d
Syntax Description
menu-name
menu-title
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The menu title command must use the same menu name used with the menu text and menu command
commands used to create a menu.
You can position the title of the menu horizontally by preceding the title text with blank characters. You
can also add lines of space above and below the title by pressing Enter.
Follow the title keyword with one or more blank characters and a delimiting character of your choice. Then
enter one or more lines of text, ending the title with the same delimiting character. You cannot use the
delimiting character within the text of the message.
When you are configuring from a terminal and are attempting to include special control characters, such as
a screen-clearing string, you must use Ctrl-V before the special control characters so that they are accepted
as part of the title string. The string ^[[H^[[J is an escape string used by many VT100-compatible terminals
to clear the screen. To use a special string, you must enter Ctrl-V before each escape character.
L through mode
menu title
You also can use the menu clear-screen global configuration command to clear the screen before
displaying menus and submenus, instead of embedding a terminal-specific string in the menu title. The
menu clear-screen command allows the same menu to be used on different types of terminals.
Examples
In the following example, the title that will be displayed is specified when the menu named Access1 is
invoked. Press Enter after the second slash (/) to display the prompt.
Router(config)# menu Access1 title /^[[H^[[J
Enter TEXT message. End with the character '/'.
Welcome to Access1 Internet Services
Type a number to select an option;
Type 9 to exit the menu.
/
Router(config)#
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
menu text
L through mode
microcode (12000)
microcode (12000)
To load a Cisco IOS software image on a line card from Flash memory or the GRP card on a Cisco 12000
series Gigabit Switch Router (GSR), use the microcode command in global configuration mode. To load
the microcode bundled with the GRP system image, use the no form of this command.
microcode {oc12-atm | oc12-pos | oc3-pos4} {flash file-id [slot] | system [slot]}
no microcode {oc12-atm | oc12-pos | oc3-pos4} [flash file-id [slot] | system [slot]]
Syntax Description
Interface name.
flash
file-id
slot
system
Command Default
The default is to load the image from the GRP card (system).
Command Modes
Global configuration
Command History
Release
Modification
11.2 GS
L through mode
microcode (12000)
Usage Guidelines
Release
Modification
12.2(33)SRA
In addition to the Cisco IOS image that resides on the GRP card, each line card on a Cisco 12000 series has
a Cisco IOS image. When the router is reloaded, the specified image is loaded onto the GRP card and then
automatically downloaded to all the line cards.
Normally, you want the same Cisco IOS image on the GRP card and all line cards. However, if you want to
upgrade a line card with a new version of microcode for testing or to fix a defect, you might need to load a
Cisco IOS image that is different from the one on the line card. Additionally, you might need to load a new
image on the line card to work around a problem that is affecting only one of the line cards.
To load a Cisco IOS image on a line card, first use the copy tftp command to download the Cisco IOS
image to a slot on one of the PCMCIA Flash memory cards. Then use the microcode command to
download the image to the line card, followed by the microcode reload command to start the image.
Immediately after you enter the microcode reload command and press Return, the system reloads all
microcode. Global configuration mode remains enabled. After the reloading is complete, enter the exit
command to return to the EXEC system prompt.
To verify that the correct image is running on the line card, use the execute-on slot slot show version
command.
For additional information on GSR configuration, refer to the documentation specific to your Cisco IOS
software release.
Examples
In the following example, the Cisco IOS software image in slot 0 is downloaded to the line card in slot 10.
This software image is used when the system is booted, a line card is inserted or removed, or the
microcode reloadglobal configuration command is issued.
Router(config)# microcode oc3-POS-4 flash slot0:fip.v141-7 10
Router(config)# microcode reload 10
In this example, the user would issue the execute-on slot 10 show version command to verify that the
correct version is loaded.
Related Commands
Command
Description
L through mode
microcode (7000/7500)
microcode (7000/7500)
To specify the location of the microcode that you want to download from Flash memory into the writable
control store (WCS) on Cisco 7000 series (including RSP based routers) or Cisco 7500 series routers, use
the microcode command in global configuration mode. To load the microcode bundled with the system
image, use the no form of this command.
microcode interface-type {flash-filesystem:filename [slot] | rom | system [slot]}
no microcode interface-type {flash-filesystem:filename [slot] | rom | system [slot]}
Syntax Description
interface-type
flash-filesystem :
filename
slot
rom
system
Command Default
The default is to load from the microcode bundled in the system image.
Command Modes
Global configuration
Command History
Release
Modification
10.3
L through mode
microcode (7000/7500)
Usage Guidelines
Release
Modification
12.2(33)SRA
If you do not use the microcode reload command after using the microcode command, the microcode
reload command will be written to the configuration file automatically.
When using Dual RSPs for simple hardware backup, ensure that the master and slave RSP card contain the
same microcode image in the same location when the router is to load the interface processor microcode
from a Flash file system. Thus, if the slave RSP becomes the master, it will be able to find the microcode
image and download it to the interface processor.
Examples
In the following example, all FIP cards will be loaded with the microcode found in Flash memoryfile
fip.v141-7 when the system is booted, when a card is inserted or removed, or when the microcode
reloadglobal configuration command is issued. The configuration is then written to the startup
configuration file.
Router(config)#
microcode fip slot0:fip.v141-7
Router(config)# end
Router# copy system:running-config nvram:startup-config
Related Commands
Command
Description
more flh:logfile
L through mode
microcode (7200)
microcode (7200)
To configure a default override for the microcode that is downloaded to the hardware on a Cisco 7200
series router, use the microcode command in global configuration mode. To revert to the default microcode
for the current running version of the Cisco IOS software, use the no form of this command.
microcode {ecpa | pcpa} location
no microcode {ecpa | pcpa}
Syntax Description
ecpa
pcpa
location
Command Default
If the default or noform of the command is specified, the driver uses the default microcode for the current
running version of the Cisco IOS software.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.3(3)T
12.2(33)SRA
If there are any default overrides when the configuration is written, then the microcode reload command
will be written to the configuration automatically. This action enables the configured microcode to be
downloaded at system startup.
The CPA microcode image is preloaded on Flash memory cards for Cisco 7200-series routers for Cisco
IOS Release 11.3(3)T and later releases. You may be required to copy a new image to Flash memory when
a new microcode image becomes available.
For more information on the CPA configuration and maintenance, refer to the Configuring Cisco
Mainframe Channel Connection Adapters chapter in the Release 12.2 Cisco IOS Bridging and IBM
Networking Configuration Guide.
L through mode
microcode (7200)
Examples
The following example instructs the Cisco IOS software to load the microcode from an individual
microcode image that is stored as a file on the Flash card inserted in Flash card slot 0:
microcode ecpa slot0:xcpa26-1
Related Commands
Command
Description
show microcode
L through mode
microcode reload (12000)
Syntax Description
Command Modes
Command History
Usage Guidelines
slot-number
Global configuration
Release
Modification
11.2 GS
12.2(33)SRA
In addition to the Cisco IOS image that resides on the GRP card, each line card on Cisco 12000 series
routers has a Cisco IOS image. When the router is reloaded, the specified Cisco IOS image is loaded onto
the GRP card and automatically downloaded to all the line cards.
Normally, you want the same Cisco IOS image on the GRP card and all line cards. However, if you want to
upgrade a line card with a new version of microcode for testing or to fix a defect, you might need to load a
different Cisco IOS image. Additionally, you might need to load a new image on the line card to work
around a problem affecting only one of the line cards.
To load a Cisco IOS image on a line card, first use the copy tftp command to download the Cisco IOS
image to a slot on one of the PCMCIA Flash memory cards. Then use the microcode command to
download the image to the line card, followed by the microcode reload command to start the image. To
verify that the correct image is running on the line card, use the execute-on slot slot show version
command.
For additional information on GSR configuration, refer to the Observing System Startup and Performing a
Basic Configuration chapter in the Cisco 12000 series installation and configuration guides.
The microcode reload (12000) command allows you to issue another command immediately.
L through mode
microcode reload (12000)
Note
Examples
Issuing a microcode reload command on any of the line cards in a Cisco 12000 GSR immediately returns
the console command prompt. This allows you to issue a subsequent command immediately to the
reloading line card. However, any commands entered at this time will not execute, and often no indication
will be given that such a command failed to run. Verify that the microcode has reloaded before issuing new
commands.
In the following example, the mirocode firmware is reloaded on the line card in slot 10:
Router(config)# microcode reload 10
Related Commands
Command
Description
microcode (12000)
L through mode
microcode reload (7000 7500)
Syntax Description
slot-number
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Note
Release
Modification
10.3
12.3(8)T
12.2(33)SRA
This command reloads the microcode without rebooting the router. Immediately after you enter the
microcode reload command, the system reloads all microcode. Global configuration mode remains
enabled.
If you modify the system configuration to load a microcode image, the microcode reload command will be
written to the configuration file automatically following the use of a microcode command. This action
enables the configured microcode to be downloaded at system startup.
L through mode
microcode reload (7000 7500)
Examples
In the following example, all controllers are reset, and the microcode specified in the current configuration
is loaded:
Router(config)# microcode reload
Related Commands
Command
Description
microcode (7000/7500)
L through mode
microcode reload (7200)
Syntax Description
Command Modes
Command History
Usage Guidelines
all
ecpa
pcpa
slot slot-number
Privileged EXEC
Release
Modification
11.3(3)T
12.2(33)SRA
Hardware types that do not support downloadable microcode are unaffected by the microcode reload all
command.
You will be prompted for confirmation before the microcode reloadcommand is executed.
Examples
The following example reloads the ESCON CPA microcode in slot 5 with the currently configured
microcode:
Router# microcode reload ecpa slot 5
L through mode
microcode reload (7200)
Related Commands
Command
Description
microcode (7200)
show microcode
L through mode
mkdir
mkdir
To create a new directory in a Class C flash file system, use the mkdir command in user EXEC, privileged
EXEC, or diagnostic mode.
mkdir directory
Syntax Description
Command Modes
Command History
directory
Release
Modification
11.3AA
12.2(33)SRA
Usage Guidelines
Examples
L through mode
mkdir
Directory of flash:
2 drwx
0
Mar 13 1993 13:16:21
8128000 bytes total (8126976 bytes free)
Related Commands
newdir
Command
Description
dir
rmdir
L through mode
mkdir disk0:
mkdir disk0:
To create a new directory in a Flash file system, use the mkdir disk0:command.
mkdir disk0:
Syntax Description
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Examples
L through mode
mkdir disk0:
Related Commands
Command
Description
cd
dir
rmdir
L through mode
mode
mode
To set the redundancy mode, use the mode command in redundancy configuration mode.
Syntax for 12.2S Release
mode {rpr | rpr-plus | sso}
Syntax for Cisco IOS XE Release 2.5 and Later Releases
mode {rpr | sso}
Syntax for 12.2XNE Release
mode sso
Syntax Description
Command Default
rpr
rpr-plus
sso
Command Default
Command Default
The default is SSO mode if the system is not configured for redundancy and the active and standby
supervisor engines have the same image.
The default is RPR mode if different versions are installed.
If redundancy is enabled, the default is the mode that you have configured.
The default is RPR+ mode if the system is not configured for redundancy and the active and standby
supervisor engines have the same image.
The default is RPR mode if different versions are installed.
If redundancy is enabled, the default is the mode that you have configured.
The default is SSO mode if the system is not configured for redundancy and the active and standby
supervisor engines have the same image.
The default is RPR mode if different versions are installed.
L through mode
mode
Command Default
Command Modes
Command History
Usage Guidelines
The default is SSO mode if the system is not configured for redundancy and the active and standby
supervisor engines have the same image.
The default is RPR mode if different versions are installed.
Release
Modification
12.2(14)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
12.2(33)XNE
Nonstop forwarding (NSF) with SSO redundancy mode supports IPv4. NSF with SSO redundancy mode
does not support IPv6, Internetwork Packet Exchange (IPX), and Multiprotocol Label Switching (MPLS).
If you have configured MPLS on the Cisco 7600 series routers with redundant supervisor engines, you
must configure the Cisco 7600 series router in RPR mode. The switch should not be running in the default
mode of SSO.
Enter the redundancy command in global configuration mode to enter redundancy configuration mode.
You can enter the mode command within redundancy configuration mode.
L through mode
mode
Follow these guidelines when configuring your system for RPR+ mode:
You must install compatible images on the active and standby supervisor engines to support RPR+
mode and SSO mode.
Both supervisor engines must run the same Cisco IOS software version.
Any modules that are not online at the time of a switchover are reset and reloaded on a switchover.
The Forwarding Information Base (FIB) tables are cleared on a switchover. As a result, routed traffic
is interrupted until route tables reconverge.
The standby supervisor engine reloads on any change of mode and begins to work in the current mode.
When you use this command to force the standby supervisor engine to run as a Distributed Forwarding
Card (DFC) card, the uplink ports in the standby engine continue to be in use and are not disabled.
Cisco IOS Release XE Release 2.5 and ASR 1000 Series Routers
For Cisco ASR 1002 and 1004 routers, RRP and stateful switchover can be used to switch between Cisco
IOS processes. RPR and SSO need to be configured by the user, however, because a second Cisco IOS
process is not available by default on Cisco ASR 1002 and 1004 routers. Enter the redundancy command
in global configuration mode to enter redundancy configuration mode. You can enter the mode command
within redundancy configuration mode.
The Cisco ASR 1006 Router supports a second Route Processor. The second Cisco IOS process can run
only on the standby Route Processor. This means that hardware redundancy is available and RPR and SSO
do not need to be configured by the user because a second Cisco IOS process is available by default on the
Cisco ASR 1006 router.
RPR+ mode is not supported on the Cisco ASR 1000 Series Routers.
Cisco IOS Release 12.2XNE and 1000 Series Routers
Enter the redundancy command in global configuration mode to enter redundancy configuration mode.
You can enter the mode command within redundancy configuration mode.
RPR mode is not supported on the Cisco 10000 router.
Examples
Related Commands
Command
Description
redundancy
redundancy force-switchover
route-converge-interval
L through mode
mode
Command
Description
show redundancy
Displays RF information.
show running-config
L through mode
mode
Syntax Description
component
clear
continuous
disable
dump
pretty
enable
one-shot
size
all-traces
merged
l3
spa
cancel
subsys
Command Default
Command Modes
Command History
Release
Modification
12.0(18)S
12.2(8)T
12.2(14)SX
Usage Guidelines
Note
Release
Modification
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(33)SXH
12.4(20)T
Use the monitor event-trace command to control what, when, and how event trace data is collected. Use
this command after you have configured the event trace functionality on the networking device using the
monitor event-trace command in global configuration mode.
The amount of data collected from the trace depends on the trace message size configured using the
monitor event-tracecommand in global configuration mode for each instance of a trace.
The Cisco IOS software allows for the subsystem components to define whether support for event tracing is
enabled or disabled at boot time. You can enable or disable event tracing in two ways: using the monitor
event-tracecommand in privileged EXEC mode or using the monitor event-tracecommand in global
configuration mode. To disable event tracing, you would enter either of these commands with the disable
keyword. To enable event tracing again, you would enter either of these commands with the enable
keyword.
To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ?
commandto get a list of software components that support event tracing. To determine whether event
tracing is enabled by default for the subsystem, use the show monitor event-trace command to display
trace messages.
Use the show monitor event-trace command to display trace messages. Use the monitor event-trace
component dump command to save trace message information for a single event. By default, trace
information is saved in binary format. If you want to save trace messages in ASCII format, possibly for
additional application processing, use the monitor event-trace component dump pretty command.
To write the trace messages for all events currently enabled on a networking device to a file, enter the
monitor event-trace dumpcommand.
To configure the file where you want to save trace information, use the monitor event-trace command in
global configuration mode. The trace messages are saved in a binary format.
Examples
The following example shows the privileged EXEC commands to stop event tracing, clear the current
contents of memory, and reenable the trace function for the interprocess communication (IPC) component.
This example assumes that the tracing function is configured and enabled on the networking device.
Router# monitor event-trace ipc disable
Router# monitor event-trace ipc clear
Router# monitor event-trace ipc enable
The following example shows how the monitor event-trace one-shotcommand accomplishes the same
function as the previous example except in one command. In this example, once the size of the trace
message file has been exceeded, the trace is terminated.
Router# monitor event-trace ipc one-shot
The following example shows the command for writing trace messages for an event in binary format. In
this example, the trace messages for the IPC component are written to a file.
Router# monitor event-trace ipc dump
The following example shows the command for writing trace messages for an event in ASCII format. In
this example, the trace messages for the MBUS component are written to a file.
Router# monitor event-trace mbus dump pretty
Catalyst 6500 Series Switches and Cisco 7600 Series Routers Examples Only
This example shows how to stop event tracing, clear the current contents of memory, and reenable the trace
function for the SPA component. This example assumes that the tracing function is configured and enabled
on the networking device.
Router# monitor event-trace spa disable
Router# monitor event-trace spa clear
Router# monitor event-trace spa enable
Related Commands
Command
Description
Syntax Description
component
disable
dump-file filename
enable
size number
timestamps
datetime
localtime
msec
show-timezone
uptime
clear
continuous
one-shot
Command Default
Command Modes
Command History
Release
Modification
12.0(18)S
12.2(8)T
12.2(14)SX
12.2(25)S
Usage Guidelines
Note
Release
Modification
12.2(28)SB
12.2(33)SRA
12.4(20)T
Use the monitor event-trace command to enable or disable event tracing and to configure event trace
parameters for Cisco IOS software subsystem components.
Event tracing is intended for use as a software diagnostic tool and should be configured only under the
direction of a Technical Assistance Center (TAC) representative. In Cisco IOS software images that do not
provide subsystem support for the event trace function, the monitor event-trace command is not available.
The Cisco IOS software allows the subsystem components to define whether support for event tracing is
enabled or disabled by default. The command interface for event tracing allows you to change the default
two ways: using the monitor event-tracecommand in privileged EXEC mode or using the monitor eventtracecommand in global configuration mode.
Additionally, default settings do not show up in the configuration file. If the subsystem software enables
event tracing by default, the monitor event-tracecomponentenable command will not show up in the
configuration file of the networking device; however, disabling event tracing that has been enabled by
default by the subsystem will create a command entry in the configuration file.
Note
The amount of data collected from the trace depends on the trace message size configured using the
monitor event-tracecommand for each instance of a trace.
To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ?
commandto get a list of software components that support event tracing.
To determine whether event tracing is enabled by default for the subsystem, use the show monitor eventtrace command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer.
Examples
The following example shows how to enable event tracing for the interprocess communication (IPC)
subsystem component in Cisco IOS software and configure the size to 4096 messages. The trace messages
file is set to ipc-dump in slot0 (flash memory).
configure terminal
!
monitor event-trace ipc enable
monitor event-trace ipc dump-file slot0:ipc-dump
monitor event-trace ipc size 4096
When you select Cisco Express Forwarding as the component for which to enable event tracing, you can
use the following additional arguments and keywords: monitor event-trace cef [events | interface | ipv6 |
ipv4][all]. The following example shows how to enable event tracing for IPv4 or IPv6 events of the Cisco
Express Forwarding component in Cisco IOS software:
configure terminal
!
monitor event-trace cef ipv4 enable
configure terminal
!
monitor event-trace cef ipv6 enable
exit
The following example shows what happens when you try to enable event tracing for a
component (in this case, adjacency events) when it is already enabled:
configure terminal
!
monitor event-trace adjacency enable
%EVENT_TRACE-6-ENABLE: Trace already enabled.
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
pretty
Privileged EXEC
Release
Modification
12.0(18)S
12.2(8)T
Use the monitor event-trace dump-traces command to save trace message information for all event traces
currently enabled on a networking device. By default, trace information is saved in binary format. If you
want to save trace messages in ASCII format, possibly for additional application processing, use the
monitor event-trace dump-traces pretty command.
To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC)
command.
To configure the file where you want to save messages, use the monitor event-trace (global) command.
Examples
The following example shows how to save the trace messages in binary format for all event traces enabled
on the networking device.
monitor event-trace dump-traces
The following example shows how to save the trace messages in ASCII format for all event traces enabled
on the networking device.
monitor event-trace dump-traces pretty
Related Commands
Command
Description
Syntax Description
destination
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
You can use the monitor pcm-tracer capture-destination command to specify a location to save the PCM
trace information. When Cisco IOS software saves the data to network file systems, such as TFTP and FTP,
it assumes the location is valid and has write access.
After the PCM capture is complete, the router automatically copies the captured contents to the specified
location. The filename format at the destination location is as follows:
<Configured name>_tx_<DS0 slot>_<DS0 unit>_<DS0 channel>--For TX
<Configured name>_rx_<DS0 slot>_<DS0 unit>_<DS0 channel>--For RX
You can identify the dial feature card (DFC) channel from where the PCM is traced using the filename
format.
Consider the following example:
Router(config)# monitor pcm-tracer capture-destination tftp: ://223.255.254.254/
benzeer/cap/cap_data
In this example, two files are created for the data corresponding to each DS0s, one for each direction
(transmitter and receiver). When the debug pcmtracer command is enabled, the trace data is copied into
the following files:
Examples
The following example shows how to configure a router to save the PCM trace information to a flash drive:
Router# configure terminal
Router(config)# monitor pcm-tracer capture-destination flash:
Related Commands
Command
Description
debug pcmtracer
monitor pcm-tracer
Syntax Description
seconds
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to configure the PCM tracer delay time to 1000 seconds:
Router# configure terminal
Router(config)# monitor pcm-tracer delayed-start 1000
Related Commands
Command
Description
monitor pcm-tracer
Syntax Description
profile-number
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
You must create at least one user profile under the channels that need to be traced. You can create the
following profile operations:
Examples
The following example shows how to create a PCM capture profile with profile number 1:
Router# configure terminal
Router(config)# monitor pcm-tracer profile 1
Related Commands
Command
Description
monitor pcm-tracer
monitor permit-list
To configure a destination port permit list or add to an existing destination port permit list, use the monitor
permit-list command in global configuration mode. To delete from or clear an existing destination port
permit list, use the no form of this command.
Activate monitoring
monitor permit-list
no monitor permit-list
Activate monitoring on one port
monitor permit-list destination interface interface-type slot /port
no monitor permit-list destination interface interface-type slot /port
Activate monitoring on one range of ports
monitor permit-list destination interface interface-type slot /port-last-port
no monitor permit-list destination interface interface-type slot / port-last-port
Activate monitoring on two or more ranges of ports
monitor permit-list destination interface interface-type slot /port-last-port , [port-last-port]
no monitor permit-list destination interface interface-type slot /port-last-port , [port-last-port]
Syntax Description
Command Default
destination
interface interface-type
slot
port
last-port
Disabled
Command Modes
Command History
Usage Guidelines
Global configuration
Release
Modification
12.2(18)SXE
12.2(33)SRA
To prevent accidental configuration of ports as destinations, you can create a permit list of the ports that are
valid for use as destinations. With a destination port permit list configured, you can only configure the ports
in the permit list as destinations.
When you enter multiple instances of interface interface-type slot/port-fastport, you must enter a space
before and after the comma. For example, interface interface-type slot/port-fastport , interface-type slot/
port-fastport , interface-type slot/port-fastport.
Examples
This example shows how to configure a destination port permit list that includes Gigabit Ethernet ports 5/1
through 5/4, and activate monitoring:
Router# configure terminal
Router(config)# monitor permit-list destination interface gigabitethernet 5/1-4
Router(config)# monitor permit-list
This example shows how to configure a destination port permit list that includes Fast Ethernet ports 1/1-48,
2/1-48, and Gigabit Ethernet ports 3/1 through 3/4, and activate monitoring:
Router# configure terminal
Router(config)# monitor permit-list destination interface fastEthernet 1/1-48 ,
fastEthernet 2/1-48 , gigabitEthernet 3/1-4
Related Commands
Command
Description
Syntax Description
Command Default
centralized
distributed
Command Modes
Command History
Release
Modification
12.2(33)SXH
12.2(33)SXH2a
Usage Guidelines
Note
Prior to Cisco IOS Release 12.2(33)SXH and the introduction of this feature, the operating mode was
centralized and could not be changed.
Centralized egress span monitoring redirects traffic to the supervisor engine for egress monitoring.
Distributed egress span monitoring is performed in the ingress module. Distributed replication for Switched
Port Analyzer (SPAN), Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN) increases the total
throughput at the span destination.
Note
Examples
Cisco IOS Release 12.2(33)SXH, SXH1, and SXH2
The following example shows how to switch the egress-span mode from the distributed default to
centralized mode:
Router(config)# monitor session egress replication-mode centralized
The following example shows how to switch the egress-span mode from centralized back to distributed
mode:
Router(config)# no monitor session egress replication-mode centralized
The following example shows how to switch the egress-span mode from distributed back to centralized
mode:
Router(config)# no monitor session egress replication-mode distributed
Related Commands
Command
Description
Syntax Description
span-session-number
erspan-destination
erspan-source
local
local-tx
rspan-destination
rspan-source
Command Default
Command Modes
Command History
Release
Modification
12.2(18)SXE
Release
Modification
12.2(18)SXF
12.2(33)SXH
Usage Guidelines
local
local-tx
rspan-destination
rspan-source
Release 12.2(18)SXE and later releases support ERSPAN with the Supervisor Engine 720, hardware
revision 3.2 or higher. Enter the show module version | include WS-SUP720-BASE command to display
the hardware revision.
ERSPAN traffic is GRE-encapsulated SPAN traffic that can only be processed by an ERSPAN destination
session.
This command is not supported on Catalyst 6500 series switches that are configured with a Supervisor
Engine 2.
All ERSPAN source sessions on a switch must use the same source IP address. You enter the origin ip
address command to configure the IP address for the ERSPAN source sessions.
All ERSPAN destination sessions on a switch must use the same IP address. You enter the ip address
command to configure the IP address for the ERSPAN destination sessions. If the ERSPAN destination IP
address is not a Supervisor Engine 720 (for example, it is a network sniffer), the traffic arrives with the
GRE and RSPAN headers/encapsulation intact.
The ERSPAN source session destination IP address, which must be configured on an interface on the
destination switch, is the source of traffic that an ERSPAN destination session sends to the destination
ports. You configure the same address in both the source and destination sessions with the ip address
command.
The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from
different ERSPAN source sessions.
The local ERSPAN session limits are as follows:
Total sessions--66
Source sessions--2 (ingress or egress or both)
Destination sessions--23
The monitor session type command creates a new ERSPAN session or allows you to enter the ERSPAN
session configuration mode. ERSPAN uses separate source and destination sessions. You configure the
source and destination sessions on different switches. The ERSPAN session configuration mode prompts
are as follows:
The table below lists the ERSPAN destination session configuration mode syntaxes.
Table 29
Syntax
Description
shutdown
no shutdown
source
erspan-id erspan-flow-id
vrf vrf-name
Table 30
Syntax
Description
shutdown
no shutdown
description session-description
erspan-id erspan-flow-id
vrf vrf-name
When you configure the monitor sessions, follow these syntax guidelines:
Note
In lists, you must enter a space before and after the comma. In ranges, you must enter a space before and
after the dash.
When you clear the monitor sessions, follow these syntax guidelines:
Note
The no monitor sessionsession-number command entered with no other parameters clears the session
session-number .
session-range is first-session-number -last-session-number.
When you enter the no monitor session range command, do not enter spaces before or after the dash. If
you enter multiple ranges, do not enter spaces before or after the commas.
Use the monitor session type local command to configure ingress, egress, or both ingress and egress
SPAN sessions.
Use the monitor session type local-tx command to configure egress-only SPAN sessions.
When you enter the local or the local egress-only SPAN session configuration mode, the prompt changes
accordingly to Router(config-mon-local)# or Router(config-mon-local-tx)#, and the following commands
are available:
description -- Describes the properties for this session using this syntax:
description description
The descriptioncan be up to 240 characters and cannot contain special characters or spaces.
destination -- Specifies the destination and the destination properties using this syntax:
destination analysis-module num anomaly-detector-module num interface type number intrusiondetection-module num
analysis-module num
anomaly-detector-module num
ingress
learning
intrusion-detection-module num
cpu rp
cpu sp
vlan vlan-id
both
rx
tx When you enter the local-tx keyword, the rx and (Optional) Monitors the transmitted traffic only.
both keywords are not available and the tx keyword
is required.
The local SPAN session limits are as follows:
Total sessions--80
Source sessions--2 (ingress or egress or both)
Egress only--14
If you enter the filter keyword on a monitored trunk interface, only traffic on the set of specified VLANs is
monitored.
Only one destination per SPAN session is supported. If you attempt to add another destination interface to a
session that already has a destination interface configured, you get an error. You must first remove a SPAN
destination interface before changing the SPAN destination to a different interface.
You can configure up to 64 SPAN destination interfaces, but you can have one egress SPAN source
interface and up to 128 ingress source interfaces only.
A SPAN session can either monitor VLANs or monitor individual interfaces, but it cannot monitor both
specific interfaces and specific VLANs. Configuring a SPAN session with a source interface and then
trying to add a source VLAN to the same SPAN session causes an error. Configuring a SPAN session with
a source VLAN and then trying to add a source interface to that session also causes an error. You must first
clear any sources for a SPAN session before switching to another type of source.
Port channel interfaces display in the list of interface options if you have them configured. VLAN
interfaces are not supported. However, you can span a particular VLAN by entering the monitor session
session source vlan vlan-id command.
When you configure the destination, use these guidelines:
A single-interface is as follows:
Note
Destination port channel interfaces must be configured with the channel-group group-num mode on
command and the no channel-protocol command.
Note
In lists, you must enter a space before and after the comma. In ranges, you must enter a space before and
after the dash.
When you clear the monitor sessions, follow these syntax guidelines:
Note
The no monitor sessionsession-number command entered with no other parameters clears the session
session-number .
session-range is first-session-number -last-session-number.
When you enter the no monitor session range command, do not enter spaces before or after the dash. If
you enter multiple ranges, do not enter spaces before or after the commas.
Examples
This example shows how to configure an ERSPAN source session number and enter the ERSPAN source
session configuration mode for the session:
Router(config)# monitor session 55 type erspan-source
Router(config-mon-erspan-src)#
This example shows how to configure an ERSPAN destination session number and enter the ERSPAN
destination session configuration mode for the session:
Router(config)# monitor session 55 type erspan-destination
Router(config-mon-erspan-dst)#
This example shows how to associate the ERSPAN destination session number with the destination ports:
Router(config-mon-erspan-dst) destination interface fastethernet 1/2 , 2/3
This example shows how to enter the ERSPAN destination session source configuration:
Router(config-mon-erspan-dst)# source
Router(config-mon-erspan-dst-src)#
This example shows how to enter the ERSPAN destination session source configuration mode:
Router(config-mon-erspan-dst)# source
Router(config-mon-erspan-dst-src)#
source
source
source
source
This example shows how to enter the ERSPAN source session destination configuration mode:
Router(config-mon-erspan-src)# destination
Router(config-mon-erspan-src-dst)#
This example shows how to configure the ID number that is used by the source and destination sessions to
identify the ERSPAN traffic:
Router(config-mon-erspan-src-dst)# erspan-id 1005
Router(config-mon-erspan-src-dst)#
This example shows how to configure session 1 to monitor ingress traffic from Gigabit Ethernet port 1/1
and configure Gigabit Ethernet port 1/2 as the destination:
Router(config)# monitor session 1 type local
Router(config-mon-local)# source interface gigabitethernet 1/1 rx
Router(config-mon-local)# destination interface gigabitethernet 1/2
This example shows how to configure session 1 to monitor egress-only traffic from Gigabit Ethernet port
5/1 and configure Gigabit Ethernet port 5/2 as the destination:
Router(config)# monitor session 1 type local-tx
Router(config-mon-local)# source interface gigabitethernet 5/1 rx
Router(config-mon-local)# destination interface gigabitethernet 5/2
Related Commands
Command
Description
mop device-code
To identify the type of device sending Maintenance Operation Protocol (MOP) System Identification
(sysid) messages and request program messages, use the mop device-code command in global
configuration mode. To set the identity to the default value, use the no form of this command.
mop device-code commandmop device-code {cisco | ds200}
no mop device-code {cisco | ds200}
Syntax Description
cisco
ds200
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The sysid messages and request program messages use the identity information indicated by this command.
Examples
The following example identifies a DECserver 200 device as sending MOP sysid and request program
messages:
mop device-code ds200
Related Commands
Command
Description
mop sysid
mop retransmit-timer
To configure the length of time that the Cisco IOS software waits before resending boot requests to a
Maintenance Operation Protocol (MOP) server, use the mop retransmit-timer command in global
configuration mode. To reinstate the default value, use the no form of this command.
mop retransmit-timer seconds
no mop retransmit-timer
Syntax Description
seconds
Command Default
4 seconds
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
By default, when the software sends a request that requires a response from a MOP boot server and the
server does not respond, the message is re-sent after 4 seconds. If the MOP boot server and router are
separated by a slow serial link, it might take longer than 4 seconds for the software to receive a response to
its message. Therefore, you might want to configure the software to wait longer than 4 seconds before
resending the message if you are using such a link.
Examples
In the following example, if the MOP boot server does not respond within 10 seconds after the router sends
a message, the server will resend the message:
mop retransmit-timer 10
Related Commands
Command
Description
mop device-code
mop enabled
mop retries
To configure the number of times the Cisco IOS software will resend boot requests to a Maintenance
Operation Protocol (MOP) server, use the mop retries command in global configuration mode. To
reinstate the default value, use the no form of this command.
mop retries count
no mop retries
Syntax Description
count
Command Default
8 times
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
In the following example, the software will attempt to resend a message to an unresponsive host 11 times
before declaring a failure:
Router(config)# mop retries 11
Related Commands
Command
Description
mop device-code
mop enabled
Command
Description
mop retransmit-timer
more
To display the contents of a file, use the morecommand in privileged EXEC mode.
more [/ascii | /binary | /ebcdic] url
Syntax Description
/ascii
/binary
/ebcdic
url
Command Default
The command displays the conent of a file in its native format. Optional formats include ascii, binary, and
ebcdic.
Command Modes
Command History
Usage Guidelines
Release
Modification
11.3 AA
12.2(33)SRA
The more system:running-config command displays the same output as the show running-config
command. The more nvram:startup-config command is recommended as a replacement for the show
startup-config command and the show configuration command.
You can use this command to display configuration files, as follows:
The more nvram:startup-config command displays the startup configuration file contained in
NVRAM or specified by the CONFIG_FILE environment variable. The Cisco IOS software informs
you whether the displayed configuration is a complete configuration or a distilled version. A distilled
configuration is one that does not contain access lists.
The more system:running-config command displays the running configuration.
These commands show the version number of the software used when you last changed the configuration
file.
You can also display the contents of files on remote systems using the more command. For example, you
could display a saved running configuration file on an FTP server using more ftp://
username:password@ftp-host1/mydirectory/7200-basic-running-config. See the description of the
copy command for more information on file-system prefixes available in the Cisco IOS CLI.
Options for filtering and redirecting the output of this command are available by appending a pipe character
(|). See the Related Commands table for a list of more <url> command extensions.
Examples
The following partial sample output displays the configuration file named startup-config in NVRAM:
Router# more nvram:startup-config
!
! No configuration change since last restart
! NVRAM config last updated at 02:03:26 PDT Thu Oct 2 1997
!
version 12.1
service timestamps debug uptime
service timestamps log uptime
service password-encryption
service udp-small-servers
service tcp-small-servers
.
.
.
end
The following is partial sample output from the more nvram:startup-config command when the
configuration file has been compressed:
Router#
more nvram:startup-config
Using 21542 out of 65536 bytes, uncompressed size = 142085 bytes
!
version 12.1
service compress-config
!
hostname rose
!
.
.
.
.
.
!
end
Related Commands
Command
Description
boot config
service compress-config
show bootvar
Syntax Description
Command Modes
Command History
url
regular-expression
User EXEC
Privileged EXEC
Release
Modification
11.3 AA
12.0(1)T
12.2(33)SRA
Usage Guidelines
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at every --More-- prompt.
To search the remaining output of the more command, use the following command at the --More-- prompt:
/ regular-expression
To filter the remaining output of the more command, use one of the following commands at the --More-prompt:
- regular-expression
+ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z.
Note
Once you specify a filter for a more command, you cannot specify another filter at a --More-- prompt. The
first specified filter remains until the more command output finishes or until you interrupt the output. The
use of the keyword begin does not constitute a filter.
Because prior output is not saved, you cannot search or filter backward through prior output.
Examples
The following is partial sample output of the more nvram:startup-config | begincommand that begins
unfiltered output with the first line that contain the regular expression ip. At the --More-- prompt, the
user specifies a filter to exclude output lines that contain the regular expression ip.
router# more nvram:startup-config | begin ip
ip subnet-zero
ip domain-name cisco.com
ip name-server 198.92.30.32
ip name-server 171.69.2.132
!
isdn switch-type primary-5ess
.
.
.
interface Ethernet1
ip address 5.5.5.99 255.255.255.0
--More--ip
filtering...
media-type 10BaseT
!
interface Serial0:23
encapsulation frame-relay
no keepalive
dialer string 4001
dialer-group 1
isdn switch-type primary-5ess
no fair-queue
Related Commands
Command
Description
Command
Description
Syntax Description
url
Command Modes
Command History
regular-expression
EXEC
Release
Modification
11.3 AA
Usage Guidelines
Release
Modification
12.0(1)T
12.2(33)SRA
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at any --More-- prompt. To search the remaining output of the more
command, use the following command at the --More-- prompt:
/ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z.
Because prior output is not saved, you cannot search or filter backward through prior output.
Examples
The following is partial sample output of the more nvram:startup-config | excludecommand. The use of |
exclude service in the command specifies a filter that excludes lines that contain the regular expression
service. At the --More-- prompt, the user searches for the regular expression Dialer1, which continues
filtered output with the first line that contains Dialer1.
router# more nvram:startup-config | exclude service
!
version 12.0
!
hostname router
!
boot system flash
no logging buffered
!
ip subnet-zero
ip domain-name cisco.com
.
.
.
--More-/Dialer1
filtering...
interface Dialer1
no ip address
no ip directed-broadcast
dialer in-band
no cdp enable
Related Commands
Command
Description
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
url
regular-expression
EXEC
Release
Modification
11.3 AA
12.0(1)T
12.2(33)SRA
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at any --More-- prompt. To search the remaining output of the more
command, use the following syntax at the --More-- prompt:
/ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z.
Because prior output is not saved, you cannot search or filter backward through prior output.
Examples
The following is partial sample output of the more nvram:startup-config | includecommand. It only
displays lines that contain the regular expression ip.
router# more nvram:startup-config | include ip
ip subnet-zero
ip domain-name cisco.com
ip name-server 198.92.30.32
ip name-server 171.69.2.132
description ip address 172.21.53.199 255.255.255.0
ip address 172.21.53.199 255.255.255.0
Related Commands
Command
Description
more flh:logfile
To view the system console output generated during the Flash load helper operation, use the more
flh:logfile privileged EXEC command.
more flh:logfile
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
11.3 AA
12.2(33)SRA
If you are a remote Telnet user performing the Flash upgrade without a console connection, this command
allows you to retrieve console output when your Telnet connection has terminated due to the switch to the
ROM image. The output indicates what happened during the download, and is particularly useful if the
download fails.
This command is a form of the more command. See the more command for more information.
Examples
Name/status
2251320
abc/igs-kf.914
[2251384 bytes used, 1942920 available, 4194304 total]
Accessing file 'abc/igs-kf.914' on 172.16.1.111...
Loading from 172.16.13.111:
Erasing device...... erased
Loading from 172.16.13.111:
- [OK 2251320/4194304 bytes]
Verifying checksum... OK (0x97FA)
Flash copy took 79292 msecs
%FLH: Re-booting system after download
Related Commands
Command
Description
more
Displays a file.
motd-banner
To enable the display of message-of-the-day (MOTD) banners on the specified line or lines, use the motdbanner command in line configuration mode. To suppress the MOTD banners on the specified line or
lines, use the no form of this command.
motd-banner
no motd-banner
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
11.1
12.2(33)SRA
This command determines whether the router will display the MOTD banner when an EXEC session is
created on the specified line or lines. The MOTD banner is defined with the banner motd global
configuration command. By default, the MOTD banner is enabled on all lines. Disable the MOTD banner
on specific lines using the no motd-banner line configuration command.
The MOTD banners can also be disabled by the no exec-banner line configuration command, which
disables both MOTD banners and EXEC banners on a line. If the no exec-banner command is configured
on a line, the MOTD banner will be disabled regardless of whether the motd-bannercommand is enabled
or disabled. The table below summarizes the effects of the exec-banner command and the motd-banner
command.
Table 31
motd-banner (default)
exec-banner (default)
no exec-banner
MOTD banner
None
EXEC banner
no motd-banner
exec-banner (default)
no exec-banner
EXEC banner
None
For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is
displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner
command or no motd-banner command is configured. The table below summarizes the effects of the
exec-banner command and the motd-banner command for reverse Telnet connections.
Table 32
Banners Displayed Based On exec-banner and motd-banner Combinations for Reverse Telnet
Sessions to Async Lines
motd-banner (default)
exec-banner (default)
no exec-banner
MOTD banner
Incoming banner
Incoming banner
no motd-banner
Examples
Incoming banner
Incoming banner
The following example suppresses the MOTD banner on vty lines 0 through 4:
line vty 0 4
no motd-banner
Related Commands
Command
Description
banner exec
banner incoming
banner motd
motd-banner
name-connection
To assign a logical name to a connection, use the name-connectioncommand in user EXEC mode.
name-connection
Syntax Description
Command Default
Command Modes
User EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Examples
The following example assigns the logical name blueto the connection:
Router> where
Conn Host
Address
Byte Idle Conn Name
* 1 doc-2509
172.30.162.131
0
0 doc-2509
Router> name-connection
Connection number: 1
Enter logical name:
blue
Connection 1 to doc-2509 will be named "BLUE" [confirm]
Related Commands
Command
Description
where
no menu
To delete a user menu from the configuration file, use the no menu command in global configuration
mode.
no menu menu-name
Syntax Description
menu-name
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Use this command to remove any menu commands for a particular menu from the configuration file.
As with all global configuration commands, this command will only effect the startup configuration file
when you save the running configuration using the copy running-config startup-config EXEC command.
Examples
Related Commands
Command
Description
menu (EXEC)
menu command
Command
Description
menu prompt
menu text
menu title
notify
To enable terminal notification about pending output from other Telnet connections, use the notify
command in line configuration mode. To disable notifications, use the noform of this command.
notify
no notify
Syntax Description
Command Default
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command sets a line to inform a user that has multiple, concurrent Telnet connections when output is
pending on a connection other than the current one.
Examples
In the following example, notification of pending output from connections is enabled on virtual terminal
lines 0 to 4:
Router(config)# line vty 0 4
Router(config-line)# notify
Related Commands
Command
Description
terminal notify
notify syslog
To enable the sending of notifications of configuration changes to a remote system message logging
(syslog), use the notify syslogcommand in configuration change logger configuration mode. To disable the
sending of notifications of configuration changes to the syslog, use the no form of this command.
notify syslog [contenttype {plaintext | xml}]
no notify syslog [contenttype {plaintext | xml}]
Syntax Description
contenttype
plaintext
xml
Command Default
Command Modes
Command History
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
Usage Guidelines
Enable the notify syslog command if you use the syslog to monitor your router. Syslog monitoring prevents
the need to gather configuration log information manually.
Examples
The following example shows how to enable the router to send notifications (in XML format) to the syslog:
Router# configure terminal
!
Router(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)# notify syslog contenttype xml
Router(config-archive-log-config)# end
Related Commands
Command
Description
archive
hidekeys
log config
logging enable
logging size
padding
To set the padding on a specific output character, use the padding command in line configuration mode. To
remove padding for the specified output character, use the no form of this command.
padding ascii-number count
no padding ascii-number
Syntax Description
ascii-number
count
Command Default
No padding
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Use this command when the attached device is an old terminal that requires padding after certain characters
(such as ones that scrolled or moved the carriage). See the ASCII Character Set and Hex Values
appendix for a list of ASCII characters.
Examples
In the following example, the Return (decimal character 13) is padded with 25 NULL bytes on the console
line:
Router(config)# line console
Router(config-line)# padding 13 25
Related Commands
Command
Description
terminal padding
parity
To define generation of a parity bit, use the parity command in line configuration mode. To specify no
parity, use the no form of this command.
parity {none | even | odd | space | mark}
no parity
Syntax Description
none
even
Even parity.
odd
Odd parity.
space
Space parity.
mark
Mark parity.
Command Default
No parity.
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.4
12.2(33)SRA
Communication protocols provided by devices such as terminals and modems sometimes require a specific
parity bit setting. Refer to the documentation for your device to determine required parity settings.
If you use this command to set parity on Cisco AS5350 and Cisco AS5400 NextPort lines, do not also set
parity by means of S-register settings in a modemcap. (A modemcap is a series of parameter settings that
are sent to your modem to configure it to interact with a Cisco device in a specified way. Cisco IOS
software defines modemcaps that have been found to properly initialize most modems so that they function
properly with Cisco routers and access servers.)
Examples
Related Commands
Command
Description
terminal parity
parser cache
To reenable the Cisco IOS software parser cache after disabling it, use the parser cache command in
global configuration mode. To disable the parser cache, use the no form of this command.
parser cache
no parser cache
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.1(5)T
12.2(33)SRA
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
The parser cache is enabled by default. However, if you wish to disable the parser cache, you may do so
using the no parser cache command in global configuration mode. To reenable the parser cache after it has
been disabled, use the parser cache command.
When the no parser cache is issued, the command line appears in the running configuration file. However,
if the parser cache is reenabled, no command line appears in the running configuration file.
Examples
In the following example, the Cisco IOS software Parser Cache feature is disabled:
Router(config)# no parser cache
Related Commands
Command
Description
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(33)SRE
15.1(1)T
Usage Guidelines
The Parser Concurrency and Locking Improvements feature ensures that exclusive access is granted only to
a requested process and prevents other users from concurrently accessing the Cisco IOS configuration. That
is, it prevents simultaneous execution of two or more commands. Use the parser command serializer
command to configure the Parser Concurrency and Locking Improvements feature.
Examples
The following example shows how to configure the Parser Concurrency and Locking Improvements
feature:
Router# configure terminal
Router(config)# parser command serializer
Related Commands
Command
Description
Syntax Description
Command Default
Disabled
Command Modes
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(25)S
12.2(27)SBC
12.2(33)SRC
12.2(33)SB
12.2(33)SXI
Enable the parser config cache interfacecommand to reduce the execution time required for running
configuration management commands such as the show running-configuration, write terminal, and copy
system:running-configuration commands. Information for these configuration management commands is
supplied by nonvolatile generation (NVGEN) processes that query the system for configuration details. The
parser config cache interfacecommand is especially useful for managing large system configurations that
contain numerous interface configurations.
Once enabled, the command provides faster execution of the NVGEN commands that process the running
system configuration by caching interface configurations in system memory, and by retrieving only
configuration information that has changed. For this reason, the device on which this command is enabled
must have enough memory available to store the interface configuration. For example, if the interface
configurations take up 15 KB of memory, using this command would require having an additional 15 KB
of memory space available.
The first time you display the configuration file, you will not see much evidence of improvement in
performance because the interface cache will be filled up. However, you will notice performance
improvements when you enter subsequent NVGEN-type commands such as the show runningconfiguration EXEC command.
Each time the interface configuration is changed, the interface cache is flushed. Entering an NVGEN-type
command after modifying the interface configuration will once again not show any performance
improvement until the next NVGEN-type command is entered.
Examples
The following example shows how to enable the functionality for reducing the time required for the
command-line interpreter to execute commands that manage the running system configuration files:
Router(config)# parser config cache interface
Related Commands
Command
Description
copy system:running-configuration
show running-configuration
write terminal
Syntax Description
No arguments or keywords.
Command Default
Command Modes
Command History
Usage Guidelines
Note
Release
Modification
12.2(33)SRB
12.2(33)SB
12.2(33)SXI
Note
Examples
Only the no form of this command will appear in configuration files. To determine if config partitioning is
supported on your system and whether it is enabled, use the show running-config parser ? command.
The following example shows how to disable partitioning of the system running configuration:
Router> enable
Router# config t
Enter configuration commands, one per line.
Router(config)# no parser config partition
System configured
Related Commands
Command
Description
parser maximum
To specify performance maximums for CLI operations use the parser maximum command in global
configuration mode. To clear any previously established maximums, us the No form of the command.
parser maximum {latencylimit | utilizationlimit}
no parser maximum {latency | utilization}
Syntax Description
latency
limit
utilization
limit
Command Default
Command Modes
Global Configuration
Command History
Release
Modification
15.1(3)T
Usage Guidelines
The Parser Maximum feature provides a workaround in the event of a problem with the coding of a
protocol, allowing the error to be bypassed untill it can be corrected.
Examples
Related Commands
Command
Description
parser cache
partition
To separate Flash memory into partitions on Class B file system platforms, use the partition command in
global configuration mode. To undo partitioning and to restore Flash memory to one partition, use the no
form of this command.
Cisco 1600 Series and Cisco 3600 Series Routers
partition flash-filesystem : [number-of-partitions] [partition-size]
no partition flash-filesystem:
All Other Class B Platforms
partition flash partitions [size1 size2]
no partition flash
Syntax Description
flash-filesystem :
Command Default
number-of-partitions
partition-size
partitions
size1
size2
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
For the Cisco 1600 series and Cisco 3600 series routers, to undo partitioning, use the partition flashfilesystem :1 or no partition flash-filesystem : command. For other Class B platforms, use either the
partition flash 1 or no partition flash command. If there are files in a partition other than the first, you
must use the erase flash-filesystem:partition-numbercommand to erase the partition before reverting to a
single partition.
When creating two partitions, you must not truncate a file or cause a file to spill over into the second
partition.
Note
Examples
The partition command will only create 3MB or larger partitions and may not be used if the device memory
contains logging persistent files.
The following example divides the Flash memory card in slot 0 into two partitions, each 8 MB in size on a
Cisco 3600 series router:
Router(config)#
partition slot0: 2 8 8
The following example creates four partitions of equal size in the card on a Cisco 1600 series router:
Router(config)# partition flash: 4
Syntax Description
url
Command Default
If this command is not configured, no location or filename prefix is specified for files in the Cisco IOS
configuration archive.
Command Modes
Command History
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SB
Usage Guidelines
When this command is entered, an archive file of the running configuration is saved when the archive
config, write-memory, or copy running-config startup-config command is entered.
URLs are commonly used to specify files or location on the World Wide Web. On Cisco routers, URLs can
be used to specify the location of a file or directory on a router or a remote file server. The path command
uses a URL to specify the location and filename prefix for the Cisco IOS configuration archive.
The locations or file systems that you can specify in the url argument are as follows:
If your platform has disk0--disk0:, disk1:, ftp:, pram:, rcp:, slavedisk0:, slavedisk1:, or tftp:
If your platform does not have disk0--ftp:, http:, pram:, rcp:, or tftp:
Examples
The following example of the path command shows how to specify the hostname, date, and time as the
filename prefix for which to save archive files of the running configuration. In this example, the timeperiod command is also configured to automatically save an archive file of the running configuration every
20 minutes.
configure terminal
!
archive
path disk0:$h$t
time-period 20
end
The following is sample output from the show archive command illustrating the format of the resulting
configuration archive filenames.
Router# show archive
There are currently 3 archive configurations saved.
The next archive file will be named routerJan-16-01:12:23.019-4
Archive # Name
0
1
disk0:routerJan-16-00:12:23.019-1
2
disk0:routerJan-16-00:32:23.019-2
3
disk0:routerJan-16-00:52:23.019-3 <- Most Recent
4
5
6
7
8
9
10
11
12
13
14
The following example show how to create the configuration archive, save the running configuration to the
archive, and display the files in the archive:
configure terminal
!
archive
path tftp://10.48.71.226/router-cfg
exit
exit
!
archive config
Router# show archive
The next archive file will be named tftp://10.48.71.226/router-cfg-2
Archive # Name
0
1
tftp://10.48.71.226/router-cfg-1 <- Most Recent
2
3
4
5
6
7
8
9
10
11
12
13
14
The following is sample output from the show archive command if you did not create the configuration file
on the TFTP server before attempting to archive the current running configuration file:
configure terminal
!
archive
path tftp://10.48.71.226/router-cfg
exit
exit
archive config
Router# show archive
The next archive file will be named tftp://10.48.71.226/router-cfg-1
Archive # Name
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Related Commands
Command
Description
archive
archive config
configure confirm
configure replace
maximum
show archive
time-period
periodic
To specify a recurring (weekly) time range for functions that support the time-range feature, use the
periodic command in time-range configuration mode. To remove the time limitation, use the no form of
this command.
periodic days-of-the-week hh:mm to [days-of-the-week] hh:mm
no periodic days-of-the-week hh:mm to [days-of-the-week] hh:mm
Syntax Description
days-of-the-week
to
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.0(1)T
12.2(33)SRA
For Cisco IOS Release 12.2(11)T, IP and Internetwork Packet Exchange (IPX) extended access lists are the
only functions that can use time ranges. For further information on using these functions, refer to the Cisco
IOS IP Configuration Guide and the Cisco IOS AppleTalk and Novell IPX Configuration Guide.
The periodiccommand is one way to specify when a time range is in effect. Another way is to specify an
absolute time period with the absolute command. Use either of these commands after the time-range
global configuration command, which specifies the name of the time range. Multiple periodicentries are
allowed per time-range command.
If the end days-of-the-week value is the same as the start value, they can be omitted.
If a time-range command has both absolute and periodic values specified, then the periodic items are
evaluated only after the absolute start time is reached, and are not further evaluated after the absolute end
time is reached.
Note
All time specifications are taken as local time. To ensure that the time range entries take effect at the
desired times, you should synchronize the system software clock using Network Time Protocol (NTP).
The table below lists some typical settings for your convenience:
Table 33
Examples
If you want:
Configure this:
The following example configuration denies HTTP traffic on Monday through Friday from 8:00 a.m. to
6:00 p.m.:
Router# show startup-config
.
.
.
time-range no-http
periodic weekdays 8:00 to 18:00
!
ip access-list extended strict
deny tcp any any eq http time-range no-http
!
interface ethernet 0
ip access-group strict in
.
.
.
The following example configuration permits Telnet traffic on Mondays, Tuesdays, and Fridays from 9:00
a.m. to 5:00 p.m.:
Router# show startup-config
.
.
.
time-range testing
periodic Monday Tuesday Friday 9:00 to 17:00
!
ip access-list extended legal
permit tcp any any eq telnet time-range testing
!
interface ethernet 0
ip access-group legal in
.
.
.
Related Commands
Command
Description
absolute
access-list (extended)
deny (IP)
permit (IP)
time-range
ping
To diagnose basic network connectivity on AppleTalk, ATM, Connectionless Network Service (CLNS),
DECnet, IP, Novell IPX, or source-route bridging (SRB) networks, use the ping command in user EXEC or
privileged EXEC mode.
ping [[protocol [tag]]{host-name | system-address}]
Syntax Description
protocol
tag
host-name
system-address
Command Default
Command Modes
Command History
Release
Modification
10.0
12.0(7)T
12.1(12c)E
12.2(2)T
Release
Modification
12.2(13)T
Usage Guidelines
apollo
vines
xns
12.2(28)SB
12.2(25)SG
12.2(33)SRA
12.2(33)SXH
The ping command sends an echo request packet to an address then waits for a reply. Ping output can help
you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is
functioning. For example, the ping clns command sends International Organization for Standardization
(ISO) CLNS echo packets to test the reachability of a remote router over a connectionless Open System
Interconnection (OSI) network.
If you enter the ping command without any keywords or argument values, an interactive system dialog
prompts you for the additional syntax appropriate to the protocol you specify. (See the Examples
section.)
To exit the interactive ping dialog before responding to all the prompts, type the escape sequence. The
default escape sequence is Ctrl-^, X (Simultaneously press and release the Ctrl, Shift, and 6 keys and then
press the X key). The escape sequence will vary depending on your line configuration. For example,
another commonly used escape sequence is Ctrl-c.
The table below describes the test characters sent by the pingfacility.
Table 34
Character
Description
Character
Description
Note
&
Not all protocols require hosts to support pings. For some protocols, the pings are Cisco defined and can be
answered only by another Cisco router.
The availability of protocol keywords depends on what protocols are enabled on your system.
Issuing the ping command in user EXEC mode will generally offer fewer syntax options than issuing the
ping command in privileged EXEC mode.
Examples
After you enter the ping command in privileged EXEC mode, the system prompts you for a protocol
keyword. The default protocol is IP.
If you enter a hostname or address on the same line as the ping command, the default action is taken as
appropriate for the protocol type of that name or address.
The following example is sample dialog from the ping command using default values. The specific dialog
varies somewhat from protocol to protocol.
Router# ping
Protocol [ip]:
Target IP address: 192.168.7.27
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.7.27, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/2/4 ms
The table below describes the significant fields shown in the display.
Table 35
Field
Description
Protocol [ip]:
Target IP address:
!!!!!
The following example verifies connectivity to the neighboring ATM device for the ATM permanent
virtual circuit (PVC) with the virtual path identifier (VPI)/virtual channel identifier (VCI) value 0/16:
Router# ping
Protocol [ip]:atm
ATM Interface:atm1/0
VPI value [0]:
VCI value [1]:16
Loopback - End(0), Segment(1) [0]:1
Repeat Count [5]:
Timeout [2]:
Type escape sequence to abort.
Sending 5, 53-byte segment OAM echoes, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
The table below describes the default ping fields shown in the display.
Table 36
Related Commands
Field
Description
Protocol [ip]:
ATM Interface:
Timeout [2]:
!!!!!
Command
Description
Command
Description
ping ip
ping ipv6
ping sna
ping vrf
ping (privileged)
To diagnose basic network connectivity on Apollo, AppleTalk, Connectionless Network Service (CLNS),
DECnet, IP, Novell IPX, VINES, or XNS networks, use the pingcommand in privileged EXEC command
mode.
ping [hostname | system-address | [protocol | tag] {hostname | system-address}] [data [hex-datapattern] | df-bit | repeat [repeat-count] | size [datagram-size] | source [source-address | async | bvi |
ctunnel | dialer | ethernet | fastethernet | lex | loopback | multilink | null | port-channel | tunnel |
vif | virtual-template | virtual-tokenring | xtagatm] | timeout [seconds] | validate]
Syntax Description
hostname
system-address
protocol
tag
data
hex-data-pattern
df-bit
repeat
repeat-count
size
datagram-size
source
source-address
async
bvi
ctunnel
dialer
ethernet
fastethernet
lex
loopback
multilink
null
port-channel
tunnel
vif
virtual-template
virtual-tokenring
xtagatm
timeout
seconds
validate
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
12.0
12.2(33)SRA
Usage Guidelines
The ping (packet internet groper) command tests the reachability of a remote router over a connectionless
Open System Interconnection (OSI) network. The command sends ISO CLNS echo packets to an address
and waits for a reply. Ping output can help you evaluate path-to-host reliability, delays over the path, and
whether the host can be reached or is functioning.
When you type the ping command, you are prompted to enter options before the ping command executes.
The characters in brackets ([]) indicate default values. When you want to use a default value, press Enter on
your keyboard.
If you enter a hostname or system address when you enter the ping command, the default action is taken
for the protocol type of that hostname or system address.
The optional data, df-bit, repeat, size, source, timeout, and validate keywords can be used to prevent
extended ping command output. You can use as many of these keywords as you need, and you can use
them in any order after the hostname or system-address arguments.
When you enter the ethernet protocol option, you will be prompted to enter MAC address and maintenance
domain in addition to the information common across protocols.
To terminate a ping session before it completes, type the escape sequence (Ctrl-^ X) by simultaneously
pressing and releasing the Ctrl, Shift, and 6 keys and then pressing the X key.
Note
Not all protocols require hosts to support pings. For some protocols, the pings are defined by Cisco and
answered only by a Cisco router.
The table below describes the test characters that the ping operation uses.
Table 37
Character
Description
Receipt of a reply.
&
Examples
The following example shows a ping command and output. The precise dialog varies from protocol to
protocol, but all are similar to the ping session shown here using default values.
Router#
ping
Protocol [ip]:
Target IP address: 192.168.7.27
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.7.27, timeout is 2 seconds:
!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/2/4 ms
The following example shows how to send a ping specifying the ethernet protocol option, MAC address,
and maintenance domain and using the default values for the remaining parameters:
Router# ping
Protocol [ip]: ethernet
Mac Address : aabb.cc00.0410
Maintenance Domain : DOMAIN_PROVIDER_L5_1 VLAN [0]: 2 Source MPID [1522]:
Repeat Count [5]:
Datagram Size [107]:
Timeout in seconds [2]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5 Ethernet CFM loopback messages, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/8 ms.
Related Commands
Command
Description
ping ethernet
ping (user)
ping vrf
ping ip
To test network connectivity on IP networks, use the ping ip command inprivileged EXEC mode.
ping ip {host-name | ip-address} [data [hex-data-pattern] | df-bit | repeat [repeat-count] | tos
[service value] | size [datagram-size] source {source-address | source-interface}] [timeout seconds]
[validate] [verbose]
Syntax Description
host-name
system-address
data hex-data-pattern
df-bit
repeat repeat-count
size
datagram-size
source
source-address
source-interface
Command Modes
Command History
timeout seconds
validate
verbose
Privileged Exec
Release
Modification
10.0
12.0
12.2(33)SRA
Usage Guidelines
Release
Modification
15.2(02)S
The ping command sends an echo request packet to an address, then awaits a reply. Ping output can help
you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is
functioning.
To abnormally terminate a ping session, type the escape sequence--by default, Ctrl-^ X. You type the
default by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
The table below describes the test characters that the ping facility sends.
Table 38
Character
Description
Note
Examples
&
Not all protocols require hosts to support pings. For some protocols, the pings are Cisco-defined and are
only answered by another Cisco router.
After you enter the ping command in privileged mode, the system prompts you for a protocol keyword.The
default protocol is IP.
If you enter a host name or address on the same line as the ping command, the default action is taken as
appropriate for the protocol type of that name or address.
The optional data, df-bit, repeat, size, source, timeout, and validate keywords can be used to avoid
extended ping command output. You can use as many of these keywords as you need, and you can use
them in any order after the host-name or system-address arguments.
Although the precise dialog varies somewhat from protocol to protocol, all are similar to the ping session
using default values shown in the following output:
Router# ping
Protocol [ip]:
Target IP address: 192.168.7.27
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.7.27, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/2/4 ms
The table below describes the default ping fields shown in the display.
Table 39
Field
Description
Protocol [ip]:
Target IP address:
Related Commands
Field
Description
!!!!!
Command
Description
ping ipv6
ping vrf
ping srb
To test network connectivity for Source Route Bridging (SRB) networks, use the ping srb command in
privileged EXEC mode.
ping srb name
Syntax Description
Command Modes
Command History
Examples
name
Release
Modification
15.0(1)M
12.2(33)SRE
12.2(33)SXI
The following example shows how to ping the target host of IP address 192.0.2.1:
Router# ping srb 192.0.2.1
Related Commands
Command
Description
ping ip
ping vrf
To test a connection in the context of a specific VPN connection, use the ping vrf command in user EXEC
or privileged EXEC mode.
ping vrf vrf-name [tag] [connection] target-address [connection-options]
Syntax Description
vrf-name
tag
connection
target-address
connection-options
Command Default
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
12.1(12c)E, 12.2
Usage Guidelines
Release
Modification
12.2(33)SRA
12.2(33)SB
12.2(33)SXI
12.2(33)SCF
A VPN routing and forwarding (VRF) instance is used to identify a VPN. To check if a configured VRF is
working, you can use the ping vrf command.
When attempting to ping from a provider edge (PE) router to a customer edge (CE) router, or from a PE
router to PE router, the standard ping command will not usually work. The ping vrf command allows you
to ping the IP addresses of LAN interfaces on CE routers.
If you are on a PE router, be sure to indicate the specific VRF (VPN) name, as shown in the Examples
section.
If all required information is not provided at the command line, the system will enter the interactive dialog
(extended mode) for ping.
Examples
In the following example, the target host in the domain 209.165.201.1 is pinged (using IP/ICMP) in the
context of the CustomerA VPN connection.
Router# ping vrf CustomerA 209.165.201.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 209.165.201.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 176/264/576 ms
Pressing the Enter key before providing all of the required options will begin the interactive dialog for ping.
In the following example, the interactive dialog is started after the ip protocol is specified, but no address
is given:
Router# ping vrf CustomerB ip
Target IP address: 209.165.200.225
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: Record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
The following example shows the various options for IP in the ping vrf command:
Router# show parser dump exec | include ping vrf
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
<string>
ip <string>
ip (interactive)
ip <string>
ip <string> source <address>
ip <string> source <interface>
ip <string> repeat <1-2147483647>
ip <string> size Number
ip <string> df-bit
ip <string> validate
ip <string> data <0-65535>
ip <string> timeout <0-3600>
ip <string> verbose
ip <string> data <0-65535>
ip <string> timeout <0-3600>
tag
atm
ipv6
appletalk
decnet
clns
ipx
sna
srb
Related Commands
Command
Description
ping
Command
Description
ping ip
ping ipv6
ping sna
platform shell
To grant shell access and enter shell access grant configuration mode, use the platform shellcommand in
global configuration mode. To disable this function, use the no form of this command.
platform shell
no platform shell
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(33)XNC
Usage Guidelines
This command should be entered before using the request platform software system shell command.
Examples
Related Commands
Command
Description
power enable
To turn on power for the modules, use the power enablecommand in global configuration mode. To power
down a module, use the no form of this command.
power enable module slot
no power enable module slot
Syntax Description
module slot
Command Default
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.2(33)SRA
When you enter the no power enable module slot command to power down a module, the modules
configuration is not saved.
When you enter the no power enable module slot command to power down an empty slot, the
configuration is saved.
The slot argument designates the module number. Valid values for slotdepend on the chassis that is used.
For example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
This example shows how to turn on the power for a module that was previously powered down:
Router(config)#
power enable module 5
Router(config)#
Related Commands
Command
Description
show power
power redundancy-mode
To set the power-supply redundancy mode, use the power redundancy-mode command in global
configuration mode.
power redundancy-mode {combined | redundant}
Syntax Description
combined
redundant
Command Default
redundant
Command Modes
Global configuration
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This example shows how to set the power supplies to the no-redundancy mode:
Router(config)#
power redundancy-mode combined
Router(config)#
This example shows how to set the power supplies to the redundancy mode:
Router(config)#
power redundancy-mode redundant
Router(config)#
Related Commands
Command
Description
show power
printer
To configure a printer and assign a server tty line (or lines) to it, use the printer command in global
configuration mode. To disable printing on a tty line, use the no form of this command.
printer printer-name {line number | rotary number} [formfeed] [jobtimeout seconds] [newlineconvert] [jobtypes type]
no printer printer-name
Syntax Description
printer-name
Printer name.
line number
rotary number
formfeed
jobtimeout seconds
newline-convert
jobtypes type
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
15.0(1)M
This command enables you to configure a printer for operations and assign either a single tty line or a
group of tty lines to it. To make multiple printers available through the same printer name, specify the
number of a rotary group.
In addition to configuring the printer with the printer command, you must modify the file /etc/printcap on
your UNIX system to include the definition of the remote printer in the Cisco IOS software. Refer to the
Cisco IOS Configuration Fundamentals Configuration Guide for additional information.
Use the optional newline-convert keyword in UNIX environments that cannot handle single-character line
terminators. This converts newline characters to a carriage-return, linefeed sequence. Use the formfeed
keyword when using the line printer daemon (lpd) protocol to print and your system is unable to separate
individual output jobs with a form feed (page eject). You can enter the newline-convert and formfeed
keywords together and in any order.
Examples
The following example shows how to configure a printer named printer1 and to assign the output to tty line
4:
Router# configure terminal
Router(config)# printer printer1 line 4
Related Commands
Command
Description
clear line
private
To save user EXEC command changes between terminal sessions, use the private command in line
configuration mode. To restore the default condition, use the no form of this command.
private
no private
Syntax Description
Command Default
User-set configuration options are cleared with the exit EXEC command or when the interval set with the
exec-timeout line configuration command has passed.
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command ensures that the terminal parameters set by the user remain in effect between terminal
sessions. This behavior is desirable for terminals in private offices.
Examples
In the following example, line 15 (in this example, vty 1) is configured to keep all user-supplied settings at
system restarts:
Router(config)# line 15
Router(config-line)# private
Related Commands
Command
Description
exec-timeout
Command
Description
exit
Syntax Description
number
size seconds
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.0(26)S
12.3(4)T
12.2(25)S
Usage Guidelines
Use the process cpu statistics limit entry-percentage command to set the entry limit and size of CPU
utilization statistics.
Examples
The following example shows how to set an entry limit at 40 percent and a size of 300 seconds:
configure terminal
!
Related Commands
Command
Description
snmp-server host
Syntax Description
total
process
interrupt
rising percentage
interval seconds
falling fall-percentage
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.0(26)S
12.3(4)T
12.2(25)S
This command defines CPU usage thresholds that, when crossed, cause a CPU thresholding notification.
When this command is enabled, Cisco IOS software polls the system at the configured interval.
Notification occurs in two situations:
Examples
The following example shows how to set the total CPU utilization notification threshold at 80 percent for a
rising threshold notification and 20 percent for a falling threshold notification, with a 5-second polling
interval:
configure terminal
!
process cpu threshold type total rising 80 interval 5 falling 20 interval 5
end
Related Commands
Command
Description
snmp-server host
process-max-time
To configure the amount of time after which a process should voluntarily yield to another process, use the
process-max-timecommand in global configuration mode. To reset this value to the system default, use the
no form of this command.
process-max-time milliseconds
no process-max-time milliseconds
Syntax Description
milliseconds
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.1
12.2(33)SRA
Lowering the maximum time a process can run is useful in some circumstances to ensure equitable division
of CPU time among different tasks.
Only use this command if recommended to do so by the Cisco Technical Assistance Center (TAC).
Examples
The following example limits the duration that a process will run to 100 milliseconds:
Router(config)# process-max-time 100
prompt
To customiz e the CLI prompt, use the promptcommand in global configuration mode. To revert to the
default prompt, use the noform of this command.
prompt string
no prompt [string]
Syntax Description
string
Command Default
The default prompt is either Router or the name defined with the hostname global configuration command,
followed by an angle bracket (>) for user EXEC mode or a pound sign (#) for privileged EXEC mode.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.3
12.2(33)SRA
You can include customized variables when specifying the prompt. All prompt variables are preceded by a
percent sign (%). The table below lists the available prompt variables.
Table 40
Prompt Variable
Interpretation
%h
%n
Prompt Variable
Interpretation
%p
%s
Space.
%t
Tab.
%%
Issuing the prompt %h command has the same effect as issuing the no prompt command.
Examples
The following example changes the EXEC prompt to include the tty number, followed by the name and a
space:
Router(config)# prompt TTY%n@%h%s%p
The following are examples of user and privileged EXEC prompts that result from the previous command:
TTY17@Router1 > enable
TTY17@Router1 #
Related Commands
Command
Description
hostname
prompt config
To configure the systems prompt for configuration mode, use the prompt config command in global
configuration mode. To disable the configuration, use the no form of this command.
prompt config hostname-length number
no prompt [config]
Syntax Description
hostname-length
number
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
This example shows how to configure the systems prompt for configuration mode:
Router(config)#
prompt config hostname-length 4
Related Commands
Command
Description
prompt
pwd
To show the current setting of the cd command, use the pwd command in EXEC mode.
pwd
Syntax Description
Command Modes
User EXEC
Priviledged EXEC
Command History
Usage Guidelines
Release
Modification
11.0
12.2(33)SRA
Use the pwd command to show which directory or file system is specified as the default by the cd
command. For all EXEC commands that have an optional filesystemargument, the system uses the file
system specified by the cd command when you omit the optional filesystemargument.
For example, the dir command contains an optional filesystemargument and displays a list of files on a
particular file system. When you omit this filesystemargument, the system shows a list of the files on the
file system specified by the cd command.
Examples
The following example shows that the present working file system specified by the cd command is slot 0:
Router> pwd
slot0:/
The following example uses the cd command to change the present file system to slot 1 and then uses the
pwd command to display that present working file system:
Router> cd slot1:
Router> pwd
slot1:/
Related Commands
Command
Description
cd
dir
R through setup
R through setup
refuse-message
refuse-message
To define and enable a line-in-use message, use the refuse-message command in line configuration mode.
To disable the message, use the noform of this command.
refuse-message d message d
no refuse-message
Syntax Description
message
Message text.
Command Default
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter
one or more lines of text, terminating the message with the second occurrence of the delimiting character.
You cannot use the delimiting character within the text of the message.
When you define a message using this command, the Cisco IOS software performs the following steps:
1 Accepts the connection.
2 Prints the custom message.
3 Clears the connection.
Examples
In the following example, line 5 is configured with a line-in-use message, and the user is instructed to try
again later:
line 5
R through setup
refuse-message
R through setup
regexp optimize
regexp optimize
To optimize the compilation of a regular expression access list, use the regexp optimize command in
global configuration mode. To disable the configuration, use the no form of this command.
regexp optimize
no regexp optimize
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
The following example shows how to optimize the compilation of regular expression access list:
Router# configure terminal
Router(config)# regexp optimize
Related Commands
Command
Description
R through setup
reload
reload
To reload the operating system, use the reload command in privileged EXEC or diagnostic mode.
reload [/verify | /noverify] [[warm file] [line | in [hhh:mm | mmm [text]] | at hh:mm [day month]
[text]] | reason [reason-string] | cancel]
Syntax Description
/verify
/noverify
file
line
in hhh : mm | mmm
text
at hh : mm
day
R through setup
reload
Command Modes
Command History
month
reason reason-string
cancel
Release
Modification
10.0
12.2(14)SX
12.3(2)T
12.2(18)S
12.2(20)S
12.0(26)S
12.3(4)T
12.2(17d)SXB
12.3(11)T
12.2(28)SB
12.2(33)SRA
R through setup
reload
Usage Guidelines
Release
Modification
15.0(1)M
The reload command halts the system. If the system is set to restart on error, it reboots itself. Use the
reload command after configuration information is entered into a file and saved to the startup
configuration.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This restriction
prevents the system from using an image stored in the ROM monitor and taking the system out of the
remote users control.
If you modify your configuration file, the system prompts you to save the configuration. During a save
operation, the system prompts whether you want to proceed with the save if the CONFIG_FILE variable
points to a startup configuration file that no longer exists. If you respond yes in this situation, the system
enters setup mode upon reload.
When you schedule a reload to occur at a later time (using the in keyword), it must take place within 24
days.
The at keyword can be used only if the system clock has been set on the router (either through Network
Time Protocol [NTP], the hardware calendar, or manually). The time is relative to the configured time zone
on the router. To schedule reloads across several routers to occur simultaneously, synchronize the time on
each router with NTP.
When you specify the reload time using the at keyword, if you specify the month and day, the reload takes
place at the specified time and date. If you do not specify the month and day, the reload takes place at the
specified time on the current day (if the specified time is later than the current time), or on the next day (if
the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The
reload must take place within 24 days.
To display information about a scheduled reload, use the show reload command.
The /verify and /noverify Keywords
If the /verify keyword is specified, the integrity of the image will be verified before it is reloaded onto a
router. If verification fails, the image reload will not occur. Image verification is important because it
assures the user that the image is protected from accidental corruption, which can occur at any time during
transit, starting from the moment the files are generated by Cisco until they reach the user.
The /noverify keyword overrides any global automatic image verification that may be enabled via the file
verify auto command.
The warm Keyword
If you issue the reload command after you have configured the warm-reboot global configuration
command, a cold reboot will occur. Thus, if you want to reload your system, but do not want to override
the warm reboot functionality, you should specify the warm keyword with the reload command. The warm
reboot functionality allows a Cisco IOS image to reload without ROM monitor intervention. That is, readwrite data is saved in RAM during a cold startup and restored during a warm reboot. Warm rebooting
R through setup
reload
allows the router to reboot quicker than conventional rebooting (where control is transferred to ROM
monitor and back to the image) because nothing is copied from flash to RAM.
Examples
The following example shows how to immediately reload the software on the router:
Router# reload
The following example shows how to reload the software on the router in 10 minutes:
Router# reload in 10
Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)
Proceed with reload? [confirm]
The following example shows how to reload the software on the router at 1:00 p.m. on that day:
Router# reload at 13:00
Router# Reload scheduled for 13:00:00 PDT Fri Apr 21 1996 (in 1 hour and 2 minutes)
Proceed with reload? [confirm]
The following example shows how to reload the software on the router on April 21 at 2:00 a.m.:
Router# reload at 02:00 apr 21
Router# Reload scheduled for 02:00:00 PDT Sat Apr 21 1996 (in 38 hours and 9 minutes)
Proceed with reload? [confirm]
The following example shows how to perform a warm reboot at 4:00 a.m. on that day:
Router# reload warm at 04:00
The following example shows how to specify a reason for the reload:
Router# reload reason reloaded with updated version
The following example shows how to specify image verification via the /verify keyword before reloading
an image onto the router:
Router# reload /verify
Verifying file integrity of bootflash:c7200-kboot-mz.121-8a.E
%ERROR:Signature not found in file bootflash:c7200-kboot-mz.121-8a.E.
Signature not present. Proceed with verify? [confirm]
Verifying file disk0:c7200-jsmz ..........................................................................
............................................................Done!
Embedded Hash
MD5 :CFA258948C4ECE52085DCF428A426DCD
Computed Hash
MD5 :CFA258948C4ECE52085DCF428A426DCD
CCO Hash
MD5 :44A7B9BDDD9638128C35528466318183
Signature Verified
Proceed with reload? [confirm]n
Related Commands
Command
Description
R through setup
reload
Command
Description
show reload
warm-reboot
R through setup
remote command
remote command
To execute a Cisco 7600 series router command directly on the switch console or a specified module
without having to log into the Cisco 7600 series router first, use the remote command command in
privileged EXEC mode.
remote command {module num | standby-rp | switch} command
Syntax Description
module num
standby-rp
switch
command
Command to be executed.
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.2(33)SRA
The module num keyword and argument designate the module number. Valid values depend on the chassis
that is used. For example, if you have a 13-slot chassis, valid values are from 1 to 13. The module num
keyword and argument are supported on DFC-equipped modules and the standby supervisor engine only.
When you execute the remote command switchcommand, the prompt changes to Switch-sp#.
This command is supported on DFC-equipped modules and the supervisor engine only.
R through setup
remote command
This command does not support command completion, but you can use shortened forms of the command
(for example, entering sh for show).
Examples
This example shows how to execute the show calendar command from the standby route processor:
Router#
remote command standby-rp show calendar
Switch-sp#
09:52:50 UTC Mon Nov 12 2001
Router#
Related Commands
Command
Description
remote login
R through setup
remote login
remote login
To access the Cisco 7600 series router console or a specific module, use the remote login command in
privileged EXEC mode.
remote login {module num | standby-rp | switch}
Syntax Description
module num
standby-rp
switch
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.2(33)SRA
Usage Guidelines
Caution
When you enter the attach or remote login command to access another console from your switch, if you
enter global or interface configuration mode commands, the switch might reset.
The module num keyword and argument designate the module number. Valid values depend on the chassis
that is used. For example, if you have a 13-slot chassis, valid values are from 1 to 13. The module num
keyword and argument are supported on DFC-equipped modules and the standby supervisor engine only.
R through setup
remote login
When you execute the remote login module num command, the prompt changes to Router-dfcx# or
Switch-sp#, depending on the type of module to which you are connecting.
When you execute the remote login standby-rp command, the prompt changes to Router-sdby#.
When you execute the remote login switch command, the prompt changes to Switch-sp#.
The remote login module num command is identical to the attach command.
There are two ways to end the session:
Switch-sp# exit
[Connection to Switch closed by foreign host]
Router#
Switch-sp# ^C
Switch-sp# ^C
Switch-sp# ^C
Terminate remote login session? [confirm] y
[Connection to Switch closed by local host]
Router#
Examples
This example shows how to perform a remote login to the Cisco 7600 series router processor:
Router# remote login switch
Trying Switch ...
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
Switch-sp#
This example shows how to perform a remote login to the standby route processor:
Router# remote login standby-rp
Trying Switch ...
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
Router-sdby#
Related Commands
Command
Description
attach
R through setup
remote-span
remote-span
To configure a virtual local area network (VLAN) as a remote switched port analyzer (RSPAN) VLAN, use
the remote-span command in config-VLAN mode. To remove the RSPAN designation, use the no form of
this command.
remote-span
no remote-span
Syntax Description
Command Default
Command Modes
Config-VLAN mode
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
Examples
R through setup
remote-span
Related Commands
Connect
Description
R through setup
rename
rename
To rename a file in a Class C Flash file system, use the rename command in EXEC, privileged EXEC, or
diagnostic mode.
rename url1 url2
Syntax Description
Command Modes
url1
url2
Command History
Release
Modification
11.3 AA
12.2(33)SRA
Usage Guidelines
Examples
-rw-rw-rw-rw-rw-
0
0
0
0
165
Jan
Jan
Jan
Jan
Jan
21
21
21
21
21
1998
1998
1998
1998
1998
09:51:29
09:51:29
09:51:29
09:51:31
09:53:17
Karen.1
Karen.2
Karen.3
Karen.4
Karen.cur
R through setup
rename
0
0
0
243
0
-rw-rw-rw-rw-rw-
0
0
0
165
0
Jan
Jan
Jan
Jan
Apr
21
21
21
21
24
1998
1998
1998
1998
1998
09:51:29
09:51:29
09:51:31
09:53:17
09:49:19
Karen.2
Karen.3
Karen.4
Karen.cur
test
R through setup
request platform software package describe file
Syntax Description
URL
detail
verbose
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
This command can only be used to gather information on individual module and Cisco IOS-XE image files.
Using this command to collect information on any other file will generate output, but the generated output
is useless.
The output of this command can be used for the following functions:
To confirm the individual module files that are part of a Cisco IOS-XE image.
To confirm whether or not a file is bootable.
To confirm the contexts in which a file must be reloaded or booted.
To confirm whether or not a file is corrupted.
To confirm file and header sizes, build dates, and various other general information.
R through setup
request platform software package describe file
Examples
In the following example, this command is entered to gather information about an individual SIP Base
module file on the bootflash: file system.
Router# request platform software package describe file bootflash:asr1000rp1sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Package: asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 36954316
Timestamp: 2007-12-05 15:36:27 UTC
Canonical path: /bootflash/asr1000rp1sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Raw disk-file SHA1sum:
3ee37cdbe276316968866b16df7d8a5733a1502e
Computed SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Contained SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Hashes match. Package is valid.
Header size:
Package type:
Package flags:
Header version:
204 bytes
10000
0
0
In the following example, this command is used to gather information about a Cisco IOS-XE image on the
bootflash: file system.
Router# request platform software package describe file bootflash:ASR1000rp1advipservicesk9.01.00.00.12-33.XN.bin
Package: ASR1000rp1-advipservicesk9.01.00.00.12-33.XN.bin
Size: 218783948
Timestamp: 2007-12-04 17:14:09 UTC
Canonical path: /bootflash/ASR1000rp1-advipservicesk9.01.00.00.12-33.XN.bin
Raw disk-file SHA1sum:
d2999fc7e27e01344903a42ffacd62c156eba4cc
Computed SHA1sum:
5f8cda8518d01d8282d80ecd34f7715783f4a813
Contained SHA1sum:
5f8cda8518d01d8282d80ecd34f7715783f4a813
Hashes match. Package is valid.
Header size:
Package type:
Package flags:
Header version:
204 bytes
30000
0
0
R through setup
request platform software package describe file
Build: v122_33_xn_asr_rls0_throttle_20071204_051318
Package is bootable from media and tftp.
Package contents:
Package: asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 52072652
Timestamp: 2007-12-04 13:33:13 UTC
Raw disk-file SHA1sum:
f1aad6d687256aa327a4efa84deab949fbed12b8
Computed SHA1sum:
15502fd1b8f9ffd4af4014ad4d8026c837929fe6
Contained SHA1sum:
15502fd1b8f9ffd4af4014ad4d8026c837929fe6
Hashes match. Package is valid.
Header size:
Package type:
Package flags:
Header version:
204 bytes
20000
0
0
204 bytes
30004
0
0
R through setup
request platform software package describe file
204 bytes
30001
0
0
204 bytes
30002
0
0
R through setup
request platform software package describe file
Header size:
Package type:
Package flags:
Header version:
204 bytes
30003
0
0
204 bytes
10000
0
0
204 bytes
10001
0
0
R through setup
request platform software package describe file
Platform: ASR1000
User: mcpre
PackageName: sipspa
Build: v122_33_xn_asr_rls0_throttle_20071204_051318
Package is not bootable.
Related Commands
Command
Description
R through setup
request platform software package expand file
Syntax Description
source-URL
to destination-URL
force
verbose
wipe
Command Default
Command Modes
Command History
Release
Modification
R through setup
request platform software package expand file
Usage Guidelines
This command only extracts individual module files and a provisioning file from the Cisco IOS-XE image.
Additional configuration is needed to configure the router to boot using the provisioning files and run using
the individual modules.
When this command is used, copies of each module and the provisioning file within the Cisco IOS-XE
image are copied and placed on the destination directory. The Cisco IOS-XE image file is unchanged after
the operation is complete.
If the todestination-URL option is not entered, the Cisco IOS-XE image contents will be extracted onto the
same directory where the Cisco IOS-XE image is currently stored.
If this command is used to extract individual module files onto a directory that already contains individual
module files, the files that would have been extracted onto the same directory are instead extracted to an
automatically created directory on the destination device.
Examples
The following example shows how to extract the individual modules and the provisioning file from a Cisco
IOS-XE image that has already been placed in the directory where the user wants to store the individual
modules and the provisioning file.
Output of the directory before and after the extraction is given to confirm the files were extracted.
Router# dir bootflash:
Directory of bootflash:/
11 drwx
16384
Dec 4 2007 11:26:07 +00:00 lost+found
14401 drwx
4096
Dec 4 2007 11:27:41 +00:00 .installer
12 -rw218783948
Dec 4 2007 12:12:16 +00:00 ASR1000rp1advipservicesk9.01.00.00.12-33.XN.bin
Router# request platform software package expand file bootflash:ASR1000rp1advipservicesk9.01.00.00.12-33.XN.bin
Verifying parameters
Validating package type
Copying package files
Router# dir bootflash:
Directory of bootflash:/
11 drwx
16384
Dec 4 2007 11:26:07 +00:00 lost+found
14401 drwx
4096
Dec 4 2007 11:27:41 +00:00 .installer
12 -rw218783948
Dec 4 2007 12:12:16 +00:00 ASR1000rp1advipservicesk9.01.00.00.12-33.XN.bin
28803 -rw52072652
Dec 4 2007 12:14:17 +00:00
asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28804 -rw21844172
Dec 4 2007 12:14:17 +00:00 asr1000rp1-rpaccessk9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28805 -rw21520588
Dec 4 2007 12:14:18 +00:00 asr1000rp1rpbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28806 -rw24965324
Dec 4 2007 12:14:19 +00:00 asr1000rp1rpcontrol.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28807 -rw48515276
Dec 4 2007 12:14:20 +00:00
asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28808 -rw36954316
Dec 4 2007 12:14:21 +00:00
asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28809 -rw19933388
Dec 4 2007 12:14:22 +00:00
asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
28802 -rw7145
Dec 4 2007 12:14:22 +00:00 packages.conf
928833536 bytes total (483700736 bytes free)
The following example shows how to extract the individual modules and the provisioning file from a Cisco
IOS-XE image that has already been placed on the router in a directory that will not store the individual
modules and the provisioning file. In this particular example, the contents of a Cisco IOS-XE image stored
in usb0: are extracted into bootflash:.
Output of the bootflash: directory before and after the extraction is given to confirm the files were
extracted.
Router# dir usb0:
R through setup
request platform software package expand file
Directory of usb0:/
1120 -rwx
213225676
Dec 4 2007 10:50:36 +00:00 asr1000rp1advipservicesk9.v122_33_xn_asr_rls0_throttle.bin
Router# dir bootflash:
Directory of bootflash:/
11 drwx
16384
Dec 4 2007 12:32:46 +00:00 lost+found
86401 drwx
4096
Dec 4 2007 14:06:24 +00:00 .ssh
14401 drwx
4096
Dec 4 2007 14:06:36 +00:00 .rollback_timer
43201 drwx
4096
Dec 4 2007 12:34:45 +00:00 .installer
Router# request platform software package expand file usb0:asr1000rp1advipservicesk9.v122_33_xn_asr_rls0_throttle.bin to bootflash:
Verifying parameters
Validating package type
Copying package files
Router# dir bootflash:
Directory of bootflash:/
11 drwx
16384
Dec 4 2007 12:32:46 +00:00 lost+found
86401 drwx
4096
Dec 4 2007 14:06:24 +00:00 .ssh
14401 drwx
4096
Dec 4 2007 14:06:36 +00:00 .rollback_timer
43201 drwx
4096
Dec 4 2007 12:34:45 +00:00 .installer
28803 -rw51986636
Dec 4 2007 16:40:38 +00:00 asr1000rp1espbase.v122_33_xn_asr_rls0_throttle.pkg
28804 -rw21838028
Dec 4 2007 16:40:39 +00:00
asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg
28805 -rw21508300
Dec 4 2007 16:40:39 +00:00
asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg
28806 -rw24963276
Dec 4 2007 16:40:40 +00:00
asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg
28807 -rw48419020
Dec 4 2007 16:40:41 +00:00
asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg
28808 -rw36946124
Dec 4 2007 16:40:43 +00:00
asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg
28809 -rw14670028
Dec 4 2007 16:40:43 +00:00
asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg
28802 -rw6563
Dec 4 2007 16:40:43 +00:00 packages.conf
928862208 bytes total (708186112 bytes free)
Related Commands
Command
Description
R through setup
request platform software package install commit
Syntax Description
rp rp-slot-number
commit
verbose
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
This command is entered after the request platform software package install rp rp-slot-number file
command is used with the auto-rollback minutes option to begin an individual sub-package or a
consolidated package upgrade. When the auto-rollback minutes option is used in this context, a rollback
timer that cancels the upgrade after the number of specified minutescancels the upgrade if the request
platform software package install rp rp-slot-number commit command is not entered to commit the
upgrade.
If this command is not entered after the request platform software package install rp rp-slot-number file
command is used with the auto-rollback minutes option to upgrade an individual sub-package or a
consolidated package and the rollback timer expires, the upgrade does not complete and the router
continues running the previous sub-package or consolidated package.
R through setup
request platform software package install commit
Examples
Related Commands
Command
Description
R through setup
request platform software package install file
Syntax Description
rp rp-slot-number
file file-URL
auto-rollback minutes
provisioning-file provisioning-file-URL
slot slot-number
bay bay-number
force
on-reboot
verbose
Command Default
Command Modes
R through setup
request platform software package install file
Command History
Usage Guidelines
Release
Modification
Examples
Managing and Configuring a consolidated package using the request platform package command
In the following example, the request platform software package install command is used to upgrade a
consolidated package running on RP 0. The force option, which forces the upgrade past any prompt (such
as already having the same consolidated package installed), is used in this example.
Router# request platform software package install rp 0 file bootflash:ASR1000rp1advipservicesk9.01.00.00.12-33.XN.bin force
--- Starting installation state synchronization --Finished installation state synchronization
--- Starting file path checking --Finished file path checking
--- Starting image file verification --Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Extracting super package content
Verifying parameters
Validating package type
Copying package files
Checking and verifying packages contained in super package
Creating candidate provisioning file
WARNING:
WARNING: Candidate software will be installed upon reboot
WARNING:
Finished image file verification
--- Starting candidate package set construction --Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Checking command output
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing --Determining whether candidate package set is compatible
R through setup
request platform software package install file
WARNING:
WARNING: Candidate software combination not found in compatibility database
WARNING:
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility with running software
Checking IPC compatibility with running software ... skipped
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Finished compatibility testing
--- Starting commit of software changes --Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# reload
Note
R through setup
request platform software package install file
R through setup
request platform software package install file
R through setup
request platform software package install file
Restarting CC1
Applying interim IPC and database definitions
*Oct 9 09:54:55.365: %MCP_OIR-6-OFFLINECARD: Card (cc) offline in slot 1
*Oct 9 09:54:55.365: %MCP_OIR-6-REMSPA: SPA removed from subslot 1/1,
interfaces disabled
*Oct 9 09:54:55.365: %MCP_OIR-6-REMSPA: SPA removed from subslot 1/2,
interfaces disabled
Notifying running software of updates
Unblocking peer synchronization of operating information
Unmounting old packages
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router#
Note that the new RPIOS sub-package will become active only after a reboot. Reboot the router to finish
this procedure.
R through setup
request platform software package install file
R through setup
request platform software package install file
Related Commands
Command
Description
R through setup
request platform software package install rollback
Syntax Description
rp rp-slot-number
as-booted
provisioning-file provisioning-file-URL
force
on-reboot
verbose
Command Default
Command Modes
Command History
Release
Modification
R through setup
request platform software package install rollback
Usage Guidelines
This command rolls back a configuration that has an active rollback timer. Active rollback timers are used
when the auto-rollback option is entered when software is being upgraded using the request platform
software package install filecommand.
Examples
In the following example, an upgrade that was using a rollback timer is rolled back to the previous
configuration instead of upgraded:
request platform software package install rp 0 rollback
Related Commands
Command
Description
R through setup
request platform software package install snapshot
Syntax Description
rp rp-slot-number
snapshot to URL
as snapshot-provisioning-filename
wipe
force
verbose
Command Default
Command Modes
R through setup
request platform software package install snapshot
Command History
Usage Guidelines
Release
Modification
This command is used to create a directory at the destination device and extract the individual subpackages in a consolidated package to that directory.
The request platform software package expand command is the only other command that can be used to
extract individual sub-packages from a consolidated package.
Examples
In the following example, a snapshot directory named snapdir1_snap is created in the bootflash: file
system, and the individual sub-package files from the consolidated package are extracted into the snapshot
directory.
The second portion of the example first sets up the router to reboot using the files in the snapshot directory
(deletes all previous boot system commands, configures the configuration register, then enters a boot
system command to boot using the extracted provisioning file), saves the new configuration, then reboots
so the router will boot using the extracted provisioning file, which allows the router to run using the
extracted individual sub-package files.
Router(diag)# request platform software package install rp 0 snapshot to
bootflash:snapdir1_snap
--- Starting active image file snapshot --- Validating snapshot parameters Creating
destination directory Copying files to destination media
Copied provisioning file as packages.conf
Copying package file asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1rpcontrol.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1-rpiosadvipservicesk9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1-rpaccessk9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Copying package file asr1000rp1espbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Moving files into final location Finished active image file snapshot
Router(config)# no boot system
Router(config)# config-register 0x1
Router(config)# boot system harddisk:snapdir1_snap/packages.conf
Router(config)# exit
*May 11 01:31:04.815: %SYS-5-CONFIG_I: Configured from console by con
Router# write mem
Building configuration...
[OK]
Router# reload
Related Commands
Command
Description
R through setup
request platform software process release
Syntax Description
slot
all
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
This command is used to restart processes in the holddown state. If a process is in the holddown state, a
console message is generated to notify the user that the process is helddown.
Before placing any process in the holddown state, the Process Manager makes up to 5 attempts over 120
seconds to enable the process. These attempts to enable the process also happen automatically at startup. If
R through setup
request platform software process release
the Process Manager is unable to enable the process after these attempts, the process will then be placed in
the holddown state.
When this command is entered, it only attempts to restart processes currently in the holddown state. Active
processes will not be affected by entering this command.
Examples
In the following example, this command is entered to restart any process currently on RP 0 in the holddown
state:
request platform software process release r0 all
R through setup
request platform software system shell
Syntax Description
Command Modes
Command History
Usage Guidelines
rp
esp
sip
Release
Modification
12.2(33)XNC
The platform shell command needs to be entered before before using the request platform software system
shell command. Providing shell access would not be necessary. However, there might be some cases where
the command may not be available, or the IOS process hangs, or IOS console may not be available. In such
cases, you can login to the shell and see the status of the system.
The shell should be accessed under Cisco supervision, and no support is provided if accessed without
supervision. The following message is displayed , before the shell access is granted:
"Activity within this shell can jeopardize the functioning of the system.
Use this functionality only under supervision of Cisco Support."
Examples
R through setup
request platform software system shell
Related Commands
Command
Description
platform shell
R through setup
request platform software shell session output format
Syntax Description
format
Command Default
All show command output is seen in plaintext (the text format)by default.
Command Modes
Command History
Usage Guidelines
Release
Modification
Entering this command can only change the output of some show commands that are available in both
privileged EXEC and diagnostic mode. At the current time, most of these commands are show platform
software and show platform hardware commands.
Only a small subset of commands currently produce output using the html option.
Examples
In the following example, the request platform software shell session output format command is used to
change the show output format from text to raw. The output of the show platform hardware slot r0
alarms visual command is shown both before and after the request platform software shell session
output format command was entered to illustrate the change in output format.
Router# show platform hardware slot r0 alarms visual
R through setup
request platform software shell session output format
In the following example, the request platform software shell session output format command is used to
change the show output format from text to xml. The output of the show platform hardware slot r0
alarms visual command is shown both before and after the request platform software shell session
output format command was entered to illustrate the change in output format.
Router# show platform hardware slot r0 alarms visual
Current Visual Alarm States
Critical: On
Major
: On
Minor
: Off
Router# request platform software shell session output format xml
Router# show platform hardware slot r0 alarms visual
<?xml version="1.0"?>
<iossr-response action="3">
<cmd-response>
<alarms_msg><tdl_cman_alarms_data><critical><TDL_TRUE/></critical>
<major><TDL_TRUE/></major>
<minor><TDL_FALSE/></minor>
</tdl_cman_alarms_data>
</alarms_msg>
<ui_req_msg><ui_req><request_id>4</request_id>
<client><location><fru><BINOS_FRU_RP/></fru>
<slotnum>0</slotnum>
<baynum>0</baynum>
</location>
<client_type><UICLIENT_INVALID/></client_type>
<term_type><UITT_INVALID/></term_type>
<ttynum>0</ttynum>
<tty_name></tty_name>
<user_name></user_name>
</client>
<command></command>
<request_name></request_name>
<flags></flags>
R through setup
request platform software shell session output format
</ui_req>
</ui_req_msg>
</cmd-response>
</iossr-response>
R through setup
request platform software snapshot
Syntax Description
snapshot
slot
cancel
create
Creates a snapshot
delete
Deletes a snapshot
restore
Restores a snapshot
name
Command Default
Command Modes
R through setup
request platform software snapshot
Command History
Release
Modification
Usage Guidelines
Use the request platform software snapshot command to create a snapshot of the bootflash, including the
NVRAM partitions and the ROMMON memory, on the harddisk. This command can also be used to
restore a snapshot.
Examples
This example shows how to create a snapshot named "stan" on the processor in the RO slot.
router#request platform software snapshot R0 create stan
Related Commands
Command
Description
R through setup
request platform software vty attach
Syntax Description
permanent
Command Default
Command Modes
Diagnostic (diag)
Command History
Usage Guidelines
Release
Modification
If persistent Telnet or persistent SSH is configured to make users wait for an IOS vty line before allowing
them to access the IOS CLI, this command can be used to attach to an IOS vty line and place the user in
EXEC mode. Exiting EXEC mode returns the user to diagnostic mode unless the permanent keyword is
entered. When the permanent keyword is entered, exiting EXEC mode exits the router.
The vty lines must be configured to allow local login for this command to work. The vty lines must also be
configured to accept the type of transport traffic (SSH or Telnet) being used to connect to the router for the
session in which the request platform software vty attach command is entered.
Examples
In the following example, this command is used to leave diagnostic mode and enter privileged EXEC
mode:
Router(diag)#
request platform software vty attach
Router#
In the following example, this command is used to leave diagnostic mode and enter privileged EXEC
mode. The user then re-enters diagnostic mode by exiting privileged EXEC mode:
Router(diag)# request platform software vty attach
Router# exit
Router(diag)#
R through setup
request platform software vty attach
In the following example, this command is used with the permanent option to leave diagnostic mode and
enter privileged EXEC mode. The user then exits the router by exiting privileged EXEC mode:
Router(diag)# request platform software vty attach permanent
Router# exit
Connection to Router closed.
R through setup
revision
revision
To set the revision number for the Multiple Spanning Tree (802.1s) (MST) configuration, use the revision
command in MST configuration submode. To return to the default settings, use the no form of this
command.
revision version
no revision
Syntax Description
version
Command Default
version is 0
Command Modes
Command History
Usage Guidelines
Caution
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Two Cisco 7600 series routers that have the same configuration but different revision numbers are
considered to be part of two different regions.
Be careful when using the revision command to set the revision number of the MST configuration because
a mistake can put the switch in a different region.
R through setup
revision
Examples
This example shows how to set the revision number of the MST configuration:
Router(config-mst)# revision 5
Router(config-mst)#
Related Commands
Command
Description
instance
show
show spanning-tree
R through setup
rmdir
rmdir
To remove an existing directory in a Class C Flash file system, use the rmdir command in EXEC,
privileged EXEC, or diagnostic mode.
rmdir directory
Syntax Description
Command Modes
directory
Directory to delete.
User EXEC
Privileged EXEC
Diagnostic
Command History
Usage Guidelines
Caution
Examples
Release
Modification
11.3 AA
12.2(33)SRA
You can use the rmdir command to remove a directory that another user is currently accessing in read-only
mode, for example if it is that users default working directory. If you use the rmdir command to remove
such a directory and a user whose current directory is set to the deleted directory then uses the pwd
command to display the current working directory, the following error message is displayed: Cannot
determine current directory.
newdir
R through setup
rmdir
Related Commands
Command
Description
dir
mkdir
R through setup
rommon-pref
rommon-pref
To select a ReadOnly or Upgrade ROMmon image to be booted on the next reload of a Cisco 7200 VXR
router or Cisco 7301 router when you are in ROMmon, use the rommon-prefcommand in ROM monitor
mode.
rommon-pref [readonly | upgrade]
Syntax Description
readonly
upgrade
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.0(28)S
12.3(8)T
12.3(9)
You might select the ReadOnly ROMmon image to be booted on the next reload because the Upgrade
image has features or side effects you do not like.
When you are in ROMmon, there is no descriptive output to inform you whether the ReadOnly ROMmon
image was reloaded. To confirm the reload, use the showmon command after entering the rommon-pref
readonly command.
R through setup
rommon-pref
Use this command when you are in ROMmon mode. Use the upgrade rom-monitor preferencecommand
when you are in Cisco IOS.
Examples
The following example, applicable to both the Cisco 7200 VXR and Cisco 7301 routers, shows how to
select the ReadOnly ROMmon image to be booted on the next reload of the router when you are already in
ROMmon mode:
rommon 2 > rommon-pref readonly
Related Commands
Command
Description
showmon
R through setup
route-converge-interval
route-converge-interval
To configure the time interval after which the old FIB entries are purged, use the route-convergeintervalcommand in main CPU submode. To return to the default settings, use the no form of this
command.
route-converge-interval seconds
no route-converge-interval
Syntax Description
seconds
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(17b)SXA
12.2(18)SXD
12.2(33)SRA
This command is not supported in Cisco 7600 series routers that are configured with a Supervisor Engine 2.
The time interval for route-converge delay is needed to simulate the route-converge time when routing
protocols restart on switchover.
R through setup
route-converge-interval
Examples
This example shows how to set the time interval for the route-converge delay:
Router(config)# redundancy
Router(config-red)# main-cpu
Router(config-red-main)# route-converge-interval 90
Router(config-red-main)#
This example shows how to return to the default time interval for the route-converge delay:
Router(config)# redundancy
Router(config-red)# main-cpu
Router(config-red-main)# no route-converge-interval
Router(config-red-main)#
Related Commands
Command
Description
redundancy
R through setup
rsh
rsh
To execute a command remotely on a remote shell protocol (rsh) host, use the rshcommand in
privilegedEXEC mode.
rsh {ip-address | host} [/user username] remote-command
Syntax Description
Command Default
Note
Command Modes
Command History
ip-address
host
/user username
remote-command
If you do not specify the /user username keyword and argument, the Cisco IOS software sends a default
remote username. As the default value of the remote username, the software sends the username associated
with the current tty process, if that name is valid. For example, if the user is connected to the router through
Telnet and the user was authenticated through the usernamecommand, then the software sends that
username as the remote username. If the tty username is invalid, the software uses the host name as the
both the remote and local usernames.
For Cisco, tty lines are commonly used for access services. The concept of tty originated with UNIX. For
UNIX systems, each physical device is represented in the file system. Terminals are sometimes called tty
devices (tty stands for teletype, the original UNIX terminal).
Privileged EXEC
Release
Modification
10.0
12.2(33)SRA
R through setup
rsh
Usage Guidelines
Use the rsh command to execute commands remotely. The host on which you remotely execute the
command must support the rsh protocol, and the .rhosts files on the rsh host must include an entry that
permits you to remotely execute commands on that host.
For security reasons, the software does not default to a remote login if no command is specified, as does
UNIX. Instead, the router provides Telnet and connect services that you can use rather than rsh.
Examples
The following command specifies that the user named sharon attempts to remotely execute the UNIX ls
command with the -a argument on the remote host named mysys.cisco.com. The command output resulting
from the remote execution follows the command example:
Router1# rsh mysys.cisco.com /user sharon ls -a
.
.
.
.alias
.cshrc
.emacs
.exrc
.history
.login
.mailrc
.newsrc
.oldnewsrc
.rhosts
.twmrc
.xsession
jazz
R through setup
scheduler allocate
scheduler allocate
To guarantee CPU time for processes, use the scheduler allocatecommand in global configuration mode.
To restore the default, use the no form of this command.
scheduler allocate interrupt-time process-time
no scheduler allocate
Syntax Description
interrupt-time
process-time
Command Default
Command Modes
Global configuration
Command History
Release
Modification
11.2
12.2(14)SX
12.2(17a)SX
12.2(17d)SXB
R through setup
scheduler allocate
Usage Guidelines
Caution
Release
Modification
12.2(33)SRA
This command applies to the Catalyst 6500 series switches, Cisco 7200 series, Cisco 7500 series, and Cisco
7600 series routers.
We recommend that you do not change the default settings. Changing settings associated with CPU
processes can negatively impact system performance.
Entering the scheduler allocate command without arguments is the same as entering the no scheduler
allocate or the default scheduler allocate command.
Examples
The following example makes 20 percent of the CPU available for process tasks:
Router(config)# scheduler allocate 2000 500
Related Commands
Command
Description
scheduler interval
R through setup
scheduler heapcheck poll
Syntax Description
Command Default
The scheduler heapcheck pollcommand is disabled by default. If no keywords are specified, a sanity
check is performed on all the memory blocks and memory pools.
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
The following example shows how to validate the memory check and edisms poll routine:
Router# configure terminal
Router(config)# scheduler heapcheck poll
Related Commands
Command
Description
R through setup
scheduler heapcheck process
Syntax Description
memory
fast
io
multibus
pci
processor
checktype
all
data
magic
mlite-data
pointer
refcount
R through setup
scheduler heapcheck process
lite-chunks
Command Default
This command is disabled by default. If no keywords are specified, a sanity check will be performed on all
the memory blocks and memory pools.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(15)T
12.3(11)T
12.4(20)T
When configuring this command, you can choose none or all memory block keywords (fast, io, multibus,
pci, processor, and checktype).
Enabling this command has a significant impact on router performance.
Examples
The following example shows how to sanity check for corruption in the I/O memory block when a process
switch occurs. In this example, the values of only the block magic, red zone, and size will be checked.
scheduler heapcheck process memory io checktype magic
The following example shows how to sanity check for corruption in the processor memory block when a
process switch occurs. In this example, the values of only the next and previous pointers will be checked.
scheduler heapcheck process memory processor checktype pointer
Related Commands
Command
Description
memory lite
memory sanity
R through setup
scheduler interrupt mask profile
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
12.4(2)T
Usage Guidelines
This command enables the collection of details regarding the total amount of time a process has masked
interrupts since the interrupt mask profiler was enabled.
Examples
Related Commands
Command
Description
R through setup
scheduler interrupt mask profile
Command
Description
R through setup
scheduler interrupt mask size
Syntax Description
buffersize
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
12.4(2)T
The following example shows how to configure 100 entries the maximum number of entries that can exist
in the interrupt mask buffer:
Router(config)# scheduler interrupt mask size 100
Related Commands
Command
Description
R through setup
scheduler interrupt mask size
Command
Description
R through setup
scheduler interrupt mask time
Syntax Description
threshold-time
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
12.4(2)T
The following shows how to configure 100 microseconds as the maximum time a process can run with
interrupts masked before another entry is created in the interrupt mask buffer:
Router(config)# scheduler interrupt mask time 100
Related Commands
Command
Description
R through setup
scheduler interrupt mask time
Command
Description
R through setup
scheduler interval
scheduler interval
To control the maximum amount of time that can elapse without running system processes, use the
scheduler interval command in global configuration mode. To restore the default, use the noform of this
command.
scheduler interval milliseconds
no scheduler interval
Syntax Description
milliseconds
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
The normal operation of the network server allows the switching operations to use as much of the central
processor as is required. If the network is running unusually heavy loads that do not allow the processor the
time to handle the routing protocols, give priority to the system process scheduler. High-priority operations
are allowed to use as much of the CPU as needed.
Changing settings associated with CPU processes can negatively impact system performance.
On the Cisco 7200 series and Cisco 7500 series, use the scheduler allocate global configuration command
instead of the scheduler interval command.
Examples
The following example changes the low-priority process schedule to an interval of 750 milliseconds:
Router(config)# scheduler interval 750
R through setup
scheduler interval
Related Commands
Command
Description
scheduler allocate
R through setup
scheduler isr-watchdog
scheduler isr-watchdog
To detect if an Interrupt Service Routine (ISR) is suspended or stalled and to schedule and manage a
watchdog timeout on an ISR, use the scheduler isr-watchdogcommand in global configuration mode. To
disable the configuration, use the no form of this command.
scheduler isr-watchdog
no scheduler isr-watchdog
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
The timer ISR checks the current context to avoid holding processes accountable for CPU time spent
servicing interrupts during the process time slice, and vice versa for interrupt-level code accountability.
However, at each timer tick, the timer ISR applies the full 4 milliseconds of CPU time to the current
context. As a result, depending on when the timer tick occurs in relation to a context switch, you might see
inaccuracies in CPU utilization accounting compared with the actual computation time because some or all
of the tick is being applied to the wrong context.
Examples
The following example shows how to detect if an ISR is suspended or stalled and to manage a watchdog
timeout on an ISR:
Router> enable
Router# configure terminal
Router(config)# scheduler isr-watchdog
R through setup
scheduler isr-watchdog
Related Commands
Command
Description
scheduler max-sched-time
R through setup
scheduler max-sched-time
scheduler max-sched-time
To configure or change the maximum time, in milliseconds that a scheduler can run without flagging an
error or overload of the CPU, use the scheduler max-sched-timecommand in global configuration mode.
To disable this configuration, use the no form of this command.
scheduler max-sched-time milliseconds
no scheduler max-sched-time
Syntax Description
milliseconds
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
The default behavior of the scheduler max-sched-time command is to stop the process only if it is fatal. A
task is defined as fatal if the task gets another watchdog within 12 hours of being assigned the first
watchdog, and a handler has been registered.
Examples
The following example shows how to configure the maximum time in milliseconds (to 1000 ms in this
example) that a scheduler can run without flagging an error:
Router> enable
Router# configure terminal
Router(config)# scheduler max-sched-time 1000
R through setup
scheduler max-sched-time
Related Commands
Command
Description
scheduler isr-watchdog
R through setup
scheduler process-watchdog
scheduler process-watchdog
To configure the default action of a watchdog timeout for a process using a scheduler, use the scheduler
process-watchdogcommand in global configuration mode. To disable the configuration, use the no form of
this command.
scheduler process-watchdog {hang | normal | reload | terminate}
no scheduler process-watchdog
Syntax Description
hang
normal
reload
terminate
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
The watchdog timer sets the interval after which the scheduler assumes a process has been suspended or
stalled and needs to be stopped.
Examples
The following example shows how to configure the default action of a watchdog timeout for a process
using a scheduler:
Router> enable
Router# configure terminal
Router(config)# scheduler process-watchdog normal
R through setup
scheduler process-watchdog
Related Commands
Command
Description
scheduler max-sched-time
R through setup
scheduler timercheck process
Syntax Description
pid
Command Default
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
Specify the show processes timercheck command after configuring the schedule timercheck process
command to display the details of the configuration.
Examples
The following example shows how to configure process-level timer validation on a scheduler with a PID
value of 5:
Router> enable
Router# configure terminal
Router(config)# scheduler timercheck process 5
Router# show processes timer
System timer check not configured.
Process timer check configuration follows.
PID
Configuration
Name
1
On every context switch. Chunk Manager
R through setup
scheduler timercheck process
Related Commands
Command
Description
R through setup
scheduler timercheck system context
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
The following example shows how to configure system level validation on context switches on a scheduler:
Router> enable
Router# configure terminal
Router(config)# scheduler timercheck system context
Related Commands
Command
Description
R through setup
send
send
To send messages to one or all terminal lines, use the sendcommand in user or privileged EXEC mode.
send {line-number | * | aux number | console number | log number [msg-ext] | tty number | vty
number | xsm [client client-id] message text}
Syntax Description
line-number
aux number
console number
log number
msg-text
client client-id
message text
tty number
vty number
xsm client-id
Command Default
Command Modes
Command History
Release
Modification
11.2
R through setup
send
Usage Guidelines
Caution
Examples
Release
Modification
12.2(33)SRA
12.2(33)SXI
15.0(1)M
After entering the send command, the system prompts for the message to be sent, which can be up to 500
characters long. Press Ctrl-Z to end the message. Press Ctrl-Cto abort this command.
Be aware that in some circumstances text sent using the send command may be interpreted as an
executable command by the receiving device. For example, if the receiving device is UNIX workstation,
and the receiving device is in a state (shell) where commands can be executed, the incoming text, if it is a
properly formatted UNIX command, will be accepted by the workstation as a command. For this reason,
you should limit your exposure to potential messages from terminal servers or other Cisco IOS-based
devices when running an interactive shell.
Related Commands
Command
Description
reload
R through setup
service compress-config
service compress-config
To compress startup configuration files, use the service compress-config command in global configuration
mode. To disable compression, use the no form of this command.
service compress-config
no service compress-config
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
After you configure the service compress-config command, the router will compress configuration files
every time you save a configuration to the startup configuration. For example, when you enter the copy
system:running-config nvram:startup-config command, the running configuration will be compressed
before storage in NVRAM.
If the file compression succeeds, the following message is displayed:
Compressing configuration from configuration-size
to compressed-size
[OK]
If the boot ROMs do not recognize a compressed configuration, the following message is displayed:
Boot ROMs do not support NVRAM compression Config NOT written to NVRAM
One way to determine whether a configuration file will be compressed enough to fit into NVRAM is to use
a text editor to enter the configuration, then use the UNIX compress command to check the compressed
size. To get a closer approximation of the compression ratio, use the UNIX compress -b12command.
R through setup
service compress-config
Once the configuration file has been compressed, the router functions normally. At boot time, the system
recognizes that the configuration file is compressed, uncompresses it, and proceeds normally. A partition
nvram:startup-config command uncompresses the configuration before displaying it.
To disable compression of the configuration file, enter configuration mode and specify the no service
compress-config command. Then, exit global configuration mode and enter the copy system:runningconfig nvram:startup-config command. The router displays an OK message if it is able to write the
uncompressed configuration to NVRAM. Otherwise, the router displays an error message indicating that
the configuration is too large to store. If the configuration file is larger than the physical NVRAM, the
following message is displayed:
##Configuration too large to fit uncompressed in NVRAM Truncate configuration? [confirm]
When the file is truncated, commands at the end of the file are erased. Therefore, you will lose part of your
configuration. To truncate and save the configuration, type Y. To not truncate and not save the
configuration, type N.
Examples
Related Commands
Command
Description
partition nvram:startup-config
R through setup
service config
service config
To enable autoloading of configuration files from a network server, use the service config command in
global configuration mode. To restore the default, use the no form of this command.
service config
no service config
Syntax Description
Command Default
Autoloading of configuration files from a network server is disabled, except on systems without NVRAM
or with invalid or incomplete information in NVRAM. In these cases, autoloading of configuration files
from a network server is enabled automatically.
Command Modes
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
Usually, the service config command is used in conjunction with the boot host or boot network command.
You must enter the service config command to enable the router to automatically configure the system
from the file specified by the boot host or boot network command. With Cisco IOS software Releases
12.3(2)T, 12.3(1)B, and later releases, you no longer have to specify the service config command for the
boot host or boot network command to be active. If you specify both the no service config command and
the boot host command, the router attempts to find the specified host configuration file. The service config
command can also be used without the boot host or boot network command. If you do not specify host or
network configuration filenames, the router uses the default configuration files. The default network
configuration file is network-confg. The default host configuration file is host-confg, where host is the
hostname of the router. If the Cisco IOS software cannot resolve its hostname, the default host
configuration file is router-confg.
You must issue the reload command for the service config command to take effect.
R through setup
service config
Examples
In the following example, a router is configured to autoload the default network and host configuration
files. Because no boot host or boot network commands are specified, the router uses the broadcast address
to request the files from a TFTP server.
Router(config)# service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be
used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which the
network configuration file resides:
Router(config)# service config
Router(config)# boot network rcp://172.16.1.111/bridge_9.1
Related Commands
Command
Description
boot host
boot network
Reload
R through setup
service counters max age
Syntax Description
seconds
Command Default
seconds is 5 seconds.
Command Modes
Global configuration
Command History
Release
Modification
12.2(18)SXD
12.2(18)SXF
12.2(33)SRA
Usage Guidelines
A fully loaded Catalyst 6500 series switch chassis running Cisco IOS software version 12.2(18)SXF or its
minor variants (SXF through SXF5) takes 1-2 minutes to update the SNMP counters maintained under
ifTable and ifXTable.
Polling the ifTable/ifXTable is done with the need to understand how much traffic is being handled by a
specific port/interface. The typical polling interval to meet this need is 3-5 minutes. No gain is achived by
reducing the polling interval to intervals lesser than 3 minutes.
R through setup
service counters max age
Note
Examples
If you decrease the time interval for retrieving statistics from the default setting (5 seconds), traffic
congestion may result in situations where frequent SNMP (SMNP bulk) retrievals occur.
This example shows how to set the time interval for retrieving statistics:
Router(config)# service counters max age 10
Router(config)#
R through setup
service decimal-tty
service decimal-tty
To specify that line numbers be displayed and interpreted as octal numbers rather than decimal numbers,
use the no service decimal-tty command in global configuration mode. To restore the default, use the
service decimal-tty command.
service decimal-tty
no service decimal-tty
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
In the following example, the router is configured to display decimal rather than octal line numbers:
Router(config)# service decimal-tty
R through setup
service exec-wait
service exec-wait
To delay the startup of the EXEC on noisy lines, use the service exec-wait command in global
configuration mode. To disable the delay function, use the no form of this command.
service exec-wait
no service exec-wait
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This command delays startup of the EXEC until the line has been idle (no traffic seen) for 3 seconds. The
default is to enable the line immediately on modem activation.
This command is useful on noisy modem lines or when a modem attached to the line is configured to
ignore MNP/V.42 negotiations, and MNP/V.42 modems may be dialing in. In these cases, noise or MNP/V.
42 packets may be interpreted as usernames and passwords, causing authentication failure before the user
has a chance to type a username or password. The command is not useful on nonmodem lines or lines
without some kind of login configured.
Examples
R through setup
service finger
service finger
The service finger command has been replaced by the ip finger command. However, the service finger
and no service finger commands continue to function to maintain backward compatibility with older
versions of Cisco IOS software. Support for this command may be removed in a future release. See the
description of the ip finger command for more information.
R through setup
service hide-telnet-address
service hide-telnet-address
To hide addresses while trying to establish a Telnet session, use the service hide-telnet-address command
in global configuration mode. To disable this service, use the noform of this command.
service hide-telnet-address
no service hide-telnet-address
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.2
12.2(33)SRA
When you attempt to connect to a device, the router displays addresses and other messages (for example,
Trying router1 (171.69.1.154, 2008)...). With the hide feature, the router suppresses the display of the
address (for example, Trying router1 address #1...). The router continues to display all other messages
that would normally be displayed during a connection attempt, such as detailed error messages if the
connection was not successful.
The hide feature improves the functionality of the busy-message feature. When you configure only the
busy-message command, the normal messages generated during a connection attempt are not displayed;
only the busy-message is displayed. When you use the hide and busy features together you can customize
the information displayed during Telnet connection attempts. When you configure the service hide-telnetaddress command and the busy-message command, the router suppresses the address and displays the
message specified with the busy-message command if the connection attempt is not successful.
Examples
R through setup
service hide-telnet-address
Related Commands
Command
Description
busy-message
R through setup
service linenumber
service linenumber
To configure the Cisco IOS software to display line number information after the EXEC or incoming
banner, use the service linenumber command in global configuration mode. To disable this function, use
the no form of this command.
service linenumber
no service linenumber
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
With the service linenumber command, you can have the Cisco IOS software display the host name, line
number, and location each time an EXEC process is started, or an incoming connection is made. The line
number banner appears immediately after the EXEC banner or incoming banner. This feature is useful for
tracking problems with modems, because the host and line for the modem connection are listed. Modem
type information can also be included.
Examples
In the following example, a user Telnets to Router2 before and after the service linenumber command is
enabled. The second time, information about the line is displayed after the banner.
Router1> telnet Router2
Trying Router2 (172.30.162.131)... Open
Welcome to Router2.
User Access Verification
Password:
Router2> enable
Password:
Router2# configure terminal
Enter configuration commands, one per line.
Router2(config)# service linenumber
Router2(config)# end
R through setup
service linenumber
Router2# logout
[Connection to Router2 closed by foreign host]
Router1> telnet Router2
Trying Router2 (172.30.162.131)... Open
Welcome to Router2.
Router2 line 10
User Access Verification
Password:
Router2>
Related Commands
Command
Description
show users
R through setup
service nagle
service nagle
To enable the Nagle congestion control algorithm, use the service nagle command in global configuration
mode. To disable the algorithm, use the no form of this command.
service nagle
no service nagle
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
When using a standard TCP implementation to send keystrokes between machines, TCP tends to send one
packet for each keystroke typed. On larger networks, many small packets use up bandwidth and contribute
to congestion.
The algorithm developed by John Nagle (RFC 896) helps alleviate the small-packet problem in TCP. In
general, it works this way: The first character typed after connection establishment is sent in a single
packet, but TCP holds any additional characters typed until the receiver acknowledges the previous packet.
Then the second, larger packet is sent, and additional typed characters are saved until the acknowledgment
comes back. The effect is to accumulate characters into larger chunks, and pace them out to the network at
a rate matching the round-trip time of the given connection. This method is usually effective for all TCPbased traffic. However, do not use the service nagle command if you have XRemote users on X Window
system sessions.
Examples
R through setup
service prompt config
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Examples
Release
Modification
11.1
12.2(33)SRA
In the following example, the no service prompt config command prevents the configuration prompt from
being displayed. The prompt is still displayed in EXEC mode. When the service prompt config command
is entered, the configuration mode prompt reappears.
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# no service prompt config
hostname newname
end
newname# configure terminal
Enter configuration commands, one per line.
service prompt config
newname(config)# hostname Router
Router(config)# end
Router#
R through setup
service prompt config
Related Commands
Command
Description
hostname
prompt
R through setup
service sequence-numbers
service sequence-numbers
To enable visible sequence numbering of system logging messages, use the service sequence-numbers
command in global configuration mode. To disable visible sequence numbering of logging messages, use
the no form of this command.
service sequence-numbers
no service sequence-numbers
Syntax Description
Command Default
Disabled.
Command Modes
Global configuration
Command History
Release
Modification
12.0
12.2(33)SRA
Usage Guidelines
Each system status messages logged in the system logging process have a sequence reference number
applied. This command makes that number visible by displaying it with the message. The sequence number
is displayed as the first part of the system status message. See the description of the logging commands for
information on displaying logging messages.
Examples
Router(config)# end
Router#
000066: .Mar 22 15:35:57 PST: %SYS-5-CONFIG_I: Configured from console by console
R through setup
service sequence-numbers
Related Commands
Command
Description
logging on
service timestamps
R through setup
service slave-log
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important error messages to the console, use
the service slave-log command in global configuration mode . To disable slave logging, use the no form of
this command.
service slave-log
no service slave-log
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Release
Modification
11.1
12.2(33)SRA
Usage Guidelines
This command allows slave slots to log error messages of level 2 or higher (critical, alerts, and
emergencies).
Examples
In the following example, the router is configured to log important messages from the slave cards to the
console:
Router(config)# service slave-log
The first line indicates which slot sent the message. The second line contains the error message.
R through setup
service tcp-keepalives-in
service tcp-keepalives-in
To generate keepalive packets on idle incoming network connections (initiated by the remote host), use the
service tcp-keepalives-in command in global configuration mode . To disable the keepalives, use the
noform of this command.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
Related Commands
Command
Description
service tcp-keepalives-out
R through setup
service tcp-keepalives-out
service tcp-keepalives-out
To generate keepalive packets on idle outgoing network connections (initiated by a user), use the service
tcp-keepalives-out command in global configuration mode . To disable the keepalives, use the noform of
this command.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
Related Commands
Command
Description
service tcp-keepalives-in
R through setup
service tcp-small-servers
service tcp-small-servers
To enable small TCP servers such as the Echo, use the service tcp-small-servers command in global
configuration mode. To disable the TCP server, use the no form of this command.
service tcp-small-servers [max-servers number | no-limit]
no service tcp-small-servers [max-servers number | no-limit]
Syntax Description
max-servers
number
no-limit
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
To use the service tcp-small-servers command, you must be in a user group associated with a task group
that includes the proper task IDs. If you suspect user group assignment is preventing you from using a
command, contact your Authentication, Authorization, and Accounting (AAA) administrator for assistance.
The TCP small servers consist of three services: Discard (port 9), Echo (port 7), and Chargen (port 19).
These services are used to test the TCP transport functionality. The discard server receives data and
R through setup
service tcp-small-servers
discards it. The echo server receives data and echoes the same data to the sending host. The chargen server
generates a sequence of data and sends it to the remote host.
Examples
The following example shows how to enable small TCP servers and set the maximum number of allowable
small servers to 14:
Router(config)#
service tcp-small-servers max-servers 14
Related Commands
Command
Description
service udp-small-servers
R through setup
service telnet-zeroidle
service telnet-zeroidle
To set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zeroidle
command in global configuration mode. To disable this service, use the no form of this command.
service telnet-zero-idle
no service telnet-zeroidle
Syntax Description
Command Default
The TCP window is not set to zero when the the Telnet connection is idle.
Command Modes
Command History
Release
Modification
10.0
12.2(33)SRA
15.0(1)M
12.2(33)SRC
Usage Guidelines
Normally, data sent to noncurrent Telnet connections is accepted and discarded. When the service telnetzero-idle command is enabled, if a session is suspended (that is, some other connection is made active or
the router is in the privileged EXEC mode), the TCP window is set to zero. This action prevents the remote
host from sending any more data until the connection is resumed. Use this command when it is important
that all messages sent by the host be seen by the users and the users are likely to use multiple sessions.
Do not use this command if your host will eventually time out and log out a TCP user whose window is
zero.
Examples
The following example shows how to set the TCP window to zero when the Telnet connection is idle:
Router(config)# service telnet-zeroidle
R through setup
service telnet-zeroidle
Related Commands
Command
Description
resume
R through setup
service timestamps
service timestamps
To configure the system to apply a time stamp to debugging messages or system logging messages, use the
service timestamps command in global configuration mode . To disable this service, use the no form of
this command.
service timestamps [debug | log] [uptime | datetime [msec]] [localtime] [show-timezone] [year]
no service timestamps [debug | log]
Syntax Description
debug
log
uptime
datetime
R through setup
service timestamps
msec
localtime
year
show-timezone
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
11.3(5)
12.3(1)
12.3(2)T
12.2(33)SRA
12.2(33)SXH
12.2(33)SB
Time stamps can be added to either debugging messages (service timestamp debug) or logging messages
(service timestamp log) independently.
R through setup
service timestamps
If the service timestampscommand is specified with no arguments or keywords, the default is service
timestamps debug uptime.
The no service timestampscommand by itself disables time stamps for both debug and log messages.
The uptime form of the command adds time stamps (such as 2w3d) that indicating the time since the
system was rebooted. The datetime form of the command adds time stamps (such as Sep 5 2002
07:28:20) that indicate the date and time according to the system clock.
Entering the service timestamps {debug | log} command a second time will overwrite any previously
configured service timestamp {debug | log} commands and associated options.
To set the local time zone, use the clock timezonezonehours-offset command in global configuration mode.
The time stamp will be preceeded by an asterisk or period if the time is potentially inaccurate. The table
below describes the symbols that proceed the time stamp.
Table 41
Examples
Symbol
Description
Example
(blank)
In the following example, the router begins with time-stamping disabled. Then, the default time-stamping is
enabled (uptime time stamps applied to debug output). Then, the default time-stamping for logging is
enabled (uptime time stamps applied to logging output).
Router# show running-config | include time
no service timestamps debug uptime
no service timestamps log uptime
Router# config terminal
Router(config)# service timestamps
! issue the show running-config
running-config | inc time
do Router(config)# do show
R through setup
service timestamps
In the following example, the user enables time-stamping on logging messages using the current time and
date in Coordinated Universal Time/Greenwich Mean Time (UTC/GMT), and enables the year to be
shown.
Router(config)#
! The following line shows the timestamp with uptime (1 week 0 days)
1w0d: %SYS-5-CONFIG_I: Configured from console by console
Router(config)# service timestamps log datetime show-timezone
year
Router(config)# end
! The following line shows the timestamp with datetime (11:13 PM March 22nd)
.Mar 22 2004 23:13:25 UTC: %SYS-5-CONFIG_I: Configured from console by console
The following example shows the change from UTC to local time:
Router# configure terminal
! Logging output can be
! logging message
Router(config)# line 0
R through setup
service timestamps
Router(config)# end
Router#
In the following example, the service timestamps log datetime command is used to change previously
configured options for the date-time time stamp.
Router(config)# service timestamps log datetime localtime show-timezone
Router(config)# end
! The year is not displayed.
Oct 13 15:44:46 PDT: %SYS-5-CONFIG_I: Configured from console by console
Router# config t
Enter configuration commands, one per line. End with the end command.
Router(config)# service timestamps log datetime show-timezone year
Router(config)# end
! note: because the
localtime option was not specified again, that option is
! removed from the output, and time is displayed in UTC (the default)
Oct 13 2004 22:45:31 UTC: %SYS-5-CONFIG_I: Configured from console by console
Related Commands
Command
Description
clock set
ntp
service sequence-numbers
R through setup
service udp-small-servers
service udp-small-servers
To enable small User Datagram Protocol (UDP) servers such as the Echo, use the service udp-smallservers command in global configuration mode. To disable the UDP server, use the no form of this
command.
service udp-small-servers [max-servers number | no-limit]
no service udp-small-servers [max-servers number | no-limit]
Syntax Description
max-servers
number
no-limit
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
To use this command, you must be in a user group associated with a task group that includes the proper
task IDs. If you suspect user group assignment is preventing you from using a command, contact your
Authentication, Authorization, and Accounting (AAA) administrator for assistance.
The UDP small servers currently consist of three services: Discard (port 9), Echo (port 7), and Chargen
(port 19). These services are used to test the UDP transport functionality. The discard server receives data
R through setup
service udp-small-servers
and discards it. The echo server receives data and echoes the same data to the sending host. The chargen
server generates a sequence of data and sends it to the remote host.
Examples
The following example shows how to enable small UDP servers and set the maximum number of allowable
small servers to 10:
Router(config)#
service udp-small-servers max-servers 10
Related Commands
Command
Description
service tcp-small-servers
R through setup
service-module apa traffic-management
Syntax Description
monitor
inline
Command Default
None
Command Modes
Command History
Usage Guidelines
Release
Modification
12.4(20)YA
To perform traffic management, you enable or disable the flow of packets by configuring the service
module interface and the router interface.
Configure the router interface with the service-module apa traffic-management [monitor |
inline]command.
Note
Monitor--will copy the packet and designate the copy as the one forwarded to the Application
Performance Assurance module (NME-APA).
Inline--will send the packet to the NME-APA, rather than sending a copy of the packet. After the
NME-APA has processes the packet, it sends it back to the router.
Enable only one traffic management option on the router, but not both concurrently.
Configure the service module interface with the Application Performance Assurance (APA) graphical
user interface (GUI). See the Cisco Application Performance Assurance User Guide for details.
R through setup
service-module apa traffic-management
Examples
The following example configures an interface on a Cisco 2851 Integrated Services Router for inline traffic
management.
Router> enable
Router# configure terminal
Router(config)# interface gigabitethernet 0/1
Router(config-if)# ip address
10.10.10.43 255.255.255.0
Router(config-if)# service-module apa traffic-management inline
Router(config-if)# exit
end
Related Commands
Command
Description
interface gigabitethernet
ip address
R through setup
service-module wlan-ap bootimage
Syntax Description
interface number
autonomous
unified
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Note
Release
Modification
12.4(20) T
When running the advanced IP services feature set on either Cisco 880 Series routers or Cisco 890 Series
routers, use the service-module wlan-ap 0 bootimage unified commandto enable the Cisco unified
software upgrade image on the embedded wireless access point. After enabling the unified image, use the
service-module wlan-ap 0 reload command to perform a graceful shutdown and reboot of the access
point.
The service-module wlan-ap 0 bootimagecommand does not support recovery images on the embedded
access point. Use the service-module wlan-ap 0 reload command to shutdown and reboot the access point.
Cisco 880 Series and Cisco 890 Series routers with embedded access point running the unified software
image require DHCP to obtain an IP address for the access point. An IP address is needed to communicate
with the Wireless LAN Controller (WLC) and to download its image upon boot up. The host router can
provide DHCP server functionality through the DHCP pool to reach the WLC, and setup option 43 for the
controller IP address in the DHCP pool configuration.
R through setup
service-module wlan-ap bootimage
Use the following guideline to setup a DHCP pool on the host router.
ip dhcp pool embedded-ap-pool
network 60.0.0.0 255.255.255.0
default router 60.0.0.1
option 43 hex f104.0a0a.0a0f /* Single WLC IP address (10.10.10.15) in HEX format */
int vlan 1 /* Default Vlan */
ip address 60.0.0.1 255.255.255.0
int Wlan-GigabitEthernet0 /* internal switch-port to AP */
switchport access vlan 1
Examples
The following example upgrades the embedded access point image from autonomous to unified.
Router#configure terminal
Router(config)#service-module wlan-ap 0 bootimage unified
*Jan 18 05:31:58.172: %WLAN_AP_SM-6-UNIFIED_IMAGE: Embedded AP will change boot image to
mini-IOS also called LWAPP recovery Please check router config to ensure connectivity
between WLC and AP. Use service-module wlan-ap 0 reload to bootup mini-IOS image on AP
Router(config)#end
Router#
*Jan 18 05:32:04.136: %SYS-5-CONFIG_I: Configured from console by console Router#servicemodule wlan-ap 0 reload
Reload will save AP config....
Do you want to proceed with reload?[confirm] Trying to reload Service Module wlan-ap0.
Router#
Service Module saved config, start reset.
Received reload request from router
Saving configuration...
Building configuration...
Related Commands
Command
Description
interface wlan-ap
R through setup
service-module wlan-ap reload
Syntax Description
interface number
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.4(20)T
Autonomous Mode
At the confirmation prompt, press Enter to confirm the action, or press n to cancel.
Note
When running in autonomous mode, the reload command saves the configuration before rebooting. If the
attempt is unsuccessful, the following message displays: Failed to save service module configuration.
Unified Mode
The service module reload command is usually handled by the Wireless LAN Controller (WLC).
Note
When running in Unified mode, the reload command will produce the following message: The embedded
wireless device is in Unified mode. Reload/reset is normally handled by WLC controller. Still want to
proceed? [yes]
R through setup
service-module wlan-ap reload
Examples
The following examples show a graceful shut down and reboot of the service module:
Autonomous Mode
Router# service-module wlan-ap0 reload
Do you want to proceed with reload?[confirm]
Router# reload
Do you want to reload the internal AP ? [yes/no]:
Do you want to save the configuration of the AP ? [yes/no]:
System configuration has been modified. Save [yes/no]:
Proceed with reload? [confirm]
Unified Mode
Router# service-module wlan-ap0 reload
The embedded AP is in Unified mode. Reload/reset is normally handled by WLC controller.
Still want to proceed? [yes]
Router# reload
The embedded AP is in Unified mode. Reload/reset is normally handled by WLC controller.
Do you want to reload the internal AP [yes/no]:
System configuration has been modified. Save [yes/no]:
Proceed with reload [Confirm]
Related Commands
Command
Description
interface wlan-ap
R through setup
service-module wlan-ap reset
Syntax Description
interface number
bootloader
default-config
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
Examples
Release
Modification
12.4(20)T
At the confirmation prompt, press Enter to confirm the action, or press n to cancel.
Because you may lose data, use the service-module wlan-ap reset command only to recover from a
shutdown or failed state.
The following example resets a wireless device on a router that is operating in either autonomous mode or
LWAPP mode:
R through setup
service-module wlan-ap reset
Autonomous Mode
Router# service-module wlan-ap0 reset
Use reset only to recover from shutdown or failed state.
LWAPP Mode
Router# service-module wlan-ap0 reset
The embedded device is in LWAPP mode. Reload/reset is normally handled by WLC controller.
Still want to proceed? [yes]
Related Commands
Command
Description
interface wlan-ap
R through setup
service-module wlan-ap session
Syntax Description
interface number
clear
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.4(20)T
Only one session is allowed at a time into the wireless device from a router console-port connection. After
starting a session, perform configuration tasks on the wireless device. You first access the router in a userlevel shell. To access the privileged EXEC command shell, where most commands are available, use the
enable command.
When you finish configuring the device, and would like to exit the console session, type Ctrl-Shift 6x to
return to the routers console. Type service-module wlan-ap session clear or disconnect to close the session
with the device. At the confirmation prompt, press Enter twiceto confirm the action or n to cancel.
Note
If you do not clear or disconnect the session on the service module, it will remain open in the background
after you return to the router's console prompt. When the session is open in the background, pressing Enter
will toggle you back to the wireless device prompt.
R through setup
service-module wlan-ap session
Examples
The following example clears the session on the service-module in the ISR:
Router#service-module wlan-ap 0 session clear
[confirm]
[OK]
Related Commands
Command
Description
enable
interface wlan-ap
R through setup
service-module wlan-ap statistics
Syntax Description
interface number
Command Default
none
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.4(20)T
Related Commands
Command
Description
interface wlan-ap
R through setup
service-module wlan-ap statistics
Command
Description
R through setup
service-module wlan-ap status
Syntax Description
interface number
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.4(20)T
Examples
The following example displays information for the wireless device on a Cisco Integrated Services Router:
Router#service-module wlan-ap 0 status
Service Module is Cisco wlan-ap0
Service Module supports session via TTY line 2
Service Module is in Steady state
Service Module reset on error is disabled
Getting status from the Service Module, please wait..
Image path = flash:c8xx_19xx_ap-k9w7-mx.acregr/c8xx_19xx_ap-k9w7-mx.acre
gr
System uptime = 0 days, 4 hours, 28 minutes, 5 seconds
Router#d was introduced for embedded wireless LAN access points on Cisco 860 and 880
Series Integrated Services Routers.
R through setup
service-module wlan-ap status
Related Commands
Command
Description
interface wlan-ap
R through setup
session slot
session slot
To open a session with a module (for example, the Multilayer Switch Module (MSM), Network Analysis
Module (NAM), or Asynchronous Transfer Mode (ATM)), use the session slot command in EXEC mode.
session slot mod processor processor-id
Syntax Description
mod
Slot number.
processor processor-id
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Examples
This example shows how to open a session with an MSM (module 4):
Router# session slot 4 processor 2
Router#
R through setup
set memory debug incremental starting-time
Syntax Description
none
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(8)T1
12.2(25)S
12.2(33)SRA
Usage Guidelines
For incremental analysis, a starting point can be defined by using the set memory debug incremental
starting-time command. When a starting time is set, only memory allocated after that starting time will be
considered for reporting as leaks.
Examples
The following example shows the command used to set the starting time for incremental analysis to the
time when the command was issued:
Router# set memory debug incremental starting-time
R through setup
set memory debug incremental starting-time
Related Commands
Command
Description
R through setup
setup
setup
To enter Setup mode, use the setup command in privileged EXEC mode.
setup
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Note
Release
Modification
11.1
12.2(33)SRA
Setup mode gives you the option of configuring your system without using the Cisco IOS Command Line
Interface (CLI). For some tasks, you may find it easier to use Setup than to enter Cisco IOS commands
individually. For example, you might want to use Setup to add a protocol suite, to make major addressing
scheme changes, or to configure a newly installed interface. Although you can use the CLI to make these
changes, Setup provides you with a high-level view of the configuration and guides you through the
configuration process.
If you are not familiar with Cisco products and the CLI, Setup is a particularly valuable tool because it
prompts you for the specific information required to configure your system.
If you use the Setup mode to modify a configuration because you have added or modified the hardware, be
sure to verify the physical connections using the show version EXEC command. Also, verify the logical
port assignments using the show running-config EXEC command to ensure that you configure the correct
port. Refer to the hardware documentation for your platform for more information on physical and logical
port assignments.
Before using the Setup mode, you should have the following information so that you can configure the
system properly:
When you enter the setup EXEC command after first-time startup, an interactive dialog called the System
Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you
R through setup
setup
through the configuration process. It prompts you first for global parameters and then for interface
parameters. The values shown in brackets next to each prompt reflect either the default settings or the last
configured setting.
The prompts and the order in which they appear on the screen vary depending on the platform and the
interfaces installed in the device.
You must progress through the System Configuration Dialog until you come to the item that you intend to
change. To accept default settings for items that you do not want to change, press the Return or Enter key.
The default choice is indicated by square brackets (for example, [yes]) before the prompt colon (:).
To exit Setup mode and return to privileged EXEC mode without making changes and without progressing
through the entire System Configuration Dialog, press Ctrl-C
The facility also provides help text for each prompt. To access help text, press the question mark (?) key at
a prompt.
When you complete your changes, the system will automatically display the configuration file that was
created during the Setup session. It also asks you if you want to use this configuration. If you answerYes,
the configuration is saved to NVRAM as the startup configuration file. If you answer No, the configuration
is not saved and the process begins again. There is no default for this prompt; you must answer either Yes
or No.
Examples
The following example displays the setup command facility to configure serial interface 0 and to add
ARAP and IP/IPX PPP support on the asynchronous interfaces:
Router# setup
--- System Configuration Dialog
--At any point you may enter a question mark '?' for help.
Use ctrl-c to
abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Continue with configuration dialog? [yes]:
First, would you like to see the current
interface summary? [yes]:
Interface
IP-Address
OK? Method
Status
Ethernet0
172.16.72.2
YES manual
up
Serial0
unassigned
YES not set
administratively down
Serial1
172.16.72.2
YES not set
up
Configuring global parameters:
Enter host name [Router]:
The enable secret is a one-way cryptographic secret used
instead of the enable password when it exists.
Enter enable secret [<Use current secret>]:
The enable password is used when there is no enable secret
and when using older software and some boot images.
Enter enable password [ww]:
Enter virtual terminal password [ww]:
Configure SNMP Network Management? [yes]:
Community string [public]:
Configure DECnet? [no]:
Configure AppleTalk? [yes]:
Multizone networks? [no]: yes
Configure IPX? [yes]:
Configure IP? [yes]:
Configure IGRP routing? [yes]:
Your IGRP autonomous system number [15]:
Configure Async lines? [yes]:
Async line speed [9600]: 57600
Protocol
up
down
up
R through setup
setup
R through setup
setup
R through setup
setup
ipx network 3
no mop enabled
!
interface Serial1
no ip address
ip unnumbered Ethernet0
appletalk cable-range 2-2 2.2
appletalk zone ZZ Serial
ipx network 2
no mop enabled
!
Interface Async1
ipx network 4
ip unnumbered Ethernet0
peer default ip address 172.16.72.4
async mode interactive
!
Interface Async2
ipx network 5
ip unnumbered Ethernet0
peer default ip address 172.16.72.5
async mode interactive
!
Interface Async3
ipx network 6
ip unnumbered Ethernet0
peer default ip address 172.16.72.6
async mode interactive
!
Interface Async4
ipx network 7
ip unnumbered Ethernet0
peer default ip address 172.16.72.7
async mode interactive
async dynamic address
!
Interface Async5
ipx network 8
ip unnumbered Ethernet0
peer default ip address 172.16.72.8
async mode interactive
!
Interface Async6
ipx network 9
ip unnumbered Ethernet0
peer default ip address 172.16.72.9
async mode interactive
!
Interface Async7
ipx network A
ip unnumbered Ethernet0
peer default ip address 172.16.72.10
async mode interactive
!
Interface Async8
ipx network B
ip unnumbered Ethernet0
peer default ip address 172.16.72.11
async mode interactive
!
Interface Async9
ipx network C
ip unnumbered Ethernet0
peer default ip address 172.16.72.12
async mode interactive
!
Interface Async10
ipx network D
ip unnumbered Ethernet0
peer default ip address 172.16.72.13
async mode interactive
!
Interface Async11
R through setup
setup
ipx network E
ip unnumbered Ethernet0
peer default ip address 172.16.72.14
async mode interactive
!
Interface Async12
ipx network F
ip unnumbered Ethernet0
peer default ip address 172.16.72.15
async mode interactive
!
Interface Async13
ipx network 10
ip unnumbered Ethernet0
peer default ip address 172.16.72.16
async mode interactive
!
Interface Async14
ipx network 11
ip unnumbered Ethernet0
peer default ip address 172.16.72.17
async mode interactive
!
Interface Async15
ipx network 12
ip unnumbered Ethernet0
peer default ip address 172.16.72.18
async mode interactive
!
Interface Async16
ipx network 13
ip unnumbered Ethernet0
peer default ip address 172.16.72.19
async mode interactive
!
router igrp 15
network 172.16.0.0
!
end
Use this configuration? [yes/no]: yes
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.
Router#
Related Commands
Command
Description
erase nvram:
show running-config
show startup-config
show version
show
To verify the Multiple Spanning Tree (MST) configuration, use the show command in MST configuration
mode.
show [current | pending]
Syntax Description
current
pending
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
The display output from the show pending command is the edited configuration that will replace the
current configuration if you enter the exit command to exit MST configuration mode.
Entering the show command with no arguments displays the pending configurations.
Examples
0
2
4001-4096
1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080, 1090, 1100, 1110
1120
3
1-1009, 1011-1019, 1021-1029, 1031-1039, 1041-1049, 1051-1059
1061-1069, 1071-1079, 1081-1089, 1091-1099, 1101-1109, 1111-1119
1121-4000
-----------------------------------------------------------------------------Router(config-mst)#
Related Commands
Command
Description
instance
revision
Syntax Description
command
| append url
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.0(21)S
12.2(13)T
To display all URL prefixes that are supported for this command, use the showcommand| append ?
command.
This command adds the show command output to the end of the specified file.
Examples
In the following example, output from the show tech-support command is redirected to an existing file on
Disk 1 with the file-name of showoutput.txt. This output is added at the end of any existing data in the
file.
Router# show tech-support | append disk1:showoutput.txt
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
command
regular-expression
EXEC
Release
Modification
8.3
12.0(1)T
12.2(33)SRA
Usage Guidelines
The regular-expressionargument is case sensitive and allows for complex matching requirements. Use
parenthesis to indicate a literal use of spaces. For example, | begin u indicates that the show output should
begin with any line that contains a u; | begin ( u) indicates that the show output should begin with any line
that contains a space and a u together (line has a word that begins with a lowercase u).
To search the remaining output of the show command, use the following command at the --More-- prompt:
/ regular-expression
You can specify a filtered search at any --More-- prompt. To filter the remaining output of the show
command, use one of the following commands at the --More-- prompt:
- regular-expression
+ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-z.
Note
Once you specify a filter for a show command, you cannot specify another filter at the next --More-prompt. The first specified filter remains until the more command output finishes or until you interrupt the
output. The use of the keyword begin does not constitute a filter.
Because prior output is not saved, you cannot search or filter backward through prior output.
Note
Examples
A few show commands that have long output requirements do not require user input at the --More-- prompt
to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or
Ctrl-Z combinations as there are --More-- prompts to completely abort output.
The following is partial sample output of the show interface | begincommand that begins unfiltered output
with the first line that contains the regular expression Ethernet. At the --More-- prompt, the user specifies
a filter to show only the lines in the remaining output that contain the regular expression Serial.
Router# show interface | begin Ethernet
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.837c.6399 (bia 0060.837c.6399)
Description: ip address is 172.1.2.14 255.255.255.0
Internet address is 172.1.2.14/24
.
.
.
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
--More-+Serial
filtering...
Serial1 is up, line protocol is up
Serial2 is up, line protocol is up
Serial3 is up, line protocol is down
Serial4 is down, line protocol is down
Serial5 is up, line protocol is up
Serial6 is up, line protocol is up
Serial7 is up, line protocol is up
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
command
regular-expression
EXEC
Release
Modification
12.0(1)T
12.2(33)SRA
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at every --More-- prompt. To search the remaining output of the show
command, use the following syntax at the --More-- prompt:
/ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z.
Because prior output is not saved, you cannot search or filter backward through prior output.
Note
Examples
A few show commands that have long output requirements do not require user input at the --More-- prompt
to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or
Ctrl-Z combinations as there are --More-- prompts to completely abort output.
The following is partial sample output of the show | excludecommand used with the show
bufferscommand. It excludes lines that contain the regular expression 0 misses. At the --More-- prompt,
the user searches for the regular expression Serial0, which continues the filtered output with the first line
that contains Serial0.
Router# show buffers | exclude 0 misses
Buffer elements:
398 in free list (500 max allowed)
Public buffer pools:
Small buffers, 104 bytes (total 50, permanent 50):
50 in free list (20 min, 150 max allowed)
551 hits, 3 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 50, permanent 50):
49 in free list (5 min, 150 max allowed)
Very Big buffers, 4520 bytes (total 10, permanent 10):
.
.
.
Huge buffers, 18024 bytes (total 0 permanent 0):
0 in free list (0 min, 4 max allowed)
--More-/Serial0
filtering...
Serial0 buffers, 1543 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
48 hits, 0 fallbacks
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
command
regular-expression
EXEC
Release
Modification
12.0(1)T
12.2(33)SRA
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at every --More-- prompt. To search the remaining output of the show
command, use the following syntax at the --More-- prompt:
/ regular-expression
When output volume is large, the search can produce long lists of output. To interrupt the output, press
Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z.
Because prior output is not saved, you cannot search or filter backward through prior output.
Note
Examples
A few show commands that have long output requirements do not require user input at the --More-- prompt
to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or
Ctrl-Z combinations as there are --More-- prompts to completely abort output.
The following is partial sample output of the show interface | includecommand. It displays only lines that
contain the regular expression ( is ). The parentheses force the inclusion of the spaces before and after
is. Use of the parenthesis ensures that only lines containing is with a space both before and after it will
be included in the output. Lines with words like disconnect will be excluded because there are not spaces
around the instance of the string is.
Router# show interface | include ( is )
ATM0 is administratively down, line protocol is down
Hardware is ATMizer BX-50
Dialer1 is up (spoofing), line protocol is up (spoofing)
Hardware is Unknown
DTR is pulsed for 1 seconds on reset
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.837c.6399 (bia 0060.837c.6399)
Internet address is 172.21.53.199/24
Ethernet1 is up, line protocol is up
Hardware is Lance, address is 0060.837c.639c (bia 0060.837c.639c)
Internet address is 5.5.5.99/24
Serial0:0 is down, line protocol is down
Hardware is DSX1
.
.
.
--More--
At the --More-- prompt, the user searches for the regular expression Serial0:13, which continues filtered
output with the first line that contains Serial0:13.
/Serial0:13
filtering...
Serial0:13 is down, line protocol is down
Hardware is DSX1
Internet address is 11.0.0.2/8
0 output errors, 0 collisions, 2 interface resets
Timeslot(s) Used:14, Transmitter delay is 0 flags
Related Commands
Command
Description
Command
Description
Syntax Description
command
| redirect url
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.0(21)S
12.2(13)T
To display all URL prefixes that are supported for this command, use the showcommand| redirect ?
command.
This command creates a new file at the specified location, or overwrites an existing file.
Examples
In the following example, output from the show tech-support command is write to the file showtech.txt
on the host at 172.16.101.101 in the directory //tftpboot/docs/ using FTP:
Router# show tech | redirect ftp://USER:[email protected]//tftpboot/docs/
showtech.txt
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
command
include
exclude
regular-expression
Privileged EXEC
Release
Modification
12.3(2)T
In many cases, it is useful to filter the output of a show command to match a specific expression. Filtering
provides some control over the type and amount of information displayed by the system. The show section
command provides enhanced filtering capabilities by matching lines in the show command output
containing specific expressions as well as matching any entries associated with those expressions. Filtering
is especially useful, for example, when displaying large configuration files using the show runningconfiguration command or the show interfaces command.
If the include or exclude keyword is not specified, include is the default.
If there are no associated entries for an expression, then only the line matching the expression is displayed.
Examples
The following examples compare the filtering characteristics of the show running-config | include
command with the show running-config | section command. The first example gathers just the lines from
the configuration file with interface in them.
Router# show running-config | include interface
interface
interface
interface
interface
Ethernet0/0
Ethernet1/0
Serial2/0
Serial3/0
The next example uses the showcommand sectioncommand to gather the lines in the configuration file with
interface in them as well as any lines associated with those entries. In this example, interface
configuration information is captured.
Router# show running-config | section include interface
interface Ethernet0/0
shutdown
no cdp enable
interface Ethernet1/0
shutdown
no cdp enable
interface Serial2/0
shutdown
no cdp enable
interface Serial3/0
shutdown
no cdp enable
Related Commands
Command
Description
Syntax Description
command
| tee url
/append
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.0(21)S
12.2(13)T
To display all URL prefixes that are supported for this command, use the showcommand| tee ? command.
The tee keyword was chosen to reflect that output is redirected to two locations; the terminal and a file (as
a tee plumbing junction redirects water to two different pipes).
Examples
In the following example, output from the show tech-support command is displayed on-screen while it is
written to the file showoutput.txt at the host 172.16.101.101 using TFTP:
Router# show tech-support | tee tftp://172.16.101.101/docs/showoutput.txt
The following example performs the same function as above, but in this case the output is added at the end
of any existing data in the file showoutput.txt:
Router# show tech-support | tee /append tftp://172.16.101.101/docs/showoutput.txt
Related Commands
Command
Description
Syntax Description
flash-filesystem :
all
bootflash
flash
slot0
slot1
slavebootflash
slaveslot0
slaveslot1
Command Modes
Command History
Usage Guidelines
chips
filesys
partition-number
detailed
err
summary
EXEC
Release
Modification
11.3 AA
12.3
12.2(33)SRA
If Flash memory is partitioned, the command displays the requested output for each partition, unless you
use the partition keyword.
The command also specifies the location of the current image.
To display the contents of boot Flash memory on Class A or B file systems, use the show bootflash:
command as follows:
Examples
The output of the showcommand depends on the type of Flash file system you select. Types include flash:,
bootflash:, slot0:, slot1:, slavebootflash:, slaveslot0:, and slaveslot1:.
Examples of output from the show flashcommand are provided in the following sections:
Although the examples use flash: as the Flash file system, you may also use the other Flash file systems
listed.
Class A Flash File System
The following three examples show sample output for Class A Flash file systems. The table below
describes the significant fields shown in the display.
The following is sample output from the show flash: command.
Router# show flash:
-#- ED --type-- --crc--- -seek-- nlen -length1
.. unknown 317FBA1B 4A0694
24 4720148
c7200-j-mz
2
.. unknown 9237F3FF 92C574
11 4767328
3
.D unknown 71AB01F1 10C94E0
10 7982828
4
.D unknown 96DACD45 10C97E0
8
639
5
.. unknown 96DACD45 10C9AE0
3
639
6
.D unknown 96DACD45 10C9DE0
8
639
7
.. unknown 96DACD45 10CA0E0
8
639
3104544 bytes available (17473760 bytes used)
Table 42
-----date/time------ name
Dec 15 2003 17:49:36 -08:00 hampton/nitro/
Jan
Jan
Jan
Jan
Jan
Jan
02
02
03
03
03
03
2004
2004
2004
2004
2004
2004
18:42:53
18:48:14
12:09:17
12:09:32
12:37:01
12:37:13
-08:00
-08:00
-08:00
-08:00
-08:00
-08:00
c7200-js-mz
rsp-jsv-mz
the_time
the_time
the_time
the_time
Field
Description
ED
Field
Description
type
crc
seek
nlen
length
date/time
name
The following is sample output from the show flash: chips command:
RouterA# show flash: chips
******** Intel Series 2+ Status/Register Dump
ATTRIBUTE MEMORY REGISTERS:
Config Option Reg (4000): 2
Config Status Reg (4002): 0
Card Status
Reg (4100): 1
Write Protect Reg (4104): 4
Voltage Cntrl Reg (410C): 0
Rdy/Busy Mode Reg (4140): 2
COMMON MEMORY REGISTERS: Bank 0
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global
Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 1
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global
Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 2
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global
Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 3
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global
Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
********
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
The following is sample output from the show flash: filesys command:
RouterA# show flash: filesys
-------- F I L E
S Y S T E M
S T A T U S -------Device Number = 0
DEVICE INFO BLOCK:
Magic Number
= 6887635
File System Vers = 10000
(1.0)
Length
= 1400000
Sector Size
= 20000
Programming Algorithm = 4
Erased State
= FFFFFFFF
File System Offset
= 20000
Length = 13A0000
MONLIB Offset
= 100
Length = C730
Bad Sector Map Offset = 1FFEC
Length = 14
Squeeze Log Offset
= 13C0000
Length = 20000
Squeeze Buffer Offset = 13E0000
Length = 20000
Num Spare Sectors
= 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
No Squeeze in progress
USAGE INFO:
Bytes Used
= 10AA0E0 Bytes Available = 2F5F20
Bad Sectors
= 0
Spared Sectors = 0
OK Files
= 4
Bytes = 90C974
Deleted Files = 3
Bytes = 79D3EC
Files w/Errors = 0
Bytes = 0
The following example shows detailed information about the second partition in internal Flash memory:
RouterB# show flash:2
System flash directory, partition 2:
File Length
Name/status
1
1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Table 43
Field
Description
addr
available
Bank
Bank number.
Bank-Size
bytes used
ccksum
Computed checksum.
Chip
Chip number.
Code
Code number.
Copy-Mode
fcksum
File
Free
Length
Name
Field
Description
Name/status
Partition
Size
State
total
Used
The following is sample output from the show flash: all command:
RouterB> show flash: all
Partition
Size
Used
1
16384K
4040K
Free
12343K
Bank-Size
4096K
State
Read/Write
Copy Mode
Direct
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
The following is sample output from the show flash: all command on a router with Flash memory
partitioned:
Router# show flash: all
System flash partition information:
Partition
Size
Used
Free
Bank-Size
State
Copy-Mode
637K
4096K
Read Only
RXBOOT-FLH
1
4096K
2
3459K
4096K
3224K
872K
4096K
Read/Write
Direct
System flash directory, partition 1:
File
Length
Name/status
addr
fcksum
ccksum
1
3459720
master/igs-bfpx.100-4.3
0x40
0x3DE1
0x3DE1
[3459784 bytes used, 734520 available, 4194304 total]
4096K bytes of processor board System flash (Read ONLY)
Chip
Bank
Code
Size
Name
1
1
89A2
1024KB
INTEL 28F008SA
2
1
89A2
1024KB
INTEL 28F008SA
3
1
89A2
1024KB
INTEL 28F008SA
4
1
89A2
1024KB
INTEL 28F008SA
Executing current image from System flash [partition 1]
System flash directory, partition2:
File
Length
Name/status
addr
fcksum
ccksum
1
3224008
igs-kf.100
0x40
0xEE91
0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip
Bank
Code
Size
Name
1
2
89A2
1024KB
INTEL 28F008SA
2
2
89A2
1024KB
INTEL 28F008SA
3
2
89A2
1024KB
INTEL 28F008SA
4
2
89A2
1024KB
INTEL 28F008SA
The following is sample output from the show flash: chips command:
RouterB> show flash: chips
16384K bytes of processor board System flash (Read/Write)
Chip
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
The following is sample output from the show flash: detailed command:
RouterB> show flash: detailed
System flash directory:
File Length
Name/status
addr
fcksum ccksum
4137888 c3640-c2is-mz.Feb24
0x40
0xED65 0xED65
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
The following is sample output from the show flash: err command:
RouterB> show flash: err
System flash directory:
File Length
Name/status
1
4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Chip
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
erase
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
write
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
See the table above for a description of the fields. The show flash: err command also displays two extra
fields: erase and write. The erase field indications the number of erase errors. The write field indicates the
number of write errors.
The following is sample output from the show flash summary command on a router with Flash memory
partitioned. The partition in the Read Only state is the partition from which the Cisco IOS image is being
executed.
Router# show flash summary
System flash partition information:
Partition
Size
Used
Free
1
4096K
2048K
2048K
2
4096K
2048K
2048K
Related Commands
Bank-Size
2048K
2048K
State
Read Only
Read/Write
Copy-Mode
RXBOOT-FLH
Direct
Command
Description
more
show aliases
To display all alias commands, or the alias commands in a specified mode, use the show aliases command
in EXEC mode.
show aliases [mode]
Syntax Description
Command Modes
Command History
Usage Guidelines
mode
EXEC
Release
Modification
10.3
12.2(33)SRA
When used without the mode argument, this command will display all aliases currently configured on the
system. Use the mode argument to display only the aliases configured for the specified command mode.
To display a list of the command mode keywords available for your system, use the show aliases ?
command.
The following is sample output from the show aliases exec commands. The aliases configured for
commands in EXEC mode are displayed.
Router> show aliases exec
Exec mode aliases:
h
help
lo
logout
p
ping
r
resume
s
show
w
where
Related Commands
Command
Description
alias
show alignment
To display alignment errors and spurious memory access errors, use the show alignment command in
privileged EXEC mode.
show alignment
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(22)S
12.2(18)SXE
12.2(33)SRA
Alignment Errors
Alignment errors are caused by misaligned reads and writes. For example, a two-byte read where the
memory address is not an even multiple of two bytes is an alignment error. Alignment errors are caused by
a software defect.
Alignment errors are reported in the system log and recorded by the router. Output from the show
alignment command provides a record of these errors along with potentially useful traceback information.
The traceback information for alignment errors can generally be decoded to reveal the function causing the
alignment problems.
Spurious Memory Access Errors
Spurious memory access errors occur when a software process attempts to access memory in a restricted
location. A read operation to this region of memory is usually caused when a nonexisting value is returned
to a function in the software, or in other words, when a null pointer is passed to a function.
Spurious memory access errors are counted and recorded, if possible, by the software. This information is
displayed with the show alignment command.
Examples
The following is sample output from the show alignment command when alignment detection is disabled.
To enable alignment detection, use the enable command to enter privileged EXEC mode
Router# show alignment
Unaligned handler is disabled
Router#
The following is sample output from the show alignment command when there are no alignment or
spurious memory errors:
Router# show alignment
No alignment data has been recorded.
No spurious memory references have been recorded.
Router#
The following is sample output from the show alignment command when there are only alignment errors.
The traceback information is necessary to determine the cause and the fix of the alignment errors.
Router# show alignment
Total Corrections 134, Recorded 1, Reads 134, Writes 0
Initial
Initial
Address Count Access Type
Traceback
1A014C5
134
32bit
read
0x6012F538 0x601338F8 0x601344D8 0x6022D528
No spurious memory references have been recorded.
Router#
The table below describes the significant fields shown in the display.
Table 44
Field
Description
Total Corrections
Recorded
Reads
Writes
Initial Address
Count
Initial Access
Type
Traceback
The following is sample output from the show alignmentcommand when there are only spurious memory
access errors:
Router# show alignment
No alignment data has been recorded.
Total Spurious Accesses 50, Recorded 3
Address Count Traceback
E
10
E
20
0x60743270
E
20
Router#
The table below describes the significant fields shown in the display.
Table 45
Field
Description
Recorded
Address
Count
Traceback
The following is sample output from the show alignmentcommand when there are alignment errors and
spurious memory access errors:
Router# show alignment
Total Corrections 134, Recorded 1, Reads 134, Writes 0
Initial
Initial
Address Count
Access
Type
Traceback
1A014C5
134
32bit
read
0x6012F538 0x601338F8
Total Spurious Accesses 50, Recorded 3
Address Count Traceback
E
10
0x605351A0 0x603CA084 0x606C4060
E
20
0x605351A0 0x6036EE7C 0x606C4060
E
20
0x605351A0 0x603C998C 0x606D53EC
x60743270
Related Commands
0x601344D8 0x6022D528
0x606D6368 0x60743284 0x60743270
0x606D6368 0x60743284 0x60743270
0x606C4060 0x606D6368 0x60743284
Command
Description
enable
show archive
To display information about the files saved in the Cisco IOS configuration archive, use the show archive
command in privileged EXEC mode.
show archive
Syntax Description
Command Modes
Command History
Examples
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SB
11
12
13
14
The following is sample output from the show archive command after several archive files of the running
configuration have been saved. In this example, the maximum number of archive files to be saved is set to
three.
Router# show archive
There are currently 3 archive configurations saved.
The next archive file will be named disk0:myconfig-8
Archive # Name
0
1
:Deleted
2
:Deleted
3
:Deleted
4
:Deleted
5
disk0:myconfig-5
6
disk0:myconfig-6
7
disk0:myconfig-7 <- Most Recent
8
9
10
11
12
13
14
The table below describes the significant fields shown in the displays.
Table 46
Related Commands
Field
Description
Archive #
Name
Command
Description
archive config
configure confirm
configure replace
Command
Description
maximum
path
time-period
Syntax Description
Command Default
filename1(path)
filename2(path)
ignorecase
If the filename1(path) and filename2(path) arguments are not specified, the first configuration file is
assumed to be the running configuration file and the second to be the startup configuration file.
If only the filename1(path)argument is specified, the second configuration file is assumed to be the running
configuration file.
Command Modes
Command History
Release
Modification
12.3(4)T
12.2(25)S
Usage Guidelines
Release
Modification
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
Interpreting the output of the show archive config differencescommand is dependent on the order in which
the two files are configured. Each entry in the generated output list is prefixed with a unique text symbol to
indicate the type of difference found. The text symbols and their meanings are as follows:
Examples
A minus symbol (-) indicates that the configuration line exists in filename1(path) but not in
filename2(path).
A plus symbol (+) indicates that the configuration line exists in filename2(path) but not in
filename1(path).
An exclamation point (!) with descriptive comments is used to identify order-sensitive configuration
lines whose location is different in filename1(path) than in filename2(path).
In this example, a diff operation is performed on the running and startup configuration files. The table
below shows the configuration files used for this example.
Table 47
no ip subnet-zero
ip cef
interface Ethernet1/0
ip address 10.7.7.7 255.0.0.0
no ip route-cache
no ip mroute-cache
duplex half
no ip classless
snmp-server community public RO
ip subnet-zero
ip cef
ip name-server 10.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
duplex half
ip default-gateway 10.5.5.5
ip classless
access-list 110 deny
ip any
access-list 110 deny
ip any
access-list 110 deny
ip any
snmp-server community private
host 10.1.1.1
host 10.1.1.2
host 10.1.1.3
RW
The following is sample output from the show archive config differencescommand. This sample output
displays the results of the diff operation performed on the configuration files in the table above.
Router# show archive config differences running-config startup-config
+ip subnet-zero
Related Commands
Command
Description
more nvram:startup-config
more system:running-config
Syntax Description
Command Modes
Command History
file
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SB
Usage Guidelines
When an incremental diff operation is performed, a list of the configuration lines that do not appear in the
running configuration file (in other words, configuration lines that only appear in the specified file that is
being compared to the running configuration file) is generated as output. An exclamation point (!) with
descriptive comments is used to identify order-sensitive configuration lines whose location is different in
the specified configuration file than in the running configuration file.
Examples
In this example, an incremental diff operation is performed on the startup and running configuration files.
The table below shows the configuration files used for this example.
Table 48
ip subnet-zero
ip cef
ip name-server 10.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
duplex half
ip default-gateway 10.5.5.5
ip classless
access-list 110 deny
ip any
access-list 110 deny
ip any
access-list 110 deny
ip any
snmp-server community private
no ip subnet-zero
ip cef
interface Ethernet1/0
ip address 10.7.7.7 255.0.0.0
no ip route-cache
no ip mroute-cache
duplex half
no ip classless
snmp-server community public RO
host 10.1.1.1
host 10.1.1.2
host 10.1.1.3
RW
The following is sample output from the show archive config incremental-diffscommand. This sample
output displays the results of the incremental diff operation performed on the configuration files in show
archive config incremental-diffs, page 774.
Router# show archive config incremental-diffs nvram:startup-config
ip subnet-zero
ip name-server 10.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
shutdown
ip default-gateway 10.5.5.5
ip classless
access-list 110 deny
ip any host 10.1.1.1
access-list 110 deny
ip any host 10.1.1.2
access-list 110 deny
ip any host 10.1.1.3
snmp-server community private RW
Related Commands
Command
Description
more nvram:startup-config
more system:running-config
Syntax Description
Command Modes
Command History
Release
Modification
12.4(15)T
12.2(33)SRC
12.2(33)SXI
Usage Guidelines
Use the show archive config rollback timercommand to view the timed rollback settings, such as the
timer type (idle timer or absolute timer), timer value, and so on, after a timed rollback is configured on a
router.
Examples
The following is sample output from the show archive config rollback timer command:
Router# show archive config rollback timer
Time configured(or reconfigured): 22:50:48 UTC Sat Feb 21 2009
Timer type: absolute timer
Timer value: 2 min
User: console
The table below describes the significant fields in the sample output.
Table 49
Related Commands
Field
Description
Timer type
Timer value
User
Command
Description
configure revert
Syntax Description
all
record-number [end-number]
user username
session session-number
statistics
provisioning
contenttype
plaintext
xml
persistent
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.3(4)T
12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.4(11)T
12.2(33)SXH
12.2(33)SB
If you do not specify the all keyword, you must specify a record number with the record-number argument.
You can optionally specify an end record number with the end-numberargument to display a range of
records. If you use the end-number argument to specify a record number that does not exist, all records
after the starting record number with a record number lower than that specified with the end-number
argument are displayed.
Specifying the provisioningkeyword results in the display appearing as it would in a configuration file,
rather than in tabular format. This output includes commands used to change configuration modes and
logged configuration commands. This output can be used to set up another router if desired.
Examples
The following is sample output from the show archive log config command, which displays configuration
log entry numbers 1 and 2:
Router# show
idx
sess
1
1
2
1
The table below describes the significant fields shown in the display.
Table 50
Field
Description
idx
sess
user@line
Logged command
The following example results in the display of all configuration log files as they would appear in a
configuration file rather than in tabular format. In addition to displaying logged commands, the example
shows the commands used to change configuration modes that are required to correctly apply the logged
commands.
Router# show archive log config all provisioning
archive
log config
logging enable
logging size 200
The following example results in the display of memory usage statistics for the configuration log:
Router# show archive log config statistics
Config Log Session Info:
Number of sessions being tracked: 1
Memory being held: 3910 bytes
Total memory allocated for session tracking: 3910 bytes
Total memory freed from session tracking: 0 bytes
Config Log log-queue Info:
Number of entries in the log-queue: 3
Memory being held in the log-queue: 671 bytes
Total memory allocated for log entries: 671 bytes
Total memory freed from log entries:: 0 bytes
<when>
<absoluteTime>2003-04-23T20:27:19.847Z</absoluteTime>
</when>
</changeInfo>
<changeItem>
<context/>
<enteredCommand>
<cli>interface e0</cli>
</enteredCommand>
<prcResultType>
<prcSuccess>
<change>PRC_CHANGE</change>
</prcSuccess>
</prcResultType>
<oldConfigState>
<cli></cli>
</oldConfigState>
<newConfigState>
<cli>interface e0</cli>
</newConfigState>
</changeItem>
</configChanged>
<configChanged>
<changeInfo>
<user>jdoe</user>
<async>
<port>con_0</port>
</async>
<when>
<absoluteTime>2003-04-23T20:28:19.847Z</absoluteTime>
</when>
</changeInfo>
<changeItem>
<context><cli>interface e0</cli></context>
<enteredCommand>
<cli>ip address 10.1.1.1 255.255.255.0</cli>
</enteredCommand>
<prcResultType>
<prcSuccess>
<change>PRC_CHANGE</change>
</prcSuccess>
</prcResultType>
<oldConfigState/>
<newConfigState>
<cli>ip address 10.1.1.1 255.255.255.0</cli>
</newConfigState>
</changeItem>
</configChanged>
<configChanged>
<changeInfo>
<user>jdoe</user>
<async>
<port>con_0</port>
</async>
<when>
<absoluteTime>2003-04-23T20:29:19.847Z</absoluteTime>
</when>
</changeInfo>
<logComment>end test test1</logComment>
</configChanged>
</configLoggerMsg>
show as5400
To display the hardware details of an application server, use the show as5400command in privileged
EXEC mode.
show as5400
Syntax Description
Command Modes
Command History
Release
Modification
12.4(22)T
Usage Guidelines
The show as5400 command provides complex troubleshooting information that pertains to the platform's
shared references rather than to a specific interface.
Examples
1
0x0000000000000004 0
0xC00285B4 0x608C4ABC (SB1125 Timer 0)
1
0x0000080000000000 22963823
0x00000000 0x608B2F84 (High IRQ interrupt)
3
0x0000800000000000 0
0x00000000 0x60380F88 (OIR Interrupt)
4
0x0000400000000000 0
0x00000000 0x608BD1EC (NRBUS Parity Error)
4
0x0000200000000000 0
0x00000000 0x608BD1EC (IO Error)
4
0x0000004000000000 0
0x00000000 0x608BD1EC (IO_BUS_Parity Error)
4
0x007C00000000E0C2 0
0x00000000 0x608C2FD8 (Spurious Intr ERROR)
4
0x0000000000020000 0
0x00000000 0x608C3A14 (Corrected ECC Error)
4
0x0000000000010000 0
0x00000000 0x608C2A7C (Bad ECC Error Handl)
4
0x0003000000000000 0
0x64A985BC 0x608C2B4C (BCM1125 Host LDT Br)
4
0x0000000000040000 0
0x00000000 0x608C2E04 (BCM1125 IO-Bus Erro)
4
0x0080000000000000 0
0x00000000 0x608C2BD4 (BCM1125 Host PCI Br)
6
0x0000000000000001 0
0x00000000 0x608C2FD8 (Watchdog Timer 0 Ha)
HT 600MHz Retry Count 0
BCM1125H HT Host Bridge, handle=0
BCM bridge, config=0x0
(0x00):dev, vendor id
= 0x0002166D
(0x04):status, command
= 0x00100107
(0x08):class code, revid
= 0x06000003
(0x0C):hdr, lat timer, cls
= 0x00010000
(0x18):bus id registers
= 0x001B0100
(0x1C):secondary status
= 0x00000141
(0x20):mem base/limit
= 0x5FF04300
(0x30):io upper limit/base
= 0x00010001
(0x34):capabilities ptr
= 0x00000040
(0x38):expansion rom bar
= 0x00000000
(0x3C):bridge ctrl
= 0x00020000
(0x40):LDT cmd, cap id,
= 0x20000008
(0x44):Link config/control
= 0x00000020
(0x48):Link frequency
= 0x801F0423
(0x50):SRIcmd, srirxden, sritxden = 0x50211010
(0x54):SRI tx numerator
= 0x0000FFFF
(0x58):SRI rx numerator
= 0x0000FFFF
(0x68):Error status/control
= 0x00009A49
(0x6C):Tx ctrl, databufalloc
= 0x00041515
(0xC8):Tx buffer count max
= 0x00FFFFFF
(0xDC):Rx CRC expected
= 0xBFFFABE0
(0xF0):Rx CRC received
= 0x7FF3FFFD
BCM PCI Host Bridge:
bus_no=0, device_no=0
DeviceID=0x0001, VendorID=0x166D, Cmd=0x0146, Status=0x02A0
Cls=0x06/0x00/0x00, Rev=0x03, LatencyTimer=0x2C, CacheLineSize=0x10
BaseAddr0=0x60000008, BaseAddr1=0x00000000, MaxLat=0x00, MinGnt=0x00
SubsysDeviceID=0x0000, SubsysVendorID=0xFFFF, ErrorAddr=0x00030400
Additional Status = 0x00000020
PLX HT2PCI Bridge A for PCM Tracer & DFC 2,4,6, handle=0
PLX HT7520 bridge, config=0x0
(0x00):dev, vendor id
= 0x74501022
(0x04):status, command
= 0x02300107
(0x08):class code, revid
= 0x06040012
(0x0C):hdr, lat timer, cls
= 0x00810000
(0x18):bus id registers
= 0xF80E0201
(0x1C):secondary status
= 0x02200141
(0x20):mem base/limit
= 0x4FF04300
(0x30):io upper limit/base
= 0x00010001
(0x34):capabilities ptr
= 0x000000A0
(0x3C):bridge ctrl
= 0x00020000
(0x40):miscellaneous
= 0x00010004
(0x4C):prefetch ctrl
= 0x00000446
(0xC0):ht cmd, cap id
= 0x00410008
(0xC4):link cfg/ctrl side a
= 0x00112020
(0xC8):link cfg/ctrl side b
= 0x770020D0
(0xCC):link freq ctrl side a = 0x00350422
(0xD0):link freq ctrl side b = 0x00350402
PLX HT2PCI Bridge B, for DFC 1,3,5,7
(0x00):dev, vendor id
= 0x74501022
(0x04):status, command
= 0x02300107
(0x08):class code, revid
= 0x06040012
(0x0C):hdr, lat timer, cls
= 0x00810000
(0x18):bus id registers
= 0xF81B0F01
(0x1C):secondary status
= 0x022001A1
(0x20):mem base/limit
= 0x5FF05000
(0x30):io upper limit/base
= 0x00010001
(0x34):capabilities ptr
(0x3C):bridge ctrl
(0x40):miscellaneous
(0x4C):prefetch ctrl
RTC chip is DS1337
=
=
=
=
0x000000A0
0x00020000
0x000B0004
0x00000446
The table below describes the significant fields shown in the display.
Table 51
Related Commands
Field
Description
Level
Mask
Maskable interrupt.
Count
Interrupt count.
Handler
RTC chip
Command
Description
as
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
The following is sample output from the show async bootp command:
Router#
show async bootp
The following extended data will be sent in BOOTP responses:
bootfile (for address 192.168.1.1) pcboot
bootfile (for address 172.16.1.111) dirtboot
subnet-mask 255.255.0.0
time-offset -3600
time-server 192.168.1.1
The table below describes the significant fields shown in the display.
Table 52
Field
Description
bootfile... pcboot
subnet-mask 255.255.0.0
Subnet mask.
time-offset -3600
time-server 192.168.1.1
Related Commands
Command
Description
async-bootp
Syntax Description
Command Modes
Command History
Release
Modification
12.4(15)T
Usage Guidelines
Use the show autoupgrade configuration unknown command to view any invalid start-up configuration.
This command prints invalid start-up configuration data only when run from an an image which was
upgraded using the Auto-Upgrade Manager. This command output is useful when you are upgrading to an
image with a different feature set.
Examples
The following example shows how to view the invalid start-up configuration lines that the Cisco IOS
software image, upgraded on the router using AUM, does not understand:
Router# show autoupgrade configuration unknown
! Config Lines not understood by the current image:
voice-card 0
no dspfarm
crypto pki trustpoint aum_cisco_ca
enrollment terminal
revocation-check none
crypto pki certificate chain aum_cisco_ca
certificate ca 40DCB71E54EE24CBE5326F8006BBA4F6 nvram:SecureServer#A4F6CA.cer
no ip http secure-server
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
Total 9 Invalid Config Lines
Router#
Related Commands
Command
Description
show bcm560x
To display the BCM560x hardware table information, use the show bcm560X command in user EXEC or
privileged EXEC mode.
show bcm560x name {offset | all} [raw]
Syntax Description
Command Modes
Command History
Examples
name
offset
all
raw
Release
Modification
12.4(15)T
show bootflash:
To display information about the bootflash: file system, use the show bootflash: command in user EXEC
or privileged EXEC mode.
show bootflash: [all | chips | filesys]
Syntax Description
all
chips
filesys
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This example shows how to display information about the file system status:
Router>
show bootflash: filesys
-------- F I L E
S Y S T E M
S T A T U S -------Device Number = 0
DEVICE INFO BLOCK: bootflash
Magic Number
= 6887635
File System Vers = 10000
(1.0)
Length
= 1000000
Sector Size
= 40000
Programming Algorithm = 39
Erased State
= FFFFFFFF
File System Offset
= 40000
Length = F40000
MONLIB Offset
= 100
Length = C628
Bad Sector Map Offset = 3FFF8
Length = 8
Squeeze Log Offset
= F80000
Length = 40000
Related Commands
Command
Description
delete
Command
Description
squeeze
show bootvar
To display the contents of the BOOT variable, the name of the configuration file pointed to by the
CONFIG_FILE variable, the contents of the BOOTLDR variable, and the configuration register setting, use
the show bootvar command in user EXEC or privileged EXEC mode.
show bootvar
Syntax Description
Command Modes
Command History
Usage Guidelines
Release
Modification
11.3 AA
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
BOOT
CONFIG_FILE
BOOTLDR
The BOOT variable specifies a list of bootable images on various devices. The CONFIG_FILE variable
specifies the configuration file used during system initialization. The BOOTLDR variable specifies the
flash device and filename containing the rxboot image that ROM uses for booting. You set these variables
with the boot system, boot config, and boot bootldr global configuration commands, respectively.
When you use this command on a device with multiple Route Switch Processor (RSP) cards (Dual RSPs),
this command also shows you the variable settings for both the master and slave RSP card.
Cisco 7600 Series Router
The show bootvar command displays information about the BOOT environmental variable.
The command output depends on how you configure the boot statement as follows:
If you enter the boot system flash bootflash: sup720_image command in the boot configuration, then
the show bootvar command output displays the bootflash information.
If you enter the boot system flash sup-bootflash: sup720_image command in the boot configuration,
then the show bootvar command output displays the sup-bootflash information. This action is the
correct way of configuring the boot statement.
The show bootvar command is available from the switch processor command-line interface (CLI) and the
route processor CLI. From the switch processor CLI, the display is always bootflash. With either the
bootflash or the sup-bootflash boot statement, the switch boots correctly. You should use sup-bootflash in
the boot configuration statement because the image is stored in the switch processor bootflash; the route
processor sees the image as sup-bootflash.
The number displayed after the image name (for example, c6sup12-js-mz.121-13.E,12) indicates the
number of times that the Cisco 7600 series router tries to reboot the file before giving up.
Examples
In this example, the BOOT variable contains a null string; that is no bootable images are specified.
The CONFIG_FILE variable points to the configuration file in NVRAM as the startup (initialization)
configuration. The run-time value for the CONFIG_FILE variable points to the router-configuration file on
the flash memory card inserted in the first slot of the RSP card. That is, during the run-time configuration,
you have modified the CONFIG_FILE variable using the boot config command, but you have not saved
the run-time configuration to the startup configuration. To save your run-time configuration to the startup
configuration, use the copy system:running-config nvram:startup-config command. If you do not save
the run-time configuration to the startup configuration, then the system reverts to the saved CONFIG_FILE
variable setting for initialization information upon reload. In this sample, the system reverts to NVRAM for
the startup configuration file.
The BOOTLDR variable does not yet exist. That is, you have not created the BOOTLDR variable using the
boot bootldr global configuration command.
The following example is output from the show bootvar command for a Cisco 7513 router configured for
high system availability (HSA):
Router# show bootvar
BOOT variable =
CONFIG_FILE variable =
Current CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
current slave is in slot 7
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
The table below describes the significant fields shown in the displays.
Table 53
Field
Description
BOOT variable
CONFIG_FILE variable
BOOTLDR variable
Configuration register
The number displayed after the image name (for example, c6sup12-js-mz.121-13.E,12) indicates the
number of times that the Cisco 7600 series router tries to reboot the file before giving up.
Related Commands
Command
Description
boot bootldr
boot bootstrap
boot config
boot system
Command
Description
copy
show version
show buffers
To display detailed information about the buffer pools on the network server when Cisco IOS, Cisco IOS
Software Modularity, or Cisco IOS XE images are running, use the show buffers command in user EXEC
or privileged EXEC mode.
show buffers [{address hex-address | failures | pool pool-name | detailed | processes | {all |
assigned [process-id] | free | old | input-interface interface-type interface-number} | [pool poolname]} [dump | header | packet | location pool-location]]
Cisco Catalyst 4500e Series Switches running IOS XE software
show buffers [detailed process id {address hex-address | all | assigned | failures | free | inputinterface interface-type interface-number | old | pool pool-name} [dump | header | packet | location
pool-location]]
Syntax Description
address
hex-address
failures
pool
pool-name
detailed process
processes
all
assigned
process-id
free
old
input-interface
interface-type
interface-number
dump
header
packet
location pool-location
Command Default
Command Modes
Command History
Examples
Release
Modification
10.0
12.3
12.2(18)SXF4
12.2(33)SRA
Example output varies between Cisco IOS, Cisco IOS Software Modularity, and Cisco IOS XE software
images. To view the appropriate output, choose one of the following sections:
The following is sample output from the show buffers command with no arguments, showing onlybuffer
pool information for Huge buffers. This output shows a highest total of five Huge buffers created five days
and 18 hours before the command was issued.
Router# show buffers
Huge buffers, 18024 bytes (total 5, permanent 0, peak 5 @ 5d18h):
4 in free list (3 min, 104 max allowed)
0 hits, 1 misses, 101 trims, 106 created
0 failures (0 no memory)
The following is sample output from the show buffers command with no arguments, showing only buffer
pool information for Huge buffers. This output shows a highest total of 184 Huge buffers created one hour,
one minute, and 15 seconds before the command was issued.
Router# show buffers
Huge buffers, 65280 bytes (total 4, permanent 2, peak 184 @ 01:01:15):
The following is sample output from the show buffers command with an interface type and interface
number:
Router# show buffers Ethernet 0
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
48 hits, 0 fallbacks
Field
Description
Buffer elements
free list
max allowed
hits
misses
created
Middle buffers
Big buffers
VeryBig buffers
Large buffers
Huge buffers
total
permanent
Field
Description
peak
free list
min
max allowed
hits
misses
trims
created
permanent
free list
min
max allowed
hits
Field
Description
fallbacks
failures
no memory
The table below describes the significant fields shown in the display that are different from the fields in the
first table.
Table 55
Field
Description
total
hits
misses
total
free list
hits
misses
Field
Description
trims
created
failures
0 failures (0 no memory)
BIPC small buffers, 128 bytes (total 250, permanent 250):
250 in free list (250 min, 250 max allowed)
92 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
BIPC middle buffers, 600 bytes (total 300, permanent 300):
300 in free list (300 min, 300 max allowed)
36 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
CF Middle buffers, 600 bytes (total 100, permanent 100):
100 in free list (100 min, 200 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Syslog ED Pool buffers, 600 bytes (total 132, permanent 132):
131 in free list (132 min, 132 max allowed)
5 hits, 0 misses
CF Big buffers, 1536 bytes (total 25, permanent 25):
25 in free list (25 min, 50 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
BIPC buffers, 4096 bytes (total 2, permanent 2):
2 in free list (1 min, 8 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
IPC Emergency buffers, 4096 bytes (total 301, permanent 300, peak 302 @ 01:05:07):
301 in free list (300 min, 300 max allowed)
39 hits, 1 fallbacks, 66 trims, 67 created
0 failures (0 no memory)
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
CF VeryBig buffers, 4520 bytes (total 2, permanent 2):
2 in free list (2 min, 4 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
CF Large buffers, 5024 bytes (total 1, permanent 1):
1 in free list (1 min, 2 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
BIPC Medium buffers, 16384 bytes (total 5, permanent 5):
5 in free list (5 min, 5 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
BIPC Large buffers, 65535 bytes (total 2, permanent 2):
2 in free list (2 min, 2 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
IPC small buffers, 128 bytes (total 250, permanent 250):
228 in free list (250 min, 250 max allowed)
124 hits, 0 fallbacks
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
IPC middle buffers, 600 bytes (total 200, permanent 200):
200 in free list (200 min, 200 max allowed)
293 hits, 0 fallbacks
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
IPC buffers, 4096 bytes (total 300, permanent 300):
298 in free list (300 min, 300 max allowed)
72 hits, 0 fallbacks
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
IPC Medium buffers, 16384 bytes (total 30, permanent 30):
30 in free list (30 min, 30 max allowed)
100 hits, 0 fallbacks
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
IPC Large buffers, 65535 bytes (total 13, permanent 13):
11 in free list (13 min, 13 max allowed)
19 hits, 0 misses
0 max cache size, 0 in cache
0 hits in cache, 0 misses in cache
Header pools:
Catalyst 4000 buffers, 0 bytes (total 14600, permanent 14600):
The following is sample shows how to run the show buffers detailed command on a Cisco Catalyst 4500e
switch, using a Cisco IOS image from Cisco IOS XE Release 3.1.0.SG and later releases and the various
keywords and arguments (Explained in the Syntax Description Table) available.
Switch#
Switch#show buffers ?
detailed Show detailed buffer statistics
|
Output modifiers
<cr>
Switch#show buffers detailed ?
process Show detailed process buffer info
Switch#show buffers detailed process ?
iosd IOSd Process
Switch#show buffers detailed process iosd ?
address
Buffer at a given address
all
All buffers
assigned
Buffers in use
failures
Buffer allocation failures
free
Buffers available for use
input-interface Buffers assigned to an input interface
old
Buffers older than one minute
pool
Buffers in a specified pool
|
Output modifiers
<cr>
show c2600
To display information for troubleshooting the Cisco 2600 series router, use the show c2600 command in
EXEC mode.
show c2600
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 XA
12.2(33)SRA
Usage Guidelines
The show c2600 command provides complex troubleshooting information that pertains to the platforms
shared references rather than to a specific interface.
Examples
Name
Xilinx bridge error interrupt
MPC860 TIMER INTERRUPT
16552 Con/Aux Interrupt
PA Network Management Int Handler
Timebase Reference Interrupt
PA Network IO Int Handler
MPC860 CPM INTERRUPT
Xilinx bridge error interrupt
]
]
]
]
]
]
]
]
Current Level = 00
= 00000000
= 000003E8
=
0
IDMA Status:
Requests = 00000349
Drops
= 00000000
Complete = 00000349
Post Coalesce Frames = 00000349
Giant
= 00000000
Available Blocks = 256/256
ISP Status:
Version string burned in chip: "A986122997"
New version after next program operation: "B018020998"
ISP family type: "2096"
ISP chip ID: 0x0013
Device is programmable
The table below describes the significant fields shown in the display.
Table 56
Field
Description
Interrupts
Assigned Handlers
Vect
Handler
# of Ints
Name
SIU_IRQ_MASK
Spurious IRQs
Interrupt Throttling:
Throttle Count
Field
Description
Timer Count
Netint usec
Active
Configured
Longest IRQ
IDMA Status
Requests
Drops
Complete
Giant
Available Blocks
ISP Status
Related Commands
Field
Description
ISP chip ID
Device is programmable
Command
Description
show context
show c7200
To display information about the CPU and midplane for Cisco 7200 series routers, use the show c7200
command in EXEC mode.
show c7200
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
12.2(33)SRA
Usage Guidelines
You can use the output of this command to determine whether the hardware version level and upgrade is
current. The information is generally useful for diagnostic tasks performed by technical support only.
Examples
A0
170-43690-170
170-170-170
60 3E 28
AA AA AA
Board revision A0
Part number
73-1536-02
RMA number
00-00-00
49 06 00 02 00 00 00 00
FF FF FF FF FF FF FF FF
show catalyst6000
To display the information about the chassis, use the show catalyst6000 command in user EXEC or
privileged EXEC mode.
show catalyst6000 {all | chassis-mac-address | switching-clock | traffic-meter}
Syntax Description
all
chassis-mac-address
switching-clock
traffic-meter
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(33)SXI
If you enter the switching-clock keywords, the output displays whether switching of the redundant clock
sources on the backplane is allowed if the active clock source fails.
There are either 64 or 1024 MAC addresses that are available to support the software features. You can
enter the show catalyst6000 chassis-mac-address command to display the MAC-address range on your
chassis.
In Cisco IOS Release 12.2(33)SXI and later releases, the traffic monitor status information is displayed in
the output. In earlier releases, only the current and peak traffic-meter readings are displayed.
Examples
This example shows how to display the MAC-address ranges and the current and peak traffic-meter
readings:
Router>
show catalyst6000 all
chassis MAC addresses: 64 addresses from 0001.6441.60c0 to 0001.6441.60ff
traffic meter =
0% Never cleared
peak =
0% reached at 08:14:38 UTC Wed Mar 19 2003
switching-clock: clock switchover and system reset is allowed
Router>
The following example shows how to display the current and peak traffic-meter readings and the traffic
monitor status:
Router
>
show catalyst6000 traffic-meter
traffic meter =
0% Never cleared
peak =
0%
reached at 10:54:49 UTC Wed Mar 19 2008
---=== Traffic Utilization Monitor Status ===--State Interval Threshold MsgCount LastMsgTime
----------------------------------------------------------------------------Backplane
Off
60s
80%
0
-Fpoe#0 In
Off
60s
80%
0
-out
Off
60s
80%
0
-Fpoe#1 In
Off
60s
80%
0
-out
Off
60s
80%
0
-Fpoe#2 In
Off
60s
80%
0
-out
Off
60s
80%
0
-Fpoe#3 In
Off
60s
80%
0
-out
Off
60s
80%
0
-Fpoe#4 In
Off
60s
80%
0
-out
Off
60s
80%
0
-.
.
.
Fpoe#19 In
Off
60s
80%
0
-out
Off
60s
80%
0
-Router
>
This example shows how to display the failure recovery mode of the switching clock:
Router> show catalyst6000 switching-clock
switching-clock: clock switchover and system reset is allowed
Router>
Related Commands
Command
Description
monitor traffic-utilbackplane
show fm summary
show cls
To display the current status of all Cisco link services (CLS) sessions on the router, use the show
clscommand in EXEC mode.
show cls [brief]
Syntax Description
brief
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
11.0
12.2(33)SRA
The Cisco link service (CLS) is used as the interface between data link users (DLUs), such as DLSw, LAN
Network Manager (LNM), downstream physical unit (DSPU), and SNASw, and their corresponding data
link circuits (DLCs) such as Logic Link Control (LLC), VDLC, and Qualified Logic Link Control (QLLC).
Each DLU registers a particular service access point (SAP) with CLS, and establishes circuits through CLS
over the DLC.
The show cls command displays the SAP values associated with the DLU and the circuits established
through CLS.
For further information about CLS, use the Release 12.2 Cisco IOS Bridging and IBM Networking
Configuration Guide.
Examples
The following is sample output from the show cls brief command:
IBD-4500B# show cls brief
DLU user:SNASW
SSap:0x04 VDLC VDLC650
DTE:1234.4000.0001 1234.4000.0002 04 04
DLU user:DLSWDLUPEER
DLU user:DLSWDLU
Bridging VDLC VDLC1000
Related Commands
Command
Description
stun peer-name
show config id
The configuration change tracking identifier (CTID) assigns a version number to each saved version of the
running-config file. To display output about the versions, use the show config idcommand in privileged
EXEC mode.
show config id [detail]
Syntax Description
detail
Command Default
This command is disabled by default. If this command is not entered, the management system has to query
the device for the current running-config file and then compare the results to the last known configuration
to determine if a change has been made.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SRC
12.2(33)SB
12.4(20)T
This configuration infrastructure command assigns a version number that is updated every time the
running-config file is changed. This version number is called the configuration change tracking identifier or
CTID. The CTID can be used to compare configuration files to track configuration changes and take
appropriate actions (for example, a configuration rollback). Config Logger can also use the CTID to
determine if there have been any changes to the running-config file.
CTID makes the management system more efficient by presenting information that indicates a change has
been made to the running-config file. Without CTID, the management system has to query the device for
the current running-config file and then compare the results to the last known configuration to determine if
a change has been made.
Examples
The following example shows that the current running-config file is version 4 and that this file was saved
on June 15, 2006 at 7.572 seconds after 3:02 p.m.:
Router# show config id
version:4 time:2006-06-15T15:02:07.572Z
The following example shows that the current running-config file is version 9 and that this file was last
saved on June 18, 2006 at 34.431 seconds after 6:34 p.m. The file was saved by the system and changed
from Init:
Router# show config id detail
Configuration version : 9
Last change time : 2006-06-18T18:34:34.431Z
Changed by user : system
Changed from process : Init
Related Commands
Command
Description
show running-config
show configuration id
To display output about configuration versions, use the show configuration idcommand in privileged
EXEC mode.
show configuration id [detail]
Syntax Description
detail
Command Default
This command is disabled by default. If this command is not entered, the management system has to query
the device for the current running-config file and then compare the results to the last known configuration
to determine if a change has been made.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SRC
12.2(33)SB
12.4(20)T
This configuration infrastructure command assigns a version number that is updated every time the
running-config file is changed. This version number is called the configuration change tracking identifier
(CTID). The CTID assigns a version number to each saved version of the running-config file. The CTID
can be used to compare configuration files to track configuration changes and take appropriate actions (for
example, a configuration rollback). Config Logger can also use the CTID to determine if there have been
any changes to the running-config file.
CTID makes the management system more efficient by presenting information that indicates a change has
been made to the running-config file. Without CTID, the management system has to query the device for
the current running-config file and then compare the results to the last known configuration to determine if
a change has been made.
Examples
The following example shows that the current running-config file is version 4 and that this file was saved
on June 15, 2006 at 7.572 seconds after 3:02 p.m.:
Router# show configuration id
version:4 time:2006-06-15T15:02:07.572Z
The following example shows that the current running-config file is version 9 and that this file was last
saved on June 18, 2006 at 34.431 seconds after 6:34 p.m. The file was saved by the system and changed
from Init. The field descriptions are self-explanatory.
Router# show configuration id detail
Configuration version : 9
Last change time : 2006-06-18T18:34:34.431Z
Changed by user : system
Changed from process : Init
Related Commands
Command
Description
show running-config
Syntax Description
Command Modes
Privileged EXEC(#)
Command History
Release
Modification
12.2(25)S
12.3(14)T
Examples
12.0(31)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SB
The following is sample output from the show configuration lockcommand when the running
configuration file is locked by another user.
Cisco IOS Release 12.2(25)S, Release 12.2(28)SB, Release 12.3(14)T, and Later Releases
Router# configure terminal
The following is sample output from the show configuration lockcommand when the running
configuration file is not locked by another user.
Router# show configuration lock
Parser Configure Lock
--------------------Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
The table below describes the significant fields shown in the displays.
Table 57
Field
Description
Owner PID
User
Owners username.
TTY
Type
State
Class
Count
Pending Requests
Remote ip address
The following example shows how to configure the configuration file for single user auto configuration
mode (using the configuration mode exclusive auto command). Use the configure terminalcommand to
enter global configuration mode and lock the configuration mode exclusively. Once the Cisco IOS
configuration mode is locked exclusively, you can verify the lock using the show configuration
lockcommand.
Router# configure terminal
Router(config)# configuration mode exclusive auto
Router(config)# end
Router# configure terminal
Router(config)# show configuration lock
Parser Configure Lock
Owner PID
: 10
User
: User1
TTY
: 3
Type
: EXCLUSIVE
State
: LOCKED
Class
: Exposed
Count
: 0
Pending Requests : 0
User debug info : 0
Related Commands
Command
Description
configure replace
show context
To display information stored in NVRAM when an unexpected system reload (system exception) occurs,
use the show context command in user EXEC or priviledged EXEC mode.
show context [summary | all | slot slot-number [crash-index] [all] [debug]]
Syntax Description
Command Modes
summary
all
debug
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
10.3
11.2 GS
12.2(33)SRA
The display from the show context command includes the following information:
Note
This command is primarily for use by Cisco technical support representatives for analyzing unexpected
system reloads.
Output for this command will vary by platform. Context information is specific to processors and
architectures. For example, context information for the Cisco 2600 series router differs from that for other
router types because the Cisco 2600 runs with an M860 processor.
Examples
The following is sample output from the show context command following a system failure:
Router> show context
System was restarted by error - a Software forced crash, PC 0x60189354
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Image text-base: 0x60010900, data-base: 0x6073E000
Stack trace from system failure:
FP: 0x60AEA798, RA: 0x60189354
FP: 0x60AEA798, RA: 0x601853CC
FP: 0x60AEA7C0, RA: 0x6015E98C
FP: 0x60AEA7F8, RA: 0x6011AB3C
FP: 0x60AEA828, RA: 0x601706CC
FP: 0x60AEA878, RA: 0x60116340
FP: 0x60AEA890, RA: 0x6011632C
Fault History Buffer:
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Signal = 23, Code = 0x24, Uptime 00:04:19
$0 : 00000000, AT : 60930120, v0 : 00000032, v1 : 00000120
a0 : 60170110, a1 : 6097F22C, a2 : 00000000, a3 : 00000000
t0 : 60AE02A0, t1 : 8000FD80, t2 : 34008F00, t3 : FFFF00FF
t4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 11010132
s0 : 00000006, s1 : 607A25F8, s2 : 00000001, s3 : 00000000
s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 6097F755
t8 : 600FABBC, t9 : 00000000, k0 : 30408401, k1 : 30410000
gp : 608B9860, sp : 60AEA798, s8 : 00000000, ra : 601853CC
EPC : 60189354, SREG : 3400EF03, Cause : 00000024
Router>
The following is sample output from the show context summary command on a Cisco 12012 router. The
show context summary command displays a summary of all the crashes recorded for each slot (line card).
Router# show context summary
CRASH INFO SUMMARY
Slot 0 : 0 crashes
Slot 1 : 0 crashes
Slot 2 : 0 crashes
Slot 3 : 0 crashes
Slot 4 : 0 crashes
Slot 5 : 0 crashes
Slot 6 : 0 crashes
Slot 7 : 2 crashes
1 - crash at 18:06:41 UTC Tue Nov 5 1996
2 - crash at 12:14:55 UTC Mon Nov 4 1996
Slot 8 : 0 crashes
Slot 9 : 0 crashes
Slot 10: 0 crashes
The following is sample output from the show contextcommand following an unexpected system reload on
a Cisco 2600 series router.
router# show context
S/W Version: Cisco IOS Software
Cisco IOS (tm) c2600 Software (c2600-JS-M), Released Version 11.3(19980115:184921]
Copyright (c) 1986-2003 by Cisco Systems, Inc.
Compiled Thu 15-Jan-98 13:49 by mmagno
Exception occurred at: 00:02:26 UTC Mon Mar 1 1993
Exception type: Data TLB Miss (0x1200)
CPU Register Context:
PC = 0x80109964 MSR = 0x00009030 CR = 0x55FFFD35 LR
= 0x80109958
CTR = 0x800154E4 XER = 0xC000BB6F DAR = 0x00000088 DSISR = 0x00000249
DEC = 0x7FFFDFCA TBU = 0x00000000 TBL = 0x15433FCF IMMR = 0x68010020
R0 = 0x80000000 R1 = 0x80E80BD0 R2 = 0x80000000 R3
= 0x00000000
R4 = 0x80E80BC0 R5 = 0x40800000 R6 = 0x00000001 R7
= 0x68010000
R8 = 0x00000000 R9 = 0x00000060 R10 = 0x00001030 R11
= 0xFFFFFFFF
R12 = 0x00007CE6 R13 = 0xFFF379E8 R14 = 0x80D50000 R15
= 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19
= 0x00000000
R20 = 0x00000000 R21 = 0x00000001 R22 = 0x00000010 R23
= 0x00000000
R24 = 0x00000000 R25 = 0x80E91348 R26 = 0x01936010 R27
= 0x80E92A80
R28 = 0x00000001 R29 = 0x019BA920 R30 = 0x00000000 R31
= 0x00000018
Stack trace:
Frame 00: SP = 0x80E80BD0
PC = 0x80109958
Frame 01: SP = 0x80E80C28
PC = 0x8010A720
Frame 02: SP = 0x80E80C40
PC = 0x80271010
Frame 03: SP = 0x80E80C50
PC = 0x8025EE64
Frame 04: SP = 0x80DEE548
PC = 0x8026702C
Frame 05: SP = 0x80DEE558
PC = 0x8026702C
The table below describes the significant fields shown in the display.
Table 58
Related Commands
Field
Description
S/W Version
Exception occurred at
Exception type
Stack trace
Command
Description
show processes
Command
Description
show stacks
Syntax Description
atm slot-number
clock
csar [register
csc-fpga
dp83800
fab-clk
fia register
Command Modes
Command History
queues [slot-number
sca
xbar
Privileged EXEC
Release
Modification
11.2 GS
12.2(33)SRA
Usage Guidelines
This information provided by this command is intended for use only by technical support representatives in
analyzing system failures in the field.
Examples
The following is sample output from the show controllers pos command for a Cisco 12012:
Router# show controllers pos 7/0
POS7/0
SECTION
LOF = 2
LOS = 0
Active Alarms: None
LINE
AIS = 2
RDI = 2
Active Alarms: None
PATH
AIS = 2
RDI = 4
LOP = 0
PSE = 8
Active Alarms: None
APS
COAPS = 3
PSBF = 2
State: PSBF_state = False
BIP(B1) = 5889
FEBE = 146
BIP(B2) = 2106453
FEBE = 63
NSE = 3
BIP(B3) = 3216
NEWPTR = 2
Related Commands
Command
Description
clear controllers
Syntax Description
atm
port-number
all
sar
summary
fia
register
frfab
tofab
bma
microcode
mis-inst
register
qelem
start-queue-element
end-queue-element
qnum
start-queue-number
end-queue-number
queues
statistics
io
l3
pos
framers
queues
registers
rxsram
port-number
queue-start-address
queue-length
txsram
events
clear
punt-sniff
is configured.
Command Modes
Command History
none
word1
word2
punt-verbose
all
Privileged EXEC
Release
Modification
11.2 GS
12.2(33)SRA
12.2(31)SB
Usage Guidelines
Release
Modification
12.2(33)SB
12.0(33)S
This information displayed by this command is of use only to technical support representatives in analyzing
unexpected system failures in the field. It is documented here in case you need to provide the displayed
statistics to an technical support engineer.
Cisco 10000 Series Router Usage Guidelines
In releases prior to Cisco IOS Release 12.2(33)SB, when you configure the t1 loopback remote command
on the local router, the command also displays in the running-config file of the far-end router. This is due to
the route processor (RP) updating an incorrect parameter when it receives the loopback event message from
the line card for loopback requests from the far end.
In Cisco IOS Release 12.2(33)SB, the RP updates the correct parameter and the show controllers command
correctly displays the loopback CLI commands applied on the local end and displays the loopback events
and status received from the line card in response to loopback requests from the far end.
This change in behavior affects the following line cards and is documented in the CSCsm84447 caveat:
In Cisco IOS Release 12.2(33)SB, the output from the show controller command includes line code
information for the 6-port channelized T3 line card and the 8-port E3/DS3 line card. However, because
SONET line cards do not have a direct physical link at the T3 or E3 level, the output from the show
controller t3 command does not include line code information.
In Cisco IOS Release 12.2(31)SB, the output from the show controller command displays line code
information. The output of the show controller t3 command for SONET-based T3 also includes line code
information.
Cisco 12000 Series Router Usage Guidelines
The packets processed by a line card are either sent to a route processor or a line card in the form of Cisco
cells. To track the packets sent to a route processor from a line card is essential for troubleshooting. The
keywords punt-sniff and punt-verbose have been added for the command show controllers events to
identify the packets sent to RP from LC.
By default, the feature is enabled and packets punt to route processor are displayed using the command
show controllers events punt-verbose. To view all the zero and non-zero punt counters use the command
show controllers events punt-verbose all.
To clear all the line card events and counters including resetting the packets to be sniffed to zero, executing
the command show controllers events clear.
Packets sent to route processor from line card can be sniffed by specifying the hexa-decimal value of the
word. Packets can only be sniffed if the word along with the hexa-decimal value is specified. Specifying
the location of the word, sniffs packets from the particular location. To reset the counters of packets to be
sniffed to zero, execute the command show controllers events punt-sniff none.
For example, use the command show controllers events punt-sniff word1 0x60000000 to sniff packets
punt to RP with the hexa-decimal value 0x60000000. As the location is not specified, it searches the entire
buffer for the value 0x60000000. Packets punt to RP can also be sniffed by specifying a particular location
using the command show controllers events punt-sniff word1 0x60000000 34.
Examples
Because you are executing this command on the line card, you must use the execute-on command to use
the show command, or you must connect to the card using the attach command. All examples in this
section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 0
TX SAR (Beta 1.0.0) is Operational;
RX SAR (Beta 1.0.0) is Operational;
Interface Configuration Mode:
STS-12c
Active Maker Channels: total # 6
VCID ChnnlID Type OutputInfo
1
0888
UBR
0C010010
2
0988
VBR
04010020
3
8BC8
UBR
0C010030
4
0E08
UBR
0C010040
10
1288
VBR
040100A0
11
8BE8
VBR
0C0100B0
InPkts
0
0
0
0
0
0
InOAMs
0
0
0
0
0
0
MacString
08882000AAAA030000000800
09882000
8BC82000AAAA030000000800
0E082000AAAA030000000800
12882000
8BE82000AAAA030000000800
The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllers
Interface POS0
Hardware is BFLC POS
lcpos_instance struct
60311B40
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
Interface POS1
Hardware is BFLC POS
lcpos_instance struct
603142E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
.
.
.
Router#
The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framers
Framer 0, addr=0x12000400:
master reset
C0
master config
1F
rrate sts3c trate sts3c fixptr
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
hcsadd
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
tnull
SPTB status
00
Framer 1, addr=0x12000600:
master reset
C0
master config
1F
rrate sts3c trate sts3c fixptr
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
hcsadd
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
tnull
SPTB status
00
Framer 2, addr=0x12000800:
master reset
C0
master config
1F
rrate sts3c trate sts3c fixptr
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
hcsadd
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
tnull
SPTB status
00
.
.
.
Router#
The following is partial sample output from the show controllers fia command:
Router# execute-on slot 7 show controllers fia
========= Line Card (Slot 7) =======
Fabric configuration: Full bandwidth redundant
Master Scheduler: Slot 17
From Fabric FIA Errors
----------------------redund fifo parity 0
redund overflow 0
crc32 lkup parity 0
cell parity
0
0
1
2
3
----------------------------los
0
0
0
0
crc16 0
0
0
0
To Fabric FIA Errors
----------------------sca not pres 0
req error
0
grant parity 0
multi req
0
cntrl parity 0
uni req
0
multi fifo
0
empty dst req 0
cell drops 0
crc32
0
4
-------0
0
uni fifo overflow
uni fifo undrflow
crc32 lkup parity
handshake error
0
0
0
0
The following is a sample output from the show controllers events punt-verbose command:
Router# execute-on slot 7 show controllers events punt-verbose
RP Punted L2 Statistics in Verbose
-----------------------------------HDLC Encap
: 927
RP Punted L3 Statistics in Verbose
-----------------------------------ICMP
: 40
UDP
: 441
OSPF
: 211
IPV6
: 40
RP Punted L3 Application Statistics in Verbose
----------------------------------------------LDP
: 441
DF Bit not Set
: 692
The following is a partial sample output from the show controllers events punt-verbose all command
which displays the zero and non-zero value of packets punt to RP from LC:
Router# execute-on slot 7 show controllers events punt-verbose all
RP Punted L2 Statistics in Verbose
-----------------------------------L2 Protocol - 0
: 0
ARPA Encap
: 0
L2 Protocol - 2
: 0
L2 Protocol - 3
: 0
L2 Protocol - 4
: 0
HDLC Encap
: 941
L2 Protocol - 6
: 0
L2 Protocol - 7
: 0
L2 Protocol - 8
: 0
L2 Protocol - 9
: 0
L2 Protocol - 10
: 0
L2 Protocol - 11
: 0
L2 Protocol - 12
: 0
L2 Protocol - 13
: 0
L2 Protocol - 14
: 0
L2 Protocol - 15
: 0
PPP Encap
: 0
L2 Protocol - 17
: 0
L2 Protocol - 18
: 0
L2 Protocol - 19
: 0
Frame Relay Encap
: 0
L2 Protocol - 21
: 0
L2 Protocol - 22
: 0
L2 Protocol - 23
: 0
L2 Protocol - 24
: 0
L2 Protocol - 25
: 0
L2 Protocol - 26
: 0
L2 Protocol - 27
: 0
L2 Protocol - 28
: 0
L2 Protocol - 29
: 0
L2 Protocol - 30
: 0
L2 Protocol - 31
: 0
L2 Protocol - 32
: 0
ATM Encap
: 0
L2 Protocol - 34
: 0
L2 Protocol - 35
: 0
RP Punted L3 Statistics in Verbose
-----------------------------------HOPOPT
: 0
ICMP
: 40
IGMP
: 0
L3 Protocol - 3
: 0
IPINIP
: 0
L3 Protocol - 5
: 0
RP Punted L3 Application Statistics in Verbose
----------------------------------------------MPLS OAM
: 0
FTP
: 0
FTPD
: 0
TFTP
: 0
.....
The following is a sample output from the show controllers events clear command:
Router# execute-on slot 7 show controllers events clear
Drop, switching and reject counters cleared
The following is a sample output from the show controllers events punt-sniff command:
Router# execute-on slot 7 show controllers events punt-sniff
Punt Sniff Statistics
-------------------------------Word
Location
Occurance
0x60000000
34
0
0xB6010102
37
5
Note: Location offset taken from the begining of BufferHeader(32 bytes).
The following is a sample output from the show controllers events punt-sniff word1 0x60000000
command. This command is used to sniff a packet with a hexa-decimal value 0x60000000from the start of
the buffer header of the packet being punt to RP:
Router# execute-on slot 7 show controllers events punt-sniff word1
0x60000000
The following is a sample output from the show controllers events punt-sniff word1 0x60000000
34command. This command is used to sniff a packet with a hexa-decimal value 0x600000000 at the
location 34 from the start of the buffer header of the packet being punt to RP:
Router# execute-on slot 7 show controllers events punt-sniff word1
0x60000000 34
The following is a sample output from the show controllers events punt-sniff none command. This
command is used to clear the counter of packets to be sniffed:
Router# execute-on slot 7 show controllers events punt-sniff none
Related Commands
Command
Description
clear controllers
Syntax Description
Command Modes
Command History
Usage Guidelines
vip slot-number
Privileged EXEC
Release
Modification
11.2
12.2(33)SRA
This command displays the state of syslog error and event logging, including host addresses, and whether
console logging is enabled.
When enabled, trap logging allows messages to be sent to a remote host (a syslog server).
Examples
The following is sample output from the show controllers logging command:
Router# show controllers vip 1 logging
show logging from Slot 1:
Syslog logging:enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0
overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 24 messages logged
Trap logging: level informational, 266 messages logged.
Logging to 209.165.202.129
Exception Logging size: 4096 bytes
Count and timestamp logging messages:disabled
Log Buffer (8192 bytes):
smallest_local_pool_entries = 256, global particles = 5149
highest_local_visible_bandwidth = 155000
00:00:05:%SYS-5-RESTART:System restarted -.
.
.
The table below describes the significant fields shown in the display.
Table 59
Field
Description
Syslog logging
Console logging
Monitor logging
Buffer logging
Trap logging
Related Commands
Command
Description
show logging
Syntax Description
Command Modes
Command History
Usage Guidelines
vip slot-number
Privileged EXEC
Release
Modification
11.2
12.2(33)SRA
Use this command to help collect general information about a VIP card when you are reporting a problem.
This command displays the equivalent of the following show commands for the VIP card:
more system:running-config
show buffers
show controllers
show interfaces
show processes cpu
show processes memory
show stacks
show version
For a sample display of the show controllers tech-support command output, refer to these show
commands.
Related Commands
Command
Description
more system:running-config
show buffers
Command
Description
show controllers
show interfaces
show processes
show stacks
show tech-support
show version
Syntax Description
Command Modes
Command History
Examples
all
first
number-of-entries
last
status
Release
Modification
12.4(24)T
The following is sample output from the show coverage history command. The output is self-explanatory.
Router# show coverage history status
History table size is 23 entries. 0 entries have been used.
Low-level count handler has been called 0 times.
There were 0 entries not traced due to recursion detection.
There were 0 entries not traced due to internal pauses.
Related Commands
Command
Description
coverage history
show data-corruption
To display data inconsistency errors of the present software version, use the show datacorruptioncommand in user EXEC or privileged EXEC mode.
show data-corruption
Syntax Description
Command Modes
Command History
Release
Modification
12.2(22)SE
12.2(33)SRB
12.4(20)T
12.2(33)SXI
Usage Guidelines
Use this command to display all data inconsistency errors or the corrupt data. If there are no data errors, the
No data inconsistency errors have been recorded message is displayed.
Examples
The following is sample output from show data-corruption command. The fields are self-explanatory.
Router# show data-corruption
Data inconsistency records for:
3800 Software (C3845-ADVIPSERVICESK9-M), Version 12.4(24)T, RELEASE
SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Compiled Thu 17-Dec-09 09:02 by xyz
Count
1842
Traceback
60523C58, 616E85FC 60523C58 62A9F648
1: Jun 12 18:24:33.960
2: Jun 12 18:24:33.960
3: Jun 12 18:24:33.960
1842: Jun 19 00:30:51.350
show debugging
To display information about the types of debugging that are enabled for your router, use the show
debugging command in privileged EXEC mode.
show debugging
Syntax Description
Command Modes
Command History
Examples
Release
Modification
11.1
12.3(7)T
12.2(33)SRA
12.2(31)SB2
12.2SX
12.4(20)T
The following is sample output from the show debugging command. In this example, the remote host is not
configured or connected.
Router# show debugging
!
TCP:
TCP Packet debugging is on
TCP ECN debugging is on
!
Router# telnet 10.1.25.234
!
Trying 10.1.25.234 ...
!
00:02:48: 10.1.25.31:11001 <---> 10.1.25.234:23 out ECN-setup SYN
The following is sample output from the show debugging command when user-group debugging is
configured:
Router# show debugging
!
usergroup:
Usergroup Deletions debugging is on
Usergroup Additions debugging is on
Usergroup Database debugging is on
Usergroup API debugging is on
!
The following is sample output from the show debugging command when SNAP debugging is configured:
Router# show debugging
Field
Description
OPTS 4
Field
Description
ECE
CWR
SYN
WIN 4128
cwnd
ssthresh
usergroup
show declassify
To display the state of the declassify function (enabled, in progress, and so forth) and the sequence of
declassification steps that will be performed, use the show declassify command in global configuration
mode.
show declassify
Syntax Description
Note
Command Modes
Command History
Examples
The show declassify command is supported on the Cisco 3200 series routers only.
Global configuration
Release
Modification
12.3(8)YD
12.4(2)T
The following example is sample output for the show declassify command:
Router# show declassify
Declassify facility: Enabled=Yes In Progress=No
Erase flash=Yes Erase nvram=Yes
Obtain memory size
Shutdown Interfaces
Declassify Console and Aux Ports
Erase flash
Declassify NVRAM
Declassify Communications Processor Module
Declassify RAM, D-Cache, and I-Cache
The table below describes the significant fields shown in the display.
Table 61
Field
Description
Enabled
Field
Description
In Progress
Erase flash
Erase nvram
Related Commands
Shutdown Interfaces
Erase flash
Declassify NVRAM
Erase NVRAM.
Scrub the main memory, erase the Data Cache (DCache), and erase the Instruction Cache (I-Cache).
Command
Description
service declassify
Invokes declassification.
show derived-config
To display the composite results of all the configuration commands that apply to an interface, including
commands that come from sources such as static templates, dynamic templates, dialer interfaces, and
authentication, authorization, and accounting (AAA) per-user attributes, use the show derived-config
command in privileged EXEC mode.
show derived-config [interface type number]
Syntax Description
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.1
12.2(33)SRA
15.1(2)S
Configuration commands can be applied to an interface from sources such as static templates, dynamic
templates bound by resource pooling, dialer interfaces, AAA per-user attributes and the configuration of
the physical interface. The show derived-config command displays all the commands that apply to an
interface.
The output for the show derived-configcommand is nearly identical to that of the show running-config
command. It differs when the configuration for an interface is derived from a template, a dialer interface, or
some per-user configuration. In those cases, the commands derived from the template, dialer interface, and
so on, will be displayed for the affected interface.
If the same command is configured differently in two different sources that apply to the same interface, the
command coming from the source that has the highest precedence will appear in the display.
Examples
The following examples show sample output for the show running-config and show derived-config
commands for serial interface 0:23 and dialer interface 0. The output of the show running-config and
show derived-config commands is the same for dialer interface 0 because none of the commands that
apply to that interface are derived from any sources other than the configuration of the dialer interface. The
output for the show running-config and show derived-config commands for serial interface 0:23 differs
because some of the commands that apply to serial interface 0:23 come from dialer interface 0.
Router# show running-config interface Serial0:23
Building configuration...
Current configuration :296 bytes
!
interface Serial0:23
description PRI to ADTRAN (#4444150)
ip unnumbered Loopback0
encapsulation ppp
dialer rotary-group 0
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool old_pool
end
Router# show running-config interface Dialer0
Building configuration...
Current configuration :257 bytes
!
interface Dialer0
description Dialin Users
ip unnumbered Loopback0
no ip proxy-arp
encapsulation ppp
dialer in-band
dialer idle-timeout 30
dialer-group 1
peer default ip address pool new_pool
ppp authentication pap chap callin
end
Router# show derived-config interface Serial0:23
Building configuration...
Derived configuration :332 bytes
!
interface Serial0:23
description PRI to ADTRAN (#4444150)
ip unnumbered Loopback0
encapsulation ppp
dialer rotary-group 0
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool new_pool
ppp authentication pap chap callin
end
Router# show derived-config interface Dialer0
Building configuration...
Derived configuration :257 bytes
!
interface Dialer0
description Dialin Users
ip unnumbered Loopback0
no ip proxy-arp
encapsulation ppp
dialer in-band
dialer idle-timeout 30
dialer-group 1
peer default ip address pool new_pool
ppp authentication pap chap callin
end
The following sample output from the show running-config and show derived-config commands show
service instance and xconnect configurations.
Router# show running-config interface ethernet 0/0
Building configuration...
Current configuration : 201 bytes
!
interface Ethernet0/0
no ip address
service-policy type control mypolicy
service instance dynamic 1 ethernet
encapsulation dot1q 2-99
ethernet subscriber
initiator unclassified vlan
!
end
Router# show derived-config interface ethernet 0/0
Building configuration...
Derived configuration : 306 bytes
!
interface Ethernet0/0
no ip address
service-policy type control mypolicy
service instance dynamic 1 ethernet
encapsulation dot1q 2-99
ethernet subscriber
initiator unclassified vlan
!
service instance 2 ethernet
encapsulation dot1q 22
xconnect 33.33.33.34 12346 encapsulation mpls
!
end
Related Commands
Command
Description
show running-config
Syntax Description
publish
subscribe
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(33)SRA
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine
2.
The CNS subsystem communicates with remote network applications through the CNS-event agent and
follows the publish and subscribe model. An application sets itself up to receive events by subscribing to
the approprate event subject name.
Examples
This example shows how to display the subject with which the diagnostic results is published:
Router# show diagnostic cns publish
Subject: cisco.cns.device.diag_results
Subject: cisco.cns.device.diag_get_results
Related Commands
Command
Description
diagnostic cns
Syntax Description
Command Default
Displays information for all the Gigabit Ethernet WAN interfaces in the Cisco 7600 series router.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(18)SXE
12.2(33)SRA
The sanity check runs a set of predetermined checks on the configuration with a possible combination of
certain system states to compile a list of warning conditions. The checks are designed to look for anything
that seems out of place and are intended to serve as an aid to maintaining the system sanity.
The following is a list of the checks that are run and the action taken when the condition is found:
Checks whether the default gateways are reachable. If so, the system stops pinging.
If a port auto-negotiates to half duplex, the system flags it.
Trunking Checks
If a trunk port has the mode set to on, the system flags it.
If a port is trunking and mode is auto, the system flags it.
If a trunk port is not trunking and the mode is desirable, the system flags it.
If a trunk port negotiates to half duplex, the system flags it.
Channeling Checks
If a port has channeling mode set to on, the system flags it.
If a port is not channeling and the mode is set to desirable, the system flags it.
If a VLAN has a Spanning-Tree root of 32K (root is not set), the system flags it.
If a VLAN has a max age on the Spanning-Tree root that is different than the default, the system flags
it.
If a VLAN has a fwd delay on the Spanning-Tree root that is different than the default, the system
flags it.
If a VLAN has a fwd delay on the bridge that is different than the default, the system flags it.
If a VLAN has a fwd delay on the bridge that is different than the default, the system flags it.
If a VLAN has a hello time on the bridge that is different than the default, the system flags it.
If a port has a port cost that is different than the default, the system flags it.
If a port has a port priority that is different than the default, the system flags it.
UDLD Checks
If a port had receive flow control disabled, the system flags it.
If a trunk port had PortFast enabled, the system flags it.
If a inline power port has any of the following states:
denied
faulty
other
off
The config register on the primary supervisor engine (and on the secondary supervisor engine if
present) must be one of the following values: 0x2 , 0x102, or 0x2102.
The system verifies the bootstring on the primary supervisor engine (and on the secondary supervisor
engine if present). The system displays a message if the bootstring is empty.
The system verifies that every file is specified in the bootstring. The system displays a message if the
file is absent or shows up with a wrong checksum.
If only device : is specified as a filename, then the system verifies that the first file is on the device.
Assorted Checks
Examples
The system displays a message if multicast routing is enabled globally but is not applied to all
interfaces.
The system displays a message if IGMP snooping is disabled and RGMP is enabled.
This example displays samples of the messages that could be displayed with the show diagnostic sanity
command:
Router# show diagnostic sanity
Pinging default gateway 10.6.141.1 ....
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.6.141.1, timeout is 2 seconds:
..!!.
Success rate is 0 percent (0/5)
IGMP snooping disabled please enable it for optimum config.
IGMP snooping disabled but RGMP enabled on the following interfaces,
please enable IGMP for proper config :
Vlan1, Vlan2, GigabitEthernet1/1
Multicast routing is enabled globally but not enabled on the following
interfaces:
GigabitEthernet1/1, GigabitEthernet1/2
A programming algorithm mismatch was found on the device bootflash:
Formatting the device is recommended.
The bootflash: does not have enough free space to accomodate the crashinfo file.
Please check your confreg value : 0x0.
Please check your confreg value on standby: 0x0.
The boot string is empty. Please enter a valid boot string .
Could not verify boot image "disk0:" specified in the boot string on the
slave.
Invalid boot image "bootflash:asdasd" specified in the boot string on the
slave.
Please check your boot string on the slave.
UDLD has been disabled globally - port-level UDLD sanity checks are
being bypassed.
OR
[
The following ports have UDLD disabled. Please enable UDLD for optimum
config:
Fa9/45
The following ports have an unknown UDLD link state. Please enable UDLD
on both sides of the link:
Fa9/45
]
The following ports have portfast enabled:
Fa9/35, Fa9/45
The following ports have trunk mode set to on:
Fa4/1, Fa4/13
The following trunks have mode set to auto:
Fa4/2, Fa4/3
The following ports with mode set to desirable are not trunking:
Fa4/3, Fa4/4
The following trunk ports have negotiated to half-duplex:
Fa4/3, Fa4/4
The following ports are configured for channel mode on:
Fa4/1, Fa4/2, Fa4/3, Fa4/4
The following ports, not channeling are configured for channel mode
desirable:
Fa4/14
The following vlan(s) have a spanning tree root of 32768:
1
The following vlan(s) have max age on the spanning tree root different from
the default:
1-2
The following vlan(s) have forward delay on the spanning tree root different
from the default:
1-2
The following vlan(s) have hello time on the spanning tree root different
from the default:
1-2
The following vlan(s) have max age on the bridge different from the
default:
1-2
The following vlan(s) have fwd delay on the bridge different from the
default:
1-2
The following vlan(s) have hello time on the bridge different from the
default:
1-2
The following vlan(s) have a different port priority than the default
on the port FastEthernet4/1
1-2
The following ports have recieve flow control disabled:
Fa9/35, Fa9/45
The following inline power ports have power-deny/faulty status:
Gi7/1, Gi7/2
The following ports have negotiated to half-duplex:
Fa9/45
The following vlans have a duplex mismatch:
Fas 9/45
The following interafaces have a native vlan mismatch:
interface (native vlan - neighbor vlan)
Fas 9/45 (1 - 64)
The value for Community-Access on read-only operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.
The value for Community-Access on write-only operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.
The value for Community-Access on read-write operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.
Please check the status of the following modules:
8,9
Module 2 had a MINOR_ERROR.
The Module 2 failed the following tests:
TestIngressSpan
The following ports from Module2 failed test1:
1,2,4,48
show disk
To display flash or file system information for a disk, use the show diskcommand in user or privileged
EXEC mode.
show {disk0 | disk1} [all | filesys]
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
disk0
disk1
all
filesys
Release
Modification
12.2
12.3(7)T
12.2(25)S
12.2(33)SRA
The show disk command is supported only on platforms that have a disk file system.
The name of the ATA monlib file may contain a platform name that does not match the platform that you
are using. Different platforms may have a similar or the same name for their ATA monlib file.
Examples
The following example displays information about disk 0. The output is self-explanatory.
Router# show disk0 all
-#- --length-- -----date/time------ path
1
19539160 Jan 27 2004 23:08:40 c7200-is-mz.123-5.7.PI3a
1011679232 bytes available (19546112 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Manufacturer Name
SMART ATA Flash Card
Model Number
SMART ATA FLASH DISK
Serial Number
00000155000000704162
Firmware Revision
V1.01
Number of Heads:
16
Number of Cylinders
1999
Sectors per Track
63
Sector Size
512
Total Sectors
2014992
ATA CARD FORMAT
Number of FAT Sectors 246
Sectors Per Cluster
32
Number of Clusters
62941
Number of Data Sectors 2014789
Base Root Sector
632
Base FAT Sector
140
Base Data Sector
664
ATA MONLIB INFO
Image Monlib size = 67256
Disk monlib size = 71680
Name = c7200-atafslib-m
Monlib Start sector = 2
Monlib End sector = 133
Monlib updated by = C7200-IS-M12.3(5.7)PI3a
Monlib version = 1
show disk0:
To display flash or file system information for a disk located in slot 0, use the show disk0:command in
user EXEC or privileged EXEC mode.
show disk0: [all | filesys]
Syntax Description
Command Modes
Command History
Usage Guidelines
all
filesys
Release
Modification
11.3AA
12.2
12.3(7)T
12.2(25)S
12.2(33)SRA
The show disk0: command is supported only on platforms that have a disk file system located in slot 0.
Use the show disk0: command to display details about the files in a particular ATA PCMCIA flash disk
memory card.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility
Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_tech_note09186a00800a7515.shtml
Note
Examples
The name of the ATA monlib file may contain a platform name that does not match the platform that you
are using. Different platforms may have a similar name or the same name for their ATA monlib file.
The following examples show displays of information about the flash disks or file system information for a
disk. The output is self-explanatory.
c7200# show disk0:
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
c7200# show disk0: all
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
4
Number of Cylinders
984
Sectors per Cylinder
32
Sector Size
512
Total Sectors
125952
ATA CARD FORMAT
Number of FAT Sectors 62
Sectors Per Cluster
8
Number of Clusters
15693
Number of Data Sectors 125812
Base Root Sector
232
Base FAT Sector
108
Base Data Sector
264
ATA MONLIB INFO
Image Monlib size = 73048
Disk monlib size = 55296
Name = NA
Monlib end sector = NA
Monlib Start sector = NA
Monlib updated by = NA
Monlib version = NA
c7200# show disk0: filesys
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
4
Number of Cylinders
984
Sectors per Cylinder
32
Sector Size
512
Total Sectors
125952
ATA CARD FORMAT
Number of FAT Sectors 62
Sectors Per Cluster
8
Number of Clusters
15693
Number of Data Sectors 125812
Base Root Sector
232
Base FAT Sector
108
Base Data Sector
264
ATA MONLIB INFO
Image Monlib size = 73048
Disk monlib size = 55296
Name = NA
Monlib end sector = NA
This example shows how to update and display the time settings on a device using the show disk0
command.
7206-1#
7206-1#sh disk0:
-#- --length-- -----date/time------ path
1
47495056 Aug 8 2009 02:04:06 -08:00 c7200-adventerprisek9-mz.124-24.6.PI11
j
2
29211500 Sep 11 2009 23:09:24 -08:00 c7200-p-mz.CSCsz11391-eagle_cnh
3
0 Aug 24 2009 02:03:40 -08:00 dtdlog
4
16089368 Sep 8 2009 08:53:58 -08:00 c7200-p-mz.CSCsz11391-v122_18_sxf_thro
ttle-test
419250176 bytes available (92807168 bytes used)
7206-1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
7206-1(config)#clock timezone UTC 0 0
7206-1(config)#end
7206-1#
*Sep 12 07:13:56.447: %SYS-6-CLOCKUPDATE: System clock has been updated from 23:13:56 PST
Fri S
ep 11 2009 to 07:13:56 UTC Sat Sep 12 2009, configured from console by console.
7206-1#
7206-1#
7206-1#
*Sep 12 07:13:57.239: %SYS-5-CONFIG_I: Configured from console by console
7206-1#
7206-1#
7206-1#sh disk0
:
-#- --length-- -----date/time------ path
1
47495056 Aug 8 2009 10:04:06 +00:00 c7200-adventerprisek9-mz.124-24.6.PI11j
2
29211500 Sep 12 2009 07:09:24 +00:00 c7200-p-mz.CSCsz11391-eagle_cnh
3
0 Aug 24 2009 10:03:40 +00:00 dtdlog
4
16089368 Sep 8 2009 16:53:58 +00:00 c7200-p-mz.CSCsz11391-v122_18_sxf_throttle-test
419250176 bytes available (92807168 bytes used)
Related Commands
Command
Description
dir disk0:
dir disk1:
show disk1:
show disk1:
To display flash or file system information for a disk located in slot 1, use the show disk1:command in
user EXEC or privileged EXEC mode.
show disk1: [all | filesys]
Syntax Description
Command Modes
Command History
Usage Guidelines
all
filesys
Release
Modification
11.3AA
12.2
12.3(7)T
12.2(25)S
12.2(33)SRA
The show disk1: command is supported only on platforms that have a disk file system. Use the show
disk01: command to display details about the files in a particular ATA PCMCIA flash disk memory card
located in slot 1.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility
Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_tech_note09186a00800a7515.shtml
Note
Examples
The name of the ATA monlib file may contain a platform name that does not match the platform that you
are using. Different platforms may have a similar name or the same name for their ATA monlib file.
The following examples show displays of information about the flash disks or file system information for a
disk. The output is self-explanatory.
c7200# show disk1:
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
c7200# show disk1: all
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
4
Number of Cylinders
984
Sectors per Cylinder
32
Sector Size
512
Total Sectors
125952
ATA CARD FORMAT
Number of FAT Sectors 62
Sectors Per Cluster
8
Number of Clusters
15693
Number of Data Sectors 125812
Base Root Sector
232
Base FAT Sector
108
Base Data Sector
264
ATA MONLIB INFO
Image Monlib size = 73048
Disk monlib size = 55296
Name = NA
Monlib end sector = NA
Monlib Start sector = NA
Monlib updated by = NA
Monlib version = NA
c7200# show disk1: filesys
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
4
Number of Cylinders
984
Sectors per Cylinder
32
Sector Size
512
Total Sectors
125952
ATA CARD FORMAT
Number of FAT Sectors 62
Sectors Per Cluster
8
Number of Clusters
15693
Number of Data Sectors 125812
Base Root Sector
232
Base FAT Sector
108
Base Data Sector
264
ATA MONLIB INFO
Image Monlib size = 73048
Disk monlib size = 55296
Name = NA
Monlib end sector = NA
Related Commands
Command
Description
dir disk0:
dir disk1:
show disk0:
show environment
To display temperature, voltage, fan, and power supply information, use the show environmentcommand
in user EXEC or privileged EXEC mode.
show environment commandshow environment [alarms | all | fans | hardware | last | leds |
power-supply | table | temperature | voltages]
Cisco 7000 Series, Cisco 7200 Series, Cisco 7304, and Cisco 7500 Series
show environment commandshow environment [all | last | table]
Cisco ASR 1000 Series
show environment {all | counters | history sensor | location sensor | sensor sensor | table sensor}
Cisco uBR10012 Routers
show environment [all | last | subslot slot/subslot | table]
Syntax Description
alarms
all
fans
hardware
last
leds
power-supply
table
temperature
voltages
counters
history
location
sensor
sensor
Sensor name.
subslot
slot
subslot
Command Default
Command Modes
Command History
Release
Modification
10.0
11.2 GS
11.3(6)AA
12.2(20)S
12.2(20)S2
Usage Guidelines
Release
Modification
12.4(4)XD
12.2(31)SB2
12.2(33)SCD2
The availability of keywords depends on your system and platform. The command does not support SPAs
on the Cisco 7200 series and on the NPE-G2 in the Cisco 7200 VXR routers.
A routine runs once a minute that reads environmental measurements from sensors and stores the output
into a buffer. For shared port adapters (SPAs), the temperature and voltage sensors are read every few
seconds to get environmental data. The environmental buffer is displayed on the console when you use the
show environment command.
If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is
printed to the system console. The system software queries the sensors for measurements once a minute,
but warnings for a given test point are printed at most once every hour for sensor readings in the warning
range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line
within these time segments, an automatic warning message appears on the console. As noted, you can
query the environmental status with the show environment command at any time to determine whether a
measurement is at the warning or critical tolerance.
A SPA is shut down when any of the SPA environment readings exceed the shutdown threshold.
If a shutdown occurs because of detection of fatal environmental margins, the last measured value from
each sensor is stored in internal nonvolatile memory.
For environmental specifications, refer to the hardware installation and configuration publication for your
individual chassis.
For network processor engines (NPEs), network services engines (NSEs), line cards, and modular services
cards (MSCs), environmental information is recorded in the CISCO-ENVMON-MIB. SPAs are not
supported by the CISCO-ENVMON-MIB. In Cisco IOS Release 12.2(20)S2 and later, the CISCOENTITY-SENSOR-MIB supports environmental information for SPAs, as well as NPEs, NSEs, line cards,
and MSCs.
If the Cisco 12000 series GSR exceeds environmental conditions, a message similar to the following is
displayed on the console:
%GSR_ENV-2-WARNING: Slot 3 Hot Sensor Temperature exceeds 40 deg C;
Check cooling systems
Note
Blower temperatures that exceed environmental conditions do not generate a warning message.
You can also enable Simple Network Management Protocol (SNMP) notifications (traps or informs) to
alert a network management system (NMS) when environmental thresholds are reached using the snmpserver enable traps envmon and snmp-server host global configuration commands.
Whenever Cisco IOS software detects a failure or recovery event from the DRPS unit, it sends an SNMP
trap to the configured SNMP server. Unlike console messages, only one SNMP trap is sent when the failure
event is first detected. Another trap is sent when the recovery is detected.
Cisco AS5300 DRPS software reuses the MIB attributes and traps defined in CISCO-ENVMON-MIB and
CISCO-ACCESS-ENVMON-MIB. CISCO-ENVMON-MIB is supported by all Cisco routers with RPS
units, and CISCO-ACCESS-ENVMON-MIB is supported by the Cisco 3600 series routers.
A power supply trap defined in CISCO-ENVMON-MIB is sent when a failure is detected and when a
failure recovery occurs for the following events: input voltage fail, DC output voltage fail, thermal fail, and
multiple failure events.
A fan failure trap defined in CISCO-ENVMON-MIB is sent when a fan failure or recovery event is
detected by Cisco IOS software.
A temperature trap defined in CISCO-ACCESS-ENVMON-MIB is sent when a board over-temperature
condition is detected by Cisco IOS software.
CISCO-ACCESS-ENVMON-MIB also defines an over-voltage trap. A similar trap is defined in CISCOENVMON-MIB, but it requires the ciscoEnvMonVoltageStatusValue in varbinds. This value indicates the
current value of the voltage in the RPS. With Cisco AS5300 RPS units, the current voltage value is not sent
to the motherboard.
CISCO-ENVMON-MIB is extended to add a new enumerated value, internalRedundant(5), for MIB
attribute ciscoEnvMonSupplySource. This is used to identify a RPS unit.
The temperature history of the Cisco uBR-MC20X20V line card, used in Cisco uBR10012 universal
broadband router, can be viewed using the show environment subslot command. The show environment
subslot command displays the thermal and power status of the Cisco uBR-MC20X20V line card. The slot/
subslot option of the show environment subslot command helps to identify the location of the line card.
Examples
Cisco ASR 1000 Series Routers
In the following example, the show environment all command displays system temperature, voltage, fan,
and power supply conditions. (It does not display environmental information for SPAs.) The State column
in show environment all output should show Normal except for fans where it indicates fan speed. A fan
speed of 65% is normal.
Router# show environment all
Sensor List: Environmental Monitoring
Sensor
Location
State
V1: VMA
F0
Normal
V1: VMB
F0
Normal
V1: VMC
F0
Normal
V1: VMD
F0
Normal
V1: VME
F0
Normal
V1: 12v
F0
Normal
V1: VDD
F0
Normal
V1: GP1
F0
Normal
Reading
1801 mV
1206 mV
1206 mV
1103 mV
1005 mV
11967 mV
3295 mV
905 mV
V2: VMA
V2: VMB
V2: VMC
V2: VMD
V2: VME
V2: VMF
V2: 12v
V2: VDD
V2: GP1
Temp: Inlet
Temp: Asic1
Temp: Exhaust1
Temp: Exhaust2
Temp: Asic2
V1: VMA
V1: VMB
V1: VMC
V1: VMD
V1: VME
V1: VMF
V1: 12v
V1: VDD
V1: GP1
V1: GP2
V2: VMB
V2: 12v
V2: VDD
V2: GP2
Temp: Left
Temp: Center
Temp: Asic1
Temp: Right
V1: VMA
V1: VMB
V1: VMC
V1: VMD
V1: VME
V1: VMF
V1: 12v
V1: VDD
V1: GP1
V1: GP2
V2: VMB
V2: 12v
V2: VDD
V2: GP2
Temp: Left
Temp: Center
Temp: Asic1
Temp: Right
PEM Iout
PEM Vout
PEM Vin
Temp: PEM
Temp: FC
Temp: FM
Temp: FC
V1: VMA
V1: VMB
V1: VMC
V1: VMD
V1: VME
V1: VMF
V1: 12v
V1: VDD
V1: GP1
V1: GP2
Temp: CPU
Temp: Outlet
Temp: Inlet
Temp: Asic1
F0
F0
F0
F0
F0
F0
F0
F0
F0
F0
F0
F0
F0
F0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
P0
P0
P0
P0
P0
P1
P1
R0
R0
R0
R0
R0
R0
R0
R0
R0
R0
R0
R0
R0
R0
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Fan Speed 65%
Normal
Fan Speed 65%
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
3295 mV
2495 mV
1499 mV
1098 mV
1000 mV
1000 mV
11923 mV
3295 mV
751 mV
27 Celsius
44 Celsius
36 Celsius
34 Celsius
40 Celsius
1103 mV
1201 mV
1503 mV
1801 mV
2495 mV
3295 mV
11967 mV
3295 mV
751 mV
903 mV
1201 mV
11967 mV
3291 mV
903 mV
28 Celsius
29 Celsius
42 Celsius
27 Celsius
1103 mV
1201 mV
1503 mV
1801 mV
2495 mV
3295 mV
11953 mV
3291 mV
754 mV
903 mV
1206 mV
11967 mV
3291 mV
905 mV
28 Celsius
30 Celsius
44 Celsius
28 Celsius
37 A
12 V AC
116 V AC
28 Celsius
25 Celsius
1 Celsius
25 Celsius
1118 mV
3315 mV
2519 mV
1811 mV
1513 mV
1220 mV
12011 mV
3300 mV
913 mV
1247 mV
29 Celsius
30 Celsius
25 Celsius
30 Celsius
The following table describes the significant fields shown in the display.
Table 62
Field
Description
Sensor
Sensor name.
Location
Chassis slot.
State
Reading
The following table describes the significant fields shown in the display.
Table 63
Field
Description
Status message
Table 64
Unit is on.
Unit is on.
additional
additional
additional
additional
additional
additional
additional
additional
voltage
voltage
voltage
voltage
voltage
voltage
voltage
voltage
reading
reading
reading
reading
reading
reading
reading
reading
on
on
on
on
on
on
on
on
NPE-G2
NPE-G2
NPE-G2
NPE-G2
NPE-G2
NPE-G2
NPE-G2
NPE-G2
show environment all Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field
Description
Unit is ...
Temperature readings
Field
Description
Voltage readings:
In the following example, the show environment last command displays the previously saved
measurements (readings) from the last environmental reading before the router was shut down. The
command also displays the reason why the router was shut down, which was power supply shutdown in
this case.
Router_npe-g2# show environment last
NPE Inlet previously measured at 26C/78F
NPE Outlet previously measured at 28C/82F
CPU Die previously measured at 56C/132F
+3.30 V previously measured at +3.32
+1.50 V previously measured at +1.48
+2.50 V previously measured at +2.46
+1.80 V previously measured at +1.75
+1.20 V previously measured at +1.17
VDD_CPU previously measured at +1.28
VDD_MEM previously measured at +2.50
VTT previously measured at +1.25
+3.45 V previously measured at +3.39
-11.95 previously measured at -11.93
+5.15 V previously measured at +4.96
+12.15 V previously measured at +12.18
last shutdown reason - power supply shutdown
Table 65
show environment last Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field
Description
In the following example, the show environment table command displays threshold levels in a table format
of the environmental monitor parameters. It displays the high warning, high critical, and high shutdown
temperature thresholds of the NPE inlet, NPE outlet, and CPU Die. It also displays the low and high critical
voltage thresholds, and low and high shut down voltage thresholds for the power rails on the NPE-G2 in the
Cisco 7200 VXR.
Note
The low range temperatures, such as the LowShut, LowCrit, and LowWarn temperature thresholds, are not
checked and are not displayed on the NPE-G2. Also the warning voltage thresholds, such as LowWarn and
HighWarn, are not checked and are not displayed on the NPE-G2.
Router_npe-g2# show environment table
Sample Point LowShut LowCrit LowWarn HighWarn
NPE Inlet
44C/111F
NPE Outlet
49C/120F
CPU Die
75C/167F
System shutdown for NPE Inlet is 80C/176F
System shutdown for NPE Outlet is 84C/183F
System shutdown for CPU Die is 100C/212F
+3.30 V
+2.30
+3.12
+1.50 V
+1.05
+1.40
+2.50 V
+1.71
+2.34
+1.80 V
+1.25
+1.67
+1.20 V
+0.82
+1.13
VDD_CPU
+0.89
+1.21
VDD_MEM
+1.71
+2.34
VTT
+0.85
+1.17
+3.45 V
+2.38
+3.28
-11.95 V
-8.44
-11.56
+5.15 V
+3.59
+4.88
+12.15 V
+8.55
+11.48
HighCrit HighShut
59C/138F
64C/147F
85C/185F
+3.47
+1.56
+2.61
+1.91
+1.28
+1.36
+2.61
+1.32
+3.63
-12.84
+5.42
+12.77
+4.29
+1.95
+3.28
+2.34
+1.56
+1.71
+3.28
+1.64
+4.49
-15.78
+6.71
+15.82
Table 66
show environment table Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field
Description
Sample Point
LowShut
HighWarn
Field
Description
Field
Description
Field
Description
The system displays the following message if voltage or temperature exceed maximum margins:
SHUTDOWN: air flow problem
In the following example, there have been two intermittent power failures since a router was turned on, and
the lower power supply is not functioning. The last intermittent power failure occurred on Monday, June
10, 1996, at 11:07 p.m.
7000# show environment all
Environmental Statistics
Environmental status as of 23:19:47 UTC Wed Jun 12 1996
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Lower Power Supply is NON-OPERATIONAL
Lower Power Supply:700W, OFF
Upper Power Supply: 700W, ON
Intermittent Powerfail(s): 2
Last on 23:07:05 UTC Mon Jun 10 1996
+12 volts measured at 12.05(V)
+5 volts measured at
4.96(V)
-12 volts measured at -12.05(V)
+24 volts measured at 23.80(V)
Airflow temperature measured at 38(C)
Inlet temperature measured at 25(C)
The following table describes the significant fields shown in the display.
Table 67
show environment all Field Descriptions for the Cisco 7000 Series Routers
Field
Description
WARNING:
Intermittent Powerfail(s)
Voltage specifications
The following example is for the Cisco 7000 series routers. The router retrieves the environmental statistics
at the time of the last shutdown. In this example, the last shutdown was Friday, May 19, 1995, at 12:40
p.m., so the environmental statistics at that time are displayed.
Router# show environment last
Environmental Statistics
Environmental status as of 14:47:00 UTC Sun May 21 1995
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Upper Power Supply is NON-OPERATIONAL
LAST Environmental Statistics
Environmental status as of 12:40:00 UTC Fri May 19 1995
Lower Power Supply: 700W, ON
Upper Power Supply: 700W, OFF
No Intermittent Powerfails
+12 volts measured at 12.05(V)
+5 volts measured at
4.98(V)
-12 volts measured at -12.00(V)
+24 volts measured at 23.80(V)
Airflow temperature measured at 30(C)
Inlet temperature measured at 23(C)
The following table describes the significant fields shown in the display.
Table 68
show environment last Field Descriptions for the Cisco 7000 Series Routers
Field
Description
WARNING:
+24(V)
20.00
24.00(V)
28.00
Temperature Parameters:
SENSE
WARNING
NORMAL
WARNING
CRITICAL
SHUTDOWN
-------|-------------|------------|-------------|--------------|----------Airflow
10
60
70
73(C)
88
Inlet
10
39
41(C)
46
64
The following table describes the significant fields shown in the display.
Table 69
show environment table Field Descriptions for the Cisco 7000 Series Routers
Field
Description
WARNING
NORMAL
CRITICAL
SHUTDOWN
The system displays the following message if the voltage or temperature enters the Critical range:
%ENVM-2-ENVCRIT: +3.45 V measured at +3.65 V
The system displays the following message if the voltage or temperature exceeds the maximum margins:
%ENVM-0-SHUTDOWN: Environmental Monitor initiated shutdown
The following message is sent to the console if a power supply has been inserted or removed from the
system. This message relates only to systems that have two power supplies.
%ENVM-6-PSCHANGE: Power Supply 1 changed from Zytek AC Power Supply to removed
The following message is sent to the console if a power supply has been powered on or off. In the case of
the power supply being shut off, this message can be due to the user shutting off the power supply or to a
failed power supply. This message relates only to systems that have two power supplies.
%ENVM-6-PSLEV: Power Supply 1 state changed from normal to shutdown
The following is sample output from the show environment all command on the Cisco 7200 series routers
when there is a voltage warning condition in the system:
7200# show environment all
Power Supplies:
The following table describes the significant fields shown in the display.
Table 70
show environment all Field Descriptions for the Cisco 7200 Series Router
Field
Description
Power Supplies
Temperature readings
Voltage readings
The following example is for the Cisco 7200 series routers. This example shows the measurements
immediately before the last shutdown and the reason for the last shutdown (if appropriate).
7200# show environment last
chassis inlet
previously measured at
chassis outlet 1
previously measured at
chassis outlet 2
previously measured at
chassis outlet 3
previously measured at
+3.3 V
previously measured at
+5.0 V
previously measured at
+12.0 V
previously measured at
-12.0 V
previously measured at
last shutdown reason - power supply shutdown
27C/80F
31C/87F
37C/98F
45C/113F
4.02
4.92
12.65
11.71
The following table describes the significant fields shown in the display.
Table 71
show environment last Field Descriptions for the Cisco 7200 Series Router
Field
Description
chassis inlet
chassis outlet
voltages
The following example is for the Cisco 7200 series routers. This information lists the temperature and
voltage shutdown thresholds for each sensor.
7200# s
how environment table
Sample Point
LowCritical
chassis inlet
chassis outlet 1
chassis outlet 2
chassis outlet 3
+3.45 V
+2.76
+5.15 V
+4.10
+12.15 V
+9.72
-11.95 V
-8.37
Shutdown system at 70C/158F
LowWarning
+3.10
+4.61
+10.91
-9.57
HighWarning
40C/104F
43C/109F
75C/167F
55C/131F
+3.80
+5.67
+13.37
-14.34
HighCritical
50C/122F
53C/127F
75C/167F
65C/149F
+4.14
+6.17
+14.60
-15.53
The following table describes the significant fields shown in the display.
Table 72
show environment table Field Descriptions for the Cisco 7200 Series Router
Field
Description
Sample Point
LowCritical
LowWarning
HighWarning
HighCritical
Shutdown system at
The following table describes the significant fields shown in the display.
Table 73
show environment all Field Descriptions for the Cisco 7500 Series Routers
Field
Description
Arbiter type 1
Power supply
Field
Description
Dbus slots:
PS1
The following example is for the Cisco 7500 series routers. This example shows the measurements
immediately before the last shutdown.
7500# show environment last
RSP(4) Inlet
previously
RSP(4) Hotpoint
previously
RSP(4) Exhaust
previously
+12 Voltage
previously
+5 Voltage
previously
-12 Voltage
previously
+24 Voltage
previously
measured
measured
measured
measured
measured
measured
measured
at
at
at
at
at
at
at
37C/98F
46C/114F
52C/125F
12.26
5.17
-12.03
23.78
The following table describes the significant fields shown in the display.
Table 74
show environment last Field Descriptions for the Cisco 7500 Series Routers
Field
Description
Voltages
The following example is for the Cisco 7500 series router. This information lists the temperature and
voltage thresholds for each sensor. These thresholds indicate when error messages occur. There are two
level of messages: warning and critical.
7500# show environment table
Sample Point
LowCritical
LowWarning
RSP(4) Inlet
RSP(4) Hotpoint
RSP(4) Exhaust
+12 Voltage
10.90
11.61
+5 Voltage
4.61
4.94
-12 Voltage
-10.15
-10.76
+24 Voltage
20.38
21.51
2.5 Reference
2.43
Shutdown boards at
70C/158F
Shutdown power supplies at
76C/168F
Restart after shutdown below 40C/104F
HighWarning
44C/111F
54C/129F
HighCritical
50C/122F
60C/140F
12.82
5.46
-13.25
26.42
2.51
13.38
5.70
-13.86
27.65
The following table describes the significant fields shown in the display.
Table 75
show environment table Field Descriptions for the Cisco 7500 Series Routers
Field
Description
Sample Point
LowCritical
LowWarning
HighWarning
HighCritical
Shutdown boards at
supported for that environmental parameter (for example, the power supply and blowers in slots 24, 26, 28,
and 29 do not have a 3V power supply, so an NA is displayed).
Router# show environment
Slot # 3V
5V
MBUS 5V Hot Sensor
(mv)
(mv)
(mv)
(deg C)
0
3300
4992
5040
42.0
2
3296
4976
5136
40.0
4
3280
4992
5120
38.5
7
3280
4984
5136
42.0
9
3292
4968
5160
39.5
11
3288
4992
5152
40.0
16
3308
NA
5056
42.5
17
3292
NA
5056
40.5
18
3304
NA
5176
36.5
19
3300
NA
5184
37.5
20
3304
NA
5168
36.5
24
NA
5536
5120
NA
26
NA
5544
5128
NA
28
NA
NA
5128
NA
29
NA
NA
5104
NA
Slot # 48V
AMP_48
(Volt) (Amp)
24
46
12
26
46
19
Slot # Fan 0
Fan 1
Fan 2
(RPM)
(RPM)
(RPM)
28
2160
2190
2160
29
2130
2190
2070
Inlet Sensor
(deg C)
37.0
33.0
31.5
32.0
31.5
30.5
38.0
36.5
35.0
33.5
34.0
31.5
31.5
NA
NA
The following table describes the significant fields shown and lists the equipment supported by each
environmental parameter. NA indicates that the reading could not be obtained, so the command should be
run again.
Table 76
show environment Field Descriptions for the Cisco 12000 Series Routers
Field
Description
Slot #
3V (mv)
5V (mv)
MBUS 5V (mv)
Field
Description
48V (Volt)
AMP_48 (Amp)
The following is sample output from the show environment all command for the Cisco 12008 router. Slots
0 through 7 are the line cards, slots 16 and 17 are the clock scheduler cards (the clock scheduler cards
control the fans), slots 18 through 20 are the switch fabric cards, and slots 24 and 26 are the power supplies.
The Cisco 12008 router does not support slots 25, 27, 28, and 29. An NA in the table means that no
values were returned. In some cases it is because the equipment is not supported for that environmental
parameter (for example, the power supplies in slots 24 and 26 do not have a hot sensor, so an NA is
displayed).
Router# show environment all
Slot # Hot Sensor
Inlet Sensor
(deg C)
(deg C)
2
31.0
22.0
5
33.5
26.5
16
25.5
21.5
18
22.0
21.0
19
22.5
21.0
24
NA
29.5
26
NA
24.5
Slot # 3V
5V
MBUS 5V
(mv)
(mv)
(mv)
2
3292
5008
5136
5
3292
5000
5128
16
3272
NA
5128
18
3300
NA
5128
19
3316
NA
5128
Slot # 5V
MBUS 5V 48V
AMP_48
(mv)
(mv)
(Volt) (Amp)
24
0
5096
3
0
26
5544
5144
47
3
Slot # Fan Information
16
Voltage 16V Speed slow: Main Fans Ok Power Supply fans Ok
Alarm Indicators
No alarms
Slot # Card Specific Leds
16
Mbus OK SFCs Failed
18
Mbus OK
19
Mbus OK
24
Input Failed
26
Input Ok
The following is sample output from the show environment table command for a Cisco 12012 router. The
show environment table command lists the warning, critical, and shutdown limits on your system and
includes the GRP card and line cards (slots 0 to 15), clock and scheduler cards (slots 16 and 17), switch
fabric cards (slots 18 to 20), and blowers.
Router# show environment table
Hot Sensor Temperature Limits (deg C):
Warning Critical Shutdown
GRP/GLC (Slots 0-15)
40
46
57
CSC
(Slots 16-17)
46
51
65
SFC
(Slots 18-20)
41
46
60
Warning
Below
Above
3200
3400
3200
3400
3200
3400
Critical
Below Above
3100
3500
3100
3500
3100
3500
Shutdown
Below Above
3050
3550
3050
3550
3050
3550
Warning
Below
Above
4850
5150
Critical
Below Above
4750
5250
Shutdown
Below Above
4680
5320
Warning
Below
Above
5000
5250
4820
5150
5000
5250
Critical
Below Above
4900
5350
4720
5250
4900
5350
Shutdown
Below Above
4750
5450
4750
5450
4750
5450
5V Ranges (mv):
GRP/GLC (Slots 0-15)
MBUS_5V Ranges (mv):
GRP/GLC (Slots 0-15)
CSC
(Slots 16-17)
SFC
(Slots 17-20)
Fan 0
Fan 1
Fan 2
Critical
Below
750
750
750
The following is sample output from the show environment leds command for a Cisco 12012 router. The
show environment leds command lists the status of the MBus LEDs on the clock, scheduler, and the
switch fabric cards.
Router#
16 leds
18 leds
19 leds
20 leds
show
Mbus
Mbus
Mbus
Mbus
environment leds
OK
OK
OK
OK
7304-MSC-100
measured at
Card in subslot 4/0:
SPA-4FE-7304 inlet
measured at
SPA-4FE-7304 outlet measured at
Voltage readings:
Active RP (NPEG100, slot 0):
npe outlet 2.5 V
measured at
npe outlet 3.3 V
measured at
npe outlet 5.0 V
measured at
npe outlet 12.0 V
measured at
npe outlet 3.3c V
measured at
npe inlet
1.5 V
measured at
npe outlet 1.8 V
measured at
npe outlet 1.2 V
measured at
npe outlet 1.2c V
measured at
Line card (7304-MSC-100, slot 4):
7304-MSC-100 0.75 V measured at
7304-MSC-100 1.5 V
measured at
7304-MSC-100 2.5 V
measured at
7304-MSC-100 3.3 V
measured at
7304-MSC-100 12 V
measured at
Card in subslot 4/0:
SPA-4FE-7304 1.8V
measured at
SPA-4FE-7304 1.5V
measured at
SPA-4FE-7304 2.5V
measured at
SPA-4FE-7304 3.3V
measured at
SPA-4FE-7304 1.0V
measured at
Envm stats saved 13 time(s) since reload
32C/89F
31C/87F
32C/89F
2.496
3.302
4.992
11.812
3.199
1.494
1.790
1.198
1.198
V
V
V
V
V
V
V
V
V
0.733
1.494
2.483
3.250
11.937
V
V
V
V
V
1.802
1.503
2.474
3.252
1.015
V
V
V
V
V
The following is sample output from the show environment lastcommand on a Cisco 7304 router with
MSCs and SPAs installed and an NSE-100:
Router# show environment last
Temperature information:
NSE board:
nse outlet
is unmeasured
nse inlet
is unmeasured
nse hotspot
is unmeasured
nse db
is unmeasured
Line card slot 4:
7304-MSC-100
is unmeasured
Card in subslot 4/1:
SPA-4FE-7304 inlet
previously measured
SPA-4FE-7304 outlet previously measured
Voltage information:
NSE board:
nse outlet 1.8 V
is unmeasured
nse outlet 2.5 V
is unmeasured
nse outlet 3.3 V
is unmeasured
nse outlet 5 V
is unmeasured
nse outlet 12 V
is unmeasured
nse inlet 1.8 V
is unmeasured
nse inlet 3.3 V
is unmeasured
nse inlet 1.5 V
is unmeasured
nse hotspot 1.8 V
is unmeasured
nse db 1.65 V
is unmeasured
nse db 1.8 V
is unmeasured
Line card slot 4:
7304-MSC-100 0.75 V is unmeasured
7304-MSC-100 1.5 V
is unmeasured
7304-MSC-100 2.5 V
is unmeasured
7304-MSC-100 3.3 V
is unmeasured
7304-MSC-100 12 V
is unmeasured
Card in subslot 4/1:
SPA-4FE-7304 1.8V
previously measured
SPA-4FE-7304 1.5V
previously measured
SPA-4FE-7304 2.5V
previously measured
SPA-4FE-7304 3.3V
previously measured
SPA-4FE-7304 1.0V
previously measured
Last shutdown reason: shutdown undefined
at 30C/86F
at 32C/89F
at
at
at
at
at
1.823
1.512
2.504
3.258
1.014
V
V
V
V
V
The following is sample output from the show environment tablecommand on a Cisco 7304 router with
MSCs and SPAs installed:
Router# show environment table
Temperature tables:
Active RP (NPEG100, slot 0):
Sample Point
HighWarning
npeg100 outlet
53C/127F
npeg100 inlet
53C/127F
npeg100 hotspot
53C/127F
Line card (7304-MSC-100, slot 4):
Sample Point
HighWarning
7304-MSC-100
48C/118F
Card in subslot 4/0:
Sample Point
HighWarning
SPA-4FE-7304 inlet 52C/125F
SPA-4FE-7304 outlet 52C/125F
Voltage tables:
Active RP (NPEG100, slot 0):
Sample Point
LowShut LowCrit
npe outlet 2.5 V 2.275 V 2.375 V
npe outlet 3.3 V 3.003 V 3.135 V
npe outlet 5.0 V 4.500 V 4.750 V
npe outlet 12.0 V 9.960 V 10.440 V
npe outlet 3.3c V 3.003 V 3.135 V
npe inlet
1.5 V 1.350 V 1.425 V
npe outlet 1.8 V 1.620 V 1.710 V
npe outlet 1.2 V 1.128 V 1.164 V
npe outlet 1.2c V 1.128 V 1.164 V
Line card (7304-MSC-100, slot 4):
Sample Point
LowShut LowCrit
7304-MSC-100 0.75 0.559 V 0.600 V
7304-MSC-100 1.5 V 1.350 V 1.440 V
7304-MSC-100 2.5 V 2.250 V 2.375 V
7304-MSC-100 3.3 V 2.970 V 3.135 V
7304-MSC-100 12 V 9.960 V 10.440 V
Card in subslot 4/0:
Sample Point
LowShut LowCrit
SPA-4FE-7304 1.8V 1.620 V 1.710 V
SPA-4FE-7304 1.5V 1.350 V 1.425 V
SPA-4FE-7304 2.5V 2.250 V 2.375 V
SPA-4FE-7304 3.3V 2.970 V 3.135 V
SPA-4FE-7304 1.0V 0.900 V 0.950 V
HighCritical HighShutdown
68C/154F
73C/163F
68C/154F
73C/163F
68C/154F
73C/163F
HighCritical HighShutdown
63C/145F
68C/154F
HighCritical HighShutdown
67C/152F
72C/161F
67C/152F
72C/161F
LowWarn HighWarn HighCrit HighShut
2.400 V 2.600 V 2.625 V 2.725 V
3.185 V 3.415 V 3.465 V 3.597 V
4.800 V 5.200 V 5.250 V 5.500 V
10.800 V 13.200 V 13.560 V 14.040 V
3.185 V 3.415 V 3.465 V 3.597 V
1.455 V 1.545 V 1.575 V 1.650 V
1.728 V 1.872 V 1.890 V 1.980 V
1.167 V 1.233 V 1.236 V 1.272 V
1.167 V 1.233 V 1.236 V 1.272 V
LowWarn HighWarn HighCrit HighShut
0.600 V 0.900 V 0.900 V 0.941 V
1.455 V 1.545 V 1.560 V 1.650 V
2.400 V 2.600 V 2.625 V 2.750 V
3.168 V 3.432 V 3.465 V 3.630 V
10.800 V 13.200 V 13.560 V 14.040 V
LowWarn
1.728 V
1.440 V
2.400 V
3.168 V
0.960 V
HighWarn
1.872 V
1.560 V
2.600 V
3.432 V
1.040 V
HighCrit
1.890 V
1.575 V
2.625 V
3.465 V
1.050 V
HighShut
1.980 V
1.650 V
2.750 V
3.630 V
1.100 V
The following table describes the significant fields shown in the display.
Table 77
show environment table Field Descriptions for the Cisco 7304 Router
Field
Description
Sample Point
LowShut
LowCrit/LowCritical
Field
Description
LowWarn/LowWarning
HighWarn/HighWarning
HighCrit/HighCritical
HighShut/HighShutdown
09/30/2009 10:18:26
168.813
48
36
44
47
40
53
46
47 45
36
47
09/30/2009 10:16:26
168.813
47
36
44
47
40
53
46
47 45
36
47
09/30/2009 10:14:26
168.813
47
36
44
47
40
53
46
47 45
36
47
09/30/2009 10:12:26
168.813
47
36
44
46
40
52
45
47 45
36
47
09/30/2009 10:10:26
168.813
47
35
44
45
39
51
45
47 45
36
47
09/30/2009 10:08:26
168.132
46
35
44
43
38
50
43
47 45
36
47
------------------------------------------------------------------------------------------
The following table describes the significant fields shown in the display.
Table 78
Related Commands
show environment subslot Field Descriptions for the Cisco uBR10012 Router
Field
Description
Sampling frequency
Sensor
Sensor name.
ID
Current Temperature
Minor
Major Threshold
Critical
Time Stamp
Alarm Condition
Alarm state.
Power Watts
Sensor
Temperature
Command
Description
snmp-server host
Syntax Description
status
threshold
frutype
Command Default
If you do not enter a frutype, all the information about the environmental alarm status is displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Note
Examples
The slotargument designates the module and port number. Valid values for slot depend on the chassis and
module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed
in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number
are from 1 to 48.
This example shows how to display all the information about the status of the environmental alarm:
Router>
show environment alarm
threshold
environmental alarm thresholds:
power-supply 1 fan-fail: OK
threshold #1 for power-supply 1 fan-fail:
(sensor value != 0) is system minor alarm
power-supply 1 power-output-fail: OK
threshold #1 for power-supply 1 power-output-fail:
(sensor value != 0) is system minor alarm
fantray fan operation sensor: OK
threshold #1 for fantray fan operation sensor:
(sensor value != 0) is system minor alarm
operating clock count: 2
threshold #1 for operating clock count:
(sensor value < 2) is system minor alarm
threshold #2 for operating clock count:
(sensor value < 1) is system major alarm
operating VTT count: 3
threshold #1 for operating VTT count:
(sensor value < 3) is system minor alarm
threshold #2 for operating VTT count:
(sensor value < 2) is system major alarm
VTT 1 OK: OK
threshold #1 for VTT 1 OK:
(sensor value != 0) is system minor alarm
VTT 2 OK: OK
threshold #1 for VTT 2 OK:
(sensor value != 0) is system minor alarm
VTT 3 OK: OK
threshold #1 for VTT 3 OK:
(sensor value != 0) is system minor alarm
clock 1 OK: OK
threshold #1 for clock 1 OK:
(sensor value != 0) is system minor alarm
clock 2 OK: OK
threshold #1 for clock 2 OK:
(sensor value != 0) is system minor alarm
module 1 power-output-fail: OK
threshold #1 for module 1 power-output-fail:
(sensor value != 0) is system major alarm
module 1 outlet temperature: 21C
threshold #1 for module 1 outlet temperature:
(sensor value > 60) is system minor alarm
threshold #2 for module 1 outlet temperature:
(sensor value > 70) is system major alarm
module 1 inlet temperature: 25C
threshold #1 for module 1 inlet temperature:
(sensor value > 60) is system minor alarm
threshold #2 for module 1 inlet temperature:
(sensor value > 70) is system major alarm
module 1 device-1 temperature: 30C
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
all
backplane
module number
Release
Modification
12.2(33)SXI 4
The output of the show environment connector command displays the connector rating of the backplane
(chassis) power connector, the connector rating of module connectors, and the power consumption of each
installed module.
If your system contains the necessary components for auxiliary power, the auxiliary power connector rating
is displayed.
If an installed module contains a voice daughterboard (VDB), the VDB connector rating is displayed.
If you enter the show environment connector command with no keywords, the information for the
backplane and all modules is displayed.
Examples
This example shows how to display the connector rating and power consumption of the backplane and all
modules:
Router>
show environment connector all
chassis connector rating: 1302.00 Watts (31.00 Amps @ 42V)
chassis auxiliary connector rating: 2016.00 Watts (48.00 Amps @ 42V)
module 3
module 3 connector rating: 1260.00 Watts (30.00 Amps @ 42V)
module
module
module 6
module
module
module 9
module
module
module
module
module
This example shows how to display the connector rating of the backplane:
Router>
show environment connector backplane
chassis connector rating: 1302.00 Watts (31.00 Amps @ 42V)
chassis auxiliary connector rating: 2016.00 Watts (48.00 Amps @ 42V)
Related Commands
Command
Description
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(33)SRA
Usage Guidelines
This command is not supported in Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display the information about the cooling parameter:
Router> show environment cooling
fan-tray 1:
fan-tray 1 fan-fail: failed
fan-tray 2:
fan 2 type: FAN-MOD-9
fan-tray 2 fan-fail: OK
chassis cooling capacity: 690 cfm
ambient temperature: 55C
chassis per slot cooling capacity:
module 1 cooling requirement: 70
module 2 cooling requirement: 70
module 5 cooling requirement: 30
module 6 cooling requirement: 70
module 8 cooling requirement: 70
module 9 cooling requirement: 30
Router>
75 cfm
cfm
cfm
cfm
cfm
cfm
cfm
Related Commands
Command
Description
Syntax Description
frutype
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXF
12.2(33)SRA
Note
Examples
The slotargument designates the module and port number. Valid values for slot depend on the chassis and
module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed
in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number
are from 1 to 48.
This example shows how to display the information about the environmental status:
Router>
show environment status
backplane:
operating clock count: 2
operating VTT count: 3
fan-tray:
fantray fan operation sensor: OK
VTT 1:
VTT 1 OK: OK
VTT 2:
VTT 2 OK: OK
VTT 3:
VTT 3 OK: OK
clock 1:
clock 1 OK: OK, clock 1 clock-inuse: not-in-use
clock 2:
clock 2 OK: OK, clock 2 clock-inuse: in-use
power-supply 1:
power-supply 1 fan-fail: OK
power-supply 1 power-output-fail: OK
module 1:
module 1 power-output-fail: OK
module 1 outlet temperature: 21C
module 1 inlet temperature: 25C
module 1 device-1 temperature: 30C
module 1 device-2 temperature: 29C
EARL 1 outlet temperature: N/O
EARL 1 inlet temperature: N/O
module 5:
module 5 power-output-fail: OK
module 5 outlet temperature: 26C
module 5 inlet temperature: 23C
module 5 device-1 temperature: 26C
module 5 device-2 temperature: 27C
Router>
This example shows how to display the information about the high-capacity power supplies:
Route># show environment status
power-supply 2
power-supply 2:
power-supply 2 fan-fail: OK
power-supply 2 power-input 1: none
power-supply 2 power-input 2: AC low
power-supply 2 power-input 3: AC high
power-supply 2 power-input 4: AC high
power-supply 2 power-output: low (mode 1)
power-supply 2 power-output-fail: OK
The table below describes the fields that are shown in the example.
Table 79
Related Commands
Field
Description
clock # clock-inuse
power-supply # fan-fail
power-input-fail
power-output-fail
outlet temperature
inlet temperature
Command
Description
Syntax Description
frutype
Command Default
If you do not enter a frutype, the module and EARL temperature readings are displayed.
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17a)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
Note
The slotargument designates the module and port number. Valid values for slot depend on the chassis and
module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed
in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number
are from 1 to 48.
The show environment temperature module command output includes the updated information after an
SCP response is received.
In the output display, the following applies:
Examples
This example shows how to display the temperature information for a specific module:
Router>
show environment temperature
module 5
module 5 outlet temperature: 34C
module 5 inlet temperature: 27C
module 5 device-1 temperature: 42C
module 5 device-2 temperature: 41C
module 5 asic-1 (SSO-1) temp: 29C
module 5 asic-2 (SSO-2) temp: 29C
module 5 asic-3 (SSO-3) temp: 29C
module 5 asic-4 (SSO-4) temp: 28C
module 5 asic-5 (SSA-1) temp: 29C
module 5 asic-6 (HYPERION-1) temp: 29C
Router>
This example shows how to display the temperature readings for all modules:
Router>
show environment temperature
VTT 1 outlet temperature: 25C
VTT 2 outlet temperature: 24C
VTT 3 outlet temperature: 28C
module 1 outlet temperature: 24C
module 1 device-2 temperature: 29C
RP 1 outlet temperature: 25C
The following table describes the fields that are shown in the example.
Table 80
Related Commands
Field
Description
outlet temperature
inlet temperature
Command
Description
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
Related Commands
Command
Description
Syntax Description
Command Default
Command Modes
EXEC
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This example shows how to display the information about the error-disable recovery timer:
Router#
show errdisable recovery
ErrDisable Reason
Timer Status
-----------------------------udld
Enabled
bpduguard
Enabled
rootguard
Enabled
pagp-flap
Enabled
dtp-flap
Enabled
link-flap
Enabled
Timer interval:300 seconds
Interfaces that will be enabled at the next timeout:
Interface
Errdisable reason
Time left(sec)
-------------------------------------Fa9/4
link-flap
279
Related Commands
Command
Description
errdisable recovery
show fastblk
To display fast block memory information, use the show fastblkcommand in privileged EXEC mode.
show fastblk [detailed]
Syntax Description
Command Modes
Command History
detailed
Release
Modification
12.4(22)T
Usage Guidelines
Use this command to display allocated fast block memory pool details. When no memory pools are
allocated, the no fastblk memory pools allocated message is displayed.
Examples
The following is sample output from the show fastblk command using the detailed keyword. The fields
are self-explanatory.
Router# show fastblk detailed
Pool name: SCTP ApplReq
flags:DYN_POOL
total = 400 inuse = 0, free = 400, max = 0
increment = 200, threshold = 100, hist max = 400
alloc failures = 0, sub-pool creation failures = 0
subpool: blks = 0x62968A2C, total = 400, inuse= 0, free = 400
delete count = 0, flags:
Pool name: SCTP BufSegHdr
flags:DYN_POOL
total = 9000 inuse = 0, free = 9000, max = 0
increment = 4500, threshold = 6750, hist max = 9000
alloc failures = 0, sub-pool creation failures = 0
subpool: blks = 0x62B8E2F4, total = 9000, inuse= 0, free = 9000
delete count = 0, flags:
Pool name: SCTP DestAddr
flags:DYN_POOL
total = 80 inuse = 0, free = 80, max = 0
increment = 40, threshold = 20, hist max = 80
alloc failures = 0, sub-pool creation failures = 0
subpool: blks = 0x62972534, total = 80, inuse= 0, free = 80
delete count = 0, flags:
Pool name: SCTP Addr
flags:DYN_POOL POOL_HAS_GRWN
total = 200 inuse = 100, free = 100, max = 0
increment = 50, threshold = 50, hist max = 200
alloc failures = 31, sub-pool creation failures = 0
subpool: blks = 0x6271B6D0, total = 50, inuse= 0, free = 50
delete count = 0, flags: DYN_SUBPOOL
subpool: blks = 0x6271D730, total = 50, inuse= 0, free = 50
delete count = 0, flags: DYN_SUBPOOL
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
12.2(33)SRA
Usage Guidelines
File descriptors are the internal representations of open files. You can use this command to learn if another
user has a file open.
Examples
The following is sample output from the show file descriptors command:
Router# show file descriptors
File Descriptors:
FD Position Open PID Path
0
187392 0001
2 tftp://dirt/hampton/c4000-i-m.a
1
184320 030A
2 flash:c4000-i-m.a
Field
Description
FD
Position
Open
PID
Field
Description
Path
Syntax Description
Command Modes
Command History
Examples
file-url
EXEC
Release
Modification
11.3 AA
12.2(33)SRA
The following is sample output from the show file information command:
Router# show file information tftp://dirt/hampton/c2500-j-l.a
tftp://dirt/hampton/c2500-j-l.a:
type is image (a.out) [relocatable, run from flash]
file size is 8624596 bytes, run size is 9044940 bytes [8512316+112248+420344]
Foreign image
Router# show file information slot0:c7200-js-mz
slot0:c7200-js-mz:
type is image (elf) []
file size is 4770316 bytes, run size is 4935324 bytes
Runnable image, entry point 0x80008000, run from ram
Router1# show file information nvram:startup-config
nvram:startup-config:
type is ascii text
Types
Description
image (a.out)
image (elf)
ascii text
coff
Types
Description
ebcdic
lzw compression
tar
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.3AA
12.3(7)T
12.2(25)S
12.2(33)SRA
12.2(33)SXI
12.4(24)T
15.0(01)XO
Usage Guidelines
Use this command to learn the alias names, the Prefixes column in the output of the file systems that your
router supports.
Examples
The following is sample output from the show file systems command:
Router# show file systems
File Systems:
Size(b)
Free(b)
Type
Flags
Prefixes
42541056
512065536
65536000
129004
125802334
0
1964024
512065536
65536000
1964024
129004
65536000
-
42541056
30834688
19811932
102228
0
609689428
1949453
30842880
19328264
1919757
102228
65536000
-
ram
opaque
disk
disk
flash
opaque
nvram
opaque
opaque
opaque
opaque
nvram
network
network
network
network
disk
disk
disk
disk
flash
nvram
nvram
flash
nvram
opaque
disk
disk
disk
rw
rw
rw
rw
rw
ro
rw
ro
rw
rw
ro
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
rw
tmp:
system:
disk1: disk1:0:#
disk0:#
bootflash: sup-bootflash:
ivfs:
const_nvram:
microcode: sup-microcode:
image: sup-image:
null:
tar:
nvram:
rcp:
tftp:
http:
ftp:
disk1:1:
disk1:2:
slavedisk0:#
slavedisk1: slavedisk1:0:
slavesup-bootflash:
slavenvram:
slaveconst_nvram:
slavebootflash:
slavercsf:
slavesystem:
slavedisk1:1:
slavedisk1:2:
slavedisk1:3:
The table below describes the significant fields shown in the display.
Table 83
Field
Description
Size(b)
Free(b)
Field
Description
Type
Flags
Prefixes
Note
As of release 15.0(01)XO, on cat4000 series routers, the show file systems and dirwill display slightly
different byte count and usage information for the same file system. This is due to slight difference in how
IOS computes these figures for this platform.
show flh-log
The show flh-log command has been replaced by the more flh:logfile command. See the description of the
more flh:logfile command for more information.
show fm inspect
To display the list and status of the access control lists (ACLs) and ports on which context based access
control (CBAC) is configured, use the show fm inspect command in user EXEC or privileged EXEC
mode.
show fm inspect [detail | interface type mod/port]
Syntax Description
detail
interface type
mod / port
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
If you can configure a VLAN access control list (VACL) on the port before you configure CBAC, the
status displayed is INACTIVE; otherwise, it is ACTIVE. If policy feature card (PFC) resources are
exhausted, the command displays BRIDGE and is followed by the number of failed currently active
NetFlow requests that have been sent to the MSFC2 for processing.
The show fm inspect command output includes this information:
The optional detail keyword displays the ACEs that are part of the ACL that is used for IP inspect on the
given interface direction.
Examples
This example shows how to display the list and status of CBAC-configured ACLs and ports:
Router>
show fm inspect
interface:Vlan305(in) status :ACTIVE
acl name:deny
interfaces:
Vlan305(out):status ACTIVE
Related Commands
Command
Description
show fm summary
show fm interface
To display the detailed information about the feature manager on a per-interface basis, use the show fm
interface command in user EXEC or privileged EXEC mode.
show fm interface {interface type mod/port | null interface-number | port-channel number | vlan
vlan-id}
Syntax Description
type
mod / port
null interface-number
port-channel number
vlan vlan-id
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17a)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
The pos, atm, and ge-wan keywords are supported on Cisco 7600 series routers that are configured with a
Supervisor Engine 2
The interface-number argument designates the module and port number. Valid values for interface-number
depend on the specified interface type and the chassis and module that are used. For example, if you
specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in
a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number
are from 1 to 48.
The port-channel numbervalues from 257 to 282 are supported on the CSM and the FWSM only.
Examples
This example shows how to display the detailed information about the feature manager on a specified
interface:
Router>
show fm interface fastethernet 2/26
Interface:FastEthernet2/26 IP is enabled
hw[EGRESS] = 1, hw[INGRESS] = 0
hw_force_default[EGRESS] = 0, hw_force_default[INGRESS] = 1
mcast = 0
priority = 2
reflexive = 0
inbound label:24
protocol:ip
feature #:1
feature id:FM_IP_ACCESS
ACL:113
vmr IP value #1:0, 0, 0, 0, 0, 0, 0, 6 - 1
vmr IP mask #1:0, 0, FFFF, FFFF, 0, 0, 0, FF
vmr IP value #2:642D4122, 0, 0, 0, 1, 0, 0, 6 - 1
vmr IP mask #2:FFFFFFFF, 0, 0, 0, 1, 0, 0, FF
vmr IP value #3:0, 64020302, 0, 0, 6, 0, 0, 6 - 1
vmr IP mask #3:0, FFFFFFFF, 0, 0, 6, 0, 0, FF
vmr IP value #4:0, 64020302, 0, 0, A, 0, 0, 6 - 1
vmr IP mask #4:0, FFFFFFFF, 0, 0, A, 0, 0, FF
vmr IP value #5:0, 64020302, 0, 0, 12, 0, 0, 6 - 1
vmr IP mask #5:0, FFFFFFFF, 0, 0, 12, 0, 0, FF
vmr IP value #6:0, 0, 0, 0, 0, 0, 0, 0 - 2
vmr IP mask #6:0, 0, 0, 0, 0, 0, 0, 0
outbound label:3
protocol:ip
feature #:1
feature id:FM_IP_WCCP
Service ID:0
Service Type:0
Router>
This example shows how to display the detailed information about the feature manager on a specific
VLAN:
Router> show fm interface vlan 21
Interface: Vlan21 IP is disabled
hw_state[INGRESS] = not reduced, hw_state[EGRESS] = not reduced
mcast = 0
priority = 0
flags = 0x0
inbound label: 8
Feature IP_VACL:
----------------------------------------------------------------------------FM_FEATURE_IP_VACL_INGRESS i/f: Vl21 map name: test
=============================================================================
-----------------------------------------------------------IP Seq. No: 10 Seq. Result : VACL_ACTION_FORWARD_CAPTURE
-----------------------------------------------------------DPort - Destination Port SPort - Source Port Pro - Protocol
Related Commands
Command
Description
show fm summary
show fm reflexive
To display the information about the reflexive entry for the dynamic feature manager, use the show fm
reflexive command in privileged EXEC mode.
show fm reflexive
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
This example shows how to display the information about the reflexive entry for the dynamic feature
manager:
Router#
show fm reflexive
Reflexive hash table:
Vlan613:refacl, OUT-REF, 64060E0A, 64060D0A, 0, 0, 7, 783, 6
Router#
show fm summary
To display a summary of feature manager information, use the show fm summary command in user EXEC
or privileged EXEC mode.
show fm summary
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Related Commands
Command
Description
show fm interface
show funi
To display the frame-based user-network interface information, use the show funicommand in user EXEC
or privileged EXEC mode.
show funi {arp-server [atm atm-interface-number] | class-links {vpi/vci-value | vci-value |
connection-name} | ilmi-configuration | ilmi-status [atm atm-interface-number] | map | pvc[vpi/
vci-value | vci-value | connection-name | dbs | ppp] | route | traffic | vp atm-vpi-number | vc {atmvcd-number | connection-name | detail [prefix {interface | vc-name | vcd | vpi/vci}]} | interface
atm atm-interface-number{connection-name | detail [prefix {interface | vc-name | vcd | vpi/vci}]} |
range lower-vcd-limit upper-vcd-limit{connection-name | detail [prefix {interface | vc-name | vcd |
vpi/vci}]} | interface atm atm-interface-number{connection-name | detail [prefix {interface | vcname | vcd | vpi/vci}]} | summary [atm atm-interface-number]}
Syntax Description
arp-server
atm atm-interface-number
class-links
vpi /vci-value
vci-value
connection-name
ilmi-configuration
ilmi-status
map
pvc
dbs
ppp
route
traffic
Command Modes
Command History
Usage Guidelines
vp
atm-vpi-number
vc
atm-vcd-number
detail
prefix
interface
vc_name
vcd
vpi/vci
range
lower-vcd-limit
upper-vcd-limit
summary
Release
Modification
12.4(24)T
Use this command to display the frame-based user-network interface information with the available
keywords and arguments.
Examples
The following is sample output from the show funi trafficcommand. The fields are self-explanatory:
Router# show funi traffic
Input OAM Queue: 0/4136 (size/max)
0 Input packets
0 Output packets
0 Broadcast packets
0 Packets received on non-existent VC
0 Packets attempted to send on non-existent VC
0 OAM cells received
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F5 InEndcc: 0, F5 InSegcc: 0,
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
0 OAM cells sent
F5 OutEndloop: 0, F5 OutSegloop: 0,
F5 OutAIS: 0
F5 OutRDI: 0
F5 OutEndcc: 0, F5 OutSegcc: 0,
F4 OutEndloop: 0, F4 OutSegloop: 0,
F4 OutRDI: 0
F4 OutAIS: 0
0 OAM cell drops
The following is sample out from the show funi vc detail prefix interface command. The fields are selfexplanatory:
Router# show funi vc detail prefix interface
Description: N/A
ATM2/0 ATM2/0: VCD: 1, VPI: 1, VCI: 100
ATM2/0 UBR, PeakRate: 0 (0 cps)
ATM2/0 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 12
ATM2/0 OAM frequency: 0 second(s)
ATM2/0 InARP frequency: 15 minutes(s)
ATM2/0 Transmit priority 6
ATM2/0 InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InCells: 0, OutCells: 0
ATM2/0 InPRoc: 0, OutPRoc: 0, Broadcasts: 0
ATM2/0 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
ATM2/0 InPktDrops: 0, OutPktDrops: 0
ATM2/0 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIE0
ATM2/0 Out CLP=1 Pkts: 0, Cells: 0
ATM2/0 OAM cells received: 0
ATM2/0 OAM cells sent: 0
ATM2/0 Status: INACTIVE
Description: N/A
ATM2/0 ATM2/0: VCD: 2, VPI: 1, VCI: 101
ATM2/0 UBR, PeakRate: 0 (0 cps)
ATM2/0 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 12
ATM2/0 OAM frequency: 0 second(s)
The following is sample out from the show funi vc detail prefix vc_name command. The fields are selfexplanatory:
Router# show funi vc detail prefix vc_name
Description: N/A
ATM2/0: VCD: 1, VPI: 1, VCI: 100
UBR, PeakRate: 0 (0 cps)
AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 12
OAM frequency: 0 second(s)
InARP frequency: 15 minutes(s)
Transmit priority 6
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InCells: 0, OutCells: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0, Cells: 0
OAM cells received: 0
OAM cells sent: 0
Status: INACTIVE
Description: N/A
ATM2/0: VCD: 2, VPI: 1, VCI: 101
UBR, PeakRate: 0 (0 cps)
AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 12
The following is sample out from the show funi vc detail prefix pvi/vci command. The fields are selfexplanatory:
Router# show funi vc detail prefix vpi/vci
Description: N/A
VPI/VCI: 1/100 ATM2/0: VCD: 1, VPI: 1, VCI: 100
VPI/VCI: 1/100 UBR, PeakRate: 0 (0 cps)
VPI/VCI: 1/100 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 2
VPI/VCI: 1/100 OAM frequency: 0 second(s)
VPI/VCI: 1/100 InARP frequency: 15 minutes(s)
VPI/VCI: 1/100 Transmit priority 6
VPI/VCI: 1/100 InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InCells: 0, OutCells: 0
VPI/VCI: 1/100 InPRoc: 0, OutPRoc: 0, Broadcasts: 0
VPI/VCI: 1/100 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
VPI/VCI: 1/100 InPktDrops: 0, OutPktDrops: 0
VPI/VCI: 1/100 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation:0
VPI/VCI: 1/100 Out CLP=1 Pkts: 0, Cells: 0
VPI/VCI: 1/100 OAM cells received: 0
VPI/VCI: 1/100 OAM cells sent: 0
VPI/VCI: 1/100 Status: INACTIVE
Description: N/A
VPI/VCI: 1/101 ATM2/0: VCD: 2, VPI: 1, VCI: 101
VPI/VCI: 1/101 UBR, PeakRate: 0 (0 cps)
VPI/VCI: 1/101 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0, Encapsize: 2
Syntax Description
Command Modes
Command History
Examples
name
Release
Modification
12.2(18)SX
Related Commands
Command
Description
show running-configuration
Syntax Description
Command Modes
Command History
Examples
default
dot1x
eapoudp
Release
Modification
12.2(18)SX
Related Commands
Command
Description
show running-configuration
Syntax Description
snapshot
slot
status
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
Use the show platform software snapshot status command to view the status of a bootflash snapshot
request.
Examples
This example shows how to view the status of bootflash snapshot requests on the processor in the RO slot.
router#show platform software snapshot R0 status
Related Commands
Command
Description
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the show
gsr command in EXEC mode.
show gsr [chassis-info [details]]
Syntax Description
Command Modes
Command History
chassis-info
details
EXEC
Release
Modification
11.2GS
12.2(33)SRA
Usage Guidelines
Use this command to determine the type of hardware installed in your Cisco 12000 series GSR router.
Examples
The following is sample output from the show gsr command for a Cisco 12012 router. This command
shows the type and state of the card installed in the slot.
Router# show gsr
Slot 0 type = Route Processor
state = IOS Running MASTER
Slot 7 type = 1 Port Packet Over SONET OC-12c/STM-4c
state = Card Powered
Slot 16 type = Clock Scheduler Card
state = Card Powered PRIMARY CLOCK
The following is sample output from the show gsr chassis-info command for a Cisco 12012 router:
Router# show gsr chassis-info
Backplane NVRAM [version 0x20] Contents Chassis: type 12012 Fab Ver: 1
Chassis S/N: ZQ24CS3WT86MGVHL
PCA: 800-3015-1 rev: A0 dev: 257 HW ver: 1.0
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
12.2(33)SRA
Usage Guidelines
This command displays information about the CPU interface, DRAM/device address space, device
parameters, direct memory access (DMA) channels, timers and counters, and protocol control information
(PCI) internal registers. The information is generally useful for diagnostic tasks performed by technical
support only.
Examples
The following is a partial sample output for the show gt64010 command:
Router# show gt64010
GT64010 Channel 0 DMA:
dma_list=0x6088C3EC, dma_ring=0x4B018480, dma_entries=256
dma_free=0x6088CECC, dma_reqt=0x6088CECC, dma_done=0x6088CECC
thread=0x6088CEAC, thread_end=0x6088CEAC
backup_thread=0x0, backup_thread_end=0x0
dma_working=0, dma_complete=6231, post_coalesce_frames=6231
exhausted_dma_entries=0, post_coalesce_callback=6231
GT64010 Register Dump: Registers at 0xB4000000
CPU Interface:
cpu_interface_conf
: 0x80030000 (b/s 0x00000380)
addr_decode_err
: 0xFFFFFFFF (b/s 0xFFFFFFFF)
Processor Address Space :
ras10_low
: 0x00000000 (b/s 0x00000000)
ras10_high
: 0x07000000 (b/s 0x00000007)
ras32_low
: 0x08000000 (b/s 0x00000008)
ras32_high
: 0x0F000000 (b/s 0x0000000F)
cs20_low
: 0xD0000000 (b/s 0x000000D0)
cs20_high
: 0x74000000 (b/s 0x00000074)
cs3_boot_low
: 0xF8000000 (b/s 0x000000F8)
cs3_boot_high
: 0x7E000000 (b/s 0x0000007E)
pci_io_low
: 0x00080000 (b/s 0x00000800)
pci_io_high
pci_mem_low
pci_mem_high
internal_spc_decode
bus_err_low
bus_err_high
:
:
:
:
:
:
0x00000000
0x00020000
0x7F000000
0xA0000000
0x00000000
0x00000000
.
.
.
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
0x00000000)
0x00000200)
0x0000007F)
0x000000A0)
0x00000000)
0x00000000)
show hardware
To display the hardware-specific information for a router, use the show hardwarecommand in user EXEC
or privileged EXEC mode.
show hardware
Syntax Description
Command Modes
Command History
Release
Modification
12.4(22)T
Usage Guidelines
Use the show hardware command to display the hardware specific information for a router.
Examples
Related Commands
Command
Description
show interfaces
show health-monitor
To display the system Health Monitor status information, use the show health-monitorcommand in user
EXEC or privileged EXEC mode.
show health-monitor [summary]
Syntax Description
Command Modes
Command History
summary
Release
Modification
15.0(1)M
Usage Guidelines
Use this command to display the state of the hardware and software subsystem. Health Monitor is a Cisco
IOS subsystem that monitors the state of the individual hardware and software subsystems. This monitoring
helps in early detection and recovery of faults in the subsystem.
Examples
The following is sample output from show health-monitorcommand. The fields are self explanatory.
Router# show health-monitor summary
Chassis:
Power Supply
Temperature
Fans
Memory:
Free Memory processor
Memory Fragmentation Processor
Free Memory I/O
Memory Fragmentation I/O
DFC's:
Slot 1 - Empty DFC
Not
Slot 2 - Empty DFC
Not
Slot 3 - AS5X-FC
Slot 4 - Empty DFC
Not
Slot 5 - Empty DFC
Not
Slot 6 - Empty DFC
Not
Slot 7 - Empty DFC
Not
Failure
OK
OK
OK
OK
OK
OK
in operation
in operation
OK
in operation
in operation
in operation
in operation
show history
To list the commands you have entered in the current EXEC session, use the show history command in
EXEC mode.
show history
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The command history feature provides a record of EXEC commands you have entered. The number of
commands that the history buffer will record is determined by the history size line configuration command
or the terminal history size EXEC command.
The table below lists the keys and functions you can use to recall commands from the command history
buffer.
Table 84
History Keys
Key
Function
Ctrl-P or Up Arrow3
Examples
The following is sample output from the show history command, which lists the commands the user has
entered in EXEC mode for this session:
Router# show history
help
where
show hosts
show history
Router#
Related Commands
Command
Description
history size
Syntax Description
Command Modes
Command History
Release
Modification
12.4(22)T
Usage Guidelines
Use the show history allcommand to display command history and reload information of a router.
Examples
Related Commands
Command
Description
show history
show hosts
To display the default domain name, the style of name lookup service, a list of name server hosts, and the
cached list of hostnames and addresses specific to a particular Domain Name System (DNS) view or for all
configured DNS views, use the show hosts command in privileged EXEC mode.
show hosts [vrf vrf-name] [view [view-name | default]] [all] [hostname | summary]
Syntax Description
vrf vrf-name
Command Modes
default
all
hostname
summary
Command History
Usage Guidelines
Release
Modification
10.0
12.2T
12.4(4)T
12.4(9)T
12.2(33)SRA
12.2SX
This command displays the default domain name, the style of name lookup service, a list of name server
hosts, and the cached list of hostnames and addresses specific to a particular DNS view or for all
configured DNS views.
If you specify the show hosts command without any optional keywords or arguments, only the entries in
the global hostname cache will be displayed.
If the output from this command extends beyond the bottom of the screen, press the Space bar to continue
or press the Q key to terminate command output.
Examples
The following is sample output from the show hosts command with no parameters specified:
Router# show hosts
Default domain is CISCO.COM
Name/address lookup uses domain service
Name servers are 192.0.2.220
Host Flag Age Type Address(es)
EXAMPLE1.CISCO.COM (temp, OK) 1 IP 192.0.2.10
EXAMPLE2.CISCO.COM (temp, OK) 8 IP 192.0.2.50
EXAMPLE3.CISCO.COM (temp, OK) 8 IP 192.0.2.115
EXAMPLE4.CISCO.COM (temp, EX) 8 IP 192.0.2.111
EXAMPLE5.CISCO.COM (temp, EX) 0 IP 192.0.2.27
EXAMPLE6.CISCO.COM (temp, EX) 24 IP 192.0.2.30
The following is sample output from the show hosts command that specifies the VRF vpn101:
Router# show hosts vrf vpn101
Default domain is example.com
Domain list: example1.com, example2.com, example3.com
Name/address lookup uses domain service
Name servers are 192.0.2.204, 192.0.2.205, 192.0.2.206
Codes: UN - unknown, EX - expired, OK - OK, ?? - revalidate
temp - temporary, perm - permanent
NA - Not Applicable None - Not defined
Host
user
www.example.com
Port
None
None
Flags
Age Type
(perm, OK) 0
IP
(perm, OK) 0
IP
Address(es)
192.0.2.001
192.0.2.111
192.0.2.112
The table below describes the significant fields shown in the display.
Table 85
Field
Description
Default domain
Domain list
Name/address lookup
Name servers
Host
Port
Flags
Age
Type
Related Commands
Field
Description
Address(es)
Command
Description
clear host
ip host
show html
To display module and port information, use the show html command in privileged EXEC mode.
show html {module [ports [l2]] | port [all | l2 | l3] [shortnames]} {command line | count | names |
options}
Syntax Description
Command Modes
Command History
module
ports
l2
port
all
l2
l3
shortnames
command
line
count
names
options
Release
Modification
12.4(24)T
Release
Modification
12.2(33)SXI
12.2(33)SRC
Usage Guidelines
Examples
The following is sample output from the show html command using the port and nameskeywords. The
field descriptions are self-explanatory.
Router# show html port names
this[0] = "FastEthernet0/0";
this[1] = "FastEthernet0/1";
this[2] = "Serial2/0";
this[3] = "Serial2/1";
this[4] = "Serial3/0";
this[5] = "Serial3/0.1";
this[6] = "Serial3/1";
this[7] = "Tunnel0";
this[8] = "Tunnel1";
this[9] = "Tunnel2";
this[10] = "Tunnel3";
this[11] = "Virtual-Access1";
this[12] = "Virtual-Template1";
this[13] = "vmi1";
this[14] = "vmi2";
The following is sample output from the show html command using the port, all, and optionskeywords.
The ouput is self-explanatory.
Router# show html port all options
<option>FastEthernet0/0
<option>FastEthernet0/1
<option>Serial2/0
<option>Serial2/1
<option>Serial3/0
<option>Serial3/0.1
<option>Serial3/1
<option>Tunnel0
<option>Tunnel1
<option>Tunnel2
<option>Tunnel3
<option>Virtual-Access1
<option>Virtual-Template1
<option>VoIP-Null0
<option>vmi1
<option>vmi2
show idb
To display information about the status of interface descriptor blocks (IDBs), use the show idbcommand in
privileged EXEC mode.
show idb
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.1
12.2(15)T
12.2(33)SRA
Ether)
Ether)
Ether)
Ether)
The table below describes the significant fields shown in the display.
Table 86
Field
Description
In use
Field
Description
Active
Inactive
Total
show idprom
To display the identification programmable read-only memory (IDPROM) information for fieldreplaceable units (FRUs), use the show idprom command in privileged EXEC mode.
show idprom {all | frutype} [detail]
Syntax Description
Command Modes
Command History
Usage Guidelines
all
frutype
detail
Privileged EXEC
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXE
12.2(33)SRA
backplane
clock number --1 and 2.
earl slot --See the following paragraph for valid slot values.
module slot / port | slot | slot / subslot[clei] }--See the following paragraphs for valid values and
descriptions.
rp slot --See the following paragraph for valid slot values.
power-supply --1 and 2.
supervisor slot --See the following paragraph for valid slot values.
transceiver slot / subslot / port | slot / subslot GigabitEthernet | GigabitEthernetWAN]}
vtt number --1 to 3.
The module slot/port argument designates the module slot location and port number.
Valid values for slot depend on the specified interface type and the chassis and module that are used. For
example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module
that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values
for the port number are from 1 to 48.
The module {slot | slot/subslot [clei]} syntax designates either the slotlocation alone of theSIP in the
chassis (to show information for the SIP only), or the slotlocation of theSIP 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 transceiverslot/
subslotGigabitEthernet form of the command.
Examples
To specify WAN Gigabit Ethernet interfaces, use the show idprom transceiverslot/
subslotGigabitEthernetWAN form of the command.
The following table describes the significant fields shown in the display.
Table 87
Field
Description
FRU is
Field
Description
OEM String
Product Number
Serial Number
Hardware Revision
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')
IDPROM image block #0:
hexadecimal contents of block:
00: AB AB 01 90 11 BE 01 00 00 02 AB 01 00 01 43 69
10: 73 63 6F 20 53 79 73 74 65 6D 73 2C 20 49 6E 63
20: 2E 00 57 53 2D 43 41 43 2D 31 33 30 30 57 00 00
30: 00 00 00 00 00 00 41 43 50 30 33 30 32 30 30 30
40: 31 00 00 00 00 00 00 00 00 00 33 34 2D 30 39 31
50: 38 2D 30 31 00 00 00 00 00 00 41 30 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 01 00 00 00 00 00 00 00 09 00 0C 00 03
80: 00 01 00 06 00 01 00 00 00 00 0A BA 00 00 00 00
block-signature = 0xABAB, block-version = 1,
block-length = 144, block-checksum = 4542
*** common-block ***
IDPROM capacity (bytes) = 256 IDPROM block-count = 2
FRU type = (0xAB01,1)
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
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.12.3.1.6.1.0
..............Ci
sco Systems, Inc
..WS-CAC-1300W..
......ACP0302000
1.........34-091
8-01......A0....
................
................
................
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
FRU
PID
VID SN
CLEI
--------------- -------------------- --- ----------- ---------module #2
7600-SIP-200
V01
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'
Product Number = '7600-SIP-400'
Serial Number = 'JAB0851042X'
Manufacturing Assembly Number = '73-8404-10'
Manufacturing Assembly Revision = '09'
Manufacturing Assembly Deviation = '00'
Hardware Revision = 0.95
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.5.1.3.1.1.2.1103
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
IDPROM for SPA module #5/0
(FRU is '4-port OC3/STM1
Product Identifier (PID)
Version Identifier (VID)
PCB Serial Number
Top Assy. Part Number
73/68 Board Revision
73/68 Board Revision
Hardware Revision
CLEI Code
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
FRU
PID
VID SN
CLEI
--------------- -------------------- --- ----------- ---------SPA module #2/3 SPA-4XOC3-POS
V01 PRTA0304155 UNASSIGNED
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
IDPROM for SPA module #2/3
(FRU is '4-port OC3/STM1 POS Shared Port Adapter')
EEPROM version
: 4
Compatible Type
: 0xFF
Controller Type
: 1088
Hardware Revision
: 0.230
Boot Timeout
: 0 msecs
PCB Serial Number
: PRTA0304155
Part Number
: 73-9313-02
73/68 Board Revision
: 04
Fab Version
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0
Product Identifier (PID) : SPA-4XOC3-POS
Version Identifier (VID) : V01
Top Assy. Part Number
: 68-2169-01
73/68 Board Revision
: 10
System Clock Frequency
: 00 00 00 00 00 00 00 00
00 00 00 00 00
CLEI Code
: UNASSIGNED
Base MAC Address
: 00 00 00 00 00 00
MAC Address block size
: 0
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Calibration Data
: Minimum: 0 dBmV, Maximum: 0 dBmV
Calibration values :
Power Consumption
: 16200 mWatts (Maximum)
Environment Monitor Data : 01 08 F6 48 43 34 F6 48
43 34 02 31 0C E4 46 32
28 13 07 09 C4 46 32 28
13 07 00 00 00 00 00 00
00 05 DC 46 32 28 13 07
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 FE 02 00
00
Asset ID
:
Asset Alias
:
show inventory
To display the product inventory listing of all Cisco products installed in the networking device, use the
show inventorycommand in user EXEC or privileged EXEC mode.
show inventory [raw] [entity]
Syntax Description
Command Modes
Command History
Usage Guidelines
raw
entity
Release
Modification
12.3(4)T
12.0(27)S
12.2(25)S
12.2(27)SBC
12.2(18)SXE5
The show inventorycommand retrieves and displays inventory information about each Cisco product in the
form of a UDI. The UDI is a combination of three separate data elements: a product identifier (PID), a
version identifier (VID), and the serial number (SN).
The PID is the name by which the product can be ordered; it has been historically called the Product
Name or Part Number. This is the identifier that one would use to order an exact replacement part.
The VID is the version of the product. Whenever a product has been revised, the VID will be incremented.
The VID is incremented according to a rigorous process derived from Telcordia GR-209-CORE, an
industry guideline that governs product change notices.
The SN is the vendor-unique serialization of the product. Each manufactured product will carry a unique
serial number assigned at the factory, which cannot be changed in the field. This is the means by which to
identify an individual, specific instance of a product.
The UDI refers to each product as an entity. Some entities, such as a chassis, will have subentities like
slots. Each entity will display on a separate line in a logically ordered presentation that is arranged
hierarchically by Cisco entities.
Use the show inventory command without options to display a list of Cisco entities installed in the
networking device that are assigned a PID.
Examples
The following is sample output from the show inventorycommand without any keywords or arguments.
This sample output displays a list of Cisco entities installed in a router that are assigned a PID.
Router# show inventory
NAME: Chassis, DESCR: 12008/GRP chassis
PID: GSR8/40
, VID: V01, SN: 63915640
NAME: slot 0, DESCR: GRP
PID: GRP-B
, VID: V01, SN: CAB021300R5
NAME: slot 1, DESCR: 4 port ATM OC3 multimode
PID: 4OC3/ATM-MM-SC
, VID: V01, SN: CAB04036GT1
NAME: slot 3, DESCR: 4 port 0C3 POS multimode
PID: LC-4OC3/POS-MM
, VID: V01, SN: CAB014900GU
NAME: slot 5, DESCR: 1 port Gigabit Ethernet
PID: GE-GBIC-SC-B
, VID: V01, SN: CAB034251NX
NAME: slot 7, DESCR: GRP
PID: GRP-B
, VID: V01, SN: CAB0428AN4O
NAME: slot 16, DESCR: GSR 12008 Clock Scheduler Card
PID: GSR8-CSC/ALRM
, VID: V01, SN: CAB0429AUYH
NAME: sfslot 1, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0428ALOS
NAME: sfslot 2, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0429AU0M
NAME: sfslot 3, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0429ARD7
NAME: PSslot 1, DESCR: GSR 12008 AC Power Supply
PID: FWR-GSR8-AC-B
, VID: V01, SN: CAB041999CW
Field
Description
NAME
DESCR
Field
Description
PID
VID
SN
For diagnostic purposes, the show inventorycommand 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.
Router# show inventory raw
NAME: Chassis, DESCR: 12008/GRP chassis
PID:
, VID: V01, SN: 63915640
NAME: slot 0, DESCR: GRP
PID:
, VID: V01, SN: CAB021300R5
NAME: slot 1, DESCR: 4 port ATM OC3 multimode
PID: 4OC3/ATM-MM-SC
, VID: V01, SN: CAB04036GT1
NAME: slot 3, DESCR: 4 port 0C3 POS multimode
PID: LC-4OC3/POS-MM
, VID: V01, SN: CAB014900GU
Enter the show inventorycommand 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
PID: GSR8-SFC
, VID: V01, SN: CAB0428ALOS
NAME: sfslot 2, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0429AU0M
NAME: sfslot 3, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0429ARD7
You can request even more specific UDI information using the show inventorycommand 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
NAME: sfslot 1, DESCR: GSR 12008 Switch Fabric Card
PID: GSR8-SFC
, VID: V01, SN: CAB0428ALOS
Related Commands
Command
Description
show diag
Command
Description
show tech-support
show location
To display the location information for an endpoint, use the show location command in user EXEC or
privileged EXEC mode.
show location {{civic-location | custom-location | geo-location {identifier id | interface name type
| static}} | host}
Syntax Description
Command Modes
Command History
Examples
civic-location
custom-location
geo-location
host
identifier id
static
Release
Modification
12.2(40)SE
12.2(55)SE
15.1(1)SG
The following sample output from the show location civic-location command displays all the civic
location information for a specific identifier:
Device# show location civic-location identifier test
Civic location information
-------------------------Identifier
: test
Building
: 24
City
State
Ports
: Milpitas
: California
: Gi1/0/10
The following sample output from the show location custom-location command displays custom location
information of a host device:
Device# show location custom-location identifier
Custom location information
--------------------------Identifier: host
Name
: bgl15
Value
: IDF2.5
The following sample output from the show location geo-location
command displays geo-spatial location information of a device:
Device# show location geo-location identifier apjtpk
Geo location information
-----------------------Identifier : apjtpk
Latitude
: 54.45
Longitude
: 37.43
Altitude
: 5 floor
Resolution : 54.45
The following sample output from the show location host
command displays all host information of a device:
Device# show location host
Civic location information
-------------------------Identifier
: host
County
: raps
City Division
: SJ
Neighborhood
: lake
Street Group
: G2
Leading street direction: trav
Trailing street suffix : C76
Street number
: 18
Street number suffix
: 54
Landmark
: park
Name
: KMD
Building
: bgl13
Unit
: apjtpk
Floor
: 3
Room
: Andaman
Type of place
: office
Postal community name
: ios
Post office box
: 12
Additional code
: apjtpk
Seat
: B5-10
Primary road name
: outerringrd
Road section
: east
Branch road name
: venus
Sub branch road name
: Tata
Street name postmodifier: ret
City
: Boston
State
: CA
Postal code
: 1345
Additional location
: cauveri
Custom location information
--------------------------Identifier: host
Name
: bgl15
Value
: IDF2.5
Geo location information
-----------------------Identifier : host
Latitude
: 12.34
Longitude
: 56.78
The following table describes the significant fields shown in the display.
Table 89
Related Commands
Field
Description
Identifier
Name
Value
Latitude
Longitude
Altitude
Resolution
Command
Description
show logging
To display the state of system logging (syslog) and the contents of the standard system logging buffer, use
the show logging command in privileged EXEC mode.
show logging [slot slot-number | summary]
Syntax Description
Command Modes
Command History
slot slot-number
summary
Privileged EXEC
Release
Modification
10.0
11.2 GS
12.2(8)T
12.2(15)T
12.3(2)T
12.3(2)XE
12.2(14)SX
Usage Guidelines
Release
Modification
12.2(25)S
12.2(33)SRA
12.4(11)T
12.2(33)SB
This command displays the state of syslog error and event logging, including host addresses, and which
logging destinations (console, monitor, buffer, or host) logging is enabled. This command also displays
Simple Network Management Protocol (SNMP) logging configuration parameters and protocol activity.
This command will also display the contents of the standard system logging buffer, if logging to the buffer
is enabled. Logging to the buffer is enabled or disabled using the [no] logging buffered command. The
number of system error and debugging messages in the system logging buffer is determined by the
configured size of the syslog buffer. This size of the syslog buffer is also set using the logging buffered
command.
To enable and set the format for syslog message time stamping, use the service timestamps logcommand.
If debugging is enabled (using any debug command), and the logging buffer is configured to include level
7 (debugging) messages, debug output will be included in the system log. Debugging output is not
formatted like system error messages and will not be preceded by the percent symbol (%).
Examples
The following is sample output from the show logging command on a software image that supports the
Embedded Syslog Manager (ESM) feature:
Router# show logging
Syslog logging: enabled (10 messages dropped, 5 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 31 messages logged, xml disabled,
filtering disabled
Monitor logging: disabled
Buffer logging: level errors, 36 messages logged, xml disabled,
filtering disabled
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
No active filter modules.
Trap logging: level informational, 45 message lines logged
Log Buffer (8192 bytes):
The following example shows output from the show logging command after a message discriminator has
been configured. Included in this example is the command to configure the message discriminator.
c7200-3(config)# logging discriminator ATTFLTR1 severity includes 1,2,5 rate-limit 100
The table below describes the significant fields shown in the output for the two preceding examples.
Table 90
Field
Description
Syslog logging:
Field
Description
Console logging:
Monitor logging:
Buffer logging:
Trap logging:
SNMP logging
Field
Description
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
.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.
The table below describes the symbols that precede the time stamp.
Table 91
Symbol
Description
Example
(blank)
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.
Router# show logging summary
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
SLOT | EMERG | ALERT | CRIT | ERROR |WARNING| NOTICE| INFO | DEBUG |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
|* 0* |
. |
. |
. |
. |
. |
. |
. |
. |
| 1 |
|
|
|
|
|
|
|
|
| 2 |
|
|
|
1 |
4 |
45 |
|
|
| 3 |
|
|
|
|
|
|
|
|
| 4 |
|
|
|
5 |
4 |
54 |
|
|
| 5 |
|
|
|
|
|
|
|
|
| 6 |
|
|
|
|
|
|
|
|
| 7 |
|
|
|
17 |
4 |
48 |
|
|
| 8 |
|
|
|
|
|
|
|
|
| 9 |
|
|
|
1 |
4 |
47 |
|
|
| 10 |
|
|
|
|
|
|
|
|
| 11 |
|
|
|
12 |
4 |
65 |
|
|
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
Router#
The table below describes the logging level fields shown in the display.
Table 92
Field
Description
SLOT
EMERG
Related Commands
Field
Description
ALERT
CRIT
ERROR
WARNING
NOTICE
INFO
DEBUG
Command
Description
clear logging
logging count
logging linecard
service timestamps
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(8)T
To enable the error log count capability (syslog counting feature), use the logging count command in
global configuration mode.
This feature works independently of the various settings of the other logging commands (such as [no]
logging on, [no] logging buffered, and so on). In other words, turning off logging by other means does not
stop the counting and timestamping from occuring.
This command displays information such as the number of times a particular system error message occurs
and the time stamp of the last occurrence of the specified message. System error messages are grouped into
logical units called Facilities based on Cisco IOS software components.
To determine if system error message counting is enabled, use the show logging command.
The service timestamps command configuration determines the timestamp format (shown in the Last
Time column) of show logging count command output. There is not quite enough space for all options of
the possible options (datetime, milliseconds, and timezone) of the service timestamps datetimecommand
to be displayed at the same time. As a result, if msec is selected, timezone will not be displayed. If showtimezone is selected but not msec, then the time zone will be displayed.
Occasionally, the length of the message name plus the facility name contains too many characters to be
printed on one line. The CLI attempts to keep the name and facility name on one line but, if necessary, the
line will be wrapped, so that the first line contains the facility name and the second line contains the
message name and the rest of the columns.
Examples
The following example shows the number of times syslog messages have occurred and the most recent time
that each error message occurred. In this example, the show logging command is used to determine if the
syslog counting feature is enabled:
Router# show logging | include count
The table below describes the significant fields shown in the display.
Table 93
Field
Description
Facility
Message Name
Sev
Occur
Last Time
Related Commands
Command
Description
clear logging
logging count
3
13
13
1
Command
Description
service timestamps
show logging
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command displays information about the syslog history table, such as the table size, the status of
messages, and text of messages stored in the table. Messages stored in the table are governed by the
logging history global configuration command.
Examples
The following example shows sample output from the show logging history command. In this example,
notifications of severity level 5 (notifications) through severity level 0 (emergencies) are configured to be
written to the logging history table.
Router# show logging history
Syslog History Table: 1 maximum table entries,
saving level notifications or higher
0 messages ignored, 0 dropped, 15 table entries flushed,
SNMP notifications not enabled
entry number 16: SYS-5-CONFIG_I
Configured from console by console
timestamp: 1110
Router#
The table below describes the significant fields shown in the output.
Table 94
Related Commands
Field
Description
messages ignored
dropped
SNMP notifications
entry number:
timestamp
Command
Description
clear logging
logging history
Command
Description
logging linecard
Syntax Description
disk
disk file-location
num-of-last-log-msgs
Command Default
Command Modes
Command History
Release
Modification
12.2(33)SXH
12.2(33)SCC
Usage Guidelines
Examples
The following example shows a sample output of the show logging system command that displays the
specified number of latest system log messages:
Router# show logging system
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
=====================================================
1: 01/24/07
2: 01/24/07
sw_mode 1
3: 01/24/07
sw_mode 1
4: 01/24/07
sw_mode 1
5: 01/24/07
sw_mode 1
6: 01/24/07
sw_mode 1
7: 01/24/07
sw_mode 1
The table below describes the significant fields shown in the display.
Table 95
Field
Description
MOD/SUB
SEV
COMP
The following example shows a sample output of the show logging system command that displays SEA
logs from the specified file location:
Router# show logging system disk disk0:my_log.dat
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
=====================================================
1: 02/01/95 00:35:51
2/3/-1: MAJ, GOLD, lc_ctrl_proc_obfl_info:test SEA log in
DFC:Diagnostic OBFL testing
2: 02/01/95 00:35:09
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/2]: sp_netint_thr[0]
3: 02/01/95 00:35:09
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/2]:
SP[81%],Tx_rate[408], Rx_rate[0]
4: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/2]: sp_netint_thr[0]
5: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/2]:
SP[82%],Tx_rate[453], Rx_rate[0]
6: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD, test_c2cot_hm_ch0_test[3]: port 13, chnl 0,
Skipped Fabric Channel HM Test
7: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD,
fabric_hm_inband_loopback_test[3/13]:diag_hit_sys_limit!test skipped.
8: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/13]: sp_netint_thr[0]
9: 02/01/95 00:35:08
2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/13]: SP[83%],
Tx_rate[453], Rx_rate[0]
The following command is used to identify the disk on PRE currently being used to store the sea_log.dat
file. The following example shows a sample output of the show logging system disk command executed
on the Cisco uBR10012 router:
Router# show logging system
disk
SEA log disk: disk1:
The following command is used to view the specified number of log messages stored in the
sea_log.dat file. The following example shows a sample output of the show logging system
last 10
command on the Cisco uBR10012 router:
Router# show logging system
last 10
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP,
MESSAGE
=====================================================
1: 05/06/09 04:47:48 5/0: NON, SEATEST, "Second Message"
2: 05/06/09 04:47:31 6/0: NON, SEATEST, "First Message"
Related Commands
logging system
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(15)T
12.2(28)SB
12.2(33)SRE
Usage Guidelines
This command displays the same syslog state information as the standard show logging command, but
displays the information in XML format. This command also displays the content of the XML syslog buffer
(if XML-formatted buffer logging is enabled).
Examples
The following example compares the output of the standard show logging command with the output of the
show logging xml command so that you can see how the standard information is formatted in XML.
Router# show logging
Syslog logging: enabled (10 messages dropped, 6 messages rate-limited, 0 flushes, 0
overruns, xml enabled)
Console logging: level debugging, 28 messages logged, xml enabled
Monitor logging: level debugging, 0 messages logged, xml enabled
Buffer logging: level debugging, 2 messages logged, xml enabled (2 messages logged)
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
Trap logging: level informational, 35 message lines logged
Logging to 10.2.3.4, 1 message lines logged, xml disabled
Logging to 192.168.2.1, 1 message lines logged, xml enabled
Log Buffer (8192 bytes):
00:04:20: %SYS-5-CONFIG_I: Configured from console by console
00:04:41: %SYS-5-CONFIG_I: Configured from console by console
Router# show logging xml
<syslog-logging status="enabled" msg-dropped="10" msg-rate-limited="6" flushes="0"
overruns="0"><xml>enabled</xml></syslog-logging>
The table below describes the significant fields shown in the displays.
Table 96
Related Commands
Field
Description
XML Tag
Syslog logging
syslog-logging
Console logging
console-logging
Monitor logging
monitor-logging
Buffer logging
buffer-logging
Trap logging
trap-logging
Command
Description
show logging
show memory
To display statistics about memory when Cisco IOS software, Cisco IOS XE or Software Modularity
images are running, use the show memory command in user EXEC or privileged EXEC mode.
Cisco IOS software
show memory [memory-type] [free] [overflow] [summary] [poisoning]
Cisco IOS XE or Software Modularity
show memory
Syntax Description
memory-type
free
overflow
summary
poisoning
Command Modes
Alloc PID
Alloc Check
Alloc PC
Alloc Name
Corrupt Ptr
Corrupt Val
TotalBytes
MarkedBytes
TIME
Command History
Usage Guidelines
Release
Modification
10.0
12.3(7)T
12.2(25)S
12.3(14)T
12.2(27)SBC
12.2(18)SXF4
12.2(33)SRA
12.4(20)T
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software
images. To view the appropriate output, see the following sections:
Used(b)
2210036
Ref
1
1
1
1
1
1
1
1
1
1
1
1
Free(b)
2971860
PrevF
NextF
Lowest(b) Largest(b)
2692456
2845368
Alloc PC
18F132
18F132
141384
14353C
14356C
1A110E
970DE8
18F132
19ABCE
19ABCE
19ABCE
19ABCE
What
List Elements
List Headers
TTY data
TTY Input Buf
TTY Output Buf
Interrupt Stack
*Init*
messages
Watched Boolean
Watched Boolean
Watched Boolean
Watched Boolean
The following is sample output from the show memory free command:
Router# show memory free
Head
Total(b)
Processor
B0EE38
5181896
Processor memory
Address
Bytes Prev.
Next
24
Free list 1
CEB844
32 CEB7A4 CEB88C
52
Free list 2
72
Free list 3
76
Free list 4
80
Free list 5
D35ED4
80 D35E30
D35F4C
D27AE8
80 D27A48
D27B60
88
Free list 6
100
Free list 7
D0A8F4
100 D0A8B0
D0A980
104
Free list 8
B59EF0
108 B59E8C
B59F84
Used(b)
2210076
Ref
PrevF
NextF
Alloc PC
What
96B894
SSE Manager
0
0
0
D35ED4
D27AE8
0
96B894
22585E
SSE Manager
SSE Manager
2258DA
SSE Manager
2258DA
(fragment)
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. The table below describes the significant fields shown in the first section of the display.
Table 97
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
The second section of the display is a block-by-block listing of memory use. The table below describes the
significant fields shown in the second section of the display.
Table 98
Field
Description
Address
Bytes
Prev.
Next
Ref
PrevF
NextF
Alloc PC
What
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
Address
Bytes Prev.
6132DA0
59264 6132664
600DDEC
500 600DA4C
600FE68
376 600FAC8
6011D54
652 60119B4
614FCA0
832 614F564
6177640 2657056 6172E90
Total: 2723244
Next
6141520
600DFE0
600FFE0
6011FEO
614FFE0
0
Ref
0
0
0
0
0
0
PrevF
0
6132DA0
600DDEC
600FE68
601FD54
614FCA0
NextF
600DDEC
600FE68
6011D54
6013D54
6177640
0
Alloc PC
3FCF0
0
0
0
0
0
What
*Packet Buffer*
The following sample output displays details of a memory block overflow correction when the exception
memory ignore overflow global configuration command is configured:
Router# show memory overflow
Count
Buffer Count
Last corrected
Crashinfo files
1
1
00:11:17
slot0:crashinfo_20030620-075755
Traceback
607D526C 608731A0 607172F8 607288E0 607A5688 607A566C
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
Address
Bytes Prev.
Next
7AE0
38178 72F0
0
Total
38178
Ref
0
PrevF
0
NextF
0
Alloc PC
0
What
The following sample output from the show memory command used on the Cisco 4000 router includes
information about SRAM memory and I/O memory:
Router# show memory
Head
Total(b)
Processor
49C724
28719324
I/O
6000000
4194304
SRAM
1000
65536
Address
Bytes Prev.
Next
1000
2032 0
17F0
17F0
2032 1000
1FE0
1FE0
544 17F0
2200
2200
52 1FE0
2234
2234
52 2200
2268
2268
52 2234
229C
72F0
2032 6E5C
7AE0
7AE0
38178 72F0
0
Used(b)
Free(b)
1510864
27208460
1297088
2897216
63400
2136
Ref PrevF
NextF
1
1
1
1
1
1
1
0
0
0
Lowest(b)
26511644
2869248
2136
Alloc PC
3E73E
3E73E
3276A
31D68
31DAA
31DF2
3E73E
0
Largest(b)
15513908
2896812
2136
What
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
Init
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 the tables above.
Router# show memory summary
Head
Total(b)
Used(b)
Free(b) Lowest(b) Largest(b)
Processor
B0EE38
5181896
2210216
2971680
2692456
2845368
Processor memory
Alloc PC
Size
Blocks
Bytes
What
0x2AB2
192
1
192
IDB: Serial Info
0x70EC
92
2
184
Init
0xC916
128
50
6400
RIF Cache
0x76ADE
4500
1
4500
XDI data
0x76E84
4464
1
4464
XDI data
0x76EAC
692
1
692
XDI data
0x77764
408
1
408
Init
0x77776
116
1
116
Init
0x777A2
408
1
408
Init
0x777B2
116
1
116
Init
0xA4600
24
3
72
List
0xD9B5C
52
1
52
SSE Manager
.
.
.
0x0
0
3413
2072576
Pool Summary
0x0
0
28
2971680
Pool Summary (Free Blocks)
0x0
40
3441
137640
Pool Summary (All Block Headers)
0x0
0
3413
2072576
Memory Summary
0x0
0
28
2971680
Memory Summary (Free Blocks)
Cisco IOS XE
The following is sample output from the show memory command when a Cisco IOS XE image is running.
Router# show memory
#show memory
System memory
Lowest(b)
Process
Config
The table below describes the significant fields shown in the display.
Table 99
Field
Description
total
used
free
kernel reserved
Process
Config
The table below describes the significant fields shown in the display.
Table 100
Field
Description
total
used
free
kernel reserved
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
totals
Release
Modification
12.0
Usage Guidelines
The show memory allocating-processcommand displays information about memory available after the
system image decompresses and loads.
Examples
The following is sample output from the show memory allocating-process command:
Router# show memory allocating-process
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
Processor
44E03560
186632636
26131896
160500740
160402052
153078204
Fast
44DE3560
131072
58280
72792
72792
72764
Processor memory
Address Bytes Prev.
Next
Ref
Alloc Proc
Alloc PC What
6148EC40
1504 0
6148F24C
1 *Init*
602310FC List Elements
6148F24C
3004 6148EC40 6148FE34
1 *Init*
60231128 List Headers
6148FE34
9000 6148F24C 61492188
1 *Init*
6023C634 Interrupt Stack
61492188
44 6148FE34 614921E0
1 *Init*
60C17FD8 *Init*
614921E0
9000 61492188 61494534
1 *Init*
6023C634 Interrupt Stack
61494534
44 614921E0 6149458C
1 *Init*
60C17FD8 *Init*
6149458C
220 61494534 61494694
1 *Init*
602450F4 *Init*
61494694
4024 6149458C 61495678
1 *Init*
601CBD64 TTY data
.
.
.
The table below describes the significant fields shown in the display.
Table 101
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
Address
Bytes
Prev.
Next
Ref
Alloc PC
What
The following is sample output from the show memory allocating-process totalscommand:
Router# show memory allocating-process totals
Head
Total(b)
Used(b)
Free(b)
Processor
44E03560
186632636
26142524
160490112
Fast
44DE3560
131072
58280
72792
Allocator PC Summary for: Processor
PC
Total
Count Name
0x4041AF8C
5710616
3189 *Packet Data*
0x4041AF40
2845480
3190 *Packet Header*
0x404DBA28
1694556
203 Process Stack
0x4066EA68
1074080
56 Init
0x404B5F68
1049296
9 pak subblock chunk
0x41DCF230
523924
47 TCL Chunks
0x404E2488
448920
6 MallocLite
0x4066EA8C
402304
56 Init
0x40033878
397108
1 Init
0x41273E24
320052
1 CEF: table event ring
0x404B510C
253152
24 TW Buckets
0x42248F0C
229428
1 Init
0x42248F28
229428
1 Init
Lowest(b)
160402052
72792
Largest(b)
153078204
72764
0x42248F48
0x423FF210
0x421CB530
0x417A07F0
0x403AFF50
229428
218048
208144
196764
187836
1
5
1
3
3
Init
Dn48oC!M
epa crypto blk
L2TP Hash Table
Init
The table below describes the significant fields shown in the display.
Table 102
Related Commands
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
PC
Program counter
Total
Count
Number of allocations.
Name
Command
Description
Syntax Description
Command Modes
Command History
totals
Release
Modification
12.0
12.2SX
Usage Guidelines
The show memory deadcommand displays information about processes that have been terminated.
Terminated processes accounts for memory allocated under another process.
Examples
The following is sample output from the show memory dead command:
Router# show memory dead
Head
Total(b)
Used(b)
I/O
600000
2097152
1635960
Free(b)
461024
Lowest(b)
1636128
Largest(b)
1635224
Processor memory
Address
1D8310
2CA964
2CAA04
2CAAA0
2ED714
2F12AC
2F1304
2F1348
300C28
Bytes
60
36
112
68
52
44
24
68
340
Prev.
1D82C8
2CA914
2CA9B4
2CAA04
2ED668
2F124C
2F12AC
2F1304
300A14
Next
1D8378
2CA9B4
2CAAA0
2CAB10
2ED774
2F1304
2F1348
2F13B8
300DA8
Ref
1
1
1
1
1
1
1
1
1
PrevF
NextF
Alloc PC
3281FFE
3281FFE
3A42144
3A420D4
3381C84
3A50234
3A420D4
3381C84
3381B42
The table below describes the significant fields shown in the display.
What
Router Init
Router Init
OSPF Stub LSA RBTree
Router Init
Router Init
Router Init
Router Init
Router Init
Router Init
Table 103
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
Address
Bytes
Prev.
Next
Ref
PrevF
NextF
Alloc PC
What
Syntax Description
Command Modes
Command History
Usage Guidelines
allocations
leaks
lowmem
summary
status
Privileged EXEC
Release
Modification
12.3(7)T
12.2(33)SRA
12.4T
The show memory debug incremental allocations command displays all the memory blocks that were
allocated after the set memory debug incremental starting-time command was entered. The displayed
memory blocks are just memory allocations, they are not necessarily leaks.
The show memory debug incremental leaks command provides output similar to the show memory
debug leaks command, except that it displays only memory that was leaked after the set memory debug
incremental starting-time command was entered.
The show memory debug incremental leaks lowmem command forces memory leak detection to work in
low memory mode. The amount of time taken for analysis is considerably greater than that of normal mode.
The output for this command is similar to the show memory debug leaks command, except that it displays
only memory that was leaked after the set memory debug incremental starting-time command was
entered. You can use this command when you already know that normal mode memory leak detection will
fail (perhaps by an unsuccessful previous attempt to invoke normal mode memory leak detection).
The show memory debug incremental leaks summary command displays a summarized report of the
memory that was leaked after the set memory debug incremental starting-time command was entered,
ordered by allocator process call address (Alloc_pc) and by memory block size.
The show memory debug incremental status command displays whether a starting point for incremental
analysis has been set and the elapsed time since then.
Note
All show memory debug commands must be used on customer networks only to diagnose the router for
memory leaks when memory depletion is observed. These CLIs will have high CPU utilization and might
result in time sensitive protocols to flap. These CLIs are recommended for customer use, only in the
maintenance window when the router is not in a scaled condition.
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.
Examples
show memory debug incremental allocations Command Example
The following example shows output from the show memory debug incrementalcommand when entered
with the allocations keyword:
Router# show memory debug incremental allocations
Address
Size
Alloc_pc PID Name
62DA4E98
176 608CDC7C 44
CDP Protocol
62DA4F48
88 608CCCC8 44
CDP Protocol
62DA4FA0
88 606224A0 3
Exec
62DA4FF8
96 606224A0 3
Exec
635BF040
96 606224A0 3
Exec
63905E50
200 606A4DA4 69
Process Events
Alloc PC
Alloc PC
0x60874198
0x60874198
0x60874198
0x60874228
0x60874228
0x60874228
I/O memory
Size
Blocks
Bytes
What
Processor memory
Size
Blocks
Bytes
0000000052 0000000001 0000000052
0000000060 0000000001 0000000060
0000000100 0000000001 0000000100
0000000052 0000000004 0000000208
0000000060 0000000002 0000000120
0000000100 0000000004 0000000400
What
Exec
Exec
Exec
Exec
Exec
Exec
Related Commands
Command
Description
Syntax Description
Command Modes
Command History
chunks
largest
lowmem
summary
Privileged EXEC
Release
Modification
12.3(8)T1
12.2(25)S
12.2(33)SRA
Usage Guidelines
If no optional keywords are specified, the show memory debug leaks command invokes normal mode
memory leak detection and does not look for memory leaks in chunks.
The show memory debug leaks chunks command invokes normal mode memory leak detection and looks
for leaks in chunks as well.
The show memory debug leaks largest command displays the top ten leaking allocator_pcs and the total
amount of memory that they have leaked. Additionally, each time this command is invoked it remembers
the previous invocation's report and compares it to the current invocation's report. If there are new entries in
the current report they are tagged as inconclusive. If the same entry appears in the previous invocation's
report and the current invocation's report, the inconclusive tag is not added. It would be beneficial to run
memory leak detection more than once and to consider only the consistently reported leaks.
The show memory debug leaks lowmem command forces memory leak detection to work in low memory
mode. The amount of time taken for analysis is considerably greater than that of normal mode. The output
for this command is similar to the show memory debug leaks command. You can use this command when
you already know that normal mode memory leak detection will fail (perhaps by an unsuccessful previous
attempt to invoke normal mode memory leak detection).
The show memory debug leaks summary command reports memory leaks based on allocator_pc and then
on the size of the block.
Examples
Note
All show memory debug commands must be used on customer networks only to diagnose the router for
memory leaks when memory depletion is observed. These CLIs will have high CPU utilization and might
result in time sensitive protocols to flap. These CLIs are recommended for customer use, only in the
maintenance window when the router is not in a scaled condition.
Note
The command show memory debug leak lowmem is extremely CPU intensive and can result in
CPUHOG/WATCHDOG crash. This command must be used only when the router has reached an unusable
state due to memory exhaustion. Its use on high end platforms such as ISR and above can potentially crash
the box. Use outside of these limitations can cause a console hang of 1 hour in some cases. As an
alternative, use the show memory debug leak command.
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software
images. To view the appropriate output, choose one of the following sections:
Name
Address
Address
62DABD28
62DABD78
62DCF240
62DCF298
62DCF2F8
62DCF350
63336C28
63370D58
633710A0
63B2BF68
63BA3FE0
63BB4020
Size
The table below describes the significant fields shown in the display.
Table 104
Field
Description
Address
Size
Alloc_pc
PID
Name
Process
Process
)
)
)
)
62D80DE8
62E8FD60
The table below describes the significant fields shown in the display.
Table 105
Field
Description
Address
Size
Alloc_pc
PID
Name
Size
Parent
Name
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...
PCI memory
Alloc_pc
total leak size
I/O memory
Alloc_pc
total leak size
Processor memory
Alloc_pc
total leak size
608D2848
32776
608D2FD8
32776
60C656AC
60C67D74
605B7E98
605B7EDC
60C659D4
605B7E70
605B7EB4
60616750
288
48
40
40
40
32
32
24
What
What
What
Init
Init
Init
Init
Init
Init
Audit Process
Audit Process
Init
Init
Init
Init
The table below describes the significant fields shown in the display.
Table 106
Field
Description
Alloc_pc
Size
Blocks
Bytes
What
Name
iosd
The table below describes the significant fields shown in the display.
Table 107
Related Commands
Field
Description
Leak
PID
Name
Command
Description
Syntax Description
Command Modes
Command History
dangling
start-address
Release
Modification
12.0
Usage Guidelines
All show memory debug commands must be used on customer networks only to diagnose the router for
memory leaks when memory depletion is observed. These CLIs will have high CPU utilization and might
result in time sensitive protocols to flap. These CLIs are recommended for customer use, only in the
maintenance window when the router is not in a scaled condition.
Examples
The following is sample output from the show memory debug referencescommand:
Router# show memory debug references 2 3
Address Reference Cont_block Cont_block_name
442850BC
2 44284960
bss
44285110
3 44284960
bss
4429C33C
2 44284960
bss
4429C34C
2 44284960
bss
4429C35C
3 44284960
bss
.
.
.
The following is sample output from the show memory debug references danglingcommand:
Router# show memory debug references dangling
Address Reference Free_block Cont_block Cont_block_name
442D5774 458CE5EC 458CE5BC
44284960
bss
442D578C 46602998 46602958
44284960
bss
442D58A0 465F9BC4 465F9B94
44284960
bss
442D58B8 4656785C
442D5954 45901E7C
.
.
.
4656781C
45901E4C
44284960
44284960
bss
bss
The table below describes the significant fields shown in the displays.
Table 108
Field
Description
Address
Reference
Free_block
Cont_block
Cont_block_name
Syntax Description
Command Modes
Command History
Examples
Release
Modification
12.0
The following is sample output from the show memory debug unusedcommand:
Router# show memory debug unused
Address Alloc_pc PID size
Name
654894B8 62BF31DC -2
44
*Init*
6549A074 601F7A84 -2
4464
XDI data
6549B218 601F7274 -2
4500
XDI data
6549DFB0 6089DDA4 42
84
Init
65509160 6089DDA4 1
84
*Init*
6550A260 6089DDA4 2
84
*Init*
6551FDB4 6089DDA4 4
84
*Init*
6551FF34 627EFA2C -2
24
*Init*
65520B3C 6078B1A4 -2
24
Parser Mode
65520B88 6078B1C8 -2
24
Parser Mode
65520C40 6078B1A4 -2
24
Parser Mode
65520C8C 6078B1C8 -2
24
Parser Mode
65520D44 6078B1A4 -2
24
Parser Mode
65520D90 6078B1C8 -2
24
Parser Mode
65520E48 6078B1A4 -2
24
Parser Mode
65520E94 6078B1C8 -2
24
Parser Mode
65520F4C 6078B1A4 -2
24
Parser Mode
65520F98 6078B1C8 -2
24
Parser Mode
65521050 6078B1A4 -2
24
Parser Mode
6552109C 6078B1C8 -2
24
Parser Mode
65521154 6078B1A4 -2
24
Parser Mode
655211A0 6078B1C8 -2
24
Parser Mode
.
.
.
Q1
Q2
Q1
Q2
Q1
Q2
Q1
Q2
Q1
Q2
Q1
Q2
Q1
Q2
The table below describes the significant fields shown in the display.
Table 109
Field
Description
Address
Alloc_pc
PID
size
Name
Syntax Description
Command Default
process-id
process-name
start-address
end-address
bigger
free
io
overflow
physical
shared
statistics
summary
No detailed memory information about POSIX and Cisco IOS processes is displayed.
Command Modes
Command History
Release
Modification
12.2(18)SXF4
Usage Guidelines
Detailed output of the process memory on the device is displayed with this command. The process memory
summary is displayed first, followed by POSIX and Cisco IOS memory information. The POSIX memory
information includes the address, the size in bytes, and the type of memory used by various segments such
as program text, data, stack, shared memory, device memory, and heap. Cisco IOS memory information
includes the native Cisco IOS display of memory blocks maintained by the Cisco IOS memory
management library.
Examples
Example output varies between Cisco IOS software releases. To view the appropriate output, choose one of
the following sections:
The first section of the display shows system summary information. The table below describes the
significant fields shown in the first section of the display.
Table 110
Field
Description
total
used
free
kernel reserved
The second section of the display includes process summary statistics about the activities of the system
memory allocator. The table below describes the significant fields shown in the second section of the
display.
Table 111
Field
Description
Process
type
PID
Process ID.
total
text
data
stack
dynamic
heapsize
allocated
free
The third section of the display shows POSIX process perspective memory information. The table below
describes the significant fields shown in the third section of the display.
Table 112
Field
Description
Address
Bytes
What
The fourth section of the display shows Cisco IOS memory information as a block-by-block listing of
memory use. The table below describes the significant fields shown in the fourth section of the display.
Table 113
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
Address
Bytes
Prev
Next
PrevF
NextF
Alloc PC
Field
Description
what
The following is sample output from the show memory detailedcommand for a POSIX process:
Router# show memory detailed 12290
System Memory: 131072K total, 115876K used, 15196K free 4000K kernel reserved
Process sbin/sysmgr.proc, type POSIX, PID = 12290
400K total, 100K text, 144K data, 12K stack, 144K dynamic
81920 heapsize, 68716 allocated, 8824 free
Address
Bytes What
0x7FDF000
126976 Program Stack (pages not allocated)
0x7FFE000
4096 Program Stack
0x8000000
122880 Program Stack (pages not allocated)
0x801E000
8192 Program Stack
0x8020000
102400 Program Text
0x8039000
147456 Program Data
0x805D000
8192 Heap Memory
0x8060000
16384 Heap Memory
0x8064000
16384 Heap Memory
0x8068000
8192 Heap Memory
0x806C000
16384 Heap Memory
0x8070000
16384 Heap Memory
0x8074000
16384 Heap Memory
0x8078000
16384 Heap Memory
0x807C000
16384 Heap Memory
0x8080000
16384 Heap Memory
The following partial sample output from the show memory detailed command with a process name and
the physical keyword that displays the summary of physical memory used by the specified process along
with the shared memory details:
Router# show memory detailed sysmgr.proc physical
Pid
Data
Stack Dynamic
Text Shared Maps Process
20482
304K
16K
256K
3480K
468K
60 sysmgr.proc
Total Physical Memory used or mapped by sysmgr.proc
Private memory used (Data/Stack/Dynamic) :
576K
Shared memory mapped (Text/Shared)
:
3948K
Number of memory maps
:
60
Dev
1:Text/Data 2:Mapped 3:Shared 4:DSO
Flags SHD:Shared PRV:Private FXD:Fixed ANN:Anon PHY:Phys
LZY:Lazy ELF:Elf STK:Stack NOC:Nocache
Phy Addr
Size
Pid
Virt Addr What
Dev Prot
MapFlags
0x0
32768K 20482 0x70000000 Text
4 R-X SHD FXD ELF
0x2000000
32768K 20482 0x72000000 Text
4 R-X SHD FXD ELF
0x4000000
32768K 20482 0x74000000 Text
4 R-X SHD FXD ELF
0x522B000
4K 20482 0x1020000
Text
4 R-X SHD FXD ELF
Phy Addr
Size
Pid
Virt Addr What
Dev Prot
MapFlags
0x9EFD4000
32K 20482 0x105C000
Heap
2 RW- PRV ANN
0x9EFF0000
32K 20482 0x1054000
Heap
2 RW- PRV ANN
0x9EFF8000
32K 20482 0x1034000
Heap
2 RW- PRV ANN
0x9F003000
4K 20482 0x7B43C000 Data
4 RW- PRV FXD ANN ELF
.
.
.
The table below describes the significant fields shown in the display.
Table 114
Field
Description
Shared
Maps
Process
Flags
Phy Addr
Size
Virt Addr
Prot
Field
Description
MapFlags
Field descriptions are the same as those in the show memory detailed, page 1021 example.
Switch#show memory detailed proc iosd
System memory : 883144K total, 591378K used, 291766K free, 165432K kernel reserved
Lowest(b)
: 5128192
Process iosd, type L, PID = 11007
777572K total, 82212K text, 537120K data, 84K stack, 240K dynamic
240 heapsize, 240 allocated, 0 free
Head
Total(b)
Used(b)
Free(b)
Lowest(b) Largest(b)
Processor
90150008
536870912
261852128
275018784
273655520
272592492
I/O
B0151000
16777216
169288
16607928
16598952
16598948
Processor memory
Address
Bytes
Prev
Next Ref
PrevF
NextF Alloc PC what
90150008 0000000436 00000000 901501E8 001 -------- -------- 1028C010 *Init*
901501E8 0000020004 90150008 90155038 001 -------- -------- 11D5E9D4 Managed Chunk
Queue Elements
90155038 0000065540 901501E8 90165068 001 -------- -------- 11D5F518 MallocLite
90165068 0000065540 90155038 90175098 001 -------- -------- 11D5F518 MallocLite
90175098 0000065540 90165068 901850C8 001 -------- -------- 11D5F518 MallocLite
901850C8 0000065540 90175098 901950F8 001 -------- -------- 11D5F518 MallocLite
901950F8 0000000524 901850C8 90195330 001 -------- -------- 1028C5C4 *Init*
90195330 0000065540 901950F8 901A5360 001 -------- -------- 11D5F518 MallocLite
901A5360 0000002620 90195330 901A5DC8 001 -------- -------- 1028C770 *Init*
901A5DC8 0000000892 901A5360 901A6170 001 -------- -------- 12A39D50 *Init*
901A6170 0000000892 901A5DC8 901A6518 001 -------- -------- 12A39D50 *Init*
901A6518 0000131076 901A6170 901C6548 001 -------- -------- 12A3A154 *Init*
Address
Bytes
Prev
Next Ref
PrevF
NextF Alloc PC what
901C6548 0000065540 901A6518 901D6578 001 -------- -------- 11D5F518 MallocLite
901D6578 0000000956 901C6548 901D6960 001 -------- -------- 11445508 IPC Seat
901D6960 0000000404 901D6578 901D6B20 001 -------- -------- 1107D218 Exec
901D6B20 0000000092 901D6960 901D6BA8 001 -------- -------- 110533B0 TTYBKG Timer
901D6BA8 0000000684 901D6B20 901D6E80 001 -------- -------- 0CCA9660 SPI PL client app
handler
901D6E80 0000000148 901D6BA8 901D6F40 001 -------- -------- 0CCA9660 SPI PL client app
handler
901D6F40 0000064252 901D6E80 901E6A68 000 9ED89128 0
13A89380 (coalesced)
901E6A68 0000080004 901D6F40 901FA318 001 -------- -------- 0CCA9660 SL async process
901FA318 0000002068 901E6A68 901FAB58 001 -------- -------- 110796B0 Exec
901FAB58 0000001108 901FA318 901FAFD8 000 9FB2D988 0
110796B0 (fragment)
901FAFD8 0000064100 901FAB58 9020AA68 001 -------- -------- 10B6D078 Process Stack
9020AA68 0001286420 901FAFD8 90344BA8 000 9FD59170 0
10B6D078 (fragment)
90344BA8 0000012804 9020AA68 90347DD8 001 -------- -------- 13A96844 *Init*
--More-- [nova-k5-14:~]$ ioucon 100
I/O memory
Address
Bytes
Prev
Next Ref
PrevF
NextF Alloc PC what
B0151000 0000000260 00000000 B0151130 001 -------- -------- 10519010 *Packet Data*
B0151130 0000000260 B0151000 B0151260 001 -------- -------- 10519010 *Packet Data*
B0151260 0000000260 B0151130 B0151390 001 -------- -------- 10519010 *Packet Data*
B0151390 0000000260 B0151260 B01514C0 001 -------- -------- 10519010 *Packet Data*
B01514C0 0000000260 B0151390 B01515F0 001 -------- -------- 10519010 *Packet Data*
B01515F0 0000000260 B01514C0 B0151720 001 -------- -------- 10519010 *Packet Data*
B0151720 0000000260 B01515F0 B0151850 001 -------- -------- 10519010 *Packet Data*
B0151850 0000000260 B0151720 B0151980 001 -------- -------- 10519010 *Packet Data*
B0151980 0000000260 B0151850 B0151AB0 001 -------- -------- 10519010 *Packet Data*
Switch#
Related Commands
Command
Description
show memory
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1(30)CC
12.0(4)XE
12.0(6)S
12.1(13)
Usage Guidelines
Use this command to determine if the router has experienced single-bit parity errors.
Examples
The following is sample output from the show memory ecc command from a 12000-series router running
Cisco IOS Release 12.0(23)S:
Router# show memory ecc
ECC Single Bit error log
-----------------------Single Bit error detected and corrected at 0x574F3640
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0xE9
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write Single Bit error detected and corrected at
0x56AB3760
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0x68
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
The table below describes the significant fields shown in the first section of the display.
Table 115
Related Commands
Field
Description
Occured n time(s)
Command
Description
show memory
Syntax Description
Command Modes
Command History
outstanding
summary
Release
Modification
15.0(1)M
Usage Guidelines
Before you can enable the show memory events command, you must configure the memory record
events command in global configuration mode.
Examples
The table below describes the significant fields shown in the display.
Table 116
Field
Description
When
Field
Description
Type
Allocation type.
Block/Chunk/DataPtr
Size
PID
What
Traceback/PC
Traceback error.
The following is sample output from the show memory eventscommand using the outstanding and
summarykeywords:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory events outstanding summary
Last-Seen
5d16h
Type
ALLOC
How-Many Size
1
320
PID What
135 Exec
Traceback/PC
61B399F4
The table below describes the significant fields shown in the display.
Table 117
Related Commands
Field
Description
Last-Seen
Type
Allocation type.
How-Many
Size
PID
What
Traceback/PC
Traceback error.
Command
Description
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.0
The following is sample output from the show memory failures alloc command:
Router# show memory failures alloc
Caller
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
0x60394744
Pool
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Size
1684
1684
1684
1684
1684
1684
1684
1684
1684
1684
Alignment
32
32
32
32
32
32
32
32
32
32
When
00:10:03
00:10:03
00:10:03
00:10:03
00:10:03
00:10:03
00:10:03
00:10:03
00:10:04
00:10:04
The table below describes the significant fields shown in the display.
Table 118
Field
Description
Caller
Pool
Size
Alignment
Field
Description
When
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
allocating-process
dead
free
totals
Exec
Release
Modification
12.1
12.2(33)SRA
The show memory fast command displays the statistics for the fast memory. Fast memory is another
name for processor memory, and is also known as cache memory. Cache memory is called fast
memory because the processor can generally access the local cache (traditionally stored on SRAM
positioned close to the processor) much more quickly than main memory or RAM.
The show memory fast command is a command alias for the show memory processor command. These
commands will issue the same output.
Examples
The following example shows sample output from the show memory fast and the show memory
processor commands:
Router>show memory fast
Processor memory
Address
Bytes
Prev
8404A580 0001493284 00000000
841B6ECC 0000020004 8404A580
Queue Elements
841BBD18 0000001504 841B6ECC
841BC320 0000005004 841BBD18
841BD6D4 0000000048 841BC320
841BD72C 0000001504 841BD6D4
841BDD34 0000001504 841BD72C
841BE33C 0000001504 841BDD34
841BE944 0000000504 841BE33C
Queue
841BEB64 0000001504 841BE944
Queue
841BF16C 0000001036 841BEB64
-- More -<Ctrl+z>
Router>show memory processor
Processor
Address
Bytes
8404A580 0001493284
841B6ECC 0000020004
Queue Elements
841BBD18 0000001504
841BC320 0000005004
841BD6D4 0000000048
841BD72C 0000001504
841BDD34 0000001504
841BE33C 0000001504
841BE944 0000000504
Queue
841BEB64 0000001504
Queue
841BF16C 0000001036
-- More -<Ctrl+z>
Router>
Next Ref
841B6ECC 000
841BBD18 001
PrevF
NextF Alloc PC
0
84BADF88 815219D8
-------- -------- 815DB094
what
(coalesced)
Managed Chunk
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
--------------------------------------------------
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
Watched Message
001
001
001
001
001
001
001
--------------------------------------------------
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
815A9630
841BF16C 001
Watcher Message
841BF5A0 001
Process Array
memory
Prev
Next Ref
00000000 841B6ECC 000
8404A580 841BBD18 001
PrevF
NextF Alloc PC
0
84BADF88 815219D8
-------- -------- 815DB094
what
(coalesced)
Managed Chunk
841B6ECC
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
--------------------------------------------------
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
Watched Message
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
001
001
001
001
001
001
001
--------------------------------------------------
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
815A9630
Watcher Message
Process Array
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:
Router#show memory fast allocating-process
Processor
Address
Bytes
8404A580 0001493284
841B6ECC 0000020004
Elements
841BBD18 0000001504
841BC320 0000005004
841BD6D4 0000000048
841BD72C 0000001504
841BDD34 0000001504
841BE33C 0000001504
841BE944 0000000504
841BEB64 0000001504
841BF16C 0000001036
--More-<Ctrl+z>
c2600-1#show memory
memory
Prev
Next Ref
00000000 841B6ECC 000
8404A580 841BBD18 001
841B6ECC
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
841BF16C
841BF5A0
001
001
001
001
001
001
001
001
001
Alloc Proc
*Init*
Alloc PC
815219D8
815DB094
What
(coalesced)
Managed Chunk Queue
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
815A9630
815A9658
815A2B24
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
Watched Message Queue
Watcher Message Queue
Process Array
0x815B6C28
0x819F1DE4
0x815C4FD4
0x815B5FDC
0x819F14DC
0x81A1E838
0x8153DFB8
0x82142438
0x82151E0C
0x819F1C8C
0x815A4858
0x8083DA44
--More-<Ctrl+z>
948680
524640
393480
351528
327900
327900
248136
133192
131116
118480
100048
97248
5
8
6
30
5
5
294
4
1
4
148
17
The following example shows sample output from the show memory fast dead command:
Router#show memory fast dead
Processor memory
Address
Bytes
Prev
Next Ref
8498FC20 0000000028 8498FB90 8498FC64 001
------68
Router#show memory fast dead totals
PrevF
NextF Alloc PC
-------- -------- 81472B24
what
AAA MI SG NAME
Syntax Description
Command Modes
Command History
Examples
processor
io
fragment
detail
Release
Modification
12.3(14)T
12.2(33)SRB
The following is sample output from the show memory processor fragment command:
Router# show memory processor fragment
Processor memory
Free memory size : 65516944 Number of free blocks:
230
Allocator PC Summary for allocated blocks in pool: Processor
PC
Total
Count Name
0x6047DDCC
852020
1 atmdx_vc_table
0x6075DC30
544392
4 ATM1/0
0x61BDBA14
131176
2 eddri_self_event
0x61913BEC
131124
1 l2tp tnl table
0x602E9820
114832
1 AutoVC Msg Chunk
0x6071253C
98408
2 Exec
0x607DF5BC
96624
12 Process Stack
0x6118DDA0
77252
1 Spanning Tree Opt Port Block
0x61F13C30
67636
1 QOS_MODULE_MAIN
0x6047DD3C
65640
2 atmdx_tx_shadow
0x614B6624
65588
1 CEF: loadinfo chunk
0x614D1924
65588
1 IP mtrie node
0x614A58A0
65588
1 CEF: 16 path chunk pool
0x619241D4
65588
1 PPTP mgd timer chunk
0x606581CC
65588
1 AAA DB Chunk
0x607E5EAC
65588
1 MallocLite
0x6192420C
65588
1 PPTP: pptp_tunneltype chunk
0x6075DCB8
45924
10 FastEthernet2/
0x607CA400
36288
2 pak subblock chunk
0x6255648C
28948
1 CCPROXY_CT
0x6047DD7C
24628
1 atmdx_bfd_cache
0x6047DAA4
23500
1 atmdx_instance
0x6047DAE8
23500
1 atmdx_instance snap
0x60962DFC
21420
17 TCP CB
0x616F729C
20052
1 AC context chunks
0x616F72C8
20052
1 AC Mgr mgd timer chunk
0x60734010
16644
19 *Packet Header*
0x6047DE0C
16436
1 atmdx_abr_stats
0x6047DCFC
16112
2 atmdx_rx_pool_info
0x60A77E98
13060
1 DHCPD Message Workspace
0x61F50008
12852
1 CCVPM_HTSP
0x60D509BC
12580
17 Virtual Exec
0x60EFA1EC
12344
1 RSVP DB Handle Bin
.
.
.
0x6067AE44
76
1 AAA Secrettype encrypt
0x61C0EEC0
76
1 Init
0x60F76B1C
76
1 SNMP Trap
0x60BE2444
76
1 Init
0x62638F78
76
1 EEM ED Syslog
0x6077C574
76
1 Init
0x608F7030
76
1 IPC Name String
0x608EEAB8
76
1 IPC Name
0x620468A8
76
1 ivr: ccapAppEntry_t name
0x6066D084
76
1 gk process
0x6064824C
76
1 AAA MI SG NAME
Allocator PC Summary for free blocks in pool: Processor
PC
Total
Count Name
0x6071253C
67387912
2 (fragment)
0x60734010
63292440
11 *Packet Header*
0x60962DFC
105552
10 (coalesced)
0x60D509BC
98384
10 (coalesced)
0x60D4A0B4
70776
9 (coalesced)
0x60803260
21488
4 (fragment)
0x60B2E488
19704
2 (fragment)
0x606E0278
19272
1 (coalesced)
0x606DD8D8
9024
113 Init
0x60B27FE8
5740
3 (fragment)
0x60778AAC
3504
1 (coalesced)
0x607AC764
2212
11 Process Events
0x60F7FCD4
1556
9 (fragment)
0x6071F3FC
1316
12 (fragment)
0x606C5324
1176
6 (coalesced)
0x60D7C518
1148
1 (coalesced)
0x624E170C
876
1 (coalesced)
0x60A68164
588
3 (fragment)
0x60B302C0
408
5 (fragment)
0x60976574
272
2 AAA Event Data
0x60801E38
216
2 (fragment)
0x611DA23C
164
1 shelf_info
0x60A6A638
148
1 (fragment)
0x60801D2C
148
1 (fragment)
0x60D29DCC
148
1 (fragment)
0x62628CA0
144
1 (fragment)
0x60A68218
104
1 (fragment)
0x606B9614
88
1 NameDB String
0x6090A978
84
1 (fragment)
0x606C51D0
84
1 (fragment)
0x62647558
76
1 (fragment)
The following is sample output from the show memory processor fragment detailcommand:
Router# show memory processor fragment detail
Processor memory
Free memory size : 65566148 Number of
Address
Bytes
Prev
Next
645A8148 0000000028 645A80F0 645A8194
645A8194 0000000040 645A8148 645A81EC
645A81EC 0000000260 645A8194 645A8320
200B42B4 0000000028 200B4268 200B4300
200B4300 0000000028 200B42B4 200B434C
200B434C 0000002004 200B4300 200B4B50
Structures
6490F79C 0000000028 6490F748 6490F7E8
6490F7E8 0000000028 6490F79C 6490F834
6490F834 0000006004 6490F7E8 64910FD8
649111A0 0000000060 64911154 6491120C
6491120C 0000000028 649111A0 64911258
64911258 0000000200 6491120C 64911350
.
.
.
504DCF54 0000001212 504DB2E4 504DD440
2C41DCA4 0000000692 2C41BCC8 2C41DF88
2C41DF88 0000005344 2C41DCA4 2C41F498
2C41F498 0000000692 2C41DF88 2C41F77C
6449A544 0000000692 64499794 6449A828
6449A828 0000007760 6449A544 6449C6A8
6449C6A8 0000008044 6449A828 6449E644
504D8778 0000000556 504D754C 504D89D4
504D89D4 0000009860 504D8778 504DB088
504DB088 0000000556 504D89D4 504DB2E4
504D168C 0000001212 504C9658 504D1B78
504D1B78 0000008328 504D168C 504D3C30
504D3C30 0000001212 504D1B78 504D411C
504C5870 0000000692 504C5504 504C5B54
504C5B54 0000005344 504C5870 504C7064
504C7064 0000000408 504C5B54 504C722C
2C42359C 0000001212 2C41F77C 2C423A88
2C423A88 0000008328 2C42359C 2C425B40
504E7DD8 0000000828 504E2660 504E8144
65006A08 0000000408 65003834 65006BD0
65006BD0 0000020520 65006A08 6500BC28
6500BC28 0000000828 65006BD0 6500BF94
5C3AE7B8 0000000828 5C3AE614 5C3AEB24
5C3AEB24 0063247532 5C3AE7B8 20000000
20000000 0000000828 5C3AEB24 2000036C
6500BF94 0000000828 6500BC28 6500C300
6500C300 0004760912 6500BF94 50000000
50000000 0000000828 6500C300 5000036C
2C42E0B4 0000000556 2C429430 2C42E310
2C42E310 0062725312 2C42E0B4 00000000
Related Commands
blocks:
PrevF
-------0
--------------645A8194
--------
230
NextF
-------200B4300
--------------6490F7E8
--------
Alloc PC
60695B20
606B9614
607C2D20
62366C80
60976574
6267D294
what
Init
NameDB String
Init
Init
AAA Event Data
Coproc Request
001
000
001
001
000
001
-------200B4300
--------------6490F7E8
--------
-------6491120C
--------------500770F0
--------
606DDA04
606DD8D8
607DF5BC
606DE82C
606DD8D8
603F0E38
Parser Linkage
Init
Process Stack
Parser Mode
Init
Init
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
001
001
000
--------------504DB2E4
--------------2C41DF88
--------------6449A828
--------------504D89D4
--------------504D1B78
--------------504C5B54
--------------504E2660
--------------0
--------------5C3AEB24
--------------6500C300
--------------6449A828
--------------504D89D4
--------------504D1B78
--------------504C5B54
--------------2C423A88
--------------504D411C
--------------0
--------------6500C300
--------------2C42E310
--------------0
60962DFC
60D509BC
60D509BC
60D509BC
60D509BC
60D509BC
60D2AACC
60D4A0B4
60D4A0B4
60D4A0B4
60962DFC
60962DFC
60962DFC
60D509BC
60D509BC
606E0E44
60962DFC
60962DFC
60734010
606E0E44
60803260
60734010
60734010
60734010
60734010
60734010
6071253C
60734010
60D4A0B4
6071253C
TCP CB
Virtual Exec
(coalesced)
Virtual Exec
Virtual Exec
(coalesced)
Virtual Exec
Virtual Exec
(coalesced)
Virtual Exec
TCP CB
(coalesced)
TCP CB
Virtual Exec
(coalesced)
Chain Cache No
TCP CB
(coalesced)
*Packet Header*
Chain Cache No
(coalesced)
*Packet Header*
*Packet Header*
(coalesced)
*Packet Header*
*Packet Header*
(coalesced)
*Packet Header*
Virtual Exec
(coalesced
Command
Description
memory io
memory processor
free
Ref
001
000
001
001
000
001
Syntax Description
Command Modes
Command History
Examples
pool
totals
statistics
summary
all
pool
Release
Modification
15.0T
The following is sample output from the show memory lite-chunks command:
Router# show memory lite-chunks pool 8
8 bytes pool
Address
69D0CCBC
69D0CCD8
69D0CCF4
69D0CD10
69D0CD2C
69D0CD48
69D0CD64
69D0CD80
69D0CD9C
69D0CDB8
69D0CDD4
Ref
000
000
000
000
000
000
000
000
000
000
000
Alloc PC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
69D0CDF0
69D0CE0C
69D0CE28
69D0CE44
69D0CE60
69D0CE7C
69D0CE98
69D0CEB4
.
000
000
000
000
000
000
000
000
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
64286AAC
The table below describes the significant fields shown in the display.
Table 119
Field
Description
Address
Ref
Alloc PC
Syntax Description
Command Modes
Command History
Examples
allocating-process [totals]
dead [totals]
fragment [detail]
free [totals]
statistics [history]
Release
Modification
12.0
The following is sample output from the show memory multibus command:
Router# show memory
Processor
Address
Bytes
6540BBA0 0000016388
6540FBD4 0000016388
65413C08 0000016388
65417C3C 0000006004
654193E0 0000012004
6541C2F4 0000411712
65480B64 0000020004
654859B8 0000010004
654880FC 0000005004
654894B8 0000000048
.
.
.
multibus
memory
Prev
00000000
6540BBA0
6540FBD4
65413C08
65417C3C
654193E0
6541C2F4
65480B64
654859B8
654880FC
Next
6540FBD4
65413C08
65417C3C
654193E0
6541C2F4
65480B64
654859B8
654880FC
654894B8
65489518
Ref
001
001
001
001
001
000
001
001
001
001
PrevF
-----------------------------------0
-----------------------------
NextF
-----------------------------------0
-----------------------------
Alloc PC
60883984
60883984
60883984
608A0D4C
608A0D4C
608A0D4C
608CF99C
6085C7F8
6085C83C
62BF31DC
what
TW Buckes
TW Buckes
TW Buckes
Process k
Process k
(fragmen)
Managed s
List Eles
List Heas
*Init*
The table below describes the significant fields shown in the display.
Table 120
Field
Description
Address
Bytes
Prev
Next
Ref
PrevF
NextF
Alloc PC
What
Syntax Description
Command Modes
Command History
Examples
Release
Modification
12.0
The following is sample output from the show memory pci command:
Router# show memory pci
I/O memory
Address
Bytes
Prev
0E000000 0000000032 00000000
0E000050 0000000272 0E000000
0E000190 0000000272 0E000050
0E0002D0 0000000272 0E000190
0E000410 0000000272 0E0002D0
0E000550 0000000272 0E000410
0E000690 0000000272 0E000550
0E0007D0 0000000272 0E000690
0E000910 0000000272 0E0007D0
0E000A50 0000000272 0E000910
0E000B90 0000000272 0E000A50
Address
Bytes
Prev
0E000CD0 0000000272 0E000B90
0E000E10 0000000272 0E000CD0
Next
0E000050
0E000190
0E0002D0
0E000410
0E000550
0E000690
0E0007D0
0E000910
0E000A50
0E000B90
0E000CD0
Next
0E000E10
0E000F50
Ref
000
001
001
001
001
001
001
001
001
001
001
Ref
001
001
PrevF
64F5EBF4
----------------------------------------------------------------------PrevF
---------------
NextF
0
----------------------------------------------------------------------NextF
---------------
Alloc PC
00000000
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
607E2EC0
Alloc PC
607E2EC0
607E2EC0
what
(fragmen)
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
*Packet *
what
*Packet *
*Packet *
The table below describes the significant fields shown in the display.
Table 121
Field
Description
Address
Bytes
Prev
Field
Description
Next
Ref
PrevF
NextF
Alloc PC
what
Syntax Description
Command Modes
Command History
Examples
allocating-process
totals
dead
totals
fragment
detail
free
totals
statistics
Release
Modification
12.0
12.4(24)T
Address
6540BBA0
6540FBD4
65413C08
65417C3C
654193E0
6541C2F4
65480B64
654859B8
654880FC
654894B8
Processor
Bytes
0000016388
0000016388
0000016388
0000006004
0000012004
0000411712
0000020004
0000010004
0000005004
0000000048
memory
Prev
00000000
6540BBA0
6540FBD4
65413C08
65417C3C
654193E0
6541C2F4
65480B64
654859B8
654880FC
Next
6540FBD4
65413C08
65417C3C
654193E0
6541C2F4
65480B64
654859B8
654880FC
654894B8
65489518
Ref
001
001
001
001
001
000
001
001
001
001
PrevF
-----------------------------------0
-----------------------------
NextF
-----------------------------------0
-----------------------------
Alloc PC
60883984
60883984
60883984
608A0D4C
608A0D4C
608A0D4C
608CF99C
6085C7F8
6085C83C
62BF31DC
what
TW Buckes
TW Buckes
TW Buckes
Process k
Process k
(fragmen)
Managed s
List Eles
List Heas
*Init*
The table below describes the significant fields shown in the display.
Table 122
Field
Description
Address
Bytes
Prev
Next
Ref
PrevF
NextF
Alloc PC
What
The following is sample output from the show memory processor allocating-processcommand:
Router# show memory processor allocating-process
PC
Total
Count
Name
0x6013A948
3719220
1 atmdx_setup_vc_table
0x6064EB28
2581132
291 Process Stack
0x627E2420
2569476
78 CCE dp subbloc
0x62A098C8
1637116
24 regex
0x62EAF010
979876
77 TW Buckets
0x602439EC
935064
962 *Packet Header*
0x614B3A4C
916724
13 Init
0x6013A89C
852020
1 atmdx_vc_table
0x61A54AEC
786292
1 Init
0x62D7BDD0
702336
160 TCL Chunks
0x62EB0458
666988
14 pak subblock chunk
0x60767C38
641076
1 CCPROXY_CT
0x607439C4
524340
1 L2X Hash Table
0x60271864
434328
28 Normal
0x602718F8
407592
148 Normal
0x600CE0C0
393528
6 Init
The following is sample output from the show memory processor deadcommand:
Router# show memory processor dead
PC
Total
Count
Name
0x61E4EB70
65588
1 IP Static Rout
0x62332A2C
65588
1 MFI: Clnt SMsg
0x6268DFE4
32820
1 PPP Context Ch
0x62660CCC
32820
1 PPP HANDLE IDs
0x61B9B350
12052
1 IP Addresses
0x614246F8
4148
1 AAA Unique Id Hash Table
0x61BA93CC
3688
1 IPAD DIT chunk
0x63B630A4
2544
12 Autoinstall
0x61824BFC
2084
2 CEF: fib GSB
0x62E82CEC
2052
1 Reg Function 1
0x62E8A028
1824
24 Autoinstall
0x617DE354
1744
2 CEF: paths
0x6149E638
1552
1 String-DB owne
0x6149E490
1552
1 String-DB entr
0x60191180
1216
8 AF entry
0x617EB5AC
1176
2 CEF: pathl
0x62EAE860
1156
1 Event Manager Table
0x6149E4BC
920
12 NameDB String
0x6176BCF4
884
2 Ether OAM subblock
The following is sample output from the show memory processor fragmentcommand:
Router# show memory processor fragment
Processor memory
Free memory size : 3144348 Number of free blocks:
96
Allocator PC Summary for allocated blocks in pool: Processor
PC
Total
Count Name
0x6069A038
262196
1 TACL FLT
0x62224AA8
219188
1 QOS_MODULE_MAIN
0x61648840
131124
1 Init
0x6218DAA4
73780
1 CCSIP_UDP_SOCKET
0x61649288
65588
1 CEF: loadinfo chunk
0x61BFD4B8
65588
1 PPTP mgd timer chunk
0x61EE1050
65588
1 eddri_self_event
0x607C13C4
49204
1 Exec
0x608A0D4C
35208
4 Process Stack
0x6069D804
32052
1 TACL hist
0x61631A90
21444
2 CEF: IPv4 Unicast RPF subblock
0x62BA5DD8
20432
1 Init
0x6086F858
20052
1 RMI-RO_RU Chun
0x608CF99C
20052
1 Managed Chunk Queue Elements
The table below describes the significant fields shown in the display.
Table 123
Field
Description
PC
Program counter.
Total
Count
Number of allocations.
Name
The following is sample output from the show memory processor freecommand:
Router# show memory processor free
Processor memory
Address
Bytes
Prev
Next Ref
PrevF
NextF Alloc PC
what
66994680
6698FFC8
659CF6B0
659CF86C
65ADB53C
65ADFC38
65B6C504
6593E924
65CCB054
65CCBD98
65CCFB70
65D0BB58
65D0C5F0
65CFF2F4
6609B7B8
24
Free list
0000000072 66994618
0000000072 6698FF60
0000000024 659CF678
0000000024 659CF710
0000000024 65ADB504
0000000024 65ADFC00
0000000024 65B6C4B8
0000000028 6593E8E8
0000000024 65CCB01C
0000000028 65CCBD60
0000000024 65CCFB38
0000000024 65D0BB20
0000000024 65D0C5B8
0000000024 65CFF2BC
0000000036 6609AFC8
1
669946FC
66990044
659CF6FC
659CF8B8
65ADB588
65ADFC84
65B6C550
6593E974
65CCB0A0
65CCBDE8
65CCFBBC
65D0BBA4
65D0C63C
65CFF340
6609B810
000
000
000
000
000
000
000
000
000
000
000
000
000
000
000
0
66994680
6698FFC8
659CF6B0
659CF86C
65ADB53C
65ADFC38
65B6C504
6593E924
65CCB054
65CCBD98
65CCFB70
65D0BB58
65D0C5F0
65CFF2F4
6698FFC8
659CF6B0
659CF86C
65ADB53C
65ADFC38
65B6C504
6593E924
65CCB054
65CCBD98
65CCFB70
65D0BB58
65D0C5F0
65CFF2F4
6609B7B8
660A0BD4
60699114
60699114
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
6078A2CC
Turbo ACr
Turbo ACr
Init
Init
Init
Init
Init
Init
Init
Init
Init
Init
Init
Init
Init
The table below describes the significant fields shown in the display.
Table 124
Field
Description
Address
Bytes
Prev
Next
Ref
PrevF
NextF
Alloc PC
what
The following is sample output from the show memory processor statisticscommand:
Router# show memory processor statistics
Head
Total(b)
Used(b)
Processor
6540BBA0
415187836
27216968
I/O
E000000
33554432
6226336
.
.
.
Free(b)
387970868
27328096
The table below describes the significant fields shown in the display.
Lowest(b)
385755044
27328096
Largest(b)
381633404
27317852
Table 125
Field
Description
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Largest(b)
Syntax Description
Command Modes
EXEC
Command History
Examples
Release
Modification
12.0(4)XE
12.0(7)T
12.2(33)SRA
If errors are detected in the system, the show memory scan command generates an error report. In the
following example, memory scan detected a parity error:
Router# show memory scan
Memory scan is on.
Total Parity Errors 1.
Address
BlockPtr
BlckSize
6115ABCD 60D5D090
9517A4
Disposit
Scrubed
Region Timestamp
Local 16:57:09 UTC Thu
Mar 18
The table below describes the fields contained in the error report.
Table 126
Field
Description
Address
BlockPtr
Field
Description
BlckSize
Disposit
Region
Timestamp
IBSS--image BSS
IData--imagedata
IText--imagetext
local--heap
Syntax Description
Command Modes
Command History
Examples
table
Release
Modification
12.3(14)T
12.2(33)SRB
The following is sample output from the show memory statistics history table command. The field
descriptions are self-explanatory.
Router# show memory statistics history table
History for Processor memory
Time: 15:48:56.806
Used(b): 422748036 Largest(b): 381064952 Free blocks :291
Maximum memory users for this period
Process Name
Holding
Num Alloc
Virtual Exec
26992
37
TCP Protocols
14460
6
IP Input
1212
1
Time: 14:42:54.506
Used(b): 422705876 Largest(b): 381064952 Free blocks :296
Maximum memory users for this period
Process Name
Holding
Num Alloc
Exec
400012740
24
Dead
1753456
90
Pool Manager
212796
257
Time: 13:37:26.918
Used(b): 20700520 Largest(b): 381064952 Free blocks :196
Maximum memory users for this period
Process Name
Holding
Num Alloc
Exec
8372
5
Time: 12:39:44.422
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Time: 11:46:25.135
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Maximum memory users for this period
Process Name
Holding
Num Alloc
CDP Protocol
3752
25
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
Process Name
Holding
Num Alloc
Entity MIB API
67784
16
TTY Background
12928
4
Exec
7704
3
Time: 00:00:17.936
Used(b): 21011192 Largest(b): 381064952 Free blocks :186
Maximum memory users for this period
Process Name
Holding
Num Alloc
Init
18653520
6600
CCPROXY_CT
599068
57
Proxy Session Applic
275424
21
History for I/O memory
Time: 15:48:56.809
Used(b): 7455520 Largest(b): 59370080 Free blocks :164
Time: 14:42:54.508
Used(b): 7458064 Largest(b): 59370080 Free blocks :165
Maximum memory users for this period
Process Name
Holding
Num Alloc
Pool Manager
141584
257
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
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
Time: 00:00:17.937
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Maximum memory users for this period
Process Name
Init
Pool Manager
Related Commands
Holding
7296000
816
Command
Description
Num Alloc
214
3
Syntax Description
Command Modes
Command History
id
exclusive
totals
Release
Modification
15.0(1)M
Usage Guidelines
Before you can enable the show memory traceback command, you must configure the memory record
events command in global configuration mode.
Examples
The following is sample output from the show memory traceback command for traceback ID 100:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory traceback 100
Traceback: [100] 0x60630D9Cz 0x60632B50z
0x6063426Cz
0x6063483Cz
0x61AE4910)
The following is sample output from the show memory traceback command using the exclusivekeyword:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory traceback exclusive
Address
Size
refcount tid
What
T43
T85
(coalesced)
(coalesced)
The table below describes the significant fields shown in the display.
Table 127
Related Commands
Field
Description
Address
Size
refcount
tid
Task ID.
What
Command
Description
Syntax Description
Command Modes
Command History
Examples
allocating-process
dead [totals]
fragment [detail]
free [totals]
statistics [history]
Release
Modification
12.0
transient
memory
Prev
Next
00000000 821BBC28
81F99C00 821C0A7C
821BBC28 821C31C0
821C0A7C 821C457C
Ref
000
001
001
001
PrevF
829C8104
----------------------
NextF
82776FD0
----------------------
Alloc PC
8060B6D0
8002D5C0
811604C0
81160500
what
(coalesc)
Managed s
List Eles
List Heas
The table below describes the significant fields shown in the display.
Table 128
Field
Description
Address
Bytes
Prev
Next
Ref
PrevF
NextF
Alloc PC
what
show microcode
To display microcode image information available on line cards, use the show microcode command in
EXEC mode.
show microcode
Syntax Description
Command Modes
EXEC
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
Description
----------SP version 2.3
EIP version 1.1
TRIP version 1.2
FIP version 1.4
HIP version 1.1
SIP version 1.1
FSIP version 1.1
In the following example for the Cisco 7200 series router, the output from the show microcode command
lists the hardware types that support microcode download. For each type, the default microcode image
name is displayed. If there is a configured default override, that name also is displayed.
router# show microcodeMicrocode images for downloadable hardware
HW Type
Microcode image names
-----------------------------------------ecpa
default
slot0:xcpa26-0
configured slot0:xcpa26-2
pcpa
default
slot0:xcpa26-4
Related Commands
Command
Description
microcode (7000/7500)
microcode (7200)
Syntax Description
module num
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(17d)SXB1
12.2(33)SRA
The total packets switched performance displayed is the rate calculated as the average rate in a period
within the last 30 seconds.
The ingress ACL denied packet count is displayed in the Total packets L3 Switched field and in the Total
packets dropped by ACL field.
The RPF failed packet count is displayed in the Total packets L3 Switched field.
If the IP multicast source sends traffic to any multicast group that does not have an (*,G) entry present in
the mroute table, the show mls statistics command displays these packets as incrementing in the Total
Mcast Packets Switched/Routed field. These packets are dropped in the hardware because there are no
receivers for that group and no entry in the mroute table.
Examples
This example shows how to display the MLS statistics for all modules:
Router#
show mls statistics
Statistics for Earl in Module 2
L2 Forwarding Engine
Total packets Switched
L3 Forwarding Engine
Total Packets Bridged
Total Packets FIB Switched
Total Packets ACL Routed
Total Packets Netflow Switched
Total Mcast Packets Switched/Routed
Total ip packets with TOS changed
Total ip packets with COS changed
Total non ip packets COS changed
Total packets dropped by ACL
Total packets dropped by Policing
Statistics for Earl in Module 9
L2 Forwarding Engine
Total packets Switched
L3 Forwarding Engine
Total Packets Bridged
Total Packets FIB Switched
Total Packets ACL Routed
Total Packets Netflow Switched
Total Mcast Packets Switched/Routed
Total ip packets with TOS changed
Total ip packets with COS changed
Total non ip packets COS changed
Total packets dropped by ACL
Total packets dropped by Policing
Router#
20273
7864
0
0
220598
0
0
0
0
705757744
: 16683@ 1 pps
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
277949053
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
L2 Forwarding Engine
Total packets Switched
>>
L3 Forwarding Engine
Total Packets Bridged
Total Packets FIB Switched
Total Packets ACL Routed
Total Packets Netflow Switched
Total Mcast Packets Switched/Routed
Total ip packets with TOS changed
Total ip packets with COS changed
Total non ip packets COS changed
Total packets dropped by ACL
Total packets dropped by Policing
Total Unicast RPF failed packets
Errors
MAC/IP length inconsistencies
Short IP packets received
IP header checksum errors
MAC/IPX length inconsistencies
Short IPX packets received
Router
#
92750@ 34 pps
7
0
0
3079200
0
0
0
0
0
0
:
:
:
:
:
0
0
0
0
0
Related Commands
Command
Description
show mls ip
show module
To display the module status and information, use the show module command in user EXEC or privileged
EXEC mode.
show module [mod-num | all | provision | version]
Syntax Description
mod -num
all
provision
version
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
In the Mod Sub-Module fields, the show module command displays the supervisor engine number but
appends the uplink daughter cards module type and information.
Entering the show module command with no arguments is the same as entering the show module all
command.
Examples
This example shows how to display information for all modules on a Cisco 7600 series router that is
configured with a Supervisor Engine 720:
Router#
show module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ ----------1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL0843557C
2 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-45AF SAL1109HZW9
3 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-45AF SAL1114KYZ7
4 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 SAL0543DGZ1
6 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1016KASS
7 48 48-port 10/100 mb RJ45 WS-X6148-45AF SAL08321X1H
8 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08528ADQ
9 48 48-port 100FX SFP Ethernet Module WS-X6148-FE-SFP SAD090208MB
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ ------1 0012.005c.86e0 to 0012.005c.870f 2.1 12.2(14r)S5 12.2(33)SXH Ok
2 001b.0ce4.9fb0 to 001b.0ce4.9fdf 2.2 8.4(1) 8.7(0.22)SXH Ok
3 001b.534f.0540 to 001b.534f.056f 2.2 8.4(1) 8.7(0.22)SXH Ok
4 0007.4f6c.69f8 to 0007.4f6c.6a27 5.0 5.4(2) 8.7(0.22)SXH Ok
6 0017.9441.44cc to 0017.9441.44cf 5.2 8.4(2) 12.2(33)SXH Ok
7 0011.bb0e.c260 to 0011.bb0e.c28f 1.1 5.4(2) 8.7(0.22)SXH Ok
8 0012.da89.a43c to 0012.da89.a43f 2.0 12.2(14r)S5 12.2(33)SXH Ok
9 0030.f273.baf0 to 0030.f273.bb1f 3.0 8.4(1) 8.7(0.22)SXH Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- ------1 Centralized Forwarding Card WS-F6700-CFC SAL08363HL6 2.0 Ok
2 IEEE Voice Daughter Card WS-F6K-48-AF SAL1108HRB1 2.3 Ok
3 IEEE Voice Daughter Card WS-F6K-48-AF SAL1114KV3P 2.3 Ok
4 Inline Power Module WS-F6K-VPWR 1.0 Ok
6 Policy Feature Card 3 WS-F6K-PFC3B SAL1015K00Q 2.3 Ok
6 MSFC3 Daughterboard WS-SUP720 SAL1016KBY3 2.5 Ok
7 IEEE Voice Daughter Card WS-F6K-FE48-AF SAL08311GGL 1.1 Ok
8 Centralized Forwarding Card WS-F6700-CFC SAL0902040K 2.0 Ok
Mod Online Diag Status
---- ------------------1 Bypass
2 Bypass
3 Bypass
4 Bypass
6 Bypass
7 Bypass
8 Bypass
9 Bypass
Router#
Related Commands
Command
Description
show interfaces
show fm summary
Syntax Description
all-traces
component
all
clock hh:mm
date
month
from-boot seconds
latest
component
Command Modes
Command History
parameters
detail
Release
Modification
12.0(18)S
12.2(8)T
12.2(25)S
12.2(18)SXE
12.4(4)T
12.0(31)S
12.2(28)SB
12.4(9)T
12.2(33)SRA
12.2(33)SXH
Usage Guidelines
Release
Modification
12.2(33)SB
12.4(20)T
Use the show monitor event-trace command to display trace message information.
The trace function is not locked while information is being displayed to the console, which means that new
trace messages can accumulate in memory. If entries accumulate faster than they can be displayed, some
messages can be lost. If this happens, the show monitor event-trace command will generate a message
indicating that some messages might be lost; however, messages will continue to display on the console. If
the number of lost messages is excessive, the show monitor event-tracecommand will stop displaying
messages.
Use the bfd keyword for the component argument to display trace messages relating to the BFD feature.
Use the cfd keyword for the component argument to display trace messages relating to the crypto fault
detection feature. This keyword displays the contents of the error trace buffers in an encryption data path.
Examples
IPC Component Example
The following is sample output from the show monitor event-tracecomponent command for the
interprocess communication (IPC) component. Notice that 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 ipc
3667:
3668:
3669:
3670:
6840.016:Message
6840.016:Message
6841.016:Message
6841.016:Message
type:3
type:4
type:5
type:6
Data=0123456789
Data=0123456789
Data=0123456789
Data=0123456
BFD Component for Cisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T
Use the show monitor event-trace bfd allcommand to display logged messages for important BFD events
in the recent past. The following trace messages show BFD session state changes:
Router# show monitor event-trace bfd all
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1],
create, state Unknown -> Fail
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1],
(from LC)
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1],
(from LC)
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1],
(from LC)
3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2],
create, state Unknown -> Fail
3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2],
(from LC)
event Session
state Fail -> Down
state Down -> Init
state Init -> Up
event Session
state Fail -> Down
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
3667:
3669:
3671:
3673:
Test2
3668:
3670:
3672:
3674:
event trace:
6840.016:Message
6841.016:Message
6842.016:Message
6843.016:Message
event trace:
6840.016:Message
6841.016:Message
6842.016:Message
6843.016:Message
type:3
type:4
type:5
type:6
Data=0123456789
Data=0123456789
Data=0123456789
Data=0123456789
type:3
type:4
type:5
type:6
Data=0123456789
Data=0123456789
Data=0123456789
Data=0123456789
[OK]
[OK]
In the following example, all event trace messages for the Cisco Express Forwarding component are
displayed:
Router# show monitor event-trace cef events all
00:00:18.884: SubSys fib_ios_chain init
00:00:18.884: Inst
unknown -> RP
00:00:24.584: SubSys fib init
00:00:24.592: SubSys fib_ios init
00:00:24.592:
00:00:24.596:
00:00:24.608:
00:00:24.612:
00:00:24.620:
00:00:24.620:
00:00:24.620:
00:00:24.624:
00:00:24.628:
00:00:24.628:
00:00:24.632:
00:00:25.304:
00:00:25.304:
00:00:25.304:
00:00:25.308:
SubSys
SubSys
SubSys
SubSys
Flag
Flag
Flag
GState
SubSys
SubSys
SubSys
Process
Flag
Process
Flag
fib_ios_if init
ipv4fib init
ipv4fib_ios init
ipv6fib_ios init
IPv4 CEF enabled set to yes
0x7BF6B62C set to yes
IPv4 CEF switching enabled set to yes
CEF enabled
ipv4fib_les init
ipv4fib_pas init
ipv4fib_util init
Background created
IPv4 CEF running set to yes
Background event loop enter
IPv4 CEF switching running set to yes
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
00:00:48.244: [Default] 127.0.0.81/32'01
FIB insert
[OK]
In the following example, all event trace message for the Cisco Express Forwarding component are
displayed:
Router# show monitor event-trace cef events all
00:00:18.884: SubSys fib_ios_chain init
00:00:18.884: Inst
unknown -> RP
00:00:24.584: SubSys fib init
00:00:24.592: SubSys fib_ios init
00:00:24.592: SubSys fib_ios_if init
00:00:24.596: SubSys ipv4fib init
00:00:24.608: SubSys ipv4fib_ios init
00:00:24.620: Flag
IPv4 CEF enabled set to yes
00:00:24.620: Flag
0x7BF6B62C set to yes
00:00:24.620: Flag
IPv4 CEF switching enabled set to yes
00:00:24.624: GState CEF enabled
00:00:24.628: SubSys ipv4fib_les init
00:00:24.628: SubSys ipv4fib_pas init
00:00:24.632: SubSys ipv4fib_util init
00:00:25.304: Process Background created
00:00:25.304: Flag
IPv4 CEF running set to yes
00:00:25.304: Process Background event loop enter
00:00:25.308: Flag
IPv4 CEF switching running set to yes
(sw
(sw
(sw
4) Create
new
4) SWIDBLnk FastEthernet1/0/0(4)
4) NameSet
00:00:24.624:
00:00:24.624:
00:00:24.624:
00:00:24.624:
00:00:24.624:
00:00:24.624:
00:00:24.624:
<empty>
<empty>
Fa0/0
<empty>
<empty>
Fa0/1
<empty>
(hw
(hw
(hw
(sw
(sw
(sw
(hw
1)
1)
1)
3)
3)
3)
2)
Create
HWIDBLnk
NameSet
Create
SWIDBLnk
NameSet
Create
new
FastEthernet1/0/0(1)
new
FastEthernet1/1/0(3)
new
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
Related Commands
Command
Description
Syntax Description
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(18)SXE
12.2(33)SRA
This example shows how to display the permit-list state and interfaces configured:
Router# show monitor permit-list
SPAN Permit-list
Permit-list ports
Router(config)#
Related Commands
:Admin Enabled
:Gi5/1-4,Gi6/1
Command
Description
monitor permit-list
Syntax Description
range session-range
local
remote
all
session
erspan-destination
erspan-source
detail
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXE
12.2(18)SXF
12.2(33)SXH
Usage Guidelines
The erspan-destination and erspan-sourcekeywords are not supported on Catalyst 6500 series switches
that are configured with a Supervisor Engine 2.
In releases prior to Release 12.2(18)SXF, ERSPAN is supported on Catalyst 6500 series switches that are
operating in compact switch fabric module functionality switching mode only.
Release 12.2(18)SXF and later releases support ERSPAN in any switch fabric module functionality
switching mode.
If the switch fabric module functionality switching mode is set to compact, the output of the show
commands display dcef mode for fabric-enabled modules with DFC3 installed and display fabric mode
for other fabric-enabled modules.
If the switch fabric module functionality switching mode is set to truncated, the output of the show
commands display fabric mode for all fabric-enabled modules.
When entering a range of sessions, use a dash (-) to specify a range and separate multiple entries with a
comma (,). Do not enter spaces before or after the comma or the dash.
You can enter multiple ranges by separating the ranges with a comma.
If you enter the show monitor session command without specifying a session, the information for all
sessions is displayed.
Examples
This example shows how to display the saved version of the monitor configuration for a specific session:
Router# show monitor session 2
Session 2
-----------Type : Remote Source Session
Source Ports:
RX Only:
Fa1/1-3
Dest RSPAN VLAN:
901
Router#
This example shows how to display the detailed information from a saved version of the monitor
configuration for a specific session:
Router# show monitor session 2 detail
Session 2
-----------Type : Remote Source Session
Source Ports:
RX Only:
Fa1/1-3
TX Only:
None
Both:
None
Source VLANs:
RX Only:
None
TX Only:
None
Both:
None
Source RSPAN VLAN: None
Destination Ports: None
Filter VLANs:
None
Dest RSPAN VLAN:
901
Router#
This example shows how to display information about the egress replication mode only:
Router# show monitor session egress replication-mode capability
No SPAN configuration is present in the system.
------------------------------------------------------Global Egress SPAN Replication Mode Capability:
Slot
Egress Replication Capability
No
LSPAN
RSPAN
ERSPAN
------------------------------------------------------3
Distributed
Distributed
Distributed
5
Distributed
Distributed
Distributed
Router#
This example shows how to display information about the destination ERSPAN sessions only:
Router# show monitor session erspan-destination
Session 2
--------Type
Status
Disabled
This example shows how to display detailed information about the destination ERSPAN sessions only:
Router# show monitor session erspan-destination detail
Session 2
--------Type
Status
Description
Source Ports
RX Only
TX Only
Both
Source VLANs
RX Only
TX Only
Both
Source RSPAN VLAN
Destination Ports
Filter VLANs
Destination RSPAN VLAN
Source IP Address
Source IP VRF
Source ERSPAN ID
Destination IP Address
Destination IP VRF
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Destination ERSPAN ID
Origin IP Address
IP QOS PREC
IP TTL
Router#
:
:
:
:
None
None
0
255
This example shows how to display information about the source ERSPAN sessions only:
Router# show monitor session erspan-source
Session 1
--------Type
Status
Disabled
3
--------Type
Status
Disabled
This example shows how to display detailed information about the source ERSPAN sessions only:
Router# show monitor session erspan-source detail
Session 1
--------Type
Status
Description
Source Ports
RX Only
TX Only
Both
Source VLANs
RX Only
TX Only
Both
Source RSPAN VLAN
Destination Ports
Filter VLANs
Destination RSPAN VLAN
Source IP Address
Source IP VRF
Source ERSPAN ID
Destination IP Address
Destination IP VRF
Destination ERSPAN ID
Origin IP Address
IP QOS PREC
IP TTL
Session 3
--------Type
Status
Description
Source Ports
RX Only
TX Only
Both
Source VLANs
RX Only
TX Only
Both
Source RSPAN VLAN
Destination Ports
Filter VLANs
Destination RSPAN VLAN
Source IP Address
Source IP VRF
Source ERSPAN ID
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Destination IP Address
Destination IP VRF
Destination ERSPAN ID
Origin IP Address
IP QOS PREC
IP TTL
Router#
:
:
:
:
:
:
None
None
None
None
0
255
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
----------------------------------------------Operational mode of egress span replication
: Centralized
Configured mode of egress span replication
: Distributed/Default
Slot
Egress Replication Capability
----------------------------------------------1
Centralized
3
Centralized
5
Centralized
Router#
Related Commands
Command
Description
monitor session
remote-span
show msfc
To display Multilayer Switching Feature Card (MSFC) information, use the show msfc command in user
EXEC or privileged EXEC mode.
show msfc {buffers | eeprom | fault | netint | tlb}
Syntax Description
buffers
eeprom
fault
netint
tlb
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
6
0
0
7
0
0
Threshold = 8192
Vlan Sel Min Max Cnt Rsvd
1016
1 6715 8192
0
0
Router#
Router# show msfc eeprom
RSFC CPU IDPROM:
IDPROM image:
(FRU is 'Cat6k MSFC 2 daughterboard')
IDPROM image block #0:
hexadecimal contents of block:
00: AB AB 01 90 13 22 01 00 00 02 60 03 00 EA 43 69
....."....`...Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 00 00 00 00 00
sco Systems.....
20: 00 00 57 53 2D 46 36 4B 2D 4D 53 46 43 32 00 00
..WS-F6K-MSFC2..
30: 00 00 00 00 00 00 53 41 44 30 36 32 31 30 30 36
......SAD0621006
40: 37 00 00 00 00 00 00 00 00 00 37 33 2D 37 32 33
7.........73-723
50: 37 2D 30 33 00 00 00 00 00 00 41 30 00 00 00 00
7-03......A0....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
70: 00 00 00 02 00 03 00 00 00 00 00 09 00 05 00 01
................
80: 00 03 00 01 00 01 00 02 00 EA FF DF 00 00 00 00
................
block-signature = 0xABAB, block-version = 1,
block-length = 144, block-checksum = 4898
*** common-block ***
IDPROM capacity (bytes) = 256 IDPROM block-count = 2
FRU type = (0x6003,234)
OEM String = 'Cisco Systems'
Product Number = 'WS-F6K-MSFC2'
Serial Number = 'SAD06210067'
Manufacturing Assembly Number = '73-7237-03'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 2.3
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.5.1.3.1.1.2.234
Power Consumption = -33 centiamperes
RMA failure code = 0-0-0-0
*** end of common block ***
IDPROM image block #1:
hexadecimal contents of block:
00: 60 03 01 62 0A C2 00 00 00 00 00 00 00 00 00 00
`..b............
10: 00 00 00 00 00 01 00 23 00 08 7C A4 CE 80 00 40
.......#..|....@
20: 01 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00
................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
40: 14 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
50: 10 00 4B 3C 41 32 80 80 80 80 80 80 80 80 80 80
..K<A2..........
60: 80 80
..
block-signature = 0x6003, block-version = 1,
block-length = 98, block-checksum = 2754
*** linecard specific block ***
feature-bits =
00000000 00000000
hardware-changes-bits =
00000000 00000001
card index = 35
mac base = 0008.7CA4.CE80
mac_len = 64
num_processors = 1
epld_num = 1
epld_versions = 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00
00 0000 0000
port numbers:
pair #0: type=14, count=01
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 = 4096
sensor_thresholds =
sensor #0: critical = 75 oC, warning = 60 oC
sensor #1: critical = 65 oC, warning = 50 oC
sensor #2: critical = -128 oC (sensor not present), warning = -128 oC (senso
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
r not present)
sensor #5: critical = -128 oC (sensor not present), warning = -128 oC
r not present)
sensor #6: critical = -128 oC (sensor not present), warning = -128 oC
r not present)
sensor #7: critical = -128 oC (sensor not present), warning = -128 oC
r not present)
*** end of linecard specific block ***
End of IDPROM image
Router#
Router# show msfc fault
Reg. set
Min
Max
TX
640
ABQ
640 16384
0
0
40
1
6715
8192
2
0
0
3
0
0
4
0
0
5
0
0
6
0
0
7
0
0
Threshold = 8192
Vlan Sel Min Max Cnt Rsvd
1016
1 6715 8192
0
0
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
Router#
Router# show msfc tlb
Mistral revision 3
TLB entries : 37
Virt Address range
Phy Address range
Attributes
0x10000000:0x1001FFFF
0x010000000:0x01001FFFF
CacheMode=2, RW, Valid
0x10020000:0x1003FFFF
0x010020000:0x01003FFFF
CacheMode=2, RW, Valid
0x10040000:0x1005FFFF
0x010040000:0x01005FFFF
CacheMode=2, RW, Valid
0x10060000:0x1007FFFF
0x010060000:0x01007FFFF
CacheMode=2, RW, Valid
0x10080000:0x10087FFF
0x010080000:0x010087FFF
CacheMode=2, RW, Valid
0x10088000:0x1008FFFF
0x010088000:0x01008FFFF
CacheMode=2, RW, Valid
0x18000000:0x1801FFFF
0x010000000:0x01001FFFF
CacheMode=0, RW, Valid
0x19000000:0x1901FFFF
0x010000000:0x01001FFFF
CacheMode=7, RW, Valid
0x1E000000:0x1E1FFFFF
0x01E000000:0x01E1FFFFF
CacheMode=2, RW, Valid
0x1E880000:0x1E881FFF
0x01E880000:0x01E881FFF
CacheMode=2, RW, Valid
0x1FC00000:0x1FC7FFFF
0x01FC00000:0x01FC7FFFF
CacheMode=2, RO, Valid
0x30000000:0x3001FFFF
0x070000000:0x07001FFFF
CacheMode=2, RW, Valid
0x40000000:0x407FFFFF
0x000000000:0x0007FFFFF
CacheMode=3, RO, Valid
0x40800000:0x40FFFFFF
0x000800000:0x000FFFFFF
CacheMode=3, RO, Valid
0x41000000:0x417FFFFF
0x001000000:0x0017FFFFF
CacheMode=3, RO, Valid
0x41800000:0x419FFFFF
0x001800000:0x0019FFFFF
CacheMode=3, RO, Valid
0x41A00000:0x41A7FFFF
0x001A00000:0x001A7FFFF
CacheMode=3, RO, Valid
0x41A80000:0x41A9FFFF
0x001A80000:0x001A9FFFF
CacheMode=3, RO, Valid
0x41AA0000:0x41ABFFFF
0x001AA0000:0x001ABFFFF
CacheMode=3, RO, Valid
0x41AC0000:0x41AC7FFF
0x001AC0000:0x001AC7FFF
CacheMode=3, RO, Valid
0x41AC8000:0x41ACFFFF
0x001AC8000:0x001ACFFFF
CacheMode=3, RO, Valid
0x41AD0000:0x41AD7FFF
0x001AD0000:0x001AD7FFF
CacheMode=3, RO, Valid
0x41AD8000:0x41AD9FFF
0x001AD8000:0x001AD9FFF
CacheMode=3, RO, Valid
0x41ADA000:0x41ADBFFF
0x001ADA000:0x001ADBFFF
CacheMode=3, RW, Valid
0x41ADC000:0x41ADDFFF
0x001ADC000:0x001ADDFFF
CacheMode=3, RW, Valid
0x41ADE000:0x41ADFFFF
0x001ADE000:0x001ADFFFF
CacheMode=3, RW, Valid
0x41AE0000:0x41AFFFFF
0x001AE0000:0x001AFFFFF
CacheMode=3, RW, Valid
0x41B00000:0x41B7FFFF
0x001B00000:0x001B7FFFF
CacheMode=3, RW, Valid
0x41B80000:0x41BFFFFF
0x001B80000:0x001BFFFFF
CacheMode=3, RW, Valid
0x41C00000:0x41DFFFFF
0x001C00000:0x001DFFFFF
CacheMode=3, RW, Valid
0x41E00000:0x41FFFFFF
0x001E00000:0x001FFFFFF
CacheMode=3, RW, Valid
0x42000000:0x43FFFFFF
0x002000000:0x003FFFFFF
CacheMode=3, RW, Valid
0x44000000:0x45FFFFFF
0x004000000:0x005FFFFFF
CacheMode=3, RW, Valid
0x46000000:0x47FFFFFF
0x006000000:0x007FFFFFF
CacheMode=3, RW, Valid
0x06E00000:0x06FFFFFF
0x006E00000:0x006FFFFFF
CacheMode=2, RW, Valid
(senso
(senso
(senso
(senso
0x07000000:0x077FFFFF
0x07800000:0x07FFFFFF
Router#
Related Commands
0x007000000:0x0077FFFFF
0x007800000:0x007FFFFFF
Command
Description
show fm summary
show pagp
To display port-channel information, use the show pagp command in user EXEC or privileged EXEC
mode.
show pagp [group-number] {counters | internal | neighbor | pgroup}
Syntax Description
group-number
counters
internal
neighbor
pgroup
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Usage Guidelines
You can enter any show pagp command to display the active port-channel information. To display the
nonactive information, enter the show pagp command with a group.
The port-channel numbervalues from 257 to 282 are supported on the CSM and the FWSM only.
Examples
This example shows how to display information about the PAgP counters:
Router#
show pagp
counters
Information
Flush
Port
Sent
Recv
Sent
Recv
-------------------------------------Channel group: 1
Fa5/4
2660
2452
0
0
Fa5/5
2676
2453
0
0
Channel group: 2
Fa5/6
289
261
0
0
Fa5/7
290
261
0
0
Channel group: 1023
Fa5/9
0
0
0
0
Channel group: 1024
Fa5/8
0
0
0
0
Router#
This example shows how to display PAgP-neighbor information for all neighbors:
Router# show pagp
neighbor
Flags: S - Device is sending Slow hello. C - Device is in Consistent state.
A - Device is in Auto mode.
P - Device learns on physical port.
Channel group 1 neighbors
Partner
Partner
Partner
Partner Group
Port
Name
Device ID
Port
Age Flags
Cap.
Fa5/4
JAB031301
0050.0f10.230c
2/45
2s SAC
2D
Fa5/5
JAB031301
0050.0f10.230c
2/46
27s SAC
2D
Channel group 2 neighbors
Partner
Partner
Partner
Partner Group
Port
Name
Device ID
Port
Age Flags
Cap.
Fa5/6
JAB031301
0050.0f10.230c
2/47
10s SAC
2F
Fa5/7
JAB031301
0050.0f10.230c
2/48
11s SAC
2F
Channel group 1023 neighbors
Partner
Partner
Partner
Partner Group
Port
Name
Device ID
Port
Age Flags
Cap.
Channel group 1024 neighbors
Partner
Partner
Partner
Partner Group
Port
Name
Device ID
Port
Age Flags
Cap.
Router#
Related Commands
Command
Description
pagp learn-method
pagp port-priority
Effective with Cisco IOS Release 15.0(1)M, the show parser dump command is not available in Cisco
IOS software.
To display the command-line interface (CLI) syntax options for all command modes or for a specified
command mode, use the show parser dump command in user EXEC or privileged EXEC mode.
show parser dump {command-mode | all} [privilege-level level] [extend] [breakage]
Syntax Description
command-mode
all
extend
output.
breakage
Command Modes
Command History
Usage Guidelines
Caution
Release
Modification
12.2(4)T
12.2(13)T
12.0(23)S
15.0(1)M
This command was developed to allow the exploration of the CLI command syntax without requiring the
user to actually enter a specific mode and use the ? command-line help.
Use caution when entering this command with the all keyword. A large amount of output can be generated
by this command, which may easily exceed buffer or system memory on smaller platforms. Also, some
configuration modes have hundreds of valid commands. For large dumps, use of the redirection to a file
using the | redirect URL syntax at the end of the command is highly recommended. (See the
documentation for the showcommand 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 number preceding the command 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, is a valid command:
type dhcp
<string>
type dhcp
type dhcp
<ipmask>
type dhcp
type dhcp
type dhcp
type dhcp
Use of the show command extensions | begin, | include, and | exclude is recommended for this command
because these extensions allow you to filter the output to display 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.
Examples
The following example shows a typical list of command mode keywords. The fields are self-explanatory.
Router# show parser dump ?
aaa-attr-list
AAA attribute list config mode
aaa-user
AAA user definition
accept-dialin
VPDN group accept dialin configuration mode
accept-dialout
VPDN group accept dialout configuration mode
acct_mlist
AAA accounting methodlist definitions
address-family
Address Family configuration mode
aic
Alarm Interface Card configuration mode
all
For all modes
alps-ascu
ALPS ASCU configuration mode
alps-circuit
ALPS circuit configuration mode
appfw-application-aim
Appfw for AIM Configuration Mode
appfw-application-msnmsgr Appfw for MSN Messenger Configuration Mode
appfw-application-ymsgr Appfw for Yahoo! Messenger Configuration Mode
appfw-policy
Application FW Policy Configuration Mode
application-http
Appfw for HTTP Configuration Mode
archive
Archive the router configuration mode
atalk-test
Appletalk test mode
atm-bm-config
ATM bundle member configuration mode
atm-bundle-config
ATM bundle configuration mode
atm-l2trans-pvc-config
ATM L2transport PVC configuration mode
atm-l2trans-pvp-config
ATM L2transport PVP configuration mode
atm-pvc-range-config
ATM PVC Range configuration mode
atm-range-pvc-config
ATM PVC in Range configuration mode
atm-svc-bm-config
ATM SVC bundle member configuration mode
atm-svc-bundle-config
ATM SVC bundle configuration mode
atm-vc-config
ATM virtual circuit configuration mode
atmsig_e164_table_mode
ATMSIG E164 Table
auto-ip-sla-mpls
Auto IP SLA MPLS LSP Monitor configs
auto-ip-sla-mpls-lpd-params Auto IP SLA MPLS LPD params configs
auto-ip-sla-mpls-params Auto IP SLA MPLS LSP Monitor Params configs
banner
Banner Input mode
bba-group
BBA Group configuration mode
boomerang
Boomerang configuration mode
bsm-cfg
BSM config definition
bulkstat-objlist
Bulk-stat Object list configuration mode
bulkstat-schemadef
Bulk-stat schema configuration mode
bulkstat-transfer
Bulk Stat configuration mode
cascustom
Cas custom configuration mode
call-filter-matchlist
Call Filter matchlist configuration mode
call-home
call-home config mode
call-home-profile
call-home profile config mode
call-router
AnnexG configuration mode
cascustom
Cas custom configuration mode
cause-code-list
Voice Cause Code List configuration mode
cfg-path
IP Host backup configuration mode
cfg-pt-ruleset
Protocol Translation ruleset configuration mode
cip-vadp
Virtual Adapter configuration mode
cip-vlan
Virtual Lan configuration mode
clid-group
CLID group configuration mode
cm-ac
AC-AC connect configuration mode
cm-fallback
cm-fallback configuration mode
cns-connect-intf-config CNS Connect Intf Info Mode
cns-connect-config
CNS Connect Info Mode
cns-tmpl-connect-config CNS Template Connect Info Mode
cns_inventory_submode
CNS Inventory SubMode
codec-profile
Codec Profile configuration mode
conf-dia-attr-list
Diameter attribute list config mode
conf-dia-peer
Diameter peer config mode
conf-dia-sg
Diameter peer group config mode
config-ip-sla-http-rr
IP SLAs HTTP raw request Configuration
config-l2tp-class
l2tp-class configuration mode
config-tgrep
TRIP-Lite configuration mode
config-rtr-http-rr
RTR HTTP raw request Configuration
config-x25-huntgroup
X.25 hunt group configuration mode
config_app_global
Configure global settings
config_app_map
Configure application mapping
config_app_monitor
Configure application monitoring
config_app_session
Define script processes
config_voice
Define application services, modules, groups
config_voice_app
Define application parameters
configure
Global configuration mode
congestion
Frame Relay congestion configuration mode
control-plane
Control Plane configuration mode
control-plane-cef-exception-mode Control Plane cef-exception configuration mode
control-plane-host-mode Control Plane host configuration mode
control-plane-transit-mode Control Plane transit configuration mode
controller
Controller configuration mode
cpf-classmap
Class-map configuration mode
cpf-policyclass
Class-in-Policy configuration mode
cpf-policymap
Policy-map configuration mode
cpu
config-owner-cpu
crypto-ca-cert-chain
Crypto certificate entry mode
crypto-ca-cert-comm
Certificate query mode
crypto-ca-cert-map
Certificate map entry mode
crypto-ca-profile-enroll Certificate enrollment profile entry mode
crypto-ca-root
Certificate authority trusted root entry mode
crypto-ca-trustpoint
Certificate authority trustpoint entry mode
crypto-cs-server
Certificate Server entry mode
crypto-gdoi-group
Crypto GDOI group policy config mode
crypto-identity
Crypto identity config mode
crypto-ikmp
Crypto ISAKMP config mode
crypto-ikmp-browser-proxy Crypto ISAKMP browser proxy config mode
crypto-ikmp-client-fw
Crypto ISAKMP client firewall policy config mode
crypto-ikmp-group
Crypto ISAKMP group policy config mode
crypto-ikmp-peer
Crypto ISAKMP peer policy configuration mode
crypto-ipsec-profile
IPSec policy profile mode
crypto-keyring
Crypto Keyring command mode
crypto-map
Crypto map config mode
crypto-map-fail-close
Crypto map fail close mode
crypto-pubkey
Crypto subsystem public key entry mode
crypto-transform
Crypto transform config mode
crypto-tti-petitioner
TTI Petitioner entry mode
crypto-tti-registrar
TTI Registrar entry mode
decnet-map
DECnet map configuration mode
dfp-submode
DFP config mode
dhcp
DHCP pool configuration mode
dhcp-class
DHCP class configuration mode
dhcp-pool-class
Per DHCP pool class configuration mode
dhcp-relay-info
DHCP class relay agent info configuration mode
dhcp-subnet-secondary
Per DHCP secondary subnet configuration mode
dnis-group
DNIS group configuration mode
dns-view
DNS View configuration mode
dns-view-list
DNS View-list configuration mode
dns-view-list-member
DNS View-list member configuration mode
dspfarm
DSP farm configuration mode
dspfarmprofile
Profile configuration mode
dynupd-http
Dynamic DNS update HTTP configuration mode
dynupd-method
Dynamic DNS update method configuration mode
emergency-response-location voice emergency response location configuration mode
emergency-response-settings voice emergency response settings configuration mode
emergency-response-zone voice emergency response zone configuration mode
enum_rule
enum configuration mode
ephone
ephone configuration mode
ephone-dn
ephone-dn configuration mode
ephone-dn-template
ephone-dn-template configuration mode
ephone-hunt
ephone-hunt configuration mode
ephone-template
ephone-template configuration mode
ephone-type
ephone-type configuration mode
ether_cfm
Ethernet CFM configuration mode
event
Event MIB event configuration mode
event-action-notification Event MIB event action notification configuration mode
event-action-set
Event MIB event action set configuration mode
event-objlist
Event MIB object list configuration mode
event-trigger
Event MIB event trigger configuration mode
event-trigger-boolean
Event MIB event trigger boolean configuration mode
event-trigger-existence Event MIB event trigger existence configuration mode
event-trigger-object-id Event MIB trigger object id configuration mode
event-trigger-threshold Event MIB event trigger threshold configuration mode
exec
Exec mode
expr-expression
Expression configuration mode
expr-object
Expression Object configuration mode
extcomm-list
IP Extended community-list configuration mode
fh_applet
FH Applet Entry Configuration
fh_applet_trigger
FH Applet Trigger Configuration
filter
Output filter mode
filterserver
AAA filter server definitions
flow-cache
Flow aggregation cache config mode
flow-sampler-map
Flow sampler map config mode
flowexp
Flow Exporter configuration mode
flowmon
Flow Monitor configuration mode
flowrec
Flow Record configuration mode
fr-fr
FR/FR connection configuration mode
fr-pw
FR/PW connection configuration mode
fr-vcb-bmode
FR VC Bundle mode
fr-vcb-mmode
FR VC Bundle Member mode
frf5
FR/ATM Network IWF configuration mode
frf8
FR/ATM Service IWF configuration mode
funi-vc-config
FUNI virtual circuit configuration mode
gatekeeper
Gatekeeper config mode
gateway
Gateway configuration mode
gdoi-coop-ks-config
Crypto GDOI server redundancy config mode
gdoi-local-server
Crypto GDOI local server policy config mode
gdoi-sa-ipsec
Crypto GDOI local server IPsec SA policy config mode
gg_fcpa-config
FC tunnel configuration mode
gk_altgk_cluster
GK Commands for Cluster defn
gk_be_annexg
GK Commands for H.323 AnnexG configuration
gk_srv_trigger_arq
GK Server ARQ Trigger config mode
gk_srv_trigger_brq
GK Server BRQ Trigger config mode
gk_srv_trigger_drq
GK Server DRQ Trigger config mode
gk_srv_trigger_irr
GK Server IRR Trigger config mode
gk_srv_trigger_lcf
GK Server LCF Trigger config mode
gk_srv_trigger_lrj
GK Server LRJ Trigger config mode
gk_srv_trigger_lrq
GK Server LRQ Trigger config mode
gk_srv_trigger_rai
GK Server RAI Trigger config mode
gk_srv_trigger_rrq
GK Server RRQ Trigger config mode
gk_srv_trigger_urq
GK Server URQ Trigger config mode
gw
Webvpn virtual gateway configuration
gw-accounting-aaa
Gateway accounting aaa configuration mode
gw-accounting-file
Gateway accounting file configuration mode
hostlist
Host list configuration mode
identity-policy-mode
identity policy configuration mode
identity-profile-mode
identity profile configuration mode
interface
Interface configuration mode
interface range
Interface range configuration mode
interface-dlci
Frame Relay dlci configuration mode
ip-explicit-path
IP explicit path configuration mode
ip-sla
IP SLAs entry configuration
ip-sla-am-grp
IP SLAs auto group config
ip-sla-am-grp-auto
IP SLAs auto group dest-auto config
ip-sla-am-schedule
IP SLAs auto schedule config
ip-sla-dhcp
IP SLAs dhcp configuration
ip-sla-dns
IP SLAs dns configuration
ip-sla-echo
IP SLAs echo configuration
ip-sla-ethernet-echo
IP SLAs Ethernet Echo configuration
ip-sla-ethernet-jitter
IP SLAs Ethernet Jitter configuration
ip-sla-ethernet-monitor IP SLAs Ethernet configs
ip-sla-ethernet-monitor-params IP SLAs Ethernet Params configs
ip-sla-frameRelay
IP SLAs FrameRelay configuration
ip-sla-ftp
IP SLAs ftp configuration
ip-sla-http
IP SLAs http configuration
ip-sla-icmp-ech-params
IP SLAs icmpEcho Parameters
ip-sla-icmp-jtr-params
IP SLAs icmpJitter Parameters
ip-sla-icmpjitter
IP SLAs icmpjitter configuration
ip-sla-jitter
IP SLAs jitter configuration
ip-sla-pathEcho
IP SLAs pathEcho configuration
ip-sla-pathJitter
IP SLAs pathJitter configuration
ip-sla-tcp-conn-params
IP SLAs tcpConnect Parameters
ip-sla-tcpConnect
IP SLAs tcpConnect configuration
ip-sla-tplt-dest
IP SLAs auto destination submode
ip-sla-tplt-icmp-ech
IP SLAs auto template icmpEcho
ip-sla-tplt-icmp-jtr
IP SLAs auto template icmpJitter
ip-sla-tplt-tcp-conn
IP SLAs auto template tcpConnect
ip-sla-tplt-udp-ech
IP SLAs auto template udpEcho
ip-sla-tplt-udp-jtr
IP SLAs auto template udpJitter
ip-sla-udp-ech-params
IP SLAs udpEcho Parameters
ip-sla-udp-jtr-params
IP SLAs udpJitter Parameters
ip-sla-udpEcho
IP SLAs udpEcho configuration
ip-sla-voip
IP SLA voip configuration
ip-sla-voip-rtp
IP SLAs rtp configuration
ip-vrf
Configure IP VRF parameters
ipc-zone-assoc-protocol-sctp ipc protocol sctp mode
ipczone
IPC Zone config mode
ipczone-assoc
IPC Association config mode
ipenacl
IP named extended access-list configuration mode
iphc-profile-mode
IPHC Profile configuration mode
ipmobile-test
IP Mobility test mode
ipnat-pool
IP NAT pool configuration mode
ipnat-portmap
IP NAT portmap configuration mode
ipnat-sbc
IP NAT SIP-SBC config mode
ipnat-sbc-vrf
IP NAT SIP-SBC vrf config mode
ipnat-snat
IP SNAT configuration mode
ipnat-snat-backup
IP SNAT Backup configuration mode
ipnat-snat-primary
IP SNAT Primary configuration mode
ipnat-snat-redundancy
IP SNAT Redundancy configuration mode
ips-seap-rules
IPS event action rules configuration mode
ips-sigdef-sig
IPS signature number name configuration mode
ipscataction
IPS Category name configuration mode
ipsnacl
IP named simple access-list configuration mode
ipssigau
IPS Auto Update configuration mode
ipssigcat
IPS signature category configuration mode
ipssigdef-action
IPS Signature actions configuration mode
ipssigdef-engine
IPS signature def Engine configuration mode
ipssigdef-status
IPS signature def Status mode
ipv6-mobile-router
MIPv6 router configuration mode
ipv6-router
IPv6 router configuration mode
ipv6acl
IPv6 access-list configuration mode
ipv6dhcp
IPv6 DHCP configuration mode
ipv6dhcpvs
IPv6 DHCP Vendor-specific configuration mode
ipx-router
IPX router configuration mode
ipxenacl
IPX named extended access-list configuration mode
ipxsapnacl
IPX named SAP access-list configuration mode
ipxsnacl
IPX named standard access-list configuration mode
ipxsumnacl
IPX named Summary access-list configuration mode
isakmp-profile
Crypto ISAKMP profile command mode
iua-cfg
ISDN user adaptation layer configuration
key-chain
Key-chain configuration mode
key-chain-key
Key-chain key configuration mode
kron-occurrence
Kron Occurrence SubMode
kron-policy
Kron Policy SubMode
l2
vfi configuration mode
line
Line configuration mode
lw-vlan-id
VLAN-id configuration mode
lw-vlan-range
VLAN-range configuration mode
local-prof
Local profile configuration mode
log_config
Log configuration changes made via the CLI
lsp-attribute-list
LSP attribute list configuration mode
map-class
Map class configuration mode
map-list
Map list configuration mode
memory
config-owner-memory
mgcpprofile
MGCP Profile configuration mode
mipv6-config-ha
Mobile IPv6 HA mode
mipv6-config-ha-host
Mobile IPv6 Home Agent Host config mode
mobile-map
Mobile Map mode
mobile-networks
Mobile Networks mode
mobile-router
Mobile Router mode
mplsmfistaticifrewrite
MPLS MFI static if rewrite configuration mode
mplsmfistaticrewrite
MPLS MFI static rewrite configuration mode
mripv6-config-ha-host
Mobile IPv6 Home Agent Host config mode
mrm-manager
IP Multicast Routing Monitor config mode
neighbor
Neighbor configuration mode
network-object-group
ACL Object Group configuration
null-interface
Null interface configuration mode
null-interface
Null interface configuration mode
nxg-service-relationship Service Relationship configuration mode
nxg-usage-indication
Usage Indication configuration mode
oam
LSP Verification configuration mode
oer_br
OER border router configuration submode
oer_mc
OER master controller configuration submode
oer_mc_api_provider
OER MC API Provider configuration submode
oer_mc_br
OER managed border router configuration submode
oer_mc_br_if
OER Border Exit configuration submode
oer_mc_learn
OER Top Talker and Delay learning configuration submode
oer_mc_learn_list
OER learn list configuration submode
oer_mc_map
oer-map config mode
parameter_map_cfg
parameter-map configuration mode
policy-list
IP Policy List configuration mode
preauth
AAA Preauth definitions
profile
Subscriber profile configuration mode
pseudowire-class
Pseudowire-class configuration mode
public-key-chain
Crypto public key identification mode
public-key-chain-key
Crypto public key entry mode
public-key-chain-key-ring Crypto public key entry mode
qosclassmap
QoS Class Map configuration mode
qosclasspolice
QoS Class Police configuration mode
qospolicymap
QoS Policy Map configuration mode
qospolicymapclass
QoS Policy Map class configuration mode
radius-attrl
Radius Attribute-List Definition
radius-locsvr
Radius Application configuration
red-group
random-detect group configuration mode
redundancy
redundancy config mode
regex-translation-rule
voip translation-rule configuration mode
request-dialin
VPDN group request dialin configuration mode
request-dialout
VPDN group request dialout configuration mode
rf-mode-interdev-local ipc sctp local config mode
rf-mode-interdev-remote ipc sctp remote config mode
rf-mode-interdevice
redundancy config mode
rlm-group
RLM Group configuration mode
rlm-group-sc
RLM server/client link configuration mode
roles
Role configuration mode
route-map
Route map config mode
router
Router configuration mode
rsvp-local-if-policy
RSVP local policy interface configuration mode
rsvp-local-policy
RSVP local policy configuration mode
rsvp-local-subif-policy RSVP local policy sub-interface configuration mode
rtr
SAA entry configuration
saa-dhcp
SAA dhcp configuration
saa-dns
SAA dns configuration
saa-echo
SAA echo configuration
saa-frameRelay
SAA FrameRelay configuration
saa-ftp
SAA ftp configuration
saa-http
SAA http configuration
saa-jitter
SAA jitter configuration
saa-pathEcho
SAA pathEcho configuration
saa-pathJitter
SAA pathJitter configuration
saa-slm-ctrlr-if
SAA SLM controller/interface configuration
saa-slmFrIf
SAA SLM FrameRelay Interface configuration
saa-slmfr
SAA SLM Frame Relay configuration
saa-tcpConnect
SAA tcpConnect configuration
saa-udpEcho
SAA udpEcho configuration
sg-radius
Radius Server-group Definition
sampler
Sampler configuration mode
sccpccmgroup
SCCP CCM group configuration mode
sccpplar
SCCP PLAR configuration mode
sctp-export
SCTP export configuration commands
seczonecfg
Security Zone Configuration Mode
seczonepaircfg
Security Zone Pair Configuration Mode
sep-init-config
WSMA Initiator profile Mode
sep-listen-config
WSMA Listener profile Mode
service-object-group
ACL Object Group configuration
serviceflow
Service Flow configuration mode
sg-tacacs+
Tacacs+ Server-group Definition
signaling-class
Signaling class configuration mode
sip-ua
SIP UA configuration mode
sla-lspPing
sla-lspTrace
slb-mode-dfp
slb-mode-real
slb-mode-sfarm
slb-mode-vserver
source-group
srst-video
sss-subscriber
subinterface
subscriber-policy
tablemap
tcl
tdm-conn
telephony-service
telephony-service-group
telephony-service-video
template
template peer-policy
template peer-session
test_cpu
test_mem
tidp-group
tidp-keyset
tn3270s-dlur
tn3270s-dlur-pu
tn3270s-dlur-sap
tn3270s-listen-point
tn3270s-listen-point-pu
tn3270s-pu
tn3270s-resp-time
tn3270s-security
tn3270s-security-profile
tn3270s-svr
top-talkers
tracking-config
trange
translation-profile
translation-rule
trunk-group
vc-class
vc-group
view
vlan
vm-integration
voice-cause-code
voice-gateway
voice-mlpp
voice-service
voice-service-h323
voice-service-session
voice-service-sip
voice-service-stun
voice-uri-class
voicecl-cptone
voicecl-cptone-dt
voicecl-dt-detect
voiceclass
voicednismaps
voiceport
voipdialpeer
voipdpcor
voipdpcorlist
vpdn-group
vpdn-template
vrf
webvpn
webvpn-acl
webvpn-cifs-url
webvpn-group-policy
webvpn-nbnslist
webvpn-port-fwd
webvpn-sso-server
webvpn-time-range
webvpn-url
webvpn-url-rewrite
x25-profile
xconnect-conn-config
xconnect-dlci-config
xconnect-if-config
xconnect-pvc-config
xconnect-pvp-config
xconnect-subif-config
xml-app
xml-transport
In the following example, only commands in RTR configuration mode are shown:
Router# show parser dump rtr
Mode Name :rtr
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address> sourceport <1-65535> control enable
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address> sourceport <1-65535> control disable
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address> sourceport <1-65535>
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type udpEcho dest-ipaddr <address> dest-port <1-65535>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control enable
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control disable
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535>
15 type jitter dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type jitter dest-ipaddr <address> dest-port <1-65535> source-port <1-65535>
15 type jitter dest-ipaddr <address> dest-port <1-65535> control enable
15 type jitter dest-ipaddr <address> dest-port <1-65535> control disable
15 type jitter dest-ipaddr <address> dest-port <1-65535> num-packets <1-60000>
15 type jitter dest-ipaddr <address> dest-port <1-65535> interval <1-60000>
15 type jitter dest-ipaddr <address> dest-port <1-65535>
15 type echo protocol ipIcmpEcho <address> source-ipaddr <address>
15 type echo protocol ipIcmpEcho <address>
15 type ftp operation get url <string> source-ipaddr <address> mode active
15 type ftp operation get url <string> source-ipaddr <address> mode passive
15 type ftp operation get url <string> source-ipaddr <address>
15 type ftp operation get url <string>
15 type http operation get url <string> name-server <address> version <string> sourceipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string> sourceipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string> sourceipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string> sourceipaddr <address> source-port <1-65535>
15 type http operation get url <string> name-server <address> version <string> sourceipaddr <address>
15 type http operation get url <string> name-server <address> version <string>
15 type http operation get url <string> name-server <address>
15 type http operation get url <string>
15 type http operation raw
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
<string>
15 type dhcp
<string>
15 type dhcp
<ipmask>
15 type dhcp
15 type dhcp
15 type dhcp
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> sourceport <1-65535> control enable
type : Type of entry
udpEcho : UDP Echo Operation
dest-ipaddr : Destination address
<address> : IP address or hostname
dest-port : Destination Port
<1-65535> : Port Number
source-ipaddr : Source address
<address> : IP address or hostname
source-port : Source Port
<1-65535> : Port Number
control : Enable or disable control packets
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.
Router(config)# rtr 1
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-execcommands.txt
In the following example, the show parser dump
command is not available in Cisco IOS software because this command was removed in Cisco
IOS 15.0(1)M:
Router# show parser dump all
Command accepted, but obsolete, parser dumper has been deprecated
Related Commands
Command
Description
show append
show begin
show exclude
show include
show redirect
show tee
Syntax Description
name macro-name
brief
description
interface interface
Command Default
Command Modes
Command History
Examples
Release
Modification
12.2(33)SXH
The following example shows how to display the contents of the cisco-router smart port macro:
Router# show parser macro name cisco-router
Macro name : cisco-router
Macro type : default interface
# macro keywords $NVID
# Do not apply to EtherChannel/Port Group
# Access Uplink to Distribution
switchport
# Define unique Native VLAN on trunk ports
# Recommended value for native vlan (NVID) should not be 1
switchport trunk native vlan $NVID
# Update the allowed VLAN range (VRANGE) such that it
The following example shows how to list the Cisco-provided smart port macros:
Router# show parser macro brief | include default
default
default
default
default
default
Related Commands
global
:
interface:
interface:
interface:
interface:
cisco-global
cisco-desktop
cisco-phone
cisco-switch
cisco-router
Command
Description
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.1(5)T
12.2(33)SRA
The number of commands in the configuration file that was last copied into the running configuration,
and the time it took for the system to parse them (a configuration file can be loaded into the running
configuration at system startup, or by issuing commands such as the copy source running-config
command).
The status of the Parser Cache feature (enabled or disabled) and the number of command matches
(indicated by hits/misses) since the system was started or since the parser cache was cleared.
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
Examples
The following example shows sample output from the show parser statistics command:
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:1272 ms
Parser cache:disabled, 0 hits, 2 misses
In this example, the Parser Cache feature is disabled, but shows the hit/miss statistics for the two
commands issued while the parser cache was last enabled.
The table below describes the key output fields.
Table 129
Number of commands:
Time:
Parser cache:
hits
misses
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
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.
Related Commands
Command
Description
parser cache
show pci
To display information about the peripheral component interconnect (PCI) hardware registers or bridge
registers for the Cisco 7200 series routers, use the show pcicommand in EXEC mode.
show pci {hardware | bridge [register]}
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
Examples
hardware
bridge
register
EXEC
Release
Modification
11.2
12.2(33)SRA
The output of this command is generally useful for diagnostic tasks performed by technical support only.
The show pci hardware EXEC command displays a substantial amount of information.
The following is sample output for the PCI bridge register 1 on a Cisco 7200 series router:
Router# show pci bridge 1
Bridge 4, Port Adaptor 1, Handle=1
DEC21050 bridge chip, config=0x0
(0x00): cfid
= 0x00011011
(0x04): cfcs
= 0x02800147
(0x08): cfccid = 0x06040002
(0x0C): cfpmlt = 0x00010010
(0x18): cfsmlt = 0x18050504
(0x1C): cfsis = 0x22805050
(0x20): cfmla = 0x48F04880
(0x24): cfpmla = 0x00004880
(0x3C): cfbc
= 0x00000000
The following is partial sample output for the PCI hardware register, which also includes information on all
the PCI bridge registers on a Cisco 7200 series router:
Router# show pci hardware
GT64010 External PCI Configuration registers:
Vendor / Device ID
: 0xAB114601 (b/s 0x014611AB)
Status / Command
: 0x17018002 (b/s 0x02800117)
Class / Revision
: 0x00000006 (b/s 0x06000000)
Latency
: 0x0F000000 (b/s 0x0000000F)
RAS[1:0] Base
: 0x00000000 (b/s 0x00000000)
RAS[3:2] Base
: 0x00000001 (b/s 0x01000000)
CS[2:0] Base
: 0x00000000 (b/s 0x00000000)
CS[3] Base
: 0x00000000 (b/s 0x00000000)
Mem Map Base
: 0x00000014 (b/s 0x14000000)
IO Map Base
: 0x01000014 (b/s 0x14000001)
Int Pin / Line
: 0x00010000 (b/s 0x00000100)
Bridge 0, Downstream MB0 to MB1, Handle=0
DEC21050 bridge chip, config=0x0
(0x00): cfid
= 0x00011011
(0x04): cfcs
= 0x02800143
(0x08): cfccid = 0x06040002
(0x0C): cfpmlt = 0x00011810
(0x18): cfsmlt = 0x18000100
(0x1C): cfsis = 0x02809050
(0x20): cfmla = 0x4AF04880
(0x24): cfpmla = 0x4BF04B00
(0x3C): cfbc
= 0x00000000
(0x40): cfseed = 0x00100000
(0x44): cfstwt = 0x00008020
.
.
.
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
11.2
12.2(33)SRA
The output of this command is generally useful for diagnostic tasks performed by technical support only:
Router# show pci hardware
hardware PCI hardware registers
Each device on the PCI bus is assigned a PCI device number.
C2600, device numbers are as follows:
Device
Device number
0
First LAN device
1
Second LAN device
2
AIM device (if present)
3
Not presently used
4
Port module - first PCI device
5
Port module - second PCI device
6
Port module - third PCI device
7
Port module - fourth PCI device
8-14
Not presently used
15
Xilinx PCI bridge
Examples
For the
The following is partial sample output for the PCI hardware register, which also includes information on all
the PCI bridge registers.
router# show pci hardware
XILINX Host-PCI Bridge Registers:
Vendor / Device ID: 0x401310EE
Status / Command: 0x040001C6
PCI Slave Base Reg 0: 0x00000000
PCI Slave Base Reg 1: 0x04000000
The table below describes the significant fields shown in the display.
Table 130
Field
Description
Device/Vendor ID
Status/Command
show perf-meas
To display the performance measurement of the router, use the show perf-meascommand in user EXEC or
privileged EXEC mode.
show perf-meas [report-types | all]
Syntax Description
report-types
all
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
Use the show perf-meascommand to display the performance measurement of the router.
Examples
The following is sample output from the show perf-meascommand. The field descriptions are selfexplanatory.
Router# show perf-meas
****** P E R F O R M A N C E
M E A S U R E M E N T ******
---------------------------------------------Fastswitch packets from: Fast-Ethernet to Fast-Ethernet
- Min Time: 0 micro seconds
- Avg Time: 0 micro seconds
- Max Time: 0 micro seconds
- Total number Fastswitch-packets: 0
- Number of packets from output queue (non-Fastswitch): 0
-------------------------------------------------------------------------------|
| Perf Ctr Min | Perf Ctr Avg | Perf Ctr Max |
-------------------------------------------------------------------------------|
Clock Cycles
| 0
| 0
| 0
|
Total-Issued Instructions
| 0
| 0
| 0
|
Floating Point Instructions Issued| 0
| 0
| 0
|
Integer Instructions Issued
| 0
| 0
| 0
|
Load Instructions Issued
| 0
| 0
| 0
|
Store Instructions Issued
| 0
| 0
| 0
|
Dual-Issued Instruction Pairs
| 0
| 0
| 0
|
Branch Pre-Fetches
| 0
| 0
| 0
|
Slip Cycles
| 0
| 0
| 0
|
Stall Cycles
| 0
| 0
| 0
|
On-Chip Secondary Cache Misses
| 0
| 0
| 0
|
Primary Instruction Cache Misses | 0
| 0
| 0
|
Primary Data Cache Misses
| 0
| 0
| 0
|
DTLB Misses
| 0
| 0
| 0
|
ITLB Misses
| 0
| 0
| 0
|
Joint TLB Instruction Misses
| 0
| 0
| 0
|
Joint TLB Data Misses
| 0
| 0
| 0
|
Taken Branch Instructions
| 0
| 0
| 0
|
Branch Instructions Issued
| 0
| 0
| 0
|
OCS Cache Write-Backs
| 0
| 0
| 0
|
Data Cache Write-Backs
| 0
| 0
| 0
|
Pending Load Stall Cycles
| 0
| 0
| 0
|
Number of Re-Misses
| 0
| 0
| 0
|
FP Possible Exception Stall Cycle | 0
| 0
| 0
|
-------------------------------------------------------------------------------|
show platform
To display platform information, use the show platform command in privileged EXEC mode.
show platform {buffers | copp rate-limit {arp | dhcp | atm-oam | ethernet-oam | icmp | igmp |
pppoe-discovery | atom ether-vc | all} | np copp [ifnum] [detail] | dma | eeprom | fault | hardware
capacity | hardware pfc mode | internal-vlan | interrupts | netint | software ipv6-multicast
connected | stats | tech-support {ipmulticast [vrf vrf-name] group-ip-addr src-ip-addr | unicast
[vrf vrf-name] destination-ip-addr destination-mask [global]} | tlb | vfi dot1q-transparency | vlans}
Cisco ASR 1000 Series Aggregation Services Routers
show platform
Syntax Description
buffers
copp rate-limit
Displays Cisco Control Plane Policing (CoPP) ratelimit information on the Cisco 7600 SIP-400.
arp
dhcp
atm-oam
ethernet-oam
icmp
igmp
pppoe-discovery
atom ether-vc
all
np copp
ifnum
detail
dma
eeprom
fault
hardware capacity
internal-vlan
interrupts
netint
stats
tech-support ipmulticast
vrf vrf-name
group-ip-addr
Group IP address.
src-ip-addr
Source IP address.
unicast
destination-ip-addr
Destination IP address.
destination-mask
Destination mask.
global
tlb
vfi
dot1q-transparency
vlans
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(18)SXD
12.2(33)SRA
12.2(33)SRC
12.2(33)SRD
Examples
The following sample output from the show platform buffers command displays buffer-allocation
information:
Router# show platform
buffers
Reg. set
Min
Max
TX
640
ABQ
640 16384
0
0
40
1
6715
8192
2
0
0
3
0
0
4
0
0
5
0
0
6
0
0
7
0
0
Threshold = 8192
Vlan Sel Min Max
1019
1 6715 8192
Router#
Cnt
0
Rsvd
0
State
Insert time (ago)
--------------------- ----------------ok
18:23:58
ok
18:22:38
ok
18:22:33
ok
18:22:38
ok
18:23:58
ok
18:22:38
ok
18:22:38
ok
18:22:38
ok, active
18:23:58
ok, standby
18:23:58
ok, active
18:23:58
ok, standby
18:23:58
ok
18:23:09
ok
18:23:09
Firmware Version
--------------------------------------12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
Cisco ASR 1000 Series Routers--Verifying Dual Cisco IOS Processes on Single RP
In the following example, a second Cisco IOS process is enabled on a Cisco ASR 1004 router using stateful
switchover (SSO). The output of the show platform command is provided before and after the SSO
configuration to verify that the second Cisco IOS process is enabled and active.
Router# show platform
Chassis type: ASR1004
Slot
Type
--------- ------------------0
ASR1000-SIP10
0/0
SPA-5X1GE-V2
0/1
SPA-2XT3/E3
R0
ASR1000-RP1
F0
ASR1000-ESP10
P0
ASR1004-PWR-AC
P1
ASR1004-PWR-AC
Slot
CPLD Version
--------- ------------------0
07091401
R0
07062111
F0
07051680
Router# configure terminal
Enter configuration commands,
Router(config)# redundancy
Router(config-red)# mode sso
State
Insert time (ago)
--------------------- ----------------ok
00:04:39
ok
00:03:23
ok
00:03:18
ok, active
00:04:39
ok, active
00:04:39
ok
00:03:52
ok
00:03:52
Firmware Version
--------------------------------------12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
one per line.
R0/0
R0/1
ESP10
P0
P1
Slot
--------0
R0
F0
ok, active
ok, standby
ok, active
ASR1004-PWR-AC
ASR1004-PWR-AC
CPLD Version
------------------07091401
07062111
07051680
00:29:34
00:27:49
F0
ASR1000-
00:29:34
ok
00:28:47
ok
00:28:47
Firmware Version
--------------------------------------12.2(33r)XN2
12.2(33r)XN2
12.2(33r)XN2
The table below describes the significant fields shown in the display.
Table 131
Field
Description
Slot
Chassis slot.
Type
Hardware type.
Field
Description
State
RP or ESP
SPA
CPLD Version
Firmware Version
Enabled
No
No
No
No
Yes
Yes
The table below describes the significant fields shown in the display.
Table 132
Field
Description
Rate
The following sample from the show platform eeprom command displays CPU EEPROM information:
Router# show platform
eeprom
MSFC CPU IDPROM:
IDPROM image:
IDPROM image block #0:
hexadecimal contents of block:
00: AB AB 02 9C 13 5B 02 00 00 02 60 03 03 E9 43 69
.....[....`...Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 00 00 00 00 00
sco Systems.....
20: 00 00 57 53 2D 58 36 4B 2D 53 55 50 33 2D 50 46
..WS-X6K-SUP3-PF
30: 43 33 00 00 00 00 53 41 44 30 36 34 34 30 31 57
C3....SAD064401W
40: 4C 00 00 00 00 00 00 00 00 00 37 33 2D 37 34 30
L.........73-740
50: 34 2D 30 37 00 00 00 00 00 00 30 35 00 00 00 00
4-07......05....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
70: 00 00 00 00 02 BD 00 00 00 00 00 09 00 05 00 01
................
80: 00 03 00 01 00 01 00 02 03 E9 00 00 00 00 00 00
................
90: 00 00 00 00 00 00 00 00 00 00 00 00
............
block-signature = 0xABAB, block-version = 2,
block-length = 156, block-checksum = 4955
*** common-block ***
IDPROM capacity (bytes) = 512 IDPROM block-count = 2
FRU type = (0x6003,1001)
OEM String = 'Cisco Systems'
Product Number = 'WS-X6K-SUP3-PFC3'
Serial Number = 'SAD064401WL'
Manufacturing Assembly Number = '73-7404-07'
Manufacturing Assembly Revision = '05'
Hardware Revision = 0.701
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.5.1.3.1.1.2.1001
Power Consumption = 0 centiamperes
RMA failure code = 0-0-0-0
CLEI =
*** end of common block ***
IDPROM image block #1:
hexadecimal contents of block:
00: 60 03 02 67 0C 24 00 00 00 00 00 00 00 00 00 00
`..g.$..........
10: 00 00 00 00 00 00 00 51 00 05 9A 3A 7E 9C 00 00
.......Q...:~...
20: 02 02 00 01 00 01 00 00 00 00 00 00 00 00 00 00
................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
40: 14 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
50: 00 00 81 81 81 81 80 80 80 80 80 80 80 80 80 80
................
60: 80 80 06 72 00 46 37
...r.F7
block-signature = 0x6003, block-version = 2,
block-length = 103, block-checksum = 3108
*** linecard specific block ***
feature-bits =
00000000 00000000
hardware-changes-bits =
00000000 00000000
card index = 81
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
0000
port numbers:
pair #0: type=14, count=01
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 = -127 oC (sensor present but ignored), warning = -127 oC (sensor
present but ignored)
sensor #1: critical = -127 oC (sensor present but ignored), warning = -127 oC (sensor
present but ignored)
sensor #2: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #3: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #4: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
block ***
The following sample output from the show platform fault command displays fault-date information:
Router# show platform
fault
Fault History Buffer:
rsp72043_rp Software (rsp72043_rp-ADVENTERPRISEK9_DBG-M), Version 12.2(32.8.1)RE
C186 ENGINEERING WEEKLY BUILD, synced to V122_32_8_11_SR186
Compiled Wed 08-Apr-09 09:22 by abcd
Uptime 2w3d
Exception Vector: 0x1500 PC 0x0B13DD4C MSR 0x00029200 LR 0x0B13DD10
r0 0x0B13DD10 r1 0x1C58A1C8 r2 0xFFFCFFFC r3 0x189EDEF4
r4 0x00000000 r5 0x00000000 r6 0x1C58A1B0 r7 0x00029200
r8 0x00029200 r9 0x00000000 r10 0x00000001 r11 0x189EDEF0
r12 0x0000001B r13 0x04044000 r14 0x08736008 r15 0x115C0000
r16 0x00000000 r17 0x00000000 r18 0x00000000 r19 0x1B751358
r20 0x00000000 r21 0x00000000 r22 0x00000000 r23 0x00000000
r24 0x00000000 r25 0x00000000 r26 0x00000000 r27 0x00000001
r28 0x13255EC0 r29 0x1C59BD00 r30 0x13255EC0 r31 0x00000000
dec 0x00007333 tbu
0x00004660 tbl
0x594BBFC4 pvr
0x80210020
dear 0x00000000 dbcr0 0x41000000 dbcr1 0x00000000 dbcr2 0x00000000
iac1 0x00000000 iac2 0x00000000 dac1 0x00000000 dac2 0x00000000
The following sample output from the show platform hardware pfc mode command displays the PFCoperating mode:
Router# show platform
hardware pfc mode
PFC operating mode : PFC3A
This following sample output from the show platform tlb command displays the TLB-register
information:
Router# show platform
tlb
Mistral revision 5
TLB entries : 42
Virt Address range
0x10000000:0x1001FFFF
0x10020000:0x1003FFFF
0x10040000:0x1005FFFF
0x10060000:0x1007FFFF
0x10080000:0x10087FFF
0x10088000:0x1008FFFF
0x18000000:0x1801FFFF
0x19000000:0x1901FFFF
0x1E000000:0x1E1FFFFF
0x1E880000:0x1E899FFF
0x1FC00000:0x1FC7FFFF
0x30000000:0x3001FFFF
RW,
RW,
RW,
RW,
RW,
RW,
RW,
RW,
RW,
RW,
RO,
RW,
Valid
Valid
Valid
Valid
Valid
Valid
Valid
Valid
Valid
Valid
Valid
Valid
0x40000000:0x407FFFFF
.
.
.
0x58000000:0x59FFFFFF
0x5A000000:0x5BFFFFFF
0x5C000000:0x5DFFFFFF
0x5E000000:0x5FFFFFFF
0x000000000:0x0007FFFFF
0x088000000:0x089FFFFFF
0x08A000000:0x08BFFFFFF
0x08C000000:0x08DFFFFFF
0x08E000000:0x08FFFFFFF
CacheMode=3,
CacheMode=3,
CacheMode=3,
CacheMode=3,
RW,
RW,
RW,
RW,
Valid
Valid
Valid
Valid
This example shows how use the atom ether-vc keyword to display line-card information for an ES20 line
card in slot 3.
Router# show platform copp rate-limit atom ether-vc
AToM Ether VC Index(12902): segtype(3) seghandle(0x5ECF7F34)
Disposition : flags(97) vlanid(502) local_vc_label(22691)
ForwardingTable: oper(12) flags(0x2100) vlan(502) dest_index(0x9ED)
Imposition: flags(0x21) egress_idx(0x0) ifnum(28)
tx_tvc(0x7D83) rvclbl[0](3356) rigplbl[1](1011) label[2](0)
label[3](0) ltl(0x9ED) mac(0014.1c80.f600) qos_info(0x0)
Platform Data:
loc_lbl acif_num fw_idx cword
eg_ifnum ckt_idx vlan ac_hdl
vc_hash
22691
615
0x0
0x3
28
0x8003
502 0x5ECF7F34 0x3266
Platform Index(0x81F68003) is_sw(1) is_vfi(0) vlan(502) pseudo_port_offset(3)
tx_tvc(0x7D83)
Statistics : Packets
Bytes
Drop Pkts Drop Bytes ID
Disposition: 0
0
0
0
0
Imposition : 0
0
0
0
0
Vlan func[1]: 502 (0x1F6) func(0:invalid) feat (0x0 )
Tx TVC Table
idx
ltl h pt cw vt efp adj v imp
x---- x-- d d- d- d- x--- x--- d x--SIP10G EoMPLS disp detailed info:
t vclbl
VLAN
Type
disp-idx
- d------- x---(d---) ------- x------0 00022691 01F6(0502) ether
00001692
SIP10G EoMPLS ipiw disp detailed info:
ipiw mac valid CE-MAC Address
b--- b-------- -------------0001 000000001 0016.9c6e.7480
VC Summary: vlan(502) VC count(1)
Related Commands
Command
Description
platform copp
pseudowire class
show msfc
Syntax Description
Command Modes
Command History
Examples
interface-type interface-number
vlan vlan-id
summary
Release
Modification
12.2(33)SRA
Options
dot1q
dot1q
default
default
dot1q-tunnel
dot1q-tunnel
access
access
access
access
access
access
access
access
access
access
access
access
access
access
access
The table below describes the significant fields shown in the display.
Table 133
Field
Description
VLAN
Interface
CircuitId
LTL
Related Commands
PseudoPort
State
Options
Command
Description
show platform
Syntax Description
Command Modes
Command History
Examples
epl
info
interface
fastethernet
gigabitethernet
port-channel
number
Interface number.
fwd_vlan
vlan-number
VLAN number.
level
vlan_list
Release
Modification
12.2(33)SRA
12.2(33)SXI
The following is sample output from the show platform cfm infocommand. The field descriptions are selfexplanatory.
Router# show platform cfm info
CFM is disabled
CFM unicast MAC 00d0.2b6c.b103, CFM multicast MAC 0180.c200.0030, AEB multicast MAC
0100.0ccc.ccc0
CFM Ingress Control Packet System Statistics:
Current software Rate Limit Setting: 1100 pkts/sec
Statistics are collected in intervals of 3 seconds.
Allow the first 3300 packets to pass each interval, drop thereafter
Current Ingress Count in this interval: 0 pkts
In this interval have we Exceeded Rate and Dropped pkts: NO
For the last 3 intervals the maximum sample had 0 packets in one interval.
Related Commands
Command
Description
show platform
Syntax Description
diag
Command Default
Command Modes
Command History
Release
Modification
Usage Guidelines
This command can be used to display debug and diagnostic information and indicate the status of field
replaceable unit (FRU) components in any Cisco ASR 1000 Series Router.
Examples
The following example displays diagnostic information for the Cisco ASR 1000 SPA Interface Processor
(SIP), shared port adapters (SPAs), Cisco ASR 1000 Embedded Services Processor (ESP), Cisco ASR 1000
Route Processors (RP), and power supplies. The ESP is shown as F0 or F1. The RPs are shown as R0 or
R1. The power supplies are shown as P0 and P1
Router#show platform diag
Chassis type: ASR1004
Slot: 0, ASR1000-SIP10
Running state
Internal state
Internal operational state
Physical insert detect time
Software declared up time
CPLD version
Firmware version
Sub-slot: 0/0, SPA-5X1GE-V2
Operational status
Internal state
Physical insert detect time
:
:
:
:
:
:
:
ok
online
ok
00:00:48 (4d22h ago)
00:01:40 (4d22h ago)
07091401
12.2(33r)XNB
: ok
: inserted
: 00:00:36 (4d22h ago)
ok
online
ok
00:00:48 (4d22h ago)
00:00:48 (4d22h ago)
07062111
12.2(33r)XNB
: ok, active
: 00:00:48 (4d22h ago)
: 00:04:56 (4d22h ago)
: ok, standby
: 00:02:50 (4d22h ago)
:
:
:
:
:
:
:
:
:
ok, active
online
ok
00:00:48 (4d22h
00:01:40 (4d22h
00:00:49 (4d22h
00:01:49 (4d22h
07051680
12.2(33r)XNB
ago)
ago)
ago)
ago)
: ok
: 00:01:40 (4d22h ago)
: ok
: 00:01:40 (4d22h ago)
The table below describes the significant fields shown in the display.
Table 134
Field
Description
Running state
Internal state
Related Commands
Field
Description
CPLD version
Firmware version
Command
Description
show platform
Syntax Description
resource-type
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(18)SXF
12.2(33)SRA
12.2(33)SXI
acl --Displays the capacities and utilizations for ACL/QoS TCAM resources.
cpu --Displays the capacities and utilizations for CPU resources.
eobc --Displays the capacities and utilizations for Ethernet out-of-band channel resources.
fabric --Displays the capacities and utilizations for Switch Fabric resources.
flash --Displays the capacities and utilizations for Flash/NVRAM resources.
forwarding --Displays the capacities and utilizations for Layer 2 and Layer 3 forwarding resources.
ibc --Displays the capacities and utilizations for interboard communication resources.
interface --Displays the capacities and utilizations for interface resources.
monitor --Displays the capacities and utilizations for SPAN resources.
multicast --Displays the capacities and utilizations for Layer 3 multicast resources.
netflow --Displays the capacities and utilizations for NetFlow resources.
pfc --Displays the capacities and utilizations for all the PFC resources including Layer 2 and Layer 3
forwarding, NetFlow, CPU rate limiters, and ACL/QoS TCAM resources.
power --Displays the capacities and utilizations for power resources.
qos --Displays the capacities and utilizations for QoS policer resources.
rate-limit --Displays the capacities and utilizations for CPU rate limiter resources.
rewrite-engine --Displays the packet drop and performance counters of the central rewrite engine on
supervisors and line cards. For detailed information, see the show platform hardware capacity
rewrite-engine command documentation.
system --Displays the capacities and utilizations for system resources.
vlan --Displays the capacities and utilizations for VLAN resources.
The show platform hardware capacity cpucommand displays the following information:
CPU utilization for the last 5 seconds (busy time and interrupt time), the percentage of the last 1minute 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 eobccommand displays the following information:
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 systemcommand 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)
Module-specific switching information, including the following information:
The show platform hardware capacity vlan command displays the following VLAN information:
Examples
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 CPU capacity and utilization information for the route processor, the
switch processor, and the LAN module in the Cisco 7600 series router:
Router# show platform hardware capacity cpu
CPU Resources
CPU utilization: Module
5 seconds
1 RP
0% / 0%
1 SP
5% / 0%
7
69% / 0%
8
78% / 0%
Processor memory: Module
Bytes:
Total
1 RP
176730048
1 SP
192825092
7
195111584
8
195111584
I/O memory: Module
Bytes:
Total
1 RP
35651584
1 SP
35651584
7
35651584
8
35651584
Router#
1 minute
1%
5%
69%
74%
Used
51774704
51978936
35769704
35798632
Used
12226672
9747952
9616816
9616816
5 minutes
1%
4%
69%
74%
%Used
29%
27%
18%
18%
%Used
34%
27%
27%
27%
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
EOBC Resources
Module
Packets/sec
Total packets
1 RP
Rx:
61
108982
Tx:
37
77298
1 SP
Rx:
34
101627
Tx:
39
115417
7
Rx:
5
10358
Tx:
8
18543
8
Rx:
5
12130
Tx:
10
20317
Router#
Dropped packets
0
0
0
0
0
0
0
0
This example shows how to display the current and peak switching utilization:
Router# show platform hardware capacity fabric
Switch Fabric Resources
Bus utilization: current is 100%, peak was 100% at 12:34 12mar45
Fabric utilization:
ingress
egress
Module channel speed current peak
current peak
1
0
20G
100% 100% 12:34 12mar45 100%
100%
1
1
20G
12%
80% 12:34 12mar45
12%
80%
4
0
20G
12%
80% 12:34 12mar45
12%
80%
13
0
8G
12%
80% 12:34 12mar45
12%
80%
Router#
12:34
12:34
12:34
12:34
12mar45
12mar45
12mar45
12mar45
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
Flash/NVRAM Resources
Usage: Module Device
Bytes:
Total
1 RP bootflash:
31981568
1 SP disk0:
128577536
1 SP sup-bootflash:
31981568
1 SP const_nvram:
129004
1 SP nvram:
391160
7
dfc#7-bootflash:
15204352
8
dfc#8-bootflash:
15204352
Router#
Used
15688048
105621504
29700644
856
22065
616540
0
%Used
49%
82%
93%
1%
6%
4%
0%
This example shows how to display the capacity and utilization of the EARLs present in the system:
Router# show platform hardware capacity forwarding
L2 Forwarding Resources
MAC Table usage:
Module Collisions Total
Used
%Used
6
0 65536
11
1%
VPN CAM usage:
Total
Used
%Used
512
0
0%
L3 Forwarding Resources
FIB TCAM usage:
Total
Used
%Used
72 bits (IPv4, MPLS, EoM)
196608
36
1%
144 bits (IP mcast, IPv6)
32768
7
1%
detail:
Protocol
Used
%Used
IPv4
36
1%
MPLS
0
0%
EoM
0
0%
IPv6
4
1%
IPv4 mcast
3
1%
IPv6 mcast
0
0%
Adjacency usage:
Total
Used
%Used
1048576
175
1%
Forwarding engine load:
Module
pps
peak-pps
peak-time
6
8
1972 02:02:17 UTC Thu Apr 21 2005
Netflow Resources
TCAM utilization:
Module
Created
Failed
%Used
6
1
0
0%
ICAM utilization:
Module
Created
Failed
%Used
6
0
0
0%
Flowmasks:
Mask#
Type
Features
IPv4:
0
reserved
none
IPv4:
1
Intf FulNAT_INGRESS NAT_EGRESS FM_GUARDIAN
IPv4:
2
unused
none
IPv4:
3
reserved
none
IPv6:
0
reserved
none
IPv6:
1
unused
none
IPv6:
2
unused
none
IPv6:
3
reserved
none
CPU Rate Limiters Resources
Rate limiters:
Total
Used
Reserved
%Used
Layer 3
9
4
1
44%
Layer 2
4
2
2
50%
ACL/QoS TCAM Resources
Total packets
5001419
1943884
Dropped packets
0
0
This example shows how to display the capacity and utilization of resources for Layer 3 multicast
functionality:
Router# show platform hardware capacity
multicast
L3 Multicast Resources
IPv4 replication mode: ingress
IPv6 replication mode: ingress
Bi-directional PIM Designated Forwarder Table usage: 4 total, 0 (0%) used
Replication capability: Module
IPv4
IPv6
5
egress
egress
9
ingress
ingress
MET table Entries: Module
Total
Used
%Used
5
65526
6
0%
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
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
QoS Policer Resources
Aggregate policers: Module
1
5
Microflow policer configurations: Module
1
5
Router#
Total
1024
1024
Total
64
64
Used
102
1
Used
32
1
%Used
10%
1%
%Used
50%
1%
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
Switching Resources: Module
Part number
Series
CEF mode
5
WS-SUP720-BASE
supervisor
CEF
9
WS-X6548-RJ-45
CEF256
CEF
Router#
Related Commands
Command
Description
show msfc
show platform
show platform hardware capacity rewrite-engine Displays the packet drop and performance counters
of the central rewrite engine on supervisors and line
cards.
Syntax Description
Command Modes
Command History
memory
detailed
msi-all
slot
session-count
slot-number
Slot number.
all
uid
subscriber-session UID
all
vrf
vrf-number
VRF ID.
all
Release
Modification
12.2(33)SRC
15.0(1)S
Examples
The following is sample output from the show platform isg vrf allcommand. The field descriptions are
self-explanatory.
Router# show platform isg vrf all
dbg_stdby_cd_fibobj
dbg_stdby_cd_rem_fibobj
dbg_stdby_cd_no_objhdl
dbg_stdby_cd_no_ps
dbg_stdby_unpck_vrf_node
dbg_stdby_unpck_pl_hdl
dbg_stdby_unpck_rem_vrf_node
Related Commands
35042
492
1120
0
1612
33922
0
Command
Description
show platform
Syntax Description
Command Modes
Command History
Examples
link-monitor
loopback
Release
Modification
12.2(33)SRC
The following is sample output from the show platform oam link-monitor interface GigabitEthernet
1/1command. The fields are self-explanatory.
Router# show platform oam link-monitor interface GigabitEthernet 1/1
Interface Gi1/1:
first_poll = 0
symprd_tlv_sent = 0
frmprd_tlv_sent = 0
frm_poll_cnt = 1
frmsec_poll_cnt = 10
rxcrc_poll_cnt = 1
txcrc_poll_cnt = 1
symbol_period_start = 00:00:01.752
prev_rx_error_frames = 2
total_rx_error_frames = 0
error_frame_period_start = 2
total_frame_period_start = 20
prev_error_frame_seconds = 0
total_error_frame_seconds = 0
prev_rx_crc_error_frames = 0
prev_tx_crc_error_frames = 2
total_frm_tlvs = 0
total_frmsec_tlvs = 0
total_symprd_tlvs = 0
total_frmprd_tlvs = 0
Related Commands
Command
Description
show platform
Syntax Description
atm
ccp
slot-number
Slot number.
cpu-number
CPU number.
cwpa-ce3
cwpa-ct3
cwpa-e1
cwpa-stm1
cwpa-t1
frame-relay
hdlc
if-config
bay-number
default-retvals
mlp
multilink-vc
Command Modes
Command History
Examples
osm-chocx
osm-ct3
ppp
shadowstate
spa-chocx
spa-ct3
switchover
Release
Modification
12.2(33)SRC
The following is sample output from the show platform redundancycommand with the if-config
keyword. The fields are self-explanatory.
Router# show platform redundancy if-config 4 0
Current number of elements = 0
Current maximum elements = 128
List was grown = 0 times
Number of elements sorted = 0
List errors = 0
List flags = 0x1E
Current element pointer = 0x0
List pointer = 0x50A27438
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| C=Command T=Type P=Port t=timedOut D=Dirty S=Sync
|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| C | T | P
| key address | t | D | S | value
|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Related Commands
Command
Description
show platform
Syntax Description
bootflash:
stby-bootflash:
fpd:
Synthetic file system that is used by the fieldprogrammable device (FPD) upgrade process--for
Cisco Technical Support only.
harddisk:
stby-harddisk:
obfl:
stby-obfl:
usb0:
stby-usb0:
usb1:
stby-usb1:
all
details
Command Default
Command Modes
Command History
Release
Modification
Usage Guidelines
Use this command to ascertain the presence or absence of specific files and to determine space usage in the
file system. This command is helpful to monitor the growth of log file sizes, because rapid growth of log
files could indicate possible problems with the router.
Examples
The following example displays information about the files in the bootflash file system. It also shows the
number of bytes used out of the total available in the bootflash file system.
Router# show platform software filesystem bootflash:
-#- --length-- ---------date/time--------- path
1
4096 Apr 01 2008 13:34:30 +00:00 /bootflash/
2
16384 Dec 04 2007 04:32:46 +00:00 /bootflash/lost+found
3
4096 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh
4
963 Dec 04 2007 06:06:16 +00:00 /bootflash/.ssh/ssh_host_key
5
627 Dec 04 2007 06:06:16 +00:00 /bootflash/.ssh/ssh_host_key.pub
6
1675 Dec 04 2007 06:06:18 +00:00 /bootflash/.ssh/ssh_host_rsa_key
7
382 Dec 04 2007 06:06:18 +00:00 /bootflash/.ssh/ssh_host_rsa_key.pub
8
668 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh/ssh_host_dsa_key
9
590 Dec 04 2007 06:06:24 +00:00 /bootflash/.ssh/ssh_host_dsa_key.pub
10
4096 Dec 04 2007 06:06:36 +00:00 /bootflash/.rollback_timer
11
4096 Mar 18 2008 17:31:17 +00:00 /bootflash/.prst_sync
12
4096 Dec 04 2007 04:34:45 +00:00 /bootflash/.installer
13 205951180 Mar 18 2008 17:23:03 +00:00 /bootflash/asr1000rp1-advipservicesk
14
46858444 Mar 18 2008 17:28:55 +00:00 /bootflash/asr1000rp1-espbase.02.01.
15
20318412 Mar 18 2008 17:28:56 +00:00 /bootflash/asr1000rp1-rpaccess-k9.02
16
22266060 Mar 18 2008 17:28:57 +00:00 /bootflash/asr1000rp1-rpbase.02.01.0
17
21659852 Mar 18 2008 17:28:57 +00:00 /bootflash/asr1000rp1-rpcontrol.02.0
18
45934796 Mar 18 2008 17:28:58 +00:00 /bootflash/asr1000rp1-rpios-advipser
19
34169036 Mar 18 2008 17:28:59 +00:00 /bootflash/asr1000rp1-sipbase.02.01.
20
22067404 Mar 18 2008 17:29:00 +00:00 /bootflash/asr1000rp1-sipspa.02.01.0
21
7180 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
The table below describes the significant fields shown in the displays of file system information.
Table 135
Field
Description
Length
Date/Time
Field
Description
Path
Filesystem Path
Filesystem Type
Related Commands
Mounted
Command
Description
Syntax Description
database database
messaging
chassis-manager slot
cpp-control-process
forwarding-manager slot
host-manager slot
interface-manager slot
1146
ios slot
logger slot
pluggable-services slot
Displays memory information for the pluggableservices process in the specified slot. Possible slot
values are:
shell-manager slot
brief
Command Default
Command Modes
Diagnostic (diag)
Command History
Usage Guidelines
Release
Modification
Examples
The following example displays memory information for the Forwarding Manager process for Cisco ASR
1000 Series RP slot 0:
Router# show platform software memory forwarding-manager r0
Module: cdllib
allocated: 900, requested: 892, overhead: 8
Allocations: 2, failed: 0, frees: 1
Module: eventutil
allocated: 117379, requested: 117059, overhead: 320
Allocations: 46, failed: 0, frees: 6
Module: uipeer
allocated: 9264, requested: 9248, overhead: 16
Allocations: 3, failed: 0, frees: 1
Module: Summary
allocated: 127543, requested: 127199, overhead: 344
Allocations: 51, failed: 0, frees: 8
The table below describes the significant fields shown in the display.
Table 136
Field
Description
Module:
Name of submodule.
allocated:
requested:
overhead:
Allocation overhead.
Allocations:
failed:
frees:
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
module
allocated
requested
allocs
frees
-----------------------------------------------------------------------CPP Features
692
668
3
0
Summary
497816
495344
323
14
chunk
419322
419290
4
0
eventutil
68546
66146
312
12
uipeer
9256
9240
4
2
The table below describes the significant fields shown in the brief keyword display.
Table 137
Field
Description
module
Name of submodule.
allocated
requested
allocs
frees
Syntax Description
slot
brief
Command Default
Command Modes
Command History
Release
Modification
Usage Guidelines
If no slot is specified, the command returns mounted file systems for the active RP.
This command allows you to ascertain the presence or absence of specific system mounts. For example,
this command might be used to determine /tmp-related mounts, which are used to create many run-time
directories and files.
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.
Examples
The following example displays mounted file systems for the active RP:
Router# show platform software mount
Filesystem
Used
rootfs
0
proc
0
sysfs
0
none
524
/dev/bootflash1
298263
/dev/harddisk1
609208
/dev/loop1
28010
/dev/loop2
26920
/dev/loop3
48236
/dev/loop4
6134
/dev/loop5
43386
/dev/loop6
30498
/dev/loop7
14082
none
524
/proc/bus/usb
0
/dev/mtdblock1
460
automount(pid4165)
0
Available
0
0
0
1037640
42410
4025132
0
0
0
0
0
0
0
1037640
0
1588
0
Use% Mounted on
- /
- /proc
- /sys
1% /dev
88% /bootflash
14% /misc/scratch
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
100% /tmp/sw/mount/2007-10-14_...
1% /dev
- /proc/bus/usb
23% /obfl
- /vol
The following example displays mounted file systems for the Cisco ASR 1000 Series ESP in ESP slot 0:
Router# show platform software mount f0
Filesystem
Used
rootfs
0
proc
0
sysfs
0
none
10864
/dev/loop1
41418
none
10864
/proc/bus/usb
0
/dev/mtdblock1
504
automount(pid3210)
0
The following example displays mounted file systems for the active Cisco ASR 1000 Series RP:
Router# show platform software mount rp active
Filesystem
Used
Available
rootfs
0
0
proc
0
0
sysfs
0
0
none
436
1037728
/dev/bootflash1
256809
83864
/dev/harddisk1
252112
4382228
/dev/loop1
30348
0
/dev/loop2
28394
0
/dev/loop3
42062
0
/dev/loop4
8384
0
/dev/loop5
41418
0
/dev/loop6
21612
0
Use% Mounted on
- /
- /proc
- /sys
1% /dev
76% /bootflash
6% /misc/scratch
100% /tmp/sw/mount/2007-09-27_...
100% /tmp/sw/mount/2007-09-27_...
100% /tmp/sw/mount/2007-09-27_...
100% /tmp/sw/mount/2007-09-27_...
100% /tmp/sw/mount/2007-09-27_...
100% /tmp/sw/mount/2007-09-27_...
/dev/loop7
none
/proc/bus/usb
/dev/mtdblock1
automount(pid4004)
16200
436
0
484
0
0
1037728
0
1564
0
100%
1%
24%
-
/tmp/sw/mount/2007-09-27_...
/dev
/proc/bus/usb
/obfl
/vol
The table below describes the significant fields shown in the SIP slot (0, 1, or 2) displays.
Table 138
Field
Description
Filesystem
Used
Available
Use%
Mounted on
The following example displays abbreviated (brief keyword) mounted file system information for Cisco
ASR 1000 Series SIP slot 0:
Router# show
Mount point:
Type
:
Location :
Options :
Mount point:
Type
:
Location :
Options :
Mount point:
Type
:
Location :
Options :
Mount point:
Type
:
Location :
Options :
Mount point:
Type
:
Location :
Options :
Mount point:
Type
:
Location :
Options :
none
tmpfs
/dev
rw
Mount point:
Type
:
Location :
Options :
/proc/bus/usb
usbfs
/proc/bus/usb
rw
Mount point:
Type
:
Location :
Options :
/dev/mtdblock1
jffs2
/obfl
rw,noatime,nodiratime
Mount point:
Type
:
Location :
Options :
automount(pid3199)
autofs
/misc1
rw,fd=5,pgrp=3199,timeout=60,minproto=2,maxproto=4,indirect
The tab le below describes the significant fields shown in the brief keyword display.
Table 139
Field
Description
Mount point:
Type:
Location:
Options:
Syntax Description
slot
name process-name
process-id process-id
sort memory
summary
Command Default
Command Modes
Command History
Release
Modification
Usage Guidelines
The name and process-id keywords can be used to narrow the process list display down to specific
processes.
The sort keyword can be used to sort the process list by memory size.
The summary keyword can be used to display summary information about running processes.
Examples
The following example displays information about running processes for Cisco ASR 1000 Series SIP slot
0:
Router# show platform software process list 0
Name
Pid
PPid Group Id Status
Priority Size
-----------------------------------------------------------------------------init
1
0
1 S
20 1974272
ksoftirqd/0
2
1
1 S
39 0
events/0
3
1
1 S
15 0
khelper
4
1
1 S
15 0
kthread
5
1
1 S
15 0
kblockd/0
19
5
1 S
15 0
khubd
23
5
1 S
15 0
pdflush
59
5
1 S
20 0
pdflush
60
5
1 S
20 0
kswapd0
61
5
1 S
15 0
aio/0
62
5
1 S
15 0
xfslogd/0
63
5
1 S
15 0
xfsdatad/0
64
5
1 S
15 0
mtdblockd
626
1
1 S
20 0
loop0
1370
1
1 S
0 0
portmap
1404
1
1404 S
20 2076672
portmap
1406
1
1406 S
20 2076672
loop1
1440
1
1 S
0 0
udevd
2104
1
2104 S
16 1974272
jffs2_gcd_mtd1
2796
1
1 S
30 0
klogd
3093
1
3093 S
20 1728512
automount
3199
1
3199 S
20 2396160
xinetd
3214
1
3214 S
20 3026944
xinetd
3216
1
3216 S
20 3026944
pvp.sh
3540
1
3540 S
20 3678208
inotifywait
3575
3540
3575 S
20 1900544
pman.sh
3614
3540
3614 S
20 3571712
pman.sh
3714
3540
3714 S
20 3571712
btrace_rotate.s
3721
3614
3721 S
20 3133440
agetty
3822
1
3822 S
20 1720320
mcp_chvrf.sh
3823
1
3823 S
20 2990080
sntp
3824
1
3824 S
20 2625536
issu_switchover
3825
1
3825 S
20 3899392
xinetd
3827
3823
3823 S
20 3026944
cmcc
3862
3714
3862 S
20 26710016
pman.sh
3883
3540
3883 S
20 3571712
pman.sh
4014
3540
4014 S
20 3575808
hman
4020
3883
4020 R
20 19615744
imccd
4114
4014
4114 S
20 31539200
inotifywait
4196
3825
3825 S
20 1896448
pman.sh
4351
3540
4351 S
20 3575808
plogd
4492
4351
4492 S
20 22663168
inotifywait
4604
3721
4604 S
20 1900544
The table below describes the significant fields shown in the display.
Table 140
Field
Description
Name
Pid
Process ID.
PPid
Group Id
Status
Process status.
Priority
Process priority.
Size
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
Process id
: 25938
Parent process id: 3891
Group id
: 3891
Status
: S
Session id
: 3816
User time
: 0
Kernel time
: 0
Priority
: 20
Virtual bytes
: 2482176
Resident pages
: 119
Resident limit
: 4294967295
Minor page faults: 182
Major page faults: 0
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
Name: init
Process id
:
Parent process id:
Group id
:
Status
:
Session id
:
User time
:
Kernel time
:
Priority
:
Virtual bytes
:
Resident pages
:
Resident limit
:
Minor page faults:
Major page faults:
1
0
1
S
1
1
741
20
1974272
161
4294967295
756
0
The table below describes the significant fields shown in the name and process-id keyworddisplays.
Table 141
show platform software process list name and process-id Field Descriptions
Field
Description
Name
Process id
Process ID.
Parent process id
Group id
Status
Process status.
Session id
User time
Kernel time
Priority
Process priority.
Virtual bytes
Resident pages
Resident limit
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
Running
: 4
Sleeping
: 50
Disk sleeping
: 0
Zombies
: 0
Stopped
: 0
Paging
: 0
Up time
: 1562
Idle time
: 1511
User time
: 1606
Kernel time
: 1319
Virtual memory
: 587894784
Pages resident
: 45436
Major page faults: 25
Minor page faults: 149098
Architecture
: ppc
Memory (kB)
Physical
: 524288
Total
: 479868
Used
: 434948
Free
: 44920
Active
: 183020
Inactive
: 163268
Inact-dirty
: 0
Inact-clean
: 0
Dirty
: 0
AnonPages
: 76380
Bounce
: 0
Cached
: 263764
Commit Limit
Committed As
High Total
High Free
Low Total
Low Free
Mapped
NFS Unstable
Page Tables
Slab
VMmalloc Chunk
VMmalloc Total
VMmalloc Used
Writeback
Swap (kB)
Total
Used
Free
Cached
Buffers (kB)
Load Average
1-Min
5-Min
15-Min
:
:
:
:
:
:
:
:
:
:
:
:
:
:
239932
201452
0
0
479868
44920
59996
0
1524
73760
426840
474856
47372
0
:
:
:
:
:
0
0
0
0
6144
: 0.00
: 0.00
: 0.00
The table below describes the significant fields shown in the summary keyword display.
Table 142
Field
Description
Running
Sleeping
Disk sleeping
Zombies
Stopped
Paging
Up time
Idle time
User time
Kernel time
Virtual memory
Pages resident
Architecture
Field
Description
Memory (kB)
Physical
Total
Used
Free
Active
Inactive
Inact-dirty
Inact-clean
Dirty
AnonPages
Bounce
Cached
Commit Limit
Committed As
High Total
Field
Description
High Free
Low Total
Low Free
Mapped
NFS Unstable
Page Tables
Slab
VMalloc Chunk
VMalloc Total
VMalloc Used
Writeback
Swap (kB)
Total
Used
Free
Cached
Buffers (kB)
Buffers heading.
Load Average
Field
Description
1-Min
5-Min
15-Min
The following example displays process summary information for Cisco ASR 1000 Series sorted by
memory size:
Router#show platform software process list R0 sort memory
Name
Pid
PPid Group Id Status
Priority Size
-----------------------------------------------------------------------------linux_iosd-imag
27982
26696
27982 S
20 4294967295
fman_rp
25857
25309
25857 S
20 684867584
vman
30685
29587
30685 S
20 194850816
smand
30494
28948
30494 S
20 103538688
libvirtd
5260
5254
5254 S
20 83197952
python
10234
10233
10210 S
20 29765632
python
10975
10234
10975 S
20 29765632
python
10977
10234
10977 S
20 29765632
python
10978
10234
10978 S
20 29765632
python
10979
10234
10979 S
20 29765632
python
10981
10234
10981 S
20 29765632
automount
15682
1
15682 S
20 25092096
cmand
25530
24760
25530 S
20 23789568
imand
27198
26090
27198 S
20 22040576
psd
31284
28535
31284 S
20 16019456
emd
25712
24917
25712 S
20 15302656
hman
26622
25617
26622 R
20 14544896
plogd
28878
27718
28878 S
20 12349440
btrace_rotate.s
25251
24643
25251 S
20 6008832
sort_files_by_i
30092
29066
30092 S
20 5234688
periodic.sh
28469
27490
28469 S
20 4812800
rotee
5403
1
5396 S
20 4788224
rotee
5412
1
5411 S
20 4788224
rotee
5438
1
5437 S
20 4788224
rotee
5482
1
5481 S
20 4788224
rotee
9844
1
9843 S
20 4788224
rotee
9958
1
9957 S
20 4788224
rotee
16942
1
16941 S
20 4788224
rotee
16946
1
16945 S
20 4788224
rotee
24383
1
24382 S
20 4788224
rotee
24742
1
24741 S
20 4788224
rotee
24960
1
24959 S
20 4788224
rotee
25107
1
25106 S
20 4788224
rotee
25534
1
25533 S
20 4788224
rotee
25542
1
25541 S
20 4788224
rotee
25880
1
25879 S
20 4788224
rotee
26390
1
26389 S
20 4788224
rotee
26881
1
26880 S
20 4788224
rotee
27728
1
27727 S
20 4788224
rotee
27882
1
27881 S
20 4788224
rotee
28867
1
28866 S
20 4788224
rotee
29220
1
29219 S
20 4788224
rotee
29257
1
29256 S
20 4788224
rotee
29405
1
29404 S
20 4788224
rotee
29784
1
29783 S
20 4788224
oom.sh
5560
5246
5560 S
20 4427776
reflector.sh
15598
1
15598 S
20 3997696
droputil.sh
15600
1
15600 S
20 3997696
pvp.sh
24336
1
24335 S
20 3870720
pman.sh
29066
24336
24335 S
14 3805184
pman.sh
24643
24336
24335 S
14 3801088
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
pman.sh
chasync.sh
lighttpd
iptbl.sh
rollback_timer.
oom.sh
wui-lighttpd-la
wui-app-launch.
mcp_chvrf.sh
mcp_chvrf.sh
auxinit.sh
mcp_chvrf.sh
mcp_chvrf.sh
libvirtd.sh
xinetd
xinetd
xinetd
xinetd
sleep
sleep
sleep
sntp
init
portmap
rpc.mountd
inotifywait
inotifywait
inotifywait
inotifywait
inotifywait
inotifywait
udevd
inotifywait
klogd
kthreadd
migration/0
ksoftirqd/0
watchdog/0
migration/1
ksoftirqd/1
watchdog/1
events/0
events/1
khelper
netns
kblockd/0
kblockd/1
kacpid
kacpi_notify
cqueue
ata/0
ata/1
ata_aux
ksuspend_usbd
khubd
kseriod
pdflush
pdflush
kswapd0
aio/0
aio/1
27490
26696
9679
9812
24760
24917
25309
25617
26090
27718
28535
28948
29587
5248
11522
5252
5226
5246
10223
10210
10233
11521
15593
5223
5224
5254
5231
5232
15714
15716
30979
31820
32645
5225
1
2654
15751
5459
16968
17050
24572
5462
5522
13853
32725
24325
2
3
4
5
6
7
8
9
10
11
14
59
60
61
62
144
148
149
150
151
156
159
210
211
212
256
257
24336
24336
24336
24336
24336
24336
24336
24336
24336
24336
24336
24336
24336
1
11521
1
1
1
9812
9679
10210
10223
1
1
1
1
5223
5224
1
1
28469
5560
30092
1
0
1
1
5248
15598
15600
24336
5226
5252
1
25251
1
0
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
24335
24335
24335
24335
24335
24335
24335
24335
24335
24335
24335
24335
24335
5248
10223
5252
5226
5246
10223
10210
10210
10223
15593
5223
5224
5254
5223
5224
15714
15716
28469
5560
30092
5225
1
2654
15751
5459
16968
17050
24335
5462
5522
13853
32725
24325
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
14
14
14
14
14
14
14
14
14
14
14
14
14
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
16
20
20
15
4294967196
15
4294967196
4294967196
15
4294967196
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
20
20
15
15
15
3801088
3788800
3784704
3784704
3784704
3784704
3784704
3784704
3784704
3784704
3784704
3784704
3784704
3620864
3543040
3477504
3014656
2977792
2605056
2600960
2596864
2596864
2584576
2580480
2580480
2576384
2183168
2183168
2183168
2183168
1925120
1925120
1925120
1863680
1859584
1806336
1789952
1761280
1761280
1761280
1761280
1757184
1757184
1757184
1757184
1650688
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
scsi_eh_0
scsi_eh_1
scsi_eh_2
scsi_eh_3
scsi_eh_4
usb-storage
scsi_eh_5
usb-storage
scsi_eh_6
usb-storage
rpciod/0
rpciod/1
nfsiod
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
loop8
lockd
nfsd
nfsd
nfsd
nfsd
nfsd
nfsd
nfsd
nfsd
lsmpi-refill
lsmpi-xmit
lsmpi-rx
ddr_err_monitor
mtdblockd
scansta
1077
1079
1081
1083
1115
1116
1129
1130
1133
1134
2333
2336
2345
2424
2708
2745
2782
2819
2928
2965
3002
3075
15741
15742
15743
15744
15745
15746
15747
15748
15749
15852
15853
15854
16267
16292
16315
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
15
15
15
15
15
15
15
15
15
15
15
15
15
0
0
0
0
0
0
0
0
0
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Syntax Description
slot
slot
Slot information.
monitor
cycles
cycles
interval
delay
lines
lines-of-output
Command Default
Command Modes
Command History
Examples
Release
Modification
The following is a sample output of the show platform software process slot command. Only 23 lines are
displayed because the lines-of-output argument is set to 23:
Router# show platform software process slot 0 monitor cycles 3 interval 2 lines 23
top - 19:29:32 up 1 day, 4:46, 0 users, load average: 0.10, 0.11, 0.09
Tasks: 78 total,
4 running, 74 sleeping,
0 stopped,
0 zombie
Cpu(s): 3.0%us, 2.9%sy, 0.0%ni, 93.9%id, 0.0%wa, 0.1%hi, 0.1%si, 0.0
Mem:
449752k total,
328940k used,
120812k free,
6436k buffers
Swap:
0k total,
0k used,
0k free,
155396k cached
PID USER
PR NI VIRT RES SHR S %CPU %MEM
TIME+ COMMAND
7223 root
20
0 124m 46m 23m R 2.0 10.5 11:13.01 mcpcc-lc-ms
8135 root
20
0 123m 46m 25m R 2.0 10.6 35:59.75 mcpcc-lc-ms
1 root
20
0 2156 644 556 S 0.0 0.1
0:02.05 init
2 root
15 -5
0
0
0 S 0.0 0.0
0:00.04 kthreadd
3 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 ksoftirqd/0
4 root
RT -5
0
0
0 S 0.0 0.0
0:00.00 watchdog/0
5 root
15 -5
0
0
0 S 0.0 0.0
0:00.04 events/0
6 root
15 -5
0
0
0 S 0.0 0.0
0:00.10 khelper
9 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 netns
55 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 kblockd/0
63 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 ata/0
64 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 ata_aux
70 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 khubd
73 root
15 -5
0
0
0 S 0.0 0.0
0:00.00 kseriod
118 root
20
0
0
0
0 S 0.0 0.0
0:00.00 pdflush
119 root
20
0
0
0
0 S 0.0 0.0
0:00.00 pdflush
top - 19:29:35 up 1 day, 4:46, 0 users, load average: 0.41, 0.17, 0.11
--More--
The table below describes the significant fields shown in the display.
Table 143
Field
Description
%CPU
CPU Usage
%MEM
Memory Usage
COMMAND
NI
Nice value
PID
Process ID
PR
Priority
RES
Process status
SHR
Field
Description
TIME+
USER
User name
VIRT
Syntax Description
snapshot
slot
status
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
Use the show platform software snapshot status command to view the status of a bootflash snapshot
request.
Examples
This example shows how to view the status of bootflash snapshot requests on the processor in the RO slot.
router#show platform software snapshot R0 status
Related Commands
Command
Description
Syntax Description
file
fpd:filename.tgz
harddisk:filename .tgz
obfl:filename.tgz
stby-obfl:filename.tgz
stby-usb0:filename.tgz
stby-usb1:filename.tgz
Command Default
Command Modes
Diagnostic (diag)
Command History
Usage Guidelines
Release
Modification
If the file keyword is specified, the specification of the bootflash: or harddisk: keyword and filename is
required.
The show platform software tech-support command without a destination file path specification returns a
large volume of information in a short period of time. You should save the output of the show platform
software tech-support command in a log file to send to Cisco Technical Support for analysis.
Examples
The following example displays system information for Cisco Technical Support:
Router# show platform software tech-support
---- show version installed ----Type: provisioning file, Version: unknown
Provisioned on: RP0, Status: active
File: packages.conf.super
Modified: 2007-11-07 15:06:12.212303000 +0000
SHA1 (header): d929d995d5ba2d3dedf67137c3e0e321b1727d7b
SHA1 (calculated): d929d995d5ba2d3dedf67137c3e0e321b1727d7b
SHA1 (external): a16881b6a7e3a5593b63bf211f72b8af9c534063
instance address
: 0X890DE9B4
fast failover address
: 00000000
cpp interface handle 0
instance address
: 0X890DE9B8
fast failover address
: 00000000
cpp interface handle 0
instance address
: 0X890DE9BC
fast failover address
: 00000000
...
Note
The show platform software tech-support command returns a large volume of information in a short period
of time. The example above has been abbreviated for the purposes of this description.
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
Syntax Description
vrf-number
all
detail
Command Default
Command Modes
Command History
Examples
Release
Modification
15.1(1)S
Related Commands
Command
Description
show platform
Syntax Description
Command Modes
Command History
Examples
mtu
slot slot-number
port port-number
Release
Modification
12.2(33)SRA
The following is sample output from the show platform supervisorcommand. The fields are selfexplanatory.
Router# show platform supervisor mtu slot 5 port 1
User configured MTU : 9216
Real Operating MTU : 9236
Related Commands
Command
Description
show platform
show power
To display information about the power status, use the show powercommand in user EXEC or privileged
EXEC mode.
show power [available | inline [interface number | module number] | redundancy-mode | status
{all | fan-tray fan-tray-number | module slot | power-supply pwr-supply-number} | total | used]
Syntax Description
available
inline
interface number
module number
redundancy-mode
status
all
fan-tray fan-tray-number
module slo t
power-supply pwr-supply-number
total
used
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17a)SX1
12.2(17b)SXA
12.2(17d)SXB
12.2(18)SXF
12.2(33)SRA
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 poweroutput 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:
Inline power
module
Examples
#
9
current
0.300A
system
system
system
system
power
power
power
power
This example shows how to display the power status for all FRU types:
Router#
show power
status all
FRU-type
power-supply
module
module
module
Router#
#
1
1
2
5
current
27.460A
4.300A
4.300A
2.690A
This example shows how to display the power status for a specific module:
Router#
show power
status module 1
FRU-type
#
module
1
Router#
current
-4.300A
This example shows how to display the power status for a specific power supply:
Router#
show power
status power-supply 1
FRU-type
#
current
power-supply
1
27.460A
Router#
Power-Capacity
Watts
A @42V
------- -----2672.04 63.62
2773.68 66.04
PS-Fan
Status
-----OK
OK
Output
Status
-----OK
OK
Oper
State
----on
on
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
Interface
-------------------FastEthernet9/1
FastEthernet9/2
.
.
. <Output truncated>
Admin
Oper
Power ( mWatt ) Device
----- ---------- --------------- ----------auto on
6300
Cisco 6500 IP Phone
auto on
6300
Cisco 6500 IP Phone
This command shows how to display the inline power status for a specific module:
Router
# show power
inline mod 7
Interface
Power
Device
Class
(Watts)
---------- ----- ---------- ------- -------------- ----------Gi7/1
auto
on
6.3 Cisco IP Phone 7960 n/a
Gi7/2
static power-deny
0 Ieee PD
3
.
.
. <Output truncated>
Related Commands
Admin
Oper
Command
Description
power enable
power redundancy-mode
show processes
To display information about the active Cisco IOS, Cisco IOS XE, or the Cisco IOS Software Modularity
POSIX-style processes, use the show processes command in user EXEC or privileged EXEC mode.
Cisco IOS Software
show processes [history | process-id | timercheck]
Cisco IOS Software Modularity Images and Cisco Catalyst 4500e Series Switches Running Cisco IOS XE
Software
show processes
Syntax Description
Command Modes
Command History
history
process-id
timercheck
Release
Modification
10.0
12.2(2)T
12.3(2)T
12.2(18)SXF4
12.3(14)T
12.2(33)SRA
Usage Guidelines
Release
Modification
15.1(2)S
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software
images. The following sections show output examples for each image:
The table below describes the significant fields shown in the display.
Table 144
Field
Description
one minute
five minutes
PID
Process ID.
Ty
* (currently running)
E (waiting for an event)
S (ready to run, voluntarily relinquished
processor)
rd (ready to run, wakeup conditions have
occurred)
we (waiting for an event)
sa (sleeping until an absolute time)
si (sleeping for a time interval)
sp (sleeping for a time interval as an alternate
call
st (sleeping until a timer expires)
hg (hung: the process will never execute again)
xx (dead: the process has terminated, but has
not yet been deleted)
PC
Runtime (ms)
Invoked
uSecs
Stacks
TTY
Process
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/en/US/products/sw/iosswrel/ps1828/
products_tech_note09186a00800a65d0.shtml.
The following is sample output from the s how processes history command:
Router# show processes history
PID Exectime(ms)
3
12
16
0
21
0
22
0
67
0
39
0
16
0
21
0
22
0
16
0
21
0
22
0
67
0
39
0
24
0
11
0
69
0
69
0
51
0
69
0
36
0
69
0
--More--
The table below describes the significant fields shown in the display.
Table 145
Field
Description
PID
Process ID.
Exectime (ms)
Caller PC
Process Name
The following is sample output from the s how processes process-id command:
Router# show processes 6
Process ID 6 [Pool Manager], TTY 0
Memory usage [in bytes]
Holding: 921148, Maximum: 940024, Allocated: 84431264, Freed: 99432136
Getbufs: 0, Retbufs: 0, Stack: 12345/67890
CPU usage
PC: 0x60887600, Invoked: 188, Giveups: 100, uSec: 24
Field
Description
Process ID
TTY
Holding
Maximum
Allocated
Freed
Getbufs
Retbufs
Stack
CPU usage
PC
Invoked
Giveups
uSec
5Sec
1Min
5Min
Field
Description
Average
Age
Runtime
State
Priority
The table below describes the significant fields shown in the display.
Table 147
Field
Description
PID
Process ID.
TID
Task ID.
Prio
Process priority.
STATE
Field
Description
Blocked
Stack
CPU
Name
Process name.
five minutes: 3%
Process
init
kthreadd
migration/0
ksoftirqd/0
migration/1
ksoftirqd/1
events/0
events/1
khelper
kblockd/0
kblockd/1
khubd
kseriod
kmmcd
pdflush
pdflush
kswapd0
aio/0
aio/1
kpsmoused
rpciod/0
rpciod/1
udevd
loop1
loop2
loop3
dbus-daemon
portmap
portmap
sshd
xinetd
xinetd
vsi work/0
The table below describes the significant fields shown in the display.
Table 148
Field
Description
Related Commands
Field
Description
one minute
five minutes
PID
Process ID.
TID
Thread ID.
Runtime(ms)
Invoked
uSecs
Stacks
Process
Process name.
Command
Description
Syntax Description
Command Modes
history
table
summary
sorted
1min
5min
5sec
detailed
process-id
process-name
Command History
Usage Guidelines
Release
Modification
12.0
12.2(2)T
12.3(8)
12.3(14)T
12.2(18)SXF4
12.2(33)SRA
12.2(33)SB
12.2(33)SCB3
15.0(1)M
Maximum usage is measured and recorded every second; average usage is calculated on periods of more
than one second. Consistently high CPU utilization over an extended period indicates a problem. Use the
show processes cpu command to troubleshoot. Also, you can use the output of this command in the Cisco
Output Interpreter tool to display potential issues and fixes. Output Interpreter is available to registered
users of Cisco.com who are logged in and have Java Script enabled.
For a list of system processes, go to http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/
products_tech_note09186a00800a65d0.shtml.
Cisco IOS Software Modularity
Cisco IOS Software Modularity images display only one graph that shows the CPU utilization for the last
60 minutes. The horizontal axis shows times (for example, 0, 5, 10, 15 minutes), and the vertical axis
shows total percentage of CPU utilization (0 to 100 percent).
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software
images. The following sections show output examples for each image:
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
90
80
* *
* *
* * * *
70 * * ***** * ** ***** *** **** ****** * *******
* *
60 #***##*##*#***#####*#*###*****#*###*#*#*##*#*##*#*##*****#
50 ##########################################################
40 ##########################################################
30 ##########################################################
20 ##########################################################
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
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 on a Cisco uBR10012 router:
Router# show processes cpu
CPU utilization for five seconds: 2%/0%; one minute: 2%; five minutes: 2%
PID Runtime(us)
Invoked
uSecs
5Sec
1Min
5Min TTY Process
1
8
471
16 0.00% 0.00% 0.00%
0 Chunk Manager
2
4
472
8 0.00% 0.00% 0.00%
0 Load Meter
3
0
1
0 0.00% 0.00% 0.00%
0 IPC 0x50000 Vers
4
0
10
0 0.00% 0.00% 0.00%
0 C10K Card Event
5
0
65
0 0.00% 0.00% 0.00%
0 Retransmission o
6
0
5
0 0.00% 0.00% 0.00%
0 IPC ISSU Dispatc
7
5112
472
10830 0.63% 0.18% 0.18%
0 Check heaps
8
0
1
0 0.00% 0.00% 0.00%
0 Pool Manager
9
0
2
0 0.00% 0.00% 0.00%
0 Timers
10
0
2
0 0.00% 0.00% 0.00%
0 Serial Backgroun
11
0
786
0 0.00% 0.00% 0.00%
0 WBCMTS process
12
0
1
0 0.00% 0.00% 0.00%
0 AAA_SERVER_DEADT
13
0
1
0 0.00% 0.00% 0.00%
0 Policy Manager
14
0
1
0 0.00% 0.00% 0.00%
0 Crash writer
15
0
1
0 0.00% 0.00% 0.00%
0 RO Notify Timers
16
0
1
0 0.00% 0.00% 0.00%
0 RMI RM Notify Wa
17
0
2364
0 0.00% 0.00% 0.00%
0 Facility Alarm
18
0
41
0 0.00% 0.00% 0.00%
0 IPC Dynamic Cach
The following is sample output from the show processes cpu command that shows an ARP probe process:
Router# show processes cpu | include ARP
17
38140
389690
97 0.00%
36
0
1
0 0.00%
40
0
1
0 0.00%
80
0
1
0 0.00%
114
0
1
0 0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0
0
0
0
0
ARP Input
IP ARP Probe
ATM ARP INPUT
RARP Input
FR ARP
Field
Description
one minutes
five minutess
PID
Process ID.
Runtime (us)
Invoked
Note
Field
Description
uSecs
5Sec
1Min
5Min
TTY
Process
Because platforms have a 4- to 8-microsecond clock resolution, run times are considered reliable only after
several invocations or a reasonable, measured run time.
The table below describes the significant fields shown in the display.
Table 150
Field
Description
Field
Description
1 minute
5 minutes
PID
Process ID.
5Sec
1Min
5Min
Process
Process name.
The following is partial sample output from the show processes cpucommand with the detailedkeyword
when a Software Modularity image is running:
Router# show processes cpu detailed
Total CPU utilization for 5 seconds: 99.6%; 1 minute: 99.3%; 5 minutes: 88.6%
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
1
0.0%
0.7%
0.7% kernel
8.900
1
0.4%
0.7%
11.4% [idle thread]
0 Ready
2m28s
2
0.0%
0.0%
0.0%
63 Receive
0.000
3
0.0%
0.0%
0.0%
10 Receive
0.000
4
0.0%
0.0%
0.1%
11 Receive
1.848
5
0.0%
0.0%
0.0%
63 Receive
0.000
.
.
.
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
8214
0.0%
0.0%
0.0% sysmgr.proc
0.216
1
0.0%
0.0%
0.0%
10 Receive
0.132
2
0.0%
0.0%
0.0%
10 Sigwaitin
0.000
3
0.0%
0.0%
0.0%
10 Receive
0.004
4
0.0%
0.0%
0.0%
10 Receive
0.000
5
0.0%
0.0%
0.0%
10 Receive
0.000
6
0.0%
0.0%
0.0%
10 Receive
0.004
7
0.0%
0.0%
0.0%
10 Receive
0.000
8
0.0%
0.0%
0.0%
10 Receive
0.000
9
0.0%
0.0%
0.0%
10 Receive
0.000
10
0.0%
0.0%
0.0%
10 Receive
0.000
11
0.0%
0.0%
0.0%
10 Receive
0.000
12
0.0%
0.0%
0.0%
10 Receive
0.000
13
0.0%
0.0%
0.0%
10 Receive
0.028
14
0.0%
0.0%
0.0%
10 Receive
0.040
15
0.0%
0.0%
0.0%
10 Receive
0.000
16
0.0%
0.0%
0.0%
10 Receive
0.000
17
0.0%
0.0%
0.0%
10 Receive
0.004
18
0.0%
0.0%
0.0%
10 Receive
0.000
19
0.0%
0.0%
0.0%
10 Receive
0.000
20
0.0%
0.0%
0.0%
10 Receive
0.000
21
0.0%
0.0%
0.0%
10 Receive
0.004
22
0.0%
0.0%
0.0%
10 Receive
0.000
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
8215
0.0%
0.0%
0.0% kosh.proc
0.044
1
0.0%
0.0%
0.0%
10 Reply
0.044
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
12290
0.0%
0.0%
0.0% chkptd.proc
0.080
1
0.0%
0.0%
0.0%
10 Receive
0.080
2
0.0%
0.0%
0.0%
10 Receive
0.000
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
12312
0.0%
0.0%
0.0% sysmgr.proc
0.112
1
0.0%
0.0%
0.0%
10 Receive
0.112
2
0.0%
0.0%
0.0%
10 Sigwaitin
0.000
PID/TID
5Sec
1Min
5Min Process
Prio STATE
CPU
12316
0.0%
0.0%
0.0% installer.proc
0.072
1
0.0%
0.0%
0.0%
10 Receive
0.000
3
0.0%
0.0%
0.0%
10 Nanosleep
0.000
4
0.0%
0.0%
0.0%
10 Sigwaitin
0.000
6
0.0%
0.0%
0.0%
10 Receive
0.000
Process sbin/ios-base, type IOS, PID = 12317
CPU utilization for five seconds: 12%/9%; one minute: 13%; five minutes: 10%
Task Runtime(us) Invoked uSecs
5Sec
1Min
5Min TTY Task Name
1
219
1503
145
0.00% 0.00% 0.00%
0 Hot Service Task
2
23680
42384
558
2.39% 6.72% 4.81%
0 Service Task
3
6104
11902
512
3.51% 1.99% 1.23%
0 Service Task
4
1720
5761
298
1.91% 0.90% 0.39%
0 Service Task
5
0
5
0
0.00% 0.00% 0.00%
0 Chunk Manager
6
0
1
0
0.00% 0.00% 0.00%
0 Connection Mgr
7
4
106
37
0.00% 0.00% 0.00%
0 Load Meter
8
6240
7376
845
0.23% 0.15% 0.55%
0 Exec
9
379
62
6112
0.00% 0.07% 0.04%
0 Check heaps
10
0
1
0
0.00% 0.00% 0.00%
0 Pool Manager
11
3
2
1500
0.00% 0.00% 0.00%
0 Timers
12
0
1
0
0.00% 0.00% 0.00%
0 AAA_SERVER_DEADT
13
0
2
0
0.00% 0.00% 0.00%
0 AAA high-capacit
14
307
517
593
0.00% 0.05% 0.03%
0 EnvMon
15
0
1
0
0.00% 0.00% 0.00%
0 OIR Handler
16
283
58
4879
0.00% 0.04% 0.02%
0 ARP Input
17
0
2
0
0.00% 0.00% 0.00%
0 Serial Backgroun
18
0
81
0
0.00% 0.00% 0.00%
0 ALARM_TRIGGER_SC
19
0
2
0
0.00% 0.00% 0.00%
0 DDR Timers
20
0
2
0
0.00% 0.00% 0.00%
0 Dialer event
21
4
2
2000
0.00% 0.00% 0.00%
0 Entity MIB API
22
0
54
0
0.00% 0.00% 0.00%
0 Compute SRP rate
23
0
9
0
0.00% 0.00% 0.00%
0 IPC Dynamic Cach
24
0
1
0
0.00% 0.00% 0.00%
0 IPC Zone Manager
25
0
1
0
0.00% 0.00% 0.00%
0 IPC Punt Process
26
4
513
7
0.00% 0.00% 0.00%
0 IPC Periodic Tim
27
11
513
21
0.00% 0.00% 0.00%
0 IPC Deferred Por
28
0
1
0
0.00% 0.00% 0.00%
0 IPC Seat Manager
29
83
1464
56
0.00% 0.00% 0.00%
0 EEM ED Syslog
.
.
.
The table below describes the significant fields shown in the display.
Table 151
Field
Description
1 minute
5 minutes
PID/TID
5Sec
1Min
Field
Description
5Min
Process
Process name.
Prio
STATE
CPU
type
Task
Runtime(us)
Invoked
uSecs
5Sec
1Min
5Min
TTY
Task Name
Task name.
The following is partial sample output from the show processes cpucommand with the detailedkeyword:
switch#show proc cpu detailed
Core 0: CPU utilization for five seconds: 0%; one minute: 6%; five minutes: 5%
Core 1: CPU utilization for five seconds: 2%; one minute: 17%; five minutes: 12%
PID
T C TID
Runtime(ms) Invoked
uSecs 5Sec
1Min 5Min TTY
Process
(%)
(%) (%)
1
L
935
596
156971 0.00 A 0.00 0.00 0
init
2
L
0
79
10405 0.00 A 0.00 0.00 0
kthreadd
3
L
13
2481
5573
0.00 A 0.00 0.00 0
migration/0
4
L
12
808
15237 0.00 A 0.00 0.00 0
ksoftirqd/0
5
L
8
1454
6157
0.00 A 0.00 0.00 0
migration/1
6
L
14
897
16341 0.00 A 0.00 0.00 0
ksoftirqd/1
7
L
31
1471
21661 0.00 A 0.00 0.00 0
events/0
8
L
33
1308
25496 0.00 A 0.00 0.00 0
events/1
9
L
5
637
9070
0.00 A 0.00 0.00 0
khelper
61
L
80
79
102031 0.00 A 0.00 0.00 0
kblockd/0
62
L
90
183
497142 0.00 A 0.00 0.00 0
kblockd/1
75
L
0
21
1238
0.00 A 0.00 0.00 0
khubd
78
L
0
23
652
0.00 A 0.00 0.00 0
kseriod
83
L
7
26
271115 0.00 A 0.00 0.00 0
kmmcd
120
L
0
25
320
0.00 A 0.00 0.00 0
pdflush
121
L
103
195
531687 0.00 A 0.00 0.00 0
pdflush
122
L
0
29
172
0.00 A 0.00 0.00 0
kswapd0
123
L
0
31
161
0.00 A 0.00 0.00 0
aio/0
124
L
0
33
121
0.00 A 0.00 0.00 0
aio/1
291
L
0
35
142
0.00 A 0.00 0.00 0
kpsmoused
--More--
The following is sample output from the show processes cpu history summarycommand:
Switch#show processes cpu history summary
History information for system:
222331111111111111111111111111111111111111111111111111111111
100
90
80
70
60
50
40
30
20
10
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per second (last 60 seconds)
* = maximum CPU%
# = average CPU%
333333333334333325333334333334333334333334333334333334333333
100
90
80
70
60
50
* *
40
30
* ** * **
*
**
*
**
20
# #
#*##*#*##*
*
*
*
10
*
#
##
##
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per minute (last 60 minutes)
* = maximum CPU%
# = average CPU%
655654555654554554555555555555555555655655555655554655655655555555565555
100
90
80
70
60
50**
40
30
20
10
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0
5
0
5
0
5
0
5
0
5
0
5
0
CPU% per hour (last 72 hours)
* = maximum CPU%
# = average CPU%
The following is sample output from the show processes cpu history detailedcommand:
Switch#show processes cpu history detailed
History information for core 0:
222331111111111111111111111111111111111111111111111111111111
100
90
80
70
60
50
40
30
20
10
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per second (last 60 seconds)
* = maximum CPU%
# = average CPU%
333333333334333325333334333334333334333334333334333334333333
100
90
80
70
60
*
50
40
30
20
** * ** *
*
*
10
* * * *
* * ** *
*
*
*
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per minute (last 60 minutes)
* = maximum CPU%
# = average CPU%
655654555654554554555555555555555555655655555655554655655655555555565555
100
90
80
70
60*
50
40
30 *
20
10
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0
5
0
5
0
5
0
5
0
5
0
5
0
CPU% per hour (last 72 hours)
* = maximum CPU%
# = average CPU%
History information for core 1:
222331111111111111111111111111111111111111111111111111111111
100
90
80
70
60
50
40
30
20
10
*****
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per second (last 60 seconds)
* = maximum CPU%
# = average CPU%
333333333334333325333334333334333334333334333334333334333333
100
*
90
*
80
70
60
50
40
**********
*
**
**
**
30
*
*
20
10*
*
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per minute (last 60 minutes)
* = maximum CPU%
# = average CPU%
655654555654554554555555555555555555655655555655554655655655555555565555
100*
90 *
80
70
60
50
40
30
20
10
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0
5
0
5
0
5
0
5
0
5
0
5
0
CPU% per hour (last 72 hours)
* = maximum CPU%
# = average CPU%
Switch#show proc cpu history table
CPU utilization for five seconds: 1%/0% at 01:14:44
PID
5Sec
Process
10319
6
iosd
CPU utilization for five seconds: 1%/0% at 01:14:49
PID
5Sec
Process
10319
6
iosd
CPU utilization for five seconds: 1%/0% at 01:14:54
PID
5Sec
Process
10319
6
iosd
CPU utilization for five seconds: 1%/0% at 01:14:59
PID
5Sec
Process
10319
6
iosd
Switch#
Field
Description
Core (#)
one minutes
five minutess
PID
Process ID.
Runtime (us)
Related Commands
Field
Description
Invoked
uSecs
5Sec
1Min
5Min
TTY
Process
Command
Description
show processes
Syntax Description
process
process-id
process-name
Command Default
If no process ID or process name is specified, detailed information is displayed about all processes.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(18)SXF4
Use the show processes detailed command to gather detailed information about the number of tasks
running, the process state, and other information about a process that is not displayed by the show
processes command.
On Cisco IOS XE images, show process detailed will also show process, thread and task details.
Examples
Example output varies between Cisco IOS software images and Cisco Catalyst 4500e Series Switches
running IOS XE software. The following sections show output examples for each image.
Cisco IOS Software
The following is sample output from the show processes detailedcommand for the process named
sysmgr.proc:
Router# show processes detailed sysmgr.proc
Job Id: 67
PID: 8210
Executable name: sysmgr.proc
Executable path: sbin/sysmgr.proc
Instance ID: 1
Args: -p
Respawn: ON
Respawn count: 1
Max. spawns per minute: 30
Last started: Mon Aug18 17:08:53 2003
Process state: Run
core: SHAREDMEM MAINMEM
Max. core: 0
Level: 39
PID
TID Stack pri state
Blked HR:MM:SS:MSEC FLAGS
NAME
8210
1
52K 10 Receive
1
0:00:00:0071 00000000 sysmgr.proc
8210
2
52K 10 Sigwaitinfo
0:00:00:0000 00000000 sysmgr.proc
8210
3
52K 10 Receive
8
0:00:00:0003 00000000 sysmgr.proc
8210
4
52K 10 Reply
1
0:00:00:0003 00000000 sysmgr.proc
8210
5
52K 10 Receive
1
0:00:00:0000 00000000 sysmgr.proc
8210
6
52K 10 Receive
1
0:00:00:0015 00000000 sysmgr.proc
8210
7
52K 10 Receive
1
0:00:00:0000 00000000 sysmgr.proc
8210
8
52K 10 Receive
1
0:00:00:0000 00000000 sysmgr.proc
----------------------------------------------------------------Job Id: 78
PID: 12308
Executable name: sysmgr.proc
Executable path: sbin/sysmgr.proc
Instance ID: 2
Args: -p
Respawn: ON
Respawn count: 1
Max. spawns per minute: 30
Last started: Mon Aug18 17:08:54 2003
Process state: Run
core: SHAREDMEM MAINMEM
Max. core: 0
Level: 40
PID
TID Stack pri state
Blked HR:MM:SS:MSEC FLAGS
NAME
12308 1
16K 10 Receive
1
0:00:00:0039 00000000 sysmgr.proc
12308 2
16K 10 Sigwaitinfo
0:00:00:0000 00000000 sysmgr.proc
-----------------------------------------------------------------
Resident Pages
: 953636
Resident Limit
: 4194303
Minor PageFaults
: 238050
Major PageFaults
: 1088
Cmdline arguments : -n 2048 -m 256 -l lanbase
Thread Listing:
PID
C
TID
Stack
Pri
TTY
10319
1
10319
84
20
0
10319
0
10873
84
30
0
10319
0
10874
84
20
0
Task Listing:
PID
QTy PC
Runtime(ms) Invoked
uSecs
1
Cwe 29764508 4
7
0
2
Csp 28101409 0
85
0
3
Hwe 26994556 0
1
0
4
Mwe 27835771 0
6
0
5
Mwe 27139064 0
1
0
6
Mwe 27138527 0
1
0
7
Lst 29780794 220
45
0
8
Cwe 29784274 0
9
0
9
Mst 28412237 0
2
0
10
Mwe 27212830 0
2
0
11
Mwe 28504055 32
22
0
12
Mwe 27808556 0
1
0
13
Mwe 27917322 12
91
0
14
Mwe 27917399 0
2
0
15
Mwe 28318114 0
2
0
16
Mwe 27927986 4
94
0
17
Cwe 27917853 0
227
0
18
Mwe 28152849 8
14
0
19
Lwe 28315806 0
1
0
20
Lwe 28397268 0
1
0
21
Mwe 28394584 0
2
0
22
Mwe 28495535 0
1
0
23
Lwe 28553141 0
7
0
24
Mwe 28793021 0
1
0
--More--
NAME
iosd
iosd
iosd
Stacks
504/35000
408/32000
328/35000
7816/35000
328/35000
328/35000
424/35000
520/35000
456/35000
472/35000
3176/35000
344/35000
552/53000
584/53000
1384/35000
4904/35000
536/35000
488/35000
312/35000
280/35000
456/35000
392/41000
696/35000
296/35000
TTY
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Process
Chunk Manager
Load Meter
Deferred Events
SpanTree Helper
Retransmission of I
IPC ISSU Receive Pr
Check heaps
Pool Manager
Timers
Serial Background
RF Slave Main Threa
ifIndex Receive Pro
IOSD ipc task
IOSD chasfs task
cpf_msg_holdq_proce
IOSd System Config
IOSD heartbeat proc
ARP Input
CEF MIB API
AAA_SERVER_DEADTIME
AAA high-capacity c
Policy Manager
Entity MIB API
IFS Agent Manager
The table below describes the significant fields shown in the display.
Table 153
Field
Description
Job Id
Job identifier.
PID
Process ID.
Executable name
Process name.
Executable path
Instance ID
Instance number.
Args
Respawn
Respawn count
Last started
Related Commands
Field
Description
Process state
Core
Max. core
Level
TID
Thread ID.
Stack
pri
Process priority.
state
Blked
HR:MM:SS:MSEC
FLAGS
NAME
Process name.
Command
Description
show processes
Command Modes
Command History
Examples
Privileged EXEC
Release
Modification
12.4(2)T
The following is sample output from the show processes interrupt mask buffer command. The output
displays stack trace and relevant information about the places where interrupts have been masked more
than the configured threshold time:
Router# show processes interrupt mask buffer
Allowable interrupt mask time : 50 micro seconds
Allowable number of half pipeline ticks for this platform : 5000
Buffer Size
: 50 entries
NETS Disable
: 3
TTY Disable
: 4
ALL Disable
: 4
emt_call
: 11
disable_interrupts : 12
PID
Level Time Spent(us) Count
Stack Trace
3
11
360
1
0x608C3C14 0x60894748
0x6089437C 0x608943AC 0x609CEC88 0x609CECFC 0x609C8524
3
11
322
1
0x608C3C14 0x608943BC
0x609CEC88 0x609CECFC 0x609C8524 0x60867C28 0x607C70B0
3
4
147
1
0x6078AED4 0x6078BE94
0x6078C750 0x6078C8D4 0x607E27F0 0x607E27C0 0x607E50B0
Related Commands
Command
Description
Command
Description
Syntax Description
Command Modes
Command History
Examples
detail
pid
Privileged EXEC
Release
Modification
12.4(2)T
The following is sample output from the show processes interrupt mask detail command. the output
displays information about the total amount of time and number of times interrupts have been masked by
all processes:
Router# show processes interrupt mask detail
PID Time Spent(us)
Count
Process Name
2
6388
1791
Load Meter
3
7957
16831
Exec
5
6710
2813
Check heaps
The following is sample output from the show processes interrupt mask detail command with the process
ID specified. The output displays the total time (accumulative), number of times interrupts have been
masked by a specific process:
Router# show processes interrupt mask detail 2
Process ID
: 2
Process Name : Load Meter
Total Interrupt Masked Time : 6586 (us)
Total Interrupt Masked Count : 1845
Related Commands
Command
Description
Syntax Description
sorted
allocated
getbufs
holding
process-name
: instance-id
process-id
alloc-summary
sorted
start
size
caller
Command Default
Command Default
The system memory followed by a one-line summary of memory information about each IOS XE or
Software Modularity process is displayed.
Command Modes
Command History
Release
Modification
10.0
12.0(23)S
12.2(13)
12.2(13)S
12.2(13)T
Release
Modification
12.0(28)S
12.2(22)S
12.3(7)T
12.0(30)S
12.2(28)S
12.3(11)T
12.2(18)SXF4
12.2(33)SRA
Usage Guidelines
The show processes memory command and the show processes memory sorted command displays a
summary of total, used, and free memory, followed by a list of processes and their memory impact.
If the standard show processes memory process-id command is used, processes are sorted by their PID. If
the show processes memory sorted command is used, the default sorting is by the Holding value.
Output Prior to Releases 12.3(7)T, 12.2(22)S, and 12.0(28)S
The first line (header line) of the show processes memory[sorted] command listed Total memory, Used
memory, and Free memory values.
Output in Releases 12.3(7)T, 12.3(8)T, and 12.2(22)S Through 12.2(27)S2, 12.0(28)S, and 12.0(29)S
In Releases 12.3(7)T, 12.2(22)S, and 12.0(28)S, the Memory Thresholding feature was introduced. This
feature affected the header line and the Holding column of the show processes memory command as
described in this section.
The value for Total in the show processes memory commandand the values listed in the Holding column
showed the total (cumulative) value for the processor memory pools and the alternate memory pool*
(typically, the I/O memory pool). However, the show processes memory sorted version of this command,
and other commands, such as the show memory summary command, did not include the alternate memory
pool in the totals; that is, these commands showed the total value for the Processor memory pool only. This
caused an observed mismatch of memory totals between commands.
If you are using these releases, use the output of the show memory summary command to determine the
individual amounts of Total and Free memory for the Processor memory pool and the I/O memory pool.
Output in Releases 12.3(11)T, 12.2(28)S, 12.0(30)S, and Later Releases
Beginning in Releases 12.3(11)T, 12.2(28)S, and 12.0(30)S, the summary information (first output lines)
for the show processes memory command is separated by memory pool. For example, there are now
individual lines for Total Process Memory, Total I/O Memory, and Total PCI Memory. In these releases or
later releases, your Total Process Memory should match the total process memory shown for other
commands, such as the show memory summarycommand.
About Alternate Memory Pools
An alternate memory pool is a memory pool that can be used as an alternative to allocate memory when
the target (main) memory pool has been filled. For example, many platforms have a memory type called
Fast that is limited to a small size (because the memory media used for Fast memory is expensive). You
can prevent memory allocations from failing once the available Fast memory has been used up, by
configuring the normal Processor memory as an alternative memory pool for the Fast memory pool.
Cisco IOS XE Software and Software Modularity
Use the show processes memory command without any arguments and keywords to display the system
memory followed by a one-line summary of memory information about each modular Cisco IOS process.
Use the detailed keyword with this command to display detailed memory information about all processes.
Other arguments and keywords are used to display Cisco IOS Software Modularity process memory
information for a specified process name or process ID.
On Cisco IOS XE images only, the detailed keyword will also show Cisco IOS task memory details.
Examples
Example output varies between Cisco IOS software releases. To see the appropriate output, choose one of
the following sections:
show processes memory Command for Cisco IOS 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
Processor Pool Total:
25954228 Used:
8368640 Free:
17585588
PID TTY Allocated
Freed
Holding
Getbufs
Retbufs Process
0
0
8629528
689900
6751716
0
0 *Init*
0
0
24048
12928
24048
0
0 *Sched*
0
0
260
328
68
350080
0 *Dead*
1
0
0
0
12928
0
0 Chunk Manager
2
0
192
192
6928
0
0 Load Meter
3
0
214664
304
227288
0
0 Exec
4
0
0
0
12928
0
0 Check heaps
5
0
0
0
12928
0
0 Pool Manager
6
0
192
192
12928
0
0 Timers
7
0
192
192
12928
0
0 Serial Backgroun
8
0
192
192
12928
0
0 AAA high-capacit
9
0
0
0
24928
0
0 Policy Manager
10
0
0
0
12928
0
0 ARP Input
11
0
192
192
12928
0
0 DDR Timers
12
0
0
0
12928
0
0 Entity MIB API
13
0
0
0
12928
0
0 MPLS HC Counter
14
0
0
0
12928
0
0 SERIAL A'detect
.
.
.
78
0
0
0
12992
0
0 DHCPD Timer
79
0
160
0
13088
0
0 DHCPD Database
8329440 Total
The table below describes the significant fields shown in the display.
Table 154
Field
Description
Used
Free
PID
Process ID.
TTY
Allocated
Freed
Holding
Field
Description
Getbufs
Retbufs
Process
Process name.
*Init*
*Sched*
*Dead*
<value> Total
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
Processor Pool Total:
PID TTY Allocated
0
0
8629528
3
0
217304
53
0
109248
56
0
0
19
0
39048
42
0
0
58
0
192
43
0
192
49
0
0
48
0
0
17
0
192
9
0
0
40
0
0
29
0
0
44
0
192
32
0
192
34
0
0
41
0
192
16
0
192
35
0
0
--More--
25954228 Used:
8371280 Free:
17582948
Freed
Holding
Getbufs
Retbufs Process
689900
6751716
0
0 *Init*
304
229928
0
0 Exec
192
96064
0
0 DHCPD Receive
0
32928
0
0 COPS
0
25192
0
0 Net Background
0
24960
0
0 L2X Data Daemon
192
24928
0
0 X.25 Background
192
24928
0
0 PPP IP Route
0
24928
0
0 TCP Protocols
0
24928
0
0 TCP Timer
192
24928
0
0 XML Proxy Client
0
24928
0
0 Policy Manager
0
24928
0
0 L2X SSS manager
0
24928
0
0 IP Input
192
24928
0
0 PPP IPCP
192
24928
0
0 PPP Hooks
0
24928
0
0 SSS Manager
192
24928
0
0 L2TP mgmt daemon
192
24928
0
0 Dialer event
0
24928
0
0 SSS Test Client
The following is sample output from the show processes memory command when a process ID (processid) is specified:
Router# show processes memory 1
Process ID: 1
Process Name: Chunk Manager
Total Memory Held: 8428 bytes
Processor memory holding = 8428 bytes
pc = 0x60790654, size =
6044, count
pc = 0x607A5084, size =
1544, count
pc = 0x6076DBC4, size =
652, count
pc = 0x6076FF18, size =
188, count
I/O memory holding = 0 bytes
Router# show processes memory 2
Process ID: 2
=
=
=
=
1
1
1
1
1
1
1
show processes memory Command for Cisco IOS 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 memorycommand before the changes to
the summary information were made. Note that the Total in the show processes summary command
output 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
summarycommand. 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
Head
Total(b)
Used(b)
Free(b)
Lowest(b)
Processor
61E379A0
27035232
8089056
18946176
17964108
I/O
3800000
8388608
2815088
5573520
5561520
5573472
.
.
.
Router# show processes memory
Total: 35423840
, Used: 10904192, Free: 24519648
PID TTY Allocated
Freed
Holding
0
0
14548868
3004980
9946092
0
0
12732
567448
12732
.
.
.
Router# show processes memory sorted
Total: 27035232
, Used: 8089188, Free: 18946044
PID TTY Allocated
Freed
Holding
0
0
14548868
3004980
9946092
64
0
76436
3084
74768
.
.
.
Router# show version | include IOS
Largest(b)
17963664
Getbufs
0
0
Retbufs Process
0 *Init*
0 *Sched*
Getbufs
0
0
Retbufs Process
0 *Init*
0 CEF process
PID TTY
0
0
13
0
48
0
18
0
.
.
.
Allocated
6796228
39056
0
0
Freed
627336
0
0
0
Holding
5325956
25264
24896
24896
Getbufs
0
0
0
0
Retbufs
0
0
0
0
Process
*Init*
Net Background
L2X SSS manager
IP Input
The table below describes the significant fields shown in the display.
Table 155
Field
Description
total
used
Field
Description
free
PID
Process ID.
Text
Data
Stack
Dynamic
Total
Process
Process name.
The following example shows the output of the show processes memory detailedcommand wherein the
process (ios-base) holds sufficient memory to process a request of the Cisco IOS tasks without having to
request more memory from the system. So although the amount of memory of the Cisco IOS tasks
increased, the ios-base process does not consume more system memory.
Router# show processes memory detailed 16424 sorted holding
System Memory : 2097152K total, 1097777K used, 999375K free, 0K kernel reserved
Lowest(b)
: 1017212928
Process sbin/ios-base, type IOS, PID = 16424
248904K total, 0K text, 0K data, 168K stack, 248736K dynamic
Heap : 385874960 total, 261213896 used, 124661064 free
Task TTY Allocated
Freed
Holding
Getbufs
Retbufs TaskName
0
0 156853816
11168 156365472
0
0 *Init*
38
0
65671128
3320184
62248368
0
0 PF_Init Process
661
0
73106800
38231816
33093704
0
0 PIM Process
487
0 2656186248 3806507384
33039576
0
0 cmfib
652
0
56256064
19166160
27087872
0
0 MFIB_mrib_read
4
0
91088216
68828800
13093720
0
0 Service Task
629
0
2059320
132840
1927392
0
0 Const2 IPv6 Pro
49
0 2155730560 2153990528
1741536
0
9579588 DiagCard1/-1
0
0 2510481432 1396998880
1463056
2804860
23260 *Dead*
444
0
7333952
5940064
1410992
0
0 FM core
411
0
12865536
7934952
1396544
0
0 CMET MGR
310
0 113849160 121164584
1284240
0
0 Exec
The following is sample output from the show processes memorycommand 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
16568K total, 16K text, 8K data, 64K stack, 16480K dynamic
Memory Summary for TaskID = 1
Holding = 10248
PC
Size Count
0x7322FC74
9192
1
0x73236538
640
1
0x73231E8C
256
1
0x74175060
160
1
The table below describes the significant fields shown in the display that are different from the table above.
Table 156
Field
Description
type
Task ID.
Holding
PC
Size
Count
The following is sample output from the show processes memorycommand 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
Process sbin/sysmgr.proc, type POSIX, PID = 12308
404K total, 100K text, 144K data, 16K stack, 144K dynamic
81920 heapsize, 68620 allocated, 8896 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
Address
Size
0x0806FFF0 0x00000010
0x080714A8 0x00000058
0x08073E18 0x00000098
0x08073FE8 0x00000018
0x08076FA0 0x00000328
0x080774B0 0x00000B50
0x0807FFB8 0x00000048
0x08080028 0x00003FD8
The table below describes the significant fields shown in the display.
Table 157
Field
Description
heapsize
allocated
free
Address
Usize
Size
Caller
RSS
1648
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
456
0
0
0
1172
532
532
992
Total
3648
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2188
0
0
0
3180
1788
1788
4596
Process
init
kthreadd
migration/0
ksoftirqd/0
migration/1
ksoftirqd/1
events/0
events/1
khelper
kblockd/0
kblockd/1
khubd
kseriod
kmmcd
pdflush
pdflush
kswapd0
aio/0
aio/1
kpsmoused
rpciod/0
rpciod/1
udevd
loop1
loop2
loop3
dbus-daemon
portmap
portmap
sshd
2602
196
2606
196
3757
76
3758
76
--More--
320
320
160
160
84
84
84
84
132
132
132
132
752
748
532
532
2964
2964
1788
1788
xinetd
xinetd
vsi work/0
vsi work/1
The following is sample output from the show processes memory detailedcommand:
Switch#show proc memory detailed
System memory
Lowest(b)
PID
Text
1
252
354
92
2203
424
2539
76
2545
76
2588
232
2602
196
2606
196
3757
76
3758
76
3891
848
3895
72
4453
848
4465
848
4596
148
TaskID TTY
1
0
2
0
3
0
4
0
5
0
6
0
7
0
8
0
9
0
10
0
--More--
The following is sample output from the show processes memory detailedcommand specifying the Iosd
process:
Switch#show proc memory detailed process iosd
Processor
I/O
PID TTY
0
0
0
0
0
0
1
0
2
0
3
0
4
0
5
0
6
0
7
0
8
0
9
0
10
0
--More--
Pool Total:
Pool Total:
Allocated
226577984
0
2568488
327920
184
0
17840
0
0
0
210880
184
184
The following is sample output from the show processes memory sortedcommand:
Switch#show proc memory sorted
System memory
Lowest(b)
PID
Text
10319
67716
4888
1132
4884
620
7635
144
9374
1048
10335
1676
4852
208
7566
168
7585
268
4880
308
4894
100
7410
68
10329
160
4968
104
5047
88
4870
80
4856
200
--More--
200108
690480
181696
298308
257544
208996
249336
167656
135080
232936
233708
142384
158828
165604
157452
132816
84
84
84
84
84
84
84
84
84
84
84
84
84
84
84
84
4076
5328
7464
1128
1252
1848
1408
1616
968
1144
1172
832
1052
700
728
688
26772
18564
16660
11488
11044
10812
8560
8432
8200
8072
7928
7144
7080
6196
6088
5872
275408
728076
202620
328992
293848
237632
273668
185556
153944
252748
253840
228360
178184
181184
172244
147940
ffm
eicored
cli_agent
licensed
licenseagentd
ha_mgr
installer
snmp_subagent
os_info_p
plogd
dtmgr
cpumemd
iifd
pdsd
sysmgr
oscore_p
The table below describes the significant fields shown in the display.
Table 158
Field
Description
Used
Free
PID
Process ID.
TTY
Allocated
Freed
Holding
Getbufs
Retbufs
Process
Process name.
*Init*
*Sched*
Related Commands
Field
Description
*Dead*
<value> Total
Command
Description
show memory
show processes
show protocols
To display the configured protocols, use the show protocols command in user EXEC or privileged EXEC
mode.
show protocols [interface-name interface-number]
Syntax Description
interface-name
voaBypassIn -VOA-Bypass-In
interface
voaBypassOut -VOA-Bypass-Out
interface
voaFilterIn -VOA-Filter-In
interface
voaFilterOut -VOA-Filter-Out
interface
voaIn --VOA-In
interface
voaOut --VOA-Out
interface
Command Modes
Command History
Release
Modification
10.0
12.0(3)T
12.2(33)SRA
(Optional) Interface
number.
Usage Guidelines
The show protocols command shows the global and interface-specific status of any configured Level 3
protocol.
Examples
The following is sample output from the show protocols command. The field names are self-explanatory.
Router# show protocols
Global values:
Internet Protocol routing is enabled
FastEthernet0/0 is up, line protocol is up
Internet address is 10.4.9.14/24
vmi1 is down, line protocol is down
FastEthernet0/1 is up, line protocol is up
Internet address is 10.4.8.14/24
ATM2/0 is administratively down, line protocol is down
ATM2/0.1 is administratively down, line protocol is down
ATM2/0.2 is administratively down, line protocol is down
ATM2/0.200 is administratively down, line protocol is down
Ethernet3/0 is administratively down, line protocol is down
Ethernet3/0.1 is administratively down, line protocol is down
Ethernet3/1 is administratively down, line protocol is down
Ethernet3/2 is administratively down, line protocol is down
Ethernet3/3 is administratively down, line protocol is down
ATM6/0 is administratively down, line protocol is down
SSLVPN-VIF0 is up, line protocol is up
Interface is unnumbered. Using address of SSLVPN-VIF0 (0.0.0.0)
Virtual-Access1 is down, line protocol is down
Virtual-Template1 is down, line protocol is down
Virtual-Access2 is up, line protocol is up
Port-channel5 is down, line protocol is down
Port-channel5.1 is down, line protocol is down
Port-channel15 is down, line protocol is down
Virtual-Template100 is down, line protocol is down
Interface is unnumbered. Using address of vmi1 (0.0.0.0)
Dialer3 is up, line protocol is up
For more information on the parameters or protocols shown in this sample output, see the Cisco IOS IP
Addressing Services Configuration Guide and the Cisco IOS IP Routing Protocols Configuration Guide.
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]
Syntax Description
address hex-address
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(13)
12.0(23)S
12.2(25)S
12.2(33)SRA
12.2(33)SRE
This command can be useful for troubleshooting system bus errors. The system encounters a bus error
when the processor tries to access a memory location that either does not exist (a software error) or does
not respond properly (a hardware problem).
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 caused 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.
If the address reported by the bus error does not fall within the ranges displayed in the show region output,
this error means that the router was trying to access an address that is not valid, which 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".
Transient Memory Allocation
The Transient Memory Allocation feature is enabled on platforms like the Cisco 7200 series router and the
Cisco 10000 series router. This feature allocates all transient memory in a separate memory address space
(separate region), so that there is no interleaving of static and transient memory blocks. Hence, the output
of the show region command will have heap region memory size in chunks of 16 MB.
Examples
End
0x7AFFFFA7
Size(b)
67108864
268435456
268435456
469762048
33560336
16016800
4038176
2511044
16777216
16777216
201326592
201326592
Class
Iomem
Local
Local
Local
IText
IData
IBss
Local
Local
Local
Local
Local
Media
R/W
R/W
R/W
R/W
R/O
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Name
iomem
extended_2
extended_1
main
main:text
main:data
main:bss
main:saved-data
main:heap
main:heap
main:(main_k0)
main:(main_k1)
Size(b)
380001916
Class
Local
Media
R/W
Name
heap
The following table describes the significant fields shown in the display.
Table 159
Field
Description
Start
End
Size(b)
Class
Media
Type of the region media. Read-only (R/O), readwrite (R/W), and so on.
Related Commands
Field
Description
Name
Iomem
Local
Local memory.
IText
IData
IBss
R/W
R/O
Read-only memory.
Command
Description
show context
show memory
show version
show registry
To display the function registry information when Cisco IOS or Cisco IOS Software Modularity images are
running, use the show registrycommand in user EXEC or privileged EXEC mode.
Cisco IOS Software
show registry [registry-name [registry-number]] [brief | statistics]
Cisco IOS Software Modularity
show registry [name [registry-name [registry-number]]] [brief [name [registry-name [registrynumber]]] | preemptions | rpcp status | statistics [brief] [name [registry-name [registry-number]]]
[remote]] [process {process-name | process-id}]
Syntax Description
registry-number
brief
statistics
registry-name
registry-number
brief
preemptions
rpcp status
statistics
remote
process
process-name
Command Default
Command Modes
Command History
Examples
Release
Modification
11.1
12.2(18)SXF4
12.2(33)SRA
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software
images. To view the appropriate output, choose one of the following sections:
.
Registry 25: ATM routing Registry
Service 25/0:
The following table describes the significant fields shown in the display.
Table 160
Field
Description
Registry objects
bytes
Registry
returnd
returnd
returnd
returnd
returno
returno
returno
The following table describes the significant fields shown in the display.
Table 161
Field
Description
Registry information
services
global bytes
heap bytes
show reload
To display the reload status on the router, use the show reload command in EXEC mode.
show reload
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
12.2(33)SRA
Usage Guidelines
You can use the show reload command to display a pending software reload. To cancel the reload, use the
reload cancel privileged EXEC command.
Examples
The following sample output from the show reload command shows that a reload is schedule for 12:00
a.m. (midnight) on Saturday, April 20:
Router# show reload
Reload scheduled for 00:00:00 PDT Sat April 20 (in 12 hours and 12 minutes)
Router#
Related Commands
Command
Description
reload
Syntax Description
Command Modes
Command History
description
statistics
Release
Modification
15.0(1)M
Usage Guidelines
Use the show resource-pool queuecommand to display the resource pool and queue information on the
router.
Examples
The following is sample output from the show resource-pool queue descriptioncommand. The field
descriptions are self-explanatory.
Router# show resource-pool description
Resource-management call state description
State Description
--------------------------- ----------RM_DNIS_AUTHOR : Waiting for DNIS author
RM_DNIS_AUTH_SUCCEEDED : Waiting for resource alloc
RM_DNIS_RES_ALLOCATED : Call established
RM_DNIS_REQ_IDLE : Disc while in RM_DNIS_AUTHOR/RM_DNIS_AUTH_SUCCEEDED
/RM_DNIS_REQ_IDLE_AUTHOR
RM_DNIS_REQ_IDLE_AUTHOR : New call while in RM_DNIS_REQ_IDLE
RM_RPM_RES_AUTHOR : Waiting for RPM author
RM_RPM_RES_ALLOCATING : Waiting for resource alloc
RM_RPM_RES_ALLOCATED : RPM call established
RM_RPM_AUTH_REQ_IDLE : Disc while in RM_RPM_RES_AUTHOR
/RM_RPM_AUTH_REQ_IDLE_AUTHOR
RM_RPM_RES_REQ_IDLE : Disc while in RM_RPM_RES_ALLOCATING
/RM_RPM_RES_REQ_IDLE_AUTHOR
RM_RPM_AUTH_REQ_IDLE_AUTHOR: New call while in RM_RPM_AUTH_REQ_IDLE
RM_RPM_RES_REQ_IDLE_AUTHOR : New call while in RM_RPM_RES_REQ_IDLE
RM_RPM_DISCONNECTING : RPM initiates disconnect and is waiting for ack
The following is sample output from the show resource-pool queue statisticscommand:
Router# show resource-pool statistics
Resource-management event queue information (queue depth 0)
Event In queue Total
--------------------------- ---------- ---------DIALER_INCALL : 0 0
DIALER_DISCON : 0 0
GUARDTIMER_EXPIRY_EVENT : 0 0
RM_DNIS_AUTHOR_SUCCESS : 0 0
RM_DNIS_AUTHOR_FAIL : 0 0
RM_DNIS_RES_ALLOC_SUCCESS : 0 0
RM_DNIS_RES_ALLOC_FAIL : 0 0
RM_DNIS_RPM_REQUEST : 0 0
RM_RPM_RES_AUTHOR_SUCCESS : 0 0
RM_RPM_RES_AUTHOR_FAIL : 0 0
RM_RPM_RES_ALLOC_SUCCESS : 0 0
RM_RPM_RES_ALLOC_FAIL : 0 0
RM_RPM_DISC_ACK : 0 0
--------------------------- ---------- ---------SUM : 0 0
Resource-management call information (0 active calls)
State Active Total
--------------------------- ---------- ---------RM_DNIS_AUTHOR : 0 0
RM_DNIS_AUTH_SUCCEEDED : 0 0
RM_DNIS_RES_ALLOCATED : 0 0
RM_DNIS_REQ_IDLE : 0 0
RM_DNIS_REQ_IDLE_AUTHOR : 0 0
RM_RPM_RES_AUTHOR : 0 0
RM_RPM_RES_ALLOCATING : 0 0
RM_RPM_RES_ALLOCATED : 0 0
RM_RPM_AUTH_REQ_IDLE : 0 0
RM_RPM_RES_REQ_IDLE : 0 0
RM_RPM_AUTH_REQ_IDLE_AUTHOR: 0 0
RM_RPM_RES_REQ_IDLE_AUTHOR : 0 0
RM_RPM_DISCONNECTING : 0 0
RM_RPM_DISCONNECTING_AUTHOR: 0 0
--------------------------- ---------- ---------SUM : 0 0
00:03:34 since last clear command
Other resource-management info:
Active Processes 4
Throttle limit 4 (0 calls rejected)
Event queue depth 0 (peak 0)
Pending calls 0 (peak 0)
Buffer queue depth 648 (low watermark 648)
show rhosts
To display information about current remote hosts, use the show rhostscommand in privileged EXEC
mode.
show rhosts
Syntax Description
Command Modes
Command History
Examples
Release
Modification
12.4(22)T
12.2(33)SRC
12.2(33)SXI
Remote user
tcp-scale-mcp2
tcp-scale-3
The following table describes the significant fields shown in the display.
Table 162
Field
Description
Local user
Related Commands
Field
Description
Host/Access list
Remote user
Command
Description
ip rcmd remote-host
show rom-monitor
To show both the read-only and the upgrade ROM monitor (ROMMON) image versions and also the
ROMMON image running on the Cisco 7200 VXR or Cisco 7301 router, use the show rommonitorcommand in user EXEC, privileged EXEC, or diagnostic mode.
Supported Platforms Other than the Cisco ASR1000 Series Routers
show rom-monitor
Cisco ASR 1000 Series Routers
show rom-monitor slot
Syntax Description
slot
Command Modes
Command History
Release
Modification
12.0(28)S
12.3(9)
12.3(8)T
Release
Modification
12.2SX
15.0(1)M
Usage Guidelines
Note
Examples
Use the show rom-monitor command when the router boots a Cisco IOS software iamge. In this case, the
device prompt will be something like Router>. Use the showmon command when the device boot to Rom
Monitor mode instead of booting a Cisco IOS image. In this case, the device prompt will be something like
rommon n > where "n" is a number.
On Cisco 1800 series routers, the show rom-monitor command does not show the version of the
upgradable ROMMON. To view the version of the upgradable ROMMON, you may need to reload the
router while using the upgradable ROMMON image. If you are using the read-only ROMMON, then the
upgradable ROMMON disappears. You need to run the upgrade rom-monitor file command for the
upgradable ROMMON. Otherwise, the upgrade rom-monitor preference upgrade command is rejected
with the message No Upgrade ROMMON present, cannot select it. During ROMMON bootup, if you are
running upgradable ROMMON, then the ROMMON first displays the read-only ROMMON message,
Running new upgrade for first time. This message is followed by the upgradable ROMMON message.
The following sample output from the show rom-monitor command, applicable to both the Cisco 7200
VXR and Cisco 7301 routers, displays both the 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.
The following is sample output from the show rom-monitor command in on Cisco 1800 series
routers. To view the version of the upgradable ROMMON, you may need to reload the router
while using the upgradable ROMMON image.
Router# show rom-monitor
ReadOnly ROMMON version:
System Bootstrap, Version 12.3(8r)YH3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2005 by cisco Systems, Inc.
Upgrade ROMMON version is not visible due to recent license activity,
such as license installation, removal, or the use of evaluation license
Reload is required to show the upgrade ROMMON version
Currently running ROMMON from Upgrade region
ROMMON from Upgrade region is selected for next boot
Router# reload
Proceed with reload? [confirm]
*Apr 13 18:44:08.583: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload
Command.
System Bootstrap, Version 12.3(8r)YH3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2005 by cisco Systems, Inc.
Running new upgrade for first time
System Bootstrap, Version 12.3(8r)YH13, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2008 by cisco Systems, Inc.
C1800 platform with 262144 Kbytes of main memory with parity disabled
Upgrade ROMMON initialized
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.
Syntax Description
Command Modes
Command History
Usage Guidelines
num
sp
rp
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
When you enter the show rom-monitor slot command, the output displays the following:
Region region1 and region2--Displays the status of the ROMMON image and the order of preference
from which the region1 or region2 images should be booted. The ROMMON image status values are
as follows:
First run--Indicates that a check of the new image is being run.
Invalid--Indicates that the new image has been checked and the upgrade process has started.
Approved--Indicates that the ROMMON field upgrade process has completed.
Currently running--This field displays the currently running image and the region.
The sp or rp keyword is required only if a supervisor engine is installed in the specified slot.
Examples
Related Commands
Command
Description
upgrade rom-monitor
Syntax Description
Command Modes
Command History
Examples
name
Release
Modification
12.2(18)SX
The following is output from the show running identity policy command:
Router# show running identity policy
Building configuration...
Current configuration:
identity policy p1
access-group some-acl
identity policy p2
access-group another-acl
redirect url http://www.foo.com/bar.html match redirect-acl
end
Related Commands
Command
Description
show running-configuration
Syntax Description
Command Modes
Command History
Examples
default
dot1x
eapoudp
Release
Modification
12.2(18)SX
Related Commands
Command
Description
show running-configuration
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 privileged EXEC mode.
show running-config [options]
Syntax Description
options
Command Default
The default syntax, show running-config, displays the contents of the running configuration file, except
commands configured using the default parameters.
Command Modes
Command History
Release
Modification
11.0
12.0
12.0(1)T
12.2(4)T
12.3(8)T
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SXH
12.2(31)SB2
12.2(33)SRC
12.2(33)SB
12.4(24)T
15.0(1)M
12.2(33)SXI
The show running-config command is technically a command alias (substitute or replacement syntax) of
the more system:running-config command. Although the use of more commands is recommended
(because of their uniform structure across platforms and their expandable syntax), the show runningconfig command remains enabled to accommodate its widespread use, and to allow typing shortcuts such
as show run.
The show running-config interface command is useful when there are multiple interfaces and you want to
look at the configuration of a specific interface.
The linenum keyword causes line numbers to be displayed in the output. This option is useful for
identifying a particular portion of a very large configuration.
You can enter additional output modifiers in the command syntax by including a pipe character (|) after the
optional keyword. For example, show running-config interface serial 2/1 linenum | begin 3. To display
the output modifiers that are available for a keyword, enter | ? after the keyword. Depending on the
platform you are using, the keywords and the arguments for the options argument may vary.
Prior to Cisco IOS Release 12.2(33)SXH, the show running-configcommand output omitted configuration
commands set with default values. Effective with Cisco IOS Release 12.2(33)SXH, the show runningconfig all command displays complete configuration information, including the default settings and values.
For example, if the Cisco Discovery Protocol (abbreviated as CDP in the output) hold-time value is set to
its default of 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 allcommands is the same; that is, the configured
parameter is displayed.
Note
In Cisco IOS Release 12.2(33)SXH, the allkeyword expands the output to include some of the commands
that are configured with default values. In subsequent Cisco IOS releases, additional configuration
commands that are configured with default values will be added to the output of the show running-config
allcommand.
Effective with Cisco IOS Release 12.2(33)SXI, the show running-config command displays ACL
information. To exclude ACL information from the output, use the show running | section exclude ip
access | access listcommand.
Cisco 7600 Series Router
In some cases, you might see a difference in the duplex mode that is displayed between the show
interfaces command and the show running-config command. The duplex mode that is displayed in the
show interfaces command is the actual duplex mode that the interface is running. The show interfaces
command displays the operating mode of an interface, and the show running-config command displays the
configured mode of the interface.
The show running-config command output for an interface might display the duplex mode but no
configuration for the speed. This output indicates that the interface speed is configured as auto and that the
duplex mode that is displayed becomes the operational setting once the speed is configured to something
other than auto. With this configuration, it is possible that the operating duplex mode for that interface does
not match the duplex mode that is displayed with the show running-config command.
Examples
The following example shows the configuration for serial interface 1. The fields are self-explanatory.
Router# show running-config interface serial 1
Building configuration...
Current configuration:
!
interface Serial1
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
end
The following example shows the configuration for Ethernet interface 0/0. Line numbers are displayed in
the output. The fields are self-explanatory.
Router# show running-config interface ethernet 0/0 linenum
Building configuration...
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
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. The fields are self-explanatory.
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. The fields are self-explanatory.
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
!
ip subnet-zero
!
ip multicast-routing
ip dvmrp route-limit 20000
ip cef
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 averagecommand
indicates that the 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 ATM
adaptation layer 5 (AAL5) service. The fields are self-explanatory
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
!
The following is sample output from the show running-config class-map command. The fields in the
display are self-explanatory.
Router# show running-config class-map
Building configuration...
Current configuration : 2910 bytes
!
class-map type stack match-all ip_tcp_stack
match field IP protocol eq 0x6 next TCP
class-map type access-control match-all my
match field UDP dest-port eq 1111
match encrypted
filter-version 0.1, Dummy Filter 2
filter-id
123
filter-hash
DE0EB7D3C4AFDD990038174A472E4789
algorithm
aes256cbc
cipherkey
realm-cisco.sym
ciphervalue
#
oeahb4L6JK+XuC0q8k9AqXvBeQWzVfdg8WV67WEXbiWdXGQs6BEXqQeb4Pfow570zM4eDw0gxlp/Er8w
/lXsmolSgYpYuxFMYb1KX/H2iCXvA76VX7w5TElb/+6ekgbfP/d5ms6DEzKa8DlOpl+Q95lP194PsIlU
wCyfVCwLS+T8p3RDLi8dKBgQMcDW4Dha1ObBJTpV4zpwhEdMvJDu5PATtEQhFjhN/UYeyQiPRthjbkJn
LzT8hQFxwYwVW8PCjkyqEwYrr+R+mFG/C7tFRiooaW9MU9PCpFd95FARvlU=#
exit
class-map type stack match-all ip_udp_stack
match field IP protocol eq 0x11 next UDP
class-map type access-control match-all psirt1
match encrypted
filter-version 0.0_DummyVersion_20090101_1830
filter-id
cisco-sa-20090101-dummy_ddts_001
filter-hash
FC50BED10521002B8A170F29AF059C53
algorithm
aes256cbc
cipherkey
realm-cisco.sym
ciphervalue
#
DkGbVq0FPAsVJKguU15lQPDfZyTcHUXWsj8+tD+dCSYW9cjkRU9jyST4vO4u69/L62QlbyQuKdyQmb10
6sAeY5vDsDfDV05k4o5eD+j8cMt78iZT0Qg7uGiBSYBbak3kKn/5w2gDd1vnivyQ7g4Ltd9+XM+GP6XL
27RrXeP5A5iGbzC7KI9t6riZXk0gmR/vFw1a5wck0D/iQHIlFa/yRPoKMSFlqfIlLTe5NM7JArSTKET2
pu7wZammTz4FF6rY#
exit
match start TCP payload-start offset 0 size 10 regex "abc.*def"
match field TCP source-port eq 1234
class-map type access-control match-all psirt2
match encrypted
filter-version 0.0_DummyVersion_20090711_1830
filter-id
cisco-sa-20090711-dummy_ddts_002
filter-hash
DE0EB7D3C4AFDD990038174A472E4789
algorithm
aes256cbc
cipherkey
realm-cisco.sym
Related Commands
Command
Description
bandwidth
boot config
configure terminal
shape
show interfaces
show policy-map
Command
Description
show startup-config
Syntax Description
cef-exception
host
transit
Command Default
Command Modes
Command History
Examples
Release
Modification
12.4(24)T
The following is sample output from the show running-config control-plane command. The field
descriptions are self-explanatory.
Router# show running-config control-plane
Building configuration...
Current configuration : 14 bytes
!
control-plane
!
end
Related Commands
Command
Description
show running-config
Syntax Description
atm
dialer
frame-relay
map-class-name
linenum
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1
The map-class extension to the show runningconfig command was introduced to show only lines
pertaining to dialer or Frame Relay map classes.
12.1(2)T
12.2(4)T
12.2(33)SRA
Usage Guidelines
Use the show running-config map-class command to display the following information from the running
configuration file:
Use the linenum keyword to display line numbers in the output. This option is useful for identifying a
particular portion of a very large configuration.
Examples
All Map Classes Configured on the Router Example
The following example displays all map classes configured on the router:
Router# 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
1
2
3
4
5
Related Commands
: !
: map-class frame-relay boy
: no frame-relay adaptive-shaping
: frame-relay cir 1000
: end
Command
Description
map-class atm
map-class dialer
map-class frame-relay
more system:running-config
Syntax Description
part
Command Default
None
Command Modes
Command History
Usage Guidelines
Note
Release
Modification
12.2(33)SRB
12.2(33)SB
12.2(33)SXI
When the Configuration Partitioning feature is enabled, the system groups the configuration state of the
device into parts (called partitions) for the purpose of generating the virtual running configuration file
(the list of configuration commands). The selective processing of the systems configuration state for the
purpose of generating a partial running configuration is called configuration partitioning.
existing extensions to the show running-config command, which only filter the generated list after all
system components have been processed.
The Configuration Partitioning feature is enabled by default in Cisco IOS software images that support the
feature. To disable the feature, use the no parser config partition command.
Examples
In the following example, the system generates a view of the running configuration by polling only the
components associated with the access-list parts of the running configuration state, and then displays only
those access-list-related configuration commands.
Router# show running-config partition access-list
Building configuration...
Current configuration : 127 bytes
!
Configuration of Partition access-list
!
access-list 90 permit 0.0.0.0 1.2.3.5
access-list 100 permit 10 any any
!
end
In the following example, only the main configuration partition associated with the interface configuration
is queried, and only the configuration commands associated with Fast Ethernet 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
Related Commands
Command
Description
show interfaces
show running-config
Command
Description
show startup-config
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 |
status}
Syntax Description
accounting
counters
linecards
details
mcast
group group-id
inst
process id
status
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
Examples
Release
Modification
12.2(18)SXE
12.2(33)SRA
15.0(1)S
-------------------------------------------------------------------------------------------------------------------------FC-state indicates the flow control state and FC-count indicates the number of times flow control has been
turned on.
This example shows how to display all the processes that have registered an SAP with SCP:
Router# show module
Mod Ports Card Type
Model
Serial No.
--- ----- -------------------------------------- ------------------ ----------1
48 48-port 10/100 mb RJ45
WS-X6148-RJ-45
SAL091800RY
2
0 2 port adapter Enhanced FlexWAN
WS-X6582-2PA
JAE0940MH7Z
3
8 8 port 1000mb GBIC Enhanced QoS
WS-X6408A-GBIC
SAL09391KZH
5
2 Supervisor Engine 720 (Active)
WS-SUP720-3BXL
SAL09337UE6
6
2 Supervisor Engine 720 (Hot)
WS-SUP720-3BXL
SAL09148P59
Mod MAC addresses
Hw
Fw
Sw
Status
--- ---------------------------------- ------ ------------ ------------ ------1 0013.c3f8.d2c4 to 0013.c3f8.d2f3
5.0
8.3(1)
8.6(0.366)TA Ok
2 0015.2bc3.5b40 to 0015.2bc3.5b7f
2.1
12.2(nightly 12.2(nightly Ok
3 0015.6324.ed48 to 0015.6324.ed4f
3.1
5.4(2)
8.6(0.366)TA Ok
5 0014.a97d.b0ac to 0014.a97d.b0af
4.3
8.4(2)
12.2(nightly Ok
6 0013.7f0d.0660 to 0013.7f0d.0663
4.3
8.4(2)
12.2(nightly Ok
Mod Sub-Module
Model
Serial
Hw
Status
---- --------------------------- ------------------ ----------- ------- ------5 Policy Feature Card 3
WS-F6K-PFC3BXL
SAL09337NVE 1.6
Ok
5 MSFC3 Daughterboard
WS-SUP720
SAL09327AU6 2.3
Ok
6 Policy Feature Card 3
WS-F6K-PFC3BXL
SAL1033Y0YK 1.8
Ok
6 MSFC3 Daughterboard
WS-SUP720
SAL09158XB3 2.3
Ok
Mod Online Diag Status
---- ------------------1 Pass
2 Pass
3 Pass
5 Pass
6 Pass
0
0
0
0
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
To display information about the PCMCIA flash memory cards file system, use the show slotcommand in
user EXEC or privileged EXEC mode.
show slot [all | chips | detailed | err | summary]
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
all
chips
detailed
err
summary
Release
Modification
12.0
Use the show slot command to display details about the files in a particular linear PCMCIA flash memory
card of less than 20 MB and some 32 MB linear PCMCIA cards.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and
show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility
Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at
slot 1 with a sector size of 128K.
Router# show version
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows all possible flash system information for all PCMCIA flash cards in the
system.
Router# show slot all
Partition
Size
Used
Free
Bank-Size State
1
20223K 10821K
9402K
4096K
Read/Write
PCMCIA Slot0 flash directory:
File Length
Name/status
addr
fcksum ccksum
1
11081464 c3660-bin-mz.123-9.3.PI5b
0x40
0x5EA3 0x5EA3
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
1
1
89A0
2048KB
INTEL 28F016SA
2
1
89A0
2048KB
INTEL 28F016SA
1
2
89A0
2048KB
INTEL 28F016SA
2
2
89A0
2048KB
INTEL 28F016SA
1
3
89A0
2048KB
INTEL 28F016SA
2
3
89A0
2048KB
INTEL 28F016SA
1
4
89A0
2048KB
INTEL 28F016SA
2
4
89A0
2048KB
INTEL 28F016SA
1
5
89A0
2048KB
INTEL 28F016SA
2
5
89A0
2048KB
INTEL 28F016SA
The following example shows flash chip information
Router# show slot chips
20480K bytes of processor board PCMCIA
Chip
Bank
Code
Size
1
1
89A0
2048KB
2
1
89A0
2048KB
1
2
89A0
2048KB
2
2
89A0
2048KB
1
3
89A0
2048KB
2
3
89A0
2048KB
1
4
89A0
2048KB
2
4
89A0
2048KB
1
5
89A0
2048KB
2
5
89A0
2048KB
Slot0
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
Copy Mode
Direct
flash (Read/Write)
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
The following example shows the flash chip erase and write retries.
Router# show slot err
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
erase
1
1
89A0
2048KB
INTEL 28F016SA
0
2
1
89A0
2048KB
INTEL 28F016SA
0
1
2
89A0
2048KB
INTEL 28F016SA
0
2
2
89A0
2048KB
INTEL 28F016SA
0
1
3
89A0
2048KB
INTEL 28F016SA
0
2
3
89A0
2048KB
INTEL 28F016SA
0
1
4
89A0
2048KB
INTEL 28F016SA
0
2
4
89A0
2048KB
INTEL 28F016SA
0
1
5
89A0
2048KB
INTEL 28F016SA
0
2
5
89A0
2048KB
INTEL 28F016SA
0
write
0
0
0
0
0
0
0
0
0
0
Related Commands
Command
Description
dir slot0:
dir slot1:
show slot0:
show slot1:
Copy Mode
Direct
show slot0:
To display information about the PCMCIA flash memory cards file system located in slot 0, use the show
slot0:command in user EXEC or privileged EXEC mode.
show slot0: [all | chips | detailed | err | summary]
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
all
chips
detailed
err
summary
Release
Modification
12.0
12.2SX
Use the show slot0: command to display details about the files in a particular linear PCMCIA flash
memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and
show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility
Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at
slot 1 with a sector size of 128K.
Router# show version
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot0:
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Router# show slot0: all
Partition
Size
Used
Free
Bank-Size State
1
20223K 10821K
9402K
4096K
Read/Write
PCMCIA Slot0 flash directory:
File Length
Name/status
addr
fcksum ccksum
1
11081464 c3660-bin-mz.123-9.3.PI5b
0x40
0x5EA3 0x5EA3
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
1
1
89A0
2048KB
INTEL 28F016SA
2
1
89A0
2048KB
INTEL 28F016SA
1
2
89A0
2048KB
INTEL 28F016SA
2
2
89A0
2048KB
INTEL 28F016SA
1
3
89A0
2048KB
INTEL 28F016SA
2
3
89A0
2048KB
INTEL 28F016SA
1
4
89A0
2048KB
INTEL 28F016SA
2
4
89A0
2048KB
INTEL 28F016SA
1
5
89A0
2048KB
INTEL 28F016SA
2
5
89A0
2048KB
INTEL 28F016SA
The following example shows flash chip information.
Router# show slot0: chips
20480K bytes of processor board PCMCIA
Chip
Bank
Code
Size
1
1
89A0
2048KB
2
1
89A0
2048KB
1
2
89A0
2048KB
2
2
89A0
2048KB
1
3
89A0
2048KB
2
3
89A0
2048KB
1
4
89A0
2048KB
2
4
89A0
2048KB
Slot0
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
flash (Read/Write)
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
Copy Mode
Direct
1
2
5
5
89A0
89A0
2048KB
2048KB
INTEL 28F016SA
INTEL 28F016SA
The following example shows the flash chip erase and write retries.
Router# show slot0: err
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
erase
1
1
89A0
2048KB
INTEL 28F016SA
0
2
1
89A0
2048KB
INTEL 28F016SA
0
1
2
89A0
2048KB
INTEL 28F016SA
0
2
2
89A0
2048KB
INTEL 28F016SA
0
1
3
89A0
2048KB
INTEL 28F016SA
0
2
3
89A0
2048KB
INTEL 28F016SA
0
1
4
89A0
2048KB
INTEL 28F016SA
0
2
4
89A0
2048KB
INTEL 28F016SA
0
1
5
89A0
2048KB
INTEL 28F016SA
0
2
5
89A0
2048KB
INTEL 28F016SA
0
write
0
0
0
0
0
0
0
0
0
0
Related Commands
Copy Mode
Direct
Command
Description
dir slot0:
dir slot1:
show slot1:
show slot
show slot1:
To display information about the PCMCIA flash memory cards file system located in slot 1, use the show
slot1:command in user EXEC or privileged EXEC mode.
show slot1: [all | chips | detailed | err | summary]
Syntax Description
Command Modes
Command History
Usage Guidelines
Note
all
chips
detailed
err
summary
Release
Modification
12.0
Use the show slot1: command to display details about the files in a particular linear PCMCIA flash
memory card of less than 20 MB and some 32 MB linear PCMCIA cards located in slot 1.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and
show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility
Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/
products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at
slot 1 with a sector size of 128K.
Router# show version
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
In some cases the show slot command will not display the file systems. Use show slot0: or show slot1:.
The following example displays information about slot 0 using the slot0:
command form. The output is self-explanatory.
Router# show slot1
:
PCMCIA Slot1 flash directory:
File Length
Name/status
1
10907068 c3660-bin-mz.123-7.9.PI4
[10907132 bytes used, 5739008 available, 16646140 total]
16384K bytes of processor board PCMCIA Slot1 flash (Read/Write)
Router# show slot1: all
Partition
Size
Used
Free
Bank-Size State
Copy Mode
1
20223K 10821K
9402K
4096K
Read/Write
Direct
PCMCIA Slot0 flash directory:
File Length
Name/status
addr
fcksum ccksum
1
11081464 c3660-bin-mz.123-9.3.PI5b
0x40
0x5EA3 0x5EA3
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
1
1
89A0
2048KB
INTEL 28F016SA
2
1
89A0
2048KB
INTEL 28F016SA
1
2
89A0
2048KB
INTEL 28F016SA
2
2
89A0
2048KB
INTEL 28F016SA
1
3
89A0
2048KB
INTEL 28F016SA
2
3
89A0
2048KB
INTEL 28F016SA
1
4
89A0
2048KB
INTEL 28F016SA
2
4
89A0
2048KB
INTEL 28F016SA
1
5
89A0
2048KB
INTEL 28F016SA
2
5
89A0
2048KB
INTEL 28F016SA
The following example shows flash chip information.
Router# show slot1: chips
20480K bytes of processor board PCMCIA
Chip
Bank
Code
Size
1
1
89A0
2048KB
2
1
89A0
2048KB
1
2
89A0
2048KB
2
2
89A0
2048KB
1
3
89A0
2048KB
2
3
89A0
2048KB
1
4
89A0
2048KB
2
4
89A0
2048KB
1
5
89A0
2048KB
2
5
89A0
2048KB
Slot0
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
flash (Read/Write)
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
File
Length
Name/status
addr
fcksum ccksum
1
11081464 c3660-bin-mz.123-9.3.PI5b
0x40
0x5EA3 0x5EA3
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows the flash chip erase and write retries.
Router# show slot1: err
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip
Bank
Code
Size
Name
erase
1
1
89A0
2048KB
INTEL 28F016SA
0
2
1
89A0
2048KB
INTEL 28F016SA
0
1
2
89A0
2048KB
INTEL 28F016SA
0
2
2
89A0
2048KB
INTEL 28F016SA
0
1
3
89A0
2048KB
INTEL 28F016SA
0
2
3
89A0
2048KB
INTEL 28F016SA
0
1
4
89A0
2048KB
INTEL 28F016SA
0
2
4
89A0
2048KB
INTEL 28F016SA
0
1
5
89A0
2048KB
INTEL 28F016SA
0
2
5
89A0
2048KB
INTEL 28F016SA
0
write
0
0
0
0
0
0
0
0
0
0
Related Commands
Command
Description
dir slot0:
dir slot1:
show slot0:
show slot
Copy Mode
Direct
Syntax Description
Command Modes
Command History
Usage Guidelines
flash0:
filename
flash1:
flash:
nvram:
usbflash0:
usbflash1:
Release
Modification
15.0(1)M
The show software authenticity file command allows you to display software authentication related
information that includes image credential information, key type used for verification, signing information,
and other attributes in the signature envelope, for a specific image file. The command handler will extract
the signature envelope and its fields from the image file and dump the required information.
Examples
The following example displays software authentication related information for an image file named
c3900-universalk9-mz.SSA:
Router# show software authenticity file flash0:c3900-universalk9-mz.SSA
File Name
: flash0:c3900-universalk9-mz.SSA
Image type
: Development
Signer Information
Common Name
: xxx
Organization Unit
: xxx
Organization Name
: xxx
Certificate Serial Number : xxx
Hash Algorithm
: SHA512
Signature Algorithm
: 2048-bit RSA
Key Version
: A
The following table describes the significant fields shown in the display.
Table 163
Related Commands
Field
Description
File Name
Image type
Signer Information
Signature information.
Common Name
Organization Unit
Organization Name
Hash Algorithm
Signature Algorithm
Key Version
Command
Description
Command
Description
Syntax Description
Command Modes
Command History
Release
Modification
15.0(1)M
Usage Guidelines
The display from this command includes the public keys that are in the storage with the key types.
Examples
The following is sample output from the show software authenticity keys command:
Router# show software authenticity keys
Public Key #1 Information
------------------------Key Type
: Release (Primary)
Public Key Algorithm : RSA
Modulus :
CC:CA:40:55:8C:71:E2:4A:3A:B6:9D:5C:94:1D:02:BA:
.....
26:04:6B:33:EB:70:2B:18:24:C7:D9:31:3E:77:24:85
Exponent : xxx
Key Version
: A
Public Key #2 Information
------------------------Key Type
: Development (Primary)
Public Key Algorithm : RSA
Modulus :
CC:CA:40:55:8C:71:E2:4A:3A:B6:9D:5C:94:1D:02:BA:
.....
26:04:6B:33:EB:70:2B:18:24:C7:D9:31:3E:77:24:85
Exponent : xxx
Key Version
: A
The following table describes the significant fields shown in the display.
Table 164
Related Commands
Field
Description
Public Key #
Key Type
Modulus
Exponent
Key Version
Command
Description
Syntax Description
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
The information displayed by the show software authenticity running command about the current
ROMMON, monlib and Cisco IOS image used for booting includes:
Examples
The following example displays software authentication related information for the current ROM monitor
(ROMMON), monitor library (monlib), and Cisco IOS image used for booting:
Router(mode-prompt
)# show software authenticity running
SYSTEM IMAGE
------------------Image type : Development
Signer Information
Common Name : xxx
Organization Unit : xxx
Organization Name : xxx
Certificate Serial Number : xxx
Hash Algorithm : xxx
Signature Algorithm : 2048-bit RSA
Key Version : xxx
Verifier Information
Verifier Name : ROMMON 2
Verifier Version : System Bootstrap, Version 12.4(20090409:084310)
ROMMON 2
---------------
The following table describes the significant fields shown in the display.
Table 165
Related Commands
Field
Description
SYSTEM IMAGE
Image type
Common Name
Organization Unit
Organization Name
Hash Algorithm
Signature Algorithm
Key Version
Verifier Name
Verifier Version
ROMMON 2
Command
Description
Command
Description
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks command in EXEC
mode.
show stacks
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The display from this command includes the reason for the last system reboot. If the system was reloaded
because of a system failure, a saved system stack trace is displayed. This information is of use only to your
technical support representative in analyzing crashes in the field. It is included here in case you need to
read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show stacks command following a system failure:
Router# show stacks
Minimum process stacks:
Free/Size Name
652/1000 Router Init
726/1000 Init
744/1000 BGP Open
686/1200 Virtual Exec
Interrupt level stacks:
Level
Called Free/Size Name
1
0 1000/1000 env-flash
3
738 900/1000 Multiport Communications Interfaces
5
178 970/1000 Console UART
System was restarted by bus error at PC 0xAD1F4, address 0xD0D0D1A
GS Software (GS3), Version 9.1(0.16), BETA TEST SOFTWARE
Compiled Tue 11-Aug-92 13:27 by jthomas
Stack trace from system failure:
FP: 0x29C158, RA: 0xACFD4
FP: 0x29C184, RA: 0xAD20C
FP: 0x29C1B0, RA: 0xACFD4
FP: 0x29C1DC, RA: 0xAD304
FP: 0x29C1F8, RA: 0xAF774
FP: 0x29C214, RA: 0xAF83E
Related Commands
Command
Description
show processes
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
To display the subsystem information, use the show subsys command in privileged EXEC mode.
show subsys [class class | name name]
Syntax Description
Command Modes
Command History
Usage Guidelines
class class
name name
Release
Modification
11.1
12.3
12.3T
12.2(33)SRA
12.2(35)SE2
Use the show subsys command to confirm that all required features are in the running image.
Examples
Class
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Library
Library
Library
Library
Library
Driver
Driver
Driver
Driver
Driver
Driver
Version
1.000.001
1.000.001
1.000.001
1.000.001
1.000.002
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
The following is sample output from the show subsys command that includes the license class:
Router# show subsys
Name
license_mgmt_local
license_admin_local
license_debug_core
license_test_ui
test_license_parser
license_ui
license_parser
license_registry
license_client
name license
Class
Version
Management 1.000.001
Management 1.000.001
Management 1.000.001
Management 1.000.001
Management 1.000.001
Management 1.000.001
Management 1.000.001
Registry
1.000.001
License
1.000.001
Field
Description
Name
Class
Version
show sup-bootflash
To display information about the sup-bootflash file system, use the show sup-bootflash command in
privileged EXEC mode.
show sup-bootflash [all | chips | filesys]
Syntax Description
all
chips
filesys
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(14)SX
12.217d)SXB
12.2(33)SRA
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
DEVICE TYPE:
Layout
: Paired x16 Mode
Write Queue Size
: 64
Queued Erase Supported : No
Router#
This example shows how to display information about the file system:
Router# show sup-bootflash filesys
-------- F I L E
S Y S T E M
S T A T U S -------Device Number = 2
DEVICE INFO BLOCK: bootflash
Magic Number
= 6887635
File System Vers = 10000
(1.0)
Length
= 1000000
Sector Size
= 40000
Programming Algorithm = 19
Erased State
= FFFFFFFF
File System Offset
= 40000
Length = F40000
MONLIB Offset
= 100
Length = F568
Bad Sector Map Offset = 3FFF8
Length = 8
Squeeze Log Offset
= F80000
Length = 40000
Squeeze Buffer Offset = FC0000
Length = 40000
Num Spare Sectors
= 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
No Squeeze in progress
USAGE INFO:
Bytes Used
= EA2620
Bad Sectors
= 0
OK Files
= 2
Deleted Files = 0
Files w/Errors = 0
Router#
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.2(17d)SXB
12.2(33)SRA
Related Commands
Command
Description
system jumbomtu
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 | voice | wccp]
Cisco 7600 Series
show tech-support [cef | ipmulticast [vrf vrf-name] | isis | password [page] | platform | page |
rsvp]
Syntax Description
page
password
cef
ipc
ipmulticast
vrf vrf-name
isis
mpls
rsvp
voice
wccp
platform
Command Default
The output scrolls without page breaks. Passwords and other security information are removed from the
output.
Command Modes
Command History
Release
Modification
11.2
11.3(7), 11.2(16)
12.0
12.2(13)T
12.2(14)SX
12.3(4)T
12.2(17d)SXB
Release
Modification
12.2(30)S
12.3(16)
12.2(18)SXF
Support to interrupt and terminate the show techsupport output was added.
12.4(4)T
Usage Guidelines
Release
Modification
12.4(7)
12.2(33)SRA
12.4(9)T
15.0(1)M
12.2(33)SRE
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 Spacebarto 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:
Note
show buffers
show cdp neighbors
show cef
show clns traffic
show context
show controllers
show decnet traffic
show disk0: all
show dmvpn details
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
Crypto information is not duplicated by the show dmvpn details command output.
When the show tech-support command is entered on a virtual switch (VS), the output displays the output
of the show module command and the show power command for both the active and standby switches.
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 techsupport command:
If you enter the ipmulticast keyword, the output displays, but is not limited to, these show commands:
If you enter the wccp keyword, the output displays, but is not limited to, these show commands:
Examples
Related Commands
For a sample display of the output from the show tech-support command, refer to the documentation for
the show commands listed in the Usage Guidelines section.
Command
Description
dir
show bootflash
Command
Description
show bootvar
show buffers
show cef
show context
show controllers
show disk:0
show environment
show interfaces
Command
Description
show inventory
show ip interface
show ip traffic
show ip wccp
show logging
show module
show power
show running-config
show spanning-tree
show stacks
show version
show vlan
show template
To display template information, use the show template command in user EXEC or privileged EXEC
mode.
show template [template-name]
Syntax Description
Command Modes
Command History
Examples
template-name
Release
Modification
12.2(33)SRE
12.2(33)SXI
12.4(24)T
The following is sample output from the show templatecommand displaying template information. The
fields are self-explanatory.
Router# show template
Template class/type Component(s)
template1 owner ppp peer dialer
Related Commands
Command
Description
template
Syntax Description
controller-number
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(14)T
12.4(11)T
Usage Guidelines
Use the show usb controllerscommand to display content such as controller register specific information,
current asynchronous buffer addresses, and period scheduling information. You can also use this command
to verify that copy operations are occurring successfully onto a USB flash module.
Examples
The following example is sample output from the show usb controllers command:
Router# show usb controllers
Name:1362HCD
Controller ID:1
Controller Specific Information:
Revision:0x11
Control:0x80
Command Status:0x0
Hardware Interrupt Status:0x24
Hardware Interrupt Enable:0x80000040
Hardware Interrupt Disable:0x80000040
Frame Interval:0x27782EDF
Frame Remaining:0x13C1
Frame Number:0xDA4C
LSThreshold:0x628
RhDescriptorA:0x19000202
RhDescriptorB:0x0
RhStatus:0x0
RhPort1Status:0x100103
RhPort2Status:0x100303
Hardware Configuration:0x3029
DMA Configuration:0x0
Transfer Counter:0x1
Interrupt:0x9
Interrupt Enable:0x196
Chip ID:0x3630
Buffer Status:0x0
Direct Address Length:0x80A00
ATL Buffer Size:0x600
ATL Buffer Port:0x0
ATL Block Size:0x100
ATL PTD Skip Map:0xFFFFFFFF
ATL PTD Last:0x20
ATL Current Active PTD:0x0
ATL Threshold Count:0x1
ATL Threshold Timeout:0xFF
Int Level:1
Transfer Completion Codes:
Success
:920
Bit Stuff
:0
No Response
:0
Underrun
:0
Buffer Overrun
:0
Transfer Errors:
Canceled Transfers
:2
Transfer Failures:
Interrupt Transfer
:0
Isochronous Transfer :0
Transfer Successes:
Interrupt Transfer
:0
Isochronous Transfer :0
USBD Failures:
Enumeration Failures :0
Power Budget Exceeded:0
USB MSCD SCSI Class Driver Counters:
Good Status Failures :3
Good Status Timed out:0
Device Never Opened :0
Illegal App Handle
:0
Invalid Unit Number :0
Application Overflow :0
Control Pipe Stall
:0
Device Stalled
:0
Device Detached
:0
Invalid Logic Unit Num:0
USB Aladdin Token Driver Counters:
Token Inserted
:1
Send Insert Msg Fail :0
Dev Entry Add Fail
:0
Dev Entry Remove Fail:0
Response Txn Fail
:0
Txn Invalid Dev Handle:0
USB Flash File System Counters:
Flash Disconnected
:0
Flash Device Fail
:0
Flash startstop Fail :0
USB Secure Token File System Counters:
Token Inserted
:1
Token FS success
:1
Token Max Inserted
:0
Token Event
:0
Watched Boolean Create Failures:0
CRC
Stall
Overrun
Other
Buffer Underrun
:0
:0
:0
:0
:0
Control Timeout :0
Bulk Transfer
:0
Control Transfer:0
Bulk Transfer
:26
Control Transfer:894
No Class Driver Found:0
Command Fail
:0
Device not Found:0
Drive Init Fail :0
Bad API Command :0
Invalid Argument:0
Device in use
:0
Malloc Error
:0
Bad Command Code:0
Unknown Error
:0
Token Removed
:0
Response Txns
:434
Request Txns
:434
Request Txn Fail:0
Command Txn Fail:0
Flash Connected :1
Flash Ok
:1
Flash FS Fail
:0
Token Detached :0
Token FS Fail
:0
Create Talker Failures:0
Destroy Talker Failures:0
Syntax Description
controller-ID
device-address
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(14)T
12.4(11)T
Usage Guidelines
Use the show usb device command to display information for either a USB flash drive or a USB eToken,
as appropriate.
Examples
The following example is sample output from the show usb device command:
Router# show usb device
Host Controller:1
Address:0x1
Device Configured:YES
Device Supported:YES
Description:DiskOnKey
Manufacturer:M-Sys
Version:2.0
Serial Number:0750D84030316868
Device Handle:0x1000000
USB Version Compliance:2.0
Class Code:0x0
Subclass Code:0x0
Protocol:0x0
Vendor ID:0x8EC
Product ID:0x15
Max. Packet Size of Endpoint Zero:64
Number of Configurations:1
Speed:Full
Selected Configuration:1
Selected Interface:0
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
The following table describes the significant fields shown in the display.
Table 167
Field
Description
Device handle
Device Protocol
Interface Protocol
Max Packet
Syntax Description
index
Command Default
Command Modes
Privileged EXEC
Command History
Examples
Release
Modification
12.3(14)T
12.4(11)T
The following example is sample output for the show usb driver command:
Router# show usb driver
Index:0
Owner Mask:0x6
Class Code:0x0
Subclass Code:0x0
Protocol:0x0
Interface Class Code:0x8
Interface Subclass Code:0x6
Interface Protocol Code:0x50
Product ID:0x655BD598
Vendor ID:0x64E90000
Attached Devices:
Controller ID:1, Device Address:1
Index:1
Owner Mask:0x1
Class Code:0x0
Subclass Code:0x0
Protocol:0x0
Interface Class Code:0x0
The following table describes the significant field shown in the display.
Table 168
Field
Description
Owner Mask
Syntax Description
Command Modes
Command History
Examples
port-number
Privileged EXEC
Release
Modification
12.3(14)T
The following sample from the show usb port command shows the status of the port 1 on the router:
Router# show usb port
Port Number:0
Status:Enabled
Connection State:Connected
Speed:Full
Power State:ON
Port Number:1
Status:Enabled
Connection State:Connected
Speed:Low
Power State:ON
Syntax Description
Command Modes
EXEC
Command History
Examples
Release
Modification
12.3(14)T
The following example is sample output from the show usb tree command. This output shows that both a
USB flash module and a USB eToken are currently enabled.
Router# show usb tree
[Host Id:1, Host Type:1362HCD, Number of RH-Port:2]
<Root Port0:Power=ON
Current State=Enabled>
Port0:(DiskOnKey) Addr:0x1 VID:0x08EC PID:0x0015 Configured (0x1000000)
<Root Port1:Power=ON
Current State=Enabled>
Port1:(eToken Pro 4254) Addr:0x11 VID:0x0529 PID:0x0514 Configured (0x1010000)
show usbtoken
To display information about the USB eToken (such as the eToken ID), use the show usbtokencommand
in privileged EXEC mode.
show usbtoken [0-9]:{all | filesystem}
Syntax Description
Command Modes
Command History
0-9
all
filesystem
Privileged EXEC
Release
Modification
12.3(14)T
12.4(11)T
Usage Guidelines
Use the show usbtoken command to verify whether a USB eToken is inserted in the router.
Examples
The following example is sample output from the show usbtoken command:
Router# show usbtoken0
Token ID
:43353334
Token device name : token0
Vendor name
: Vendor34
Product Name
:Etoken Pro
Serial number
: 22273a334353
Firmware version
:
4.1.3.2
Total memory size : 32 KB
Free memory size
: 16 KB
FIPS version
: Yes/No
Token state
: Active | User locked | Admin locked | System Error |
Uknown
ATR (Answer To Reset) :"3B F2 98 0
FF C1 10 31 FE 55 C8 3"
The following table describes the significant fields shown in the display.
Table 169
Field
Description
Token ID
Token identifier.
show version
To display information about the currently loaded software along with hardware and device information,
use the show version command in user EXEC, privileged EXEC, or diagnostic mode.
show version
Cisco ASR 1000 Series Routers
show version [rp-slot] [installed [user-interface] | provisioned | running]
Cisco Catalyst 4500e Series Switches running IOS XE software
show version [rp-slot] [running]
Cisco Catalyst 6500 Series Routers
show version [epld slot]
Syntax Description
rp-slot
r0 --the RP in RP slot 0.
r1 --the RP in RP slot 1.
rp active --the active RP.
rp standby --the standby RP.
installed
user-interface
provisioned
running
epld slot
Command Default
Command Modes
User EXEC (>) Privileged EXEC (#) Diagnostic (diag)--Cisco ASR 1000 Series Routers only
Command History
Release
Modification
9.0
12.1EC
12.1(1a)T1
12.3BC
12.3(4)T
12.2(14)SX
12.2(17d)SXB
12.2(25)S
12.2(33)SCA
12.2(33)SRA
Usage Guidelines
12.2(18)SX
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
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
<software-type>
See the Examples section for descriptions of the fields in this output.
Cisco ASR 1000 Series Routers
Entering show versionwithout any of the options on the Cisco ASR 1000 Series Router will generate
output similar to show version on other Cisco routers.
In order to understand the show versionoutput on Cisco ASR 1000 Series Routers, it is important to
understand that the individual sub-packages run the processes on the router. Among other things, the output
of this command provides information on where various individual sub-packages are stored on the router,
and which processes these individual sub-packages are and are not currently running.
More specifically, the command displays each individual sub-package file on the router, the hardware
where the sub-package could be running, and whether the sub-package is currently being run on that
hardware.
The show version provisioned command displays only the individual sub-packages that can be
provisioned, which are the RP-specific sub-packages (RP Access, RP Base, RP Control, and RP IOS) and
the provisioning file. The output includes the individual sub-package file, the hardware where the subpackage could be running, and whether the sub-package is currently being run on that hardware.
The command displays only the individual sub-packages that are currently active. The output includes the
individual sub-package file and the hardware where the sub-package is running.
Cisco Catalyst 4500e Series Switches
Entering show version without any of the options on a Cisco Catalyst 4500e Series Switch running IOS XE
software will generate output similar to show version on other Cisco platforms. One notable difference is
that the output displays the IOS XE software version instead of the IOS image version.
The IOS XE software bundle includes a set of individual packages that comprise the complete set of
software that runs on the switch. The show version running command displays the list individual packages
that are currently active, that is, the set of packages included in the IOS XE software bundle currently
running on the Cisco Catalyst 4500e Series Switch.
Examples
Cisco 3660 Router
The following is sample output from the show version command issued on a Cisco 3660 running Cisco
IOS Release 12.3(4)T:
Router# show version
Cisco IOS Software, 3600 Software (C3660-I-M), Version 12.3(4)T
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by Cisco Systems, Inc.
Compiled Thu 18-Sep-03 15:37 by ccai
ROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
ROM:
C3660-1 uptime is 1 week, 3 days, 6 hours, 41 minutes
System returned to ROM by power-on
System image file is "slot0:tftpboot/c3660-i-mz.123-4.T"
Cisco 3660 (R527x) processor (revision 1.0) with 57344K/8192K bytes of memory.
Processor board ID JAB055180FF
R527x CPU at 225Mhz, Implementation 40, Rev 10.0, 2048KB L2 Cache
3660 Chassis type: ENTERPRISE
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
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
Router#
For information about PCI buses and bandwidth calculation, go to the "Cisco 7200 Series Port Adapter
Installation Requirements" chapter, of the Cisco 7200 Series Port Adapter Hardware Configuration
Guidelines guide.
The following table describes the significant fields shown in the display.
Table 170
Field
Description
For example:
Cisco IOS Software, 7200 Software (C7200-G4JSM), Version 12.3(4)T
BOOTFLASH:
Field
Description
For example:
C3660-1 uptime is 1 week, 3 days, 6 hours, 41
minutes
System returned to ROM by reload-reason at
timedaydate
For example:
System returned to ROM by reload at 20:56:53
UTC Tue Nov 4 2003
Last reload reason: reload-reason
For example:
Last reload reason: Reload command
Last reset from reset-reason
For example:
Last reset from power-on
Field
Description
Field
Description
so you need to add both numbers to find out the real
amount of DRAM. In the example to the left for the
Cisco 3660, the router has 57,344 kilobytes (KB) of
free DRAM and 8,192 KB dedicated to Packet
memory. Adding the two numbers together gives
you 57,344K + 8,192K = 65,536K, or 64
megabytes (MB) of DRAM.
For more details on memeory requirements, see the
document "How to Choose a Cisco IOS Software
Release" on Cisco.com.
The following table describes the fields that are shown in the example.
Table 171
Field
Description
Router uptime is
System restarted by
Configuration register is
The output of the show version EXEC command can 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.
This example shows how to display the ELPD version information of a slot:
Router# show version epld 4
Module 4 EPLD's:
Number of EPLD's: 6
EPLD A : 0x5
EPLD B : 0x2
EPLD C : 0x1
EPLD D : 0x1
EPLD E : 0x1
Router#
Field
Description
Field
Description
Router uptime is
System restarted at
Configuration register is
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.
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
[email protected].
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.
In the following example, the 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).
PE23_ASR-1006#
Package: Provisioning File, version: n/a, status: active
File: consolidated:packages.conf, on: RP0
Built: n/a, by: n/a
File SHA1 checksum: b6cb06b1ed02e041d48644340aa077833cff2076
Package: rpbase, version: 02.04.00.122-33.XND, status: active
File: consolidated:asr1000rp1-rpbase.02.04.00.122-33.XND.pkg, on: RP0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 093f2c935b9dc4ed136623bc43488c6517b9a4ae
Package: rpcontrol, version: 02.04.00.122-33.XND, status: active
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP0/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: active
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg, on: RP0/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
Package: rpaccess, version: 02.04.00.122-33.XND, status: active
File: consolidated:asr1000rp1-rpaccess.02.04.00.122-33.XND.pkg, on: RP0/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 0b0d108cd2683570778668697b7ffca2451b78b3
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP0/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg, on: RP0/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
Package: rpaccess, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpaccess.02.04.00.122-33.XND.pkg, on: RP0/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 0b0d108cd2683570778668697b7ffca2451b78b3
Package: rpbase, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpbase.02.04.00.122-33.XND.pkg, on: RP1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 093f2c935b9dc4ed136623bc43488c6517b9a4ae
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP1/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg, on: RP1/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
In the following example, the show version provisionedcommand 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).
PE23_ASR-1006#show version provisioned
Package: Provisioning File, version: n/a, status: active
File: consolidated:packages.conf, on: RP0
Built: n/a, by: n/a
File SHA1 checksum: b6cb06b1ed02e041d48644340aa077833cff2076
Package: rpbase, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpbase.02.04.00.122-33.XND.pkg, on: RP0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 093f2c935b9dc4ed136623bc43488c6517b9a4ae
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP0/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg,
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
Package: rpaccess, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpaccess.02.04.00.122-33.XND.pkg, on: RP0/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 0b0d108cd2683570778668697b7ffca2451b78b3
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP0/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg,
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
Package: rpaccess, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpaccess.02.04.00.122-33.XND.pkg, on: RP0/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 0b0d108cd2683570778668697b7ffca2451b78b3
Package: rpbase, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpbase.02.04.00.122-33.XND.pkg, on: RP1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 093f2c935b9dc4ed136623bc43488c6517b9a4ae
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP1/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg,
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
Package: rpaccess, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpaccess.02.04.00.122-33.XND.pkg, on: RP1/0
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 0b0d108cd2683570778668697b7ffca2451b78b3
Package: rpcontrol, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpcontrol.02.04.00.122-33.XND.pkg, on: RP1/1
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: d71e05c824cb889048b3353257bd16129eb72c44
Package: rpios-advipservicesk9, version: 02.04.00.122-33.XND, status: n/a
File: consolidated:asr1000rp1-rpios-advipservicesk9.02.04.00.122-33.XND.pkg,
Built: 2009-06-29_23.07, by: mcpre
File SHA1 checksum: 4167d300514153f67c3815c487c270c14449185d
on: RP0/0
on: RP0/1
on: RP1/0
on: RP1/1
In the following example, the 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#
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
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
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
Package: rpios-advipservicesk9, version: unknown, status: active
File: unknown, on: CC0/0
Built: 2007-11-11_17.16, by: mcpre
File SHA1 checksum: unknown
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
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#
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
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
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#
Table 173
Field
Description
Package:
version:
status:
File:
on:
Built:
In the following example, the show version running command is entered on a Cisco Catalyst 4500e Series
Switch to view the list of packages contained in the IOS XE software bundle currently loaded on the
system.
Switch# show version running
Package: Base, version: 3.0.0, status: active
30
File: cat4500e-base.SSA.3.0.0.pkg, on: Slot5
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:08:38 PDT 2010, by: xxxx
Package: Infra, version: 3.0.0, status: active
File: cat4500e-infra.SSA.3.0.0.pkg, on: Slot5
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:09:30 PDT 2010, by: xxxx
Package: IOS, version: 150-1.XO, status: active
File: cat4500e-universalk9.SSA.150-1.XO.pkg, on: Slot5
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:10:02 PDT 2010, by: xxxx
Package: Base, version: 3.0.0, status: active
File: cat4500e-base.SSA.3.0.0.pkg, on: Slot6
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:08:38 PDT 2010, by: xxxx
Package: Infra, version: 3.0.0, status: active
File: cat4500e-infra.SSA.3.0.0.pkg, on: Slot6
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:09:30 PDT 2010, by: xxxx
Package: IOS, version: 150-1.XO, status: active
File: cat4500e-universalk9.SSA.150-1.XO.pkg, on: Slot6
From Bundle: cat4500e-universalk9.SSA.3.1.0.SG
Built: Mon Apr 19 10:10:02 PDT 2010, by: xxxx
Switch#
Table 174
Table 5,Cisco Catalyst 4500e Series Switched show version running Field Descriptions
Field
Description
Package:
version:
status:
Related Commands
Field
Description
File:
on:
From Bundle:
Built:
Command
Description
show diag
show inventory
show warm-reboot
To display the statistics for attempted warm reboots, use the show warm-rebootcommand in privileged
EXEC mode.
show warm-reboot
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(2)T
12.2(18)S
12.2(28)SB
Usage Guidelines
Use the show warm-reboot command to see if warm rebooting is enabled, and, if so, how many warm
reloads have occurred and how much space in kilobytes (KB) is consumed by warm-reboot storage, which
is the RAM area used to store the data segment that enables warm reloading to function.
Examples
The following example is sample output from the show warm-reboot command:
Router# show warm-reboot
Warm Reboot is enabled
Statistics:
10 warm reboots have taken place since the last cold reboot
XXX KB taken up by warm reboot storage
Related Commands
Command
Description
warm-reboot
show wiretap
To display the intercept status, use the show wiretap command in privileged EXEC mode.
show wiretap [id [stream-id] | idbs]
Syntax Description
id
stream-id
idbs
Command Default
If the id is not specified , information for all wiretap configurations and IDBs is displayed.
Command Modes
Command History
Release
Modification
15.0(1)M
12.2 (33)SXI
Usage Guidelines
Examples
The following is sample output from the show wiretap command. The field descriptions are selfexplanatory.
Router# show wiretap
Mediation Device 0x00000001
TTl
= 3130
Time left = 3127 minutes
MD IP Address = 6.6.6.12
MD SNMP IF index = 0
MD HW IF index = 0
MD Source IP address = 6.6.6.14
MD UDP port = 7777
DSCP value = af41
Platform data = 0x00000000
Stream count = 1
Streams associated with MD
Generic stream 0x00000002
Status = 1
Packets intercepted = 0
Packets dropped = 0
Type = Session
Index
0x00000002
Acnt ID 0x00000001
SNMP provisioned intercept
Status
0
show whoami
To display information about the terminal line of the current user, including host name, line number, line
speed, and location, use the show whoami command in EXEC mode.
show whoami [text]
Syntax Description
Command Modes
Command History
Usage Guidelines
text
EXEC
Release
Modification
10.0
12.2(33)SRA
If text is included as an argument in the command, that text is displayed as part of the additional data about
the line.
To prevent the information from being lost if the menu display clears the screen, this command always
displays a --More-- prompt before returning. Press the space bar to return to the prompt.
Examples
The following example is sample output from the show whoami command:
Router> show whoami
Comm Server "Router", Line 0 at 0bps.
--More-Router>
showmon
To show both the ReadOnly and the Upgrade ROMmon image versions when you are in ROMmon mode,
as well as which ROMmon image is running on the Cisco 7200 VXR or Cisco 7301 router, use the
showmoncommand in ROM monitor mode.
showmon
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.0(28)S
12.3(8)T
12.3(9)
Usage Guidelines
Use the showmon command when you are in ROM monitor mode. Use the show rom-monitor command
when you are in Cisco IOS.
Examples
The following example, applicable to both the Cisco 7200 VXR and Cisco 7301 routers, uses the showmon
command in ROMmon to display both ROMmon images and to verify that the Upgrade ROMmon image is
running:
rommon 1 > showmon
ReadOnly ROMMON version is:
System Bootstrap, Version 12.2(20031011:151758) [biff]
Related Commands
Command
Description
rommon-pref
Syntax Description
Command Default
Enabled
Command Modes
Global configuration
Command History
Release
Modification
11.1
12.2(33)SRA
Usage Guidelines
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for dual RSP cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
In automatic synchronization mode, when you issue a copy EXEC command that specifies the masters
startup configuration (nvram:startup-config) as the target, the master also copies the same file to the
slaves startup configuration (slavenvram:startup-config). Use this command when implementing HSA
for simple hardware backup or for software error protection to ensure that the master and slave RSP contain
the same configuration files.
Examples
The following example turns on automatic configuration file synchronization. When the copy
system:running-config nvram:startup-config command is entered, the running configuration is saved to
the startup configurations of both the master RSP and the slave RSP.
Router(config)# slave auto-sync config
Router(config)# end
Router# copy system:running-config nvram:startup-config
Related Commands
Command
Description
show stacks
show version
slave default-slot
To specify the default slave Route Switch Processor (RSP) card on a Cisco 7507 or Cisco 7513 router, use
the slave default-slot global configuration command.
slave default-slot processor-slot-number
Syntax Description
processor-slot-number
Command Default
The default slave is the RSP card located in the higher number processor slot. On the Cisco 7507 router,
processor slot 3 contains the default slave RSP. On the Cisco 7513 router, processor slot 7 contains the
default slave RSP.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.1
12.2(33)SRA
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
The router uses the default slave information when booting as follows:
If a system boot is due to powering up the router or using the reload EXEC command, then the
specified default slave will be the slave RSP.
If a system boot is due to a system crash or hardware failure, then the system ignores the default slave
designation, and makes the crashed or faulty RSP card the slave RSP.
Examples
In the following example, the user sets the default slave RSP to processor slot 2 on a Cisco 7507 router:
c7507(config)# slave default-slot 2
Related Commands
Command
Description
reload
show stack s
show version
slave image
To specify the image that the slave Route Switch Processor (RSP) runs on a Cisco 7507 or Cisco 7513
router, use the slave image command in global configuration mode.
slave image {system | file-url}
Syntax Description
system
file-url
Command Default
Command Modes
Command History
Usage Guidelines
Note
Release
Modification
11.1
12.2(33)SRA
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
Use the slave image command to override the slave image that is bundled with the master image.
When using HSA for simple hardware backup, ensure that the slave image is in the same location on the
master and the slave RSP card. Thus, if the slave RSP card becomes the master, it will be able to find the
slave image and download it to the new slave.
The default length of the bootstring filename is 64 characters. Depending on the platform a longer
bootstring filename can be used and supported.
Examples
In the following example, the slave RSP is specified to run the rsp-dw-mz.ucode.111-3.2 image from slot 0:
Router(config)# slave image slot0:rsp-dw-mz.ucode.111-3.2
Related Commands
Command
Description
show stack s
show version
slave reload
slave reload
To force a reload of the image that the slave Route Switch Processor (RSP) card is running on a Cisco 7507
or Cisco 7513 router, use the slave reload global configuration command.
slave reload
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.1
12.2913)T
12.2(33)SRA
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
After using the slave image global configuration command to specify the image that the slave RSP runs on
a Cisco 7507 or Cisco 7513 router, use the slave reload command to reload the slave with the new image.
The slave reload command can also be used to force the slave to reboot its existing image.
Examples
In the following example, an inactive slave RSP card is reloaded. If the slave reloads, it will return to an
active slave state. If the master RSP fails, the slave RSP will become the master.
c7507(config)# slave reload
Related Commands
Command
Description
show stack s
show version
slave image
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
11.1
12.2(13)T
12.2(33)SRA
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
This command allows you to synchronize the configuration files of the master and slave RSP cards on a
case-by-case basis when you do not have automatic synchronization turned on. This command copies the
masters configuration file to the slave RSP card.
Note
Examples
You must use this command when you insert a new slave RSP card into a Cisco 7507 or Cisco 7513 router
for the first time to ensure that the new slave is configured consistently with the master.
In the following example, the configuration files on the master and slave RSP card are synchronized:
c7507(config)# slave sync config
Related Commands
Command
Description
show stack s
show version
slave terminal
To enable access to the slave Route Switch Processor (RSP) console, use the slave terminal global
configuration command. To disable access to the slave RSP console, use the no form of this command.
slave terminal
no slave terminal
Syntax Description
Command Default
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
11.1
12.2(13)T
12.2(33)SRA
The slave console does not have enable password protection. Thus, an individual connected to the slave
console port can enter privileged EXEC mode and view or erase the configuration of the router. Use the no
slave terminal command to disable slave console access and prevent security problems. When the slave
console is disabled, users cannot enter commands.
If slave console access is disabled, the following message appears periodically on the slave console:
%%Slave terminal access is disabled. Use "slave terminal" command in master RSP
configuration mode to enable it.
Examples
In the following example, the user disables console access to the slave RSP:
c7507(config)# no slave terminal
Related Commands
Command
Description
show stack s
show version
special-character-bits
To configure the number of data bits per character for special characters such as software flow control
characters and escape characters, use the special-character-bits command in line configuration mode. To
restore the default value, use the no form of this command.
special-character-bits {7 | 8}
no special-character-bits
Syntax Description
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Setting the special character bits to 8 allows you to use twice as many special characters as with the 7-bit
ASCII character set. The special characters affected by this setting are the escape, hold, stop, start,
disconnect, and activation characters.
Examples
The following example allows the full 8-bit international character set for special characters on line 5:
Router(config)# line 5
Router(config-line)# special-character-bits 8
Related Commands
Command
Description
default-value exec-character-bits
default-value special-character-bits
Configures the flow control default value from a 7bit width to an 8-bit width.
exec-character-bits
terminal exec-character-bits
terminal special-character-bits
squeeze
To permanently erase files tagged as deleted or error on Class A flash file systems, use the squeeze
command in privileged EXEC mode.
squeeze [/nolog] [/quiet] filesystem:
Cisco 7600 Series Router
squeeze filesystem:
Syntax Description
/nolog
/quiet
filesystem :
Command Modes
Command History
Privileged EXEC
Release
Modification
11.1
12.2(1)
12.0(17)S
12.2(1a)
12.0(17)ST
12.1(9)E
12.2(2)B
Usage Guidelines
Release
Modification
12.2(4)XL
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
When flash memory is full, you might need to rearrange the files so that the space used by the files marked
deleted can be reclaimed. (This squeeze process is required for linear flash memory cards to make
sectors contiguous; the free memory must be in a block to be usable.)
When you enter the squeeze command, the router copies all valid files to the beginning of flash memory
and erases all files marked deleted. After the squeeze process is completed, you can write to the
reclaimed flash memory space.
Caution
After performing the squeeze process, you cannot recover deleted files using the undelete EXEC mode
command.
In addition to removing deleted files, use the squeeze command to remove any files that the system has
marked as error. An error file is created when a file write fails (for example, the device is full). To
remove error files, you must use the squeeze command.
Rewriting flash memory space during the squeeze operation may take several minutes.
Using the /nolog keyword disables the log for the squeeze process. In most cases, this process will speed up
the squeeze process. However, if power is lost or the flash card is removed during the squeeze process, all
the data on the flash card will be lost, and the device will have to be reformatted.
Note
Examples
Supported Platforms Other tha the Cisco 7600 Series Router
In the following example, the file named config1 is deleted, and then the squeeze command is used to
reclaim the space used by that file. The /nolog option is used to speed up the squeeze process.
Router# delete config1
Delete filename [config1]?
Delete slot0:conf? [confirm]
Router# dir slot0:
! Note that the deleted file name appears in square brackets
Directory of slot0:/
1 -rw4300244
Apr 02 2001 03:18:07 c7200-boot-mz.122-0.14
2 -rw2199
Apr 02 2001 04:45:15 [config1]
3 -rw4300244
Apr 02 2001 04:45:23 image
20578304 bytes total (11975232 bytes free)
!20,578,304 - 4,300,244 - 4,300,244 - 2,199 - 385 = 11975232
Router# squeeze /nolog slot0:
%Warning: Using /nolog option would render squeeze operation uninterruptible.
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of slot0 completed in 291.832 secs .
Router# dir slot0:
Directory of slot0:/
1 -rw4300244
Apr 02 2001 03:18:07 c7200-boot-mz.122-0.14
2 -rw4300244
Apr 02 2001 04:45:23 image
20578304 bytes total (11977560 bytes free)
!20,578,304 - 4,300,244 - 4,300,244 - 256 = 11977560
Related Commands
Command
Description
delete
dir
erase
undelete
stack-mib portname
To specify a name string for a port, use the stack-mib portnamecommand in interface configuration mode.
stack-mib portname portname
Syntax Description
portname
Command Default
Command Modes
Interface configuration
Command History
Release
Modification
12.2(14)SX
12.2917d)SXB
12.2(33)SRA
Usage Guidelines
Using the stack-mib command to set a name string to a port corresponds to the portName MIB object in
the portTable of CISCO-STACK-MIB. portName is the MIB object in the portTable of CISCO-STACKMIB. You can set this object to be descriptive text describing the function of the interface.
Examples
state-machine
To specify the transition criteria for the state of a particular state machine, use the state-machine command
in global configuration mode . To remove a particular state machine from the configuration, use the no
form of this command.
state-machine name state first-character last-character [next-state delay | transmit]
no state-machine name
Syntax Description
name
Name for the state machine (used in the dispatchmachine line configuration command). The user
can specify any number of state machines, but each
line can have only one state machine associated
with it.
state
first-character last-character
Command Default
next-state
delay
transmit
Command Modes
Command History
Release
Modification
10.0
12.2(33)SRA
15.0(1)M
Usage Guidelines
This command is paired with the dispatch-machine line configuration command, which defines the line on
which the state machine is effective.
Examples
In the following example a dispatch machine named function is configured to ensure that the function
key characters on an ANSI terminal are kept in one packet. Because the default in the example is to remain
in state 0 without sending anything, normal key signals are sent immediately.
Router(config)# line 1 20
Router(config-line)# dispatch-machine function
Router(config-line)# exit
Router(config)# state-machine function 0 0 255 6 transmit
Related Commands
Command
Description
dispatch-character
dispatch-machine
dispatch-timeout
stopbits
To set the number of the stop bits transmitted per byte, use the stopbits command in line configuration
mode. To restore the default value, use the no form of this command.
stopbits {1 | 1.5 | 2}
no stopbits
Syntax Description
1.5
Command Default
Command Modes
Line configuration
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific stopbit setting.
Examples
In the following example, the stop bits transmitted per byte are changed from the default of two stop bits to
one stop bit as a performance enhancement for line 4:
Router(config)# line 4
Router(config-line)# stopbits 1
Related Commands
Command
Description
terminal stopbits
storm-control level
To set the suppression level, use the storm-control level command in interface configuration mode. To
turn off the suppression mode, use the no form of this command.
storm-control {broadcast | multicast | unicast} level level [. level]
no storm-control {broadcast | multicast | unicast} level
Syntax Description
broadcast
multicast
unicast
level
. level
Command Default
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
You can enter this command on switch ports and router ports.
Enter the storm-control level command to enable traffic storm control on the interface, configure the
traffic storm-control level, and apply the traffic storm-control level to all traffic storm-control modes that
are enabled on the interface.
Only one suppression level is shared by all three suppression modes. For example, if you set the broadcast
level to 30 and set the multicast level to 40, both levels are enabled and set to 40.
The Cisco 7600 series router supports storm control for multicast and unicast traffic only on Gigabit
Ethernet LAN ports. The switch supports storm control for broadcast traffic on all LAN ports.
The multicast and unicast keywords are supported on Gigabit Ethernet LAN ports only. These keywords
are not supported on 10 Mbps, 10/100 Mbps, 100 Mbps, or 10-Gigabit Ethernet modules.
The period is required when you enter the fractional-suppression level.
The suppression level is entered as a percentage of the total bandwidth. A threshold value of 100 percent
means that no limit is placed on traffic. A threshold value of 0 or 0.0 (fractional) percent means that all
specified traffic is blocked on a port, with the following guidelines:
A fractional level value of 0.33 or lower is the same as 0.0 on the following modules:
WS-X6704-10GE
WS-X6748-SFP
WS-X6724-SFP
WS-X6748-GE-TX
A fractional level value of 0.29 or lower is the same as 0.0 on the WS-X6716-10G-3C / 3CXL in
Oversubscription Mode.
Enter 0 on all other modules to block all specified traffic on a port.
Enter the show interfaces counters broadcast command to display the discard count.
Enter the show running-config command to display the enabled suppression mode and level setting.
To turn off suppression for the specified traffic type, you can do one of the following:
Examples
Set the level to 100 percent for the specified traffic type.
Use the no form of this command.
This example shows how to enable and set the suppression level:
Router(config-if)#
storm-control broadcast level 30
Related Commands
Command
Description
show running-config
sync-restart-delay
To set the synchronization-restart delay timer to ensure accurate status reporting, use the sync-restartdelay command in interface configuration mode. To disable the synchronization-restart delay timer, use the
no form of this command.
sync-restart-delay timer
no sync-restart-delay timer
Syntax Description
timer
Command Default
Command Modes
Interface configuration
Command History
Usage Guidelines
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
Examples
This example shows how to set the Gigabit Ethernet synchronization-restart delay timer:
Router(config-if)# sync-restart-delay 2000
Related Commands
Command
Description
show running-config
systat
Note
Syntax Description
Command Modes
Command History
Examples
Release
Modification
15.0(1)M
12.2(33)SRB
12.2(33)SXI
Related Commands
all
Host(s)
idle
Idle
Mode
Location
00:00:00
Idle
Peer Address
Command
Description
show users
Syntax Description
default
auto
on
Command Default
auto
Command Modes
Global configuration
Command History
Release
Modification
12.2(18)SXF
12.2(33)SRA
Usage Guidelines
Note
We recommend that you leave the system flow control in auto mode and use the other modes under the
advice of Cisco TAC only.
Examples
This example shows how to monitor the FIFO overflow error count and send a warning message if the
FIFO overflow error count exceeds a configured error threshold in 5-second intervals:
Router(config)# system flowcontrol bus auto
This example shows how to specify the original FIFO threshold settings:
Router(config)# system flowcontrol bus on
system jumbomtu
To set the maximum size of the Layer 2 and Layer 3 packets, use the system jumbomtu command in global
configuration mode. To revert to the default MTU setting, use the no form of this command.
system jumbomtu mtu-size
no system jumbomtu
Syntax Description
mtu-size
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
1.2(14)SX
12.2(17d)SXB
12.2(33)SRA
The mtu-size parameter specifies the Ethernet packet size, not the total Ethernet frame size. The Layer 3
MTU is changed as a result of entering the system jumbomtucommand.
The system jumbomtucommand enables the global MTU for port ASICs. On a port ASIC after jumbo
frames are enabled, the port ASIC accepts any size packet on the ingress side and checks the outgoing
packets on the egress side. The packets on the egress side that exceed the global MTU are dropped by the
port ASIC.
For example, if you have port A in VLAN 1 and Port B in VLAN 2, and if VLAN 1 and VLAN 2 are
configured for mtu 9216 and you enter the system jumbomtu 4000 command, the packets that are larger
than 4000 bytes are not transmitted out because Ports B and A drop anything larger than 4000 bytes.
Examples
This example shows how to set the global MTU size to 1550 bytes:
Router(config)# system jumbomtu 1550
Related Commands
Command
Description
mtu
show interfaces
Syntax Description
priority-number
slot / ds1-port
external
freerun
Command Default
If no clocks are configured, the system uses a default, primary clock. An external clock is never selected by
default; it must be explicitly configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Release
Modification
12.2(8)T
12.2(33)SRA
The TDM bus can receive an input clock from one of three sources on the gateway:
Note
BITS is a single building master timing supply. BITS generally supplies DS1- and DS0-level timing
throughout an office. BITS is the clocks that provide and distribute timing to a wireline networks lower
levels.
Trunk-Card Ports
The TDM bus can be synchronized with any trunk cards. On the CT1/CE1 trunk card, each port receives
the clock from the T1/E1 line. The CT3 trunk card uses an M13 multiplexer to receive the DS1 clock. Each
port on each trunk-card slot has a default clock priority. Also, clock priority is configurable through the
tdm clock priority command.
External Clock
The TDM bus can be synchronized with an external clock source that can be used as an additional network
reference. If no clocks are configured, the system uses a primary clock through a software-controlled
default algorithm. If you want the external T1/E1 clock (from the BITS interface) as the primary clock
source, you must configure it using the external keyword with the tdm clock priority command; the
external clock is never selected by default.
The BITS interface requires a T1 line composite clock reference set at 1.544 MHz and an E1 line
composite clock reference set at 2.048 MHz.
Free-Running Clock
If there is no good clocking source from a trunk card or an external clock source, then select the freerunning clock from the internal oscillator using the freerun keyword with the tdm clock priority
command.
Examples
In the following example, a trunk clock from a CT1 trunk card is set at priority 2 and uses slot 4 and DS1
port (controller) 6:
AS5400(config)# tdm clock priority priority 2 4/6
In the following example, a trunk clock from a CT3 trunk card is set at priority 2 and uses slot 1, DS3 port
0, and DS1 port 19:
AS5400(config)# tdm clock priority priority 2 1/0:19
Related Commands
Command
Description
dial-tdm-clock
terminal databits
To change the number of data bits per character for the current terminal line for this session, use the
terminal databits command in EXEC mode.
terminal databits {5 | 6 | 7 | 8}
Syntax Description
Command Default
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific data
bit setting. The terminal databits command can be used to mask the high bit on input from devices that
generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity
generation is in effect, specify 8 data bits per character. The other keywords (5 and 6) are supplied for
compatibility with older devices and are generally not used.
Examples
In the following example, the databits per character is changed to seven for the current session:
Router# terminal databits 7
Related Commands
Command
Description
databits
terminal parity
terminal data-character-bits
To set the number of data bits per character that are interpreted and generated by the Cisco IOS software
for the current line and session, use the terminal data-character-bits command in EXEC mode.
terminal data-character-bits {7 | 8}
Syntax Description
Command Default
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command is used primarily to strip parity from X.25 connections on routers with the protocol
translation software option. The terminal data-character-bits command does not work on hard-wired
lines.
Examples
The following example sets the data bits per character to seven on the current line:
Router# terminal data-character-bits 7
Related Commands
Command
Description
data-character-bits
terminal dispatch-character
To define a character that causes a packet to be sent for the current session, use the terminal dispatchcharacter command in EXEC mode.
terminal dispatch-character ascii-number [ascii-number2...]
Syntax Description
Command Modes
Command History
ascii-number
ascii-number2...
EXEC
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
At times, you might want to queue up a string of characters until they fill a complete packet and then
transmit the packet to a remote host. This can make more efficient use of a line, because the access server
or router normally dispatches each character as it is entered.
Examples
The following example defines the characters Ctrl-D (ASCII decimal character 4) and Ctrl-Y (ASCII
decimal character 25) as the dispatch characters:
Router# terminal dispatch-character 4 25
Related Commands
Command
Description
dispatch-character
terminal dispatch-timeout
To set the character dispatch timer for the current terminal line for the current session, use the terminal
dispatch-timeout command in EXEC mode.
terminal dispatch-timeout milliseconds
Syntax Description
Command Modes
Command History
Usage Guidelines
milliseconds
EXEC
Release
Modification
10.0
12.2(33)SRA
Use this command to increase the processing efficiency of the remote host.
The dispatch-timeout line configuration command causes the software to buffer characters into packets for
transmission to the remote host. The Cisco IOS software sends a packet a specified amount of time after the
first character is put into the buffer. You can use the terminal dispatch-timeoutand terminal dispatchcharacter line configuration commands together. In this case, the software dispatches a packet each time
the dispatch character is entered, or after the specified dispatch timeout interval, depending on which
condition is met first.
Note
Examples
The router response time might appear intermittent if the timeout interval is greater than 100 milliseconds
and remote echoing is used.
Related Commands
Command
Description
dispatch-timeout
terminal download
To temporarily set the ability of a line to act as a transparent pipe for file transfers for the current session,
use the terminal download command in EXEC mode.
terminal download
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
You can use this feature to run a program such as KERMIT, XMODEM, or CrossTalk that downloads a
file across an access server or router line. This command configures the terminal line to send data and is
equivalent to entering all the following commands:
Examples
terminal editing
To reenable the enhanced editing mode for only the current terminal session, use the terminal editing
command in EXEC mode. To disable the enhanced editing mode on the current line, use the no form of this
command.
terminal editing
terminal no editing
Syntax Description
Command Default
Enabled
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This command is identical to the editing EXEC mode command, except that it controls (enables or
disables) enhanced editing for only the terminal session you are using. For a description of the available
editing keys, see the description of the editing command in this document.
Examples
In the following example, enhanced editing mode is reenabled for only the current terminal session:
Router> terminal editing
Related Commands
Command
Description
editing
terminal escape-character
To set the escape character for the current terminal line for the current session, use the terminal escapecharacter command in EXEC mode.
terminal escape-character ascii-number
Syntax Description
ascii-number
Command Default
Ctrl-^ (Ctrl-Shift-6)
Command Modes
EXEC
Command History
Usage Guidelines
Note
Examples
Release
Modification
10.0
12.2(33)SRA
See the "ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters and their
numerical representation.
This command is useful, for example, if you have the default escape character defined for a different
purpose in your keyboard file. Entering the escape character followed by the X key returns you to EXEC
mode when you are connected to another computer.
The Break key generally cannot be used as an escape character on the console terminal because the
operating software interprets the Break command on a console line as an instruction to halt the system.
In the following example, the escape character to Ctrl-P (ASCII decimal character 16) for the current
session:
Router# terminal escape-character 16
Related Commands
Command
Description
escape-character
terminal exec-character-bits
To locally change the ASCII character set used in EXEC and configuration command characters for the
current session, use the terminal exec-character-bits command in EXEC mode.
terminal exec-character-bits {7 | 8}
Syntax Description
Command Default
7-bit ASCII character set (unless set otherwise in global configuration mode)
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
This EXEC command overrides the default-value exec-character-bits global configuration command.
Configuring the EXEC character width to 8 bits enables you to view special graphical and international
characters in banners, prompts, and so on.
When the user exits the session, the character width is reset to the default value established by the execcharacter-bits global configuration command. However, setting the EXEC character width to 8 bits can
also cause failures. For example, if a user on a terminal that is sending parity enters the help command, an
unrecognized command message appears because the system is reading all 8 bits, and the eighth bit is not
needed for the help command.
Examples
The following example temporarily configures the system to use a full 8-bit user interface for system
banners and prompts, allowing the use of additional graphical and international characters:
Router# terminal exec-character-bits 8
Related Commands
Command
Description
exec-character-bits
terminal flowcontrol
To set flow control for the current terminal line for the current session, use the terminal flowcontrol
command in EXEC mode.
terminal flowcontrol {none | software[in | out] | hardware}
Syntax Description
Command Modes
Command History
Usage Guidelines
none
software
in | out
hardware
EXEC
Release
Modification
10.0
12.2(33)SRA
Flow control enables you to regulate the rate at which data can be transmitted from one point so that it is
equal to the rate at which it can be received at another point. Flow control protects against loss of data
because the terminal is not capable of receiving data at the rate it is being sent. You can set up data flow
control for the current terminal line in one of two ways: software flow control, which you do with control
key sequences, and hardware flow control, which you do at the device level.
For software flow control, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON).
You can change them with the terminal stop-character and terminal start-character EXEC commands.
Examples
In the following example, incoming software flow control is set for the current session:
Router# terminal flowcontrol software in
Related Commands
Command
Description
flowcontrol
terminal full-help
To get help for the full set of user-level commands, use the terminal full-help command in EXEC mode.
terminal full-help
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The terminal full-help command enables a user to see all of the help messages available from the terminal.
It is used with the show ? command.
Examples
In the following example, the difference between the output of the show ? command before and after using
the terminal full-help command is shown:
Router> show
bootflash
calendar
clock
context
dialer
history
hosts
isdn
kerberos
modemcap
ppp
rmon
sessions
snmp
terminal
users
version
?
Boot Flash information
Display the hardware calendar
Display the system clock
Show context information
Dialer parameters and statistics
Display the session command history
IP domain-name, lookup style, nameservers, and host table
ISDN information
Show Kerberos Values
Show Modem Capabilities database
PPP parameters and statistics
rmon statistics
Information about Telnet connections
snmp statistics
Display terminal configuration parameters
Display information about terminal lines
System hardware and software status
Related Commands
Command
Description
full-help
help
terminal history
To enable the command history function with 10 lines for the current terminal session, use the terminal
history command in user EXEC or privileged EXEC mode. To disable the command history function, use
the no form of this command.
terminal history
terminal no history
Syntax Description
Command Default
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The history function provides a record of commands you have entered. This function is particularly useful
for recalling long or complex commands or entries for the purposes of modifying them slightly and
reexecuting them.
The terminal history command enables the command history function with the default buffer size or the
last buffer size specified using the terminal history size command.
The following table lists the keys and functions you can use to recall commands from the history buffer.
Table 175
Examples
History Keys
Key(s)
Function
Ctrl-P or Up Arrow4
In the following example, the command history feature is disabled for the current terminal session:
Router> terminal no history
Related Commands
Command
Description
history
show history
Syntax Description
number-of-lines
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The history feature provides a record of commands you have entered. This feature is particularly useful for
recalling long or complex commands or entries for the purposes of modifying them slightly and reissuing
them.
The terminal history size command enables the command history feature and sets the command history
buffer size. The terminal no history size command resets the buffer size to the default of 10 command
lines.
The following table lists the keys and functions you can use to recall commands from the history buffer.
When you use these keys, the commands recalled will be from EXEC mode if you are in EXEC mode, or
from all configuration modes if you are in any configuration mode.
Table 176
History Keys
Key
Function
Ctrl-P or Up Arrow5
In EXEC mode, you can also use the show history command to show the contents of the command history
buffer.
To check the current settings for the command history feature on your line, use the show line command.
Examples
In the following example, the number of command lines recorded is set to 15 for the current terminal
session. The user then checks to see what line he/she is connected to using the show users command. The
user uses this line information to issue the show line command. (In this example, the user uses the show
begin option in the show line command to start the output at the Editing is enabled/disabled line.)
Router# terminal history size 15
Router# show users
Line
User
Host(s)
Idle
Location
* 50 vty 0
admin
idle
00:00:00
! the * symbol indicates the active terminal session for the user (line 50)
Router# show line 50 | begin Editing
Editing is enabled.
! the following line shows the history settings for the line
History is enabled, history size is 15.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed transports are telnet. Preferred is none.
No output characters are padded
No special data dispatching characters
Related Commands
Command
Description
history
Command
Description
show history
terminal history
terminal hold-character
To define the hold character for the current session, use the terminal hold-character command in EXEC
mode. To return the hold character definition to the default, use the no form of this command.
terminal hold-character ascii-number
terminal no hold-character
Syntax Description
ascii-number
Command Default
The default hold character is defined by the hold-character global configuration command.
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
You can define a local hold character that temporarily suspends the flow of output on the terminal. When
information is scrolling too quickly, you can enter the hold character to pause the screen output, then enter
any other character to resume the flow of output.
You cannot suspend output on the console terminal. To send the hold character to the host, precede it with
the escape character.
Examples
In the following example, the hold character for the current (local) session is set to Ctrl-P. The show
terminal output is included to show the verification of the setting (the value for the hold character is shown
in the Special Characters listing).
Router# terminal hold-character 16
"^P" is the local hold character
Router# show terminal
Line 50, Location: "", Type: "VT220"
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600
Status: PSI Enabled, Ready, Active, No Exit Banner, Automore On
Capabilities: none
Modem state: Ready
Group codes:
0
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x
^P
none
Timeouts:
Idle EXEC
Idle Session
Modem Answer Session
00:10:00
never
none
Idle Session Disconnect Warning
never
Login-sequence User Response
00:00:30
Autoselect Initial Wait
not set
Modem type is unknown.
Session limit is not set.
Time since activation: 00:04:13
Editing is enabled.
History is enabled, history size is 10.
.
.
.
Related Commands
Command
Description
hold-character
show terminal
Dispatch
not set
terminal international
If you are using Telnet to access a Cisco IOS platform and you want to display 8-bit and multibyte
international characters (for example, Kanji) and print the Escape character as a single character instead of
as the caret and bracket symbols (^[) for a current Telnet session, use the terminal international command
in user EXEC or priviledged mode. To display characters in 7-bit format for a current Telnet session, use
the no form of this command.
terminal international
no terminal international
Syntax Description
Command Default
Disabled
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
11.3
12.2(33)SRA
Usage Guidelines
If you are configuring a Cisco IOS platform using the Cisco web browser UI, this feature is enabled
automatically when you enable the Cisco web browser UI using the ip http server global configuration
command.
Examples
The following example enables a Cisco IOS platform to display 8-bit and multibyte characters and print the
Escape character as a single character instead of as the caret and bracket symbols (^[) when you are using
Telnet to access the platform for the current Telnet session:
Router# terminal international
Related Commands
Command
Description
international
terminal keymap-type
To specify the current keyboard type for the current session, use the terminal keymap-type command in
EXEC mode.
terminal keymap-type keymap-name
Syntax Description
keymap-name
Command Default
VT100
Command Modes
EXEC
Command History
Release
Modification
11.2
12.2(33)SRA
Usage Guidelines
You must use this command when you are using a keyboard other than the default of VT100.
Examples
The following example specifies a VT220 keyboard as the current keyboard type:
Router# terminal keymap-type vt220
Related Commands
Command
Description
show keymap
terminal length
To set the number of lines on the current terminal screen for the current session, use the terminal length
command in EXEC, privileged EXEC, and diagnostic mode.
terminal length screen-length
Syntax Description
screen-length
Command Default
24 lines
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The system uses the length value to determine when to pause during multiple-screen output. A value of
zero prevents the router from pausing between screens of output.
Some types of terminal sessions do not require you to specify the screen length because the screen length
specified can be learned by some remote hosts. For example, the rlogin protocol uses the screen length to
set up terminal parameters on a remote UNIX host.
Examples
In the following example, the system is configured to prevent output from pausing if it exceeds the length
of the screen:
Router# terminal length 0
Related Commands
Command
Description
length
terminal monitor
To display debug command output and system error messages for the current terminal and session, use the
terminal monitor command in EXEC mode.
terminal monitor
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Remember that all terminal parameter-setting commands are set locally and do not remain in effect after a
session is ended.
Examples
In the following example, the system is configured to display debug command output and error messages
during the current terminal session:
Router# terminal monitor
terminal notify
To enable terminal notification about pending output from other Telnet connections for the current session,
use the terminal notify command in EXEC mode. To disable notifications for the current session, use the
no form of this command.
terminal notify
terminal no notify
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Enabling notifications may be useful if, for example, you want to know when another connection receives
mail, or when a process has been completed.
This command enables or disables notifications for only the current session. To globally set these
notifications, use the notify line configuration command.
Examples
In the following example, notifications will be displayed to inform the user when output is pending on
another connection:
Router# terminal notify
Related Commands
Command
Description
notify
terminal padding
To change the character padding on a specific output character for the current session, use the terminal
padding command in EXEC mode.
terminal padding ascii-number count
Syntax Description
ascii-number
count
Command Default
No padding
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Character padding adds a number of null bytes to the end of the string and can be used to make a string an
expected length for conformity.
Use this command when the attached device is an old terminal that requires padding after certain characters
(such as ones that scrolled or moved the carriage). See the "ASCII Character Set and Hexidecimal Values"
appendix for a list of ASCII characters.
Examples
The following example pads Ctrl-D (ASCII decimal character 4) with 164 NULL bytes:
Router# terminal padding 4 164
Related Commands
Command
Description
padding
terminal parity
To define the generation of the parity bit for the current terminal line and session, use the terminal parity
command in EXEC mode.
terminal parity {none | even | odd | space | mark}
Syntax Description
none
even
Even parity.
odd
Odd parity.
space
Space parity.
mark
Mark parity.
Command Default
No parity.
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Communication protocols provided by devices such as terminals and modems will sometimes require a
specific parity bit setting. Refer to the documentation for your device to determine required parity settings.
Examples
In the following example, odd parity checking is enabled for the current session:
Router# terminal parity odd
Related Commands
Command
Description
parity
terminal rxspeed
To set the terminal receive speed (how fast information is sent to the terminal) for the current line and
session, use the terminal rxspeed command in EXEC mode.
terminal rxspeed bps
Syntax Description
bps
Command Default
9600 bps
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Set the speed to match the baud rate of whatever device you have connected to the port. Some baud rates
available on devices connected to the port might not be supported on the system. The system will indicate if
the speed you select is not supported.
Examples
The following example sets the current auxiliary line receive speed to 115200 bps:
Router# terminal rxspeed 115200
Related Commands
Command
Description
rxspeed
terminal rxspeed
Command
Description
terminal txspeed
terminal speed
terminal special-character-bits
To change the ASCII character widths to accept special characters for the current terminal line and session,
use the terminal special-character-bits command in EXEC mode.
terminal special-character-bits 7 | 8
Syntax Description
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Configuring the width to 8 bits enables you to use twice as many special characters as with the 7-bit setting.
This selection enables you to add special graphical and international characters in banners, prompts, and so
on.
This command is useful, for example, if you want the router to provide temporary support for international
character sets. It overrides the default-value special-character-bits global configuration command and is
used to compare character sets typed by the user with the special character available during a data
connection, which includes software flow control and escape characters.
When you exit the session, character width is reset to the width established by the default-value execcharacter-bits global configuration command.
Note that setting the EXEC character width to eight bits can cause failures. For example, if a user on a
terminal that is sending parity enters the help command, an unrecognized command message appears
because the Cisco IOS software is reading all eight bits, and the eighth bit is not needed for the help
command.
Examples
The following example temporarily configures a router to use a full 8-bit user interface for system banners
and prompts.
Router# terminal special-character-bits 8
Related Commands
Command
Description
default-value exec-character-bits
special-character-bits
terminal speed
To set the transmit and receive speeds of the current terminal line for the current session, use the terminal
speed command in EXEC mode.
terminal speed bps
Syntax Description
bps
Command Default
9600 bps
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Set the speed to match the transmission rate of whatever device you have connected to the port. Some baud
rates available on devices connected to the port might not be supported on the router. The router indicates
whether the speed you selected is not supported.
Examples
The following example restores the transmit and receive speed on the current line to 9600 bps:
Router# terminal speed 9600
Related Commands
Command
Description
speed
terminal start-character
To change the flow control start character for the current session, use the terminal start-character
command in EXEC mode.
terminal start-character ascii-number
Syntax Description
ascii-number
Command Default
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The flow control start character signals the start of data transmission when software flow control is in
effect.
Examples
The following example changes the start character to Ctrl-O (ASCII decimal character 15):
Router# terminal start-character 15
Related Commands
Command
Description
start-character
terminal stopbits
To change the number of stop bits sent per byte by the current terminal line during an active session, use
the terminal stopbits command in EXEC mode.
terminal stopbits {1 | 1.5 | 2}
Syntax Description
1.5
Command Default
2 stop bits
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific stopbit setting.
Examples
In the following example, the setting for stop bits is changed to one for the current session:
Router# terminal stopbits 1
Related Commands
Command
Description
stopbits
terminal stop-character
To change the flow control stop character for the current session, use the terminal stop-character
command in EXEC mode.
terminal stop-character ascii-number
Syntax Description
ascii-number
Command Default
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The flow control stop character signals the end of data transmission when software flow control is in effect.
See the "ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters.
Examples
In the following example, the stop character is configured as Ctrl-E (ASCII character decimal 5) for the
current session:
Router# terminal stop-character 5
Related Commands
Command
Description
stop-character
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
The hardware Break signal occurs when a Telnet interrupt-process (ip) command is received on that
connection. The terminal telnet break-on-ip command can be used to control the translation of Telnet
interrupt-process commands into X.25 Break indications.
In this command, the acronym ip indicates interrupt-process, not Internet Protocol (IP).
This command is also a useful workaround in the following situations:
Several user Telnet programs send an ip command, but cannot send a Telnet Break signal.
Some Telnet programs implement a Break signal that sends an ip command.
Some EIA/TIA-232 hardware devices use a hardware Break signal for various purposes. A hardware Break
signal is generated when a Telnet Break command is received.
You can verify if this command is enabled with the show terminal EXEC command. If enabled the
following line will appear in the output: Capabilities: Send BREAK on IP .
Examples
In the following example, a Break signal is generated for the current connection when an interrupt-process
command is issued:
Router# terminal telnet break-on-ip
Related Commands
Command
Description
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
You can set the line to allow access server to refuse full-duplex, remote echo connection requests from the
other end . This command suppresses negotiation of the Telnet Remote Echo and Suppress Go Ahead
options.
Examples
In the following example, the current session is configured to refuse full-duplex, remote echo requests:
Router# terminal telnet refuse-negotiations
Syntax Description
default-speed
maximum-speed
Command Default
9600 bps (unless otherwise set using the speed, txspeed or rxspeed line configuration commands)
Command Modes
EXEC
Command History
Usage Guidelines
Note
Release
Modification
10.0
12.2(33)SRA
You can match line speeds on remote systems in reverse Telnet, on host machines connected to an access
server to access the network, or on a group of console lines connected to the access server when disparate
line speeds are in use at the local and remote ends of the connections listed above. Line speed negotiation
adheres to the Remote Flow Control option, defined in RFC 1080.
This command applies only to access servers. It is not supported on standalone routers.
Examples
The following example enables the access server to negotiate a bit rate on the line using the Telnet option.
If no speed is negotiated, the line will run at 2400 bps. If the remote host requests a speed greater than 9600
bps, then 9600 bps will be used.
Router# terminal telnet speed 2400 9600
Syntax Description
Command Default
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Note
Examples
Release
Modification
10.0
12.2(33)SRA
You can configure the session to cause a reverse Telnet line to send a Telnet Synchronize signal when it
receives a Telnet Break signal. The TCP Synchronize signal clears the data path, but still interprets
incoming commands.
This command applies only to access servers. It is not supported on standalone routers.
The following example sets an asynchronous line to cause the access server to send a Telnet Synchronize
signal:
Router# terminal telnet sync-on-break
Syntax Description
Command Default
CR followed by an LF
Command Modes
EXEC
Command History
Usage Guidelines
Note
Examples
Release
Modification
10.0
12.2(33)SRA
The end of each line typed at the terminal is ended with a Return (CR). This command permits
interoperability with different interpretations of end-of-line demarcation in the Telnet protocol
specification.
This command applies only to access servers. It is not supported on stand-alone routers.
In the following example, the session is configured to send a CR signal as a CR followed by a NULL:
Router# terminal telnet transparent
terminal terminal-type
To specify the type of terminal connected to the current line for the current session, use the terminal
terminal-type command in EXEC, privileged EXEC, and diagnostic mode.
terminal terminal-type terminal-type
Syntax Description
terminal-type
Command Default
VT100
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
Examples
In the following example, the terminal type is defined as VT220 for the current session:
Router# terminal terminal-type VT220
Related Commands
Command
Description
terminal keymap-type
terminal-type
terminal txspeed
To set the terminal transmit speed (how fast the terminal can send information) for the current line and
session, use the terminal txspeed command in EXEC mode.
terminal txspeed bps
Syntax Description
bps
Command Default
9600 bps
Command Modes
EXEC
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
In the following example, the line transmit speed is set to 2400 bps for the current session:
Router# terminal txspeed 2400
Related Commands
Command
Description
rxspeed
terminal rxspeed
terminal terminal-type
txspeed
terminal width
To set the number of character columns on the terminal screen for the current line for a session, use the
terminal width command in EXEC, privileged EXEC, or diagnostic mode.
terminal width characters
Syntax Description
characters
Command Default
80 characters
Command Modes
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
By default, the route provides a screen display width of 80 characters. You can reset this value for the
current session if it does not meet the needs of your terminal.
The rlogin protocol uses the value of the characters argument to set up terminal parameters on a remote
host.
Examples
Related Commands
Command
Description
width
terminal-queue entry-retry-interval
To change the retry interval for a terminal port queue, use the terminal-queue entry-rety-interval
command in global configuration mode. To restore the default terminal port queue interval, use the no form
of this command.
terminal-queue entry-retry-interval seconds
no terminal-queue entry-retry-interval
Syntax Description
seconds
Command Default
60 seconds
Command Modes
Global configuration
Command History
Release
Modification
11.1
12.2(33)SRA
Usage Guidelines
If a remote device (such as a printer) is busy, the connection attempt is placed in a terminal port queue. If
you want to decrease the waiting period between subsequent connection attempts, decrease the default of
60 to an interval of 10 seconds. Decrease the time between subsequent connection attempts when, for
example, a printer queue stalls for long periods.
Examples
The following example changes the terminal port queue retry interval from the default of 60 seconds to 10
seconds:
Router# terminal-queue entry-retry-interval 10
terminal-type
To specify the type of terminal connected to a line, use the terminal-type command in line configuration
mode. To remove any information about the type of terminal and reset the line to the default terminal
emulation, use the no form of this command.
terminal-type {terminal-name | terminal-type}
no terminal-type
Syntax Description
terminal-name
Terminal name.
terminal-type
Terminal type.
Command Default
VT100
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
This command records the type of terminal connected to the line. The terminal-nameargument provides a
record of the terminal type and allows terminal negotiation of display management by hosts that provide
that type of service.
For TN3270 applications, this command must follow the corresponding ttycap entry in the configuration
file.
Examples
test cable-diagnostics
To test the condition of 10-Gigabit Ethernet links or copper cables on 48-port 10/100/1000 BASE-T
modules, use the test cable-diagnosticscommand in privileged EXEC mode.
test cable-diagnostics tdr interface type number
Syntax Description
tdr
interface type
number
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(17a)SX
12.2(17b)SXA
12.2(17d)SXB
12.2(33)SRA
Cable diagnostics can help you detect whether your cable has connectivity problems.
The TDR test guidelines are as follows:
6500 and Cisco 7600 Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2 for the
list of the modules that support TDR.
The valid values for interface typeare fastethernet and gigabitethernet.
Do not start the test at the same time on both ends of the cable. Starting the test at both ends of the
cable at the same time can lead to false test results.
Do not change the port configuration during any cable diagnostics test. This action may result in
incorrect test results.
The interface must be up before running the TDR test. If the port is down, the test cable-diagnostics
tdr command is rejected and the following message is displayed:
Examples
If the port speed is 1000 and the link is up, do not disable the auto-MDIX feature.
For fixed 10/100 ports, before running the TDR test, disable auto-MDIX on both sides of the cable.
Failure to do so can lead to misleading results.
For all other conditions, you must disable the auto-MDIX feature on both ends of the cable (use the no
mdix autocommand). Failure to disable auto-MDIX will interfere with the TDR test and generate
false results.
If a link partner has auto-MDIX enabled, this action will interfere with the TDR-cable diagnostics test
and test results will be misleading. The workaround is to disable auto-MDIX on the link partner.
If you change the port speed from 1000 to 10/100, enter the no mdix autocommand before running the
TDR test. Note that entering the speed 1000 command enables auto-MDIX regardless of whether the
no mdix autocommand has been run.
Related Commands
Command
Description
test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash command in EXEC
mode.
test flash
Syntax Description
Command Default
Command Modes
EXEC
Command History
Examples
Release
Modification
10.0
12.2(33)SRA
Related Commands
Command
Description
test interfaces
test memory
test interfaces
To test the system interfaces on the modular router, use the test interfaces command in EXEC mode.
test interfaces
Syntax Description
Command Default
Command Modes
EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The test interfaces EXEC command is intended for the factory checkout of network interfaces. It is not
intended for diagnosing problems with an operational router. The test interfaces output does not report
correct results if the router is attached to a live network. For each network interface that has an IP address
that can be tested in loopback (MCI and ciscoBus Ethernet and all serial interfaces), the test interfaces
command sends a series of ICMP echoes. Error counters are examined to determine the operational status
of the interface.
Examples
Related Commands
Command
Description
test flash
Command
Description
test memory
test memory
To perform a test of Multibus memory (including nonvolatile memory) on the modular router, use the test
memory command in privileged EXEC mode. The memory test overwrites memory.
test memory
Syntax Description
Command Default
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
12.2(33)SRA
Usage Guidelines
The memory test overwrites memory. If you use the test memory command, you will need to rewrite
nonvolatile memory. For example, if you test Multibus memory, which is the memory used by the CSC-R
4-Mbps Token Ring interfaces, you will need to reload the system before the network interfaces will
operate properly. The test memory command is intended primarily for use by Cisco personnel.
Examples
Related Commands
Command
Description
test flash
test interfaces
Syntax Description
chunk
mgd-chunk
force-chunk
dangling-reference
chunk-id
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
Examples
Release
Modification
12.2(33)SRC
The force-chunk keyword destroys a chunk of ordinary (not managed) memory, even if the memory has
elements or siblings that are not free.
Use the force-chunk keyword carefully. A crash or corruption will occur if someone refers to the destroyed
chunk or its elements.
Related Commands
Command
Description
Syntax Description
Command Default
Command Modes
Command History
Release
Modification
12.2(33)SRD1
Usage Guidelines
Use this command under the exec command of the line card console. It is not visible from the route
processor (RP) console.
Examples
The following example shows how to get the IPv6 internal police rate:
Router> enable
Router# test platform police get
IPv6 with HBH header is policed at 100000 kbps
Related Commands
Command
Description
Syntax Description
rate
Command Default
For ES40 line cards, the default police rate is 12.8 Mbps.
For the SIP-400, the default police rate is 21.36 kpps.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.2(33)SRD1
Use this command under the EXEC command of the line card console. It is not visible from the route
processor (RP) console.
Note
There is not a no version of this command. If you have set a rate limit and wish to cancel it, you will need
to use this command to set the rate to 0.
For both the ES+ line cards and the SIP-400, setting the police rate to 0 turns off the policing.
For both the ES+ line cards and the SIP-400, when the policer is set from the the line card console, the
setting remains effective even if the line card is moved to another chassis running the Cisco IOS Release
12.2(33)SRD1 (or later) image.
For the SIP-400, IPv6 HBH packets will continue to go through the QoS policing configured on the line
card. For ES+ line cards, IPv6 HBH packets will bypass any QoS configured on the line card.
Examples
The following examples shows how to set the IPv6 with HBH header to be policed at 100000 kbps:
Router> enable
Router# test platform police set 100000
Related Commands
Command
Description
tftp-server
To configure a router or a Flash memory device on the router as a TFTP server, use one of the following
tftp-server commands in global configuration mode. This command replaces the tftp-server system
command. To remove a previously defined filename, use the no form of this command with the appropriate
filename.
tftp-server flash [partition-number :] filename1 [alias filename2] [access-list-number]
tftp-server rom alias filename1 [access-list-number]
no tftp-server {flash [partition-number :] filename1 | rom alias filename2}
Cisco 1600 Series and Cisco 3600 Series Routers
tftp-server flash [device :] [partition-number :] filename
no tftp-server flash [device :] [partition-number :] filename
Cisco 7000 Family Routers
tftp-server flash device : filename
no tftp-server flash device : filename
Syntax Description
flash
rom
filename1
alias
filename2
access-list-number
partition-number :
device :
filename
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.0
12.2(33)SRA
Usage Guidelines
You can specify multiple filenames by repeating the tftp-server command. The system sends a copy of the
system image contained in ROM or one of the system images contained in Flash memory to any client that
issues a TFTP Read Request with this filename.
If the specified filename1or filename2argument exists in Flash memory, a copy of the Flash image is sent.
On systems that contain a complete image in ROM, the system sends the ROM image if the specified
filename1or filename2argument is not found in Flash memory.
Images that run from ROM cannot be loaded over the network. Therefore, it does not make sense to use
TFTP to offer the ROMs on these images.
On the Cisco 7000 family routers, the system sends a copy of the file contained on one of the Flash
memory devices to any client that issues a TFTP Read Request with its filename.
Examples
In the following example, the system uses TFTP to send a copy of the version-10.3 file located in Flash
memory in response to a TFTP Read Request for that file. The requesting host is checked against access list
22.
tftp-server flash version-10.3 22
In the following example, the system uses TFTP to send a copy of the ROM image gs3-k.101in response to
a TFTP Read Request for the gs3-k.101 file:
tftp-server rom alias gs3-k.101
In the following example, the system uses TFTP to send a copy of the version-11.0filein response to a
TFTP Read Request for that file. The file is located on the Flash memory card inserted in slot 0.
tftp-server flash slot0:version-11.0
The following example enables a Cisco 3600 series router to operate as a TFTP server. The source file
c3640-i-mz is in the second partition of internal Flash memory.
Router#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c3640-i-mz
In the following example, the source file is in the second partition of the Flash memory PC card in slot 0 on
a Cisco 3600 series:
Router#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
tftp-server flash slot0:2:dirt/gate/c3640-j-mz
The following example enables a Cisco 1600 series router to operate as a TFTP server. The source file
c1600-i-mz is in the second partition of Flash memory:
router#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c1600-i-mz
Related Commands
Command
Description
access-list
tftp-server system
The tftp -server system command has been replaced by the tftp-server command. See the description of
the tftp-server command in this chapter for more information.
time-period
To set the time increment for automatically saving an archive file of the current running configuration in
the Cisco IOS configuration archive, use the time-period command in archive configuration mode. To
disable this function, use the no form of this command.
time-period minutes
no time-period minutes
Syntax Description
minutes
Command Default
Command Modes
Command History
Release
Modification
12.3(7)T
12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(31)SB2
12.2(33)SXH
12.2(33)SB
Usage Guidelines
Note
Before using this command, you must configure the path command to specify the location and filename
prefix for the files in the Cisco IOS configuration archive.
If this command is configured, an archive file of the current running configuration is automatically saved
after the given time specified by the minutes argument. Archive files continue to be automatically saved at
this given time increment until this function is disabled. Use the maximum command to set the maximum
number of archive files of the running configuration to be saved.
Note
Examples
This command saves the current running configuration to the configuration archive whether or not the
running configuration has been modified since the last archive file was saved.
In the following example, a value of 20 minutes is set as the time increment for which to automatically save
an archive file of the current running configuration in the Cisco IOS configuration archive:
Router# configure terminal
!
Router(config)# archive
Router(config-archive)# path disk0:myconfig
Router(config-archive)# time-period 20
Router(config-archive)# end
Related Commands
Command
Description
archive config
configure confirm
configure replace
maximum
path
show archive
trace (privileged)
To discover the routes that packets will actually take when traveling to their destination, use the trace
command in privileged EXEC mode.
trace [protocol] [destination]
Syntax Description
protocol
destination
Command Default
The protocol argument is based on the Cisco IOS software examination of the format of the destination
argument. For example, if the software finds a destination argument in IP format, the protocol value
defaults to ip.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(13)T
12.2(33)SRA
The trace command works by taking advantage of the error messages generated by routers when a
datagram exceeds its time-to-live (TTL) value.
The trace command starts by sending probe datagrams with a TTL value of one. This causes the first router
to discard the probe datagram and send back an error message. The trace command sends several probes at
each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet may result in one or two error
messages. A time exceeded error message indicates that an intermediate router has seen and discarded
the probe. A destination unreachable error message indicates that the destination node has received the
probe and discarded it because it could not deliver the packet. If the timer goes off before a response comes
in, the tracecommand prints an asterisk (*).
The trace command terminates when the destination responds, when the maximum TTL is exceeded, or
when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, type
Ctrl-^ X by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
To use nondefault parameters and invoke an extended trace test, enter the command without a destination
argument. You will be stepped through a dialog to select the desired parameters.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and routers, the IP trace command may behave in
unexpected ways.
Not all destinations will respond correctly to a probe message by sending back an ICMP port unreachable
message. A long sequence of TTL levels with only asterisks, terminating only when the maximum TTL has
been reached, may indicate this problem.
There is a known problem with the way some hosts handle an ICMP TTL exceeded message. Some hosts
generate an ICMP message but they reuse the TTL of the incoming packet. Because this is zero, the
ICMP packets do not make it back. When you trace the path to such a host, you may see a set of TTL
values with asterisks (*). Eventually the TTL gets high enough that the ICMP message can get back. For
example, if the host is six hops away, the trace command will time out on responses 6 through 11.
Trace IP Routes
The following display shows sample IP trace output when a destination host name has been specified:
Router# trace ABA.NYC.mil
Type escape sequence to abort.
Tracing the route to ABA.NYC.mil (26.0.0.73)
1 DEBRIS.CISCO.COM (192.180.1.6) 1000 msec 8 msec 4 msec
2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec
3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec
4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec
5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec
6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec
7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
The following table describes the significant fields shown in the display.
Table 177
Field
Description
DEBRIS.CISCO.COM
192.180.1.6
The following display shows a sample trace session involving the extended dialog of the trace command:
Router# trace
Protocol [ip]:
Target IP address: mit.edu
Source address:
Numeric display [n]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Port Number [33434]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Type escape sequence to abort.
Tracing the route to MIT.EDU (18.72.2.1)
1 ICM-DC-2-V1.ICP.NET (192.108.209.17) 72 msec 72 msec 88 msec
2 ICM-FIX-E-H0-T3.ICP.NET (192.157.65.122) 80 msec 128 msec 80 msec
3 192.203.229.246 540 msec 88 msec 84 msec
4 T3-2.WASHINGTON-DC-CNSS58.T3.ANS.NET (140.222.58.3) 84 msec 116 msec 88 msec
5 T3-3.WASHINGTON-DC-CNSS56.T3.ANS.NET (140.222.56.4) 80 msec 132 msec 88 msec
6 T3-0.NEW-YORK-CNSS32.T3.ANS.NET (140.222.32.1) 92 msec 132 msec 88 msec
7 T3-0.HARTFORD-CNSS48.T3.ANS.NET (140.222.48.1) 88 msec 88 msec 88 msec
8 T3-0.HARTFORD-CNSS49.T3.ANS.NET (140.222.49.1) 96 msec 104 msec 96 msec
9 T3-0.ENSS134.T3.ANS.NET (140.222.134.1) 92 msec 128 msec 92 msec
10 W91-CISCO-EXTERNAL-FDDI.MIT.EDU (192.233.33.1) 92 msec 92 msec 112 msec
11 E40-RTR-FDDI.MIT.EDU (18.168.0.2) 92 msec 120 msec 96 msec
12 MIT.EDU (18.72.2.1) 96 msec 92 msec 96 msec
The following table describes the fields that are unique to the extended trace sequence, as shown in the
display.
Table 178
Field
Description
Target IP address
Source address
Numeric display
Timeout in seconds
Probe count
Field
Description
Port Number
Loose
Strict
Record
Timestamp
Verbose
The following table describes the characters that can appear in trace command output.
Table 179
Char
Description
nn msec
Host unreachable.
Network unreachable.
Protocol unreachable.
Related Commands
Char
Description
Source quench.
Port unreachable.
Command
Description
trace (user)
trace (user)
To discover the IP routes that packets will actually take when traveling to their destination, use the trace
command in EXEC mode.
trace [protocol] [destination]
Syntax Description
protocol
destination
Command Default
The protocol argument is based on the Cisco IOS software examination of the format of the destination
argument. For example, if the software finds a destination argument in IP format, the protocol defaults to
ip.
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(13)T
12.2(33)SRA
The trace command works by taking advantage of the error messages generated by routers when a
datagram exceeds its time-to-live (TTL) value.
The trace command starts by sending probe datagrams with a TTL value of one. This causes the first router
to discard the probe datagram and send back an error message. The trace command sends several probes at
each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet may result in one or two error
messages. A time exceeded error message indicates that an intermediate router has seen and discarded
the probe. A destination unreachable error message indicates that the destination node has received the
probe and discarded it because it could not deliver the packet. If the timer goes off before a response comes
in, trace prints an asterisk (*).
The trace command terminates when the destination responds, when the maximum TTL is exceeded, or
when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, type
Ctrl-^ X by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and routers, the IP trace command may behave in
unexpected ways.
Not all destinations will respond correctly to a probe message by sending back an ICMP port unreachable
message. A long sequence of TTL levels with only asterisks, terminating only when the maximum TTL has
been reached, may indicate this problem.
There is a known problem with the way some hosts handle an ICMP TTL exceeded message. Some hosts
generate an ICMP message but they reuse the TTL of the incoming packet. Since this is zero, the ICMP
packets do not make it back. When you trace the path to such a host, you may see a set of TTL values with
asterisks (*). Eventually the TTL gets high enough that the ICMP message can get back. For example, if
the host is six hops away, trace will time out on responses 6 through 11.
Trace IP Routes
The following display shows sample IP trace output when a destination host name has been specified:
Router# trace ip ABA.NYC.mil
Type escape sequence to abort.
Tracing the route to ABA.NYC.mil (26.0.0.73)
1 DEBRIS.CISCO.COM (192.180.1.6) 1000 msec 8 msec 4 msec
2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec
3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec
4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec
5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec
6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec
7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
The following table describes the significant fields shown in the display.
Table 180
Field
Description
DEBRIS.CISCO.COM
192.180.1.61
The following table describes the characters that can appear in trace output.
Table 181
Related Commands
Char
Description
nn msec
Host unreachable.
Network unreachable.
Protocol unreachable.
Source quench.
Port unreachable.
Command
Description
trace (privileged)
traceroute
To discover the routes that packets will actually take when traveling to their destination address, use the
traceroute command in user EXEC or privileged EXEC mode.
traceroute [vrf vrf-name | topology topology-name] [protocol] destination
Syntax Description
vrf vrf-name
topology topology-name
protocol
destination
Command Default
When not specified, the protocol argument is determined by the software examining the format of the
destination argument. For example, if the software finds a destination argument in IP format, the protocol
value defaults to IP.
Command Modes
Command History
Release
Modification
10.0
12.0(5)T
12.2(2)T
12.0(21)ST
12.0(22)S
12.2(11)T
12.2(14)S
12.3(5)
12.0(26)S1
12.2(20)S
12.2(28)SB
12.2(25)SG
12.2(33)SRA
12.2(33)SRB
12.2(33)SXH
12.2(33)SRE
Usage Guidelines
Release
Modification
15.0(1)SY
The traceroute command works by taking advantage of the error messages generated by routers when a
datagram exceeds its hop limit value.
The traceroute command starts by sending probe datagrams with a hop limit of 1. Including a hop limit of
1 with a probe datagram causes the neighboring routers to discard the probe datagram and send back an
error message. The traceroute command sends several probes with increasing hop limits and displays the
round-trip time for each.
The traceroutecommand sends out one probe at a time. Each outgoing packet might result in one or more
error messages. A time-exceeded error message indicates that an intermediate router has seen and discarded
the probe. A destination unreachable error message indicates that the destination node has received and
discarded the probe because the hop limit of the packet reached a value of 0. If the timer goes off before a
response comes in, the traceroute command prints an asterisk (*).
The traceroutecommand terminates when the destination responds, when the hop limit is exceeded, or
when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, type
Ctrl-^ X--by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X
key.
To use nondefault parameters and invoke an extended traceroute test, enter the command without a
protocol or destination argument in privileged EXEC mode. You are stepped through a dialog to select the
desired parameters. Extended traceroute tests are not supported in user EXEC mode. The user-level
traceroute feature provides a basic trace facility for users who do not have system privileges. The
destination argument is required in user EXEC mode.
If the system cannot map an address for a hostname, it returns a %No valid source address for destination
message.
If the vrf vrf-name keyword and argument are used, the topology option is not displayed because only the
default VRF is supported. The topology topology-name keyword and argument and the DiffServ Code
Point (DSCP) option in the extended traceroute system dialog are displayed only if a topology is configured
on the router.
In Cisco IOS XE Release 3.2S, output of the traceroute command with the vrf keyword was enhanced to
make troubleshooting easier by displaying the incoming VRF name/tag and the outgoing VRF name/tag.
Examples
After you enter the traceroute command in privileged EXEC mode, the system prompts you for a protocol.
The default protocol is IP.
If you enter a hostname or address on the same line as the traceroute command, the default action is taken
as appropriate for the protocol type of that name or address.
The following example is sample dialog from the traceroute command using default values. The specific
dialog varies somewhat from protocol to protocol.
Router# traceroute
Protocol [ip]:
Target IP address:
Source address:
DSCP Value [0]: ! Only displayed if a topology is configured on the router.
Numeric display [n]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Port Number [33434]:
Loose, Strict, Record, Timestamp, Verbose [none]:
The following example displays output available in Cisco IOS XE Release 3.2S and later. Output of the
traceroute command with the vrf keyword includes the incoming VRF name/tag and the outgoing VRF
name/tag.
Router# traceroute vrf red 10.0.10.12
Type escape sequence to abort.
Tracing the route to 10.0.10.12
VRF info: (vrf in name/id, vrf out name/id)
1 10.1.13.15 (red/13,red/13) 0 msec
10.1.16.16 (red/13,red/13) 0 msec
10.1.13.15 (red/13,red/13) 1 msec
2 10.1.8.13 (red/13,red/13) 0 msec
10.1.7.13 (red/13,red/13) 0 msec
10.1.8.13 (red/13,red/13) 0 msec
3 10.1.2.11 (red/13,blue/10) 1 msec 0 msec 0 msec
4 * * *
Related Commands
Command
Description
ping (MTR)
traceroute mac
To display the Layer 2 path taken by the packets from the specified source to the specified destination, use
the traceroute maccommand in privileged EXEC mode.
traceroute mac source-mac-address {destination-mac-address | interface type interface-number
destination-mac-address} [vlan vlan-id] [detail]
traceroute mac interface type interface-number source-mac-address {destination-mac-address |
interface type interface-number destination-mac-address} [vlan vlan-id] [detail]
traceroute mac ip {source-ip-address | source-hostname} {destination-ip-address | destinationhostname} [detail]
Syntax Description
source-mac-address
destination-mac-address
interface type
interface-number
vlan vlan-id
detail
ip
source-ip-address
source-hostname
destination-ip-address
destination-hostname
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.2(18)SXE
12.2(33)SRA
This command is not supported on the Cisco 7600 series router that is configured with a Supervisor Engine
2.
Do not use leading zeros when entering a VLAN ID.
For Layer 2 traceroute to functional properly, you must enable CDP on all of the switches in the network.
Do not disable CDP.
When the switch detects a device in the Layer 2 path that does not support Layer 2 traceroute, the switch
continues to send Layer 2 trace queries and lets them time out.
The maximum number of hops identified in the path is ten .
Layer 2 traceroute supports only unicast traffic. If you specify a multicast source or destination MAC
address, the physical path is not identified, and a message appears.
The traceroute mac command output shows the Layer 2 path when the specified source and destination
addresses belong to the same VLAN. If you specify source and destination addresses that belong to
different VLANs, the Layer 2 path is not identified, and a message appears.
If the source or destination MAC address belongs to multiple VLANs, you must specify the VLAN to
which both the source and destination MAC addresses belong. If the VLAN is not specified, the path is not
identified, and a message appears.
When multiple devices are attached to one port through hubs (for example, multiple CDP neighbors are
detected on a port), the Layer 2 traceroute utility terminates at that hop and displays an error message.
This feature is not supported in Token Ring VLANs.
Examples
This example shows how to display detailed information about the Layer 2 path:
Router# traceroute mac 0001.0000.0204 0001.0000.0304 detail
Source 1001.0000.0204 found on VAYU[WS-C6509] (10.1.1.10)
1 VAYU / WS-C6509 / 10.1.1.10 :
Gi6/1 [full, 1000M] => Po100 [auto, auto]
2 PANI / WS-C6509 / 10.1.1.12 :
Po100 [auto, auto] => Po110 [auto, auto]
3 BUMI / WS-C6509 / 10.1.1.13 :
Po110 [auto, auto] => Po120 [auto, auto]
4 AGNI / WS-C6509 / 10.1.1.11 :
This example shows the output when the switch is not connected to the source switch:
Router# traceroute mac 0000.0201.0501 0000.0201.0201 detail
Source not directly connected, tracing source .....
Source 1000.0201.0501 found on con5[WS-C6509] (10.2.5.5)
con5 / WS-C6509 / 10.2.5.5 :
Fa0/1 [auto, auto] =>Gi0/1 [auto, auto]
con1 / WS-C6509 / 10.2.1.1 :
Gi0/1 [auto, auto] =>Gi0/2 [auto, auto]
con2 / WS-C6509 / 10.2.2.2 :
Gi0/2 [auto, auto] =>Fa0/1 [auto, auto]
Destination 1000.0201.0201 found on con2[WS-C6509] (10.2.2.2)
Layer 2 trace completed.
Router#
This example shows the output when the switch cannot find the destination port for the source MAC
address:
Router# traceroute mac 0000.0011.1111 0000.0201.0201
Error:Source Mac address not found.
Layer2 trace aborted.
Router#
This example shows the output when the source and destination devices are in different VLANs:
Router# traceroute mac 0000.0201.0601 0000.0301.0201
Error:Source and destination macs are on different vlans.
Layer2 trace aborted.
Router#
This example shows the output when the destination MAC address is a multicast address:
Router# traceroute mac 0000.0201.0601 0100.0201.0201
Invalid destination mac address
Router#
This example shows the output when the source and destination switches belong to multiple VLANs:
Router# traceroute mac 0000.0201.0601 0000.0201.0201
Error:Mac found on multiple vlans.
Layer2 trace aborted.
Router#
This example shows how to display the Layer 2 path by specifying the interfaces on the source and
destination switches:
Router# traceroute mac interface fastethernet0/1 0000.0201.0601 interface fastethernet0/3
0000.0201.0201
Source 1000.0201.0601 found on con6[WS-C6509] (10.2.6.6)
con6 (10.2.6.6) :Fa0/1 =>Fa0/3
con5
(10.2.5.5
) :
Fa0/3 =>Gi0/1
con1
(10.2.1.1
) :
Gi0/1 =>Gi0/2
con2
(10.2.2.2
) :
Gi0/2 =>Fa0/1
Destination 1000.0201.0201 found on con2[WS-C6509] (10.2.2.2)
Layer 2 trace completed
Router#
:
=>Fa0/3 [auto, auto]
:
=>Gi0/1 [auto, auto]
:
=>Gi0/2 [auto, auto]
:
=>Fa0/1 [auto, auto]
found on con2[WS-C6509] (10.2.2.2)
This example shows how to display the Layer 2 path by specifying the source and destination hostnames:
Router# traceroute mac ip con6 con2
Translating IP to mac .....
10.2.66.66 =>0000.0201.0601
10.2.22.22 =>0000.0201.0201
Source 0000.0201.0601 found on con6
con6 (10.2.6.6) :Fa0/1 =>Fa0/3
con5
(10.2.5.5
) :
con1
(10.2.1.1
) :
con2
(10.2.2.2
) :
Destination 0000.0201.0201 found on con2
Layer 2 trace completed
Router#
Fa0/3 =>Gi0/1
Gi0/1 =>Gi0/2
Gi0/2 =>Fa0/1
This example shows the output when ARP cannot associate the source IP address with the corresponding
MAC address:
Router# traceroute mac ip 10.2.66.66 10.2.77.77
Arp failed for destination 10.2.77.77.
Layer2 trace aborted.
Router#
undelete
To recover a file marked deleted on a Class A Flash file system, use the undelete command in user
EXEC or privileged EXEC mode.
undelete index [filesystem :]
Syntax Description
index
filesystem :
Command Default
Command Modes
Command History
Usage Guidelines
Release
Modification
11.0
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
For Class A Flash file systems, when you delete a file, the Cisco IOS software simply marks the file as
deleted, but it does not erase the file. This command allows you to recover a deleted file on a specified
Flash memory device. You must undelete a file by its index because you could have multiple deleted files
with the same name. For example, the deleted list could contain multiple configuration files with the
name router-config. You undelete by index to indicate which of the many router-config files from the list to
undelete. Use the dir command to learn the index number of the file you want to undelete.
You cannot undelete a file if a valid (undeleted) file with the same name exists. Instead, you first delete the
existing file and then undelete the file you want. For example, if you had an undeleted version of the routerconfig file and you wanted to use a previous, deleted version instead, you could not simply undelete the
previous version by index. You would first delete the existing router-config file and then undelete the
previous router-config file by index. You can delete and undelete a file up to 15 times.
On Class A Flash file systems, if you try to recover the configuration file pointed to by the CONFIG_FILE
environment variable, the system prompts you to confirm recovery of the file. This prompt reminds you
that the CONFIG_FILE environment variable points to an undeleted file. To permanently delete all files
marked deleted on a Flash memory device, use the squeeze EXEC command.
For further information on Flash File System types (classes), see http://www.cisco.com/en/US/products/hw/
routers/ps341/products_tech_note09186a00800a7515.shtml.
Examples
Related Commands
Command
Description
delete
dir
squeeze
unprofile
To free the memory either by deleting data or disabling the profiles, use the unprofilecommand in
privilegedEXEC mode.
unprofile {process {process-ID | process-name}} {start-address end-address increment | all | task}
Syntax Description
Command Modes
Command History
Examples
process
process-ID
process-name
start-address
end-address
increment
all
task
Release
Modification
15.0(1)M
12.2(33)SRB
12.2(33)SXI
The following example shows how to delete all the profile data:
Router# unprofile
process all
Syntax Description
Command Default
The reload of the router with the Cisco IOS software image is not scheduled. The disk-management utility
is disabled.
Command Modes
Command History
Release
Modification
12.4(15)T
Usage Guidelines
Use the upgrade automatic abortversion command to cancel a reload that has already been scheduled
with either the upgrade automatic getversion command or the upgrade automatic runversion command.
Examples
The following example shows how to cancel a reload that is scheduled within one hour and 15 minutes.
The reload was scheduled by using the upgrade automatic runversion command.
Router# upgrade automatic runversion in 01:15
Upgrading to "flash:c1841-adventerprisek9-mz.calvin-build-20060714". Wait..
Reload scheduled for 09:51:38 UTC Thu Aug 3 2006 (in 1 hour and 15 minutes) with image flash:c1841-adventerprisek9-mz.calvin-build-20060714 by console
Reload reason: Auto upgrade
Device will WARM UPGRADE in 1:15:00
To cancel the upgrade, enter the command "upgrade automatic abortversion"
Aug 3 08:36:38.072: %SYS-5-SCHEDULED_RELOAD: Reload requested for 09:51:38 UTC Thu Aug 3
2006 at 08:36:38 UTC Thu Aug 3 2006 by console. Reload Reason: Auto upgrade.
Router# upgrade automatic abortversion
Auto upgrade of image which was scheduled earlier is aborted!
***
*** --- SHUTDOWN ABORTED --***
Aug 3 08:37:02.292: %SYS-5-SCHEDULED_RELOAD_CANCELLED: Scheduled reload cancelled at
08:37:02 UTC Thu Aug 3 2006
Related Commands
Command
Description
Syntax Description
cisco
username username
password password
image
image
url
at
in hh:mm
disk-management
Command Default
The reload of the router with the Cisco IOS software image is not scheduled. The disk-management utility
is disabled.
Command Modes
Command History
Usage Guidelines
Release
Modification
12.4(15)T
Use the upgrade automatic getversion command to download the Cisco IOS software image to a router.
You can either download the image from the Cisco website (www.cisco.com) or from a non-Cisco server to
which the Cisco IOS software image has already been downloaded from the Cisco website.
You can also use this command to schedule a reload. Additionally, this command can use the disk cleanup
utility to delete files if there is not enough space to download the new Cisco IOS software image.
Examples
Downloading the Cisco IOS Image from the Cisco Website
The following example shows how to download a Cisco IOS software image from the Cisco website
(www.cisco.com). Here, the reloading of the router with the downloaded Cisco IOS software image is not
scheduled. Also, the disk-cleanup utility is not enabled.
Router# upgrade automatic getversion cisco username myusername password mypassword image
c3825-adventerprisek9-mz.124-2.XA.bin
Downloading the Cisco IOS Image from a Non-Cisco TFTP Server Using the Interactive Mode
The following example shows how to use this command in interactive mode to download a Cisco IOS
software image from a non-Cisco server. Here, the reloading of the device with the downloaded Cisco IOS
software image is not scheduled.
Router# upgrade automatic
################################################################################
Welcome to the Cisco IOS Auto Upgrade Manager. To upgrade your device, please answer the
following questions. To accept the default value for a question, simply hit <ENTER>
################################################################################
Would you like to download an image directly from Cisco Server over the Internet? A valid
Cisco login will be required.
Related Commands
Command
Description
Syntax Description
at
in hh:mm
Command Modes
Command History
Usage Guidelines
Note
Examples
Release
Modification
12.4(15)T
Use the upgrade automatic runversion command to schedule a reload after downloading a Cisco IOS
software image using the upgrade automatic getversion command.
You can also use the upgrade automatic getversion command to reload the router with the new Cisco IOS
software image. However, if you have already downloaded the Cisco IOS software image using the
upgrade automatic getversion command, you should use the upgrade automatic runversion command
to reload the router.
The following example shows how to schedule a reload after downloading a Cisco IOS software image:
Router# show clock
09:01:36.124 UTC Thu Aug 3 2006
Router# upgrade automatic runversion at 10:20
Upgrading to "flash:c1841-adventerprisek9-mz.calvin-build-20060714". Wait..
Reload scheduled for 10:20:00 UTC Thu Aug 3 2006 (in 1 hour and 18 minutes) with image flash:c1841-adventerprisek9-mz.calvin-build-20060714 by console
Related Commands
Command
Description
Syntax Description
disk0
disk1
Command Default
Command Modes
Privileged EXEC(#)
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(25)S
12.2YST
If you attempt to upgrade the ATA monlib file on a disk that has not been formatted on a router running
Cisco IOS software, the upgrade operation will fail.
If the amount of space available on the disk for the monlib image is smaller than the monlib image you are
trying to upgrade to, the upgrade operation will fail. The amount of space available for the monlib file can
be determined by issuing the show disk command with the all keyword specified. The Disk monlib size
field displays the number of bytes available for the ATA monlib file.
Examples
The following example shows how to upgrade the ATA monlib file on disk 0:
Router# upgrade filesystem monlib disk0
Hash Computation:
100%Done!
Computed Hash
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Embedded Hash
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Related Commands
Command
Description
format
show disk
upgrade rom-monitor
To set the execution preference on a read-only memory monitor (ROMMON), use the upgrade rommonitor command in privileged EXEC or diagnostic mode.
upgrade rom-monitor slot num {sp | rp} file filename
upgrade rom-monitor slot num {sp | rp} {invalidate | preference} {region1 | region2}
Cisco ASR 1000 Series Aggregation Services Routers
upgrade rom-monitor filename URL slot
Syntax Description
slot num
sp
rp
file filename
invalidate
preference
region1
region2
filename
URL
slot
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.4(24)T
Usage Guidelines
Caution
If you enter the upgrade rom-monitor command from a Telnet session instead of a console connection,
service may be interrupted.
The slot numkeyword and argument combination is required for this command to function properly.
The sp or rpkeyword is required if you installed a supervisor engine in the specified slot.
Valid values for file filename are the following:
bootflash:
disk0:
disk1:
flash:
ftp:
rcp:
sup-bootflash:
sup-slot0:
tftp:
On Cisco ASR 1000 Series Routers, this command can be used to upgrade ROMMON in privileged EXEC
and diagnostic mode. The hardware receiving the ROMMON upgrade must be reloaded to complete the
upgrade.
From Cisco IOS Release 12.4(24)T, you can use the upgrade rom-monitor command on Cisco 3200
series routers to upgrade ROMMON and the system bootstrap, if a newer version of ROMMON is
available on the system.
Examples
This example shows how to upgrade the new ROMMON image to the flash device on a Supervisor Engine
2:
Router# upgrade rom-monitor
slot 1 sp file tftp://dirt/tftpboot-users/A2_71059.srec
ROMMON image upgrade in progress
Erasing flash
Programming flash
Verifying new image
ROMMON image upgrade complete
The card must be reset for this to take effect
Router#
In the following example, a ROMMON upgrade is performed to upgrade to Cisco IOS Release
12.2(33r)XN1 on a Cisco ASR 1000 Series Router using an ROMMON image stored on the bootflash: file
system. All hardware is upgraded on the Cisco ASR 1000 Series Router in this example, and the router is
then reloaded to complete the procedure.
Router# show rom-monitor 0
System Bootstrap, Version 12.2(33)XN1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2007 by cisco Systems, Inc.
Router# show rom-monitor F0
System Bootstrap, Version 12.2(33)XN1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2007 by cisco Systems, Inc.
Router# show rom-monitor R0
System Bootstrap, Version 12.2(33)XN1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2007 by cisco Systems, Inc.
Router# copy tftp bootflash:
Address or name of remote host []? 127.23.16.81
Source filename []? auto/tftp-boot/asr1000-rommon.122-33r.XN1.pkg
Destination filename [asr1000-rommon.122-33r.XN1.pkg]?
Accessing tftp://127.23.16.81/auto/tftp-boot/asr1000-rommon.122-33r.XN1.pkg...
Loading auto/tftp-boot/asr1000-rommon.122-33r.XN1.pkg from 127.23.16.81 (via
GigabitEthernet0): !!!
Related Commands
Command
Description
show rom-monitor
Syntax Description
disk0
disk1
Command Default
Command Modes
Privileged EXEC(#)
Command History
Usage Guidelines
Release
Modification
12.3(7)T
12.2(25)S
12.2YST
If you attempt to upgrade the ATA monlib file on a disk that has not been formatted on a router running
Cisco IOS software, the upgrade operation will fail.
If the amount of space available on the disk for the monlib image is smaller than the monlib image you are
trying to upgrade to, the upgrade operation will fail. The amount of space available for the monlib file can
be determined by issuing the show disk command with the all keyword specified. The Disk monlib size
field displays the number of bytes available for the ATA monlib file.
Examples
The following example shows how to upgrade the ATA monlib file on disk 0:
Router# upgrade filesystem monlib disk0
Hash Computation:
100%Done!
Computed Hash
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Embedded Hash
SHA2: DFBA87256310DC8A7B7BF8158451F7F4
0AC333C9B396D9D0E42DDBD542C30E08
F3946DDE692AF04F0B20F29BE51C49C4
1B631790A542D81F9A7C90ABC2426960
Related Commands
Command
Description
format
show disk
Syntax Description
readonly
upgrade
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
12.0(28)S
12.3(8)T
12.3(9)
After running the upgrade rom-monitor preference command, you must reload the router for the selected
ROMmon image to take effect.
Use the rommon-prefcommand when you are in ROMmon mode.
Examples
The following example applicable to both the Cisco 7200 VXR and Cisco 7301 routers selects the
ReadOnly ROMmon image to be booted on the next reload of the router:
Router# upgrade rom-monitor preference readonly
You are about to mark ReadOnly region of ROMMON for the highest boot preference.
Proceed? [confirm]
Done! Router must be reloaded for this to take effect.
Related Commands
Command
Description
rommon-pref
vacant-message
To display an idle terminal message, use the vacant-message command in line configuration mode. To
remove the default vacant message or any other vacant message that may have been set, use the no form of
this command.
vacant-message [d message d]
no vacant-message
Syntax Description
Command Default
message
Command Modes
Command History
Usage Guidelines
Line configuration
Release
Modification
10.0
12.2(33)SRA
This command enables the banner to be displayed on the screen of an idle terminal. The vacant-message
command without any arguments restores the default message.
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter
one or more lines of text, terminating the message with the second occurrence of the delimiting character.
Note
Examples
For a rotary group, you need to define only the message for the first line in the group.
The following example turns on the system banner and displays this message:
Router(config)# line 0
Router(config-line)# vacant-message %
Welcome to Cisco Systems, Inc.
Press Return to get started.
%
verify
To verify the checksum of a file on a flash memory file system or compute a Message Digest 5 (MD5)
signature for a file, use the verify command in privileged EXEC mode.
verify [/md5 [md5-value]] filesystem : [file-url]
Cisco 7600 Series Router
verify {/md5 flash-filesystem [expected-md5-signature] | /ios flash-filesystem | flash-filesystem}
Syntax Description
/md5
md5-value
filesystem :
file-url
expected-md5-signature
/ios flash-filesystem
flash-filesystem
Command Default
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
11.0
12.2(4)T
12.2(18)S
12.0(26)S
12.2(14)SX
12.3(4)T
12.2(17d)SXB
12.2(33)SRA
This command replaces the copy verify and copy verify flash commands.
Use the verify command to verify the checksum of a file before using it.
Each software image that is distributed on disk uses a single checksum for the entire image. This checksum
is displayed only when the image is copied into flash memory; it is not displayed when the image file is
copied from one disk to another.
Supported Platforms Other than the Cisco 7600 Series Router
Before loading or duplicating a new image, record the checksum and MD5 information for the image so
that you can verify the checksum when you copy the image into flash memory or onto a server. A variety of
image information is available on Cisco.com. For example, you can get the Release, Feature Set, Size, BSD
Checksum, Router Checksum, MD5, and Publication Date information by clicking on the image file name
prior to downloading it from the Software Center on Cisco.com.
To display the contents of flash memory, use the show flash command. The flash contents listing does not
include the checksum of individual files. To recompute and verify the image checksum after the image has
been copied into flash memory, use the verify command. Note, however, that the verify command only
performs a check on the integrity of the file after it has been saved in the file system. It is possible for a
corrupt image to be transferred to the router and saved in the file system without detection. If a corrupt
image is transferred successfully to the router, the software will be unable to tell that the image is corrupted
and the file will verify successfully.
To use the message-digest5 (MD5) hash algorithm to ensure file validation, use the verify command with
the /md5 option. MD5 is an algorithm (defined in RFC 1321) that is used to verify data integrity through
the creation of a unique 128-bit message digest. The /md5 option of the verify command allows you to
check the integrity of a Cisco IOS software image by comparing its MD5 checksum value against a known
MD5 checksum value for the image. MD5 values are now made available on Cisco.com for all Cisco IOS
software images for comparison against local system image values.
To perform the MD5 integrity check, issue the verify command using the /md5 keyword. For example,
issuing the verify flash:c7200-is-mz.122-2.T.bin /md5command will calculate and display the MD5 value
for the software image. Compare this value with the value available on Cisco.com for this image.
Alternatively, you can get the MD5 value from Cisco.com first, then specify this value in the command
syntax. For example, issuing the verify flash:c7200-is-mz.122-2.T.bin /md5
8b5f3062c4caeccae72571440e962233 command will display a message verifying that the MD5 values
match or that there is a mismatch. A mismatch in MD5 values means that either the image is corrupt or the
wrong MD5 value was entered.
Cisco 7600 Series Router
The Readme file, which is included with the image on the disk, lists the name, file size, and checksum of
the image. Review the contents of the Readme file before loading or duplicating the new image so that you
can verify the checksum when you copy it into the flash memory or onto a server.
Use the verify /md5 command to verify the MD5 signature of a file before using it. This command
validates the integrity of a copied file by comparing a precomputed MD5 signature with the signature that
is computed by this command. If the two MD5 signatures match, the copied file is identical to the original
file.
You can find the MD5 signature that is posted on the Cisco.com page with the image.
You can use the verify /md5 command in one of the following ways:
Verify the MD5 signatures manually by entering the verify /md5 filename command.
Check the displayed signature against the MD5 signature that is posted on the Cisco.com page.
Allow the system to compare the MD5 signatures by entering the verify /md5 flash-filesystem:filenam
expected-md5-signature command.
After completing the comparison, the system returns with a verified message. If an error is detected, the
output is similar to the following:
Router# verify /md5 disk0:c6msfc2-jsv-mz 0f
.
.
.
Done
!
%Error verifying disk0:c6msfc2-jsv-mz
Computed signature = 0f369ed9e98756f179d4f29d6e7755d3
Submitted signature = 0f
To display the contents of the flash memory, enter the show flash command. The listing of the flash
contents does not include the checksum of the individual files. To recompute and verify the image
checksum after the image has been copied into the flash memory, enter the verify command.
A colon (:) is required after the specified device.
Examples
Supported Platforms Other than Cisco 7600 Series Router
The following example shows how to use the verify command to check the integrity of the file c7200-js-mz
on the flash memory card inserted in slot 0:
Router# dir slot0:
Directory of slot0:/
1 -rw4720148
Aug 29 1997
2 -rw4767328
Oct 01 1997
5 -rw639
Oct 02 1997
7 -rw639
Oct 02 1997
20578304 bytes total (3104544 bytes
Router# verify slot0:c7200-js-mz
17:49:36
18:42:53
12:09:32
12:37:13
free)
hampton/nitro/c7200-j-mz
c7200-js-mz
rally
the_time
Verified slot0:c7200-js-mz
In the following example, the /md5 keyword is used to display the MD5 value for the image:
Router# verify /md5 disk1:
Verify filename []? c7200-js-mz
.
.
.
Done
!
verify /md5 (disk1:c7200-js-mz) = 0f369ed9e98756f179d4f29d6e7755d3
In the following example, the known MD5 value for the image (obtained from Cisco.com) is specified in
the verify command, and the system checks the value against the stored value:
Router# verify /md5 disk1:c7200-js-mz ?
WORD Expected md5 signature
<cr>
router# verify /md5 disk1:c7200-js-mz 0f369ed9e98756f179d4f29d6e7755d3
.
.
.
Done
!
Verified (disk1:c7200-js-mz) = 0f369ed9e98756f179d4f29d6e7755d3
The following example shows how the output of the verify command was enhanced to show the hash value
in addition to the entire hash image (CCO hash):
Router# verify disk0:c7200-js-mz
%Filesystem does not support verify operations
Verifying file integrity of disk0:c7200-js-mz
.
.
.
Done
!
Embedded Hash
MD5 :CFA258948C4ECE52085DCF428A426DCD
Computed Hash
MD5 :CFA258948C4ECE52085DCF428A426DCD
CCO Hash
MD5 :44A7B9BDDD9638128C35528466318183
Signature Verified
.
.
File cat6k_r47_1.cbi verified OK.
This example shows how to allow the system to compare the MD5 signatures:
Router# verify /md5 disk0:c6msfc2-jsv-mz 0f369ed9e98756f179d4f29d6e7755d3
.
.
.
Done
!
verified /md5 (disk0:c6sup12-jsv-mz) = 0f369ed9e98756f179d4f29d6e7755d3
Router#
This example shows how to verify the compressed checksum of the Cisco IOS image:
Router# verify /ios disk0:c6k222-jsv-mz
Verified compressed IOS image checksum for disk0:c6k222-jsv-mz
Related Commands
Command
Description
cd
copy
copy /noverify
dir
pwd
show flash
vtp
To configure the global VLAN Trunking Protocol (VTP) state, use the vtp command in global
configuration mode. To return to the default value, use the no form of this command.
vtp {domain domain-name | file filename | interface interface-name [only] | mode {client | off |
server | transparent} {vlan | mst | unknown} | password password-value [hidden | secret] |
pruning | version {1 | 2 | 3}}
no vtp
Syntax Description
domain domain-name
file filename
interface interface-name
Sets the name of the preferred source for the VTPupdater ID for this device.
only
mode client
mode off
mode server
mode transparent
vlan
mst
unknown
password password-value
hidden
secret
pruning
version {1 | 2 | 3}
Command Default
Command Modes
Command History
Release
Modification
12.2(14)SX
12.2(17d)SXB
12.2(33)SRA
12.2(33)SXH
12.2(33)SXI
Usage Guidelines
Note
The vtp pruning, vtp password, and vtp version commands are also available in privileged EXEC mode.
We recommend that you use these commands in global configuration mode only; do not use these
commands in privileged EXEC mode.
If you configure VTP in secure mode, the management domain does not function properly if you do not
assign a management domain password to each network device in the domain.
A VTP version 2-capable network device can operate in the same VTP domain as a network device running
VTP version 1 if VTP version 2 is disabled on the VTP version 2-capable network device (VTP version 2 is
disabled by default).
Do not enable VTP version 2 on a network device unless all of the network devices in the same VTP
domain are version 2-capable. When you enable VTP version 2 on a network device, all of the version 2capable network devices in the domain enable VTP version 2.
In a Token Ring environment, you must enable VTP version 2 for VLAN switching to function properly.
Enabling or disabling VTP pruning on a VTP server enables or disables VTP pruning for the entire
management domain.
Configuring VLANs as pruning eligible or pruning ineligible on a Cisco 7600 series router affects pruning
eligibility for those VLANs on that switch only; it does not affect pruning eligibility on all network devices
in the VTP domain.
The vtp password, vtp pruning, and vtp version commands are not placed in startup memory but are
included in the VTP transparent-mode startup configuration file.
Extended-range VLANs are not supported by VTP.
You can configure the pruning keyword in VTP-server mode; the version keyword is configurable in
VTP-server mode or VTP transparent mode.
The password-value argument is an ASCII string from 8 to 64 characters identifying the administrative
domain for the device.
VTP pruning causes information about each pruning-eligible VLAN to be removed from VTP updates if
there are no stations belonging to that VLAN.
All Cisco 7600 series routers in a VTP domain must run the same version of VTP. VTP version 1 and VTP
version 2 do not operate on Cisco 7600 series routers in the same VTP domain.
If all Cisco 7600 series routers in a domain are VTP version 2-capable, you need only to enable VTP
version 2 on one Cisco 7600 series router; the version number is then propagated to the other version 2capable Cisco 7600 series routers in the VTP domain.
If you toggle the version 2 mode, certain default VLAN parameters are modified.
If you enter the vtp mode off command, it sets the device to off. If you enter the no vtp mode off
command, it resets the device to the VTP server mode.
In VTP version 3, the VTP mode has to be specified on a per-feature basis. Use the vlan and mst keywords
to configure the VTP mode on VLAN and MST instances. To configure the VTP mode for any other
feature, use the unknown keyword. When you convert from either VTP version 1 or 2 to version 3, the
current mode configuration will be preserved.
With VTP version 3, a new method is available for hiding the VTP password from the configuration file.
When you use the hidden keyword, the secret key that is generated from the password string is saved in the
const_nvram:vlan.dat file. If you use the secret keyword, you can directly configure the password secret
key. By using the secret keyword, you can distribute the password in the secret key format rather than in
the cleartext format.
Examples
This example shows how to specify the file in the IFS-file system where the VTP configuration is stored:
Router(config)#
vtp file vtpconfig
Setting device to store VLAN database at filename vtpconfig.
This example shows how to reset the device to the VTP server mode:
Router(config)# no vtp mode off
Setting device to VTP OFF mode.
Related Commands
Command
Description
show vtp
warm-reboot
To enable a router to do a warm-reboot, use the warm-rebootcommand in global configuration mode. To
disable warm rebooting, use the no form of this command.
warm-reboot [count number] [uptime minutes]
no warm-reboot count number uptime minutes
Syntax Description
Command Default
count number
uptime minutes
Command Modes
Command History
Usage Guidelines
Global configuration
Release
Modification
12.3(2)T
12.2(18)S
12.2(28)SB
Use the warm-rebootcommand to enable the router to reload a Cisco IOS image without ROM monitor
mode (ROMMON) intervention, in which the image restores read-write data from a previously saved copy
in the RAM and starts execution from that point. Unlike a cold reboot, this process does not involve a flash
to RAM copy or self-decompression of the image.
Note
After a warm reboot is enabled, it will not become active until after the next cold reboot because a warm
reboot requires a copy of the initialized memory.
Note
If the system crashes before the image completes the warm reboot process, a cold reboot is initiated.
Examples
The following example shows how to enable a warm reboot on the router:
Router#(config) warm-reboot count 10 uptime 10
Related Commands
Command
Description
show warm-reboot
where
To list the open sessions, use the wherecommand in EXEC mode.
where
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
The where command displays all open sessions associated with the current terminal line.
The break (Ctrl-Shift-6, x), where, and resume commands are available with all supported connection
protocols.
Examples
Address
192.31.7.21
131.108.12.19
Byte
0
0
Idle
0
0
Conn Name
MATHOM
CHAFF
Field
Description
Conn
Related Commands
Field
Description
Host
Address
Byte
Idle
Conn Name
Command
Description
show line
show sessions
width
To set the terminal screen width, use the width command in line configuration mode. To return to the
default screen width, use the no form of this command.
width characters
no width
Syntax Description
characters
Command Default
80 character columns
Command Modes
Line configuration
Command History
Usage Guidelines
Release
Modification
10.0
12.2(33)SRA
By default, the route provides a screen display width of 80 characters. You can reset this value for the
current session if it does not meet the needs of your terminal.
The rlogin protocol uses the value of the characters argument to set up terminal parameters on a remote
host.
Examples
In the following example the location for line 7 is defined as console terminal and the display is set to
132 columns wide:
Router(config)# line 7
Router(config-line)# location console terminal
Router(config-line)# width 132
Related Commands
Command
Description
terminal width
write core
To test the configuration of a core dump setup, use the write core command in privileged EXEC mode.
write core [hostname [LINE] | destination-address [LINE]]
Syntax Description
Command Default
hostname
destination-address
LINE
If the hostname or destination arguments are not specified, the core dump file is written to the IP address or
hostname specified by the exception dump command.
If the LINE keyword is not specified, the name of the core dump file is assigned as the host name of the
remote server followed by the word -core.
Command Modes
Command History
Usage Guidelines
Privileged EXEC
Release
Modification
12.2(11)T
When a router reloads, it is sometimes useful to obtain a full copy of the memory image (called a core
dump) to identify the cause of the reload. Core dumps are generally useful to your technical support
representative. Not all types of router reloads will produce a core dump.
The write core command causes the router to generate a core dump without reloading, which may be
useful if the router is malfunctioning but has not reloaded. The core dump files will be the size of the
respective memory regions. It is important to remember that the entire memory region is dumped, not just
the memory that is in use.
Caution
Use the write core command only under the direction of a technical support representative. Creating a core
dump while the router is functioning in a network can disrupt network operation. When using this
command, the router will not reload until the content of its memory is dumped. This event might take some
time, depending on the amount of DRAM present on the router. Also, the resulting binary file, which is
very large, must be transferred to a Trivial File Transfer Protocol (TFTP), File Transfer Protocol (FTP), or
remote copy protocol (rcp) server and subsequently interpreted by technical personnel who have access to
source code and detailed memory maps.
Depending on your TFTP server, you might need to create an empty target file to which the router can
write the core dump.
Examples
The following example shows how to test the configuration of a core dump setup. In this example, the core
dump file is written to the remote server with the host name test.
write core test
write erase
The write erase command is replaced by the erase nvram: command. See the description of the
erasecommand for more information.
write memory
To save the running configuration to the nonvolatile random-access memory (NVRAM), use the write
memory command in privileged EXEC mode.
write memory
Syntax Description
Command Modes
Command History
Release
Modification
12.2(11)T
12.2(14)SX
12.2(33)SRA
Usage Guidelines
If you try to configure the write memory command when a router is low on memory and the backup buffer
cannot be allocated, then the command will fail with the error message, Not enough space. When the
write memory command fails to apply the new configuration, the backup configuration is used to restore
the original configuration.
Examples
The following example shows how to save the running configuration to NVRAM:
Router> enable
Router# write memory
write mib-data
To save MIB data to system memory (NVRAM) for MIB Data Persistence, use the write mibdatacommand in EXEC mode.
write mib-data
Syntax Description
Command Modes
Command History
Usage Guidelines
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
The MIB Data Persistence feature allows the SNMP data of a MIB to be persistent across reloads; that is,
the values of certain MIB objects are retained even if your networking device reboots.
To determine which MIBs support MIB Persistence in your release, use the snmp mib persist command
in global configuration mode.
Any modified MIB data must be written to NVRAM memory using the write mib-data command. If the
write mib-data command is not used, modified MIB data is not saved automatically, even if MIB
Persistence is enabled. Executing the write mib-data command saves only the current MIB data; if the
MIB object values are changed, you should reenter the write mib-data command to ensure that those
values are persistent across reboots.
Examples
The following example shows the enabling of event MIB persistence, circuit MIB persistence, and saving
the changes to set object values for these MIBs to NVRAM:
Router# configure terminal
Router(config)# snmp mib persist circuit
Router(config)# snmp mib persist event
Router(config)# end
Router# write mib-data
Related Commands
Command
Description
write network
Note
Syntax Description
Command Modes
Command History
host-file-address
Release
Modification
15.0(1)M
12.2(33)SRC
12.2(33)SXI
Usage Guidelines
The write network command cannot be used to upload software to the ATM module.
Examples
This example shows how to upload the system5.cfg file to the mercury host using the write network
command:
Router# write network
IP address or name of host? mercury
Name of configuration file to write? system5.cfg
Upload configuration to system5.cfg on mercury (y/n) [y]? y
/
Done. Finished Network Upload. (9003 bytes)
Related Commands
Command
Description
copy
show config
write terminal
This command is deprecated. Deprecated commands are considered obsolete, and their use is discouraged.
Support for this command may be removed.
The write terminal command is now enabled only as a command alias for the show running-config
command.
The show running-config command offers additional options not available for the write terminal
command; see the documentation of the show running-config command for details.
Command Modes
Command History
Privileged EXEC
Release
Modification
8.0
11.0
12.2(33)SRA
xmodem
To copy a Cisco IOS image to a router using the ROM monitor and the Xmodem or Ymodem protocol, use
the xmodem command in ROM monitor mode.
xmodem [-c] [-y] [-e] [-f] [-r] [-x] [[-s] data-rate] [filename]
Syntax Description
-c
-y
-e
-f
-r
-x
-s data-rate
filename
Command Default
Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
Command Modes
ROM monitor
Command History
Usage Guidelines
Release
Modification
11.2 P
12.2(33)SRA
The Cisco 3600 series routers does not support XBOOT functionality. If your Cisco IOS image is erased or
damaged, you cannot load a new image over the network.
Use the xmodem ROM monitor command to download a new system image to your router from a local
personal computer (such as a PC, Mac, or UNIX workstation), or a remote computer over a modem
connection, to the routers console port. The computer must have a terminal emulation application that
supports these protocols.
Cisco 3600 Series Routers
Your router must have enough DRAM to hold the file being transferred, even if you are copying to Flash
memory. The image is copied to the first file in internal Flash memory. Any existing files in Flash memory
are erased. There is no support for partitions or copying as a second file.
Cisco 1600 Series Routers
If you include the -r option, your router must have enough DRAM to hold the file being transferred. To run
from Flash, an image must be positioned as the first file in Flash memory. If you are copying a new image
to boot from Flash, erase all existing files first.
Caution
Note
Examples
A modem connection from the telephone network to your console port introduces security issues that you
should consider before enabling the connection. For example, remote users can dial in to your modem and
access the routers configuration settings.
If the file to be downloaded is not a valid router image, the copy operation is automatically terminated.
The following example uses the xmodem -c filename ROM monitor command to copy the file named newios-image from a remote or local computer:
rommon > xmodem -c new-ios-image
Do not start the sending program yet...
File size
Checksum
File name
1738244 bytes (0x1a8604)
0xdd25 george-admin/c3600-i-mz
WARNING: All existing data in bootflash will be lost!
Invoke this application only for disaster recovery.
Do you wish to continue? y/n [n]: yes
Ready to receive file new-ios-image ...
Related Commands
Command
Description
copy xmodem:
copy ymodem:
Note
This document is a reference for only the standard ASCII character set. Extended ASCII character sets are
not generally recommended for use in Cisco IOS commands. Extended ASCII character set references are
widely available on the internet.
Table 183
Numeric Values
ASCII Character
Meaning
Keyboard Entry
Decimal
Hex
00
NUL
Null
Ctrl-@
01
SOH
Start of heading
Ctrl-A
02
STX
Start of text
Ctrl-B
03
ETX
Break/end of text
Ctrl-C
04
EOT
End of
transmission
Ctrl-D
05
ENQ
Enquiry
Ctrl-E
06
ACK
Positive
acknowledgment
Ctrl-F
07
BEL
Bell
Ctrl-G
Numeric Values
ASCII Character
Meaning
Keyboard Entry
08
BS
Backspace
Ctrl-H
09
HT
Horizontal tab
Ctrl-I
10
0A
LF
Line feed
Ctrl-J
11
0B
VT
Vertical tab
Ctrl-K
12
0C
FF
Form feed
Ctrl-L
13
0D
CR
Carriage return
(in the CLI,
equivalent to the
Enter or Return
key)
Ctrl-M
14
0E
SO
Shift out
Ctrl-N
15
0F
SI
Shift in/XON
(resume output)
Ctrl-O
16
10
DLE
Ctrl-P
17
11
DC1
Device control
character 1
Ctrl-Q
18
12
DC2
Device control
character 2
Ctrl-R
19
13
DC3
Device control
character 3
Ctrl-S
20
14
DC4
Device control
character 4
Ctrl-T
21
15
NAK
Negative
acknowledgment
Ctrl-U
22
16
SYN
Synchronous idle
Ctrl-V
23
17
ETB
End of
transmission
block
Ctrl-W
24
18
CAN
Cancel
Ctrl-X
25
19
EM
End of medium
Ctrl-Y
26
1A
SUB
Substitute/end of
file
Ctrl-Z
27
1B
ESC
Escape
Ctrl-[
Numeric Values
ASCII Character
Meaning
Keyboard Entry
28
1C
FS
File separator
Ctrl-\
29
1D
GS
Group separator
Ctrl-]
30
1E
RS
Record separator
Ctrl-^
31
1F
US
Unit separator
Ctrl-_
32
20
SP
Space
Space
33
21
34
22
"
"
"
35
23
36
24
37
25
38
26
&
&
&
39
27
40
28
41
29
42
2A
43
2B
44
2C
45
2D
46
2E
47
2F
48
30
Zero
49
31
One
50
32
Two
51
33
Three
52
34
Four
53
35
Five
54
36
Six
55
37
Seven
Numeric Values
ASCII Character
Meaning
Keyboard Entry
56
38
Eight
57
39
Nine
58
3A
59
3B
60
3C
<
<
<
61
3D
62
3E
>
>
>
63
3F
64
40
65
41
66
42
67
43
68
44
69
45
70
46
71
47
72
48
73
49
74
4A
75
4B
76
4C
77
4D
78
4E
79
4F
80
50
81
51
82
52
83
53
Numeric Values
ASCII Character
Meaning
Keyboard Entry
84
54
85
55
86
56
87
57
88
58
89
59
90
5A
91
5B
92
5C
93
5D
94
5E
95
5F
96
60
97
61
98
62
99
63
100
64
101
65
102
66
103
67
104
68
105
69
106
6A
107
6B
108
6C
109
6D
110
6E
111
6F
Numeric Values
ASCII Character
Meaning
Keyboard Entry
112
70
113
71
114
72
115
73
116
74
117
75
118
76
119
77
120
78
121
79
122
7A
123
7B
124
7C
125
7D
126
7E
Tilde
127
7F
DEL
Delete
Del