R3166-R3206-HP High-End Firewalls High Availability Configuration Guide-6PW101

48
Follow these steps to associate track with static routing:
To do… Use the command…
Remarks
Enter system view system-view —
Associate the static route
with a track entry to check
the reachability of the
next hop
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 ]
Required
Use either command.
Not configured by
default.
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 ]
NOTE:
• You can associate a nonexistent track entry with a static route. The association takes effect only after you
use the track command to create the track entry.
• 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 confi
g
ured
for the NQA test group. Otherwise, the reachability 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 Network Management Configuration Guide .
Associating track with PBR
Policy-based routing (PBR) is a routing mechanism based on user-defined policies. Different from the
traditional destination-based routing mechanism, PBR enables you to use a policy (based on the source
address, packet length, and other criteria) to route packets. You can specify the VPN instance, packet
priority, outgoing interface, next hop, default outgoing interface, default next hop, and other parameters
to guide the forwarding of packets that match specific ACLs or have specific lengths.
PBR cannot detect the availability of any action taken on packets. When an action is not available,
packets processed by the action may be discarded. For example, configure PBR to forward packets that
match certain criteria through a specified interface. When the specified interface fails, PBR cannot sense
the failure, and continues to forward matching packets out of the interface.
This problem can be solved by associating track with PBR, which improves the flexibility of PBR
application, and enables PBR to sense topology changes.
After you associate a track entry with an apply clause, the detection module associated with the track
entry sends the detection result of the availability of the object (an interface or an IP address) specified
in the apply clause.
• The Positive state of the track entry shows that the object is available, and the apply clause is valid.
• The Negative state of the track entry shows that the object is not available, and the apply clause is
invalid.
• The Invalid state of the track entry shows that the apply clause is valid.