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

Kron Occurrence 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:

Router# show logging 

Syslog logging: enabled (10 messages dropped, 5 messages rate-limited,

                0 flushes, 0 overruns, xml disabled, filtering disabled)

    Console logging: level debugging, 31 messages logged, xml disabled,

                     filtering disabled

    Monitor logging: disabled

    Buffer logging: level errors, 36 messages logged, xml disabled,

                    filtering disabled

    Logging Exception size (8192 bytes)

    Count and timestamp logging messages: disabled

No active filter modules.

    Trap logging: level informational, 45 message lines logged

Log Buffer (8192 bytes):

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.

Router> show logging

Syslog logging:enabled (2 messages dropped, 0 flushes, 0 overruns)

    Console logging:disabled

    Monitor logging:level debugging, 0 messages logged

    Buffer logging:level debugging, 4104 messages logged

    Trap logging:level debugging, 4119 message lines logged

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

Notification sent

.Jul 11 15:31:34 EDT:%BGP-3-NOTIFICATION:sent to neighbor 209.165.200.226 3/1 
(update malformed) 0 bytes

 .

 .

 .

The software clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the "authoritative" flag is set, the flag prevents peers from synchronizing to the software clock.

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

|  1  |       |       |       |       |       |       |       |       |

|  2  |       |       |       |     1 |     4 |    45 |       |       |

|  3  |       |       |       |       |       |       |       |       |

|  4  |       |       |       |     5 |     4 |    54 |       |       |

|  5  |       |       |       |       |       |       |       |       |

|  6  |       |       |       |       |       |       |       |       |

|  7  |       |       |       |    17 |     4 |    48 |       |       |

|  8  |       |       |       |       |       |       |       |       |

|  9  |       |       |       |     1 |     4 |    47 |       |       |

| 10  |       |       |       |       |       |       |       |       |

| 11  |       |       |       |    12 |     4 |    65 |       |       |

+-----+-------+-------+-------+-------+-------+-------+-------+-------+

Router#

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            RESTART                            5    1   00:00:11

SYS            CONFIG_I                           5    1   00:00:05

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

SYS TOTAL                                              3

LINEPROTO      UPDOWN                             5   13   00:00:19

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

LINEPROTO TOTAL                                       13

LINK           UPDOWN                             3    1   00:00:18

LINK           CHANGED                            5   12   00:00:09

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

LINK TOTAL                                            13

SNMP           COLDSTART                          5    1   00:00:11

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

SNMP TOTAL                                             1

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

SYS TOTAL                                              3

LINEPROTO TOTAL                                       13

LINK TOTAL                                            13

SNMP TOTAL                                             1

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

  timestamp: 1110

Router#

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.

Router# show logging

Syslog logging: enabled (10 messages dropped, 6 messages rate-limited, 0 flushes, 0 
overruns, xml enabled)

    Console logging: level debugging, 28 messages logged, xml enabled

    Monitor logging: level debugging, 0 messages logged, xml enabled

    Buffer logging: level debugging, 2 messages logged, xml enabled (2 messages logged)

    Logging Exception size (8192 bytes)

    Count and timestamp logging messages: disabled

    Trap logging: level informational, 35 message lines logged

        Logging to 1.2.3.4, 1 message lines logged, xml disabled

        Logging to 4.3.2.1, 1 message lines logged, xml enabled

Log Buffer (8192 bytes):

00:04:20: %SYS-5-CONFIG_I: Configured from console by console

00:04:41: %SYS-5-CONFIG_I: Configured from console by console

Router# show logging xml

<syslog-logging status="enabled" msg-dropped="10" msg-rate-limited="6" flushes="0" 
overruns="0"><xml>enabled</xml></syslog-logging>

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

Router#

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

