Configuring Dynamic BFD for IPv6 Static Routes
Dynamic BFD for IPv6 static routes enables devices to fast detect link changes, improving network reliability.
Usage Scenario
To use BFD sessions to provide link detection for IPv6 static routes on the public network, you can bind static routes to BFD sessions. One IPv6 static route can be bound to one BFD session.
Optimal IPv6 static routes are delivered to the forwarding table for packet forwarding. However, IPv6 static routes cannot detect the status of the link to the next hop. You can bind IPv6 static routes to BFD sessions. A BFD session can fast detect changes over a link and inform the routing management system of the changes. The routing management system immediately deletes the IPv6 static route that is bound to the BFD session from the forwarding table and recalculates another active route. In this manner, fast route convergence is implemented.
Pre-configuration Tasks
Before configuring dynamic BFD for IPv6 static routes, configure parameters of the link layer protocol and IPv6 addresses for interfaces and ensure that the link layer protocol on the interfaces is Up.
Procedure
- Run system-view
The system view is displayed.
- Run bfd
Global BFD is enabled on the node.
- Run quit
Return to the system view.
- (Optional) Run ipv6 route-static default-bfd { detect-multiplier multiplier | min-rx-interval min-rx-interval | min-tx-interval min-tx-interval }*
- Run ipv6 route-static bfd [ interface-type interface-number | vpn-instance vpn-destination-name ] nexthop-address local-address address [ detect-multiplier multiplier ] [ min-rx-interval min-rx-interval ] [ min-tx-interval min-tx-interval ] *
The BFD parameters of an IPv6 static route are set.
If interface-type interface-number is not set, local-address ipv6-address must be specified.
If none of min-rx-interval, min-tx-interval, or detect-multiplier is specified, the default values of the BFD parameters are used globally.
- Run either of the following commands as required:
Run ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-destination-name [ nexthop-ipv6-address ] | nexthop-ipv6-address } [ preference preference | tag tag ]* bfd enable [ description text ]
A BFD session is bound to an IPv6 static route on the public network.
Run ipv6 route-static vpn-instance vpn-source-name dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-destination-name [ nexthop-ipv6-address ] | nexthop-ipv6-address [ public ] } [ preference preference | tag tag ]* bfd enable [ description text ]
A BFD session is bound to an IPv6 static route on the VPN network.
The outbound interface and next hop IP address specified when binding the IPv6 static route to a BFD session must be the same as those specified when configuring BFD parameters for the IPv6 static route.
- Run commit
The configuration is committed.
Checking the Configurations
Run the following commands to check the previous configuration.
Run the display bfd session { all | discriminator discr-value } [ verbose ] command to check information about BFD sessions.
Run the display current-configuration | include bfd command to check configurations of BFD for IPv6 static routes.
Information about a BFD session can be viewed only after parameters of the BFD session are set and the BFD session is established.
If a BFD session has been established, the status of the BFD session is Up. Run the display current-configuration | include bfd command in the system view, and you can see that the BFD session has been bound to a static route.