Table Of Contents

show kron schedule

show logging

show logging count

show logging history

show logging xml

show management event

show memory

show memory ecc

show memory fast

show memory scan

show microcode

show ntp associations

show ntp status

show parser dump

show parser statistics

show pci

show pci hardware

show processes

show processes memory

show protocols

show region

show registry

show reload

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

show rtr enhanced-history collection-statistics

show rtr enhanced-history distribution-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.

Default

None

Command Mode

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 73 describes the significant fields shown in the display.

Table 73 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 message 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.

Default

None

Command Mode

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

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 logging messages, and will not be preceeded by the percent symbol (%).

Examples

The following is sample output from the show logging command. In this example, buffer logging is disabled, so no syslog messages are displayed with this command.

Router# show logging

Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes)

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

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

     Buffer logging: disabled, xml disabled

     Logging Exception size (4096 bytes)

     Count and timestamp logging messages: enabled

     Trap logging: level informational, 35 message lines logged

Table 74 describes the significant fields shown in the display.

Table 74 show logging Field Descriptions

Field	Description
Syslog logging	Shows general state of system logging (enabled or disabled), and status of logged messages (number of messages dropped, rate-limited, or flushed).
Console logging	Logging to the console port. Shows "disabled" or, if enabled, the severity level limit and number of messages logged. Enabled using the logging console command.
Monitor logging	Logging to the monitor (all TTY lines). Shows "disabled" or, if enabled, the severity level limit and number of messages logged. Enabled using the logging monitor command.
Buffer logging	Logging to the standard syslog buffer. Shows "disabled" or, if enabled, the severity level limit and number of messages logged. Enabled using the logging buffered command.
Trap logging	Logging to a remote host (syslog host). Shows "disabled" or, if enabled, the severity level limit and number of messages logged. (The word "trap" means a trigger in the system software for sending error messages to a remote host.) Prior to Cisco IOS release 12.2(15)T, trap logging was enabled using the logging <host-name> command. Now enabled using 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.

The following example includes syslog messages from the system buffer, with timestamping :

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 75 decribes the symbols that proceed the timestamp.

Table 75 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 76 describes the logging level fields shown in the display.

Table 76 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 occuring, use the show logging command in privileged Exec mode.

show logging count

Syntax Description

This command has no arguements or keywords.

Command Mode

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

This command displays information such as the number of times a particular system error message occurs and the time stamp of the last occurrence of the specified message. System error messages are grouped into logical units called "Facilities" based on Cisco IOS software components.

To determine if system error message counting is enabled, use the show logging command.

The service timestamps command configuration determines the timestamp format (shown in the "Last Time" column) of show logging count command output. There is not quite enough space for all options of the possible options (datetime, milliseconds, and timezone) of the service timestamps 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 77 describes the significant fields shown in the display.

Table 77 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 Mode

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 78 describes the significant fields shown in the output.

Table 78 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 Mode

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 79 describes the significant fields shown in the displays.

Table 79 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 Mode

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 show statistics about memory, including memory-free pool statistics, use the show memory command in Exec mode.

show memory [address] [memory-type] [free] [summary]

Syntax Description

address	Show memory details starting at the specified address. Note You can also use the standard show command extensions to filter the output, such as show memory | begin address.
memory-type	(Optional) Memory type to display. If memory-type is not specified, statistics for all memory types present are displayed. Memory types include: •dead •free •io •multibus •overflow •pci •processor •statistics (memory pool statistics)
free	(Optional) Displays free memory statistics.
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 Mode

Exec

Command History

Release	Modification
10.0	This command was introduced.

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 

Router#

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 80 describes the significant fields shown in the first section of the display.

Table 80 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 81 describes the significant fields shown in the second section of the display.

