commit

Function

The commit command commits all configured BFD sessions.

Format

commit

Parameters

None

Views

BFD session view

Default Level

2: Configuration level

Usage Guidelines

You must run the commit command to make BFD configurations take effect.

To set up BFD sessions, the following conditions should be met:

The status of the bound interface is Up.
There are routes to peer-ip.

If the conditions to set sessions are not met, the sessions cannot be set up but the system keeps the configuration entries of the sessions when you use the commit command.

The system periodically scans the BFD configuration entries that are committed but fail to set up sessions. If the conditions are met, sessions are set up.

The system limits the number of BFD sessions. If the number of BFD sessions reaches the upper limit, the system generates the log information to display the failed session setup when you use the commit command for the newly set up sessions.

Auto-negotiated static BFD sessions are automatically created through the bfd bind peer-ip source-ip auto command and are tagged with the commit label, without the commit command configured to submit configurations. After the parameters (such as the BFD control packet sending interval, receiving interval, and local detection multiplier) are changed, they take effect immediately without the commit command executed. The commit command is still available but does not take effect actually.

Example

# Commit the current configurations of BFD sessions.

<sysname> system-view
[sysname] bfd 1
[sysname-bfd-session-1] commit