Downloads |
Table Of Contents
Related Features and Technologies
Configuring Optional Operation Characteristics
Monitoring and Maintaining the SAA
Configuring a DHCP Operation Example
Configuring a DLSw Operation Example
Configuring a DNS Operation Example
Configuring an HTTP Operation Example
Configuring a Jitter Operation Example
show rtr collection-statistics
Service Assurance Agent
This document is specific to Cisco IOS Release 12.0(5)T.
Note
The Service Assurance Agent (SAA) replaces the Response Time Reporter (RTR) feature. The SAA can be used in conjunction with the existing RTR feature (described in the Cisco IOS Release 12.0(3)T Response Time Reporter Enhancements feature module document). The command line interface for the feature does not reflect the name change; commands retain the RTR name.
Feature Overview
The Service Assurance Agent (SAA) is an both an enhancement to and a new name for the Response Time Reporter (RTR) feature that was introduced in Cisco IOS release 11.2. The feature allows you to monitor network performance by measuring key Service Level Agreement (SLA) metrics such as response time, network resources, availability, jitter, connect time, packet loss and application performance.
With Cisco IOS release 12.0(5)T, the SAA provides new capabilities that enable you to:
•
•
•
Benefits
The SAA feature extends IP support and enhances the management and measurement of enterprise and service provider networks. With the increasing importance of mission-critical applications and networks that link global enterprises, customers are demanding SLAs that guarantee minimum acceptable levels of service. The SAA provides a reliable mechanism to accurately monitor and measure the key metrics in SLAs.
The SAA allows you to measure and monitor the following:
•
•
•
•
Specifically, the SAA feature allows you to define the following operations:
•
•
•
•
•
Related Features and Technologies
Related features and technologies include the Simple Network Management Protocol (SNMP), Remote Monitoring (RMON), and Response Time Monitoring (RTTMON).
Because SA Agent is accessible using SNMP, it can also be used by performance monitoring applications and Network Management Systems such as CiscoWorks2000 (CiscoWorks Blue) and the Internetwork Performance Monitor (IPM). SAA notifications can also be enabled via SNA NMVT for applications such as NetView.
Related Documents
For full documentation of this feature, use the following documents in conjunction with this feature module update:
•
•
•
Supported Platforms
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported MIBs and RFCs
MIBs
The SAA supports the Cisco Round Trip Time Monitor (RTTMON) MIB and the following MIB enhancements:
•
•
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
•
List of Terms and Acronyms
bound—Client has accepted an IP address from the DHCP server.
DHCP—Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them.
DLSw—data-link switching. Interoperability standard, described in RFC 1795 and 2166, that provides a method for forwarding SNA and NetBIOS traffic over TCP/IP networks using data link layer switching and encapsulation.
DNS—domain name server. System used in the Internet for translating names of network nodes into addresses.
data-link switching—See DLSw.
Discover—A broadcast frame looking for DHCP server.
domain name server—See DNS.
Dynamic Host Configuration Protocol—See DHCP.
HTTP—Hypertext Transfer Protocol. The protocol used by Web browsers and Web servers to transfer files, such as text and graphic files.
Hypertext Transfer Protocol—See HTTP.
jitter—Jitter is the inter-packet delay variance; the difference between inter-packet arrival and departure. Jitter is an important QoS metric for voice and video applications.
lease—IP address that lasts a fixed amount of time.
operation—Test that measures network performance. See synthetic operation.
offer—Frame from a DHCP server with a proposed IP address for the client.
QoS—Quality of Service. Measure of performance for a transmission system that reflects its transmission quality and service availability.
Quality of Service—See QoS.
RTR—Response Time Reporter. Cisco IOS feature that monitors network performance, network resources, and applications by measuring response times and availability. This feature was expanded in Cisco IOS 12.0(5)T and was renamed Service Assurance Agent (SAA). The Command-Line Interface (CLI) retains the use of the RTR term
response time reporter—See RTR.
Service Level Agreement—See SLA.
SLA—Agreement between a service provider and a customer that specifies and guarantees minimum acceptable levels of service.
SSP—Switch-to-Switch Protocol. Protocol specified in the DLSw standard that routers use to establish DLSw connections, locate resources, forward data, and handle flow control and error recovery.
Switch-to-Switch Protocol—See SSP.
synthetic operation—Packets sent into the network that appear to be user data traffic but actually measure network performance. Formerly known as a probe. Also referred to as "operation."
Configuration Tasks
Perform the following tasks to configure the SAA feature. Refer to the "Command Reference" section for detailed syntax description of the commands used in these tasks. Configuring the operation and scheduling the operation are required tasks; the remaining task is optional.
•
•
•
•
Configuring the Operation
Response time and availability information is collected by operations that you configure on the router. You must configure the operation type before you can configure any of the other characteristics.
Note
The tasks in this section describe how to:
Configure an HTTP Operation
To define a HTTP operation, use the following commands starting in global configuration mode:
Configure a DNS Operation
To define a DNS operation, use the following commands starting in global configuration mode:
1
Specifies an SAA operation and enters RTR configuration mode.
2
Defines a DNS operation.
Configure a Jitter Operation
To define a jitter operation, use the following commands starting in global configuration mode:
Configure a DLSw Operation
To define a DLSw operation, use the following commands starting in global configuration mode:
1
Specifies an SAA operation and enters RTR configuration mode.
2
Defines a DLSw operation.
Configure a DHCP Operation
To define a DHCP operation, use the following commands starting in global configuration mode:
1
Specifies an SAA operation and enters RTR configuration mode.
2
Defines a DHCP operation.
Configuring Optional Operation Characteristics
To configure optional characteristics, use one or more of the following commands in response time reporter configuration mode:
Scheduling the Operation
After you have configured the operation, you must schedule the operation to begin capturing statistics and collecting error information. You can schedule an operation to start immediately or start at a certain month, day, or hour. Use the pending keyword to set an operation to wait to be triggered. Pending is also an internal state of the operation visible through SNMP.
To schedule an SAA operation, use the following command in global configuration mode:
Schedules the operation by configuring the time parameters.
Note
If the operation is in a pending state (the default), you can define the conditions under which the operation makes the transition from pending to active with the rtr reaction-trigger command. When the operation is in an active state it immediately begins collecting information.
Verifying SAA
To verify that the SAA feature is configured properly, use the following commands:
•
•
•
•
The following example verifies how many operations are running.
router#show rtr applicationResponse Time ReporterVersion:2.1.0 Round Trip Time MIBMax Packet Data Size (ARR and Data):16384Time of Last Change in Whole RTR:*22:37:12.000 UTC Sat Mar 6 1993System Max Number of Entries:500Number of Entries configured:5Number of active Entries:5Number of pending Entries:0Number of inactive Entries:0Supported Operation TypesType of Operation to Perform: echoType of Operation to Perform: pathEchoType of Operation to Perform: udpEchoType of Operation to Perform: tcpConnectType of Operation to Perform: httpType of Operation to Perform: dnsType of Operation to Perform: jitterType of Operation to Perform: dlswType of Operation to Perform: dhcpSupported ProtocolsProtocol Type:ipIcmpEchoProtocol Type:ipUdpEchoApplProtocol Type:ipTcpConnProtocol Type:httpApplProtocol Type:dnsApplProtocol Type:jitterApplProtocol Type:dhcpNumber of configurable probe is 490The following example verifies that the statistics are being collected for an HTTP operation:
router#show rtr collection-statisticsCollected StatisticsEntry Number:1HTTP URL:http://172.20.150.200Start Time:*00:01:16.000 UTC Mon Mar 1 1993Comps:1 RTTMin:343OvrTh:0 RTTMax:343DNSTimeOut:0 RTTSum:343TCPTimeOut:0 RTTSum2:117649TraTimeOut:0 DNSRTT:0DNSError:0 TCPConRTT:13HTTPError:0 TransRTT:330IntError:0 MesgSize:1771Busies:0The following example verifies that the operations are running:
router#show rtr operational-stateCurrent Operational StateEntry Number:3Modification Time:*22:15:43.000 UTC Sat Mar 6 1993Diagnostics Text:Last Time this Entry was Reset:NeverNumber of Octets in use by this Entry:1332Number of Operations Attempted:2Current Seconds Left in Life:3511Operational State of Entry:activeLatest Completion Time (milliseconds):544Latest Operation Start Time:*22:16:43.000 UTC Sat Mar 6 1993Latest Oper Sense:okLatest Sense Description:200 OKTotal RTT:544DNS RTT:12TCP Connection RTT:28HTTP Transaction RTT:504HTTP Message Size:9707The output for the show rtr operational-state command and the show rtr collection-statistics command have been expanded to show detailed information about Jitter operations. The following example shows information about a Jitter operation which has been numbered as 1. For an explanation of the report fields, please see the documentation in the command reference section of this document.
saa-ts1-6#show rtr operational-state 1Current Operational StateEntry Number:1Modification Time:*19:20:55.000 UTC Mon Mar 22 1993Diagnostics Text:Last Time this Entry was Reset:NeverNumber of Octets in use by this Entry:1382Number of Operations Attempted:1Current Seconds Left in Life:3545Operational State of Entry:activeLatest Operation Start Time:*19:20:55.000 UTC Mon Mar 22 1993RTT Values:NumOfRTT:10 RTTSum:32 RTTSum2:128Packet Loss Values:PacketLossSD:0 PacketLossDS:0PacketOutOfSequence:0 PacketMIA:0 PacketLateArrival:0InternalError:0 Busies:0Jitter Values:MinOfPositivesSD:4 MaxOfPositivesSD:4NumOfPositivesSD:2 SumOfPositivesSD:8 Sum2PositivesSD:32MinOfNegativesSD:4 MaxOfNegativesSD:4NumOfNegativesSD:1 SumOfNegativesSD:4 Sum2NegativesSD:16MinOfPositivesDS:0 MaxOfPositivesDS:0NumOfPositivesDS:0 SumOfPositivesDS:0 Sum2PositivesDS:0MinOfNegativesDS:4 MaxOfNegativesDS:4NumOfNegativesDS:1 SumOfNegativesDS:4 Sum2NegativesDS:16The following example verifies that the SAA is configured:
router#show rtr configurationComplete Configuration Table (includes defaults)Entry Number:3Owner:JoeTag:AppleTreeType of Operation to Perform:httpReaction and History Threshold (milliseconds):5000Operation Frequency (seconds):60Operation Timeout (milliseconds):5000Verify Data:FALSEStatus of Entry (SNMP RowStatus):activeProtocol Type:httpApplTarget Address:Source Address:0.0.0.0Target Port:0Source Port:0Request Size (ARR data portion):1Response Size (ARR data portion):1Control Packets:enabledLoose Source Routing:disabledLSR Path:Type of Service Parameters:0x0HTTP Operation:getHTTP Server Version:1.0URL:http://www.cisco.comCache Control:enabledLife (seconds):3600Next Scheduled Start Time:Start Time already passedEntry Ageout:neverConnection 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:1Statistic Distribution Interval (milliseconds):20Number of History Lives kept:0Number of History Buckets kept:15Number of History Samples kept:1History Filter Type:noneMonitoring and Maintaining the SAA
To shut down the SAA (stop all operations and clear the SAA configuration), use the following command in global configuration mode:
CautionUse the rtr reset command only in extreme situations such as the incorrect configuration of a number of operations. The rtr reset command reconfigures the router to its startup configuration.
Stops all operations and clears the SAA configuration information.
In addition to stopping all operations and clearing the SAA configuration information, the rtr reset command returns the SAA feature to the startup condition. All rows in the rttMonStatsCaptureTable and rttMonHistoryCaptureTable will be deleted. This command does not reread the configuration stored in NVRAM. You must retype the SAA configuration.
Configuration Examples
This section provides the following configuration examples for setting up operations on the router to monitor network performance and send notifications:
•
•
•
•
•
Configuring a DHCP Operation Example
In the following example, SAA operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3:
Router(config)# rtr 4Router(config-rtr)# type dhcpRouter(config-rtr)# exitRouter(config)# ip dhcp-server 172.16.20.3Configuring a DLSw Operation Example
In the example shown in , DLSw peers 172.20.26.10 and 172.21.27.11 are configured:
Figure 1 DLSw Operation
Router A
RouterA(config)# dlsw local-peer peer-id 172.20.26.10RouterA(config)# dlsw remote-peer 0 tcp 172.21.27.11RouterA(config)# rtr 1RouterA(config-rtr)# type dlsw peer-ipaddr 172.21.27.11RouterA(config-rtr)# exitRouterA(config)# rtr schedule 1 start-time nowRouter B
RouterB(config)# dlsw local-peer peer-ip 172.21.27.11RouterB(config)# dlsw remote-peer 0 tcp 172.20.26.10For more information on DLSw commands, see the "DLSw+ Commands" chapter of the Cisco IOS 12.0 Bridging and IBM Networking Command Reference.
Configuring a DNS Operation Example
In the example shown in , SAA operation 7 is created and configured as a DNS operation using the name server IP address 172.20.2.132:
Figure 2 DNS Operation
Router B
RouterB(config)# rtr 7RouterB(config-rtr)# type dns target-addr lethe name-server 172.20.2.132Configuring an HTTP Operation Example
In the example shown in , an HTTP operation is polling the HTTP server:
Figure 3 HTTP Operation
Router B
RouterB(config)# rtr 1RouterB(config-rtr)# type http operation get url http://www.cisco.comConfiguring a Jitter Operation Example
In the example shown in , SAA number 5 is created and configured as a Jitter operation using the destination IP address 172.24.132.100 destination UDP port number 99. The operation will send 20 packets at 20 ms intervals. You must enable the RTR responder on Router A for the Jitter operation to run.
Figure 4 Jitter Operation
Router B
RouterB(config)# rtr 5RouterB(config-rtr)# type jitter dest-ip 172.24.132.100 dest-port 99 num-packets 20 interval 20Command Reference
Note
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS release 12.0 command references and in the Cisco IOS 12.0(3)T Response Time Reporter Enhancements feature module.
•
•
•
•
•
•
•
•
•
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
rtr low-memory
To configure how much system memory must be available to configure the SAA, use the rtr low-memory response time reporter configuration command. To remove the type configuration for the operation, use the no form of this command.
rtr low-memory value
no rtr low-memory
Syntax Description
Defaults
The default value is 25 percent of the memory available on the system.
Command Modes
RTR configuration
Command History
Usage Guidelines
The rtr low-memory command allows the user to specify the amount of memory that the SAA can use. If the amount of available free memory falls below the value specified in the rtr low-memory command, then the SAA will not allow new operations to be configured.
The value of the rtr low-memory command should not exceed the amount of free memory available on the system. To determine the amount of free memory available on the system, use the show memory EXEC command.
Examples
In the following example, the SAA is configured so that the router will have no less than 2 MB of free memory for the SAA:
Router(config)# rtr low-memory 2000000Related Commands
rtr
Specifies an operation and enters response time reporter configuration mode.
show memory
Shows statistics about memory, including memory-free pool statistics.
show rtr collection-statistics
To display information collected about SAA operations, use the show rtr collection-statistics EXEC command.
show rtr collection-statistics [number] [tabular | full]
Syntax Description
Default
If an operation number is not specified, all current operations are displayed. If a format keyword is not specified, output is displayed in full format.
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2. The output for this command was expanded in Cisco IOS Release 12.0(5)T to include information for Jitter operations.
This command displays information collected for the amount of time specified by the hours-of-statistics kept command. Use the show rtr collection-statistics command to display information such as the number of failed operations and the failure reason. See the examples below for an explanation of the output fields.
Sample Display
The following shows sample output from the show rtr collection-statistics command, where operation 1 is a Jitter operation:
Router# show rtr collection-statistics 1Collected StatisticsEntry Number:1Target Address:10.0.55.106, Port Number:99Start Time:*19:20:54.000 UTC Mon Mar 22 1993RTT Values:NumOfRTT:30 RTTSum:40 RTTSum2:160Packet Loss Values:PacketLossSD:0 PacketLossDS:0PacketOutOfSequence:0 PacketMIA:0 PacketLateArrival:0InternalError:0 Busies:0Jitter Values:MinOfPositivesSD:4 MaxOfPositivesSD:4NumOfPositivesSD:2 SumOfPositivesSD:8 Sum2PositivesSD:32MinOfNegativesSD:4 MaxOfNegativesSD:4NumOfNegativesSD:3 SumOfNegativesSD:12 Sum2NegativesSD:48MinOfPositivesDS:0 MaxOfPositivesDS:0NumOfPositivesDS:0 SumOfPositivesDS:0 Sum2PositivesDS:0MinOfNegativesDS:4 MaxOfNegativesDS:4NumOfNegativesDS:1 SumOfNegativesDS:4 Sum2NegativesDS:16The values shown indicate the aggregated values for the current hour. RTT stands for Round-Trip-Time. SD stands for Source-to-Destination. DS stands for Destination-to-Source. describes the significant fields shown in this output.
The DS values show the same information as above for Destination-to-Source Jitter values.
Related Commands
show rtr configuration
show rtr distributions-statistics
show rtr operational-state
show rtr totals-statisticsshow rtr operational-state
To display the operational state of the last attempted SAA operation (probe), use the show rtr operational-state EXEC command.
show rtr operational-state [number] [tabular | full]
Syntax Description
Default
If an operation number is not specified, all current operations are displayed. If a format keyword is not specified, output is displayed in full format.
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2. The output for this command was expanded in Cisco IOS Release 12.0(5)T to include information for Jitter operations.
Use the show rtr operational-state command to determine whether a connection loss, timeout, or over-threshold occurred; how much life the specified operation has left; whether the operation is active; and the completion time. This command displays the results of the latest operation attempt.
Sample Display
The following is sample output from the show rtr operational-state command in full format:
Router# show rtr operational-state 1 fullCurrent 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.176The following example shows sample output when the specified operation is a Jitter operation:
Router# show rtr operational-state 1Current Operational StateEntry Number:1Modification Time:*19:20:55.000 UTC Mon Mar 22 1993Diagnostics Text:Last Time this Entry was Reset:NeverNumber of Octets in use by this Entry:1382Number of Operations Attempted:1Current Seconds Left in Life:3545Operational State of Entry:activeLatest Operation Start Time:*19:20:55.000 UTC Mon Mar 22 1993RTT Values:NumOfRTT:10 RTTSum:32 RTTSum2:128Packet Loss Values:PacketLossSD:0 PacketLossDS:0PacketOutOfSequence:0 PacketMIA:0 PacketLateArrival:0InternalError:0 Busies:0Jitter Values:MinOfPositivesSD:4 MaxOfPositivesSD:4NumOfPositivesSD:2 SumOfPositivesSD:8 Sum2PositivesSD:32MinOfNegativesSD:4 MaxOfNegativesSD:4NumOfNegativesSD:1 SumOfNegativesSD:4 Sum2NegativesSD:16MinOfPositivesDS:0 MaxOfPositivesDS:0NumOfPositivesDS:0 SumOfPositivesDS:0 Sum2PositivesDS:0MinOfNegativesDS:4 MaxOfNegativesDS:4NumOfNegativesDS:1 SumOfNegativesDS:4 Sum2NegativesDS:16The values shown indicate the values for the last SAA operation. RTT stands for Round-Trip-Time. SD stands for Source-to-Destination. DS stands for Destination-to-Source. For a description of the output fields, see in the show rtr collection-statistics command documentation.
Related Commands
show rtr collection-statistics
type dhcp
To configure a DHCP SAA operation, use the type dhcp RTR configuration command. To disable a DHCP SAA operation, use the no form of this command.
type dhcp
no type dhcp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
You may configure the ip dhcp-server command to identify the DHCP server that the DHCP operation will measure.
If the ip dhcp-server command is not configured, then DHCP discover packets will be sent on every available IP interface.
Examples
In the following example, SAA operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3:
Router(config)# rtr 4Router(config-rtr)# type dhcpRouter(config-rtr)# exitRouter(config)# ip dhcp-server 172.16.20.3Related Commands
rtr
Specifies an operation and enters response time reporter configuration mode.
ip dhcp-server
Specifies the address of one or more DHCP servers available on the network.
type dlsw
To configure a DLSw SAA operation, use the type dlsw response time reporter configuration command. To remove the type configuration for the operation, use the no form of this command.
type dlsw peer-ipaddr ipaddr
no type dlsw peer-ipaddr ipaddr
Syntax Description
Defaults
The default for the optional characteristic request-data-size for a DLSw SAA operation is 0 bytes.
The default for the optional characteristic timeout for a DLSw SAA operation is 30 seconds.
Command Modes
RTR configuration
Command History
Usage Guidelines
In order to configure a DLSw operation, the DLSw feature must be configured on the local and target routers.
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
In the following example, SAA operation number 4 is configured as a DLSw operation enabled for remote peer ip address 172.21.27.11. The data size is 15 bytes.
Router(config)# rtr 4Router(config-rtr)# type dlsw peer-ipaddr 172.21.27.11Router(config-rtr)# request-data-size 15Related Commands
type dns
To configure a DNS SAA operation, use the type dns RTR configuration command. To remove the type configuration for the operation, use the no form of this command.
type dns target-addr {name | ipaddr} name-server ipaddress
no type dns target-addr target address name-server ipaddress
Syntax Description
Defaults
No default behavior or values.
Command Modes
RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
In the following example, SAA operation 7 is created and configured as a DNS operation using the target IP address 172.20.2.132:
Router(config)# rtr 7Router(config-rtr)# type dns target-addr lethe name-server 172.20.2.132Related Commands
rtr
Specifies an operation and enters response time reporter configuration mode.
type echo
To configure an echo operation, use the type echo RTR configuration command. To remove the type configuration for the operation, use the no form of this command.
type echo protocol protocol-type target-addr [source-ipaddr ipaddr]
no type echo protocol protocol-type target-addr [source-ipaddr ipaddr]
Syntax Description
Defaults
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Prior to sending a operation packet to the responder, the SAA collector sends a control message to the responder to enable the destination port.
The default for the optional characteristic request-data-size for a type echo ipIcmpEcho SAA operation is 28 bytes. This is the payload portion of the Icmp packet which makes a 64 byte IP packet.
Command Modes
RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Support of echo to a protocol and pathEcho to a protocol is dependent on the protocol type and implementation. In general most protocols support echo and few protocols support pathEcho.
Note
Examples
In the following example, operation 10 is created and configured as echo using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
rtr 10type echo protocol ipIcmpEcho 172.16.1.175Related Commands
type http
To configure an HTTP response time reporter operation, use the type http response time reporter configuration command. To remove the type configuration for the operation, use the no form of this command.
type http operation {get | raw} url url [name-server ipaddress] [version version-number] [source-ipaddr {name | ipaddr}] [source-port port number] [cache {enable | disable}] [proxy proxy-url]
no type http operation {get | raw} url url [name-server ipaddress] [version version number] [source-ipaddr {name | ipaddr}] [source-port port number] [cache {enable | disable}] [proxy proxy-url]
Syntax Description
Default
No default behavior or values.
Command Mode
RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
HTTP GET operation
In this example operation 5 is created and configured as an HTTP GET operation. The destination URL is http://www.cisco.com.
(config)# rtr 5(config-rtr)# type http operation get url http://www.cisco.com(config-rtr)# exit(config)# rtr schedule 5 start-time nowHTTP RAW operation using RAW submode
In this example operation 6 is created and configured as an HTTP RAW operation. To use the raw commands, HTTP-RAW submode is entered using the http-raw-request command. The SAA-RTR HTTP-RAWsubmode is indicated by the (config-rtr-http) router prompt.
(config)# rtr 6(config-rtr)# type http operation raw url http://www.cisco.com(config-rtr)# http-raw-request(config-rtr-http)# GET /index.html HTTP/1.0\r\n(config-rtr-http)# \r\n(config-rtr-http)# exit(config)# rtr schedule 6 start-time nowHTTP RAW operation through a Proxy Server
In this example http://www.proxy.cisco.com is the proxy server and http://www.yahoo.com is the HTTP Server.
(config)# rtr 6(config-rtr)# type http operation raw url http://www.proxy.cisco.com(config-rtr)# http-raw-request(config-rtr-http)# GET http://www.yahoo.com HTTP/1.0\r\n(config-rtr-http)# \r\n(config-rtr-http)# exit(config)# rtr schedule 6 start-time nowRelated Commands
type jitter
To configure a jitter SAA operation, use the type jitter response time reporter configuration command. To disable a jitter operation, use the no form of this command.
type jitter dest-ipaddr {name | ipaddr} dest-port port number [source-ipaddr {name | ipaddr}] [source-port port number] [control {enable | disable}] [num-packets number of packets] [interval inter-packet interval]
no type jitter dest-ipaddr {name | ipaddr} dest-port port number [source-ipaddr {name | ipaddr}] [source-port port number] [control {enable | disable}] [num-packets number of packets] [interval inter-packet interval]
Syntax Description
Defaults
Prior to sending a operation packet to the responder, the SAA collector sends a control message to the responder to enable the destination port.
The default for the optional characteristic request-data-size for a jitter SAA operation is 32 bytes of UDP data.
Command Modes
RTR configuration
Command History
Usage Guidelines
You must enable the RTR (SAA) responder on the target router before you can configure a jitter operation.
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
In the following example, operation 6 is created and configured as a UDP jitter operation using the destination IP address 172.30.125.15, the destination port number 2000, 20 packets, and an interval of 20:
Router(config)# rtr 6Router(config-rtr)# type jitter dest-ip 172.30.125.15 dest-port 2000 num-packets 20 interval 20Related Commands
Debug Commands
This section documents modified debug commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 Command References.
debug rtr error
To enable logging of SAA runtime errors, use the debug rtr error EXEC command. To disable debugging output, use the no form of this command.
[no] debug rtr error [probe]
Syntax Description:
Defaults
Logging is off.
Command History
Usage Guidelines
The debug rtr error command displays runtime errors. When a probe number other than 0 is specified, all runtime errors for that probe are displayed when the probe is active. When the probe number is 0 all runtime errors relating to the response time reporter scheduler process are displayed. When no probe number is specified, all runtime errors for all active probes configured on the router and probe control are displayed.
Note
Examples
The following example shows output from the debug rtr error command. The output indicates failure because the target is not there or because the responder is not enabled on the target. All debug output for the response time reporter (including debug rtr trace) has the format shown in .
Router# debug rtr errorMay 5 05:00:35.483: control message failure:1May 5 05:01:35.003: control message failure:1May 5 05:02:34.527: control message failure:1May 5 05:03:34.039: control message failure:1May 5 05:04:33.563: control message failure:1May 5 05:05:33.099: control message failure:1May 5 05:06:32.596: control message failure:1May 5 05:07:32.119: control message failure:1May 5 05:08:31.643: control message failure:1May 5 05:09:31.167: control message failure:1May 5 05:10:30.683: control message failure:1describes the debug rtr error command fields.
Related Commands
debug rtr trace
To trace the execution of an SAA operation, use the debug rtr trace EXEC command. To disable trace debugging output (but not debug rtr error output), use the no form of this command.
[no] debug rtr trace [probe]
Syntax Description:
Defaults
No default behavior or values.
Command History
Usage Guidelines
Note
When a probe number other than 0 is specified, execution for that probe is traced. When the probe number is 0, the response time reporter scheduler process is traced. When no probe number is specified, all active probes and every probe control is traced.
The debug rtr trace command also enables debug rtr error command for the specified probe. However, the no debug rtr trace command does not disable the debug rtr error command. You must manually disable the command by using the no debug rtr error command.
All debug output (including debug rtr error command output) has the format shown in the debug rtr error command output example.
Examples
The following output is from the debug rtr trace command. In this example, a probe is traced through a single operation attempt: the setup of a connection to the target, the attempt at an echo to calculate UDP packet response time.
rtr9#debug rtr tracertr9#RTR 1:Starting An Echo Operation - IP RTR Probe 1May 5 05:25:08.584:rtt hash insert :3.0.0.3 3383May 5 05:25:08.584: source=3.0.0.3(3383) dest-ip=5.0.0.1(9)May 5 05:25:08.588:sending control msg:May 5 05:25:08.588: Ver:1 ID:51 Len:52May 5 05:25:08.592:cmd:command:RTT_CMD_UDP_PORT_ENABLE, ip:5.0.0.1, port:9, duration:5000May 5 05:25:08.607:receiving replyMay 5 05:25:08.607: Ver:1 ID:51 Len:8May 5 05:25:08.623: local delta:8May 5 05:25:08.627: delta from responder:1May 5 05:25:08.627: received <16> bytes and responseTime = 3 (ms)May 5 05:25:08.631:rtt hash remove:3.0.0.3 3383RTR 1:Starting An Echo Operation - IP RTR Probe 1May 5 05:26:08.104:rtt hash insert :3.0.0.3 2974May 5 05:26:08.104: source=3.0.0.3(2974) dest-ip=5.0.0.1(9)May 5 05:26:08.108:sending control msg:May 5 05:26:08.108: Ver:1 ID:52 Len:52May 5 05:26:08.112:cmd:command:RTT_CMD_UDP_PORT_ENABLE, ip:5.0.0.1, port:9, duration:5000May 5 05:26:08.127:receiving replyMay 5 05:26:08.127: Ver:1 ID:52 Len:8May 5 05:26:08.143: local delta:8May 5 05:26:08.147: delta from responder:1May 5 05:26:08.147: received <16> bytes and responseTime = 3 (ms)May 5 05:26:08.151:rtt hash remove:3.0.0.3 2974RTR 1:Starting An Echo Operation - IP RTR Probe 1Related Commands
