Cisco IOS Software Modularity Command Reference

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-configs

The following example shows how to display the contents of the c2940-tv0-m.tar file that is in flash memory. The contents of the TAR file appear on the screen.

Switch# archive tar /table flash:c2940-tv0-m.tar

info (219 bytes)

c2940-tv0-mz-121/ (directory)

c2940-tv0-mz-121/html/ (directory)

c2940-tv0-mz-121/html/foo.html (0 bytes)

c2940-tv0-mz-121/vegas-tv0-mz-121.bin (610856 bytes)

c2940-tv0-mz-121/info (219 bytes)

info.ver (219 bytes)

The following example shows how to extract the contents of a TAR file on the TFTP server at 172.20.10.30. This command extracts only the new-configs directory into the root directory on the local flash file system. The remaining files in the saved.tar file are ignored.

Switch# archive tar /xtract tftp:/172.20.10.30/saved.tar flash:/ new-configs

clear 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

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

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

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

Usage Guidelines

Use the debug registry command to troubleshoot Software Modularity registry operations.

Caution Use 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.proc

Debug registry events debugging is on

The following example turns on debugging messages for Software Modularity registry errors:

Router# debug registry errors

Debug registry errors debugging is on

exception 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

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 This command is of use only to Cisco technical support representatives in analyzing system failures in the field. Under normal circumstances, there should be no reason to change the core dump options. For that reason, this command should be used only by Cisco Certified Internetwork Experts (CCIEs) or under the direction of Cisco Technical Assistance Center (TAC) personnel.

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 terminal

 exception core cdp2.proc mainmem-text maxcore 100

Related Commands

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

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 This command is of use only to Cisco technical support representatives in analyzing system failures in the field. Under normal circumstances, there should be no reason to change the default core filename. For that reason, this command should be used only by Cisco Certified Internetwork Experts (CCIEs) or under the direction of Cisco Technical Assistance Center (TAC) personnel.

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 red 

ip ftp password blue 

exception protocol ftp 

exception dump 172.17.92.2 

exception core-file dumpfile 

Cisco 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 mainmem

exception core-file dump-tcp limit 20 compress timestamp

Note The exception protocol and exception dump commands are not supported in Software Modularity images.

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 If you are running a Software Modularity image, setting the crashinfo buffer size to the default of 32 KB does not limit the crashinfo buffer size. The crashinfo file size is limited to the value set if the value is set to anything other than the default 32 KB.

Examples

In the following example, the crashinfo buffer is set to 100 KB:

Router(config)# exception crashinfo buffersize 100

Related Commands

exception flash

To handle the device and erase permission for exceptions, and set the local dump location for core files when a process reloads, use the exception flash command in global configuration mode.

exception flash {all | iomem | procmem} device-name

no exception flash

Syntax Description

Command Default

No core dump location is set for a process.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Core dumps are taken when every process reloads. 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 This command is of use only to Cisco technical support representatives in analyzing system failures in the field. Under normal circumstances, there should be no reason to set a local core dump location for a process. For that reason, this command should be used only by Cisco Certified Internetwork Experts (CCIEs) or under the direction of Cisco Technical Assistance Center (TAC) personnel.

Examples

In the following example, three dump locations are configured to dump all the memory:

Router# configure terminal

Router(config)# exception flash all disk1:

Router(config)# exception flash all bootflash:

Router(config)# exception flash all 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

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 This command is of use only to Cisco technical support representatives in analyzing system failures in the field. Under normal circumstances, there should be no reason to dump the kernel memory. For that reason, this command should be used only by Cisco Certified Internetwork Experts (CCIEs) or under the direction of Cisco Technical Assistance Center (TAC) personnel.

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 terminal

 exception kernel filepath /disk0:/core memory kernel

exception switch 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 switch kernel filesystem filename

no exception switch kernel filesystem filename

Syntax Description

Command Default

No kernel memory is dumped.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Caution This command is useful only to Cisco technical support representatives for analyzing system failures in the field. Under normal circumstances, you should not need to dump the kernel memory. For that reason, this command should be used only by Cisco Certified Internetwork Experts (CCIEs), or under the direction of Cisco Technical Assistance Center (TAC) personnel.

The exception switch kernel command is available in Cisco IOS Releases 12.2(33)SXI4 and 12.2(33)SXI4a

Use the exception switch kernel command to dump kernel memory when the kernel reloads on the SP. This operation 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:, the exception switch kernel command is all that is required.

