Table Of Contents
Router and Network Monitoring Commands
distributions-of-statistics-kept
show rtr collection-statistics
show rtr distributions-statistics
snmp-server manager session-timeout
snmp-server trap-authentication
statistics-distribution-interval
Router and Network Monitoring Commands
This chapter describes commands used to monitor the router and network in Cisco IOS Release 12.0.
For system management configuration tasks and examples, refer to the "Monitoring the Router and Network" chapter in the Cisco IOS Release 12.0 Configuration Fundamentals Configuration Guide.
buckets-of-history-kept
To set the number of history buckets that are kept during the response time reporter probe's lifetime, use the buckets-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.
buckets-of-history-kept size
no buckets-of-history-kept
Syntax Description
size
Number of history buckets kept during the response time reporter probe's lifetime. The default is 50 buckets.
Defaults
50 buckets
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
A response time reporter probe can collect history and capture statistics. By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept response time reporter configuration command to collect history. You can optionally adjust the buckets-of-history-kept, filter-for-history, and samples-of-history-kept response time reporter configuration commands.
When the number of buckets reaches the size specified, no further history for this life is stored.
Note
Collecting history increases the RAM usage. Only collect history when you think there is a problem. For general network response time information, use statistics.
If history is collected, each bucket contains one or more history entries from the probe. When the probe type is pathEcho, an entry is created for each hop along the path that the probe takes to reach its destination. The type of entry stored in the history table is controlled by the filter-for-history response time reporter configuration command. The total number of entries stored in the history table is controlled by the combination of samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept response time reporter configuration commands.
Each time the probe starts a response time reporter operation, a new bucket is created until the number of history buckets matches the specified size or the probe's lifetime expires. History buckets do not wrap. The probe's lifetime is defined by the rtr schedule global configuration command. The probe starts a response time reporter operation based on the seconds specified by the frequency response time reporter configuration command.
Examples
The following example configures probe 1 to keep 25 history buckets during the probe's lifetime:
rtr 1type echo protocol ipIcmpEcho 172.16.161.21buckets-of-history-kept 25lives-of-history-kept 1Related Commands
cdp enable
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable interface configuration command. Use the no form of this command to disable CDP on an interface.
cdp enable
no cdp enable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled at the global level and on all supported interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
CDP is enabled by default at the global level and on each supported interface in order to send or receive CDP information. However, some interfaces, such as ATM interfaces, do not support CDP.
Note
Examples
The following example enables CDP on Ethernet interface 0:
interface ethernet 0cdp enableRelated Commands
cdp holdtime
To specify the amount of time the receiving device should hold a CDP packet from your router before discarding it, use the cdp holdtime global configuration command. Use the no form of this command to revert to the default setting.
cdp holdtime seconds
no cdp holdtime
Syntax Description
Defaults
180 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
CDP packets are sent with time-to-live, or hold time, that is nonzero after an interface is enabled and a hold time of 0 immediately before an interface is idled down.
The CDP hold time must be set to a higher number of seconds than the time between CDP transmissions, which is set using the cdp timer command.
Examples
In the following example, the CDP packets being sent from your router should be held by the receiving device for 60 seconds before being discarded. You might want to set the hold time lower than the default setting of 180 seconds if information about your router changes often and you want the receiving devices to purge this information more quickly.
cdp holdtime 60Related Commands
Specifies how often the Cisco IOS software sends CDP updates.
"Displays global CDP information, including timer and hold-time information."
cdp run
To enable CDP, use the cdp run global configuration command. Use the no form of this command to disable CDP.
cdp run
no cdp run
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
CDP is enabled on your router by default, which means the Cisco IOS software will receive CDP information. CDP also is enabled on supported interfaces by default. To disable CDP on an interface, use the no cdp enable interface configuration command.
Note
Examples
The following example disables CDP:
no cdp runRelated Commands
cdp timer
To specify how often the Cisco IOS software sends CDP updates, use the cdp timer global configuration command. Use the no form of this command to revert to the default setting.
cdp timer seconds
no cdp timer
Syntax Description
Defaults
60 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
The trade-off with sending more frequent transmissions is providing up-to-date information versus using bandwidth more often.
Note
Examples
In the following example, CDP updates are sent every 80 seconds, less frequently than the default setting of 60 seconds. You might want to make this change if you are concerned about preserving bandwidth.
cdp timer 80Related Commands
clear cdp counters
To reset CDP traffic counters to zero (0), use the clear cdp counters privileged EXEC command.
clear cdp counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the CDP counters. The show cdp traffic output shows that all of the traffic counters have been reset to zero (0).
Router# clear cdp countersRouter# show cdp trafficCDP counters:Packets output: 0, Input: 0Hdr syntax: 0, Chksum error: 0, Encaps failed: 0No memory: 0, Invalid packet: 0, Fragmented: 0Related Commands
Clears the table that contains CDP information about neighbors.
Displays traffic information from the CDP table.
clear cdp table
To clear the table that contains CDP information about neighbors, use the clear cdp table privileged EXEC command.
clear cdp table
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the CDP table. The output of the show cdp neighbors command shows that all information has been deleted from the table.
Router# clear cdp tableCDP-AD: Deleted table entry for neon.cisco.com, interface Ethernet0CDP-AD: Deleted table entry for neon.cisco.com, interface Serial0Router# show cdp neighborsCapability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMPDevice ID Local Intrfce Holdtme Capability Platform Port IDRelated Commands
distributions-of-statistics-kept
To set the number of statistic distributions kept per hop during the response time reporter probe's lifetime, use the distributions-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
distributions-of-statistics-kept size
no distributions-of-statistics-kept
Syntax Description
Defaults
1 distribution
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
In most situations, you do not need to change the statistic distribution size for the response time reporter. Only change the size when distributions are needed (for example, when performing statistical modeling of your network).
Note
When the number of distributions reaches the size specified, no further distribution information is stored.
Examples
The following example sets the distribution to 5 and the distribution interval to 10 ms. This means that the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity.
rtr 1type echo protocol ipIcmpEcho 172.16.161.21distributions-of-statistics-kept 5statistics-distribution-interval 10Related Commands
filter-for-history
To define the type of information kept in the history table for the response time reporter probe, use the filter-for-history response time reporter configuration command. Use the no form of this command to return to the default value.
filter-for-history {none | all | overThreshold | failures}
no filter-for-history {none | all | overThreshold | failures}
Syntax Description
Defaults
none
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
Use the filter-for-history command to control what gets stored in the history table for the response time reporter. To control how much history gets saved in the history table, use the lives-of-history-kept, buckets-of-history-kept, and the samples-of-history-kept response time reporter configuration commands.
A probe can collect history and capture statistics. By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept command to collect history.
Note
Examples
In the following example, only probe packets that fail are kept in the history table:
rtr 1type echo protocol ipIcmpEcho 172.16.161.21lives-of-history-kept 1filter-for-history failuresRelated Commands
frequency
To set the rate at which the response time reporter probe starts a response time operation, use the frequency response time reporter configuration command. Use the no form of this command to return to the default value.
frequency second
no frequency
Syntax Description
second
Number of seconds between the probe's response time reporter operations. The default value is 60 seconds.
Defaults
60 seconds
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
Caution
If the probe takes longer to execute the current response time reporter operation than the specified frequency value, a statistics counter called busy is incremented in lieu of starting a second operation.
The value specified for the frequency command cannot be less than the value specified for the timeout response time reporter configuration command.
Examples
The following example configures the probe to execute a response time reporter operation every 90 seconds:
rtr 1type echo protocol ipIcmpEcho 172.16.1.176frequency 90Related Commands
Configures a response time reporter probe.
Sets the amount of time the response time reporter probe waits for a response from its request packet.
hops-of-statistics-kept
To set the number of hops for which statistics are maintained per path for the response time reporter probe, use the hops-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
hops-of-statistics-kept size
no hops-of-statistics-kept
Syntax Description
size
Number of hops for which statistics are maintained per path. The default is 16 hops for type pathEcho and 1 hop for type echo.
Defaults
16 hops for type pathEcho
1 hop for type echo
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
One hop is the passage of a timed packet from this router to another network device. The other network device (is assumed to) be a device along the path to the destination (including the destination) when the probe type is pathEcho, or just the destination when the type is echo.
When the number of hops reaches the size specified, no further hop information is stored.
Examples
The following example monitors probe 2's statistics for only 10 hops:
rtr 2type pathecho protocol ipIcmpEcho 172.16.1.177hops-of-statistics-kept 10Related Commands
hours-of-statistics-kept
To set the number of hours for which statistics are maintained for the response time reporter probe, use the hours-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
hours-of-statistics-kept hours
no hours-of-statistics-kept
Syntax Description
Defaults
2 hours
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
This command first appeared in Cisco IOS Release .
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest information is replaced by newer information).
Examples
The following example maintains probe 2's statistics for 3 hours:
rtr 2type pathecho protocol ipIcmpEcho 172.16.1.177hours-of-statistics-kept 3Related Commands
lives-of-history-kept
To set the number of lives maintained in the history table for the response time reporter probe, use the lives-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.
lives-of-history-kept lives
no lives-of-history-kept
Syntax Description
Defaults
0 lives
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
The default value (0 lives) means that history is not collected for the probe. To disable history collection, use the default value for the lives-of-history-kept command rather than the filter-for-history none response time reporter configuration command. The lives-of-history-kept command disables history collection before the probe's operation is attempted, and the filter-for-history command checks for history inclusion after the probe's operation attempt is made.
When the number of lives exceeds the specified value, the history table wraps (that is, the oldest information is replaced by newer information).
When a probe makes a transition from pending to active, a life starts. When a probe's life ends, the probe makes a transition from active to pending.
Examples
The following example maintains probe 1's history for 5 lives:
rtr 1type echo protocol ipIcmpEcho 172.16.1.176lives-of-history-kept 5Related Commands
owner
To configure the SNMP owner of the response time reporter probe, use the owner response time reporter configuration command. Use the no form of this command to return to the default value.
owner text
no owner
Syntax Description
Defaults
No owner is specified.
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
The owner name contains one or more of the following: ASCII form of the network management station's transport address, network management station name (that is, the domain name), and network management personnel's name, location, or phone number. In some cases, the agent itself will be the owner of the probe. In these cases, the name can begin with "agent."
Examples
The following example sets probe 1's owner is set:
rtr 1type echo protocol ipIcmpEcho 172.16.1.176owner 172.16.1.189 cwb.cisco.com John Doe RTP 555-1212Related Commands
paths-of-statistics-kept
To set the number of paths for which statistics are maintained per hour for the response time reporter probe, use the paths-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
paths-of-statistics-kept size
no paths-of-statistics-kept
Syntax Description
size
Number of paths for which statistics are maintained per hour. The default is 5 paths for type pathEcho and 1 path for type echo.
Defaults
5 paths for type pathEcho
1 path for type echo
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
A path is the route the probe's request packet takes through the network to get to its destination. The probe may take a different path to reach its destination for each response time reporter operation.
When the number of paths reaches the size specified, no further path information is stored.
Examples
The following example maintains probe 2's statistics for only 3 paths:
rtr 2type pathEcho protocol ipIcmpEcho 172.16.1.177paths-of-statistics-kept 3Related Commands
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.
Defaults
1 byte
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
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).
Examples
The following example sets probe 3's request packet size to 40 bytes:
rtr 3type echo protocol snalu0echoappl cwbc0arequest-data-size 40Related Commands
Sets the protocol data size in the payload of the response time reporter probeís response packet.
Configures a response time reporter probe.
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.
Defaults
For "appl" protocols, 0 bytes
For all others, the same value as the request-data-size
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
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.
Examples
The following example sets probe 3's response packet size to 1440 bytes:
rtr 3type echo protocol snalu0echoappl cwbc0aresponse-data-size 1440Related Commands
Sets the protocol data size in the payload of the response time reporter probeís request packet.
Configures a response time reporter probe.
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
Defaults
RMON is disabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command enables RMON on Ethernet interfaces of Cisco 2500 series and Cisco AS5200 series routers only. A generic RMON console application is recommended 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
All Cisco IOS software Release 11.3 feature sets support RMON alarm and event groups. Additional RMON groups are supported in certain feature sets. Refer to the 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.
Examples
The following example enables RMON on Ethernet interface 0 and allows the router to examine only packets destined for the interface:
interface ethernet 0rmon nativeRelated Commands
rmon alarm
To set an alarm on any MIB object, use the rmon alarm global 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
Defaults
No alarms configured
Command Modes
Global configuration
Command History
Usage Guidelines
The MIB object must be specified as a dotted decimal value after the entry sequence (for example, ifEntry.10.1). You cannot specify the variable name and the instance (for example, ifInOctets.1) or the entire dotted decimal notation. The variable must be of the form entry.integer.instance.
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.
Examples
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 0owner jjohnsonThis 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 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
Defaults
No events configured
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies only to the Cisco 2500 series and Cisco AS5200 series.
See RFC 1757 for more information about the RMON MIB.
Examples
The following example enables the rmon event command:
rmon event 1 log trap eventtrap description "High ifOutErrors" owner sdurhamThis 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
Enables Remote Network Monitoring (RMON) on an Ethernet interface
Displays the current RMON agent status on the router.
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.
Defaults
64 packets
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to the RMON function, which is available on Ethernet interfaces of Cisco 2500 series and Cisco AS5200 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.
Examples
The following example configures the RMON queue size to be 128 packets:
rmon queuesize 128Related Commands
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
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
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 "Monitoring the Router and Network" chapter in the Configuration Fundamentals Configuration Guide and the Cisco Round-Trip Time Monitor (RTTMON) MIB.
This command places you in response time reporter configuration mode.
Note
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.
Examples
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 1type echo protocol snalu0echoappl cwbc0arequest-data-size 40response-data-size 1440
Note
Related Commands
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
Defaults
No reactions are generated.
Command Modes
Global configuration
Command History
Usage Guidelines
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
Examples
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 trapOnlyFigure 1 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 1 Example of Rising and Falling Thresholds
Related Commands
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
Defaults
No trigger combination is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Triggers are usually used for diagnostics purposes and are not used in normal operation.
Examples
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 1Related Commands
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.
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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.
Examples
The following example resets the response time reporter feature:
rtr resetRelated Commands
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
Defaults
Place the probe in a pending state (that is, the probe is started but not actively collecting information).
Command Modes
Global configuration
Command History
Usage Guidelines
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----------------------Zwhere:
•
•
•
•
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
Examples
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 43200Related Commands
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.
Defaults
16 entries for type pathEcho
1 entry for type echo
Command Modes
Response time reporter configuration
Command History
Usage Guidelines
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.
A probe can collect history and capture statistics. By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept response time reporter configuration command to collect history.
Note
Examples
In the following example, ten entries are kept in the history table for each of the of probe's three lives:
rtr 1type pathecho protocol ipIcmpEcho 172.16.1.176lives-of-history-kept 3samples-of-history-kept 10Related Commands
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 Modes
Privileged EXEC
Command History
Examples
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 cdpGlobal CDP information:Sending CDP packets every 60 secondsSending a holdtime value of 180 secondsRelated Commands
show cdp entry
To display information about 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
Command Modes
Privileged EXEC
Command History
Examples
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.comEntry address(es):IP address: 192.168.68.18CLNS address: 490001.1111.1111.1111.00DECnet address: 10.1Platform: cisco 4500, Capabilities: RouterInterface: Ethernet0/1, Port ID (outgoing port): Ethernet0Holdtime : 125 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) 4500 Software (C4500-J-M), Version 11.1(10.4), MAINTENANCE INTERIM SOFTWARECopyright (c) 1986-1997 by cisco Systems, Inc.Compiled Mon 07-Apr-97 19:51 by dschwartThe following is sample output from the show cdp entry protocol command. Only information about the protocols enabled on device.cisco.com is displayed.
Router# show cdp entry device.cisco.com protocolProtocol information for device.cisco.com:IP address: 192.168.68.18CLNS address: 490001.1111.1111.1111.00DECnet address: 10.1The 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 versionVersion information for device.cisco.com:Cisco Internetwork Operating System SoftwareIOS (tm) 4500 Software (C4500-J-M), Version 11.1(10.4), MAINTENANCE INTERIM SOFTWARECopyright (c) 1986-1997 by cisco Systems, Inc.Compiled Mon 07-Apr-97 19:51 by dschwartRelated Commands
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 Modes
Privileged EXEC
Command History
Examples
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 interfaceSerial0 is up, line protocol is up, encapsulation is SMDSSending CDP packets every 60 secondsHoldtime is 180 secondsEthernet0 is up, line protocol is up, encapsulation is ARPASending CDP packets every 60 secondsHoldtime is 180 secondsThe 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 0Ethernet0 is up, line protocol is up, encapsulation is ARPASending CDP packets every 60 secondsHoldtime is 180 secondsRelated Commands
show cdp neighbors
To display information about neighbors, use the show cdp neighbors privileged EXEC command.
show cdp neighbors [type number] [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
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 neighborsCapability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMP, r - RepeaterDevice ID Local Intrfce Holdtme Capability Platform Port IDdevice1.cisco.com Eth 0/1 122 T S WS-C2900 2/11device2.cisco.com Eth 0/1 179 R 4500 Eth 0device3.cisco.com Eth 0/1 155 R 2500 Eth 0device4.cisco.com Eth 0/1 155 R 2509 Eth 0The following is sample output for one neighbor 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: device2.cisco.comEntry address(es):IP address: 171.68.162.134Platform: cisco 4500, Capabilities: RouterInterface: Ethernet0/1, Port ID (outgoing port): Ethernet0Holdtime : 156 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) 4500 Software (C4500-J-M), Version 11.1(10.4), MAINTENANCE INTERIM SOFTWARECopyright (c) 1986-1997 by Cisco Systems, Inc.Compiled Mon 07-Apr-97 19:51 by dschwartRelated Commands
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 Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show cdp traffic command.
Router# show cdp trafficCDP counters:Packets output: 94, Input: 75Hdr syntax: 0, Chksum error: 0, Encaps failed: 0No memory: 0, Invalid packet: 0, Fragmented: 0In 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.
Related Commands
show rmon
Use the show rmon EXEC command to display the current RMON agent status on the router.
show rmon [alarms | capture | events | filter | history | hosts | matrix | statistics | task | topn]
Syntax Description
Defaults
If no option is specified, the task option is displayed.
Command Modes
EXEC
Command History
Usage Guidelines
Refer to the specific show rmon command for an example and description of the fields.
For additional information, refer to the RMON MIB described in RFC 1757.
Examples
The following is sample output from the show rmon command. All counters are from the time the router was initialized.
Router# show rmon145678 packets input (34562 promiscuous), 0 drops145678 packets processed, 0 on queue, queue utilization 15/64Table 40 describes the fields shown in the display.
Related Commands
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms to display alarm information with the show rmon alarms command.
Examples
The following is sample output from the show rmon alarms command:
Router# show rmon alarmsAlarm 2 is active, owned by manager1Monitors ifEntry.1.1 every 30 secondsTaking delta samples, last value was 0Rising threshold is 15, assigned to event 12Falling threshold is 0, assigned to event 0On startup enable rising or falling alarmTable 41 describes the fields shown in the display.
Related Commands
Enables Remote Network Monitoring (RMON) on an Ethernet interface.
Sets an alarm on any MIB object.
Displays the current RMON agent status on the router.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon capture command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon capture command:
Router# show rmon captureBuffer 4096 is active, owned by manager1Captured data is from channel 4096Slice size is 128, download size is 128Download offset is 0Full Status is spaceAvailable, full action is lockWhenFullGranted 65536 octets out of 65536 requestedBuffer has been on since 00:01:16, and has captured 1 packetsCurrent capture buffer entries:Packet 1 was captured 416 ms since buffer was turned onIts length is 326 octets and has a status type of 0Packet ID is 634, and contains the following data:00 00 0c 03 12 ce 00 00 0c 08 9d 4e 08 00 45 0001 34 01 42 00 00 1d 11 e3 01 ab 45 30 15 ac 1531 06 05 98 00 a1 01 20 9f a8 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00Table 42 describes the fields shown in the display.
Related Commands
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON events to display alarm information with the show rmon events command.
Examples
The following is sample output from the show rmon events command:
Router# show rmon eventsEvent 12 is active, owned by manager1Description is interface-errorsEvent firing causes log and trap to community rmonTrap, last fired 00:00:00Table 43 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon filter command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon filter command:
Router# show rmon filterFilter 4096 is active, and owned by manager1Data offset is 12, withData of 08 00 00 00 00 00 00 00 00 00 00 00 00 00 ab 45 30 15 ac 15 31 06Data Mask is ff ff 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ffData Not Mask is 0Pkt status is 0, status mask is 0, not mask is 0Associated channel 4096 is active, and owned by manager1Type of channel is acceptFailed, data control is offGenerate event index 0Event status is eventFired, # of matches is 1482Turn on event index is 0, turn off event index is 0Description:Table 44 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon history command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon history command:
Router# show rmon historyEntry 1 is active, and owned by manager1Monitors ifEntry.1.1 every 30 secondsRequested # of time intervals, ie buckets, is 5Granted # of time intervals, ie buckets, is 5Sample # 14 began measuring at 00:11:00Received 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 0Network utilization is estimated at 10Table 45 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon hosts command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon hosts command:
Router# show rmon hostsHost Control Entry 1 is active, and owned by manager1Monitors host ifEntry.1.1Table size is 51, last time an entry was deleted was 00:00:00Creation Order number is 1Physical address is 0000.0c02.5808Packets: rcvd 6963, transmitted 7041Octets: rcvd 784062, transmitted 858530# of packets transmitted: broadcast 28, multicast 48# of bad packets transmitted is 0Table 46 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon matrix command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon matrix command:
Router# show rmon matrixMatrix 1 is active, and owned by manager1Monitors ifEntry.1.1Table size is 451, last time an entry was deleted was at 00:00:00Table 47 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display alarm information with the show rmon statistics command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon statistics command:
Router# show rmon statisticsInterface 1 is active, and owned by configMonitors ifEntry.1.1 which hasReceived 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:2547Table 48 describes the fields shown in the display.
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 arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON events to display alarm information with the show rmon events command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon topn command:
Router# show rmon topnHost Entry 1 of report 1 is active, owned by manager1The rate of change is based on hostTopNInPktsThis report was last started at 00:00:00Time remaining in this report is 0 out of 0Hosts physical address is 00ad.beef.002bRequested # of hosts: 10, # of hosts granted: 10Report # 1 of Top N hosts entry 1 is recordingHost 0000.0c02.5808 at a rate of 12Table 49 describes the fields shown in the display.
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
Defaults
Full format
Command Modes
EXEC
Command History
Usage Guidelines
Use the show rtr application command to display information such as supported operation types and supported protocols.
Examples
The following is sample output from the show rtr application command in full format.
Router# show rtr applicationResponse Time ReporterVersion: 1.0.0 Initial Round Trip Time MIBMax Packet Data Size (ARR and Data): 16384Time of Last Change in Whole RTR: *16:49:53.000 UTC Thu May 16 1996System Max Number of Entries: 20Supported Operation TypesType of Operation to Perform: echoType of Operation to Perform: pathEchoSupported ProtocolsProtocol Type: ipIcmpEchoProtocol Type: snaRUEchoProtocol Type: snaLU0EchoApplProtocol Type: snaLU2EchoApplRelated Commands
Displays configuration values including all defaults for all response time reporter probes or the specified probe.
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
Defaults
Full format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
Use the show rtr collection-statistics command to display information such as the number of failed operations and the failure reason. You can also use the show rtr distribution-statistics and show rtr totals-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr collection-statistics command in full format.
Router# show rtr collection-statistics 1Collected StatisticsEntry Number: 1Start Time Index: *17:15:41.000 UTC Thu May 16 1996Path Index: 1Hop in Path Index: 1Number of Failed Operations due to a Disconnect: 0Number of Failed Operations due to a Timeout: 0Number of Failed Operations due to a Busy: 0Number of Failed Operations due to a No Connection: 0Number of Failed Operations due to an Internal Error: 0Number of Failed Operations due to a Sequence Error: 0Number of Failed Operations due to a Verify Error: 0Target Address: 172.16.1.176Related 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
Defaults
Full format for all probes
Command Modes
EXEC
Command History
Examples
The following is sample output from the show rtr configuration command in full format:
Router# show rtr configuration 1Complete Configuration Table (includes defaults)Entry Number: 1Owner: "Sample Owner"Tag: "Sample Tag Group"Type of Operation to Perform: echoReaction and History Threshold (milliseconds): 5000Operation Frequency (seconds): 60Operation Timeout (milliseconds): 5000Verify Data: FALSEStatus of Entry (SNMP RowStatus): activeProtocol Type: ipIcmpEchoTarget Address: 172.16.1.176Request Size (ARR data portion): 1Response Size (ARR data portion): 1Life (seconds): 3600Next Start Time: Start Time already passedEntry Ageout (seconds): 3600Connection Loss Reaction Enabled: FALSETimeout Reaction Enabled: FALSEThreshold Reaction Type: neverThreshold Falling (milliseconds): 3000Threshold Count: 5Threshold Count2: 5Reaction Type: noneNumber of Statistic Hours kept: 2Number of Statistic Paths kept: 1Number of Statistic Hops kept: 1Number of Statistic Distribution Buckets kept: 1Number of Statistic Distribution Intervals (milliseconds): 20Number of History Lives kept: 0Number of History Buckets kept: 50Number of History Samples kept: 1History Filter Type: noneRelated Commands
show rtr distributions-statistics
Use the show rtr distributions-statistics EXEC command to display statistic distribution information (captured response times) for all response time reporter probes or the specified probe.
show rtr distributions-statistics [probe] [tabular | full]
Syntax Description
Defaults
Tabular format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
The distributions statistics consist of:
•
•
•
•
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr distributions-statistics command in tabular format.
Router# show rtr distributions-statisticsCaptured StatisticsMultiple Lines per EntryLine 1Entry = Entry NumberStartT = Start Time of Entry (hundredths of seconds)Pth = Path IndexHop = Hop in Path IndexDst = Time Distribution IndexComps = Operations CompletedOvrTh = Operations Completed Over ThresholdsSumCmp = Sum of Completion Times (milliseconds)Line 2SumCmp2L = 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 SumCmpSumCmp2L SumCmp2H TMax TMin1 17417068 1 1 1 2 0 1288192 0 64 64Related Commands
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
Defaults
Tabular format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
The response return codes are listed in Table 50.
Table 50 Response Return Codes
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.
Examples
The following is sample output from the show rtr history command in tabular format:
Router# show rtr historyPoint by point HistoryMultiple Lines per EntryLine 1Entry = Entry NumberLifeI = Life IndexBucketI = Bucket IndexSampleI = Sample IndexSampleT = Sample Start TimeCompT = Completion Time (milliseconds)Sense = Response Return CodeLine 2 has the Target AddressEntry LifeI BucketI SampleI SampleT CompT Sense2 1 1 1 17436548 16 1AB 45 A0 162 1 2 1 17436551 4 1AC 12 7 292 1 2 2 17436551 1 1AC 12 5 222 1 2 3 17436552 4 1AB 45 A7 222 1 2 4 17436552 4 1AB 45 A0 16Related Commands
Displays configuration values including all defaults for all response time reporter probes or the specified probe.
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
Defaults
Full format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
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.
Examples
The following is sample output from the show rtr operational-state command in full format:
Router# show rtr operational-state 1Current Operational StateEntry Number: 1Modification Time: *17:15:41.000 UTC Thu May 16 1996Diagnostics Text:Last Time this Entry was Reset: NeverNumber of Octets in use by this Entry: 2438Connection Loss Occurred: FALSETimeout Occurred: FALSEOver Thresholds Occurred: FALSENumber of Operations Attempted: 6Current Seconds Left in Life: 3336Operational State of Entry: activeLatest Completion Time (milliseconds): 60Latest Operation Return Code: okLatest Operation Start Time: *17:19:41.000 UTC Thu May 16 1996Latest Target Address: 172.16.1.176Related Commands
Displays configuration values including all defaults for all response time reporter probes or the specified probe.
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
Defaults
Full format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
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.
Examples
The following is sample output from the show rtr reaction-trigger command in full format:
Router# show rtr reaction-trigger 1Reaction TableEntry Number: 1Target Entry Number: 2Status of Entry (SNMP RowStatus): activeOperational State: pendingRelated Commands
Displays configuration values including all defaults for all response time reporter probes or the specified probe.
show rtr totals-statistics
Use the show rtr totals-statistics EXEC command to display the total statistical values (accumulation of error counts and completions) for all response time reporter probes or the specified probe.
show rtr totals-statistics [probe] [tabular | full]
Syntax Description
Defaults
Full format for all probes
Command Modes
EXEC
Command History
Usage Guidelines
The total statistics consist of the following items:
•
•
•
•
You can also use the show rtr distributions-statistics and show rtr collection-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr totals-statistics command in full format:
Router# show rtr totals-statisticsStatistic TotalsEntry Number: 1Start Time Index: *17:15:41.000 UTC Thu May 16 1996Age of Statistics Entry (hundredths of seconds): 48252Number of Initiations: 10Related Commands
show snmp
To check the status of SNMP communications, use the show snmp EXEC command.
show snmp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
This command provides counter information for SNMP operations. It also displays the chassis ID string defined with the snmp-server chassis-id command.
Examples
The following is sample output from the show snmp command:
Router# show snmpChassis: 0150619937 SNMP packets input0 Bad SNMP version errors4 Unknown community name0 Illegal operation for community name supplied0 Encoding errors24 Number of requested variables0 Number of altered variables0 Get-request PDUs28 Get-next PDUs0 Set-request PDUs78 SNMP packets output0 Too big errors (Maximum packet size 1500)0 No such name errors0 Bad values errors0 General errors24 Response PDUs13 Trap PDUsSNMP logging: enabledLogging to 171.69.58.33.162, 0/10, 13 sent, 0 dropped.SNMP Manager-role output packets4 Get-request PDUs4 Get-next PDUs6 Get-bulk PDUs4 Set-request PDUs23 Inform-request PDUs30 Timeouts0 DropsSNMP Manager-role input packets0 Inform response PDUs2 Trap PDUs7 Response PDUs1 Responses with errorsSNMP informs: enabledInforms in flight 0/25 (current/max)Logging to 171.69.217.141.1624 sent, 0 in-flight, 1 retries, 0 failed, 0 droppedLogging to 171.69.58.33.1620 sent, 0 in-flight, 0 retries, 0 failed, 0 droppedTable 51 describes the fields shown in the display.
Related Commands
show snmp pending
To display the current set of pending SNMP requests, use the show snmp pending EXEC command.
show snmp pending
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
After the SNMP manager sends a request, the request is "pending" until the manager receives a response or the request timeout expires.
Examples
The following is sample output from the show snmp pending command:
Router# show snmp pendingreq id: 47, dest: 171.69.58.33.161, V2C community: public, Expires in 5 secsreq id: 49, dest: 171.69.58.33.161, V2C community: public, Expires in 6 secsreq id: 51, dest: 171.69.58.33.161, V2C community: public, Expires in 6 secsreq id: 53, dest: 171.69.58.33.161, V2C community: public, Expires in 8 secsTable 52 describes the fields shown in the display.
Related Commands
Checks the status of SNMP communications.
Displays the current SNMP sessions.
Starts the SNMP manager process.
Sets the amount of time before a non-active session is destroyed.
show snmp sessions
To display the current SNMP sessions, use the show snmp sessions EXEC command.
show snmp sessions [brief]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Sessions are created when the SNMP manager in the router sends SNMP requests, such as inform requests, to a host or receives SNMP notifications from a host. One session is created for each destination host. If there is no further communication between the router and host within the session timeout period, the corresponding session will be deleted.
Examples
The following is sample output from the show snmp sessions command:
Router# show snmp sessionsDestination: 171.69.58.33.162, V2C community: publicRound-trip-times: 0/0/0 (min/max/last)packets output0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs0 Timeouts, 0 Dropspackets input0 Traps, 0 Informs, 0 Responses (0 errors)Destination: 171.69.217.141.162, V2C community: public, Expires in 575 secsRound-trip-times: 1/1/1 (min/max/last)packets output0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs0 Timeouts, 0 Dropspackets input0 Traps, 0 Informs, 4 Responses (0 errors)The following is sample output from the show snmp sessions brief command:
Router# show snmp sessions briefDestination: 171.69.58.33.161, V2C community: public, Expires in 55 secsTable 53 describes the fields shown in these displays.
Related Commands
snmp-server access-policy
This command is no longer valid. The functionality provided by this command has been removed from the Cisco IOS software.
snmp-server chassis-id
To provide a message line identifying the SNMP server serial number, use the snmp-server chassis-id global configuration command. Use the no form of this command to restore the default value, if any.
snmp-server chassis-id text
no snmp-server chassis-id
Syntax Description
Defaults
On hardware platforms where the serial number can be machine read, the default is the serial number. For example, a Cisco 7000 has a default value of its serial number.
Command Modes
Global configuration
Command History
Usage Guidelines
The Cisco MIB provides a chassis MIB variable that enables the SNMP manager to gather data on system card descriptions, chassis type, chassis hardware version, chassis ID string, software version of ROM monitor, software version of system image in ROM, bytes of processor RAM installed, bytes of NVRAM installed, bytes of NVRAM in use, current configuration register setting, and the value of the configuration register at the next reload. The following installed card information is provided: type of card, serial number, hardware version, software version, and chassis slot number.
The chassis ID message can be seen with the show snmp command.
Examples
In the following example, the chassis serial number specified is 1234456:
snmp-server chassis-id 1234456Related Commands
snmp-server community
To set up the community access string to permit access to the SNMP protocol, use the snmp-server community global configuration command. The no form of this command removes the specified community string.
snmp-server community string [view view-name] [ro | rw] [number]
no snmp-server community string
Syntax Description
Defaults
By default, an SNMP community string permits read-only access to all objects.
Command Modes
Global configuration
Command History
Usage Guidelines
The no snmp-server command disables both versions of SNMP (SNMPv1 and SNMPv2C).
The first snmp-server command that you enter enables both versions of SNMP.
Examples
The following example assigns the string comaccess to SNMP allowing read-only access and specifies that IP access list 4 can use the community string:
snmp-server community comaccess ro 4The following example assigns the string mgr to SNMP allowing read-write access to the objects in the restricted view:
snmp-server community mgr view restricted rwThe following example removes the community comaccess.
no snmp-server community comaccessThe following example disables both versions of SNMP:
no snmp-serverRelated Commands
access-list
Configures the access list mechanism for filtering frames by protocol type or vendor code.
Creates or update a view entry.
snmp-server contact
To set the system contact (sysContact) string, use the snmp-server contact global configuration command. Use the no form to remove the system contact information.
snmp-server contact text
no snmp-server contact
Syntax Description
Defaults
No system contact string is set.
Command Modes
Global configuration
Command History
Examples
The following is an example of a system contact string:
snmp-server contact Dial System Operator at beeper # 27345Related Commands
snmp-server context
This command is no longer valid. The functionality provided by this command has been removed from the Cisco IOS software.
snmp-server enable traps
To enable the router to send SNMP traps and informs, use the snmp-server enable traps global configuration command. Use the no form of this command to disable SNMP notifications.
snmp-server enable traps [notification-type] [notification-option]
no snmp-server enable traps [notification-type] [notification-option]
Syntax Description
Defaults
This command is disabled by default. Most notification types are disabled. However, some notification types cannot be controlled with this command. For example, some notification types are always enabled. Other notification types can be controlled through other commands. For example, after enabling linkUp and linkDown notifications globally, you can disable or re-enable these notifications on a per-interface basis using the snmp trap link-status interface configuration command.
If you enter this command with no notification-type keywords, the default is to enable all notification types controlled by this command.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is useful for disabling notifications that are generating a large amount of uninteresting or useless noise.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types.
If you do not enter an snmp-server enable traps command, no notifications controlled by this command are sent. In order to configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. In order to enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order to send notifications, you must configure at least one snmp-server host command.
For a host to receive a notification controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the notification type is not controlled by this command, just the appropriate snmp-server host command must be enabled.
The notification types used in this command all have an associated MIB object that allows them to be globally enabled or disabled. Not all of the notification types available in the snmp-server host command have notificationEnable MIB objects, so some of these cannot be controlled using the snmp-server enable command.
The snmp-server enable traps snmp form of this command enables the notifications (traps) defined in RFC 1157. Specificall, this command globally enables authentication Failure notifications, link status (linkUp / linkDown) notifications, and coldstart notifications. After enabling linkUp/linkDown traps globally, you can disable the sending of these traps on a per-interface basis using the snmp trap link-status command in interface configuration mode. The linkUp/linkDown traps are enabled by default on all interfaces, but will not be sent until the snmp-server enable traps snmp global configuration command is executed. New CLI keywords for controlling these traps individually were introduced in Cisco IOS Release 12.1(3)T and 12.0(20)S.
Examples
The following example enables the router to send all traps to the host myhost.cisco.com using the community string public:
snmp-server enable trapssnmp-server host myhost.cisco.com publicThe following example enables the router to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string public:
snmp-server enable traps frame-relaysnmp-server enable traps envmon temperaturesnmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps.
snmp-server enable traps bgpsnmp-server host bob public isdnThe following example enables the router to send all inform requests to the host myhost.cisco.com using the community string public:
snmp-server enable trapssnmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server host
To specify the recipient of an SNMP notification operation, use the snmp-server host global configuration command. Use the no form of this command to remove the specified host.
snmp-server host host [traps | informs] [version {1 | 2c}] community-string [udp-port port] [notification-type]
no snmp-server host host [traps | informs]
Syntax Description
Defaults
This command is disabled by default. No notifications are sent.
If you enter this command with no keywords, the default is to send all trap types to the host. No informs will be sent to this host.
If no version keyword is present, the default is SNMPv1. If no traps or informs keyword is present, traps are enabled.
The no snmp-server host command with no keywords will disable traps, but not informs, to the host. In order to disable informs, use the no snmp-server host informs command.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response PDU. If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely to reach their intended destination.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once, while an inform may be retried several times. The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. In order to configure the router to send SNMP notifications, you must enter at least one snmp-server host command. If you enter the command with no keywords, all trap types are enabled for the host. In order to enable multiple hosts, you must issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command will be in effect. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable command. Use the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable command and the snmp-server host command for that host must be enabled.
However, some notification types cannot be controlled with the snmp-server enable command. For example, some notification types are always enabled. Other notification types are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command. These notification types do not require an snmp-server enable command.
A notification-type option's availability depends on the router type and Cisco IOS software features supported on the router. For example, the envmon notification-type is available only if the environmental monitor is part of the system.
Examples
The following example sends the SNMP traps defined in RFC 1157 to the host specified by the name myhost.cisco.com. The community string is defined as comaccess.
snmp-server enable trapssnmp-server host myhost.cisco.com comaccess snmpThe following example sends the SNMP and Cisco environmental monitor enterprise-specific traps to address 172.30.2.160:
snmp-server enable trapssnmp-server host 172.30.2.160 public snmp envmonThe following example enables the router to send all traps to the host myhost.cisco.com using the community string public:
snmp-server enable trapssnmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but only the ISDN traps are enabled to be sent to a host.
snmp-server enable traps bgpsnmp-server host bob public isdnThe following example enables the router to send all inform requests to the host myhost.cisco.com using the community string public:
snmp-server enable trapssnmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server informs
To specify inform request options, use the snmp-server informs global configuration command. The no form of this command returns the settings to the defaults.
snmp-server informs [retries retries] [timeout seconds] [pending pending]
no snmp-server informs [retries retries] [timeout seconds] [pending pending]
Syntax Description
Defaults
Inform requests are resent three times. Informs are resent after 30 seconds if no response is received. The maximum number of informs waiting for acknowledgments at any one time is 25.
Command Modes
Global configuration
Command History
Examples
If you are seeing a large number of inform drops, you may want to increase the pending queue size.
snmp-server informs pending 50If you are sending informs over slow network links, you may want to increase the default timeout. Since informs will be sitting in the queue for a longer period of time, you may also need to increase the pending queue size.
snmp-server informs timeout 60 pending 40If you are sending informs over very fast links, you may want to decrease the default timeout.
snmp-server informs timeout 5If you are sending informs over unreliable links, it may be desirable to increase the retry count. Since informs will be sitting in the queue for a longer period of time, you may need to increase the pending queue size.
snmp-server informs retries 10 pending 45Related Commands
snmp-server location
To set the system location string, use the snmp-server location global configuration command. Use the no form of this command to remove the location string.
snmp-server location text
no snmp-server location
Syntax Description
Defaults
No system location string is set.
Command Modes
Global configuration
Command History
Examples
The following example illustrates a system location string:
snmp-server location Building 3/Room 214Related Commands
snmp-server manager
To start the SNMP manager process, use the snmp-server manager global configuration command. The no form of this command stops the SNMP manager process.
snmp-server manager
no snmp-server manager
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The SNMP manager process sends SNMP requests to agents and receives SNMP responses and notifications from agents. When the SNMP manager process is enabled, the router can query other SNMP agents and process incoming SNMP traps.
Most network security policies assume that routers will be accepting SNMP requests, sending SNMP responses, and sending SNMP notifications. With the SNMP manager functionality enabled, the router may also be sending SNMP requests, receiving SNMP responses, and receiving SNMP notifications. The security policy implementation may need to be updated prior to enabling this functionality.
SNMP requests are typically sent to UDP port 161. SNMP responses are typically sent from UDP port 161. SNMP notifications are typically sent to UDP port 162.
Examples
The following example enables the SNMP manager process:
snmp-server managerRelated Commands
snmp-server manager session-timeout
To set the amount of time before a non-active session is destroyed, use the snmp-server manager session-timeout global configuration command. The no form of this command returns the value to its default.
snmp-server manager session-timeout seconds
no snmp-server manager session-timeout
Syntax Description
Defaults
Idle sessions time out after 600 seconds (10 minutes).
Command Modes
Global configuration
Command History
Usage Guidelines
Sessions are created when the SNMP manager in the router sends SNMP requests, such as inform requests, to a host or receives SNMP notifications from a host. One session is created for each destination host. If there is no further communication between the router and host within the session timeout period, the session will be deleted.
The router tracks statistics, such as the average round-trip time required to reach the host, for each session. Using the statistics for a session, the SNMP manager in the router can set reasonable timeout periods for future requests, such as informs, for that host. If the session is deleted, all statistics are lost. If another session with the same host is later created, the request timeout value for replies will return to the default value.
However, sessions consume memory. A reasonable session timeout value should be large enough such that regularly used sessions are not prematurely deleted, yet small enough such that irregularly used, or one-shot sessions, are purged expeditiously.
Examples
The following example sets the session timeout to a larger value than the default:
snmp-server managersnmp-server manager session-timeout 1000Related Commands
Displays the current set of pending SNMP requests.
Displays the current SNMP sessions.
Starts the SNMP manager process.
snmp-server packetsize
To establish control over the largest SNMP packet size permitted when the SNMP server is receiving a request or generating a reply, use the snmp-server packetsize global configuration command. Use the no form of this command to restore the default value.
snmp-server packetsize byte-count
no snmp-server packetsize
Syntax Description
Defaults
1500 bytes
Command Modes
Global configuration
Command History
Examples
The following example establishes a packet filtering of a maximum size of 1024 bytes:
snmp-server packetsize 1024Related Commands
snmp-server party
This command is no longer valid. The functionality provided by this command has been removed from the Cisco IOS software.
snmp-server queue-length
To establish the message queue length for each trap host, use the snmp-server queue-length global configuration command.
snmp-server queue-length length
Syntax Description
length
Integer that specifies the number of trap events that can be held before the queue must be emptied.
Defaults
10 events
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines the length of the message queue for each trap host. Once a trap message is successfully transmitted, software will continue to empty the queue, but never faster than at a rate of four trap messages per second.
Examples
The following example establishes a message queue that traps four events before it must be emptied:
snmp-server queue-length 4Related Commands
Establishes control over the largest SNMP packet size permitted when the SNMP server is receiving a request or generating a reply.
snmp-server system-shutdown
To use the SNMP message reload feature, the router configuration must include the snmp-server system-shutdown global configuration command. The no form of this command prevents an SNMP system-shutdown request (from an SNMP manager) from resetting the Cisco agent.
snmp-server system-shutdown
no snmp-server system-shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
This command is not included in the configuration file.
Command Modes
Global configuration
Command History
Examples
The following example enables the SNMP message reload feature:
snmp-server system-shutdownsnmp-server tftp-server-list
To limit the TFTP servers used via SNMP-controlled TFTP operations (saving and loading configuration files) to the servers specified in an access list, use the snmp-server tftp-server-list global configuration command. To disable this feature, use the no form of this command.
snmp-server tftp-server-list number
no snmp-server tftp-server-list
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Examples
The following example limits the TFTP servers that can be used for configuration file copies via SNMP to the servers in access list 44.
snmp-server tftp-server-list 44snmp-server trap-authentication
The snmp-server enable traps snmp a
