You can monitor RTR by displaying status and configuration information using the following tasks:
Display global information about RTR.
To display global information about RTR:
host1#show rtr application
numberOfEntries entriesEnabled entriesActive
------------------ ----------------- ---------------
echo 1 1 1
pathEcho 1 1 1
total 2 2 2Table 1 lists the show rtr application command output fields.
Table 1: show rtr application Output Fields
Field Name | Field Description |
|---|---|
numberOfEntries | Number of RTR entries according to type |
entriesEnabled | RTR entries with administrative status enabled |
entriesActive | RTR entries with operational status enabled |
Display statistical information for a particular probe operation or for all operations.
To display statistical information for all probe operations:
host1#show rtr collection-statistics
Echo Entries:
rtrIndex operationsSent operationsRcvd lastGoodResponse ---------- -------------- -------------- ---------------- 1 5208 5187 08/30/2000 05:09
rtrIndex operStatus minRtt maxRtt avgRtt rttSumSqr ---------- ---------- ------ ------ ------ --------- 1 enabled 0 1785 3 7109208
PathEcho Entries:
rtrIndex testAttempts testSuccesses lastGoodResponse ---------- ------------ ------------- ---------------- 2 156 156 08/30/2000 05:09
rtrIndex operStatus currentHop currentOperation ---------- ---------- ---------- ---------------- 2 enabled 2 4
Table 2 lists the show rtr collection-statistics command output fields.
Table 2: show rtr collection-statistics Output Fields
Field Name | Field Description |
|---|---|
rtrIndex | Index number of the RTR probe |
operationsSent | Number of probe operations sent |
operationsRcvd | Number of probe operations received |
lastGoodResponse | Time when last valid probe operation was received |
operStatus | Operational status of the probe: enabled, disabled |
minRtt | Minimum round-trip time in milliseconds |
maxRtt | Maximum round-trip time in milliseconds |
avgRtt | Average round-trip time in milliseconds |
rttSumSqr | Sum of the square of all round-trip times in milliseconds |
testAttempts | Number of times the test ran |
testSuccesses | Number of times the test ran successfully |
currentHop | Current hop (TTL) used in the test |
currentOperation | Current probe operation index sent to the hop |
Display the configuration for a particular probe or for all probes.
To display the configuration for all probes:
host1#show rtr configuration rtrIndex type targetAddress reqSize freq life ------- -------- ------------ ------ ------ ----- 1 echo 10.5.0.200 1 1 20 2 pathEcho 10.5.0.11 1 1 30
rtrIndex source restartTime owner ---------- ------------------ ----------- ---------- 1 fastEthernet0/0 10 2 60
rtrIndex samples admin tos reactionConfiguration ---------- ------- -------- --- ------------------------ 1 5 enabled 0 2 5 enabled 0
rtrIndex receiveInterface ---------- ---------------- 1 fastEthernet0/0
rtrIndex operFail testFail timeout tag ---------- -------- -------- ------- ------ 1 1 1 10000
rtrIndex operPerHop maxFail hopKpt tag ---------- ---------- ------- ------ ------ 2 5 3 16
Table 3 lists the show rtr configuration command output fields.
Table 3: show rtr configuration Output Fields
Field Name | Field Description |
|---|---|
rtrIndex | Index number of the RTR probe |
type | Probe type: echo, pathEcho |
targetAddress | Address of the probe’s target |
reqSize | Protocol data size in the request packet |
freq | Rate in seconds that the RTR probe uses to start a response time operation |
life | Length of the test |
source | Interface from which the probe is sent |
restartTime | Restart time of the test in seconds |
owner | Owner of the probe |
samples | Maximum number of entries saved in the history table for this RTR probe |
admin | Administrative status of the probe: enabled, disabled |
tos | Setting of the ToS byte in the probe’s IP header |
reactionConfiguration | RTR reactions that are configured for the probe |
receiveInterface | Type and specifier of the interface on which the probe expects to receive responses; this field is blank if the optional receive-interface characteristic is not configured |
operFail | Operation failure event is triggered when this number of consecutive probe operations is not received or when the operations are received after a timeout |
testFail | Test failure event is triggered when this number of probe operations is not received or when the operations are received after a timeout |
timeout | Time in milliseconds that the probe waits for a response |
tag | Identifier configured for the probe |
operPerHop | Number of RTR probe operations sent to a given hop |
maxFail | Maximum number of consecutive failures to respond to a probe’s request. When the maximum number is reached, the test stops. Applies only to pathEcho entries. |
hopKpt | Number of hops per path for which statistics are collected. When this number is reached, no additional statistical information about the path is stored. Applies only to pathEcho entries. |
Display history (data samples) for a particular probe or for all probes.
To display history (data samples) for all probes:
host1#show rtr history Echo Entries:
rtrIndex operation rtt statusDescription timeStamp -------- --------- --- ----------------- --------- 1 5476 0 responseReceived 08/30/2000 05:17 1 5477 0 responseReceived 08/30/2000 05:17 1 5478 0 responseReceived 08/30/2000 05:17 1 5479 0 responseReceived 08/30/2000 05:17 1 5480 0 responseReceived 08/30/2000 05:17
PathEcho Entries:
rtrIndex test hop operation rtt statusDescription
---------- ------ ---- --------- ------ -----------------
2 165 3 5 0 responseReceived
2 165 3 1 0 responseReceived
2 165 3 2 0 responseReceived
2 165 3 3 0 responseReceived
2 165 3 4 0 responseReceived rtrIndex test hop operation timeStamp address
---------- ------ ---- --------- ---------------- --------
2 165 3 5 08/30/2000 20:39 10.5.0.11
2 165 3 1 08/30/2000 20:40 10.5.0.11
2 165 3 2 08/30/2000 20:40 10.5.0.11
2 165 3 3 08/30/2000 20:40 10.5.0.11
2 165 3 4 08/30/2000 20:40 10.5.0.11Table 4 lists the show rtr history command output fields.
Table 4: show rtr history Output Fields
Field Name | Field Description |
|---|---|
rtrIndex | Index number of the RTR probe |
operation | Index number of the probe operation |
rtt | Round-trip time in milliseconds |
statusDescription |
|
timeStamp | Date and time when the RTR entry was created |
test | Index number of the pathEcho test |
hop | Index number of the hop count |
address | Address of router at the hop |
Display RTR hops information.
To display RTR hops information:
host1#show rtr hops
rtrIndex hop address minRtt maxRtt avgRtt rttSumSqr
---------- ---- ----------- ------ ------ ------ --------
2 1 192.168.1.1 1 276 1 955363
2 2 10.2.0.3 0 1109 2 10094451rtrIndex hop operationsSent operationsRcvd lastGoodResponse -------- --- -------------- -------------- ------------ 2 1 36985 36838 09/18/2000 20:20 2 2 30717 21494 09/18/2000 20:20
Table 5 lists the show rtr hops command output fields.
Table 5: show rtr hops Output Fields
Field Name | Field Description |
|---|---|
rtrIndex | Index number of the RTR probe |
hop | Index number of the hop count |
address | Address of the router at the hop |
minRtt | Minimum round-trip time in milliseconds |
maxRtt | Maximum round-trip time in milliseconds |
avgRtt | Average round-trip time in milliseconds |
rttSumSqr | Sum of the square of all round-trip times in milliseconds |
operationsSent | Number of probe operations sent |
operationsRcvd | Number of probe operations received |
lastGoodResponse | Time when last valid probe operation was received |
Display RTR operational information.
To display RTR operational information:
host1#show rtr operational-state
rtrIndex type entryStatus adminStatus operStatus
---------- -------- ----------- ----------- ----------
1 echo active enabled enabled
2 pathEcho active enabled enabled Table 6 lists the show rtr operational-state command output fields.
Table 6: show rtr operational-state Output Fields
Field Name | Field Description |
|---|---|
rtrIndex | Index number of the RTR probe |
type | Type of RTR probe: echo, pathEcho |
entryStatus | If the entry was created via the SNMP DISMAN MIB, the row may be partially constructed; if that is the case, the CLI displays notReady as the entry’s status |
adminStatus | Derived from the rtr schedule start-time command; if the option is now, the status is enabled; if the option is pending, the status is disabled |
operStatus | Enabled only if entryStatus and adminStatus are enabled and the test is running; operStatus remains enabled if the test finishes and restart time is not 0 |