The process-interface-status command enables the association between the status of the BFD session and the status of the bound interface.
The undo process-interface-status command restores the default setting.
By default, the association between the status of the BFD session and the status of the bound interface is not enabled. The change of BFD session status does not affect interface status recorded in IFNET.
process-interface-status [ sub-if ] [ reboot-no-impact ]
undo process-interface-status [ sub-if ] [ reboot-no-impact ]
| Parameter | Description | Value |
|---|---|---|
| sub-if | Enabled the association between the status of the BFD session and the status of the bound sub-interface. That is, the status change of a BFD session that is bound to a primary interface affects the status of the primary interface and sub-interface in IFNET. | - |
| reboot-no-impact | Disables the association between a multicast BFD session and interface during device startup. |
- |
Usage Scenario
After the process-interface-status command is configured, the application program can obtain the status of the BFD session through querying the interface status recorded in IFNET.
Precautions
Configure the process-interface-status command for only the one-hop BFD session that uses the default multicast address to allow the BFD session to be bound to the primary interface or sub-interface.
The status of a VE interface cannot be associated with the status of the BFD session.
If one interface is bound to multiple BFD sessions, enable the process-interface-status command in only one session. The change of only one BFD session changes the status of the bound interface.
After the association between the status of the BFD session and the status of the bound interface is enabled, if the BFD session fails and turns to be Down, the interface bound to it accordingly turns to be "BFD Down".
When the process-interface-status command and the commit command are run in succession, the BFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, the BFD session does not notify the interface of the BFD status immediately, avoiding that the BFD session notifies the interface of incorrect status information that results in incorrect interface status change. After the configuration is committed, the BFD sessions can notify the interface of the BFD status change. In this manner, the BFD session status is associated with the interface status.
If the process-interface-status command is saved in the configuration file, the BFD session that is bound to the interface notifies the interface that the BFD session is Down when the router is restarted, in view of the initial status of an interface being Down.
Before the BFD status is associated with the interface status, the BFD configurations on the two routers must be correct and symmetrical. If the BFD status on the local interface is Down, check whether the BFD configuration on the peer is correct or whether the BFD session is shut down.
If the networking requires that the BFD status must be synchronized with the interface status, you can run the shutdown and undo shutdown commands to change the status of the BFD session. When the undo shutdown command is run, a timer to test the BFD session status is started. If the BFD session goes Up through negotiation before the timer expires, the BFD session notifies the interface of the Up state. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down state after the timer expires. The BFD session status and the interface status are in real-time synchronization.