H3C Technologies H3C SR8800 - Manual (Page 25)

9
Step Command Remarks
2. Detect reachability
of the static route’s
next hop through
BFD.
• Approach 1:
ip route-static dest-address { mask | mask-length }
interface-type interface-number next-hop-address [ bfd
{ control-packet | echo-packet } ] [ preference
preference-value ] [ tag tag-value ] [ description
description-text ]
• Approach 2:
ip route-static vpn-instance s-vpn-instance-name&<1-6>
dest-address { mask | mask-length } interface-type
interface-number next-hop-address [ bfd { control-packet |
echo-packet } ] [ preference preference-value ] [ tag tag-value ]
[ description description-text ]
Not
configured
by default
NOTE:
•
To implement BFD in the control-packet mode, the remote end must create a BFD session; otherwise the
BFD function cannot work. To implement BFD in the echo-packet mode, the BFD function can work
without the remote end needing to create any BFD session.
• If a route flap occurs, enabling BFD may worsen the flapping. Be cautious for use of this feature.
Detecting next hop reachability through track
If you specify the next hop but not outgoing interface when configuring a static route, you can associate
the static route with a track entry to check the static route validity.
• When the track entry is positive, the static route's next hop is reachable and the static route takes
effect;
• When the track entry is negative, the static route's next hop is unreachable and the static route is
invalid.
For more information about track, see High Availability Configuration Guide.
Network requirements
To detect the reachability of a static route's next hop through a Track entry, you must create a Track first.
For the Track configuration procedure, see High Availability Configuration Guide.
Configuration procedure
To detect the reachability of a static route's next hop through Track:
Step Command Remarks
1. Enter system view. system-view N/A