System Management Commands

priority-list interface

To establish queuing priorities on packets entering from a given interface, use the priority-list interface global configuration command. Use the no form of this command with the appropriate arguments to remove an entry from the list.

priority-list list-number interface interface-type interface-number {high | medium |
normal | low}
no priority-list list-number interface interface-type interface-number {high | medium |
normal | low}

Syntax Description

list-number	Arbitrary integer between 1 and 16 that identifies the priority list selected by the user.
interface-type	Specifies the name of the interface.
interface-number	Number of the specified interface.
high \| medium \| normal \| low	Priority queue level.

Default

No queuing priorities are established.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

The following example sets any packet type entering on Ethernet interface 0 to a medium priority:

priority-list 3 interface ethernet 0 medium

Related Commands

priority-list protocol

To establish queuing priorities based upon the protocol type, use the priority-list protocol global configuration command. Use the no form of this command with the appropriate list number to remove an entry from the list.

priority-list list-number protocol protocol-name {high | medium | normal | low}
queue-keyword keyword-value
no priority-list list-number protocol [protocol-name {high | medium | normal | low}
queue-keyword keyword-value]

Syntax Description

list-number	Arbitrary integer between 1 and 16 that identifies the priority list selected by the user.
protocol-name	Specifies the protocol type: aarp, arp, apollo, appletalk, bridge (transparent), clns, clns_es, clns_is, compressedtcp, cmns, decnet, decnet_node, decnet_router-l1, decnet_router-l2, ip, ipx, pad, rsrb, stun, vines, xns, and x25.
high \| medium \| normal \| low	Priority queue level.
queue-keyword keyword-value	Possible keywords are fragments, gt, lt, list, tcp, and udp. See Table 69.

Default

No queuing priorities are established.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

When using multiple rules for a single protocol, remember that the system reads the priority settings in order of appearance. When classifying a packet, the system searches the list of rules specified by priority-list commands for a matching protocol or interface type. When a match is found, the packet is assigned to the appropriate queue. The list is searched in the order it is specified, and the first matching rule terminates the search.

The decnet_router-l1 keyword refers to the multicast address for all level-1 routers, which are intra-area routers, and the decnet_router-l2 keyword refers to all level 2 routers, which are interarea routers.

Use Table 69, Table 70, and Table 71 to configure the queuing priorities for your system.

**Table 69: Protocol Priority Queue Keywords and Values**
Option	Description
fragments	Assigns the priority level defined to fragmented IP packets (for use with IP protocol only). More specifically, IP packets whose fragment offset field is nonzero are matched by this command. The initial fragment of a fragmented IP packet has a fragment offset of zero, so such packets are not matched by this command. Note: Packets with a nonzero fragment offset do not contain TCP or UDP headers, so other instances of this command that use the tcp or udp keyword will always fail to match such packets.
gt byte-count	Specifies a greater-than count. The priority level assigned goes into effect when a packet size exceeds the value entered for the argument byte-count. The size of the packet must also include additional bytes because of MAC encapsulation on the outgoing interface.
lt byte-count	Specifies a less-than count. The priority level assigned goes into effect when a packet size is less than the value entered for the argument byte-count. The size of the packet must also include additional bytes because of MAC encapsulation on the outgoing interface.
list list-number	Assigns traffic priorities according to a specified list when used with AppleTalk, bridging, IP, IPX, VINES, or XNS. The list-number argument is the access list number as specified by the access-list global configuration command for the specified protocol-name. For example, if the protocol is AppleTalk, list-number should be a valid AppleTalk access list number.
tcp port	Assigns the priority level defined to TCP segments originating from or destined to a specified port (for use with the IP protocol only). Table 70 lists common TCP services and their port numbers.
udp port	Assigns the priority level defined to UDP packets originating from or destined to a specified port (for use with the IP protocol only). Table 71 lists common UDP services and their port numbers.

**Table 70: Common TCP Services and Their Port Numbers (Continued)**
Service	Port
Telnet	23
SMTP	25

**Table 71: Common UDP Services and Their Port Numbers (Continued)**
Service	Port
TFTP	69
NFS	2049
SNMP	161
RPC	111
DNS	53

Note The TCP and UDP ports listed in Table 70 and Table 71 include some of the more common port numbers. However, you can specify any port number to be prioritized; you are not limited to those listed.
For some protocols, such as TFTP and FTP, only the initial request uses port 69. Subsequent packets use a randomly chosen port number. For these types of protocols, the use of port numbers fails to be an effective method to manage queued traffic.

Use the no priority-list global configuration command followed by the appropriate list-number argument and the protocol keyword to remove a priority list entry assigned by protocol type.

Examples

The following example assigns 1 as the arbitrary priority list number, specifies DECnet as the protocol type, and assigns a high-priority level to the DECnet packets transmitted on this interface:

priority-list 1 protocol decnet high

The following example assigns a medium-priority level to every DECnet packet with a size greater than 200 bytes:

priority-list 2 protocol decnet medium gt 200

The following example assigns a medium-priority level to every DECnet packet with a size less than 200 bytes:

priority-list 4 protocol decnet medium lt 200

The following example assigns a high-priority level to traffic that matches IP access list 10:

priority-list 1 protocol ip high list 10

The following example assigns a medium-priority level to Telnet packets:

priority-list 4 protocol ip medium tcp 23

The following example assigns a medium-priority level to UDP Domain Name service packets:

priority-list 4 protocol ip medium udp 53

The following example assigns a high-priority level to traffic that matches Ethernet type code access list 201:

priority-list 1 protocol bridge high list 201

Related Commands

priority-list queue-limit

To specify the maximum number of packets that can be waiting in each of the priority queues, use the priority-list queue-limit global configuration command.The no form of this command selects the normal queue.

priority-list list-number queue-limit high-limit medium-limit normal-limit low-limit
no priority-list list-number queue-limit

Syntax Description

list-number	Arbitrary integer between 1 and 16 that identifies the priority list selected by the user.
high-limit medium-limit normal-limit low-limit	Priority queue maximum length. A value of 0 for any of the four arguments means that the queue can be of unlimited size for that particular queue.

Default

The default queue limit arguments are listed in Table 72.

**Table 72: Priority Queue Packet Limits**
Priority Queue Argument	Packet Limits
high-limit	20
medium-limit	40
normal-limit	60
low-limit	80

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

If a priority queue overflows, excess packets are discarded and quench messages can be sent, if appropriate, for the protocol.

Example

The following example sets the maximum packets in the priority queue to 10:

priority-list 2 queue-limit 10 40 60 80

Related Commands

custom-queue-list
show queueing

prompt

To customiz e the prompt, use the prompt global configuration command. To revert to the default prompt, use the no form of this command.

prompt string
no prompt [string]

Syntax Description

string

Prompt. It can consist of all printing characters and the escape sequences listed in Table 73.

Default

