Configuring Track-Static Routing Collaboration - 3Com S7906E Configuration Manual

Configuring Track-Static Routing Collaboration

A static route is a manually configured route. With a static route configured, packets to the specified
destination are forwarded through the path specified by the administrator.
The disadvantage of using static routes is that they cannot adapt to network topology changes. If a fault
or a topological change occurs in the network, the routes will be unreachable and the network breaks.
To prevent this problem, you can 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.
You can check the reachability 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
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.
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
Use the command...
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 ]
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 ]
1-6
Remarks
—
Required
Use either command.
Not configured by default.