Mgmt Triggers:

 (1): Owner: joe_user

  (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

      StartUp:  Present, Absent

         ObjOwn: , Obj: , EveOwn: aseem, Eve: 09 

      Boolean Entry:

         Value: 10, Cmp: 1, Start: 1

         ObjOwn: , Obj: , EveOwn: aseem, Eve: 09 

      Threshold Entry:

         Rising: 50000, Falling: 20000

         ObjOwn: ase, Obj: 01 RisEveOwn: ase, RisEve: 09 , FallEveOwn: ase, FallEve: 09 

      Delta Value Table:

  (0): Thresh: Rising, Exis: 1, Read: 0, OID: ifEntry.10.3 , val: 69356097

 Mgmt Events:

 (1): Owner: aseem

   (1)Name: 09 , Comment: , Action: Set, Notify, Enabled: 1 Status: 1

      Notification Entry:

         ObjOwn: , Obj: , OID: ifEntry.10.1

      Set:

         OID: ciscoSyslogMIB.1.2.1.0, SetValue: 199, Wildcard: 2 TAG: , ContextName: 

 Object Table:

 (1): Owner: aseem

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

Router# show memory

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

Processor    B0EE38    5181896    2210036    2971860    2692456    2845368

          Processor memory

Address   Bytes Prev.    Next     Ref  PrevF   NextF   Alloc PC  What

B0EE38     1056 0        B0F280     1                  18F132    List Elements

B0F280     2656 B0EE38   B0FD08     1                  18F132    List Headers

B0FD08     2520 B0F280   B10708     1                  141384    TTY data

B10708     2000 B0FD08   B10F00     1                  14353C    TTY Input Buf

B10F00      512 B10708   B11128     1                  14356C    TTY Output Buf

B11128     2000 B10F00   B11920     1                  1A110E    Interrupt Stack 

B11920       44 B11128   B11974     1                  970DE8    *Init*

B11974     1056 B11920   B11DBC     1                  18F132    messages

B11DBC       84 B11974   B11E38     1                  19ABCE    Watched Boolean 

B11E38       84 B11DBC   B11EB4     1                  19ABCE    Watched Boolean 

B11EB4       84 B11E38   B11F30     1                  19ABCE    Watched Boolean 

B11F30       84 B11EB4   B11FAC     1                  19ABCE    Watched Boolean 

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

Router# show memory free

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

Processor      B0EE38    5181896    2210076    2971820    2692456    2845368

          Processor memory

Address   Bytes Prev.    Next     Ref  PrevF   NextF   Alloc PC  What

             24    Free list 1

CEB844       32  CEB7A4 CEB88C      0  0       0       96B894    SSE Manager

             52    Free list 2

             72    Free list 3

             76    Free list 4

             80    Free list 5

D35ED4       80 D35E30   D35F4C     0  0       D27AE8  96B894    SSE Manager

D27AE8       80 D27A48   D27B60     0  D35ED4  0       22585E    SSE Manager

             88    Free list 6

            100    Free list 7

D0A8F4      100 D0A8B0   D0A980     0  0       0       2258DA    SSE Manager

            104    Free list 8

B59EF0      108 B59E8C   B59F84     0  0       0       2258DA    (fragment)

The output of the show memory free command contains the same types of information as the show memory output, except that only free memory is displayed, and the information is 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:

Router# show memory io

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

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

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

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

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

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

6177640 2657056 6172E90 0        0   614FCA0 0        0 

Total: 2723244

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

Router# show memory overflow

Count   Buffer Count     Last corrected      Crashinfo files

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

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

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

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

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

Router# show memory sram

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

7AE0      38178 72F0    0        0    0       0       0

Total     38178 

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

Router# show memory

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

Processor    49C724   28719324    1510864   27208460   26511644   15513908

      I/O   6000000    4194304    1297088    2897216    2869248    2896812

     SRAM      1000      65536      63400       2136       2136       2136

Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What

1000       2032 0       17F0       1                  3E73E     *Init*

17F0       2032 1000    1FE0       1                  3E73E     *Init*

1FE0        544 17F0    2200       1                  3276A     *Init*

2200         52 1FE0    2234       1                  31D68     *Init*

2234         52 2200    2268       1                  31DAA     *Init*

2268         52 2234    229C       1                  31DF2     *Init*

72F0       2032 6E5C    7AE0       1                  3E73E     Init

7AE0      38178 72F0    0          0    0      0      0         

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

The following is a partial sample output from the show memory summary command. This output shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see Table 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

          Processor memory

Alloc PC        Size     Blocks      Bytes    What

0x2AB2           192          1        192    IDB: Serial Info

0x70EC            92          2        184    Init

0xC916           128         50       6400    RIF Cache

0x76ADE         4500          1       4500    XDI data

0x76E84         4464          1       4464    XDI data

0x76EAC          692          1        692    XDI data

0x77764          408          1        408    Init

0x77776          116          1        116    Init

0x777A2          408          1        408    Init

0x777B2          116          1        116    Init

0xA4600           24          3         72    List

0xD9B5C           52          1         52    SSE Manager

.......................

0x0                0       3413    2072576    Pool Summary

0x0                0         28    2971680    Pool Summary (Free Blocks)

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

0x0                0       3413    2072576    Memory Summary

0x0                0         28    2971680    Memory Summary (Free Blocks)

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

          Processor memory

 Address  Bytes Prev.    Next     Ref    Alloc Proc    Alloc PC  What

6148EC40   1504 0        6148F24C   1  *Init*          602310FC  List Elements

6148F24C   3004 6148EC40 6148FE34   1  *Init*          60231128  List Headers

6148FE34   9000 6148F24C 61492188   1  *Init*          6023C634  Interrupt Stack

61492188     44 6148FE34 614921E0   1  *Init*          60C17FD8  *Init*

614921E0   9000 61492188 61494534   1  *Init*          6023C634  Interrupt Stack

61494534     44 614921E0 6149458C   1  *Init*          60C17FD8  *Init*

6149458C    220 61494534 61494694   1  *Init*          602450F4  *Init*

61494694   4024 6149458C 61495678   1  *Init*          601CBD64  TTY data

.

.

.

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

    PC          Total   Count  Name

0x4041AF8C    5710616    3189  *Packet Data*

0x4041AF40    2845480    3190  *Packet Header*

0x404DBA28    1694556     203  Process Stack

0x4066EA68    1074080      56  Init

0x404B5F68    1049296       9  pak subblock chunk

0x41DCF230     523924      47  TCL Chunks

0x404E2488     448920       6  MallocLite

0x4066EA8C     402304      56  Init

0x40033878     397108       1  Init

0x41273E24     320052       1  CEF: table event ring

0x404B510C     253152      24  TW Buckets

0x42248F0C     229428       1  Init

0x42248F28     229428       1  Init

0x42248F48     229428       1  Init

0x423FF210     218048       5  Dn48oC!M

0x421CB530     208144       1  epa crypto blk

0x417A07F0     196764       3  L2TP Hash Table

0x403AFF50     187836       3  Init

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:

Router# show memory dead 

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

       I/O    600000    2097152     461024    1636128      1635224      1635960 

          Processor memory 

 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

Adding blocks for GD...

                 PCI memory

Address    Size   Alloc_pc  PID  Name

                 I/O memory

Address    Size   Alloc_pc  PID  Name

                 Processor memory

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

Adding blocks for GD...

                 PCI memory

Address    Size   Alloc_pc  PID  Name

Chunk Elements:

Address  Size  Parent   Name

                 I/O memory

Address    Size   Alloc_pc  PID  Name

Chunk Elements:

Address  Size  Parent   Name

                 Processor memory

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

Chunk Elements:

Address  Size  Parent   Name

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

Adding blocks for GD...

                 PCI memory

Alloc_pc    total leak size

                 I/O memory

Alloc_pc    total leak size

                 Processor memory

Alloc_pc    total leak size

608D2848    32776     inconclusive

608D2FD8    32776     inconclusive

60C656AC    288       inconclusive

60C67D74    48        inconclusive

605B7E98    40        inconclusive

605B7EDC    40        inconclusive

60C659D4    40        inconclusive

605B7E70    32        inconclusive

605B7EB4    32        inconclusive

60616750    24        inconclusive

The following example shows output from the second invocation of the show memory debug leaks largest command:

Router# show memory debug leaks largest

Adding blocks for GD...

                 PCI memory

Alloc_pc    total leak size

                 I/O memory

Alloc_pc    total leak size

                 Processor memory

Alloc_pc    total leak size

608D2848    32776

608D2FD8    32776

60C656AC    288

60C67D74    48

605B7E98    40

605B7EDC    40

60C659D4    40

605B7E70    32

605B7EB4    32

60616750    24

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

Adding blocks for GD...

                 PCI memory

Alloc PC        Size     Blocks      Bytes    What

                 I/O memory

Alloc PC        Size     Blocks      Bytes    What

                 Processor memory

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

442850BC        2  44284960   bss

44285110        3  44284960   bss

4429C33C        2  44284960   bss

4429C34C        2  44284960   bss

4429C35C        3  44284960   bss

.

.

.

The following is sample output from the show memory debug references 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:

Router# show memory ecc

ECC Single Bit error log

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

Single Bit error detected and corrected at 0x574F3640

- Occured 1 time(s)

- Whether a scrub was attempted at this address: Yes

- Syndrome of the last error at this address: 0xE9

- Error detected on a read-modify-write cycle ? No

- Address region classification: Unknown

- Address media classification : Read/Write Single Bit error detected and corrected at 
0x56AB3760

- Occured 1 time(s)

- Whether a scrub was attempted at this address: Yes

- Syndrome of the last error at this address: 0x68

- Error detected on a read-modify-write cycle ? No

- Address region classification: Unknown

- 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 

Processor memory

Free memory size : 65516944 Number of free blocks:      230

Allocator PC Summary for allocated blocks in pool: Processor

    PC          Total   Count  Name

0x6047DDCC     852020       1  atmdx_vc_table

0x6075DC30     544392       4  ATM1/0

0x61BDBA14     131176       2  eddri_self_event

0x61913BEC     131124       1  l2tp tnl table

0x602E9820     114832       1  AutoVC Msg Chunk

0x6071253C      98408       2  Exec

0x607DF5BC      96624      12  Process Stack

0x6118DDA0      77252       1  Spanning Tree Opt Port Block

0x61F13C30      67636       1  QOS_MODULE_MAIN

0x6047DD3C      65640       2  atmdx_tx_shadow

0x614B6624      65588       1  CEF: loadinfo chunk

0x614D1924      65588       1  IP mtrie node

0x614A58A0      65588       1  CEF: 16 path chunk pool

0x619241D4      65588       1  PPTP mgd timer chunk

0x606581CC      65588       1  AAA DB Chunk

0x607E5EAC      65588       1  MallocLite

0x6192420C      65588       1  PPTP: pptp_tunneltype chunk

0x6075DCB8      45924      10  FastEthernet2/

0x607CA400      36288       2  pak subblock chunk

0x6255648C      28948       1  CCPROXY_CT

0x6047DD7C      24628       1  atmdx_bfd_cache

0x6047DAA4      23500       1  atmdx_instance

0x6047DAE8      23500       1  atmdx_instance snap

0x60962DFC      21420      17  TCP CB

0x616F729C      20052       1  AC context chunks

0x616F72C8      20052       1  AC Mgr mgd timer chunk

0x60734010      16644      19  *Packet Header*

0x6047DE0C      16436       1  atmdx_abr_stats

0x6047DCFC      16112       2  atmdx_rx_pool_info

0x60A77E98      13060       1  DHCPD Message Workspace

0x61F50008      12852       1  CCVPM_HTSP

0x60D509BC      12580      17  Virtual Exec

0x60EFA1EC      12344       1  RSVP DB Handle Bin

.

.

.

0x6067AE44         76       1  AAA Secrettype encrypt

0x61C0EEC0         76       1  Init

0x60F76B1C         76       1  SNMP Trap

0x60BE2444         76       1  Init

0x62638F78         76       1  EEM ED Syslog

0x6077C574         76       1  Init

0x608F7030         76       1  IPC Name String

0x608EEAB8         76       1  IPC Name

0x620468A8         76       1  ivr: ccapAppEntry_t name

0x6066D084         76       1  gk process

0x6064824C         76       1  AAA MI SG NAME

Allocator PC Summary for free blocks in pool: Processor

    PC          Total   Count  Name

0x6071253C   67387912       2  (fragment)

0x60734010   63292440      11  *Packet Header*

0x60962DFC     105552      10  (coalesced)

0x60D509BC      98384      10  (coalesced)

0x60D4A0B4      70776       9  (coalesced)

0x60803260      21488       4  (fragment)

0x60B2E488      19704       2  (fragment)

0x606E0278      19272       1  (coalesced)

0x606DD8D8       9024     113  Init

0x60B27FE8       5740       3  (fragment)

0x60778AAC       3504       1  (coalesced)

0x607AC764       2212      11  Process Events

0x60F7FCD4       1556       9  (fragment)

0x6071F3FC       1316      12  (fragment)

0x606C5324       1176       6  (coalesced)

0x60D7C518       1148       1  (coalesced)

0x624E170C        876       1  (coalesced)

0x60A68164        588       3  (fragment)

0x60B302C0        408       5  (fragment)

0x60976574        272       2  AAA Event Data

0x60801E38        216       2  (fragment)

0x611DA23C        164       1  shelf_info

0x60A6A638        148       1  (fragment)

0x60801D2C        148       1  (fragment)

0x60D29DCC        148       1  (fragment)

0x62628CA0        144       1  (fragment)

0x60A68218        104       1  (fragment)

0x606B9614         88       1  NameDB String

0x6090A978         84       1  (fragment)

0x606C51D0         84       1  (fragment)

0x62647558         76       1  (fragment)

The following is sample output from the show memory processor fragment detail command:

Router# show memory processor fragment detail 

Processor memory

Free memory size : 65566148 Number of free blocks:      230

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

645A8148 0000000028 645A80F0 645A8194 001  -------- -------- 60695B20  Init

645A8194 0000000040 645A8148 645A81EC 000  0        200B4300 606B9614  NameDB String

645A81EC 0000000260 645A8194 645A8320 001  -------- -------- 607C2D20  Init

200B42B4 0000000028 200B4268 200B4300 001  -------- -------- 62366C80  Init

200B4300 0000000028 200B42B4 200B434C 000  645A8194 6490F7E8 60976574  AAA Event Data

200B434C 0000002004 200B4300 200B4B50 001  -------- -------- 6267D294  Coproc Request 
Structures

6490F79C 0000000028 6490F748 6490F7E8 001  -------- -------- 606DDA04  Parser Linkage

6490F7E8 0000000028 6490F79C 6490F834 000  200B4300 6491120C 606DD8D8  Init

6490F834 0000006004 6490F7E8 64910FD8 001  -------- -------- 607DF5BC  Process Stack

649111A0 0000000060 64911154 6491120C 001  -------- -------- 606DE82C  Parser Mode

6491120C 0000000028 649111A0 64911258 000  6490F7E8 500770F0 606DD8D8  Init

64911258 0000000200 6491120C 64911350 001  -------- -------- 603F0E38  Init

.

.

.

504DCF54 0000001212 504DB2E4 504DD440 001  -------- -------- 60962DFC  TCP CB

2C41DCA4 0000000692 2C41BCC8 2C41DF88 001  -------- -------- 60D509BC  Virtual Exec

2C41DF88 0000005344 2C41DCA4 2C41F498 000  504DB2E4 6449A828 60D509BC  (coalesced)

2C41F498 0000000692 2C41DF88 2C41F77C 001  -------- -------- 60D509BC  Virtual Exec

6449A544 0000000692 64499794 6449A828 001  -------- -------- 60D509BC  Virtual Exec

6449A828 0000007760 6449A544 6449C6A8 000  2C41DF88 504D89D4 60D509BC  (coalesced)

6449C6A8 0000008044 6449A828 6449E644 001  -------- -------- 60D2AACC  Virtual Exec

504D8778 0000000556 504D754C 504D89D4 001  -------- -------- 60D4A0B4  Virtual Exec

504D89D4 0000009860 504D8778 504DB088 000  6449A828 504D1B78 60D4A0B4  (coalesced)

504DB088 0000000556 504D89D4 504DB2E4 001  -------- -------- 60D4A0B4  Virtual Exec

504D168C 0000001212 504C9658 504D1B78 001  -------- -------- 60962DFC  TCP CB

504D1B78 0000008328 504D168C 504D3C30 000  504D89D4 504C5B54 60962DFC  (coalesced)

504D3C30 0000001212 504D1B78 504D411C 001  -------- -------- 60962DFC  TCP CB

504C5870 0000000692 504C5504 504C5B54 001  -------- -------- 60D509BC  Virtual Exec

504C5B54 0000005344 504C5870 504C7064 000  504D1B78 2C423A88 60D509BC  (coalesced)

504C7064 0000000408 504C5B54 504C722C 001  -------- -------- 606E0E44  Chain Cache No

2C42359C 0000001212 2C41F77C 2C423A88 001  -------- -------- 60962DFC  TCP CB

2C423A88 0000008328 2C42359C 2C425B40 000  504C5B54 504D411C 60962DFC  (coalesced)

504E7DD8 0000000828 504E2660 504E8144 001  -------- -------- 60734010  *Packet Header*

65006A08 0000000408 65003834 65006BD0 001  -------- -------- 606E0E44  Chain Cache No

65006BD0 0000020520 65006A08 6500BC28 000  504E2660 0        60803260  (coalesced)

6500BC28 0000000828 65006BD0 6500BF94 001  -------- -------- 60734010  *Packet Header*

5C3AE7B8 0000000828 5C3AE614 5C3AEB24 001  -------- -------- 60734010  *Packet Header*

5C3AEB24 0063247532 5C3AE7B8 20000000 000  0        6500C300 60734010  (coalesced)

20000000 0000000828 5C3AEB24 2000036C 001  -------- -------- 60734010  *Packet Header*

6500BF94 0000000828 6500BC28 6500C300 001  -------- -------- 60734010  *Packet Header*

6500C300 0004760912 6500BF94 50000000 000  5C3AEB24 2C42E310 6071253C  (coalesced)

50000000 0000000828 6500C300 5000036C 001  -------- -------- 60734010  *Packet Header*

2C42E0B4 0000000556 2C429430 2C42E310 001  -------- -------- 60D4A0B4  Virtual Exec

2C42E310 0062725312 2C42E0B4 00000000 000  6500C300 0        6071253C  (coalesced)

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

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

6540BBA0 0000016388 00000000 6540FBD4 001  -------- -------- 60883984  TW Buckes

6540FBD4 0000016388 6540BBA0 65413C08 001  -------- -------- 60883984  TW Buckes

65413C08 0000016388 6540FBD4 65417C3C 001  -------- -------- 60883984  TW Buckes

65417C3C 0000006004 65413C08 654193E0 001  -------- -------- 608A0D4C  Process k

654193E0 0000012004 65417C3C 6541C2F4 001  -------- -------- 608A0D4C  Process k

6541C2F4 0000411712 654193E0 65480B64 000  0        0        608A0D4C  (fragmen)

65480B64 0000020004 6541C2F4 654859B8 001  -------- -------- 608CF99C  Managed s

654859B8 0000010004 65480B64 654880FC 001  -------- -------- 6085C7F8  List Eles

654880FC 0000005004 654859B8 654894B8 001  -------- -------- 6085C83C  List Heas

654894B8 0000000048 654880FC 65489518 001  -------- -------- 62BF31DC  *Init*

.

.

.

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:

Router# show memory pci

          I/O memory

 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

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

6540BBA0 0000016388 00000000 6540FBD4 001  -------- -------- 60883984  TW Buckes

6540FBD4 0000016388 6540BBA0 65413C08 001  -------- -------- 60883984  TW Buckes

65413C08 0000016388 6540FBD4 65417C3C 001  -------- -------- 60883984  TW Buckes

65417C3C 0000006004 65413C08 654193E0 001  -------- -------- 608A0D4C  Process k

654193E0 0000012004 65417C3C 6541C2F4 001  -------- -------- 608A0D4C  Process k

6541C2F4 0000411712 654193E0 65480B64 000  0        0        608A0D4C  (fragmen)

65480B64 0000020004 6541C2F4 654859B8 001  -------- -------- 608CF99C  Managed s

654859B8 0000010004 65480B64 654880FC 001  -------- -------- 6085C7F8  List Eles

654880FC 0000005004 654859B8 654894B8 001  -------- -------- 6085C83C  List Heas

654894B8 0000000048 654880FC 65489518 001  -------- -------- 62BF31DC  *Init*

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

          Processor memory

Free memory size :  3144348 Number of free blocks:       96

Allocator PC Summary for allocated blocks in pool: Processor

    PC          Total   Count  Name

0x6069A038     262196       1  TACL FLT

0x62224AA8     219188       1  QOS_MODULE_MAIN

0x61648840     131124       1  Init

0x6218DAA4      73780       1  CCSIP_UDP_SOCKET

0x61649288      65588       1  CEF: loadinfo chunk

0x61BFD4B8      65588       1  PPTP mgd timer chunk

0x61EE1050      65588       1  eddri_self_event

0x607C13C4      49204       1  Exec

0x608A0D4C      35208       4  Process Stack

0x6069D804      32052       1  TACL hist

0x61631A90      21444       2  CEF: IPv4 Unicast RPF subblock

0x62BA5DD8      20432       1  Init

0x6086F858      20052       1  RMI-RO_RU Chun

0x608CF99C      20052       1  Managed Chunk Queue Elements

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

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

             24    Free list 1

66994680 0000000072 66994618 669946FC 000  0        6698FFC8 60699114  Turbo ACr

6698FFC8 0000000072 6698FF60 66990044 000  66994680 659CF6B0 60699114  Turbo ACr

659CF6B0 0000000024 659CF678 659CF6FC 000  6698FFC8 659CF86C 6078A2CC  Init

659CF86C 0000000024 659CF710 659CF8B8 000  659CF6B0 65ADB53C 6078A2CC  Init

65ADB53C 0000000024 65ADB504 65ADB588 000  659CF86C 65ADFC38 6078A2CC  Init

65ADFC38 0000000024 65ADFC00 65ADFC84 000  65ADB53C 65B6C504 6078A2CC  Init

65B6C504 0000000024 65B6C4B8 65B6C550 000  65ADFC38 6593E924 6078A2CC  Init

6593E924 0000000028 6593E8E8 6593E974 000  65B6C504 65CCB054 6078A2CC  Init

65CCB054 0000000024 65CCB01C 65CCB0A0 000  6593E924 65CCBD98 6078A2CC  Init

65CCBD98 0000000028 65CCBD60 65CCBDE8 000  65CCB054 65CCFB70 6078A2CC  Init

65CCFB70 0000000024 65CCFB38 65CCFBBC 000  65CCBD98 65D0BB58 6078A2CC  Init

65D0BB58 0000000024 65D0BB20 65D0BBA4 000  65CCFB70 65D0C5F0 6078A2CC  Init

65D0C5F0 0000000024 65D0C5B8 65D0C63C 000  65D0BB58 65CFF2F4 6078A2CC  Init

65CFF2F4 0000000024 65CFF2BC 65CFF340 000  65D0C5F0 6609B7B8 6078A2CC  Init

6609B7B8 0000000036 6609AFC8 6609B810 000  65CFF2F4 660A0BD4 6078A2CC  Init

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:

Router# show memory scan

Memory scan is on.

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:

Router# show memory scan

Memory scan is on.

Total Parity Errors 1.

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

Time: 15:48:56.806

Used(b): 422748036 Largest(b): 381064952 Free blocks :291

Maximum memory users for this period

Process Name           Holding   Num Alloc

Virtual Exec             26992          37

TCP Protocols            14460           6

IP Input                  1212           1

Time: 14:42:54.506

Used(b): 422705876 Largest(b): 381064952 Free blocks :296

Maximum memory users for this period

Process Name           Holding   Num Alloc

Exec                  400012740          24

Dead                   1753456          90

Pool Manager            212796         257

Time: 13:37:26.918

Used(b): 20700520 Largest(b): 381064952 Free blocks :196

Maximum memory users for this period

Process Name           Holding   Num Alloc

Exec                      8372           5

Time: 12:39:44.422

Used(b): 20701436 Largest(b): 381064952 Free blocks :193

Time: 11:46:25.135

Used(b): 20701436 Largest(b): 381064952 Free blocks :193

Maximum memory users for this period

Process Name           Holding   Num Alloc

CDP Protocol              3752          25

Time: 10:44:24.342

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 09:38:53.038

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 08:33:35.154

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 07:28:05.987

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 06:35:22.878

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 05:42:14.286

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 04:41:53.486

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 03:48:47.891

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 02:46:32.391

Used(b): 20701400 Largest(b): 381064952 Free blocks :194

Time: 01:54:27.931

Used(b): 20717804 Largest(b): 381064952 Free blocks :189

Time: 01:02:05.535

Used(b): 20717804 Largest(b): 381064952 Free blocks :189

Maximum memory users for this period

Process Name           Holding   Num Alloc

Entity MIB API           67784          16

TTY Background           12928           4

Exec                      7704           3

Time: 00:00:17.936

Used(b): 21011192 Largest(b): 381064952 Free blocks :186

Maximum memory users for this period

Process Name           Holding   Num Alloc

Init                  18653520        6600

CCPROXY_CT              599068          57

Proxy Session Applic    275424          21

History for I/O memory

Time: 15:48:56.809

Used(b):  7455520 Largest(b): 59370080 Free blocks :164

Time: 14:42:54.508

Used(b):  7458064 Largest(b): 59370080 Free blocks :165

Maximum memory users for this period

Process Name           Holding   Num Alloc

Pool Manager            141584         257

Time: 13:37:26.920

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 12:39:44.424

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 11:46:25.137

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 10:44:24.344

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 09:38:53.040

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 08:33:35.156

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 07:28:05.985

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 06:35:22.877

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 05:42:14.285

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 04:41:53.485

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 03:48:47.889

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 02:46:32.389

Used(b):  7297744 Largest(b): 59797664 Free blocks :25

Time: 01:54:27.929

Used(b):  7308336 Largest(b): 59797664 Free blocks :23

Time: 01:02:05.533

Used(b):  7308336 Largest(b): 59797664 Free blocks :23

Time: 00:00:17.937

Used(b):  7308336 Largest(b): 59797664 Free blocks :23

Maximum memory users for this period

Process Name           Holding   Num Alloc

Init                   7296000         214

Pool Manager               816           3

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

          Processor memory

 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:

Router# show microcode

Microcode bundled in system

Card    Microcode    Target Hardware    Description

Type    Version      Version

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

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.

router# show microcode

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 

Test1 event trace:

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

Test2 event trace:

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

00:01:07.320:  1     CPU                None

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

00:01:07.320:  1     CPU                None

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 21:03:56

Queue Statistics

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

             Exec Count  Total CPU    Response Time        Queue Length

                                       (avg/max)             (avg/max)

Critical           1          0          0/0                   1/1         

High               5          0          0/0                   1/1         

Normal           178          0          0/0                   2/9         

Low               15          0          0/0                   2/3         

Common Process Information

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

 PID Name            Prio Style

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

  10 AAA high-capacit M  New

 133 RADIUS TEST CMD  M  New

  47 VNM DSPRM MAIN   H  New

  58 TurboACL         M  New

  97 IP Background    M  New

  99 CEF: IPv4 proces L  New

 112 X.25 Background  M  New

 117 LFDp Input Proc  M  New

   3 Init             M  Old

CPU Intensive processes

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

 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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

   3          6          1

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

  10          1 15192/15192

 133          1 15192/15192

  58          1 15192/15192

 112          1 15192/15192

 117          1 15192/15192

  99          1 15172/15172

  47          1 15172/15172

  97          1 15172/15172

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 00:00:00

Queue Statistics

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

        Exec Count  Total CPU     Response Time           Queue Length

                                    (avg/max)                (avg/max)

Critical      0          0              0/0                    0/0         

High          0          0              0/0                    0/0         

Normal        0          0              0/0                    0/0         

Low           0          0              0/0                    0/0         

Common Process Information

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

 PID Name            Prio Style

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

CPU Intensive processes

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

 PID Total       Exec    Quant         Burst  Burst size  Schedcall  Schedcall 

     CPUms      Count   avg/max        Count avg/max(ms)      Count Per avg/max

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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

################################################################################

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:

Router> show ntp status

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

15 type dhcp 

indicates that the type dhcp command has a privilege level of 15 assigned to it. For information about privilege levels, see the "Configuring Passwords and Privileges" chapter in the Cisco IOS Security Configuration Guide.

Any given command-line string should indicate the full syntax needed to make the command complete and valid. In other words, the command line string ends where the carriage return (Enter) could be entered, as indicated in command-line help by the <cr> syntax. You will typically see multiple forms of a command, each showing a valid syntax combination. For example, each of the following syntax combinations, as seen in the output of the show parser dump rtr | include dhcp command, 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> 

type dhcp 

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

  all                      For all modes

  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

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

 Mode Name :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 dhcp 

15 type dns target-addr <string> name-server <address> source-ipaddr <address> source-port 
<1-65535> 

15 type dns target-addr <string> name-server <address> source-ipaddr <address> 

15 type dns target-addr <string> name-server <address> 

15 type pathEcho protocol ipIcmpEcho <address> source-ipaddr <address> 

15 type pathEcho protocol ipIcmpEcho <address> 

15 type pathJitter dest-ipaddr <address> source-ipaddr <address> 

15 type pathJitter dest-ipaddr <address> num-packets <1-100> 

15 type pathJitter dest-ipaddr <address> interval <1-1000> 

15 type pathJitter dest-ipaddr <address> targetOnly 

15 type pathJitter dest-ipaddr <address> 

15 type slm frame-relay pvc 

15 type slm controller T1 <controller> 

15 type slm controller E1 <controller> 

15 type slm controller T3 <controller> 

15 type slm controller E3 <controller> 

15 exit 

In the following example, only those commands in RTR Configuration mode containing the keyword dhcp are shown:

Router# show parser dump rtr | include dhcp 

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> circuit-id 
<string> 

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> remote-id 
<string> 

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> subnet-mask 
<ipmask> 

15 type dhcp dest-ipaddr <address> source-ipaddr <address> option <82-82> 

15 type dhcp dest-ipaddr <address> source-ipaddr <address> 

15 type dhcp dest-ipaddr <address> 

15 type dhcp 

Router#

The following example shows how the extend keyword displays the syntax descriptions that match those shown using the ? command-line help:

Router# show parser dump rtr extend   

 Mode Name :rtr

15 type udpEcho dest-ipaddr <address> dest-port <1-65535> source-ipaddr <address> 
source-port <1-65535> control enable 

type : Type of entry

udpEcho : UDP Echo Operation

dest-ipaddr : Destination address

<address> : IP address or hostname

dest-port : Destination Port

<1-65535> : Port Number

source-ipaddr : Source address

<address> : IP address or hostname

source-port : Source Port

<1-65535> : Port Number

control : Enable or disable control packets

enable : Enable control packets exchange (default)

 .

 .

 .

! Ctrl-Z used here to interrupt output and return to CLI prompt.

Router# config terminal 

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# rtr 1 

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 ? 

  <1-65535>  Port Number

Router(config-rtr)# type udpEcho dest-ipaddr HOSTNAME dest-port 1 ? 

  control        Enable or disable control packets

  source-ipaddr  Source address

  source-port    Source Port

  <cr>

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:

Device    Device number

0         First LAN device

1         Second LAN device

2         AIM device (if present)

3         Not presently used

4         Port module - first PCI device

5         Port module - second PCI device

6         Port module - third PCI device

7         Port module - fourth PCI device

8-14      Not presently used

15        Xilinx PCI bridge

Examples

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:

Router# show processes

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

   3          12 0x0        Exec                            

  16           0 0x603F4DEC GraphIt                         

  21           0 0x603CFEF4 TTY Background                  

  22           0 0x6042FD7C Per-Second Jobs                 

  67           0 0x6015CD38 SMT input                       

  39           0 0x60178804 FBM Timer                       

  16           0 0x603F4DEC GraphIt                         

  21           0 0x603CFEF4 TTY Background                  

  22           0 0x6042FD7C Per-Second Jobs                 

  16           0 0x603F4DEC GraphIt                         

  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                  

 --More-- 

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:

Router# show processes 6 

Process ID 6 [Pool Manager], TTY 0

Memory usage [in bytes]

 Holding: 921148, Maximum: 940024, Allocated: 84431264, Freed: 99432136

 Getbufs: 0, Retbufs: 0, Stack: 12345/67890

CPU usage

 PC: 0x60887600, Invoked: 188, Giveups: 100, uSec: 24

 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

100 

90 

80         *  *                     * *     *  * *  * 

70  * * ***** *  ** ***** ***  **** ******  *  *******     * * 

60  #***##*##*#***#####*#*###*****#*###*#*#*##*#*##*#*##*****# 

50  ########################################################## 

40  ########################################################## 

30  ########################################################## 

20  ########################################################## 

10  ##########################################################

   0....5....1....1....2....2....3....3....4....4....5....5.... 

             0    5    0    5    0    5    0    5    0    5 

              CPU% per minute (last 60 minutes)

             * = maximum CPU% # = average CPU%

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

0x6075DD40 0x60755638

0x6075DD24 0x60755638

0x6075563C 0x60755638

0x60755638 0x60755638

0x60755638 0x60755638

0x6075DD10 0x60755638

0x6075DD40 0x60755638

0x6075DD40 0x60755638

0x6075563C 0x60755638

0x6075DCE0 0x60755638

0x6075DD44 0x60755638

.

.

.

0x6075DCCC 0x60755638

0x6075DCDC 0x60755638

0x6075563C 0x60755638

0x6075DD3C 0x60755638

0x6075DD20 0x60755638

0x6075DD58 0x60755638

0x6075DD1C 0x60755638

0x6075DD10 0x60755638

0x6075DCDC 0x60755638

0x6075DCF8 0x60755638

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

Release	Modification
12.3(14)T	This command was introduced.

Examples

The following is sample output from the show processes cpu extended command:

Router# show processes cpu extended 

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 21:03:56

Queue Statistics

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

          Exec Count    Total CPU     Response Time        Queue Length

                                      (avg/max)             (avg/max)

Critical           1          0          0/0                   1/1         

High               5          0          0/0                   1/1         

Normal           178          0          0/0                   2/9         

Low               15          0          0/0                   2/3         

Common Process Information

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

 PID Name            Prio Style

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

CPU Intensive processes

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

 PID Total       Exec    Quant         Burst  Burst size  Schedcall  Schedcall 

     CPUms      Count   avg/max        Count avg/max(ms)      Count Per avg/max

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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

################################################################################

The following is sample output from the show processes cpu extended history command:

Router# show processes cpu extended history 

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 21:04:26

Queue Statistics

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

          Exec Count    Total CPU    Response Time         Queue Length

                                      (avg/max)             (avg/max)

Critical           1          0          0/0                   1/1         

High               5          0          0/0                   1/1         

Normal           179         12          0/12                  2/9         

Low               18          0          0/12                  1/3         

Common Process Information

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

 PID Name            Prio Style

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

CPU Intensive processes

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

 PID Total       Exec    Quant         Burst  Burst size  Schedcall  Schedcall 

     CPUms      Count   avg/max        Count avg/max(ms)      Count Per avg/max

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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 21:04:21

Queue Statistics

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

          Exec Count      Total CPU   Response Time        Queue Length

                                       (avg/max)            (avg/max)

Critical           1          0          0/0                   1/1         

High               5          0          0/0                   1/1         

Normal           174          0          0/0                   2/9         

Low               15          0          0/0                   2/3         

Common Process Information

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

 PID Name            Prio Style

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

CPU Intensive processes

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

 PID Total       Exec    Quant         Burst  Burst size  Schedcall  Schedcall 

     CPUms      Count   avg/max        Count avg/max(ms)      Count Per avg/max

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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

.

.

.

################################################################################

Global Statistics

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

5 sec CPU util 0%/0% Timestamp 21:03:31

Queue Statistics

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

          Exec Count  Total CPU    Response Time           Queue Length

                                    (avg/max)                (avg/max)

Critical           1          0          0/0                   1/1         

High               5          0          0/0                   1/1         

Normal           176          0          0/0                   2/9         

Low               15          0          0/0                   2/3         

Common Process Information

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

 PID Name            Prio Style

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

CPU Intensive processes

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

 PID Total       Exec    Quant         Burst  Burst size  Schedcall  Schedcall 

     CPUms      Count   avg/max        Count avg/max(ms)      Count Per avg/max

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

Priority Suspends

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

 PID Exec Count Prio-Susps

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

Latencies

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

 PID Exec Count   Latency

                  avg/max

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

Related Commands

Command	Description
process cpu extended [history history-size]	Collects the extended CPU load for the specified history size.

show processes memory

To show the amount of memory used by each system process, use the show processes memory command in Privileged Exec mode.

show processes memory [ pid | sorted [allocated | getbufs | holding] ]

Syntax Description

pid	(Optional) Process ID (PID) number of a specific process. When you specify a process ID, only detail for the specified process will be shown.
sorted [holding]	(Optional) Displays memory data sorted by the "Holding" column. If the sorted keyword is used by itself, data is sorted by the "Holding" column by default.
sorted allocated	(Optional) Displays memory data sorted by the "Allocated" column.
sorted getbufs	(Optional) Displays memory data sorted by the "Getbufs" (Get Buffers) column.

Defaults

Memory details are shown in order (sorted) by the process ID (PID).

Command Modes

Privileged Exec

Command History

Release	Modification
10.0	This command was introduced.
12.0(23)S, 12.2(13), 12.2(13)S, 12.2(13)T	The sorted [allocated | getbufs | holding] syntax was introduced. [CSCdy22469]
12.0(28)S, 12.2(22)S, 12.3(7)T	The output of the show processes memory pid command was updated. [CSCin50560]
12.0(29.2)S, 12.2(27)S2, 12.3(11)T	The summary information (first lines of output) for this command was separated out and labeled by memory pool type (for example, Total Process Memory, Total I/O Memory, and so on). This enhancement also corrected the total process memory mismatch error described in CSCed13322 ( mismatch between show process memory, show process memory sorted and show memory and its variants).

Usage Guidelines

The show processes memory command (and show process memory sorted command) displays a summary of total, used, and free memory, followed by a list of processes and their memory impact.

If the standard show processes memory processes command is used, processes are sorted by their process ID (PID). If the show processes memory sorted command is used, the default sorting is by the Holding value.

Output Prior to Releases 12.3(7)T, 12.2(18)S, and 12.0(26)S

The first line (header line) of the show processes memory [sorted] command listed Total memory, Used memory, and Free memory values.

Output in Releases 12.3(7)T through 12.3(10.02)T; 12.0(26)S through 12.0(29.2)S, and 12.2(18)S through 12.2(27)S2

In Releases 12.3(7)T, 12.2(18)S, 12.0(26)S the "Memory Thresholding" feature was introduced. This feature affected the header line and the "Holding" column of the show processes memory command as follows.

The value for "Total" in show process memory command, and the values listed in the Holding column, showed the total (cumulative) value for the processor memory pools and its alternate memory pool* (typically, the I/O memory pool). However, the show processes memory sorted version of this command, and other commands, such as the show memory summary command, did not include the alternate memory pool in the totals (in other words, these commands showed the total value for the Processor memory pool only). This caused an observed mismatch of memory totals between commands. This issue was addressed (fixed) by CSCed13322.

If you are using these Releases, use the output of show memory summary command to determine the individual amounts of Total and Free memory for the Processor memory pool and the I/O memory pool.

Output in Releases 12.3(11)T, 12.0(30)S, 12.2(28)S and Later

Beginning in Releases 12.0(30)S, 12.2(28)S, and 12.3(11)T, the summary information (first output lines) for the show processes memory command is separated by memory pool. For example, there are now individual lines for "Total Process Memory", "Total I/O Memory", and "Total PCI Memory." If using these releases or later, your Total Process Memory should match the total process memory shown for other commands, such as show memory summary.

*About Alternate Memory Pools

An "alternate memory pool" is a memory pool which can be used as an alternative to allocate memory when the target (main) memory pool has been filled. For example, many platforms have a memory type called "Fast" that is limited to a small size (as the memory media used for Fast memory is expensive). To prevent memory allocations from failing once the available Fast memory has been used up, the normal Processor memory can be configured as an alternative memory pool for the Fast memory pool.

Examples

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

Router# show processes memory

Processor Pool Total:   25954228 Used:    8368640 Free:   17585588

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0    8629528     689900    6751716          0          0 *Init*          

   0   0      24048      12928      24048          0          0 *Sched*         

   0   0        260        328         68     350080          0 *Dead*          

   1   0          0          0      12928          0          0 Chunk Manager   

   2   0        192        192       6928          0          0 Load Meter      

   3   0     214664        304     227288          0          0 Exec            

   4   0          0          0      12928          0          0 Check heaps     

   5   0          0          0      12928          0          0 Pool Manager    

   6   0        192        192      12928          0          0 Timers          

   7   0        192        192      12928          0          0 Serial Backgroun

   8   0        192        192      12928          0          0 AAA high-capacit

   9   0          0          0      24928          0          0 Policy Manager  

  10   0          0          0      12928          0          0 ARP Input       

  11   0        192        192      12928          0          0 DDR Timers      

  12   0          0          0      12928          0          0 Entity MIB API  

  13   0          0          0      12928          0          0 MPLS HC Counter 

  14   0          0          0      12928          0          0 SERIAL A'detect

.

.

.

  78   0          0          0      12992          0          0 DHCPD Timer     

  79   0        160          0      13088          0          0 DHCPD Database  

                                  8329440 Total

Table 151 describes the significant fields shown in the display.

Table 151 show processes memory Field Descriptions 

Field	Description
Processor Pool Total:	Total amount of memory held for the Processor memory pool.
Used:	Total amount of used memory in the Processor memory pool. (Note that this value matches the Total holding value shown on the last line of the output.)
Free:	Total amount of free memory in the Processor memory pool.
PID	Process ID.
TTY	Terminal that controls the process.
Allocated	Bytes of memory allocated by the process.
Freed	Bytes of memory freed by the process, regardless of who originally allocated it.
Holding	Amount of memory currently allocated to the process.
Getbufs	Number of times the process has requested a packet buffer.
Retbufs	Number of times the process has relinquished a packet buffer.
Process	Process name.
*Init*	System initialization process.
*Sched*	The scheduler process.
*Dead*	Processes as a group that are now dead.
<value> Total	Total amount of memory held by all processes (sum of the "Holding" column).

The following is sample output from the show processes memory command when the sorted keyword is used. In this case, the output is sorted by the Holding column, from largest to smallest.

Router# show processes memory sorted 

Processor Pool Total:   25954228 Used:    8371280 Free:   17582948

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0    8629528     689900    6751716          0          0 *Init*          

   3   0     217304        304     229928          0          0 Exec            

  53   0     109248        192      96064          0          0 DHCPD Receive   

  56   0          0          0      32928          0          0 COPS            

  19   0      39048          0      25192          0          0 Net Background  

  42   0          0          0      24960          0          0 L2X Data Daemon 

  58   0        192        192      24928          0          0 X.25 Background 

  43   0        192        192      24928          0          0 PPP IP Route    

  49   0          0          0      24928          0          0 TCP Protocols   

  48   0          0          0      24928          0          0 TCP Timer       

  17   0        192        192      24928          0          0 XML Proxy Client

   9   0          0          0      24928          0          0 Policy Manager  

  40   0          0          0      24928          0          0 L2X SSS manager 

  29   0          0          0      24928          0          0 IP Input        

  44   0        192        192      24928          0          0 PPP IPCP        

  32   0        192        192      24928          0          0 PPP Hooks       

  34   0          0          0      24928          0          0 SSS Manager     

  41   0        192        192      24928          0          0 L2TP mgmt daemon

  16   0        192        192      24928          0          0 Dialer event    

  35   0          0          0      24928          0          0 SSS Test Client 

 --More-- 

The following is sample output from the show processes memory command when a Process ID (pid) is specified:

Router# show processes memory 1 

Process ID: 1

Process Name: Chunk Manager

Total Memory Held: 8428 bytes

Processor memory holding = 8428 bytes

pc = 0x60790654, size =      6044, count =    1

pc = 0x607A5084, size =      1544, count =    1

pc = 0x6076DBC4, size =       652, count =    1

pc = 0x6076FF18, size =       188, count =    1

I/O memory holding = 0 bytes

Router# show processes memory 2 

Process ID: 2

Process Name: Load Meter

Total Memory Held: 3884 bytes

Processor memory holding = 3884 bytes

pc = 0x60790654, size =      3044, count =    1

pc = 0x6076DBC4, size =       652, count =    1

pc = 0x6076FF18, size =       188, count =    1

I/O memory holding = 0 bytes

Show Process Memory for Releases Prior to 12.0(29.02)S, 12.2(27)S2, and 12.3(10.02)T: Example

The following example shows the output of the show process memory command before the changes to the summary information were made. Note that the "Total:" in the show process summary command indicates total memory for all mempools; in this example, the show processes memory Total of 35423840 can be obtained by adding the Processor and I/O totals shown in the output of the show memory summary command. Note also that the show processes memory sorted command lists the Total Processor Memory (matches the "show memory summary" Processor Total, but the show processes memory command (without the "sorted" keyword) lists the Total for all memory pools (Processor plus I/O memory).

C3660-1# show version | include IOS 

Cisco IOS Software, 3600 Software (C3660-BIN-M), Version 12.3(9) 

C3660-1# show memory summary

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

Processor   61E379A0    27035232     8089056    18946176    17964108    17963664

      I/O    3800000     8388608     2815088     5573520     5561520     5573472

 . . .

C3660-1# show processes memory 

Total: 35423840, Used: 10904192, Free: 24519648

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0   14548868    3004980    9946092          0          0 *Init*          

   0   0      12732     567448      12732          0          0 *Sched*         

 . . .

 --More-- <break>

C3660-1# show processes memory sorted 

Total: 27035232, Used: 8089188, Free: 18946044

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0   14548868    3004980    9946092          0          0 *Init*          

  64   0      76436       3084      74768          0          0 CEF process     

 . . .

 --More-- <break>

Router# show version | inc IOS 

Cisco IOS (tm) Solaris Software (UNIX-P-M), Version 12.0(29)S, 

Router# show processes memory

Total: 50,994,868, Used: 6220092, Free: 44774776

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0    6796228     627336    5325956          0          0 *Init*          

   0   0        200      29792        200          0          0 *Sched*         

   0   0        192        744          0     349000          0 *Dead*          

   1   0          0          0      12896          0          0 Chunk Manager 

. . .

Router# show process memory sorted 

Total: 50,994,868, Used: 6222644, Free: 44772224

 PID TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0   0    6796228     627336    5325956          0          0 *Init*          

  13   0      39056          0      25264          0          0 Net Background  

  48   0          0          0      24896          0          0 L2X SSS manager 

  18   0          0          0      24896          0          0 IP Input 

 . . .

R1# show memory summary

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

Processor 126CB10 49,331,668 6454676 42876992 42642208 42490796

Related Commands

Command	Description
show memory	Displays statistics about memory, including memory-free pool statistics.
show processes	Displays information about the active processes.

show protocols

To display the configured protocols, use the show protocols command in EXEC mode.

This command shows the global and interface-specific status of any configured Level 3 protocol; for example, IP, DECnet, IPX, AppleTalk, and so on.

show protocols

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 protocols command:

Router# show protocols

Global values:

  Internet Protocol routing is enabled

  DECNET routing is enabled

  XNS routing is enabled

  Appletalk routing is enabled

  X.25 routing is enabled

Ethernet 0 is up, line protocol is up

  Internet address is 192.168.1.1, subnet mask is 255.255.255.0

  Decnet cost is 5

  XNS address is 2001.AA00.0400.06CC

  AppleTalk address is 4.129, zone Twilight

Serial 0 is up, line protocol is up

  Internet address is 192.168.7.49, subnet mask is 255.255.255.240

Ethernet 1 is up, line protocol is up

  Internet address is 192.168.2.1, subnet mask is 255.255.255.0

  Decnet cost is 5

  XNS address is 2002.AA00.0400.06CC

  AppleTalk address is 254.132, zone Twilight

Serial 1 is down, line protocol is down

  Internet address is 192.168.7.177, subnet mask is 255.255.255.240

  AppleTalk address is 999.1, zone Magnolia Estates

For more information on the parameters or protocols shown in this sample output, see the Cisco IOS Network Protocols Configuration Guide, Part 1, Network Protocols Configuration Guide, Part 2, and Network Protocols Configuration Guide, Part 3.

show region

To display valid memory regions (memory mapping) in use on your system, use the show region command in Privileged Exec mode.

show region [address hex-address]

Syntax Description

address hex-address

(Optional) If a hex address is specified, this command will search the region list for the specified address.

Defaults

All memory regions are displayed.

Command Modes

Privileged Exec

Command History

Release	Modification
12.1, 12.0(9)S	The show region command output was made available in the output of the show technical-support command.
12.2(15)ZN, 12.2(15)BZ, 12.1(14)E, 12.2(13)S, 12.2(13), 12.2(13)T, 12.0(23)S	The show region command was enabled as a separate command.
12.2(25)S, 12.3(14)T	The show region command output was updated to display information about free regions.

Usage Guidelines

This command can be useful for troubleshooting system bus errors. The system encounters a bus error when the processor tries to access a memory location that either does not exist (a software error) or does not respond properly (a hardware problem).

To use the show region command to troubleshoot a bus error, note the memory location address from the show version command, the show context command, or from the system error message that alerted you to the bus error. The show region command can then be used to determine if that address is a valid memory location.

For example, in the output of the show version command after a system restart caused by a bus error, you will see output similar to "System restarted by bus error at PC 0x30EE546, address 0xBB4C4." In this case, the memory location that the router tried to access is 0xBB4C4. If the address falls within one of the ranges in the show region output, it means that the router was accessing a valid memory address, but the hardware corresponding to that address is not responding properly. This indicates a hardware problem.

If the address reported by the bus error does not fall within the ranges displayed in the show region output, this means that the router was trying to access an address that is not valid. This indicates that it is a Cisco IOS software problem.

More detailed information is available on Cisco.com in Tech Note #7949, Troubleshooting Bus Error Crashes.

Examples

The following is sample output from the show region command:

Router# show region

Region Manager:

      Start         End     Size(b)  Class  Media  Name

 0x40000000  0x40001FFF        8192  Iomem  REG    qa

 0x40002000  0x401FFFFF     2088960  Iomem  R/W    memd

 0x48000000  0x48001FFF        8192  Iomem  REG    qa:writethru

 0x50002000  0x501FFFFF     2088960  Iomem  R/W    memd:(memd_bitswap)

 0x58002000  0x581FFFFF     2088960  Iomem  R/W    memd:(memd_uncached)

 0x60000000  0x6FFFFFFF   268435456  Local  R/W    main

 0x600109C8  0x611BEBE1    18539034  IText  R/O    main:text

 0x611C0000  0x61642C7F     4729984  IData  R/W    main:data

 0x61642C80  0x6186607F     2241536  IBss   R/W    main:bss

 0x61866080  0x6188607F      131072  Local  R/W    main:fastheap

 0x61886080  0x6FFFFFFF   242720640  Local  R/W    main:heap

 0x80000000  0x87FFFFFF   134217728  Local  R/W    main:(main_k0)

 0x88000000  0x88001FFF        8192  Iomem  REG    qa_k0

 0x88002000  0x881FFFFF     2088960  Iomem  R/W    memd:(memd_k0)

 0xA0000000  0xA7FFFFFF   134217728  Local  R/W    main:(main_k1)

 0xA8000000  0xA8001FFF        8192  Iomem  REG    qa_k1

 0xA8002000  0xA81FFFFF     2088960  Iomem  R/W    memd:(memd_k1)

Related Commands

Command	Description
show context	Displays information stored in NVRAM when an unexpected system reload (system exception) occurs.
show memory	Displays detailed memory statistics for the system.
show version	Shows hardware and software information for the system.

show registry

To show the function registry information, use the show registry command in EXEC mode.

show registry [registry-name [registry-number]] [brief | statistics]

Syntax Description

registry-name	(Optional) Name of the registry to examine.
registry-number	(Optional) Number of the registry to examine.
brief	(Optional) Displays limited functions and services information.
statistics	(Optional) Displays function registry statistics.

Command Modes

EXEC

Command History

Release	Modification
11.1	This command was introduced.

Examples

The following is sample output from the show registry command using the brief keyword:

Router> show registry atm 3/0/0 brief

Registry objects: 1799  bytes: 213412

--

Registry 23: ATM Registry

  Service 23/0:

  Service 23/1:

  Service 23/2:

  Service 23/3:

  Service 23/4:

  Service 23/5:

  Service 23/6:

  Service 23/7:

  Service 23/8:

  Service 23/9:

  Service 23/10:

  Service 23/11:

  Service 23/12:

  Service 23/13:

  Service 23/14:

--

RegistrY 25: ATM routing Registry

  Service 25/0:

show reload

To display the reload status on the router, use the show reload command in EXEC mode.

show reload

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

You can use the show reload command to display a pending software reload. To cancel the reload, use the reload cancel privileged EXEC command.

Examples

The following sample output from the show reload command shows that a reload is schedule for 12:00 a.m. (midnight) on Saturday, April 20:

Router# show reload

Reload scheduled for 00:00:00 PDT Sat April 20 (in 12 hours and 12 minutes)

Router#

Related Commands

Command	Description
reload	Reloads the operating system.

show resource all

To display the details of a resource owner, use the show resource all command in user EXEC or privileged EXEC mode.

show resource all [brief | detailed]

Syntax Description

all	Displays all the resource details.
brief	(Optional) Displays the brief details of the ROs.
detail	(Optional) Displays all the details of the ROs.

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 resource all command:

Router# show resource all

Resource Owner: cpu

Resource User Type: iosprocess

Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

  Resource User: Scheduler(ID: 0x1000002)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

  Resource User: Dead(ID: 0x1000003)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

  Resource User: Interrupt(ID: 0x1000004)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

  Resource User: Memory RO RU(ID: 0x1000005)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

  Resource User: Chunk Manager(ID: 0x1000006)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           0        13          0  0.00%  0.00%  0.00% Chunk Manager   

  Resource User: Load Meter(ID: 0x1000007)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223        2872     36029         79  0.00%  0.00%  0.00% Load Meter      

  Resource User: Check heaps(ID: 0x1000009)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225      352744     33446      10546  0.00%  0.20%  0.17% Check heaps     

  Resource User: Pool Manager(ID: 0x100000A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777226           0         1          0  0.00%  0.00%  0.00% Pool Manager    

  Resource User: Buffer RO RU(ID: 0x100000B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777227           0         0          0  0.00%  0.00%  0.00% Buffer RO RU    

  Resource User: Timers(ID: 0x100000C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777228           0         2          0  0.00%  0.00%  0.00% Timers          

  Resource User: Serial Background(ID: 0x100000D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777229           0         2          0  0.00%  0.00%  0.00% Serial Backgroun

  Resource User: AAA_SERVER_DEADTIME(ID: 0x100000E)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777230           0         1          0  0.00%  0.00%  0.00% AAA_SERVER_DEADT

  Resource User: AAA high-capacity counters(ID: 0x100000F)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777231           0         2          0  0.00%  0.00%  0.00% AAA high-capacit

  Resource User: Policy Manager(ID: 0x1000010)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777232           0         1          0  0.00%  0.00%  0.00% Policy Manager  

  Resource User: Crash writer(ID: 0x1000011)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777233           0         1          0  0.00%  0.00%  0.00% Crash writer    

  Resource User: RO Notify Timers(ID: 0x1000012)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777234           0         1          0  0.00%  0.00%  0.00% RO Notify Timers

  Resource User: RMI RM Notify Watched Policy(ID: 0x1000013)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777235           0         1          0  0.00%  0.00%  0.00% RMI RM Notify Wa

  Resource User: EnvMon(ID: 0x1000014)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777236       11164     92859        120  0.00%  0.00%  0.00% EnvMon          

  Resource User: IPC Dynamic Cache(ID: 0x1000015)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777237           0      3004          0  0.00%  0.00%  0.00% IPC Dynamic Cach

  Resource User: IPC Periodic Timer(ID: 0x1000017)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777239           0    180082          0  0.00%  0.00%  0.00% IPC Periodic Tim

  Resource User: IPC Managed Timer(ID: 0x1000018)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777240         572     79749          7  0.00%  0.00%  0.00% IPC Managed Time

  Resource User: IPC Deferred Port Closure(ID: 0x1000019)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777241           4    180088          0  0.00%  0.00%  0.00% IPC Deferred Por

  Resource User: IPC Seat Manager(ID: 0x100001A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777242       97560   1408799         69  0.23%  0.02%  0.00% IPC Seat Manager

  Resource User: IPC Session Service(ID: 0x100001B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777243           0         1          0  0.00%  0.00%  0.00% IPC Session Serv

  Resource User: ARP Input(ID: 0x100001C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777244          20      3082          6  0.00%  0.00%  0.00% ARP Input       

  Resource User: EEM ED Syslog(ID: 0x100001D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

.

.

.

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Chunk Elements :

Allocated Size(b): 35152564 Count: 91901 Freed Size(b): 31793276 Count: 39159

Processor memory

Total Memory held : 46596832 bytes

pc = 0x403089D8, size =  10499724, count =    1

pc = 0x402996C8, size =   6737976, count = 8298

pc = 0x402F0C9C, size =   5821352, count =   10

pc = 0x40A25134, size =   4194324, count =    1

pc = 0x41D6D414, size =   1704144, count =   52

pc = 0x40451BE0, size =   1114180, count =   17

pc = 0x402D0DAC, size =    917600, count =    1

pc = 0x4043E5F4, size =    836076, count = 12291

pc = 0x404A276C, size =    617476, count =    1

pc = 0x41CDED1C, size =    569844, count =  125

pc = 0x4194C2D0, size =    524292, count =    1

pc = 0x405FD93C, size =    516100, count =    1

pc = 0x414D67AC, size =    473224, count =  199

pc = 0x41016294, size =    458756, count =    1

pc = 0x4046E618, size =    432096, count =    1

pc = 0x400A1134, size =    412420, count =    1

pc = 0x402ABB50, size =    317316, count =   93

pc = 0x41D53668, size =    262148, count =    1

pc = 0x4049BA04, size =    206640, count =   84

pc = 0x41E3FE30, size =    196620, count =    3

pc = 0x40B05214, size =    196612, count =    1

pc = 0x40494D94, size =    180180, count = 4095

pc = 0x402ABB6C, size =    144708, count =   93

pc = 0x41586A38, size =    144004, count =    1

pc = 0x4030B408, size =    140028, count =    7

pc = 0x415090EC, size =    131768, count =    4

pc = 0x41E37B94, size =    131088, count =    4

pc = 0x4195C348, size =    131076, count =    1

pc = 0x400A1194, size =    124420, count =    1

pc = 0x41503BC4, size =    122768, count =    1

pc = 0x404E888C, size =    114660, count = 4095

pc = 0x40494D50, size =    114660, count = 4095

pc = 0x404D99B0, size =    114660, count = 4095

pc = 0x4023F5B4, size =     98312, count =    2

pc = 0x41E45894, size =     97456, count =  626

pc = 0x41E2D4C4, size =     91584, count =   12

pc = 0x416D9768, size =     84004, count =    1

pc = 0x40452790, size =     84000, count = 3000

pc = 0x40322A74, size =     81948, count =    7

pc = 0x41D0FF4C, size =     81924, count =    1

pc = 0x40E9F7B0, size =     81364, count =    1

pc = 0x414FB1BC, size =     78740, count =    2

pc = 0x414D4A64, size =     72916, count =    2

pc = 0x40328770, size =     72144, count =   36

pc = 0x414FA938, size =     71592, count =    2

pc = 0x414EF938, size =     71096, count =    2

pc = 0x41947EEC, size =     65540, count =    1

pc = 0x41935B5C, size =     65540, count =    1

pc = 0x4193A348, size =     65540, count =    1

pc = 0x4193FF5C, size =     65540, count =    1

pc = 0x41D6E32C, size =     65540, count =    1

pc = 0x41DD534C, size =     65540, count =    1

pc = 0x414B5870, size =     65540, count =    1

pc = 0x4078521C, size =     65540, count =    1

.

.

.

I/O memory

Total Memory held : 9816224 bytes

pc = 0x4029983C, size =   9791584, count = 8290

pc = 0x403EC2A4, size =      8208, count =    1

pc = 0x403F8CD0, size =      8208, count =    1

pc = 0x403EC2E0, size =      4112, count =    1

pc = 0x403F8D0C, size =      4112, count =    1

Resource User: Scheduler(ID: 0x1000002)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 13052 bytes

pc = 0x4037BCC8, size =     12004, count =    1

pc = 0x40327110, size =      1048, count =   24

Resource User: Dead(ID: 0x1000003)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 447448 bytes

pc = 0x404A276C, size =    395636, count =    5

pc = 0x4043E5F4, size =     18676, count =  271

pc = 0x40494D94, size =      6888, count =   82

pc = 0x4044B9E4, size =      6672, count =    6

pc = 0x40C8BAB4, size =      5780, count =   34

pc = 0x404943DC, size =      2836, count =   82

pc = 0x40494D50, size =      2796, count =   82

pc = 0x4044DAF0, size =      2224, count =    2

pc = 0x40393168, size =      1772, count =    1

pc = 0x40FF2688, size =       728, count =    6

pc = 0x40CBC5A4, size =       400, count =    4

pc = 0x40455144, size =       320, count =   10

pc = 0x40C9A8D8, size =       288, count =    8

pc = 0x40CADE10, size =       260, count =    5

pc = 0x40B19484, size =       256, count =    2

pc = 0x4052BD2C, size =       208, count =    4

pc = 0x40CADE50, size =       188, count =    5

pc = 0x4044FBD8, size =       184, count =    1

pc = 0x40A9B2F0, size =       184, count =    1

pc = 0x40CBC45C, size =       160, count =    2

pc = 0x4038BF34, size =       144, count =    2

pc = 0x40529610, size =       136, count =    2

pc = 0x405CF034, size =       104, count =    1

pc = 0x414D67AC, size =       104, count =    1

pc = 0x4038BF68, size =        88, count =    2

pc = 0x4044F078, size =        84, count =    3

pc = 0x41555624, size =        84, count =    1

pc = 0x40685250, size =        76, count =    1

pc = 0x40481AD4, size =        68, count =    1

pc = 0x4044DB18, size =        56, count =    2

pc = 0x401B6960, size =        48, count =    1

Resource User: Interrupt(ID: 0x1000004)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 39652 Count: 1070

Processor memory

Total Memory held : 0 bytes

Resource User: Memory RO RU(ID: 0x1000005)

Chunk Elements :

Allocated Size(b): 12320 Count: 120 Freed Size(b): 10164 Count: 99

Processor memory

Total Memory held : 131080 bytes

pc = 0x40357C54, size =     65540, count =    1

pc = 0x40357D98, size =     65540, count =    1

Resource User: Chunk Manager(ID: 0x1000006)

Chunk Elements :

Allocated Size(b): 124 Count: 6 Freed Size(b): 48 Count: 3

Processor memory

Total Memory held : 9788 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x40332490, size =      3008, count =    2

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: Load Meter(ID: 0x1000007)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 44 Count: 1

Processor memory

Total Memory held : 3780 bytes

pc = 0x4037BCC8, size =      3004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: Check heaps(ID: 0x1000009)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 44 Count: 1

Processor memory

Total Memory held : 7236 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x41E2B0D0, size =       324, count =    1

pc = 0x403604BC, size =       140, count =    1

pc = 0x40351D2C, size =        76, count =    1

pc = 0x40351CF8, size =        56, count =    1

Resource User: Pool Manager(ID: 0x100000A)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: Buffer RO RU(ID: 0x100000B)

Chunk Elements :

Allocated Size(b): 4960 Count: 40 Freed Size(b): 4092 Count: 33

Processor memory

Total Memory held : 0 bytes

Resource User: Timers(ID: 0x100000C)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 44 Count: 1

.

.

.

Resource User: PF_Init Process(ID: 0x100004F)

Chunk Elements :

Allocated Size(b): 8104 Count: 126 Freed Size(b): 1400 Count: 29

Processor memory

Total Memory held : 31204 bytes

pc = 0x4027EF10, size =     21540, count =    5

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4044DAF0, size =      1112, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x4038BF68, size =       308, count =    7

pc = 0x4038BF34, size =       280, count =    7

pc = 0x403604BC, size =       280, count =    2

pc = 0x41E45ED0, size =       240, count =    5

pc = 0x401FB400, size =       236, count =    5

pc = 0x40529610, size =       136, count =    2

pc = 0x4047D560, size =       108, count =    2

pc = 0x4038C114, size =        88, count =    2

pc = 0x4044DB18, size =        72, count =    1

pc = 0x40211DCC, size =        56, count =    2

pc = 0x4038E038, size =        44, count =    1

pc = 0x40402C98, size =        32, count =    1

pc = 0x40455144, size =        32, count =    1

Resource User: PF_Split Sync Process(ID: 0x1000052)

Chunk Elements :

Allocated Size(b): 6092 Count: 87 Freed Size(b): 5644 Count: 81

Processor memory

Total Memory held : 10356 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4060364C, size =      1760, count =   10

pc = 0x41E45894, size =       960, count =    2

pc = 0x4060AE18, size =       856, count =   10

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: RPC pf-split-rp(ID: 0x1000053)

Chunk Elements :

Allocated Size(b): 1348 Count: 20 Freed Size(b): 1304 Count: 19

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: RPC idprom-MP(ID: 0x1000054)

Chunk Elements :

Allocated Size(b): 4708 Count: 68 Freed Size(b): 4664 Count: 67

Processor memory

Total Memory held : 16648 bytes

pc = 0x405023D4, size =      9732, count =   18

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

pc = 0x405D000C, size =       136, count =    1

Resource User: Net Input(ID: 0x1000055)

Chunk Elements :

Allocated Size(b): 88 Count: 2 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: Compute load avgs(ID: 0x1000056)

Chunk Elements :

Allocated Size(b): 11948724 Count: 215941 Freed Size(b): 11948724 Count: 215941

Processor memory

Total Memory held : 10720 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x404FC9C0, size =      3940, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: RTTYS Process(ID: 0x1000057)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: BACK CHECK(ID: 0x1000059)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: chkpt message handler(ID: 0x100005A)

Chunk Elements :

Allocated Size(b): 156 Count: 2 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x4037BCC8, size =      6004, count =    1

pc = 0x4035E160, size =       636, count =    1

pc = 0x403604BC, size =       140, count =    1

Resource User: cpf_process_msg_holdq(ID: 0x100005B)

Chunk Elements :

Allocated Size(b): 152 Count: 3 Freed Size(b): 0 Count: 0

.

.

.

Resource Owner: Buffer

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Getbufs  Retbufs  Holding  RU Name

1367     31237    4294937426 Init            

Resource User: Scheduler(ID: 0x1000002)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Scheduler       

Resource User: Dead(ID: 0x1000003)

Getbufs  Retbufs  Holding  RU Name

6        3        3        Dead            

Resource User: Interrupt(ID: 0x1000004)

Getbufs  Retbufs  Holding  RU Name

221580   221580   0        Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Chunk Manager   

Resource User: Load Meter(ID: 0x1000007)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Load Meter      

Resource User: Check heaps(ID: 0x1000009)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Check heaps     

Resource User: Pool Manager(ID: 0x100000A)

Getbufs  Retbufs  Holding  RU Name

5554     0        5554     Pool Manager    

Resource User: Buffer RO RU(ID: 0x100000B)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Buffer RO RU    

Resource User: Timers(ID: 0x100000C)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Timers          

Resource User: Serial Background(ID: 0x100000D)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Serial Backgroun

Resource User: AAA_SERVER_DEADTIME(ID: 0x100000E)

Getbufs  Retbufs  Holding  RU Name

0        0        0        AAA_SERVER_DEADT

Resource User: AAA high-capacity counters(ID: 0x100000F)

Getbufs  Retbufs  Holding  RU Name

0        0        0        AAA high-capacit

Resource User: Policy Manager(ID: 0x1000010)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Policy Manager  

Resource User: Crash writer(ID: 0x1000011)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Crash writer    

Resource User: RO Notify Timers(ID: 0x1000012)

Getbufs  Retbufs  Holding  RU Name

0        0        0        RO Notify Timers

Resource User: RMI RM Notify Watched Policy(ID: 0x1000013)

Getbufs  Retbufs  Holding  RU Name

0        0        0        RMI RM Notify Wa

.

.

.

Resource User: DHCPD Timer(ID: 0x100011B)

Getbufs  Retbufs  Holding  RU Name

0        0        0        DHCPD Timer     

Resource User: DHCPD Database(ID: 0x100011C)

Getbufs  Retbufs  Holding  RU Name

0        0        0        DHCPD Database  

Resource User: draco-oir-process:slot 2(ID: 0x100011E)

Getbufs  Retbufs  Holding  RU Name

0        0        0        draco-oir-proces

Resource User: SCP async: Draco-LC4(ID: 0x1000125)

Getbufs  Retbufs  Holding  RU Name

35849    243101   4294760044 SCP async: Draco

Resource User: IFCOM Msg Hdlr(ID: 0x1000127)

Getbufs  Retbufs  Holding  RU Name

2        2        0        IFCOM Msg Hdlr  

Resource User: IFCOM Msg Hdlr(ID: 0x1000128)

Getbufs  Retbufs  Holding  RU Name

28       28       0        IFCOM Msg Hdlr  

Resource User: Exec(ID: 0x100012C)

Getbufs  Retbufs  Holding  RU Name

912      912      0        Exec            

Resource Owner: test_mem

Resource User Type: test_process

Resource User Type: mem_rut

Resource Owner: test_cpu

Resource User Type: test_process

Resource User Type: cpu_rut

The following is a sample output from the show resource all brief command:

Router# show resource all brief

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

  Resource User: Scheduler(ID: 0x1000002)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

  Resource User: Dead(ID: 0x1000003)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

  Resource User: Interrupt(ID: 0x1000004)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

  Resource User: Memory RO RU(ID: 0x1000005)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

  Resource User: Chunk Manager(ID: 0x1000006)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           0        13          0  0.00%  0.00%  0.00% Chunk Manager   

  Resource User: Load Meter(ID: 0x1000007)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223        2872     36069         79  0.00%  0.00%  0.00% Load Meter      

  Resource User: Check heaps(ID: 0x1000009)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225      353092     33481      10546  0.00%  0.17%  0.17% Check heaps     

  Resource User: Pool Manager(ID: 0x100000A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777226           0         1          0  0.00%  0.00%  0.00% Pool Manager    

  Resource User: Buffer RO RU(ID: 0x100000B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777227           0         0          0  0.00%  0.00%  0.00% Buffer RO RU    

  Resource User: Timers(ID: 0x100000C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777228           0         2          0  0.00%  0.00%  0.00% Timers          

  Resource User: Serial Background(ID: 0x100000D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777229           0         2          0  0.00%  0.00%  0.00% Serial Backgroun

  Resource User: AAA_SERVER_DEADTIME(ID: 0x100000E)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777230           0         1          0  0.00%  0.00%  0.00% AAA_SERVER_DEADT

  Resource User: AAA high-capacity counters(ID: 0x100000F)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777231           0         2          0  0.00%  0.00%  0.00% AAA high-capacit

  Resource User: Policy Manager(ID: 0x1000010)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777232           0         1          0  0.00%  0.00%  0.00% Policy Manager  

  Resource User: Crash writer(ID: 0x1000011)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777233           0         1          0  0.00%  0.00%  0.00% Crash writer    

  Resource User: RO Notify Timers(ID: 0x1000012)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777234           0         1          0  0.00%  0.00%  0.00% RO Notify Timers

  Resource User: RMI RM Notify Watched Policy(ID: 0x1000013)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777235           0         1          0  0.00%  0.00%  0.00% RMI RM Notify Wa

  Resource User: EnvMon(ID: 0x1000014)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777236       11176     92958        120  0.00%  0.00%  0.00% EnvMon          

  Resource User: IPC Dynamic Cache(ID: 0x1000015)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777237           0      3007          0  0.00%  0.00%  0.00% IPC Dynamic Cach

  Resource User: IPC Periodic Timer(ID: 0x1000017)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777239           0    180279          0  0.00%  0.00%  0.00% IPC Periodic Tim

  Resource User: IPC Managed Timer(ID: 0x1000018)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777240         572     79833          7  0.00%  0.00%  0.00% IPC Managed Time

  Resource User: IPC Deferred Port Closure(ID: 0x1000019)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777241           4    180285          0  0.00%  0.00%  0.00% IPC Deferred Por

  Resource User: IPC Seat Manager(ID: 0x100001A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777242       97684   1410183         69  0.00%  0.03%  0.00% IPC Seat Manager

  Resource User: IPC Session Service(ID: 0x100001B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777243           0         1          0  0.00%  0.00%  0.00% IPC Session Serv

  Resource User: ARP Input(ID: 0x100001C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777244          20      3085          6  0.00%  0.00%  0.00% ARP Input       

  Resource User: EEM ED Syslog(ID: 0x100001D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777245           0        49          0  0.00%  0.00%  0.00% EEM ED Syslog   

  Resource User: DDR Timers(ID: 0x100001E)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777246           0         2          0  0.00%  0.00%  0.00% DDR Timers      

  Resource User: Dialer event(ID: 0x100001F)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777247           0         2          0  0.00%  0.00%  0.00% Dialer event    

  Resource User: Entity MIB API(ID: 0x1000020)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777248          28        16       1750  0.00%  0.00%  0.00% Entity MIB API  

  Resource User: Compute SRP rates(ID: 0x1000021)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777249           0     18037          0  0.00%  0.00%  0.00% Compute SRP rate

  Resource User: SERIAL A'detect(ID: 0x1000022)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777250           0         1          0  0.00%  0.00%  0.00% SERIAL A'detect 

  Resource User: GraphIt(ID: 0x1000023)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777251           0    180267          0  0.00%  0.00%  0.00% GraphIt         

  Resource User: rf proxy rp agent(ID: 0x1000024)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777252          40       416         96  0.00%  0.00%  0.00% rf proxy rp agen

  Resource User: HC Counter Timers(ID: 0x1000025)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777253          60     41360          1  0.00%  0.00%  0.00% HC Counter Timer

  Resource User: Snmp ICC Process(ID: 0x1000026)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777254           0         1          0  0.00%  0.00%  0.00% Snmp ICC Process

  Resource User: Cat6k SNMP(ID: 0x1000027)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777255          20        29        689  0.00%  0.00%  0.00% Cat6k SNMP      

  Resource User: Cat6k SNMP Trap handler(ID: 0x1000028)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777256           0         7          0  0.00%  0.00%  0.00% Cat6k SNMP Trap 

  Resource User: Critical Bkgnd(ID: 0x1000029)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777257           0         1          0  0.00%  0.00%  0.00% Critical Bkgnd  

  Resource User: Net Background(ID: 0x100002A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777258         112     44787          2  0.00%  0.00%  0.00% Net Background  

  Resource User: Logger(ID: 0x100002B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777259           0        50          0  0.00%  0.00%  0.00% Logger          

  Resource User: TTY Background(ID: 0x100002C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777260           0    180263          0  0.00%  0.00%  0.00% TTY Background  

  Resource User: Per-Second Jobs(ID: 0x100002D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777261          52    180549          0  0.00%  0.00%  0.00% Per-Second Jobs 

  Resource User: Per-minute Jobs(ID: 0x100002E)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

.

.

.

Resource User: Exec(ID: 0x100012C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777516        8964       965       9289  0.39%  0.66%  1.55% Exec            

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Processor memory

Allocated   Freed  Holding   Blocks

55233064  8636232 46596832    48832

I/O memory

Allocated   Freed  Holding   Blocks

 9816224        0  9816224     8294

  Resource User: Scheduler(ID: 0x1000002)

Processor memory

Allocated   Freed  Holding   Blocks

   13052        0    13052       25

  Resource User: Dead(ID: 0x1000003)

Processor memory

Allocated   Freed  Holding   Blocks

  687916   240468   447448      630

  Resource User: Interrupt(ID: 0x1000004)

Processor memory

Allocated   Freed  Holding   Blocks

       0        0        0        0

  Resource User: Memory RO RU(ID: 0x1000005)

Processor memory

Allocated   Freed  Holding   Blocks

  131080        0   131080        2

  Resource User: Chunk Manager(ID: 0x1000006)

Processor memory

Allocated   Freed  Holding   Blocks

   14300     4512     9788        5

  Resource User: Load Meter(ID: 0x1000007)

Processor memory

Allocated   Freed  Holding   Blocks

    3920      140     3780        3

  Resource User: Check heaps(ID: 0x1000009)

Processor memory

Allocated   Freed  Holding   Blocks

    7376      140     7236        6

  Resource User: Pool Manager(ID: 0x100000A)

Processor memory

Allocated   Freed  Holding   Blocks

    6780        0     6780        3

  Resource User: Buffer RO RU(ID: 0x100000B)

Processor memory

Allocated   Freed  Holding   Blocks

       0        0        0        0

  Resource User: Timers(ID: 0x100000C)

Processor memory

Allocated   Freed  Holding   Blocks

    6920      140     6780        3

  Resource User: Serial Background(ID: 0x100000D)

Processor memory

Allocated   Freed  Holding   Blocks

    6920      140     6780        3

.

.

.

Resource User: IFCOM Msg Hdlr(ID: 0x1000128)

Getbufs  Retbufs  Holding  RU Name

28       28       0        IFCOM Msg Hdlr  

  Resource User: Exec(ID: 0x100012C)

Getbufs  Retbufs  Holding  RU Name

1404     1404     0        Exec            

Resource Owner: test_mem

 Resource User Type: test_process

 Resource User Type: mem_rut

Resource Owner: test_cpu

 Resource User Type: test_process

 Resource User Type: cpu_rut

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

Router# show resource all detailed

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

  Resource User: Scheduler(ID: 0x1000002)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

  Resource User: Dead(ID: 0x1000003)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

  Resource User: Interrupt(ID: 0x1000004)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

  Resource User: Memory RO RU(ID: 0x1000005)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

  Resource User: Chunk Manager(ID: 0x1000006)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           0        13          0  0.00%  0.00%  0.00% Chunk Manager   

  Resource User: Load Meter(ID: 0x1000007)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223        2872     36075         79  0.00%  0.00%  0.00% Load Meter      

  Resource User: Check heaps(ID: 0x1000009)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225      353168     33486      10546  0.00%  0.10%  0.15% Check heaps     

  Resource User: Pool Manager(ID: 0x100000A)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777226           0         1          0  0.00%  0.00%  0.00% Pool Manager    

  Resource User: Buffer RO RU(ID: 0x100000B)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777227           0         0          0  0.00%  0.00%  0.00% Buffer RO RU    

  Resource User: Timers(ID: 0x100000C)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777228           0         2          0  0.00%  0.00%  0.00% Timers          

  Resource User: Serial Background(ID: 0x100000D)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777229           0         2          0  0.00%  0.00%  0.00% Serial Backgroun

  Resource User: AAA_SERVER_DEADTIME(ID: 0x100000E)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777230           0         1          0  0.00%  0.00%  0.00% AAA_SERVER_DEADT

  Resource User: AAA high-capacity counters(ID: 0x100000F)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777231           0         2          0  0.00%  0.00%  0.00% AAA high-capacit

  Resource User: Policy Manager(ID: 0x1000010)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777232           0         1          0  0.00%  0.00%  0.00% Policy Manager  

  Resource User: Crash writer(ID: 0x1000011)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777233           0         1          0  0.00%  0.00%  0.00% Crash writer    

  Resource User: RO Notify Timers(ID: 0x1000012)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777234           0         1          0  0.00%  0.00%  0.00% RO Notify Timers

  Resource User: RMI RM Notify Watched Policy(ID: 0x1000013)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777235           0         1          0  0.00%  0.00%  0.00% RMI RM Notify Wa

  Resource User: EnvMon(ID: 0x1000014)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777236       11176     92958        120  0.00%  0.00%  0.00% EnvMon          

  Resource User: IPC Dynamic Cache(ID: 0x1000015)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777237           0      3008          0  0.00%  0.00%  0.00% IPC Dynamic Cach

  Resource User: IPC Periodic Timer(ID: 0x1000017)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

.

.

.

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Chunk Elements :

Allocated Size(b): 35152564 Count: 91901 Freed Size(b): 31793276 Count: 39159

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

4393BAA0 0010499772 00000000 4433F15C 001 513DD000  *Init*

4433F15C 0000012852 4393BAA0 44342390 001 513DD000  *Init*

44342390 0000005052 4433F15C 4434374C 001 513DD000  List Headers

4434374C 0000000096 44342390 443437AC 001 513DD000  *Init*

443437AC 0000000096 4434374C 4434380C 001 513DD000  *Init*

4434380C 0000000096 443437AC 4434386C 001 513DD000  *Init*

4434386C 0000000096 4434380C 443438CC 001 513DD000  *Init*

443438CC 0000000096 4434386C 4434392C 001 513DD000  *Init*

4434392C 0000004356 443438CC 44344A30 001 513DD000  TTY data

44344A30 0000000564 4434392C 44344C64 001 513DD000  TTY Output Buf

44344C64 0000000096 44344A30 44344CC4 001 513DD000  *Init*

44344CC4 0000001552 44344C64 443452D4 001 513DD000  Watched messages

443452D4 0000010052 44344CC4 44347A18 001 513DD000  Watched Boolean

44347A18 0000001552 443452D4 44348028 001 513DD000  Watched Semaphore

44348028 0000000380 44347A18 443481A4 001 513DD000  Watched Message Queue

443481A4 0000003052 44348028 44348D90 001 513DD000  Read/Write Locks

44348D90 0000020052 443481A4 4434DBE4 001 513DD000  RMI-RO_RU Chunks

4434DBE4 0000000116 44348D90 4434DC58 001 513DD000  Resource Owner IDs

4434DC58 0000001552 4434DBE4 4434E268 001 513DD000  String-DB entries

4434E268 0000000532 4434DC58 4434E47C 001 513DD000  String-DB handles

4434E47C 0000000076 4434E268 4434E4C8 001 513DD000  NameDB String

4434E4C8 0000000116 4434E47C 4434E53C 001 513DD000  Resource User Type IDs

4434E53C 0000000184 4434E4C8 4434E5F4 001 513DD000  *Init*

4434E5F4 0000002100 4434E53C 4434EE28 001 513DD000  Resource Owner IDs

4434EE28 0000000076 4434E5F4 4434EE74 001 513DD000  NameDB String

4434EE74 0000000076 4434EE28 4434EEC0 001 513DD000  NameDB String

4434EEC0 0000065588 4434EE74 4435EEF4 001 513DD000  Buffer RU Notify Chunks

44360754 0000000076 44360698 443607A0 001 513DD000  *Init*

443607A0 0000002100 44360754 44360FD4 001 513DD000  Resource User Type IDs

44360FD4 0000004148 443607A0 44362008 001 513DD000  Resource User IDs

44362008 0000000076 44360FD4 44362054 001 513DD000  NameDB String

44362054 0000000076 44362008 443620A0 001 513DD000  NameDB String

443620A0 0000000096 44362054 44362100 001 513DD000  *Init*

443623AC 0000000076 44362100 443623F8 001 513DD000  NameDB String

443623F8 0000010052 443623AC 44364B3C 001 513DD000  List Elements

44364B3C 0000010052 443623F8 44367280 001 513DD000  List Elements

4436758C 0000001552 4436752C 44367B9C 001 513DD000  Reg Function iList

44367B9C 0000000164 4436758C 44367C40 001 513DD000  *Init*

44367C40 0000000076 44367B9C 44367C8C 001 513DD000  Parser Linkage

44367C8C 0000000076 44367C40 44367CD8 001 513DD000  Parser Linkage

44367CD8 0000000076 44367C8C 44367D24 001 513DD000  Parser Linkage

44367D70 0000000076 44367D24 44367DBC 001 513DD000  Parser Linkage

44367DBC 0000000076 44367D70 44367E08 001 513DD000  Cond Debug definition

44367E08 0000000076 44367DBC 44367E54 001 513DD000  Parser Linkage

44367E54 0000000076 44367E08 44367EA0 001 513DD000  Cond Debug definition

44367EA0 0000000076 44367E54 44367EEC 001 513DD000  Cond Debug definition

44367EEC 0000000076 44367EA0 44367F38 001 513DD000  Cond Debug definition

44367F38 0000000076 44367EEC 44367F84 001 513DD000  Cond Debug definition

44367F84 0000000384 44367F38 44368104 001 513DD000  *Init*

4436B5C8 0000000076 4436B57C 4436B614 001 513DD000  Init

4436B614 0000000076 4436B5C8 4436B660 001 513DD000  Init

4436B660 0000000076 4436B614 4436B6AC 001 513DD000  Init

4436BC04 0000000076 4436BBB8 4436BC50 001 513DD000  Init

4436BC50 0000003460 4436BC04 4436C9D4 001 513DD000  *Hardware IDB*

4436C9D4 0000000076 4436BC50 4436CA20 001 513DD000  Init

4436CA20 0000001080 4436C9D4 4436CE58 001 513DD000  Index Table Block

4436CE58 0000000076 4436CA20 4436CEA4 001 513DD000  Init

4436CEA4 0000000076 4436CE58 4436CEF0 001 513DD000  Init

4436CEF0 0000000308 4436CEA4 4436D024 001 513DD000  Init

4436D024 0000000076 4436CEF0 4436D070 001 513DD000  NameDB String

4436D070 0000000104 4436D024 4436D0D8 001 513DD000  NameDB String

4436D434 0000000096 4436D188 4436D494 001 513DD000  Init

4436D740 0000000096 4436D494 4436D7A0 001 513DD000  Init

4436D7A0 0000010052 4436D740 4436FEE4 001 513DD000  Packet Elements

4436FEE4 0000000372 4436D7A0 44370058 001 513DD000  Pool Info

44370058 0000000372 4436FEE4 443701CC 001 513DD000  Pool Info

443701CC 0000000372 44370058 44370340 001 513DD000  Pool Info

44370340 0000000860 443701CC 4437069C 001 513DD000  *Packet Header*

4437069C 0000000372 44370340 44370810 001 513DD000  Pool Info

44370810 0000000860 4437069C 44370B6C 001 513DD000  *Packet Header*

44370B6C 0000000860 44370810 44370EC8 001 513DD000  *Packet Header*

44370EC8 0000000860 44370B6C 44371224 001 513DD000  *Packet Header*

44371224 0000000860 44370EC8 44371580 001 513DD000  *Packet Header*

44371580 0000000860 44371224 443718DC 001 513DD000  *Packet Header*

443718DC 0000000860 44371580 44371C38 001 513DD000  *Packet Header*

44371C38 0000000860 443718DC 44371F94 001 513DD000  *Packet Header*

44371F94 0000000860 44371C38 443722F0 001 513DD000  *Packet Header*

443722F0 0000000860 44371F94 4437264C 001 513DD000  *Packet Header*

4437264C 0000000860 443722F0 443729A8 001 513DD000  *Packet Header*

443729A8 0000000860 4437264C 44372D04 001 513DD000  *Packet Header*

.

.

.

Resource User: Compute SRP rates(ID: 0x1000021)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

446D502C 0000006052 446D4D5C 446D67D0 001 513DD000  Init

446D67D0 0000000188 446D502C 446D688C 001 513DD000  Process Events

5055163C 0000000684 505512CC 505518E8 001 513DD000  Init

  Resource User: SERIAL A'detect(ID: 0x1000022)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 0 Count: 0

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

44722FCC 0000000684 4471DE58 44723278 001 513DD000  Init

50598A4C 0000006052 505989E8 5059A1F0 001 513DD000  Init

5059A1F0 0000000188 50598A4C 5059A2AC 001 513DD000  Process Events

  Resource User: GraphIt(ID: 0x1000023)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 44 Count: 1

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

447235B8 0000000684 4472356C 44723864 001 513DD000  Init

5059A8A8 0000006052 5059A350 5059C04C 001 513DD000  Init

5059C04C 0000000188 5059A8A8 5059C108 001 513DD000  Process Events

  Resource User: rf proxy rp agent(ID: 0x1000024)

Chunk Elements :

Allocated Size(b): 39056 Count: 504 Freed Size(b): 33756 Count: 452

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

446B752C 0000000144 446B74D4 446B75BC 001 513DD000  NameDB String

44728FC0 0000000684 44728F74 4472926C 001 513DD000  Init

44B19780 0000001160 44B1867C 44B19C08 001 513DD000  IPC Port

44B204A0 0000000148 44B2042C 44B20534 001 513DD000  IPC Name String

44B220E8 0000000096 44B2202C 44B22148 001 513DD000  rf proxy rp agent

44B22148 0000001160 44B220E8 44B225D0 001 513DD000  IPC Port

44B22938 0000000076 44B2287C 44B22984 001 513DD000  NameDB String

44B22984 0000000096 44B22938 44B229E4 001 513DD000  rf proxy rp agent

44B22D4C 0000000076 44B22C90 44B22D98 001 513DD000  NameDB String

44B22D98 0000000096 44B22D4C 44B22DF8 001 513DD000  rf proxy rp agent

44B23160 0000000076 44B230A4 44B231AC 001 513DD000  NameDB String

44B231AC 0000000096 44B23160 44B2320C 001 513DD000  rf proxy rp agent

44B2320C 0000000076 44B231AC 44B23258 001 513DD000  IPC Name String

50543ABC 0000000104 50543A00 50543B24 001 513DD000  IPC Name

5061CC34 0000000188 5059EC00 5061CCF0 001 513DD000  Process Events

5061CDB4 0000006052 5061CD68 5061E558 001 513DD000  Init

50A8780C 0000000132 50A877C0 50A87890 001 513DD000  IPC Name String

50AC8094 0000065588 50AC7C0C 50AD80C8 001 513DD000  EvtMgr active chunk

50AD986C 0000001160 50AD80C8 50AD9CF4 001 513DD000  IPC Port

  Resource User: HC Counter Timers(ID: 0x1000025)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

.

.

.

Resource User: NetFlow Agg Task(ID: 0x1000114)

Getbufs  Retbufs  Holding  RU Name

0        0        0        NetFlow Agg Task

  Resource User: CWAN OIR IPC Ready Process(ID: 0x1000115)

Getbufs  Retbufs  Holding  RU Name

0        0        0        CWAN OIR IPC Rea

  Resource User: PF Clock Process(ID: 0x1000116)

Getbufs  Retbufs  Holding  RU Name

0        0        0        PF Clock Process

  Resource User: CEF IPC Background(ID: 0x1000117)

Getbufs  Retbufs  Holding  RU Name

0        0        0        CEF IPC Backgrou

  Resource User: RTTYS Process(ID: 0x1000118)

Getbufs  Retbufs  Holding  RU Name

0        0        0        RTTYS Process   

  Resource User: DHCPD Timer(ID: 0x100011B)

Getbufs  Retbufs  Holding  RU Name

0        0        0        DHCPD Timer     

  Resource User: DHCPD Database(ID: 0x100011C)

Getbufs  Retbufs  Holding  RU Name

0        0        0        DHCPD Database  

  Resource User: draco-oir-process:slot 2(ID: 0x100011E)

Getbufs  Retbufs  Holding  RU Name

0        0        0        draco-oir-proces

  Resource User: SCP async: Draco-LC4(ID: 0x1000125)

Getbufs  Retbufs  Holding  RU Name

35908    243517   4294759687 SCP async: Draco

  Resource User: IFCOM Msg Hdlr(ID: 0x1000127)

Getbufs  Retbufs  Holding  RU Name

2        2        0        IFCOM Msg Hdlr  

  Resource User: IFCOM Msg Hdlr(ID: 0x1000128)

Getbufs  Retbufs  Holding  RU Name

28       28       0        IFCOM Msg Hdlr  

  Resource User: Exec(ID: 0x100012C)

Getbufs  Retbufs  Holding  RU Name

17552    17552    0        Exec            

Resource Owner: test_mem

 Resource User Type: test_process

 Resource User Type: mem_rut

Resource Owner: test_cpu

 Resource User Type: test_process

 Resource User Type: cpu_rut

Table 152 describes the significant fields shown in the display.

Table 152 show resource all Field Descriptions 

Field	Description
Runtime(ms)	The runtime of the process in milliseconds.
Invoked	The number of times an RU has been allowed to run.
uSecs	The amount of runtime per invocation in microseconds.
Allocated Size(b)	The number of bytes of memory that is allocated.
Freed Size(b)	The number of bytes of memory that is freed.
Count	The number of elements that are allocated or freed. For example, if two elements of 50 bytes each are allocated, then the allocated count is 2 and allocated size is 100.
pc	Displays the details of the memory that is held by a process. Each line of the output displays one or more blocks of memory. The pc is the allocator pc of a particular block of memory.
size	The total size of memory allocated to each block. The sum of the size of all blocks is equivalent to the total memory held by the process.
count	The count is the number of blocks of memory.
Getbufs	The number of buffers allocated by the RU.
Retbufs	The number of buffers freed by the RU.
Holding	The number of buffers the RU is holding currently.

Related Commands

Command	Description
buffer public	Enters the buffer owner configuration mode and sets thresholds for buffer usage.
cpu interrupt	Enters the CPU owner configuration mode and sets thresholds for interrupt level CPU utilization.
cpu process	Enters the CPU owner configuration mode and sets thresholds for processor level CPU utilization.
cpu total	Enters the CPU owner configuration mode and sets thresholds for total CPU utilization.
critical rising	Sets the critical level threshold values for the buffer, CPU, and memory ROs.
major rising	Sets the major level threshold values for the buffer, CPU, and memory ROs.
memory io	Enters the memory owner configuration mode and sets threshold values for I/O memory.
memory processor	Enters the memory owner configuration mode and sets threshold values for processor memory.
minor rising	Sets the minor level threshold values for the buffer, CPU, and memory ROs.
policy (ERM)	Configures an ERM resource policy.
resource policy	Enters ERM configuration mode.
show resource database	Displays the database details of ROs.
show resource owner	Displays the RO details.
show resource relationship	Displays the relationship between the RUs and the ROs.

show resource database

To display the details of a resource owner, use the show resource database command in user EXEC or privileged EXEC mode.

show resource database

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 resource database command:

Router# show resource database

List of all Resource Owners :

Owner: cpu                       Id:0x1

Owner's list of monitors is empty.

Owner: memory                    Id:0x2

Owner's list of monitors is empty.

Owner: Buffer                    Id:0x3

Owner's list of monitors is empty.

Owner: test_mem                  Id:0x4

Owner's list of monitors is empty.

Owner: test_cpu                  Id:0x5

Owner's list of monitors is empty.

Owner: test_RO0                  Id:0x7

Owner's list of monitors is empty.

Owner: test_RO1                  Id:0x8

Owner's list of monitors is empty.

Owner: test_RO2                  Id:0x9

Owner's list of monitors is empty.

Owner: test_RO3                  Id:0xA

Owner's list of monitors is empty.

Owner: test_RO4                  Id:0xB

Owner's list of monitors is empty.

Owner: test_RO5                  Id:0xC

Owner's list of monitors is empty.

.

.

.

List of all Resource Usertypes :

RUT: iosprocess                Id:0x1

RUT: test_process              Id:0x2

RUT: mem_rut                   Id:0x3

RUT: cpu_rut                   Id:0x4

RUT: test_RUT0                 Id:0x5

RUT: test_RUT1                 Id:0x6

RUT: test_RUT2                 Id:0x7

RUT: test_RUT3                 Id:0x8

RUT: test_RUT4                 Id:0x9

RUT: test_RUT5                 Id:0xA

.

.

.

List of all Resource User Groups :

List of all Resource Users :

usertype: iosprocess                Id:0x1

 user: Init                      Id:0x1000001, priority:0

 user: Scheduler                 Id:0x1000002, priority:0

 user: Dead                      Id:0x1000003, priority:0

 user: Interrupt                 Id:0x1000004, priority:0

 user: Memory RO RU              Id:0x1000005, priority:0

 user: Chunk Manager             Id:0x1000006, priority:1

 user: Load Meter                Id:0x1000007, priority:1

 user: Check heaps               Id:0x1000009, priority:4

 user: Pool Manager              Id:0x100000A, priority:1

 user: Buffer RO RU              Id:0x100000B, priority:0

 user: Timers                    Id:0x100000C, priority:3

 user: Serial Background         Id:0x100000D, priority:3

 user: ALARM_TRIGGER_SCAN        Id:0x100000E, priority:4

 user: AAA_SERVER_DEADTIME       Id:0x100000F, priority:4

 user: AAA high-capacity counter Id:0x1000010, priority:3

 user: Policy Manager            Id:0x1000011, priority:3

 user: Crash writer              Id:0x1000012, priority:3

 user: RO Notify Timers          Id:0x1000013, priority:3

 user: RMI RM Notify Watched Pol Id:0x1000014, priority:3

 user: EnvMon                    Id:0x1000015, priority:3

 user: OIR Handler               Id:0x1000016, priority:3

 user: IPC Dynamic Cache         Id:0x1000017, priority:3

 user: IPC Zone Manager          Id:0x1000018, priority:3

 user: IPC Periodic Timer        Id:0x1000019, priority:3

 user: IPC Managed Timer         Id:0x100001A, priority:3

 user: IPC Deferred Port Closure Id:0x100001B, priority:3

.

.

.

Resource Monitor: test_ROM0, ID: 0x1B

 Not Watching any Relations.

 Not Watching any Policies.

Resource Monitor: test_ROM1, ID: 0x1C

 Not Watching any Relations.

 Not Watching any Policies.

Resource Monitor: test_ROM2, ID: 0x1D

 Not Watching any Relations.

 Not Watching any Policies.

Related Commands

Command	Description
buffer public	Enters the buffer owner configuration mode and sets thresholds for buffer usage.
cpu interrupt	Enters the CPU owner configuration mode and sets thresholds for interrupt level CPU utilization.
cpu process	Enters the CPU owner configuration mode and sets thresholds for processor level CPU utilization.
cpu total	Enters the CPU owner configuration mode and sets thresholds for total CPU utilization.
critical rising	Sets the critical level threshold values for the buffer, CPU, and memory ROs.
major rising	Sets the major level threshold values for the buffer, CPU, and memory ROs.
memory io	Enters the memory owner configuration mode and sets threshold values for I/O memory.
memory processor	Enters the memory owner configuration mode and sets threshold values for processor memory.
minor rising	Sets the minor level threshold values for the buffer, CPU, and memory ROs.
policy (ERM)	Configures an ERM resource policy.
resource policy	Enters ERM configuration mode.
show resource all	Displays all the resource details.
show resource owner	Displays the RO details.
show resource relationship	Displays the relationship between the RUs and the ROs.

show resource owner

To display the details of a resource owner, use the show resource owner command in user EXEC or privileged EXEC mode.

show resource owner {resource-owner-name | all} user {resource-user-type-name | all} [brief [triggers] | detailed [triggers] | triggers]

Syntax Description

resource-owner-name	The name of the specified RO whose details are displayed.
all	Displays details of all the ROs.
user	Displays details of the specified resource user type.
resource-user-type-name	Specifies a single resource user type.
all	Displays details of all the resource user types.
brief	Displays brief details.
detailed	Displays complete details.
triggers	Displays the triggers.

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 resource owner command:

Router# show resource owner all user all 

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

Resource User: Scheduler(ID: 0x1000002)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource User: Dead(ID: 0x1000003)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource User: Interrupt(ID: 0x1000004)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           4         3       1333  0.00%  0.00%  0.00% Chunk Manager   

Resource User: Load Meter(ID: 0x1000007)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223           4       292         13  0.00%  0.00%  0.00% Load Meter      

Resource User: Check heaps(ID: 0x1000009)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225         376       192       1958  0.00%  0.02%  0.00% Check heaps     

Resource User: Pool Manager(ID: 0x100000A)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777226           0         1          0  0.00%  0.00%  0.00% Pool Manager    

Resource User: Buffer RO RU(ID: 0x100000B)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777227           0         0          0  0.00%  0.00%  0.00% Buffer RO RU    

Resource User: Timers(ID: 0x100000C)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777228           0         2          0  0.00%  0.00%  0.00% Timers          

Resource User: Serial Background(ID: 0x100000D)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

.

.

.

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Chunk Elements :

Allocated Size(b): 25967632 Count: 46612 Freed Size(b): 21487684 Count: 26053

Processor memory

Total Memory held : 15250376 bytes

pc = 0x6072D840, size =   4040536, count =    6

pc = 0x6034E040, size =   1937508, count =    2

pc = 0x6070DAF0, size =    560096, count =    1

pc = 0x606D7530, size =    556220, count =  685

pc = 0x613AFA74, size =    350972, count =   25

pc = 0x60ECA4F0, size =    280004, count =    1

pc = 0x606DEC1C, size =    270600, count =  100

pc = 0x616EF268, size =    262148, count =    1

pc = 0x6085C318, size =    196620, count =    3

pc = 0x61479630, size =    144004, count =    1

pc = 0x613E1DB0, size =    131768, count =    4

.

.

.

I/O memory

Total Memory held : 4059856 bytes

pc = 0x606DEC30, size =   3408704, count =   52

pc = 0x606DEB94, size =    442464, count =    6

pc = 0x606D76A4, size =    179872, count =  146

pc = 0x600ED530, size =     16448, count =    4

pc = 0x600ED498, size =      8256, count =    4

pc = 0x6080D3F0, size =      4112, count =    1

  Resource User: Scheduler(ID: 0x1000002)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 12172 bytes

pc = 0x607B44F0, size =     12004, count =    1

pc = 0x607643B8, size =       168, count =    4

.

.

.

Resource User: Critical Bkgnd(ID: 0x1000026)

Chunk Elements :

Allocated Size(b): 44 Count: 1 Freed Size(b): 0 Count: 0

Processor memory

Total Memory held : 6780 bytes

pc = 0x607B44F0, size =      6004, count =    1

pc = 0x6079CB28, size =       636, count =    1

pc = 0x6079EE84, size =       140, count =    1

.

.

.

Resource Owner: Buffer

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Getbufs  Retbufs  Holding  RU Name

319      51       268      Init            

Resource User: Scheduler(ID: 0x1000002)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Scheduler       

Resource User: Dead(ID: 0x1000003)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Dead            

Resource User: Interrupt(ID: 0x1000004)

Getbufs  Retbufs  Holding  RU Name

1356     1356     0        Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

Getbufs  Retbufs  Holding  RU Name

0        0        0        Chunk Manager   

.

.

.

Resource Owner: test_mem

 Resource User Type: test_process

 Resource User Type: mem_rut

Resource Owner: test_cpu

 Resource User Type: test_process

 Resource User Type: cpu_rut

Resource User: test_RU0(ID: 0x4000001)

>>>RU: Blank

Resource User: test_RU1(ID: 0x4000002)

>>>RU: Blank

Resource User: test_RU2(ID: 0x4000003)

>>>RU: Blank

Resource User: test_RU3(ID: 0x4000004)

>>>RU: Blank

.

.

.

Resource User Type: test_RUT143

 Resource User Type: test_RUT144

 Resource User Type: test_RUT145

 Resource User Type: test_RUT146

 Resource User Type: test_RUT147

The following is sample output from the show resource owner all user all brief command:

Router# show resource owner all user all brief 

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

Resource User: Scheduler(ID: 0x1000002)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource User: Dead(ID: 0x1000003)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource User: Interrupt(ID: 0x1000004)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           4         3       1333  0.00%  0.00%  0.00% Chunk Manager   

Resource User: Load Meter(ID: 0x1000007)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223           4       322         12  0.00%  0.01%  0.00% Load Meter      

Resource User: Check heaps(ID: 0x1000009)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225         424       214       1981  0.00%  0.04%  0.00% Check heaps     

.

.

.

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Processor memory

Allocated   Freed  Holding   Blocks

21916780  6666404 15250376     8688

I/O memory

Allocated   Freed  Holding   Blocks

 4059856        0  4059856      213

Resource User: Scheduler(ID: 0x1000002)

Processor memory

Allocated   Freed  Holding   Blocks

   12172        0    12172        5

.

.

.

Resource Owner: test_mem

 Resource User Type: test_process

 Resource User Type: mem_rut

Resource Owner: test_cpu

 Resource User Type: test_process

 Resource User Type: cpu_rut

Resource User: test_RU0(ID: 0x4000001)

>>>RU: Blank

Resource User: test_RU1(ID: 0x4000002)

>>>RU: Blank

Resource User: test_RU2(ID: 0x4000003)

>>>RU: Blank

Resource User: test_RU3(ID: 0x4000004)

>>>RU: Blank

Resource User: test_RU4(ID: 0x4000005)

>>>RU: Blank

.

.

.

Resource Owner: test_RO0

Resource User Type: test_RUT0

Resource User Type: test_RUT1

Resource User Type: test_RUT2

Resource User Type: test_RUT3

Resource User Type: test_RUT4

Resource User Type: test_RUT5

Resource User Type: test_RUT6

Resource User Type: test_RUT7

Resource User Type: test_RUT8

Resource User Type: test_RUT9

Resource User Type: test_RUT10

Resource User Type: test_RUT11

Resource User Type: test_RUT12

Resource User Type: test_RUT13

Resource User Type: test_RUT14

Resource User Type: test_RUT15

Resource User Type: test_RUT16

The following is sample output from the show resource owner all user all brief triggers command:

Router# show resource owner all user all brief triggers 

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

Resource User: Scheduler(ID: 0x1000002)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource User: Dead(ID: 0x1000003)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource User: Interrupt(ID: 0x1000004)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           4         3       1333  0.00%  0.00%  0.00% Chunk Manager   

.

.

.

Resource Owner: test_mem

Resource User Type: test_process

Resource User Type: mem_rut

Resource Owner: test_cpu

Resource User Type: test_process

Resource User Type: cpu_rut

Resource User: test_RU0(ID: 0x4000001)

>>>RU: Blank

Resource User: test_RU1(ID: 0x4000002)

>>>RU: Blank

Resource User: test_RU2(ID: 0x4000003)

>>>RU: Blank

Resource User: test_RU3(ID: 0x4000004)

>>>RU: Blank

Resource User: test_RU4(ID: 0x4000005)

>>>RU: Blank

Resource User: test_RU5(ID: 0x4000006)

>>>RU: Blank

The following is sample output from the show resource owner all user detailed command:

Router# show resource owner all user all detailed 

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

Resource User: Scheduler(ID: 0x1000002)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource User: Dead(ID: 0x1000003)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource User: Interrupt(ID: 0x1000004)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777222           4         3       1333  0.00%  0.00%  0.00% Chunk Manager   

Resource User: Load Meter(ID: 0x1000007)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777223           4       353         11  0.00%  0.01%  0.00% Load Meter      

Resource User: Check heaps(ID: 0x1000009)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777225         456       232       1965  0.00%  0.01%  0.00% Check heaps     

Resource User: Pool Manager(ID: 0x100000A)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777226           0         1          0  0.00%  0.00%  0.00% Pool Manager    

Resource User: Buffer RO RU(ID: 0x100000B)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777227           0         0          0  0.00%  0.00%  0.00% Buffer RO RU    

Resource User: Timers(ID: 0x100000C)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777228           0         2          0  0.00%  0.00%  0.00% Timers          

.

.

.

Resource Owner: memory

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

Chunk Elements :

Allocated Size(b): 25967632 Count: 46612 Freed Size(b): 21487684 Count: 26053

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

63700E18 0000020052 636FDCD4 63705C6C 001 6412D2C0  Managed Chunk Queue Elements

63705C6C 0000012852 63700E18 63708EA0 001 6412D2C0  *Init*

63708EA0 0000010052 63705C6C 6370B5E4 001 6412D2C0  List Elements

6370B5E4 0000005052 63708EA0 6370C9A0 001 6412D2C0  List Headers

6370C9A0 0000009052 6370B5E4 6370ECFC 001 6412D2C0  Interrupt Stack

6370ECFC 0000000096 6370C9A0 6370ED5C 001 6412D2C0  *Init*

6370ED5C 0000000084 6370ECFC 6370EDB0 001 6412D2C0  *Init*

6370EDB0 0000000132 6370ED5C 6370EE34 001 6412D2C0  *Init*

6370EE34 0000000092 6370EDB0 6370EE90 001 6412D2C0  *Init*

6370EE90 0000000436 6370EE34 6370F044 001 6412D2C0  *Init*

6370F044 0000000076 6370EE90 6370F090 001 6412D2C0  *Init*

6370F090 0000000132 6370F044 6370F114 001 6412D2C0  *Init*

6370F114 0000000092 6370F090 6370F170 001 6412D2C0  *Init*

.

.

.

Resource User: Scheduler(ID: 0x1000002)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

63799F04 0000012052 63799EB8 6379CE18 001 6412D2C0  Scheduler Stack

643E9A38 0000000076 643D9A04 643E9A84 001 6412D2C0  *Sched*

644C47F0 0000000076 644C4790 644C483C 001 6412D2C0  *Sched*

645FF744 0000000096 645FF6E8 645FF7A4 001 6412D2C0  *Sched*

64904354 0000000112 649040D0 649043C4 001 6412D2C0  *Sched*

  Resource User: Dead(ID: 0x1000003)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

63F9D328 0000000096 63F984D4 63F9D388 001 6412D2C0  AAA MI SG NAME

  Resource User: Interrupt(ID: 0x1000004)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

The following is sample output from the show resource owner all user all detailed triggers command:

Router# show resource owner all user all detailed triggers

Resource Owner: cpu

 Resource User Type: iosprocess

  Resource User: Init(ID: 0x1000001)

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777217           0         0          0  0.00%  0.00%  0.00% Init            

Resource User: Scheduler(ID: 0x1000002)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource User: Dead(ID: 0x1000003)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource User: Interrupt(ID: 0x1000004)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource User: Memory RO RU(ID: 0x1000005)

RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource User: Chunk Manager(ID: 0x1000006)

.

.

.

Resource User: Scheduler(ID: 0x1000002)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

Processor memory

 Address      Bytes     Prev     Next Ref   Alloc PC  What

63799F04 0000012052 63799EB8 6379CE18 001 6412D2C0  Scheduler Stack

643E9A38 0000000076 643D9A04 643E9A84 001 6412D2C0  *Sched*

644C47F0 0000000076 644C4790 644C483C 001 6412D2C0  *Sched*

645FF744 0000000096 645FF6E8 645FF7A4 001 6412D2C0  *Sched*

64904354 0000000112 649040D0 649043C4 001 6412D2C0  *Sched*

  Resource User: Dead(ID: 0x1000003)

Chunk Elements :

Allocated Size(b): 0 Count: 0 Freed Size(b): 0 Count: 0

.

.

.

Resource User Type: test_RUT142

Resource User Type: test_RUT143

Resource User Type: test_RUT144

Resource User Type: test_RUT145

Resource User Type: test_RUT146

Resource User Type: test_RUT147

Resource User Type: test_RUT148

Resource User Type: test_RUT149

Table 152 describes the significant fields shown in the display.

Table 153 show resource owner Field Descriptions 

Field	Description
Runtime(ms)	The runtime of the process in milliseconds.
Invoked	The number of times an RU has been allowed to run.
uSecs	The amount of runtime per invocation in microseconds.
Allocated Size(b)	The number of bytes of memory that is allocated.
Freed Size(b)	The number of bytes of memory that is freed.
Count	The number of elements that are allocated or freed. For example, if two elements of 50 bytes each are allocated, then the allocated count is 2 and allocated size is 100.
pc	Displays the details of the memory that is held by a process. Each line of the output displays one or more blocks of memory. The pc is the allocator pc of a particular block of memory.
size	The total size of memory allocated to each block. The sum of the size of all blocks is equivalent to the total memory held by the process.
count	The count is the number of blocks of memory.
Getbufs	The number of buffers allocated by the RU.
Retbufs	The number of buffers freed by the RU.
Holding	The number of buffers the RU is holding currently.

Related Commands

Command	Description
buffer public	Enters the buffer owner configuration mode and sets thresholds for buffer usage.
cpu interrupt	Enters the CPU owner configuration mode and sets thresholds for interrupt level CPU utilization.
cpu process	Enters the CPU owner configuration mode and sets thresholds for processor level CPU utilization.
cpu total	Enters the CPU owner configuration mode and sets thresholds for total CPU utilization.
critical rising	Sets the critical level threshold values for the buffer, CPU, and memory ROs.
major rising	Sets the major level threshold values for the buffer, CPU, and memory ROs.
memory io	Enters the memory owner configuration mode and sets threshold values for I/O memory.
memory processor	Enters the memory owner configuration mode and sets threshold values for processor memory.
minor rising	Sets the minor level threshold values for the buffer, CPU, and memory ROs.
policy (ERM)	Configures an ERM resource policy.
resource policy	Enters ERM configuration mode.
show resource all	Displays all the resource details.
show resource database	Displays entire database of all resource entry relationships.
show resource relationship	Displays the relationship between the RUs and the ROs.

show resource relationship

To display the details of relationships between different resource owners, use the show resource relationship command in user EXEC or privileged EXEC mode.

show resource relationship user resource-user-type

Syntax Description

user	Identifies the RU.
resource-user-type	Type of the RU.

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 resource relationship command:

Router# show resource relationship

Resource User Type: iosprocess (ID: 0x1)

 -> Resource Owner: cpu (ID: 0x1)

 -> Resource Owner: memory (ID: 0x2)

 -> Resource Owner: Buffer (ID: 0x3)

 -> Resource User: Init (ID: 0x1000001)

 -> Resource User: Scheduler (ID: 0x1000002)

 -> Resource User: Dead (ID: 0x1000003)

 -> Resource User: Interrupt (ID: 0x1000004)

 -> Resource User: Memory RO RU (ID: 0x1000005)

 -> Resource User: Chunk Manager (ID: 0x1000006)

 -> Resource User: Load Meter (ID: 0x1000007)

 -> Resource User: Check heaps (ID: 0x1000009)

 -> Resource User: Pool Manager (ID: 0x100000A)

 -> Resource User: Buffer RO RU (ID: 0x100000B)

 -> Resource User: Timers (ID: 0x100000C)

 -> Resource User: Serial Background (ID: 0x100000D)

 -> Resource User: ALARM_TRIGGER_SCAN (ID: 0x100000E)

 -> Resource User: AAA_SERVER_DEADTIME (ID: 0x100000F)

 -> Resource User: AAA high-capacity counters (ID: 0x1000010)

 -> Resource User: Policy Manager (ID: 0x1000011)

 -> Resource User: Crash writer (ID: 0x1000012)

 -> Resource User: RO Notify Timers (ID: 0x1000013)

 -> Resource User: RMI RM Notify Watched Policy (ID: 0x1000014)

 -> Resource User: EnvMon (ID: 0x1000015)

 -> Resource User: OIR Handler (ID: 0x1000016)

 -> Resource User: IPC Dynamic Cache (ID: 0x1000017)

 -> Resource User: IPC Zone Manager (ID: 0x1000018)

 -> Resource User: IPC Periodic Timer (ID: 0x1000019)

 -> Resource User: IPC Managed Timer (ID: 0x100001A)

 -> Resource User: IPC Deferred Port Closure (ID: 0x100001B)

 -> Resource User: IPC Seat Manager (ID: 0x100001C)

 -> Resource User: IPC Session Service (ID: 0x100001D)

 -> Resource User: Compute SRP rates (ID: 0x100001E)

 -> Resource User: ARP Input (ID: 0x100001F)

 -> Resource User: DDR Timers (ID: 0x1000020)

 -> Resource User: Dialer event (ID: 0x1000021)

 -> Resource User: Entity MIB API (ID: 0x1000022)

 -> Resource User: SERIAL A'detect (ID: 0x1000023)

 -> Resource User: GraphIt (ID: 0x1000024)

 -> Resource User: HC Counter Timers (ID: 0x1000025)

.

.

.

Resource User Type: test_RUT141 (ID: 0x92)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT142 (ID: 0x93)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT143 (ID: 0x94)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT144 (ID: 0x95)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT145 (ID: 0x96)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT146 (ID: 0x97)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT147 (ID: 0x98)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT148 (ID: 0x99)

 -> Resource Owner: test_RO0 (ID: 0x7)

 Resource User Type: test_RUT149 (ID: 0x9A)

 -> Resource Owner: test_RO0 (ID: 0x7)

Related Commands

Command	Description
buffer public	Enters the buffer owner configuration mode and sets thresholds for buffer usage.
cpu interrupt	Enters the CPU owner configuration mode and sets thresholds for interrupt level CPU utilization.
cpu process	Enters the CPU owner configuration mode and sets thresholds for processor level CPU utilization.
cpu total	Enters the CPU owner configuration mode and sets thresholds for total CPU utilization.
critical rising	Sets the critical level threshold values for the buffer, CPU, and memory ROs.
major rising	Sets the major level threshold values for the buffer, CPU, and memory ROs.
memory io	Enters the memory owner configuration mode and sets threshold values for I/O memory.
memory processor	Enters the memory owner configuration mode and sets threshold values for processor memory.
minor rising	Sets the minor level threshold values for the buffer, CPU, and memory ROs.
policy (ERM)	Configures an ERM resource policy.
resource policy	Enters ERM configuration mode.
show resource all	Displays all the resource details.
show resource database	Displays entire database of all resource entry relationships.
show resource owner	Displays the RO details.

show resource user

To display the policy or RU template details of a resource user, use the show resource user command in user EXEC or privileged EXEC mode.

show resource user {all | resource-user-type} [brief | detailed]

Syntax Description

all	Displays the policy details of all the RUs.
resource-user-type	Specifies the policy details of a particular resource user type.
brief	(Optional) Displays a short description of the policy details.
detailed	(Optional) Displays all details of a policy.

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 resource user command:

Router# show resource user all

Resource User Type: iosprocess

Resource Grp: Init

Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

27197780  8950144 18247636     6552

I/O memory

Allocated   Freed  Holding   Blocks

 7296000     9504  7286496      196

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777224       14408       116     124206 100.40%  8.20%  1.70% Init            

Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

332      60       272      Init            

Resource User: Init

Resource User: Scheduler

Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

   77544        0    77544        2

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777218           0         0          0  0.00%  0.00%  0.00% Scheduler       

Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

0        0        0        Scheduler       

Resource User: Dead

Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

 1780540      260  1780280      125

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777219           0         0          0  0.00%  0.00%  0.00% Dead            

Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

9        8        1        Dead            

Resource User: Interrupt

Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

       0        0        0        0

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777220           0         0          0  0.00%  0.00%  0.00% Interrupt       

Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

14128    14128    0        Interrupt       

Resource User: Memory RO RU

Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

  132560     1480   131080        2

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777221           0         0          0  0.00%  0.00%  0.00% Memory RO RU    

Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

64       64       0        Memory RO RU    

.

.

.

Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777401        7124      4250       1676  0.00%  0.03%  0.01% Exec            

  Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

38       38       0        Exec            

 Resource User: BGP Router

  Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

   43380    26556    16824        8

  Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777404          12     19705          0  0.00%  0.00%  0.00% BGP Router      

  Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

0        0        0        BGP Router      

 Resource User: BGP I/O

  Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

    6892     6892        0        0

  Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777405           0         1          0  0.00%  0.00%  0.00% BGP I/O         

  Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

0        0        0        BGP I/O         

 Resource User: BGP Scanner

  Resource Owner: memory

Processor memory

Allocated   Freed  Holding   Blocks

    9828     9828        0        0

  Resource Owner: cpu

    RUID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min Res Usr 

16777406         660       659       1001  0.00%  0.00%  0.00% BGP Scanner     

  Resource Owner: Buffer

Getbufs  Retbufs  Holding  RU Name

0        0        0        BGP Scanner     

Resource User Type: test_process

Resource User Type: mem_rut

Resource User Type: cpu_rut

Table 154 describes the significant fields shown in the display.

Table 154 show resource user Field Descriptions 

Field	Description
Allocated Size(b)	The number of bytes of memory that is allocated.
Freed Size(b)	The number of bytes of memory that is freed.
Count	The number of elements that are allocated or freed. For example, if two elements of 50 bytes each are allocated, then the allocated count is 2 and allocated size is 100.
Runtime(ms)	The runtime of the process in milliseconds.
Invoked	The number of times an RU has been allowed to run.
uSecs	The amount of runtime per invocation in microseconds.
Getbufs	The number of buffers allocated by the RU.
Retbufs	The number of buffers freed by the RU.
Holding	The number of buffers the RU is holding currently.

Related Commands

Command	Description
buffer public	Enters the buffer owner configuration mode and sets thresholds for buffer usage.
cpu interrupt	Enters the CPU owner configuration mode and sets thresholds for interrupt level CPU utilization.
cpu process	Enters the CPU owner configuration mode and sets thresholds for processor level CPU utilization.
cpu total	Enters the CPU owner configuration mode and sets thresholds for total CPU utilization.
critical rising	Sets the critical level threshold values for the buffer, CPU, and memory ROs.
major rising	Sets the major level threshold values for the buffer, CPU, and memory ROs.
memory io	Enters the memory owner configuration mode and sets threshold values for I/O memory.
memory processor	Enters the memory owner configuration mode and sets threshold values for processor memory.
minor rising	Sets the minor level threshold values for the buffer, CPU, and memory ROs.
policy (ERM)	Configures an ERM resource policy.
resource policy	Enters ERM configuration mode.
show resource all	Displays all the resource details.
show resource database	Displays entire database of all resource entry relationships.
show resource owner	Displays the RO details.

show rmon

To display the current RMON agent status on the router, use the show rmon command in EXEC mode.

show rmon [alarms | capture | events | filter | history | hosts | matrix | statistics | task | topn]

Syntax Description

alarms	(Optional) Displays the RMON alarm table.
capture	(Optional) Displays the RMON buffer capture table. Available on Cisco 2500 series and Cisco AS5200 series only.
events	(Optional) Displays the RMON event table.
filter	(Optional) Displays the RMON filter table. Available on Cisco 2500 series and Cisco AS5200 series only.
history	(Optional) Displays the RMON history table. Available on Cisco 2500 series and Cisco AS5200 series only.
hosts	(Optional) Displays the RMON hosts table. Available on Cisco 2500 series and Cisco AS5200 series only.
matrix	(Optional) Displays the RMON matrix table. Available on Cisco 2500 series and Cisco AS5200 series only.
statistics	(Optional) Displays the RMON statistics table. Available on Cisco 2500 series and Cisco AS5200 series only.
task	(Optional) Displays general RMON statistics. This is the default.
topn	(Optional) Displays the RMON top-n hosts table. Available on Cisco 2500 series and Cisco AS5200 series only.

Defaults

If no option is specified, the task option is displayed.

Command Modes

EXEC

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

Refer to the specific show rmon command for an example and description of the fields.

For additional information, refer to the RMON MIB described in RFC 1757.

Examples

The following is sample output from the show rmon command. All counters are from the time the router was initialized.

Router# show rmon

145678 packets input (34562 promiscuous), 0 drops

145678 packets processed, 0 on queue, queue utilization 15/64

Table 155 describes the significant fields shown in the output.

Table 155 show rmon Field Descriptions 

Field	Description
x packets input	Number of packets received on RMON-enabled interfaces.
x promiscuous	Number of input packets that were seen by the router only because RMON placed the interface in promiscuous mode.
x drops	Number of input packets that could not be processed because the RMON queue overflowed.
x packets processed	Number of input packets actually processed by the RMON task.
x on queue	Number of input packets that are sitting on the RMON queue, waiting to be processed.
queue utilization x/y	y is the maximum size of the RMON queue; x is the largest number of packets that were ever on the queue at a particular time.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
rmon queuesize	Changes the size of the queue that holds packets for analysis by the RMON process.
show rmon alarms	Displays the contents of the router's RMON alarm table.
show rmon capture	Displays the contents of the router's RMON capture table.
show rmon events	Displays the contents of the router's RMON event table.
show rmon filter	Displays the contents of the router's RMON filter table.
show rmon history	Displays the contents of the router's RMON history table.
show rmon hosts	Displays the contents of the router's RMON hosts table.
show rmon matrix	Displays the contents of the router's RMON matrix table.
show rmon statistics	Displays the contents of the router's RMON statistics table.
show rmon topn	Displays the contents of the router's RMON p-N host table.

show rmon alarms

To display the contents of the RMON alarm table of the router, use the show rmon alarms command in EXEC mode.

show rmon alarms

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON alarms to display alarm information with the show rmon alarms command.

Examples

The following is sample output from the show rmon alarms command:

Router# show rmon alarms

Alarm 2 is active, owned by manager1

 Monitors ifEntry.1.1 every 30 seconds

 Taking delta samples, last value was 0

 Rising threshold is 15, assigned to event 12

 Falling threshold is 0, assigned to event 0

 On startup enable rising or falling alarm

Table 156 describes the significant fields shown in the display.

Table 156 show rmon alarms Field Descriptions 

Field	Description
Alarm 2 is active, owned by manager1	Unique index into the alarmTable, showing the alarm status is active, and the owner of this row, as defined in the alarmTable of RMON.
Monitors ifEntry.1.1	Object identifier of the particular variable to be sampled. Equivalent to alarmVariable in RMON.
every 30 seconds	Interval in seconds over which the data is sampled and compared with the rising and falling thresholds. Equivalent to alarmInterval in RMON.
Taking delta samples	Method of sampling the selected variable and calculating the value to be compared against the thresholds. Equivalent to alarmSampleType in RMON.
last value was	Value of the statistic during the last sampling period. Equivalent to alarmValue in RMON.
Rising threshold is	Threshold for the sampled statistic. Equivalent to alarmRisingThreshold in RMON.
assigned to event	Index of the eventEntry that is used when a rising threshold is crossed. Equivalent to alarmRisingEventIndex in RMON.
Falling threshold is	Threshold for the sampled statistic. Equivalent to alarmFallingThreshold in RMON.
assigned to event	Index of the eventEntry that is used when a falling threshold is crossed. Equivalent to alarmFallingEventIndex in RMON.
On startup enable rising or falling alarm	Alarm that may be sent when this entry is first set to valid. Equivalent to alarmStartupAlarm in RMON.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
show rmon	Displays the current RMON agent status on the router.

show rmon capture

To display the contents of the router's RMON capture table, use the show rmon capture command in EXEC mode.

show rmon capture

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon capture command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

Examples

The following is sample output from the show rmon capture command:

Router# show rmon capture

Buffer 4096 is active, owned by manager1

 Captured data is from channel 4096

 Slice size is 128, download size is 128

 Download offset is 0

 Full Status is spaceAvailable, full action is lockWhenFull

 Granted 65536 octets out of 65536 requested

 Buffer has been on since 00:01:16, and has captured 1 packets

  Current capture buffer entries:

   Packet 1 was captured 416 ms since buffer was turned on

   Its length is 326 octets and has a status type of 0

   Packet ID is 634, and contains the following data:

00 00 0c 03 12 ce 00 00 0c 08 9d 4e 08 00 45 00    

01 34 01 42 00 00 1d 11 e3 01 ab 45 30 15 ac 15    

31 06 05 98 00 a1 01 20 9f a8 00 00 00 00 00 00    

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    

00 00 00 00 

Table 157 describes the significant fields shown in the output.

Table 157 show rmon capture Field Descriptions 

Field	Description
Buffer 4096 is active	Equates to bufferControlIndex in the bufferControlTable of RMON. Uniquely identifies a valid (active) row in this table.
owned by manager1	Denotes the owner of this row. Equates to bufferControlOwner in the bufferControlTable of RMON.
Captured data is from channel	Equates to the bufferControlChannelIndex and identifies which RMON channel is the source of these packets.
Slice size is	Identifies the maximum number of octets of each packet that will be saved in this capture buffer. Equates to bufferControlCaptureSliceSize of RMON.
download size is	Identifies the maximum number of octets of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. Equates to bufferControlDownloadSliceSize in RMON.
Download offset is	Offset of the first octet of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. Equates to bufferControlDownloadOffset in RMON.
Full Status is spaceAvailable	Shows whether the buffer is full or has room to accept new packets. Equates to bufferControlFullStatus in RMON.
full action is lockWhenFull	Controls the action of the buffer when it reaches full status. Equates to bufferControlFullAction in RMON.
Granted 65536 octets	Actual maximum number of octets that can be saved in this capture buffer. Equates to bufferControlMaxOctetsGranted in RMON.
out of 65536 requested	Requested maximum number of octets to be saved in this capture buffer. Equates to bufferControlMaxOctetsRequested in RMON.
Buffer has been on since	Indicates how long the buffer has been available.
and has captured 1 packets	Number of packets captured since buffer was turned on. Equates to bufferControlCapturedPackets in RMON.
Current capture buffer entries:	Lists each packet captured.
Packet 1 was captured 416 ms since buffer was turned on Its length is 326 octets and has a status type of 0	Zero indicates the error status of this packet. Equates to captureBufferPacketStatus in RMON, where its value options are documented.
Packet ID is	Index that describes the order of packets received on a particular interface. Equates to captureBufferPacketID in RMON.
and contains the following data:	Data inside the packet, starting at the beginning of the packet.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon events

To display the contents of the router's RMON event table, use the show rmon events command in EXEC mode.

show rmon events

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON events to display alarm information with the show rmon events command.

Examples

The following is sample output from the show rmon events command:

Router# show rmon events

Event 12 is active, owned by manager1

 Description is interface-errors

 Event firing causes log and trap to community rmonTrap, last fired 00:00:00

Table 158 describes the significant fields shown in the display.

Table 158 show rmon events Field Descriptions 

Field	Description
Event 12 is active, owned by manager1	Unique index into the eventTable, showing the event status is active, and the owner of this row, as defined in the eventTable of RMON.
Description is interface-errors	Type of event, in this case an interface error.
Event firing causes log and trap	Type of notification that the router will make about this event. Equivalent to eventType in RMON.
community rmonTrap	If an SNMP trap is to be sent, it will be sent to the SNMP community specified by this octet string. Equivalent to eventCommunity in RMON.
last fired	Last time the event was generated.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon filter

To display the contents of the router's RMON filter table, use the show rmon filter command in EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon filter command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

Examples

The following is sample output from the show rmon filter command:

Router# show rmon filter

Filter 4096 is active, and owned by manager1

 Data offset is 12, with 

 Data of  08 00 00 00 00 00 00 00 00 00 00 00 00 00 ab 45 30 15 ac 15 31 06 

 Data Mask is ff ff 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff

 Data Not Mask is 0

 Pkt status is 0, status mask is 0, not mask is 0

 Associated channel 4096 is active, and owned by manager1

 Type of channel is acceptFailed, data control is off

 Generate event index 0

 Event status is eventFired, # of matches is 1482

 Turn on event index is 0, turn off event index is 0

 Description: 

Table 159 describes the significant fields shown in the display.

Table 159 show rmon filter Field Descriptions 

Field	Description
Filter x is active, and owned by y	Unique index of the filter, its current state, and the owner, as defined in the filterTable of RMON.
Data offset is	Offset from the beginning of each packet where a match of packet data will be attempted. Equivalent to filterPktDataOffset in RMON.
Data of	Data that is to be matched with the input packet. Equivalent to filterPktData in RMON.
Data Mask is	Mask that is applied to the match process. Equivalent to filterPktDataMask in RMON.
Data Not Mask is	Inversion mask that is applied to the match process. Equivalent to filterPktDataNotMask in RMON.
Pkt status is	Status that is to be matched with the input packet. Equivalent to filterPktStatus in RMON.
status mask is	Mask that is applied to the status match process. Equivalent to filterPktStatusMask in RMON.
not mask is	Inversion mask that is applied to the status match process. Equivalent to filterPktStatusNotMask in RMON.
Associated channel x is active, and owned by y	Unique index of the channel, its current state, and the owner, as defined in the channelTable of RMON.
Type of channel is {acceptMatched | acceptFailed}	This object controls the action of the filters associated with this channel. Equivalent to channelAcceptType of RMON.
data control is {off | on }	This object controls the flow of data through this channel. Equivalent to channelDataControl in RMON.
Generate event index 0	Value of this object identifies the event that is configured to be generated when the associated channelDataControl is on and a packet is matched. Equivalent to channelEventIndex in RMON.
Event status is eventFired	When the channel is configured to generate events when packets are matched, this message indicates the means of controlling the flow of those events. Equivalent to channelEventStatus in RMON.
# of matches is	Number of times this channel has matched a packet. Equivalent to channelMatches in RMON.
Turn on event index is	Value of this object identifies the event that is configured to turn the associated channelDataControl from off to on when the event is generated. Equivalent to channelTurnOnEventIndex in RMON.
Turn off event index is	Value of this object identifies the event that is configured to turn the associated channelDataControl from on to off when the event is generated. Equivalent to channelTurnOffEventIndex in RMON.
Description:	Comment describing this channel.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon history

To display the contents of the router's RMON history table, use the show rmon history command in EXEC mode.

show rmon history

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon history command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

Examples

The following is sample output from the show rmon history command:

Router# show rmon history

Entry 1 is active, and owned by manager1

 Monitors ifEntry.1.1 every 30 seconds

 Requested # of time intervals, ie buckets, is 5

 Granted # of time intervals, ie buckets, is 5

  Sample # 14 began measuring at 00:11:00

   Received 38346 octets, 216 packets,

   0 broadcast and 80 multicast packets,

   0 undersized and 0 oversized packets,

   0 fragments and 0 jabbers,

   0 CRC alignment errors and 0 collisions.

   # of dropped packet events is 0

   Network utilization is estimated at 10

Table 160 describes the significant fields shown in the display.

Table 160 show rmon history Field Descriptions 

Field	Description
Entry 1 is active, and owned by manager1	Unique index of the history entry, its current state, and the owner as defined in the historyControlTable of RMON.
Monitors ifEntry.1.1	This object identifies the source of the data for which historical data was collected and placed in a media-specific table. Equivalent to historyControlDataSource in RMON.
every 30 seconds	Interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControlEntry. Equivalent to historyControlInterval in RMON.
Requested # of time intervals, ie buckets, is	Requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry. Equivalent to historyControlBucketsRequested in RMON.
Granted # of time intervals, ie buckets, is	Actual number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry. Equivalent to historyControlBucketsGranted in RMON.
Sample # 14 began measuring at	Time at the start of the interval over which this sample was measured.
Received 38346 octets	Total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). Equivalent to etherHistoryOctets in RMON.
x packets	Number of packets (including bad packets) received during this sampling interval. Equivalent to etherHistoryPkts in RMON.
x broadcast	Number of good packets received during this sampling interval that were directed to the broadcast address. Equivalent to etherHistoryBroadcastPkts in RMON.
x multicast packets	Number of good packets received during this sampling interval that were directed to a multicast address. Equivalent to etherHistoryMulticastPkts in RMON.
x undersized	Number of packets received during this sampling interval that were fewer than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed. Equivalent to etherHistoryUndersizedPkts in RMON.
x oversized packets	Number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed. Equivalent to etherHistoryOversizePkts in RMON.
x fragments	Total number of packets received during this sampling interval that were fewer than 64 octets in length (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Equivalent to etherHistoryFragments in RMON.
x jabbers	Number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). Equivalent to etherHistoryJabbers in RMON.
x CRC alignment errors	Number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) from 64 to 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Equivalent to etherHistoryCRCAlignErrors in RMON.
x collisions	Best estimate of the total number of collisions on this Ethernet segment during this sampling interval. Equivalent to etherHistoryCollisions in RMON.
# of dropped packet events is	Total number of events in which packets were dropped by the operation because of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected. Equivalent to etherHistoryDropEvents in RMON.
Network utilization is estimated at	Best estimate of the mean physical-layer network usage on this interface during this sampling interval, in hundredths of a percent. Equivalent to etherHistoryUtilization in RMON.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon hosts

To display the contents of the router's RMON hosts table, use the show rmon hosts command in EXEC mode.

show rmon hosts

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon hosts command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

For additional information, refer to the RMON MIB described in RFC 1757.

Examples

The following is sample output from the show rmon hosts command:

Router# show rmon hosts

Host Control Entry 1 is active, and owned by manager1

 Monitors host ifEntry.1.1

 Table size is 51, last time an entry was deleted was 00:00:00

  Creation Order number is 1

   Physical address is 0000.0c02.5808

   Packets: rcvd 6963, transmitted 7041

   Octets: rcvd 784062, transmitted 858530

   # of packets transmitted: broadcast 28, multicast 48

   # of bad packets transmitted is 0

Table 161 describes the significant fields shown in the display.

Table 161 show rmon hosts Field Descriptions 

Field	Description
Host Control Entry 1 is active, and owned by manager1	Unique index of the host entry, its current state, and the owner as defined in the hostControlTable of RMON.
Monitors host ifEntry.1.1	This object identifies the source of the data for this instance of the host function. Equivalent to hostControlDataSource in RMON.
Table size is	Number of hostEntries in the hostTable and the hostTimeTable associated with this hostControlEntry. Equivalent to hostControlTableSize in RMON.
last time an entry was deleted was	Time when the last entry was deleted from the hostTable.
Creation Order number is	Index that defines the relative ordering of the creation time of hosts captured for a particular hostControlEntry. Equivalent to hostCreationOrder in RMON.
Physical address is	Physical address of this host. Equivalent to hostAddress in RMON.
Packets: rcvd	Number of good packets transmitted to this address. Equivalent to hostInPkts in RMON.
transmitted	Number of packets, including bad packets transmitted by this address. Equivalent to hostOutPkts in RMON.
Octets: rcvd	Number of octets transmitted to this address since it was added to the hostTable (excluding framing bits but including FCS octets), except for those octets in bad packets. Equivalent to hostInOctets in RMON.
transmitted	Number of octets transmitted by this address since it was added to the hostTable (excluding framing bits but including FCS octets), including those octets in bad packets. Equivalent to hostOutOctets in RMON.
# of packets transmitted:	Number of good packets transmitted by this address that were broadcast or multicast.
# of bad packets transmitted is	Number of bad packets transmitted by this address.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon matrix

To display the contents of the router's RMON matrix table, use the show rmon matrix command in EXEC mode.

show rmon matrix

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon matrix command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

For additional information, refer to the RMON MIB described in RFC 1757.

Examples

The following is sample output from the show rmon matrix command:

Router# show rmon matrix

Matrix 1 is active, and owned by manager1

 Monitors ifEntry.1.1

 Table size is 451, last time an entry was deleted was at 00:00:00

Table 162 describes the significant fields shown in the display.

Table 162 show rmon matrix Field Descriptions 

Field	Description
Matrix 1 is active, and owned by manager1	Unique index of the matrix entry, its current state, and the owner as defined in the matrixControlTable of RMON.
Monitors ifEntry.1.1	This object identifies the source of the data for this instance of the matrix function. Equivalent to matrixControlDataSource in RMON.
Table size is 451, last time an entry was deleted was at	Size of the matrix table and the time that the last entry was deleted.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon statistics

To display the contents of the router's RMON statistics table, use the show rmon statistics command in EXEC mode.

show rmon statistics

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon statistics command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

Examples

The following is sample output from the show rmon statistics command:

Router# show rmon statistics

Interface 1 is active, and owned by config

 Monitors ifEntry.1.1 which has

 Received 60739740 octets, 201157 packets,

 1721 broadcast and 9185 multicast packets,

 0 undersized and 0 oversized packets,

 0 fragments and 0 jabbers,

 0 CRC alignment errors and 32 collisions.

 # of dropped packet events (due to lack of resources): 511

 # of packets received of length (in octets):

  64: 92955, 65-127: 14204, 128-255: 1116,

  256-511: 4479, 512-1023: 85856, 1024-1518:2547

Table 163 describes the significant fields shown in the display.

Table 163 show rmon statistics Field Descriptions 

Field	Description
Interface 1 is active, and owned by config	Unique index of the statistics entry, its current state, and the owner as defined in the etherStatsTable of RMON.
Monitors ifEntry.1.1	This object identifies the source of the data that this etherStats entry is configured to analyze. Equivalent to etherStatsDataSource in RMON.
Received 60739740 octets	Total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). Equivalent to etherStatsOctets in RMON.
x packets	Number of packets (including bad packets) received. Equivalent to etherStatsPkts in RMON.
x broadcast	Number of good packets received that were directed to the broadcast address. Equivalent to etherStatsBroadcastPkts in RMON.
x multicast packets	Number of good packets received that were directed to a multicast address. Equivalent to etherStatsMulticastPkts in RMON.
x undersized	Number of packets received that were fewer than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed. Equivalent to etherStatsUndersizedPkts in RMON.
x oversized packets	Number of packets received that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed. Equivalent to etherStatsOversizePkts in RMON.
x fragments	Total number of packets received that were fewer than 64 octets in length (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Equivalent to etherStatsFragments in RMON.
x jabbers	Number of packets received that were longer than 1518 octets (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). Equivalent to etherStatsJabbers in RMON.
x CRC alignment errors	Number of packets received that had a length (excluding framing bits but including FCS octets) from 64 to 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Equivalent to etherStatsCRCAlignErrors in RMON.
x collisions	Best estimate of the total number of collisions on this Ethernet segment. Equivalent to etherHistoryCollisions in RMON.
# of dropped packet events (due to lack of resources):	Total number of events in which packets were dropped by the operation because of a lack of resources. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected. Equivalent to etherStatsDropEvents in RMON.
# of packets received of length (in octets):	Separates the received packets (good and bad) by packet size in the given ranges (64, 65 to 127,128 to 255, 256 to 511, 512 to 1023, 1024 to 1516).

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rmon topn

To display the contents of the router's RMON Top-N host table, use the show rmon topn command in EXEC mode.

show rmon topn

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

For additional information, refer to the RMON MIB described in RFC 1757.

You must have first enabled RMON on the interface, and configured RMON events to display alarm information with the show rmon events command.

This command is available on the Cisco 2500 series and Cisco AS5200 series only.

Examples

The following is sample output from the show rmon topn command:

Router# show rmon topn

Host Entry 1 of report 1 is active, owned by manager1

 The rate of change is based on hostTopNInPkts

 This report was last started at 00:00:00

 Time remaining in this report is 0 out of 0

 Hosts physical address is 00ad.beef.002b

 Requested # of hosts: 10, # of hosts granted: 10

Report # 1 of Top N hosts entry 1 is recording

Host 0000.0c02.5808 at a rate of 12

Table 164 describes the significant fields shown in the display.

Table 164 show rmon topn Field Descriptions 

Field	Description
Host Entry 1 of report 1 is active, owned by manager1	Unique index of the hostTopN entry, its current state, and the owner as defined in the hostTopNControlTable of RMON.
The rate of change is based on hostTopNInPkts	Variable for each host that the hostTopNRate variable is based on.
This report was last started at	Time the report was started.
Time remaining in this report is	Number of seconds left in the report currently being collected. Equivalent to hostTopNTimeRemaining in RMON.
out of	Number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval. Equivalent to hostTopNDuration in RMON.
Hosts physical address is	Host address.
Requested # of hosts:	Maximum number of hosts requested for the Top-N table. Equivalent to hostTopNRequestedSize in RMON.
# of hosts granted:	Maximum number of hosts granted for the Top-N table.Eqivalent to hostTopNGrantedSiz in RMON.
Report # 1 of Top N hosts entry 1 is recording	Report number and entry.
Host 0000.0c02.5808 at a rate of	Physical address of the host, and the amount of change in the selected variable during this sampling interval. Equivalent to hostTopNAddress and hostTopNRate in RMON.

Related Commands

Command	Description
rmon	Enables RMON on an Ethernet interface.
rmon alarm	Sets an alarm on any MIB object.
rmon event	Adds or removes an event in the RMON event table that is associated with an RMON event number.
show rmon	Displays the current RMON agent status on the router.

show rom-monitor

To show both the ReadOnly and the Upgrade ROMmon image versions, as well as which ROMmon image is running on the Cisco 7200 VXR or Cisco 7301 router, use the show rom-monitor command in privileged EXEC mode.

show rom-monitor

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(28)S	This command was introduced on the Cisco 7200 VXR router.
12.3(8)T	This command was integrated into Cisco IOS Release 12.3(8)T and supported on the Cisco 7200 VXR router and Cisco 7301 router.
12.3(9)	This command was integrated into Cisco IOS Release 12.3(9) and supported on the Cisco 7200 VXR router and Cisco 7301 router.

Usage Guidelines

Use the show rom-monitor command when you are in Cisco IOS. Use the showmon command when you are in ROMmon mode.

Examples

The following example, applicable to both the Cisco 7200 VXR and Cisco 7301 routers, uses the show rom-monitor command in Cisco IOS to display both ROMmon images and to verify that the Upgrade ROMmon image is running:

Router> show rom-monitor

ReadOnly ROMMON version:

System Bootstrap, Version 12.2(20031011:151758)

Copyright (c) 2004 by Cisco Systems, Inc.

Upgrade ROMMON version:

System Bootstrap, Version 12.2(20031011:151758)

Copyright (c) 2004 by Cisco Systems, Inc.

Currently running ROMMON from Upgrade region

ROMMON from Upgrade region is selected for next boot

Related Commands

Command	Description
showmon	Shows both the ReadOnly and the Upgrade ROMmon image versions when you are in ROMmon mode, as well as which ROMmon image is running.

show rtr application

---

Note Effective with Cisco IOS Release 12.3(14)T, the show rtr application command is replaced by the show ip sla monitor application command. See the show ip sla monitor application command for more information.

---

To display global information about Cisco IOS IP Service Level Agreements (IP SLAs), use the show rtr application command in EXEC mode.

show rtr application [tabular | full]

Syntax Description

tabular	(Optional) Displays information in a column format reducing the number of screens required to display the information.
full	(Optional) Displays all information using identifiers next to each displayed value. This is the default.

Defaults

Full format

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.3(14)T	This command was replaced by the show ip sla monitor application command.

Usage Guidelines

Use the show rtr application command to display information such as supported operation types and supported protocols.

Examples

The following is sample output from the show rtr application command in full format:

Router# show rtr application 

        SA Agent 

Version: 2.2.0 Round Trip Time MIB

Time of last change in whole RTR: *17:21:30.819 UTC Tue Mar 19 2002

Estimated system max number of entries: 4699

Number of Entries configured:5

    Number of active Entries:5

   Number of pending Entries:0

  Number of inactive Entries:0

         Supported Operation Types

Type of Operation to Perform:  echo

Type of Operation to Perform:  pathEcho

Type of Operation to Perform:  udpEcho

Type of Operation to Perform:  tcpConnect

Type of Operation to Perform:  http

Type of Operation to Perform:  dns

Type of Operation to Perform:  jitter

Type of Operation to Perform:  dlsw

Type of Operation to Perform:  dhcp

Type of Operation to Perform:  ftp

        Supported Protocols

Protocol Type: ipIcmpEcho

Protocol Type: ipUdpEchoAppl

Protocol Type: snaRUEcho

Protocol Type: snaLU0EchoAppl

Protocol Type: snaLU2EchoAppl

Protocol Type: ipTcpConn

Protocol Type: httpAppl

Protocol Type: dnsAppl

Protocol Type: jitterAppl

Protocol Type: dlsw

Protocol Type: dhcp

Protocol Type: ftpAppl

Number of configurable probe is 490

Related Commands

Command	Description
show rtr configuration	Displays configuration values including all defaults for all IP SLAs operations or the specified operation.

show rtr authentication

---

Note Effective with Cisco IOS Release 12.3(14)T, the show rtr authentication command is replaced by the show ip sla monitor authentication command. See the show ip sla monitor authentication command for more information.

---

To display Cisco IOS IP Service Level Agreements (IP SLAs) authentication information, use the show rtr authentication command in EXEC mode.

show rtr authentication

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
12.0(3)T	This command was introduced.
12.3(14)T	This command was replaced by the show ip sla monitor authentication command.

Usage Guidelines

Use the show rtr authentication command to display information such as supported operation types and supported protocols.

Examples

The following is sample output from the show rtr authentication command:

Router# show rtr authentication 

RTR control message uses MD5 authentication, key chain name is: rtr

Related Commands

Command	Description
show rtr configuration	Displays configuration values for IP SLAs operations.

show rtr collection-statistics

---

Note Effective with Cisco IOS Release 12.3(14)T, the show rtr collection-statistics command is replaced by the show ip sla monitor collection-statistics command. See the show ip sla monitor collection-statistics command for more information.

---

To display statistical errors for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or a specified operation, use the show rtr collection-statistics command in EXEC mode.

show rtr collection-statistics [operation-number]

Syntax Description

operation-number

(Optional) Number of the IP SLAs operation to display.

Defaults

Shows statistics for the past two hours.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.0(5)T	The output for this command was expanded to show information for Jitter operations.
12.1	The tabular and full keywords were removed.
12.1(1)T	The output for this command was expanded to show information for the FTP operation type and for One Way Delay Jitter operations.
12.2(8)T, 12.2(8)S	Output for "NumOfJitterSamples" was added (CSCdv30022).
12.2(11)T	The SAA Engine II was implemented. The maximum number of operations was increased from 500 to 2000.
12.3(4)T	Output (MOS and ICPIF scores) for the Jitter (codec) operation type was added.
12.3(7)T	Decimal granularity for MOS scores was added.
12.3(14)T	This command was replaced by the show ip sla monitor collection-statistics command.

Usage Guidelines

Use the show rtr collection-statistics command to display information such as the number of failed operations and the failure reason. You can also use the show rtr distribution-statistics and show rtr totals-statistics commands to display additional statistical information.

This command shows information collected over the past two hours, unless you specify a different amount of time using the hours-of-statistics-kept command.

For One Way Delay Jitter operations, the clocks on each device must be synchronized using NTP (or GPS systems). If the clocks are not synchronized, one way measurements are discarded. (If the sum of the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the round trip time, the one way measurement values are assumed to be faulty, and are discarded.)

---

Note This command does not support the IP SLAs ICMP path jitter operation.

---

Examples

The following shows sample output from the show rtr collection-statistics command in full format.

Router# show rtr collection-statistics 1 

        Collected Statistics

Entry Number: 1

Start Time Index: *17:15:41.000 UTC Thu May 16 1996

Path Index: 1

Hop in Path Index: 1

Number of Failed Operations due to a Disconnect: 0

Number of Failed Operations due to a Timeout: 0

Number of Failed Operations due to a Busy: 0

Number of Failed Operations due to a No Connection: 0

Number of Failed Operations due to an Internal Error: 0

Number of Failed Operations due to a Sequence Error: 0

Number of Failed Operations due to a Verify Error: 0

Target Address: 172.16.1.176

Output for HTTP Operations

The following example shows output from the show rtr collection-statistics command when the specified operation is an HTTP operation:

Router# show rtr collection-statistics 2

        Collected Statistics

Entry Number:2

HTTP URL:http://172.20.150.200

Start Time:*00:01:16.000 UTC Mon Nov 1 2003

             Comps:1              RTTMin:343       

             OvrTh:0              RTTMax:343       

        DNSTimeOut:0              RTTSum:343       

        TCPTimeOut:0             RTTSum2:117649  

        TraTimeOut:0              DNSRTT:0         

          DNSError:0           TCPConRTT:13        

         HTTPError:0            TransRTT:330       

          IntError:0            MesgSize:1771      

            Busies:0         

Output for Jitter Operations

The following is sample output from the show rtr collection-statistics command, where operation 2 is a Jitter operation that includes One Way statistcis:

Router# show rtr collection-statistics

Collected Statistics

Entry Number: 2

Target Address: 5.0.0.1, Port Number:99

Start Time: 11:12:03.000 UTC Thu Jul 1 1999

RTT Values:

NumOfRTT: 600  RTTSum: 3789  RTTSum2: 138665

Packet Loss Values:

PacketLossSD: 0  PacketLossDS: 0

PacketOutOfSequence: 0  PacketMIA: 0  PacketLateArrival: 0

InternalError: 0  Busies: 0

Jitter Values:

MinOfPositivesSD: 1   MaxOfPositivesSD: 2

NumOfPositivesSD: 26  SumOfPositivesSD: 31   Sum2PositivesSD: 41

MinOfNegativesSD: 1   MaxOfNegativesSD: 4

NumOfNegativesSD: 56  SumOfNegativesSD: 73   Sum2NegativesSD: 133

MinOfPositivesDS: 1   MaxOfPositivesDS: 338

NumOfPositivesDS: 58  SumOfPositivesDS: 409  Sum2PositivesDS: 114347

MinOfNegativesDS: 1   MaxOfNegativesDS: 338

NumOfNegativesDS: 48  SumOfNegativesDS: 396  Sum2NegativesDS: 114332

One Way Values:

NumOfOW: 440

OWMinSD: 2  OWMaxSD: 6    OWSumSD: 1273  OWSum2SD: 4021

OWMinDS: 2  OWMaxDS: 341  OWSumDS: 1643  OWSum2DS: 120295

The values shown indicate the aggregated values for the current hour. RTT stands for Round-Trip-Time. SD stands for Source-to-Destination. DS stands for Destination-to-Source. OW stands for One Way. Table 165 describes the significant fields shown in this output.

Output for Jitter (codec) Operations

The following is sample output from the show rtr collection-statistics command, where operation 10 is a Jitter (codec) operation:

Router# show rtr collection-statistics 10

Entry number: 10

Start Time Index: 13:18:49.904 PST Mon Jun 24 2002

Number of successful operations: 2

Number of operations over threshold: 0

Number of failed operations due to a Disconnect: 0

Number of failed operations due to a Timeout: 0

Number of failed operations due to a Busy: 0

Number of failed operations due to a No Connection: 0

Number of failed operations due to an Internal Error: 0

Number of failed operations due to a Sequence Error: 0

Number of failed operations due to a Verify Error: 0

Voice Scores:

MinOfICPIF: 0   MaxOfICPIF: 0   MinOfMOS: 0     MaxOfMOS: 0

RTT Values:

NumOfRTT: 122   RTTAvg: 2       RTTMin: 2       RTTMax: 3

RTTSum: 247     RTTSum2: 503

Packet Loss Values:

PacketLossSD: 0 PacketLossDS: 0

PacketOutOfSequence: 0  PacketMIA: 0    PacketLateArrival: 0

InternalError: 0        Busies: 0       PacketSkipped: 78  <<<<<===========

Jitter Values:

MinOfPositivesSD: 1     MaxOfPositivesSD: 1

NumOfPositivesSD: 9     SumOfPositivesSD: 9     Sum2PositivesSD: 9

MinOfNegativesSD: 1     MaxOfNegativesSD: 1

NumOfNegativesSD: 8     SumOfNegativesSD: 8     Sum2NegativesSD: 8

MinOfPositivesDS: 1     MaxOfPositivesDS: 1

NumOfPositivesDS: 6     SumOfPositivesDS: 6     Sum2PositivesDS: 6

MinOfNegativesDS: 1     MaxOfNegativesDS: 1

NumOfNegativesDS: 7     SumOfNegativesDS: 7     Sum2NegativesDS: 7

Interarrival jitterout: 0       Interarrival jitterin: 0

One Way Values:

NumOfOW: 0

OWMinSD: 0      OWMaxSD: 0      OWSumSD: 0      OWSum2SD: 0

OWMinDS: 0      OWMaxDS: 0      OWSumDS: 0      OWSum2DS: 0

Table 165 show rtr collection-statistics Field Descriptions 

Field	Description
Voice Scores:	Indicates that Voice over IP statistics appear on the following lines. Voice score data is computed when the operation type is configured as type jitter (codec).
ICPIF	The Calculated Planning Impairment Factor (ICPIF) value for the operation. The ICPIF value is computed by IP SLAs using the formula Icpif = Io + Iq + Idte + Idd + Ie - A, where •the values for Io, Iq, and Idte are set to zero, •the value Idd is computed based on the measured one way delay, •the value Ie is computed based on the measured packet loss, •and the value of A is specified by the user. ICPIF values are expressed in a typical range of 5 (very low impairment) to 55 (very high impairment). ICPIF values numerically less than 20 are generally considered "adequate." Note This value is intended only for relative comparisons, and may not match ICPIF values generated using alternate methods.
MinOfICPIF:	The lowest (minimum) ICPIF value computed for the collected statistics.
MaxOfICPIF:	The highest (maximum) ICPIF value computed for the collected statistics.
Mos	The estimated Mean Opinion Score (Conversational Quality, Estimated) for the latest iteration of the operation. The MOS-CQE is computed by IP SLAs as a function of the ICPIF. MOS values are expressed as a number from 1 (1.00) to 5 (5.00), with 5 being the highest level of quality, and 1 being the lowest level of quality. A MOS value of 0 (zero) indicates that MOS data could not be generated for the operation.
MinOfMos:	The lowest (minimum) MOS value computed for the collected statistics.
MaxOfMos:	The highest (maximum) ICPIF value computed for the collected statistics.
RTT Values:	Indicates that Round-Trip-Time statistics appear on the following lines.
NumOfRTT	The number of successful round trips.
RTTSum	The sum of all successful round trip values (in milliseconds).
RTTSum2	The sum of squares of those round trip values (in milliseconds).
PacketLossSD	The number of packets lost from source to destination.
PacketLossDS	The number of packets lost from destination to source.
PacketOutOfSequence	The number of packets returned out of order.
PacketMIA	The number of packets lost where the direction (SD/DS) cannot be determined.
PacketLateArrival	The number of packets that arrived after the timeout.
PacketSkipped	The number of packets that are not sent during the IP SLAs jitter operation.
InternalError	The number of times an operation could not be started due to other internal failures.
Busies	The number of times this operation could not be started because the previously scheduled run was not finished.
Jitter Values:	Indicates that Jitter statistics appear on the following lines. Jitter is inter-packet delay variance.
NumOfJitterSamples:	The number of jitter samples collected. This is the number of samples that are used to calculate the following jitter statitstics.
MinOfPositivesSD  MaxOfPositivesSD	The minimum and maximum positive jitter values from source to destination, in milliseconds.
NumOfPositivesSD	The number of jitter values from source to destination that are positive (i.e., network latency increases for two consecutive test packets).
SumOfPositivesSD	The sum of those positive values (in milliseconds).
Sum2PositivesSD	The sum of squares of those positive values.
MinOfNegativesSD  MaxOfNegativesSD	The minimum and maximum negative jitter values from source to destination. The absolute value is given.
NumOfNegativesSD	The number of jitter values from source to destination that are negative (i.e., network latency decreases for two consecutive test packets).
SumOfNegativesSD	The sum of those values.
Sum2NegativesSD	The sum of the squares of those values.
Interarrival jitterout:	The source to destination(SD) jitter value calculation, as defined in RFC 1889.
Interarrival jitterin:	The destination to souce (DS) jitter value calculation, as defined in RFC 1889.
One Way Values	Indicates that one way measurement statistics appear on the following lines. One Way (OW) Values are the amount of time it took the packet to travel from the source router to the target router (SD) or from the target router to the source router (DS).
NumOfOW	Number of successful one way time measurements.
OWMinSD	Minimum time from the source to the destination.
OWMaxSD	Maximum time from the source to the destination.
OWSumSD	Sum of the OWMinSD and OWMaxSD values.
OWSum2SD	Sum of the squares of the OWMinSD and OWMaxSD values.

The DS values show the same information as above for Destination-to-Source Jitter values.

Related Commands

Command	Description
show ntp status	Displays the status of the Network Time Protocol configuration on your system.
show rtr configuration	Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
show rtr distributions-statistics	Displays statistic distribution information (captured response times) for all IP SLAs operations or the specified operation.
show rtr totals-statistics	Displays the total statistical values (accumulation of error counts and completions) for all IP SLAs operations or the specified operation.