commit

Usage Scenario

To make the modification on a BFD session take effect, you must run the commit command.

Precautions

• To establish a BFD session, the interface bound to the BFD session must be Up and there is a reachable route to the peer IP address.

• If conditions for BFD session setup are not met, the system keeps the configuration entries of the BFD session. The BFD session, however, cannot be established when you use the commit command.

• The system periodically scans BFD configuration entries that are committed but not used to establish sessions. If conditions are met, a session is established.

• The number of BFD sessions that can be established in the system is limited. When the number of established BFD sessions reaches the upper limit and you use the commit command to commit the configurations of a new BFD session, the system generates a log indicating that the BFD session cannot be established and sends traps.

• After creating a BFD session, if you need to modify session parameters, such as process-pst, process-interface-status, min-tx-interval, min-rx-interval, detect-multiplier, tos-exp (BFD session view), wtr, description, authentication-mode (BFD), trigger if-down delay or receiving-admindown trigger if-down you can directly run the corresponding commands without running the commit command, and the modification takes effect immediately.

• After running the bfd bind peer-ip source-ip auto command to create configurations for a static BFD session with automatically negotiated discriminators, you do not need to run the commit command to commit the configurations. BFD sessions can be automatically established, and relevant configurations are labeled with the commit tags. The commit command can still be used but does not take effect.