H3C Technologies H3C SecPath F1000-E - Manual (Page 291)

8
NOTE:
•
For the configuration of track-static routing collaboration, the specified static route can be an existent or
nonexistent one. For an existent static route, the static route and the specified track entry are associated
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 Configuration in the IP Routing
Volume.
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 VPN instance for packet forwarding, setting
the priority of the packets, setting the outgoing interface and next hop of the packets, and setting the
default outgoing interface and next hop of the packets) will be performed to instruct packet forwarding.
Policy routing cannot be aware of reachability of the link where the outgoing interface, default outgoing
interface, next hop or default next hop resides. When the link where the outgoing interface, default
outgoing interface, next hop or default next hop resides is unreachable, operations such as setting the
outgoing interface and next hop, and setting the default outgoing interface and next hop will result in
packet forwarding failure.
The problem above 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 outgoing interface, the default outgoing interface,
the next hop, and the default next hop of the packets, and use the detection modules to monitor the
reachability of the link where the outgoing interface, default outgoing interface, next hop or default 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, the link is reachable, and the operations such as setting the
outgoing interface and next hop, and setting the default outgoing interface and next hop take effect,
and can be used to instruct forwarding.
• If the status of the track entry is Negative, the link is unreachable, and the operations such as setting
the outgoing interface and next hop, and setting the default outgoing interface and next hop do not
take effect, and the configuration is ignored during packet forwarding.