Table Of Contents
Cisco IOS Software Modularity Commands
exception crashinfo buffersize
write core (Software Modularity)
Cisco IOS Software Modularity Commands
archive tar
To create a TAR file, to list the files in a TAR file, or to extract the files from a TAR file, use the archive tar command in privileged EXEC mode.
archive tar {/create destination-url flash:/file-url | /table source-url | /xtract source-url flash:/file-url [dir/file...]}
Syntax Description
Command Default
A TAR archive file is not created.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Filenames, directory names, and image names are also case sensitive.
The TAR file is an archive file from which you can extract files by using the archive tar command.
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.
Switch# archive tar /create tftp:172.20.136.9/saved.tar flash:/new-configsThe following example shows how to display the contents of the c2940-tv0-m.tar file that is in flash memory. The contents of the TAR file appear on the screen.
Switch# archive tar /table flash:c2940-tv0-m.tar
info (219 bytes)
c2940-tv0-mz-121/ (directory)
c2940-tv0-mz-121/html/ (directory)
c2940-tv0-mz-121/html/foo.html (0 bytes)
c2940-tv0-mz-121/vegas-tv0-mz-121.bin (610856 bytes)
c2940-tv0-mz-121/info (219 bytes)
info.ver (219 bytes)
The following example shows how to extract the contents of a TAR file on the TFTP server at 172.20.10.30. This command extracts only the new-configs directory into the root directory on the local flash file system. The remaining files in the saved.tar file are ignored.
Switch# archive tar /xtract tftp:/172.20.10.30/saved.tar flash:/ new-configsclear raw statistics
To clear raw IP statistics when Cisco IOS Software Modularity software is running, use the clear raw statistics command in privileged EXEC mode.
clear raw statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
There are three transport protocols used when Software Modularity software is running: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and raw IP. The transport protocol statistics are generally counters, but some are averages or time stamps. Use the clear raw statistics command to reset the raw IP statistics, and use the show raw statistics command to display the raw IP statistics. Many of the statistics are relevant to all of the transport protocols. To clear the other transport protocol statistics used in Software Modularity, use the clear tcp statistics and clear udp statistics commands.
Examples
The following example shows how to clear the raw IP statistics using the clear raw statistics command:
Router# clear raw statistics[confirm]Related Commands
clear tcp statistics
Clears TCP statistics.
clear udp statistics
Clears UDP statistics.
show raw statistics
Displays raw IP statistics.
clear udp statistics
To clear User Datagram Protocol (UDP) statistics when Cisco IOS Software Modularity software is running, use the clear udp statistics command in privileged EXEC mode.
clear udp statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
There are three transport protocols used when Software Modularity software is running: Transmission Control Protocol (TCP), UDP, and raw IP. The transport protocol statistics are generally counters, but some are averages or time stamps. Use the clear udp statistics command to reset the UDP statistics, and use the show udp statistics command to display the UDP statistics. Many of the statistics are relevant to all of the transport protocols. To clear the other transport protocol statistics used in Software Modularity, use the clear raw statistics and clear tcp statistics commands.
Examples
The following example shows how to clear the UDP statistics using the clear udp statistics command:
Router# clear udp statistics[confirm]Related Commands
clear raw statistics
Clears raw IP statistics.
clear tcp statistics
Clears TCP statistics.
show udp statistics
Displays UDP statistics.
debug registry
To turn on the debugging output for registry events or errors when Cisco IOS Software Modularity software is running, use the debug registry command in privileged EXEC mode. To turn off debugging output, use the no form of this command or the undebug command.
debug registry {events | errors} [process-name | pid]
no debug registry {events | errors} [process-name | pid]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the debug registry command to troubleshoot Software Modularity registry operations.
CautionUse any debugging command with caution because the volume of generated output can slow or stop the router operations. We recommend that this command be used only under the supervision of a Cisco engineer.
Examples
The following example turns on debugging messages for Software Modularity registry events for the TCP process:
Router# debug registry events tcp.procDebug registry events debugging is onThe following example turns on debugging messages for Software Modularity registry errors:
Router# debug registry errorsDebug registry errors debugging is onexception core
To set or change the core dump options for a Cisco IOS Software Modularity process, use the exception core command in global configuration mode. To reset the core dump options to their default settings, use the no form of this command.
exception core process-name {{off | mainmem | mainmem-sharedmem | mainmem-text | mainmem-text-sharedmem | sharedmem [maxcore value]}| maxcore value}
no exception core process-name
Syntax Description
Command Default
Default core dump options are set for a process.
Command Modes
Global configuration (config)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Core dumps are taken when every process crashes. Each Cisco IOS Software Modularity software component has an associated .startup file that determines the core dump options (and other attributes) of that process. Use the show processes detailed command to display the core dump options for a process. Use the exception core command to override the default values set in the .startup file for the specific software component.
Note
Examples
In the following example, the maximum number of core dumps for all instances of the Cisco Discovery Protocol (CDP) process is set to 100. The command also limits the core dump output to the main memory text segments.
configure terminalexception core cdp2.proc mainmem-text maxcore 100Related Commands
exception flash
Configures the dump location for core files when a process reloads.
show processes detailed
Displays detailed process information.
exception core-file
To specify the name of the core dump file in Cisco IOS or Cisco IOS Software Modularity software, use the exception core-file command in global configuration mode. To return to the default core filename, use the no form of this command.
Cisco IOS Software
exception core-file filename
no exception core-file
Cisco IOS Software Modularity
exception core-file [filename] [limit upper-limit] [compress] [timestamp]
no exception core-file
Syntax Description
Command Default
Cisco IOS Software: The core file is named hostname-core, where hostname is the name of the router.
Cisco IOS Software Modularity: The core file is named using the name of the process that is being dumped.Command Modes
Global configuration (config)
Command History
10.2
This command was introduced.
12.2(18)SXF4
The limit, compress, and timestamp keywords were added to support Software Modularity images.
Usage Guidelines
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the router's memory is larger than 16 MB, the whole core file will not be copied to the server. Therefore, use rcp or FTP to dump the core file. The network dump is not supported in Software Modularity images.
Caution
Examples
Cisco IOS Software
In the following example, the router is configured to use FTP to dump a core file named dumpfile to the FTP server at 172.17.92.2 when the router crashes:
ip ftp username redip ftp password blueexception protocol ftpexception dump 172.17.92.2exception core-file dumpfileCisco IOS Software Modularity
In the following example, the router is configured to dump the main memory used by the TCP process to a file named dump-tcp when the TCP process crashes. The dump file is configured with an upper limit of 20, to be compressed, and to have a time stamp applied.
exception core tcp.proc mainmemexception core-file dump-tcp limit 20 compress timestamp
Note
Related Commands
exception crashinfo buffersize
To change the size of the buffer used for crashinfo files, use the exception crashinfo buffersize command in global configuration mode. To revert to the default buffer size, use the no form of this command.
exception crashinfo buffersize kilobytes
no exception crashinfo buffersize kilobytes
Syntax Description
Command Default
Crashinfo buffer is 32 KB.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The crashinfo file saves information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The device writes the crash information to the console at the time of the failure, and the file is created the next time you boot the Cisco IOS image after the failure (instead of while the system is failing).
Note
Examples
In the following example, the crashinfo buffer is set to 100 KB:
Router(config)# exception crashinfo buffersize 100Related Commands
exception crashinfo file
Enables the creation of a diagnostic file at the time of unexpected system shutdowns.
exception flash
To set the local dump location for core files when a process reloads, use the exception flash command in global configuration mode.
exception flash device-name
no exception flash device-name
Syntax Description
Command Default
No core dump location is set for a process.
Command Modes
Global configuration (config)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Core dumps are taken when every process crashes. You can configure up to three destinations, and the order in which the dump locations are used follows the order in which the destinations are configured.
Each Cisco IOS Software Modularity component has an associated .startup file that determines the core dump options (and other attributes) of that process. Use the show processes detailed command to display the core dump options for a process. Use the exception core command to override the default values set in the .startup file for the specific software component.
Caution
Examples
In the following example, three dump locations are configured:
configure terminalexception flash disk1:exception flash bootflash:exception flash sup-bootdisk:Related Commands
exception kernel
To configure a networking device to dump the kernel memory, use the exception kernel command in global configuration mode. To turn off the kernel dump facility, use the no form of this command.
exception kernel [filename filename] filepath path [memory kernel]
no exception kernel
Syntax Description
Command Default
No kernel memory is dumped.
Command Modes
Global configuration (config)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the exception kernel command to dump kernel memory when the kernel reloads. Please note that this is different from process dump, in which a process on the networking device reloads, but not the networking device itself. This command is used to configure where and what to dump. If the dump is to bootflash:, this command is all that is required.
For distributed networking devices, the line card number is added to the default name assigned to the kernel core dump file. For example, the default kernel core dump file for the line card in slot 6 would be kernel_core6.Z.
Caution
Examples
The following example writes kernel exceptions to the disk0:/core directory. Only kernel memory is dumped, and because no filename is specified, the kernel core dump file is given the default name kernel_core.z.
configure terminalexception kernel filepath /disk0:/core memory kernelinstall activate
To activate the current pending change set, use the install activate command in privileged EXEC mode.
install activate search-root-directory [reload]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
12.2(33)SXI1
The reload keyword was added.
Usage Guidelines
Use the install activate command after a patch file or maintenance pack (MP) has been installed. The state of files in the pending change set will change depending on whether a reload is required. By using the optional reload keyword with this command, you can speed up the activation process.
Cisco IOS Software Modularity introduces the concept of installed software that is different from just booting an image on the networking device. Cisco IOS Software Modularity images can be saved into the flash file system and booted like a Cisco IOS image, but this is referred to as uninstalled software. To gain the benefits of the Cisco IOS Software Modularity Installer and permit patch files to be installed, use the install file command to write the software to flash. Installation and activation are now separate processes. The install bind command is used to bind Cisco IOS Software Modularity base images system-wide; and the install activate command must be entered to activate a patch. Some patches will require a reload to be performed, and a message appears on the console after the install activate command has been entered to note the current state of the patch.
Table 5 shows whether the patch code is running in the various patch states. For more details about activating a patch, including a flowchart of the various patch states, see the "Cisco IOS Software Modularity Installation and Configuration" module.
Examples
The following example shows how to activate the current pending change set for the sys directory:
Router# install activate disk0:/sysRelated Commands
install bind
Binds Cisco IOS Software Modularity images.
install file
Installs base system files and patches.
install bind
To bind a Cisco IOS Software Modularity image system-wide, use the install bind command in global configuration mode. To remove the Software Modularity binding, use the no form of this command.
install bind search-root-directory [prepend]
no install bind
Syntax Description
Command Default
The Cisco IOS Software Modularity image is not bound.
Command Modes
Global configuration (config)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
12.2(33)SXI1
The prepend keyword was added.
Usage Guidelines
The install bind command generates a boot system command, but the install bind command is not inserted into the configuration. The benefit of using the install bind command is that you just specify the search root directory, which is the destination directory used in the install file command, and the Cisco IOS Software Modularity software will determine the directory structure and image file. If you use the boot system command, you must enter the complete directory path and image name.
Each instance of the boot system command generated by an install bind command is saved in the configuration file in the order in which it was configured, which is the normal behavior for boot system commands. To configure a system to have the newly installed Software Modularity image as the primary image to boot, you must remove all previous boot system commands in the configuration and enter them in the order in which you want them to run. You can use the optional prepend keyword to automatically move the latest boot system command to the top of the boot variable, thereby making it the primary image to boot. By using the prepend keyword, you avoid the extra steps of first removing all previous boot system commands and then reentering them to ensure that the latest installed image is the primary image. Alternatively, you can download the startup configuration to a text file, insert the new install bind or boot system command, and copy the changes back into the startup configuration.
To remove all boot system commands from the configuration file, use the no form of the boot system command without any arguments. Using the no form of the install bind command will remove only the boot system commands for installed software and leave other boot system commands intact.
Note
Examples
The following example shows how to remove all existing boot system commands and to bind the Software Modularity image in the directory named sys:
Router# configure terminalRouter(config)# no boot systemRouter(config)# install bind disk0:/sysRouter(config)# exitRouter# copy running-config startup-configRelated Commands
boot system
Specifies the system image that the router loads at startup.
install file
Installs base system files and patches.
install clear
To remove an entire installed software system, use the install clear command in privileged EXEC mode.
install clear search-root-directory
Syntax Description
search-root-directory
Local directory specified in the destination-directory argument of a previously executed install file command. Valid root directories are /sys, /oldsys, and /newsys.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the install clear command with caution because the command cannot be reversed. After an installation is cleared, it cannot be undone. Software that is currently running or that has been bound to run cannot be cleared. For bound software, you must remove the binding with the no install bind command before using the install clear command.
Examples
The following example shows how to clear the system installed in the local directory named sys:
Router# install clear disk0:/sysRelated Commands
install bind
Binds Cisco IOS Software Modularity images.
install file
Installs base system files and patches.
install commit
To define a tag name for a set of Cisco IOS Software Modularity software installed in the destination directory of a previously executed install file command, use the install commit command in privileged EXEC mode.
install commit search-root-directory tag-name
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
This command creates a point to which a user can roll back a system after a patch is installed that is considered unsatisfactory. The tag-name argument provides a name for the point. A tag name must be unique to the local file system.
Use the install prune command to remove a previously defined tag from the installed software.
Examples
The following example shows how to define a tag named tag1 to identify the software installed in the local directory named sys:
Router# install commit disk0:/sys tag1Related Commands
install copy
To make a copy of the Cisco IOS Software Modularity software, use the install copy command in privileged EXEC mode.
install copy source-root-directory destination-root-directory
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the install copy command to duplicate the Cisco IOS Software Modularity software at the source directory and place it at the destination directory. Both the source and destination directories must be local to the device.
Examples
The following example shows how to copy the software in the directory named sys into a directory named oldsys:
Router# install copy disk0:/sys disk0:/oldsysRelated Commands
install file
To install Cisco IOS Software Modularity base system files and patches, use the install file command in privileged EXEC mode.
install file source-file-url destination-directory [second-destination-directory] [interactive]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
12.2(33)SXI1
The optional second-destination-directory argument was added.
Usage Guidelines
Cisco IOS Software Modularity introduces the concept of installed software that is different from just booting an image on the networking device. Cisco IOS Software Modularity images can be saved into the flash file system and booted like a Cisco IOS image, but this is referred to as uninstalled software. To gain the benefits of the Cisco IOS Software Modularity Installer and permit patch files to be installed, use the install file command to write the software to local storage. Installation and activation are now separate processes; and the install activate command must be entered to activate patches. Some patches will require a reload to be performed, and a message appears on the console after the install activate command has been entered to note the current state of the patch.
Use the optional second-destination-directory argument to install an image or patch to more than one destination directory. With the current ION installation process, if an image or patch needs to be installed to more than one location, such as on a High Availability (HA) system, the install file command must be run separately. By using the second-destination-directory argument, the installation process repeats for a second location, thereby helping to reduce waiting time.
Use the optional interactive keyword to display more detailed output during the installation. Messages indicating current tasks that are being performed during the installation may be displayed. The default output is a series of ! characters to indicate progress and a message at the end indicating success or failure.
Use the show install command to display information about the currently installed software. Use the install clear command to remove an entire installed software system, or use the install rollback command to remove specific patches installed on top of the software version.
Examples
The following example shows how to install two different files from two different paths into the same local directory:
Router# install file tftp://username@hostname//directory/c6kpatch-vz disk0:/sysRouter# install file rcp://s72033/base/s72033-adventerprisek9_wan_dbg-vz disk0:/sysRelated Commands
install move
To move the Cisco IOS Software Modularity software from a source URL to a destination URL, use the install move command in privileged EXEC mode.
install move source-root-directory destination-root-directory
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the install move command to copy the Cisco IOS Software Modularity software from a source directory to a destination directory and then remove the software from the source directory. Both the source and destination directories must be local.
Examples
The following example shows how to move the software from the directory named /sys to the directory named /oldsys. The software will be removed from the /sys directory.
Router# install move disk0:/sys disk0:/oldsysRelated Commands
install prune
To remove a tag or unused files from the software that is installed in the destination directory specified in a previously executed install file command, use the install prune command in privileged EXEC mode.
install prune search-root-directory tag-name [files]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
12.2(18)SXF8
The files keyword was added.
Usage Guidelines
In addition to removing the tag from the installed software, the install prune command removes any files that are no longer required by the system as a result of the tag removal. After this command is executed, rollback can be performed to any previously installed tag.
When this command is executed using the optional files keyword, all of the tags from the base image to the tag specified are removed except for the specified tag. After this command is entered with the optional files keyword, rollback cannot be done to any tag beyond the specified tag; rollback can be performed to the base image only.
Examples
The following example shows how to remove the tag named tag1 from the installed software.
Router# install prune disk0:/sys tag1The following example shows how to remove all of the tags from the base image up to tag1. Tag1 is not removed.
Router# install prune disk0:/sys tag1 filesRelated Commands
install commit
Defines a tag for a set of software installed by the install file command.
install file
Installs base system files and patches.
install repackage
To create an installation or backup installable file from an installed system when a Cisco IOS Software Modularity image is running, use the install repackage command in privileged EXEC mode.
install repackage source-root-directory destination-file-url [compress]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
To allow for easier deployment of a base image and several patches to multiple routers, an installable bundled image, referred to as a repackage, can be replicated. Use the install repackage command to generate a installable file from an installed system. The installable file can be used in an installation on another device or as a backup installation for the current device. While the image is being replicated, the Software Modularity Installer saves everything in the installed state including rollback tags. An initial boot must be performed on the device on which the replicated image is to be installed. The ability to create a repackage allows standard installations to be performed across the network and saves installation time.
Examples
The following example shows how to create an installation or backup file named s72033-finance-vm.repackage from an installed system:
Router# install repackage disk0:/sys disk0:/s72033-finance-vm.repackageRelated Commands
install rollback
To roll back the installed Cisco IOS Software Modularity software to the point at which a tag was defined, use the install rollback command in privileged EXEC mode.
install rollback search-root-directory tag-name
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Similar to the idea of a database rollback, Cisco IOS Software Modularity images can roll back to a set of installed files defined by a tag. The installed system is captured at a point in time by defining a tag using the install commit command. If a subsequent installation of a patch file adversely affects the installed system, a rollback can be performed using the defined tag. The install activate command must be entered after the install rollback command to activate the rollback. All installation actions performed since the tag was defined are deleted, and the processes affected by the rollback of installed software are restarted after the rollback is activated. After the restart, these processes use the software that was present at the time the tag was created. Tags can be deleted, and the system will remove all installation files that will now never be used because the tag has been removed.
Examples
The following example shows how to roll back the software to the time that tag1 was defined and then restart all the affected processes. The tag named tag1 is assumed to have been created using the install commit command in an earlier configuration.
Router# install rollback disk0:/sys tag1Router# install activate disk0:/sysRelated Commands
process restart
To terminate and restart a process when a Cisco IOS Software Modularity image is running, use the process restart command in privileged EXEC mode.
process restart process-name [:instance-id] [cold]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The process restart command can be used to restart a newly installed version of an executable. Under special circumstances, it can also be used to restart a process that is operating in suboptimal mode. Only processes that are controlled by the System Manager can be restarted.
When restarting, a process will retrieve the previous state information from the saved configuration checkpoint. A cold restart means that the process will delete the previous state information from the saved configuration checkpoint.
If the process restart command is entered without first saving the active running configuration session and checkpointing the configuration changes, the changes could be lost. The following console warning about this possible configuration loss is displayed:
Some config has not yet been checkpointed and may be lost. It is recommended to do a `write checkpoint' to checkpoint the config and re-start the process. Do you want tocontinue ? [no]:If you restart the process, a message similar to the following is displayed:
Restarting process iprouting.iosproc02:51:21: %kern-6-SYSLOG_GEN: <30>:02:51:21:;1144354584.745:sysmgr.proc[72]: Some config for process iprouting.iosproc:1 has not yet beencheckpointed and may be lostTo checkpoint the configuration, use the write checkpoint command. Some commands also checkpoint internally upon being entered, such as the write memory command, the copy running-config startup-config command and the show running-config command.
In Software Modularity, you cannot restart a process on the standby router. The standby router console is disabled by default. If you enable the standby router console, and then enter the process restart command to restart a process, the standby console will reload and display one of the following error messages:
Standby process exited, rebooting.or
This process is not known to sysmgr.Examples
The following example restarts the Cisco Discovery Protocol (CDP) process:
Router# process restart cdp2.iosprocRelated Commands
process start
To initiate (spawn) a foreground or background POSIX process when a Cisco IOS Software Modularity image is running, use the process start command in privileged EXEC mode.
process start path/process-name [argument-1...argument-n] [&]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
The process start command is used to control POSIX processes and processes that are registered with sysmgr by using .startup and .init files. To terminate a POSIX process that is running in the foreground, use the Ctrl-C (^C) keyboard sequence.
Output for processes that are running in the foreground is directed to the tty (including Telnet) that initiates the command. Output for processes that are running in the background is directed only to the console.
Examples
The following example initiates a POSIX process to run in the background:
Router# process start disk0:/sbin/process1 &Related Commands
process stop
Terminates a process when running a Cisco IOS Software Modularity image without restarting the process.
process stop
To terminate a process without restarting the process when a Cisco IOS Software Modularity image is running, use the process stop command in privileged EXEC mode.
process stop process-name [:instance-id]
Syntax Description
Command Default
After a process is terminated, the process is restarted.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the process stop command to shut down (terminate) the specified process and any simultaneously executing copies. The process is not restarted, even if it had a respawn option specified.
Note
Examples
The following example shuts down all instances of the POSIX process named process1:
Router# process stop process1Related Commands
service checkpoint-config
To enable implicit configuration checkpointing when a Cisco IOS Software Modularity image is running, use the service checkpoint-config command in global configuration mode. To return to the default setting, use the no form of this command.
service checkpoint-config
no service checkpoint-config
Syntax Description
This command has no arguments or keywords.
Command Default
Implicit configuration checkpointing is disabled.
Command Modes
Global configuration (config)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
12.2(33)SXH
Automatic configuration checkpointing is disabled by default.
Usage Guidelines
Implicit configuration checkpointing means that configuration checkpointing occurs for all processes. A Software Modularity process can be restarted under an error condition or after upgrading. When the process is restarted and operational, the state of the process returns to the state the process was in prior to the restart. The software checkpoints the configuration information and when the process restarts, the configuration information is read from the checkpoint.
Configuration checkpoint information is implicitly generated as follows:
•
•
•
If you have a large configuration file, the default configuration checkpoint process may take some time to complete and prevent you from entering other CLI commands to save or display the configuration.
In Cisco IOS Release 12.2(18)SXF4, the checkpoint process is enabled by default. To disable the checkpoint process, enter the no form of the service checkpoint-config command. When you are ready to run the configuration checkpoint process, use the write checkpoint command to run the configuration checkpoint process.
In Cisco IOS Release 12.2(33)SXH, the default setting was changed to no service checkpoint-config, which means the checkpoint process is diabled by default. To enable the checkpoint process in this release, use the service checkpoint-config command.
Examples
In the following example for Cisco IOS Release 12.2(18)SXF4, the no form of the service checkpoint-config command is entered to disable the configuration checkpoint process, configuration commands are entered, and after exiting from the configuration mode the write checkpoint command is entered to run the configuration checkpoint process.
configure terminalno service checkpoint-config!! Configuration commands are entered.endwrite checkpointRelated Commands
write checkpoint
Runs the configuration checkpoint process when a Cisco IOS Software Modularity image is running.
show buffers
To display statistics for the buffer pools on the network server when Cisco IOS or Cisco IOS Software Modularity images are running, use the show buffers command in user EXEC or privileged EXEC mode.
show buffers [{address hex-address | failures | pool pool-name | processes | {all | assigned [process-id] | free | old | input-interface interface-type interface-number} [pool pool-name]} [dump | header | packet]]
Syntax Description
Command Default
If no options are specified, all buffer pool information is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
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
The following is sample output from the show buffers command with no arguments, showing all buffer pool information:
Router# show buffersBuffer elements:398 in free list (500 max allowed)1266 hits, 0 misses, 0 createdPublic buffer pools:Small buffers, 104 bytes (total 50, permanent 50):50 in free list (20 min, 150 max allowed)551 hits, 0 misses, 0 trims, 0 createdMiddle buffers, 600 bytes (total 25, permanent 25):25 in free list (10 min, 150 max allowed)39 hits, 0 misses, 0 trims, 0 createdBig buffers, 1524 bytes (total 50, permanent 50):49 in free list (5 min, 150 max allowed)27 hits, 0 misses, 0 trims, 0 createdVeryBig buffers, 4520 bytes (total 10, permanent 10):10 in free list (0 min, 100 max allowed)0 hits, 0 misses, 0 trims, 0 createdLarge buffers, 5024 bytes (total 0, permanent 0):0 in free list (0 min, 10 max allowed)0 hits, 0 misses, 0 trims, 0 createdHuge buffers, 18024 bytes (total 0, permanent 0):0 in free list (0 min, 4 max allowed)0 hits, 0 misses, 0 trims, 0 createdInterface buffer pools:Ethernet0 buffers, 1524 bytes (total 64, permanent 64):16 in free list (0 min, 64 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cacheEthernet1 buffers, 1524 bytes (total 64, permanent 64):16 in free list (0 min, 64 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cacheSerial0 buffers, 1524 bytes (total 64, permanent 64):16 in free list (0 min, 64 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cacheSerial1 buffers, 1524 bytes (total 64, permanent 64):16 in free list (0 min, 64 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cacheTokenRing0 buffers, 4516 bytes (total 48, permanent 48):0 in free list (0 min, 48 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cacheTokenRing1 buffers, 4516 bytes (total 32, permanent 32):32 in free list (0 min, 48 max allowed)16 hits, 0 fallbacks0 failures (0 no memory)The following is sample output from the show buffers command with no arguments, showing onlybuffer pool information for Huge buffers. This output shows a highest total of five Huge buffers created five days and 18 hours before the command was issued.
Router# show buffersHuge buffers, 18024 bytes (total 5, permanent 0, peak 5 @ 5d18h): 4 in free list (3 min, 104 max allowed) 0 hits, 1 misses, 101 trims, 106 created 0 failures (0 no memory)The following is sample output from the show buffers command with no arguments, showing only buffer pool information for Huge buffers. This output shows a highest total of 184 Huge buffers created one hour, one minute, and 15 seconds before the command was issued.
Router# show buffersHuge buffers, 65280 bytes (total 4, permanent 2, peak 184 @ 01:01:15):4 in free list (0 min, 4 max allowed)32521 hits, 143636 misses, 14668 trims, 14670 created143554 failures (0 no memory)The following is sample output from the show buffers command with an interface type and interface number:
Router# show buffers Ethernet 0Ethernet0 buffers, 1524 bytes (total 64, permanent 64):16 in free list (0 min, 64 max allowed)48 hits, 0 fallbacks16 max cache size, 16 in cache
Table 6 describes the significant fields shown in the display.
Cisco IOS Software Modularity
The following is sample output from the show buffers command using a Cisco IOS Modularity image from Cisco IOS Release 12.2(18)SXF4 and later releases. Two new output fields were introduced—Public buffer heads and Temporary buffer heads—and are shown within comments in the following sample output.
Router# show buffersBuffer elements:500 in free list (500 max allowed)106586 hits, 0 misses, 0 createdPublic buffer pools:Small buffers, 104 bytes (total 50, permanent 50, peak 54 @ 1d13h):49 in free list (20 min, 150 max allowed)54486 hits, 0 misses, 4 trims, 4 created0 failures (0 no memory)Middle buffers, 600 bytes (total 25, permanent 25, peak 27 @ 1d13h):25 in free list (10 min, 150 max allowed)20 hits, 0 misses, 2 trims, 2 created0 failures (0 no memory)Big buffers, 1536 bytes (total 50, permanent 50):50 in free list (40 min, 150 max allowed)6 hits, 0 misses, 0 trims, 0 created0 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 created0 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 created0 failures (0 no memory)Huge buffers, 18024 bytes (total 1, permanent 0, peak 1 @ 1d13h):0 in free list (0 min, 4 max allowed)1 hits, 0 misses, 0 trims, 0 created0 failures (0 no memory)! Start of Cisco IOS Software Modularity fieldsPublic buffer headers:Header buffers, 880 bytes (total 1000, peak 142 @ 1d13h):864 in permanent free list142 hits, 0 missesTemporary buffer headers:Header buffers, 896 bytes (total 0):0 in free list0 hits, 0 misses, 0 trims, 0 created0 failures! End of Cisco IOS Software Modularity fieldsInterface buffer pools:Logger Pool buffers, 600 bytes (total 150, permanent 150):150 in free list (150 min, 150 max allowed)22 hits, 0 missesTable 7 describes the significant fields shown in the display that are different from the fields in Table 6.
show exception
To display the current exception configuration when a Cisco IOS Software Modularity image is running, use the show exception command in user EXEC or privileged EXEC mode.
show exception
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
Use the show exception command to display the current process and kernel dumper configuration as configured by the various exception commands used in Software Modularity images.
Examples
The following is sample output from the show exception command:
Router# show exceptionCore Dump Configurations:Choice 1========Filepath : disk0:Filename : test1Lower Filename Suffix : 0Upper Filename Suffix : 4Current Filename Suffix : 0Compression : onChoice 2========Filepath : disk1:Filename : test1Lower Filename Suffix : 0Upper Filename Suffix : 4Current Filename Suffix : 0Compression : onChoice 3========Filepath : slot0Filename : test1Lower Filename Suffix : 0Upper Filename Suffix : 4Current Filename Suffix : 0Compression : onTable 8 describes the significant fields shown in the display.
Related Commands
show install
To display information about the installed Cisco IOS Software Modularity software, including patch files, use the show install command in user EXEC or privileged EXEC mode.
show install [tags] {running | search-root-directory} [tagname tag-name] [detailed | pending]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show install running command:
Router# show install runningSoftware running on card installed at location s72033 - Slot 5 :B/P C State Filename--- - -------- --------B Active disk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vm(12.2(99)SX1010)Software running on card installed at location s72033_rp - Slot 5 :B/P C State Filename--- - -------- --------P Active disk0:/sys/s72033_rp/patch/patch-AAA1258-patch-0-n.soSoftware running on card installed at location s72033 - Slot 6 :B/P C State Filename--- - -------- --------B Active slavedisk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vm(12.2(99)SX1010)LEGEND:-------:B/P/MP - (B)ase image, (P)atch, or (M)aintenance (P)ack'C' - (C)ommittedPruned - This file has been pruned from the systemActive - This file is active in the systemPendInst - This file is set to be made available to run on thesystem after next activation.PendRoll - This file is set to be rolled back after next activation.InstPRel - This file will run on the system after next reloadRollPRel - This file will be removed from the system after next reloadRPRPndIn - This file is both rolled back pending a reload, and pendinginstallation. On reload, this file will not run and will move toPendInst state. If 'install activate' is done before reload, pendingremoval and install cancel each other and file simply remains activeIPRPndRo - This file is both installed pending a reload, and pending rollback.If the card reloads, it will be active on the system pending a rollbackIf 'install activate' is done before a reload, the pending install andremoval with cancel each other and the file will simply be removedOccluded - This file has been occluded from the system,a newer version of itself has superceded it.Ignored - This file is ignored, is not consumed by target.Table 9 describes the significant fields shown in the display.
The following is sample output from the show install running command with the detailed keyword:
Router# show install running detailedSoftware running on card installed at location s72033 - Slot 5 :Base image : disk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vmVersion : 12.2(99)SX1010File state: Active File Checksum : 8BB2F966EA945E8E25010A1BAC7205C3DFBCA197Date Installed : 19:51:22 UTC Sep 8 2005 Commit Tags : baseSoftware running on card installed at location s72033_rp - Slot 5 :Base image : disk0:/sys/s72033_rp/base/DRACO2_MPFile state: Active File Checksum : 48849DBB2E47A8C55AC68CF3F6EE747B054CD392Date Installed : 19:49:06 UTC Sep 8 2005 Commit Tags : baseSoftware running on card installed at location s72033 - Slot 6 :Base image : slavedisk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vmVersion : 12.2(99)SX1010File state: Active File Checksum : 8BB2F966EA945E8E25010A1BAC7205C3DFBCA197Date Installed : 19:32:21 UTC Sep 8 2005 Commit Tags : base Patch : slavedisk0:/sys/s72033/patch/patch-AAA1258-patch-0-n.soFile state: PendInst File Checksum : A129339A6A3ED1F8B92D6992AD1BE67C716E4430Date Installed : 20:31:01 UTC Sep 9 2005 Commit Tags : NONE Maintenance Pack : MA0005Table 10 describes the significant fields shown in the display.
In the following example, the show install privileged EXEC command is used to display information about the tags that are defined for this system:
Router# show install tags runningTags defined over software running on location s72033 - Slot 5 :Tagname # of Files Date Committed-------------------- ---------- ------------------------base 1 20:08:51 UTC Sep 9 2005MA0005 1 20:34:16 UTC Sep 9 2005Tags defined over software running on location s72033_rp - Slot 5 :Tagname # of Files Date Committed-------------------- ---------- ------------------------base 1 20:08:51 UTC Sep 9 2005MA0005 1 20:34:16 UTC Sep 9 2005Tags defined over software running on location s72033 - Slot 6 :Tagname # of Files Date Committed-------------------- ---------- ------------------------base 1 20:28:54 UTC Sep 9 2005Table 11 describes the significant fields shown in the display.
In the following example, the show install privileged EXEC command is used to display detailed information about the tags that are defined for this system:
Router# show install tags running detailedTags defined over software running on location s72033 :Tag Name :baseDate Committed :Fri Sep 9 17:54:37 2005Files under this tag:disk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vmIn the following example, the show install privileged EXEC command is used to display detailed information about the tag named tag1:
Router# show install tags running tagname tag1 detailedTags defined over software running on location c7200:Tag Name : tag1Date Committed : 01:49:23 UTC Mar 8 2006Files under this tag: disk0:/sys/c7200/base/c7200-p-vmTable 12 describes the significant fields shown in the display.
Related Commands
show memory
To display statistics about memory when Cisco IOS or Cisco IOS software Modularity images are running, use the show memory command in user EXEC or privileged EXEC mode.
Cisco IOS Software
show memory [memory-type] [free] [overflow] [summary]
Cisco IOS Software Modularity
show memory
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Cisco IOS Software
The show memory command displays information about memory available after the system image decompresses and loads.
Cisco IOS Software Modularity
No optional keywords or arguments are supported for the show memory command when a Software Modularity image is running. To display details about PSOIX and Cisco IOS style system memory information when Software Modularity images are running, use the show memory detailed command.
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
The following is sample output from the show memory command:
Router# show memoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210036 2971860 2692456 2845368Processor memoryAddress Bytes Prev. Next Ref PrevF NextF Alloc PC WhatB0EE38 1056 0 B0F280 1 18F132 List ElementsB0F280 2656 B0EE38 B0FD08 1 18F132 List HeadersB0FD08 2520 B0F280 B10708 1 141384 TTY dataB10708 2000 B0FD08 B10F00 1 14353C TTY Input BufB10F00 512 B10708 B11128 1 14356C TTY Output BufB11128 2000 B10F00 B11920 1 1A110E Interrupt StackB11920 44 B11128 B11974 1 970DE8 *Init*B11974 1056 B11920 B11DBC 1 18F132 messagesB11DBC 84 B11974 B11E38 1 19ABCE Watched BooleanB11E38 84 B11DBC B11EB4 1 19ABCE Watched BooleanB11EB4 84 B11E38 B11F30 1 19ABCE Watched BooleanB11F30 84 B11EB4 B11FAC 1 19ABCE Watched BooleanThe following is sample output from the show memory free command:
Router# show memory freeHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210076 2971820 2692456 2845368Processor memoryAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What24 Free list 1CEB844 32 CEB7A4 CEB88C 0 0 0 96B894 SSE Manager52 Free list 272 Free list 376 Free list 480 Free list 5D35ED4 80 D35E30 D35F4C 0 0 D27AE8 96B894 SSE ManagerD27AE8 80 D27A48 D27B60 0 D35ED4 0 22585E SSE Manager88 Free list 6100 Free list 7D0A8F4 100 D0A8B0 D0A980 0 0 0 2258DA SSE Manager104 Free list 8B59EF0 108 B59E8C B59F84 0 0 0 2258DA (fragment)The output of the show memory free command contains the same types of information as the show memory output, except that only free memory is displayed, and the information is ordered by free list.
The first section of the display includes summary statistics about the activities of the system memory allocator. Table 13 describes the significant fields shown in the first section of the display.
The second section of the display is a block-by-block listing of memory use. Table 14 describes the significant fields shown in the second section of the display.
The show memory io command displays the free I/O memory blocks. On the Cisco 4000 router, this command quickly shows how much unused I/O memory is available.
The following is sample output from the show memory io command:
Router# show memory ioAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What6132DA0 59264 6132664 6141520 0 0 600DDEC 3FCF0 *Packet Buffer*600DDEC 500 600DA4C 600DFE0 0 6132DA0 600FE68 0600FE68 376 600FAC8 600FFE0 0 600DDEC 6011D54 06011D54 652 60119B4 6011FEO 0 600FE68 6013D54 0614FCA0 832 614F564 614FFE0 0 601FD54 6177640 06177640 2657056 6172E90 0 0 614FCA0 0 0Total: 2723244The following example displays details of a memory block overflow correction when the exception memory ignore overflow global configuration command is configured:
Router# show memory overflowCount Buffer Count Last corrected Crashinfo files1 1 00:11:17 slot0:crashinfo_20030620-075755Traceback 607D526C 608731A0 607172F8 607288E0 607A5688 607A566CThe report includes the amount of time since the last correction was made and the name of the file that logged the memory block overflow details.
The show memory sram command displays the free SRAM memory blocks. For the Cisco 4000 router, this command supports the high-speed static RAM memory pool to make it easier for you to debug or diagnose problems with allocation or freeing of such memory.
The following is sample output from the show memory sram command:
Router# show memory sramAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What7AE0 38178 72F0 0 0 0 0 0Total 38178The following example of the show memory command used on the Cisco 4000 router includes information about SRAM memory and I/O memory:
Router# show memoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 49C724 28719324 1510864 27208460 26511644 15513908I/O 6000000 4194304 1297088 2897216 2869248 2896812SRAM 1000 65536 63400 2136 2136 2136Address Bytes Prev. Next Ref PrevF NextF Alloc PC What1000 2032 0 17F0 1 3E73E *Init*17F0 2032 1000 1FE0 1 3E73E *Init*1FE0 544 17F0 2200 1 3276A *Init*2200 52 1FE0 2234 1 31D68 *Init*2234 52 2200 2268 1 31DAA *Init*2268 52 2234 229C 1 31DF2 *Init*72F0 2032 6E5C 7AE0 1 3E73E Init7AE0 38178 72F0 0 0 0 0 0The show memory summary command displays a summary of all memory pools and memory usage per Alloc PC (address of the system call that allocated the block).
The following is a partial sample output from the show memory summary command. This output shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see Table 13 and Table 14.
Router# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210216 2971680 2692456 2845368Processor memoryAlloc PC Size Blocks Bytes What0x2AB2 192 1 192 IDB: Serial Info0x70EC 92 2 184 Init0xC916 128 50 6400 RIF Cache0x76ADE 4500 1 4500 XDI data0x76E84 4464 1 4464 XDI data0x76EAC 692 1 692 XDI data0x77764 408 1 408 Init0x77776 116 1 116 Init0x777A2 408 1 408 Init0x777B2 116 1 116 Init0xA4600 24 3 72 List0xD9B5C 52 1 52 SSE Manager...0x0 0 3413 2072576 Pool Summary0x0 0 28 2971680 Pool Summary (Free Blocks)0x0 40 3441 137640 Pool Summary (All Block Headers)0x0 0 3413 2072576 Memory Summary0x0 0 28 2971680 Memory Summary (Free Blocks)Cisco IOS Software Modularity
The following is sample output from the show memory command when a Cisco IOS Software Modularity image is running.
Router# show memorySystem Memory: 262144K total, 116148K used, 145996K free 4000K kernel reservedTable 15 describes the significant fields shown in the display.
Related Commands
show memory detailed
To display detailed memory information about POSIX and Cisco IOS processes when Cisco IOS Software Modularity images are running, use the show memory detailed command in privileged EXEC mode.
show memory detailed {process-id | process-name} [start-address [end-address] | bigger | free | statistics | summary]
Syntax Description
Command Default
No detailed memory information about POSIX and Cisco IOS processes is displayed.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
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
The following is partial sample output from the show memory detailed command for a Cisco IOS process:
Router# show memory detailed cdp2.iosprocSystem Memory: 131072K total, 115836K used, 15236K free 4000K kernel reservedProcess sbin/cdp2.iosproc, type IOS, PID = 12329636K total, 4K text, 4K data, 28K stack, 600K dynamic16384 heapsize, 3972 allocated, 10848 freeAddress Bytes What0x3B42000 4194304 Shared Memory0x7FBB000 8192 Program Stack0x8020000 49152 Program Text0x802C000 4096 Program Data0x802D000 8192 Allocated memory0x60000000 4096 Shared Memory "SHM_IDB"0x60001000 32768 Shared MemoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 8034058 508152 480420 27732 17368 18716Processor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what08034058 0000020008 00000000 08038EB8 001 -------- -------- 727FB668 Managed Chunk Queue Elements08038EB8 0000002568 08034058 080398F8 001 -------- -------- 72871A44 *Init*080398F8 0000001512 08038EB8 08039F18 001 -------- -------- 728819D4 List Elements...The first section of the display shows system summary information. Table 16 describes the significant fields shown in the first section of the display.
The second section of the display includes process summary statistics about the activities of the system memory allocator. Table 17 describes the significant fields shown in the second section of the display.
The third section of the display shows POSIX process perspective memory information. Table 18 describes the significant fields shown in the third section of the display.
The fourth section of the display shows Cisco IOS memory information as a block-by-block listing of memory use. Table 19 describes the significant fields shown in the fourth section of the display.
The following is sample output from the show memory detailed command for a POSIX process:
Router# show memory detailed 12290System Memory: 131072K total, 115876K used, 15196K free 4000K kernel reservedProcess sbin/sysmgr.proc, type POSIX, PID = 12290400K total, 100K text, 144K data, 12K stack, 144K dynamic81920 heapsize, 68716 allocated, 8824 freeAddress Bytes What0x7FDF000 126976 Program Stack (pages not allocated)0x7FFE000 4096 Program Stack0x8000000 122880 Program Stack (pages not allocated)0x801E000 8192 Program Stack0x8020000 102400 Program Text0x8039000 147456 Program Data0x805D000 8192 Heap Memory0x8060000 16384 Heap Memory0x8064000 16384 Heap Memory0x8068000 8192 Heap Memory0x806C000 16384 Heap Memory0x8070000 16384 Heap Memory0x8074000 16384 Heap Memory0x8078000 16384 Heap Memory0x807C000 16384 Heap Memory0x8080000 16384 Heap MemoryRelated Commands
show processes
To display information about the active Cisco IOS processes or the Cisco IOS Software Modularity POSIX-style processes, use the show processes command in privileged EXEC mode.
Cisco IOS Software
show processes [history | process-id]
Cisco IOS Software Modularity
show processes
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Cisco IOS Software Modularity
Although no optional keywords or arguments are supported for the base show processes command when a Software Modularity image is running, more details about processes are displayed using the show processes cpu, show processes detailed, show processes kernel, and show processes memory commands.
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
The following is sample output from the show processes command:
Router# show processesCPU utilization for five seconds: 21%/0%; one minute: 2%; five minutes: 2%PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process1 Cwe 606E9FCC 0 1 0 5600/6000 0 Chunk Manager2 Csp 607180F0 0 121055 0 2608/3000 0 Load Meter3 M* 0 8 90 88 9772/12000 0 Exec4 Mwe 619CB674 0 1 023512/24000 0 EDDRI_MAIN5 Lst 606F6AA4 82064 61496 1334 5668/6000 0 Check heaps6 Cwe 606FD444 0 127 0 5588/6000 0 Pool Manager7 Lwe 6060B364 0 1 0 5764/6000 0 AAA_SERVER_DEADT8 Mst 6063212C 0 2 0 5564/6000 0 Timers9 Mwe 600109D4 0 2 0 5560/6000 0 Serial Backgroun10 Mwe 60234848 0 2 0 5564/6000 0 ATM Idle Timer11 Mwe 602B75F0 0 2 0 8564/9000 0 ATM AutoVC Perio12 Mwe 602B7054 0 2 0 5560/6000 0 ATM VC Auto Crea13 Mwe 606068B8 0 2 0 5552/6000 0 AAA high-capacit14 Msi 607BABA4 251264 605013 415 5628/6000 0 EnvMon15 Mwe 607BFF8C 0 1 0 8600/9000 0 OIR Handler16 Mwe 607D407C 0 10089 0 5676/6000 0 IPC Dynamic Cach17 Mwe 607CD03C 0 1 0 5632/6000 0 IPC Zone Manager18 Mwe 607CCD80 0 605014 0 5708/6000 0 IPC Periodic Tim19 Mwe 607CCD24 0 605014 0 5704/6000 0 IPC Deferred Por20 Mwe 607CCE2C 0 1 0 5596/6000 0 IPC Seat ManagerTable 20 describes the fields shown in the display.
Note
For a list of process descriptions, see http://www.cisco.com/warp/public/63/showproc_cpu.html.
The following is sample output from the show processes history command:
Router# show processes historyPID Exectime(ms) Caller PC Process Name3 12 0x0 Exec16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs67 0 0x6015CD38 SMT input39 0 0x60178804 FBM Timer16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs67 0 0x6015CD38 SMT input39 0 0x60178804 FBM Timer24 0 0x60425070 Compute load avgs11 0 0x605210A8 ARP Input69 0 0x605FDAF4 DHCPD Database69 0 0x605FD568 DHCPD Database51 0 0x60670B3C IP Cache Ager69 0 0x605FD568 DHCPD Database36 0 0x606E96DC SSS Test Client69 0 0x605FD568 DHCPD Database--More--Table 21 describes the significant fields shown in the display.
The following is sample output from the show processes process-id command:
Router# show processes 6Process ID 6 [Pool Manager], TTY 0Memory usage [in bytes]Holding: 921148, Maximum: 940024, Allocated: 84431264, Freed: 99432136Getbufs: 0, Retbufs: 0, Stack: 12345/67890CPU usagePC: 0x60887600, Invoked: 188, Giveups: 100, uSec: 245Sec: 3.03%, 1Min: 2.98%, 5Min: 1.55%, Average: 0.58%,Age: 662314 msec, Runtime: 3841 msecState: Running, Priority: NormalTable 22 describes the fields shown in the display.
Cisco IOS Software Modularity
The following is sample output from the show processes command when a Cisco IOS Software Modularity image is running:
Router# show processesTotal CPU utilization for 5 seconds: 99.7%; 1 minute: 98.9%; 5 minutes: 86.5%PID TID Prio STATE Blocked Stack CPU Name1 1 0 Ready 0 (128K) 2m28s procnto-cisco1 2 63 Receive 1 0 (128K) 0.000 procnto-cisco1 3 10 Receive 1 0 (128K) 0.000 procnto-cisco1 4 11 Receive 1 0 (128K) 1.848 procnto-cisco1 5 63 Receive 1 0 (128K) 0.000 procnto-cisco1 6 63 Receive 1 0 (128K) 0.000 procnto-cisco12290 1 10 Receive 1 12288(128K) 0.080 chkptd.proc12290 2 10 Receive 8 12288(128K) 0.000 chkptd.proc3 1 15 Condvar 1027388 12288(128K) 0.016 qdelogger3 2 15 Receive 1 12288(128K) 0.004 qdelogger3 3 16 Condvar 1040024 12288(128K) 0.004 qdelogger4 1 10 Receive 1 4096 (128K) 0.016 devc-pty6 1 62 Receive 1 8192 (128K) 0.256 devc-ser26816 2 63 Intr 8192 (128K) 0.663 devc-ser26817 1 10 Receive 1 32768(128K) 0.080 dumper.proc7 2 10 Receive 1 32768(128K) 0.008 dumper.proc7 3 10 Receive 1 32768(128K) 0.000 dumper.proc7 4 10 Receive 1 32768(128K) 0.020 dumper.proc7 5 10 Receive 1 32768(128K) 0.008 dumper.proc4104 2 10 Receive 1 12288(128K) 0.000 pipe4104 3 10 Receive 1 12288(128K) 0.000 pipe8210 1 10 Nanosleep 8192 (128K) 0.040 watchdog.proc8211 1 10 Receive 1 16384(128K) 0.044 syslogd.proc8211 2 10 Receive 7 16384(128K) 0.000 syslogd.proc8211 3 10 Sigwaitin 16384(128K) 0.000 syslogd.proc8212 2 10 Receive 1 24576(128K) 0.024 name_svr.proc8212 3 10 Receive 1 24576(128K) 0.100 name_svr.proc8212 4 10 Receive 1 24576(128K) 0.340 name_svr.proc8212 5 10 Receive 1 24576(128K) 0.304 name_svr.proc8213 1 10 Receive 1 24576(128K) 0.644 wdsysmon.proc8213 2 10 Receive 5 24576(128K) 0.052 wdsysmon.proc8213 3 10 Receive 10 24576(128K) 0.004 wdsysmon.proc8213 4 63 Nanosleep 24576(128K) 0.000 wdsysmon.proc8214 1 10 Receive 1 94208(128K) 0.132 sysmgr.proc8214 2 10 Sigwaitin 94208(128K) 0.000 sysmgr.proc8214 3 10 Receive 8 94208(128K) 0.004 sysmgr.proc8214 4 10 Receive 1 94208(128K) 0.000 sysmgr.proc8214 5 10 Receive 1 94208(128K) 0.000 sysmgr.proc8214 6 10 Receive 1 94208(128K) 0.004 sysmgr.proc8214 7 10 Receive 1 94208(128K) 0.000 sysmgr.proc8214 8 10 Receive 1 94208(128K) 0.000 sysmgr.proc8214 9 10 Receive 1 94208(128K) 0.000 sysmgr.proc8214 10 10 Receive 1 94208(128K) 0.000 sysmgr.proc12317 1 10 Receive 23 73728(128K) 2.212 ios-base12317 2 10 Receive 1 73728(128K) 0.064 ios-base12317 3 10 Reply 1 73728(128K) 17.800 ios-base12317 4 11 Nanosleep 73728(128K) 0.000 ios-base12317 5 10 Receive 1 73728(128K) 21.108 ios-base12317 6 45 Intr 73728(128K) 0.000 ios-base12317 7 35 Intr 73728(128K) 0.064 ios-base12317 8 10 Reply 12336 73728(128K) 0.776 ios-base12317 9 10 Receive 1 73728(128K) 12.608 ios-base12317 10 25 Intr 73728(128K) 26.404 ios-base12317 11 25 Intr 73728(128K) 0.088 ios-base12317 12 45 Intr 73728(128K) 0.000 ios-base12317 13 10 Receive 1 73728(128K) 6.456 ios-base12317 14 20 Reply 6 73728(128K) 0.064 ios-base12317 15 10 Receive 1 73728(128K) 8.064 ios-base12324 1 10 Receive 1 40960(128K) 73.088 iprouting.iosproc12324 2 10 Ready 40960(128K) 32.552 iprouting.iosproc12324 4 11 Nanosleep 40960(128K) 0.000 iprouting.iosproc12324 5 10 Receive 1 40960(128K) 4.312 iprouting.iosproc12324 6 10 Receive 1 40960(128K) 6.988 iprouting.iosproc12324 7 10 Reply 1 40960(128K) 41.108 iprouting.iosproc12324 8 10 Receive 1 40960(128K) 0.032 iprouting.iosproc12324 9 10 Reply 1 40960(128K) 0.332 iprouting.iosproc12330 1 10 Receive 1 36864(128K) 0.000 cdp2.iosproc12330 2 10 Receive 1 36864(128K) 0.004 cdp2.iosproc12330 3 10 Receive 1 36864(128K) 0.024 cdp2.iosproc12330 4 11 Nanosleep 36864(128K) 0.000 cdp2.iosproc12330 5 10 Reply 1 36864(128K) 0.228 cdp2.iosproc12330 6 10 Receive 1 36864(128K) 0.000 cdp2.iosproc12330 7 10 Receive 9 36864(128K) 0.000 cdp2.iosproc12334 1 10 Receive 1 45056(128K) 0.000 inetd.proc12334 2 10 Sigwaitin 45056(128K) 0.000 inetd.proc12334 3 10 Receive 1 45056(128K) 0.000 inetd.proc12334 4 10 Receive 1 45056(128K) 0.020 inetd.proc12334 5 10 Receive 1 45056(128K) 0.000 inetd.proc12335 1 10 Receive 1 118784(128K) 0.000 tcp.proc12335 2 10 Receive 1 118784(128K) 0.000 tcp.proc12335 3 10 Sigwaitin 118784(128K) 0.000 tcp.proc12335 4 10 Condvar 7A602080 118784(128K) 5.092 tcp.proc12335 5 10 Ready 118784(128K) 21.092 tcp.proc12335 6 10 Receive 1 118784(128K) 14.280 tcp.proc12335 7 10 Receive 1 118784(128K) 0.000 tcp.proc12336 1 10 Receive 1 53248(128K) 0.000 udp.proc12336 3 10 Sigwaitin 53248(128K) 0.000 udp.proc12336 4 10 Condvar 7A602080 53248(128K) 0.000 udp.proc12336 5 10 Receive 11 53248(128K) 0.072 udp.proc12336 6 10 Receive 1 53248(128K) 0.028 udp.proc12336 7 10 Receive 1 53248(128K) 0.000 udp.proc12336 8 10 Receive 1 53248(128K) 0.000 udp.procTable 23 describes the significant fields shown in the display.
Related Commands
show processes cpu
To display detailed CPU utilization statistics (CPU use per process) when Cisco IOS or Cisco IOS Software Modularity images are running, use the show processes cpu command in privileged EXEC mode.
Cisco IOS Software
show processes cpu [history | sorted]
Cisco IOS Software Modularity
show processes cpu [detailed [process-id | process-name] | history]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Cisco IOS Software
If you use the optional history keyword, three graphs are displayed for Cisco IOS images:
•
•
•
Maximum usage is measured and recorded every second; average usage is calculated on periods of more than one second. Consistently high CPU utilization over an extended period of time indicates a problem and using the show processes cpu command is useful for troubleshooting. Also, you can use the output of this command in the Cisco Output Interpreter tool to display potential issues and fixes. Output Interpreter is available to registered users of Cisco.com who are logged in and have Java Script enabled.
For a list of system processes, go to http://www.cisco.com/warp/public/63/showproc_cpu.html.
Cisco IOS Software Modularity
Cisco IOS Software Modularity images display only one graph that shows the CPU utilization for the last 60 minutes. The horizontal axis shows times (for example, 0, 5, 10, 15 minutes), and the vertical axis shows total percentage of CPU utilization (0 to 100 percent).
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software images. To view the appropriate output, choose one of the following sections:
•
Cisco IOS Software
The following is sample output from the show processes cpu command without keywords:
Router# show processes cpuCPU utilization for five seconds: 5%/2%; one minute: 3%; five minutes: 2%PID Runtime (ms) Invoked uSecs 5Sec 1Min 5Min TTY Process1 1736 58 29931 0% 0% 0% 0 Check heaps2 68 585 116 1.00% 1.00% 0% 0 IP Input3 0 744 0 0% 0% 0% 0 TCP Timer4 0 2 0 0% 0% 0% 0 TCP Protocols5 0 1 0 0% 0% 0% 0 BOOTP Server6 16 130 123 0% 0% 0% 0 ARP Input7 0 1 0 0% 0% 0% 0 Probe Input8 0 7 0 0% 0% 0% 0 MOP Protocols9 0 2 0 0% 0% 0% 0 Timers10 692 64 10812 0% 0% 0% 0 Net Background11 0 5 0 0% 0% 0% 0 Logger12 0 38 0 0% 0% 0% 0 BGP Open13 0 1 0 0% 0% 0% 0 Net Input14 540 3466 155 0% 0% 0% 0 TTY Background15 0 1 0 0% 0% 0% 0 BGP I/O16 5100 1367 3730 0% 0% 0% 0 IGRP Router17 88 4232 20 0.20% 1.00% 0% 0 BGP Router18 152 14650 10 0% 0% 0% 0 BGP Scanner19 224 99 2262 0% 0% 1.00% 0 ExecThe following is sample output of the one-hour portion of the output. The Y-axis of the graph is the CPU utilization. The X-axis of the graph is the increment within the time period displayed in the graph. This example shows the individual minutes during the previous hour. The most recent measurement is on the left of the X-axis.
Router# show processes cpu history!--- One minute output omitted6665776865756676676666667667677676766666766767767666566667 63780161989935137097719914437323586899327408582696439226131009080 * * * * * * * *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 5CPU% per minute (last 60 minutes)* = maximum CPU% # = average CPU%!--- 72-hour output omittedThe top two rows, read vertically, display the highest percentage of CPU utilization recorded during the time increment. In this example, the CPU utilization for the last minute recorded is 66 percent. The device may have reached 66 percent only once during that minute, or it may have reached 66 percent multiple times. The device records only the peak reached during the time increment and the average over the course of that increment.
The following is sample output from the show processes cpu command that shows an ARP probe process:
Router# show processes cpu | include ARP17 38140 389690 97 0.00% 0.00% 0.00% 0 ARP Input36 0 1 0 0.00% 0.00% 0.00% 0 IP ARP Probe40 0 1 0 0.00% 0.00% 0.00% 0 ATM ARP INPUT80 0 1 0 0.00% 0.00% 0.00% 0 RARP Input114 0 1 0 0.00% 0.00% 0.00% 0 FR ARPTable 24 describes the fields shown in the output.
Note
Cisco IOS Software Modularity
The following is sample output from the show processes cpu command when a Software Modularity image is running:
Router# show processes cpuTotal CPU utilization for 5 seconds: 99.6%; 1 minute: 98.5%; 5 minutes: 85.3%PID 5Sec 1Min 5Min Process1 0.0% 0.1% 0.8% kernel3 0.0% 0.0% 0.0% qdelogger4 0.0% 0.0% 0.0% devc-pty6 0.7% 0.2% 0.1% devc-ser26817 0.0% 0.0% 0.0% dumper.proc4104 0.0% 0.0% 0.0% pipe8201 0.0% 0.0% 0.0% mqueue8202 0.0% 0.0% 0.0% fsdev.proc8203 0.0% 0.0% 0.0% flashfs_hes_slot1.proc8204 0.0% 0.0% 0.0% flashfs_hes_slot0.proc8205 0.0% 0.0% 0.0% flashfs_hes_bootflash.proc8206 0.0% 0.0% 0.0% dfs_disk2.proc8207 0.0% 0.0% 0.0% dfs_disk1.proc8208 0.0% 0.0% 0.0% dfs_disk0.proc8209 0.0% 0.0% 0.0% ldcache.proc8210 0.0% 0.0% 0.0% watchdog.proc8211 0.0% 0.0% 0.0% syslogd.proc8212 0.0% 0.0% 0.0% name_svr.proc8213 0.0% 0.1% 0.0% wdsysmon.proc8214 0.0% 0.0% 0.0% sysmgr.proc8215 0.0% 0.0% 0.0% kosh.proc12290 0.0% 0.0% 0.0% chkptd.proc12312 0.0% 0.0% 0.0% sysmgr.proc12313 0.0% 0.0% 0.0% syslog_dev.proc12314 0.0% 0.0% 0.0% itrace_exec.proc12315 0.0% 0.0% 0.0% packet.proc12316 0.0% 0.0% 0.0% installer.proc12317 29.1% 28.5% 19.6% ios-base12318 0.0% 0.0% 0.0% fh_fd_oir.proc12319 0.0% 0.0% 0.1% fh_fd_cli.proc12320 0.0% 0.0% 0.0% fh_metric_dir.proc12321 0.0% 0.0% 0.0% fh_fd_snmp.proc12322 0.0% 0.0% 0.0% fh_fd_none.proc12323 0.0% 0.0% 0.0% fh_fd_intf.proc12324 48.5% 48.5% 35.8% iprouting.iosproc12325 0.0% 0.0% 0.0% fh_fd_timer.proc12326 0.0% 0.0% 0.0% fh_fd_ioswd.proc12327 0.0% 0.0% 0.0% fh_fd_counter.proc12328 0.0% 0.0% 0.0% fh_fd_rf.proc12329 0.0% 0.0% 0.0% fh_server.proc12330 0.0% 0.0% 0.0% cdp2.iosproc12331 0.0% 0.0% 0.0% fh_policy_dir.proc12332 0.0% 0.0% 0.0% ipfs_daemon.proc12333 0.0% 0.0% 0.0% raw_ip.proc12334 0.0% 0.0% 0.0% inetd.proc12335 19.1% 20.4% 12.6% tcp.proc12336 0.0% 0.0% 0.0% udp.procTable 25 describes the significant fields shown in the display.
The following is partial sample output from the show processes cpu command with the detailed keyword when a Software Modularity image is running:
Router# show processes cpu detailedTotal CPU utilization for 5 seconds: 99.6%; 1 minute: 99.3%; 5 minutes: 88.6%PID/TID 5Sec 1Min 5Min Process Prio STATE CPU1 0.0% 0.7% 0.7% kernel 8.9001 0.4% 0.7% 11.4% [idle thread] 0 Ready 2m28s2 0.0% 0.0% 0.0% 63 Receive 0.0003 0.0% 0.0% 0.0% 10 Receive 0.0004 0.0% 0.0% 0.1% 11 Receive 1.8485 0.0% 0.0% 0.0% 63 Receive 0.000...PID/TID 5Sec 1Min 5Min Process Prio STATE CPU8214 0.0% 0.0% 0.0% sysmgr.proc 0.2161 0.0% 0.0% 0.0% 10 Receive 0.1322 0.0% 0.0% 0.0% 10 Sigwaitin 0.0003 0.0% 0.0% 0.0% 10 Receive 0.0044 0.0% 0.0% 0.0% 10 Receive 0.0005 0.0% 0.0% 0.0% 10 Receive 0.0006 0.0% 0.0% 0.0% 10 Receive 0.0047 0.0% 0.0% 0.0% 10 Receive 0.0008 0.0% 0.0% 0.0% 10 Receive 0.0009 0.0% 0.0% 0.0% 10 Receive 0.00010 0.0% 0.0% 0.0% 10 Receive 0.00011 0.0% 0.0% 0.0% 10 Receive 0.00012 0.0% 0.0% 0.0% 10 Receive 0.00013 0.0% 0.0% 0.0% 10 Receive 0.02814 0.0% 0.0% 0.0% 10 Receive 0.04015 0.0% 0.0% 0.0% 10 Receive 0.00016 0.0% 0.0% 0.0% 10 Receive 0.00017 0.0% 0.0% 0.0% 10 Receive 0.00418 0.0% 0.0% 0.0% 10 Receive 0.00019 0.0% 0.0% 0.0% 10 Receive 0.00020 0.0% 0.0% 0.0% 10 Receive 0.00021 0.0% 0.0% 0.0% 10 Receive 0.00422 0.0% 0.0% 0.0% 10 Receive 0.000PID/TID 5Sec 1Min 5Min Process Prio STATE CPU8215 0.0% 0.0% 0.0% kosh.proc 0.0441 0.0% 0.0% 0.0% 10 Reply 0.044PID/TID 5Sec 1Min 5Min Process Prio STATE CPU12290 0.0% 0.0% 0.0% chkptd.proc 0.0801 0.0% 0.0% 0.0% 10 Receive 0.0802 0.0% 0.0% 0.0% 10 Receive 0.000PID/TID 5Sec 1Min 5Min Process Prio STATE CPU12312 0.0% 0.0% 0.0% sysmgr.proc 0.1121 0.0% 0.0% 0.0% 10 Receive 0.1122 0.0% 0.0% 0.0% 10 Sigwaitin 0.000PID/TID 5Sec 1Min 5Min Process Prio STATE CPU12316 0.0% 0.0% 0.0% installer.proc 0.0721 0.0% 0.0% 0.0% 10 Receive 0.0003 0.0% 0.0% 0.0% 10 Nanosleep 0.0004 0.0% 0.0% 0.0% 10 Sigwaitin 0.0006 0.0% 0.0% 0.0% 10 Receive 0.000Process sbin/ios-base, type IOS, PID = 12317CPU utilization for five seconds: 12%/9%; one minute: 13%; five minutes: 10%Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name1 219 1503 145 0.00% 0.00% 0.00% 0 Hot Service Task2 23680 42384 558 2.39% 6.72% 4.81% 0 Service Task3 6104 11902 512 3.51% 1.99% 1.23% 0 Service Task4 1720 5761 298 1.91% 0.90% 0.39% 0 Service Task5 0 5 0 0.00% 0.00% 0.00% 0 Chunk Manager6 0 1 0 0.00% 0.00% 0.00% 0 Connection Mgr7 4 106 37 0.00% 0.00% 0.00% 0 Load Meter8 6240 7376 845 0.23% 0.15% 0.55% 0 Exec9 379 62 6112 0.00% 0.07% 0.04% 0 Check heaps10 0 1 0 0.00% 0.00% 0.00% 0 Pool Manager11 3 2 1500 0.00% 0.00% 0.00% 0 Timers12 0 1 0 0.00% 0.00% 0.00% 0 AAA_SERVER_DEADT13 0 2 0 0.00% 0.00% 0.00% 0 AAA high-capacit14 307 517 593 0.00% 0.05% 0.03% 0 EnvMon15 0 1 0 0.00% 0.00% 0.00% 0 OIR Handler16 283 58 4879 0.00% 0.04% 0.02% 0 ARP Input17 0 2 0 0.00% 0.00% 0.00% 0 Serial Backgroun18 0 81 0 0.00% 0.00% 0.00% 0 ALARM_TRIGGER_SC19 0 2 0 0.00% 0.00% 0.00% 0 DDR Timers20 0 2 0 0.00% 0.00% 0.00% 0 Dialer event21 4 2 2000 0.00% 0.00% 0.00% 0 Entity MIB API22 0 54 0 0.00% 0.00% 0.00% 0 Compute SRP rate23 0 9 0 0.00% 0.00% 0.00% 0 IPC Dynamic Cach24 0 1 0 0.00% 0.00% 0.00% 0 IPC Zone Manager25 0 1 0 0.00% 0.00% 0.00% 0 IPC Punt Process26 4 513 7 0.00% 0.00% 0.00% 0 IPC Periodic Tim27 11 513 21 0.00% 0.00% 0.00% 0 IPC Deferred Por28 0 1 0 0.00% 0.00% 0.00% 0 IPC Seat Manager29 83 1464 56 0.00% 0.00% 0.00% 0 EEM ED Syslog...Table 26 describes the significant fields shown in the display.
Related Commands
show processes
Displays information about active processes.
show processes memory
Displays the amount of system memory used per system process.
show processes detailed
To display detailed information about POSIX and Cisco IOS processes when Cisco IOS Software Modularity images are running, use the show processes detailed command in user EXEC or privileged EXEC mode.
show processes detailed [process-id | process-name]
Syntax Description
Command Default
If no process ID or process name is specified, detailed information is displayed about all processes.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
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.
Examples
The following is sample output from the show processes detailed command for the process named sysmgr.proc:
Router# show processes detailed sysmgr.procJob Id: 67PID: 8210Executable name: sysmgr.procExecutable path: sbin/sysmgr.procInstance ID: 1Args: -pRespawn: ONRespawn count: 1Max. spawns per minute: 30Last started: Mon Aug18 17:08:53 2003Process state: Runcore: SHAREDMEM MAINMEMMax. core: 0Level: 39PID TID Stack pri state Blked HR:MM:SS:MSEC FLAGS NAME8210 1 52K 10 Receive 1 0:00:00:0071 00000000 sysmgr.proc8210 2 52K 10 Sigwaitinfo 0:00:00:0000 00000000 sysmgr.proc8210 3 52K 10 Receive 8 0:00:00:0003 00000000 sysmgr.proc8210 4 52K 10 Reply 1 0:00:00:0003 00000000 sysmgr.proc8210 5 52K 10 Receive 1 0:00:00:0000 00000000 sysmgr.proc8210 6 52K 10 Receive 1 0:00:00:0015 00000000 sysmgr.proc8210 7 52K 10 Receive 1 0:00:00:0000 00000000 sysmgr.proc8210 8 52K 10 Receive 1 0:00:00:0000 00000000 sysmgr.proc-----------------------------------------------------------------Job Id: 78PID: 12308Executable name: sysmgr.procExecutable path: sbin/sysmgr.procInstance ID: 2Args: -pRespawn: ONRespawn count: 1Max. spawns per minute: 30Last started: Mon Aug18 17:08:54 2003Process state: Runcore: SHAREDMEM MAINMEMMax. core: 0Level: 40PID TID Stack pri state Blked HR:MM:SS:MSEC FLAGS NAME12308 1 16K 10 Receive 1 0:00:00:0039 00000000 sysmgr.proc12308 2 16K 10 Sigwaitinfo 0:00:00:0000 00000000 sysmgr.proc-----------------------------------------------------------------Table 27 describes the significant fields shown in the display.
Related Commands
show processes kernel
To display information about System Manager kernel processes when Cisco IOS Software Modularity images are running, use the show processes kernel command in user EXEC or privileged EXEC mode.
show processes kernel {family | files | signal | startup}
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Examples
The following is sample output from the show processes kernel command with the family keyword:
Router# show processes kernel familyPID Name Session Pgroup PPID Sibling Child1 kernel 1 1 0 0 6712290 dumper.proc 1 87 67 56 03 devc-pty 1 66 67 0 04 devc-ser2681 1 54 67 66 06 pipe 1 69 67 5 08199 mqueue 1 68 67 69 08200 fsdev.proc 1 57 67 68 08201 flashfs_hes_slot1.proc 1 58 67 57 08202 flashfs_hes_bootflash.proc 1 51 67 58 08203 flashfs_hes_slot0.proc 1 50 67 51 08204 dfs_disk1.proc 1 61 67 50 08205 dfs_disk0.proc 1 60 67 61 08206 ldcache.proc 1 64 67 60 08207 syslogd.proc 1 65 67 64 08208 name_svr.proc 1 63 67 65 08209 wdsysmon.proc 1 52 67 63 08210 sysmgr.proc 1 67 1 0 748211 kosh.proc 56 56 67 52 012308 sysmgr.proc 1 78 67 87 012309 chkptd.proc 1 70 67 78 012310 syslog_dev.proc 1 81 67 70 012311 fh_metric_dir.proc 1 82 67 81 0Table 28 describes the significant fields shown in the display.
The following is sample output from the show processes kernel command with the files keyword:
Router# show processes kernel filesPID Open Files Open Channels Name1 2 42 kernel12290 11 8 dumper.proc3 3 68 devc-pty4 3 43 devc-ser26816 4 4 pipe8199 4 11 mqueue8200 10 15 fsdev.proc8201 8 4 flashfs_hes_slot1.proc8202 8 4 flashfs_hes_bootflash.proc8203 9 4 flashfs_hes_slot0.proc8204 10 4 dfs_disk1.proc8205 10 4 dfs_disk0.proc8206 10 7 ldcache.proc8207 12 11 syslogd.proc8208 9 37 name_svr.proc8209 10 42 wdsysmon.proc8210 21 35 sysmgr.proc8211 6 1 kosh.proc12308 11 10 sysmgr.proc12309 12 22 chkptd.proc12310 11 8 syslog_dev.proc12311 14 8 fh_metric_dir.procTable 29 describes the significant fields shown in the display.
The following is sample output from the show processes kernel command with the signal keyword:
Router# show processes kernel signalPID Name Signals Pending Signals Ignored Signals Queued8199 mqueue 0000000000000000 0000000006800000 00000000000000001 0000000000000000 0000000000020000PID Name Signals Pending Signals Ignored Signals Queued8200 fsdev.proc 0000000000000000 0000000006800000 00000000000000001 0000000000000000 00000000002040032 0000000000000000 00000000002040033 0000000000000000 00000000002040034 0000000000000000 00000000002040035 0000000000000000 00000000002040036 0000000000000000 00000000002040037 0000000000000000 0000000000204003Table 30 describes the significant fields shown in the display.
The following is sample output from the show processes kernel command with the startup keyword:
Router# show processes kernel startupPID Last Started State RCnt Name:Instance_Id Args3 08/18/2003 17:08 Run 1 devc-pty:1 -n 324 08/18/2003 17:08 Run 1 devc-ser2681:1 -e -2 -b9600,96000x1e840404^3,0x50 Not configured None 0 ldcache_preload.proc:1 preload6 08/18/2003 17:08 Run 1 pipe:10 Not configured None 0 clock_chip.proc:1 -r0 Not configured None 0 c7200-p-blob:1 -b8199 08/18/2003 17:08 Run 1 mqueue:18200 08/18/2003 17:08 Run 1 fsdev.proc:1 /dev/slot0: /dev/slot1:/dev/disk0: /dev/disk1: /dev/bootflash:8201 08/18/2003 17:08 Run 1 flashfs_hes_slot1.proc:1 -m /slot1: -d/dev/slot1:8202 08/18/2003 17:08 Run 1 flashfs_hes_bootflash.proc:1 -m/bootflash: -d /dev/bootflash:8203 08/18/2003 17:08 Run 1 flashfs_hes_slot0.proc:1 -m /slot0: -d/dev/slot0:8204 08/18/2003 17:08 Run 1 dfs_disk1.proc:1 -m /disk1: -d/dev/disk1:8205 08/18/2003 17:08 Run 1 dfs_disk0.proc:1 -m /disk0: -d/dev/disk0:8206 08/18/2003 17:08 Run 1 ldcache.proc:18207 08/18/2003 17:08 Run 1 syslogd.proc:18208 08/18/2003 17:08 Run 1 name_svr.proc:1 /chan/reg_svr8209 08/18/2003 17:08 Run 1 wdsysmon.proc:1Table 31 describes the significant fields shown in the display.
Related Commands
show processes memory
To show the amount of memory used by each system process in Cisco IOS or Cisco IOS Software Modularity images, use the show processes memory command in privileged EXEC mode.
Cisco IOS Software
show processes memory [process-id | sorted [allocated | getbufs | holding]]
Cisco IOS Software Modularity
show processes memory [detailed [process-name[:instance-id] | process-id [taskid task-id]]] [alloc-summary | sorted {start | size | caller}]
Syntax Description
Command Default
Cisco IOS Software
The memory used by all types of system processes is displayed.
Cisco IOS Software Modularity
The system memory followed by a one-line summary of memory information about each Software Modularity process is displayed.
Command Modes
Privileged Exec (#)
Command History
Usage Guidelines
The show processes memory command (and 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 process ID (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, 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 follows.
The value for "Total" in the show processes memory command and 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 (in other words, 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 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." If using these releases or later releases, your Total Process Memory should match the total process memory shown for other commands, such as the show memory summary command.
About Alternate Memory Pools
An "alternate memory pool" is a memory pool which 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). To prevent memory allocations from failing once the available Fast memory has been used up, the normal Processor memory can be configured as an alternative memory pool for the Fast memory pool.
Cisco IOS 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.
Examples
Example output varies between Cisco IOS software releases. To view the appropriate output, choose one of the following sections:
•
•
•
show processes memory Command for Releases Prior to 12.3(7)T, 12.2(22)S, and 12.0(28)S
The following is sample output from the show processes memory command:
Router# show processes memoryProcessor Pool Total: 25954228 Used: 8368640 Free: 17585588PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 8629528 689900 6751716 0 0 *Init*0 0 24048 12928 24048 0 0 *Sched*0 0 260 328 68 350080 0 *Dead*1 0 0 0 12928 0 0 Chunk Manager2 0 192 192 6928 0 0 Load Meter3 0 214664 304 227288 0 0 Exec4 0 0 0 12928 0 0 Check heaps5 0 0 0 12928 0 0 Pool Manager6 0 192 192 12928 0 0 Timers7 0 192 192 12928 0 0 Serial Backgroun8 0 192 192 12928 0 0 AAA high-capacit9 0 0 0 24928 0 0 Policy Manager10 0 0 0 12928 0 0 ARP Input11 0 192 192 12928 0 0 DDR Timers12 0 0 0 12928 0 0 Entity MIB API13 0 0 0 12928 0 0 MPLS HC Counter14 0 0 0 12928 0 0 SERIAL A'detect...78 0 0 0 12992 0 0 DHCPD Timer79 0 160 0 13088 0 0 DHCPD Database8329440 TotalTable 32 describes the significant fields shown in the display.
The following is sample output from the show processes memory command when the sorted keyword is used. In this case, the output is sorted by the "Holding" column, from largest to smallest.
Router# show processes memory sortedProcessor Pool Total: 25954228 Used: 8371280 Free: 17582948PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 8629528 689900 6751716 0 0 *Init*3 0 217304 304 229928 0 0 Exec53 0 109248 192 96064 0 0 DHCPD Receive56 0 0 0 32928 0 0 COPS19 0 39048 0 25192 0 0 Net Background42 0 0 0 24960 0 0 L2X Data Daemon58 0 192 192 24928 0 0 X.25 Background43 0 192 192 24928 0 0 PPP IP Route49 0 0 0 24928 0 0 TCP Protocols48 0 0 0 24928 0 0 TCP Timer17 0 192 192 24928 0 0 XML Proxy Client9 0 0 0 24928 0 0 Policy Manager40 0 0 0 24928 0 0 L2X SSS manager29 0 0 0 24928 0 0 IP Input44 0 192 192 24928 0 0 PPP IPCP32 0 192 192 24928 0 0 PPP Hooks34 0 0 0 24928 0 0 SSS Manager41 0 192 192 24928 0 0 L2TP mgmt daemon16 0 192 192 24928 0 0 Dialer event35 0 0 0 24928 0 0 SSS Test Client--More--The following is sample output from the show processes memory command when a Process ID (process-id) is specified:
Router# show processes memory 1Process ID: 1Process Name: Chunk ManagerTotal Memory Held: 8428 bytesProcessor memory holding = 8428 bytespc = 0x60790654, size = 6044, count = 1pc = 0x607A5084, size = 1544, count = 1pc = 0x6076DBC4, size = 652, count = 1pc = 0x6076FF18, size = 188, count = 1I/O memory holding = 0 bytesRouter# show processes memory 2Process ID: 2Process Name: Load MeterTotal Memory Held: 3884 bytesProcessor memory holding = 3884 bytespc = 0x60790654, size = 3044, count = 1pc = 0x6076DBC4, size = 652, count = 1pc = 0x6076FF18, size = 188, count = 1I/O memory holding = 0 bytesshow processes memory Command for Releases Prior to 12.3(11)T, 12.2(28)S, and 12.0(30)S
The following example shows the output of the show processes memory command before the changes to the summary information were made. Note that the "Total:" in the show processes summary command indicates total memory for all memory pools; in this example, the show processes memory Total of 35423840 can be obtained by adding the Processor and I/O totals shown in the output of the show memory summary command. Note also that the show processes memory sorted command lists the Total Processor Memory (matches the show memory summary Processor Total, but the show processes memory command (without the sorted keyword) lists the Total for all memory pools (Processor plus I/O memory).
Router# show version | include IOSCisco IOS Software, 3600 Software (C3660-BIN-M), Version 12.3(9)Router# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 61E379A0 27035232 8089056 18946176 17964108 17963664I/O 3800000 8388608 2815088 5573520 5561520 5573472...Router# show processes memoryTotal: 35423840, Used: 10904192, Free: 24519648PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 14548868 3004980 9946092 0 0 *Init*0 0 12732 567448 12732 0 0 *Sched*...Router# show processes memory sortedTotal: 27035232, Used: 8089188, Free: 18946044PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 14548868 3004980 9946092 0 0 *Init*64 0 76436 3084 74768 0 0 CEF process...Router# show version | include IOSCisco IOS Software, 3600 Software (c3660-p-mz), Version 12.0(29)S,Router# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 126CB10 49,331,668 6454676 42876992 42642208 42490796Router# show processes memoryTotal: 50,994,868, Used: 6220092, Free: 44774776PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 6796228 627336 5325956 0 0 *Init*0 0 200 29792 200 0 0 *Sched*0 0 192 744 0 349000 0 *Dead*1 0 0 0 12896 0 0 Chunk Manager...Router# show processes memory sortedTotal: 50,994,868, Used: 6222644, Free: 44772224PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 6796228 627336 5325956 0 0 *Init*13 0 39056 0 25264 0 0 Net Background48 0 0 0 24896 0 0 L2X SSS manager18 0 0 0 24896 0 0 IP Input...show processes memory Command for Cisco IOS Software Modularity
The following is sample output from the show processes memory command when a Cisco IOS Software Modularity image is running:
Router# show processes memorySystem Memory : 262144K total, 113672K used, 148472K freePID Text Data Stack Dynamic Total Process1 0 0 12 0 12 kernel12290 52 8 28 196 284 dumper.proc3 12 8 8 144 172 devc-pty4 132 8 8 32 180 devc-ser26816 16 12 24 48 100 pipe8199 12 12 8 48 80 mqueue8200 16 24 48 452 540 fsdev.proc8201 52 20 8 96 176 flashfs_hes_slot1.proc8202 52 20 8 80 160 flashfs_hes_bootflash.proc8203 52 20 8 128 208 flashfs_hes_slot0.proc8204 20 68 12 164 264 dfs_disk1.proc8205 20 68 12 164 264 dfs_disk0.proc8206 36 4 8 144 192 ldcache.proc8207 32 8 20 164 224 syslogd.proc8208 24 4 28 464 520 name_svr.proc8209 124 104 28 344 600 wdsysmon.proc8210 100 144 52 328 624 sysmgr.proc8211 12 4 28 64 108 kosh.proc12308 100 144 16 144 404 sysmgr.proc12309 24 4 12 112 152 chkptd.proc12310 12 4 8 96 120 syslog_dev.proc12311 44 4 24 248 320 fh_metric_dir.proc12312 36 4 24 216 280 fh_fd_snmp.proc12313 36 4 24 216 280 fh_fd_intf.proc12314 32 4 24 216 276 fh_fd_timer.proc12315 40 4 24 216 284 fh_fd_ioswd.proc12316 28 4 24 200 256 fh_fd_counter.proc12317 80 20 44 368 512 fh_server.proc12326 140 40 28 280 488 tcp.proc12327 48 4 24 256 332 udp.proc12328 4 4 28 4660 4696 iprouting.iosproc12329 4 4 36 600 644 cdp2.iosprocTable 33 describes the significant fields shown in the display.
The following is sample output from the show processes memory command with details about the memory of the process named cdp2.iosproc:
Router# show processes memory detailed cdp2.iosprocSystem Memory : 262144K total, 113460K used, 148684K freeProcess sbin/cdp2.iosproc, type IOS, PID = 12329640K total, 4K text, 4K data, 32K stack, 600K dynamicMemory Summary for TaskID = 1Holding = 10032PC Size Count0x7322FC74 9192 10x73236538 640 10x73231E8C 200 1The following is sample output from the show processes memory command with details about the memory of process 12322 and the task with the ID of 1:
Router# show processes memory detailed 12322 taskid 1System Memory : 262144K total, 113456K used, 148688K freeProcess sbin/c7200-p-blob, type IOS, PID = 1232216568K total, 16K text, 8K data, 64K stack, 16480K dynamicMemory Summary for TaskID = 1Holding = 10248PC Size Count0x7322FC74 9192 10x73236538 640 10x73231E8C 256 10x74175060 160 1Table 34 describes the significant fields shown in the display that are different from Table 33.
The following is sample output from the show processes memory command with details about the memory of POSIX process ID 234567 with summary process memory usage per allocator:
Router# show processes memory detailed 234567 alloc-summarySystem Memory : 262144K total, 113672K used, 148472K freeProcess sbin/sysmgr.proc, type POSIX, PID = 12308404K total, 100K text, 144K data, 16K stack, 144K dynamic81920 heapsize, 68620 allocated, 8896 freeAllocated BlocksAddress Usize Size Caller0x0806C358 0x00000478 0x000004D0 0x721C72900x0806D1E0 0x00000128 0x00000130 0x72B902480x0806D318 0x00003678 0x000036E0 0x72B9820C0x0806D700 0x000002A0 0x000002C0 0x72B8EB580x0806D770 0x00000058 0x00000060 0x72BA54880x0806D7D8 0x000000A0 0x000000B0 0x72B8D2280x0806D8A8 0x00000200 0x00000208 0x721A728C0x0806FF78 0x00000068 0x00000070 0x72BA78EC0x08071438 0x0000005C 0x00000068 0x72B908A80x08071508 0x0000010E 0x00000120 0x72BA7AFC0x08072840 0x000000A8 0x000000C0 0x7270A0600x08072910 0x0000010C 0x00000118 0x7273A8980x08072A30 0x000000E4 0x000000F0 0x727490740x08072B28 0x000000B0 0x000000B8 0x7276E87C0x08072BE8 0x0000006C 0x00000078 0x727367A40x08072C68 0x000000B8 0x000000C0 0x7271E2A40x08072D30 0x000000D0 0x000000D8 0x7273834C0x08072E10 0x00000250 0x00000258 0x72718A700x08073070 0x000002F4 0x00000300 0x727264840x08073378 0x000006A8 0x000006B0 0x73EA4DC40x08073A30 0x00000060 0x00000068 0x7352A9F80x08073B38 0x00000068 0x00000070 0x72B920080x08073BB0 0x00000058 0x00000060 0x72B9201C0x08073EB8 0x00002FB4 0x000031C0 0x08026FEC0x08074028 0x000020B8 0x000020C0 0x72709C9C0x08077400 0x000000A0 0x000000A8 0x721DED940x08078028 0x000022B8 0x000022C0 0x727446B80x0807C028 0x00002320 0x00002328 0x72B907C4Free BlocksAddress Size0x0806FFF0 0x000000100x080714A8 0x000000580x08073E18 0x000000980x08073FE8 0x000000180x08076FA0 0x000003280x080774B0 0x00000B500x0807FFB8 0x000000480x08080028 0x00003FD8Table 35 describes the significant fields shown in the display.
Related Commands
show memory
Displays statistics about memory, including memory-free pool statistics.
show processes
Displays information about the active processes.
show raw statistics
To display raw IP statistics when Cisco IOS Software Modularity software is running, use the show raw statistics command in user EXEC or privileged EXEC mode.
show raw statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Usage Guidelines
There are three transport protocols used in Software Modularity: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and raw IP. The transport protocol statistics are generally counters, though some are averages and time stamps. Use the show raw statistics command to display the raw IP statistics, and use the clear raw statistics command to reset the raw IP statistics. Many of the statistics are relevant to all of the transport protocols. To view the other transport protocol statistics used in Software Modularity, see the show tcp statistics and show udp statistics commands.
Examples
The following is sample output from the show raw statistics command:
Router# show raw statisticsCurrent packet level is 0 (Clear)Rcvd: 0 packets, 0 bytes0 packets dropped in total (0 %)0 packets dropped due to invalid length0 packets dropped due to no protocol listener0 packets dropped due to receive packet limits0 packets dropped due to receive byte limits0 bytes dropped due to receive limitsSent: 11 packets, 0 bytes26 Open sockets0 Packets used by socket I/O0 Packets recovered after starvation0 Packet memory warnings0 Packet memory alarms0 Packet allocation errors0 Transmission pulse errors0 Packet punts from IP9 Packet punts to IP9 Packet punts from application0 Packet punts to application1 packets delivered to IP at a time1 packets received from application at a time3 read notification pulses0 millisecond delay between notification and readTable 36 describes the significant fields shown in the display.
Related Commands
clear raw statistics
Clears raw IP statistics.
show tcp statistics
Displays TCP statistics.
show udp statistics
Displays UDP statistics.
show registry
To display the function registry information when Cisco IOS or Cisco IOS Software Modularity images are running, use the show registry command in user EXEC or privileged EXEC mode.
Cisco IOS Software
show registry [registry-name [registry-number]] [brief | statistics]
Cisco IOS Software Modularity
show registry [name [registry-name [registry-number]]] [brief [name [registry-name [registry-number]]] | preemptions | rpcp status | statistics [brief] [name [registry-name [registry-number]]] [remote]] [process {process-name | process-id}]
Syntax Description