The filepath keyword only accepts file systems available to the SP. Use this command for configuring modular Cisco IOS kernel core files on the SP.

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.

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 terminal

 exception switch kernel filesystem /disk0:/core memory kernel

Related Commands

install activate

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install activate command is not available in Cisco IOS software.

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

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.

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:/sys

Related Commands

install bind

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install bind command is not available in Cisco IOS software.

To bind a Cisco IOS Software Modularity software image system-wide, use the install bind command in global configuration mode. To remove the Software Modularity software 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 software image is not bound.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The install bind command generates a boot system command, but the install bind command is not inserted into the configuration. The benefit in 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. 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 Use the install bind command to bind one or more Software Modularity images, and then copy the changes to the startup configuration file. Be aware that an image reload or switchover must be performed before the installed and bound image is actually running on the device.

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 terminal

Router(config)# no boot system

Router(config)# install bind disk0:/sys

Router(config)# exit

Router# copy running-config startup-config

Related Commands

install clear

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install clear command is not available in Cisco IOS software.

To remove an entire installed software system, use the install clear command in privileged EXEC mode.

install clear search-root-directory

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

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:/sys

Related Commands

install commit

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install commit command is not available in Cisco IOS software.

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

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 tag1

Related Commands

install copy

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install copy command is not available in Cisco IOS software.

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

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:/oldsys

Related Commands

install file

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install file command is not available in Cisco IOS software.

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

Usage Guidelines

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.

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 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:/sys

Router# install file rcp://s72033/base/s72033-adventerprisek9_wan_dbg-vz disk0:/sys

Related Commands

install move

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install move command is not available in Cisco IOS software.

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

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:/oldsys

Related Commands

install prune

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install prune command is not available in Cisco IOS software.

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

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 tag1

The 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 files

Related Commands

install repackage

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install repackage command is not available in Cisco IOS software.

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

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

Related Commands

install rollback

Note Effective with Cisco IOS Release 12.2(33)SXI3, the install rollback command is not available in Cisco IOS software.

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

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 tag1

Router# install activate disk0:/sys

Related 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 to 

continue ? [no]:

If you restart the process, a message similar to the following is displayed:

Restarting process iprouting.iosproc

02: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 been 

checkpointed and may be lost 

To 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.iosproc

Related 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

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

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

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 System-manager-controlled processes (for example, cdp2.iosproc) cannot be stopped.

Examples

The following example shuts down all instances of the POSIX process named process1:

Router# process stop process1

Related 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

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:

•Each time you exit from global configuration mode.

•Each time you enter the write memory, copy running-config, or show running-config command.

•When the action generated by the write checkpoint command has completed. The write checkpoint command is visible only after you enter the no service checkpoint-config command.

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 terminal

 no service checkpoint-config

!

! Configuration commands are entered.

 end

write checkpoint

Related Commands

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

•Cisco IOS Software Modularity

Cisco IOS Software

The following is sample output from the show buffers command with no arguments, showing all buffer pool information:

Router# show buffers

Buffer elements:

     398 in free list (500 max allowed)

     1266 hits, 0 misses, 0 created

Public 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 created

Middle buffers, 600 bytes (total 25, permanent 25):

     25 in free list (10 min, 150 max allowed)

     39 hits, 0 misses, 0 trims, 0 created

Big buffers, 1524 bytes (total 50, permanent 50):

     49 in free list (5 min, 150 max allowed)

     27 hits, 0 misses, 0 trims, 0 created

VeryBig buffers, 4520 bytes (total 10, permanent 10):

     10 in free list (0 min, 100 max allowed)

     0 hits, 0 misses, 0 trims, 0 created

Large buffers, 5024 bytes (total 0, permanent 0):

     0 in free list (0 min, 10 max allowed)

     0 hits, 0 misses, 0 trims, 0 created

Huge buffers, 18024 bytes (total 0, permanent 0):

     0 in free list (0 min, 4 max allowed)

     0 hits, 0 misses, 0 trims, 0 created

Interface buffer pools:

Ethernet0 buffers, 1524 bytes (total 64, permanent 64):

     16 in free list (0 min, 64 max allowed)

     48 hits, 0 fallbacks

     16 max cache size, 16 in cache

Ethernet1 buffers, 1524 bytes (total 64, permanent 64):

     16 in free list (0 min, 64 max allowed)

     48 hits, 0 fallbacks

     16 max cache size, 16 in cache

