H3C Technologies H3C S12500 Series Switches - Manual (Page 216)

205
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 or
VF restores its priority automatically.
• You can associate a track entry with a VRRP group or VF before or after you create the track entry.
However, the association takes effect only after you create the track entry with the track command.
Associating Track with static routing
IMPORTANT:
•
If the Track module detects the next hop reachability of the static route in a private network through
NQA, the VPN instance name of the next hop of the static route must be consistent with that configured
for the NQA test group. Otherwise, the reachability detection cannot function correctly.
• 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 might be considered invalid.
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, 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 break and enhancing network reliability.
To check the reachability of a static route in real time, establish association between 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 to check the reachability
of the static route according to 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 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
the configured static route is invalid.
• The Invalid state of the track entry shows that the reachability of the next hop of the static route is
unknown, and the static route is valid.
To associate Track with static routing:
Step Command Remarks
1. Enter system view. system-view N/A