The trigger if-down delay command sets a delay time after which a local device instructs the interface protocol to go down after the device detects a BFD down event.
The undo trigger if-down delay command restores the default delay time.
The default delay time is 0s.
| Parameter | Description | Value |
|---|---|---|
delay-time |
Sets the delay time, after which a local device instructs the interface protocol to go down after the device detects a BFD down event. |
The value is an integer ranging from 1 to 10000, in seconds. |
If no link fault is detected and negotiation of a BFD session times out, the BFD session goes down. In this case, if the BFD session is associated with the status of the interface bound to the BFD session, the link protocol of the interface also goes down. To delay the associated notification, run the trigger if-down delay command. If the BFD session is still down after the delay time elapses, the link status of the associated interface goes down.
Prerequisites
The BFD session status has been associated with the status of the interface bound to the BFD session using the process-interface-status command.
Precautions
This command takes effect on multicast BFD only in BFD non-authentication scenarios and is mutually exclusive with the authentication-mode command.
If the receiving-admindown trigger if-down command is run, the local device can instruct the interface protocol to go down immediately after receiving an admindown packet.
# Set the delay time to 50s, after which a local device instructs the interface protocol to go down after the device detects a BFD down event.
<HUAWEI> system-view [HUAWEI] bfd test bind peer-ip default-ip interface gigabitethernet0/0/1 [HUAWEI-bfd-session-test] process-interface-status [HUAWEI-bfd-session-test] trigger if-down delay 50