R0106-HP MSR Router Series High Availability Configuration Guide(V7)
70
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 NotReady 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.
When you associate Track with static routing, follow these restrictions and guidelines:
• 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.
• For static routing-Track-NQA collaboration, you must configure the same VPN instance name for the
static route's next hop and the NQA operation. Otherwise, the accessibility detection cannot
function correctly.
• 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 might be considered
invalid.
To associate Track with static routing:
Ste
p
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-length |
mask } { interface-type interface-number
[ next-hop-address ] | next-hop-address
[ track track-entry-number ] | 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-length | mask } { interface-type
interface-number [ next-hop-address ] |
next-hop-address [ public ] [ track
track-entry-number ] | 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 uses user-defined policies (based on such criteria as the source address and packet length) to route
packets. You can specify the VPN instance, packet priority, output interface, next hop, default output
interface, default next hop, and other parameters to guide the forwarding of packets that match specific