60
To associate Track with static routing:
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Associate the static
route with a track
entry to check the
accessibility of the
next hop.
• Method 1:
ip route-static dest-address { mask | mask-length }
{ next-hop-address [ track track-entry-number ] |
interface-type interface-number
[ next-hop-address ] | vpn-instance
d-vpn-instance-name next-hop-address [ track
track-entry-number ] } [ permanent ] [ preference
preference-value ] [ tag tag-value ] [ description
description-text ]
• Method 2:
ip route-static vpn-instance s-vpn-instance-name
dest-address { mask | mask-length }
{ next-hop-address [ public ] [ track
track-entry-number ] | interface-type
interface-number [ next-hop-address ] |
vpn-instance d-vpn-instance-name
next-hop-address [ track track-entry-number ] }
[ permanent ] [ preference preference-value ] [ tag
tag-value ] [ description description-text ]
Not configured by
default.
Associating Track with PBR
PBR is a routing mechanism based on user-defined policies. Different from the traditional
destination-based routing mechanism, PBR allows you to use a policy (based on such criteria as the
source address and packet length) 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. For more information about
PBR, see Layer 3—IP Routing Configuration Guide.
PBR cannot detect the availability of any action taken on packets. When an action is not available,
packets processed by the action might be discarded. For example, configure PBR to forward packets that
match certain criteria through a user-specified interface. When the 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 the 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 NotReady state of the track entry shows that the apply clause is valid.
The following objects can be associated with a track entry:
• Outgoing interface.
• Next hop.
To Next Page
Loading...
