Table Of Contents
show kron schedule
show logging
show logging count
show logging history
show logging xml
show management event
show memory
show memory allocating-process
show memory dead
show memory debug incremental
show memory debug leaks
show memory debug references
show memory debug unused
show memory ecc
show memory failures alloc
show memory fragment
show memory multibus
show memory pci
show memory processor
show memory scan
show memory statistics history table
show memory transient
show microcode
show monitor event-trace
show monitor event-trace cpu-report
show ntp associations
show ntp status
show parser dump
show parser statistics
show pci
show pci hardware
show processes
show processes cpu
show processes cpu autoprofile hog
show processes cpu extended
show processes memory
show protocols
show region
show registry
show reload
show resource all
show resource database
show resource owner
show resource relationship
show resource user
show rmon
show rmon alarms
show rmon capture
show rmon events
show rmon filter
show rmon history
show rmon hosts
show rmon matrix
show rmon statistics
show rmon topn
show rom-monitor
show rtr application
show rtr authentication
show rtr collection-statistics
show kron schedule
To display the status and schedule information of Command Scheduler occurrences, use the show kron schedule command in user EXEC or privileged EXEC mode.
show kron schedule
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
Usage Guidelines
Use the show kron schedule command to view all currently configured occurrences and when they are next scheduled to run.
Examples
The following sample output displays each configured policy name and the time interval before the policy is scheduled to run:
Router# show kron schedule
week inactive, will run again in 7 days 01:02:33
may inactive, will run once in 32 days 20:43:31 at 6:30 on Jun 20
Table 114 describes the significant fields shown in the display.
Table 114 show kron schedule Field Descriptions
Field
|
Description
|
week inactive
|
The policy list named week is currently inactive.
|
run again in 7 days 01:02:33
|
Time in days, hours, minutes and seconds before the policy will run. This policy is scheduled to run on a recurring basis.
|
run once in 32 days 20:434:31
|
Time in days, hours, minutes and seconds before the policy will run. This policy is scheduled to run just once.
|
Related Commands
Command
|
Description
|
kron occurrence
|
Specifies schedule parameters for a Command Scheduler occurrence and enters kron-occurrence configuration mode.
|
policy-list
|
Specifies the policy list associated with a Command Scheduler occurrence.
|
show logging
To display the state of system logging (syslog) and the contents of the standard system logging buffer, use the show logging command in privileged EXEC mode.
show logging [slot slot-number | summary]
Syntax Description
slot slot-number
|
(Optional) Displays information in the syslog history table for a specific line card. Slot numbers range from 0 to 11 for the Cisco 12012 Internet router and 0 to 7 for the Cisco 12008 Internet router.
|
summary
|
(Optional) Displays counts of messages by type for each line card.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.2 GS
|
The slot and summary keywords were added for the Cisco 12000 family.
|
12.2(8)T
|
Command output was expanded to show the status of the logging count facility ("Count and timestamp logging messages").
|
12.2(15)T
|
Command output was expanded to show the status of XML syslog formatting.
|
12.3(2)T
|
Command output was expanded (on supported software images) to show details about the status of system logging processed through the Embedded Syslog Manager (ESM). These lines appear as references to "filtering" or "filter modules".
|
12.3(2)XE
|
This command was integrated into Cisco IOS Release 12.3(2)XE.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and which logging destinations (console, monitor, buffer, or host) logging is enabled. This command also displays Simple Network Management Protocol (SNMP) logging configuration parameters and protocol activity.
This command will also display the contents of the standard system logging buffer, if logging to the buffer is enabled. Logging to the buffer is enabled or disabled using the [no] logging buffered command. The number of system error and debugging messages in the system logging buffer is determined by the configured size of the syslog buffer. This size of the syslog buffer is also set using the logging buffered command.
To enable and set the format for syslog message timestamping, use the service timestamps log command.
If debugging is enabled (using any debug command), and the logging buffer is configured to include level 7 (debugging) messages, debug output will be included in the system log. Debugging output is not formatted like system error messages and will not be preceded by the percent symbol (%).
Examples
The following is sample output from the show logging command on a software image that supports the Embedded Syslog Manager (ESM) feature:
Syslog logging: enabled (10 messages dropped, 5 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 31 messages logged, xml disabled,
Monitor logging: disabled
Buffer logging: level errors, 36 messages logged, xml disabled,
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
No active filter modules.
Trap logging: level informational, 45 message lines logged
Table 115 describes the significant fields shown in the display.
Table 115 show logging Field Descriptions
Field
|
Description
|
Syslog logging:
|
Shows general state of system logging (enabled or disabled), the status of logged messages (number of messages dropped, rate-limited, or flushed), and whether XML formatting or ESM filtering is enabled.
|
Console logging:
|
Logging to the console port. Shows "disabled" or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the logging console, logging console xml, or logging console filtered commands.
|
Monitor logging:
|
Logging to the monitor (all TTY lines). Shows "disabled" or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the logging monitor, logging monitor xml, or logging monitor filtered commands.
|
Buffer logging:
|
Logging to the standard syslog buffer. Shows "disabled" or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the logging buffered, logging buffered xml, or logging buffered filtered commands.
|
Trap logging:
|
Logging to a remote host (syslog collector). Shows "disabled" or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
(The word "trap" means a trigger in the system software for sending error messages to a remote host.)
Corresponds to the configuration of the logging host command. The severity level limit is set using the logging trap command.
|
SNMP logging
|
Displays whether SNMP logging is enabled, the number of messages logged, and the retransmission interval. If not shown on your platform, use the show logging history command.
|
Logging Exception size (8192 bytes)
|
Corresponds to the configuration of the logging exception command.
|
Count and timestamp logging messages:
|
Corresponds to the configuration of the logging count command.
|
No active filter modules.
|
Appears if no syslog filter modules are configured with the logging filter command.
Syslog filter modules are Tcl script files used when the Embedded Syslog Manager (ESM) is enabled. ESM is enabled when any of the filtered keywords are used in the logging commands.
If configured, the URL and filename of configured syslog filter modules will appear at this position in the output. Syslog filter modules are executed in the order in which they appear here.
|
Log Buffer (8192 bytes):
|
The value in parentheses corresponds to the configuration of the logging buffered buffer-size command. If no messages are currently in the buffer, the output ends with this line. If messages are stored in the syslog buffer, they appear after this line.
|
The following example includes syslog messages from the system buffer, with timestamping. Note that in this example, the software image does not support XML formatting or ESM filtering of syslog messages.
Syslog logging:enabled (2 messages dropped, 0 flushes, 0 overruns)
Monitor logging:level debugging, 0 messages logged
Buffer logging:level debugging, 4104 messages logged
Trap logging:level debugging, 4119 message lines logged
Logging to 216.231.111.14, 4119 message lines logged
Log Buffer (262144 bytes):
Jul 11 12:17:49 EDT:%BGP-4-MAXPFX:No. of prefix received from 209.165.200.225
(afi 0) reaches 24, max 24
! THE FOLLOWING LINE IS A DEBUG MESSAGE FROM NTP.
! NOTE THAT IT IS NOT PRECEEDED BY THE % SYMBOL.
Jul 11 12:17:48 EDT: NTP: Maxslew = 213866
Jul 11 15:15:41 EDT:%SYS-5-CONFIG:Configured from
tftp://host.com/addc5505-rsm.nyiix
.Jul 11 15:30:28 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Up
.Jul 11 15:31:34 EDT:%BGP-3-MAXPFXEXCEED:No. of prefix received from
209.165.200.226 (afi 0):16444 exceed limit 375
.Jul 11 15:31:34 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Down BGP
.Jul 11 15:31:34 EDT:%BGP-3-NOTIFICATION:sent to neighbor 209.165.200.226 3/1
(update malformed) 0 bytes
The software clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the "authoritative" flag is set, the flag prevents peers from synchronizing to the software clock.
Table 116 describes the symbols that proceed the timestamp.
Table 116 Timestamping Symbols for syslog Messages
Symbol
|
Description
|
Example
|
*
|
Time is not authoritative: the software clock is not in sync or has never been set.
|
*15:29:03.158 UTC Tue Feb 25 2003:
|
(blank)
|
Time is authoritative: the software clock is in sync or has just been set manually.
|
15:29:03.158 UTC Tue Feb 25 2003:
|
.
|
Time is authoritative, but NTP is not synchronized: the software clock was in sync, but has since lost contact with all configured NTP servers.
|
.15:29:03.158 UTC Tue Feb 25 2003:
|
The following is sample output from the show logging summary command for a Cisco 12012 router. A number in the column indicates that the syslog contains that many messages for the line card. For example, line card in slot 9 has 1 error message, 4 warning messages, and 47 notification messages.
Note
For similar log counting on other platforms, use the show logging count command.
Router# show logging summary
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
SLOT | EMERG | ALERT | CRIT | ERROR |WARNING| NOTICE| INFO | DEBUG |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
|* 0* | . | . | . | . | . | . | . | . |
| 2 | | | | 1 | 4 | 45 | | |
| 4 | | | | 5 | 4 | 54 | | |
| 7 | | | | 17 | 4 | 48 | | |
| 9 | | | | 1 | 4 | 47 | | |
| 11 | | | | 12 | 4 | 65 | | |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
Table 117 describes the logging level fields shown in the display.
Table 117 show logging summary Field Descriptions
Field
|
Description
|
SLOT
|
Indicates the slot number of the line card. An asterisk next to the slot number indicates the GRP card whose error message counts are not displayed. For information on the GRP card, use the show logging command.
|
EMERG
|
Indicates that the system is unusable.
|
ALERT
|
Indicates that immediate action is needed.
|
CRIT
|
Indicates a critical condition.
|
ERROR
|
Indicates an error condition.
|
WARNING
|
Indicates a warning condition.
|
NOTICE
|
Indicates a normal but significant condition.
|
INFO
|
Indicates an informational message only.
|
DEBUG
|
Indicates a debugging message.
|
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
logging count
|
Enables the error log count capability.
|
logging history size
|
Changes the number of syslog messages stored in the history table of the router.
|
logging linecard
|
Logs messages to an internal buffer on a line card and limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
|
service timestamps
|
Configures the system to timestamp debugging or logging messages.
|
show logging count
|
Displays a summary of system error messages (syslog messages) by facility and severity.
|
show logging xml
|
Displays the state of system logging and the contents of the XML-specific logging buffer.
|
show logging count
To display a summary of the number of times certain system error messages are occurring, use the show logging command in privileged EXEC mode.
show logging count
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
To enable the error log count capability (syslog counting feature), use the logging count command in global configuration mode.
This feature works independently of the various settings of the other logging commands (such as [no] logging on, [no] logging buffered, and so on). In other words, turning off logging by other means does not stop the counting and timestamping from occurring.
This command displays information such as the number of times a particular system error message occurs and the time stamp of the last occurrence of the specified message. System error messages are grouped into logical units called "Facilities" based on Cisco IOS software components.
To determine if system error message counting is enabled, use the show logging command.
The service timestamps command configuration determines the timestamp format (shown in the "Last Time" column) of show logging count command output. There is not quite enough space for all options of the possible options (datetime, milliseconds, and timezone) of the service timestamps datetime command to be displayed at the same time. As a result, if msec is selected, timezone will not be displayed. If show-timezone is selected but not msec, then the time zone will be displayed.
Occasionally, the length of the message name plus the facility name contains too many characters to be printed on one line. The CLI attempts to keep the name and facility name on one line but, if necessary, the line will be wrapped, so that the first line contains the facility name and the second line contains the message name and the rest of the columns.
Examples
The following example shows the number of times syslog messages have occurred and the most recent time that each error message occurred. In this example, the show logging command is used to determine if the syslog counting feature is enabled:
Router# show logging | include count
Count and timestamp logging messages: enabled
Router# show logging count
Facility Message Name Sev Occur Last Time
=============================================================================
SYS BOOTTIME 6 1 00:00:12
SYS CONFIG_I 5 1 00:00:05
------------- ------------------------------- -----------------------------
LINEPROTO UPDOWN 5 13 00:00:19
------------- ------------------------------- -----------------------------
LINK CHANGED 5 12 00:00:09
------------- ------------------------------- -----------------------------
SNMP COLDSTART 5 1 00:00:11
------------- ------------------------------- -----------------------------
Table 118 describes the significant fields shown in the display.
Table 118 show logging count Field Descriptions
Field
|
Description
|
Facility
|
The facility, such as syslog, from which these error messages are occurring.
|
Message Name
|
The name of this message.
|
Sev
|
The severity level of this message.
|
Occur
|
How many times this message has occurred.
|
Last Time
|
The last (most recent) time this message occurred. Timestamping is by default based on the system uptime (for example "3w1d" indicates 3 weeks and 1 day from the last system reboot.)
|
Sys Total / Lineproto Total / Link Total / SNMP Total
|
Total number of error messages that have occurred for the specified Facility.
|
In the following example, the user is interested only in the totals:
Router# show logging count | include total
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
logging count
|
Enables the system error message log count capability.
|
service timestamps
|
Configures the system to time-stamp debugging or logging messages.
|
show logging
|
Displays general information about the state of system logging.
|
show logging history
To display information about the state of the syslog history table, use the show logging history command in privileged EXEC mode.
show logging history
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command displays information about the syslog history table, such as the table size, the status of messages, and text of messages stored in the table. Messages stored in the table are governed by the logging history global configuration command.
Examples
The following example shows sample output from the show logging history command. In this example, notifications of severity level 5 (notifications) through severity level 0 (emergencies) are configured to be written to the logging history table.
Router# show logging history
Syslog History Table: 1 maximum table entries,
saving level notifications or higher
0 messages ignored, 0 dropped, 15 table entries flushed,
SNMP notifications not enabled
entry number 16: SYS-5-CONFIG_I
Configured from console by console
Table 119 describes the significant fields shown in the output.
Table 119 show logging history Field Descriptions
Field
|
Description
|
maximum table entry
|
Number of messages that can be stored in the history table. Set with the logging history size command.
|
saving level notifications <x> or higher
|
Level of messages that are stored in the history table and sent to the SNMP server (if SNMP notification is enabled). The severity level can be configured with the logging history command.
|
messages ignored
|
Number of messages not stored in the history table because the severity level is greater than that specified with the logging history command.
|
dropped
|
Number of messages that could not be processed due to lack of system resources. Dropped messages do not appear in the history table and are not sent to the SNMP server.
|
table entries flushed
|
Number of messages that have been removed from the history table to make room for newer messages.
|
SNMP notifications
|
Whether syslog traps of the appropriate level are sent to the SNMP server. The sending of syslog traps are enabled or disabled through the snmp-server enable traps syslog command.
|
entry number:
|
Number of the message entry in the history table. In the example above, the message "SYS-5-CONFIG_I Configured from console by console" indicates a syslog message consisting of the facility name (SYS), which indicates where the message came from, the severity level (5) of the message, the message name (CONFIG_I), and the message text.
|
timestamp
|
Time, based on the up time of the router, that the message was generated.
|
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
logging history
|
Limits syslog messages sent to the router's history table to a specified severity level.
|
logging history size
|
Changes the number of syslog messages that can be stored in the history table.
|
logging linecard
|
Logs messages to an internal buffer on a line card. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
|
snmp-server enable traps
|
The [no] snmp-server enable traps syslog form of this command controls (enables or disables) the sending of system-logging messages to a network management station.
|
show logging xml
To display the state of system message logging in an XML format, and to display the contents of the XML syslog buffer, use the show logging xml command in privileged EXEC mode.
show logging xml
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
This command displays the same syslog state information as the standard show logging command, but displays the information in XML format. This command also displays the content of the XML syslog buffer (if XML-formatted buffer logging is enabled).
Examples
The following example compares the output of the standard show logging command with the output of the show logging xml command so that you can see how the standard information is formatted in XML.
Syslog logging: enabled (10 messages dropped, 6 messages rate-limited, 0 flushes, 0
overruns, xml enabled)
Console logging: level debugging, 28 messages logged, xml enabled
Monitor logging: level debugging, 0 messages logged, xml enabled
Buffer logging: level debugging, 2 messages logged, xml enabled (2 messages logged)
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
Trap logging: level informational, 35 message lines logged
Logging to 1.2.3.4, 1 message lines logged, xml disabled
Logging to 4.3.2.1, 1 message lines logged, xml enabled
00:04:20: %SYS-5-CONFIG_I: Configured from console by console
00:04:41: %SYS-5-CONFIG_I: Configured from console by console
<syslog-logging status="enabled" msg-dropped="10" msg-rate-limited="6" flushes="0"
overruns="0"><xml>enabled</xml></syslog-logging>
<console-logging level="debugging"
messages-logged="28"><xml>enabled</xml></console-logging>
<monitor-logging level="debugging"
messages-logged="0"><xml>enabled</xml></monitor-logging>
<buffer-logging level="debugging" messages-logged="2"><xml
messages-logged="2">enabled</xml></buffer-logging>
<logging-exception size="8192 bytes"></logging-exception>
<count-and-timestamp-logging status="disabled"></count-and-timestamp-logging>
<trap-logging level="informational" messages-lines-logged="35"></trap-logging>
<logging-to><dest id="0" ipaddr="1.2.3.4"
message-lines-logged="1"><xml>disabled</xml><dest></logging-to>
<logging-to><dest id="1" ipaddr="4.3.2.1"
message-lines-logged="1"><xml>enabled</xml><dest></logging-to>
<log-xml-buffer size="44444 bytes"></log-xml-buffer>
<ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time>
00:04:20</time><args><arg id="0">console</arg><arg
id="1">console</arg></args></ios-log-msg>
<ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time>
00:04:41</time><args><arg id="0">console</arg><arg
id="1">console</arg></args></ios-log-msg>
Table 120 describes the significant fields shown in the displays.
Table 120 show logging and show logging xml Field Descriptions
Field
|
Description
|
XML Tag
|
Syslog logging
|
The global state of system message logging (syslog); "enabled" or "disabled."
|
syslog-logging
|
Console logging
|
State of logging to console connections.
|
console-logging
|
Monitor logging
|
State of logging to monitor (TTY and Telnet) connections.
|
monitor-logging
|
Buffer logging
|
State of logging to the local system logging buffer.
|
buffer-logging
|
Count and timestamp logging messages:
|
Indicates whether the logging count feature is enabled. Corresponds to the logging count command.
|
count-and-timestamp-logging
|
Trap logging
|
State of logging to a remote host.
|
trap-logging
|
Related Commands
Command
|
Description
|
show logging count
|
Displays counts of each system error message.
|
show logging history
|
Displays the contents of the SNMP syslog history table.
|
show logging
|
Displays the contents of the standard syslog buffer.
|
show management event
To display the Simple Network Management Protocol (SNMP) Event values that have been configured on your routing device through the use of the Event MIB, use the show management event command in privileged EXEC mode.
show management event
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
The Event MIB allows you to configure your own traps, informs, or set operations through the use of an external network management application. The show management event command is used to display the values for the Events configured on your system. There are no Cisco IOS CLI commands for configuring Event MIB values. For information on Event MIB functionality, see RFC 2981, available at http://www.ietf.org.
Examples
The following example shows sample output of the show management event command:
Router# show management event
(1): 01, Comment: TestEvent, Sample: Abs, Freq: 120
Test: Existence Threshold Boolean
ObjectOwner: aseem, Object: sethi
OID: ifEntry.10.3, Enabled 1, Row Status 1
Existence Entry: , Absent, Changed
ObjOwn: , Obj: , EveOwn: aseem, Eve: 09
Value: 10, Cmp: 1, Start: 1
ObjOwn: , Obj: , EveOwn: aseem, Eve: 09
Rising: 50000, Falling: 20000
ObjOwn: ase, Obj: 01 RisEveOwn: ase, RisEve: 09 , FallEveOwn: ase, FallEve: 09
(0): Thresh: Rising, Exis: 1, Read: 0, OID: ifEntry.10.3 , val: 69356097
(1)Name: 09 , Comment: , Action: Set, Notify, Enabled: 1 Status: 1
ObjOwn: , Obj: , OID: ifEntry.10.1
OID: ciscoSyslogMIB.1.2.1.0, SetValue: 199, Wildcard: 2 TAG: , ContextName:
(1)Name: sethi, Index: 1, OID: ifEntry.10.1, Wild: 1, Status: 1
Related Commands
Command
|
Description
|
debug management event
|
Allows real-time monitoring of Event MIB activities for the purposes of debugging.
|
show memory
To display statistics about memory, including memory-free pool statistics, use the show memory command in EXEC mode.
show memory [memory-type] [free] [overflow] [summary]
Syntax Description
memory-type
|
(Optional) Memory type to display (processor, multibus, io, or sram). If memory-type is not specified, statistics for all memory types present are displayed.
|
free
|
(Optional) Displays free memory statistics.
|
overflow
|
(Optional) Displays details about memory block header corruption corrections when the exception memory ignore overflow global configuration command is configured.
|
summary
|
(Optional) Displays a summary of memory usage including the size and number of blocks allocated for each address of the system call that allocated the block.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.3(7)T
|
This command was enhanced with the overflow keyword to display details about memory block header corruption corrections.
|
12.2(25)S, 12.3(14)T
|
The command output was updated to display information about transient memory pools.
|
Usage Guidelines
The show memory command displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the show memory command:
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210036 2971860 2692456 2845368
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:
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210076 2971820 2692456 2845368
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
CEB844 32 CEB7A4 CEB88C 0 0 0 96B894 SSE Manager
D35ED4 80 D35E30 D35F4C 0 0 D27AE8 96B894 SSE Manager
D27AE8 80 D27A48 D27B60 0 D35ED4 0 22585E SSE Manager
D0A8F4 100 D0A8B0 D0A980 0 0 0 2258DA SSE Manager
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 displayed in order for each free list.
The first section of the display includes summary statistics about the activities of the system memory allocator. Table 121 describes the significant fields shown in the first section of the display.
Table 121 show memory Field Descriptions-First Section
Field
|
Description
|
Head
|
Hexadecimal address of the head of the memory allocation chain.
|
Total(b)
|
Sum of used bytes plus free bytes.
|
Used(b)
|
Amount of memory in use.
|
Free(b)
|
Amount of memory not in use.
|
Lowest(b)
|
Smallest amount of free memory since last boot.
|
Largest(b)
|
Size of largest available free block.
|
The second section of the display is a block-by-block listing of memory use. Table 122 describes the significant fields shown in the second section of the display.
Table 122 Characteristics of Each Block of Memory-Second Section
Field
|
Description
|
Address
|
Hexadecimal address of block.
|
Bytes
|
Size of block (in bytes).
|
Prev.
|
Address of previous block (should match the address on previous line).
|
Next
|
Address of next block (should match the address on next line).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of previous free block (if free).
|
NextF
|
Address of next free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
What
|
Name of process that owns the block, or "(fragment)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
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:
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
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:
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
7AE0 38178 72F0 0 0 0 0 0
The following example of the show memory command used on the Cisco 4000 router includes information about SRAM memory and I/O 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 121 and Table 122.
Router# show memory summary
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210216 2971680 2692456 2845368
Alloc PC Size Blocks Bytes What
0x2AB2 192 1 192 IDB: Serial Info
0xC916 128 50 6400 RIF Cache
0x76ADE 4500 1 4500 XDI data
0x76E84 4464 1 4464 XDI data
0x76EAC 692 1 692 XDI data
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)
Related Commands
Command
|
Description
|
exception memory ignore overflow
|
Configures the Cisco IOS software to correct corruptions in memory block headers and allow a router to continue its normal operation.
|
show processes memory
|
Displays memory used per process.
|
show memory allocating-process
To display statistics on allocated memory with corresponding allocating processes, use the show memory allocating-process command in user EXEC or privileged EXEC mode.
show memory allocating-process [totals]
Syntax Description
totals
|
(Optional) Displays allocating memory totals.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
The show memory allocating-process command displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the show memory allocating-process command:
Router# show memory allocating-process
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 44E03560 186632636 26131896 160500740 160402052 153078204
Fast 44DE3560 131072 58280 72792 72792 72764
Address Bytes Prev. Next Ref Alloc Proc Alloc PC What
6148EC40 1504 0 6148F24C 1 *Init* 602310FC List Elements
6148F24C 3004 6148EC40 6148FE34 1 *Init* 60231128 List Headers
6148FE34 9000 6148F24C 61492188 1 *Init* 6023C634 Interrupt Stack
61492188 44 6148FE34 614921E0 1 *Init* 60C17FD8 *Init*
614921E0 9000 61492188 61494534 1 *Init* 6023C634 Interrupt Stack
61494534 44 614921E0 6149458C 1 *Init* 60C17FD8 *Init*
6149458C 220 61494534 61494694 1 *Init* 602450F4 *Init*
61494694 4024 6149458C 61495678 1 *Init* 601CBD64 TTY data
Table 123 describes the significant fields shown in the display.
Table 123 show memory allocating-process Field Descriptions
Field
|
Description
|
Head
|
Hexadecimal address of the head of the memory allocation chain.
|
Total(b)
|
Sum of used bytes plus free bytes.
|
Used(b)
|
Amount of memory in use in bytes.
|
Free(b)
|
Amount of memory not in use (in bytes).
|
Lowest(b)
|
Smallest amount of free memory since last boot (in bytes).
|
Largest(b)
|
Size of largest available free block (in bytes).
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev.
|
Address of the preceding block (should match the address on preceding row).
|
Next
|
Address of the following block (should match the address on following row).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
Alloc PC
|
Address of the system call that allocated the block.
|
What
|
Name of process that owns the block, or "(fragment)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
The following is sample output from the show memory allocating-process totals command:
Router# show memory allocating-process totals
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 44E03560 186632636 26142524 160490112 160402052 153078204
Fast 44DE3560 131072 58280 72792 72792 72764
Allocator PC Summary for: Processor
0x4041AF8C 5710616 3189 *Packet Data*
0x4041AF40 2845480 3190 *Packet Header*
0x404DBA28 1694556 203 Process Stack
0x4066EA68 1074080 56 Init
0x404B5F68 1049296 9 pak subblock chunk
0x41DCF230 523924 47 TCL Chunks
0x404E2488 448920 6 MallocLite
0x4066EA8C 402304 56 Init
0x41273E24 320052 1 CEF: table event ring
0x404B510C 253152 24 TW Buckets
0x423FF210 218048 5 Dn48oC!M
0x421CB530 208144 1 epa crypto blk
0x417A07F0 196764 3 L2TP Hash Table
Table 121 describes the significant fields shown in the display.
Table 124 show memory allocating-process totals Field Descriptions
Field
|
Description
|
Head
|
Hexadecimal address of the head of the memory allocation chain.
|
Total(b)
|
Sum of used bytes plus free bytes.
|
Used(b)
|
Amount of memory in use (in bytes).
|
Free(b)
|
Amount of memory not in use (in bytes).
|
Lowest(b)
|
Smallest amount of free memory since last boot (in bytes).
|
Largest(b)
|
Size of the largest available free block in bytes.
|
PC
|
Program counter
|
Total
|
Total memory allocated by the process (in bytes).
|
Count
|
Number of allocations.
|
Name
|
Name of the allocating process.
|
Related Commands
Command
|
Description
|
show processes memory
|
Displays memory used per process.
|
show memory dead
To display statistics of memory allocated by processes that are now dead, use the show memory dead command in user EXEC or privileged EXEC mode.
show memory dead [totals]
Syntax Description
totals
|
(Optional) Displays memory totals for processes that have been terminated.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
The show memory dead command displays information about processes that have been terminated. Terminated processes accounts for memory allocated under another process.
Examples
The following is sample output from the show memory dead command:
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
I/O 600000 2097152 461024 1636128 1635224 1635960
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
1D8310 60 1D82C8 1D8378 1 3281FFE Router Init
2CA964 36 2CA914 2CA9B4 1 3281FFE Router Init
2CAA04 112 2CA9B4 2CAAA0 1 3A42144 OSPF Stub LSA RBTree
2CAAA0 68 2CAA04 2CAB10 1 3A420D4 Router Init
2ED714 52 2ED668 2ED774 1 3381C84 Router Init
2F12AC 44 2F124C 2F1304 1 3A50234 Router Init
2F1304 24 2F12AC 2F1348 1 3A420D4 Router Init
2F1348 68 2F1304 2F13B8 1 3381C84 Router Init
300C28 340 300A14 300DA8 1 3381B42 Router Init
Table 121 describes the significant fields shown in the display.
Table 125 show memory dead Field Descriptions
Field
|
Description
|
Head
|
Hexadecimal address of the head of the memory allocation chain.
|
Total(b)
|
Sum of used bytes plus free bytes.
|
Used(b)
|
Amount of memory in use.
|
Free(b)
|
Amount of memory not in use (in bytes).
|
Lowest(b)
|
Smallest amount of free memory since last boot (in bytes).
|
Largest(b)
|
Size of the largest available free block (in bytes).
|
Address
|
Hexadecimal address of the block (in bytes).
|
Bytes
|
Size of the block (in bytes).
|
Prev.
|
Address of the preceding block.
|
Next
|
Address of the following block.
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
What
|
Name of the process that owns the block, or "(fragment)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
show memory debug incremental
To display information about memory leaks after a starting time has been established, use the show memory debug incremental command in privileged EXEC mode.
show memory debug incremental {allocations | leaks [lowmem] | status}
Syntax Description
allocations
|
Displays all memory blocks that were allocated after issuing the set memory debug incremental starting-time command.
|
leaks
|
Displays only memory that was leaked after issuing the set memory debug incremental starting-time command.
|
lowmem
|
(Optional) Forces the memory leak detector to work in low memory mode, making no memory allocations.
|
status
|
Displays all memory blocks that were allocated after issuing the set memory debug incremental starting-time command.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(7)T
|
This command was introduced.
|
Usage Guidelines
The show memory debug incremental allocations command displays all the memory blocks that were allocated after the issue of a set memory debug incremental starting-time command. The displayed memory blocks are just memory allocations, they are not necessarily leaks.
The show memory debug incremental leaks command provides output similar to the show memory debug leaks command, except that it displays only memory that was leaked after the issue of a set memory debug incremental starting-time command.
The show memory debug incremental leaks lowmem command forces memory leak detection to work in low memory mode. The amount of time taken for analysis is considerably greater than that of normal mode. The output for this command is similar to the show memory debug leaks command, except that it displays only memory that was leaked after the issue of a set memory debug incremental starting-time command. You can use this command when you already know that normal mode memory leak detection will fail (perhaps by an unsuccessful previous attempt to invoke normal mode memory leak detection).
The show memory debug incremental status command displays whether a starting point for incremental analysis has been set and the elapsed time since then.
Note
All memory leak detection commands invoke normal mode memory leak detection, except when the low memory option is specifically invoked by use of the lowmem keyword. In normal mode, if memory leak detection determines that there is insufficient memory to proceed in normal mode, it will display an appropriate message and switch to low memory mode
Examples
show memory debug incremental allocations Command Example
The following example shows output from the show memory debug incremental command when entered with the allocations keyword:
Router# show memory debug incremental allocations
Address Size Alloc_pc PID Name
62DA4E98 176 608CDC7C 44 CDP Protocol
62DA4F48 88 608CCCC8 44 CDP Protocol
62DA4FA0 88 606224A0 3 Exec
62DA4FF8 96 606224A0 3 Exec
635BF040 96 606224A0 3 Exec
63905E50 200 606A4DA4 69 Process Events
show memory debug incremental status Command Example
The following example shows output from the show memory debug incremental command entered with the status keyword:
Router# show memory debug incremental status
Incremental debugging is enabled
Time elapsed since start of incremental debugging: 00:00:10
Related Commands
Command
|
Description
|
set memory debug incremental starting-time
|
Sets the current time as the starting time for incremental analysis.
|
show memory debug leaks
|
Displays detected memory leaks.
|
show memory debug leaks
To display detected memory leaks, use the show memory debug leaks command in privileged EXEC mode.
show memory debug leaks [chunks | largest | lowmem | summary]
Syntax Description
chunks
|
(Optional) Displays the memory leaks in chunks.
|
largest
|
(Optional) Displays the top ten leaking allocator_pcs based on size, and the total amount of memory they have leaked.
|
lowmem
|
(Optional) Forces the memory leak detector to work in low memory mode, making no memory allocations.
|
summary
|
(Optional) Reports summarized memory leaks based on allocator_pc and size of the memory block.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(8)T1
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
If no optional keywords are specified, the show memory debug leaks command invokes normal mode memory leak detection and does not look for memory leaks in chunks.
The show memory debug leaks chunks command invokes normal mode memory leak detection and looks for leaks in chunks as well.
The show memory debug leaks largest command displays the top ten leaking allocator_pcs and the total amount of memory that they have leaked. Additionally, each time this command is invoked it remembers the previous invocation's report and compares it to the current invocation's report. If there are new entries in the current report they are tagged as "inconclusive." If the same entry appears in the previous invocation's report and the current invocation's report, the inconclusive tag is not added. It would be beneficial to run memory leak detection more than once and to consider only the consistently reported leaks.
The show memory debug leaks lowmem command forces memory leak detection to work in low memory mode. The amount of time taken for analysis is considerably greater than that of normal mode. The output for this command is similar to the show memory debug leaks command. You can use this command when you already know that normal mode memory leak detection will fail (perhaps by an unsuccessful previous attempt to invoke normal mode memory leak detection).
The show memory debug leaks summary command reports memory leaks based on allocator_pc and then on the size of the block.
Note
All memory leak detection commands invoke normal mode memory leak detection, except when the low memory option is specifically invoked by use of the lowmem keyword. In normal mode, if memory leak detection determines that there is insufficient memory to proceed in normal mode, it will display an appropriate message and switch to low memory mode
Examples
show memory debug leaks Command Example
The following example shows output from the show memory debug leaks command:
Router# show memory debug leaks
Address Size Alloc_pc PID Name
Address Size Alloc_pc PID Name
Address Size Alloc_pc PID Name
62DABD28 80 60616750 -2 Init
62DABD78 80 606167A0 -2 Init
62DCF240 88 605B7E70 -2 Init
62DCF298 96 605B7E98 -2 Init
62DCF2F8 88 605B7EB4 -2 Init
62DCF350 96 605B7EDC -2 Init
63336C28 104 60C67D74 -2 Init
63370D58 96 60C656AC -2 Init
633710A0 304 60C656AC -2 Init
63B2BF68 96 60C659D4 -2 Init
63BA3FE0 32832 608D2848 104 Audit Process
63BB4020 32832 608D2FD8 104 Audit Process
Table 126 describes the significant fields shown in the display.
Table 126 show memory debug leaks Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the leaked block.
|
Size
|
Size of the leaked block (in bytes).
|
Alloc_pc
|
Address of the system call that allocated the block.
|
PID
|
The process identifier of the process that allocated the block.
|
Name
|
The name of the process that allocated the block.
|
show memory debug leaks chunks Command Example
The following example shows output from the show memory debug leaks chunks command:
Router# show memory debug leaks chunks
Address Size Alloc_pc PID Name
Address Size Alloc_pc PID Name
Address Size Alloc_pc PID Name
62DABD28 80 60616750 -2 Init
62DABD78 80 606167A0 -2 Init
62DCF240 88 605B7E70 -2 Init
62DCF298 96 605B7E98 -2 Init
62DCF2F8 88 605B7EB4 -2 Init
62DCF350 96 605B7EDC -2 Init
63336C28 104 60C67D74 -2 Init
63370D58 96 60C656AC -2 Init
633710A0 304 60C656AC -2 Init
63B2BF68 96 60C659D4 -2 Init
63BA3FE0 32832 608D2848 104 Audit Process
63BB4020 32832 608D2FD8 104 Audit Process
62D80DA8 16 62D7BFD0 (Managed Chunk )
62D80DB8 16 62D7BFD0 (Managed Chunk )
62D80DC8 16 62D7BFD0 (Managed Chunk )
62D80DD8 16 62D7BFD0 (Managed Chunk )
62D80DE8 16 62D7BFD0 (Managed Chunk )
62E8FD60 216 62E8F888 (IPC Message He)
Table 127 describes the significant fields shown in the display.
Table 127 show memory debug leaks chunks Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the leaked block.
|
Size
|
Size of the leaked block (in bytes).
|
Alloc_pc
|
Address of the system call that allocated the block.
|
PID
|
The process identifier of the process that allocated the block.
|
Name
|
The name of the process that allocated the block.
|
Size
|
(Chunk Elements) Size of the leaked element (bytes).
|
Parent
|
(Chunk Elements) Parent chunk of the leaked chunk.
|
Name
|
(Chunk Elements) The name of the leaked chunk.
|
show memory debug leaks largest Command Example
The following example shows output from the show memory debug leaks largest command:
Router# show memory debug leaks largest
608D2848 32776 inconclusive
608D2FD8 32776 inconclusive
60C656AC 288 inconclusive
The following example shows output from the second invocation of the show memory debug leaks largest command:
Router# show memory debug leaks largest
show memory debug leaks summary Command Example
The following example shows output from the show memory debug leaks summary command:
Router# show memory debug leaks summary
Alloc PC Size Blocks Bytes What
Alloc PC Size Blocks Bytes What
Alloc PC Size Blocks Bytes What
0x605B7E70 0000000032 0000000001 0000000032 Init
0x605B7E98 0000000040 0000000001 0000000040 Init
0x605B7EB4 0000000032 0000000001 0000000032 Init
0x605B7EDC 0000000040 0000000001 0000000040 Init
0x60616750 0000000024 0000000001 0000000024 Init
0x606167A0 0000000024 0000000001 0000000024 Init
0x608D2848 0000032776 0000000001 0000032776 Audit Process
0x608D2FD8 0000032776 0000000001 0000032776 Audit Process
0x60C656AC 0000000040 0000000001 0000000040 Init
0x60C656AC 0000000248 0000000001 0000000248 Init
0x60C659D4 0000000040 0000000001 0000000040 Init
0x60C67D74 0000000048 0000000001 0000000048 Init
Table 128 describes the significant fields shown in the display.
Table 128 show memory debug leaks summary Field Descriptions
Field
|
Description
|
Alloc_pc
|
Address of the system call that allocated the block.
|
Size
|
Size of the leaked block.
|
Blocks
|
Number of blocks leaked.
|
Bytes
|
Total amount of memory leaked.
|
What
|
Name of the process that owns the block.
|
Related Commands
Command
|
Description
|
set memory debug incremental starting-time
|
Sets the current time as the starting time for incremental analysis.
|
show memory debug incremental allocation
|
Displays all memory blocks that were allocated after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental leaks
|
Displays only memory that was leaked after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental leaks lowmem
|
Forces incremental memory leak detection to work in low memory mode. Displays only memory that was leaked after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental status
|
Displays if the starting point of incremental analysis has been defined and the time elapsed since then.
|
show memory debug references
To display the list of blocks containing references to a given range of addresses in the memory or references to free memory, use the show memory debug references command in user EXEC or privileged EXEC mode.
show memory debug references [dangling[start-address start-address ]]
Syntax Description
dangling
|
(Optional) Displays the possible references to free memory.
|
start-address
|
(Optional) Address numbers <0-4294967295> that determine the address range.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory debug references command:
Router# show memory debug references 2 3
Address Reference Cont_block Cont_block_name
The following is sample output from the show memory debug references dangling command:
Router# show memory debug references dangling
Address Reference Free_block Cont_block Cont_block_name
442D5774 458CE5EC 458CE5BC 44284960 bss
442D578C 46602998 46602958 44284960 bss
442D58A0 465F9BC4 465F9B94 44284960 bss
442D58B8 4656785C 4656781C 44284960 bss
442D5954 45901E7C 45901E4C 44284960 bss
Table 121 describes the significant fields shown in the displays.
Table 129 show memory debug references Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block that has the given or dangling reference.
|
Reference
|
Address which is given or dangling.
|
Free_block
|
Address of the free block which now contains the memory referenced by the dangling reference.
|
Cont_block
|
Address of the control block which contains the block that has the reference.
|
Cont_block_name
|
Name of the control block.
|
show memory debug unused
To display the list of memory blocks which have been allocated but not used, use the show memory debug unused command in user EXEC or privileged EXEC mode.
show memory debug unused
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory debug unused command:
Router# show memory debug unused
Address Alloc_pc PID size Name
654894B8 62BF31DC -2 44 *Init*
6549A074 601F7A84 -2 4464 XDI data
6549B218 601F7274 -2 4500 XDI data
6549DFB0 6089DDA4 42 84 Init
65509160 6089DDA4 1 84 *Init*
6550A260 6089DDA4 2 84 *Init*
6551FDB4 6089DDA4 4 84 *Init*
6551FF34 627EFA2C -2 24 *Init*
65520B3C 6078B1A4 -2 24 Parser Mode Q1
65520B88 6078B1C8 -2 24 Parser Mode Q2
65520C40 6078B1A4 -2 24 Parser Mode Q1
65520C8C 6078B1C8 -2 24 Parser Mode Q2
65520D44 6078B1A4 -2 24 Parser Mode Q1
65520D90 6078B1C8 -2 24 Parser Mode Q2
65520E48 6078B1A4 -2 24 Parser Mode Q1
65520E94 6078B1C8 -2 24 Parser Mode Q2
65520F4C 6078B1A4 -2 24 Parser Mode Q1
65520F98 6078B1C8 -2 24 Parser Mode Q2
65521050 6078B1A4 -2 24 Parser Mode Q1
6552109C 6078B1C8 -2 24 Parser Mode Q2
65521154 6078B1A4 -2 24 Parser Mode Q1
655211A0 6078B1C8 -2 24 Parser Mode Q2
Table 123 describes the significant fields shown in the display.
Table 130 show memory debug unused Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Alloc_pc
|
Address of the system call that allocated the block.
|
PID
|
Process identifier of the process that allocated the block.
|
size
|
Size of the unused block (in bytes).
|
Name
|
Name of the process that owns the block.
|
show memory ecc
To display single-bit Error Code Correction (ECC) error logset data, use the show memory ecc command in privileged EXEC mode.
show memory ecc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1(30)CC
|
This command was introduced in Cisco IOS Release 11.1(30)CC.
|
12.0(4)XE
|
This command was integrated into Cisco IOS Release 12.0(4)XE.
|
12.0(6)S
|
This command was integrated into Cisco IOS Release 12.0(6)S.
|
12.1(13)
|
This command was integrated into Cisco IOS Release 12.1(13).
|
Usage Guidelines
Use this command to determine if the router has experienced single-bit parity errors.
Examples
The following is sample output from the show memory ecc command from a 12000-series router running Cisco IOS Release 12.0(23)S:
Single Bit error detected and corrected at 0x574F3640
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0xE9
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write Single Bit error detected and corrected at
0x56AB3760
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0x68
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write
Total Single Bit error(s) thus far: 2
Table 121 describes the significant fields shown in the first section of the display.
Table 131 show memory ecc Field Descriptions
Field
|
Description
|
Occured n time(s)
|
Number of single-bit errors that has occurred.
|
Whether a scrub was attempted at this address:
|
Indicates whether a scrub has been performed.
|
Syndrome of the last error at this address:
|
Describes the syndrome of last error.
|
Error detected on a read-modify-write cycle ?
|
Indicates whether an error has occurred.
|
Address region classification: Unknown
|
Describes the region of the error.
|
Address media classification :
|
Describes the media of the error and correction.
|
Related Commands
Command
|
Description
|
show memory
|
Displays statistics about memory, including memory-free pool statistics.
|
show memory failures alloc
To display statistics about failed memory allocation requests, use the show memory failures alloc command in the privileged EXEC mode.
show memory failures alloc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory failures alloc command:
Router# show memory failures alloc
Caller Pool Size Alignment When
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:03
0x60394744 I/O 1684 32 00:10:04
0x60394744 I/O 1684 32 00:10:04
Table 121 describes the significant fields shown in the display.
Table 132 show memory failures alloc Field Descriptions
Field
|
Description
|
Caller
|
Address of the allocator function that issued memory allocation request that failed.
|
Pool
|
Pool from which the memory was requested.
|
Size
|
Size of the memory requested in bits.
|
Alignment
|
Memory alignment in bits.
|
When
|
Time of day at which the memory allocation request was issued.
|
show memory fragment
To display the block details of fragmented free blocks and allocated blocks, which is physically just before or after the blocks on the free list, use the show memory fragment command in user EXEC or privileged EXEC mode.
show memory [processor | io] fragment [detail]
Syntax Description
processor
|
(Optional) Displays the processor memory information.
|
io
|
(Optional) Displays the I/O memory information.
|
fragment
|
Displays the information of the free blocks and the blocks surrounding the free blocks.
|
detail
|
(Optional) Displays the detailed information of all the free blocks and the blocks surrounding the free blocks that is located between the allocated blocks.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Examples
The following is sample output from the show memory processor fragment command:
Router# show memory processor fragment
Free memory size : 65516944 Number of free blocks: 230
Allocator PC Summary for allocated blocks in pool: Processor
0x6047DDCC 852020 1 atmdx_vc_table
0x6075DC30 544392 4 ATM1/0
0x61BDBA14 131176 2 eddri_self_event
0x61913BEC 131124 1 l2tp tnl table
0x602E9820 114832 1 AutoVC Msg Chunk
0x607DF5BC 96624 12 Process Stack
0x6118DDA0 77252 1 Spanning Tree Opt Port Block
0x61F13C30 67636 1 QOS_MODULE_MAIN
0x6047DD3C 65640 2 atmdx_tx_shadow
0x614B6624 65588 1 CEF: loadinfo chunk
0x614D1924 65588 1 IP mtrie node
0x614A58A0 65588 1 CEF: 16 path chunk pool
0x619241D4 65588 1 PPTP mgd timer chunk
0x606581CC 65588 1 AAA DB Chunk
0x607E5EAC 65588 1 MallocLite
0x6192420C 65588 1 PPTP: pptp_tunneltype chunk
0x6075DCB8 45924 10 FastEthernet2/
0x607CA400 36288 2 pak subblock chunk
0x6255648C 28948 1 CCPROXY_CT
0x6047DD7C 24628 1 atmdx_bfd_cache
0x6047DAA4 23500 1 atmdx_instance
0x6047DAE8 23500 1 atmdx_instance snap
0x60962DFC 21420 17 TCP CB
0x616F729C 20052 1 AC context chunks
0x616F72C8 20052 1 AC Mgr mgd timer chunk
0x60734010 16644 19 *Packet Header*
0x6047DE0C 16436 1 atmdx_abr_stats
0x6047DCFC 16112 2 atmdx_rx_pool_info
0x60A77E98 13060 1 DHCPD Message Workspace
0x61F50008 12852 1 CCVPM_HTSP
0x60D509BC 12580 17 Virtual Exec
0x60EFA1EC 12344 1 RSVP DB Handle Bin
0x6067AE44 76 1 AAA Secrettype encrypt
0x60F76B1C 76 1 SNMP Trap
0x62638F78 76 1 EEM ED Syslog
0x608F7030 76 1 IPC Name String
0x620468A8 76 1 ivr: ccapAppEntry_t name
0x6066D084 76 1 gk process
0x6064824C 76 1 AAA MI SG NAME
Allocator PC Summary for free blocks in pool: Processor
0x6071253C 67387912 2 (fragment)
0x60734010 63292440 11 *Packet Header*
0x60962DFC 105552 10 (coalesced)
0x60D509BC 98384 10 (coalesced)
0x60D4A0B4 70776 9 (coalesced)
0x60803260 21488 4 (fragment)
0x60B2E488 19704 2 (fragment)
0x606E0278 19272 1 (coalesced)
0x60B27FE8 5740 3 (fragment)
0x60778AAC 3504 1 (coalesced)
0x607AC764 2212 11 Process Events
0x60F7FCD4 1556 9 (fragment)
0x6071F3FC 1316 12 (fragment)
0x606C5324 1176 6 (coalesced)
0x60D7C518 1148 1 (coalesced)
0x624E170C 876 1 (coalesced)
0x60A68164 588 3 (fragment)
0x60B302C0 408 5 (fragment)
0x60976574 272 2 AAA Event Data
0x60801E38 216 2 (fragment)
0x611DA23C 164 1 shelf_info
0x60A6A638 148 1 (fragment)
0x60801D2C 148 1 (fragment)
0x60D29DCC 148 1 (fragment)
0x62628CA0 144 1 (fragment)
0x60A68218 104 1 (fragment)
0x606B9614 88 1 NameDB String
0x6090A978 84 1 (fragment)
0x606C51D0 84 1 (fragment)
0x62647558 76 1 (fragment)
The following is sample output from the show memory processor fragment detail command:
Router# show memory processor fragment detail
Free memory size : 65566148 Number of free blocks: 230
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
645A8148 0000000028 645A80F0 645A8194 001 -------- -------- 60695B20 Init
645A8194 0000000040 645A8148 645A81EC 000 0 200B4300 606B9614 NameDB String
645A81EC 0000000260 645A8194 645A8320 001 -------- -------- 607C2D20 Init
200B42B4 0000000028 200B4268 200B4300 001 -------- -------- 62366C80 Init
200B4300 0000000028 200B42B4 200B434C 000 645A8194 6490F7E8 60976574 AAA Event Data
200B434C 0000002004 200B4300 200B4B50 001 -------- -------- 6267D294 Coproc Request
Structures
6490F79C 0000000028 6490F748 6490F7E8 001 -------- -------- 606DDA04 Parser Linkage
6490F7E8 0000000028 6490F79C 6490F834 000 200B4300 6491120C 606DD8D8 Init
6490F834 0000006004 6490F7E8 64910FD8 001 -------- -------- 607DF5BC Process Stack
649111A0 0000000060 64911154 6491120C 001 -------- -------- 606DE82C Parser Mode
6491120C 0000000028 649111A0 64911258 000 6490F7E8 500770F0 606DD8D8 Init
64911258 0000000200 6491120C 64911350 001 -------- -------- 603F0E38 Init
504DCF54 0000001212 504DB2E4 504DD440 001 -------- -------- 60962DFC TCP CB
2C41DCA4 0000000692 2C41BCC8 2C41DF88 001 -------- -------- 60D509BC Virtual Exec
2C41DF88 0000005344 2C41DCA4 2C41F498 000 504DB2E4 6449A828 60D509BC (coalesced)
2C41F498 0000000692 2C41DF88 2C41F77C 001 -------- -------- 60D509BC Virtual Exec
6449A544 0000000692 64499794 6449A828 001 -------- -------- 60D509BC Virtual Exec
6449A828 0000007760 6449A544 6449C6A8 000 2C41DF88 504D89D4 60D509BC (coalesced)
6449C6A8 0000008044 6449A828 6449E644 001 -------- -------- 60D2AACC Virtual Exec
504D8778 0000000556 504D754C 504D89D4 001 -------- -------- 60D4A0B4 Virtual Exec
504D89D4 0000009860 504D8778 504DB088 000 6449A828 504D1B78 60D4A0B4 (coalesced)
504DB088 0000000556 504D89D4 504DB2E4 001 -------- -------- 60D4A0B4 Virtual Exec
504D168C 0000001212 504C9658 504D1B78 001 -------- -------- 60962DFC TCP CB
504D1B78 0000008328 504D168C 504D3C30 000 504D89D4 504C5B54 60962DFC (coalesced)
504D3C30 0000001212 504D1B78 504D411C 001 -------- -------- 60962DFC TCP CB
504C5870 0000000692 504C5504 504C5B54 001 -------- -------- 60D509BC Virtual Exec
504C5B54 0000005344 504C5870 504C7064 000 504D1B78 2C423A88 60D509BC (coalesced)
504C7064 0000000408 504C5B54 504C722C 001 -------- -------- 606E0E44 Chain Cache No
2C42359C 0000001212 2C41F77C 2C423A88 001 -------- -------- 60962DFC TCP CB
2C423A88 0000008328 2C42359C 2C425B40 000 504C5B54 504D411C 60962DFC (coalesced)
504E7DD8 0000000828 504E2660 504E8144 001 -------- -------- 60734010 *Packet Header*
65006A08 0000000408 65003834 65006BD0 001 -------- -------- 606E0E44 Chain Cache No
65006BD0 0000020520 65006A08 6500BC28 000 504E2660 0 60803260 (coalesced)
6500BC28 0000000828 65006BD0 6500BF94 001 -------- -------- 60734010 *Packet Header*
5C3AE7B8 0000000828 5C3AE614 5C3AEB24 001 -------- -------- 60734010 *Packet Header*
5C3AEB24 0063247532 5C3AE7B8 20000000 000 0 6500C300 60734010 (coalesced)
20000000 0000000828 5C3AEB24 2000036C 001 -------- -------- 60734010 *Packet Header*
6500BF94 0000000828 6500BC28 6500C300 001 -------- -------- 60734010 *Packet Header*
6500C300 0004760912 6500BF94 50000000 000 5C3AEB24 2C42E310 6071253C (coalesced)
50000000 0000000828 6500C300 5000036C 001 -------- -------- 60734010 *Packet Header*
2C42E0B4 0000000556 2C429430 2C42E310 001 -------- -------- 60D4A0B4 Virtual Exec
2C42E310 0062725312 2C42E0B4 00000000 000 6500C300 0 6071253C (coalesced)
Related Commands
Command
|
Description
|
memory io
|
Configures thresholds for I/O memory.
|
memory processor
|
Configures thresholds for processor memory.
|
show memory multibus
To display statistics about multibus memory, including memory-free pool statistics, use the show memory multibus command in user EXEC or privileged EXEC mode.
show memory multibus [allocating-process [totals]| dead [totals]| free [totals]]
Syntax Description
allocating-process [totals]
|
(Optional) Displays allocating memory totals by name.
|
dead [totals]
|
(Optional) Displays memory totals on dead processes.
|
fragment [detail]
|
(Optional) Displays memory statistics for fragmented processes.
|
free [totals]
|
(Optional) Displays statistics on free memory.
|
statistics [history]
|
(Optional) Displays memory pool history statistics on all processes.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory multibus command:
Router# show memory multibus
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes
6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes
65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes
65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k
654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k
6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)
65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s
654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles
654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas
654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*
Table 133 describes the significant fields shown in the display.
Table 133 show memory multibus Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev
|
Address of the preceding block (should match the address on the preceding line).
|
Next
|
Address of the following block (should match the address on the following line).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
What
|
Name of the process that owns the block, or "(fragmen)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
show memory pci
To display statistics about Peripheral Component Interconnect (PCI) memory, use the show memory pci command in user EXEC or privileged EXEC mode.
show memory pci
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory pci command:
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
0E000000 0000000032 00000000 0E000050 000 64F5EBF4 0 00000000 (fragmen)
0E000050 0000000272 0E000000 0E000190 001 -------- -------- 607E2EC0 *Packet *
0E000190 0000000272 0E000050 0E0002D0 001 -------- -------- 607E2EC0 *Packet *
0E0002D0 0000000272 0E000190 0E000410 001 -------- -------- 607E2EC0 *Packet *
0E000410 0000000272 0E0002D0 0E000550 001 -------- -------- 607E2EC0 *Packet *
0E000550 0000000272 0E000410 0E000690 001 -------- -------- 607E2EC0 *Packet *
0E000690 0000000272 0E000550 0E0007D0 001 -------- -------- 607E2EC0 *Packet *
0E0007D0 0000000272 0E000690 0E000910 001 -------- -------- 607E2EC0 *Packet *
0E000910 0000000272 0E0007D0 0E000A50 001 -------- -------- 607E2EC0 *Packet *
0E000A50 0000000272 0E000910 0E000B90 001 -------- -------- 607E2EC0 *Packet *
0E000B90 0000000272 0E000A50 0E000CD0 001 -------- -------- 607E2EC0 *Packet *
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
0E000CD0 0000000272 0E000B90 0E000E10 001 -------- -------- 607E2EC0 *Packet *
0E000E10 0000000272 0E000CD0 0E000F50 001 -------- -------- 607E2EC0 *Packet *
Table 121 describes the significant fields shown in the display.
Table 134 show memory pci Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev
|
Address of the preceding block (should match the address on the preceding line).
|
Next
|
Address of the following block (should match the address on the following line).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
what
|
Name of process that owns the block, or "(fragmen)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
show memory processor
To display statistics on the router processor memory, use the show memory processor command in user EXEC or privileged EXEC mode.
show memory processor [fragment | free | statistics]
Syntax Description
fragment
|
(Optional) Displays the block details of fragmented free blocks and allocated blocks, which are shown either preceding or following the blocks on the free list.
|
free
|
(Optional) Displays the number of free blocks.
|
statistics
|
(Optional) Displays only memory processor statistics.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory processor commands:
Router# show memory processor
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes
6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes
65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes
65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k
654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k
6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)
65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s
654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles
654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas
654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*
Table 135 describes the significant fields shown in the display.
Table 135 show memory processor Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev.
|
Address of the preceding block (should match the address on the preceding line).
|
Next
|
Address of the following block (should match the address on the following line).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
What
|
Name of the process that owns the block, or "(fragmen)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
The following is sample output from the show memory processor fragment command:
Router# show memory processor fragment
Free memory size : 3144348 Number of free blocks: 96
Allocator PC Summary for allocated blocks in pool: Processor
0x6069A038 262196 1 TACL FLT
0x62224AA8 219188 1 QOS_MODULE_MAIN
0x6218DAA4 73780 1 CCSIP_UDP_SOCKET
0x61649288 65588 1 CEF: loadinfo chunk
0x61BFD4B8 65588 1 PPTP mgd timer chunk
0x61EE1050 65588 1 eddri_self_event
0x608A0D4C 35208 4 Process Stack
0x6069D804 32052 1 TACL hist
0x61631A90 21444 2 CEF: IPv4 Unicast RPF subblock
0x6086F858 20052 1 RMI-RO_RU Chun
0x608CF99C 20052 1 Managed Chunk Queue Elements
Table 136 describes the significant fields shown in the display.
Table 136 show memory processor fragment Field Descriptions
Field
|
Description
|
PC
|
Program counter
|
Total
|
Total memory allocated by the process (in bytes).
|
Count
|
Number of allocations.
|
Name
|
Name of the allocating process.
|
The following is sample output from the show memory processor free command:
Router# show memory processor free
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
66994680 0000000072 66994618 669946FC 000 0 6698FFC8 60699114 Turbo ACr
6698FFC8 0000000072 6698FF60 66990044 000 66994680 659CF6B0 60699114 Turbo ACr
659CF6B0 0000000024 659CF678 659CF6FC 000 6698FFC8 659CF86C 6078A2CC Init
659CF86C 0000000024 659CF710 659CF8B8 000 659CF6B0 65ADB53C 6078A2CC Init
65ADB53C 0000000024 65ADB504 65ADB588 000 659CF86C 65ADFC38 6078A2CC Init
65ADFC38 0000000024 65ADFC00 65ADFC84 000 65ADB53C 65B6C504 6078A2CC Init
65B6C504 0000000024 65B6C4B8 65B6C550 000 65ADFC38 6593E924 6078A2CC Init
6593E924 0000000028 6593E8E8 6593E974 000 65B6C504 65CCB054 6078A2CC Init
65CCB054 0000000024 65CCB01C 65CCB0A0 000 6593E924 65CCBD98 6078A2CC Init
65CCBD98 0000000028 65CCBD60 65CCBDE8 000 65CCB054 65CCFB70 6078A2CC Init
65CCFB70 0000000024 65CCFB38 65CCFBBC 000 65CCBD98 65D0BB58 6078A2CC Init
65D0BB58 0000000024 65D0BB20 65D0BBA4 000 65CCFB70 65D0C5F0 6078A2CC Init
65D0C5F0 0000000024 65D0C5B8 65D0C63C 000 65D0BB58 65CFF2F4 6078A2CC Init
65CFF2F4 0000000024 65CFF2BC 65CFF340 000 65D0C5F0 6609B7B8 6078A2CC Init
6609B7B8 0000000036 6609AFC8 6609B810 000 65CFF2F4 660A0BD4 6078A2CC Init
Table 123 describes the significant fields shown in the display.
Table 137 show memory processor free Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev
|
Address of the preceding block (should match the address on preceding row).
|
Next
|
Address of the following block (should match the address on following row).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
what
|
Name of the process that owns the block, or "(fragment)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
The following is sample output from the show memory processor statistics command:
Router# show memory processor statistics
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 6540BBA0 415187836 27216968 387970868 385755044 381633404
I/O E000000 33554432 6226336 27328096 27328096 27317852
Table 121 describes the significant fields shown in the display.
Table 138 show memory processor statistics Field Descriptions
Field
|
Description
|
Head
|
Hexadecimal address of the head of the memory allocation chain.
|
Total(b)
|
Sum of the used bytes plus free bytes.
|
Used(b)
|
Amount of memory in use (in bytes).
|
Free(b)
|
Amount of memory not in use (in bytes).
|
Lowest(b)
|
Smallest amount of free memory since last boot (in bytes).
|
Largest(b)
|
Size of the largest available free block (in bytes).
|
show memory scan
To monitor the number and type of parity (memory) errors on your system, use the show memory scan command in EXEC mode.
show memory scan
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(4)XE
|
This command was introduced.
|
12.0(7)T
|
This command was implemented in Cisco IOS Release 12.0(7) T.
|
Examples
The following example shows a result with no memory errors:
No parity error has been detected.
If errors are detected in the system, the show memory scan command generates an error report. In the following example, memory scan detected a parity error:
Address BlockPtr BlckSize Disposit Region Timestamp
6115ABCD 60D5D090 9517A4 Scrubed Local 16:57:09 UTC Thu Mar 18
Table 139 describes the fields contained in the error report.
Table 139 show memory scan Field Descriptions
Field
|
Description
|
Address
|
The byte address where the error occurred.
|
BlockPtr
|
The pointer to the block that contains the error.
|
BlckSize
|
The size of the memory block
|
Disposit
|
The action taken in response to the error:
• BlockInUse—An error was detected in a busy block.
• InFieldPrev—An error was detected in the previous field of a block header.
• InHeader—An error was detected in a block header.
• Linked—A block was linked to a bad list.
• MScrubed—The same address was "scrubbed" more than once, and the block was linked to a bad list.
• MultiError—Multiple errors have been found in one block.
• NoBlkHdr—No block header was found.
• NotYet—An error was found; no action has been taken at this time.
• Scrubed—An error was "scrubbed."
• SplitLinked—A block was split, and only a small portion was linked to a bad list.
|
Region
|
The memory region in which the error was found:
• IBSS—image BSS
• IData—imagedata
• IText—imagetext
• local—heap
|
Timestamp
|
The time the error occurred.
|
show memory statistics history table
To display the history of memory consumption, use the show memory statistics history table command in user EXEC or privileged EXEC mode.
show memory statistics history table
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
The show memory statistics history table command displays a histogram of memory usage. The quantity on the x-axis is percentage of memory free and on the y-axis is time. The height of the histogram at any given point in time indicates the percentage of free memory in the pool.
Examples
The following is sample output from the show memory statistics history table command:
Router# show memory statistics history table
History for Processor memory
Used(b): 422748036 Largest(b): 381064952 Free blocks :291
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 422705876 Largest(b): 381064952 Free blocks :296
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 20700520 Largest(b): 381064952 Free blocks :196
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Used(b): 20717804 Largest(b): 381064952 Free blocks :189
Used(b): 20717804 Largest(b): 381064952 Free blocks :189
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 21011192 Largest(b): 381064952 Free blocks :186
Maximum memory users for this period
Process Name Holding Num Alloc
Proxy Session Applic 275424 21
Used(b): 7455520 Largest(b): 59370080 Free blocks :164
Used(b): 7458064 Largest(b): 59370080 Free blocks :165
Maximum memory users for this period
Process Name Holding Num Alloc
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Maximum memory users for this period
Process Name Holding Num Alloc
Table 126 describes the significant fields shown in the display.
Table 140 show memory statistics history table Field Descriptions
Field
|
Description
|
Time:
|
Time at which snapshot was taken. In hh:mm:ss.ms format.
|
Used(b):
|
Memory used (in bytes).
|
Largest(b):
|
Size of the largest block (in bytes).
|
Free blocks:
|
Number of free blocks.
|
Process Name
|
Name of the process.
|
Holding
|
Memory in bytes held by the process.
|
Num Alloc
|
Number of successful memory allocation requests made by the process.
|
Related Commands
Command
|
Description
|
memory statistics history table
|
Changes the memory log time.
|
show memory transient
To display statistics about transient memory, use the show memory transient command in user EXEC or privileged EXEC mode.
show memory transient [allocating-process [totals]| dead [totals]| fragment [detail]| free
[totals]| statistics [history]]
Syntax Description
allocating-process
|
(Optional) Displays allocating memory totals by name.
|
dead [totals]
|
(Optional) Displays memory totals on dead processes.
|
fragment [detail]
|
(Optional) Displays memory statistics for fragmented processes.
|
free [totals]
|
(Optional) Displays statistics on free memory.
|
statistics [history]
|
(Optional) Displays memory pool history statistics on all processes.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following is sample output from the show memory transient command:
Router# show memory transient
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
81F99C00 0002236408 00000000 821BBC28 000 829C8104 82776FD0 8060B6D0 (coalesc)
821BBC28 0000020004 81F99C00 821C0A7C 001 -------- -------- 8002D5C0 Managed s
821C0A7C 0000010004 821BBC28 821C31C0 001 -------- -------- 811604C0 List Eles
821C31C0 0000005004 821C0A7C 821C457C 001 -------- -------- 81160500 List Heas
Table 121 describes the significant fields shown in the display.
Table 141 show memory transient Field Descriptions
Field
|
Description
|
Address
|
Hexadecimal address of the block.
|
Bytes
|
Size of the block (in bytes).
|
Prev
|
Address of the preceding block (should match the address on preceding line).
|
Next
|
Address of the following block (should match the address on following line).
|
Ref
|
Reference count for that memory block, indicating how many different processes are using that block of memory.
|
PrevF
|
Address of the preceding free block (if free).
|
NextF
|
Address of the following free block (if free).
|
Alloc PC
|
Address of the system call that allocated the block.
|
what
|
Name of the process that owns the block, or "(fragment)" if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
|
show microcode
To display microcode image information available on line cards, use the show microcode command in EXEC mode.
show microcode
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show microcode command:
Microcode bundled in system
Card Microcode Target Hardware Description
---- --------- --------------- -----------
SP 2.3 11.x SP version 2.3
EIP 1.1 1.x EIP version 1.1
TRIP 1.2 1.x TRIP version 1.2
FIP 1.4 2.x FIP version 1.4
HIP 1.1 1.x HIP version 1.1
SIP 1.1 1.x SIP version 1.1
FSIP 1.1 1.x FSIP version 1.1
In the following example for the Cisco 7200 series router, the output from the show microcode command lists the hardware types that support microcode download. For each type, the default microcode image name is displayed. If there is a configured default override, that name also is displayed.
Microcode images for downloadable hardware
HW Type Microcode image names
------------------------------------------
ecpa default slot0:xcpa26-0
configured slot0:xcpa26-2
pcpa default slot0:xcpa26-4
Related Commands
Command
|
Description
|
microcode (7000/7500)
|
Specifies where microcode should be loaded from on Cisco 7500/7000RSP routers.
|
microcode (7200)
|
Configures a default override for the microcode that is downloaded to the hardware on a Cisco 7200 series router.
|
show monitor event-trace
To display event trace messages for Cisco IOS software subsystem components, use the show monitor event-trace command in privileged EXEC mode.
show monitor event-trace [all-traces] [component {all | back time | clock time | from-boot
seconds | latest | parameters}]
Syntax Description
all-traces
|
(Optional) Displays all event trace message in memory to the console.
|
component
|
(Optional) Name of the Cisco IOS software subsystem component that is the object of the event trace. To get a list of components that support event tracing in this release, use the monitor event-trace ? command.
|
all
|
Displays all event trace messages currently in memory for the specified component.
|
back
|
Specifies how far back from the current time you want to view messages. For example, you can gather messages from the last 30 minutes.
|
time
|
Length of time in hours and minutes format (hh:mm).
|
clock
|
Displays event trace messages starting from a specific clock time.
|
time
|
Time from which to display messages in hours and minutes format (hh:mm).
|
from-boot
|
Displays event trace messages starting from a specified number of seconds after booting.
|
seconds
|
Number of seconds since the networking device was last booted (uptime). To view the uptime, in seconds, enter the show monitor event-trace component from-boot ? command.
|
latest
|
Displays only the event trace messages since the last show monitor event-trace command was entered.
|
parameters
|
Displays the trace parameters. Currently, the only parameter displayed is the size (number of trace messages) of the trace file.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(18)S
|
This command was introduced.
|
12.2(8)T
|
This feature was integrated into Cisco IOS Release 12.2(8)T.
|
Usage Guidelines
Use the show monitor event-trace command to display trace message information.
The trace function is not locked while information is being displayed to the console, which means that new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed, some messages can be lost. If this happens, the show monitor event-trace command will generate a message indicating that some messages might be lost; however, messages will continue to display on the console. If the number of lost messages is excessive, the show monitor event-trace command will stop displaying messages.
Examples
The following sample output illustrates the show monitor event-trace component command output for the IPC component. Notice that each trace message is numbered and is followed by a the timestamp (derived from the device uptime). Following the timestamp is the component-specific message data.
Router# show monitor event-trace ipc
3667: 6840.016:Message type:3 Data=0123456789
3668: 6840.016:Message type:4 Data=0123456789
3669: 6841.016:Message type:5 Data=0123456789
3670: 6841.016:Message type:6 Data=0123456
To view trace information for all components configured for event tracing on the networking device, enter the show monitor event-trace all-traces command. In this example, separate output is provided for each event and message numbers are interleaved between the events.
Router# show monitor event-trace all-traces
3667: 6840.016:Message type:3 Data=0123456789
3669: 6841.016:Message type:4 Data=0123456789
3671: 6842.016:Message type:5 Data=0123456789
3673: 6843.016:Message type:6 Data=0123456789
3668: 6840.016:Message type:3 Data=0123456789
3670: 6841.016:Message type:4 Data=0123456789
3672: 6842.016:Message type:5 Data=0123456789
3674: 6843.016:Message type:6 Data=0123456789
Related Commands
Command
|
Description
|
monitor event-trace (EXEC)
|
Controls event trace functions for a specified Cisco IOS software subsystem component.
|
monitor event-trace (global)
|
Configures event tracing for a specified Cisco IOS software subsystem component.
|
monitor event-trace dump-traces
|
Saves trace messages for all event traces currently enabled on the networking device.
|
show monitor event-trace cpu-report
To display event trace messages for the CPU, use the show monitor event-trace cpu-report command in user EXEC or privileged EXEC mode.
show monitor event-trace cpu-report {brief {all [detail] | back time | clock time | from-boot
seconds | detail] | latest [detail]} | handle handle-number}
Syntax Description
brief
|
Displays a brief CPU report.
|
all
|
Displays all event trace messages currently in memory for the CPU.
|
detail
|
(Optional) Displays detailed event trace information.
|
back time
|
Specifies how far back from the current time you want to view messages. For example, you can gather messages from the last 30 minutes.
The time argument specifies the length of time in hours and minutes format (hh:mm).
|
clock time
|
Displays event trace messages starting from a specific clock time.
The time argument specifies the time from which to display messages in hours and minutes format (hh:mm).
|
from-boot seconds
|
Displays event trace messages starting from a specified number of seconds after booting.
The seconds argument specifies the number of seconds since the networking device was last booted (uptime). To view the uptime, in seconds, enter the show monitor event-trace component from-boot ? command.
|
latest
|
Displays only the event trace messages since the last show monitor event-trace command was entered.
|
handle handle-number
|
Displays a detailed CPU report for the specified handle number. Valid values for the handle-number argument are from 1 to 255.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
Use the show monitor event-trace cpu-report command with the brief keyword to display the CPU report details. To see individual snapshots, use the show monitor event-trace cpu-report handle handle-number command.
Examples
To view CPU report details for event tracing on a networking device, enter the show monitor event-trace cpu-report brief all command:
Router# show monitor event-trace cpu-report brief all
Timestamp : Handle Name Description
To view CPU report details for event tracing on a networking device for the handle number 1, enter the show monitor event-trace cpu-report brief handle 1 command:
Router# show monitor event-trace cpu-report handle 1
################################################################################
5 sec CPU util 0%/0% Timestamp 21:03:56
Exec Count Total CPU Response Time Queue Length
Common Process Information
-------------------------------
-------------------------------
10 AAA high-capacit M New
133 RADIUS TEST CMD M New
99 CEF: IPv4 proces L New
112 X.25 Background M New
117 LFDp Input Proc M New
-------------------------------------------------------------------------------
PID Total Exec Quant Burst Burst size Schedcall Schedcall
CPUms Count avg/max Count avg/max(ms) Count Per avg/max
-------------------------------------------------------------------------------
3 820 6 136/236 1 24/24 18 887/15172
------------------------------------
PID Exec Count Prio-Susps
------------------------------------
-------------------------
-------------------------
################################################################################
5 sec CPU util 0%/0% Timestamp 00:00:00
Exec Count Total CPU Response Time Queue Length
Common Process Information
-------------------------------
-------------------------------
-------------------------------------------------------------------------------
PID Total Exec Quant Burst Burst size Schedcall Schedcall
CPUms Count avg/max Count avg/max(ms) Count Per avg/max
-------------------------------------------------------------------------------
------------------------------------
PID Exec Count Prio-Susps
------------------------------------
-------------------------
-------------------------
################################################################################
Related Commands
Command
|
Description
|
monitor event-trace cpu-report (EXEC)
|
Monitors event tracing of the CPU reports.
|
monitor event-trace cpu-report (global)
|
Monitors the collection of CPU report traces.
|
monitor event-trace dump-traces
|
Saves trace messages for all event traces currently enabled on the networking device.
|
show ntp associations
To show the status of Network Time Protocol (NTP) associations, use the show ntp associations command in EXEC mode.
show ntp associations [detail]
Syntax Description
detail
|
(Optional) Displays detailed information about each NTP association.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
Detailed descriptions of the information displayed by this command can be found in the NTP specification (RFC 1305).
The following is sample output from the show ntp associations command:
Router> show ntp associations
address ref clock st when poll reach delay offset disp
~172.31.32.2 172.31.32.1 5 29 1024 377 4.2 -8.59 1.6
+~192.168.13.33 192.168.1.111 3 69 128 377 4.1 3.48 2.3
*~192.168.13.57 192.168.1.111 3 32 128 377 7.9 11.18 3.6
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
Table 142 describes the significant fields shown in the display.
Table 142 show ntp associations Field Descriptions
Field
|
Description
|
(leading characters in display lines)
|
The first characters in a display line can be one or more of the following characters:
* —Synchronized to this peer
# —Almost synchronized to this peer
+ —Peer selected for possible synchronization
- —Peer is a candidate for selection
~ —Peer is statically configured
|
address
|
Address of peer.
|
ref clock
|
Address of reference clock of peer.
|
st
|
Stratum of peer.
|
when
|
Time since last NTP packet was received from peer.
|
poll
|
Polling interval (in seconds).
|
reach
|
Peer reachability (bit string, in octal).
|
delay
|
Round-trip delay to peer (in milliseconds).
|
offset
|
Relative time of peer clock to local clock (in milliseconds).
|
disp
|
Dispersion
|
The following is sample output of the show ntp associations detail command:
Router> show ntp associations detail
172.31.32.2 configured, insane, invalid, stratum 5
ref ID 172.31.32.1, time AFE252C1.6DBDDFF2 (00:12:01.428 PDT Mon Jul 5 1993)
our mode active, peer mode active, our poll intvl 1024, peer poll intvl 64
root delay 137.77 msec, root disp 142.75, reach 376, sync dist 215.363
delay 4.23 msec, offset -8.587 msec, dispersion 1.62
precision 2**19, version 3
org time AFE252E2.3AC0E887 (00:12:34.229 PDT Mon Jul 5 1993)
rcv time AFE252E2.3D7E464D (00:12:34.240 PDT Mon Jul 5 1993)
xmt time AFE25301.6F83E753 (00:13:05.435 PDT Mon Jul 5 1993)
filtdelay = 4.23 4.14 2.41 5.95 2.37 2.33 4.26 4.33
filtoffset = -8.59 -8.82 -9.91 -8.42 -10.51 -10.77 -10.13 -10.11
filterror = 0.50 1.48 2.46 3.43 4.41 5.39 6.36 7.34
192.168.13.33 configured, selected, sane, valid, stratum 3
ref ID 192.168.1.111, time AFE24F0E.14283000 (23:56:14.078 PDT Sun Jul 4 1993)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 83.72 msec, root disp 217.77, reach 377, sync dist 264.633
delay 4.07 msec, offset 3.483 msec, dispersion 2.33
precision 2**6, version 3
org time AFE252B9.713E9000 (00:11:53.442 PDT Mon Jul 5 1993)
rcv time AFE252B9.7124E14A (00:11:53.441 PDT Mon Jul 5 1993)
xmt time AFE252B9.6F625195 (00:11:53.435 PDT Mon Jul 5 1993)
filtdelay = 6.47 4.07 3.94 3.86 7.31 7.20 9.52 8.71
filtoffset = 3.63 3.48 3.06 2.82 4.51 4.57 4.28 4.59
filterror = 0.00 1.95 3.91 4.88 5.84 6.82 7.80 8.77
192.168.13.57 configured, our_master, sane, valid, stratum 3
ref ID 192.168.1.111, time AFE252DC.1F2B3000 (00:12:28.121 PDT Mon Jul 5 1993)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 125.50 msec, root disp 115.80, reach 377, sync dist 186.157
delay 7.86 msec, offset 11.176 msec, dispersion 3.62
precision 2**6, version 2
org time AFE252DE.77C29000 (00:12:30.467 PDT Mon Jul 5 1993)
rcv time AFE252DE.7B2AE40B (00:12:30.481 PDT Mon Jul 5 1993)
xmt time AFE252DE.6E6D12E4 (00:12:30.431 PDT Mon Jul 5 1993)
filtdelay = 49.21 7.86 8.18 8.80 4.30 4.24 7.58 6.42
filtoffset = 11.30 11.18 11.13 11.28 8.91 9.09 9.27 9.57
filterror = 0.00 1.95 3.91 4.88 5.78 6.76 7.74 8.71
Table 143 describes the significant fields shown in the display.
Table 143 show ntp associations detail Field Descriptions
Field
|
Descriptions
|
configured
|
Peer was statically configured.
|
dynamic
|
Peer was dynamically discovered.
|
our_master
|
Local machine is synchronized to this peer.
|
selected
|
Peer is selected for possible synchronization.
|
candidate
|
Peer is a candidate for selection.
|
sane
|
Peer passes basic sanity checks.
|
insane
|
Peer fails basic sanity checks.
|
valid
|
Peer time is believed to be valid.
|
invalid
|
Peer time is believed to be invalid.
|
leap_add
|
Peer is signalling that a leap second will be added.
|
leap-sub
|
Peer is signalling that a leap second will be subtracted.
|
unsynced
|
Peer is not synchronized to any other machine.
|
ref ID
|
Address of machine peer is synchronized to.
|
time
|
Last time stamp peer received from its master.
|
our mode
|
Our mode relative to peer (active/passive/client/server/bdcast/bdcast client).
|
peer mode
|
Peer's mode relative to us.
|
our poll intvl
|
Our poll interval to peer.
|
peer poll intvl
|
Peer's poll interval to us.
|
root delay
|
Delay along path to root (ultimate stratum 1 time source).
|
root disp
|
Dispersion of path to root.
|
reach
|
Peer reachability (bit string in octal).
|
sync dist
|
Peer synchronization distance.
|
delay
|
Round-trip delay to peer.
|
offset
|
Offset of peer clock relative to our clock.
|
dispersion
|
Dispersion of peer clock.
|
precision
|
Precision of peer clock in Hertz.
|
version
|
NTP version number that peer is using.
|
org time
|
Originate time stamp.
|
rcv time
|
Receive time stamp.
|
xmt time
|
Transmit time stamp.
|
filtdelay
|
Round-trip delay (in milliseconds) of each sample.
|
filtoffset
|
Clock offset (in milliseconds) of each sample.
|
filterror
|
Approximate error of each sample.
|
Related Commands
Command
|
Description
|
show ntp status
|
Displays the status of the NTP.
|
show ntp status
To show the status of the Network Time Protocol (NTP), use the show ntp status command in EXEC mode.
show ntp status
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show ntp status command:
Clock is synchronized, stratum 4, reference is 192.168.13.57
nominal freq is 250.0000 Hz, actual freq is 249.9990 Hz, precision is 2**19
reference time is AFE2525E.70597B34 (00:10:22.438 PDT Mon Jul 5 1993)
clock offset is 7.33 msec, root delay is 133.36 msec
root dispersion is 126.28 msec, peer dispersion is 5.98 msec
Table 144 describes the significant fields shown in the display.
Table 144 show ntp status Field Descriptions
Field
|
Description
|
synchronized
|
System is synchronized to an NTP peer.
|
unsynchronized
|
System is not synchronized to any NTP peer.
|
stratum
|
NTP stratum of this system.
|
reference
|
Address of peer the system is synchronized to.
|
nominal freq
|
Nominal frequency of system hardware clock.
|
actual freq
|
Measured frequency of system hardware clock.
|
precision
|
Precision of the clock of this system (in Hertz).
|
reference time
|
Reference time stamp.
|
clock offset
|
Offset of the system clock to synchronized peer.
|
root delay
|
Total delay along path to root clock.
|
root dispersion
|
Dispersion of root path.
|
peer dispersion
|
Dispersion of synchronized peer.
|
Related Commands
Command
|
Description
|
show ntp associations
|
Displays the status of the NTP associations.
|
show parser dump
To display the CLI syntax options for all command modes or for a specified command mode, use the show parser dump command in privileged EXEC mode.
show parser dump {command-mode | all} [privilege-level level] [extended] [breakage]
Syntax Description
command-mode
|
A keyword indicating the command mode. The output will include the syntax for commands only in the specified command mode. The list of command mode keywords will vary depending on your software image. Use the show parser dump ? command to display the list of command mode keyword options. For further assistance determining the proper command mode, see the "Cisco IOS Command Modes" Release 12.2 document, available on Cisco.com.
|
all
|
Indicates that all commands in all modes should be displayed in the output.
Caution  This keyword generates a very large amount of output, which may exceed your system or buffer memory.
|
privilege-level level
|
(Optional) Lists CLI commands only with the privilege level specified in the level argument.
|
breakage
|
(Optional) Enables detection of potential parser chain syntax breakage. This keyword is intended for internal use.
|
extend
|
(Optional) Enables the extended display mode. The extended parser display shows the keyword and argument descriptions typically shown with the command-line help (? command).
Note This keyword can produce a large amount of output.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(4)T
|
This command was introduced.
|
12.2(13)T, 12.0(23)S
|
This command was enhanced to resolve certain execution errors.
|
Usage Guidelines
This command was developed to allow the exploration of the CLI command syntax without requiring the user to actually enter a specific mode and use the ? command line help.
Caution 
Use caution when entering this command with the
all keyword. A large amount of output can be generated by this command, which may easily exceed buffer or system memory on smaller platforms. Also, some configuration modes have hundreds of valid commands. For large dumps, use of the redirection to a file using the
| redirect URL syntax at the end of the command is highly recommended. (See the documentation for the
show <command> redirect command for more information on using this command extension.)
Output for this command will show the syntax options for all commands available in the specified mode. The preceding number shows the privilege level associated with that command. For example, the line
indicates that the type dhcp command has a privilege level of 15 assigned to it. For information about privilege levels, see the "Configuring Passwords and Privileges" chapter in the Cisco IOS Security Configuration Guide.
Any given command-line string should indicate the full syntax needed to make the command complete and valid. In other words, the command line string ends where the carriage return (Enter) could be entered, as indicated in command-line help by the <cr> syntax. You will typically see multiple forms of a command, each showing a valid syntax combination. For example, each of the following syntax combinations, as seen in the output of the show parser dump rtr | include dhcp command, are valid commands:
type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id <string>
type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id <string>
type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask
<ipmask>
type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82>
type dhcp dest-ipaddr <address> source-ipaddr <address>
type dhcp dest-ipaddr <address>
Use of the show command extensions | begin, | include, and | exclude are recommended for this command, as these extensions allow you to filter the output to show only the commands you are interested in. The redirection extensions | redirect, | append, and | tee allow you to redirect the output of this command to local or remote storage as a file.
As with most show commands, you can typically exit from the --More-- prompt back to EXEC mode using Ctrl-Z. For some connections, Ctrl-Shift-6 (Ctrl^) or Ctrl-Shift-6-X should be used instead.
Examples
The following example shows a typical list of command mode keywords:
Router# show parser dump ?
aaa-user AAA user definition
accept-dialin VPDN group accept dialin configuration mode
accept-dialout VPDN group accept dialout configuration mode
address-family Address Family configuration mode
aic Alarm Interface Card configuration mode
bba-group BBA Group configuration mode
bsm-cfg BSM config definition
cascustom Cas custom configuration mode
clid-group CLID group configuration mode
cns-connect-intf-config CNS Connect Intf Info Mode
config-l2tp-class l2tp-class configuration mode
config-rtr-http-rr RTR HTTP raw request Configuration
config-x25-huntgroup X.25 hunt group configuration mode
configure Global configuration mode
congestion Frame Relay congestion configuration mode
controller Controller configuration mode
dhcp DHCP pool configuration mode
dnis-group DNIS group configuration mode
filter Output filter mode
filterserver AAA filter server definitions
flow-cache Flow aggregation cache config mode
flow-sampler-map Flow sampler map config mode
fr-fr FR/FR connection configuration mode
frf5 FR/ATM Network IWF configuration mode
frf8 FR/ATM Service IWF configuration mode
interface Interface configuration mode
interface Interface range configuration mode
interface-dlci Frame Relay dlci configuration mode
ip-vrf Configure IP VRF parameters
ipenacl IP named extended access-list configuration mode
ipnat-pool IP NAT pool configuration mode
ipnat-snat IP SNAT configuration mode
ipnat-snat-backup IP SNAT Backup configuration mode
ipnat-snat-primary IP SNAT Primary configuration mode
ipnat-snat-redundancy IP SNAT Redundancy configuration mode
ipsnacl IP named simple access-list configuration mode
iua-cfg ISDN user adaptation layer configuration
key-chain Key-chain configuration mode
key-chain-key Key-chain key configuration mode
kron-occurrence Kron Occurrence SubMode
kron-policy Kron Policy SubMode
line Line configuration mode
lw-vlan-id VLAN-id configuration mode
lw-vlan-range VLAN-range configuration mode
map-class Map class configuration mode
map-list Map list configuration mode
mrm-manager IP Multicast Routing Monitor config mode
null-interface Null interface configuration mode
policy-list IP Policy List configuration mode
preauth AAA Preauth definitions
qosclassmap QoS Class Map configuration mode
qosclasspolice QoS Class Police configuration mode
qospolicymap QoS Policy Map configuration mode
qospolicymapclass QoS Policy Map class configuration mode
radius-attrl Radius Attribute-List Definition
red-group random-detect group configuration mode
request-dialin VPDN group request dialin configuration mode
request-dialout VPDN group request dialout configuration mode
roles Role configuration mode
route-map Route map config mode
router Router configuration mode
rsvp-local-policy RSVP local policy configuration mode
rtr SAA entry configuration
saa-dhcp SAA dhcp configuration
saa-dns SAA dns configuration
saa-echo SAA echo configuration
saa-frameRelay SAA FrameRelay configuration
saa-ftp SAA ftp configuration
saa-http SAA http configuration
saa-jitter SAA jitter configuration
saa-pathEcho SAA pathEcho configuration
saa-pathJitter SAA pathJitter configuration
saa-slm-ctrlr-if SAA SLM controller/interface configuration
saa-slmFrIf SAA SLM FrameRelay Interface configuration
saa-slmfr SAA SLM Frame Relay configuration
saa-tcpConnect SAA tcpConnect configuration
saa-udpEcho SAA udpEcho configuration
sg-radius Radius Server-group Definition
sg-tacacs+ Tacacs+ Server-group Definition
signaling-class Signaling class configuration mode
sss-subscriber SSS subscriber configuration mode
subinterface Subinterface configuration mode
subscriber-policy Subscriber policy configuration mode
tablemap Table Map configuration mode
tdm-conn TDM connection configuration mode
template Template configuration mode
tracking-config Tracking configuration mode
trange time-range configuration mode
trunk-group Trunk group configuration mode
vc-class VC class configuration mode
vc-group VC group configuration mode
vlan VLAN database editing buffer
vpdn-group VPDN group configuration mode
vpdn-template VPDN template configuration mode
x25-profile X.25 profile configuration mode
In the following example, only commands in RTR Configuration mode are shown:
Router# show parser dump rtr
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control enable
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control disable
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535>
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type udpEcho dest-ipaddr <address> dest-port <1-65535>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control enable
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control disable
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type tcpConnect dest-ipaddr <address> dest-port <1-65535>
15 type jitter dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
15 type jitter dest-ipaddr <address> dest-port <1-65535> source-port <1-65535>
15 type jitter dest-ipaddr <address> dest-port <1-65535> control enable
15 type jitter dest-ipaddr <address> dest-port <1-65535> control disable
15 type jitter dest-ipaddr <address> dest-port <1-65535> num-packets <1-60000>
15 type jitter dest-ipaddr <address> dest-port <1-65535> interval <1-60000>
15 type jitter dest-ipaddr <address> dest-port <1-65535>
15 type echo protocol ipIcmpEcho <address> source-ipaddr <address>
15 type echo protocol ipIcmpEcho <address>
15 type ftp operation get url <string> source-ipaddr <address> mode active
15 type ftp operation get url <string> source-ipaddr <address> mode passive
15 type ftp operation get url <string> source-ipaddr <address>
15 type ftp operation get url <string>
15 type http operation get url <string> name-server <address> version <string>
source-ipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string>
source-ipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string>
source-ipaddr <address> source-port <1-65535> cache
15 type http operation get url <string> name-server <address> version <string>
source-ipaddr <address> source-port <1-65535>
15 type http operation get url <string> name-server <address> version <string>
source-ipaddr <address>
15 type http operation get url <string> name-server <address> version <string>
15 type http operation get url <string> name-server <address>
15 type http operation get url <string>
15 type http operation raw
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id
<string>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id
<string>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask
<ipmask>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82>
15 type dhcp dest-ipaddr <address> source-ipaddr <address>
15 type dhcp dest-ipaddr <address>
15 type dns target-addr <string> name-server <address> source-ipaddr <address> source-port
<1-65535>
15 type dns target-addr <string> name-server <address> source-ipaddr <address>
15 type dns target-addr <string> name-server <address>
15 type pathEcho protocol ipIcmpEcho <address> source-ipaddr <address>
15 type pathEcho protocol ipIcmpEcho <address>
15 type pathJitter dest-ipaddr <address> source-ipaddr <address>
15 type pathJitter dest-ipaddr <address> num-packets <1-100>
15 type pathJitter dest-ipaddr <address> interval <1-1000>
15 type pathJitter dest-ipaddr <address> targetOnly
15 type pathJitter dest-ipaddr <address>
15 type slm frame-relay pvc
15 type slm controller T1 <controller>
15 type slm controller E1 <controller>
15 type slm controller T3 <controller>
15 type slm controller E3 <controller>
In the following example, only those commands in RTR Configuration mode containing the keyword dhcp are shown:
Router# show parser dump rtr | include dhcp
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id
<string>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id
<string>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask
<ipmask>
15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82>
15 type dhcp dest-ipaddr <address> source-ipaddr <address>
15 type dhcp dest-ipaddr <address>
The following example shows how the extend keyword displays the syntax descriptions that match those shown using the ? command-line help:
Router# show parser dump rtr extend
15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address>
source-port <1-65535> control enable
udpEcho : UDP Echo Operation
dest-ipaddr : Destination address
<address> : IP address or hostname
dest-port : Destination Port
source-ipaddr : Source address
<address> : IP address or hostname
source-port : Source Port
control : Enable or disable control packets
enable : Enable control packets exchange (default)
! Ctrl-Z used here to interrupt output and return to CLI prompt.
Enter configuration commands, one per line. End with CNTL/Z.
Router(config-rtr)# type udpEcho ?
dest-ipaddr Destination address
Router(config-rtr)# type udpEcho dest-ipaddr ?
Hostname or A.B.C.D IP address or hostname
Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME ?
dest-port Destination Port
Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port ?
Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port 1 ?
control Enable or disable control packets
source-ipaddr Source address
Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port 1 control ?
disable Disable control packets exchange
enable Enable control packets exchange (default)
In the following example, show parser dump output is redirected to a file on a remote TFTP server:
show parser dump exec extend | redirect
tftp://209.165.200.225/userdirectory/123-exec-commands.txt
Related Commands
Command
|
Description
|
show <command> append
|
Redirects and adds the output of any show command to an existing file.
|
show <command> redirect
|
Redirects the output of any show command to a file.
|
show <command> tee
|
Copies the output of any show command to a file while displaying it on the terminal.
|
show <command> include
|
Filters show command output so that only lines that containing the specified string are displayed.
|
show <command> begin
|
Filters the output of any show command to display the output from the first instance of a specified string.
|
show <command> exclude
|
Filters show command output so that it excludes lines that contain a particular regular expression.
|
show parser statistics
To displays statistics about the last configuration file parsed and the status of the Parser Cache feature, use the show parser statistics command in privileged EXEC mode.
show parser statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
The show parser statistics command displays two sets of data:
•
The number of commands in the configuration file that was last copied into the running configuration, and the time it took for the system to parse them (a configuration file can be loaded into the running configuration at system startup, or by issuing commands such as the copy source running-config command).
•
The status of the Parser Cache feature (enabled or disabled) and the number of command matches (indicated by hits/misses) since the system was started or since the parser cache was cleared.
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines, decreasing the time required to process large configuration files.
Examples
The following example shows sample output from the show parser statistics command:
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:1272 ms
Parser cache:disabled, 0 hits, 2 misses
In this example, the Parser Cache feature is disabled, but shows the hit/miss statistics for the two commands issued while the parser cache was last enabled.
Table 145 describes the key output fields.
Table 145 show parser statistics Output Fields
Last configuration file parsed:
|
Displays statistics on the last configuration file copied into the running configuration (at startup or using the copy command).
|
Number of commands:
|
The number of command lines in the last configuration file parsed.
|
Time:
|
Time (in milliseconds) taken for the system to load the last configuration file.
|
Parser cache:
|
Displays whether the Parser Cache feature is enabled or disabled, and the hit/miss statistics related to the feature. Statistics are stored since the initialization of the system, or since the last time the parser cache was cleared.
|
hits
|
Number of commands the parser cache was able to parse more efficiently by matching them to similar commands executed previously.
|
misses
|
Number of commands the parser cache was unable to match to previously executed commands. The performance enhancement provided by the Parser Cache feature cannot be applied to unmatched commands.
|
In the following example the show parser statistics command is used to compare the parse-time of a large configuration file with the Parser Cache feature disabled and enabled. In this example, a configuration file with 1484 access list commands is loaded into the running configuration.
Router# configure terminal
!parser cache is disabled
Router(config)# no parser cache
!configuration file is loaded into the running configuration
Router# copy slot0:acl_list running-config
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:1272 ms
Parser cache:disabled, 0 hits, 2 misses
!the parser cache is reenabled
Router(config)# parser cache
!configuration file is loaded into the running configuration
Router# copy slot0:acl_list running-config
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:820 ms
Parser cache:enabled, 1460 hits, 26 misses
These results show an improvement to the load time for the same configuration file from 1272 milliseconds (ms) to 820 ms when the Parser Cache feature was enabled. As indicated in the "hits" field of the show command output, 1460 commands were able to be parsed more efficiently by the parser cache.
Related Commands
Command
|
Description
|
clear parser cache
|
Clears the parse cache entries and hit/miss statistics stored for the Parser Cache feature.
|
parser cache
|
Enables or disables the Parser Cache feature.
|
show pci
To display information about the peripheral component interconnect (PCI) hardware registers or bridge registers for the Cisco 7200 series routers, use the show pci command in EXEC mode.
show pci {hardware | bridge [register]}
Syntax Description
hardware
|
Displays PCI hardware registers.
|
bridge
|
Displays PCI bridge registers.
|
register
|
(Optional) Number of a specific bridge register in the range from 0 to 7. If not specified, this command displays information about all registers.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
The output of this command is generally useful for diagnostic tasks performed by technical support only.
Note
The show pci hardware EXEC command displays a substantial amount of information.
Examples
The following is sample output for the PCI bridge register 1 on a Cisco 7200 series router:
Router# show pci bridge 1
Bridge 4, Port Adaptor 1, Handle=1
DEC21050 bridge chip, config=0x0
(0x00): cfid = 0x00011011
(0x04): cfcs = 0x02800147
(0x08): cfccid = 0x06040002
(0x0C): cfpmlt = 0x00010010
(0x18): cfsmlt = 0x18050504
(0x1C): cfsis = 0x22805050
(0x20): cfmla = 0x48F04880
(0x24): cfpmla = 0x00004880
(0x3C): cfbc = 0x00000000
(0x40): cfseed = 0x00100000
(0x44): cfstwt = 0x00008020
The following is partial sample output for the PCI hardware register, which also includes information on all the PCI bridge registers on a Cisco 7200 series router:
Router# show pci hardware
GT64010 External PCI Configuration registers:
Vendor / Device ID : 0xAB114601 (b/s 0x014611AB)
Status / Command : 0x17018002 (b/s 0x02800117)
Class / Revision : 0x00000006 (b/s 0x06000000)
Latency : 0x0F000000 (b/s 0x0000000F)
RAS[1:0] Base : 0x00000000 (b/s 0x00000000)
RAS[3:2] Base : 0x00000001 (b/s 0x01000000)
CS[2:0] Base : 0x00000000 (b/s 0x00000000)
CS[3] Base : 0x00000000 (b/s 0x00000000)
Mem Map Base : 0x00000014 (b/s 0x14000000)
IO Map Base : 0x01000014 (b/s 0x14000001)
Int Pin / Line : 0x00010000 (b/s 0x00000100)
Bridge 0, Downstream MB0 to MB1, Handle=0
DEC21050 bridge chip, config=0x0
(0x00): cfid = 0x00011011
(0x04): cfcs = 0x02800143
(0x08): cfccid = 0x06040002
(0x0C): cfpmlt = 0x00011810
(0x18): cfsmlt = 0x18000100
(0x1C): cfsis = 0x02809050
(0x20): cfmla = 0x4AF04880
(0x24): cfpmla = 0x4BF04B00
(0x3C): cfbc = 0x00000000
(0x40): cfseed = 0x00100000
(0x44): cfstwt = 0x00008020
show pci hardware
To display information about the Host-PCI bridge, use the show pci hardware command in EXEC mode.
show pci hardware
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
The output of this command is generally useful for diagnostic tasks performed by technical support only:
Router# show pci hardware
hardware PCI hardware registers
Each device on the PCI bus is assigned a PCI device number. For the
C2600, device numbers are as follows:
2 AIM device (if present)
4 Port module - first PCI device
5 Port module - second PCI device
6 Port module - third PCI device
7 Port module - fourth PCI device
Examples
The following is partial sample output for the PCI hardware register, which also includes information on all the PCI bridge registers.
router# show pci hardware
XILINX Host-PCI Bridge Registers:
Vendor / Device ID: 0x401310EE
Status / Command: 0x040001C6
PCI Slave Base Reg 0: 0x00000000
PCI Slave Base Reg 1: 0x04000000
Table 146 describes the significant fields shown in the display.
Table 146 show pci hardware Field Descriptions
Field
|
Description
|
Device/Vendor ID
|
Identifies the PCI vendor and device. The value 0x401310EE identifies the device as the Xilinx-based Host-PCI bridge for the Cisco 2600 router.
|
Status/Command
|
Provides status of the Host-PCI bridge. Refer to the PCI Specification for more information.
|
PCI Slave Base Reg 0
|
The base address of PCI Target Region 0 for the Host-PCI bridge. This region is used for Big-Endian transfers between PCI devices and memory.
|
PCI Slave Base Reg 1
|
The base address of PCI Target Region 1 for the Host-PCI bridge. This region is used for Little-Endian transfers between PCI devices and memory.
|
show processes
To display information about the active processes, use the show processes command in privileged EXEC mode.
show processes [history | pid]
Syntax Description
history
|
(Optional) Displays the process history in an ordered format.
|
pid
|
(Optional) An integer that specifies the process for which memory and CPU utilization data shall be returned.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(2)T
|
The history keyword was added.
|
12.3(2)T
|
The pid argument was added.
|
Examples
The following is sample output from the show processes command:
CPU utilization for five seconds: 21%/0%; one minute: 2%; five minutes: 2%
PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process
1 Cwe 606E9FCC 0 1 0 5600/6000 0 Chunk Manager
2 Csp 607180F0 0 121055 0 2608/3000 0 Load Meter
3 M* 0 8 90 88 9772/12000 0 Exec
4 Mwe 619CB674 0 1 023512/24000 0 EDDRI_MAIN
5 Lst 606F6AA4 82064 61496 1334 5668/6000 0 Check heaps
6 Cwe 606FD444 0 127 0 5588/6000 0 Pool Manager
7 Lwe 6060B364 0 1 0 5764/6000 0 AAA_SERVER_DEADT
8 Mst 6063212C 0 2 0 5564/6000 0 Timers
9 Mwe 600109D4 0 2 0 5560/6000 0 Serial Backgroun
10 Mwe 60234848 0 2 0 5564/6000 0 ATM Idle Timer
11 Mwe 602B75F0 0 2 0 8564/9000 0 ATM AutoVC Perio
12 Mwe 602B7054 0 2 0 5560/6000 0 ATM VC Auto Crea
13 Mwe 606068B8 0 2 0 5552/6000 0 AAA high-capacit
14 Msi 607BABA4 251264 605013 415 5628/6000 0 EnvMon
15 Mwe 607BFF8C 0 1 0 8600/9000 0 OIR Handler
16 Mwe 607D407C 0 10089 0 5676/6000 0 IPC Dynamic Cach
17 Mwe 607CD03C 0 1 0 5632/6000 0 IPC Zone Manager
18 Mwe 607CCD80 0 605014 0 5708/6000 0 IPC Periodic Tim
19 Mwe 607CCD24 0 605014 0 5704/6000 0 IPC Deferred Por
20 Mwe 607CCE2C 0 1 0 5596/6000 0 IPC Seat Manager
Table 147 describes the fields shown in the display.
Table 147 show processes Field Descriptions
Field
|
Description
|
CPU utilization for five seconds:
|
CPU utilization for the last 5 seconds. The second number indicates the percent of CPU time spent at the interrupt level.
|
one minute:
|
CPU utilization for the last minute.
|
five minutes:
|
CPU utilization for the last 5 minutes.
|
PID
|
Process ID.
|
Q
|
Process queue priority. Possible values: C (critical), H (high), M (medium), L (low).
|
Ty
|
Scheduler test. Possible values: * (currently running), E (waiting for an event), S (ready to run, voluntarily relinquished processor), rd (ready to run, wakeup conditions have occurred), we (waiting for an event), sa (sleeping until an absolute time), si (sleeping for a time interval), sp (sleeping for a time interval (alternate call), st (sleeping until a timer expires), hg (hung; the process will never execute again), xx (dead: the process has terminated, but has not yet been deleted).
|
PC
|
Current program counter.
|
Runtime (ms)
|
CPU time the process has used (in milliseconds).
|
Invoked
|
Number of times the process has been invoked.
|
uSecs
|
Microseconds of CPU time for each process invocation.
|
Stacks
|
Low water mark/Total stack space available (in bytes).
|
TTY
|
Terminal that controls the process.
|
Process
|
Name of the process.
|

Note
Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after a large number of invocations or a reasonable, measured run time.
For a list of process descriptions, refer to http://www.cisco.com/warp/public/63/showproc_cpu.html.
The following is sample output from the show processes history command:
Router# show processes history
PID Exectime(ms) Caller PC Process Name
21 0 0x603CFEF4 TTY Background
22 0 0x6042FD7C Per-Second Jobs
67 0 0x6015CD38 SMT input
39 0 0x60178804 FBM Timer
21 0 0x603CFEF4 TTY Background
22 0 0x6042FD7C Per-Second Jobs
21 0 0x603CFEF4 TTY Background
22 0 0x6042FD7C Per-Second Jobs
67 0 0x6015CD38 SMT input
39 0 0x60178804 FBM Timer
24 0 0x60425070 Compute load avgs
11 0 0x605210A8 ARP Input
69 0 0x605FDAF4 DHCPD Database
69 0 0x605FD568 DHCPD Database
51 0 0x60670B3C IP Cache Ager
69 0 0x605FD568 DHCPD Database
36 0 0x606E96DC SSS Test Client
69 0 0x605FD568 DHCPD Database
Table 148 describes the significant fields shown in the display.
Table 148 show processes history Field Descriptions
Field
|
Description
|
PID
|
Process ID.
|
Exectime (ms)
|
Execution time of the most recent run, or the total execution time of the most recent consecutive runs.
|
Caller PC
|
Current Program Counter of this process before it was suspended.
|
Process Name
|
Name of the process.
|
Note
Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after a large number of invocations or a reasonable, measured run time.
For a list of process descriptions, refer to http://www.cisco.com/warp/public/63/showproc_cpu.html.
The following is sample output from the show processes pid command:
Process ID 6 [Pool Manager], TTY 0
Holding: 921148, Maximum: 940024, Allocated: 84431264, Freed: 99432136
Getbufs: 0, Retbufs: 0, Stack: 12345/67890
PC: 0x60887600, Invoked: 188, Giveups: 100, uSec: 24
5Sec: 3.03%, 1Min: 2.98%, 5Min: 1.55%, Average: 0.58%,
Age: 662314 msec, Runtime: 3841 msec
State: Running, Priority: Normal
Table 149 describes the fields shown in the display.
Table 149 show processes pid Field Descriptions
Field
|
Description
|
Process ID
|
Process ID number and process name.
|
TTY
|
Terminal that controls the process.
|
Memory usage [in bytes]
|
This section contains fields that show the memory used by the specified process.
|
Holding
|
Amount of memory currently allocated to the process.
|
Maximum
|
Maximum amount of memory allocated to the process since its invocation.
|
Allocated
|
Bytes of memory allocated by the process.
|
Freed
|
Bytes of memory freed by the process.
|
Getbufs
|
Number of times the process has requested a packet buffer.
|
Retbufs
|
Number of times the process has relinquished a packet buffer.
|
Stack
|
Low water mark/Total stack space available (in bytes).
|
CPU usage
|
This section contains fields that show the CPU resources used by the specified process.
|
PC
|
Current Program Counter of this process before it was suspended.
|
Invoked
|
Number of times the process executed since its invocation.
|
Giveups
|
Number of times the process voluntarily gave up the CPU.
|
uSec
|
Microseconds of CPU time for each process invocation.
|
5Sec
|
CPU utilization by process in the last five seconds.
|
1Min
|
CPU utilization by process in the last minute.
|
5Min
|
CPU utilization by process in the last five minutes.
|
Average
|
The average amount of CPU utilization by the process since its invocation.
|
Age
|
Milliseconds since the process was invoked.
|
Runtime
|
CPU time the process has used (in milliseconds).
|
State
|
Current state of the process. Possible values: Running, Waiting for Event, Sleeping (Mgd Timer), Sleeping (Periodic), Ready, Idle, Dead.
|
Priority
|
The priority of the process. Possible values: Low, Normal, High.
|

Note
Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after a large number of invocations or a reasonable, measured run time.
For a list of process descriptions, refer to http://www.cisco.com/warp/public/63/showproc_cpu.html.
Related Commands
Command
|
Description
|
show processes memory
|
Displays amount of system memory used per system process.
|
show processes cpu
To display CPU utilization information about the active processes in a device, use the show processes cpu command in privileged EXEC mode.
show processes cpu [history | sorted]
Syntax Description
history
|
(Optional) Displays CPU history in a graph format.
|
sorted
|
(Optional) Displays CPU utilization sorted by percentage.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
12.2(2)T
|
The history keyword was added.
|
12.3(8)T
|
This command was enhanced to display Address Resolution Protocol (ARP) output.
|
Usage Guidelines
When you use the optional history keyword, output shows (in ASCII graphical form) the total CPU usage on the device over a period of time. Time periods are one minute, one hour, and 72 hours, displayed in increments of one second, one minute, and one hour, respectively. 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.
Examples
The following is sample output from the show processes cpu command without keywords:
Router# show processes cpu
CPU utilization for five seconds: 5%/2%; one minute: 3%; five minutes: 2%
PID Runtime (ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
1 1736 58 29931 0% 0% 0% 0 Check heaps
2 68 585 116 1.00% 1.00% 0% 0 IP Input
3 0 744 0 0% 0% 0% 0 TCP Timer
4 0 2 0 0% 0% 0% 0 TCP Protocols
5 0 1 0 0% 0% 0% 0 BOOTP Server
6 16 130 123 0% 0% 0% 0 ARP Input
7 0 1 0 0% 0% 0% 0 Probe Input
8 0 7 0 0% 0% 0% 0 MOP Protocols
9 0 2 0 0% 0% 0% 0 Timers
10 692 64 10812 0% 0% 0% 0 Net Background
11 0 5 0 0% 0% 0% 0 Logger
12 0 38 0 0% 0% 0% 0 BGP Open
13 0 1 0 0% 0% 0% 0 Net Input
14 540 3466 155 0% 0% 0% 0 TTY Background
15 0 1 0 0% 0% 0% 0 BGP I/O
16 5100 1367 3730 0% 0% 0% 0 IGRP Router
17 88 4232 20 0.20% 1.00% 0% 0 BGP Router
18 152 14650 10 0% 0% 0% 0 BGP Scanner
19 224 99 2262 0% 0% 1.00% 0 Exec
The following is sample output of the one-hour portion of the output. The Y-axis of the graph is the CPU utilization. The X-axis of the graph is the increment within the time period displayed in the graph. This example shows the individual minutes during the previous hour. The most recent measurement is on the left of the X-axis.
router# show processes cpu history
!--- One minute output omitted
6665776865756676676666667667677676766666766767767666566667
6378016198993513709771991443732358689932740858269643922613
70 * * ***** * ** ***** *** **** ****** * ******* * *
60 #***##*##*#***#####*#*###*****#*###*#*#*##*#*##*#*##*****#
50 ##########################################################
40 ##########################################################
30 ##########################################################
20 ##########################################################
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
!--- 72-hour output omitted
The top two rows, read vertically, display the highest percentage of CPU utilization recorded during the time increment. In this example, the CPU utilization for the last minute recorded is 66 percent. The device may have reached 66 percent only once during that minute, or it may have reached 66 percent multiple times. The device records only the peak reached during the time increment and the average over the course of that increment.
The following is sample output from the show processes cpu command that shows an ARP probe process:
Router# show processes cpu | include ARP
17 38140 389690 97 0.00% 0.00% 0.00% 0 ARP Input
36 0 1 0 0.00% 0.00% 0.00% 0 IP ARP Probe
40 0 1 0 0.00% 0.00% 0.00% 0 ATM ARP INPUT
80 0 1 0 0.00% 0.00% 0.00% 0 RARP Input
114 0 1 0 0.00% 0.00% 0.00% 0 FR ARP
Table 150 describes the fields shown in the output.
Table 150 show processes cpu Field Descriptions
Field
|
Description
|
CPU utilization for five seconds
|
CPU utilization for the last 5 seconds and the percent of CPU time spent at the interrupt level.
|
one minute
|
CPU utilization for the last minute and the percent of CPU time spent at the interrupt level.
|
five minutes
|
CPU utilization for the last 5 minutes and the percent of CPU time spent at the interrupt level.
|
PID
|
Process ID.
|
Runtime (ms)
|
CPU time the process has used (in milliseconds).
|
Invoked
|
Number of times the process has been invoked.
|
uSecs
|
Microseconds of CPU time for each process invocation.
|
5Sec
|
CPU utilization by task in the last 5 seconds.
|
1Min
|
CPU utilization by task in the last minute.
|
5Min
|
CPU utilization by task in the last 5 minutes.
|
TTY
|
Terminal that controls the process.
|
Process
|
Name of the process.
|
Note
Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only after several invocations or a reasonable, measured run time.
Related Commands
Command
|
Description
|
show processes memory
|
Displays the amount of system memory used per system process.
|
show processes cpu autoprofile hog
To see the CPUHOG profile data, use the show processes cpu autoprofile hog command in user EXEC or privileged EXEC mode.
show processes cpu autoprofile hog
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Examples
The following is sample output from the show processes cpu autoprofile hog command:
Router# show processes cpu autoprofile hog
Related Commands
Command
|
Description
|
processes cpu autoprofile hog
|
Enables automatic CPU profiling.
|
show processes cpu extended
To see an extended CPU load report, use the show processes cpu extended command in user EXEC or privileged EXEC mode.
show processes cpu extended [history]
Syntax Description
history
|
(Optional) Displays the extended CPU load statistics for the entire history available, as configured by the process cpu extended [history history-size] command. The absence of the history keyword displays only the last report.
|
Command Modes
User EXEC
Privileged EXEC
Command History