Serial0 buffers, 1524 bytes (total 64, permanent 64):

     16 in free list (0 min, 64 max allowed)

     48 hits, 0 fallbacks

     16 max cache size, 16 in cache

Serial1 buffers, 1524 bytes (total 64, permanent 64):

     16 in free list (0 min, 64 max allowed)

     48 hits, 0 fallbacks

     16 max cache size, 16 in cache

TokenRing0 buffers, 4516 bytes (total 48, permanent 48):

     0 in free list (0 min, 48 max allowed)

     48 hits, 0 fallbacks

     16 max cache size, 16 in cache

TokenRing1 buffers, 4516 bytes (total 32, permanent 32):

     32 in free list (0 min, 48 max allowed)

     16 hits, 0 fallbacks

     0 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 buffers

Huge buffers, 18024 bytes (total 5, permanent 0, peak 5 @ 5d18h): 
     4 in free list (3 min, 104 max allowed) 
     0 hits, 1 misses, 101 trims, 106 created 
     0 failures (0 no memory)

The following is sample output from the show buffers command with no arguments, showing only buffer pool information for Huge buffers. This output shows a highest total of 184 Huge buffers created one hour, one minute, and 15 seconds before the command was issued.

Router# show buffers

Huge buffers, 65280 bytes (total 4, permanent 2, peak 184 @ 01:01:15):

     4 in free list (0 min, 4 max allowed)

     32521 hits, 143636 misses, 14668 trims, 14670 created

     143554 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 0

Ethernet0 buffers, 1524 bytes (total 64, permanent 64):

     16 in free list (0 min, 64 max allowed)

     48 hits, 0 fallbacks

16 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 buffers

Buffer elements: 

    500 in free list (500 max allowed) 

    106586 hits, 0 misses, 0 created 

Public 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 created 

    0 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 created 

    0 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 created 

    0 failures (0 no memory) 

VeryBig buffers, 4520 bytes (total 10, permanent 10): 

    10 in free list (0 min, 100 max allowed) 

    0 hits, 0 misses, 0 trims, 0 created 

    0 failures (0 no memory) 

Large buffers, 5024 bytes (total 0, permanent 0): 

    0 in free list (0 min, 10 max allowed) 

    0 hits, 0 misses, 0 trims, 0 created 

    0 failures (0 no memory) 

Huge buffers, 18024 bytes (total 1, permanent 0, peak 1 @ 1d13h): 

    0 in free list (0 min, 4 max allowed) 

    1 hits, 0 misses, 0 trims, 0 created 

    0 failures (0 no memory) 

! Start of Cisco IOS Software Modularity fields

Public buffer headers: 

Header buffers, 880 bytes (total 1000, peak 142 @ 1d13h): 

    864 in permanent free list 

    142 hits, 0 misses 

Temporary buffer headers: 

Header buffers, 896 bytes (total 0): 

    0 in free list 

    0 hits, 0 misses, 0 trims, 0 created 

    0 failures  

! End of Cisco IOS Software Modularity fields

Interface buffer pools: 

Logger Pool buffers, 600 bytes (total 150, permanent 150): 

    150 in free list (150 min, 150 max allowed) 

    22 hits, 0 misses

Table 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

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 exception

Core Dump Configurations:

Choice 1

========

 Filepath                 : disk0:

 Filename                 : test1

 Lower Filename Suffix    : 0

 Upper Filename Suffix    : 4

 Current Filename Suffix  : 0

 Compression              : on

Choice 2

========

 Filepath                 : disk1:

 Filename                 : test1

 Lower Filename Suffix    : 0

 Upper Filename Suffix    : 4

 Current Filename Suffix  : 0

 Compression              : on

Choice 3

========

 Filepath                 : slot0

 Filename                 : test1

 Lower Filename Suffix    : 0

 Upper Filename Suffix    : 4

 Current Filename Suffix  : 0

 Compression              : on

Table 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 running

Software 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.so

Software 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)ommitted

Pruned - This file has been pruned from the system

Active - This file is active in the system

PendInst - This file is set to be made available to run on the

   system 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 reload

RollPRel - This file will be removed from the system after next reload

RPRPndIn - This file is both rolled back pending a reload, and pending

   installation.  On reload, this file will not run and will move to

   PendInst state.  If 'install activate' is done before reload, pending

   removal and install cancel each other and file simply remains active

IPRPndRo - This file is both installed pending a reload, and pending rollback.

   If the card reloads, it will be active on the system pending a rollback

   If 'install activate' is done before a reload, the pending install and

   removal with cancel each other and the file will simply be removed

