-
Cisco IOS Configuration Fundamentals Command Reference, Release 12.2T
-
About the Cisco IOS Release 12.2 T Documentation Set
-
Basic Command-Line Interface Commands
-
The Setup Command
-
Terminal Operating Characteristics Commands
-
Connection, Menu, and System Banner Commands
-
Cisco IOS Web Browser User Interface Commands
-
Cisco IOS File System Commands
-
Configuration File Management Commands
-
System Image and Microcode Commands
-
Router Memory Commands
-
Booting Commands
-
Basic File Transfer Services Commands
-
Basic System Management Commands
-
Troubleshooting and Fault Management Commands
-
SNMP Commands
-
CDP Commands
-
RMON Commands
-
Cisco Service Assurance Agent Commands
-
WCCP Commands
-
CNS Commands
-
Distributed Director Commands
-
XSM Commands for VPN Device Manager (VDM)
-
Appendix: ASCII Character Set and Hex Values
-
Index: Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 T
-
Table Of Contents
Cisco Service Assurance Agent Commands
distributions-of-statistics-kept
rtr responder type frame-relay
show rtr collection-statistics
show rtr distributions-statistics
statistics-distribution-interval
Cisco Service Assurance Agent Commands
This chapter describes the commands used to monitor network performance using Cisco Service Assurance Agent (SAA) in Cisco IOS Release 12.2(11)T.
For SAA configuration tasks and examples, see the "Network Monitoring Using Cisco Service Assurance Agent" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 and the following 12.2 T feature guides:
•
SAA Application Performance Monitor (APM), Cisco IOS Release 12.2(2)T
•
•
atm-slm statistics
To enable the ATM Service Level Monitoring (SLM) feature for the Service Assurance Agent (SAA), use the atm-slm statistics command in global configuration mode. To disable ATM SLM, use the no form of this command.
atm-slm statistics
no atm-slm statistics
Syntax Description
This command has no arguments or keywords.
Defaults
ATM Service Level Monitoring is disabled.
Command Modes
Global configuration mode
Command History
Usage Guidelines
To generate and retrieve performance statistics for ATM services using SAA, the ATM SLM feature must first be enabled on the device using the atm-slm statistics global configuration command. (Note that these performance statistics can be retrieved by other applications such as CNS or Visual Uptime.) If this command is not used, SAA SLM operations (type atm-slm, type slm, or type t1-slm) can not be configured on the system.
Disabling the ATM SLM feature with the no atm-slm statistics command will cause any currently configured SAA SLM operations to be removed from the configuration. When ATM SLM is disabled, no CNS/XML requests are processed.
Examples
In the following example, the ATM SLM feature is enabled before an SAA SLM operation is configured for ATM interface 0/1:
Router(config)# atm-slm statisticsRouter(config)# rtr 1Router(config-rtr)# type atm-slm interface ATM0/1Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 1 start-time now life foreverbuckets-of-history-kept
To set the number of history buckets that are kept during the operation lifetime of the SAA, use the buckets-of-history-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
buckets-of-history-kept size
no buckets-of-history-kept
Syntax Description
size
Number of history buckets kept during the lifetime of the operation. The default is 50 buckets.
Defaults
50 buckets
Command Modes
SAA RTR configuration
SAA FrameRelay configuration
Command History
11.2
This command was introduced.
12.2(2)T
This command was integrated as an SAA FrameRelay configuration submode command.
Usage Guidelines
History collection and statistics capturing is enabled for the following SAA operations: ICMP Echo, SNA Echo, ICMP PathEcho, UDP Echo, TcpConnect, DNS, and DLSW. History collection is not supported for HTTP and Jitter (UDP+) operations.
By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept SAA RTR configuration command to collect history. You can optionally adjust the buckets-of-history-kept, filter-for-history, and samples-of-history-kept SAA RTR configuration commands.
When the number of buckets reaches the size specified, no further history for this life is stored.
Note
If history is collected, each bucket contains one or more history entries from the operation. When the operation type is pathEcho, an entry is created for each hop along the path that the operation takes to reach its destination. The type of entry stored in the history table is controlled by the filter-for-history SAA RTR configuration command. The total number of entries stored in the history table is controlled by the combination of samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept SAA RTR configuration commands.
Each time the SAA starts an operation, a new bucket is created until the number of history buckets matches the specified size or the operation's lifetime expires. History buckets do not wrap. The operation's lifetime is defined by the rtr schedule global configuration command. The operation starts an SAA operation based on the seconds specified by the frequency SAA RTR configuration command.
Examples
The following example configures operation 1 to keep 25 history buckets during the lifetime of the operation lifetime:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.161.21Router(config-rtr)# buckets-of-history-kept 25Router(config-rtr)# lives-of-history-kept 1Related Commands
clear saa apm cache
To delete files from the SAA Application Performance Monitor (APM) cache, use the clear saa apm cache command in global configuration mode.
clear saa apm cache {local | remote | file filename} [force]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
This command will not delete files tagged as "sticky" in the APM cache unless the force keyword is used. The sticky bit is set for a file when the file is copied to the router using the saa apm copy command. To check if files have the sticky bit set, use the show saa apm cache command; those files that show a value of 1 in the "SBit" column have the sticky bit enabled, while those with a sticky value of 0 do not have the sticky bit enabled.
Examples
In the following example, all files that are not tagged as "sticky" (as seen in the SBit column of the show saa apm cache output) are deleted from the APM cache:
Router# show saa apm cacheCache Size (bytes):100000Cache used (bytes):2056TimeCreated TimeAccessed Size Ref Loc Type SBit FileName09/21 13:31:25 09/21 13:31:48 1170 0 1 SCR 0 user/scripts/ldap-rem.scr09/21 13:31:20 09/21 13:31:27 1513 0 1 SCR 1 user/scripts/ldap.scr09/20 14:29:13 09/20 14:29:36 735 0 1 SCR 0 user/scripts/udp-rem.scrRouter# configure terminalRouter(config)# clear saa apm cache localRouter(config)# endRouter# show saa apm cacheCache Size (bytes):100000Cache used (bytes):1513TimeCreated TimeAccessed Size Ref Loc Type SBit FileName09/21 13:31:20 09/21 13:31:27 1513 0 1 SCR 1 user/scripts/ldap.scrRelated Commands
show saa apm cache
Displays the amount of memory available in the SAA APM cache and information about the files stored in the cache.
data-pattern
To specify the data pattern in an SAA udpEcho operation to test for data corruption, use the data pattern command in SAA RTR configuration mode. 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 hex-pattern is ABCD.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The data-pattern command allows users to specify a alphanumeric character string to verify that operation payload does not get corrupted in either direction (source-to-destination (SD) or destination-to-source (DS)).
For Cisco IOS Release 12.2(11)T, the data-pattern command is applicable to the udpEcho operation only. This command also applies to the Frame Relay operation in 12.2(1)T and later T releases.
Examples
The following example specifies 1234ABCD5678 as the data pattern:
Router(config)# rtr 1Router(config-rtr)# type udpEcho dest-ipaddr 10.0.54.205 dest-port 101Router(config-rtr)# data-pattern 1234ABCD5678Related Commands
distributions-of-statistics-kept
To set the number of statistic distributions kept per hop during the lifetime operation of the SAA, use the distributions-of-statistics-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
distributions-of-statistics-kept size
no distributions-of-statistics-kept
Syntax Description
Defaults
1 distribution
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
In most situations, you do not need to change the statistic distribution size for the SAA. Only change the size when distributions are needed (for example, when performing statistical modeling of your network).
Note
When the number of distributions reaches the size specified, no further distribution information is stored.
Examples
The following example sets the distribution to 5 and the distribution interval to 10 ms. This setting means that the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity.
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.161.21Router(config-rtr)# distributions-of-statistics-kept 5Router(config-rtr)# statistics-distribution-interval 10Related Commands
filter-for-history
To define the type of information kept in the history table for an SAA operation, use the filter-for-history command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
filter-for-history {none | all | overThreshold | failures}
no filter-for-history {none | all | overThreshold | failures}
Syntax Description
Defaults
No SAA history is kept for an operation.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Use the filter-for-history command to control what gets stored in the history table for the SAA. To control how much history gets saved in the history table, use the lives-of-history-kept, buckets-of-history-kept, and the samples-of-history-kept SAA RTR configuration commands.
An operation can collect history and capture statistics. By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept command to collect history.
Note
Examples
In the following example, only operation packets that fail are kept in the history table:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.161.21Router(config-rtr)# lives-of-history-kept 1Router(config-rtr)# filter-for-history failuresRelated Commands
frequency
To set the rate at which a specified SAA operation is sent into the network, use the frequency command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
frequency seconds
no frequency
Syntax Description
Defaults
60 seconds
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
If an individual SAA operational probe takes longer to execute than the specified frequency value, a statistics counter called "busy" is incremented rather than sending a second probe.
Note
The value specified for the frequency command cannot be less than the value specified for the timeout SAA RTR configuration command.
Examples
The following example configures SAA IP/ICMP Echo operation 1 to send a probe every 90 seconds:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# frequency 90Related Commands
Specifies an SAA operation and enters SAA RTR configuration mode.
Sets the amount of time the SAA operation waits for a response from its request packet.
hops-of-statistics-kept
To set the number of hops for which statistics are maintained per path for the SAA operation, use the hops-of-statistics-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
hops-of-statistics-kept size
no hops-of-statistics-kept
Syntax Description
size
Number of hops for which statistics are maintained per path. The default is 16 hops for type pathEcho and 1 hop for type echo.
Defaults
16 hops for type pathEcho
1 hop for type echo
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
One hop is the passage of a timed packet from this router to another network device. The other network device is assumed to be a device along the path to the destination (including the destination) when the operation type is pathEcho, or just the destination when the type is echo.
When the number of hops reaches the size specified, no further hop information is stored.
Examples
The following example monitors the statistics of operation 2 for only 10 hops:
Router(config)# rtr 2Router(config-rtr)# type pathecho protocol ipIcmpEcho 172.16.1.177Router(config-rtr)# hops-of-statistics-kept 10Related Commands
http-raw-request
To explicitly specify the options for a GET request for an SAA HTTP operation, use the http-raw-request command in SAA RTR configuration mode.
http-raw-request
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Using the http-raw-request command puts you in HTTP Raw Request configuration mode, indicated by the (config-rtr-http) router prompt.
The http-raw-request command should follow the type http operation raw command. Use the raw-request option when you wish to explicitly specify the content of an HTTP request. Use HTTP 1.0 commands in HTTP Raw Request configuration mode.
The SAA will specify the content of an HTTP request for you if you use the type http operation get command. SA Agent will send the HTTP request, receive the reply, and report RTT statistics (including the size of the page returned).
Examples
In the following example, SAA operation 6 is created and configured as an HTTP operation. The HTTP GET command is explicitly specified:
Router(config)# rtr 6Router(config-rtr)# type http operation raw url http://www.cisco.comRouter(config-rtr)# http-raw-requestRouter(config-rtr-http)# GET /index.html HTTP/1.0\r\nRouter(config-rtr-http)# \r\nRouter(config-rtr-http)# exitRouter(config)# rtr schedule 6 start-time nowRelated Commands
hours-of-statistics-kept
To set the number of hours for which statistics are maintained for the SAA operation, use the hours-of-statistics-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
hours-of-statistics-kept hours
no hours-of-statistics-kept
Syntax Description
Defaults
2 hours
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest information is replaced by newer information).
This command sets the amount of time statistics are kept for use by the show rtr collection-statistics command and show rtr distribution command.
Examples
The following example maintains 3 hours of statistics for SAA operation 2:
Router(config)# rtr 2Router(config-rtr)# type pathecho protocol ipIcmpEcho 172.16.1.177Router(config-rtr)# hours-of-statistics-kept 3Related Commands
lives-of-history-kept
To set the number of lives maintained in the history table for the SAA operation, use the lives-of-history-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
lives-of-history-kept lives
no lives-of-history-kept
Syntax Description
lives
Number of lives maintained in the history table for the operation. If you specify 0 lives, history is not collected for the operation.
Defaults
0 lives
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The number of lives you can specify is dependent on the type of operation you are configuring. Use the lives-of-history-kept ? command to determine the available options.
The default value of 0 lives means that history is not collected for the operation.
To disable history collection, use no lives-of-history-kept command rather than the filter-for-history none SAA RTR configuration command. The no lives-of-history-kept command disables history collection before an operation is attempted, while the filter-for-history command causes the SAA to check for history inclusion after the operation attempt is made.
When the number of lives exceeds the specified value, the history table wraps (that is, the oldest information is replaced by newer information).
When an operation makes a transition from pending to active, a life starts. When the life of an operation ends, the operation makes a transition from active to pending.
Examples
The following example maintains the history for 5 lives of operation 1:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# lives-of-history-kept 5Related Commands
lsr-path
To define a loose source routing (LSR) path for a Cisco SAA IP echo operation, use the lsr-path command in SAA RTR configuration mode. To remove the definition, use the no form of this command.
lsr-path {hostname | ip-address} [{hostname | ip-address} ...]
no lsr-path
Syntax Description
Defaults
LSR path is disabled.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The maximum number of hops available is eight when an LSR path is configured.
Examples
In the following example, the LSR path is defined for SAA echo operation 1. The target destination for the operation is at 172.16.1.176. The first hop on the LSR path is 172.18.4.149. The second hop on the LSR path is 172.18.16.155.
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# lsr-path 172.18.4.149 172.18.26.155Related Commands
Specifies an identification for an SAA operation and enters SAA RTR configuration mode.
owner
To configure the Simple Network Management Protocol (SNMP) owner of an SAA operation, use the owner command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
owner text
no owner
Syntax Description
Defaults
No owner is specified.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The owner name contains one or more of the following: ASCII form of the network management station's transport address, network management station name (that is, the domain name), and network management personnel's name, location, or phone number. In some cases, the agent itself will be the owner of the operation. In these cases, the name can begin with "agent."
Examples
The following example sets the owner of operation 1 to 172.16.1.189 cwb.cisco.com John Doe RTP 555-1212:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# owner 172.16.1.189 cwb.cisco.com John Doe RTP 555-1212Related Commands
paths-of-statistics-kept
To set the number of paths for which statistics are maintained per hour for the SAA operation, use the paths-of-statistics-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
paths-of-statistics-kept size
no paths-of-statistics-kept
Syntax Description
size
Number of paths for which statistics are maintained per hour. The default is 5 paths for type pathEcho and 1 path for type echo.
Defaults
5 paths for type pathEcho
1 path for type echo
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
A path is the route the request packet of the operation takes through the network to get to its destination. The operation may take a different path to reach its destination for each SAA operation.
When the number of paths reaches the size specified, no further path information is stored.
Examples
The following example maintains statistics for only 3 paths for operation 2:
Router(config)# rtr 2Router(config-rtr)# type pathEcho protocol ipIcmpEcho 172.16.1.177Router(config-rtr)# paths-of-statistics-kept 3Related Commands
request-data-size
To set the protocol data size in the payload of the SAA operation's request packet, use the request-data-size command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
request-data-size byte
no request-data-size
Syntax Description
byte
Size of the protocol data in the payload of the request packet of the operation. Range is 0 to the maximum of the protocol. The default is 1 byte.
Defaults
1 byte
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
When the protocol name has the suffix "appl," the packet uses both a request and respond data size (see the response-data-size SAA RTR configuration command), and the data size is 12 bytes smaller than the normal payload size (this 12 bytes is the ARR Header used to control send and data response sizes).
Examples
The following example sets the request packet size to 40 bytes for operation 3:
Router(config)# rtr 3Router(config-rtr)# type echo protocol snalu0echoappl cwbc0aRouter(config-rtr)# request-data-size 40Related Commands
Sets the protocol data size in the payload of the SAA operation's response packet.
Specifies an SAA operation and enters SAA RTR configuration mode.
response-data-size
To set the protocol data size in the payload of an SAA operation's response packet, use the response-data-size command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
response-data-size byte
no response-data-size
Syntax Description
byte
Size of the protocol data in the payload in the operation's response packet. For "appl" protocols, the default is 0 bytes. For all others, the default is the same value as the request-data-size.
Defaults
0 bytes
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The response-data-size command is only applicable for the following operations:
•
•
•
•
Note that these protocols are defined with the type command that end in "appl" (for example, snalu0echoappl). When the protocol ends in "appl," the response data size is 12 bytes smaller than normal payload size.
Examples
The following example configures the response packet size of snaLU0 Echo operation 3 to 1440 bytes:
Router(config)# rtr 3Router(config-rtr)# type echo protocol snalu0echoappl cwbc0aRouter(config-rtr)# response-data-size 1440Related Commands
Sets the protocol data size in the payload of the SAA operation's request packet.
Specifies an SAA operation and enters SAA RTR configuration mode.
rtr
To begin configuring an SAA operation by entering SAA RTR configuration mode, use the rtr command in global configuration mode. To remove all configuration information for an operation, including the schedule of the operation, reaction configuration, and reaction triggers, use the no form of this command.
rtr operation-number
no rtr operation-number
Syntax Description
operation-number
Operation number used for the identification of the SAA operation you wish to configure.
Defaults
None
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.2(11)T
The maximum number of operations was increased from 500 to 2000 (SAA Engine II).
Usage Guidelines
The rtr command is used to configure Cisco Service Assurance Agent (SAA) operations. Use this command to specify an identification number for the operation you are about to configure. After you enter this command, you will enter the SAA RTR configuration mode, indicated by the (config-rtr) router prompt. The "Related Commands" table lists the commands you can use in SAA RTR configuration mode.
For detailed information on the configuration of the Cisco SAA feature, see the "Network Monitoring Using Cisco Service Assurance Agent" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2.
SAA allows a maximum of 2000 operations.
Debugging is supported only on the first 32 operation numbers.
After you configure a operation, you must schedule the operation. For information on scheduling a operation, refer to the rtr schedule global configuration command. You can also optionally set reaction triggers for the operation. For information on reaction triggers, refer to the rtr reaction-configuration and rtr reaction-trigger global configuration commands.
Note
To display the current configuration settings of the operation, use the show rtr configuration EXEC command.
Examples
In the following example, operation 1 is configured to perform end-to-end response time operations using an SNA LU Type 0 connection with the host name cwbc0a. Only the type SAA RTR configuration command is required; all others are optional.
Router(config)# rtr 1Router(config-rtr)# type echo protocol snalu0echoappl cwbc0aRouter(config-rtr)# request-data-size 40Router(config-rtr)# response-data-size 1440Router(config-rtr)# exitRouter(config)#
Note
Related Commands
rtr key-chain
To enable SAA control message authentication and specify an MD5 key chain, use the rtr key-chain command in global configuration mode. To remove control message authentication, use the no form of this command.
rtr key-chain name
no rtr key-chain
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
The authentication configuration on the SAA collector and SAA Responder must be the same. Both sides must configure the same key chain or both sides must not use authentication.
Examples
In the following example, the SAA control message uses MD5 authentication, and the key chain name is CSAA:
Router(config)# rtr key-chain csaaRelated Commands
rtr low-memory
To specify how much unused memory must be available to allow SAA configuration, use the rtr low-memory command in global configuration mode. 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
value
Specifies amount of memory, in bytes, that must be available to configure SAA (RTR). The range is from 0 to the maximum amount of free memory bytes available.
Defaults
The default value is 25 percent of the memory available on the system.
Command Modes
Global 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. If this command is not used, the default low-memory value is 25 percent. This means that if 75 percent of system memory has been utilized you will not be able to configure any SAA characteristics.
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 router is configured so that no less than 2 MB of memory will be free for RTR configuration:
Router(config)# rtr low-memory 2000000Related Commands
rtr
Specifies an identification number for an operation and enters SAA RTR configuration mode.
show memory
Displays statistics about memory, including memory-free pool statistics.
rtr reaction-configuration
To configure certain actions to occur based on events under the control of the SAA, use the rtr reaction-configuration command in global configuration mode. To return to the default values of the operation, use the no form of this command.
rtr reaction-configuration operation-number [verify-error-enable] [connection-loss-enable] [timeout-enable] [threshold-falling milliseconds] [threshold-type option] [action-type option]
no rtr reaction-configuration operation-number
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:
Router(config)# rtr reaction-configuration 19 threshold-type immediate action-type trapOnlyFigure 1 shows that an alert (rising trap) would be issued immediately when the response time exceeds the rising threshold and a resolution (falling trap) would be issued immediately when the response time drops below the falling threshold.
Figure 1 Example of Rising and Falling Thresholds
Related Commands
rtr reaction-trigger
To define a second SAA operation to make the transition from a pending state to an active state when one of the trigger action-type options are defined with the rtr reaction-configuration command, use the rtr reaction-trigger command in global configuration mode. To remove the trigger combination, use the no form of this command.
rtr reaction-trigger operation-number target-operation
no rtr reaction-trigger operation
Syntax Description
Defaults
No trigger combination is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Triggers are usually used for diagnostics purposes and are not used in normal operation.
Examples
In the following example, the state of operation 1 is changed from pending state to active state when action-type of operation 2 occurs:
Router(config)# rtr reaction-trigger 2 1Related Commands
rtr reset
To perform a shutdown and restart of the Service Assurance Agent engine, use the rtr reset command in global configuration mode.
rtr reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The rtr reset command stops all operations, clears SAA/RTR configuration information, and returns the SAA feature to the startup condition. This command does not reread the SAA RTR configuration stored in startup-config in NVRAM. You must retype the configuration or load a previously saved configuration file.
Caution
Examples
The following example resets SAA, clearing all stored SAA information and configuration:
Router(config)# rtr resetRelated Commands
rtr responder
To enable the SAA Responder for general SAA operations, use the rtr responder command in global configuration mode. To disable the SAA Responder, use the no form of this command.
rtr responder
no rtr responder
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used on the destination device for SAA operations to enable the sending of recieving of RTR Control packets. Enabling the SAA/RTR Responder allows the generation of packet loss statistics on the device sending SAA operations.
Examples
The following example enables the SAA Responder:
Router(config)# rtr responderRelated Commands
Enables the SAA Responder for TCP Connect operations.
Enables the SAA Responder for UDP Echo and Jitter operations.
rtr responder type tcpConnect
To enable the SAA Responder for TCP Connect operations, use the rtr responder type tcpConnect command in global configuration mode. To disable the SAA Responder, use the no form of this command.
rtr responder type tcpConnect ipaddress ipaddr port port
no rtr responder type tcpConnect ipaddress ipaddr port port
Syntax Description
ipaddress ipaddr
(Optional) Specifies the IP address that the operation will be received at.
port port
(Optional) Specifies the port number that the operation will be received on.
Defaults
None
Command Modes
Global configuration
Command History
12.0(3)T
This command was introduced.
12.1(1)T
The ipaddr and port keywords were added.
Usage Guidelines
This command is used on the destination device for SAA operations to enable the acceptance and return of TCP Connect operation packets.
Related Commands
rtr responder type udpEcho
To enable the SAA Responder for UDP Echo or Jitter operations, use the rtr responder command in global configuration mode. To disable the SAA Responder, use the no form of this command.
rtr responder type udpEcho ipaddress ipaddr port port
no rtr responder type udpEcho ipaddress ipaddr port port
Syntax Description
ipaddress ipaddr
Specifies the IP address that the operation will be received at.
port port
Specifies the port number that the operation will be received on.
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used on the destination device for SAA operations to enable UPD Echo and Jitter (UDP+) operations on non-native interfaces.
Examples
The following example enables the SAA Responder for Jitter operations:
Router(config)# rtr responder type udpEcho ipaddress A.B.C.D port 1Related Commands
Enables the SAA Responder for non-specific SAA operations.
Enables the SAA Responder for Frame Relay operations.
rtr responder type frame-relay
To enable the SAA Responder on the operational target device for Frame Relay operations, use the rtr responder type frame-relay command in global configuration mode. To disable the SAA Responder, use the no form of this command.
rtr responder type frame-relay {all | interface {serial | fr-atm} interface-ID dlci dlci-number}
no rtr responder type frame-relay {all | interface {serial | fr-atm} interface-ID dlci dlci-number}
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows the SAA Responder to respond to Frame Relay operations without receiving RTR Control Protocol packets.
Note that if you use this command, packet loss statistics will not be able to be generated for the operation because the Responder will not be able to determine the order of the received packets. To generate packet loss statistics, use the rtr responder command without specifying an operation type.
Examples
In the following example, the SAA Responder is configured to respond to Frame Relay operations specifically on Serial interface 1/0, using DLCI number 16:
Router(config)# rtr responder type frame-relay interface serial1/0 dlci 16Related Commands
rtr restart
To restart an SAA operation, use the rtr restart command in global configuration mode.
rtr restart operation-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration.
Command History
12.1(1)T
This command was introduced.
12.2(11)T
The maximum number of operations was increased from 500 to 2000 (SAA Engine II).
Usage Guidelines
To restart an operation, the operation should be in an "active" state (as defined in the rtr reaction-configuration command).
SAA allows a maximum of 2000 operations.
This command does not have a no form.
Examples
The following example restarts operation 12:
Router(config)# rtr restart 12Related Commands
Clears all current SAA/RTR statistics and configuration information from the router and resets the SAA engine.
rtr schedule
To configure the time parameters for an SAA operation, use the rtr schedule command in global configuration mode. To stop the operation and place it in the default state (pending), use the no form of this command.
rtr schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm::ss}] [ageout seconds]
no rtr schedule operation-number
Syntax Description
Defaults
The operation is placed in a pending state (that is, the operation is enabled 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. To change the configuration of the operation, use the no form of the rtr global configuration 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).
Router(config)# 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:
Router(config)# rtr schedule 1 start after 00:05:00In the following example, operation 3 begins collecting data immediately and is scheduled to run indefinitely:
Router(config)# rtr schedule 3 start-time now life foreverRelated Commands
saa apm cache-size
To set the size of the SAA Application Performance Monitor (APM) cache, use the saa apm cache-size command in global configuration mode. To reset the SAA APM cache size to its default, use the no form of this command.
saa apm cache-size bytes
no saa apm cache-size bytes
Syntax Description
Defaults
The default APM cache size is 100000 bytes.
Command Modes
Global configuration
Command History
Usage Guidelines
SAA APM script and scheduler files are kept in an area of memory called the SAA APM cache. The cache size is checked by the system before each attempt to copy a new file to the cache. If the file to be downloaded puts the cache over its size limit, a "cache trimming" operation is performed, and all files in the cache not tagged with a "sticky bit" (sticky=1) will be deleted.
Examples
In the following example, the SAA APM cache is set to 80,000 bytes (approximately 78 kilobytes):
Router(config)# saa apm cache-size 80000Router(config)# endRouter#00:01:50: %SYS-5-CONFIG_I: Configured from console by consoleRouter# show saa apm cacheCache Size (bytes): 80000Cache used (bytes): 793File Name TimeCreated TimeAccessed ref Type stickyapm.cf.1234567 00:02:50 00:00:00 1 CFG 0apm/config/smtp-1000.cfg 00:02:50 00:00:00 1 CFG 0Related Commands
Displays the amount of memory available in the SAA APM cache and information about the files stored in the cache.
saa apm copy
To copy script or scheduler files from an FTP server to the device that will initiate the SAA Application Performance Monitor (APM) operations, use the saa apm copy command in global configuration mode.
saa apm copy {script | scheduler} ftp://[username:password@]server-name/path-to-file/file-name [sticky]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The saa apm copy command downloads an SAA APM script or scheduler file from an FTP server to the local SAA APM cache in NVRAM.
A file tagged as "sticky" will not be deleted from the local APM cache during a cache trimming operation. APM cache trimming operations are initiated when the saa apm lowWaterMark value is reached.
You can force a file tagged as "sticky" to be deleted using the clear saa apm cache command.
Examples
In the following example, a Frame Relay emulation script titled "frm.scr" is downloaded from the FTP server FTP101. The username "joe" and the password "letmein" are used to access the server:
Router(config)# saa apm copy script ftp://joe:letmein@FTP101/userbin/joefiles/frm.scr stickyRelated Commands
saa apm lowWaterMark
To specify the lowest amount of free memory that must be available on the system to allow additional SAA Application Performance Monitor (APM) operations to be configured, use the saa apm lowWaterMark command in global configuration mode. To restore the default low-memory-watermark value, use the no form of this command.
saa apm lowWaterMark bytes
no saa apm lowWaterMark
Syntax Description
Defaults
The default APM low-memory-watermark is 25 percent of free memory at startup.
Command Modes
Global configuration
Command History
Usage Guidelines
The saa apm lowWaterMark global configuration command configures the lowest amount of free memory (low-memory-watermark) that must be available on the system. If the amount of available free memory falls below the value specified in the saa apm lowWaterMark command, then the SAA will not allow new APM operations to be configured. The default value is 25 percent of the memory available on the system at startup.
Note
For example, if there are 6 MB of free memory when the router starts up, and the default low-memory-watermark of 25 percent is used, then the SAA APM can use up to 4.5 MB memory for creating operations. If the free memory drops below 1.5 MB, then new APM operations cannot be created.
The value of the saa apm lowWaterMark 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.
The show saa apm information EXEC command will display the number of operations that can be configured on the device in the "Max Number of oper supported" field.
Examples
In the following example, the SAA APM low-memory-watermark is set to 3,145,728 bytes (3 MB):
Router(config)# saa apm lowWaterMark 3145728Router(config)# endRouter# show saa apm informationService Assurance Agent: Application Performance MonitorAPM Engine Version: 1.0Max Number of oper supported: 23Number of configurable oper: 23Number of oper configured: 0Number of files in cache: 0Cache Size (bytes): 100000Cache used (bytes): 0APM low memory water-mark: 3,145,728Related Commands
saa apm operation
To start or stop an SAA Application Performance Monitor (APM) operation, use the saa apm operation command in global configuration mode. To delete existing SAA APM operations, use the no form of this command.
saa apm operation operation-number {start ftp://[user:password@]server-name/path-to-file/filename | stop}
no saa apm operation [operation-number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The following files are required to perform an SAA APM operation:
•
•
•
•
All filenames can have a maximum of 255 characters.
The saa apm operation start command points to the APM configuration file to be used for the operation. The APM configuration file specifies the location of the other files used in the operation, and the target IP address for the operation.
To download script, configuration, data, and scheduler template files used by the SAA APM, and to download the documentation ("readme" files) for the scripts, go to the "Cisco SAA APM" page at http://www.cisco.com/pcgi-bin/tablebuild.pl/saa-apm.
After an operation is started using the saa apm operation start command, the operation should be stopped using the saa apm operation stop command.
Examples
In the following example, an SAA APM NNTP operation is started and stopped, and the operation is deleted from the configuration:
Router# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# saa apm operation 2 start ftp://user:password@saa-nms/apm/config/nntp-20.cfRouter(config)#1d09h: SAA-APM-1: downloading file (apm/config/nntp-20.cf) of size (532)1d09h: SAA-APM-1: using cached file (apm/scheduler/master.sch)1d09h: SAA-APM-1: using cached file (apm/scripts/nntp.scr)1d09h: SAA-APM-1: sending APM_SCRIPT_DONE message1d09h: SAA-APM-1: operation doneRouter(config)# saa apm operation 2 stopRouter(config)# no saa apm operation 2Related Commands
samples-of-history-kept
To set the number of entries kept in the history table per bucket for the SAA operation, use the samples-of-history-kept command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
samples-of-history-kept samples
no samples-of-history-kept
Syntax Description
samples
Number of entries kept in the history table per bucket. The default is 16 entries for type pathEcho and 1 entry for type echo.
Defaults
16 entries for type pathEcho
1 entry for type echo
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Use the samples-of-history-kept command to control how many entries are saved in the history table. To control the type of information that gets saved in the history table, use the filter-for-history command. To set how many buckets get created in the history table, use the buckets-of-history-kept command.
An operation can collect history and capture statistics. By default, history is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), you can configure the lives-of-history-kept SAA RTR configuration command to collect history.
Note
Examples
In the following example, ten entries are kept in the history table for each of the lives of operation 3:
Router(config)# rtr 1Router(config-rtr)# type pathecho protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# lives-of-history-kept 3Router(config-rtr)# samples-of-history-kept 10Related Commands
show rtr application
To display global information about the SAA feature, use the show rtr application command in EXEC mode.
show rtr application [tabular | full]
Syntax Description
Defaults
Full format
Command Modes
EXEC
Command History
Usage Guidelines
Use the show rtr application command to display information such as supported operation types and supported protocols.
Examples
The following is sample output from the show rtr application command in full format:
router#show rtr applicationResponse Time ReporterVersion: 2.2.0 Round Trip Time MIBMax Packet Data Size (ARR and Data): 16384Time of Last Change in Whole RTR: 03:34:44.000 UTC Sun Feb 11 2001System Max Number of Entries: 2000Number 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: dhcpType of Operation to Perform: ftpSupported ProtocolsProtocol Type: ipIcmpEchoProtocol Type: ipUdpEchoApplProtocol Type: snaRUEchoProtocol Type: snaLU0EchoApplProtocol Type: snaLU2EchoApplProtocol Type: ipTcpConnProtocol Type: httpApplProtocol Type: dnsApplProtocol Type: jitterApplProtocol Type: dlswProtocol Type: dhcpProtocol Type: ftpApplNumber of configurable probe is 490Related Commands
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr authentication
To display SAA RTR authentication information, use the show rtr authentication command in EXEC mode.
show rtr authentication
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use the show rtr authentication command to display information such as supported operation types and supported protocols.
Examples
The following is sample output from the show rtr application command:
Router# show rtr authenticationRTR control message uses MD5 authentication, key chain name is: rtrRelated Commands
show rtr collection-statistics
To display statistical errors for all SAA operations or a specified operation, use the show rtr collection-statistics command in EXEC mode.
show rtr collection-statistics [operation-number] [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.
For One Way Delay Jitter operations, the clocks on each device must be synchronized using NTP (or GPS systems). If the clocks are not synchronized, one-way measurements are discarded. (If the sum of the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the round trip time, the one-way measurement values are assumed to be faulty, and are discarded.)
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 which includes One Way reporting Values:
Router# 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: 120295The 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. OW stands for One Way. Table 128 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
To display configuration values including all defaults for all SAA operations or the specified operation, use the show rtr configuration command in EXEC mode.
show rtr configuration [operation] [tabular | full]
Syntax Description
Defaults
Full format for all operations
Command Modes
EXEC
Command History
Examples
The following is sample output from the show rtr configuration command in full format:
Router# show rtr configuration 1Complete Configuration Table (includes defaults)Entry Number: 1Owner: "Sample Owner"Tag: "Sample Tag Group"Type of Operation to Perform: echoReaction and History Threshold (milliseconds): 5000Operation Frequency (seconds): 60Operation Timeout (milliseconds): 5000Verify Data: FALSEStatus of Entry (SNMP RowStatus): activeProtocol Type: ipIcmpEchoTarget Address: 172.16.1.176Request Size (ARR data portion): 1Response Size (ARR data portion): 1Life (seconds): 3600Next Start Time: Start Time already passedEntry Ageout (seconds): 3600Connection Loss Reaction Enabled: FALSETimeout Reaction Enabled: FALSEThreshold Reaction Type: neverThreshold Falling (milliseconds): 3000Threshold Count: 5Threshold Count2: 5Reaction Type: noneNumber of Statistic Hours kept: 2Number of Statistic Paths kept: 1Number of Statistic Hops kept: 1Number of Statistic Distribution Buckets kept: 1Number of Statistic Distribution Intervals (milliseconds): 20Number of History Lives kept: 0Number of History Buckets kept: 50Number of History Samples kept: 1History Filter Type: noneThe following example verifies the configuration of an HTTP operation:
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:none
Related Commands
show rtr distributions-statistics
To display statistic distribution information (captured response times) for all 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
Defaults
Tabular format for all operations
Command Modes
EXEC
Command History
Usage Guidelines
The distributions statistics consist of the following:
•
•
•
•
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr distributions-statistics command in tabular format:
Router# show rtr distributions-statisticsCaptured StatisticsMultiple Lines per EntryLine 1Entry = Entry NumberStartT = Start Time of Entry (hundredths of seconds)Pth = Path IndexHop = Hop in Path IndexDst = Time Distribution IndexComps = Operations CompletedOvrTh = Operations Completed Over ThresholdsSumCmp = Sum of Completion Times (milliseconds)Line 2SumCmp2L = Sum of Completion Times Squared Low 32 Bits (milliseconds)SumCmp2H = Sum of Completion Times Squared High 32 Bits (milliseconds)TMax = Completion Time Maximum (milliseconds)TMin = Completion Time Minimum (milliseconds)Entry StartT Pth Hop Dst Comps OvrTh SumCmpSumCmp2L SumCmp2H TMax TMin1 17417068 1 1 1 2 0 1288192 0 64 64Related Commands
show rtr history
To display history collected for all 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
Defaults
Tabular format, history for all operations is displayed
Command Modes
EXEC
Command History
Usage Guidelines
Table 129 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.
Examples
The following is sample output from the show rtr history command in tabular format:
Router# show rtr historyPoint by point HistoryMultiple Lines per EntryLine 1Entry = Entry NumberLifeI = Life IndexBucketI = Bucket IndexSampleI = Sample IndexSampleT = Sample Start TimeCompT = Completion Time (milliseconds)Sense = Response Return CodeLine 2 has the Target AddressEntry LifeI BucketI SampleI SampleT CompT Sense2 1 1 1 17436548 16 1AB 45 A0 162 1 2 1 17436551 4 1AC 12 7 292 1 2 2 17436551 1 1AC 12 5 222 1 2 3 17436552 4 1AB 45 A7 222 1 2 4 17436552 4 1AB 45 A0 16Related Commands
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr operational-state
To display the operational state of all SAA operations or the specified operation, use the show rtr operational-state command in EXEC mode.
show rtr operational-state [operation-number] [tabular | full]
Syntax Description
Defaults
Full format for all operations
Command Modes
EXEC
Command History
11.2
This command was introduced.
12.0(5)T
This command was expanded to show information about Jitter operations.
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-stateCurrent Operational StateEntry Number:3Modification Time:*22:15:43.000 UTC Sun Feb 11 2001Diagnostics 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 Sun Feb 11 2001Latest 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:
router#show rtr operational-state 1Current Operational StateEntry Number:1Modification Time:*03:34:44.000 UTC Sun Feb 11 2001Diagnostics 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:*03:34:44.000 UTC Sun Feb 11 2001RTT 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. The * symbol in front of the time stamps indicate the time is synchronized using NTP or SNTP. For a description of the output fields, see Table 128 in the show rtr collection-statistics command documentation.
Related Commands
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr reaction-trigger
To display the reaction trigger information for all 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
Defaults
Full format for all operations
Command Modes
EXEC
Command History
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 1Reaction TableEntry Number: 1Target Entry Number: 2Status of Entry (SNMP RowStatus): activeOperational State: pendingRelated Commands
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr responder
To display SAA RTR Responder information, use the show rtr responder command in EXEC mode.
show rtr responder
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use the show rtr responder command to display information about recent sources of SAA control messages, such as who has sent recent control messages and who has sent invalid control messages.
Examples
The following is sample output from the show rtr responder command:
Router# show rtr responderRTR Responder is: EnabledNumber of control message received: 19 Number of errors: 1Recent sources:4.0.0.1 [19:11:49.035 UTC Sat Dec 2 1995]4.0.0.1 [19:10:49.023 UTC Sat Dec 2 1995]4.0.0.1 [19:09:48.707 UTC Sat Dec 2 1995]4.0.0.1 [19:08:48.687 UTC Sat Dec 2 1995]4.0.0.1 [19:07:48.671 UTC Sat Dec 2 1995]Recent error sources:4.0.0.1 [19:10:49.023 UTC Sat Dec 2 1995] RTT_AUTH_FAILRelated Commands
show rtr totals-statistics
To display the total statistical values (accumulation of error counts and completions) for all SAA operations or the specified operation, use the show rtr totals-statistics command in EXEC mode.
show rtr totals-statistics [number] [tabular | full]
Syntax Description
Defaults
Full format for all operations
Command Modes
EXEC
Command History
Usage Guidelines
The total statistics consist of the following items:
•
•
•
•
You can also use the show rtr distributions-statistics and show rtr collection-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr totals-statistics command in full format:
Router# show rtr totals-statisticsStatistic TotalsEntry Number: 1Start Time Index: *17:15:41.000 UTC Thu May 16 1996Age of Statistics Entry (hundredths of seconds): 48252Number of Initiations: 10Related Commands
show saa apm cache
To display the amount of memory available in the SAA Application Performance Monitor (APM) cache and information about the files stored in the cache, use the show saa apm cache command in EXEC mode.
show saa apm cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
SAA APM script and scheduler files are kept in an area of system memory called the SAA APM cache.
Examples
The following is sample output from the show saa apm cache command:
Router# show saa apm cacheCache Size (bytes): 100000Cache used (bytes): 6849TimeCreated TimeAccessed Size Ref Loc Type SBit FileName03/21 13:31:25 03/21 13:31:48 1170 0 1 SCR 0 user/scripts/ldap-rem.scr03/21 13:31:23 03/21 13:31:48 38 0 1 DAT 0 user/data/ldap-rem.dat03/21 13:31:22 03/21 13:31:27 69 1 0 DAT 0 user/data/ldap.dat03/21 13:31:20 03/21 13:31:27 1513 1 0 SCR 0 user/scripts/ldap.scr03/21 13:31:19 03/21 13:31:27 2500 1 0 SCH 0 user/scheduler/master.sch03/21 13:31:17 03/21 13:31:27 256 1 0 CFG 0 apm.cfg.103/21 13:31:17 03/21 13:31:17 568 1 0 CFG 0 user/config/ldap.cf03/20 14:29:13 03/20 14:29:36 735 0 1 SCR 0 user/scripts/udp-rem.scrTable 130 describes the significant fields shown in the display.
Related Commands
show saa apm information
To display details about SAA Application Performance Monitor (APM) running on the system, use the show saa apm information command in EXEC mode.
show saa apm information
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show saa apm information command:
Router# show saa apm informationService Assurance Agent: Application Performance MonitorAPM Engine Version: 1.0Max Number of oper supported: 50Number of configurable oper: 50Number of oper configured: 0Number of files in cache: 0Cache Size (bytes): 100000Cache used (bytes): 0APM low memory water-mark: 6708828Related Commands
Specifies the lowest amount of free memory that must be available on the system to allow additional SAA APM operations to be configured.
show saa apm operation
To display details about SAA Application Performance Monitor (APM) operations, use the show saa apm information command in EXEC mode.
show saa apm information [operation-number]
Syntax Description
Defaults
Information for all APM operations is displayed.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show saa apm operation command:
Router# show saa apm operationOperation Information:Operation ID: 1234567Owner: CLIControlFile URL: ftp://user:password@saa-nms/apm/config/smtp-1000.cfgSNMP Row Status: activeLatest Operation Time: *08:13:40.000 UTC Mon Oct 08 2001Latest Operation Status: 0show saa apm results
To display the accumulated data for SAA Application Performance Monitor (APM) operations, use the show saa apm results command in EXEC mode.
show saa apm results [operation-number]
Syntax Description
operation-number
(Optional) A number that uniquely identifies an APM operation. If an operation-number is not specified, all operation results in the buffer are displayed.
.
Defaults
All APM operation results are displayed.
Command Modes
EXEC
Command History
Usage Guidelines
SAA APM script and scheduler files are kept in an area of system memory called the SAA APM cache.
Examples
The following is sample output from the show saa apm results command:
Router# show saa apm resultsCache Size (bytes): 100000Cache used (bytes): 14188File Name TimeCreated TimeAccessed ref Type stickyapm/data/ldap-13.dat 13:37:20 13:37:25 1 DAT 0apm.cf.9 13:37:18 13:37:25 1 CFG 0apm/config/ldap-13.cf 13:37:18 00:00:00 1 CFG 0apm/data/ldap-12.dat 13:37:15 13:37:20 1 DAT 0apm.cf.8 13:37:14 13:37:20 1 CFG 0apm/config/ldap-12.cf 13:37:14 00:00:00 1 CFG 0apm/data/ldap-11.dat 13:37:11 13:37:16 1 DAT 0apm.cf.7 13:37:11 13:37:16 1 CFG 0apm/config/ldap-11.cf 13:37:11 00:00:00 1 CFG 0apm/scripts/ldap.scr 13:37:07 13:37:29 3 SCR 0apm/data/iptv-2.dat 13:36:49 13:36:54 1 DAT 0apm/config/iptv-2.cf 13:36:48 00:00:00 1 CFG 0apm/scripts/iptv.scr 13:36:47 13:37:08 1 SCR 0apm/scheduler/master.sch 13:36:45 13:37:34 4 SCH 0Table 131 describes the significant fields shown in the display.
Related Commands
statistics-distribution-interval
To set the time interval for each statistics distribution kept for the SAA, use the statistics-distribution-interval command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
statistics-distribution-interval milliseconds
no statistics-distribution-interval
Syntax Description
milliseconds
Number of milliseconds (ms) used for each statistics distribution kept. The default is 20 ms.
Defaults
20 ms
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
In most situations, you do not need to change the statistical distribution interval or size. Only change the interval or size when distributions are needed, for example, when performing statistical modeling of your network. To set the statistical distributions size, use the distributions-of-statistics-kept SAA RTR configuration command.
Examples
In the following example, the distribution is set to five and the distribution interval is set to 10 ms. This means that the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity.
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.28.161.21Router(config-rtr)# distribution-of-statistics-kept 5Router(config-rtr)# statistics-distribution-interval 10Related Commands
tag
To create a user-specified identifier for an SAA operation, use the tag command in SAA RTR configuration mode. To remove a tag from a operation, use the no form of this command.
tag text
no tag
Syntax Description
Defaults
No operations are tagged.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
An operation tag is normally used to logically link operations in a group
Tags can be used to support automation (for example, by using the same tag for two different operations on two different routers echoing the same target).
Examples
In the following example, operation 1 is tagged with the label bluebell:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# tag bluebellRelated Commands
threshold
To set the rising threshold (hysteresis) that generates a reaction event and stores history information for the SAA operation, use the threshold command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
threshold milliseconds
no threshold
Syntax Description
milliseconds
Number of milliseconds required for a rising threshold to be declared. The default value is 5000 ms.
Defaults
5000 ms
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The value specified for the threshold command must not exceed the value specified for the timeout SAA RTR configuration command.
The threshold value is used by the rtr reaction-configuration and filter-for-history commands.
Examples
In the following example, the threshold of operation 1 is set to 2500 ms:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# threshold 2500Related Commands
timeout
To set the amount of time the SAA operation waits for a response from its request packet, use the timeout command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
timeout milliseconds
no timeout
Syntax Description
milliseconds
Number of milliseconds (ms) the operation waits to receive a response from its request packet.
Defaults
The default timeout values vary by operation. Per the RTTMON-MIB, the defaults are:
DLSw+ (type dlsw) and FTP (type ftp) operations - 30000 ms
DNS (type dns) operations - 9 seconds
(as defined by multiplying the MAX_DNS_WAITTIME value by the MAXDNSTRIES value)TCP Connection (type tcpConnect) and HTTP (type http) operations - 60 seconds
(as defined by multiplying the MAXALIVETRIES value by the MAXSYNTRYTICKS value)Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Use the timeout command to set how long the operation waits to receive a response, and use the frequency SAA RTR configuration command to set the rate at which the SAA starts an operation.
The value specified for the timeout command cannot be greater than the value specified for the frequency command.
Examples
In the following example, the timeout for the IP/ICMP Echo operation 1 is set for 2500 ms:
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# timeout 2500Related Commands
Sets the rate at which the SAA operation starts a response time operation.
Specifies an SAA operation and enters SAA RTR configuration mode.
tos
To define a type of service (ToS) byte in the IP header of SAA operations, use the tos command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
tos number
no tos
Syntax Description
Defaults
The default type-of-service value is 0.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The type-of-service (ToS) value is an 8-bit field in IP headers. This field contains information such as precedence and TOS. This is useful for policy-routing as well as features like CAR (Committed Access Rate), where routers examine for TOS values.
When the type-of-service is defined for an operation, the SAA Responder will reflect the ToS value it recieves.
Examples
In the following example, SAA operation 1 is configured as an echo probe using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175. The ToS value is set to 0x80.
Router(config)# rtr 1Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176Router(config-rtr)# tos 0x80Related Commands
type atm-slm
To configure an ATM Service Level Monitoring (SLM) Service Assurance Agent operation, use the type atm-slm command in SAA RTR configuration mode. To disable an ATM SLM operation, use the no form of this command.
type atm-slm interface atm-interface-id
no atm-slm interface atm-interface-id
Syntax Description
Defaults
No ATM SLM SAA operations are configured.
Command Modes
SAA configuration
Command History
Usage Guidelines
This command puts you into SAA SLM configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
ATM SLM must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated.
To get complete ATM SLM statistics, you should configure all three ATM SAA operations.
Examples
In the following example, SAA operation 1 is configured as an ATM SLM operation:
Router(config)# rtr 1Router(config-rtr)# type atm-slm interface ATM0/0Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 1 start-time now life foreverRelated Commands
type dhcp
To configure a Dynamic Host Configuration Protocol SAA operation, use the type dhcp command in SAA RTR configuration mode. To disable a DHCP SAA operation, use the no form of this command.
type dhcp [source-ipaddr source-ipaddr] [dest-ipaddr dest-ipaddr] [option decimal-option [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]]
no type dhcp
Syntax Description
Defaults
The subnet-mask value is 255.255.255.0.
Command Modes
SAA 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.
Option 82 is called the Relay Agent Information option and is inserted by the DHCP relay agent when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing the Relay Agent Information option may use the information to implement IP address or other parameter assignment policies. The DHCP Server echoes the option back verbatim to the relay agent in server-to-client replies, and the relay agent strips the option before forwarding the reply to the client.
The Relay Agent Information option is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent. The initial sub-options are defined for a relay agent that is co-located in a public circuit access unit. These suboptions are as follows: a circuit-id for the incoming circuit, a remote-id which provides a trusted identifier for the remote high-speed modem, and a subnet-mask designation for the logical IP subnet from which the relay agent received the client DHCP packet.
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, 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 dhcp option 82 circuit-id 10005A6F1234Router(config-rtr)# exitRouter(config)# ip dhcp-server 172.16.20.3Related Commands
type dlsw
To configure a data-link switching (DLSw) SAA operation, use the type dlsw command in SAA RTR configuration mode. 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
None
Command Modes
SAA 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.
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.
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 Domain Name System (DNS) SAA operation, use the type dns command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type dns target-addr {ip-address | hostname} name-server ip-address
no type dns target-addr {ip-address | hostname} name-server ip-address
Syntax Description
target-addr {ip-address | hostname}
Target (destination) IP address or hostname.
name-server ip-address
IP address of the Domain Name Server.
Defaults
No default behavior or values.
Command Modes
SAA 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
type echo
To configure an SAA end-to-end echo response time probe operation, use the type echo command in SAA RTR configuration mode. To remove the operation from the configuration, use the no form of this command.
type echo protocol protocol-type target [source-ipaddr ip-address]
no type echo protocol protocol-type target [source-ipaddr ip-address]
Syntax Description
Defaults
The default SNA host sna-application name for a SNA LU type echo is NSPEcho.
The default data size for a IP/ICMP echo operation is 28 bytes.Command Modes
SAA RTR configuration
Command History
11.2
This command was introduced.
12.0(5)T
The source-ipaddr ipaddr keyword/argument combination was added to support the specification of an IP source for the operation.
Usage Guidelines
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
Prior to sending a operation packet to the responder, the SAA sends a control message to the Responder to enable the destination port.
The default for the optional characteristic request-data-size for a ipIcmpEcho operation is 28 bytes. This is the payload portion of the Icmp packet, which makes a 64 byte IP packet.
Examples
In the following example, operation 10 is created and configured as an echo probe using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.175Related Commands
Specifies an SAA operation and enters SAA RTR configuration mode.
Displays configuration values for RTR operations.
type frame-relay
To measure response time, frame loss, or data corruption across a Frame Relay permanent virtual circuit (PVC) using the Service Assurance Agent, use the type frameRelay command in global configuration mode. To delete a preconfigured frame-relay operation, use the no form of this command.
type frame-relay interface interface-ID dlci dlci-number
no type frame-relay interface interface-ID dlci dlci-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
RTR Entry configuration mode
Command History
Usage Guidelines
The SAA Responder must be enabled on the target router before this command is used. Use the rtr responder type frame-relay all global configuration command or the rtr responder global configuration command on the target router to enable the responder.
If the first measurement does not have the correct values for frames sent and frames lost, the Frame Relay monitoring operation cannot work properly. There need to be at least two successful measurements for the frames sent and frames lost to be correct.
If the encapsulation on the target interface is not Frame Relay (for example, if the encapsulation is changed), the Frame Relay operation will be removed automatically from the configuration.
Examples
In the following example, a Frame Relay monitoring operation is configured to be sent from serial interface 0/1 using DLCI subinterface 22:
Router(config)# rtr 1Router(config-rtr)#type frame-relay ?interface Serial interface over which to send measurement packetsRouter(config-rtr)#type frame-relay interface ?FR-ATM FR-ATM InterworkingSerial SerialRouter(config-rtr)#type frame-relay interface Serial ?<0-1> Serial interface numberRouter(config-rtr)#type frame-relay interface Serial 0.1 ?dlci dlci number for Frame Relay operationRouter(config-rtr)#type frame-relay interface Serial 0.1 dlci ?<16-1007> Frame-Relay DLCI NumberRouter(config-rtr)#type frame-relay interface Serial 0.1 dlci 101 ?<cr>Router(config-rtr)#type frame-relay interface Serial 0.1 dlci 101slm1-3(config-rtr-frameRelay)# ?SAA FrameRelay Configuration Commands:buckets-of-history-kept Maximum number of history buckets to collectdata-pattern Data Patterndefault Set a command to its defaultsdistributions-of-statistics-kept Maximum number of statistics distributionbuckets to captureenhanced-history Enable enhanced history collectionexit Exit probe configurationfilter-for-history Add operation to History when...frequency Frequency of an operationhours-of-statistics-kept Maximum number of statistics hour groups tocapturelives-of-history-kept Maximum number of history lives to collectno Negate a command or set its defaultsowner Owner of Entryrequest-data-size Request data sizestatistics-distribution-interval Statistics distribution interval sizetag User defined tagthreshold Operation threshold in millisecondstimeout Timeout of an operationverify-data Verify dataRouter(config-rtr-frameRelay)#Related Commands
type ftp
To configure an FTP operation, use the type ftp command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type ftp operation get url url [source-ipaddr source-ipaddr] [mode {passive | active}]
no type ftp operation get url url [source-ipaddr source-ipaddr] [mode {passive | active}]
Syntax Description
Defaults
The default FTP transfer mode is passive.
Command Modes
SAA 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.
Router(config)# rtr 3Router(config-rtr)# type ftp operation get ftp://joe:young@zxq/testRelated Commands
Displays statistical errors for all SAA operations or the specified operation.
Displays the operational state of all SAA operations or the specified operation.
type http
To configure a Hypertext Transfer Protocol (HTTP) SAA operation, use the type http command in SAA RTR configuration mode. 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
Defaults
No default behavior or values.
Command Modes
SAA 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.
Router(config)# rtr 5Router(config-rtr)# type http operation get url http://www.cisco.comRouter(config-rtr)# exitRouter(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 request commands, HTTP-RAW submode is entered using the http-raw-request command. The RTR HTTP-RAWsubmode is indicated by the (config-rtr-http) router prompt.
Router(config)# rtr 6Router(config-rtr)# type http operation raw url http://www.cisco.comRouter(config-rtr)# http-raw-requestRouter(config-rtr-http)# GET /index.html HTTP/1.0\r\nRouter(config-rtr-http)# \r\nRouter(config-rtr-http)# exitRouter(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:
Router(config)# rtr 6Router(config-rtr)# type http operation raw url http://www.proxy.cisco.comRouter(config-rtr)# http-raw-requestRouter(config-rtr-http)# GET http://www.example.com HTTP/1.0\r\nRouter(config-rtr-http)# \r\nRouter(config-rtr-http)# exitRouter(config)# rtr schedule 6 start-time nowRelated Commands
type jitter
To configure a jitter SAA operation, use the type jitter command in SAA RTR configuration mode. 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
The default for the optional characteristic request-data-size for a SAA Jitter operation is 32 bytes of UDP data.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The type jitter command configures a UDP Plus SAA operation. The UDP Plus operation is a superset of the UDP echo operation. In addition to measuring UDP round trip time, the UDP Plus operation measures per-direction packet-loss and Jitter. Jitter is inter-packet delay variance. Packet loss is a critical element in SLAs, and Jitter statistics are useful for analyzing traffic in a VoIP network.
You must enable the SAA Responder on the target router before you can configure a Jitter operation. Prior to sending a operation packet to the responder, the SAA sends a control message to the SA Agent Responder to enable the destination port.
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
rtr
Specifies an SAA operation and enters SAA RTR configuration mode.
request-data-size
Sets the payload size for SAA operation requests.
type pathEcho
To configure an IP/ICMP Path Echo SAA operation, use the type pathEcho command in SAA RTR configuration mode. To remove the operation from the configuration, use the no form of this command.
type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
no type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
Syntax Description
Defaults
None
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Keywords are not case sensitive and are shown in mixed case for readability only.
Examples
In the following example, SAA operation 10 is created and configured as pathEcho probe using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10Router(config-rtr)# type pathEcho protocol ipIcmpEcho 172.16.1.175Related Commands
Specifies an SAA operation and enters SAA RTR configuration mode.
Displays configuration values for RTR operations (probes).
type pathJitter
To configure an SAA Path Jitter monitoring operation, use the type pathJitter command in RTR Entry configuration mode. To remove an inactive Path Jitter entry from the RTR configuration, use the no form of this command.
type pathJitter dest-ipaddress ip-address [source-ipaddress source-ip] [num-packets packet-number] [interval time-ms] [targetOnly]
no type pathJitter dest-ipaddress ip-address [source-ipaddress source-ip] [num-packets packet-number] [interval time-ms] [targetOnly]
Syntax Description
Defaults
packet-number: 10
time-ms: 20 ms
Command Modes
RTR Entry configuration
Command History
Usage Guidelines
The Path Jitter SAA operation traces a specified IP path from the source to the destination and then sends a specified number of packets to each hop along the traced path. Optionally, the time interval between each test packet can be specified.
If the number of packets and the time interval are not specified, the path jitter operation will use the default values.
If the targetOnly keyword is not used, the path jitter operation will trace the "hop-by-hop" IP path from the source to the destination and send the specified number of test packets to each hop along the trace path, using the specified time interval between each test packet.
If the targetOnly keyword is used, the command will cause the pathJitter operation to send echos to the destination only (the path from the source to the destination is not traced).
Examples
The following example enables the Path Jitter operation to trace the IP path to the destination 172.69.1.129 and send ten test packets to each hop with an interval of 20 ms between each test packet:
Router# config terminalRouter(config)# rtr 1Router(config-rtr)# type pathJitter dest-ipaddr 172.69.1.129The following example enables the Path Jitter operation to send 50 test packets to 172.69.5.6 with an interval of 30 ms between each test packet:
Router# config terminalRouter(config)# rtr 2Router(config-rtr)# type pathJitter 172.69.5.6 num-packets 50 interval 30 targetOnlytype slm
To configure a permanent virtual circuit (PVC) Service Level Monitoring (SLM) Service Assurance Agent operation, use the type slm command in SAA RTR configuration mode. To disable a PVC SLM operation, use the no form of this command.
type slm interface interface-number pvc pvc-number
no type slm interface interface-number pvc pvc-number
Syntax Description
interface interface-number
Specifies the ATM interface for the operation.
pvc pvc-number
Specifies the PVC for the operation.
Defaults
No PVC SLM SAA operations are configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
This command puts you into SAA RTR SLM configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
ATM Service Level Monitoring must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated.
Examples
In the following example, SAA operation 3 is configured as a PVC SLM operation:
Router(config)# rtr 3Router(config-rtr)# type slm interface ATM0/0 pvc 200/200Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 3 start-time now life foreverRelated Commands
type t1-slm
To configure a T1-Service Level Monitoring (SLM) Service Assurance Agent (SAA) operation, use the type t1-slm command in SAA RTR configuration mode. To disable a T1-SLM operation, use the no form of this command.
type t1-slm {controller t1 controller-number | interface ima-identification-number }
no type t1-slm {controller t1 controller-number | interface ima-identification-number }
Syntax Description
controller t1 controller-number
Specifies the T1 controller for the operation.
interface ima-interface-number
Specifies the Inverse Multiplexing over ATM (IMA) group for the operation.
Defaults
No T1-SLM SAA operations are configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You can configure a T1-SLM operation on a specific controller, or on an Inverse Multiplexing over ATM (IMA) group of controllers.
This command puts you into SAA RTR SLM configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
ATM SLM must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated.
Examples
In the following example, SAA operation 5 is configured as a T1-SLM operation:
Router(config)# rtr 5Router(config-rtr)# type t1-slm controller T1 0/0Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr)# rtr schedule 5 start-time now life foreverRelated Commands
type tcpConnect
To define a tcpConnect probe, use the type tcpConnect command in SAA RTR configuration mode. To remove the type configuration for the probe, use the no form of this command.
type tcpConnect dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name | ipaddr} source-port port-number] [control {enable | disable}]
no type tcpConnect dest-ipaddr {name | ipaddr} dest-port port-number
Syntax Description
Defaults
The control protocol is enabled.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You must configure an SAA operation type before you can configure any of the other characteristics of the operation.
The Transmission Control Protocol (TCP) Connection operation is used to discover the time it takes to connect to the target device. This operation can be used to test virtual circuit availability or application availability. If the target is a Cisco router, then SA Agent makes a TCP connection to any port number specified by the user. If the destination is a non-Cisco IP host, then the user must specify a known target port number (for example, 21 for FTP, 23 for Telnet, or 80 for HTTP Server). This operation is useful in testing Telnet or HTTP connection times.
Examples
In the following example, SAA operation 11 is created and configured as a tcpConnect probe using the destination IP address 172.16.1.175, and the destination port 2400:
Router(config)# rtr 11Router(config-rtr)# type tcpConnect dest-ipaddr 172.16.1.175 dest-port 2400Related Commands
Specifies an SAA operation begins configuration for that operation.
Displays configuration values for SAA operations.
type udpEcho
To define a udpEcho probe, use the type udpEcho command in SAA RTR configuration mode. To remove the type configuration for the probe, use the no form of this command.
type udpEcho dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name | ipaddr} source-port port-number] [control {enable | disable}]
no type udpEcho dest-ipaddr {name | ipaddr} dest-port port-number
Syntax Description
Defaults
The control protocol is enabled. Prior to sending a probe packet to the Responder, the SAA collector sends a control message to the Responder to enable the destination port.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You must configure an operation type before you can configure any of the other characteristics of the operation.
The source IP address and port number are optional. If they are not specified, SAA selects the IP address nearest to the target and an available UDP port.
Examples
In the following example, SAA operation 12 is created and configured as udpEcho probe using the destination IP address 172.16.1.175 and destination port 2400:
Router# configure terminalRouter(config)# rtr 12Router(config-rtr)# type udpEcho dest-ipaddr 172.16.1.175 dest-port 2400Related Commands
Specifies an SAA operation and enters SAA RTR configuration mode.
Displays configuration values for SAA operations.
verify-data
To cause the SAA operation to check each response for corruption, use the verify-data command in SAA RTR configuration mode. To return to the default value, use the no form of this command.
verify-data
no verify-data
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Only use the verify-data command when corruption may be an issue.
Caution
Examples
In the following example, operation 5 is configured to verify the data for each response:
Router(config)# rtr 5Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.174Router(config-rtr)# response-data-size 2Router(config-rtr)# verify-dataRelated Commands
vrfName
To allow monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using SAA operations, use the vrfName command in RTR Entry configuration mode.
vrfName vrf-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
RTR Entry configuration
Command History
Usage Guidelines
If the vrf keyword and vrf-name argument combination is configured for an SAA operation, the SA Agent uses vrf-name to identify the VRF for this operation. This command should only be used if it is necessary to measure the response time over the VPN tunnel.
Examples
The following examples illustrate how to set up different SAA operations that support MPLS VPNs. These examples show how test traffic can be sent in an already existing VPN tunnel between two endpoints. Only the following operations can measure response time of a VPN tunnel.
Note that for all of the following operation types, the source IP address is not specified. The SAA will automatically specify the correct source interface when the vrfName command is used.
Configuring an Echo Operation Example
rtr 1type echo protocol ipIcmpEcho 1.1.1.1vrfName vpn1endrtr schedule 1 start nowConfiguring a Path Echo Operation Examplertr 1type pathEcho protocol ipIcmpEcho 1.1.1.1vrfName vpn1rtr schedule 1 start nowConfiguring a UDP Echo Operation Examplertr 1type udpEcho dest-ipaddr 1.1.1.1 dest-port 1213vrfName vpn1rtr schedule 1 start nowConfiguring a Jitter Operation Examplertr 1type jitter dest-ipaddr 1.1.1.1 dest-port 1213vrfName vpn1rtr schedule 1 start nowRelated Commands
