Avaya G430, Руководство пользователя

Страница: 286 / 696

• Use the
wait-interval
command to specify how long to wait for a response
from the device. When the wait-interval is exceeded, the probe is considered
an unanswered probe. The default value is the current value of
frequency
.
• Use the
fail-retries
command to specify how many consecutive
unanswered probes change the state of an RTR from up to down. The default
value is 5.
Note:
When an RTR starts running, its state is considered up.
• Use the
success-retries
command to specify how many consecutive
answered probes change the state of an RTR from down to up. The default
value is 5.
For example:
Gxxx-001(config-rtr icmp 5)# wait-interval 2 seconds
Done!
Gxxx-001(config-rtr icmp 5)# fail-retries 3
Done!
Gxxx-001(config-rtr icmp 5)# success-retries 1
Done!
8. Exit the RTR type context, and activate the RTR with the
rtr-schedule
command.
To deactivate the RTR, use the
no rtr-schedule
command.
For example:
Gxxx-001(config-rtr icmp 5)# exit
Gxxx-001(config)# rtr-schedule 5 start-time now life forever
Once an RTR’s probing method and remote device address are configured, you
cannot change them. If you exit the RTR type context and you want to modify the
configuration of the RTR, you can enter the RTR context using the
rtr
command
and specifying the RTR ID. From the RTR context, you can run the various
modification commands described in Steps 3 to 7.
Object tracking provisioning
About this task
To configure object tracking, you must first configure at least one simple object tracker, that
is, an object tracker that tracks a single RTR. If you wish, you can then configure a track list
which contains multiple simple object trackers and specifies how to calculate the overall state
of the list. Note that a track list is itself an object tracker. Therefore, you can configure track
lists containing object trackers which are either simple object trackers, or other track lists.
Related topics:
Configuring a simple object tracker on page 287
WAN interfaces
286 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com