The default prompt is either Router or the name defined with the hostname global configuration command, followed by an angle bracket (>) for EXEC mode or a pound sign (#) for privileged EXEC mode.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

You can include escape sequences when specifying the prompt. All escape sequences are preceded by a percent sign (%). Table 73 lists the valid escape sequences.

**Table 73: Custom Prompt Escape Sequences**
Escape Sequence	Interpretation
%h	Host name. This is either Router or the name defined with the hostname global configuration command.
%n	Physical terminal line (TTY) number of the EXEC user.
%p	Prompt character itself. It is either an angle bracket (>) for EXEC mode or a pound sign (#) for privileged EXEC mode.
%s	Space.
%t	Tab.
%%	Percent sign (%)

Issuing the prompt%h command has the same effect as issuing the no prompt command.

Examples

The following example changes the EXEC prompt to include the TTY number, followed by the name and a space:

prompt TTY%n@%h%s%p

The following are examples of user and privileged EXEC prompts that result from the previous command:

TTY17@Router1 >
TTY17SRouter1 #

Related Command

hostname

queue-list default

To assign a priority queue for those packets that do not match any other rule in the queue list, use the queue-list default global configuration command. To restore the default value, use the no form of this command.

queue-list list-number default queue-number
no queue-list list-number default queue-number

Syntax Description

list-number	Number of the queue list. An integer from 1 to 16.
queue-number	Number of the queue. An integer from 1 to 16.

Default

Queue number 1

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

When using multiple rules, remember that the system reads the queue-list commands in order of appearance. When classifying a packet, the system searches the list of rules specified by queue-list commands for a matching protocol or interface type. When a match is found, the packet is assigned to the appropriate queue. The list is searched in the order it is specified, and the first matching rule terminates the search.

Queue number 0 is a system queue. It is emptied before any of the other queues are processed. The system enqueues high-priority packets, such as keepalives, to this queue.

Use the show interface command to display the current status of the output queues.

Example

In the following example, the default queue for list 10 is set to queue number 2:

queue-list 10 default 2

Related Commands

custom-queue-list
show queueing

queue-list interface

To establish queuing priorities on packets entering on an interface, use the queue-list interface global configuration command. To remove an entry from the list, use the no form of the command.

queue-list list-number interface type number queue-number
no queue-list list-number interface queue-number

Syntax Description

list-number	Number of the queue list. An integer from 1 to 16.
type	Required argument that specifies the name of the interface.
number	Number of the specified interface.
queue-number	Number of the queue. An integer from 1 to 16.

Default

No queuing priorities are established.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

In the following example, queue list 4 established queuing priorities for packets entering on interface tunnel 3. The queue number assigned is 10.

queue-list 4 interface tunnel 3 10

Related Commands

custom-queue-list
show queueing

queue-list protocol

To establish queuing priority based upon the protocol type, use the queue-list protocol global configuration command. Use the no form of this command with the appropriate list number to remove an entry from the list.

queue-list list-number protocol protocol-name queue-number queue-keyword keyword-value
no queue-list list-number protocol protocol-name

Syntax Description

list-number	Number of the queue list. An integer from 1 to 16.
protocol-name	Required argument that specifies the protocol type: aarp, arp, apollo, appletalk, bridge (transparent), clns, clns_es, clns_is, compressedtcp, cmns, decnet, decnet_node, decnet_routerl1, decnet_routerl2, dlsw, ip, ipx, pad, rsrb, stun, vines, xns, and x25.
queue-number	Number of the queue. An integer from 1 to 16.
queue-keyword keyword-value	Possible keywords are gt, lt, list, tcp, and udp. See Table 69.

Default

No queuing priorities are established.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The rsrb keyword refers only to RSRB direct encapsulation.

Use Table 69, Table 70, and Table 71 from the priority-list protocol command to configure custom queuing for your system.

Examples

The following example assigns 1 as the custom queue list, specifies DECnet as the protocol type, and assigns 3 as a queue number to the packets transmitted on this interface:

queue-list 1 protocol decnet 3

The following example assigns DECnet packets with a size greater than 200 bytes to queue number 2:

queue-list 2 protocol decnet 2 gt 200

The following example assigns DECnet packets with a size less than 200 bytes to queue number 2:

queue-list 4 protocol decnet 2 lt 200

The following example assigns traffic that matches IP access list 10 to queue number 1:

queue-list 1 protocol ip 1 list 10

The following example assigns Telnet packets to queue number 2:

queue-list 4 protocol ip 2 tcp 23

The following example assigns UDP Domain Name service packets to queue number 2:

queue-list 4 protocol ip 2 udp 53

The following example assigns traffic that matches Ethernet type code access list 201 to queue number 1:

queue-list 1 protocol bridge 1 list 201

Related Commands

queue-list queue byte-count

To designate the byte size allowed per queue, use the queue-list queue byte-count global configuration command. To return the byte size to the default value, use the no form of the command.

queue-list list-number queue queue-number byte-count byte-count-number
no queue-list list-number queue queue-number byte-count byte-count-number

Syntax Description

list-number	Number of the queue list. An integer from 1 to 16.
queue-number	Number of the queue. An integer from 1 to 16.
byte-count-number	Specifies the lower boundary on how many bytes the system allows to be delivered from a given queue during a particular cycle.

Default

1500 bytes

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

In the following example, queue list 9 establishes the byte-count as 1400 for queue number 10:

queue-list 9 queue 10 byte-count 1400

Related Commands

custom-queue-list
show queueing

queue-list queue limit

To designate the queue length limit for a queue, use the queue-list queue limit global configuration command. To return the queue length to the default value, use the no form of the command.

queue-list list-number queue queue-number limit limit-number
no queue-list list-number queue queue-number limit limit-number

Syntax Description

list-number	Number of the queue list. An integer from 1 to 16.
queue-number	Number of the queue. An integer from 1 to 16.
limit-number	Maximum number of packets which can be enqueued at any time. Range is 0 to 32767 queue entries. A value of 0 means that the queue can be of unlimited size.

Default

20 entries

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

In the following example, the queue length of queue 10 is increased to 40:

queue-list 5 queue 10 limit 40

Related Commands

custom-queue-list
show queueing

random-detect

To enable random early detection on an interface, use the random-detect interface configuration command. Use the no form of this command to disable random early detection on the interface.

random-detect [weighting]
no random-detect

Syntax Description

weighting

(Optional) Exponential weighting constant in the range 1 to 16 used to determine the rate that packets are dropped when congestion occurs. The default is 10 (that is, drop 1 packet every 210).

Default

Random early detection is disabled.

Command Mode

Interface configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Random early detection (RED) is useful in high-speed TCP/IP networks to avoid congestion by dropping packets at a controlled rate. RED is not recommended for protocols, such as AppleTalk or Novell Netware, that respond to dropped packets by retransmitting the packets at the same rate. RED should only be configured on an interface where most of the traffic is TCP/IP traffic.

Cisco recommends using the default value for the exponential weighting constant; however, you may need to change this value depending on your operational environment. For example, a value of 10 (the default), which might achieve a loss rate of 10-4, is recommended for high-speed links such as DS3 and OC3, whereas a value of 7, which might achieve a loss rate of 10-3, is recommended for T1 links.

Random early detection cannot be configured on an interface already configured with custom, priority, or fair queueing.

When RSVP is configured on the interface, packets from other traffic flows are dropped before RSVP flows (when possible). Also, the IP precedence of the packet determines whether the packet is dropped. Lower-precedence traffic is dropped before higher-precedence traffic. Therefore, lower-precedence traffic is more likely to be throttled back.

Example

The following example shows how to enable random early detection on a serial interface:

interface serial 0
random-detect

Related Commands

A dagger (⁺) indicates that the command is documented outside this chapter.

custom-queue-list
fair-queue
ip rsvp bandwidth ^⁺priority-group
priority-list default
queue-list default
random-detect
show interface ^⁺

request-data-size

To set the protocol data size in the payload of the response time reporter probe's request packet, use the request-data-size response time reporter configuration command. Use the no form of this command to return to the default value.

request-data-size byte
no request-data-size

Syntax Description

byte

Size of the protocol data in the payload of the probe's request packet. Range is 0 to the protocol's maximum. The default is 1 byte.

Default

1 byte

Command Mode

Response time reporter configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

When the protocol name has the suffix "appl," the packet uses both a request and respond data size (see the response-data-size response time reporter configuration command), and the data size is 12 bytes smaller than the normal payload size (this 12 bytes is the ARR Header used to control send and data response sizes).

Example

In the following example, probe 3's request packet size is set to 40 bytes:

rtr 3
 type echo protocol snalu0echoappl cwbc0a
 request-data-size 40

Related Commands

response-data-size
rtr

response-data-size

To set the protocol data size in the payload of the response time reporter probe's response packet, use the response-data-size response time reporter configuration command. Use the no form of this command to return to the default value.

response-data-size byte
no response-data-size

Syntax Description

byte

Size of the protocol data in the payload in the probe's response packet. For "appl" protocols, the default is 0 bytes. For all others, the default is the same value as the request-data-size.

Default

For "appl" protocols, 0 bytes

For all others, the same value as the request-data-size

Command Mode

Response time reporter configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

The response-data-size command is only applicable for protocols defined with the type command that end in "appl" (for example, snalu0echoappl). When the protocol ends in "appl," the response data size is 12 bytes smaller than normal payload size.

Example

In the following example, probe 3's response packet size is set to 1440 bytes:

rtr 3
 type echo protocol snalu0echoappl cwbc0a
 response-data-size 1440

Related Commands

request-data-size
rtr

rmon

To enable Remote Network Monitoring (RMON) on an Ethernet interface, use the rmon interface configuration command. Use the no form of this command to disable RMON on the interface.

rmon {native | promiscuous}
no rmon

Syntax Description

native	Enables RMON on the Ethernet interface. In native mode, the router processes only packets destined for this interface.
promiscuous	Enables RMON on the Ethernet interface. In promiscuous mode, the router examines every packet.

Default

RMON is disabled on the interface.

Command Mode

Interface configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

This command enables RMON on Ethernet interfaces of Cisco 2500 series routers only. A generic RMON console application such as Frontier NETscout ManagerTM or Traffic DirectorTM is required in order to use the RMON network management capabilities. SNMP must also be configured. RMON provides visibility of individual nodal activity and allows you to monitor all nodes and their interaction on a LAN segment. When the rmon command is issued, the router automatically installs an Ethernet statistics study for the associated interface.

Note RMON can be very data and processor intensive. Users should measure usage effects to ensure that router performance is not degraded and to minimize excessive management traffic overhead. Native mode is less intensive than promiscuous mode.

All Cisco IOS software Release 11.1 feature sets support RMON alarm and event groups. Additional RMON groups are supported in certain feature sets. Refer to the Cisco IOS Release 11.1 Release Notes for feature set descriptions. As a security precaution, support for the packet capture group allows capture of packet header information only; data payloads are not captured.

The RMON MIB is described in RFC 1757.

Example

The following example enables RMON on Ethernet interface 0 and allows the router to examine only packets destined for the interface:

interface ethernet 0
 rmon native

Related Commands

rmon alarm
rmon event
rmon queuesize
show rmon

rmon alarm

To set an alarm on any MIB object, use the rmon alarm configuration command. Use the no form of this command to disable the alarm.

rmon alarm number variable interval {delta | absolute} rising-threshold value [event-number]
falling-threshold value [event-number] [owner string]
no rmon alarm number

Syntax Description

number	Alarm number, which is identical to the alarmIndex in the alarmTable in the Remote Monitoring (RMON) MIB.
variable	MIB object to monitor, which translates into the alarmVariable used in the alarmTable of the RMON MIB.
interval	Time in seconds the alarm monitors the MIB variable, which is identical to the alarmValue used in the alarmTable of the RMON MIB.
delta	Tests the change between MIB variables, which affects the alarmSampleType in the alarmTable of the RMON MIB.
absolute	Tests each MIB variable directly, which affects the alarmSampleType in the alarmTable of the RMON MIB.
rising-threshold value	Value at which the alarm is triggered.
event-number	(Optional) Event number to trigger when the rising or falling threshold exceeds its limit. This value is identical to the alarmRisingEventIndex or the alarmFallingEventIndex in the alarmTable of the RMON MIB.
falling-threshold value	Value at which the alarm is reset.
owner string	(Optional) Specifies an owner for the alarm, which is identical to the alarm owner in the alarmTable of the RMON MIB.

Default

No alarms configured

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

To disable the RMON alarms, you must use the no form of the command on each configured alarm. For example, enter no rmon alarm 1, where the 1 identifies which alarm is to be removed.

See RFC 1757 for more information about the RMON alarm group.

Example

The following example configures an RMON alarm using the rmon alarm command:

rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1 falling-threshold 0
     owner jjohnson

This example configures RMON alarm number 10. The alarm monitors the MIB variable ifEntry.20.1 once every 20 seconds until the alarm is disabled, and checks the change in the variable's rise or fall. If the ifEntry.20.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. Possible events include a log entry or a SNMP trap. If the ifEntry.20.1 value changes by 0 (falling-threshold 0), the alarm is reset and can be triggered again.

Related Commands

rmon
rmon event
show rmon

rmon event

To add or remove an event in the RMON event table that is associated with an RMON event number, use the rmon event global configuration command. Use the no form of this command to disable RMON on the interface.

rmon event number [log] [trap community] [description string] [owner string]
no rmon event number

Syntax Description

number	Assigned event number, which is identical to the eventIndex in the eventTable in the RMON MIB.
log	(Optional) Generates an RMON log entry when the event is triggered and sets the eventType in the RMON MIB to log or log-and-trap.
trap community	(Optional) SNMP community string used for this trap. Configures the setting of the eventType in the RMON MIB for this row as either snmp-trap or log-and-trap. This value is identical to the eventCommunityValue in the eventTable in the RMON MIB.
description string	(Optional) Specifies a description of the event, which is identical to the event description in the eventTable of the RMON MIB.
owner string	(Optional) Owner of this event, which is identical to the eventDescription in the eventTable of the RMON MIB.

Default

No events configured

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

This command applies only to the AS5200 access server.

See RFC 1757 for more information about the RMON MIB.

Example

The following example enables the rmon event command:

rmon event 1 log trap eventtrap description "High ifOutErrors" owner sdurham

This example configuration creates RMON event number 1, which is defined as High ifOutErrors, and generates a log entry when the event is triggered by an alarm. The user sdurham owns the row that is created in the event table by this command. This configuration also generates a Simple Network Management Protocol (SNMP) trap when the event is triggered.

Related Commands

rmon
show rmon

rmon queuesize

To change the size of the queue that holds packets for analysis by the Remote Network Monitoring (RMON) process, use the rmon queuesize global configuration command. Use the no form of this command to restore the default value.

rmon queuesize size
no rmon queuesize

Syntax Description

size

Number of packets allowed in the queue awaiting RMON analysis. Default queue size is 64 packets.

Default

64 packets

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

This command applies to the RMON function, which is available on Ethernet interfaces of Cisco 2500 series routers only.

You might want to increase the queue size if the RMON function indicates it is dropping packets. You can determine this from the output of the show rmon command or from the etherStatsDropEvents object in the etherStats table. A feasible maximum queue size depends on the amount of memory available in the router and the configuration of the buffer pool.

Example

The following example configures the RMON queue size to be 128 packets:

rmon queuesize 128

Related Commands

rmon
show rmon

rtr

To configure a response time reporter probe, use the rtr global configuration command. Use the no form of this command to remove all configuration information for a probe including the probe's schedule, reaction configuration, and reaction triggers.

rtr probe
no rtr probe

Syntax Description

probe

Number of the response time reporter probe (instance) to configure.

Default

None

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

A probe is used for the purpose of collecting response time information.

Each platform has a limit on the number of probes that can be configured. In general this limit is less than 20.

Debugging is supported only on the first 32 probe numbers.

The response time reporter feature allows customers to monitor the performance of their network, network resources, and applications by measuring response times and availability. With this feature, a customer can perform troubleshooting, problem notification, and preproblem analysis. The response time reporter feature is currently available only with the IBM feature set of the Cisco IOS software. For more information, refer to the "Managing the System" chapter in the Configuration Fundamentals Configuration Guide and the Cisco Round-Trip Time Monitor (RTTMON) MIB in the Cisco MIB User Quick Reference.

This command places you in (config-rtr) mode.

Note After you schedule a probe with the rtr schedule global configuration command, you cannot modify the probe's configuration. To modify the probe's configuration after it is scheduled, use the no rtr command. You can now reenter the probe's configuration with the rtr command.

Use the following response time reporter configuration commands (config-rtr) to configure the probe's characteristics:

After you configure a probe, you must schedule the probe. For information on scheduling a probe, refer to the rtr schedule global configuration command. You can also optionally set reaction triggers for the probe. For information on reaction triggers, refer to the rtr reaction-configuration and rtr reaction-trigger global configuration commands.

To display the probe's current configuration settings, use the show rtr configuration EXEC command.

Example

In the following example, probe 1 is configured to perform end-to-end response time operations using an SNA LU Type 0 connection with the host name cwbc0a. Only the type response time reporter configuration command is required; all others are optional.

rtr 1
 type echo protocol snalu0echoappl cwbc0a
 request-data-size 40
 response-data-size 1440

Note If probe 1 already existed and it has not been scheduled, you are placed into response time reporter configuration command mode. If the probe already exists and has been scheduled, this command will fail.

Related Commands

rtr reaction-configuration
rtr reaction-trigger
rtr reset
rtr schedule

rtr reaction-configuration

To configure certain actions to occur based on events under the control of the response time reporter, use the rtr reaction-configuration global configuration command. Use the no form of this command to return to the probe's default values.

rtr reaction-configuration probe [connection-loss-enable] [timeout-enable]
[threshold-falling milliseconds] [threshold-type option] [action-type option]
no rtr reaction-configuration probe

Syntax Description

probe	Number of the response time reporter probe to configure.
connection-loss-enable	(Optional) Enable checking for connection loss in connection-oriented protocols. The default is disabled.
timeout-enable	(Optional) Enable checking for response time reporting operation timeouts based on the timeout value configured for the probe with the timeout response time reporter configuration command. The default is disabled.
threshold-falling milliseconds	(Optional) Set the falling threshold (standard RMON-type hysteresis mechanism) in milliseconds. When the falling threshold is met, generate a resolution reaction event. The probe's rising over threshold is set with the threshold response time reporter configuration command. The default value is 3000 ms.
threshold-type option	(Optional) Specify the algorithm used by the response time reporter to calculate over and falling threshold violations. Option can be one of the following keywords: · never--Do not calculate threshold violations (the default). · immediate--When the response time exceeds the rising over threshold or drops below the falling threshold, immediately perform the action defined by action-type. · consecutive [occurrences]--When the response time exceeds the rising threshold consecutively 5 times or drops below the falling threshold consecutively 5 times, perform the action defined by action-type. Optionally specify the number of consecutive occurrences. The default is 5. · xofy [x-value y-value]--When the response time exceeds the rising threshold 5 out of the last 5 times or drops below the falling threshold 5 out of the last 5 times, perform the action defined by action-type. Optionally specify the number of violations that must occur and the number that must occur within a specified number. The default is 5 for both x-value and y-value.
	· average [attempts]--When the average of the last 5 response times exceeds the rising threshold or when the average of the last 5 response times drops below the falling threshold, perform the action defined by action-type. Optionally specify the number of operations to average. The default is the average of the last 5 response time operations. For example: if the probe's threshold is 5000 ms and the probe's last 3 attempts results are 6000, 6000, and 5000 ms, the average would be 6000+6000+5000=17000/3>5000, thus violating the 5000-ms threshold.
action-type option	(Optional) Specify what action or combination of actions the probe performs when you configure connection-loss-enable or timeout-enable, or threshold events occur. For the action-type to occur for threshold events, the threshold-type must be defined to anything other than never. Option can be one of the following keywords: · none--No action is taken. · trapOnly--Send an SNMP trap on both over and falling threshold violations. · nmvtOnly--Send an SNA NMVT Alert on over threshold violation and an SNA NMVT Resolution on falling threshold violations. · triggerOnly--Have one or more target probe's operational state make the transition from "pending" to "active" on over (and falling) threshold violations. The target probes are defined with the rtr reaction-trigger command. A target probe will continue until its life expires as specified by the target probe's life value configured with the rtr schedule global configuration command. A triggered target probe must finish its life before it can be triggered again. · trapAndMmvt--Send a combination of trapOnly and nmvtOnly. · trapAndTrigger--Send a combination of trapOnly and triggerOnly. · nmvtAndTrigger--Send a combination of nmvtOnly and triggerOnly. · trapNmvtAndTrigger--Send a combination of trapOnly, nmvtOnly, and triggerOnly.

Default

No reactions are generated.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Triggers are used for diagnostics purposes and are not used in normal operation.

You can use triggers to assist you in determining where delays are happening in the network when excessive delays are being seen on an end-to-end basis.

The reaction applies only to attempts to the target (that is, attempts to any hops along the path in pathEcho do not generate reactions).

Note Keywords are not case sensitive and are shown in mixed case for readability only.

Example

In the following example, probe 19 sends an SNMP trap when there is an over or falling threshold violation:

rtr reaction-configuration 19 threshold-type immediate action-type trapOnly

Figure 2 shows that an alert (rising trap) would be issued immediately when the response time exceeds the rising threshold and a resolution (falling trap) would be issued immediately when the response time drops below the falling threshold.

Figure 2: Example of Rising and Falling Thresholds

Related Commands

rtr
rtr reaction-trigger
threshold
timeout

rtr reaction-trigger

To define a second response time reporter probe to make the transition from a "pending" state to an "active" state when one of the trigger action-type options are defined with the rtr reaction-configuration global configuration command, use the rtr reaction-trigger global configuration command. Use the no form of this command to remove the trigger combination.

rtr reaction-trigger probe target-probe
no rtr reaction-trigger probe

Syntax Description

probe	Number of the probe in the "active" state that has the action-type set with the rtr reaction-configuration global configuration command.
target-probe	Number of the probe in the "pending" state that is waiting to be triggered with the rtr global configuration command.

Default

None

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Triggers are usually used for diagnostics purposes and are not used in normal operation.

Example

In the following example, probe 1's state is changed from pending state to active state when probe 2's action-type occurs:

rtr reaction-trigger 2 1

Related Commands

rtr
rtr reaction-configuration
rtr schedule

rtr reset

To perform a shutdown and restart of the response time reporter, use the rtr reset global configuration command.

rtr reset

Syntax Description

This command has no arguments or keywords.

Default

None

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Caution Use the rtr reset command only in extreme situations such as the incorrect configuration of a number of probes.

The rtr reset command stops all probes, clears response time reporter configuration information, and returns the response time reporter feature to the startup condition. This command does not reread the response time reporter configuration stored in startup-config in NVRAM. You must retype the configuration or perform a config memory command.

Example

The following example illustrates how to reset the response time reporter feature:

rtr reset

rtr schedule

To configure the time parameters for a response time reporter probe, use the rtr schedule global configuration command. Use the no form of this command to stop the probe and restart it with the default parameters (that is, pending).

rtr schedule probe [life seconds] [start-time {pending | now | hh:mm [month day |
day month]}] [ageout seconds]
no rtr schedule probe

Syntax Description

probe	Number of the response time reporter probe to schedule.
life seconds	(Optional) Number of seconds the probe actively collects information. The default is 3600 seconds (one hour).
start-time	(Optional) Time when the probe starts collecting information. If the start-time is not specified, no information is collected until the start-time is configured or a trigger occurs that performs a start-time now.
pending	No information is collected. This is the default value.
now	Information is immediately collected.
hh:mm	Information is collected at the specified time (use a 24-hour clock). The time is the current day if you do not specify the month and day.
month	(Optional) Name of the month, any characters in a unique string. If month is not specified, the current month is used. This requires a day.
day	Number of the day in the range 1 to 31. If day is not specified, the current day is used. This requires a month.
ageout seconds	(Optional) Number of seconds to keep the probe when it is not actively collecting information. The default is 0 seconds (never ages out).

Default

Place the probe in a pending state (that is, the probe is started but not actively collecting information).

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

After you schedule the probe with the rtr schedule command, you cannot change the probe's configuration (with the rtr global configuration command). To change the probe's configuration, use the no form of the rtr global command and reenter the configuration information.

If the probe is in a pending state, you can define the conditions under which the probe makes the transition from pending to active with the rtr reaction-trigger and rtr reaction-configuration global configuration commands. When the probe is in an active state, it immediately begins collecting information.

The following time line shows the probe's age-out process:

W----------------------X----------------------Y----------------------Z

where:

W is the time the probe was configured with the rtr global configuration command.
X is the probe's start time or start of life (that is, when the probe became "active").
Y is the end of life as configured with the rtr schedule global configuration command (life seconds have counted down to zero).
Z is the probe's age out.

Age out starts counting down at W and Y, is suspended between X and Y, and is reset to its configured size at Y.

It is possible for the probe to age out before it executes (that is, Z can occur before X). To ensure that this does not happen, the difference between the probe's configuration time and start time (X and W) must be less than the age-out seconds.

Note The total RAM required to hold the history and statistics tables is allocated at this time. This is to prevent router memory problems when the router gets heavily loaded and to lower the amount of overhead the feature causes on a router when it is active.

Example

In the following example, probe 25 begins actively collecting data at 3:00 p.m. on April 5. This probe will age out after 12 hours of inactivity, which can be before it starts or after it has finished with its life. When this probe ages out, all configuration information for the probe is removed (that is, the configuration information is no longer in the running-config in RAM.

rtr schedule 25 life 43200 start-time 15:00 apr 5 ageout 43200

Related Commands

rtr
rtr reaction-configuration
rtr reaction-trigger

samples-of-history-kept

To set the number of entries kept in the history table per bucket for the response time reporter probe, use the samples-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.

samples-of-history-kept samples
no samples-of-history-kept

Syntax Description

samples

Number of entries kept in the history table per bucket. The default is 16 entries for type pathEcho and 1 entry for type echo.

Default

16 entries for type pathEcho

1 entry for type echo

Command Mode

Response time reporter configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Use the samples-of-history-kept command to control how many entries are saved in the history table. To control the type of information that gets saved in the history table, use the filter-for-history command. To set how many buckets get created in the history table, use the buckets-of-history-kept command.

Note Collecting history increases the usage of RAM. Only collect history when you think there is a problem. For general network response time information, use statistics.

Example

In the following example, ten entries are kept in the history table for each of the of probe's three lives:

rtr 1
 type pathecho protocol ipIcmpEcho 172.16.1.176
 lives-of-history-kept 3
 samples-of-history-kept 10

Related Commands

buckets-of-history-kept
filter-for-history
lives-of-history-kept
rtr

scheduler allocate

To guarantee CPU time for processes, use the scheduler allocate global configuration command on the Cisco 7200 series and Cisco 7500 series. The no form of this command restores the default.

scheduler allocate interrupt-time process-time
no scheduler allocate

Syntax Description

interrupt-time	Integer (in microseconds) that limits the maximum number of microseconds to spend on fast switching within any one network interrupt context. The range is 400 to 60000 microseconds. The default is 4000 microseconds.
process-time	Integer (in microseconds) that guarantees the minimum number of microseconds to spend at the process level when network interrupts are disabled. The range is 100 to 4000. The default is 200 microseconds.

Default

Approximately 5 percent of the CPU is available for process tasks.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

This command applies to the Cisco 7200 series and Cisco 7500 series.

Caution Cisco recommends that you do not change the default values.

Example

The following example makes 20 percent of the CPU available for process tasks:

scheduler allocate 2000 500

Related Command

scheduler interval

scheduler interval

To control the maximum amount of time that can elapse without running system processes, use the scheduler interval global configuration command. The no form of this command restores the default.

scheduler interval milliseconds
no scheduler interval

Syntax Description

milliseconds

Integer that specifies the interval, in milliseconds. The minimum interval that you can specify is 500 milliseconds; there is no maximum value.

Default

High-priority operations are allowed to use as much of the central processor as needed.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The normal operation of the network server allows the switching operations to use as much of the central processor as is required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, give priority to the system process scheduler. High-priority operations are allowed to use as much of the central processor as needed.

On the Cisco 7200 series and Cisco 7500 series, use the scheduler allocate global configuration command.

Example

The following example changes the low-priority process schedule to an interval of 750 milliseconds:

scheduler interval 750

Related Command

scheduler allocate

service decimal-tty

To specify that line numbers be displayed and interpreted as decimal numbers rather than octal numbers, use the service decimal-tty global configuration command. Use the no form of this command to restore the default.

service decimal-tty
no service decimal-tty

Syntax Description

This command has no arguments or keywords.

Default

Decimal numbers on the 500-CS and Cisco 2500 Series.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

The following example shows how to display decimal rather than octal line numbers:

service decimal-tty

service exec-wait

To delay the startup of the EXEC on noisy lines, use the service exec-wait global configuration command. Use the no form of this command to disable this feature.

service exec-wait
no service exec-wait

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

This command delays startup of the EXEC until the line has been idle (no traffic seen) for 3 seconds. The default is to enable the line immediately on modem activation.

This command is useful on noisy modem lines or when a modem attached to the line is configured to ignore MNP or V.42 negotiations, and MNP or V.42 modems may be dialing in. In these cases, noise or MNP/V.42 packets may be interpreted as usernames and passwords, causing authentication failure before the user gets a chance to type a username/password. The command is not useful on non-modem lines or lines without some kind of login configured.

Example

The following example delays the startup of the EXEC:

service exec-wait

service finger

To allow Finger protocol requests (defined in RFC 742) to be made of the network server, use the service finger global configuration command. This service is equivalent to issuing a remote show users command. Use the no form of this command to remove this service.

service finger
no service finger

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

The following is an example of how to disable the Finger protocol:

no service finger

service hide-telnet-address

To hide addresses while trying to establish a Telnet session, use the service hide-telnet-address global configuration command. Use the no form of this command to remove this service.

service hide-telnet-address
no service hide-telnet-address

Syntax Description

This command has no arguments or keywords.

Default

Addresses are displayed.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

When you attempt to connect to a device, the router displays addresses and other messages (for example, Trying router1 (171.69.1.154, 2008)...). With the hide feature, the router suppresses the display of the address (for example, Trying router1 address #1...). The router continues to display all other messages that would normally display during a connection attempt, such as detailed error messages if the connection was not successful.

The hide feature improves the functionality of the busy-message feature. When you configure only the busy-message command, the normal messages generated during a connection attempt are not displayed; only the busy-message is displayed. When you use the hide and busy features together you can customize the information displayed during Telnet connection attempts. When you configure the service hide-telnet-address command and the busy-message command, the router suppresses the address and displays the message specified with the busy-message command if the connection attempt is not successful.

Example

The following example shows how to hide Telnet addresses:

service hide-telnet-address

Related Command

A dagger (⁺) indicates that the command is documented outside this chapter.

busy-message^⁺

service nagle

To enable the Nagle congestion control algorithm, use the service nagle global configuration command. Use the no form of this command to disable this feature.

service nagle
no service nagle

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

When using a standard TCP implementation to send keystrokes between machines, TCP tends to send one packet for each keystroke typed. On larger networks, many small packets use up bandwidth and contribute to congestion.

John Nagle's algorithm (RFC 896) helps alleviate the small-packet problem in TCP. In general, it works this way: The first character typed after connection establishment is sent in a single packet, but TCP holds any additional characters typed until the receiver acknowledges the previous packet. Then the second, larger packet is sent, and additional typed characters are saved until the acknowledgment comes back. The effect is to accumulate characters into larger chunks, and pace them out to the network at a rate matching the round-trip time of the given connection. This method is usually a good for all TCP-based traffic. However, do not use the service nagle command if you have XRemote users on X Window sessions.

Example

The following example enables the Nagle algorithm:

service nagle

service prompt config

To display the configuration prompt (config), use the service prompt config global configuration command. Use the no form of this command to remove the configuration prompt.

service prompt config
no service prompt config

Syntax Description

This command has no arguments or keywords.

Default

Router(config)#

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

Examples

In the following example, notice how the configuration prompt varies, depending on what subdivision of configuration mode you are using:

Router#config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface ethernet 0
Router(config-if)#line config 0
Router(config-line)#router rip
Router(config-router)#map-list muruga 
Router(config-map-list)#map-class atm bar
Router(config-map-class)#exit
Router(config)#exit
Router#

Related Commands

hostname
prompt

service slave-log

To allow slave Versatile Interface Processor (VIP) cards to log important error messages to the console, use the service slave-log global configuration command. Use the no form of this command to disable slave logging.

service slave-log
no service slave-log

Syntax Description

This command has no arguments or keywords.

Default

This command is enabled by default.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

This command allows slave slots to log error messages of level 2 or higher (critical, alerts, and emergencies).

Examples

The following example logs important messages from the slave cards to the console:

service slave-log

The following example illustrates sample output when this command is enabled:

%IPC-5-SLAVELOG: VIP-SLOT2:
 IPC-2-NOMEM: No memory available for IPC system initialization

The first line indicates which slot sent the message. The second line contains the error message.

service tcp-keepalives-in

To generate keepalive packets on idle incoming network connections (initiated by the remote host), use the service tcp-keepalives-in global configuration command. The no form of this command with the appropriate keyword disables the keepalives.

service tcp-keepalives-in
no service tcp-keepalives-in

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

The following example generates keepalives on incoming TCP connections:

service tcp-keepalives-in

service tcp-keepalives-out

To generate keepalive packets on idle outgoing network connections (initiated by a user), use the service tcp-keepalives-out global configuration command. The no form of this command with the appropriate keyword disables the keepalives.

service tcp-keepalives-out
no service tcp-keepalives-out

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Example

The following example generates keepalives on outgoing TCP connections:

service tcp-keepalives-out

service tcp-small-servers

To access minor TCP/IP services available from hosts on the network, use the service tcp-small-servers command. Use the no form of the command to disable these services.

service tcp-small-servers
no service tcp-small-servers

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

By default, the TCP servers for Echo, Discard, Chargen, and Daytime services are enabled.

When you disable the minor TCP/IP servers, access to the Echo, Discard, Chargen, and Daytime ports cause the Cisco IOS software to send a TCP RESET packet to the sender and discard the original incoming packet.

Note Unlike defaults for other commands, this command will display when you perform show running config to display current settings whether or not you have changed the default using the no service tcp-small-servers command.

Example

The following example enables minor TCP/IP services available from the network:

service tcp-small-servers

service telnet-zero-idle

To set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zero-idle global configuration command. Use the no form of this command to disable this feature.

service telnet-zero-idle
no service telnet-zero-idle

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Normally, data sent to noncurrent Telnet connections is accepted and discarded. When service telnet-zero-idle is enabled, if a session is suspended (that is, some other connection is made active or the EXEC is sitting in command mode), the TCP window is set to zero. This action prevents the remote host from sending any more data until the connection is resumed. Use this command when it is important that all messages sent by the host be seen by the users and the users are likely to use multiple sessions.

Do not use this command if your host will eventually time out and log out a TCP user whose window is zero.

Example

The following example sets the TCP window to zero when the Telnet connection is idle:

service telnet-zero-idle

Related Command

A dagger (⁺) indicates that the command is documented outside this chapter.

resume^⁺

service timestamps

To configure the system to timestamp debugging or logging messages, use one of the service timestamps global configuration commands. Use the no form of this command to disable this service.

service timestamps type [uptime]
service timestamps type datetime [msec] [localtime] [show-timezone]
no service timestamps type

Syntax Description

type	Type of message to timestamp: debug or log.
uptime	(Optional) Timestamp with time since the system was rebooted.
datetime	Timestamp with the date and time.
msec	(Optional) Include milliseconds in the date and timestamp.
localtime	(Optional) Timestamp relative to the local time zone.
show-timezone	(Optional) Include the time zone name in the timestamp.

Default

No timestamping.

If service timestamps is specified with no arguments or keywords, default is service timestamps debug uptime.

The default for service timestamps type datetime is to format the time in UTC, with no milliseconds and no time zone name.

The command no service timestamps by itself disables timestamps for both debug and log messages.

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Timestamps can be added to either debugging or logging messages independently. The uptime form of the command adds timestamps in the format HHHH:MM:SS, indicating the time since the system was rebooted. The datetime form of the command adds timestamps in the format MMM DD HH:MM:SS, indicating the date and time according to the system clock. If the system clock has not been set, the date and time are preceded by an asterisk (*) to indicate that the date and time are probably not correct.

Examples

The following example enables timestamps on debugging messages, showing the time since reboot:

service timestamps debug uptime

The following example enables timestamps on logging messages, showing the current time and date relative to the local time zone, with the time zone name included:

service timestamps log datetime localtime show-timezone

Related Commands

A dagger (⁺) indicates that the command is documented in the Debug Command Reference.

clock set
debug ^⁺ntp

service udp-small-servers

To access minor User Datagram Protocol (UDP) services available from hosts on the network, use the service udp-small-servers command. Use the no form of the command to disable these services.

service udp-small-servers
no service udp-small-servers

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Global configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

By default the UPD servers for Echo, Discard, and Chargen services are enabled.

When you disable the servers, access to Echo, Discard, and Chargen ports causes the Cisco IOS software to send an "ICMP port unreachable" message to the sender and discard the original incoming packet.

Example

The following example disables minor UDP services on the router:

no service udp-small-servers

show aliases

To display all alias commands, or the alias commands in a specified mode, use the show aliases EXEC command.

show aliases [mode]

Syntax Description

mode

(Optional) Command mode. See Table 61 in the description of the alias command for acceptable options for the mode argument.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

All of the modes listed in Table 61 have their own prompts, except for the null interface mode. For example, the prompt for interface configuration mode is Router(config-if).

Sample Display

The following is sample output from the show aliases exec commands. The aliases configured for commands in EXEC mode are displayed.

Router# show aliases exec
Exec mode aliases:
  h                    help
  lo                   logout
  p                    ping
  r                    resume
  s                    show
  w                    where

Related Command

alias

show buffers

Use the show buffers EXEC command to display statistics for the buffer pools on the network server.

show buffers [type number | alloc [dump]]

Syntax Description

type number	(Optional) Displays interface pool information. If the specified interface type and number has its own buffer pool, displays information for that pool. Value of type can be ethernet, serial, tokenring, fddi, bri, atm, e1, t1.
alloc	(Optional) Displays a brief listing of all allocated buffers.
dump	(Optional) Dumps all allocated buffers. This keyword must be used with the alloc keyword, not by itself.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Displays

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

Router# show buffers
Buffer elements:
     398 in free list (500 max allowed)
     1266 hits, 0 misses, 0 created
 
Public buffer pools:
Small buffers, 104 bytes (total 50, permanent 50):
     50 in free list (20 min, 150 max allowed)
     551 hits, 0 misses, 0 trims, 0 created
Middle buffers, 600 bytes (total 25, permanent 25):
     25 in free list (10 min, 150 max allowed)
     39 hits, 0 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 50, permanent 50):
     49 in free list (5 min, 150 max allowed)
     27 hits, 0 misses, 0 trims, 0 created
VeryBig buffers, 4520 bytes (total 10, permanent 10):
     10 in free list (0 min, 100 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
Large buffers, 5024 bytes (total 0, permanent 0):
     0 in free list (0 min, 10 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
Huge buffers, 18024 bytes (total 0, permanent 0):
     0 in free list (0 min, 4 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
          
Interface buffer pools:
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Ethernet1 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Serial0 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Serial1 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
TokenRing0 buffers, 4516 bytes (total 48, permanent 48):
     0 in free list (0 min, 48 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
TokenRing1 buffers, 4516 bytes (total 32, permanent 32):
     32 in free list (0 min, 48 max allowed)
     16 hits, 0 fallbacks
0 failures (0 no memory)

Table 74 describes significant fields shown in the display.

**Table 74: Show Buffers Field Descriptions (Continued)**
Field	Description
Buffer elements	Buffer elements are small structures used as placeholders for buffers in internal operating system queues. Buffer elements are used when a buffer may need to be on more than one queue.
Free list	Total number of the currently unallocated buffer elements.
Max allowed	Maximum number of buffers that are available for allocation.
Hits	Count of successful attempts to allocate a buffer when needed.
Misses	Count of buffer allocation attempts that resulted in growing the buffer pool to allocate a buffer.
Created	Count of new buffers created to satisfy buffer allocation attempts when the available buffers in the pool have already been allocated.
Public buffer pools:
Small buffers	Buffers that are 104 bytes long.
Middle buffers	Buffers that are 600 bytes long.
Big buffers	Buffers that are 1524 bytes long.
VeryBig buffers	Buffers that are 4520 bytes long.
Large buffers	Buffers that are 5024 bytes long.
Huge buffers	Buffers that are 18024 bytes long.
Total	Total number of this type of buffer.
Permanent	Number of these buffers that are permanent.
Free list	Number of available or unallocated buffers in that pool.
Min	Minimum number of free or unallocated buffers in the buffer pool
Max allowed	Maximum number of free or unallocated buffers in the buffer pool
Hits	Count of successful attempts to allocate a buffer when needed.
Misses	Count of buffer allocation attempts that resulted in growing the buffer pool in order to allocate a buffer.
Trims	Count of buffers released to the system because they were not being used. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
Created	Count of new buffers created in response to misses. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
Interface buffer pools:
Total	Total number of this type of buffer.
Permanent	Number of these buffers that are permanent.
Free list	Number of available or unallocated buffers in that pool.
Min	Minimum number of free or unallocated buffers in the buffer pool.
Max allowed	Maximum number of free or unallocated buffers in the buffer pool.
Hits	Count of successful attempts to allocate a buffer when needed.
Fall backs	Count of buffer allocation attempts that resulted in falling back to the public buffer pool that is the smallest pool at least as big as the interface buffer pool.
Max Cache Size	Maximum number of buffers from that interface's pool that can be in that interface buffer pool's cache. Each interface buffer pool has its own cache. These are not additional to the permanent buffers; they come from the interface's buffer pools. Some interfaces place all of their buffers from the interface pool into the cache. In this case, it is normal for the free list to display 0.
Failures	Total number of allocation requests that have failed because no buffer was available for allocation; the datagram was lost. Such failures normally occur at interrupt level.
(no memory)	Number of failures that occurred because no memory was available to create a new buffer.

The following is sample output from the show buffers command with an interface type and number:

Router# show buffers Ethernet 0
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache

The following is sample output from the show buffers command when alloc is specified:

Router# show buffers alloc
Buffer elements:
     398 in free list (500 max allowed)
     1266 hits, 0 misses, 0 created
 
Public buffer pools:
Small buffers, 104 bytes (total 50, permanent 50):
     50 in free list (20 min, 150 max allowed)
     551 hits, 0 misses, 0 trims, 0 created
Middle buffers, 600 bytes (total 25, permanent 25):
     25 in free list (10 min, 150 max allowed)
     39 hits, 0 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 50, permanent 50):
     49 in free list (5 min, 150 max allowed)
     27 hits, 0 misses, 0 trims, 0 created
VeryBig buffers, 4520 bytes (total 10, permanent 10):
     10 in free list (0 min, 100 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
Large buffers, 5024 bytes (total 0, permanent 0):
     0 in free list (0 min, 10 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
Huge buffers, 18024 bytes (total 0, permanent 0):
     0 in free list (0 min, 4 max allowed)
     0 hits, 0 misses, 0 trims, 0 created
          
Interface buffer pools:
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Ethernet1 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Serial0 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
Serial1 buffers, 1524 bytes (total 64, permanent 64):
     16 in free list (0 min, 64 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
TokenRing0 buffers, 4516 bytes (total 48, permanent 48):
     0 in free list (0 min, 48 max allowed)
     48 hits, 0 fallbacks
     16 max cache size, 16 in cache
TokenRing1 buffers, 4516 bytes (total 32, permanent 32):
     32 in free list (0 min, 48 max allowed)
     16 hits, 0 fallbacks
0 failures (0 no memory)
Address  PakAddr  Data     Off Data  Pool  Ref Link Enc     Flags Output  Input
                  Area     set Size        Cnt Type Type    (Hex) Idb     Idb
--------------------------------------------------------------------------------
604B37A0 604B37C0 40004A38  62    60 Big     1   65    3        0 Et0          
604C6DA0 604C6DC0 40007038  84     0 Ether   1    0    0        0              
604C6F60 604C6F80 400076E4  84     0 Ether   1    0    0        0              
604C7120 604C7140 40007D90  84     0 Ether   1    0    0        0              
604C72E0 604C7300 4000843C  84     0 Ether   1    0    0        0              
604C74A0 604C74C0 40008AE8  84     0 Ether   1    0    0        0              
604C7660 604C7680 40009194  84     0 Ether   1    0    0        0              
604C7820 604C7840 40009840  84     0 Ether   1    0    0        0              
.
.
.

show c7200

Use the show c7200 EXEC command to display information about the CPU and midplane for Cisco 7200 series routers.

show c7200

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

You can use the output of this command to determine whether the hardware version level and upgrade is current. The information is generally useful for diagnostic tasks performed by technical support only.

Sample Display

The following is sample output from the show c7200 command:

router# show c7200
C7200 Network IO Interrupt Throttling:
 throttle count=0, timer count=0
 active=0, configured=0
 netint usec=3999, netint mask usec=200
 
C7200 Midplane EEPROM:
        Hardware revision 1.2           Board revision A0
        Serial number     2863311530    Part number    170-43690-170
        Test history      0xAA          RMA number     170-170-170
        MAC=0060.3e28.ee00, MAC Size=1024
        EEPROM format version 1, Model=0x6
        EEPROM contents (hex):
          0x20: 01 06 01 02 AA AA AA AA AA AA AA AA 00 60 3E 28
          0x30: EE 00 04 00 AA AA AA AA AA AA AA 50 AA AA AA AA
 
C7200 CPU EEPROM:
        Hardware revision 2.0           Board revision A0
        Serial number     3509953       Part number     73-1536-02
        Test history      0x0           RMA number      00-00-00
        EEPROM format version 1
        EEPROM contents (hex):
          0x20: 01 15 02 00 00 35 8E C1 49 06 00 02 00 00 00 00
          0x30: 50 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF

show calendar

To display the calendar hardware setting for the Cisco 7000 series, Cisco 7200 series, or Cisco 4500 series, use the show calendar EXEC command:

show calendar

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

You can compare the time and date shown with this command with the time and date listed via the show clock command to verify that the calendar and system clock are in sync with each other. The time displayed is relative to the configured time zone.

Sample Display

In the following sample display, the hardware calendar indicates the timestamp of 12:13:44 p.m. on Friday, July 19, 1996:

Router# show calendar
12:13:44 PST Fri Jul 19 1996

Related Command

show clock

show cdp

To display global CDP information, including timer and hold-time information, use the show cdp privileged EXEC command.

show cdp

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Display

The following is sample output from the show cdp command. Global CDP timer and hold-time parameters are set to the defaults of 60 and 180 seconds, respectively.

Router# show cdp
Global CDP information:
        Sending CDP packets every 60 seconds
        Sending a holdtime value of 180 seconds

Related Commands

cdp holdtime
cdp timer
show cdp entry
show cdp neighbors

show cdp entry

To display information ab out a neighbor device listed in the CDP table, use the show cdp entry privileged EXEC command.

show cdp entry {* | entry-name [protocol | version]}

Syntax Description

*	Shows all of the CDP neighbors.
entry-name	Name of neighbor about which you want information. You can enter an aserisk () at the end of an entry-name, such as `show cdp entry dev`, which would show information about the neighbor, device.cisco.com.
protocol	(Optional) Limits the display to information about the protocols enabled on a router.
version	(Optional) Limits the display to information about the version of software running on the router.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Displays

The following is sample output from the show cdp entry command with no limits. Information about the neighbor device.cisco.com is displayed, including device ID, address and protocol, platform, interface, hold time, and version.

Router# show cdp entry device.cisco.com
Device ID: device.cisco.com
Entry address(es): 
  IP address: 192.168.68.18
  CLNS address: 490001.1111.1111.1111.00
  DECnet address: 10.1
Interface: Ethernet0, Port ID (outgoing port): Ethernet0
Holdtime: 155 sec
Version:
GS Software (GS3), Experimental Version 10.2(10302) [asmith 161]
Copyright (c) 1986-1994 by cisco Systems, Inc.
Compiled Mon 07-Nov-94 14:34

The following is sample output from the show cdp entry privilege command. Only information about the protocols enabled on neon-cisco.com is displayed.

Router# show cdp entry device.cisco.com protocol
Protocol information for device.cisco.com:
  IP address: 192.168.68.18
  CLNS address: 490001.1111.1111.1111.00
  DECnet address: 10.1

The following is sample output from the show cdp entry version command. Only information about the version of software running on device.cisco.com is displayed.

Router# show cdp entry device.cisco.com version 
Version information for device.cisco.com:
  GS Software (GS3), Experimental Version 10.2(10302) [asmith 161]
Copyright (c) 1986-1994 by cisco Systems, Inc.
Compiled Mon 07-Nov-94 14:34

Related Command

show cdp neighbors

show cdp interface

To display information about the interfaces on which CDP is enabled, use the show cdp interface privileged EXEC command.

show cdp interface [type number]

Syntax Description

type	(Optional) Type of interface about which you want information.
number	(Optional) Number of the interface about which you want information.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Displays

The following sample output form the show cdp interface command. Status information and information about CDP timer and hold time settings is displayed for all interfaces on which CDP is enabled.

Router# show cdp interface
Serial0 is up, line protocol is up, encapsulation is SMDS
  Sending CDP packets every 60 seconds
  Holdtime is 180 seconds
Ethernet0 is up, line protocol is up, encapsulation is ARPA
  Sending CDP packets every 60 seconds
  Holdtime is 180 seconds

The following is sample output from the show cdp interface command with an interface specified. Status information and information about CDP timer and holdtime settings is displayed for Ethernet interface 0 only.

Router# show cdp interface ethernet 0
Ethernet0 is up, line protocol is up, encapsulation is ARPA
  Sending CDP packets every 60 seconds
  Holdtime is 180 seconds

s how cdp neighbors

To display information about neighbors, use the show cdp neighbors privileged EXEC command.

show cdp neighbors [type number] [detail]

Syntax Description

type	(Optional) Type of the interface connected to the neighbors about which you want information.
number	(Optional) Number of the interface connected to the neighbors about which you want information.
detail	(Optional) Displays detailed information about a neighbor (or neighbors) including network address, enabled protocols, hold time, and software version.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Displays

The following is sample output from the show cdp neighbors command. Device ID, interface type and number, holdtime settings, capabilities, platform, and port ID information about neighbors is displayed.

Router# show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP
Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
device.cisco.com      Eth 0          151         R T        AGS       Eth 0
device.cisco.com      Ser 0          165         R T        AGS       Ser 3

The following is sample output from the show cdp neighbors detail command. Additional detail is shown about neighbors, including network address, enabled protocols, and software version:

Router# show cdp neighbors detail 
Device ID: device.cisco.com
Entry address(es): 
  IP address: 192.168.68.18
  CLNS address: 490001.1111.1111.1111.00
  DECnet address: 10.1
Platform: AGS, Capabilities: Router Trans-Bridge 
Interface: Ethernet0, Port ID (outgoing port): Ethernet0
Holdtime: 143 sec
Version:
GS Software (GS3), Experimental Version 10.2(10302) [asmith 161]
Copyright (c) 1986-1994 by cisco Systems, Inc.
Compiled Mon 07-Nov-94 14:34

Related Command

show cdp entry

show cdp traffic

To display traffic information from the CDP table, use the show cdp traffic privileged EXEC command.

show cdp traffic

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

Sample Display

The following is sample output from the show cdp traffic command.

Router# show cdp traffic
CDP counters:
        Packets output: 94, Input: 75
        Hdr syntax: 0, Chksum error: 0, Encaps failed: 0
        No memory: 0, Invalid packet: 0, Fragmented: 0

In this example, traffic information is displayed including the numbers of packets sent, the number of packets received, header syntax, checksum errors, failed encapsulations, memory problems, and invalid and fragmented packets is displayed. Header syntax indicates the number of packets CDP receives with that have an invalid header format.

show clock

To display the system clock, use the show clock EXEC command.

show clock [detail]

Syntax Description

detail

(Optional) Indicates the clock source (NTP, VINES, 7000 calendar, 7200 calendar, and so forth) and the current summer-time setting (if any).

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The system clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the system clock has been set by a timing source (Cisco 7000 calendar, NTP, VINES, and so forth), 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 clock when the peers' time is invalid.

The symbol that precedes the show clock display indicates the following:

Symbol	Description
*	Time is not authoritative.
(blank)	Time is authoritative.
.	Time is authoritative, but NTP is not synchronized.

Sample Display

The following sample output shows that the current clock is authoritative and that the time source is NTP:

Router# show clock detail
15:29:03.158 PST Mon Mar 1 1993
Time source is NTP
Router#

Related Commands

clock set
show calendar

show context

Use the show context EXEC command to display information stored in NVRAM when the router crashes. This command only works on the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series platforms.

show context

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

The display from the show context command includes the following information:

Reason for the system reboot
Stack trace
Software version
The signal number, code, and router uptime information
All the register contents at the time of the crash

This information is of use only to your technical support representative in analyzing crashes in the field. It is included here in case you need to read the displayed statistics to an engineer over the phone.

Sample Display

The following is sample output from the show context command following a system failure:

Router> show context
System was restarted by error - a Software forced crash, PC 0x60189354
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Image text-base: 0x60010900, data-base: 0x6073E000
Stack trace from system failure:
FP: 0x60AEA798, RA: 0x60189354
FP: 0x60AEA798, RA: 0x601853CC
FP: 0x60AEA7C0, RA: 0x6015E98C
FP: 0x60AEA7F8, RA: 0x6011AB3C
FP: 0x60AEA828, RA: 0x601706CC
FP: 0x60AEA878, RA: 0x60116340
FP: 0x60AEA890, RA: 0x6011632C
Fault History Buffer:
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Signal = 23, Code = 0x24, Uptime 00:04:19
$0 : 00000000, AT : 60930120, v0 : 00000032, v1 : 00000120
a0 : 60170110, a1 : 6097F22C, a2 : 00000000, a3 : 00000000
t0 : 60AE02A0, t1 : 8000FD80, t2 : 34008F00, t3 : FFFF00FF
t4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 11010132
s0 : 00000006, s1 : 607A25F8, s2 : 00000001, s3 : 00000000
s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 6097F755
t8 : 600FABBC, t9 : 00000000, k0 : 30408401, k1 : 30410000
gp : 608B9860, sp : 60AEA798, s8 : 00000000, ra : 601853CC
EPC : 60189354, SREG : 3400EF03, Cause : 00000024

Related Commands

show processes
show stacks

show debugging

To display information about the types of CDP debugging that are enabled for your router, use the show debugging privileged EXEC command.

show debugging

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

Sample Display

The following is sample output from the show debugging command. In this example, all three types of CDP debugging are enabled.

Router# show debugging
CDP:
  CDP packet info debugging is on
  CDP events debugging is on
  CDP neighbor info debugging is on
CDP-PA: Packet received from neon.cisco.com on interface Ethernet0
CDP-EV: Encapsulation on interface Serial0 failed
CDP-AD: Aging entry for neon.cisco.com, on interface Ethernet0

Related Commands

A dagger (⁺) indicates that the command is documented in the Debug Command Reference.

debug cdp adjacency ^⁺debug cdp events ^⁺debug cdp packets ^⁺

show environment

Use the show environment EXEC command to display temperature and voltage information on the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series routers.

show environment [all | last | table]

Syntax Description

all	(Optional) Displays a detailed listing of the power supplies, temperature readings, and voltage readings.
last	(Optional) Displays the reason for the last system shutdown that was related to voltage or temperature and the environmental status at that time.
table	(Optional) Displays the temperature and voltage thresholds and a table that lists the ranges of environmental measurements that are within specification.

Default

If no options are specified, the router displays the date and time that the environmental measurements were last checked and whether the environmental measurements were within specifications. For the Cisco 7500 series, the router displays only measurements that are out of normal range.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Once a minute a routine is run that gets environmental measurements from sensors and stores the output into a buffer. This buffer is displayed on the console when show environment is invoked.

If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is printed to the system console. The system software queries the sensors for measurements once a minute, but warnings for a given test point are printed at most once every hour for sensor readings in the warning range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line within these time segments, an automatic warning message appears on the console. As noted, you can query the environmental status with the show environment command at any time to determine whether a measurement is at the warning or critical tolerance.

If a shutdown occurs because of detection of fatal environmental margins, the last measured value from each sensor is stored in internal nonvolatile memory.

For environmental specifications, refer to the hardware installation and maintenance publication for your individual chassis.

Sample Displays

The following example shows the typical show environment display when there are no warning conditions in the system for the Cisco 7000 series and Cisco 7200 series. This information may vary slightly depending on the platform you are using. The date and time of the query are displayed, along with the data refresh information and a message indicating that there are no warning conditions.

Router> show environment
Environmental Statistics
  Environmental status as of 13:17:39 UTC Thu Jun 6 1996 
  Data is 7 second(s) old, refresh in 53 second(s)
  All Environmental Measurements are within specifications

Table 75 describes the fields shown in the display.

**Table 75: Show Environment Field Descriptions**
Field	Description
Environmental status as of...	Current date and time.
Data is..., refresh in...	Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
Status message	If environmental measurements are not within specification, warning messages are displayed.

Sample Displays for the Cisco 7000 Series

The following are examples of messages that display on the system console when a measurement has exceeded an acceptable margin:

ENVIRONMENTAL WARNING: Air flow appears marginal.
ENVIRONMENTAL WARNING: Internal temperature measured 41.3(C)
ENVIRONMENTAL WARNING: +5 volt testpoint measured 5.310(V)

The system displays the following message if voltage or temperature exceed maximum margins:

SHUTDOWN: air flow problem

In the following example, there have been two intermittent power failures since a router was turned on, and the lower power supply is not functioning. The last intermittent power failure occurred on Monday, June 10, 1996, at 11:07 p.m.

7000# show environment all
Environmental Statistics
  Environmental status as of 23:19:47 UTC Wed Jun 12 1996 
  Data is 6 second(s) old, refresh in 54 second(s)
  WARNING: Lower Power Supply is NON-OPERATIONAL
  Lower Power Supply:700W, OFF     Upper Power Supply: 700W, ON
  Intermittent Powerfail(s): 2     Last on 23:07:05 UTC Mon Jun 10 1996 
  +12 volts measured at  12.05(V)
   +5 volts measured at   4.96(V)
  -12 volts measured at -12.05(V)
  +24 volts measured at  23.80(V)
  Airflow temperature measured at 38(C)
  Inlet temperature measured at 25(C)

Table 76 describes the fields shown in the display.

**Table 76: Show Environment All Field Descriptions for the Cisco 7000**
Field	Description
Environmental status as of...	Date and time of last query.
Data is..., refresh in...	Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
WARNING:	If environmental measurements are not within specification, warning messages are displayed.
Lower Power Supply	Type of power supply installed and its status (On or Off).
Upper Power Supply	Type of power supply installed and its status (On or Off).
Intermittent Powerfail(s)	Number of power hits (not resulting in shutdown) since the system was last booted.
Voltage Specifications	System voltage measurements.
Airflow and inlet temperature	Temperature of air coming in and going out.

The following example is for the Cisco 7000 series router. The router retrieves the environmental statistics at the time of the last shutdown. In this example, the last shutdown was Friday, May 19, 1995, at 12:40 p.m., so the environmental statistics at that time are displayed:

Router# show environment last
Environmental Statistics
  Environmental status as of 14:47:00 UTC Sun May 21 1995 
  Data is 6 second(s) old, refresh in 54 second(s)
  WARNING: Upper Power Supply is NON-OPERATIONAL
LAST Environmental Statistics
  Environmental status as of 12:40:00 UTC Fri May 19 1995 
  Lower Power Supply: 700W, ON     Upper Power Supply: 700W, OFF
  No Intermittent Powerfails
  +12 volts measured at  12.05(V)
   +5 volts measured at   4.98(V)
  -12 volts measured at -12.00(V)
  +24 volts measured at  23.80(V)
 Airflow temperature measured at 30(C)
  Inlet  temperature measured at 23(C)

Table 77 describes the fields shown in the display.

**Table 77: Show Environment Last Field Descriptions for the Cisco 7000**
Field	Description
Environmental status as of...	Current date and time.
Data is..., refresh in...	Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
WARNING:	If environmental measurements are not within specification, warning messages are displayed.
LAST Environmental Statistics	Displays test point values at time of the last environmental shutdown.
Lower Power Supply: Upper Power Supply:	For the Cisco 7000, indicates the status of the two 700W power supplies. For the Cisco 7010, indicates the status of the single 600W power supply.

The following sample output shows the current environmental status in tables that list voltage and temperature parameters. There are three warning messages: one each about the lower power supply, the airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level:

Router> show environment table
Environmental Statistics
  Environmental status as of Mon 11-2-1992 17:43:36
  Data is 52 second(s) old, refresh in 8 second(s)
  WARNING: Lower Power Supply is NON-OPERATIONAL
  WARNING: Airflow temperature has reached CRITICAL level at 73(C)
  WARNING: Inlet temperature has reached WARNING level at 41(C)
Voltage Parameters:
 SENSE        CRITICAL                NORMAL                CRITICAL
-------|--------------------|------------------------|--------------------
+12(V)                    10.20      12.05(V)      13.80
 +5(V)                     4.74       4.98(V)       5.26
-12(V)                   -10.20     -12.05(V)     -13.80
+24(V)                    20.00      24.00(V)      28.00
Temperature Parameters:
 SENSE     WARNING      NORMAL      WARNING      CRITICAL      SHUTDOWN
-------|-------------|------------|-------------|--------------|-----------
Airflow             10           60            70    73(C)    88
Inlet               10           39    41(C)   46             64

Table 78 describes the fields shown in the display.

**Table 78: Show Environment Table Field Descriptions for the Cisco 7000**
Field	Description
SENSE (Voltage Parameters)	Voltage specification for DC line.
SENSE (Temperature Parameters)	Air being measured. Inlet measures the air coming in, and Airflow measures the temperature of the air inside the chassis.
WARNING	System is approaching an out-of-tolerance condition.
NORMAL	All monitored conditions meet normal requirements.
CRITICAL	Out-of-tolerance condition exists.
SHUTDOWN	Processor has detected condition that could cause physical damage to the system.

Sample Displays for the Cisco 7200 Series

The system displays the following message if the voltage or temperature enters the "Warning" range:

%ENVM-4-ENVWARN: Chassis outlet 3 measured at 55C/131F

The system displays the following message if the voltage or temperature enters the "Critical" range:

%ENVM-2-ENVCRIT: +3.45 V measured at +3.65 V

The system displays the following message if the voltage or temperature exceeds the maximum margins:

%ENVM-0-SHUTDOWN: Environmental Monitor initiated shutdown

The following message is sent to the console if a power supply has been inserted or removed from the system. This message relates only to systems that have two power supplies:

%ENVM-6-PSCHANGE: Power Supply 1 changed from Zytek AC Power Supply to removed

The following message is sent to the console if a power supply has been powered on or off. In the case of the power supply being shut off, this message can be due to the user shutting off the power supply or to a failed power supply. This message relates only to systems that have two power supplies:

%ENVM-6-PSLEV: Power Supply 1 state changed from normal to shutdown

The following is sample output from the show environment all command on the Cisco 7200 series router when there is a voltage warning condition in the system:

7200# show environment all
Power Supplies:
        Power supply 1 is unknown. Unit is off.
        Power supply 2 is Zytek AC Power Supply. Unit is on.
Temperature readings:
        chassis inlet    measured at 25C/77F
        chassis outlet 1 measured at 29C/84F
        chassis outlet 2 measured at 36C/96F
        chassis outlet 3 measured at 44C/111F
Voltage readings:
        +3.45 V measured at +3.83 V:Voltage in Warning range!
        +5.15 V measured at +5.09 V
        +12.15  measured at +12.42 V
        -11.95  measured at -12.10 V

Table 79 describes the fields shown in the display.

**Table 79: Show Environment All Field Descriptions for the Cisco 7200**
Field	Description
Power Supplies:	Current condition of the power supplies including the type and whether the power supply is on or off.
Temperature readings:	Current measurements of the chassis temperature at the inlet and outlet locations.
Voltage readings:	Current measurement of the power supply test points.

The following example is for the Cisco 7200 series router. This example shows the measurements immediately before the last shutdown and the reason for the last shutdown (if appropriate).

7200# show environment last
   chassis inlet      previously measured at 27C/80F
   chassis outlet 1   previously measured at 31C/87F
   chassis outlet 2   previously measured at 37C/98F
   chassis outlet 3   previously measured at 45C/113F
   +3.3 V             previously measured at 4.02
   +5.0 V             previously measured at 4.92
   +12.0 V            previously measured at 12.65
   -12.0 V            previously measured at 11.71
last shutdown reason - power supply shutdown

Table 80 describes the fields shown in the display.

**Table 80: Show Environment Last Field Descriptions for the Cisco 7200**
Field	Description
chassis inlet	Temperature measurements at the inlet area of the chassis.
chassis outlet	Temperature measurements at the outlet areas of the chassis.
voltages	Power supply test point measurements.
last shutdown reason	Possible shutdown reasons are power supply shutdown, critical temperature, and critical voltage.

The following example is for the Cisco 7200 series router. This information lists the temperature and voltage shutdown thresholds for each sensor.

7200# show environment table
Sample Point      LowCritical    LowWarning     HighWarning    HighCritical
chassis inlet                                   40C/104F       50C/122F
chassis outlet 1                                43C/109F       53C/127F
chassis outlet 2                                75C/167F       75C/167F
chassis outlet 3                                55C/131F       65C/149F
+3.45 V           +2.76          +3.10          +3.80          +4.14
+5.15 V           +4.10          +4.61          +5.67          +6.17
+12.15 V          +9.72          +10.91         +13.37         +14.60
-11.95 V          -8.37          -9.57          -14.34         -15.53
Shutdown system at 70C/158F

Table 81 describes the fields shown in the display.

**Table 81: Show Environment Table Field Descriptions for the Cisco 7200**
Field	Description
Sample Point	Area for which measurements are taken.
LowCritical	Level at which a critical message is issued for an out-of-tolerance voltage condition. The system continues to operate; however, the system is approaching shutdown.
LowWarning	Level at which a warning message is issued for an out-of-tolerance voltage condition. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
HighWarning	Level at which a warning message is issued. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
HighCritical	Level at which a critical message is issued. For the chassis, the router is shut down. For the power supply, the power supply is shut down.
Shutdown system at	The system is shut down if the specified temperature is met.

Sample Displays for the Cisco 7500 Series

The sample output for the Cisco 7500 series routers may vary depending on the specific model (for example, the Cisco 7513). The following is sample output from the show environment all command on the Cisco 7500 series router:

7500#show environment all
Arbiter type 1, backplane type 7513 (id 2) 
Power supply #1 is 1200W AC (id 1), power supply #2 is removed (id 7) 
Active fault conditions: none
Fan transfer point: 100%
Active trip points: Restart_Inhibit
15 of 15 soft shutdowns remaining before hard shutdown 
                        1
              0123456789012
Dbus slots:   X     XX    X
card        inlet      hotpoint      exhaust
RSP(6)     35C/95F     47C/116F      40C/104F
RSP(7)     35C/95F     43C/109F      39C/102F
Shutdown temperature source is 'hotpoint' on RSP(6), requested RSP(6) 
+12V measured at 12.31
+5V measured at 5.21
-12V measured at -12.07
+24V measured at 22.08
+2.5 reference is 2.49
PS1 +5V Current      measured at 59.61 A (capacity 200 A) 
PS1 +12V Current     measured at 5.08 A (capacity 35 A) 
PS1 -12V Current     measured at 0.42 A (capacity 3 A) 
PS1 output is 378 W

Table 82 describes the fields shown in the display.

**Table 82: Show Environment All Field Descriptions for the Cisco 7500**
Field	Description
Arbiter type 1	Numbers indicating the arbiter type and backplane type.
Power supply	Number and type of power supply installed in the chassis.
Active fault conditions:	If any fault conditions exist (such as power supply failure, fan failure, and temperature too high), they are listed here.
Fan transfer point:	Software controlled fan speed. If the router is operating below its automatic restart temperature, the transfer point is reduced by 10 percent of the full range each minute. If the router is at or above its automatic restart temperature, the transfer point is increased in the same way.
Active trip points:	Temperature sensor is compared against the values displayed at the bottom of the show environment table command output.
15 of 15 soft shutdowns remaining	When the temperature increases above the "board shutdown" level, a soft shutdown occurs (that is, the cards are shut down, and the power supplies, fans, and CI continue to operate). When the system cools to the restart level, the system restarts. The system counts the number of times this occurs and keeps the up/down cycle from continuing forever. When the counter reaches zero, the system performs a hard shutdown, which requires a power cycle to recover. The soft shutdown counter is reset to its maximum value after the system has been up for 6 hours.
Dbus slots:	Indicates which chassis slots are occupied.
card, inlet, hotpoint, exhaust	Temperature measurements at the inlet, hotpoint, and exhaust areas of the card. The (6) and (7) indicate the slot numbers. Dual-RSP chassis can show two RSPs.
Shutdown temperature source	Indicates which of the three temperature sources is selected for comparison against the "shutdown" levels listed with the show environment table command.
Voltages (+12V, +5V, -12V, +24V, +2.5)	Voltages measured on the backplane.
Power supply current (PS1)	Current measured on the power supply.

The following example is for the Cisco 7500 series router. This example shows the measurements immediately before the last shutdown.

7500#show environment last
 RSP(4) Inlet       previously measured at 37C/98F
 RSP(4) Hotpoint    previously measured at 46C/114F
 RSP(4) Exhaust     previously measured at 52C/125F
 +12 Voltage        previously measured at 12.26
 +5 Voltage         previously measured at 5.17
 -12 Voltage        previously measured at -12.03
 +24 Voltage        previously measured at 23.78

Table 83 describes the fields shown in the display

**Table 83: Show Environment Last Field Descriptions for the Cisco 7500**
Field	Description
RSP(4) Inlet, Hotpoint, Exhaust	Temperature measurements at the inlet, hotpoint, and exhaust areas of the card.
Voltages	Voltages measured on the backplane.

The following example is for the Cisco 7500 series router. This information lists the temperature and voltage thresholds for each sensor. These thresholds indicate when error messages occur. There are two level of messages: warning and critical.

7500#show env table
Sample Point      LowCritical    LowWarning     HighWarning    HighCritical   
RSP(4) Inlet                                    44C/111F       50C/122F       
RSP(4) Hotpoint                                 54C/129F       60C/140F       
RSP(4) Exhaust                                                                
+12 Voltage       10.90          11.61          12.82          13.38          
+5 Voltage        4.61           4.94           5.46           5.70           
-12 Voltage       -10.15         -10.76         -13.25         -13.86         
+24 Voltage       20.38          21.51          26.42          27.65          
2.5 Reference                    2.43           2.51                          
Shutdown boards at           70C/158F
Shutdown power supplies at   76C/168F
Restart after shutdown below 40C/104F

Table 84 describes the fields shown in the display.

**Table 84: Show Environment Table Field Descriptions for the Cisco 7500**
Field	Description
Sample Point	Area for which measurements are taken.
LowCritical	Level at which a critical message is issued for an out-of-tolerance voltage condition. The system continues to operate; however, the system is approaching shutdown.
LowWarning	Level at which a warning message is issued for an out-of-tolerance voltage condition. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
HighWarning	Level at which a warning message is issued. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
HighCritical	Level at which a critical message is issued. For the chassis, the router is shut down. For the power supply, the power supply is shut down.
Shutdown boards at	The card is shut down if the specified temperature is met.
Shutdown power supplies at	The system is shut down if the specified temperature is met.
Restart after shutdown	The system will restart when the specified temperature is met.

show gt64010

Use the show gt64010 EXEC command to display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers.

show gt64010

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

This command displays information about the CPU interface, DRAM/device address space, device parameters, DMA channels, timers and counters, and PCI internal registers. The information is generally useful for diagnostic tasks performed by technical support only.

Sample Display

The following is a partial sample output for the show gt64010 command:

Router# show gt64010
GT64010 Channel 0 DMA:
 dma_list=0x6088C3EC, dma_ring=0x4B018480, dma_entries=256
 dma_free=0x6088CECC, dma_reqt=0x6088CECC, dma_done=0x6088CECC
 thread=0x6088CEAC, thread_end=0x6088CEAC
 backup_thread=0x0, backup_thread_end=0x0
 dma_working=0, dma_complete=6231, post_coalesce_frames=6231
 exhausted_dma_entries=0, post_coalesce_callback=6231
GT64010 Register Dump: Registers at 0xB4000000
CPU Interface:
 cpu_interface_conf   : 0x80030000 (b/s 0x00000380)
 addr_decode_err      : 0xFFFFFFFF (b/s 0xFFFFFFFF)
Processor Address Space :
 ras10_low            : 0x00000000 (b/s 0x00000000)
 ras10_high           : 0x07000000 (b/s 0x00000007)
 ras32_low            : 0x08000000 (b/s 0x00000008)
 ras32_high           : 0x0F000000 (b/s 0x0000000F)
 cs20_low             : 0xD0000000 (b/s 0x000000D0)
 cs20_high            : 0x74000000 (b/s 0x00000074)
 cs3_boot_low         : 0xF8000000 (b/s 0x000000F8)
 cs3_boot_high        : 0x7E000000 (b/s 0x0000007E)
 pci_io_low           : 0x00080000 (b/s 0x00000800)
 pci_io_high          : 0x00000000 (b/s 0x00000000)
 pci_mem_low          : 0x00020000 (b/s 0x00000200)
 pci_mem_high         : 0x7F000000 (b/s 0x0000007F)
 internal_spc_decode  : 0xA0000000 (b/s 0x000000A0)
 bus_err_low          : 0x00000000 (b/s 0x00000000)
 bus_err_high         : 0x00000000 (b/s 0x00000000)
...

show logging

Use the show logging EXEC command to display the state of logging (syslog).

show logging [history]

Syntax Description

history

(Optional) Display information in the syslog history table only.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

This command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled. This command also displays Simple Network Management Protocol (SNMP) configuration parameters and protocol activity.

When you use the optional history keyword, information about the syslog history table is displayed 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.

Sample Display

The following is sample output from the show logging command:

Router# show logging
Syslog logging: enabled
     Console logging: disabled
     Monitor logging: level debugging, 266 messages logged.
     Trap logging: level informational, 266 messages logged.
     Logging to 192.180.2.238
SNMP logging: disabled, retransmission after 30 seconds
    0 messages logged

Table 85 describes significant fields shown in the display.

**Table 85: Show Logging Field Descriptions (Continued)**
Field	Description
Syslog logging	When enabled, system logging messages are sent to a UNIX host that acts as a syslog server; that is, it captures and saves the messages.
Console logging	If enabled, states the level; otherwise, this field displays disabled.
Monitor logging	Minimum level of severity required for a log message to be sent to a monitor terminal (not the console).
Trap logging	Minimum level of severity required for a log message to be sent to a syslog server.
SNMP logging	Shows whether SNMP logging is enabled and the number of messages logged, and the retransmission interval.

The following is sample output from the show logging history command:

Router# show logging history
Syslog History Table: 1 maximum table entry, 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

Table 86 describes the significant fields shown in the display.

**Table 86: Show Logging History Field Descriptions (Continued)**
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 or higher	Level of messages that are stored in the history table and sent to the SNMP server (if SNMP notification is enabled). Set 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. Syslog traps are either enabled or not enabled through the snmp-server enable command.
entry number	Number of the message entry in the history table.
SYS-5-CONFIG_I Configured from console by console	Cisco IOS syslog message consisting of the facility name (SYS) which indicates where the message came from, the severity level (5), the message name (CONFIG_I), and the message text.
timestamp	Time, based on the router's up time, that the message was generated.

Related Command

logging history size

show memory

Use the show memory EXEC command to show statistics about memory, including memory free pool statistics.

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

Syntax Description

memory-type	(Optional) Memory type to display (processor, multibus, io, sram). If type is not specified, statistics for all memory types present are displayed.
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

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

The show memory command displays information about memory available after the system image decompresses and loads.

Sample Displays

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 display of show memory free contains the same types of information as the show memory display, 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 87 describes significant fields shown in the first section of the display.

**Table 87: Show Memory Field Descriptions--First Section (Continued)**
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 88 describes significant fields shown in the second section of the display.

**Table 88: Characteristics of Each Block of Memory--Second Section (Continued)**
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 IO memory blocks. On the Cisco 4000, this command quickly shows how much unused IO 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 sram command displays the free SRAM memory blocks. For the Cisco 4000, this command supports the high-speed static RAM memory pool to make it easier to debug or diagnose problems with allocation or freeing of such memory.

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

Router# show memory sram
Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What
7AE0      38178 72F0    0        0    0       0       0
Total     38178

The show memory command on the Cisco 4000 includes information about SRAM memory and IO memory, and appears as follows:

Router# show memory
               Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)
Processor    49C724   28719324    1510864   27208460   26511644   15513908
      I/O   6000000    4194304    1297088    2897216    2869248    2896812
     SRAM      1000      65536      63400       2136       2136       2136
Address   Bytes Prev.   Next     Ref  PrevF   NextF   Alloc PC  What
1000       2032 0       17F0       1                  3E73E     *Init*
17F0       2032 1000    1FE0       1                  3E73E     *Init*
1FE0        544 17F0    2200       1                  3276A     *Init*
2200         52 1FE0    2234       1                  31D68     *Init*
2234         52 2200    2268       1                  31DAA     *Init*
2268         52 2234    229C       1                  31DF2     *Init*
72F0       2032 6E5C    7AE0       1                  3E73E     Init
7AE0      38178 72F0    0          0    0      0      0         
Router#

The show memory summary command displays a summary of all memory pools as well as 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 87 and Table 88.

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 Command

show processes memory

show ntp associations

To show the status of Network Time Protocol (NTP) associations, use the show ntp associations EXEC command.

show ntp associations [detail]

Syntax Description

detail

(Optional) Shows detailed information about each NTP association.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Displays

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

**Table 89: 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 peer's reference clock.
st	Peer's stratum.
when	Time since last NTP packet received from peer.
poll	Polling interval (seconds).
reach	Peer reachability (bit string, in octal).
delay	Round-trip delay to peer (milliseconds).
offset	Relative time of peer's clock to local clock (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 90 describes significant fields shown in the display.

**Table 90: 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 signaling that a leap second will be added.
leap-sub	Peer is signaling 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 timestamp 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 ivl	Our poll interval to peer.
peer poll ivl	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 Hz.
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 Command

show ntp status

show ntp status

To show the status of Network Time Protocol (NTP), use the show ntp status EXEC command.

show ntp status

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

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 91 shows the significant fields in the display.

**Table 91: 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 we are synchronized to.
nominal freq	Nominal frequency of system hardware clock.
actual freq	Measured frequency of system hardware clock.
precision	Precision of this system's clock (in Hz).
reference time	Reference timestamp.
clock offset	Offset of our 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 Command

show ntp associations

show pci

Use the show pci EXEC command to display information about the peripheral component interconnect (PCI) hardware registers or bridge registers for the Cisco 7200 series routers.

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 0 to 7. If not specified, this command displays information about all registers.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

The output of this command is generally useful for diagnostic tasks performed by technical support only.

Note The show pci hardware command displays a significant amount of information.

Sample Display

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 processes

Use the show processes EXEC command to display information about the active processes.

show processes [cpu]

Syntax Description

cpu

(Optional) Displays detailed CPU utilization statistics.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Displays

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

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

**Table 92: Show Processes Field Descriptions (Continued)**
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: 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 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, shown in bytes.
TTY	Terminal that controls the process.
Process	Name of 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 Command

show processes memory

show processes memory

Use the show processes memory EXEC command to show memory used.

show processes memory

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

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

**Table 93: Show Processes Memory Field Descriptions (Continued)**
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.
Getbuffs	Number of times the process has requested a packet buffer.
Retbuffs	Number of times the process has relinguished 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

show memory
show processes

show protocols

Use the show protocols EXEC command to display the configured protocols.

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

show protocols

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Sample Display

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 Network Protocols Configuration Guide, Part 1, Network Protocols Configuration Guide, Part 2, and Network Protocols Configuration Guide, Part 3.

show queueing

To list the current state of the queue lists, use the show queueing privileged EXEC command.

show queueing [custom | fair | priority]

Syntax Description

custom	(Optional) Shows status of custom queuing list configuration.
fair	(Optional) Shows status of the fair queuing configuration. This is the default.
priority	(Optional) Shows status of priority queuing list configuration.

Default

Fair queuing configuration

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 10.3.

If no keyword is entered, this command show the status of fair queuing configuration.

Sample Displays

The following is sample output from the show queueing custom EXEC command:

Router# show queueing custom
Current custom queue configuration:
List   Queue  Args
3      10     default
3      3      interface Tunnel3
3      3      protocol ip
3      3      byte-count 444 limit 3

The following is sample output from the show queueing command. On interface Serial0, there are two active conversations. Weighted fair queuing ensures that both of these IP data streams--both using TCP--receive equal bandwidth on the interface while they have messages in the pipeline, even though there is more FTP data in the queue than rcp data.

Router# show queueing 
Current fair queue configuration:
Interface Serial0
  Input queue: 0/75/0 (size/max/drops); Total output drops: 0
  Output queue: 18/64/30 (size/threshold/drops)
     Conversations 2/8 (active/max active)
     Reserved Conversations 0/0 (allocated/max allocated)
  (depth/weight/discards) 3/4096/30
  Conversation 117, linktype: ip, length: 556, flags: 0x280
  source: 172.31.128.115, destination: 172.31.58.89, id: 0x1069, ttl: 59,
  TOS: 0 prot: 6, source port 514, destination port 1022
  (depth/weight/discards) 14/4096/0
  Conversation 155, linktype: ip, length: 1504, flags: 0x280
  source: 172.31.128.115, destination: 172.31.58.89, id: 0x104D, ttl: 59, 
  TOS: 0 prot: 6, source port 20, destination port 1554

Related Commands

custom-queue-list
priority-group
priority-list interface
priority-list queue-limit
prompt
queue-list default
queue-list interface
queue-list protocol
queue-list queue byte-count
queue-list queue limit

show rmon

Use the show rmon EXEC command to display the current RMON agent status on the router.

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 only.
events	(Optional) Displays the RMON event table.
filter	(Optional) Displays the RMON filter table. Available on Cisco 2500 series and Cisco AS5200 only.
history	(Optional) Displays the RMON history table. Available on Cisco 2500 series and Cisco AS5200 only.
hosts	(Optional) Displays the RMON hosts table. Available on Cisco 2500 series and Cisco AS5200 only.
matrix	(Optional) Displays the RMON matrix table. Available on Cisco 2500 series and Cisco AS5200 only.
statistics	(Optional) Displays the RMON statistics table. Available on Cisco 2500 series and Cisco AS5200 only.
task	(Optional) Displays general RMON statistics.
topn	(Optional) Displays the RMON top-n hosts table. Available on Cisco 2500 series and Cisco AS5200 only.

Default

If no option is specified, the task option is displayed.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.1.

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.

Sample Display

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

**Table 94: 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

rmon
rmon alarm
rmon event
rmon queuesize
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 rmon alarms

Use the show rmon alarms EXEC command to display the contents of the router's RMON alarm table.

show rmon alarms

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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.

Sample Display

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

**Table 95: 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

rmon
rmon alarm
show rmon

show rmon capture

Use the show rmon capture EXEC command to display the contents of the router's RMON capture table.

show rmon capture

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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

Sample Display

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

**Table 96: 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

rmon
rmon event
show rmon

show rmon events

Use the show rmon events EXEC command to display the contents of the router's RMON event table.

show rmon events

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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.

Sample Display

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

**Table 97: 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

show rmon filter

Use the show rmon filter EXEC command to display the contents of the router's RMON filter table.

show rmon filter

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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

Sample Display

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

**Table 98: Show RMON Filter Field Descriptions**
Field	Description
Filter 4096 is active, and owned by manager1	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 4096 is active, and owned by manager1	Unique index of the channel, its current state, and the owner, as defined in the channelTable of RMON.
Type of channel is acceptMatched	This object controls the action of the filters associated with this channel. Equivalent to channelAcceptType of RMON.
data control is off	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

show rmon history

Use the show rmon history EXEC command to display the contents of the router's RMON history table.

show rmon history

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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

Sample Display

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

**Table 99: 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 probe 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

show rmon hosts

Use the show rmon hosts EXEC command to display the contents of the router's RMON hosts table.

show rmon hosts

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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 hosts command.

This command is available on the Cisco 2500 series and Cisco AS5200 only.

Sample Display

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

**Table 100: 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

show rmon matrix

Use the show rmon matrix EXEC command to display the contents of the router's RMON matrix table.

show rmon matrix

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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 matrix command.

This command is available on the Cisco 2500 series and Cisco AS5200 only.

Sample Display

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

**Table 101: 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

show rmon statistics

Use the show rmon statistics EXEC command to display the contents of the router's RMON statistics table.

show rmon statistics

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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

Sample Display

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

**Table 102: 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 probe 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

show rmon topn

Use the show rmon topn EXEC command to display the contents of the router's RMON Top-N host table.

show rmon topn

Syntax Description

This command has no keywords or arguments.

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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

Sample Display

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

**Table 103: Show RMON Top-N 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

show rtr application

Use the show rtr application EXEC command to display global information about the response time reporter feature.

show rtr application [tabular | full]

Syntax Description

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.

Default

Full format

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Use the show rtr application command to display information such as supported operation types and supported protocols.

Sample Display

The following is sample output from the show rtr application command in full format.

router# show rtr application 
        Response Time Reporter
Version: 1.0.0 Initial Round Trip Time MIB
Max Packet Data Size (ARR and Data): 16384
Time of Last Change in Whole RTR: *16:49:53.000 UTC Thu May 16 1996
System Max Number of Entries: 20
        Supported Operation Types
Type of Operation to Perform: echo
Type of Operation to Perform: pathEcho
        Supported Protocols
Protocol Type: ipIcmpEcho
Protocol Type: snaRUEcho
Protocol Type: snaLU0EchoAppl
Protocol Type: snaLU2EchoAppl

Related Command

show rtr configuration
show rtr distribution-statistics
show rtr totals-statistics

show rtr collection-statistics

Use the show rtr collection-statistics EXEC command to display statistical errors for all response time reporter probes or the specified probe.

show rtr collection-statistics [probe] [tabular | full]

Syntax Description

probe	(Optional) Number of the response time reporter probe 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.

Default

Full format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

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.

Sample Display

The following is 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

Related Commands

show rtr configuration

Use the show rtr configuration EXEC command to display configuration values including all defaults for all response time reporter probes or the specified probe.

show rtr configuration [probe] [tabular | full]

Syntax Description

probe	(Optional) Number of the response time reporter probe 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.

Default

Full format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Sample Display

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

Related Commands

show rtr application
show rtr collection-statistics
show rtr distribution-statistics
show rtr history
show rtr operational-state
show rtr reaction-trigger
show rtr totals-statistics

show rtr distribution-statistics

Use the show rtr distribution-statistics EXEC command to display statistic distribution information (captured response times) for all response time reporter probes or the specified probe.

show rtr distribution-statistics [probe] [tabular | full]

Syntax Description

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

Default

Tabular format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

The distributions statistics consist of:

The sum of completion times (used to calculate the mean)
The sum of the completions times squared (used to calculate standard deviation)
The maximum and minimum completion time
The number of completed attempts

You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.

Sample Display

The following is sample output from the show rtr distributions-statistics command in tabular format.

router# show rtr distributions-statistics 
        Captured Statistics
        Multiple Lines per Entry
Line 1
Entry    = Entry Number
StartT   = Start Time of Entry (hundredths of seconds)
Pth      = Path Index
Hop      = Hop in Path Index
Dst      = Time Distribution Index
Comps    = Operations Completed
OvrTh    = Operations Completed Over Thresholds
SumCmp   = Sum of Completion Times (milliseconds)
Line 2
SumCmp2L = Sum of Completion Times Squared Low 32 Bits (milliseconds)
SumCmp2H = Sum of Completion Times Squared High 32 Bits (milliseconds)
TMax     = Completion Time Maximum (milliseconds)
TMin     = Completion Time Minimum (milliseconds)
Entry StartT     Pth Hop Dst Comps      OvrTh      SumCmp
  SumCmp2L   SumCmp2H   TMax       TMin
1     17417068   1   1   1   2          0           128
   8192      0          64         64

Related Commands

show rtr collection-statistics
show rtr configuration
show rtr totals-statistics

show rtr history

Use the show rtr history EXEC command to display history collected for all response time reporter probes or the specified probe.

show rtr history [probe] [tabular | full]

Syntax Description

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

Default

Tabular format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

The response return codes are listed in Table 104.

**Table 104: Response Return Codes**
Code	Meaning
1	Okay.
2	Disconnected.
3	Over threshold.
4	Timeout.
5	Busy.
6	Not connected.
7	Dropped.
8	Sequence error.
9	Verify error.
10	Application specific.

Sample Display

The following is sample output from the show rtr history command in tabular format:

router# show rtr history 
        Point by point History
          Multiple Lines per Entry
Line 1
Entry    = Entry Number
LifeI    = Life Index
BucketI  = Bucket Index
SampleI  = Sample Index
SampleT  = Sample Start Time
CompT    = Completion Time (milliseconds)
Sense    = Response Return Code
Line 2 has the Target Address
Entry LifeI      BucketI    SampleI    SampleT    CompT      Sense
2     1          1          1          17436548   16          1
  AB 45 A0 16 
2     1          2          1          17436551   4           1
  AC 12 7  29 
2     1          2          2          17436551   1           1
  AC 12 5  22 
2     1          2          3          17436552   4           1
  AB 45 A7 22 
2     1          2          4          17436552   4           1
  AB 45 A0 16

Related Command

show rtr operational-state

Use the show rtr operational-state EXEC command to display the operational state of all response time reporter probes or the specified probe.

show rtr operational-state [probe] [tabular | full]

Syntax Description

probe	(Optional) Number of the response time reporter probe 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.

Default

Full format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Use the show rtr operational-state command to determine whether a connection loss, timeout, and over threshold occurred; how much life the probe has left; whether the probe is active; and the completion time. It also displays the results of the latest operation attempt.

Sample Display

The following is sample output from the show rtr operational-state command in full format:

router# show rtr operational-state 1 
        Current Operational State
Entry Number: 1
Modification Time: *17:15:41.000 UTC Thu May 16 1996
Diagnostics Text: 
Last Time this Entry was Reset: Never
Number of Octets in use by this Entry: 2438
Connection Loss Occurred: FALSE
Timeout Occurred: FALSE
Over Thresholds Occurred: FALSE
Number of Operations Attempted: 6
Current Seconds Left in Life: 3336
Operational State of Entry: active
Latest Completion Time (milliseconds): 60
Latest Operation Return Code: ok
Latest Operation Start Time: *17:19:41.000 UTC Thu May 16 1996
Latest Target Address: 172.16.1.176

Related Command

show rtr reaction-trigger

Use the show rtr reaction-trigger EXEC command to display the reaction trigger information for all response time reporter probes or the specified probe.

show rtr reaction-trigger [probe] [tabular | full]

Syntax Description

probe	(Optional) Number of the response time reporter probe 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.

Default

Full format for all probes

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Use the show rtr reaction-trigger command to display the configuration status and operational state of target probes that will be triggered as defined with the rtr reaction-configuration global command.

Sample Display

The following is sample output from the show rtr reaction-trigger command in full format:

router# show rtr reaction-trigger 1
        Reaction Table
Entry Number: 1
Target Entry Number: 2
Status of Entry (SNMP RowStatus): active
Operational State: pending

Related Command