H3C Technologies H3C S10500 Series Switches - Manual (Page 181)

172
NOTE:
•
VRRP tracking is not valid on an IP address owner. An IP address owner refers to a router when the IP
address of the virtual router is the IP address of an interface on the router in the VRRP group.
• When the status of the track entry changes from Negative to Positive or Invalid, the associated router
restores its priority automatically.
• You can associate a nonexistent track entry with a VRRP group. The association takes effect only after
you use the track command to create the track entry.
• For more information about VRRP, see the chapter “VRRP configuration.”
Associating track with static routing
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. Faults or
topological changes in the network can make the routes unreachable, causing network breaks.
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, avoiding network breaks and enhancing network reliability.
To check the accessibility of a static route in real time, establish association between the track and the
static route.
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. This enables you to
check the accessibility of the static route by the status of the track entry.
• The Positive state of the track entry shows that the next hop of the static route is reachable and that
the configured static route is valid.
• The Negative state of the track entry shows that the next hop of the static route is not reachable and
that the configured static route is invalid.
• The Invalid state of the track entry shows that the accessibility of the next hop of the static route is
unknown and that the static route is valid.
Follow these steps to associate track with static routing:
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 ]
Associate the static route with
a track entry to check the
accessibility of the next hop
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.