Table 81 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 Address on previous line).
Next	Address of next block (should match 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 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 command shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see Table 20 and Table 21.

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
show memory fast	Displays fast (processor) memory statistics.
show processes memory	Displays memory used per process.

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 80 describes the significant fields shown in the first section of the display.

Table 82 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 fast

To display fast memory details for the router, use the show memory fast command.

show memory fast [allocating-process [totals] | dead [totals] | free [totals]]

Syntax Description

allocating-process	(Optional) Include allocating process names with the standard output.
dead	(Optional) Display only memory owned by dead processes.
free	(Optional) Display only memory not allocated to a process.
totals	(Optional) Summarizes the statistics for allocating processes, dead memory, or free memory.

Command Modes

Exec

Command History

Release	Modification
12.1	This command was introduced in a release prior to 12.1. This command replaced the show memory sram command.

Usage Guidelines

The show memory fast command displays the statistics for the fast memory. "Fast memory" is another name for "processor memory," and is also known as "cache memory." Cache memory is called fast memory because the processor can generally access the local cache (traditionally stored on SRAM positioned close to the processor) much more quickly than main memory or RAM.

---

Note The show memory fast command is a command alias for the show memory processor command. These commands will issue the same output.

---

Examples

The following example shows sample output from the show memory fast and the show memory processor commands:

Router>show memory fast 

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

8404A580 0001493284 00000000 841B6ECC 000  0        84BADF88 815219D8  (coalesced)

841B6ECC 0000020004 8404A580 841BBD18 001  -------- -------- 815DB094  Managed Chunk Queue 
Elements

841BBD18 0000001504 841B6ECC 841BC320 001  -------- -------- 8159EAC4  List Elements

841BC320 0000005004 841BBD18 841BD6D4 001  -------- -------- 8159EB04  List Headers

841BD6D4 0000000048 841BC320 841BD72C 001  -------- -------- 81F2A614  *Init*

841BD72C 0000001504 841BD6D4 841BDD34 001  -------- -------- 815A9514  messages

841BDD34 0000001504 841BD72C 841BE33C 001  -------- -------- 815A9540  Watched messages

841BE33C 0000001504 841BDD34 841BE944 001  -------- -------- 815A95E4  Watched Semaphore

841BE944 0000000504 841BE33C 841BEB64 001  -------- -------- 815A9630  Watched Message 
Queue

841BEB64 0000001504 841BE944 841BF16C 001  -------- -------- 815A9658  Watcher Message 
Queue

841BF16C 0000001036 841BEB64 841BF5A0 001  -------- -------- 815A2B24  Process Array

-- More --

<Ctrl+z>

Router>show memory processor 

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

8404A580 0001493284 00000000 841B6ECC 000  0        84BADF88 815219D8  (coalesced)

841B6ECC 0000020004 8404A580 841BBD18 001  -------- -------- 815DB094  Managed Chunk Queue 
Elements

841BBD18 0000001504 841B6ECC 841BC320 001  -------- -------- 8159EAC4  List Elements

841BC320 0000005004 841BBD18 841BD6D4 001  -------- -------- 8159EB04  List Headers

841BD6D4 0000000048 841BC320 841BD72C 001  -------- -------- 81F2A614  *Init*

841BD72C 0000001504 841BD6D4 841BDD34 001  -------- -------- 815A9514  messages

841BDD34 0000001504 841BD72C 841BE33C 001  -------- -------- 815A9540  Watched messages

841BE33C 0000001504 841BDD34 841BE944 001  -------- -------- 815A95E4  Watched Semaphore

841BE944 0000000504 841BE33C 841BEB64 001  -------- -------- 815A9630  Watched Message 
Queue

841BEB64 0000001504 841BE944 841BF16C 001  -------- -------- 815A9658  Watcher Message 
Queue

841BF16C 0000001036 841BEB64 841BF5A0 001  -------- -------- 815A2B24  Process Array

-- More --

<Ctrl+z>

Router>

The following example shows sample output from the show memory fast allocating-process command, followed by sample output from the show memory fast allocating-process totals command:

Router#show memory fast allocating-process   

          Processor memory

 Address      Bytes     Prev     Next Ref   Alloc Proc     Alloc PC  What

8404A580 0001493284 00000000 841B6ECC 000                  815219D8  (coalesced)

841B6ECC 0000020004 8404A580 841BBD18 001  *Init*          815DB094  Managed Chunk Queue 
Elements

841BBD18 0000001504 841B6ECC 841BC320 001  *Init*          8159EAC4  List Elements

841BC320 0000005004 841BBD18 841BD6D4 001  *Init*          8159EB04  List Headers

841BD6D4 0000000048 841BC320 841BD72C 001  *Init*          81F2A614  *Init*

841BD72C 0000001504 841BD6D4 841BDD34 001  *Init*          815A9514  messages

841BDD34 0000001504 841BD72C 841BE33C 001  *Init*          815A9540  Watched messages

841BE33C 0000001504 841BDD34 841BE944 001  *Init*          815A95E4  Watched Semaphore

841BE944 0000000504 841BE33C 841BEB64 001  *Init*          815A9630  Watched Message Queue

841BEB64 0000001504 841BE944 841BF16C 001  *Init*          815A9658  Watcher Message Queue

841BF16C 0000001036 841BEB64 841BF5A0 001  *Init*          815A2B24  Process Array

 --More-- 

<Ctrl+z>

c2600-1#show memory fast allocating-process totals 

Allocator PC Summary for: Processor

    PC          Total   Count  Name

0x815C085C    1194600     150  Process Stack

0x815B6C28     948680       5  pak subblock chunk

0x819F1DE4     524640       8  BGP (0) update

0x815C4FD4     393480       6  MallocLite

0x815B5FDC     351528      30  TW Buckets

0x819F14DC     327900       5  connected

0x81A1E838     327900       5  IPv4 Unicast net-chunk(8)

0x8153DFB8     248136     294  *Packet Header*

0x82142438     133192       4  CEF: 16 path chunk pool

0x82151E0C     131116       1  Init

0x819F1C8C     118480       4  BGP (0) attr

0x815A4858     100048     148  Process

0x8083DA44      97248      17  

 --More-- 

<Ctrl+z>

The following example shows sample output from the show memory fast dead command:

Router#show memory fast dead 

          Processor memory

 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what

8498FC20 0000000028 8498FB90 8498FC64 001  -------- -------- 81472B24  AAA MI SG NAME

        -------

             68

Router#show memory fast dead totals 

Dead Proc Summary for: Processor

    PC          Total   Count  Name

0x81472B24         68       1  AAA MI SG NAME

Router#

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.

Default

None

Command Mode

Exec

Command History

Release	Modification
12.0(4)XE	This command was introduced for the Cisco 7500 series.
12.0(7)T	This command was implemented in Cisco IOS Release 12.0T for the Cisco 7500 series.
12.0(6)S	This command was implemented in Cisco IOS Release 12.0S for the Cisco 7500 series.
12.1(1)E	This command was implemented in Cisco IOS Release 12.1E for the Cisco 7500 series.

Usage Guidelines

For the show memory scan command to function, the memory scan feature must be enabled on the RSP using the memory scan global configuraiton mode command.

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 83 describes the fields contained in the error report.

Table 83 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 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 Mode

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

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 84 describes the significant fields shown in the display.

Table 84 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 85 describes the significant fields shown in the display.

Table 85 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 Mode

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 86 describes the significant fields shown in the display.

Table 86 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 Mode

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 Mode

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 87 describes the key output fields.

Table 87 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 Mode

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 Mode

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 88 describes the significant fields shown in the display.

Table 88 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 Exec mode.

show processes [cpu]

Syntax Description

cpu	(Optional) Displays detailed central processing unit (CPU) utilization statistics (CPU use per process).

Command Mode

Exec

Command History

Release	Modification
10.0	This command was introduced.

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 Mwe  2FEA4E         1808	       464    3896     1796/3000   0  IP-EIGRP Router

  2 Lst  11682	          10236	      109   93908     1828/2000   0  Check heaps

  3 Mst  3AE9C              	0	      280       0     1768/2000   0  Timers

  4 Lwe  74AD2              	0       	12	       0     1492/2000   0  ARP Input

  5.ME   912E4	              0	        2       	0     1892/2000   0  IPC Zone Manager

  6.ME   91264	              0	        1       	0     1936/2000   0  IPC Realm Manager

  7.ME   91066              	0       30	       0     1784/2000   0  IPC Seat Manager

  8.ME  133368              	0	        1	       0     1928/2000   0  CXBus hot stall

  9.ME  1462EE	              0	        1       	0     1940/2000   0 Microcode load

 10 Msi 127538              	4       76      	52     1608/2000   0 Env Mon

 11.ME  160CF4              	0        	1       	0     1932/2000   0 MIP Mailbox

 12 Mwe 125D7C	              4	      280	      14     1588/2000   0 SMT input

 13 Lwe AFD0E	               0	        1       	0     1772/2000   0 Probe Input

 14 Mwe AF662	               0        	1	       0     1784/2000   0 RARP Input

 15 Hwe A1F9A	             228	      549	     415     3240/4000   0 IP Input

 16 Msa C86A0	               0      	114	       0     1864/2000   0 TCP Timer

 17 Lwe CA700               	0	        1       	0     1756/2000   0 TCP Protocols

 18.ME  CCE7C	               0        	1	       0     1940/2000   0 TCP Listener

 19 Mwe AC49E	               0        	1	       0     1592/2000   0 BOOTP Server

 20 Mwe 10CD84	             24       	77	     311     1652/2000   0 CDP Protocol

 21 Mwe 27BF82              	0	        2	       0     1776/2000   0 ATMSIG Input

Table 89 describes the significant fields shown in the output.

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

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%  Check heaps

    2            68        585     116  1.00% 1.00%    0%  IP Input

    3             0        744       0     0%    0%    0%  TCP Timer

    4             0          2       0     0%    0%    0%  TCP Protocols

    5             0          1       0     0%    0%    0%  BOOTP Server

    6            16        130     123     0%    0%    0%   ARP Input

    7             0          1       0     0%    0%    0%  Probe Input

    8             0          7       0     0%    0%    0%  MOP Protocols

    9             0          2       0     0%    0%    0%  Timers

   10           692         64   10812     0%    0%    0%  Net Background

   11             0          5       0     0%    0%    0%  Logger

   12             0         38       0     0%    0%    0%  BGP Open

   13             0          1       0     0%    0%    0%  Net Input

   14           540       3466     155     0%    0%    0%  TTY Background

   15             0          1       0     0%    0%    0%  BGP I/O

   16          5100       1367    3730     0%    0%    0%  IGRP Router

   17            88       4232      20  0.20% 1.00%    0%  BGP Router

   18           152      14650      10     0%    0%    0%  BGP Scanner

   19           224         99    2262     0%    0% 1.00%  Exec

Table 89 describes the significant fields shown in the display.

Table 89 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.
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.

---

Note Because the network server has a 4-millisecond clock resolution, run times are considered reliable only after a large number of invocations or a reasonable, measured run time.

---

Related Commands

Command	Description
show processes memory	Displays amount of system memory used per system process.

show processes memory

To show memory used, use the show processes memory command in Exec mode.

show processes memory

Syntax Description

This command has no arguments or keywords.

Command Mode

Exec

Command History

Release	Modification
10.0	This command was introduced.

Examples

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

Router# show processes memory

Total: 5611448, Used: 2307548, Free: 3303900

 PID  TTY  Allocated      Freed    Holding    Getbufs    Retbufs Process

   0    0     199592       1236    1907220          0          0 *Init*

   0    0        400      76928        400          0          0 *Sched*

   0    0    5431176    3340052     140760     349780          0 *Dead*

   1    0        256        256       1724          0          0 Load Meter

   2    0        264          0       5032          0          0 Exec

   3    0          0          0       2724          0          0 Check heaps

   4    0      97932          0       2852      32760          0 Pool Manager

   5    0        256        256       2724          0          0 Timers

   6    0         92          0       2816          0          0 CXBus hot stall

   7    0          0          0       2724          0          0 IPC Zone Manager

   8    0          0          0       2724          0          0 IPC Realm Manager

   9    0          0          0       2724          0          0 IPC Seat Manager

  10    0        892        476       3256          0          0 ARP Input

  11    0         92          0       2816          0          0 SERIAL A'detect

  12    0        216          0       2940          0          0 Microcode Loader

  13    0          0          0       2724          0          0 RFSS watchdog

  14    0   15659136   15658584       3276          0          0 Env Mon

.

.

.

  77    0        116          0       2844          0          0 IPX-EIGRP Hello

                                   2307224 Total

Table 90 describes the significant fields shown in the display.

Table 90 show processes memory Field Descriptions 

Field	Description
Total	Total amount of memory held.
Used	Total amount of used memory.
Free	Total amount of free memory.
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.
*Sched*	The scheduler.
*Dead*	Processes as a group that are now dead.
Total	Total amount of memory held by all processes.

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 Mode

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	Show region 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 an independant command.

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

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 Mode

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

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 91 describes the significant fields shown in the ouput.

Table 91 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 Mode

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 92 describes the significant fields shown in the display.

Table 92 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 Mode

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 93 describes the significant fields shown in the ouput.

Table 93 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 Mode

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 94 describes the significant fields shown in the display.

Table 94 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 Mode

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 95 describes the significant fields shown in the display.

Table 95 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 Mode

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 96 describes the significant fields shown in the display.

Table 96 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 Mode

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 97 describes the significant fields shown in the display.

Table 97 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 Mode

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 98 describes the significant fields shown in the display.

Table 98 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 Mode

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 99 describes the significant fields shown in the display.

Table 99 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 Mode

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 100 describes the significant fields shown in the display.

Table 100 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 Mode

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

To display global information about the Service Assurance Agent (SAA) feature, 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 Mode

Exec

Command History

Release	Modification
11.2	This command was introduced.

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#s how rtr application

        Response Time Reporter

Version: 2.2.0 Round Trip Time MIB

Max Packet Data Size (ARR and Data): 16384

Time of Last Change in Whole RTR: 03:34:44.000 UTC Sun Feb 11 2001

System Max Number of Entries: 2000

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 SAA operations or the specified operation.

show rtr authentication

To display Service Assurance Agent (SAA) Response Time Reporter (RTR) authentication information, use the show rtr authentication command in Exec mode.

show rtr authentication

Syntax Description

This command has no arguments or keywords.

Command Mode

Exec

Command History

Release	Modification
12.0(3)T	This command was introduced.

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 RTR operations (probes).

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

show rtr configuration

To display configuration values including all defaults for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr configuration command in Exec mode.

show rtr configuration [operation] [tabular | full]

Syntax Description

operation	(Optional) Number of the SAA operation to display.
tabular	(Optional) Display information in a column format reducing the number of screens required to display the information.
full	(Optional) Display all information using identifiers next to each displayed value. This is the default.

Defaults

Full format for all operations

Command Mode

Exec

Command History

Release	Modification
11.2	This command was introduced.

Examples

The following is sample output from the show rtr configuration command in full format:

Router# show rtr configuration 1

        Complete Configuration Table (includes defaults)

Entry Number: 1

Owner: "Sample Owner"

Tag: "Sample Tag Group"

Type of Operation to Perform: echo

Reaction and History Threshold (milliseconds): 5000

Operation Frequency (seconds): 60

Operation Timeout (milliseconds): 5000

Verify Data: FALSE

Status of Entry (SNMP RowStatus): active

Protocol Type: ipIcmpEcho

Target Address: 172.16.1.176

Request Size (ARR data portion): 1

Response Size (ARR data portion): 1

Life (seconds): 3600

Next Start Time: Start Time already passed

Entry Ageout (seconds): 3600

Connection Loss Reaction Enabled: FALSE

Timeout Reaction Enabled: FALSE

Threshold Reaction Type: never

Threshold Falling (milliseconds): 3000

Threshold Count: 5

Threshold Count2: 5

Reaction Type: none

Number of Statistic Hours kept: 2

Number of Statistic Paths kept: 1

Number of Statistic Hops kept: 1

Number of Statistic Distribution Buckets kept: 1

Number of Statistic Distribution Intervals (milliseconds): 20

Number of History Lives kept: 0

Number of History Buckets kept: 50

Number of History Samples kept: 1

History Filter Type: none

The following example verifies the configuration of an HTTP operation:

Router# show rtr configuration 

        Complete Configuration Table (includes defaults)

Entry Number:3

Owner:Joe

Tag:AppleTree

Type of Operation to Perform:http

Reaction and History Threshold (milliseconds):5000

Operation Frequency (seconds):60

Operation Timeout (milliseconds):5000

Verify Data:FALSE

Status of Entry (SNMP RowStatus):active

Protocol Type:httpAppl

Target Address:

Source Address:0.0.0.0

Target Port:0

Source Port:0

Request Size (ARR data portion):1

Response Size (ARR data portion):1

Control Packets:enabled

Loose Source Routing:disabled

LSR Path:

Type of Service Parameters:0x0

HTTP Operation:get

HTTP Server Version:1.0

URL:http://www.cisco.com

Cache Control:enabled

Life (seconds):3600

Next Scheduled Start Time:Start Time already passed

Entry Ageout:never

Connection Loss Reaction Enabled:FALSE

Timeout Reaction Enabled:FALSE

Threshold Reaction Type:never

Threshold Falling (milliseconds):3000

Threshold Count:5

Threshold Count2:5

Reaction Type:none

Number of Statistic Hours kept:2

Number of Statistic Paths kept:1

Number of Statistic Hops kept:1

Number of Statistic Distribution Buckets kept:1

Statistic Distribution Interval (milliseconds):20

Number of History Lives kept:0

Number of History Buckets kept:15

Number of History Samples kept:1

History Filter Type:none

Related Commands

Command	Description
show rtr application	Displays global information about the SAA feature.
show rtr collection-statistics	Displays statistical errors for all SAA operations or the specified operation.
show rtr distributions-statistics	Displays statistic distribution information (captured response times) for all SAA operations or the specified operation.
show rtr history	Displays history collected for all SAA operations or the specified operation.
show rtr operational-state	Displays the operational state of all SAA operations or the specified operation.
show rtr reaction-trigger	Displays the reaction trigger information for all SAA operations or the specified operation.
show rtr totals-statistics	Displays the total statistical values (accumulation of error counts and completions) for all SAA operations or the specified operation.

show rtr enhanced-history collection-statistics

To display enhanced history statistics for all collected history buckets for the specified Service Assurance Agent (SAA) operation, use the show rtr enhanced-history distributio-statistics command in user Exec or privileged Exec mode.

show rtr enhanced-history collection-statistics [operation-number]

Syntax Description

operation-number	(Optional) Displays enhanced history distribution statistics for only the specified operation.
dlci	Data link connection identifier of the permanent virtual circuit (PVC) to be monitored.

Command Mode

User Exec

Privileged Exec

Command History

Release	Modification
12.3(1)	This command was introduced.

Usage Guidelines

This command displays data for each bucket of enhanced history data shown individually (one after the other).

The number of buckets and the collection interval is set using the enhanced-history interval seconds buckets number-of-buckets SAA RTR configuration mode command.

For SLM operations, the enhanced history collection interval is set at 900 seconds and the number of buckets is set at 100. Because the enhanced history aggregationinterval is fixed at 900 seconds, the optional interval keyword available for this command will not work for SLM operations.

Examples

The output of this command will vary depending on the operation type. The following examples show output for various SAA operations.

Output for SLM Controller Operation

Router# show rtr configuration 1 | include Type 

Type of operation to perform: slm controller

Reaction Type: None

Router# show running-config | begin rtr 

.

.

.

rtr 1

 type slm controller T1 0

 enhanced-history interval 900 buckets 100

rtr schedule 1 start-time now life forever

.

.

.

Router# show rtr enhanced-history collection-statistics 1 

Entry number: 1

Aggregation Interval: 900

Bucket Index: 1

Aggregation start time 00:15:00.003 UTC Thur May 1 2003

Target Address: 

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

  Ds1StatRxLineStatus:  16385

  Ds1StatRxBPVs:  0,             Ds1StatRxCrcFrameErrors:  0

  Ds1StatRxErrSecs:  0,          Ds1StatRxSevereErrSecs:  0

  Ds1StatRxUnavailSecs:  0,      Ds1StatRxBurstyErrSecs:  0

Sample Index = 1

Bucket Index: 2

 .

 .

 .

Table 102 describes the significant fields shown in the display.

Table 102 show rtr enhanced-history Field Descriptions for SLM Controller Operations 

Field	Description
Aggregation Interval:	The number of seconds the operation runs for each enhanced history bucket. For example, a value of 900 indicates that statistics were gathered for 15 minutes before the next bucket was created.
Bucket Index:	The number identifying the collection bucket. The number of buckets is set using the enhanced-history SAA RTR configuration command.
Ds1StatRx	DS1 and E1 Received Statistics—The Ds1StatRx prefix is used for DS1 and E1 interfaces. DS1 and E1 interfaces are physical interfaces that run at a medium speed (for example, 1544 Kbps for DS1 interfaces). "Rx" indicates "received."
Ds1StatRxLineStatus:	Line Status—This variable indicates the Line Status of the interface. The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple conditions, like Excess Zeros and B8ZS detect, simultaneously. For example, the outOfFrame condition is implied by an outOfSignal condition. Possible values include: •2 — yellowAlarm •8 — blueAlarm •32 — outOfFrame •64 — outOfSignal •8192 — excessZeros •16384 — b8zsDetect
Ds1StatRxBPVs:	Bi-Polar Violations—The total number of Bipolar Violations (BPVs) received on the interface.
Ds1StatRxCrcFrameErrors:	CRC or Frame Errors—he total number of Cyclic Redundancy Check (CRC) Errors (with ESF framing) or Frame Errors (with D4 framing) received on the interface.
Ds1StatRxErrSecs:	Errored Seconds—The total number of Errored Seconds that have occurred on the interface. This includes both Line Errored and Path Errored Seconds.
Ds1StatRxSevereErrSecs:	Severely Errored Seconds—The total number of Severely Errored Seconds that have occurred on the interface. This includes both Line Severely Errored Seconds and Path Severely Errored Seconds.
Ds1StatRxUnavailSecs:	Unavailable Seconds—The total number of Unavailable Seconds that have occurred on the interface.
Ds1StatRxBurstyErrSecs:	Type B Errored Seconds—The total number of Type B (Bursty) Errored Seconds that have occurred on the interface.
Ds1StatRxREBEs:	E1 Remote-End Block Errors—The total number of Remote-End Block Error (REBE) Events received on an E1 interface. (This data does not appear for DS1 interfaces.)

Output for SLM Frame Relay Operation

Router# show rtr configuration 2 | include Type 

Type of operation to perform: Slm Frame-relay Interface

Reaction Type: None

Router#

Router# show rtr ennhanced-history collection-statistics 2 

Entry number: 2

Aggregation Interval: 900

Bucket Index: 1

Aggregation start time 00:15:00.003 UTC Mon Mar 1 1993

Target Address: 

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

LinkState :1 

Tx Total Frames:  24                       Rx Total Frames:  24

Tx Total Octets:  312                      Rx Total Octets:  344 

Tx FCSAlignErrors:  0                      Rx FCSAlignErrors:  0 

Tx Aborted Frames:  0                      Rx Aborted Frames:  0 

Tx Long Frames:  0                         Rx Long Frames:  0 

Tx Short Frames:  0                        Rx Short Frames:  0 

Tx MaxThroughput:  88                      Rx MaxThroughput:  152 

Tx MaxUtilization:  0                      Rx MaxUtilization:  0 

Tx MaxFramesSec:  1                        Rx MaxFramesSec:  1 

UnavailSecs:  0                            Drop Events:  0 

Tx OverFlowOctets:  0                      Rx OverFlowOctets:  0              

Tx Burst Percent1(sec):  238               Rx Burst Percent1(sec): 238

Tx Burst Percent2(sec):  0                 Rx Burst Percent2(sec): 0

Tx Burst Percent3(sec):  0                 Rx Burst Percent3(sec): 0

Tx Burst Percent4(sec):  0                 Rx Burst Percent4(sec): 0

Tx Burst Percent5(sec):  0                 Rx Burst Percent5(sec): 0

Sample Index = 1

Bucket Index: 2

 .

 .

 .

Table 103 describes the significant fields shown in the display. In the output "Tx" indicates "transmitted," "Rx" indicates "received."

Table 103 show rtr enhanced-history collection-statistics Field Descriptions for SLM Frame Relay Operations 

Field	Description
LinkState	The Link State of the Frame Relay access channel being monitored. The link state is determined by the presence of LMI messages on the user and network side of the line. The link state can take the following values: •up(1)—Both sides of the access channel are up. •networkDown(2)—The network side of the circuit has not responded to at least frDlcmiErrorThreshold Status Enquiry messages. •userDown(3)—The user side of the access channel has not sent a Status Enquiry LMI message in FrConfigPollingTimeoutInterval (T391) seconds. •down(4)—Both sides of the access channel have been down over some portion of the sampling interval. •spoofNetworkUp(5)—The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been up over the entire sampling interval. •spoofNetworkDown(6)— The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been down over the entire sampling interval.
Tx Total Frames:	The total number of frames (including errored frames) transmitted by the interface. Aborted frames are not included in this count. (MIB variable: FrStatTxFrames)
Rx Total Frames:	The total number of non-errored frames received by the interface. Aborted frames are not included. (MIB variable: FrStatRxFrames)
Tx Total Octets:	The total number of octets transmitted in frames from the interface (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count. (MIB variable: FrStatTxOctets)
Rx Total Octets:	The total number of octets received by the interface in non-errored frames (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count. (MIB variable: FrStatRxOctets)
Tx FCSAlignErrors:	The total number of frames transmitted by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Agents that cannot count this transmit-side object will return a value of zero. (MIB variable: FrStatTxFcsAlignErrors)
Rx FCSAlignErrors:	The total number of frames received by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). (MIB variable: FrStatRxFcsAlignErrors)
Tx Burst Percent1(sec):	The number of one second intervals where the transmitted throughput (t) is greater than or equal to zero and less than or equal to BurstLimit 1 (0 <= t <= BurstLimit1). BurstLimit1 is defined as a percentage of the CircuitBurstNominalRate in the RTTMON MIB. Note: The burst parameters used in this definition are defined in the CircuitConfigTable of the RTTMON MIB.

show rtr enhanced-history distribution-statistics

To display enhanced history distribution statistics for Service Assurance Agent (SAA) operations in tabular format, use the show rtr enhanced-history distribution-statistics command in user EXEC or privileged EXEC mode.

show rtr enhanced-history distribution-statistics [operation-number [interval seconds]]

Syntax Description

operation-number	(Optional) Displays enhanced history distribution statistics for only the specified operation.
interval seconds	(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval for only the specified operation. •The valid range is from 1 to 3,600 seconds (1 hour). The default interval for enhanced history collection is 900 seconds. •This keyword will not function for SLM operations.

Command Modes

User Exec

Privileged Exec

Command History

Release	Modification
12.3(1)	This command was introduced.

Usage Guidelines

The distribution statistics consist of the following:

•The sum of completion times (used to calculate the mean)

•The sum of the completion times squared (used to calculate standard deviation)

•The maximum and minimum completion times

•The number of completed attempts

You can also use the following commands to display additional statistics or history information, or to view the status of the operation:

•show rtr enhanced-history collection-statistics

•show rtr enhanced-history totals-statistics

---

Tip If the character `n' appears in your output, or not all fields are displayed, you should increase the screen width for your CLI display (for example, using the width line configuration command or the terminal width Exec mode command).

---

Examples

The following is sample output from the show rtr enhanced-history distribution-statistics command for an SLM Frame Relay Circuit (Slm Frame-relay Pvc) operation. Please note the following:

•The fields are defined at the beginning of the output for the command.

•RTT means round-trip-time.

•The time elapsed between BucketIndex 1 (started at 257,850,000) and BucketIndex 2 (started at 258,750,002) in this example is 900,002 milliseconds, or 900 seconds.

•Table 104 provides further details about the significant fields shown in this output.

Router# show rtr configuration 3 | include Type 

Type of operation to perform: Slm Frame-relay Pvc

Reaction Type: None

Router# show rtr enhanced-history distribution-statistics 3 

 Point by point Enhanced History

Entry    = Entry Number

Int      = Aggregation Interval (seconds)

BucI     = Bucket Index

StartT   = Aggregation Start Time

Pth      = Path index

Hop      = Hop in path index

Comps    = Operations completed

OvrTh    = Operations completed over thresholds

SumCmp   = Sum of RTT (milliseconds)

SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)

SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)

TMax     = RTT maximum (milliseconds)

TMin     = RTT minimum (milliseconds)

Entry Int BucI StartT    Pth Hop Comps OvrTh SumCmp   SumCmp2L  SumCmp2H   TMax    TMin

3     900 1    257850000 1   1   3     0     43       617       0          15      14

3     900 2    258750002 1   1   3     0     45       677       0          16      14

3     900 3    259650000 1   1   3     0     44       646       0          15      14

3     900 4    260550002 1   1   3     0     42       594       0          15      12

3     900 5    261450003 1   1   3     0     42       590       0          15      13

3     900 6    262350001 1   1   3     0     46       706       0          16      15

3     900 7    263250003 1   1   3     0     46       708       0          16      14

 .

 .

 .

Table 104 show rtr enhanced-history distribution-statistics Field Descriptions 

Field	Description
Entry (Entry ID Number)	The operation ID number you specified for the SAA operation.
Int (Interval)	Aggregation Interval - This is the configured statistical distribution buckets interval, in seconds. For example, a value of 900 for Int means that statistics are gathered for 900 seconds per bucket.
BucI (Bucket Index)	Bucket Index Number—A number uniquely identifying the statistical distribution (aggregation) bucket. •The number of history buckets to be kept is configured using the buckets-of-history-kept command. •A bucket will gather statistics for the specified interval of time (aggregation interval), after which a new statistics bucket is created. •If a number-of-buckets-kept value is configured, the interval for the last bucket is infinity (until the end of the operation). •Buckets are not applicable to HTTP and Jitter monitoring operations. •This field is equivalant to the rttMonStatsCaptureDistIndex object in the Cisco Rttmon MIB.
StartT (StartTime)	Aggregation Start Time — Start time for the aggregation interval (per Bucket Index). •Shows the start time as the number of milliseconds since the router started; in other words, the time stamp is the number of milliseconds since the last system boot-up.
Pth (Path)	Path Index Number — The Path index number is an idenitifier for a set of different paths to the target destination that have been discovered. For example, if the first probe iteration finds the path h1, h2, h3, h4, then this path is labeled as "1". If, on a later iteration, a new path is discovered, say h1, h2, h5, h6, h4, then this new path will be identified as "2", and so on. •Data collection per path is available only for IP/ICMP Path Echo operations ("pathEcho probes"). For all other operations, a value of "1" will always appear. •Data collection per path is configured using the paths-of-statistics-kept number command when configuring the operation.
Hop	Hop Index Number — Statistics data per hop. A hop is data transmission between two points in a path (for example, from device h2 to device h3). •Data collection per hop is available only for IP/ICMP Path Echo operations ("pathEcho probes"). For all other operations, a value of "1" will always appear. •Data collection per hop is configured using the hops-of-statistics-kept number command when configuring the operation. •This field is equivalant to the rrttMonStatsCaptureHopIndex object in the Cisco Rttmon MIB.
Comps (Completed Round-Trip-Time Probes)	Completions —The number of RTT probes that have completed without an error and without timing out, per bucket index. •This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the Cisco Rttmon MIB object.
SumCmp (Sum of Completed Round-Trip-Times)	Sum of Completed Probe Times (1) — The total of all round-trip-time values for all succesfull probes in the row, in milliseconds.
SumCmp2L (Sum of Squares of Completed Round-Trip-Times, Squared, Low-Order Value)	Sum of the Squares of Completed Probe Times (2), Low-Order — The sum of the square roots of round-trip-times for probes that were successfully measured, in milliseconds; displays the low-order 32 bits of the value only. •32 low-order bits and 32 high-order bits are ordered in unsigned 64-bit integers (Int64) as follows:  ------------------------------------------------- | High-order 32 bits     | Low-order 32 bits      |  ------------------------------------------------- •The "SumCmp2" values are split into "high-order" and "low-order" numbers because of limitations of SNMP. The maximum value allowed for an SNMP object is 4,294,967,295 (the `Gauge32' limit). If the sum of the square roots for your operation exceeds this value, then the "high-order" value will be utilized. (For example, the number 4,294,967,296 would have all low-order bits as '0', and the rightmost high-order bit would be `1'). •The Low-order value (SumCmp2L) appears first in the output because in most cases, the value will be less than 4,294,967,295, which means that the value of SumCmp2H will appear as zero. For example: SumCmp2L  SumCmp2H 617       0
SumCmp2H (Sum of Squares of Completed Round-Trip-Times, Squared, High-order Value)	Sum of the Squares of Completed Probe Times (2), High-Order— The high-order 32 bits of the accumulated squares of completion times (in milliseconds) of probe operations which completed successfully.
TMax	Round-Trip-Time, Maximum— The highest recorded round-trip-time, in milliseconds, per aggregation interval.
TMin	Round-Trip-Time, Minimum—The lowest recorded round-trip-time, in milliseconds, per aggregation interval.

 

Related Commands

Command	Description
rtr	Allows configuration of SAA operations by entering rtr configuration mode for the specified operation number.
show rtr enhanced-history collection-statistics	Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.