Occluded - 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 detailed

Software running on card installed at location s72033 - Slot 5 :

Base image : disk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vm

Version : 12.2(99)SX1010

File state: Active    File Checksum : 8BB2F966EA945E8E25010A1BAC7205C3DFBCA197

Date Installed : 19:51:22 UTC Sep 8 2005 Commit Tags :  base  

Software running on card installed at location s72033_rp - Slot 5 :

Base image : disk0:/sys/s72033_rp/base/DRACO2_MP

File state: Active    File Checksum : 48849DBB2E47A8C55AC68CF3F6EE747B054CD392

Date Installed : 19:49:06 UTC Sep 8 2005 Commit Tags :  base  

Software running on card installed at location s72033 - Slot 6 :

Base image : slavedisk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vm

Version : 12.2(99)SX1010

File state: Active    File Checksum : 8BB2F966EA945E8E25010A1BAC7205C3DFBCA197

Date Installed : 19:32:21 UTC Sep 8 2005 Commit Tags :  base Patch : 
slavedisk0:/sys/s72033/patch/patch-AAA1258-patch-0-n.so

File state: PendInst  File Checksum : A129339A6A3ED1F8B92D6992AD1BE67C716E4430

Date Installed : 20:31:01 UTC Sep 9 2005 Commit Tags : NONE  Maintenance Pack : MA0005

Table 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 running

Tags defined over software running on location s72033 - Slot 5 :

Tagname              # of Files          Date Committed     

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

base                      1          20:08:51 UTC Sep 9 2005  

MA0005                    1          20:34:16 UTC Sep 9 2005  

Tags defined over software running on location s72033_rp - Slot 5 :

Tagname              # of Files          Date Committed     

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

base                      1          20:08:51 UTC Sep 9 2005  

MA0005                    1          20:34:16 UTC Sep 9 2005  

Tags defined over software running on location s72033 - Slot 6 :

Tagname              # of Files          Date Committed     

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

base                      1          20:28:54 UTC Sep 9 2005  

Table 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 detailed

Tags defined over software running on location s72033 :

Tag Name :base

Date Committed :Fri Sep 9 17:54:37 2005

Files under this tag:

disk0:/sys/s72033/base/s72033-adventerprisek9_wan_dbg-vm

In 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 detailed 

Tags defined over software running on location c7200: 

Tag Name : tag1 

Date Committed : 01:49:23 UTC Mar 8 2006 

Files under this tag: disk0:/sys/c7200/base/c7200-p-vm

Table 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

•Cisco IOS Software Modularity

Cisco IOS Software

The following is sample output from the show memory command:

Router# show memory

               Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)

Processor    B0EE38    5181896    2210036    2971860    2692456    2845368

          Processor memory

Address   Bytes Prev.    Next     Ref  PrevF   NextF   Alloc PC  What

B0EE38     1056 0        B0F280     1                  18F132    List Elements

B0F280     2656 B0EE38   B0FD08     1                  18F132    List Headers

B0FD08     2520 B0F280   B10708     1                  141384    TTY data

B10708     2000 B0FD08   B10F00     1                  14353C    TTY Input Buf

B10F00      512 B10708   B11128     1                  14356C    TTY Output Buf

B11128     2000 B10F00   B11920     1                  1A110E    Interrupt Stack 

B11920       44 B11128   B11974     1                  970DE8    *Init*

B11974     1056 B11920   B11DBC     1                  18F132    messages

B11DBC       84 B11974   B11E38     1                  19ABCE    Watched Boolean 

B11E38       84 B11DBC   B11EB4     1                  19ABCE    Watched Boolean 

B11EB4       84 B11E38   B11F30     1                  19ABCE    Watched Boolean 

B11F30       84 B11EB4   B11FAC     1                  19ABCE    Watched Boolean 

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

Router# show memory free

               Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)

Processor      B0EE38    5181896    2210076    2971820    2692456    2845368

          Processor memory

Address   Bytes Prev.    Next     Ref  PrevF   NextF   Alloc PC  What

             24    Free list 1

CEB844       32  CEB7A4 CEB88C      0  0       0       96B894    SSE Manager

             52    Free list 2

             72    Free list 3

             76    Free list 4

             80    Free list 5

D35ED4       80 D35E30   D35F4C     0  0       D27AE8  96B894    SSE Manager

D27AE8       80 D27A48   D27B60     0  D35ED4  0       22585E    SSE Manager

             88    Free list 6

            100    Free list 7

