The mpls bgp bfd-trigger-tunnel command specifies a policy to establish BGP BFD sessions.
The undo mpls bgp bfd-trigger-tunnel command deletes a policy to establish BGP BFD sessions.
By default, no trigger policy is configured.
mpls bgp bfd-trigger-tunnel { host | ip-prefix ip-prefix-name }
undo mpls bgp bfd-trigger-tunnel
| Parameter | Description | Value |
|---|---|---|
| host | Allows a device to use host addresses to establish BGP BFD sessions. | - |
| ip-prefix ip-prefix-name | Allows a device to use an IP address prefix list with a specified name to establish BGP BFD sessions. | The value is an existing IP address prefix list. |
Usage Scenario
BFD for BGP tunnel rapidly detects faults in E2E BGP tunnels. Before a BGP BFD session is established, the mpls bgp bfd enable command must be run to enable the MPLS ability to dynamically establish BGP BFD sessions on the ingress of a BGP tunnel. Then to specify the policy for dynamically establish BGP BFD sessions, run the mpls bgp bfd-trigger-tunnel command.
Either of the following trigger policies can be used:
Host address-based policy: used when all host addresses are available to trigger the creation of BGP BFD sessions.
IP address prefix list-based policy: used when only some host addresses can be used to establish BFD sessions.
Prerequisites
BFD has been globally enabled using the bfd command.
Precautions
If the mpls bgp bfd-trigger-tunnel command is run more than once, the latest configuration overrides the previous one.
Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all host addresses trigger BGP BFD session establishment.