Configuring RTR

You can configure RTR with the following tasks:

Configuring the Probe Type for RTR

You can configure the probe type—either an echo probe or a path echo probe after entering into the RTR Configuration mode.

You must specify the probe type value before any other RTR probe configuration. If you change the type for an existing RTR entry, all values are reset, including the administrative status. There is no default value. More than one RTR entry can become active, provided each entry’s target address is unique.

If you configure multiple RTR entries to use the same target address, you must issue the receive-interface command to specify the interface on which the RTR probe expects to receive responses. (For information, see Setting the Receiving Interface for the RTR Entry.)

If you use a target address already configured for another RTR entry that is active, the test will not run if both entries are in the same virtual router. If they are in distinct virtual routers, however, there is no restriction.

To enter into the RTR configuration mode:

To configure the probe type:

Configuring the Probe Characteristics for RTR

You can configure the probe characteristics presented in Table 7.

Table 7: Probe Characteristics

Characteristic

Description

frequency

Time between tests (in seconds)

hops-of-statistics-kept

Hops per path for which statistics are gathered

max-response-failure

Maximum number of consecutive failures

operations-per-hop

Number of probes per hop

owner

Owner of the probe

receive-interface

Interface on which the probe expects to receive responses

request-data-size

Request’s payload size

samples-of-history-kept

Maximum number of history samples

tag

User-defined tag

timeout

Probe timeout (in milliseconds)

tos

A value for the TOS byte

Note: You cannot set any of these characteristics until you have set the probe type using the type command. The default values of these characteristics depend on the type of the entry.

To configure the probe characteristics:

Setting the Reaction Conditions for the RTR Probe

You can set the RTR probe to react to events that take place and to send notifications about these events.

Note:

  • You cannot set any of these characteristics until you have set the probe type using the type command. The default values of these characteristics depend on the type of the entry.
  • The only no version for all the rtr reaction-configuration commands is no rtr reaction-configuration rtrIndex. Use the no version to clear all traps. This works for all the options.

To set one or more reaction conditions for the RTR probe:

Scheduling the RTR Probe

When you have configured the RTR probe, you must schedule the operation to begin collecting statistics and other information about problems that may arise.

Note:

  • You cannot set any of these characteristics until you have set the probe type using the type command. The default values of these characteristics depend on the type of the entry.
  • The only no version for all the rtr schedule commands is no rtr schedule rtrIndex. Use the no version to stop the test. The no version stops the probe operation by putting it in the pending state. The no version also resets the restart-time attribute and the life attribute.

To schedule the probe:

Capturing Statistics and Collecting Error Information for the RTR Probe

The primary objective of RTR is to collect statistics and information about network performance. You can control the number and type of statistics collected using the hops-of-statistics-kept and max-response-failure commands.

Note: You cannot set any of these characteristics until you have set the probe type using the type command. The default values of these characteristics depend on the type of the entry.

To control the number and type of statistics collected:

Collecting History for the RTR Probe

RTR can collect data samples for a given probe. These samples are referred to as history data. When RTR collects history, it refers to tests. A test is the lifetime of a probe operation.

You can set the maximum number of entries in the history table for each RTR probe using the samples-of-history-kept command.

This command enables you to control the number of samples saved in the history table. If you set the number of samples to 0, no samples are kept.

Note: You cannot set this characteristic until you have set the probe type using the type command. The default values of this characteristic depend on the type of the entry.

Best Practice: Collect history only when there is a problem in your network because collecting history increases memory usage.

To set the maximum number of entries in the history table for each RTR probe:

Setting the Receiving Interface for the RTR Entry

When you configure multiple RTR entries to use the same target address, you must issue the receive-interface command to set the interface on which the probe expects to receive responses. This action enables the router to map incoming responses to the proper RTR entry, even when multiple RTR entries have the same target address.

Note: You cannot set this characteristic until you have set the probe type using the type command.

To specify the interface on which the RTR probe expects to receive responses:

Related Documentation