D0A8F4      100 D0A8B0   D0A980     0  0       0       2258DA    SSE Manager

            104    Free list 8

B59EF0      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 io

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

6132DA0   59264 6132664 6141520  0    0      600DDEC  3FCF0     *Packet Buffer*

600DDEC     500 600DA4C 600DFE0  0   6132DA0 600FE68  0 

600FE68     376 600FAC8 600FFE0  0   600DDEC 6011D54  0 

6011D54     652 60119B4 6011FEO  0   600FE68 6013D54  0 

614FCA0     832 614F564 614FFE0  0   601FD54 6177640  0 

6177640 2657056 6172E90 0        0   614FCA0 0        0 

Total: 2723244

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

Router# show memory overflow

Count   Buffer Count     Last corrected      Crashinfo files

1       1                00:11:17            slot0:crashinfo_20030620-075755

Traceback   607D526C 608731A0 607172F8 607288E0 607A5688 607A566C

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

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

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

Router# show memory sram

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

7AE0      38178 72F0    0        0    0       0       0

Total     38178 

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

Router# show memory

               Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)

Processor    49C724   28719324    1510864   27208460   26511644   15513908

      I/O   6000000    4194304    1297088    2897216    2869248    2896812

     SRAM      1000      65536      63400       2136       2136       2136

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

1000       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     Init

7AE0      38178 72F0    0          0    0      0      0         

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

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

Router# show memory summary

Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)

Processor    B0EE38    5181896    2210216    2971680    2692456    2845368

          Processor memory

Alloc PC        Size     Blocks      Bytes    What

0x2AB2           192          1        192    IDB: Serial Info

0x70EC            92          2        184    Init

0xC916           128         50       6400    RIF Cache

0x76ADE         4500          1       4500    XDI data

0x76E84         4464          1       4464    XDI data

0x76EAC          692          1        692    XDI data

0x77764          408          1        408    Init

0x77776          116          1        116    Init

0x777A2          408          1        408    Init

0x777B2          116          1        116    Init

0xA4600           24          3         72    List

0xD9B5C           52          1         52    SSE Manager

.

.

.

0x0                0       3413    2072576    Pool Summary

0x0                0         28    2971680    Pool Summary (Free Blocks)

0x0               40       3441     137640    Pool Summary (All Block Headers)

0x0                0       3413    2072576    Memory Summary

0x0                0         28    2971680    Memory Summary (Free Blocks)

Cisco IOS Software Modularity

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

Router# show memory

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

Table 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 | physical | shared | statistics | summary]

Syntax Description

Command Default

No detailed memory information about POSIX and Cisco IOS processes is displayed.

Command Modes

