113
Associate the static route
with a track entry to check
the accessibility of the next
hop
ip route-static dest-address { mask | mask-length }
{ next-hop-address } track track-entry-number [
preference preference-value ] [ tag tag-value ] [
description description-text ]
Required
Not configured by
default.
NOTE:
You can associate a nonexistent track entry with a static route. The association takes effect only after you create
the track entry with the track command.
If a static route needs route recursion, the associated track entry 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 more information about static route configuration, see the
Layer 3—IP Routing Configuration Guide
.
Displaying and maintaining track entries
Display information about the
specified or all track entries
display track { track-entry-number
| all } [ | { begin | exclude |
include } regular-expression ]
Track configuration example
Static routing-track-NQA collaboration configuration example
Network requirements
As shown in Figure 29, Switch A, Switch B, Switch C, and Switch D are connected to two segments
20.1.1.0/24 and 30.1.1.0/24. Configure static routes on these switches so that the two segments can
communicate with each other, and configure route backup to improve reliability of the network.
Switch A is the default gateway of the hosts in segment 20.1.1.0/24. Two static routes to 30.1.1.0/24 exist
on Switch A, with the next hop being Switch B and Switch C respectively. These two static routes back up
each other as follows:
The static route with Switch B as the next hop has a higher priority and is the master route. If this
route is available, Switch A forwards packets to 30.1.1.0/24 through Switch B.
The static route with Switch C as the next hop acts as the backup route.
Configure static routing-track-NQA collaboration to determine whether the master route is available
in real time. If the master route is unavailable, the backup route takes effect, and Switch A forwards
packets to 30.1.1.0/24 through Switch C.
Similarly, Switch D is the default gateway of the hosts in segment 30.1.1.0/24. Two static routes to
20.1.1.0/24 exist on Switch D, with the next hop being Switch B and Switch C respectively. These two
static routes back up each other as follows:
The static route with Switch B as the next hop has a higher priority and is the master route. If this
route is available, Switch D forwards packets to 20.1.1.0/24 through Switch B.
The static route with Switch C as the next hop acts as the backup route.