Downloads |
Table Of Contents
Service Assurance Agent Enhancements
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring a One-way Delay Report Using a Jitter Operation
Configuring the SA Agent Responder
Configuring Optional Operation Characteristics
Verifying Data for the udpEcho Operation
Specifying the data pattern in udpEcho packets
Monitoring and Maintaining the SA Agent
Configuring a DHCP Operation Specifying Option 82
Configuring the SA Agent Responder
show rtr collection-statistics
Service Assurance Agent Enhancements
Note
The Service Assurance (SA) Agent is a new name for the Response Time Reporter (RTR) feature. The command line interface for the feature does not reflect the name change; commands retain the RTR name. Unless otherwise noted, RTR commands retain the functionality of earlier Cisco IOS releases.
This feature module describes the SA Agent Enhancements feature. It includes information on the benefits of the new feature, supported platforms and related documents.
This document contains the following sections:
•
•
Feature Overview
The SA Agent 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 between a Cisco router and a remote device (which can be another Cisco router, an IP host, or a mainframe host) by measuring key Service Level Agreement (SLA) metrics such as response time, network resources, availability, jitter, connect time, packet loss, and application performance. This feature enables you to perform troubleshooting, problem analysis, and notification based on the statistics collected by the SA Agent.
The SA Agent Enhancements feature introduces new performance measurement operations and enhancements to assist in the measurement of SLAs. With Cisco IOS release 12.1(1)T, the SA Agent provides new capabilities that enable you to:
•
•
•
•
•
•
•
Benefits
The SA Agent Enhancements feature enhances the management and measurement of enterprise and service provider networks. SLAs are useful for managed network services such as managed WAN access and managed virtual private network (VPN) services. The SA Agent Enhancement feature provides tools for measuring network performance using FTP, which is one of the most popular traffic types in Internet service provider (ISP) networks, and jitter (one-way delay), which is important for applications such as Voice over IP (VoIP).
Related Features and Technologies
The SA Agent feature module is related to the existing RTR feature, which is documented in the Cisco IOS Configuration Fundamentals Configuration Guide.
Related Documents
•
•
Supported Platforms
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
No standards are supported by this feature.
MIBs
The SA Agent 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 the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No RFCs are supported by this feature.
Configuration Tasks
See the following sections for configuration tasks for the SA Agent Enhancements feature. Refer to the Command Reference section for detailed syntax descriptions of the commands used in these tasks. Each task in the list indicates if the task is optional or required.
•
•
•
•
Configuring the Operation
Response time and availability information is collected by operations (formerly known as probes) that you configure on a Cisco device such as a router or access server. Operations use synthetic packets specifically placed in a network to collect data about the network. These packets simulate other forms of network traffic, as determined by the type of operation you configure. SA Agent operations are given specific identification numbers so you can track the various operations you configure and execute. SA Agent operations are configured in RTR configuration mode. You must configure the operation type before you can configure any of the other characteristics.
See the following sections for tasks for configuring the operation for the SA Agent Enhancements feature:
•
•
Configuring an FTP Operation
To define an FTP operation, use the following commands starting in global configuration mode:
Configuring a DHCP Operation
To define a DHCP operation, use the following commands starting in global configuration mode:
Configuring a One-way Delay Report Using a Jitter Operation
Note
Note
To define a jitter operation with one-way delay reporting, use the following commands starting in global configuration mode:
Configuring the SA Agent Responder
To enable SA Agent Responder functionality, use the following command starting in global configuration mode:
Router(config-rtr)# rtr responder [type protocol [ipaddr ipaddr] {port port}]
Enables SA Agent Responder functionality on a device.
Configuring Optional Operation Characteristics
See the following sections for tasks for configuring the optional operation characteristics for the SA Agent Enhancements feature:
•
•
Verifying Data for the udpEcho Operation
To verify data for a udpEcho operation, use the following command in global configuration mode:
Router(config)# rtr operation_id
Specifies an operation and enters SA Agent configuration mode.
Router(config-rtr)# verify-data
Enables data verification for udpEcho.
Specifying the data pattern in udpEcho packets
To specify the data pattern for a udpEcho operation, use the following command in global configuration mode:
Scheduling the Operation
Operations can be configured and not executed. In order to execute an operation, you must schedule it.
To schedule and restart an operation, use the following commands starting in global configuration mode:
Verifying SA Agent
To verify that the SA Agent 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 following example verifies that the SA Agent 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 SA Agent
To monitor the jitter one-way delay measurements, use the following commands:
•
•
The following example verifies that a one-way delay report jitter operation is running:
rtr7# show rtr operational-stateCurrent Operational StateEntry Number: 1Modification Time: 11:12:02.000 UTC Thu Jul 1 1999Diagnostics Text:Last Time this Entry was Reset: NeverNumber of Octets in use by this Entry: 1370Number of Operations Attempted: 52Current Seconds Left in Life: 9996936Operational State of Entry: activeLatest Operation Start Time: 12:03:03.000 UTC Thu Jul 1 1999RTT Values:NumOfRTT: 10 RTTSum: 75 RTTSum2: 571Packet Loss Values:PacketLossSD: 0 PacketLossDS: 0PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0InternalError: 0 Busies:0Jitter Values:MinOfPositivesSD: 2 MaxOfPositivesSD: 2NumOfPositivesSD: 1 SumOfPositivesSD: 2 Sum2PositivesSD: 4MinOfNegativesSD: 0 MaxOfNegativesSD: 0NumOfNegativesSD: 0 SumOfNegativesSD: 0 Sum2NegativesSD: 0MinOfPositivesDS: 1 MaxOfPositivesDS: 1NumOfPositivesDS: 2 SumOfPositivesDS: 2 Sum2PositivesDS: 2MinOfNegativesDS: 1 MaxOfNegativesDS: 1NumOfNegativesDS: 1 SumOfNegativesDS: 1 Sum2NegativesDS: 1One Way Values:NumOfOW: 10OWMinSD: 3 OWMaxSD: 5 OWSumSD: 48 OWSum2SD: 234OWMinDS: 2 OWMaxDS: 3 OWSumDS: 27 OWSum2DS: 75The following example verifies that the statistics are being collected for a one-way delay report using a jitter operation:
rtr7# show rtr collection-statisticsCollected StatisticsEntry Number: 1Target Address: 5.0.0.1, Port Number:99Start Time: 11:12:03.000 UTC Thu Jul 1 1999RTT Values:NumOfRTT: 600 RTTSum: 3789 RTTSum2: 138665Packet Loss Values:PacketLossSD: 0 PacketLossDS: 0PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0InternalError: 0 Busies: 0Jitter Values:MinOfPositivesSD: 1 MaxOfPositivesSD: 2NumOfPositivesSD: 26 SumOfPositivesSD: 31 Sum2PositivesSD: 41MinOfNegativesSD: 1 MaxOfNegativesSD: 4NumOfNegativesSD: 56 SumOfNegativesSD: 73 Sum2NegativesSD: 133MinOfPositivesDS: 1 MaxOfPositivesDS: 338NumOfPositivesDS: 58 SumOfPositivesDS: 409 Sum2PositivesDS: 114347MinOfNegativesDS: 1 MaxOfNegativesDS: 338NumOfNegativesDS: 48 SumOfNegativesDS: 396 Sum2NegativesDS: 114332One Way Values:NumOfOW: 440OWMinSD: 2 OWMaxSD: 6 OWSumSD: 1273 OWSum2SD: 4021OWMinDS: 2 OWMaxDS: 341 OWSumDS: 1643 OWSum2DS: 120295Configuration Examples
This section provides the following configuration examples:
•
•
Configuring an FTP Operation
An FTP operation is configured as shown in Figure 1.
Figure 1 FTP Operation
In the following example, SA Agent operation 20 is configured as an FTP operation. ira is the user, smith is the password, zxq is the host name or address, and test is the file name.
(config)# rtr 20(config-rtr)# ftp://ira:smith@zxq/testConfiguring a DHCP Operation Specifying Option 82
In the following example, SA Agent operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3:
(config)# rtr 4(config-rtr)# type dhcp option 82 circuit-id 10005A6F1234(config)# ip dhcp-server 172.16.20.3Configuring the SA Agent Responder
The following example enables the SA Responder:
rtr responderCommand Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 Configuration Fundamentals Command Reference.
•
data-pattern
To specify the data pattern in a udpEcho packet, use the data pattern RTR configuration mode command. To remove the data pattern specification, use the no form of this command.
data-pattern hex-pattern
no data-pattern hex-pattern
Syntax Description
Defaults
The default is ABCD.
Command Modes
RTR configuration
Command History
Usage Guidelines
The data-pattern command is applicable to the udpEcho operation, only.
Examples
The following example specifies 1234ABCD5678 as the data pattern:
rtr 1type udpEcho dest-ipaddr 10.0.54.205 dest-port 101data-pattern 1234ABCD5678Related Commands
rtr reaction-configuration
To configure certain actions to occur based on events under the control of the SA Agent, use the rtr reaction-configuration global configuration command. Use the no form of this command to return to the default values of the operation.
rtr reaction-configuration operation [verify-error-enable] [connection-loss-enable] [timeout-enable] [threshold-falling milliseconds] [threshold-type option] [action-type option]
no rtr reaction-configuration operation
Syntax Description
Defaults
No reactions are generated.
Error verification is disabled.
Connection loss is disabled.
Checking the timeout is disabled.
The falling threshold value is 3000 ms.
The algorithm threshold is never.
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.1(1)T
The verify-error-enable optional keyword was added.
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, operation 19 sends an SNMP trap when there is an over or falling threshold violation:
rtr reaction-configuration 19 threshold-type immediate action-type trapOnlyFigure 2 shows that an alert (rising trap) would be issued immediately when the response time exceeds the rising threshold and a resolution (falling trap) would be issued immediately when the response time drops below the falling threshold.
Figure 2 Example of Rising and Falling Thresholds
Related Commands
rtr responder
To enable the SA Agent Responder feature on a target router, use the rtr responder global configuration command. Use the no form of this command to disable the SA Responder.
rtr responder [type protocol [ipaddr ipaddr] {port port}]
no rtr responder [type protocol [ipaddr ipaddr] {port port}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.0(3)T
This command was introduced.
12.1(1)T
The type, ipaddr, and port keywords were added.
Usage Guidelines
This command is used on the intended target router of SA Agent operations to enable certain types of operations on non-native interfaces.
The type, ipaddr, and port keywords enable the SA Agent Responder to respond to probe packets without receiving control packets. The applicable protocols are jitter, udpEcho, and tcpConnect. The jitter operation will not compute packet loss because the SA Agent Responder does not know which probe packet has been received first.
Examples
The following example enables the SA Responder:
rtr responderRelated Commands
rtr restart
To restart a SA Agent operation, use the rtr restart global configuration command.
rtr restart operation-id
Syntax Description
operation-id
Number (id) of the SA Agent operation to restart. SA Agent allows a maximum of 500 operations.
Defaults
No default behavior or values.
Command Modes
Global configuration.
Command History
Usage Guidelines
To restart an operation, the operation should be in active status.
SA Agent allows a maximum of 500 operations.
This command does not have a no form.
Examples
The following example restarts operation 12:
router(config)#rtr restart 12rtr schedule
To configure the time parameters for an SA Agent operation, use the rtr schedule global configuration command. Use the no form of this command to stop the operation and restart it with the default parameters (that is, pending).
rtr schedule operation-id [life {forever | seconds}] [start-time {pending | now | after hh:mm:ss | hh:mm [month day | day month] | hh:mm:ss [month day | day month]] [ageout seconds]
no rtr schedule operation-id
Syntax Description
Defaults
Place the operation in a pending state (that is, the operation is started but not actively collecting information).
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.1(1)T
The after and forever keywords were added.
Usage Guidelines
After you schedule the operation with the rtr schedule command, you cannot change the configuration of the operation (with the rtr global configuration command). To change the configuration of the operation, use the no form of the rtr global command and reenter the configuration information.
If the operation is in a pending state, you can define the conditions under which the operation makes the transition from pending to active with the rtr reaction-trigger and rtr reaction-configuration global configuration commands. When the operation is in an active state, it immediately begins collecting information.
The following time line shows the age-out process of the operation:
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 operation to age out before it executes (that is, Z can occur before X). To ensure that this does not happen, the difference between the operation's configuration time and start time (X and W) must be less than the age-out seconds.
Note
Examples
In the following example, operation 25 begins actively collecting data at 3:00 p.m. on April 5. This operation will age out after 12 hours of inactivity, which can be before it starts or after it has finished with its life. When this operation ages out, all configuration information for the operation 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 43200In the following example, operation 1 begins collecting data after a 5 minute delay:
rtr schedule 1 start after 00:05:00In the following example, operation 3 begins collecting data immediately and is scheduled to run indefinitely:
rtr schedule 3 start-time now life foreverRelated Commands
show rtr collection-statistics
To display statistical errors for all SA Agent operations or the specified operation, use the show rtr collection-statistics EXEC command.
show rtr collection-statistics [operation] [tabular | full]
Syntax Description
Defaults
Full format for all operations. Shows statistics for the past two hours.
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.
This command shows information collected over the past two hours, unless you specify a different amount of time using the hours-of-statistics-kept command.
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.176The following example verifies that the statistics are being collected for an HTTP operation:
router# show rtr collection-statistics 2Collected StatisticsEntry Number:2HTTP 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 shows sample output from the show rtr collection-statistics command, where operation 1 is a Jitter operation:
Note
Note
router# show rtr collection-statistics 1Collected StatisticsEntry Number: 1Target Address: 5.0.0.1, Port Number:99Start Time: 11:12:03.000 UTC Thu Jul 1 1999RTT Values:NumOfRTT: 600 RTTSum: 3789 RTTSum2: 138665Packet Loss Values:PacketLossSD: 0 PacketLossDS: 0PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0InternalError: 0 Busies: 0Jitter Values:MinOfPositivesSD: 1 MaxOfPositivesSD: 2NumOfPositivesSD: 26 SumOfPositivesSD: 31 Sum2PositivesSD: 41MinOfNegativesSD: 1 MaxOfNegativesSD: 4NumOfNegativesSD: 56 SumOfNegativesSD: 73 Sum2NegativesSD: 133MinOfPositivesDS: 1 MaxOfPositivesDS: 338NumOfPositivesDS: 58 SumOfPositivesDS: 409 Sum2PositivesDS: 114347MinOfNegativesDS: 1 MaxOfNegativesDS: 338NumOfNegativesDS: 48 SumOfNegativesDS: 396 Sum2NegativesDS: 114332One Way Values:NumOfOW: 440OWMinSD: 2 OWMaxSD: 6 OWSumSD: 1273 OWSum2SD: 4021OWMinDS: 2 OWMaxDS: 341 OWSumDS: 1643 OWSum2DS: 120295The values shown indicate the aggregated values for the current hour. RTT stands for Round-Trip-Time. SD stands for source-to-destination and represents the time from the source to the destination. DS stands for destination-to-source and represents the time from the destination to the source. Table 1 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 operational-state
To display the operational state of all SA Agent operations or the specified operation, use the show rtr operational-state EXEC command.
show rtr operational-state [operation] [tabular | full]
Syntax Description
Defaults
Full format for all operations
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 operation has left; whether the operation is active; and the completion time. It also displays the results of the latest operation attempt.
Examples
The following example shows sample output from the show rtr operational-state command in full format:
router# show rtr operational-state fullCurrent 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 following example shows sample output when the specified operation is a Jitter operation.
Note
Note
router# show rtr operational-state 1Current Operational StateEntry Number:1Modification Time: 11:12:02.000 UTC Thu Jul 1 1999Diagnostics Text:Last Time this Entry was Reset: NeverNumber of Octets in use by this Entry: 1370Number of Operations Attempted: 52Current Seconds Left in Life: 9996936Operational State of Entry: activeLatest Operation Start Time: 12:03:03.000 UTC Thu Jul 1 1999RTT Values:NumOfRTT: 10 RTTSum: 75 RTTSum2: 571Packet Loss Values:PacketLossSD: 0 PacketLossDS: 0PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0InternalError: 0 Busies:0Jitter Values:MinOfPositivesSD: 2 MaxOfPositivesSD: 2NumOfPositivesSD: 1 SumOfPositivesSD: 2 Sum2PositivesSD: 4MinOfNegativesSD: 0 MaxOfNegativesSD: 0NumOfNegativesSD: 0 SumOfNegativesSD: 0 Sum2NegativesSD: 0MinOfPositivesDS: 1 MaxOfPositivesDS: 1NumOfPositivesDS: 2 SumOfPositivesDS: 2 Sum2PositivesDS: 2MinOfNegativesDS: 1 MaxOfNegativesDS: 1NumOfNegativesDS: 1 SumOfNegativesDS: 1 Sum2NegativesDS: 1One Way Values:NumOfOW: 10OWMinSD: 3 OWMaxSD: 5 OWSumSD: 48 OWSum2SD: 234OWMinDS: 2 OWMaxDS: 3 OWSumDS: 27 OWSum2DS: 75The values shown indicate the values for the last SA Agent 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 Table 1 in the show rtr collection-statistics command documentation.
Related Commands
type dhcp
To configure a Dynamic Host Configuration Protocol SA Agent operation, use the type dhcp RTR configuration command. To disable a DHCP SA Agent operation, use the no form of this command.
type dhcp [source-ipaddr source-ipaddr] [dest-ipaddr dest-ipaddr] [option decimal-option [circuit-id] [remote-id] [subnet-mask]]
no type dhcp
Syntax Description
Defaults
The subnet-mask value is 255.255.255.0.
Command Modes
RTR configuration
Command History
12.0(5)T
This command was introduced.
12.1(1)T
The following keywords were added:
•
•
•
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
If the source IP address is configured, then packets will be sent with that source address.
You may configure the ip dhcp-server command to identify the DHCP server that the DHCP operation will measure.
If the target IP address is configured, then only that device will be measured.
If the ip dhcp-server command is not configured and the target IP address is not configured, then DHCP discover packets will be sent on every available IP interface.
If an odd number of characters are specified for the circuit-id, a zero will be added to the end of the string.
Examples
In the following example, SA Agent operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3:
(config)# rtr 4(config-rtr)# type dhcp option 82 circuit-id 10005A6F1234(config)# ip dhcp-server 172.16.20.3Related Commands
type ftp operation
To configure an FTP operation, use the type ftp operation RTR configuration command. To remove the type configuration for the operation, use the no form of this command.
type ftp operation operation-type url url [source-ipaddr source-ipaddr] [mode {passive | active}]
no command type ftp operation
Syntax Description
Defaults
The default is passive mode.
Command Modes
RTR configuration
Command History
Usage Guidelines
Get is the only valid operation value. The URL must be in one of the following formats:
•
•
If the user and password keywords are not specified, the defaults are anonymous and test, respectively.
Examples
In the following example, an FTP operation is configured. Joe is the user and Young is the password. zxq is the host and test is the file name.
type ftp operation get ftp://joe:young@zxq/testRelated Commands
Displays statistical errors for all SA Agent operations or the specified operation.
Displays the operational state of all SA Agent operations or the specified operation.
Glossary
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.
DNS—domain name server. System used in the Internet for translating names of network nodes into addresses.
Discover—A broadcast frame looking for DHCP server.
domain name server—See DNS.
Dynamic Host Configuration Protocol—See DHCP.
FTP—file transfer protocol. Application protocol, part of the TCP/IP protocol stack, used for transferring files between network nodes. FTP is defined in RFC 959.
File Transfer Protocol—See FTP
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.
ISP—Internet service provider. Company that provides Internet access to other companies and individuals.
Internet service provider—See ISP.
jitter—Jitter is the inter-packet delay variance; that is 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.
NTP—Network Time Protocol. Protocol built on top of TCP that assures accurate local time-keeping with reference to radio and atomic clocks located on the Internet. This protocol is capable of synchronizing distributed clocks within milliseconds over long time periods.
Network Time Protocol—See NTP.
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. Also known as Service Assurance (SA) Agent.
response time reporter—See RTR.
Service Level Agreement—See SLA.
SLA—Agreement that specifies and guarantees minimum acceptable levels of service.
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."
VoIP—Voice over IP. Enables a router to carry voice traffic (for example, telephone calls and faxes) over an IP network. In Voice over IP, the DSP segments the voice signal into frames, which are then coupled in groups of two and stored in voice packets. These voice packets are transported using IP in compliance with ITU-T specification H.323.
VPN—Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses "tunneling" to encrypt all information at the IP level.
Virtual Private Network—See VPN.
Voice over IP—See VoIP.
