Associating Track With Static Routing - HP 6125G Configuration Manual

NOTE:
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 nonexistent track entry with a VRRP group or VF. The association takes effect only
•
after you use the track command to create the track entry.

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.
If the track module detects the next hop accessibility 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 accessibility detection cannot function properly.
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 Layer 3—IP Routing Configuration Guide.
To associate track with static routing:
Step
1. Enter system view.
Command
system-view
188
Remarks
N/A