Table Of Contents
show rtr distributions-statistics
show rtr enhanced-history collection-statistics
show rtr enhanced-history distribution-statistics
show rtr group schedule
show rtr history
show rtr operational-state
show rtr reaction-trigger
show rtr responder
show rtr totals-statistics
show running-config
show running-config map-class
show saa apm cache
show saa apm information
show saa apm operation
show saa apm results
show slot
show slot0:
show slot1:
show snmp
show snmp engineID
show snmp group
show snmp mib
show snmp mib ifmib ifindex
show snmp mib notification-log
show snmp pending
show snmp sessions
show snmp user
show sntp
show stacks
show startup-config
show subsys
show tcp
show tcp brief
show tdm data
show tech-support
show time-range
show version
show whoami
show xsm status
show xsm xrd-list
showmon
snmp ifmib ifalias long
snmp mib notification-log default
snmp mib notification-log default disable
snmp mib notification-log globalageout
snmp mib notification-log globalsize
snmp mib persist
snmp trap link-status
snmp-server chassis-id
snmp-server community
snmp-server contact
snmp-server enable informs
show rtr distributions-statistics
To display statistic distribution information (captured response times) for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr distributions-statistics command in EXEC mode.
show rtr distributions-statistics [operation] [tabular | full]
Syntax Description
operation
|
(Optional) Number of the SAA operation to display.
|
tabular
|
(Optional) Displays information in a column format reducing the number of screens required to display the information. This is the default.
|
full
|
(Optional) Displays all information using identifiers next to each displayed value.
|
Defaults
Tabular format for all operations is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3(01)
|
This command integrated in Release 12.3
|
12.3(14)T
|
This command was replaced by the show ip sla monitor statistics command.
|
Usage Guidelines
The distributions statistics consist of the following:
•
The sum of completion times (used to calculate the mean)
•The sum of the completions times squared (used to calculate standard deviation)
•The maximum and minimum completion time
•The number of completed attempts
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.
For enhanced-history distribution statistics, see the show rtr enhanced-history distribution-statistics command.
Examples
The following is sample output from the show rtr distributions-statistics command in tabular format when the output is split over multiple lines
Router# show rtr distributions-statistics
StartT = Start Time of Entry (hundredths of seconds)
Dst = Time Distribution Index
Comps = Operations Completed
OvrTh = Operations Completed Over Thresholds
SumCmp = Sum of Completion Times (milliseconds)
SumCmp2L = Sum of Completion Times Squared Low 32 Bits (milliseconds)
SumCmp2H = Sum of Completion Times Squared High 32 Bits (milliseconds)
TMax = Completion Time Maximum (milliseconds)
TMin = Completion Time Minimum (milliseconds)
Entry StartT Pth Hop Dst Comps OvrTh SumCmp
SumCmp2L SumCmp2H TMax TMin
The following example shows the output as it appears on a single line:
Entry StartT Pth Hop Dst Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
10 3581 1 1 1 0 0 0 0 0 0 0
Related Commands
Command
|
Description
|
show rtr collection-statistics
|
Displays statistical errors for all SAA operations or the specified operation.
|
show rtr configuration
|
Displays configuration values including all defaults for all SAA operations or the specified operation.
|
show rtr totals-statistics
|
Displays the total statistical values (accumulation of error counts and completions) for all SAA operations or the specified operation.
|
show rtr enhanced-history collection-statistics
To display enhanced history statistics for all collected history buckets for the specified Service Assurance Agent (SAA) operation, use the show rtr enhanced-history collection-statistics command in user EXEC or privileged EXEC mode.
show rtr enhanced-history collection-statistics [operation-number] [interval seconds]
Syntax Description
operation-number
|
(Optional) Displays enhanced history distribution statistics for only the specified operation.
|
interval seconds
|
(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval.
•This keyword will not function for SLM operations.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced in Early Deployment Release 12.2T.
|
12.3(01)
|
This command was integrated in Release 12.3.
|
Usage Guidelines
This command displays data for each bucket of enhanced history data shown individually (one after the other).
The number of buckets and the collection interval is set using the enhanced-history interval seconds buckets number-of-buckets SAA RTR configuration mode command.
For SLM operations, the enhanced history collection interval is set at 900 seconds and the number of buckets is set at 100. Because the enhanced history aggregation interval is fixed at 900 seconds, the optional interval keyword available for this command will not work for SLM operations.
Examples
The output of this command will vary depending on the operation type. The following examples show output for various SAA operations.
Output for SLM Controller Operation
Router# show rtr configuration 1 | include Type
Type of operation to perform: slm controller
Router# show running-config | begin rtr
enhanced-history interval 900 buckets 100
rtr schedule 1 start-time now life forever
Router# show rtr enhanced-history collection-statistics 1
Aggregation Interval: 900
Aggregation start time 00:15:00.003 UTC Thur May 1 2003
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Ds1StatRxLineStatus: 16385
Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0
Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0
Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0
Table 103 describes the significant fields shown in the display.
Table 103 show rtr enhanced-history Field Descriptions for SLM Controller Operations
Field
|
Description
|
Aggregation Interval:
|
The number of seconds the operation runs for each enhanced history bucket. For example, a value of 900 indicates that statistics were gathered for 15 minutes before the next bucket was created.
|
Bucket Index:
|
The number identifying the collection bucket. The number of buckets is set using the enhanced-history SAA RTR configuration command.
|
Ds1StatRx
|
DS1 and E1 Received Statistics—The Ds1StatRx prefix is used for DS1 and E1 interfaces. DS1 and E1 interfaces are physical interfaces that run at a medium speed (for example, 1544 Kbps for DS1 interfaces). "Rx" indicates "received."
|
Ds1StatRxLineStatus:
|
Line Status—This variable indicates the Line Status of the interface. The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple conditions, like Excess Zeros and B8ZS detect, simultaneously. For example, the outOfFrame condition is implied by an outOfSignal condition.
Possible values include:
•2 — yellowAlarm
•8 — blueAlarm
•32 — outOfFrame
•64 — outOfSignal
•8192 — excessZeros
•16384 — b8zsDetect
|
Ds1StatRxBPVs:
|
Bi-Polar Violations—The total number of Bipolar Violations (BPVs) received on the interface.
|
Ds1StatRxCrcFrameErrors:
|
CRC or Frame Errors—he total number of Cyclic Redundancy Check (CRC) Errors (with ESF framing) or Frame Errors (with D4 framing) received on the interface.
|
Ds1StatRxErrSecs:
|
Errored Seconds—The total number of Errored Seconds that have occurred on the interface. This includes both Line Errored and Path Errored Seconds.
|
Ds1StatRxSevereErrSecs:
|
Severely Errored Seconds—The total number of Severely Errored Seconds that have occurred on the interface. This includes both Line Severely Errored Seconds and Path Severely Errored Seconds.
|
Ds1StatRxUnavailSecs:
|
Unavailable Seconds—The total number of Unavailable Seconds that have occurred on the interface.
|
Ds1StatRxBurstyErrSecs:
|
Type B Errored Seconds—The total number of Type B (Bursty) Errored Seconds that have occurred on the interface.
|
Ds1StatRxREBEs:
|
E1 Remote-End Block Errors—The total number of Remote-End Block Error (REBE) Events received on an E1 interface. (This data does not appear for DS1 interfaces.)
|
Output for SLM Frame Relay Operation
Router# show rtr configuration 2 | include Type
Type of operation to perform: Slm Frame-relay Interface
Router# show rtr ennhanced-history collection-statistics 2
Aggregation Interval: 900
Aggregation start time 00:15:00.003 UTC Mon Mar 1 1993
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Tx Total Frames: 24 Rx Total Frames: 24
Tx Total Octets: 312 Rx Total Octets: 344
Tx FCSAlignErrors: 0 Rx FCSAlignErrors: 0
Tx Aborted Frames: 0 Rx Aborted Frames: 0
Tx Long Frames: 0 Rx Long Frames: 0
Tx Short Frames: 0 Rx Short Frames: 0
Tx MaxThroughput: 88 Rx MaxThroughput: 152
Tx MaxUtilization: 0 Rx MaxUtilization: 0
Tx MaxFramesSec: 1 Rx MaxFramesSec: 1
UnavailSecs: 0 Drop Events: 0
Tx OverFlowOctets: 0 Rx OverFlowOctets: 0
Tx Burst Percent1(sec): 238 Rx Burst Percent1(sec): 238
Tx Burst Percent2(sec): 0 Rx Burst Percent2(sec): 0
Tx Burst Percent3(sec): 0 Rx Burst Percent3(sec): 0
Tx Burst Percent4(sec): 0 Rx Burst Percent4(sec): 0
Tx Burst Percent5(sec): 0 Rx Burst Percent5(sec): 0
Table 104 describes the significant fields shown in the display. In the output "Tx" indicates "transmitted," "Rx" indicates "received."
Table 104 show rtr enhanced-history collection-statistics Field Descriptions for SLM Frame Relay Operations
Field
|
Description
|
LinkState
|
The Link State of the Frame Relay access channel being monitored. The link state is determined by the presence of LMI messages on the user and network side of the line.
The link state can take the following values:
•up(1)—Both sides of the access channel are up.
•networkDown(2)—The network side of the circuit has not responded to at least frDlcmiErrorThreshold Status Enquiry messages.
•userDown(3)—The user side of the access channel has not sent a Status Enquiry LMI message in FrConfigPollingTimeoutInterval (T391) seconds.
•down(4)—Both sides of the access channel have been down over some portion of the sampling interval.
•spoofNetworkUp(5)—The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been up over the entire sampling interval.
•spoofNetworkDown(6)— The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been down over the entire sampling interval.
|
Tx Total Frames:
|
The total number of frames (including errored frames) transmitted by the interface. Aborted frames are not included in this count.
(MIB variable: FrStatTxFrames)
|
Rx Total Frames:
|
The total number of non-errored frames received by the interface. Aborted frames are not included.
(MIB variable: FrStatRxFrames)
|
Tx Total Octets:
|
The total number of octets transmitted in frames from the interface (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count.
(MIB variable: FrStatTxOctets)
|
Rx Total Octets:
|
The total number of octets received by the interface in non-errored frames (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count.
(MIB variable: FrStatRxOctets)
|
Tx FCSAlignErrors:
|
The total number of frames transmitted by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Agents that cannot count this transmit-side object will return a value of zero.
(MIB variable: FrStatTxFcsAlignErrors)
|
Rx FCSAlignErrors:
|
The total number of frames received by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
(MIB variable: FrStatRxFcsAlignErrors)
|
Tx Burst Percent1(sec):
|
The number of one second intervals where the transmitted throughput (t) is greater than or equal to zero and less than or equal to BurstLimit 1 (0 <= t <= BurstLimit1). BurstLimit1 is defined as a percentage of the CircuitBurstNominalRate in the RTTMON MIB.
Note: The burst parameters used in this definition are defined in the CircuitConfigTable of the RTTMON MIB.
|
show rtr enhanced-history distribution-statistics
To display enhanced history distribution statistics for Service Assurance Agent (SAA) operations in tabular format, use the show rtr enhanced-history distribution-statistics command in user EXEC or privileged EXEC mode.
show rtr enhanced-history distribution-statistics [operation-number [interval seconds]]
Syntax Description
operation-number
|
(Optional) Displays enhanced history distribution statistics for only the specified operation.
|
interval seconds
|
(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval for only the specified operation.
•The valid range is from 1 to 3,600 seconds (1 hour).
The default is 900 seconds.
•This keyword will not function for SLM operations.
|
Command Modes
User Exec
Privileged Exec
Command History
Release
|
Modification
|
12.3(01)
|
This command was introduced.
|
Usage Guidelines
Enhanced history statistics (recorded in milliseconds instead of centiseconds) are enabled using the enhanced-history command when configuring the SAA operation.
The distribution statistics consist of the following:
•The sum of completion times (used to calculate the mean)
•The sum of the completion times squared (used to calculate standard deviation)
•The maximum and minimum completion times
•The number of completed attempts
You can also use the following commands to display additional statistics or history information, or to view the status of the operation:
•show rtr enhanced-history collection-statistics
•show rtr enhanced-history totals-statistics
Tip If the character `n' appears in your output, or not all fields are displayed, you should increase the screen width for your CLI display (for example, using the width line configuration command or the terminal width Exec mode command).
Examples
The following is sample output from the show rtr enhanced-history distribution-statistics command for an SLM Frame Relay Circuit (Slm Frame-relay Pvc) operation. Please note the following:
•The fields are defined at the beginning of the output for the command.
•RTT means round-trip-time.
•The time elapsed between BucketIndex 1 (started at 257,850,000) and BucketIndex 2 (started at 258,750,002) in this example is 900,002 milliseconds, or 900 seconds.
•Table 129 provides further details about the significant fields shown in this output.
Router# show rtr configuration 3 | include Type
Type of operation to perform: Slm Frame-relay Pvc
Router# show rtr enhanced-history distribution-statistics 3
Point by point Enhanced History
Int = Aggregation Interval (seconds)
StartT = Aggregation Start Time
Comps = Operations completed
OvrTh = Operations completed over thresholds
SumCmp = Sum of RTT (milliseconds)
SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)
SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)
TMax = RTT maximum (milliseconds)
TMin = RTT minimum (milliseconds)
Entry Int BucI StartT Pth Hop Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
3 900 1 257850000 1 1 3 0 43 617 0 15 14
3 900 2 258750002 1 1 3 0 45 677 0 16 14
3 900 3 259650000 1 1 3 0 44 646 0 15 14
3 900 4 260550002 1 1 3 0 42 594 0 15 12
3 900 5 261450003 1 1 3 0 42 590 0 15 13
3 900 6 262350001 1 1 3 0 46 706 0 16 15
3 900 7 263250003 1 1 3 0 46 708 0 16 14
Table 105 show rtr enhanced-history distribution-statistics Field Descriptions
Field
|
Description
|
|
The operation ID number you specified for the SAA operation.
|
|
Aggregation Interval - This is the configured statistical distribution buckets interval, in seconds.
For example, a value of 900 for Int means that statistics are gathered for 900 seconds per bucket.
|
|
Bucket Index Number—A number uniquely identifying the statistical distribution (aggregation) bucket.
•The number of history buckets to be kept is configured using the buckets-of-history-kept command.
•A bucket will gather statistics for the specified interval of time (aggregation interval), after which a new statistics bucket is created.
•If a number-of-buckets-kept value is configured, the interval for the last bucket is infinity (until the end of the operation).
•Buckets are not applicable to HTTP and Jitter monitoring operations.
•This field is equivalant to the rttMonStatsCaptureDistIndex object in the Cisco Rttmon MIB.
|
|
|
Aggregation Start Time — Start time for the aggregation interval (per Bucket Index).
•Shows the start time as the number of milliseconds since the router started; in other words, the time stamp is the number of milliseconds since the last system boot-up.
|
|
Path Index Number — The Path index number is an idenitifier for a set of different paths to the target destination that have been discovered. For example, if the first probe iteration finds the path h1, h2, h3, h4, then this path is labeled as "1". If, on a later iteration, a new path is discovered, say h1, h2, h5, h6, h4, then this new path will be identified as "2", and so on.
•Data collection per path is available only for IP/ICMP Path Echo operations ("pathEcho probes"). For all other operations, a value of "1" will always appear.
•Data collection per path is configured using the paths-of-statistics-kept number command when configuring the operation.
|
|
Hop Index Number — Statistics data per hop. A hop is data transmission between two points in a path (for example, from device h2 to device h3).
•Data collection per hop is available only for IP/ICMP Path Echo operations ("pathEcho probes"). For all other operations, a value of "1" will always appear.
•Data collection per hop is configured using the hops-of-statistics-kept number command when configuring the operation.
•This field is equivalant to the rrttMonStatsCaptureHopIndex object in the Cisco Rttmon MIB.
|
Comps (Completed
Round-Trip-Time Probes)
|
Completions —The number of RTT probes that have completed without an error and without timing out, per bucket index.
•This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the Cisco Rttmon MIB object.
|
SumCmp (Sum of Completed
Round-Trip-Times)
|
Sum of Completed Probe Times (1) — The total of all round-trip-time values for all succesfull probes in the row, in milliseconds.
|
SumCmp2L (Sum of Squares
of Completed
Round-Trip-Times,
Squared, Low-Order Value)
|
Sum of the Squares of Completed Probe Times (2), Low-Order — The sum of the square roots of round-trip-times for probes that were successfully measured, in milliseconds; displays the low-order 32 bits of the value only.
•32 low-order bits and 32 high-order bits are ordered in unsigned 64-bit integers (Int64) as follows:
-------------------------------------------------
| High-order 32 bits | Low-order 32 bits |
-------------------------------------------------
•The "SumCmp2" values are split into "high-order" and "low-order" numbers because of limitations of SNMP. The maximum value allowed for an SNMP object is 4,294,967,295 (the `Gauge32' limit).
If the sum of the square roots for your operation exceeds this value, then the "high-order" value will be utilized. (For example, the number 4,294,967,296 would have all low-order bits as '0', and the rightmost high-order bit would be `1').
•The Low-order value (SumCmp2L) appears first in the output because in most cases, the value will be less than 4,294,967,295, which means that the value of SumCmp2H will appear as zero. For example:
|
SumCmp2H (Sum of Squares
of Completed
Round-Trip-Times,
Squared, High-order
Value)
|
Sum of the Squares of Completed Probe Times (2), High-Order— The high-order 32 bits of the accumulated squares of completion times (in milliseconds) of probe operations which completed successfully.
|
|
Round-Trip-Time, Maximum— The highest recorded round-trip-time, in milliseconds, per aggregation interval.
|
|
Round-Trip-Time, Minimum—The lowest recorded round-trip-time, in milliseconds, per aggregation interval.
|
Related Commands
Command
|
Description
|
rtr
|
Allows configuration of SAA operations by entering rtr configuration mode for the specified operation number.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.
|
show rtr group schedule
To display the group schedule details of the Service Assurance Agent (SAA) operations, use the show rtr group schedule command in user EXEC or privileged EXEC mode.
show rtr group schedule [group-operation-number]
Syntax Description
group-operation-number
|
(Optional) Number of the SAA group operation to display.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced as part of the Service Assurance Agent (SAA) Multi-Operation Scheduler (Multiple Operation Scheduling) feature.
|
12.2(25)S
|
This command was integrated in Release 12.2S.
|
Note This command not available in Release 12.3(x) (the 12.3 "mainline" release).
Examples
The following is sample output from the show rtr group schedule command that shows information about group (multiple) scheduling. The last line in the example indicates that the SAA operations are multiple scheduled (TRUE):
Router# show rtr group schedule
Multi-Scheduling Configuration:
Probes to be scheduled: 2,3,4,9-30,89
Group operation frequency: 30
The following is sample output from the show rtr group schedule command that shows information about group (multiple) scheduling, with the frequency value the same as the schedule-period value, the life value as 3600 seconds, and the ageout value as never:
Router# show rtr group schedule
Probes to be scheduled: 3,4,6-10
Total number of probes: 7
Group operation frequency: Equals schedule period
Status of entry (SNMP RowStatus): Active
Next Scheduled Start Time: Start Time already passed
Entry Ageout (seconds): never
Table 106 describes the significant fields shown in the displays.
Table 106 show rtr group schedule Field Descriptions
Field
|
Description
|
Group Entry Number
|
The operation group number specified for SAA multiple operations scheduling.
|
Probes to be scheduled
|
The operations numbers specified in the operation group 1.
|
Scheduled period
|
The time in seconds you mentioned while scheduling the operation.
|
Group operation frequency
|
The frequency at which each operation is started.
|
Multi-scheduled
|
The value TRUE shows that group scheduling is active.
|
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays the scheduling details.
|
show running configuration
|
Displays the configuration details which includes the SAA multiple operations scheduling information.
|
show rtr history
To display history collected for all Service Assurance Agent (SAA) operations or for a specified operation, use the show rtr history command in EXEC mode.
show rtr history [operation-number] [tabular | full]
Syntax Description
operation-number
|
(Optional) Displays history for only the specified operation.
|
tabular
|
(Optional) Displays information in a column format reducing the number of screens required to display the information. This is the default.
|
full
|
(Optional) Displays all information using identifiers next to each displayed value.
|
Defaults
Tabular format history for all operations is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
Table 131 lists the Response Return values used in the output of the show rtr history command. If the default (tabular) format is used, the Response Return description is displayed as a code in the Sense column. If the full format is used, the Response Return is displayed as indicated in the Description column.
Table 107 Response Return (Sense Column) Codes
Code
|
Description
|
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:
SampleT = Sample Start Time
CompT = Completion Time (milliseconds)
Sense = Response Return Code
Line 2 has the Target Address
Entry LifeI BucketI SampleI SampleT CompT Sense
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays configuration values including all defaults for all SAA operations or the specified operation.
|
show rtr operational-state
Note Effective with Cisco IOS Release 12.3(14)T, the show rtr operational-state command is replaced by the show ip sla monitor statistics command. See the show ip sla monitor statistics command for more information.
To display the operational state of all Cisco IOS IP Service Level Agreements (IP SLAs) operations or a specified operation, use the show rtr operational-state command in EXEC mode.
show rtr operational-state [operation-number]
Syntax Description
operation-number
|
(Optional) ID number of the IP SLAs operation to display.
|
Defaults
Displays output for all running IP SLAs operations.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.0(5)T
|
Output for the Jitter operation type was added.
|
12.1
|
The tabular and full keywords were removed.
|
12.2(8)T
|
Output for "NumOfJitterSamples" was added (CSCdv30022).
|
12.2(8)S
|
Output for "NumOfJitterSamples" was added (CSCdv30022).
|
12.3(4)T
|
Output (MOS and ICPIF scores) for the Jitter (codec) operation type was added.
|
12.3(7)T
|
Decimal granularity for MOS scores was added.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor statistics command.
|
Usage Guidelines
Use the show rtr operational-state command to display the current state of IP SLAs operations, including how much life the operation has left, whether the operation is active, and the completion time. The output will also include the monitoring data returned for the last (most recently completed) operation.
Examples
The following example shows basic sample output from the show rtr operational-state command:
Router# show rtr operational-state
Current Operational State
Modification Time: *22:15:43.000 UTC Sun Feb 11 2001
Last Time this Entry was Reset: Never
Number of Octets in use by this Entry: 1332
Number of Operations Attempted: 2
Current Seconds Left in Life: 3511
Operational State of Entry: active
Latest Completion Time (milliseconds): 544
Latest Operation Start Time: *22:16:43.000 UTC Sun Feb 11 2001
Latest Sense Description: 200 OK
HTTP Transaction RTT: 504
The following example shows sample output from the show rtr operational-state command when the specified operation is a Jitter (codec) operation:
Router# show rtr operational-state 1
Modification time: 13:18:38.012 PST Mon Jun 24 2002
Number of Octets Used by this Entry: 10392
Number of operations attempted: 2
Number of operations skipped: 0
Current seconds left in Life: Forever
Operational state of entry: Active
Last time this entry was reset: Never
Connection loss occurred: FALSE
Over thresholds occurred: FALSE
Latest RTT (milliseconds): 2
Latest operation start time: *13:18:42.896 PST Mon Jun 24 2002
Latest operation return code: OK
ICPIF Value: 0 MOS score: 0
NumOfRTT: 61 RTTAvg: 2 RTTMin: 2 RTTMax: 3
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0
InternalError: 0 Busies: 0 PacketSkipped: 39 <<<<<<==========
MinOfPositivesSD: 1 MaxOfPositivesSD: 1
NumOfPositivesSD: 1 SumOfPositivesSD: 1 Sum2PositivesSD: 1
MinOfNegativesSD: 1 MaxOfNegativesSD: 1
NumOfNegativesSD: 1 SumOfNegativesSD: 1 Sum2NegativesSD: 1
MinOfPositivesDS: 0 MaxOfPositivesDS: 0
NumOfPositivesDS: 0 SumOfPositivesDS: 0 Sum2PositivesDS: 0
MinOfNegativesDS: 0 MaxOfNegativesDS: 0
NumOfNegativesDS: 0 SumOfNegativesDS: 0 Sum2NegativesDS: 0
Interarrival jitterout: 0 Interarrival jitterin: 0
OWMinSD: 0 OWMaxSD: 0 OWSumSD: 0 OWSum2SD: 0
OWMinDS: 0 OWMaxDS: 0 OWSumDS: 0 OWSum2DS: 0
The values shown indicate the values for the last IP SLAs operation. RTT stands for Round-Trip-Time. SD stands for Source-to-Destination. DS stands for Destination-to-Source. OW stands for One Way. The * symbol in front of the time stamps indicates the time is synchronized using NTP or SNTP. Table 108 describes the significant fields shown in this output.
Table 108 show rtr operational-state Field Descriptions
Field
|
Description
|
Voice Scores:
|
Indicates that Voice over IP statistics appear on the following lines. Voice score data is computed when the operation type is configured as type jitter (codec).
|
ICPIF:
|
The Calculated Planning Impairment Factor (ICPIF) value for the latest iteration of the operation. The ICPIF value is computed by IP SLAs using the formula Icpif = Io + Iq + Idte + Idd + Ie - A, where
•the values for Io, Iq, and Idte are set to zero,
•the value Idd is computed based on the measured one way delay,
•the value Ie is computed based on the measured packet loss,
•and the value of A is specified by the user.
ICPIF values are expressed in a typical range of 5 (very low impairment) to 55 (very high impairment). ICPIF values numerically less than 20 are generally considered "adequate."
Note This value is intended only for relative comparisons, and may not match ICPIF values generated using alternate methods.
|
MOS:
|
The estimated Mean Opinion Score (Conversational Quality, Estimated) for the latest iteration of the operation. The MOS-CQE is computed by IP SLAs as a function of the ICPIF.
MOS values are expressed as a number from 1 (1.00) to 5 (5.00), with 5 being the highest level of quality, and 1 being the lowest level of quality. A MOS value of 0 (zero) indicates that MOS data could not be generated for the operation.
|
RTT Values:
|
Indicates that Round-Trip-Time statistics appear on the following lines.
|
NumOfRTT
|
The number of successful round trips.
|
RTTSum
|
The sum of those round trip values (in milliseconds).
|
RTTSum2
|
The sum of squares of those round trip values (in milliseconds).
|
Packet Loss Values:
|
Indicates that Packet Loss statistics appear on the following lines.
|
PacketLossSD
|
The number of packets lost from source to destination.
|
PacketLossDS
|
The number of packets lost from destination to source.
|
PacketOutOfSequence
|
The number of packets returned out of order.
|
PacketMIA
|
The number of packets lost where the direction (SD or DS) cannot be determined (MIA: "missing in action").
|
PacketLateArrival
|
The number of packets that arrived after the timeout.
|
PacketSkipped
|
The number of packets that are not sent during the IP SLAs jitter operation.
|
InternalError
|
The number of times an operation could not be started due to other internal failures.
|
Busies
|
The number of times this operation could not be started because the previously scheduled run was not finished.
|
Jitter Values:
|
Indicates that jitter operation statistics appear on the following lines.
Jitter is inter-packet delay variance.
|
NumOfJitterSamples:
|
The number of jitter samples collected. This is the number of samples that are used to calculate the following jitter statitstics.
|
MinOfPositivesSD
MaxOfPositivesSD
|
The minimum and maximum positive jitter values from source to destination, in milliseconds.
|
NumOfPositivesSD
|
The number of jitter values from source to destination that are positive (i.e., network latency increases for two consecutive test packets).
|
SumOfPositivesSD
|
The sum of those positive values (in milliseconds).
|
Sum2PositivesSD
|
The sum of squares of those positive values.
|
MinOfNegativesSD
MaxOfNegativesSD
|
The minimum and maximum negative jitter values from source to destination. The absolute value is given.
|
NumOfNegativesSD
|
The number of jitter values from source to destination that are negative (i.e., network latency decreases for two consecutive test packets).
|
SumOfNegativesSD
|
The sum of those values.
|
Sum2NegativesSD
|
The sum of the squares of those values.
|
Interarrival jitterout:
|
The source to destination(SD) jitter value calculation, as defined in RFC 1889.
|
Interarrival jitterin:
|
The destination to souce (DS) jitter value calculation, as defined in RFC 1889.
|
One Way Values
|
Indicates that One Way measurement statistics appear on the following lines.
One Way (OW) Values are the amount of time it took the packet to travel from the source router to the target router (SD) or from the target router to the source router (DS).
|
NumOfOW
|
Number of successful one way time measurements.
|
OWMinSD
|
Minimum time from the source to the destination.
|
OWMaxSD
|
Maximum time from the source to the destination.
|
OWSumSD
|
Sum of the OWMinSD and OWMaxSD values.
|
OWSum2SD
|
Sum of the squares of the OWMinSD and OWMaxSD values.
|
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr reaction-trigger
To display the reaction trigger information for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr reaction-trigger command in EXEC mode.
show rtr reaction-trigger [operation-number] [tabular | full]
Syntax Description
operation-number
|
(Optional) Number of the SAA operation to display.
|
tabular
|
(Optional) Display information in a column format reducing the number of screens required to display the information.
|
full
|
(Optional) Display all information using identifiers next to each displayed value. This is the default.
|
Defaults
Full format for all operations
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3
|
This command was integrated in Release 12.3.
|
Usage Guidelines
Use the show rtr reaction-trigger command to display the configuration status and operational state of target operations 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 1
Status of Entry (SNMP RowStatus): active
Operational State: pending
Related Commands