Privileged EXEC (#)

Command History

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

System Memory: 131072K total, 115836K used, 15236K free 4000K kernel reserved

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

    636K total, 4K text, 4K data, 28K stack, 600K dynamic

    16384 heapsize, 3972 allocated, 10848 free

Address       Bytes What

0x3B42000   4194304 Shared Memory

0x7FBB000      8192 Program Stack

0x8020000     49152 Program Text

0x802C000      4096 Program Data

0x802D000      8192 Allocated memory

0x60000000     4096 Shared Memory "SHM_IDB"

0x60001000    32768 Shared Memory

             Head       Total(b)  Used(b)    Free(b)   Lowest(b)  Largest(b)

Processor    8034058    508152    480420     27732     17368      18716

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

08034058 0000020008 00000000 08038EB8 001  -------- -------- 727FB668 Managed Chunk Queue 
Elements

08038EB8 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 12290

System Memory: 131072K total, 115876K used, 15196K free 4000K kernel reserved

Process sbin/sysmgr.proc, type POSIX, PID = 12290

    400K total, 100K text, 144K data, 12K stack, 144K dynamic

    81920 heapsize, 68716 allocated, 8824 free

Address       Bytes What

0x7FDF000    126976 Program Stack (pages not allocated)

0x7FFE000      4096 Program Stack

0x8000000    122880 Program Stack (pages not allocated)

0x801E000      8192 Program Stack

0x8020000    102400 Program Text

0x8039000    147456 Program Data

0x805D000      8192 Heap Memory

0x8060000     16384 Heap Memory

0x8064000     16384 Heap Memory

0x8068000      8192 Heap Memory

0x806C000     16384 Heap Memory

0x8070000     16384 Heap Memory

0x8074000     16384 Heap Memory

0x8078000     16384 Heap Memory

0x807C000     16384 Heap Memory

0x8080000     16384 Heap Memory

The following partial sample output from the show memory detailed command with a process name and the physical keyword that displays the summary of physical memory used by the specified process along with the shared memory details:

Router# show memory detailed sysmgr.proc physical

Pid       Data   Stack Dynamic    Text  Shared  Maps  Process

20482     304K     16K    256K   3480K    468K   60  sysmgr.proc              

Total Physical Memory used or mapped by sysmgr.proc

  Private memory used  (Data/Stack/Dynamic) :      576K

  Shared memory mapped (Text/Shared)        :     3948K

  Number of memory maps                     :       60

Dev   1:Text/Data 2:Mapped 3:Shared 4:DSO

Flags SHD:Shared PRV:Private FXD:Fixed ANN:Anon PHY:Phys

      LZY:Lazy ELF:Elf STK:Stack NOC:Nocache

Phy Addr      Size     Pid   Virt Addr  What    Dev  Prot   MapFlags

0x0          32768K  20482  0x70000000  Text     4  R-X  SHD FXD ELF

0x2000000    32768K  20482  0x72000000  Text     4  R-X  SHD FXD ELF

0x4000000    32768K  20482  0x74000000  Text     4  R-X  SHD FXD ELF

0x522B000        4K  20482  0x1020000   Text     4  R-X  SHD FXD ELF

Phy Addr      Size     Pid   Virt Addr  What    Dev  Prot   MapFlags

0x9EFD4000      32K  20482  0x105C000   Heap     2  RW-  PRV ANN

0x9EFF0000      32K  20482  0x1054000   Heap     2  RW-  PRV ANN

0x9EFF8000      32K  20482  0x1034000   Heap     2  RW-  PRV ANN

0x9F003000       4K  20482  0x7B43C000  Data     4  RW-  PRV FXD ANN ELF

.

.

.

Table 20 describes the significant fields shown in the display.

Related Commands

show memory detailed all

To display detailed memory information of all applicable processes when Cisco IOS Software Modularity images are running, use the show memory detailed all command in privileged EXEC mode.

show memory detailed all [[start-address [end-address] | failures alloc | shared | statistics [history] | summary] | [fast | io | multibus [pci] | pci | processor] [allocating-process [totals] | dead [totals] | free | physical]]

Syntax Description

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

Detailed output of all applicable processes on the device is displayed with this command. Use the optional arguments and keywords to display specific detailed information.

Examples

The following is partial sample output from the show memory detailed all command:

Router# show memory detailed all

System Memory: 2097152K total, 1303301K used, 793851K free, 0K kernel reserved

Lowest(b)    : 812904448

Process kernel, type POSIX, PID = 1

Process sbin/chkptd.proc, type POSIX, PID = 16386

    3448K total, 2516K text, 672K data, 16K stack, 244K dynamic

    204800 heapsize, 108612 allocated, 56448 free

Address       Bytes What

0x4813D000     4096 Unknown type

0x4813E000   126976 Program Stack (pages not allocated)

0x4815D000     4096 Program Stack

0x4815E000     4096 Unknown type

0x4815F000   126976 Program Stack (pages not allocated)

0x4817E000     4096 Program Stack

0x4817F000     4096 Unknown type

0x48180000   516096 Program Stack (pages not allocated)

0x481FE000     8192 Program Stack

0x48200000     8192 Shared object data "sbin/chkptd.proc"

0x48202000     4096 Shared object data "sbin/chkptd.proc"

0x48203000   237568 Heap Memory

0x68000000   917504 Shared Memory

0x680E0000 66191360 Shared Memory

0x80100000     8192 Shared Memory

0x80102000     4096 Shared Memory

0x80103000   397312 Shared Memory

0x80164000     4096 Shared Memory

0xFE300000   614400 Shared object text "lib/libc.so"

0xFE396000    45056 Shared object data "lib/libc.so"

0xFE3A1000    12288 Heap Memory

0xFE3A4000    20480 Shared object text "lib/s72044-adventerprisek9_dbg-014-dso-"

0xFE3A9000    65536 Shared object data "/dev/zero"

0xFE3B9000     4096 Shared object data "lib/s72044-adventerprisek9_dbg-014-dso-"

0xFE3BA000   434176 Shared object text "lib/s72044-adventerprisek9_dbg-001-dso-"

0xFE424000    65536 Shared object data "/dev/zero".

.

.

.

.

The first section of the display shows system summary information. Table 21 describes the significant fields shown in the first section of the display.