LSP BFD Configuration

  1. Configure a BFD template.
  2. Enable LSP BFD on the tail node and configure the maximum number of LSP BFD sessions at the tail node.
    Note:

    The default number of LSP BFD sessions is zero.

  3. Apply a BFD template to the LSP or LSP path.
  4. Enable BFD on the LSP or LSP path.

What to do next

LSP BFD uses BFD templates to set generic BFD session parameters.

The BFD template is configured as follows:

config
   router
      bfd
         bfd-template name
            transmit-interval transmit-interval
            receive-interval receive-interval
            echo-receive echo-interval
            multiplier multiplier
            exit 

Network processor BFD is not supported for LSPs. The minimum supported BFD receive or transmit timer interval for RSVP LSPs is 100 milliseconds. Therefore, an error is generated if a user tries to bind a BFD template with the type cpm-np command or any unsupported transmit or receive interval value to an LSP. An error is generated when the user attempts to commit changes to a BFD template that is already bound to an LSP if the new values are invalid for LSP BFD.

BFD templates may be used by different BFD applications (for example, LSPs or pseudowires). If the BFD timer values are changed in a template, the BFD sessions on LSPs or spoke SDPs to which that template is bound tries to renegotiate their timers to the new values.

The bfd-template uses a begin-commit model. To edit any value within the BFD template, a <begin> needs to be executed before the template context has been entered. However, a value is stored temporarily in the template-module until the commit is issued. Values are actually used after the commit is issued.