H3C Technologies H3C SecPath F1000-E - Manual (Page 290)

7
To prevent this problem, configure another route to back up the static route. When the static route is
reachable, packets are forwarded through the static route; when the static route is unreachable, packets
are forwarded through the backup route, thus avoiding network break and enhancing network
reliability.
To check the reachability of a static route in real time, establish collaboration between track and static
routing.
If you specify the next hop but not the egress interface when configuring a static route, you can establish
collaborations among the static route, the track module, and detection modules, and thus check the
reachability of the static route according to the status of the track entry.
• If the status of the track entry 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 entry is Negative, then the next hop of the static route is unreachable, and
the configured static route is invalid.
• If the status of the track entry is Invalid, the configured static route is valid.
Follow these steps to configure the track-static routing collaboration:
To do… Use the command… Remarks
Enter system view system-view —
ip route-static dest-address { mask |
mask-length } { next-hop-address | vpn-instance
d-vpn-instance-name next-hop-address } track
track-entry-number [ preference
preference-value ] [ tag tag-value ] [ description
description-text ]
Configure the track-static
routing collaboration, so as to
check the reachability of the
next hop of the static route
ip route-static vpn-instance
s-vpn-instance-name&<1-6> dest-address { mask |
mask-length } { next-hop-address track
track-entry-number [ public ] | vpn-instance
d-vpn-instance-name next-hop-address track
track-entry-number } [ preference
preference-value ] [ tag tag-value ] [ description
description-text ]
Required
Use either command.
Not configured by
default.