Configuring Track-Policy Routing Collaboration - H3C S9500E Series Configuration Manual

directly; for a nonexistent static route, the system creates the static route and then associates it with the
specified track entry.
The track entry to be associated with the static route can be a nonexistent one. After you use the track
•
command to create the track entry, the association takes effect.
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 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 Static Routing in the Layer 3 – IP Routing
•
Configuration Guide.

Configuring track-policy routing collaboration

Policy routing is a routing mechanism based on user-defined policies. Different from the
traditional destination-based routing mechanism, policy routing enables you to use policies
(based on the source address, packet length, and other criteria) to route packets flexibly. For
packets matching a certain criterion (packet length or ACL rule), operations (setting the next hop
of the packets) will be performed to instruct packet forwarding.
Policy routing cannot be aware of reachability of the link where the next hop resides. When the
link where the next hop resides is unreachable, setting the next hop will result in packet
forwarding failure.
The above problem can be solved with the collaboration function, enhancing the flexibility of
policy routing application and its awareness of the dynamic networking environment. You can
associate the policy routing with a track entry when configuring the next hop of the packets, and
use the detection modules to monitor the reachability of the link where the next hop of the packets
resides, so as to dynamically determine the availability of the policy.
•
If the status of the track entry is Positive or Invalid, the link is reachable, and the operation of
setting the next hop takes effect, and can be used to instruct forwarding.
•
If the status of the track entry is Negative, the link is unreachable, and the operation of
setting the next hop does not take effect, and the configuration is ignored during packet
forwarding.
Configuration prerequisites
Before configuring track-policy routing, you need to create a policy or a policy node and
configure the match rules as well.
Configuration procedure
To configure the track-policy routing collaboration:
To do...
1. Enter system view
Use the command...
system-view
184
Remarks
—