Cisco IOS Configuration Fundamentals Command Reference
Cisco IOS Configuration Fundamentals Command Reference
Command Reference
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
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
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
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
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
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
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
Prefix Description
ftp: Specifies a File Transfer Protocol (FTP) network
server.
The following table lists the available suffix options (file indentification suffixes) for the URL prefixes
used in the previous table.
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.
Prefix Description
bootflash: Boot flash memory.
Prefix Description
flash: partition-number Flash memory. This prefix is available on all
platforms. For platforms that do not have a device
named flash:, the prefix flash: is aliased to slot0:.
Therefore, you can use the prefix flash: to refer to
the main Flash memory storage area on all
platforms.
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.
activation-character
To define the character you ent er at a vacant terminal to begin a terminal session, use the activation-
character 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
Usage Guidelines See the “ASCII Character Set and Hexadecimal Values” document for a list of ASCII characters.
Note If you are using the autoselect function, set the activation character to the default, Return, and exec-
character-bits to 7. If you change these defaults, the application will not recognize the activation request.
Examples The following example shows how to set the activation character for the console to Delete, which is
decimal character 127:
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.
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.
Usage Guidelines You can use simple words or abbreviations as command aliases.
The table below lists the basic EXEC mode aliases that are enabled by default.
p ping
r resume
s show
w 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”:
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
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:
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.
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:
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
Examples In the following example, the alias fixmyrtis configured for the clear iproute 192.168.116.16 EXEC mode
command:
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
archive
To enter archive configuration mode, use the archive command in global configuration mode.
archive
Examples The following example shows how to place the router in archive configuration mode:
Command Description
maximum Sets the maximum number of archive files of the
running configuration to be saved in the Cisco IOS
configuration archive.
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
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
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:
Command Description
configure replace Replaces the current running configuration with a
saved Cisco IOS configuration file.
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.
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:
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.
Syntax Description /create destination-url flash:/ file-url Creates a new TAR file on the local or network file
system.
For destination-url, specify the destination URL
alias for the local or network file system and the
name of the TAR file to create. The following
options are supported:
• flash: --Syntax for the local flash file system.
• ftp: [[// username[: password]@ location]/
directory]/ tar-filename.tar-- Syntax for FTP.
• rcp: [[// username @ location]/ directory]/
tar-filename.tar--Syntax for Remote Copy
Protocol (RCP).
• tftp: [[// location]/ directory]/ tar-
filename.tar--Syntax for TFTP.
The tar-filename.tar is the name of the TAR file to
be created.
For flash:/ file-url, specify the location on the local
flash file system from which the new TAR file is
created.
An optional list of files or directories within the
source directory can be specified to write to the
new TAR file. If none is specified, all files and
directories at this level are written to the newly
created TAR file.
/xtract source-url flash:/ file-url [dir/file...] Extracts files from a TAR file to the local file
system.
For source-url, specify the source URL alias for the
local file system. These options are supported:
• flash: --Syntax for the local flash file system.
• ftp: [[// username[: password]@ location]/
directory]/ tar-filename.tar-- Syntax for FTP.
• rcp: [[// username @ location]/ directory]/
tar-filename.tar--Syntax for Remote Copy
Protocol (RCP).
• tftp: [[// location]/directory]/tar-filename.tar--
Syntax for TFTP.
The tar-filename.tar is the name of the TAR file to
be created.
Release Modification
12.4(22)YB This command was integrated into Cisco IOS
Release 12.4(22)YB.
Usage Guidelines Filenames, directory names, and image names are case sensitive.
The TAR file is an archive file from which you can extract files by using the archive tarcommand.
Examples The following example shows how to create a TAR file. The command writes the contents of the new-
configs directory on the local flash device to a file named saved.tar on the TFTP server at 172.20.136.9.
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.
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.
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.
Keyword Description
bootfile Specifies use of a server boot file from which to
download the boot program. Use the
optional :hostname argument and the data argument
to specify the filename.
Keyword Description
DNS-server address Dotted decimal address specifying the IP address of
domain name servers (as defined by RFC 1034).
hostname name The name of the client, which may or may not be
domain qualified, depending upon the site.
Command Default If no extended BOOTP commands are entered, the Cisco IOS software generates a gateway and subnet
mask appropriate for the local network.
Usage Guidelines Use the show async-bootp EXEC command to list the configured parameters. Use the no async-bootp
command to clear the list.
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.”
The following example specifies a negative time offset of the local subnetwork of 3600 seconds:
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.
Syntax Description slot-number Slot number of the line card to which you wish to
connect.
If you omit the slot number, you will be prompted
for it.
Note Do not execute the configEXEC command from the Cisco IOS software image on the line card.
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 Switch-
sp#, 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:
• You can enter the exit command as follows:
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!
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#
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
Usage Guidelines 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).
Note Automatic baud detection must be disabled by using the no autobaud command prior to setting the txspeed,
rxspeed, or speed commands.
Examples In the following example, the auxiliary port is configured for autobaud detection:
Router(config-line)# autobaud
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.
Command Default 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)
Examples
Cisco 7600 Series Routers
The following example shows how (from the default configuration) to enable automatic synchronization of
the configuration register in the main CPU:
Router#
configure terminal
Router (config)#
redundancy
Router (config-r)#
main-cpu
Router (config-r-mc)#
no auto-sync standard
Router (config-r-mc)#
auto-sync config-register
router(config)# redundancy
router(config-r)# main-cpu
router(config-r-mc)# auto-sync startup-config
router(config-r-mc)# exit
router(config-r)# exit
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
autoupgrade disk-cleanup
To configure the Cisco IOS Auto-Upgrade Manager disk cleanup utility, use the autoupgrade disk-
cleanup command in global configuration mode. To disable this configuration, use the no form of this
command.
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.
Examples The following example shows how to clean-up filesystems that support undelete operation:
autoupgrade status email Configures the address to which the status email is
to be sent.
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:
autoupgrade status email Configures the address to which the status email is
to be sent.
Command Description
upgrade automatic getversion Downloads a Cisco IOS software image directly
from www.cisco.com or from a non-Cisco server.
Syntax Description recipient The address to which the Cisco IOS Auto-Upgrade
Manager (AUM) status is to be sent.
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.
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:
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.
Usage Guidelines 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
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 router’s host name and IP address. The tokens are described
in the table below.
Examples 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.
Command Description
exec-banner Controls (enables or disables) the display of EXEC
banners and message-of-the-day banners on a
specified line or lines.
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.
Usage Guidelines 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
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 router’s host name and IP address. The tokens are described
in the table below.
Examples The following example sets an incoming connection banner. The pound sign (#) is used as a delimiting
character.
The following example sets an incoming connection banner that uses several tokens. The percent sign (%)
is used as a delimiting character.
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.
Command Description
banner login Defines a customized banner to be displayed before
the username and password login prompts.
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.
Usage Guidelines 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.
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 router’s host name and IP address. The tokens are described
in the table below.
Examples 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.
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.
Command Description
banner slip-ppp Defines a customized banner to be displayed when
a serial-line IP or point-to-point connection is
made.
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
Usage Guidelines 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
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 router’s host name and IP address. The tokens are described
in the table below.
Examples 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.
When the MOTD banner is executed, the user will see the following. Notice that the $(token ) syntax is
replaced by the corresponding configuration variable.
Command Description
banner slip-ppp Defines and enables a customized banner to be
displayed when a serial-line IP or point-to-point
connection is made.
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.
The banner message when using the service old-slip-prompt command is:
Usage Guidelines 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.
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.
Examples The following example sets the SLIP/PPP banner using several tokens and the percent sign (%) as the
delimiting character:
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...
Command Description
banner motd Defines and enables a customized message-of-the-
day banner.
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]
Syntax Description file-url URL of the image to boot (for example, boot tftp://
172.16.15.112/routertest).
flash Boots the router from Flash memory. Note that this
keyword is required in some boot images.
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.
Usage Guidelines 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.
• 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 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.
> boot
F3:
(ROM Monitor copyrights)
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:
The following example shows the boot flash command without the filename argument. The first valid file
in Flash memory is loaded.
The following example boots from Flash memory using the file named gs7-k:
In the following example, the boot flash flash: command boots the relocatable image file named igs-bpx-l
from partition 2 in Flash memory:
In the following command, the Cisco 7000 family router accepts the flash keyword for compatibility but
ignores it, and boots from slot 0:
In the following example, the command did not function because it must be entered in lowercase:
The following example boots the first file in the first partition of internal Flash memory of a Cisco 3600
series router:
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:
The following example shows the ROM monitor booting the first file in the first Flash memory partition on
a Cisco 1600 series router:
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.
Syntax Description file-url URL of the boot image on a Flash file system.
Command Default Refer to your platform documentation for the location of the default boot image.
Usage Guidelines 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.
Examples In the following example, the internal Flash memory contains the boot image:
The following example specifies that the Flash memory card inserted in slot 0 contains the boot image:
show (flash file system) Displays the layout and contents of a Flash memory
file system.
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.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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:
Command Description
boot system Specifies the system image that the router loads at
startup.
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.
Command Default The default location for the configuration file is NVRAM (nvram:).
Release Modification
12.2(14)SX Support for this command was added for the Cisco
7600 Supervisor Engine 720.
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.
The following example instructs a Cisco 7500 series router to use the configuration file named router-
config 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.
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.
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.
Usage Guidelines 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.
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 router-
confg.
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.
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:
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.
Usage Guidelines 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
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 router-
confg.
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.
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:
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:
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.
Syntax Description file-url The URL of the system image to load at system
startup.
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.
Usage Guidelines 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.
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.
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:
The following example boots the system boot relocatable image file named igs-bpx-l from partition 2 of the
flash device:
The following example instructs the router to boot from an image located on the flash memory card
inserted in slot 0:
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.
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:
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.
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:
Enter configuration commands, one per line. End with the end command.
Router(config)# boot system slot0:
Router(config)# end
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:
boot system Specifies the system software image that the router
loads at startup.
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.
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:
Enter configuration commands, one per line. End with the end command.
Router(config)# boot system slot0:
Router(config)# end
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:
boot system Specifies the system software image that the router
loads at startup.
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 filesystem : (Optional) The URL or alias of the directory or file
systems followed by a colon.
Command Default 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.
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:/
Router# cd disk0:
Router#
pwd
disk0:/
show file systems Lists available file systems and their alias prefix
names.
Syntax Description force (Optional) Eliminates the confirm step before the
contents of the archive log are cleared.
Command Default If this command is not used, the database entries accumulate in the archive log.
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:
Examples This example shows how to clear the traffic meter counters:
Examples The following is sample output from the clear configuration lockcommand when the running
configuration file is not locked by the configure replace command:
The following is sample output from the clear configuration lockcommand when the running
configuration file is locked by the configure replace command:
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:
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>
show configuration lock Displays information about the lock status of the
running configuration file during a configuration
replace operation.
clear diagnostic event-log {event-type {error | info | warning} | module {num | slot subslot | all}}
module num | slot subslot Specifies clearing events for a specific module.
Usage Guidelines 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.
This example shows how to clear error event logs on all the modules:
Syntax Description cache all Removes all HTTP client cache entries.
cache session session-name Removes HTTP client cache entries of the HTTP
client application session specified by the session-
name argument.
cache url complete-url Removes the HTTP client cache entry whose
location is specified by the complete-url argument,
a Cisco IOS File System (IFS) Uniform Resource
Locator (URL), and that consists of HTML files
used by an HTTP server.
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:
The following example removes HTTP client cache entries that belong to the HTTP Client File System
(CFS) application:
The following example removes HTTP client cache entries at the location http://myrouter.cisco.com/flash:/:
clear logging
To clear messages from the logging buffer, use the clear logging command in privileged EXEC mode.
Cisco IOS XE Release 2.4 This command was modified. The persistentand
url keywords, and the filesystem:/directory
arguments were added.
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.
The following example shows how to clear persistent logging files from a specific directory:
Syntax Description disk name (Optional) Stores the system event log in the
specified disk.
Usage Guidelines 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.
Related Commands copy logging system Copies the archived system events to another
location.
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.
Command Description
show logging xml Displays the state of XML-formatted system
message logging, followed by the contents of the
XML-specific buffer.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines This command clears all processor threshold values and the input/output memory threshold values, if any.
Examples The following example shows how to clear the low-water-mark memory:
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#
Usage Guidelines 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 The following example shows the clearing of the parser cache:
show parser statistics Displays statistics about the last configuration file
parsed and the status of the Parser Cache feature.
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..
Bootup hits:125
Bootup misses:43
Bootup clear parser cache:0
show parser statistics Displays statistics about the last configuration file
parsed and the status of the Parser Cache feature.
Examples This example shows how to clear the interrupt-throttling counters for the platform:
Router#
clear platform netint
Router#
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:
scheduler interrupt mask size Configures the maximum number of entries that
can exist in the interrupt mask buffer.
scheduler interrupt mask time Configures the maximum time that a process can
run with interrupts masked.
show process interrupt mask buffer Displays the information stored in the interrupt
mask buffer.
Command Description
show processes interrupt mask detail Displays interrupt masked details for the specified
processes or all processes in the system.
Examples The following example shows how to clear the SCP accounting information:
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 line line-number Line number of the TCP connection to clear.
local hostname port remote hostname port Host name of the local router and port and host
name of the remote router and port of the TCP
connection to clear.
Usage Guidelines 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.
SRTT: 710 ms, RTTO: 4442 ms, RTV: 1511 ms, KRTT: 0 ms
minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms
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.
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.
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:
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.
• 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 passive-
clock 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.
show running-config interface Displays the status and configuration of the module
or Layer 2 VLAN.
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.
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:
config-register
To change the configuration register settings, use the config-register command in global configuration
mode.
config-register 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.
Usage Guidelines 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.
• 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 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.
Examples In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x2102
Examples The following example shows how to check the syntax configuration using the configure check syntax
command:
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.
Release Modification
12.2(33)SXI This command was integrated into a release earlier
than Cisco IOS Release 12.2(33)SXI.
Cisco IOS XE Release 3.1S This command was replaced by the parser
command serializer command.
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.
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
The configuration mode is locked exclusively. The lock is cleared after you exit from configuration mode
by entering the end or exitcommand.
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
Building configuration...
Current configuration : 2298 bytes
configuration mode exclusive manual <==== 'manual' policy
Router# show configuration lock
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
lock Lock configuration mode <======= 'lock' option displayed when in 'manual' policy
Router# configure terminal lock
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.
Command Description
debug configuration lock Enables debugging of the Cisco IOS configuration
lock.
show configuration lock Displays information about the lock status of the
running configuration file during a configuration
replace operation.
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
Usage Guidelines 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).
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:
path (config-archive) Specifies the location and filename prefix for the
files in the Cisco IOS configuration archive.
configure memory
To configure the system from the system memory, use the configure memory command in privileged
EXEC mode.
configure memory
Usage Guidelines 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:
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.
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.
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 URL (accessible by the Cisco IOS file system) of
the saved Cisco IOS configuration file that is to
replace the current running configuration.
Usage Guidelines 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.
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.
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.
In the following example, the list keyword is specified to display the command lines that were applied
during the configuration replace operation:
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:
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:
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 now Cancels the timed rollback and reverts immediately.
Usage Guidelines 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:
• Confirm the configuration change
• Reset the timer
• Cancel the timer and trigger rollback immediately
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
path (config-archive) Specifies the location and filename prefix for the
files in the Cisco IOS configuration archive.
2. configure terminal
To enter global configuration mode, use the configure terminal command in privileged EXEC mode.
configure terminal
idle minutes Idle time in minutes (1-120) for which to wait for
confirmation.
Release Modification
12.4(20)T The revertkeyword option was added, along with
the timer parameters of idle and minutes.
Usage Guidelines 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:
configuration mode exclusive Enables locking of the configuration file for single
user access.
Command Description
show running-config Displays the currently running configuration.
or
more system:running-config
confreg
To change the configuration register settings while in ROM monitor mode, use the confreg command in
ROM monitor mode.
confreg [value]
Command Default Refer to your platform documentation for the default configuration register value.
Usage Guidelines 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.
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:
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
continue
Usage Guidelines 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.
Caution While in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a reset or
the continue command.
Examples In the following example, the continue command switches the router from ROM monitor to EXEC mode:
> continue
Router#
copy
To copy any file from a source to a destination, use the copy command in privileged EXEC or diagnostic
mode.
Syntax Description /erase (Optional) Erases the destination file system before
copying.
Note This option is typically provided on
platforms with limited memory to allow for
an easy way to clear local flash memory
space.
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.
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.
The table belows lists URL prefix keywords for remote file systems.
The table below lists URL prefix keywords for local writable storage file systems.
Table 14 URL Prefix Keywords for Local Writable Storage File Systems
Release Modification
12.2(28)SB This command was integrated into Cisco IOS
Release 12.2(28)SB.
Cisco IOS XE Release 2.1 The Cisco ASR1000 series routers became
available, and introduced the copy command in
diagnostic mode.
Usage Guidelines 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:startup-
configcommand). 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:
• From a running configuration to a running configuration
Character Description
! For network transfers, an exclamation point
indicates that the copy process is taking place. Each
exclamation point indicates the successful transfer
of ten packets (512 bytes each).
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
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
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 Verify the image in flash memory before booting the image.
Verifying Images
When copying a new image to your router, you should confirm that the image was not corrupted during the
copy process. You can verify the integrity of the image in any of the following ways:
• 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.
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.
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.
On a Cisco 7507 or Cisco 7513 router configured for Dual RSPs, if you copy a file to nvram:startup-
configuration 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.
Router#
copy rcp://[email protected]/file1 flash:file1
Destination file name [file1]?
Accessing file 'file1' on 172.16.101.101...
Loading file1 from 172.16.101.101 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
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 flash: rcp:
IP address of remote host [255.255.255.255]? 172.16.13.110
Name of file to copy? gsxx
writing gsxx - copy complete
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:
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.
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#
copy bootflash:file1 tftp://192.168.117.23/file1
Verifying checksum for 'file1' (file # 1)... OK
Copy 'file1' from Flash to server
as 'file1'? [yes/no]y
!!!!...
Upload to server done
Flash copy took 0:00:00 [hh:mm:ss]
Router#
copy rcp://[email protected]/host1-confg system:running-config
Configure using host1-confg from 172.16.101.101? [confirm]
Connected to 172.16.101.101
Loading 1112 byte file host1-confg:![OK]
Router#
%SYS-5-CONFIG: Configured from host1-config by rcp from 172.16.101.101
Router#
copy ftp://netadmin1:[email protected]/host2-confg nvram:startup-config
Configure using rtr2-confg from 172.16.101.101?[confirm]
Connected to 172.16.101.101
Loading 1112 byte file rtr2-confg:![OK]
[OK]
Router#
%SYS-5-CONFIG_NV:Non-volatile store configured from rtr2-config by
FTP from 172.16.101.101
Router(config)#
end
Router#
copy system:running-config rcp:
Router#
copy nvram:startup-config tftp:
Remote host[]? 172.16.101.101
The following example shows the warning that the system provides if you try to save configuration
information from bootstrap into the system:
Building configuration...
Router# copy
http://
www.example.com:8080/configs/config1 flash:config1
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(config)# end
In the following example, an HTTP proxy server is specified before using the copy http:// command:
Router(config)# end
Router# copy
http://
www.example.com/configs/config3 flash:/configs/config3
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:
boot system Specifies the system image that the router loads at
startup.
show (flash file system) Displays the layout and contents of a flash memory
file system.
copy http
The copy http:// command is documented as part of the copy command.
copy https
The copy https:// command is documented as part of the copy command.
Syntax Description target : Specifies the destination file system; Valid values
are as follows:
• bootflash:
• disk0:
• disk1:
• ftp:
• http:
• https:
• rcp:
• slavebootflash:
• slavedisk0:
• slavedisk1:
• slavesup-bootdisk:
• slavesup-bootflash:
• sup-bootdisk:
• sup-bootflash:
• tftp:
Release Modification
12.2(33)SCC The command was introduced for the Cisco
uBR10012 router in the Cisco IOS Software
Release 12.2(33)SCC.
Usage Guidelines 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:
The following example shows how to copy the SEA using the remote file copy function (rcp):
Related Commands clear logging system Clears the event records stored in the SEA.
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.
Usage Guidelines 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 router’s internal Flash
memory using the Xmodem protocol:
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.
Usage Guidelines 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 router’s internal Flash
memory using the Ymodem protocol:
copy noverify
To disable the automatic image verification for the current copy operation, use the copy /
noverifycommand.
Usage Guidelines 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).
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:startup-
configcommand). These aliases allow you to continue using some of the common commands that are used
in previous versions of Cisco IOS software.
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.
The table below lists the URL prefix aliases for network file systems.
The table below lists the URL prefix aliases for local writable storage file systems.
Table 19 URL Prefix Aliases for Local Writable Storage File Systems
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:
Command Description
verify Verifies the checksum of a file on a Flash memory
file system or compute an MD5 signature for a file.
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
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
terminal databits Changes the number of data bits per character for
the current terminal line for this session.
terminal data-character-bits Sets the number of data bits per character that are
interpreted and generated by the Cisco IOS
software for the current line and session.
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
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:
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
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
Examples The following example shows how to set the default number of data character bits to 8:
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 7 Selects the 7-bit ASCII character set. This is the
default.
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:
default-value modem-interval
To configure the default frequency time to scan modem signals, use the default-value modem-
intervalcommand in global configuration mode. To disable the configured frequency, use the no form of
this command.
Examples The following example shows how to set the default time to scan the modem signal to 345 ms:
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.
Syntax Description 7 Selects the 7-bit character set. This is the default.
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:
Command Description
exec-character-bits Configures the character widths of EXEC and
configuration command characters.
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.
Usage Guidelines
• 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
◦ 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
delete
To delete a file on a Flash memory device or NVRAM, use the delete command in EXEC, privileged
EXEC, or diagnostic mode.
Syntax Description url Cisco IOS File System URL of the file to be
deleted. Include the file system prefix, followed by
a colon, and, optionally, the name of a file or
directory. See the table below for a list of supported
URLs.
Release Modification
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers and the following
enhancements were introduced:
• This command was introduced in diagnostic
mode for the first time. The command can be
entered in both privileged EXEC and
diagnostic mode on the Cisco ASR1000 Series
Routers.
• The harddisk:, obfl:, stby-bootflash: stby-
harddisk:, stby-nvram: , stby-obfl:, stby-
usb[0-1]:, and usb[0 1]: url options were
introduced.
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.
Prefix Filesystem
bootflash: Delete the file from boot Flash memory.
obfl: Delete the file from the onboard failure logging file
system.
Prefix Filesystem
stby-harddisk: Delete the file from the standby harddisk file
system.
stby-obfl: Delete the file from the onboard failure logging file
system on the standby hardware.
stby-usb [ 0 - 1 ]: Delete the file from the standby USB Flash drive.
Examples The following example deletes the file named test from the Flash card inserted in slot 0:
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 slot-number Slot number of the line card you want to test. Slot
numbers range from 0 to 11 for the Cisco 12012
and 0 to 7 for the Cisco 12008 router. Slot numbers
for the CSC are 16 and 17, and for the FSC are 18,
19, and 20.
Command Default No field diagnostics tests are performed on the line card.
Usage Guidelines 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 router’s 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.
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:
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#
Usage Guidelines Setting the diagnostic level determines the level of testing that occurs when the system or module is reset.
The two levels are as follows:
• Complete--Runs all tests.
• Minimal--Runs only EARL tests for the supervisor engine and loopback tests for all ports in the
system.
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
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.
Command Default The following are the default settings for diagnostic cns:
diagnostic cns publish cisco.cns.device.diag_results
diagnostic cns subscribe cisco.cns.device.diag_commands
Usage Guidelines 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.
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 enable the publishing of diagnostic results:
Router(config)#
diagnostic cns publish my.cns.publish
Router(config)#
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)#
Router(config)#
default
diagnostic cns publish
Router(config)#
show diagnostic cns subscribe Displays the subscribe information about the CNS
subject.
Syntax Description size Diagnostic event-log sizes. The valid values range
from 1 to 10000 entries.
Usage Guidelines The events are dynamically allocated and stored in a circular queue.
You can enter either the default diagnostic event-log size command or the no diagnostic event-log size
command to return to the default settings.
Examples The following example shows how to set the diagnostic event-log size:
Router(config)#
diagnostic event-log size 600
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.
Usage Guidelines 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.
Examples The following example shows how to enable diagnostic power-on tests:
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 This output is displayed when the system is booting, not when the command is issued.
show c7300 Displays the types of cards (NSE and line cards)
installed in a Cisco 7300 series router.
show redundancy (7300) Displays redundancy information for the active and
standby NSEs.
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}
bay slot/bay Indicates the card slot and bay number where the
diagnostic test is run periodically and monitored.
The bay keyword is used to refer a SPA on the
router. The valid range for the slot number is from
1 to 8 and 0 to 3 for the bay number.
slot slotnumber Indicates the slot number of the full-height line card
where the diagnostic test is run periodically and
monitored. The slot keyword is used to refer a full-
height line card on the router. The valid range for
the slot is from 1 to 8.
failure count failures Configures the count for maximum failures allowed
after which the failed test results are displayed in
the output of the show diagnostic resultscommand.
The range for number of allowed failures is 0 to 99.
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:
The following example shows how to enable the generation of a syslog message when any health-
monitoring test fails:
Router(config)#
diagnostic monitor syslog
The following example shows how to enable the diagnostic monitoring on bay 1/0:
Router(config)# diangostic monitor bay 1/0 test 2
The following example shows how to enable logging of failed messages to 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:
diagnostic ondemand
To configure the on-demand diagnostics, use the diagnostic ondemand command in privileged EXEC
mode.
Syntax Description iteration iteration-count Sets the number of times the same test to rerun
when the command is issued . The valid range for
iteration-count is between 1 to 999.
Release Modification
12.2(33)SCC The command was integrated in this release to
support Generic Online Diagnostics (GOLD)
functionalityfor Cisco UBR10012 Universal
Broadband Router.
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#
diagnostic schedule module {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 | weekly day-of-week hh:mm}
no diagnostic schedule module {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 | weekly day-of-week hh:mm}
Command Default Test-based diagnostic testing for a specific module is not scheduled.
You can specify a periodic switchover (daily or weekly) or a single switchover occurrence at a specific
time using these commands:
• diagnostic schedule module slot / subslot test test-id on mm dd yyyy hh:mm
• diagnostic schedule module slot / subslot test test-id daily hh:mm
• diagnostic schedule module slot / subslot test test-id weekly day-of-week hh:mm
Note 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.
Examples The following example shows how to schedule the diagnostic testing on a specific month, date and time for
a specific module:
The following example shows how to schedule the diagnostic testing to occur daily at a certain time for a
specific module:
The following example shows how to schedule the diagnostic testing to occur weekly on a certain day for a
specific module:
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
bay slot/bay Indicates the card slot and bay number where the
diagnostic test is executed. The bay keyword is
used to refer a SPA on the router. The valid range
for the slot number is from 1 to 8 and 0 to 3 for the
bay number.
slot slot-no Indicates the slot number of the full-height line card
where the diagnostic test is executed. The slot
keyword is used to refer a full-height line card on
the router. The valid range for slot is from 1 to 8.
Release Modification
12.2(33)SCC The command was integrated in this release to
support Generic Online Diagnostics (GOLD)
functionalityfor Cisco UBR10012 Universal
Broadband Router. The keywords bay, slot, and
subslot were added for the Cisco UBR10012
Universal Broadband Router.
Usage Guidelines
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.
Note 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:
show diagnostic description Provides the description for the diagnostic tests.
Command Description
show diagnostic ondemand settings Displays the settings for the on-demand
diagnostics.
show diagnostic result Displays the diagnostic test results for a module.
diagnostic stop
To stop the testing process, use the diagnostic stop command in privileged EXEC mode.
bay slot/bay Indicates the card slot and bay number of the SPA
for which the diagnostic test has stopped. The bay
keyword is used to refer a SPA on the router. The
valid range for the slot number is from 1 to 8 and 0
to 3 for the bay number.
slot slot-no Indicates the slot number of full height line card for
which the diagnostic test has to be stopped. The slot
keyword is used to refer a full-height line card on
the router. Valid range for the slot is from 1 to 8.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines Use the diagnostic start command to start 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 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:
This example shows how to stop the diagnostic test process for subslot 5/0 on the Cisco UBR10012
Universal Broadband Router:
show diagnostic description Provides the description for the diagnostic tests.
Command Description
diagnostic bootup level Configures the diagnostic bootup level.
show diagnostic ondemand settings Displays the settings for the on-demand
diagnostics.
show diagnostic result Displays the diagnostic test results for a module.
dir
To display a list of files on a file system, use the dircommand in EXEC, privileged EXEC, or diagnostic
mode.
Syntax Description /all (Optional) Lists deleted files, undeleted files, and
files with errors.
Command Default When you omit the /all keyword, the Cisco IOS software displays only undeleted files.
Command Modes User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Release Modification
12.4(11)T This command was modified. Support for this
command was implemented on the Cisco 7200VXR
NPE-G2 platform.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and the following
enhancements were introduced:
• The command was made available in
diagnostic mode.
• The /recursive option was introduced.
• The file systems available with the Cisco ASR
1000 Series Routers became available as
filesystem: options.
Usage Guidelines Use the show file systemscommand to display more details about the files in a particular file system.
Note 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.
Command Purpose
append regular expression Appends redirected output to URL (only to the
URLs supporting the append operation).
begin regular expression Displays the first line that matches the regular
expression, and then all other lines that follow that
line.
include regular expression Displays all lines that match the regular expression.
Command Purpose
exclude regular expression Displays all lines except those that match the
regular expression.
format regular expression Formats the output using the specification file.
Note The append, redirect and tee keywords do not support rcp in the display.
The table below describes the significant fields shown in the displays.
Field Description
1 Index number of the file.
Field Description
4720148 Size of the file, in bytes.
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.
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 privilege-level (Optional) Specific privilege level (other than user
EXEC mode).
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and became available in
diagnostic mode.
Usage Guidelines 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.
Note 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.
Examples 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>
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
Usage Guidelines 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:
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.
Usage Guidelines 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.
Examples The following example defines the Return character (decimal 13) as the dispatch character for virtual
terminal line (vty) line 4:
dispatch-machine
To specify an identifier for a TCP packet dispatch state machine on a particular line, use the dispatch-
machine 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 Name of the state machine that determines when to
send packets on the asynchronous line.
Usage Guidelines 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)# line 1
Router(config-line)# dispatch-machine linefeed
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
Usage Guidelines 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.
Note 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.
Examples The following example sets the dispatch timer to 80 milliseconds for virtual terminal line (vty) lines 0
through 4:
terminal dispatch-timeout Sets the character dispatch timer for the current
session.
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
Command Default A user EXEC or privileged EXEC command is not executed from a configuration mode.
Usage Guidelines 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.
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:
The following example shows how to enter the clear vpdn tunnel user EXEC or privileged EXEC
command from within VPDN configuration mode:
downward-compatible-config
To generate a configuration that is compatible with an earlier Cisco IOS release, use the downward-
compatible-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 Cisco IOS release number, not earlier than Release
10.2.
Note You must have a period (.) in the version
number. For example, 12.4.
Command Default The configuration is not compatible with earlier Cisco IOS releases.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines In Cisco IOS Release 10.3, IP access lists changed format. Use the downward-compatible-
configcommand 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.
Examples The following example shows how to generate a configuration file compatible with Cisco IOS Release 10.2
access lists:
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
Usage Guidelines 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.
Return (at the --More-- prompt) Continue Displays the next line of output.
Space Bar (at the --More-- Continue Displays the next screen of
prompt) output. The amount of output you
see will depend on the screen
depth setting of your terminal.
Left Arrow1 or Ctrl-B B ack character Moves the cursor one character to
the left. When you enter a
command that extends beyond a
single line, you can press the Left
Arrow or Ctrl-B keys repeatedly
to scroll back toward the system
prompt and verify the beginning
of the command entry.
Right Arrow1 or Ctrl-F F orward character Moves the cursor one character to
the right.
Esc, D D elete next word Deletes from the cursor to the end
of the word.
Ctrl-W Delete previous word Deletes the word to the left of the
cursor.
Ctrl-U or Ctrl-X Delete line backward Deletes all characters from the
cursor back to the beginning of
the command line.
Esc, Y Recall next deleted command Recalls the next entry in the
delete buffer. The delete buffer
contains the last ten items you
have deleted. Press Ctrl-Y first to
recall the most recent entry. Then
press Esc Y up to nine times to
recall the remaining entries in the
buffer. If you bypass an entry,
continue to press Esc Y to cycle
back to it.
Router(config)# line 3
Router(config-line)# no editing
1. 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.
Release Modification
12.2(33)SB This command was integrated into Cisco IOS
Release 12.2(22)SB.
Cisco IOS XE Release 2.1 This command became available on the ASR 1000
Series Routers, and became available in diagnostic
mode for the first time.
Usage Guidelines 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>
The following example shows which commands are available inside the CLI view “first” after the user has
logged into this view:
The following example shows how to use the enable view command to switch from the root view to the
CLI 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'
privilege level (line) Sets a privilege level for a command for a specific
line.
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.
Command Default The password parameters for the router are not enabled.
Examples 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
end
To en d the current configuration session and return to privileged EXEC mode, use the end command in
global configuration mode.
end
Usage Guidelines This command will bring you back to privileged EXEC mode regardless of what configuration mode or
configuration submode you are in.
Note This global configuration command can be used in any configuration mode.
Use this command when you are done configuring the system and you want to return to EXEC mode to
perform verification steps.
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(config-alps-ascu)# end
Router# show interface serial 1:1
Examples 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)#
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
Usage Guidelines 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 This example shows how to enable the ambient temperature control:
Router(config)#
environment temperature-controlled
Router(config)#
This example shows how to disable the ambient temperature control:
Router(config)#
no environment temperature-controlled
Router(config)#
erase
To erase a file system or all files available on a file system, use the erasecommand in privileged EXEC or
diagnostic mode.
Cisco 7600 Series Routers and Cisco ASR 1000 Series Routers
erase {/all nvram: | filesystem: | startup-config}
Syntax Description /all Erases all files in the specified file system.
Release Modification
Cisco IOS XE Release 2.1 This command was modified. The command was
introduced in diagnostic mode on the Cisco ASR
1000 Series Routers, and the /all keyword was
added.
Usage Guidelines The erase nvram: command replaces the write erase command and the erase startup-config command.
Caution 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.
Examples The following example shows how to erase the NVRAM, including the startup configuration located there:
The following example shows how to erase all of partition 2 in internal flash memory:
The following example shows how to erase flash memory when flash is partitioned, but no partition is
specified in the command:
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.
Command Description
squeeze Removes all deleted files from the flash file system
and recovers the memory space used by deleted
files.
erase bootflash
The erase bootflash: and erase bootflash commands have identical functions. See the description of the
erasecommand in this chapter for more information.
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 error-
disable 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
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.
Usage Guidelines A cause (bpduguard, channel-misconfig, dhcp-rate-limit, dtp-flap, l2ptguard, link-flap, pagp-flap, psecure-
violation, security-violation, rootguard, udld, or unicast-flood) is defined as the reason why the error-
disable 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.
You must enter the shutdown command and then the no shutdown command to manually recover an
interface from the error-disable state.
Note 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.
Examples 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
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 Sets the escape character to Break. Note that the
Break key should not be used as an escape
character on a console terminal.
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).
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:
• The length of the logout sequence must be 14 characters or fewer.
• The soft escape character cannot be the same as the generic Cisco escape character, Break, or the
characters b, d, n, or s.
• The soft escape character should be an ASCII value from 1 to 127. Do not use the number 30.
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 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
terminal escape-character Sets the escape character for the current terminal
line for the current session.
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
Usage Guidelines 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.
Router(config)# line 7
Router(config-line)# no exec
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
Usage Guidelines 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.
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
Examples The following example suppresses the EXEC and MOTD banners on virtual terminal lines 0 to 4:
Router(config-line)# no exec-banner
exec-character-bits
To configure the character widths of EXEC and configuration command characters, use the exec-
character-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 7 Selects the 7-bit character set. This is the default.
Usage Guidelines 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.
Note 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.
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.
exec-timeout
To set the interval that the EXEC command interpreter waits until user input is detected, use the exec-
timeout command in line configuration mode. To remove the timeout definition, use the no form of this
command.
Syntax Description minutes Integer that specifies the number of minutes. The
default is 10 minutes.
Usage Guidelines 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.
Router(config-line)# exec-timeout 0 10
execute-on
To execute commands on a line card, use the execute-on command in privileged EXEC mode.
Syntax Description slot slot-number Executes the command on the line card in the
specified slot. Slot numbers can be chosen from the
following ranges:
• Cisco 12012 router: 0 to 11
• Cisco 12008 access server: 0 to 7
• Cisco AS5800 access server: 0 to 13
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.
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.
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 tech-
supportcommand.
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.
The show tech-supportcommand for each dial shelf card is bundled into the router shelf's show tech-
support command via the execute-on facility.
The execute-on command also support interactive commands such as the following:
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:
slot
reload
You can use the execute-on command to enable remote execution of the commands included in the
following partial list:
• debug dsc clock
• show context
• show diag
• show environment
• show dsc clock
• show dsi
• show dsip
• show tech-support
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:
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:
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
exit (EXEC)
To close an active terminal session by logging off the router, use the exit command in EXEC mode.
exit
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
Command Description
exit (global) Exits from the current configuration mode to the
next highest configuration mode.
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
Usage Guidelines 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)#
file prompt
To specify the level of prompting, use the file promptcommand in global configuration mode.
Usage Guidelines 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:
Command Default Image verification is not automatically applied to all images that are copied or reloaded onto a router.
Usage Guidelines 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
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 The following example shows how to enable automatic image verification:
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.
Command Default spare-number : 0monlib-filename:The monlib file bundled with the system software
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers and the following
enhancements were introduced:
• This command was introduced in diagnostic
mode for the first time. The command can be
entered in both privileged EXEC and
diagnostic mode on the Cisco ASR 1000 Series
Routers.
• The harddisk:, obfl:, stby-harddisk:, stby-
usb[0-1]: and usb[0-1]: filesystem1 : options
were introduced.
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
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:
• 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 :arguments’s own monlib file in this argument. If the system cannot
find a monlib file, it terminates its formatting.
Note 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.
Examples The following example shows how to format a flash memory card that is inserted in slot 0:
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:
This follwing example shows how a format operation cleans up the disk and writes the monitor library on
the disk filesystem:
show disk0: all Displays ATA MONLIB file information for disk0.
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:]
Command Default 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.
This command is available in both privileged EXEC and diagnostic mode on the Cisco ASR1000 series
routers.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers and the following
enhancements were introduced:
• This command was introduced in diagnostic
mode for the first time. The command can be
entered in both privileged EXEC and
diagnostic mode on the Cisco ASR 1000 series
routers.
• The /all option was introduced.
• The harddisk:, obfl:, stby-harddisk:, stby-
usb[0-1]:,and usb[0-1]: filesystem : options
were introduced.
Usage Guidelines Supported Platforms Other than Cisco 7600 Series Router
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.
Checks Actions
Checks the boot sector and the partition table and reports the No action.
errors.
Validates the media with the signature in the last 2 bytes of the No action.
first sector (0x55 and 0xaa, respectively).
Checks the number of FAT’s field (correct values are 1 and 2). No action.
Checks Actions
Checks these values: No action.
• n_fat_sectors cannot be less than 1.
• n_root_entries cannot be less than 16.
• n_root_sectors cannot be less than 2.
• base_fat_sector, n_sectors_per_cluster, n_heads,
n_sectors_per_track is not 0.
Checks the FAT for invalid cluster numbers. If the cluster is a part of a file chain, the cluster is changed to
end of file (EOF). If the cluster is not part of a file chain, it is
added to the free list and unused cluster chain. The table below
lists valid cluster numbers; numbers other than those listed in
the table below are invalid numbers.
Checks the file’s cluster chain for loops. If the loop is broken, the file is truncated at the cluster where
the looping occurred.
Checks the directories for nonzero size fields. If directories are found with nonzero size fields, the size is reset
to zero.
Checks for invalid start cluster file numbers. If the start cluster number of a file is invalid, the file is deleted.
Checks files for bad or free clusters. If the file contains bad or free clusters, the file is truncated at
the last good cluster; an example is the cluster that points to
this bad/free cluster.
Checks to see if the file’s cluster chain is longer than indicated If the file’s cluster chain is longer than indicated by the size
by the size fields. fields, the file size is recalculated and the directory entry is
updated.
Checks to see if two or more files share the same cluster If two or more files are crosslinked, you are prompted to accept
(crosslinked). the repair, and one of the files is truncated.
Checks to see if the file’s cluster chain is shorter than is If the file’s cluster chain is shorter than is indicated by the size
indicated by the size fields. fields, the file size is recalculated and the directory entry is
updated.
Checks to see if there are any unused cluster chains. 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.
Available cluster 0 0
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
Checking the boot sector and partition table...
Checking FAT, Files and Directories...
Files
1) disk0:/FILE3 and
2) disk0:/FILE2
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
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 Boot Flash information
calendar Display the hardware calendar
clock Display the system clock
context Show context information
dialer Dialer parameters and statistics
history Display the session command history
hosts IP domain-name, lookup style, nameservers, and host table
isdn ISDN information
kerberos Show Kerberos Values
modemcap Show Modem Capabilities database
ppp PPP parameters and statistics
rmon rmon statistics
sessions Information about Telnet connections
snmp snmp statistics
terminal Display terminal configuration parameters
users Display information about terminal lines
version System hardware and software status
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
help
To display a brief description of the help system, use the help command in any command mode.
help
Usage Guidelines The help command provides a brief description of the context-sensitive help system, which functions as
follows:
• 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.
Examples 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
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 copy
Router# co
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.
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
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(config)# archive
Router(config-archive)# log config
Router(config-archive-log-config)# hidekey
s
Router(config-archive-log-config)# end
show archive log config Displays entries from the configuration log.
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
Usage Guidelines 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.
Key(s) Functions
Ctrl-P or Up Arrow2 Recalls commands in the history buffer in a
backward sequence, beginning with the most recent
command. Repeat the key sequence to recall
successively older commands.
Examples In the following example, the command history function is disabled on line 4:
Router(config)# line 4
Router(config-line)# no history
show history Lists the commands you have entered in the current
EXEC session.
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.
Syntax Description number-of-lines Specifies the number of command lines that the
system will record in its history buffer. The range is
from 0 to 256. The default is 10.
Usage Guidelines 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.
Note 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.
Examples 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
show history Lists the commands you have entered in the current
EXEC session.
terminal history size Enables the command history function for the
current terminal session or changes the size of the
command history buffer for the current terminal
session.
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
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
hostname
To specify or modify the hostname for the network server, use the hostname command in global
configuration mode.
hostname name
Cisco IOS XE Release 2.5 This command was integrated into Cisco IOS XE
Release 2.5.
Usage Guidelines The hostname is used in prompts and default configuration filenames.
Do not expect case to be preserved. Uppercase and lowercase characters look the same to many internet
software applications. It may seem appropriate to capitalize a name the same way you might do in English,
but conventions dictate that computer names appear all lowercase. For more information, refer to RFC
1178, Choosing a Name for Your Computer .
The name must also follow the rules for ARPANET hostnames. They must start with a letter, end with a
letter or digit, and have as interior characters only letters, digits, and hyphens. Names must be 63 characters
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.
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.
Syntax Description module num Applies the command to a specific module; see the
“Usage Guidelines” section for valid values.
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.
Router#
hw-module module 3 reset
hw-module shutdown
To shut down the module, use the hw-module shutdown command in privileged EXEC mode.
Syntax Description module num Applies the command to a specific module; see the
“Usage Guidelines” section for valid values.
Usage Guidelines 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:
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
Usage Guidelines Use this command to identify a modem line as insecure for DEC local area transport (LAT) classification.
Router(config)# line 10
Router(config-line)# insecure
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
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
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
Usage Guidelines 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.
Note 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.
Examples In the following example, BOOTP and DHCP services are disabled on the router:
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
Usage Guidelines 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.
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.
Router(config)# no ip finger
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
Examples In the following example, the router is configured to use only passive FTP connections:
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.
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.
Examples The following example configures the router to use the username “red” and the password “blue” for FTP
connections:
ip ftp source-interface
To specify the source IP address for File Transfer Protocol (FTP) connections, use the ip ftp source-
interfacecommand in global configuration mode. To use the address of the interface where the connection
is made, use the no form of this command.
Syntax Description interface-type interface-number The interface type and number to use to obtain the
source address for FTP connections.
Command Default The FTP source address is the IP address of the interface that the FTP packets use to leave the router.
Usage Guidelines 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.
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:
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.
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 “blue”for
FTP connections:
Command Description
ip ftp password Specifies the password to be used for FTP
connections.
ip rarp-server
To enable the router to act as a Reverse Address Resolution Protocol (RARP) server, use the ip rarp-
server 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
Usage Guidelines 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 it’s workstations. By bridging RARP packets and using both the ip helper-address
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:
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.
In the following example, a router is configured to act as a RARP server, with TFTP and portmapper
requests forwarded to the Sun server:
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
Usage Guidelines 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 domain-
lookup command takes precedence over the ip rcmd domain-lookupcommand. This means that if the no
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):
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
Command Default To ensure security, the router is not enabled for rcp by default.
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 “netadmin3”on the remote host 172.16.101.101:
Router(config)# ip rcmd rcp-enable
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.
Syntax Description local-username Name of the user on the local router. You can
specify the router name as the username. This name
needs to be communicated to the network
administrator or to the user on the remote system.
To be allowed to remotely execute commands on
the router, the remote user must specify this value
correctly.
remote-username Name of the user on the remote host from which the
router will accept remotely executed commands.
Usage Guidelines 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 host’s 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.
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.
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.
Syntax Description username Name of the remote user on the server. This name
is used for rcp copy requests. All files and images
to be copied are searched for or written relative to
the directory of the remote user’s account, if the
server has a directory structure, for example, as do
UNIX systems.
Command Default 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.
Note 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 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).
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines 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 user’s account.
Note 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.
boot system rcp Specifies the system image that the router loads at
startup.
bridge acquire Forwards any frames for stations that the system
has learned about dynamically.
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
Command Default To ensure security, the router is not enabled for rsh by default.
Usage Guidelines 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.
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 The name and number used to identify the
interface. For example, Loopback2.
Command Default The address of the interface closest to the destination is used as the source interface for rcp/rsh
communications.
Usage Guidelines 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.
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
!
.
.
.
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.
Command Default The address of the closest interface to the destination is the source address.
Usage Guidelines 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 :
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.
Syntax Description bytes The size in bytes of the TFTP block from 512 to
8192.
Examples The following example shows how to set a 1024 byte TFTP blocksize:
Router> enable
Router# configure terminal
Router(config)# ip tftp bblocksize 1024
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.
Syntax Description type The type of the interface to be used. You can
choose from a list of interfaces.
Examples 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
ip tftp min-timeout
To specify the minimum timeout period for retransmission of data using TFTP, use the ip tftp min-
timeoutcommand in global configuration mode. To disable, use the no form of this command.
Syntax Description seconds Specifies the timeout value, in seconds. The range
is from 4 to 20.
Command Default The default minimum timeout period for retransmission of data is 4 seconds.
Examples 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
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 The interface type and number whose address is to
be used as the source for TFTP connections.
Command Default The address of the closest interface to the destination is selected as the source address.
Usage Guidelines 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.
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 :
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.
Syntax Description group-address group-address (Optional) Directs the router to use a specified
multicast IP address for communication with the
WCCP service group. See the “Usage Guidelines”
section for additional information.
Command Default When this command is not configured, hardware acceleration for WCCPv1 is not enabled.
Release Modification
12.2(18)SXD1 This command was changed to support the
Supervisor Engine 720.
Usage Guidelines 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 access-
list 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:
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 The number of lines on the screen. A value of zero
disables pausing between screens of output.
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
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 Length of time for which data is used to compute
load statistics. Value is a multiple of 30, from 30 to
600 (30, 60, 90, 120, and so on). The default is 300
seconds.
Usage Guidelines 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.
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.
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
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”:
lock
To configure a temporary password on a line, use the lockcommand in EXEC mode.
lock
Usage Guidelines 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
Password: <password>
Again: <password>
Locked
Password: <password>
Router#
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
Command Default Sessions on the line are not lockable (the lock EXEC command has no effect).
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:
Password: <password>
Router#
log config
To enter configuration change logger configuration mode, use the log configcommand in archive
configuration mode.
log config
Examples The following example shows how to place the router in configuration change logger configuration mode:
show archive log config Displays entries from the configuration log.
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
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
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:
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
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.
The following example shows how to clear the configuration log by disabling and then reenabling the
configuration log:
show archive log config Displays entries from the configuration log.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
Usage Guidelines You can use the no logging esm config command to disallow configuration changes from ESM filters.
Examples The following example shows how to configure the ESM filters:
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:
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 port-
channel 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 port-
channel Port-channel2
Usage Guidelines 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.
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:
This example shows how to enable the system logging of interface state-change events on all interfaces
during system initialization:
This example shows how to disable the system logging of interface state-change events on all interfaces:
This example shows how to disable the system logging of interface state-change events during system
initialization:
Usage Guidelines To enable system logging of interface state-change events on a specific interface, enter the logging event
link-status command.
Examples The following example shows how to enable link-status event messaging on an interface:
Usage Guidelines 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:
This example shows how to disable the system logging of the interface state-change events on a
subinterface:
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:
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.
Syntax Description message-limit (Optional) Sets the limit on the number of messages
that can be logged during reload.
Cisco IOS XE Releas e2.1 This command was integrated into Cisco IOS XE
Release 2.1.
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:
Syntax Description entries entries Specifies the maximum number of log entries that
are cached in the software; valid values are from 0
to 1048576 entries.
rate-limit pps Specifies the number of packets that are logged per
second in the software; valid values are from 10 to
1000000 pps.
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 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
Examples 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
Command Description
show logging ip access-list Displays information about the logging IP access
list.
update-interval seconds Removes entries from the cache that are inactive for
the duration that is specified in the command.
Usage Guidelines 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.
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 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
Router(config-if)#
logging ip access-list cache in
Router(config-if)#
logging ip access-list cache out
update-interval seconds Removes entries from the cache that are inactive for
the duration that is specified in the command.
Command Default The configuration commands are not saved to the Cisco IOS secure file system.
Command Modes Archive configuration mode, log config (configuration-change logger) submode (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
archive log config persistent save Saves the persisted commands in the configuration
log to the Cisco IOS secure file system.
Command Default The configuration commands saved in the configuration logger database are not applied to the running-
config file.
Command Modes Archive config mode; log config (configuration change logger) submode (config-archive-log-cfg)#
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:
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.
Usage Guidelines When the configuration log is full, the oldest log entry will be removed every time a new entry is added.
Note 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.
Examples The following example shows how to specify that the configuration log may have a maximum of 200
entries:
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
show archive log config Displays entries from the configuration log.
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 (Optional) Specifies the message severity level.
Messages with a severity level equal to or higher
than this value are printed asynchronously. Low
numbers indicate greater severity and high numbers
indicate lesser severity. The default value is 2.
Usage Guidelines 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.
Tip 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-3-
MSGLOST 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 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.
Examples 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:
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
* 0 CTY - - - - - 0 3 0/0 -
.
.
.
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
Router(config-line)# end
Router# show ru
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 4
Router(config-line)# logging synchronous level 6
Router(config-line)# exit
Router(config)# line 2
Router(config-line)# logging synchronous level 7 limit 1000
Router(config-line)# end
Router#
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.
Syntax Description disk name (Optional) Stores the system event archive (system
event log file) in the specified disk. The specified
disk must be already have been configured to allow
for the storage of the system event archive.
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:).
Usage Guidelines 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.
Note To store the system event logs, the SEA requires either PCMCIA ATA disk or Compact Flash disk in
compact flash adapter for PRE2.
Examples The following example shows how to specify that the SEA log file should be written to the disk “disk1:”:
Router(config)# end
Related Commands clear logging system Clears the event records stored in the SEA.
copy logging system Copies the archived system event log to another
location.
logout
To close an active terminal session by logging off the router, use the logout command in user EXEC mode.
logout
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 logout command is used to log off (exit from the active session):
Router(config)# exit
Router# disable
Router> logout
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
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
Command Description
session-timeout Sets the interval for closing the connection when
there is no input or output traffic.
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 macro-
name ? 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 “test-
server” and to set the IP precedence value to 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:
Usage Guidelines 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.
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:
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:
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
Command Default By default, a maximum of 10 archive files of the running configuration are saved in the Cisco IOS
configuration archive.
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 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.
Examples 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
Command Default Memory cache error recovery mechanisms are not enabled.
Examples The following example shows how to enable the memory cache error-recovery command:
Router> enable
Router# configure terminal
Router(config)# memory cache error-recovery
Syntax Description abort-if-same-content Abort recovery if the cache contains the same
content as the memory.
Command Default Memory cache error recovery mechanisms are not enabled.
Examples The following example shows how to enable the memory cache error-recovery optionscommand:
Router> enable
Syntax Description processor threshold Sets the processor memory threshold in kilobytes.
When available processor memory falls below this
threshold, a notification message is triggered. Valid
values are 1 to 4294967295.
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:
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:
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
Usage Guidelines 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 The following example shows how to disable the malloc_lite feature:
no memory lite
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 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 Reserves the memory size for a console session.
Command Default 256 KB is reserved for console memory access. 100 KB is reserved for cricial memory access.
Release Modification
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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:
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
Command Default 100 kilobytes of memory is reserved for the logging process.
Usage Guidelines 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.
Note 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.
Examples The following example shows how to reserve 1,000 KB of system memory for logging messages at the
next system restart:
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
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.
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 time-
stamps 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
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
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:
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.
Command Default The default memory allocation is 25 percent of the DRAM to I/O memory and 75 percent of the DRAM to
processor memory.
Note 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.
Usage Guidelines 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.
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.
menu (EXEC)
To display a preconfigured user menu, use the menu command in user EXEC or privileged EXEC mode.
menu menu-name
Usage Guidelines 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.
Syntax Description menu-name Name of the menu this command should be applied
to.
Command Default Enabled for menus with more than nine items; disabled for menus with nine or fewer items.
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:
Command Description
menu default Specifies the menu item to use as the default.
menu clear-screen
To clear the terminal screen before displaying a menu, use the menu clear-screen command in global
configuration mode.
Syntax Description menu-name Name of the menu this command should be applied
to.
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:
Command Description
menu default Specifies the menu item to use as the default.
menu command
To specify underlying commands for user menus, use the menu command command in global
configuration mode.
Syntax Description menu-name Name of the menu. You can specify a maximum of
20 characters.
Usage Guidelines 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.
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 user’s list of
connections. This function allows you to create a single menu entry that steps through all of the user’s
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:
The following example allows a menu user to exit a menu by entering Exit at the menu prompt:
Command Description
menu default Specifies the menu item to use as the default.
menu default
To specify the menu item to use as the default, use the menu default command in global configuration
mode.
Syntax Description menu-name Name of the menu. You can specify a maximum of
20 characters.
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 line-mode
To require the user to press Enter after specifying an item, use the menu line-mode command in global
configuration mode.
Syntax Description menu-name Name of the menu this command should be applied
to.
Command Default Enabled for menus with more than nine items. Disabled for menus with nine or fewer items.
Usage Guidelines 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 options
To set options for items in user menus, use the menu options command in global configuration mode.
Syntax Description menu-name The name of the menu. You can specify a
maximum of 20 characters.
Cisco IOS XE Release 3.1S This command was integrated into a release earlier
than Cisco IOS Release 3.1S.
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
menu prompt
To specify the prompt for a user menu, use the menu prompt command in global configuration mode.
Syntax Description menu-name Name of the menu. You can specify a maximum of
20 characters.
Usage Guidelines 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.”:
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.
Syntax Description menu-name Name of the menu this command should be applied
to.
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 router’s host name, the user’s 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:
Command Description
menu command Specifies underlying commands for user menus.
menu text
To specify th e text of a menu item in a user menu, use the menu text command in global configuration
mode.
Syntax Description menu-name Name of the menu. You can specify a maximum of
20 characters.
Usage Guidelines 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 title
To create a t itle (banner) for a user menu, use the menu title command in global configuration mode.
Syntax Description menu-name Name of the menu. You can specify a maximum of
20 characters.
Usage Guidelines 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.
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.
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.
Command Default The default is to load the image from the GRP card (system).
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines 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.
In this example, the user would issue the execute-on slot 10 show version command to verify that the
correct version is loaded.
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.
Command Default The default is to load from the microcode bundled in the system image.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines 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
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.
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.
Usage Guidelines 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.
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:
Syntax Description slot-number (Optional) Slot number of the line card that you
want to reload the Cisco IOS software image on.
Slot numbers range from 0 to 11 for the Cisco
12012 and from 0 to 7 for the Cisco 12008 router. If
you do not specify a slot number, the Cisco IOS
software image is reloaded on all line cards.
Usage Guidelines 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.
Note 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.
Examples In the following example, the mirocode firmware is reloaded on the line card in slot 10:
Syntax Description slot-number (Optional) Reloads the specified processor card slot
on a Cisco 7500 series router.
Usage Guidelines 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.
Note 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.
Examples In the following example, all controllers are reset, and the microcode specified in the current configuration
is loaded:
Syntax Description all Resets and reloads all hardware types that support
downloadable microcode.
Usage Guidelines 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:
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
Command Modes User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Cisco IOS XE Release 2.1 This command was modified and implemented on
the Cisco ASR 1000 Aggregation Services Routers.
The following enhancements were made:
• This command was introduced in diagnostic
mode. The command can be entered in both
privileged EXEC and diagnostic mode on the
Cisco ASR 1000 Series Routers.
• The harddisk:, obfl:, stby-harddisk:, stby-
nvram:, stby-obfl:, stby-usb[0-1]:,and
usb[0-1]: directory options were added.
Usage Guidelines This command is valid only on Class C flash file systems.
When executing the mkdir directory command on a USB token device, you can create only two levels of
subdirectories under a directory. A new directory (third level directory) cannot be created on the USB
token, but you can copy files to the existing subdirectories.
Directory of flash:
2 drwx 0 Mar 13 1993 13:16:21 newdir
8128000 bytes total (8126976 bytes free)
mkdir disk0:
To create a new directory in a Flash file system, use the mkdir disk0:command.
mkdir disk0:
mode
To set the redundancy mode, use the mode command in redundancy configuration mode.
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.
Command Default
• 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.
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.
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.
Cisco IOS XE Release 2.5 This command was modified. This command was
implemented on the Cisco ASR 1000 Series
Routers.
Usage Guidelines Cisco IOS Release 12.2S and 7600 Series Routers
SSO is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
On releases prior to Release 12.2(17d)SXB, single router mode (SRM) with SSO redundancy does not
support stateful switchover for multicast traffic. When a switchover occurs, all multicast hardware
switching entries are removed and are then re-created and reinstalled in the hardware by the newly active
multilayer switch feature card (MSFC).
SRM/SSO is supported in the following releases only:
• Release 12.2(17b)SXA and subsequent rebuilds.
• Release 12.2(17d)SXB and subsequent rebuilds.
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.
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 This example shows how to set the redundancy mode to RPR+:
Router(config)# redundancy
Router(config-red)# mode rpr-plus
Router(config)# redundancy
Router(config-red)# mode sso
route-converge-interval Configures the time interval after which the old FIB
entries are purged.
Command Description
show redundancy Displays RF information.
monitor event-trace component {clear | continuous | disable | dump [pretty] | enable | one-shot}
Release Modification
12.2(25)S This command was integrated into Cisco IOS
Release 12.2(25)S. The monitor event-trace cef
ipv4 clearcommand replaces the clear ip cef
event-logcommand.
Usage Guidelines 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.
Note 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.
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.
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.
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.
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.
monitor event-trace dump-traces Saves trace messages for all event traces currently
enabled on the networking device.
show monitor event-trace Displays event trace messages for Cisco IOS
software subsystem components.
monitor event-trace component {disable | dump-file filename | enable | size number | stacktrace
number} timestamps [datetime [localtime] [msec] [show-timezone] | uptime]
dump-file filename Specifies the file where event trace messages are
written from memory on the networking device.
The maximum length of the filename (path and
filename) is 100 characters, and the path can point
to flash memory on the networking device or to a
TFTP or FTP server.
Command Default Event tracing is enabled or disabled depending on the software component.
Release Modification
12.2(28)SB This command was integrated into Cisco IOS
Release 12.2(28)SB and implemented on the Cisco
10000 series routers.
Usage Guidelines Use the monitor event-trace command to enable or disable event tracing and to configure event trace
parameters for Cisco IOS software subsystem components.
Note 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 event-
tracecommand 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 event-
trace 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.
monitor event-trace dump-traces Saves trace messages for all event traces currently
enabled on the networking device.
show monitor event-trace Displays event trace messages for Cisco IOS
software subsystem components.
Syntax Description pretty (Optional) Saves the event trace message in ASCII
format.
Usage Guidelines 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.
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 (global) Configures event tracing for a specified Cisco IOS
software subsystem component.
show monitor event-trace Displays event trace messages for Cisco IOS
software subsystem components.
Usage Guidelines 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:
You can identify the dial feature card (DFC) channel from where the PCM is traced using the filename
format.
Consider the following example:
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:
• cap_data_tx_6_1_22 and cap_data_rx_6_1_22--This corresponds to the traffic flowing through DS0
6/1:22.
• cap_data_tx_6_1_22 and cap_data_rx_6_1_22--cap_data_tx_6_1_22 is the data in the transmit
direction (from the DFC to the system backplane) and cap_data_rx_6_1_22 is the data in the receiver
direction (to the DFC from the system backplane).
Examples The following example shows how to configure a router to save the PCM trace information to a flash drive:
Examples The following example shows how to configure the PCM tracer delay time to 1000 seconds:
Usage Guidelines You must create at least one user profile under the channels that need to be traced. You can create the
following profile operations:
• Create a user profile identified by a profile number.
• Add one or more profiles. A user profile consists of capture groups in which the channels that are to be
traced are specified.
• Configure one or more capture groups under a profile.
Examples The following example shows how to create a PCM capture profile with profile number 1:
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
Usage Guidelines 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:
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:
Command Default Cisco IOS Releases 12.2(33)SXH2a and later releases: Centralized mode
Cisco IOS Releases 12.2(33)SXH, SXH1, and SXH2: Distributed mode
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 Distributed egress span (DES) mode is applied to ASIC-based sessions only.
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:
The following example shows how to switch the egress-span mode from centralized back to distributed
mode:
The following example shows how to switch the egress-span mode from distributed back to centralized
mode:
Release Modification
12.2(18)SXF This command was changed as follows:
• Support for this command was introduced on
the Supervisor Engine 32.
• ERSPAN is supported in any switch fabric
module functionality switching mode.
Usage Guidelines 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:
• Router(config-mon-erspan-src)--Indicates the ERSPAN source session configuration mode.
Syntax Description
Global Configuration Mode
monitor session erspan-destination-session-number | rspan- Enters ERSPAN or RSPAN destination session configuration
destination-session-number type erspan-destination | erspan- mode and changes the prompt to the following:
destination Router(config-mon-erspan-dst)#
Router(config-mon-rspan-dst)#
destination {single-interface | interface-list | interface-range | Associates the ERSPAN destination session number with the
mixed-interface-list } destination ports.
ip address ip-address [force] Configures the ERSPAN flow destination IP address, which
must also be configured on an interface on the destination
switch and be entered in the ERSPAN destination session
configuration.
vrf vrf-name (Optional) Configures the VRF name of the packets in the
ERSPAN traffic.
The table below lists the ERSPAN source session configuration mode syntaxes.
Syntax Description
Global Configuration Mode
monitor session erspan-source-session-number type erspan- Enters ERSPAN or RSPAN source session configuration mode
source | rspan-source and changes the prompt as appropriate to the following:
Router(config-mon-erspan-src)#
Router(config-mon-rspan-src)#
source {{single-interface | interface-list | interface-range | Associates the ERSPAN or RSPAN source session number
mixed-interface-list | single-vlan | vlan-list | vlan-range | mixed- with the source ports or VLANs, and selects the traffic
vlan-list } [rx | tx | both]} direction to be monitored.
filter { single-vlan | vlan-list | vlan-range | mixed-vlan-list } (Optional) Configures source VLAN filtering when the
ERSPAN or RSPAN source is a trunk port.
erspan-id erspan-flow-id Configures the ID number used by the source and destination
sessions to identify the ERSPAN or RSPAN traffic.
origin ip address ip-address Configures the IP address used as the source of the ERSPAN or
RSPAN traffic.
ip {{ttlttl-value } | {precipp-value } | {dscpdscp-value }} (Optional) Configures the following packet values in the
ERSPAN or RSPAN traffic:
• ttl ttl -value --IP time-to-live (TTL) value
• prec ipp-value-- IP-precedence value
• dscp dscp-value-- IP-precedence value
vrf vrf-name (Optional) Configures the VRF name of the packets in the
ERSPAN or RSPAN traffic.
When you configure the monitor sessions, follow these syntax guidelines:
• erspan-destination-span-session-number can range from 1 to 66.
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.
Note 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 intrusion-
detection-module num
analysis-module num Specifies the SPAN destination analysis-module.
interface type number Specifies the interface type and number as follows:
• GigabitEthernet mod /port
• port-channel num --Ethernet Channel of
interfaces; valid values are from 1 to 496.
interface type number Specifies the interface type and number as follows:
• FastEthernet mod /port
• GigabitEthernet mod /port
• Port-channel num --Ethernet Channel of
interfaces; valid values are from 1 to 496.
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.
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:
◦ interface type slot/port; type is fastethernet, gigabitethernet, or tengigabitethernet.
◦ interface port-channel number
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.
Note 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-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-mon-erspan-dst)#
This example shows how to associate the ERSPAN destination session number with the destination ports:
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)#
This example shows how to configure multiple sources for a session:
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:
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.
Syntax Description cisco Denotes a Cisco device code. This is the default.
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 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.
Syntax Description seconds Sets the length of time (in seconds) that the
software waits before resending a message. The
value is a number from 1 to 20.
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
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.
Syntax Description count Indicates the number of times the software will
resend a MOP boot request. The value is a number
from 3 to 24. The default is 8.
Examples In the following example, the software will attempt to resend a message to an unresponsive host 11 times
before declaring a failure:
Command Description
mop retransmit-timer Configures the length of time that the Cisco IOS
software waits before resending boot requests to a
MOP server.
more
To display the contents of a file, use the morecommand in privileged EXEC mode.
Command Default The command displays the conent of a file in its native format. Optional formats include ascii, binary, and
ebcdic.
Cisco IOS XE Release 2.5 This command was implemented on Cisco ASR
1000 series routers.
Usage Guidelines 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:
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
Building configuration...
Current configuration:
!
version 12.1
no service udp-small-servers
no service tcp-small-servers
!
hostname Router2
!
.
.
.
!
end
more <url> exclude Filters the output of any more command to exclude
a matched string.
more <url> include Filters the output of any more command to display
only the lines that match the specified string.
Syntax Description url The Universal Resource Locator (RLl) of the file to
display. More commands are advanced show
commands; for details, see the command reference
page in this book for the more command.
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.”
Command Description
more <url> include Filters more command output so that it displays
only lines that contain a particular regular
expression.
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
Syntax Description url The Universal Resource Locator (URL) of the file
to display. More commands are advanced show
commands; for details, see the command reference
page in this book for the more command.
The Cisco IOS File System (IFS) uses URLs to
specify the location of a file system, directory, and
file. Typical URL elements include:
prefix:[directory/]filename
Prefixes can be local file systems or file locations,
such as nvram: or system:. Alternatively, you can
specify network locations using the following
syntax:
ftp: [[//[username [:password ]@]location ]/
directory ]/filename
tftp: [[//location ]/directory ]/filename
rcp: [[//[username @]location ]/directory ]/
filename
Release Modification
12.0(1)T This extension of the more command was
introduced.
Usage Guidelines 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.”
Command Description
more <url> include Filters more command output so that it displays
only lines that contain a particular regular
expression.
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
Syntax Description url The Universal Resource Locator (URL) of the file
to display. More commands are advanced show
commands; for details, see the command reference
page in this book for the more command.
Usage Guidelines 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.”
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
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
Usage Guidelines 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.
Length Name/status
1 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
motd-banner
To enable the display of message-of-the-day (MOTD) banners on the specified line or lines, use the motd-
banner 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
Usage Guidelines 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.
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
Examples The following example suppresses the MOTD banner on vty lines 0 through 4:
line vty 0 4
no motd-banner
name-connection
To assign a logical name to a connection, use the name-connectioncommand in user EXEC mode.
name-connection
Usage Guidelines This command can be useful for keeping track of multiple connections.
You are prompted for the connection number and name to assign. The where command displays a list of
the assigned logical connection names.
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]
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 Name of the menu to delete from the configuration
file.
Usage Guidelines 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.
no menu Access1
Command Description
menu prompt Specifies the prompt for a user menu.
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
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:
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.
Syntax Description contenttype (Optional) Allows you to choose a format for the
configuration change messages that are sent via
syslog.
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:
show archive log config Displays entries from the configuration log.
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.
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)# padding 13 25
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.
Usage Guidelines 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 In the following example, even parity is configured for line 34:
Router(config)# line 34
Router(config-line)# parity even
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
Usage Guidelines 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:
show parser statistics Displays statistics about the last configuration file
parsed and the status of the Parser Cache feature.
Command Default Access is granted only to the user holding the lock.
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:
test parser session-lock Tests the behavior of the Parser Concurrency and
Locking Improvements feature.
Usage Guidelines 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 running-
configuration 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:
Usage Guidelines This command controls (enables or disables) the Configuration Partitioning feature.
To display the list of commands that make up the current running configuration for a specific part
(“partition”) of the system’s global running configuration, use the show running-config partition
command in privileged Exec mode.
The Configuration Partitioning feature uses a small amount of system resources. The no parser config
partition command allows you to disable this feature if the feature is not needed on your system.
Note 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.
Examples The following example shows how to disable partitioning of the system running configuration:
Router> enable
Router# config t
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.
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 The following example shows how to impose a latency limit of 100.
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.
Syntax Description flash-filesystem : One of the following Flash file systems, which
must be followed by a colon (:). The Cisco 1600
series can only use the flash: keyword.
• flash: -- Internal Flash memory
• slot0: -- Flash memory card in PCMCIA slot 0
• slot1: -- Flash memory card in PCMCIA slot 1
Usage Guidelines For the Cisco 1600 series and Cisco 3600 series routers, to undo partitioning, use the partition flash-
filesystem :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 The partition command will only create 3MB or larger partitions and may not be used if the device memory
contains logging persistent files.
Examples The following example creates two partitions of 4 MB each in Flash memory:
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:
path url
no path url
Syntax Description url URL (accessible by the Cisco IOS file system) used
for saving archive files of the running configuration
file in the Cisco IOS configuration archive.
Command Default If this command is not configured, no location or filename prefix is specified for files in the Cisco IOS
configuration archive.
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:
The colon is required in the location format.
The filename of the first archive file is the filename specified in the url argument followed by -1. The
filename of the second archive file is the filename specified in the url argument followed by -2 and so on.
Because some file systems are incapable of storing the date and time that a file was written, the filename of
the archive file can contain the date, time, and router hostname. To include the router hostname in the
archive file filename, enter the characters $h (for example, disk0:$h). To include the date and time in the
archive file filename, enter the characters $t.
When a configuration archive operation is attempted on a local file system, the file system is tested to
determine if it is writable and if it has sufficient space to save an archive file. If the file system is read-only
or if there is not enough space to save an archive file, an error message is displayed.
If you specify the tftp: file server as the location with the path command, you need to create the
configuration file on the TFTP file server and change the file’s privileges before the archive config
command works properly.
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 time-
period 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.
12
13
14
> touch
router-cfg-1
> chmod
777 router-cfg-1
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
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.
Syntax Description days-of-the-week The first occurrence of this argument is the starting
day or day of the week that the associated time
range is in effect. The second occurrence is the
ending day or day of the week the associated
statement is in effect.
This argument can be any single day or
combinations of days: Monday, Tuesday,
Wednesday, Thursday, Friday, Saturday, and
Sunday. Other possible values are:
• daily --Monday through Sunday
• weekdays --Monday through Friday
• weekend --Saturday and Sunday
If the ending days of the week are the same as the
starting days of the week, they can be omitted.
Usage Guidelines 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:
Every day of the week, from 8:00 a.m. to 6:00 p.m. periodic daily 8:00 to 18:00
only
Every minute from Monday 8:00 a.m. to Friday periodic monday 8:00 to friday 20:00
8:00 p.m.
All weekend, from Saturday morning through periodic weekend 00:00 to 23:59
Sunday night
Saturdays and Sundays, from noon to midnight periodic weekend 12:00 to 23:59
Examples The following example configuration denies HTTP traffic on Monday through Friday from 8:00 a.m. to
6:00 p.m.:
.
.
.
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.:
.
.
.
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
.
.
.
deny (IP) Sets conditions under which a packet does not pass
a named IP access list.
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.
Release Modification
12.2(13)T The atmprotocol keyword was added.
The following keywords were removed because the
Apollo Domain, Banyan VINES, and XNS
protocols are no longer supported in Cisco IOS
software:
• apollo
• vines
• xns
Cisco IOS XE Release 2.1 This command was introduced on Cisco ASR 1000
Series Routers.
Usage Guidelines 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.
Character Description
! Each exclamation point indicates receipt of a reply.
Character Description
. Each period indicates that the network server timed
out while waiting for a reply.
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.
Field Description
Protocol [ip]: Prompt for a supported protocol. Default: ip.
Repeat count [5]: Number of ping packets that will be sent to the
destination address. Default: 5.
Datagram size [100]: Size of the ping packet (in bytes). Default: 100
bytes.
Sweep range of sizes [n]: Allows you to vary the sizes of the echo packets
being sent. This capability is useful for determining
the minimum sizes of the maximum transmission
units (MTUs) configured on the nodes along the
path to the destination address. Packet
fragmentation contributing to performance
problems can then be reduced.
round-trip min/avg/max = 1/2/4 ms Round-trip travel time intervals for the protocol
echo packets, including minimum/average/
maximum (in milliseconds).
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
The table below describes the default ping fields shown in the display.
Field Description
Protocol [ip]: Prompt for a supported protocol. Default: ip.
VPI value [0]: Prompt for the virtual path identifier. Default: 0.
VCI value [1]: Prompt for the virtual channel identifier. Default:1.
Loopback - End(0), Segment(1) [0]: Prompt to specify end loopback, which verifies
end-to-end PVC integrity, or segment loopback,
which verifies PVC integrity to the neighboring
ATM device. Default: segment loopback.
Repeat Count [5]: Number of ping packets that will be sent to the
destination address. Default: 5.
round-trip min/avg/max = 1/1/1 ms Round-trip travel time intervals for the protocol
echo packets, including minimum/average/
maximum (in milliseconds).
Command Description
ping ip Tests network connectivity on IP networks.
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.
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.
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:
!!!!!
ping ip
To test network connectivity on IP networks, use the ping ip command inprivileged EXEC mode.
tos service value (Optional) Specifies the type of service value. The
range is from 1 to 255.
Release Modification
15.2(02)S The tos keyword was added.
Usage Guidelines 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.
Character Description
! Each exclamation point indicates receipt of a reply.
Note Not all protocols require hosts to support pings. For some protocols, the pings are Cisco-defined and are
only answered by another Cisco router.
Examples 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.
Field Description
Protocol [ip]: Prompts for a supported protocol. The default is IP.
Repeat count [5]: Prompts for the number of ping packets that will be
sent to the destination address. The default is 5
packets.
Datagram size [100]: Prompts for the size of the ping packet (in bytes).
The default is 100 bytes.
Timeout in seconds [2]: Prompts for the timeout interval. The default is 2
seconds.
Sweep range of sizes [n]: Allows you to vary the sizes of the echo packets
being sent. This capability is useful for determining
the minimum sizes of the MTUs configured on the
nodes along the path to the destination address.
Packet fragmentation contributing to performance
problems can then be reduced.
Field Description
!!!!! Each exclamation point ( !) indicates receipt of a
reply. A p eriod ( .) indicates that the network
server timed out while waiting for a reply. Other
characters may appear in the ping output display,
depending on the protocol type.
round-trip min/avg/max = 1/2/4 ms Indicates the round-trip travel time intervals for the
protocol echo packets, including minimum/average/
maximum (in milliseconds).
ping srb
To test network connectivity for Source Route Bridging (SRB) networks, use the ping srb command in
privileged EXEC mode.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1 and implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Examples The following example shows how to ping the target host of IP address 192.0.2.1:
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.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines 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.
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:
Command Description
ping ip Tests the connection to a remote host on the
network using IPv4.
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
Usage Guidelines This command should be entered before using the request platform software system shell command.
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.
Syntax Description module slot Specifies a module slot number; see the “Usage
Guidelines” section for valid values.
Usage Guidelines When you enter the no power enable module slot command to power down a module, the module’s
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)#
Router(config)#
no power enable module 5
Router(config)#
power redundancy-mode
To set the power-supply redundancy mode, use the power redundancy-mode command in global
configuration mode.
Examples 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)#
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] [newline-
convert] [jobtypes type]
no printer printer-name
Usage Guidelines 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:
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
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.
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
Command Description
exit Exits any configuration mode, or closes an active
terminal session and terminates the EXEC.
Syntax Description number Integer from 1 to 100 that indicates the percentage
of CPU utilization that a process must use to
become part of the history table.
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
!
process cpu threshold type {total | process | interrupt} rising percentage interval seconds
[falling fall-percentage interval seconds]
no process cpu threshold type {total | process | interrupt}
Syntax Description total Sets the CPU threshold type to total CPU
utilization.
Usage Guidelines 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:
• When a configured CPU usage threshold is exceeded (rising percentage)
• When CPU usage falls below the configured threshold (falling fall-percentage)
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
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
Usage Guidelines 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:
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 Text that will be displayed on screen as the CLI
prompt, including any desired prompt variables.
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.
Usage Guidelines 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.
%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:
The following are examples of user and privileged EXEC prompts that result from the previous command:
prompt config
To configure the system’s prompt for configuration mode, use the prompt config command in global
configuration mode. To disable the configuration, use the no form of this command.
Syntax Description hostname-length Sets the length of the hostname in the configuration
prompt.
Command Default The system's prompt is not configured for configuration mode.
Examples This example shows how to configure the system’s prompt for configuration mode:
Router(config)#
prompt config hostname-length 4
pwd
To show the current setting of the cd command, use the pwd command in EXEC mode.
pwd
Usage Guidelines 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:/
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
Usage Guidelines 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
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
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Examples The following example shows how to optimize the compilation of regular expression access list:
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 (Optional) Verifies the digital signature of the file
that will be loaded onto the operating system.
Release Modification
15.0(1)M This command was modified. The reason keyword
and reason-stringargument were added.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Aggregation Services Router and was
made available in diagnostic mode.
Usage Guidelines 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 user’s 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, read-
write data is saved in RAM during a cold startup and restored during a warm reboot. Warm rebooting
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:
The following example shows how to reload the software on the router on April 21 at 2:00 a.m.:
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:
Command Description
file verify auto Enables automatic image verification.
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.
Syntax Description module num Specifies the module to access; see the “Usage
Guidelines” section for valid values.
Usage Guidelines 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.
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#
remote login
To access the Cisco 7600 series router console or a specific module, use the remote login command in
privileged EXEC mode.
Syntax Description module num Specifies the module to access; see the “Usage
Guidelines” section for valid values.
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.
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:
• You can enter the exit command as follows:
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 a specific module:
This example shows how to perform a remote login to the Cisco 7600 series router processor:
This example shows how to perform a remote login to the standby route processor:
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
Usage Guidelines This command is not supported in the VLAN database mode.
You can enter the show vlan remote-span command to display the RSPAN VLANs in the Cisco 7600
series router.
rename
To rename a file in a Class C Flash file system, use the rename command in EXEC, privileged EXEC, or
diagnostic mode.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Router and was made available in
diagnostic mode.
Usage Guidelines This command is valid only on Class C Flash file systems.
Examples In the following example, the file named Karen.1 is renamed test:
Router# dir
Directory of disk0:/Karen.dir/
Router# dir
Directory of disk0:/Karen.dir/
Syntax Description URL Specifies the URL to the file. The URL contains the
file system, directories, and the filename.
Usage Guidelines 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.
Examples In the following example, this command is entered to gather information about an individual SIP Base
module file on the bootflash: file system.
Computed SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Contained SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Hashes match. Package is valid.
Computed SHA1sum:
5f8cda8518d01d8282d80ecd34f7715783f4a813
Contained SHA1sum:
5f8cda8518d01d8282d80ecd34f7715783f4a813
Hashes match. Package is valid.
Build: v122_33_xn_asr_rls0_throttle_20071204_051318
Package: asr1000rp1-espbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 52072652
Timestamp: 2007-12-04 13:33:13 UTC
Computed SHA1sum:
15502fd1b8f9ffd4af4014ad4d8026c837929fe6
Contained SHA1sum:
15502fd1b8f9ffd4af4014ad4d8026c837929fe6
Hashes match. Package is valid.
Package: asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 21844172
Timestamp: 2007-12-04 13:33:01 UTC
Computed SHA1sum:
ea1b358324ba5815b9ea623b453a98800eae1c78
Contained SHA1sum:
ea1b358324ba5815b9ea623b453a98800eae1c78
Hashes match. Package is valid.
Package: asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 21520588
Timestamp: 2007-12-04 13:33:06 UTC
Computed SHA1sum:
83c0335a3adcea574bff237a6c8640a110a045d4
Contained SHA1sum:
83c0335a3adcea574bff237a6c8640a110a045d4
Hashes match. Package is valid.
Package: asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 24965324
Timestamp: 2007-12-04 13:33:08 UTC
Computed SHA1sum:
19b58886f97c79f885ab76c1695d1a6f4348674e
Contained SHA1sum:
19b58886f97c79f885ab76c1695d1a6f4348674e
Hashes match. Package is valid.
Package: asr1000rp1-rpios-
advipservicesk9.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 48515276
Timestamp: 2007-12-04 13:33:13 UTC
Computed SHA1sum:
f1235d703cc422e53bce850c032ff3363b587d70
Contained SHA1sum:
f1235d703cc422e53bce850c032ff3363b587d70
Hashes match. Package is valid.
Package: asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 36954316
Timestamp: 2007-12-04 13:33:11 UTC
Computed SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Contained SHA1sum:
f2db80416a1245a5b1abf2988088860b38ce7898
Hashes match. Package is valid.
Package: asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle_20071204_051318.pkg
Size: 19933388
Timestamp: 2007-12-04 13:33:06 UTC
Computed SHA1sum:
b1d5faf093b183e196c7c8e1023fe1f7aafdd36d
Contained SHA1sum:
b1d5faf093b183e196c7c8e1023fe1f7aafdd36d
Hashes match. Package is valid.
Platform: ASR1000
User: mcpre
PackageName: sipspa
Build: v122_33_xn_asr_rls0_throttle_20071204_051318
request platform software package expand file source-URL [to destination-URL] [force]
[verbose] [wipe]
Syntax Description source-URL Specifies the URL to the Cisco IOS-XE file that
stores the contents that will be extracted.
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.
Directory of usb0:/
1120 -rwx 213225676 Dec 4 2007 10:50:36 +00:00 asr1000rp1-
advipservicesk9.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:asr1000rp1-
advipservicesk9.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 -rw- 51986636 Dec 4 2007 16:40:38 +00:00 asr1000rp1-
espbase.v122_33_xn_asr_rls0_throttle.pkg
28804 -rw- 21838028 Dec 4 2007 16:40:39 +00:00
asr1000rp1-rpaccess-k9.v122_33_xn_asr_rls0_throttle.pkg
28805 -rw- 21508300 Dec 4 2007 16:40:39 +00:00
asr1000rp1-rpbase.v122_33_xn_asr_rls0_throttle.pkg
28806 -rw- 24963276 Dec 4 2007 16:40:40 +00:00
asr1000rp1-rpcontrol.v122_33_xn_asr_rls0_throttle.pkg
28807 -rw- 48419020 Dec 4 2007 16:40:41 +00:00
asr1000rp1-rpios-advipservicesk9.v122_33_xn_asr_rls0_throttle.pkg
28808 -rw- 36946124 Dec 4 2007 16:40:43 +00:00
asr1000rp1-sipbase.v122_33_xn_asr_rls0_throttle.pkg
28809 -rw- 14670028 Dec 4 2007 16:40:43 +00:00
asr1000rp1-sipspa.v122_33_xn_asr_rls0_throttle.pkg
28802 -rw- 6563 Dec 4 2007 16:40:43 +00:00 packages.conf
928862208 bytes total (708186112 bytes free)
Usage Guidelines 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.
request platform software package install Rolls back a previous software upgrade.
rollback
request platform software package install rp rp-slot-number file file-URL [auto-rollback minutes]
[provisioning-file URL] [slot slot-number] [bay bay-number] [force] [on-reboot] [verbose]
auto-rollback minutes Specifies the setting of a rollback timer, and sets the
number of minutes on the rollback timer before the
rollback timer expires.
slot slot-number Specifies the router slot number where a SIP can be
installed.
Usage Guidelines This command is used to upgrade consolidated packages and individual sub-packages.
When this command is used to upgrade a SIPBASE sub-package, the slot slot-number of the SIP must be
specified.
When this command is used to upgrade a SIPSPA sub-package, the slot slot-numberof the SIP and the bay
bay-number of the SPA must be specified.
When the auto-rollback minutes option is used, the request platform software package install rp rp-
slot-number commit command must be entered before the rollback timer expires to complete the upgrade.
If this command is not entered, the router rolls back to the previous software version. The rollback timer
expires after the number of specified minutes. If the auto-rollback minutes option is not used, the upgrade
simply occurs.
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.
WARNING:
WARNING: Candidate software will be installed upon reboot
WARNING:
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
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
request platform software package install Rolls back a previous software upgrade.
rollback
request platform software package install Creates a snapshot directory that will contain all the
snapshot files extracted from a consolidated package.
Syntax Description rp rp-slot-number Specifies the slot number of the RP doing the
request.
provisioning-file provisioning-file-URL Specifies that the software update will not occur,
and that the router will instead boot using the
specified provisioning file.
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 file Upgrades a consolidated package or an individual
sub-package.
request platform software package install rp rp-slot-number snapshot to URL [as snapshot-
provisioning-filename] [force] [verbose] [wipe]
snapshot to URL Creates a directory and extracts all files from the
consolidated package into that directory. The
directory is named in the command-line as part of
the URL_FS.
If the URL_FSis specified as a file system, the files
in the consolidated package will be extracted onto
the file system and not a directory on the file
system.
Usage Guidelines This command is used to create a directory at the destination device and extract the individual sub-
packages 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# reload
Usage Guidelines 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
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:
Syntax Description
rp Specifies the Route Processor (RP); it can be either
active or standby.
Usage Guidelines 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."
Syntax Description format Specifies the output format for show command
output. Options include:
• html --Specifies Hypertext Markup Language
(HTML) output.
• raw --Specifies the raw message output.
• text --Specifies plaintext output, which is the
default.
• xml -- Specifies Extensible Markup Language
(XML) output
Command Default All show command output is seen in plaintext (the text format)by default.
Usage Guidelines 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.
message@alarms_msg: {
tdl_cman_alarms_data@tdl_cman_alarms_data: {
critical@tdl_boolean:TDL_TRUE
major@tdl_boolean:TDL_TRUE
minor@tdl_boolean:TDL_FALSE
}
}
message@ui_req_msg: {
ui_req@ui_req: {
request_id@U64:2
client@ui_client: {
location@svc_loc: {
fru@b_fru:BINOS_FRU_RP
slotnum@I16:0
baynum@I16:0
}
client_type@ui_client_type:UICLIENT_INVALID
term_type@ui_terminal_type:UITT_INVALID
ttynum@U32:0
tty_name@NS:
user_name@NS:
}
command@NS:
request_name@NS:
flags@ui_req_flag:
}
}
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.
<?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>
</ui_req>
</ui_req_msg>
</cmd-response>
</iossr-response>
request platform software snapshot slot {cancel | create | delete | restore} name
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.
Syntax Description permanent (Optional) Specifies that the router should not
return to diagnostic mode if EXEC mode is exited.
Usage Guidelines 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)#
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:
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 Revision number for the configuration; valid values
are from 0 to 65535.
Usage Guidelines Two Cisco 7600 series routers that have the same configuration but different revision numbers are
considered to be part of two different regions.
Caution 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.
Examples This example shows how to set the revision number of the MST configuration:
Router(config-mst)# revision 5
Router(config-mst)#
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
Cisco IOS XE Release 2.1 This command was introduced on the Cisco
ASR1000 Series Router and was made available in
diagnostic mode.
Usage Guidelines This command is valid only on Class C Flash file systems.
Caution 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 user’s 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.
Router# dir
Directory of flash:
2 drwx 0 Mar 13 1993 13:16:21 newdir
Directory of flash:
No files in directory
8128000 bytes total (8126976 bytes free)
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.
Usage Guidelines 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.
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:
route-converge-interval
To configure the time interval after which the old FIB entries are purged, use the route-converge-
intervalcommand 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 Time interval, in seconds, after which the old FIB
entries are purged ; valid values are from 60 to
3600 seconds.
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)#
rsh
To execute a command remotely on a remote shell protocol (rsh) host, use the rshcommand in
privilegedEXEC mode.
Command Default 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.
Note 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).
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:
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.
Syntax Description interrupt-time Integer (in microseconds) that limits the maximum
number of microseconds to spend on fast switching
within any one network interrupt context. The range
is from 400 to 60000 microseconds. The default is
4000 microseconds.
Command Default Approximately 5 percent of the CPU is available for process tasks.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines This command applies to the Catalyst 6500 series switches, Cisco 7200 series, Cisco 7500 series, and Cisco
7600 series routers.
Caution 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:
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.
Examples The following example shows how to validate the memory check and edisms poll routine:
scheduler heapcheck process [memory [fast] [io] [multibus] [pci] [processor] [checktype {all |
data | magic | mlite-data | pointer | refcount | lite-chunks}]]
no scheduler heapcheck process
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.
Usage Guidelines 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.
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.
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 The following example shows how to enable interrupt mask profiling:
scheduler interrupt mask size Configures the maximum number of entries that
can exist in the interrupt mask buffer.
Command Description
scheduler interrupt mask time Configures the maximum allowed time that a
process can run with interrupts masked.
show process interrupt mask buffer Displays the information stored in the interrupt
mask buffer.
show processes interrupt mask detail Displays interrupt masked details for the specified
process or all processes in the system.
Syntax Description buffersize Specifies the number of entries that can exist in the
interrupt mask buffer.
Examples The following example shows how to configure 100 entries the maximum number of entries that can exist
in the interrupt mask buffer:
scheduler interrupt mask profile Enables or disables interrupt mask profiling for all
processes running on the system.
scheduler interrupt mask time Configures the maximum amount of time a process
can run with interrupts masked.
Command Description
show processes interrupt mask buffer Displays interrupt masked details for the specified
process or all processes in the system and displays
information stored in the interrupt mask buffer.
show processes interrupt mask detail Displays interrupt masked details for the specified
or all processes in the system.
Examples 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:
scheduler interrupt mask profile Enables or disables interrupt mask profiling for all
processes running on the system.
Command Description
scheduler interrupt mask size Configures the maximum number of entries that
can exist in the interrupt mask buffer.
show processes interrupt mask buffer Displays the information stored in the interrupt
mask buffer.
show processes interrupt mask detail Displays interrupt masked details for the specified
process or all processes in the system.
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.
Syntax Description milliseconds Integer that specifies the interval (in milliseconds).
The minimum interval that you can specify is 500
milliseconds; there is no maximum value.
Command Default High-priority operations are allowed to use as much of the CPU as needed.
Usage Guidelines 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.
Note 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:
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 There are no additional keywords or arguments with this command.
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
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.
Command Default The default time is 2000 ms to signal an overload of the CPU.
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
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.
Syntax Description hang Retains the process but does not schedule it.
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
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
Command Default The system-level validation on context switches on a scheduler is not configured.
Examples 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
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 Line number to which the message will be sent.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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.
Caution 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.
Examples The following example shows how to send a message to all lines:
Router# send
*
Enter message, end with CTRL/Z; abort with CTRL/C:
The system 2509 will be shut down in 10 minutes for repairs.^Z
Send message? [confirm]
Router#
***
***
*** Message from tty0 to all terminals:
***
The system 2509 will be shut down in 10 minutes for repairs.
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
Usage Guidelines 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:
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.
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:running-
config 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:
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.
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
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.
Usage Guidelines 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.
Note You must issue the reload command for the service config command to take effect.
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.
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:
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.
Note 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.
Examples This example shows how to set the time interval for retrieving statistics:
Router(config)# no
service counters max age
Router(config)#
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
Examples In the following example, the router is configured to display decimal rather than octal line numbers:
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
Usage Guidelines 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.
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.
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
Usage Guidelines 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-telnet-
address 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.
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
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.
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>
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
Usage Guidelines 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 TCP-
based traffic. However, do not use the service nagle command if you have XRemote users on X Window
system sessions.
Examples 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.
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
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 In the following example logging message sequence numbers are enabled:
Router(config)# end
Router#
000066: .Mar 22 15:35:57 PST: %SYS-5-CONFIG_I: Configured from console by console
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
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:
%IPC-5-SLAVELOG: VIP-SLOT2:
IPC-2-NOMEM: No memory available for IPC system initialization
The first line indicates which slot sent the message. The second line contains the error message.
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
Examples In the following example, keepalives on incoming TCP connections are generated:
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
Examples In the following example, keepalives on outgoing TCP connections are generated:
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.
Syntax Description max-servers (Optional) Sets the number of allowable TCP small
servers.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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
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
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
Command Default The TCP window is not set to zero when the the Telnet connection is idle.
Usage Guidelines Normally, data sent to noncurrent Telnet connections is accepted and discarded. When the service telnet-
zero-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
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]
Command Default Time stamps are applied to debug and logging messages.
Usage Guidelines Time stamps can be added to either debugging messages (service timestamp debug) or logging messages
(service timestamp log) independently.
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.
Examples 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).
! issue the show running-config command in config mode using do Router(config)# do show
running-config | inc time
Router(config)# end
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:
! Logging output can be quite long; first changing line width to show full
! logging message
Router(config)# line 0
Router(config-line)# end
Enter configuration commands, one per line. End with the end command.
! Timezone set as Pacific Standard Time, with an 8 hour offset from UTC
Router(config)# clock timezone PST -8
Router(config)#
Oct 13 23:21:27 UTC: %SYS-6-CLOCKUPDATE:
System clock has been updated from 23:21:27 UTC Wed Oct 13 2004
to 15:21:27 PST Wed Oct 13 2004, configured from console by console.
Router(config)#
! Pacific Daylight Time (PDT) configured to start in April and end in October.
! Default offset is +1 hour.
Router(config)# clock summer-time PDT recurring first Sunday April 2:00 last Sunday
October 2:00
Router(config)#
! Time changed from 3:22 P.M. Pacific Standard Time (15:22 PST)
Router(config)# end
Enter configuration commands, one per line. End with the end command.
Router(config)# service sequence-numbers
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.
Enter configuration commands, one per line. End with the end command.
Router(config)# service timestamps log datetime show-timezone year
Router(config)# end
! removed from the output, and time is displayed in UTC (the default)
service udp-small-servers
To enable small User Datagram Protocol (UDP) servers such as the Echo, use the service udp-small-
servers 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 (Optional) Sets the number of allowable UDP small
servers.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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
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
Usage Guidelines 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.
Two traffic management options are available:
• ◦ 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.
Note 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.
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
Syntax Description interface number The interface number for the wireless device.
Always use 0.
Usage Guidelines 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.
Note 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.
Use the following guideline to setup a DHCP pool on the host router.
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#service-
module 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...
Syntax Description interface number The interface number for the wireless device.
Always use 0.
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]
Examples The following examples show a graceful shut down and reboot of the service module:
Autonomous Mode
Unified Mode
Syntax Description interface number The interface number for the wireless device.
Always use 0.
Usage Guidelines At the confirmation prompt, press Enter to confirm the action, or press n to cancel.
Caution Because you may lose data, use the service-module wlan-ap reset command only to recover from a
shutdown or failed state.
Examples The following example resets a wireless device on a router that is operating in either autonomous mode or
LWAPP mode:
Autonomous Mode
LWAPP Mode
Syntax Description interface number The interface number for the wireless device.
Always use 0.
Usage Guidelines 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 user-
level 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 router’s 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.
Examples The following example shows a session being opened on a service-module in an ISR:
The following example clears the session on the service-module in the ISR:
Syntax Description interface number The interface number for the wireless device.
Always use 0.
Examples The following example displays information for wireless-enabled Cisco ISRs:
Command Description
service-module wlan-ap reload Performs a graceful shutdown and reboot on the
wireless device.
Syntax Description interface number The interface number for the wireless device.
Aways use 0.
Examples The following example displays information for the wireless device on a Cisco Integrated Services Router:
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.
Examples This example shows how to open a session with an MSM (module 4):
Syntax Description none (Optional) Resets the defined start time for
incremental analysis.
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:
show memory debug incremental leaks Displays only memory that was leaked after the
issue of the set memory debug incremental
starting-time command.
show memory debug incremental leaks lowmem Forces incremental memory leak detection to work
in low memory mode. Displays only memory that
was leaked after the issue of the set memory debug
incremental starting-time command.
show memory debug incremental status Displays if the starting point of incremental
analysis has been defined and the time elapsed
since then.
setup
To enter Setup mode, use the setup command in privileged EXEC mode.
setup
Usage Guidelines 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.
Note 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:
• Which interfaces you want to configure
• Which routing protocols you wish to enable
• Whether the router is to perform bridging
• Network addresses for the protocols being configured
• Password strategy for your environment
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
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 Protocol
Ethernet0 172.16.72.2 YES manual up up
Serial0 unassigned YES not set administratively down down
Serial1 172.16.72.2 YES not set up 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>]:
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
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#
show
To verify the Multiple Spanning Tree (MST) configuration, use the show command in MST configuration
mode.
Usage Guidelines 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.
0 4001-4096
2 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)#
show spanning-tree mst Displays the information about the MST protocol.
Usage Guidelines 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.
show <command> tee Copies the show command output to a file while
displaying it on the terminal.
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 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.
Examples 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.”
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 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 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.
Examples 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.”
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
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 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 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.
Examples 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”.
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
Command Description
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
Usage Guidelines 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:
Usage Guidelines 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 running-
configuration 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.
interface Ethernet0/0
interface Ethernet1/0
interface Serial2/0
interface 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.
Usage Guidelines 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:
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”:
Syntax Description flash-filesystem : Flash memory file system, followed by a colon. The
availablity of Flash file system keywords will vary
by platform. Valid flash file system keywords
inlude:
• bootflash
• flash
• slot0
• slot1
• slavebootflash
• slaveslot0
• slaveslot1
Usage Guidelines 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:
• Class A Flash File System
• Class B Flash File Systems
Although the examples use flash: as the Flash file system, you may also use the other Flash file systems
listed.
Field Description
# Index number for the file.
Field Description
type File type (1 = configuration file, 2 = image file).
The software displays these values only when the
file type is certain. When the file type is unknown,
the system displays “unknown” in this field.
date/time Date and time the file was created. In the example,
-08:00 indicates that the given date and time is 8
hours behind Coordinated Universal Time (UTC).
The following is sample output from the show flash: chips command:
The following is sample output from the show flash: filesys command:
The following example shows detailed information about the second partition in internal Flash memory:
Field Description
addr Address of the file in Flash memory.
Field Description
Name/status Filename and status of a system image file. The
status [invalidated] appears when a file has been
rewritten (recopied) into Flash memory. The first
(now invalidated) copy of the file is still present
within Flash memory, but it is rendered unusable in
favor of the newest version. The [invalidated] status
can also indicate an incomplete file that results
from the user abnormally terminating the copy
process, a network timeout, or a Flash memory
overflow.
The following is sample output from the show flash: all command:
The following is sample output from the show flash: all command on a router with Flash memory
partitioned:
1 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:
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.
show aliases
To display all alias commands, or the alias commands in a specified mode, use the show aliases command
in EXEC mode.
Usage Guidelines 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.
show alignment
To display alignment errors and spurious memory access errors, use the show alignment command in
privileged EXEC mode.
show alignment
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
The following is sample output from the show alignment command when there are no alignment or
spurious memory errors:
Field Description
Total Corrections Total number of alignment corrections made.
The following is sample output from the show alignmentcommand when there are only spurious memory
access errors:
The table below describes the significant fields shown in the display.
Table 45 show alignment Field Descriptions for Spurious Memory Access Errors
Field Description
Total Spurious Accesses Total number of spurious memory accesses made.
The following is sample output from the show alignmentcommand when there are alignment errors and
spurious memory access errors:
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
Examples The following is sample output from the show archive command:
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.
The table below describes the significant fields shown in the displays.
Field Description
Archive # Indicates the number of the running configuration
file saved to the Cisco IOS configuration archive.
You can set the maximum number of archive files
of the running configuration to be saved in the
configuration archive. The most recent archive file
is the last one shown in the display.
Command Description
maximum Sets the maximum number of archive files of the
running configuration to be saved in the Cisco IOS
configuration archive.
Command Default 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.
Release Modification
12.2(27)SBC This command was integrated into Cisco IOS
Release 12.2(27)SBC.
Usage Guidelines 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:
• 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).
Examples 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.
no ip subnet-zero ip subnet-zero
ip cef ip cef
interface Ethernet1/0 ip name-server 10.4.4.4
ip address 10.7.7.7 255.0.0.0 voice dnis-map 1
no ip route-cache dnis 111
no ip mroute-cache interface Ethernet1/0
duplex half no ip address
no ip classless no ip route-cache
snmp-server community public RO no ip mroute-cache
shutdown
duplex half
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
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.
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 Configuration Files Used for the Incremental Diff Operation Example
ip subnet-zero no ip subnet-zero
ip cef ip cef
ip name-server 10.4.4.4 interface Ethernet1/0
voice dnis-map 1 ip address 10.7.7.7 255.0.0.0
dnis 111 no ip route-cache
interface Ethernet1/0 no ip mroute-cache
no ip address duplex half
no ip route-cache no ip classless
no ip mroute-cache snmp-server community public RO
shutdown
duplex half
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
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.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
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:
The table below describes the significant fields in the sample output.
Field Description
Time configured (or reconfigured) The time with which the timer refreshes every time
the ENTER key is presses.
Timer value Displays the time, in minutes, for which to wait for
confirmation.
configure terminal revert timer Enter global configuration mode and sets the
parameters for reverting the configuration if
confirmation of the new configuration is not
received.
show archive log config {all | record-number [end-number] | user username[ session session-
number] record-number [end-number] | statistics} [provisioning] [contenttype {plaintext | xml}]
[persistent]
Usage Guidelines 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:
The table below describes the significant fields shown in the display.
Field Description
idx The record number of the configuration log entry.
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.
<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
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 The following is sample output from the show as5400 command:
The table below describes the significant fields shown in the display.
Field Description
System I/O Controller PLD version The version of the programmable logic device
(PLD) on the system.
Examples 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.
Field Description
bootfile... “pcboot” Boot file for address 192.168.1.1 is named pcboot.
time-offset -3600 Local time is one hour (3600 seconds) earlier than
UTC time.
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#
upgrade automatic runversion Reloads the device with a new Cisco IOS software
image.
show bcm560x
To display the BCM560x hardware table information, use the show bcm560X command in user EXEC or
privileged EXEC mode.
Syntax Description name Displays the bcm50x hardware table name. The
hardware table name can be VLAN table name
(VTABLE) or Port based VLAN table name
(PTABLE):
Examples The following is sample output from the show bcm560X allcommand:
show bootflash:
To display information about the bootflash: file system, use the show bootflash: command in user EXEC
or privileged EXEC mode.
Examples 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
Router>
show bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image 8C5A393A 237E3C 14 2063804 Aug 23 1999 16:18:45 c6msfc-boot-mz
2 .. image D86EE0AD 957CE8 9 7470636 Sep 20 1999 13:48:49 rp.halley
Router>
Router>
show bootflash: all
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image 8C5A393A 237E3C 14 2063804 Aug 23 1999 16:18:45 c6msfc-boot-
mz
2 .. image D86EE0AD 957CE8 9 7470636 Sep 20 1999 13:48:49 rp.halley
6456088 bytes available (9534696 bytes used)
-------- 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
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 = 917CE8 Bytes Available = 628318
Bad Sectors = 0 Spared Sectors = 0
OK Files = 2 Bytes = 917BE8
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
Router>
Command Description
squeeze Removes files from bootflash that have been
marked for deletion.
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
Usage Guidelines Supported Platforms Other than the Cisco 7600 Series Router
The show bootvar command replaces the show bootcommand.
The show bootvar command allows you to view the current settings for the following variables:
• 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
Supported Platforms Other than the Cisco 7600 Series Router
The following is sample output from the show bootvar command:
Field Description
BOOT variable Displays a list of specified bootable images.
BOOTLDR variable Identifies the location of the boot image that ROM
uses for booting, if it is specified.
current slave is in slot 7 Indicates the slot where the redundant system is
located in HSA configurations.
Router#
show bootvar
BOOT variable = sup-bootflash:c6sup12-js-mz.121-13.E,12
CONFIG_FILE variable =
BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-13.E.bin
Configuration register is 0x2102
Standby is up
Standby has 112640K/18432K bytes of memory.
Standby BOOT variable = bootflash:c6sup12-js-mz.121-13.E,12
Standby CONFIG_FILE variable =
Standby BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-13.E.bin
Standby Configuration register is 0x2102
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.
boot system Specifies the system image that the router loads at
startup.
Command Description
copy Copies a file from source to a destination.
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 pool-
name]} [dump | header | packet | location pool-location]]
Command Default If no options are specified, all buffer pool information is displayed.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches with support for
the detailed process command option.
Examples 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:
• show buffers, page 797
• show buffers, page 797
• show buffers, page 797
The following is sample output from the show buffers command with an interface type and interface
number:
The table below describes the significant fields shown in the display.
Field Description
Buffer elements Small structures used as placeholders for buffers in
internal operating system queues. Used when a
buffer may need to be on more than one queue.
Field Description
peak Maximum number of buffers created (highest total)
and the time when that peak occurred. Formats
include weeks, days, hours, minutes, and seconds.
Not all systems report a peak value, which means
this field may not display in output.
Field Description
fallbacks Count of buffer allocation attempts that resulted in
falling back to the public buffer pool that is the
smallest pool at least as big as the interface buffer
pool.
max cache size Maximum number of buffers from the pool of that
interface that can be in the buffer pool cache of that
interface. Each interface buffer pool has its own
cache. These are not additional to the permanent
buffers; they come from the buffer pools of the
interface. Some interfaces place all of their buffers
from the interface pool into the cache. In this case,
it is normal for the free list to display 0.
The table below describes the significant fields shown in the display that are different from the fields in the
first table.
Field Description
Public Buffer Headers
Field Description
trims Count of buffers released to the system because
they were not being used. This field is displayed
only for dynamic buffer pools, not interface buffer
pools, which are static.
Switch#show buffers
PDS public buffers
Public buffer pools:
Packet buffer, 2048 bytes (total 1000, permanent 1000):
1000 in free list (1000 max allowed)
Header pools:
Packet Header Memory, 0 bytes (total 0, permanent 0):
0 in free list (0 max allowed)
Buffer Header Memory, 0 bytes (total 0, permanent 0):
0 in free list (0 max allowed)
IOSd private buffers:
Buffer elements:
354 in free list (500 max allowed)
27134 hits, 0 misses, 500 created
Public buffer pools:
Small buffers, 104 bytes (total 134, permanent 50, peak 134 @ 01:04:39):
134 in free list (20 min, 150 max allowed)
2554 hits, 28 misses, 0 trims, 84 created
0 failures (0 no memory)
Middle buffers, 600 bytes (total 52, permanent 25, peak 52 @ 01:04:39):
52 in free list (10 min, 150 max allowed)
61 hits, 9 misses, 0 trims, 27 created
0 failures (0 no memory)
Big buffers, 1536 bytes (total 50, permanent 50):
50 in free list (5 min, 150 max allowed)
157 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
VeryBig buffers, 4520 bytes (total 10, permanent 10):
10 in free list (0 min, 100 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Large buffers, 5024 bytes (total 0, permanent 0):
0 in free list (0 min, 10 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Huge buffers, 18024 bytes (total 0, permanent 0):
0 in free list (0 min, 4 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Interface buffer pools:
CF Small buffers, 104 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)
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
Usage Guidelines The show c2600 command provides complex troubleshooting information that pertains to the platform’s
shared references rather than to a specific interface.
Examples The following is sample output from the show c2600 command:
Assigned Handlers...
Vect Handler # of Ints Name
00 801F224C 00000000 Xilinx bridge error interrupt
01 801DE768 0D3EE155 MPC860 TIMER INTERRUPT
02 801E94E0 0000119E 16552 Con/Aux Interrupt
04 801F0D94 00000000 PA Network Management Int Handler
05 801E6C34 00000000 Timebase Reference Interrupt
06 801F0DE4 00002C1A PA Network IO Int Handler
07 801F0EA0 0000015D MPC860 CPM INTERRUPT
14 801F224C 00000000 Xilinx bridge error interrupt
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.
Field Description
Interrupts Denotes that the next section describes the status of
the interrupt services.
IOS Priority Masks Denotes the subsection of the Interrupt section that
displays internal Cisco IOS priorities. Each item in
this subsection indicates a Cisco IOS interrupt level
and the bit mask used to mask out interrupt sources
when that Cisco IOS level is being processed. Used
exclusively for debugging.
Field Description
Timer Count Number of times throttle has deactivated because
the maximum masked out time for network
interrupt level has been reached.
Field Description
New version after next program operation Version of ISP hardware after next ISP
programming operation.
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
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 The following is sample output from the show c7200 command:
show catalyst6000
To display the information about the chassis, use the show catalyst6000 command in user EXEC or
privileged EXEC mode.
Syntax Description all Displays the MAC-address ranges and the current
and peak traffic-meter reading.
Usage Guidelines 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>
Router#
show catalyst6000 chassis-mac-address
chassis MAC addresses: 1024 addresses from 00d0.004c.1800 to 00d0.004c.1c00
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:
monitor traffic-util fpoe Sets the fabric channel traffic utilization monitor to
generate SYSLOG messages.
show environment status Displays the information about the operational FRU
status.
show cls
To display the current status of all Cisco link services (CLS) sessions on the router, use the show
clscommand in EXEC mode.
Usage Guidelines 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 command:
The following is sample output from the show cls brief command:
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.
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.
Usage Guidelines 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.:
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:
Configuration version : 9
Last change time : 2006-06-18T18:34:34.431Z
Changed by user : system
Changed from process : Init
show configuration id
To display output about configuration versions, use the show configuration idcommand in privileged
EXEC mode.
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.
Cisco IOS XE Release 2.5 This command was implemented on Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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.:
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.
Configuration version : 9
Last change time : 2006-06-18T18:34:34.431Z
Changed by user : system
Changed from process : Init
Examples 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(config)# end
Router# show running-config
| include configuration
The following is sample output from the show configuration lockcommand when the running
configuration file is not locked by another user.
The table below describes the significant fields shown in the displays.
Field Description
Owner PID Process identifier (PID) of the process that owns the
lock.
User debug info Any string given by the process (used for
debugging only).
No of exec cmds getting executed Total number of EXEC commands (show and
clear) being executed simultaneously from
different sessions.
Lock active time (in Sec) Amount of time, in seconds, that elapsed since the
lock was acquired.
Lock Expiration timer (in Sec) The amount of time, in seconds, that expires before
the lock is automatically released.
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.
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.
slot slot-number crash-index Displays information for a particular line card. Slot
numbers range from 0 to 11 for the Cisco 12012
router and from 0 to 7 for the Cisco 12008. The
index number allows you to look at previous crash
contexts. Contexts from the last 24 line card crashes
are saved on the GRP card. If the GRP reloads, the
last 24 line card crash contexts are lost. For
example, show context slot 3 2 shows the second
most recent crash for line card in slot 3. Index
numbers are displayed by the show context
summary command.
Usage Guidelines 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:
The following is sample output from the show contextcommand following an unexpected system reload on
a Cisco 2600 series router.
The table below describes the significant fields shown in the display.
Field Description
S/W Version Standard Cisco IOS version string as displayed.
Command Description
show stacks Monitors the stack usage of processes and interrupt
routines.
show controllers [atm slot-number | clock | csar [register] | csc-fpga | dp83800 | fab-clk | fia
[register] | pos [slot-number] [details] | queues [slot-number] | sca | xbar]
Syntax Description atm slot-number (Optional) Displays the ATM controllers. Number
is slot-number/ port-number (for example, 4/0). Slot
numbers range from 0 to 11 for the Cisco 12012
router and from 0 to 7 for the Cisco 12008 router.
pos [slot-number] [details (Optional) Displays the POS framer state and
optionally displays all the details for the interface.
Number is slot-number/port-number (for example,
4/0). Slot numbers range from 0 to 11 for the Cisco
12012 router and from 0 to 7 for the Cisco 12008
router.
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:
show controllers (line card image) Displays information that is specific to the
hardware on a line card.
Release Modification
12.2(33)SB This command’ behavior was modified on the
Cisco 10000 series router for the PRE3 and PRE4.
Usage Guidelines 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:
• 4-port channelized STM1
• 1-port channelized OC-12
• 6-port channelized T3
• 4-port half-height channelized T3
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:
The following is partial sample output from the show controllers command:
.
.
Router#
The following is partial sample output from the show controllers fia command:
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:
The following is a sample output from the show controllers events punt-sniff command:
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:
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:
Usage Guidelines 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:
00:00:05:%SYS-5-RESTART:System restarted --
.
.
.
The table below describes the significant fields shown in the display.
Field Description
Syslog logging Shows general state of system logging (enabled or
disabled), and status of logged messages (number
of messages dropped, rate-limited, or flushed).
Usage Guidelines 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.
Command Description
show controllers Displays information that is specific to the
hardware.
Examples The following is sample output from the show coverage history command. The output is self-explanatory.
show data-corruption
To display data inconsistency errors of the present software version, use the show data-
corruptioncommand in user EXEC or privileged EXEC mode.
show data-corruption
Cisco IOS 2.3 XE This command was integrated into Cisco IOS XE
Release 2.3.
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.
Count Traceback
1842 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
Examples The following is sample output from the show debugging command. In this example, the remote host is not
configured or connected.
The following is sample output from the show debugging command when user-group debugging is
configured:
!
The following is sample output from the show debugging command when SNAP debugging is configured:
Field Description
OPTS 4 Bytes of TCP expressed as a number. In this case,
the bytes are 4.
Field Description
ECE Echo congestion experience.
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
Note The show declassify command is supported on the Cisco 3200 series routers only.
Examples The following example is sample output for the show declassify command:
The table below describes the significant fields shown in the display.
Field Description
Enabled A “Yes” value indicates that zeroization is enabled.
A “No” value indicates that zeroization is disabled.
Field Description
In Progress A “Yes” value indicates that zeroization is currently
in progress.
A “No” value indicates that zeroization is currently
not in progress.
Obtain memory size Obtain the main memory size in order to understand
how much of the memory is to be scrubbed.
Declassify Console and AUX Ports Remove potentially sensitive information from
console and AUX port FIFOs.
Declassify RAM, D-Cache, and I-Cache Scrub the main memory, erase the Data Cache (D-
Cache), and erase the Instruction Cache (I-Cache).
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.
Syntax Description interface type number (Optional) Displays the derived configuration for a
specific interface. If you use the interface keyword,
you must specify the interface type and the
interface number (for example, interface ethernet
0).
Usage Guidelines 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.
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...
Building configuration...
Syntax Description publish Displays the subject with which the diagnostic
results is published.
Usage Guidelines 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:
Subject: cisco.cns.device.diag_results
Subject: cisco.cns.device.diag_get_results
Command Default Displays information for all the Gigabit Ethernet WAN interfaces in the Cisco 7600 series router.
Usage Guidelines 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.
Spanning-Tree VLAN Checks
• 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.
Spanning-Tree Port Checks
• 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 has UDLD disabled, the system flags it.
• If a port had UDLD shut down, the system flags it.
• If a port had a UDLD undetermined state, the system flags it.
Assorted Port 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 system flags it.
• If a port has a native VLAN mismatch, the system flags it.
• If a port has a duplex mismatch, the system flags it.
Bootstring and Config Register Checks
• 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
• The system displays a message if IGMP snooping is disabled.
• The system displays a message if any of the values of the snmp community access strings
{RO,RW,RW-ALL} is the same as the default.
• The system displays a message if any of the modules are in states other than “Ok.”
• The system displays a message that lists all the tests that failed (displayed as an “F”) in the show test
all command.
• The system displays a message if *fast is not configured on the switch anywhere.
• The system displays a message if there is enough room for the crashinfo file on the bootflash:.
• 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.
Examples 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
show disk
To display flash or file system information for a disk, use the show diskcommand in user or privileged
EXEC mode.
Usage Guidelines The show disk command is supported only on platforms that have a disk file system.
Note 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.
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.
Usage Guidelines 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 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.
Examples The following examples show displays of information about the flash disks or file system information for a
disk. The output is self-explanatory.
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)
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.
Usage Guidelines 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 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.
Examples The following examples show displays of information about the flash disks or file system information for a
disk. The output is self-explanatory.
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]
Release Modification
12.4(4)XD This command was integrated into Cisco IOS
Release 12.4(4)XD to support the NPE-G2 on the
Cisco 7200 VXR using the all, last, and table
keywords. Command output was modified for the
NPE-G2.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1 on the Cisco ASR 1000 Series Routers.
Usage Guidelines 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 CISCO-
ENTITY-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:
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 snmp-
server 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 CISCO-
ENVMON-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.
The following table describes the significant fields shown in the display.
Field Description
Sensor Sensor name.
The following table describes the significant fields shown in the display.
Field Description
Environmental status as of... Current date and time.
Table 64 show environment all Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field Description
Power Supply x is present. Specifies whether the indicated (x) power supply
slot is populated. If a power supply slot is
populated, the manufacturer name and whether it is
an AC or DC power supply is displayed.
NPE Inlet measured at 25C/77F Indicates that the temperature measurements at the
inlet area of the chassis is 25C/77F, which is within
normal operating range. System shutdown for NPE
Inlet is 80C/176F.
NPE Outlet measured at 28C/82F Indicates that the temperature measurements at the
outlet area of the chassis is 28C/82F, which is
within normal operating range. System shutdown
for NPE Outlet is 84C/183F.
Field Description
CPU Die measured at 56C/132F Indicates that the temperature measurement at the
CPU Die (internal silicon of the CPU) area of the
chassis is 56C/132F, which is within normal
operating range. System shutdown for CPU Die is
100C/212F.
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.
Table 65 show environment last Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field Description
NPE Inlet previously measured at 26C/78F The last measured temperature of the inlet air of the
router prior to shutdown.
NPE Outlet previously measured at 28C/82F The last measured temperature of the outlet air of
the router prior to shutdown.
CPU Die previously measured at 56C/132F The last measured temperature of the CPU Die
prior to shutdown.
+3.30 V previously measured at +3.32 The last measured voltage of the 3.30 V power rail
prior to shutdown.
VDD_CPU previously measured at +1.28 The last measured voltage of the VDD_CPU power
rail prior to shutdown.
VDD_MEM previously measured at +2.50 The last measured voltage of the VDD_MEM
power rail prior to shutdown.
VTT previously measured at +1.25 The last measured voltage of the VTT power rail
prior to shutdown.
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.
Table 66 show environment table Field Descriptions for NPE-G2 in Cisco 7200 VXR Router
Field Description
Sample Point This is the area for which temperature or system
voltage thresholds are displayed.
Field Description
NPE Inlet 44C/111F 59C/138F These are the HighWarn and HighCrit temperature
thresholds, respectively, for the NPE Inlet.
If the NPE Inlet temperature value reaches the
HighWarn (44C/111F) and HighCrit (59C/138F)
levels, warning and critical messages, respectively,
are issued.
If the value reaches 44C/111F or greater, you
receive a warning message indicating HighWarn.
The system continues to operate, but operator
action is recommended to bring the system back to
a normal state.
If the value reaches 59C/138F or greater, you
receive a critical (HighCrit) message instead, that
indicates the system continues to operate, but the
system is approaching shutdown.
Note Beware if the temperature reaches or
exceeds 80C/176F, which is the HighShut
value, a Shutdown message is issued, and
the NPE Inlet area shuts down.
NPE Outlet 49C/120F 64C/147F These are the HighWarn and HighCrit temperature
thresholds, respectively, for the NPE Outlet.
If the NPE Outlet temperature value reaches the
HighWarn (49C/120F) and HighCrit (64C/147F)
levels, warning and critical messages, respectively,
are issued.
If the value reaches 49C/120F or greater, you
receive a warning message indicating HighWarn.
The system continues to operate, but operator
action is recommended to bring the system back to
a normal state.
If the value reaches 64C/147F or greater, you
receive a critical (HighCrit) message instead that
indicates the system continues to operate, but the
system is approaching shutdown.
Note Beware if the temperature reaches or
exceeds 84C/183F, which is the HighShut
value, a Shutdown message is issued, and
the NPE Outlet area shuts down.
Field Description
CPU Die 75C/167F 85C/185F These are the HighWarn and HighCrit temperature
thresholds, respectively, for the CPU Die.
If the CPU Die temperature value reaches the
HighWarn (75C/167F) and HighCrit (85C/185F)
levels, warning and critical messages, respectively,
are issued.
If the value reaches 75C/167F or greater, you
receive a warning message indicating HighWarn.
The system continues to operate, but operator
action is recommended to bring the system back to
a normal state.
If the value reaches 85C/185F or greater, you
receive a critical (HighCrit) message instead, that
indicates the system continues to operate, but the
system is approaching shutdown.
Note Beware if the temperature reaches or
exceeds 100C/212F, which is the HighShut
value, a Shutdown message is issued and the
CPU Die area shuts down.
System shutdown for NPE Inlet is 80C/176F This is the HighShut temperature threshold for the
NPE Inlet.
If the temperature reaches or exceeds 80C/176F, a
Shutdown message is issued and the NPE Inlet area
is shut down.
System shutdown for NPE Outlet is 84C/183F This is the HighShut temperature threshold for the
NPE Outlet.
If the temperature reaches or exceeds 84C/183F, a
Shutdown message is issued and the NPE Outlet
area is shut down.
System shutdown for CPU Die is 100C/212F This is the HighShut temperature threshold for the
CPU Die.
If the temperature reaches or exceeds 100C/212F, a
Shutdown message is issued and the CPU Die area
is shut down.
Field Description
+3.30 V +2.30 +3.12 +3.47 +4.29 The voltage thresholds for the +3.30 V power rail
are as follows:
• +2.30 is the LowShut voltage threshold.
• +3.12 is the LowCrit voltage threshold.
• +3.47 is the HighCrit voltage threshold.
• +4.29 is the HighShut voltage threshold.
Note The LowWarn and HighWarn voltage levels
are not checked and their thresholds are not
displayed on the NPE-G2.
VDD_CPU +0.89 +1.21 +1.36 +1.71 The voltage thresholds for the VDD_CPU power
rail are as follows:
• +0.89 is the LowShut voltage threshold.
• +1.21 is the LowCrit voltage threshold.
• +1.36 is the HighCrit voltage threshold.
• +1.71 is the HighShut voltage threshold.
Note The LowWarn and HighWarn voltage levels
are not checked and their thresholds are not
displayed on the NPE-G2.
VDD_MEM +1.71 +2.34 +2.61 +3.28 The voltage thresholds for the VDD_MEM power
rail are as follows:
• +1.71 is the LowShut voltage threshold.
• +2.34 is the LowCrit voltage threshold.
• +2.61 is the HighCrit voltage threshold.
• +3.28 is the HighShut voltage threshold.
Note The LowWarn and HighWarn voltage levels
are not checked and their thresholds are not
displayed on the NPE-G2.
VTT +0.85 +1.17 +1.32 +1.64 The voltage thresholds for the VTT power rail are
as follows:
• +0.85 is the LowShut voltage threshold.
• +1.17 is the LowCrit voltage threshold.
• +1.32 is the HighCrit voltage threshold.
• +1.64 is the HighShut voltage threshold.
Note The LowWarn and HighWarn voltage levels
are not checked and their thresholds are not
displayed on the NPE-G2.
The system displays the following message if voltage or temperature exceed maximum margins:
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.
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
Environmental status as of... Date and time of last query.
Lower Power Supply Type of power supply installed and its status (on or
off).
Upper Power Supply Type of power supply installed and its status (on or
off).
Airflow and inlet temperature Temperature of air coming in and going out.
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.
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
Environmental status as of... Date and time of last query.
LAST Environmental Statistics Displays test point values at time of the last
environmental shutdown.
Lower Power Supply For the Cisco 7000 router, indicates the status of the
two 700W power supplies.
Upper Power Supply
For the Cisco 7010 router, indicates the status of the
single 600W power supply.
The following example shows sample output for the current environmental status in tables that list voltage
and temperature parameters. There are three warning messages: one each about the lower power supply, the
airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the
normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level.
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
SENSE (Voltage Parameters) Voltage specification for a DC line.
SENSE (Temperature Parameters) Air being measured. Inlet measures the air coming
in, and Airflow measures the temperature of the air
inside the chassis.
The system displays the following message if the voltage or temperature enters the “Critical” range:
The system displays the following message if the voltage or temperature exceeds the maximum margins:
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.
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.
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:
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 Current condition of the power supplies including
the type and whether the power supply is on or off.
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).
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 Temperature measurements at the inlet area of the
chassis.
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 LowWarning HighWarning HighCritical
chassis inlet 40C/104F 50C/122F
chassis outlet 1 43C/109F 53C/127F
chassis outlet 2 75C/167F 75C/167F
chassis outlet 3 55C/131F 65C/149F
+3.45 V +2.76 +3.10 +3.80 +4.14
+5.15 V +4.10 +4.61 +5.67 +6.17
+12.15 V +9.72 +10.91 +13.37 +14.60
-11.95 V -8.37 -9.57 -14.34 -15.53
Shutdown system at 70C/158F
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 Area for which measurements are taken.
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 Numbers indicating the arbiter type and backplane
type.
Active fault conditions: Lists any fault conditions that exist (such as power
supply failure, fan failure, and temperature too
high).
15 of 15 soft shutdowns remaining When the temperature increases above the “board
shutdown” level, a soft shutdown occurs (that is,
the cards are shut down, and the power supplies,
fans, and CI continue to operate). When the system
cools to the restart level, the system restarts. The
system counts the number of times this occurs and
keeps the up/down cycle from continuing forever.
When the counter reaches zero, the system
performs a hard shutdown, which requires a power
cycle to recover. The soft shutdown counter is reset
to its maximum value after the system has been up
for 6 hours.
Field Description
Dbus slots: Indicates which chassis slots are occupied.
Voltages (+12V, +5V, -12V, +24V, +2.5) Voltages measured on the backplane.
The following example is for the Cisco 7500 series routers. This example shows the measurements
immediately before the last shutdown.
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
RSP(4) Inlet, Hotpoint, Exhaust Temperature measurements at the inlet, hotpoint,
and exhaust areas of the card.
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.
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 Area for which measurements are taken.
Restart after shutdown The system will restart when the specified
temperature is met.
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).
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 # Slot number of the equipment. On the Cisco 12012
router, slots 0 through 11 are the line cards, slots 16
and 17 are the clock and scheduler cards, slots 18
through 20 are the switch fabric cards, slots 24
through 27 are the power supplies, and slots 28 and
29 are the blowers.
Hot Sensor (deg C) Measures the temperature at the hot sensor on the
card. The hot sensor is on the line cards, GRP card,
clock and scheduler cards, switch fabric cards, and
blowers.
Field Description
Inlet Sensor (deg C) Measures the current inlet temperature on the card.
The inlet sensor is on the line cards, GRP card,
clock and scheduler cards, switch fabric cards, and
power supplies.
Fan 0, Fan 1, Fan 2 (RPM) Measures the fan speed in rotations per minute.
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).
3V Ranges (mv):
Warning Critical Shutdown
Below Above Below Above Below Above
GRP/GLC (Slots 0-15) 3200 3400 3100 3500 3050 3550
CSC (Slots 16-17) 3200 3400 3100 3500 3050 3550
SFC (Slots 18-20) 3200 3400 3100 3500 3050 3550
5V Ranges (mv):
Warning Critical Shutdown
Below Above Below Above Below Above
GRP/GLC (Slots 0-15) 4850 5150 4750 5250 4680 5320
Bottom Blower:
Warning Critical
Below Below
Fan 0 1000 750
Fan 1 1000 750
Fan 2 1000 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.
The following is sample output from the show environment lastcommand on a Cisco 7304 router with
MSCs and SPAs installed and an NSE-100:
The following is sample output from the show environment tablecommand on a Cisco 7304 router with
MSCs and SPAs installed:
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 Area for which measurements are taken.
Field Description
LowWarn/LowWarning Level at which a warning message is issued for an
out-of-tolerance voltage condition. The system
continues to operate, but operator action is
recommended to bring the system back to a normal
state.
The following table describes the significant fields shown in the display.
Table 78 show environment subslot Field Descriptions for the Cisco uBR10012 Router
Field Description
Number of Temperature Sensors The number of temperature sensors for which
measurements are taken.
Command Default If you do not enter a frutype, all the information about the environmental alarm status is displayed.
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.
Examples 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
Usage Guidelines 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)
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)
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:
Syntax Description frutype (Optional) FRU type; see the Note for a list of valid
values.
Command Default If you do not enter a frutype, all FRU status information is displayed.
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.
Examples 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:
The table below describes the fields that are shown in the example.
Field Description
operating clock count Physical clock count.
fan tray fan operation sensor System fan tray failure status. The failure of the
system fan tray is indicated as a minor alarm.
VTT 1, VTT2, and VTT3 Status of the chassis backplane power monitors that
are located on the rear of the chassis, under the rear
cover. Operation of at least two VTTs is required
for the system to function properly. A minor system
alarm is signaled when one of the three VTTs fails.
A major alarm is signaled when two or more VTTs
fail and the supervisor engine is accessible through
the console port.
power-supply # fan-fail Fan failure. Fan failures on either or both (if any)
power supplies are considered minor alarms.
device-1 and device-2 temperature Two devices that measure the internal temperature
on each indicated module. The temperature shown
indicates the temperature that the device is
recording. The devices are not placed at an inlet or
an exit but are additional reference points.
Syntax Description frutype (Optional) Field replaceable unit (FRU) type; see
the “Usage Guidelines” section for a list of valid
values.
Command Default If you do not enter a frutype, the module and EARL temperature readings are displayed.
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:
• N/O means not operational--The sensor is broken, returning impossible values.
• N/A means not available--The sensor value is presently not available; try again later.
• VTT 1, 2, and 3 refer to the power monitors that are located on the chassis backplane under the rear
cover.
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
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.
Field Description
outlet temperature Exhaust temperature value.
device-1 and device-2 temperature Two devices that measure the internal temperature
on the indicated module. The temperature shown
indicates the temperature that the device is
recording. The devices are not placed at an inlet or
an exit but are additional reference points.
show environment status Displays the information about the operational FRU
status.
Examples This example shows how to display the error-disable detection status:
Router>
show errdisable detect
ErrDisable Reason Detection status
----------------- ----------------
udld Enabled
bpduguard Enabled
rootguard Enabled
packet-buffer-err Enabled
pagp-flap Enabled
dtp-flap Enabled
link-flap Enabled
Router#
Examples 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
show fastblk
To display fast block memory information, use the show fastblkcommand in privileged EXEC mode.
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.
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:
Field Description
FD File descriptor. The file descriptor is a small integer
used to specify the file once it has been opened.
Field Description
Path Location of the file.
Examples The following is sample output from the show file information command:
Types Description
image (a.out) Runnable image in a.out format.
Types Description
ebcdic Text generated on an IBM mainframe.
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:
- - ram rw tmp:
- - opaque rw system:
42541056 42541056 disk rw disk1: disk1:0:#
* 512065536 30834688 disk rw disk0:#
65536000 19811932 flash rw bootflash: sup-bootflash:
- - opaque ro ivfs:
129004 102228 nvram rw const_nvram:
125802334 0 opaque ro microcode: sup-microcode:
0 609689428 opaque rw image: sup-image:
- - opaque rw null:
- - opaque ro tar:
1964024 1949453 nvram rw nvram:
- - network rw rcp:
- - network rw tftp:
- - network rw http:
- - network rw ftp:
- - disk rw disk1:1:
- - disk rw disk1:2:
512065536 30842880 disk rw slavedisk0:#
- - disk rw slavedisk1: slavedisk1:0:
65536000 19328264 flash rw slavesup-bootflash:
1964024 1919757 nvram rw slavenvram:
129004 102228 nvram rw slaveconst_nvram:
65536000 65536000 flash rw slavebootflash:
- - nvram rw slavercsf:
- - opaque rw slavesystem:
- - disk rw slavedisk1:1:
- - disk rw slavedisk1:2:
- - disk rw slavedisk1:3:
The table below describes the significant fields shown in the display.
Field Description
Size(b) Amount of memory in the file system (in bytes).
The "*" references the default device/directory
when flash is used in a generic manner. For
example, if you were to type sh flash and the device
actually has bootflash:, the output of sh flash will
actually be the output of dir bootflash: show file
systems shows the devices that this rtr can access.
The "*" indicates the default device.
Field Description
Type Type of file system. The file system can be one of
the following types:
• disk-- The file system is for a rotating medium.
• flash-- The file system is for a flash memory
device.
• network-- The file system is a network file
system (TFTP, rcp, FTP, and so on).
• nvram-- The file system is for an NVRAM
device.
• opaque-- The file system is a locally generated
“pseudo” file system (for example, the
“system”) or a download interface, such as
brimux.
• ram-- The file system is for a RAM or EPROM
device.
• tty-- The file system is for a collection of
terminal devices.
• unknown -- The file system is of unknown
type.
Flags Permissions for the file system. The file system can
have one of the following permission states:
• ro--The file system is Read Only.
• wo--The file system is Write Only.
• rw--The file system is Read/Write.
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.
Usage Guidelines 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:
• interface:--Interface on which the internet protocol (IP) inspect feature is enabled
• (direction)--Direction in which the IP inspect feature is enabled (IN or OUT)
• acl name:--Name that is used to identify packets being inspected
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
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 Interface type; possible valid values are ethernet,
fastethernet, gigabitethernet, tengigabitethernet,
port-channel, pos, atm, null, tunnel, and ge-wan
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 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
Examples 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
Examples This example shows how to display a summary of feature manager information:
Router>
show fm summary
Current global ACL merge algorithm:BDD
Interface:FastEthernet2/10
ACL merge algorithm used:
inbound direction: ODM
outbound direction:BDD
TCAM screening for features is ACTIVE outbound
TCAM screening for features is ACTIVE inbound
Interface:FastEthernet2/26
ACL merge algorithm used:
inbound direction: ODM
outbound direction:BDD
TCAM screening for features is ACTIVE outbound
TCAM screening for features is INACTIVE inbound
.
.
.
Router>
show funi
To display the frame-based user-network interface information, use the show funicommand in user EXEC
or privileged EXEC mode.
Usage Guidelines 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:
The following is sample out from the show funi vc detail prefix pvi/vci command. The fields are self-
explanatory:
Examples The following is output from the show identity policy command:
Name: p2
Description: NONE
Access-Group: another-acl
URL-Redirect Match ACL: redirect-acl
URL-Redirect URL: http://www.foo.com/bar.html
Router#
Usage Guidelines 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.
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the show
gsr command in EXEC mode.
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.
The following is sample output from the show gsr chassis-info command for a Cisco 12012 router:
show gt64010
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:
show hardware
To display the hardware-specific information for a router, use the show hardwarecommand in user EXEC
or privileged EXEC mode.
show hardware
Usage Guidelines Use the show hardware command to display the hardware specific information for a router.
Examples The following is sample output from the show hardware command:
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.
2 FastEthernet interfaces
4 Serial interfaces
125K bytes of NVRAM.
62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
125440K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2002
show health-monitor
To display the system Health Monitor status information, use the show health-monitorcommand in user
EXEC or privileged EXEC mode.
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.
show history
To list the commands you have entered in the current EXEC session, use the show history command in
EXEC mode.
show history
Usage Guidelines 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.
Key Function
Ctrl-P or Up Arrow3 Recalls commands in the history buffer in a
backward sequence, beginning with the most recent
command. Repeat the key sequence to recall
successively older commands.
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:
terminal history size Enables the command history feature for the current
terminal session, or changes the size of the
command history buffer for the current terminal
session.
Usage Guidelines Use the show history allcommand to display command history and reload information of a router.
Examples The following is sample output from the show history allcommand:
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 (Optional) The vrf-name argument specifies the
name of the Virtual Private Network (VPN) routing
and forwarding (VRF) instance associated with the
DNS view whose hostname cache entries are to be
displayed. Default is the global VRF (that is, the
VRF whose name is a NULL string) with the
specified or default DNS view.
Note More than one DNS view can be associated
with a VRF. To uniquely identify a DNS
view, specify both the view name and the
VRF with which it is associated.
Usage Guidelines 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:
The table below describes the significant fields shown in the display.
Field Description
Default domain Default domain name to be used to complete
unqualified names if no domain list is defined.
Field Description
Address(es) IP address of the host. One host may have up to
eight addresses.
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}
Release Modification
12.2(33)SXI This command was integrated into a release earlier
than Cisco IOS Release 12.2(33)SXI.
Usage Guidelines Use the show htmlcommand to display module and port information.
Examples The following is sample output from the show html command using the port and nameskeywords. The
field descriptions are self-explanatory.
The following is sample output from the show html command using the port, all, and optionskeywords.
The ouput is self-explanatory.
<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
Examples The following is sample output from the show idb command:
The table below describes the significant fields shown in the display.
Field Description
In use Total number of software IDBs (SWIDBs) that
have been allocated. This number never decreases.
SWIDBs are never deallocated.
Field Description
Active Total number of hardware IDBs (HWIDBs) and
SWIDBs that are allocated and in use.
show idprom
To display the identification programmable read-only memory (IDPROM) information for field-
replaceable units (FRUs), use the show idprom command in privileged EXEC mode.
Syntax Description all Displays the information for all FRU types.
• 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.
• To specify WAN Gigabit Ethernet interfaces, use the show idprom transceiverslot/
subslotGigabitEthernetWAN form of the command.
Examples This example shows how to display IDPROM information for clock 1:
Router#
show idprom clock 1
IDPROM for clock #1
(FRU is 'Clock FRU')
OEM String = 'Cisco Systems'
Product Number = 'WS-C6000-CL'
Serial Number = 'SMT03073115'
Manufacturing Assembly Number = '73-3047-04'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 1.0
Current supplied (+) or consumed (-) = 0.000A
The following table describes the significant fields shown in the display.
Field Description
FRU is Indicates the type of the field-replacement unit
(FRU) to which the information that follows
applies.
Field Description
OEM String Names the original equipment manufacturer
(OEM).
Current supplied (+) or consumed (-) Indicated the amount of electrical current that the
device supples or uses.
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 ..............Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 2C 20 49 6E 63 sco Systems, Inc
20: 2E 00 57 53 2D 43 41 43 2D 31 33 30 30 57 00 00 ..WS-CAC-1300W..
30: 00 00 00 00 00 00 41 43 50 30 33 30 32 30 30 30 ......ACP0302000
40: 31 00 00 00 00 00 00 00 00 00 33 34 2D 30 39 31 1.........34-091
50: 38 2D 30 31 00 00 00 00 00 00 41 30 00 00 00 00 8-01......A0....
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
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:
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:
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:
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:
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.
Usage Guidelines 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.
Field Description
NAME Physical name (text string) assigned to the Cisco
entity. For example, console or a simple component
number (port or module number), such as “1,”
depending on the physical component naming
syntax of the device.
Field Description
PID Entity product identifier. Equivalent to the
entPhysicalModelName MIB variable in RFC 2737.
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.
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.
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.
Command Description
show tech-support Displays general information about the router when
it reports a problem.
show location
To display the location information for an endpoint, use the show location command in user EXEC or
privileged EXEC mode.
interface type number Specifies the interface type and interface number.
Examples The following sample output from the show location civic-location command displays all the civic
location information for a specific identifier:
City : Milpitas
State : California
Ports : Gi1/0/10
The following sample output from the show location custom-location command displays custom location
information of a host device:
The following table describes the significant fields shown in the display.
Field Description
Identifier Information identifier of the civic location, custom
location, and geo-spatial location.
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.
Release Modification
12.2(25)S This command was integrated into Cisco IOS
Release 12.2(25)S.
Usage Guidelines 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:
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.
The table below describes the significant fields shown in the output for the two preceding examples.
Field Description
Syslog logging: Shows general state of system logging (enabled or
disabled), the status of logged messages (number of
messages dropped, rate-limited, or flushed), and
whether XML formatting or ESM filtering is
enabled.
Field Description
Console logging: Logging to the console port. Shows “disabled” or, if
enabled, the severity level limit, number of
messages logged, and whether XML formatting or
ESM filtering is enabled.
Corresponds to the configuration of the logging
console, logging console xml, or logging console
filtered command.
Logging Exception size (8192 bytes) Corresponds to the configuration of the logging
exception command.
Count and timestamp logging messages: Corresponds to the configuration of the logging
count command.
Field Description
No active filter modules. Appears if no syslog filter modules are configured
with the logging filter command.
Syslog filter modules are Tcl script files used when
the Embedded Syslog Manager (ESM) is enabled.
ESM is enabled when any of the filtered keywords
are used in the logging commands.
If configured, the URL and filename of configured
syslog filter modules will appear at this position in
the output. Syslog filter modules are executed in the
order in which they appear here.
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.
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.
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.
The table below describes the logging level fields shown in the display.
Field Description
SLOT Indicates the slot number of the line card. An
asterisk next to the slot number indicates the GRP
card whose error message counts are not displayed.
For information on the GRP card, use the show
logging command.
Field Description
ALERT Indicates that immediate action is needed.
show logging xml Displays the state of system logging and the
contents of the XML-specific logging buffer.
Usage Guidelines 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 show-
timezone 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:
The table below describes the significant fields shown in the display.
Field Description
Facility The facility, such as syslog, from which these error
messages are occurring.
Last Time The last (most recent) time this message occurred.
Timestamping is by default based on the system
uptime (for example “3w1d” indicates 3 weeks and
1 day from the last system reboot.)
Sys Total / Lineproto Total / Link Total / SNMP Total number of error messages that have occurred
Total for the specified Facility.
Command Description
service timestamps Configures the system to time-stamp debugging or
logging messages.
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.
The table below describes the significant fields shown in the output.
Field Description
maximum table entry Number of messages that can be stored in the
history table. Set with the logging history size
command.
saving level notifications <x> or higher Level of messages that are stored in the history
table and sent to the SNMP server (if SNMP
notification is enabled). The severity level can be
configured with the logging history command.
table entries flushed Number of messages that have been removed from
the history table to make room for newer messages.
logging history size Changes the number of syslog messages that can be
stored in the history table.
Command Description
logging linecard Logs messages to an internal buffer on a line card.
This command limits the logging messages
displayed on terminal lines other than the console
line to messages with a level at or above level.
snmp-server enable traps The [no] snmp-server enable traps syslog form of
this command controls (enables or disables) the
sending of system-logging messages to a network
management station.
Syntax Description disk (Optional) Displays SEA log disk, where the logs
will be stored.
Usage Guidelines The show logging systemcommand displays the latest messages first.
Examples The following example shows a sample output of the show logging system command that displays the
specified number of latest system log messages:
Field Description
MOD/SUB Module or the submodule that generated the log
message.
The following example shows a sample output of the show logging system command that displays SEA
logs from the specified file location:
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 clear logging system Clears the event records stored in the SEA.
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.
The table below describes the significant fields shown in the displays.
show logging history Displays the contents of the SNMP syslog history
table.
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 XE Release 3.1.0.SG The show memory stand-alone command was
introduced on the Cisco Catalyst 4500e Serfies
Switches. The command functions as shown in the
show memory, page 996 examples.
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:
• show memory, page 996
• show memory, page 996
• show memory, page 996
The following is sample output from the show memory free command:
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.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
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.
Field Description
Address Hexadecimal address of block.
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:
The following sample output displays details of a memory block overflow correction when the exception
memory ignore overflow global configuration command is configured:
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:
The following sample output from the show memory command used on the Cisco 4000 router includes
information about SRAM memory and I/O memory:
The show memory summary command displays a summary of all memory pools and memory usage per
Alloc PC (address of the system call that allocated the block).
The following is a partial sample output from the show memory summary command. This output shows
the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the
other fields, see the tables above.
Cisco IOS XE
The following is sample output from the show memory command when a Cisco IOS XE image is running.
#show memory
System memory : 1943928K total, 735007K used, 1208921K free, 153224K kernel reserved
Lowest(b) : 641880064
Total(K) Used(K) Free(K)
Process 1141112 514129 626984
Config 802816 220879 581937
The table below describes the significant fields shown in the display.
Field Description
total Total amount of memory on the device, in
kilobytes.
The table below describes the significant fields shown in the display.
Field Description
total Total amount of memory on the device, in
kilobytes.
show memory detailed Displays POSIX and Cisco IOS style system
memory information.
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:
The table below describes the significant fields shown in the display.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
The following is sample output from the show memory allocating-process totalscommand:
The table below describes the significant fields shown in the display.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
PC Program counter
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:
Processor memory
The table below describes the significant fields shown in the display.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
Syntax Description allocations Displays all memory blocks that were allocated
after issuing the set memory debug incremental
starting-time command.
Usage Guidelines 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 CLI’s will have high CPU utilization and might
result in time sensitive protocols to flap. These CLI’s 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:
I/O memory
Alloc PC Size Blocks Bytes What
Processor memory
Alloc PC Size Blocks Bytes What
0x60874198 0000000052 0000000001 0000000052 Exec
0x60874198 0000000060 0000000001 0000000060 Exec
0x60874198 0000000100 0000000001 0000000100 Exec
0x60874228 0000000052 0000000004 0000000208 Exec
0x60874228 0000000060 0000000002 0000000120 Exec
0x60874228 0000000100 0000000004 0000000400 Exec
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches to display per-
process memory leak ammounts.
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.
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 CLI’s will have high CPU utilization and might
result in time sensitive protocols to flap. These CLI’s 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.
Examples 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:
• show memory debug leaks, page 1011
• show memory debug leaks, page 1011
Field Description
Address Hexadecimal address of the leaked block.
Field Description
Address Hexadecimal address of the leaked block.
60C656AC 288
60C67D74 48
605B7E98 40
605B7EDC 40
60C659D4 40
605B7E70 32
605B7EB4 32
60616750 24
The table below describes the significant fields shown in the display.
Field Description
Alloc_pc Address of the system call that allocated the block.
The table below describes the significant fields shown in the display.
Field Description
Leak Size of the leaked block.
show memory debug incremental allocation Displays all memory blocks that were allocated
after the issue of the set memory debug
incremental starting-time command.
show memory debug incremental leaks Displays only memory that was leaked after the
issue of the set memory debug incremental
starting-time command.
show memory debug incremental leaks lowmem Forces incremental memory leak detection to work
in low memory mode. Displays only memory that
was leaked after the issue of the set memory debug
incremental starting-time command.
show memory debug incremental status Displays if the starting point of incremental
analysis has been defined and the time elapsed
since then.
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 CLI’s will have high CPU utilization and might
result in time sensitive protocols to flap. These CLI’s 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:
The following is sample output from the show memory debug references danglingcommand:
The table below describes the significant fields shown in the displays.
Field Description
Address Hexadecimal address of the block having the given
or dangling reference.
Examples The following is sample output from the show memory debug unusedcommand:
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
Command Default No detailed memory information about POSIX and Cisco IOS processes is displayed.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches.
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:
• show memory detailed, page 1021
• show memory detailed, page 1021
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.
Field Description
total Total amount of memory on the device, in
kilobytes.
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.
Field Description
Process Process name and path.
heapsize Size of the process heap. Note that the Cisco IOS
memory management library allocates heap
dynamically. This is shown in the Cisco IOS
memory details that follow the POSIX memory
display.
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.
Field Description
Address Hexadecimal address of block.
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.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
Field Description
what Type of memory segment that owns the block, or
“(fragment)” if the block is a fragment, or
“(coalesced)” if the block was coalesced from
adjacent free blocks.
The following is sample output from the show memory detailedcommand for a POSIX process:
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:
The table below describes the significant fields shown in the display.
Field Description
Shared Amount of memory shared by the specified process,
in kilobytes.
Field Description
MapFlags Represents special mapping properties used for the
memory.
Note Field descriptions are the same as those in the show memory detailed, page 1021 example.
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:
The table below describes the significant fields shown in the first section of the display.
Field Description
Occured n time(s) Number of single-bit errors that has occurred.
Whether a scrub was attempted at this address: Indicates whether a scrub has been performed.
Syndrome of the last error at this address: Describes the syndrome of last error.
Address media classification : Describes the media of the error and correction.
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 following is sample output from the show memory eventscommand:
The table below describes the significant fields shown in the display.
Field Description
When Time when the memory event was last seen by the
system (in hours and days).
Field Description
Type Allocation type.
The following is sample output from the show memory eventscommand using the outstanding and
summarykeywords:
The table below describes the significant fields shown in the display.
Field Description
Last-Seen Time when the memory event was last seen by the
system (in hours and days).
Examples The following is sample output from the show memory failures alloc command:
The table below describes the significant fields shown in the display.
Field Description
Caller Address of the allocator function that issued
memory allocation request that failed.
Field Description
When Time of day at which the memory allocation
request was issued.
Usage Guidelines 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.
Note 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:
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
8404A580 0001493284 00000000 841B6ECC 000 0 84BADF88 815219D8 (coalesced)
841B6ECC 0000020004 8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk
Queue Elements
841BBD18 0000001504 841B6ECC 841BC320 001 -------- -------- 8159EAC4 List Elements
841BC320 0000005004 841BBD18 841BD6D4 001 -------- -------- 8159EB04 List Headers
841BD6D4 0000000048 841BC320 841BD72C 001 -------- -------- 81F2A614 *Init*
841BD72C 0000001504 841BD6D4 841BDD34 001 -------- -------- 815A9514 messages
841BDD34 0000001504 841BD72C 841BE33C 001 -------- -------- 815A9540 Watched messages
841BE33C 0000001504 841BDD34 841BE944 001 -------- -------- 815A95E4 Watched Semaphore
841BE944 0000000504 841BE33C 841BEB64 001 -------- -------- 815A9630 Watched Message
Queue
841BEB64 0000001504 841BE944 841BF16C 001 -------- -------- 815A9658 Watcher Message
Queue
841BF16C 0000001036 841BEB64 841BF5A0 001 -------- -------- 815A2B24 Process Array
-- More --
<Ctrl+z>
Router>show memory processor
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
8404A580 0001493284 00000000 841B6ECC 000 0 84BADF88 815219D8 (coalesced)
841B6ECC 0000020004 8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk
Queue Elements
841BBD18 0000001504 841B6ECC 841BC320 001 -------- -------- 8159EAC4 List Elements
841BC320 0000005004 841BBD18 841BD6D4 001 -------- -------- 8159EB04 List Headers
841BD6D4 0000000048 841BC320 841BD72C 001 -------- -------- 81F2A614 *Init*
841BD72C 0000001504 841BD6D4 841BDD34 001 -------- -------- 815A9514 messages
841BDD34 0000001504 841BD72C 841BE33C 001 -------- -------- 815A9540 Watched messages
841BE33C 0000001504 841BDD34 841BE944 001 -------- -------- 815A95E4 Watched Semaphore
841BE944 0000000504 841BE33C 841BEB64 001 -------- -------- 815A9630 Watched Message
Queue
841BEB64 0000001504 841BE944 841BF16C 001 -------- -------- 815A9658 Watcher Message
Queue
841BF16C 0000001036 841BEB64 841BF5A0 001 -------- -------- 815A2B24 Process Array
-- More --
<Ctrl+z>
Router>
The following example shows sample output from the show memory fast allocating-process command,
followed by sample output from the show memory fast allocating-process totals command:
Processor memory
Address Bytes Prev Next Ref Alloc Proc Alloc PC What
8404A580 0001493284 00000000 841B6ECC 000 815219D8 (coalesced)
841B6ECC 0000020004 8404A580 841BBD18 001 *Init* 815DB094 Managed Chunk Queue
Elements
841BBD18 0000001504 841B6ECC 841BC320 001 *Init* 8159EAC4 List Elements
841BC320 0000005004 841BBD18 841BD6D4 001 *Init* 8159EB04 List Headers
841BD6D4 0000000048 841BC320 841BD72C 001 *Init* 81F2A614 *Init*
841BD72C 0000001504 841BD6D4 841BDD34 001 *Init* 815A9514 messages
841BDD34 0000001504 841BD72C 841BE33C 001 *Init* 815A9540 Watched messages
841BE33C 0000001504 841BDD34 841BE944 001 *Init* 815A95E4 Watched Semaphore
841BE944 0000000504 841BE33C 841BEB64 001 *Init* 815A9630 Watched Message Queue
841BEB64 0000001504 841BE944 841BF16C 001 *Init* 815A9658 Watcher Message Queue
841BF16C 0000001036 841BEB64 841BF5A0 001 *Init* 815A2B24 Process Array
--More--
<Ctrl+z>
c2600-1#show memory fast allocating-process totals
The following example shows sample output from the show memory fast dead command:
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
8498FC20 0000000028 8498FB90 8498FC64 001 -------- -------- 81472B24 AAA MI SG NAME
-------
68
Router#show memory fast dead totals
Examples The following is sample output from the show memory processor fragment command:
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
The following is sample output from the show memory processor fragment detailcommand:
Processor memory
Free memory size : 65566148 Number of free blocks: 230
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
645A8148 0000000028 645A80F0 645A8194 001 -------- -------- 60695B20 Init
645A8194 0000000040 645A8148 645A81EC 000 0 200B4300 606B9614 NameDB String
645A81EC 0000000260 645A8194 645A8320 001 -------- -------- 607C2D20 Init
200B42B4 0000000028 200B4268 200B4300 001 -------- -------- 62366C80 Init
200B4300 0000000028 200B42B4 200B434C 000 645A8194 6490F7E8 60976574 AAA Event Data
200B434C 0000002004 200B4300 200B4B50 001 -------- -------- 6267D294 Coproc Request
Structures
6490F79C 0000000028 6490F748 6490F7E8 001 -------- -------- 606DDA04 Parser Linkage
6490F7E8 0000000028 6490F79C 6490F834 000 200B4300 6491120C 606DD8D8 Init
6490F834 0000006004 6490F7E8 64910FD8 001 -------- -------- 607DF5BC Process Stack
649111A0 0000000060 64911154 6491120C 001 -------- -------- 606DE82C Parser Mode
6491120C 0000000028 649111A0 64911258 000 6490F7E8 500770F0 606DD8D8 Init
64911258 0000000200 6491120C 64911350 001 -------- -------- 603F0E38 Init
.
.
.
504DCF54 0000001212 504DB2E4 504DD440 001 -------- -------- 60962DFC TCP CB
2C41DCA4 0000000692 2C41BCC8 2C41DF88 001 -------- -------- 60D509BC Virtual Exec
2C41DF88 0000005344 2C41DCA4 2C41F498 000 504DB2E4 6449A828 60D509BC (coalesced)
2C41F498 0000000692 2C41DF88 2C41F77C 001 -------- -------- 60D509BC Virtual Exec
6449A544 0000000692 64499794 6449A828 001 -------- -------- 60D509BC Virtual Exec
6449A828 0000007760 6449A544 6449C6A8 000 2C41DF88 504D89D4 60D509BC (coalesced)
6449C6A8 0000008044 6449A828 6449E644 001 -------- -------- 60D2AACC Virtual Exec
504D8778 0000000556 504D754C 504D89D4 001 -------- -------- 60D4A0B4 Virtual Exec
504D89D4 0000009860 504D8778 504DB088 000 6449A828 504D1B78 60D4A0B4 (coalesced)
504DB088 0000000556 504D89D4 504DB2E4 001 -------- -------- 60D4A0B4 Virtual Exec
504D168C 0000001212 504C9658 504D1B78 001 -------- -------- 60962DFC TCP CB
504D1B78 0000008328 504D168C 504D3C30 000 504D89D4 504C5B54 60962DFC (coalesced)
504D3C30 0000001212 504D1B78 504D411C 001 -------- -------- 60962DFC TCP CB
504C5870 0000000692 504C5504 504C5B54 001 -------- -------- 60D509BC Virtual Exec
504C5B54 0000005344 504C5870 504C7064 000 504D1B78 2C423A88 60D509BC (coalesced)
504C7064 0000000408 504C5B54 504C722C 001 -------- -------- 606E0E44 Chain Cache No
2C42359C 0000001212 2C41F77C 2C423A88 001 -------- -------- 60962DFC TCP CB
2C423A88 0000008328 2C42359C 2C425B40 000 504C5B54 504D411C 60962DFC (coalesced)
504E7DD8 0000000828 504E2660 504E8144 001 -------- -------- 60734010 *Packet Header*
65006A08 0000000408 65003834 65006BD0 001 -------- -------- 606E0E44 Chain Cache No
65006BD0 0000020520 65006A08 6500BC28 000 504E2660 0 60803260 (coalesced)
6500BC28 0000000828 65006BD0 6500BF94 001 -------- -------- 60734010 *Packet Header*
5C3AE7B8 0000000828 5C3AE614 5C3AEB24 001 -------- -------- 60734010 *Packet Header*
5C3AEB24 0063247532 5C3AE7B8 20000000 000 0 6500C300 60734010 (coalesced)
20000000 0000000828 5C3AEB24 2000036C 001 -------- -------- 60734010 *Packet Header*
6500BF94 0000000828 6500BC28 6500C300 001 -------- -------- 60734010 *Packet Header*
6500C300 0004760912 6500BF94 50000000 000 5C3AEB24 2C42E310 6071253C (coalesced)
50000000 0000000828 6500C300 5000036C 001 -------- -------- 60734010 *Packet Header*
2C42E0B4 0000000556 2C429430 2C42E310 001 -------- -------- 60D4A0B4 Virtual Exec
2C42E310 0062725312 2C42E0B4 00000000 000 6500C300 0 6071253C (coalesced
Syntax Description pool Displays malloc lite allocation information for all
or a specific pool.
Examples The following is sample output from the show memory lite-chunks command:
8 bytes pool
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
Examples The following is sample output from the show memory multibus command:
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
Examples The following is sample output from the show memory pci command:
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
Field Description
Next Address of the following block (should match the
address on the following line).
Examples The following is sample output from the show memory processorcommand:
Router# show memory processor
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes
6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes
65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes
65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k
654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k
6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)
65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s
654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles
654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas
654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
The following is sample output from the show memory processor allocating-processcommand:
The following is sample output from the show memory processor deadcommand:
The following is sample output from the show memory processor fragmentcommand:
The table below describes the significant fields shown in the display.
Field Description
PC Program counter.
The following is sample output from the show memory processor freecommand:
24 Free list 1
66994680 0000000072 66994618 669946FC 000 0 6698FFC8 60699114 Turbo ACr
6698FFC8 0000000072 6698FF60 66990044 000 66994680 659CF6B0 60699114 Turbo ACr
659CF6B0 0000000024 659CF678 659CF6FC 000 6698FFC8 659CF86C 6078A2CC Init
659CF86C 0000000024 659CF710 659CF8B8 000 659CF6B0 65ADB53C 6078A2CC Init
65ADB53C 0000000024 65ADB504 65ADB588 000 659CF86C 65ADFC38 6078A2CC Init
65ADFC38 0000000024 65ADFC00 65ADFC84 000 65ADB53C 65B6C504 6078A2CC Init
65B6C504 0000000024 65B6C4B8 65B6C550 000 65ADFC38 6593E924 6078A2CC Init
6593E924 0000000028 6593E8E8 6593E974 000 65B6C504 65CCB054 6078A2CC Init
65CCB054 0000000024 65CCB01C 65CCB0A0 000 6593E924 65CCBD98 6078A2CC Init
65CCBD98 0000000028 65CCBD60 65CCBDE8 000 65CCB054 65CCFB70 6078A2CC Init
65CCFB70 0000000024 65CCFB38 65CCFBBC 000 65CCBD98 65D0BB58 6078A2CC Init
65D0BB58 0000000024 65D0BB20 65D0BBA4 000 65CCFB70 65D0C5F0 6078A2CC Init
65D0C5F0 0000000024 65D0C5B8 65D0C63C 000 65D0BB58 65CFF2F4 6078A2CC Init
65CFF2F4 0000000024 65CFF2BC 65CFF340 000 65D0C5F0 6609B7B8 6078A2CC Init
6609B7B8 0000000036 6609AFC8 6609B810 000 65CFF2F4 660A0BD4 6078A2CC Init
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
The following is sample output from the show memory processor statisticscommand:
The table below describes the significant fields shown in the display.
Field Description
Head Hexadecimal address of the head of the memory
allocation chain.
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:
The table below describes the fields contained in the error report.
Field Description
Address The byte address where the error occurred.
Field Description
BlckSize The size of the memory block
Examples The following is sample output from the show memory statistics history table command. The field
descriptions are self-explanatory.
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
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:
The following is sample output from the show memory traceback command using the exclusivekeyword:
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
show memory transient [allocating-process [totals] | dead [totals] | fragment [detail] | free
[totals] | statistics [history]]
Examples The following is sample output from the show memory transientcommand:
The table below describes the significant fields shown in the display.
Field Description
Address Hexadecimal address of the block.
show microcode
To display microcode image information available on line cards, use the show microcode command in
EXEC mode.
show microcode
Examples The following is sample output from the show microcode command:
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.
Syntax Description module num (Optional) Displays the MLS statistics for a specific
module.
Usage Guidelines 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 : 20273@ 22552 pps
L3 Forwarding Engine
Total Packets Bridged : 20273
Total Packets FIB Switched : 7864
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 220598
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 705757744
Statistics for Earl in Module 9
L2 Forwarding Engine
Total packets Switched : 16683@ 1 pps
L3 Forwarding Engine
Total Packets Bridged : 0
Total Packets FIB Switched : 0
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 0
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 277949053
Router#
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 : 2748166@ 22332 pps
>>
L3 Forwarding Engine
Total Packets Bridged : 92750@ 34 pps
Total Packets FIB Switched : 7
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 3079200
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 0
Total Unicast RPF failed packets : 0
Errors
MAC/IP length inconsistencies : 0
Short IP packets received : 0
IP header checksum errors : 0
MAC/IPX length inconsistencies : 0
Short IPX packets received : 0
Router
#
show module
To display the module status and information, use the show module command in user EXEC or privileged
EXEC mode.
Usage Guidelines In the Mod Sub-Module fields, the show module command displays the supervisor engine number but
appends the uplink daughter card’s 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
Router#
show module 2
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD0644030K
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
5 00e0.aabb.cc00 to 00e0.aabb.cc3f 1.0 12.2(2003012 12.2(2003012 Ok
Mod Sub-Module Model Serial Hw Status
--- --------------------------- --------------- --------------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3 SAD0644031P 0.302 Ok
5 MSFC3 Daughtercard WS-SUP720 SAD06460172 0.701
Mod Online Diag Status
--- -------------------
5 Not Available
Router#
This example shows how to display version information:
Router#
show module version
show environment status Displays the information about the operational FRU
status.
show monitor event-trace [all-traces] component {all | back hour:minute | clock hour:minute |
from-boot seconds | latest | parameters}
back mmm | hhh:mm} Specifies how far back from the current time you
want to view messages. For example, you can
gather messages from the last 30 minutes. The time
argument is specified either in minutes or in hours
and minutes format (mmm or hh:mm).
12.4(4)T Support for the bfd keyword was added for Cisco
IOS Release 12.4(4)T.
12.0(31)S Support for the bfd keyword was added for Cisco
IOS Release 12.0(31)S.
Release Modification
12.2(33)SB This command was integrated into Cisco IOS
Release 12.2(33)SB.
Usage Guidelines 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.
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:
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.
Note If no packets have been dropped, this command does not display any output.
monitor event-trace (global) Configures event tracing for a specified Cisco IOS
software subsystem component.
monitor event-trace dump-traces Saves trace messages for all event traces currently
enabled on the networking device.
Examples This example shows how to display the permit-list state and interfaces configured:
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:
This example shows how to display the detailed information from a saved version of the monitor
configuration for a specific session:
Session 2
---------
Type : ERSPAN Destination Session
Status : Admin
Disabled
Router#
This example shows how to display detailed information about the destination ERSPAN sessions only:
Session 2
---------
Type : ERSPAN Destination Session
Status : Admin Disabled
Description : -
Source Ports :
RX Only : None
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
Destination RSPAN VLAN : None
Source IP Address : None
Source IP VRF : None
Source ERSPAN ID : None
Destination IP Address : None
Destination IP VRF : None
Session 1
---------
Type : ERSPAN Source Session
Status : Admin
Disabled
Session
3
---------
Type : ERSPAN Source Session
Status : Admin
Disabled
Router#
This example shows how to display detailed information about the source ERSPAN sessions only:
Session 1
---------
Type : ERSPAN Source Session
Status : Admin Disabled
Description : -
Source Ports :
RX Only : None
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
Destination RSPAN VLAN : None
Source IP Address : None
Source IP VRF : None
Source ERSPAN ID : None
Destination IP Address : None
Destination IP VRF : None
Destination ERSPAN ID : None
Origin IP Address : None
IP QOS PREC : 0
IP TTL : 255
Session 3
---------
Type : ERSPAN Source Session
Status : Admin Disabled
Description : -
Source Ports :
RX Only : None
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
Destination RSPAN VLAN : None
Source IP Address : None
Source IP VRF : None
Source ERSPAN ID : None
This example shows how to display the operational mode and configured mode of the session and module
session capabilities:
show msfc
To display Multilayer Switching Feature Card (MSFC) information, use the show msfc command in user
EXEC or privileged EXEC mode.
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 (senso
r not present)
sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (senso
r not present)
sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (senso
r not present)
sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (senso
r not present)
*** end of linecard specific block ***
End of IDPROM image
Router#
Router# show msfc fault
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
show environment status Displays the information about the operational FRU
status.
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}
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:
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.
Usage Guidelines 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.
Caution 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:
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.
In the following example, only commands in RTR configuration mode are shown:
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:
The following example shows how the extend keyword displays the syntax descriptions that match those
shown using the ? command-line help:
In the following example, show parser dump output is redirected to a file on a remote TFTP server:
show include Filters show command output so that only lines that
containing the specified string are displayed.
Examples The following example shows how to display the macro description:
The following example shows how to list the Cisco-provided smart port macros:
Usage Guidelines The show parser statistics command displays two sets of data:
• 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:
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.
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.
Usage Guidelines The output of this command is generally useful for diagnostic tasks performed by technical support only.
Note The show pci hardware EXEC command displays a substantial amount of information.
Examples The following is sample output for the PCI bridge register 1 on a Cisco 7200 series router:
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:
Usage Guidelines The output of this command is generally useful for diagnostic tasks performed by technical support only:
Examples The following is partial sample output for the PCI hardware register, which also includes information on all
the PCI bridge registers.
The table below describes the significant fields shown in the display.
Field Description
Device/Vendor ID Identifies the PCI vendor and device. The value
0x401310EE identifies the device as the Xilinx-
based Host-PCI bridge for the Cisco 2600 router.
PCI Slave Base Reg 0 The base address of PCI Target Region 0 for the
Host-PCI bridge. This region is used for Big-
Endian transfers between PCI devices and memory.
PCI Slave Base Reg 1 The base address of PCI Target Region 1 for the
Host-PCI bridge. This region is used for Little-
Endian transfers between PCI devices and memory.
show perf-meas
To display the performance measurement of the router, use the show perf-meascommand in user EXEC or
privileged EXEC mode.
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 self-
explanatory.
-------------------------------------------------------------------------------|
| 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}
hardware pfc mode Displays the type of installed Policy Feature Card
(PFC).
software ipv6-multicast connected Displays all the IPv6 subnet Access Control List
(ACL) entries on the Route Processor (RP); see the
show platform software ipv6-multicast command.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
Examples The following sample output from the show platform buffers command displays buffer-allocation
information:
Threshold = 8192
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.
The table below describes the significant fields shown in the display.
Field Description
Slot Chassis slot.
Field Description
State Online state of the hardware. One of the following
values:
All Hardware
• booting--Hardware is initializing and software
is booting.
• disabled--Hardware is not operational.
• init--Hardware or Cisco IOS process is
initializing.
• ok--Hardware is operational.
• shutdown--Hardware was administratively shut
down using the no shutdown command.
• unknown--Hardware is not operational; state is
unknown.
RP or ESP
• init, standby--Standby RP or ESP is
operational but is not yet in a high availability
(HA) state. An RP or ESP switchover is not
yet possible.
• ok, active--Active RP or ESP is operational.
• ok, standby--Standby RP or ESP is
operational. The standby RP or ESP is ready to
become active in the event of a switchover.
SPA
• admin down--SPA was disabled using the
shutdown command.
• inserted--SPA is being inserted.
• missing--SPA was removed.
• out of service--SPA is not operational.
• retrieval error--An error occurred while
retrieving the SPA state; state is unknown.
• stopped--SPA was gracefully deactivated using
the hw-module subslot stop command.
Fan or Power Supply
• fan, fail--Fan is failing.
• ps, fail--Power supply is failing.
Field Description
Rate Limiter Status Indicates if a rate limiter has been enabled on the
interface.
Per Interface Rate Limiter Information Displays the list of interfaces on which the rate
limiter is active. In this example:
• GigabitEthernet5/1.1 is free from attack.
• GigabitEthernet5/2.1 has an exceed count of 4,
and has a rate limiter enabled. The observation
period is 35 minutes, which indicates that
currently the interface is free from attack and
is being kept under observation. The interface
will remain under observation for an additional
35 minutes. If it remains free from attack after
that time, the rate limiter is automatically
removed.
• GigabitEthernet5/2.2 has an exceed count of
16 and has a rate limiter enabled. The
observation period has been designated as
Max. This indicates that the interface is still
under attack and has not yet entered the
observation time window.
The following sample from the show platform eeprom command displays CPU EEPROM information:
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)
sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
max_connector_power = 1650
cooling_requirement = 70
ambient_temp = 55
*** end of linecard specific block ***
The following sample output from the show platform fault command displays fault-date information:
This example shows how use the atom ether-vc keyword to display line-card information for an ES20 line
card in slot 3.
platform copp observation period Sets the observation period before automatically
turning off the per-interface rate limiter on the
Cisco 7600 SIP-400.
Examples The following is sample output from the show platform bridgecommand:
The table below describes the significant fields shown in the display.
Field Description
VLAN The VLAN for which bridging is configured.
show platform cfm {epl | info | interface {fastethernet | gigabitethernet | port-channel} number
{fwd_vlan vlan-number | level | vlan_list}}
Syntax Description epl Displays CFM Ethernet private line (EPL) details.
Examples The following is sample output from the show platform cfm infocommand. The field descriptions are self-
explanatory.
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.
Syntax Description diag Displays diagnostic and debug information for the
platform components.
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
The table below describes the significant fields shown in the display.
Field Description
Running state The current online running state of the FRU
component.
Internal state The internal debug state of the FRU component for
diagnostic purposes.
Physical insert detect time The time of the most recent physical insertion of
the FRU component detected by the platform code.
Software declared up time The time that the software on the FRU component
was declared running by the platform code.
Hardware ready signal time The time that the hardware ready signal was
detected by the platform code.
Field Description
Packet ready signal time The time that the Embedded Service Processor
(ESP) packet ready signal was detected by the
platform code.
Logical insert detect time The time that the SPA was logically detected by the
platform code.
Became HA Active time The time that this FRU became High Availability
(HA) active status.
Syntax Description resource-type (Optional) Hardware resource type; see the “Usage
Guidelines” section for the valid values.
• 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 1-
minute average busy time, and the percentage of the last 5-minute average busy time.
• Processor memory total available bytes, used bytes, and percentage used.
• I/O memory total available bytes, used bytes, and percentage used.
The show platform hardware capacity eobccommand displays the following information:
• Transmit and receive rate
• Packets received and packets sent
• Dropped received packets and dropped transmitted packets
The show platform hardware capacity forwarding command displays the following information:
• The total available entries, used entries, and used percentage for the MAC tables.
• The total available entries, used entries, and used percentage for the FIB TCAM tables. The display is
done per protocol base.
• The total available entries, used entries, and used percentage for the adjacency tables. The display is
done for each region in which the adjacency table is divided.
• The created entries, failures, and resource usage percentage for the NetFlow TCAM and ICAM tables.
• The total available entries and mask, used entries and mask, reserved entries and mask, and entries and
mask used percentage for the ACL/QoS TCAM tables. The output displays the available, used,
reserved, and used percentage of the labels. The output displays the resource of other hardware
resources that are related to the ACL/QoS TCAMs (such as available, used, reserved, and used
percentage of the LOU, ANDOR, and ORAND).
• The available, used, reserved, and used percentage for the CPU rate limiters.
The show platform hardware capacity interface command displays the following information:
• Tx/Rx drops--Displays the sum of transmit and receive drop counters on each online module
(aggregate for all ports) and provides the port number that has the highest drop count on the module.
• Tx/Rx per port buffer size--Summarizes the port-buffer size on a per-module basis for modules where
there is a consistent buffer size across the module.
The show platform hardware capacity monitor command displays the following SPAN information:
• The maximum local SPAN sessions, maximum RSPAN sessions, maximum ERSPAN sessions, and
maximum service module sessions.
• The local SPAN sessions used/available, RSPAN sessions used/available, ERSPAN sessions used/
available, and service module sessions used/available.
The show platform hardware capacity multicast command displays the following information:
• Multicast Replication Mode: ingress and egress IPv4 and IPv6 modes.
• The MET table usage that indicates the total used and the percentage used for each module in the
system.
• The bidirectional PIM DF table usage that indicates the total used and the percentage used.
The show platform hardware capacity 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:
◦ Part number (WS-SUP720-BASE, WS-X6548-RJ-45, and so forth)
◦ Series (supervisor engine, fabric, CEF720, CEF256, dCEF256, or classic)
◦ CEF Mode (central CEF, dCEF)
The show platform hardware capacity vlan command displays the following VLAN information:
• Total VLANs
• VTP VLANs that are used
• External VLANs that are used
• Internal VLANs that are used
• Free VLANs
Examples 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:
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:
This example shows how to display the current and peak switching utilization:
Key: ACLent - ACL TCAM entries, ACLmsk - ACL TCAM masks, AND - ANDOR,
QoSent - QoS TCAM entries, QOSmsk - QoS TCAM masks, OR - ORAND,
Lbl-in - ingress label, Lbl-eg - egress label, LOUsrc - LOU source,
LOUdst - LOU destination, ADJ - ACL adjacency
Module ACLent ACLmsk QoSent QoSmsk Lbl-in Lbl-eg LOUsrc LOUdst AND OR ADJ
6 1% 1% 1% 1% 1% 1% 0% 0% 0% 0% 1%
Router#
This example shows how to display the capacity and utilization of resources for Layer 3 multicast
functionality:
This example shows how to display information about the system power capacities and utilizations:
This example shows how to display the capacity and utilization of QoS policer resources per EARL in the
Cisco 7600 series router:
This example shows how to display information about the key system resources:
show platform hardware capacity rewrite-engine Displays the packet drop and performance counters
of the central rewrite engine on supervisors and line
cards.
show platform isg {memory{detailed} | msi-all | slot | session-count | {slot-number | all} | uid |
{subscriber-session UID | all} | vrf | {vrf-number | all}}
Examples The following is sample output from the show platform isg vrf allcommand. The field descriptions are
self-explanatory.
dbg_stdby_cd_fibobj 35042
dbg_stdby_cd_rem_fibobj 492
dbg_stdby_cd_no_objhdl 1120
dbg_stdby_cd_no_ps 0
dbg_stdby_unpck_vrf_node 1612
dbg_stdby_unpck_pl_hdl 33922
dbg_stdby_unpck_rem_vrf_node 0
interface type number (Optional) Displays the interface name and number.
Examples The following is sample output from the show platform oam link-monitor interface GigabitEthernet
1/1command. The fields are self-explanatory.
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
show platform redundancy {atm | ccb slot-number cpu-number | cwpa-ce3 | cwpa-ct3 | cwpa-e1 |
cwpa-stm1 | cwpa-t1 | frame-relay | hdlc | if-config {slot-number cpu-number [bay-number] |
default-retvals} | mlp | multilink-vc | osm-chocx | osm-ct3 | ppp | shadowstate | spa-chocx | spa-
ct3 | switchover}
Examples The following is sample output from the show platform redundancycommand with the if-config
keyword. The fields are self-explanatory.
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.
The following example displays information only about the bootflash file system itself, such as file system
type and access permissions:
The table below describes the significant fields shown in the displays of file system information.
Field Description
# Display line number.
Field Description
Path Full path of a file in the file system.
Usage Guidelines The specification of the database and brief keywords are optional.
The specification of a process and slot are required.
Examples The following example displays memory information for the Forwarding Manager process for Cisco ASR
1000 Series RP slot 0:
The table below describes the significant fields shown in the display.
Field Description
Module: Name of submodule.
The following example displays abbreviated (brief keyword) memory information for the Chassis Manager
process for Cisco ASR 1000 Series ESP slot 0:
The table below describes the significant fields shown in the brief keyword display.
Field Description
module Name of submodule.
Syntax Description slot (Optional) Displays mounted file systems for the
specified slot. Possible slot values are:
• 0 --Cisco ASR 1000 Series SIP slot 0
• 1 --Cisco ASR 1000 Series SIP slot 1
• 2 --Cisco ASR 1000 Series SIP slot 2
• f0 --Cisco ASR 1000 Series ESP slot 0
• f1 --Cisco ASR 1000 Series ESP slot 1
• fp active --Active Cisco ASR 1000 Series ESP
• fp standby --Standby Cisco ASR 1000 Series
ESP
• r0 --Cisco ASR 1000 Series RP slot 0
• r1 --Cisco ASR 1000 Series RP slot 1
• rp active --Active Cisco ASR 1000 Series RP
• rp standby --Standby Cisco ASR 1000 Series
RP
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:
The following example displays mounted file systems for the Cisco ASR 1000 Series ESP in ESP slot 0:
The following example displays mounted file systems for the active Cisco ASR 1000 Series RP:
Table 138 show platform software mount SIP slot Field Descriptions
Field Description
Filesystem Logical name of the file system device.
The following example displays abbreviated (brief keyword) mounted file system information for Cisco
ASR 1000 Series SIP slot 0:
The tab le below describes the significant fields shown in the brief keyword display.
Field Description
Mount point: Logical name of the file system device.
show platform software process list slot [name process-name | process-id process-id | sort
memory | summary]
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
Field Description
Name Name of the process.
The following example displays information about a specific named process for Cisco ASR 1000 Series
SIP slot 0:
The following example displays information about a specific process identifier for Cisco ASR 1000 Series
SIP slot 0:
Name: init
Process id : 1
Parent process id: 0
Group id : 1
Status : S
Session id : 1
User time : 1
Kernel time : 741
Priority : 20
Virtual bytes : 1974272
Resident pages : 161
Resident limit : 4294967295
Minor page faults: 756
Major page faults: 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 Name of the process.
The following example displays process summary information for Cisco ASR 1000 Series SIP slot 0:
The table below describes the significant fields shown in the summary keyword display.
Table 142 show platform software process list summary Field Descriptions
Field Description
Total number of processes Total number of processes in all possible states.
Field Description
Memory (kB) System memory heading.
Field Description
High Free Amount of free memory (in kilobytes) that is not
directly mapped into kernel space. The High Free
value can vary based on the type of kernel used.
Field Description
1-Min Average number of processes running for the last
minute.
The following example displays process summary information for Cisco ASR 1000 Series sorted by
memory size:
scsi_eh_0 1077 2 0 S 15 0
scsi_eh_1 1079 2 0 S 15 0
scsi_eh_2 1081 2 0 S 15 0
scsi_eh_3 1083 2 0 S 15 0
scsi_eh_4 1115 2 0 S 15 0
usb-storage 1116 2 0 S 15 0
scsi_eh_5 1129 2 0 S 15 0
usb-storage 1130 2 0 S 15 0
scsi_eh_6 1133 2 0 S 15 0
usb-storage 1134 2 0 S 15 0
rpciod/0 2333 2 0 S 15 0
rpciod/1 2336 2 0 S 15 0
nfsiod 2345 2 0 S 15 0
loop0 2424 2 0 S 0 0
loop1 2708 2 0 S 0 0
loop2 2745 2 0 S 0 0
loop3 2782 2 0 S 0 0
loop4 2819 2 0 S 0 0
loop5 2928 2 0 S 0 0
loop6 2965 2 0 S 0 0
loop7 3002 2 0 S 0 0
loop8 3075 2 0 S 0 0
lockd 15741 2 0 S 15 0
nfsd 15742 2 0 S 15 0
nfsd 15743 2 0 S 15 0
nfsd 15744 2 0 S 15 0
nfsd 15745 2 0 S 15 0
nfsd 15746 2 0 S 15 0
nfsd 15747 2 0 S 15 0
nfsd 15748 2 0 S 15 0
nfsd 15749 2 0 S 15 0
lsmpi-refill 15852 2 0 S 15 0
lsmpi-xmit 15853 2 0 S 15 0
lsmpi-rx 15854 2 0 S 15 0
ddr_err_monitor 16267 2 0 S 15 0
mtdblockd 16292 2 0 S 15 0
scansta 16315 2 0 S 15 0
show platform software process slot slot monitor [cycles cycles][interval delay][lines lines-of-
output]
Syntax Description slot Specifies the Field Replace Unit (FRU) where the
command is run.
Examples 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.
Field Description
%CPU CPU Usage
NI Nice value
PID Process ID
PR Priority
S Process status
Field Description
TIME+ Elapsed execution time
Usage Guidelines 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.
bootflash: filename .tgz Creates a technical support information tar file for
the boot flash memory file system on the active RP.
stby-bootflash: filename .tgz Creates a technical support information tar file for
the boot flash memory file system on the standby
RP. The information displayed is for internal
debugging puposes only.
stby-harddisk: filename .tgz Creates a technical support information tar file for
the hard disk file system on the standby RP. The
information displayed is for internal debugging
puposes only.
Usage Guidelines 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:
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:
The following example creates a technical support information tar file for the hard disk file system on the
active RP:
Examples This is sample output from the show platform subscriber-group allcommand:
Examples The following is sample output from the show platform supervisorcommand. The fields are self-
explanatory.
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]
fan-tray fan-tray-number Displays the power status for the fan tray .
Usage Guidelines The interface-number argument designates the module and port number. Valid values for interface-number
depend on the specified interface type and the chassis and module that are used. For example, if you
specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in
a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number
are from 1 to 48.
Valid values for vlan-id are from 1 to 4094.
The Inline power field in the show 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:
Examples This example shows how to display the available system power:
Router>
show power
available
system power available = 20.470A
Router>
Router#
show power
redundancy-mode
system power redundancy mode = redundant
Router#
system power
redundancy mode = combined
system power
total = 3984.12 Watts (94.86 Amps @ 42V)
system power
used = 1104.18 Watts (26.29 Amps @ 42V)
system power
available = 2879.94 Watts (68.57 Amps @ 42V)
Power-Capacity PS-Fan Output Oper
PS Type Watts A @42V Status Status State
---- ------------------ ------- ------ ------ ------ -----
1 WS-CAC-3000W 2830.80 67.40 OK OK on
2 WS-CAC-1300W 1153.32 27.46 OK OK on
Note: PS2 capacity is limited to 2940.00 Watts (70.00 Amps @ 42V)
when PS1 is not present
Pwr-Allocated Oper
Fan Type Watts A @42V State
---- ------------------ ------- ------ -----
1 FAN-MOD-9 241.50 5.75 OK
2 241.50 5.75 failed
Pwr-Requested Pwr-Allocated Admin Oper
Slot Card-Type Watts A @42V Watts A @42V State State
---- ------------------ ------- ------ ------- ------ ----- -----
1 WS-X6K-SUP2-2GE 145.32 3.46 145.32 3.46 on on
2 - - 145.32 3.46 - -
3 WS-X6516-GBIC 118.02 2.81 118.02 2.81 on on
5 WS-C6500-SFM 117.18 2.79 117.18 2.79 on on
7 WS-X6516A-GBIC 214.20 5.10 - - on off (insuff cooling capacity)
8 WS-X6516-GE-TX 178.50 4.25 178.50 4.25 on on
9 WS-X6816-GBIC 733.98 17.48 - - on off (connector rating
exceeded)
Router>
This example shows how to display the power status for all FRU types:
Router#
show power
status all
FRU-type # current admin state oper
power-supply 1 27.460A on on
module 1 4.300A on on
module 2 4.300A - - (reserved)
module 5 2.690A on on
Router#
This example shows how to display the power status for a specific module:
Router#
show power
status module 1
FRU-type # current admin state oper
module 1 -4.300A on on
Router#
This example shows how to display the power status for a specific power supply:
Router#
show power
status power-supply 1
FRU-type # current admin state oper
power-supply 1 27.460A on on
Router#
Router#
show power
status power-supply 2
Power-Capacity PS-Fan Output Oper
PS Type Watts A @42V Status Status State
---- ------------------ ------- ------ ------ ------ -----
1 WS-CAC-6000W 2672.04 63.62 OK OK on
2 WS-CAC-9000W-E 2773.68 66.04 OK OK on
Router#
This example shows how to display the total power that is available from the power supplies:
Router#
show power
total
system power total = 27.460A
Router#
This example shows how to display the total power that is budgeted for powered-on items:
Router#
show power
used
system power used = -6.990A
Router#
This command shows how to display the inline power status on the interfaces:
Router#
show power
inline
Interface Admin Oper Power ( mWatt ) Device
-------------------- ----- ---------- --------------- -----------
FastEthernet9/1 auto on 6300 Cisco 6500 IP Phone
FastEthernet9/2 auto on 6300 Cisco 6500 IP Phone
.
.
. <Output truncated>
This command shows how to display the inline power status for a specific module:
Router
# show power
inline mod 7
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 Modularity Images and Cisco Catalyst 4500e Series Switches Running Cisco IOS XE
Software
show processes
Syntax Description history (Optional) For Cisco IOS processes only. Displays
the process history in an ordered format.
Release Modification
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Series Switches.
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:
• show processes, page 1179
• show processes, page 1179
• show processes, page 1179
The table below describes the significant fields shown in the display.
Field Description
CPU utilization for five seconds CPU utilization for the last 5 seconds. The second
number indicates the percentage of CPU time spent
at the interrupt level.
Runtime (ms) CPU time that the process has used (in
milliseconds).
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.
Field Description
PID Process ID.
The following is sample output from the s how processes process-id command:
Field Description
Process ID Process ID number and process name.
Memory usage [in bytes] This section contains fields that show the memory
used by the specified process.
CPU usage This section contains fields that show the CPU
resources used by the specified process.
Field Description
Average The average amount of CPU utilization by the
process since its invocation.
The table below describes the significant fields shown in the display.
Field Description
PID Process ID.
Field Description
Blocked Thread (with given process ID) that is currently
blocked by the process.
The table below describes the significant fields shown in the display.
Field Description
CPU utilization for five seconds CPU utilization for the last 5 seconds. The 3%
indicates the percentage of CPU time spent at the
interrupt level.
Field Description
one minute CPU utilization for the last minute.
show processes memory Displays the amount of system memory used per
system process.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches.
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:
• show processes cpu, page 1187
• show processes cpu, page 1187
• show processes cpu, page 1187
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.
The following is sample output from the show processes cpu command that shows an ARP probe process:
Field Description
CPU utilization for five seconds CPU utilization for the last 5 seconds. The second
number indicates the percent of CPU time spent at
the interrupt level.
Runtime (us) CPU time that the process has used (in
microseconds).
Field Description
uSecs Microseconds of CPU time for each process
invocation.
Note 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.
Field Description
Total CPU utilization for five seconds Total CPU utilization for the last 5 seconds. The
second number indicates the percent of CPU time
spent at the interrupt level.
Field Description
1 minute CPU utilization for the last minute.
The following is partial sample output from the show processes cpucommand with the detailedkeyword
when a Software Modularity image is running:
The table below describes the significant fields shown in the display.
Table 151 show processes cpu detailed (Software Modularity) Field Descriptions
Field Description
Total CPU utilization for five seconds Total CPU utilization for the last 5 seconds. The
second number indicates the percent of CPU time
spent at the interrupt level.
Field Description
5Min Percentage of CPU time spent at the interrupt level
for this process during the last five minutes.
The following is partial sample output from the show processes cpucommand with the detailedkeyword:
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:
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 (#) Core for which CPU utilization is being generated.
CPU utilization for five seconds CPU utilization for the last 5 seconds. The second
number indicates the percent of CPU time spent at
the interrupt level.
Runtime (us) CPU time that the process has used (in
microseconds).
Field Description
Invoked Number of times that the process has been invoked.
show processes memory Displays the amount of system memory used per
system process.
Command Default If no process ID or process name is specified, detailed information is displayed about all processes.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches.
Usage Guidelines 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.
The table below describes the significant fields shown in the display.
Field Description
Job Id Job identifier.
Max. spawns per minute Maximum number of respawns per minute for this
process.
Last started Date and time the process was last started.
Field Description
Process state Current state of process.
Examples 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:
Command Description
scheduler interrupt mask profile Enables or disables interrupt mask profiling for all
processes running on the system.
scheduler interrupt mask size Configures the maximum number of entries that
can exist in the interrupt mask buffer.
scheduler interrupt mask time Configures the maximum amount of time a process
can run with interrupts masked.
show processes interrupt mask detail Displays interrupt masked details for the specified
process or all processes in the system.
Syntax Description detail Displays information about the total amount of time
and the number of times interrupts have been
masked by all processes.
Examples 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:
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:
scheduler interrupt mask profile Enables or disables interrupt mask profiling for all
processes running on the system.
scheduler interrupt mask size Configures the maximum number of entries that
can exist in the interrupt mask buffer.
scheduler interrupt mask time Configures the maximum amount of time a process
can run with interrupts masked.
show processes interrupt mask buffer Displays the information stored in the interrupt
mask buffer.
Command Default The memory used by all types of system processes is displayed.
Command Default The system memory followed by a one-line summary of memory information about each IOS XE or
Software Modularity process is displayed.
Release Modification
12.0(28)S The output of the header line was updated to
support the Memory Thresholding feature.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Series Switches.
Cisco IOS XE Release 3.3S This command was introducted on the Cisco ASR
1000 Series Aggregation Services Routers.
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, page 1207
• show processes memory, page 1207
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:
The table below describes the significant fields shown in the display.
Field Description
Processor Pool Total Total amount of memory, in kilobytes (KB), held
for the Processor memory pool.
Field Description
Getbufs Number of times the process has requested a packet
buffer.
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.
Process ID: 1
Process Name: Chunk Manager
Total Memory Held: 8428 bytes
Processor memory holding = 8428 bytes
pc = 0x60790654, size = 6044, count = 1
pc = 0x607A5084, size = 1544, count = 1
pc = 0x6076DBC4, size = 652, count = 1
pc = 0x6076FF18, size = 188, count = 1
I/O memory holding = 0 bytes
Router# show processes memory 2
Process ID: 2
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).
Total: 35423840
, Used: 10904192, Free: 24519648
PID TTY Allocated Freed Holding Getbufs Retbufs Process
0 0 14548868 3004980 9946092 0 0 *Init*
0 0 12732 567448 12732 0 0 *Sched*
.
.
.
Router# show processes memory sorted
Total: 27035232
, Used: 8089188, Free: 18946044
PID TTY Allocated Freed Holding Getbufs Retbufs Process
0 0 14548868 3004980 9946092 0 0 *Init*
64 0 76436 3084 74768 0 0 CEF process
.
.
.
Router# show version | include IOS
Total: 50,994,868
, Used: 6222644, Free: 44772224
The table below describes the significant fields shown in the display.
Field Description
total Total amount of memory, in KB, on the device.
Field Description
free Amount of free memory, in KB, available in the
system.
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.
The table below describes the significant fields shown in the display that are different from the table above.
Table 156 show processes memory detailed process-id taskid Field Descriptions
Field Description
type Type of process: POSIX or IOS.
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:
0x0807FFB8 0x00000048
0x08080028 0x00003FD8
The table below describes the significant fields shown in the display.
Field Description
heapsize Size of the process heap, in KB,.
System memory : 1943928K total, 733702K used, 1210221K free, 153224K kernel reserved
Lowest(b) : 642265088
PID Text Data Stack Dynamic RSS Total Process
1 252 480 84 444 1648 3648 init
2 0 0 0 0 0 0 kthreadd
3 0 0 0 0 0 0 migration/0
4 0 0 0 0 0 0 ksoftirqd/0
5 0 0 0 0 0 0 migration/1
6 0 0 0 0 0 0 ksoftirqd/1
7 0 0 0 0 0 0 events/0
8 0 0 0 0 0 0 events/1
9 0 0 0 0 0 0 khelper
61 0 0 0 0 0 0 kblockd/0
62 0 0 0 0 0 0 kblockd/1
75 0 0 0 0 0 0 khubd
78 0 0 0 0 0 0 kseriod
83 0 0 0 0 0 0 kmmcd
120 0 0 0 0 0 0 pdflush
121 0 0 0 0 0 0 pdflush
122 0 0 0 0 0 0 kswapd0
123 0 0 0 0 0 0 aio/0
124 0 0 0 0 0 0 aio/1
291 0 0 0 0 0 0 kpsmoused
309 0 0 0 0 0 0 rpciod/0
310 0 0 0 0 0 0 rpciod/1
354 92 180 84 136 456 2188 udevd
700 0 0 0 0 0 0 loop1
716 0 0 0 0 0 0 loop2
732 0 0 0 0 0 0 loop3
2203 424 164 84 132 1172 3180 dbus-daemon
2539 76 160 84 132 532 1788 portmap
2545 76 160 84 132 532 1788 portmap
2588 232 396 84 132 992 4596 sshd
System memory : 1943928K total, 734271K used, 1209657K free, 153224K kernel reserved
Lowest(b) : 642265088
PID Text Data Stack Dynamic RSS Total Process
1 252 480 84 444 1648 3648 init
354 92 180 84 136 456 2188 udevd
2203 424 164 84 132 1172 3180 dbus-daemon
2539 76 160 84 132 532 1788 portmap
2545 76 160 84 132 532 1788 portmap
2588 232 396 84 132 992 4596 sshd
2602 196 320 84 132 752 2964 xinetd
2606 196 320 84 132 748 2964 xinetd
3757 76 160 84 132 532 1788 vsi work/0
3758 76 160 84 132 532 1788 vsi work/1
3891 848 148 84 88 1432 2984 check_gdb_statu
3895 72 160 84 132 580 1676 watchdog
4453 848 276 84 216 1512 3112 app_printf.sh
4465 848 272 84 212 1508 3108 app_printf.sh
4596 148 43972 84 528 5176 56664 slproc
TaskID TTY Allocated Freed Holding Getbufs Retbufs Task
1 0 327920 1544 367952 0 0 Chunk Manager
2 0 184 184 37032 0 0 Load Meter
3 0 0 0 40032 0 0 Deferred Events
4 0 17840 3888 40032 0 0 SpanTree Helper
5 0 0 0 40032 0 0 Retransmission of I
6 0 0 0 40032 0 0 IPC ISSU Receive Pr
7 0 0 0 40032 0 0 Check heaps
8 0 179248 173976 45304 144568 140316 Pool Manager
9 0 184 184 40032 0 0 Timers
10 0 184 184 40032 0 0 Serial Background
--More--
The following is sample output from the show processes memory detailedcommand specifying the Iosd
process:
System memory : 1943928K total, 734279K used, 1209649K free, 153224K kernel reserved
Lowest(b) : 642265088
PID Text Data Stack Dynamic RSS Total Process
10319 67716 798420 84 252 954524 1012856 iosd
The table below describes the significant fields shown in the display.
Field Description
Processor Pool Total Total amount of memory, in KB, held for the
Processor memory pool.
I/O Pool Total Total amount of memory, in KB, held for the I/O
memory pool.
Field Description
*Dead* Processes as a group that are now dead.
show protocols
To display the configured protocols, use the show protocols command in user EXEC or privileged EXEC
mode.
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
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.
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.
Usage Guidelines 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 The following is sample output from the show region command:
The following table describes the significant fields shown in the display.
Field Description
Start Start address of the memory block.
Field Description
Name Name of the region.
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.
Command Default If no options are specified, registry information is displayed for all registries.
Examples 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:
• Cisco IOS Software
• Cisco IOS Software Modularity
.
Registry 25: ATM routing Registry
Service 25/0:
The following table describes the significant fields shown in the display.
Field Description
Registry objects Number of objects in the registry.
The following table describes the significant fields shown in the display.
Field Description
Registry information Displays the registry information by process name.
show reload
To display the reload status on the router, use the show reload command in EXEC mode.
show reload
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:
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.
The following is sample output from the show resource-pool queue statisticscommand:
Router# show resource-pool statistics
show rhosts
To display information about current remote hosts, use the show rhostscommand in privileged EXEC
mode.
show rhosts
Cisco IOS 2.1 XE This command was integrated into Cisco IOS XE
Release 2.1.
Examples The following is sample output from the show rhosts command.
The following table describes the significant fields shown in the display.
Field Description
Local user Displays the name of the user on the local router.
This name gets communicated to the network
administrator or to the user on the remote system.
Field Description
Host/Access list Displays the name or the IP address of the remote
host from which the local router will accept
remotely executed commands.
Remote user Displays the name of the user on the remote host
from which the router will accept remotely
executed commands.
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 rom-
monitorcommand in user EXEC, privileged EXEC, or diagnostic mode.
Syntax Description slot Specifies the slot that contains the ROMMON.
Options include:
• number --The number of the SIP slot that
requires the ROMMON upgrade.
• F0 --Embedded Service Processor slot 0.
• F1 --Embedded Service Processor slot 1.
• FP active --Active Embedded Service
Processor.
• FP standby --Sstandby Embedded Service
Processor.
• R0 --Route Processor slot 0.
• R1 --Route Processor slot 1.
• RP active --Active Route Processor.
• RP standby --Standby Route Processor.
Command Modes User EXEC (>) Privileged EXEC (#) Diagnostic (diag)
Release Modification
12.2SX This command is supported in the Cisco IOS
Release 12.2SX train. Support in a specific 12.2SX
release of this train depends on your feature set,
platform, and platform hardware.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers and the following
enhancements were introduced:
• This command was introduced in diagnostic
mode. The command can be entered in both
privileged EXEC and diagnostic mode on the
Cisco ASR 1000 Series Routers.
• The slot argument was introduced.
Usage Guidelines 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.
Note 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.
Examples 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:
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:
Syntax Description num Displays the slot number of the ROMMON for
which the status is to be displayed.
Usage Guidelines 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 The following is output from the show running identity policy command:
Examples The following is output from the show running identity profilecommand:
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.
Command Default The default syntax, show running-config, displays the contents of the running configuration file, except
commands configured using the default parameters.
Release Modification
12.2(14)SX This command was integrated into Cisco IOS
Release 12.2(14)SX. The module number and vlan
vlan-id keywords and arguments were added for the
Supervisor Engine 720.
Usage Guidelines 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 running-
config 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 running-
config 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:
• The show running-config command does not display this value.
• The show running-config all displays the following output: cdp holdtime 180.
If the Cisco Discovery Protocol holdtime is changed to a nondefault value (for example, 100), the output of
the show running-config and show running-config 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.
The following example shows the configuration for Ethernet interface 0/0. Line numbers are displayed in
the output. The fields are self-explanatory.
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
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
Command Description
show startup-config Displays the contents of NVRAM (if present and
valid) or displays the configuration file pointed to
by the CONFIG_FILE environment variable.
(Command alias for the more:nvram startup-
config command.)
Command Default If no keyword is specified, all information about the control plane is displayed.
Examples The following is sample output from the show running-config control-plane command. The field
descriptions are self-explanatory.
Building configuration...
Current configuration : 14 bytes
!
control-plane
!
end
Command Default Displays all map-class configuration in the running configuration file.
Usage Guidelines Use the show running-config map-class command to display the following information from the running
configuration file:
• All map classes configured on the router.
• Map classes configured specifically for ATM, Frame Relay, or dialer.
• A specific ATM, Frame Relay, or dialer map class.
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:
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
Building configuration...
Current configuration:
!
map-class frame-relay cir60
frame-relay bc 16000
frame-relay adaptive-shaping becn
!
map-class frame-relay cir70
no frame-relay adaptive-shaping
frame-relay priority-group 2
end
Building configuration...
Current configuration:
1 : !
2 : map-class frame-relay boy
3 : no frame-relay adaptive-shaping
4 : frame-relay cir 1000
5 : end
Usage Guidelines 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 system’s configuration state for the
purpose of generating a partial running configuration is called “configuration partitioning.”
Note This command is not related to hard drive or flash drive partitioning.
This granular access to configuration information offers important performance benefits for high-end
routing platforms with very large configuration files, as the system wide generation of a complete virtual
configuration file from all components on systems with large and complex configurations can become
overly resource intensive and be unacceptably slow.
The show running-config partition command allows you to display only the part of the running
configuration that you want to examine, while also allowing the system to process only the collection of
system components (such as specific interfaces) that you need to display. This is in contrast to other
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.
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.
Command Description
show startup-config Displays the contents of NVRAM (if present and
valid) or displays the configuration file pointed to
by the CONFIG_FILE environment variable.
(Command alias for the more:nvram startup-
config command.)
show 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}
Release Modification
12.2(18)SXE The output of the show scp process command was
changed to display all the processes that have
registered an SAP with SCP on the Supervisor
Engine 720 only.
--------------------------------------------------------------------------------------------------------------------------
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# 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.
Usage Guidelines 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.
Note 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.
.
.
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.
Note In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
Examples The following example displays information about slot 0. The output is self-explanatory.
The following example shows all possible flash system information for all PCMCIA flash cards in the
system.
The following example shows the flash chip erase and write retries.
Router# show
slot summary
show slot0:
To display information about the PCMCIA flash memory card’s file system located in slot 0, use the show
slot0:command in user EXEC or privileged EXEC mode.
Usage Guidelines 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.
Note 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.
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.
Note In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
Examples The following example displays information about slot 0. The output is self-explanatory.
The following example shows the flash chip erase and write retries.
Router# show
slot0: summary
show slot1:
To display information about the PCMCIA flash memory card’s file system located in slot 1, use the show
slot1:command in user EXEC or privileged EXEC mode.
Usage Guidelines 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.
Note 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.
.
.
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.
Note In some cases the show slot command will not display the file systems. Use show slot0: or show slot1:.
Examples 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
The following example shows the flash chip erase and write retries.
Router# show
slot1: summary
Usage Guidelines 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:
The following table describes the significant fields shown in the display.
Field Description
File Name Name of the filename in the memory. For example,
flash0:c3900-universalk9-mz.SSA refers to
filename c3900-universalk9-mz.SSA in flash
memory (flash0:).
Certificate Serial Number Displays the certificate serial number for the digital
signature.
Command Description
show software authenticity running Displays information related to software
authentication for the current ROMMON, monitor
library (monlib), and Cisco IOS image used for
booting.
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:
The following table describes the significant fields shown in the display.
Field Description
Public Key # Public key number.
Key Type Displays the key type used for image verification.
Public Key Algorithm Displays the name of the algorithm used for public
key cryptography.
Usage Guidelines The information displayed by the show software authenticity running command about the current
ROMMON, monlib and Cisco IOS image used for booting includes:
• Image credential information
• Key type used for verification
• Signing information
• Any other attributes in the signature envelope
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.
Field Description
SYSTEM IMAGE Section of the output displaying the system image
information.
Certificate Serial Number Displays the certificate serial number for the digital
signature.
Command Description
show software authenticity keys Displays the software public keys that are in the
storage with the key types.
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks command in EXEC
mode.
show stacks
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:
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.
Syntax Description class class (Optional) Displays the subsystems of the specified
class. Valid classes are driver, ehsa, ifs, kernel,
library, license, management, microcode, pre-
ehsa, pre-driver, protocol, registry,and sysinit.
Usage Guidelines Use the show subsys command to confirm that all required features are in the running image.
Examples The following is sample output from the show subsys command:
The following is sample output from the show subsys command that includes the license class:
Field Description
Name Name of the subsystem.
show sup-bootflash
To display information about the sup-bootflash file system, use the show sup-bootflash command in
privileged EXEC mode.
Router#
show sup-bootflash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image EBC8FC4D A7487C 6 10700796 Nov 19 1999 07:07:37 halley
2 .. unknown C7EB077D EE2620 25 4644130 Nov 19 1999 07:50:44 cat6000-sup_
5-3-3-CSX.bin
645600 bytes available (15345184 bytes used)
Router#
This example shows how to display all bootflash information:
Router#
Complete Stats
No Unrecovered Errors
No Squeeze in progress
USAGE INFO:
Bytes Used = EA2620 Bytes Available = 9D9E0
Bad Sectors = 0 Spared Sectors = 0
OK Files = 2 Bytes = EA2520
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
Router#
Examples This example shows how to display the global MTU setting:
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]
Command Default The output scrolls without page breaks. Passwords and other security information are removed from the
output.
Release Modification
12.2(30)S The show tech-support ipmulticast command was
changed as follows:
• Support for bidirectional PIM and Multicast
VPN (MVPN) was added.
• The vrf vrf-name option was added.
The output of the show tech-support ipmulticast
command (without the vrf vrf-name keyword and
argument) was changed to include the output from
these commands:
• show ip pim int df
• show ip pim mdt
• show ip pim mdt bgp
• show ip pim rp metric
Release Modification
12.4(7) This command was integrated into Cisco IOS
Release 12.4(7).
Cisco IOS XE Release 2.5 This command was modified. The wccpkeyword
was added.
Usage Guidelines To interrupt and terminate the show tech-support output, simultaneously press and release the CTRL,
ALT, and 6 keys.
Press the Return key to display the next line of output, or press the 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:
• show appletalk traffic
• show bootflash
• show bootvar
• show buffers
• show cdp neighbors
• show cef
• show clns traffic
• show context
• show controllers
• show decnet traffic
• show disk0: all
• show dmvpn details
• show environment
• show fabric channel-counters
• show file systems
• show interfaces
• show interfaces switchport
• show interfaces trunk
• show ip interface
• show ip traffic
• show logging
• show mac-address-table
• show module
• show power
• show processes cpu
• show processes memory
• show running-config
• show spanning-tree
• show stacks
• show version
• show vlan
Note Crypto information is not duplicated by the show dmvpn details command output.
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 tech-
support command:
• show adjacency summary
• show cef drop
• show cef events
• show cef interface
Examples 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
show bootvar Displays the contents of the BOOT environment
variable, the name of the configuration file pointed
to by the CONFIG_FILE environment variable, the
contents of the BOOTLDR environment variable,
and the configuration register setting.
show clns traffic Displays a list of the CLNS packets this router has
seen.
show < command > | redirect Redirects the output of any show command to a
file.
show controllers tech-support Displays general information about a VIP card for
problem reporting.
show fabric channel counters Displays the fabric channel counters for a module.
Command Description
show interfaces switchport Displays the administrative and operational status
of a switching (nonrouting) port.
show logging Displays the state of syslog and the contents of the
standard system logging buffer.
show template
To display template information, use the show template command in user EXEC or privileged EXEC
mode.
Cisco IOS 2.1 XE This command was integrated into Cisco IOS XE
Release 2.1 on the Cisco ASR 1000 Series
Aggregation Services Router.
Examples The following is sample output from the show templatecommand displaying template information. The
fields are self-explanatory.
Command Default Information about all controllers on the system are displayed.
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:
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 CRC :0
Bit Stuff :0 Stall :0
No Response :0 Overrun :0
Underrun :0 Other :0
Buffer Overrun :0 Buffer Underrun :0
Transfer Errors:
Canceled Transfers :2 Control Timeout :0
Transfer Failures:
Interrupt Transfer :0 Bulk Transfer :0
Isochronous Transfer :0 Control Transfer:0
Transfer Successes:
Interrupt Transfer :0 Bulk Transfer :26
Isochronous Transfer :0 Control Transfer:894
USBD Failures:
Enumeration Failures :0 No Class Driver Found:0
Power Budget Exceeded:0
USB MSCD SCSI Class Driver Counters:
Good Status Failures :3 Command Fail :0
Good Status Timed out:0 Device not Found:0
Device Never Opened :0 Drive Init Fail :0
Illegal App Handle :0 Bad API Command :0
Invalid Unit Number :0 Invalid Argument:0
Application Overflow :0 Device in use :0
Control Pipe Stall :0 Malloc Error :0
Device Stalled :0 Bad Command Code:0
Device Detached :0 Unknown Error :0
Invalid Logic Unit Num:0
USB Aladdin Token Driver Counters:
Token Inserted :1 Token Removed :0
Send Insert Msg Fail :0 Response Txns :434
Dev Entry Add Fail :0 Request Txns :434
Dev Entry Remove Fail:0 Request Txn Fail:0
Response Txn Fail :0 Command Txn Fail:0
Txn Invalid Dev Handle:0
USB Flash File System Counters:
Flash Disconnected :0 Flash Connected :1
Flash Device Fail :0 Flash Ok :1
Flash startstop Fail :0 Flash FS Fail :0
USB Secure Token File System Counters:
Token Inserted :1 Token Detached :0
Token FS success :1 Token FS Fail :0
Token Max Inserted :0 Create Talker Failures:0
Token Event :0 Destroy Talker Failures:0
Watched Boolean Create Failures:0
Command Default Information for all devices attached to the system are displayed.
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:
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.
Field Description
Device handle Internal memory handle allocated to the device.
Device Subclass code The subclass code supported by the device. This
number is allocated by the USB-IF.
Interface Class code The class code supported by the interface. If the
value is set to 0xFF, the interface class is vendor
specific. All other values are allocated by the USB-
IF.
Interface Subclass code The subclass code supported by the interface. All
values are allocated by the USB-IF.
Cisco IOS XE Release 3.6 This command was integrated into Cisco IOS XE
Release 3.6.
Examples The following example is sample output for the show usb driver command:
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.
Field Description
Owner Mask Indicates the fields that are used in enumeration
comparison. The driver can own different devices
on the basis of their product or vendor IDs and
device or interface class, subclass, and protocol
codes.
Examples The following sample from the show usb port command shows the status of the port 1 on the router:
Examples 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.
show usbtoken
To display information about the USB eToken (such as the eToken ID), use the show usbtokencommand
in privileged EXEC mode.
Syntax Description 0-9 (Optional) One of the ten available flash drives you
can choose from; valid values: 0-9. If you do not
specify a number, 0 is used by default
Cisco IOS XE Release 3.6 This command was integrated into Cisco IOS XE
Release 3.6.
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:
“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.
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
Command Modes User EXEC (>) Privileged EXEC (#) Diagnostic (diag)--Cisco ASR 1000 Series Routers only
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and the following
enhancements were introduced:
• the command became available in diagnostic
mode.
• the rp-slot, installed, user-interface,
provisioned, and running options all became
available for the first time.
Cisco IOS XE Release 2.4 The output format of this command was updated.
Cisco IOS XE Release 3.1.0.SG This command was introduced on the Cisco
Catalyst 4500e Serfies Switches with support for
the rp-slot parameter and running command option.
Usage Guidelines This command displays information about the Cisco IOS software version currently running on a routing
device, the ROM Monitor and Bootflash software versions, and information about the hardware
configuration, including the amount of system memory. Because this command displays both software and
hardware information, the output of this command is the same as the output of the show hardware
command. (The show hardware command is a command alias for the show version command.)
Specifically, the show version command provides the following information:
• Software information
◦ Main Cisco IOS image version
◦ Main Cisco IOS image capabilities (feature set)
◦ Location and name of bootfile in ROM
◦ Bootflash image version (depending on platform)
• Device-specific information
◦ Device name
◦ System uptime
◦ System reload reason
◦ Config-register setting
◦ Config-register settings for after the next reload (depending on platform)
• Hardware information
◦ Platform type
◦ Processor type
◦ Processor hardware revision
◦ Amount of main (processor) memory installed
◦ Amount I/O memory installed
◦ Amount of Flash memory installed on different types (depending on platform)
◦ Processor board ID
The output of this command uses the following format:
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 sub-
package 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:
is configured on the Cisco 7200. Displaying bandwidth capacity is available in Cisco IOS Release 12.2 and
later releases.
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.
Field Description
Cisco IOS Software, platform Software (image-id), platform --Cisco hardware device name.
Version software-version, release-type image-id --The coded software image identifier, in
For example: the format platform-features-format (for example,
“c7200-g4js-mz”.
Cisco IOS Software, 7200 Software (C7200-G4JS-
M), Version 12.3(4)T software-version --The Cisco IOS software release
number, in the format x.y(z)A, where x.y is the main
release identifier, z is the maintenance release
number, and A, where applicable, is the special
release train identifier. For example, 12.3(4)T
indicates the fourth maintenance release of the
12.3T special technology release train.
Note In the full software image filename,
12.3(4)T appears as 123-4.T. In the IOS
Upgrade Planner, 12.3(4)T appears as
12.3.4T (ED).
release-type --The description of the release type.
Possible values include MAINTENANCE [for
example, 12.3(3)] or INTERIM [for example,
12.3(3.2)].
Tip Refer to “The ABC’s of Cisco IOS
Networking” (available on Cisco.com) for
more information on Cisco IOS software
release numbering and software versions.
Cisco IOS is a registered trademark (R) of Cisco
Systems, Inc.
ROM: System Bootstrap, Version 12.0(6r)T, The system “bootstrap” software, stored in ROM
RELEASE SOFTWARE (fc1) memory.
Field Description
device uptime is ... The amount of time the system has been up and
running.
For example:
C3660-1 uptime is 1 week, 3 days, 6 hours, 41
minutes
System returned to ROM by reload-reason at Shows the last recorded reason for a system reload,
timedaydate and time of last reload.
For example:
System returned to ROM by reload at 20:56:53
UTC Tue Nov 4 2003
Last reload reason: reload-reason Shows the last recorded reason for a system reload.
For example:
Last reload reason: Reload command
Last reset from reset-reason Shows the last recorded reason for a system reset.
Possible reset-reason values include:
For example:
Last reset from power-on • power-on--System was reset with the initial
power on or a power cycling of the device.
• s/w peripheral--System was reset due to a
software peripheral.
• s/w nmi--System was reset by a nonmaskable
interrupt (NMI) originating in the system
software. For example, on some systems, you
can configure the device to reset automatically
if two or more fans fail.
• push-button--System was reset by manual
activation of a RESET push-button (also called
a hardware NMI).
• watchdog--System was reset due to a
watchdog process.
• unexpected value--May indicate a bus error,
such as for an attempt to access a nonexistent
address (for example, “System restarted by bus
error at PC 0xC4CA, address 0x210C0C0”).
(This field was formerly labeled as the “System
restarted by” field.”)
System image file is “file-location/ file-name ” Displays the file location (local or remote
filesystem) and the system image name.
For example:
System image file is "slot0:tftpboot/c3660-i-mz.
123-3.9.T2"
Field Description
Cisco platform (processor-type ) processor This line can be used to determine how much
(revision processor-revision-id ) with free -DRAM- Dynamic RAM (DRAM) is installed on your
memory K/ packet-memory K bytes of memory. system, in order to determine if you meet the “Min.
Memory” requirement for a software image.
Example--Separate DRAM and Packet Memory:
DRAM (including SDRAM) is used for system
Cisco RSP4 (R5000) processor with 65536K/ processing memory and for packet memory.
2072K bytes of memory
Two values, separated by a slash, are given for
Example--Combined DRAM and Packet Memory: DRAM: The first value tells you how DRAM is
available for system processing, and the second
Cisco 3660 (R527x) processor (revision 1.0) with value tells you how much DRAM is being used for
57344K/8192K bytes of memory. Packet memory.
The first value, Main Processor memory, is either:
• The amount of DRAM available for the
processor, or
• The total amount of DRAM installed on the
system.
The second value, Packet memory, is either:
• The total physical input/output (I/O) memory
(or “Fast memory”) installed on the router
(Cisco 4000, 4500, 4700, and 7500 series), or
• The amount of “shared memory” used for
packet buffering. In the shared memory
scheme (Cisco 2500, 2600, 3600, and 7200
Series), a percentage of DRAM is used for
packet buffering by the router's network
interfaces.
Note The terms “I/O memory” or “iomem”;
“shared memory”; “Fast memory” and “PCI
memory” all refer to “Packet Memory”.
Packet memory is either separate physical
RAM or shared DRAM.
Separate DRAM and Packet Memory
The 4000, 4500, 4700, and 7500 series routers have
separate DRAM and Packet memory, so you only
need to look at the first number to determine total
DRAM. In the example to the left for the Cisco
RSP4, the first value shows that the router has
65536K (65,536 kilobytes, or 64 megabytes) of
DRAM. The second value, 8192K, is the Packet
memory.
Combined DRAM and Packet Memory
The 2500, 2600, 3600, and 7200 series routers
require a minimum amount of I/O memory to
support certain interface processors.
The 1600, 2500, 2600, 3600, and 7200 series
routers use a fraction of DRAM as Packet memory,
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.
Configuration register is value Shows the current configured hex value of the
software configuration register. If the value has
For example:
been changed with the config-register command,
Configuration register is 0x2142 (will be 0x2102 at the register value that will be used at the next reload
next reload) is displayed in parenthesis.
The boot field (final digit) of the software
configuration register dictates what the system will
do after a reset.
For example, when the boot field of the software
configuration register is set to 00 (for example,
0x0), and you press the NMI button on a
Performance Route Processor (PRP), the user-
interface remains at the ROM monitor prompt
(rommon>) and waits for a user command to boot
the system manually. But if the boot field is set to
01 (for example, 0x1), the system automatically
boots the first Cisco IOS image found in the
onboard Flash memory SIMM on the PRP.
The factory-default setting for the configuration
register is 0x2102. This value indicates that the
router will attempt to load a Cisco IOS software
image from Flash memory and load the startup
configuration file.
The following table describes the fields that are shown in the example.
Field Description
IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version number. Always specify the complete
Version 12.1(nightly.E020626) NIGHTLY BUILD version number when reporting a possible software
problem. In the example output, the version number
is 12.1.
Router uptime is Amount of time that the system has been up and
running.
Time since Router switched to active Amount of time since switchover occurred.
System restarted by Log of how the system was last booted, both as a
result of normal system startup and of system error.
For example, information can be displayed to
indicate a bus error that is typically the result of an
attempt to access a nonexistent address, as follows:
System restarted by bus error at PC 0xC4CA,
address 0x210C0C0
System image file is If the software was booted over the network, the
Internet address of the boot host is shown. If the
software was loaded from onboard ROM, this line
reads “running default software.”
cisco Catalyst 6000 (R7000) processor with Remaining output in each display that shows the
112640K/18432K bytes of memory. hardware configuration and any nonstandard
software options.
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:
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#
Router#
Cisco Internetwork Operating System Software
IOS (tm) 7200 Software (UBR7200-P-M), Version 12.1(10)EC, RELEASE SOFTWARE
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Wed 02-Feb-00 16:49 by ccai
Image text-base:0x60008900, data-base:0x61192000
ROM:System Bootstrap, Version 12.0(15)SC, RELEASE SOFTWARE
VXR1 uptime is 2 days, 1 hour, 24 minutes
System returned to ROM by power-on at 10:54:38 PST Sat Feb 5 2000
System restarted at 11:01:08 PST Sat Feb 5 2000
System image file is "slot1:ubr7200-p-mz.121-0.8.T"
cisco uBR7246VXR (NPE300) processor (revision B) with 122880K/40960K bytes of memory.
Processor board ID SAB0329005N
R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
6 slot VXR midplane, Version 2.0
Last reset from power-on
X.25 software, Version 3.0.0.
National clock card with T1 controller
1 FastEthernet/IEEE 802.3 interface(s)
2 Cable Modem network interface(s)
125K bytes of non-volatile configuration memory.
16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
4096K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0
Router#
Field Description
IOS (tm) 7200 Software (UBR7200-P-M), Version Always specify the complete version number when
xx.x reporting a possible software problem. In the
example, the version number is Cisco IOS Release
12.1(10)EC.
Field Description
Router uptime is The amount of time the system has been up and
running.
System restarted at Also displayed is a log of how the system was last
booted, as a result of normal system startup or
system error.
System image file is If the software was booted over the network, the
Internet address of the boot host is shown. If the
software was loaded from onboard ROM, this line
reads “running default software.”
cisco uBR7246VXR (NPE300) processor The remaining output in each display shows the
hardware configuration and any nonstandard
software options.
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.
In the following example, the show version command is responsible for displaying the
packages installed, provisioned and running on the current RP.
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).
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
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 show version installed, provisioned, and running Field Descriptions
Field Description
Package: The individual sub-package name.
File SHA1 checksum: The SHA1 sum for the file. This sum can be
compared against a SHA1 sum generated by any
SHA1 sum-generating tool.
All rights reserved. Certain components of Cisco IOS-XE software are licensed under the
GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL
Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute
and/or modify such GPL code under the terms of GPL Version 2.0. For more details, see
the documentation or "License Notice" file accompanying the IOS-XE software, or the
applicable URL provided on the flyer accompanying the IOS-XE software.
ROM: 12.2(54r)XO(0.246)
Jawa Revision 7, Snowtrooper Revision 0x0.0x14
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
Switch#
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
Table 174 Table 5,Cisco Catalyst 4500e Series Switched show version running Field Descriptions
Field Description
Package: The individual sub-package name.
Field Description
File: The filename of the individual package file.
show warm-reboot
To display the statistics for attempted warm reboots, use the show warm-rebootcommand in privileged
EXEC mode.
show warm-reboot
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:
show wiretap
To display the intercept status, use the show wiretap command in privileged EXEC mode.
Command Default If the id is not specified , information for all wiretap configurations and IDBs is displayed.
Usage Guidelines Use the show wiretapcommand to display the intercept status.
Examples The following is sample output from the show wiretap command. The field descriptions are self-
explanatory.
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.
Usage Guidelines 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:
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
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:
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 master’s
startup configuration (nvram:startup-config) as the target, the master also copies the same file to the
slave’s 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
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.
Syntax Description processor-slot-number Number of a processor slot that contains the default
slave RSP. On the Cisco 7507 router, valid values
are 2 or 3. On the Cisco 7513 router, valid values
are 6 or 7. The default is the higher number
processor slot.
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.
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.
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:
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 Loads the slave image that is bundled with the
master system image. This is the default.
Command Default The default is to load the image from the system bundle.
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.
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.
Note 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:
slave reload Forces a reload of the image that the slave RSP card
is running on a Cisco 7507 or Cisco 7513 router.
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
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.
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.
slave image Specifies the image that the slave RSP runs on a
Cisco 7507 or Cisco 7513 router.
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.
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
master’s configuration file to the slave RSP card.
Note 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.
Examples In the following example, the configuration files on the master and slave RSP card are synchronized:
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
Usage Guidelines 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:
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 7 Selects the 7-bit ASCII character set. This is the
default.
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
squeeze
To permanently erase files tagged as “deleted” or “error” on Class A flash file systems, use the squeeze
command in privileged EXEC mode.
Syntax Description /nolog (Optional) Disables the squeeze log (recovery data)
and accelerates the squeeze process.
Release Modification
12.2(4)XL This command was implemented on the Cisco 1700
series routers.
Usage Guidelines 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 Using the /nolog keyword makes the squeeze process uninterruptible.
Using the /quiet keyword disables the output of status messages to the console during the squeeze process.
If the optional keywords are not used, the progress of the squeeze process will be displayed to the console,
a log for the process will be maintained, and the squeeze process is interruptible.
On Cisco 2600 or Cisco 3600 series routers, the entire file system has to be erased once before the squeeze
command can be used. After being erased once, the squeeze command should operate properly on the flash
file system for the rest of the flash file system’s history.
To erase an entire flash file system on a Cisco 2600 or 3600 series router, perform the following steps:
1 If the flash file system has multiple partitions, enter the no partition command to remove the partitions.
The reason for removing partitions is to ensure that the entire flash file system is erased. The squeeze
command can be used in a flash file system with partitions after the flash file system is erased once.
2 Enter the erase command to erase the flash file system.
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.
Directory of slot0:/
1 -rw- 4300244 Apr 02 2001 03:18:07 c7200-boot-mz.122-0.14
2 -rw- 4300244 Apr 02 2001 04:45:23 image
20578304 bytes total (11977560 bytes free)
!20,578,304 - 4,300,244 - 4,300,244 - 256 = 11977560
Router#
squeeze flash:
stack-mib portname
To specify a name string for a port, use the stack-mib portnamecommand in interface configuration mode.
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-STACK-
MIB. You can set this object to be descriptive text describing the function of the interface.
Router(config-if)#
stack-mib portname portall
Router(config-if)#
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.
Syntax Description name Name for the state machine (used in the dispatch-
machine line configuration command). The user
can specify any number of state machines, but each
line can have only one state machine associated
with it.
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
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
Usage Guidelines Communication protocols provided by devices such as terminals and modems often require a specific stop-
bit 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
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.
Usage Guidelines 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:
• Set the level to 100 percent for the specified traffic type.
• Use the no form of this command.
Examples This example shows how to enable and set the suppression level:
Router(config-if)#
storm-control broadcast level 30
Router(config-if)#
no storm-control multicast level
sync-restart-delay
To set the synchronization-restart delay timer to ensure accurate status reporting, use the sync-restart-
delay 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
Usage Guidelines This command is supported on Gigabit Ethernet fiber ports only.
The status register records the current status of the link partner.
Examples This example shows how to set the Gigabit Ethernet synchronization-restart delay timer:
systat
Note This command has been replaced by the show users command.
To display information about the active lines on the router, use the systatcommand in user EXEC or
privilegedEXEC mode.
systat all
Syntax Description all Displays all lines, regardless of whether the lines
are used or not.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Examples The following example shows how to display the active lines:
Router# systat
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00
Interface User Mode Idle Peer Address
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:
This example shows how to specify the original FIFO threshold settings:
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.
Syntax Description mtu-size Maximum size of the Layer 2 and Layer 3 packet s;
valid values are from 1500 to 9216 bytes.
Usage Guidelines 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:
Syntax Description priority-number Priority of the clock source. The priority range is
from 1 to 99. A clock set to priority 100 will not
drive the TDM bus.
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.
Usage Guidelines The TDM bus can receive an input clock from one of three sources on the gateway:
• CT1, CE1, and CT3 trunk cards
• An external T1/E1 clock source feed directly through the Building Integrated Timing Supply (BITS)
interface port on the motherboard
• Free-running clock providing clock from an oscillator
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 network’s 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 free-
running clock from the internal oscillator using the freerun keyword with the tdm clock priority
command.
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:
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:
show tdm clocks Displays default system clocks and clock history.
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}
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:
terminal parity Defines the generation of the parity bit for the
current terminal line and session.
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}
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:
terminal dispatch-character
To define a character that causes a packet to be sent for the current session, use the terminal dispatch-
character command in EXEC mode.
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:
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.
Usage Guidelines 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 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.
Note The router response time might appear intermittent if the timeout interval is greater than 100 milliseconds
and remote echoing is used.
Examples In the following example, the dispatch timeout timer is set to 80 milliseconds:
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
Usage Guidelines 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:
• terminal telnet transparent
• terminal no escape-character (see terminal escape-character )
• terminal no hold-character (see terminal hold-character )
• terminal no padding 0 (see terminal padding )
• terminal no padding 128 (seeterminal padding )
• terminal parity none
• terminal databits 8
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
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:
terminal escape-character
To set the escape character for the current terminal line for the current session, use the terminal escape-
character command in EXEC mode.
terminal escape-character ascii-number
Usage Guidelines 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.
Note 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.
Examples In the following example, the escape character to Ctrl-P (ASCII decimal character 16) for the current
session:
Router# terminal escape-character 16
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 7 Selects the 7-bit ASCII character set. This is the
default.
Command Default 7-bit ASCII character set (unless set otherwise in global configuration mode)
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 exec-
character-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:
terminal flowcontrol
To set flow control for the current terminal line for the current session, use the terminal flowcontrol
command in EXEC mode.
Usage Guidelines 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:
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
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 Boot Flash information
calendar Display the hardware calendar
clock Display the system clock
context Show context information
dialer Dialer parameters and statistics
history Display the session command history
hosts IP domain-name, lookup style, nameservers, and host table
isdn ISDN information
kerberos Show Kerberos Values
modemcap Show Modem Capabilities database
ppp PPP parameters and statistics
rmon rmon statistics
sessions Information about Telnet connections
snmp snmp statistics
terminal Display terminal configuration parameters
users Display information about terminal lines
version System hardware and software status
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
Usage Guidelines 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.
Key(s) Function
Ctrl-P or Up Arrow4 Recalls commands in the history buffer in a
backward sequence, beginning with the most recent
command. Repeat the key sequence to recall
successively older commands.
Examples In the following example, the command history feature is disabled for the current terminal session:
show history Lists the commands you have entered in the current
EXEC session.
terminal history size Sets the size of the history buffer for the command
history feature for the current terminal session.
Syntax Description number-of-lines Number of command lines that the system will
record in its history buffer. The range is from 0 to
256. The default is 10.
Usage Guidelines 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.
Key Function
Ctrl-P or Up Arrow5 Recalls commands in the history buffer in a
backward sequence, beginning with the most recent
command. Repeat the key sequence to recall
successively older commands.
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.)
show <command> begin Searches the output of any show command and
displays the output from the first instance of a
specified string.
Command Description
show history Lists the commands you have entered in the current
EXEC session.
terminal history Enables the command history feature for the current
terminal session.
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.
Command Default The default hold character is defined by the hold-character global configuration command.
Usage Guidelines 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).
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 Dispatch
00:10:00 never none not set
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.
.
.
.
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
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:
terminal keymap-type
To specify the current keyboard type for the current session, use the terminal keymap-type command in
EXEC mode.
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:
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.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and became available in
diagnostic mode.
Usage Guidelines 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:
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
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:
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
Usage Guidelines 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:
terminal padding
To change the character padding on a specific output character for the current session, use the terminal
padding command in EXEC mode.
Usage Guidelines 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:
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.
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:
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.
Syntax Description bps Baud rate in bits per second (bps). The default is
9600.
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:
terminal rxspeed Sets the terminal receive speed for the current
session.
Command Description
terminal txspeed Sets the terminal transmit speed for a specified line
or lines.
terminal speed Sets the transmit and receive speeds for the current
session.
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 7 Selects the 7-bit ASCII character set. This is the
default.
Usage Guidelines 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 exec-
character-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.
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.
Syntax Description bps Baud rate in bits per second (bps). The default is
9600.
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:
terminal start-character
To change the flow control start character for the current session, use the terminal start-character
command in EXEC mode.
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):
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.
Usage Guidelines Communication protocols provided by devices such as terminals and modems often require a specific stop-
bit setting.
Examples In the following example, the setting for stop bits is changed to one for the current session:
terminal stop-character
To change the flow control stop character for the current session, use the terminal stop-character
command in EXEC mode.
Usage Guidelines 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:
Usage Guidelines 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.
Note In this command, the acronym “ip” indicates “interrupt-process,” not Internet Protocol (IP).
Examples In the following example, a Break signal is generated for the current connection when an interrupt-process
command is issued:
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:
Syntax Description default-speed Line speed, in bits per second (bps), that the access
server will use if the device on the other end of the
connection has not specified a speed.
Command Default 9600 bps (unless otherwise set using the speed, txspeed or rxspeed line configuration commands)
Usage Guidelines 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.
Note 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.
Usage Guidelines 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.
Note This command applies only to access servers. It is not supported on standalone routers.
Examples The following example sets an asynchronous line to cause the access server to send a Telnet Synchronize
signal:
Usage Guidelines 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.
Note This command applies only to access servers. It is not supported on stand-alone routers.
Examples In the following example, the session is configured to send a CR signal as a CR followed by a NULL:
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.
Syntax Description terminal-type Defines the terminal name and type, and permits
terminal negotiation by hosts that provide that type
of service. The default is VT100.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and became available in
diagnostic mode.
Usage Guidelines Indicate the terminal type if it is different from the default of VT100.
The terminal type name is used by TN3270s for display management and by Telnet and rlogin to inform
the remote host of the terminal type.
Examples In the following example, the terminal type is defined as VT220 for the current session:
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.
Syntax Description bps Baud rate in bits per second (bps). The default is
9600 bps.
Examples In the following example, the line transmit speed is set to 2400 bps for the current session:
terminal rxspeed Sets the terminal receive speed for the current line
and session.
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.
Cisco IOS XE Release 2.1 This command was introduced on the Cisco ASR
1000 Series Routers, and became available in
diagnostic mode.
Usage Guidelines 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 The following example sets the terminal character columns to 132:
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.
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:
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.
Usage Guidelines 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.
Router(config)# line 7
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.
Syntax Description tdr Activates the TDR test for copper cables on 48-port
10/100/1000 BASE-T modules.
Usage Guidelines Cable diagnostics can help you detect whether your cable has connectivity problems.
The TDR test guidelines are as follows:
• TDR can test cables up to a maximum length of 115 meters.
• The TDR test is supported on Cisco 7600 series routers running Release 12.2(17a)SX and later
releases on specific mdoules. See the Release Notes for Cisco IOS Release 12.2SX on the Catalyst
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:
• 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.
show cable-diagnostics tdr Displays the test results for the TDR cable
diagnostics.
test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash command in EXEC
mode.
test flash
test flash
test interfaces
To test the system interfaces on the modular router, use the test interfaces command in EXEC mode.
test interfaces
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.
test interfaces
Command Description
test memory Performs a test of Multibus memory (including
nonvolatile memory) on the modular router.
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
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.
test memory
Command Default This command destroys memory chunks or dangling references on a router.
Usage Guidelines The force-chunk keyword destroys a chunk of ordinary (not managed) memory, even if the memory has
elements or siblings that are not free.
Caution Use the force-chunk keyword carefully. A crash or corruption will occur if someone refers to the destroyed
chunk or its elements.
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
Syntax Description rate Specifies the internal police rate. The range is from
0 to 100000 kbps.
• For the SIP-400, you can configure a rate up
to, and including 25600 packets per second
(PPS).
• For the ES+ line cards and the 7600-ES
+ITU-2TG and 7600-ES+ITU-4TG line cards,
you can configure rates of:
◦ 16 Kbps to 2 Mbps; granularity of 16 kbps
◦ 2 Mbps to 100 Mbps; granularity of 64
kbps
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.
Usage Guidelines 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
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.
filename2 Alternate name of the file that the TFTP server uses
in answering TFTP Read Requests. A client of the
TFTP server can use this alternate name in its Read
Requests.
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.
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:
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.
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
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
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 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.
Examples 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:
trace (privileged)
To discover the routes that packets will actually take when traveling to their destination, use the trace
command in privileged EXEC mode.
Syntax Description protocol (Optional) Protocols that can be used are appletalk,
clns, ip and vines.
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.
Usage Guidelines 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:
The following table describes the significant fields shown in the display.
Field Description
1 Indicates the sequence number of the router in the
path to the host.
1000 msec 8 msec 4 msec Round-trip time for each of the three probes that are
sent.
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.
Field Description
Target IP address You must enter a host name or an IP address. There
is no default.
Minimum Time to Live [1] The TTL value for the first probes. The default is 1,
but it can be set to a higher value to suppress the
display of known hops.
Maximum Time to Live [30] The largest TTL value that can be used. The default
is 30. The trace command terminates when the
destination is reached or when this value is reached.
Field Description
Port Number The destination port used by the User Datagram
Protocol (UDP) probe messages. The default is
33434.
Loose, Strict, Record, Timestamp, Verbose IP header options. You can specify any
combination. The trace command issues prompts
for the required fields. Note that the trace
command will place the requested options in each
probe; however, there is no guarantee that all
routers (or end nodes) will process the options.
The following table describes the characters that can appear in trace command output.
Char Description
nn msec For each node, the round-trip time (in milliseconds)
for the specified number of probes.
H Host unreachable.
N Network unreachable.
P Protocol unreachable.
Char Description
Q Source quench.
U Port unreachable.
trace (user)
To discover the IP routes that packets will actually take when traveling to their destination, use the trace
command in EXEC mode.
Syntax Description protocol (Optional) Protocols that can be used are appletalk,
clns, ip and vines.
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.
Usage Guidelines 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:
The following table describes the significant fields shown in the display.
Field Description
1 Indicates the sequence number of the router in the
path to the host.
1000 msec 8 msec 4 msec Round-trip time for each of the three probes that are
sent.
The following table describes the characters that can appear in trace output.
Char Description
nn msec For each node, the round-trip time (in milliseconds)
for the specified number of probes.
H Host unreachable.
N Network unreachable.
P Protocol unreachable.
Q Source quench.
U Port unreachable.
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.
Syntax Description vrf vrf-name (Optional) Specifies the name of a Virtual Private
Network (VPN) routing and forwarding (VRF)
instance table in which to find the destination
address. The only keyword that you can select for
the protocol argument when you use the vrf vrf-
name keyword-argument pair is the ip keyword.
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.
Cisco IOS XE Release 3.2S This command was modified. When the vrf
keyword is used, the output displays the incoming
VRF name/tag and the outgoing VRF name/tag.
Release Modification
15.0(1)SY This command was modified. When the vrf
keyword is used, the output displays the incoming
VRF name/tag and the outgoing VRF name/tag.
Usage Guidelines 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.
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.
Syntax Description source-mac-address Media Access Control (MAC) address of the source
switch in hexadecimal format.
Usage Guidelines 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:
This example shows how to display the Layer 2 path by specifying the source and destination hostnames:
This example shows the output when ARP cannot associate the source IP address with the corresponding
MAC address:
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 A number that indexes the file in the dir command
output.
Command Default The default file system is the one specified by the cd command.
Usage Guidelines 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 router-
config 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.
unprofile
To free the memory either by deleting data or disabling the profiles, use the unprofilecommand in
privilegedEXEC mode.
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Examples The following example shows how to delete all the profile data:
Router# unprofile
process all
Command Default The reload of the router with the Cisco IOS software image is not scheduled. The disk-management utility
is disabled.
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
upgrade automatic runversion Reloads the router with a new Cisco IOS software
image.
upgrade automatic getversion{cisco username username password password image image | url}
{[at hh:mm] | now | [in hh:mm]} [disk-management {auto | confirm | no}]
Command Default The reload of the router with the Cisco IOS software image is not scheduled. The disk-management utility
is disabled.
Usage Guidelines 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.
################################################################################
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.
upgrade automatic runversion Reloads the router with a new Cisco IOS software
image.
Usage Guidelines Use the upgrade automatic runversion command to schedule a reload after downloading a Cisco IOS
software image using the upgrade automatic getversion command.
Note 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.
Examples The following example shows how to schedule a reload after downloading a Cisco IOS software image:
Usage Guidelines 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:
upgrade rom-monitor
To set the execution preference on a read-only memory monitor (ROMMON), use the upgrade rom-
monitor command in privileged EXEC or diagnostic mode.
Syntax Description slot num Specifies the slot number of the ROMMON to be
upgraded.
file filename Specifies the name of the S-record (SREC) file; see
the “Usage Guidelines” section for valid values.
slot The slot that contains the hardware that will receive
the ROMMON upgrade. Options are:
• number --the number of the Session Initiation
Protocol (SIP) slot that requires the
ROMMON upgrade
• all --All hardware on the router
• F0 --Embedded-Service-Processor slot 0
• F1 --Embedded-Service-Processor slot 1
• FP --All installed Embedded-Service-
Processors
• R0 --Route-Processor slot 0
• R1 --Route-Processor slot 1
• RP --Route-Processor
Cisco IOS XE Release 2.1 This command was integrated into Cisco ASR 1000
Series Routers, and introduced in diagnostic mode.
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:
Usage Guidelines 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:
Usage Guidelines 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:
Proceed? [confirm]
Done! Router must be reloaded for this to take effect.
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
<blank lines>
hostname tty# is now available
<blank lines>
Press RETURN to get started.
Usage Guidelines 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 For a rotary group, you need to define only the message for the first line in the group.
Examples 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.
Syntax Description /md5 (Optional) Calculates and displays the MD5 value
for the specified software image. Compare this
value with the value available on Cisco.com for this
image.
Command Default The current working device is the default device (file system).
Usage Guidelines 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:
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:
Directory of slot0:/
1 -rw- 4720148 Aug 29 1997 17:49:36 hampton/nitro/c7200-j-mz
2 -rw- 4767328 Oct 01 1997 18:42:53 c7200-js-mz
5 -rw- 639 Oct 02 1997 12:09:32 rally
7 -rw- 639 Oct 02 1997 12:37:13 the_time
20578304 bytes total (3104544 bytes free)
Router# verify slot0:c7200-js-mz
Verified slot0:c7200-js-mz
In the following example, the /md5 keyword is used to display the MD5 value for the image:
.
.
.
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:
.
.
File cat6k_r47_1.cbi verified OK.
This example shows how to allow the system to compare the MD5 signatures:
This example shows how to verify the compressed checksum of the Cisco IOS image:
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 Sets the VTP administrative domain name.
file filename Sets the ASCII name of the IFS file system file
where the VTP configuration is stored.
interface interface-name Sets the name of the preferred source for the VTP-
updater ID for this device.
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.
Caution 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 2-
capable 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 2-
capable 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 set the device’s management domain:
Router(config)#
vtp domain DomainName1
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.
Router(config)#
vtp mode client
Setting device to VTP CLIENT mode.
This example shows how to reset the device to the VTP server mode:
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.
Usage Guidelines 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:
where
To list the open sessions, use the wherecommand in EXEC mode.
where
Usage Guidelines 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.
Router#
where
Conn Host Address Byte Idle Conn Name
1 MATHOM 192.31.7.21 0 0 MATHOM
* 2 CHAFF 131.108.12.19 0 0 CHAFF
Field Description
Conn Name or address of the remote host to which the
connection is made.
Field Description
Host Remote host to which the router is connected
through a Telnet session.
Idle Interval (in minutes) since data was last sent on the
line.
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
Usage Guidelines 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
write core
To test the configuration of a core dump setup, use the write core command in privileged EXEC mode.
Syntax Description hostname (Optional) Host name of the remote server where
the core dump file is to be written.
Command Default 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.”
Usage Guidelines 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
Cisco IOS XE Release 2.1 This command was integrated into Cisco IOS XE
Release 2.1.
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 mib-
datacommand in EXEC mode.
write mib-data
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
Usage Guidelines 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(config)# end
Router# write mib-data
write network
Note This command has been replaced by copy system:/running-config command.
To upload the current configuration to the network, use the write network command in privileged EXEC
mode.
write network [host-file-address]
Cisco IOS XE Release 2.1 This command was implemented on the Cisco ASR
1000 Series Aggregation Services Routers.
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:
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.
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]
Command Default Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
Usage Guidelines 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 router’s 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 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 router’s configuration settings.
Note If the file to be downloaded is not a valid router image, the copy operation is automatically terminated.
Examples The following example uses the xmodem -c filename ROM monitor command to copy the file named new-
ios-image from a remote or local computer:
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.
32 20 SP Space Space
33 21 ! ! !
35 23 # # #
36 24 $ $ $
37 25 % % %
39 27 ’ ’ ’
40 28 ( ( (
41 29 ) ) )
42 2A * * *
43 2B + + +
44 2C , , ,
45 2D - - -
46 2E . . .
47 2F / / /
48 30 0 Zero 0
49 31 1 One 1
50 32 2 Two 2
51 33 3 Three 3
52 34 4 Four 4
53 35 5 Five 5
54 36 6 Six 6
55 37 7 Seven 7
57 39 9 Nine 9
58 3A : : :
59 3B ; ; ;
61 3D = = =
63 3F ? ? ?
64 40 @ @ @
65 41 A A A
66 42 B B B
67 43 C C C
68 44 D D D
69 45 E E E
70 46 F F F
71 47 G G G
72 48 H H H
73 49 I I I
74 4A J J J
75 4B K K K
76 4C L L L
77 4D M M M
78 4E N N N
79 4F O O O
80 50 P P P
81 51 Q Q Q
82 52 R R R
83 53 S S S
85 55 U U U
86 56 V V V
87 57 W W W
88 58 X X X
89 59 Y Y Y
90 5A Z Z Z
91 5B [ [ [
92 5C \ \ \
93 5D ] ] ]
94 5E ^ ^ ^
95 5F _ _ _
96 60 ` ` `
97 61 a a a
98 62 b b b
99 63 c c c
100 64 d d d
101 65 e e e
102 66 f f f
103 67 g g g
104 68 h h h
105 69 i i i
106 6A j j j
107 6B k k k
108 6C l l l
109 6D m m m
110 6E n n n
111 6F o o o
113 71 q q q
114 72 r r r
115 73 s s s
116 74 t t t
117 75 u u u
118 76 v v v
119 77 w w w
120 78 x x x
121 79 y y y
122 7A z z z
123 7B { { {
124 7C | | |
125 7D } } }
126 7E ~ Tilde ~