[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Setting Reaction Conditions
You can set the RTR probe to react to events that
take place and to send notifications about these events.
 |
Note:
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.
|
rtr reaction-configuration action-type
- Use to specify the type of actions to occur depending
on the events controlled by RTR.
- The default is to take the traps of enabled events.
- Example
- host1(config)#rtr reaction-configuration 1
action-type trapOnly
- There is no no version.
- See rtr reaction-configuration action-type
rtr reaction-configuration operation-failure
- Use to enable the operation-failure reaction.
- The operation-failure event is triggered when a number
of consecutive probe operations are not received or when they are
received after a timeout.
- Example
- host1(config)#rtr reaction-configuration 1
operation-failure 3
- There is no no version.
- See rtr reaction-configuration operation-failure
rtr reaction-configuration path-change
- Use to enable the path-change reaction.
- The path-change event is triggered when a change is detected
in the hop table. At most, there can be one such event per test.
- Example
- host1(config)#rtr reaction-configuration 1
path-change
- There is no no version.
- See rtr reaction-configuration path-change
rtr reaction-configuration test-completion
- Use to enable test-completion reaction.
- The test-completion event is triggered when a test is
completed successfully.
- For echo, a successful test means that all probes were
sent.
- For pathEcho, a successful test means that the destination
was reached at least once.
- At most, there can be one such event per test.
- Example
- host1(config)#rtr reaction-configuration 1
test-completion
- There is no no version.
- See rtr reaction-configuration test-completion
rtr reaction-configuration test-failure
- Use to enable test-failure reaction.
- The test-failure event is triggered when a test fails.
Failure is determined in the following ways:
- If Echo, this event is triggered after testFailureValue
probes are either not received or are received after a timeout.
- If PathEcho, this event is triggered when the test ends
and no responses are received from the destination.
- At most, there can be one such event per test.
- Example
- host1(config)#rtr reaction-configuration 1
test-failure
- There is no no version.
- See rtr reaction-configuration test-failure
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]