3Com Switch 4800G 24-Port Configuration Manual page 1240

1240 C 98: T
HAPTER RACK
n
Configuring Track-Static
Routing Collaboration
n
C
ONFIGURATION
Do not perform Track object monitoring on the IP address owner.
■
When the status of the monitored Track object turns from Negative to Positive,
■
the corresponding master restores its priority automatically.
The monitored Track object can be nonexistent, so that you can first specify the
■
Track object to be monitored using the vrrp vrid track command, and then
create the Track object using the track command.
Refer to "VRRP Configuration" on page 1073.
■
You can check the validity of a static route in real time by establishing
collaboration between Track and static routing.
If you specify the next hop but not the egress interface when configuring a static
route, you can associate the static route with a Track object and thus check the
validity of the static route according to the status of the Track object.
If the status of the Track object is Positive, then the next hop of the static
■
route is reachable, and the configured static route is valid.
If the status of the Track object is Negative, then the next hop of the static
■
route is unreachable, and the configured static route is invalid.
Follow these steps to configure the Track-Static Routing collaboration:
To do...
Enter system view
Configure the Track-Static
Routing collaboration, so as to
check the reachability of the
next hop of the static route
For the configuration of Track-Static Routing collaboration, the specified static
■
route can be an existent or nonexistent one. For an existent static route, the
static route and the specified Track object are associated directly; for a
nonexistent static route, the system creates the static route and then associates
it with the specified Track object.
The Track object to be associated with the static route can be a nonexistent
■
one. After you use the track command to create the Track object, the
association takes effect.
If a static route needs route recursion, the associated Track object must monitor
■
the next hop of the recursive route instead of that of the static route;
otherwise, a valid route may be considered invalid.
For details of static route configuration, refer to the "Static Routing
■
Configuration" on page 251.
Use the command...
system-view
ip route-static dest-address
{ mask | mask-length }
next-hop-address track
track-entry-number
[ preference
preference-value ] [ tag
tag-value ] [ description
description-text ]
Remarks
-
Required
Not configured by default.