Configuring Collaboration Between the Track Module and the
Application Modules
Configuring Track-Static Routing Collaboration
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 Static Routing Configuration in the IP Routing
Volume.
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 ]
7-3
Remarks
—
Required
Not configured by default.