The oam-bind ingress bfd-session trigger if-down egress interface command enables unidirectional transmission of information about a fault from a Bidirectional Forwarding Detection (BFD) session to an interface.
The undo oam-bind ingress bfd-session trigger if-down egress interface command cancels the unidirectional transmission of information about a fault from a BFD session to an interface.
By default, unidirectional transmission of information about a fault from a BFD session to an interface is not configured.
oam-bind ingress bfd-session bfd-session-id trigger if-down egress interface { interface-name | interface-type interface-number }
undo oam-bind ingress bfd-session bfd-session-id trigger if-down egress interface { interface-name | interface-type interface-number }
| Parameter | Description | Value |
|---|---|---|
| bfd-session bfd-session-id | Specifies the BFD local discriminator. | An integer ranging from 1 to 8191 |
| trigger if-down | Indicates that an interface goes Down when the BFD session associated with the interface monitors a fault. | - |
| interface { interface-name | interface-type interface-number } | Specifies the type and the number of an interface. | - |
| ingress egress | Indicates that the ingress BFD session reports faults to the egress interface. | - |
In the scenario where a CE is directly connected to a PE, if a BFD session is configured between PEs, and the BFD session is associated with an interface, when a link fault is detected, the BFD session on the local device informs the Operation Administration and Maintenance (OAM) management module, which triggers the physical state of the interface to go Down. When the faulty link recovers, BFD on the local device informs the OAM management module, which triggers the interface to go Up.
The unidirectional transmission of information about a fault from a BFD session to an interface can be configured only when the following requirements are met:
Both BFD sessions have been set up, and the BFD sessions must in the Up state.
The BFD session is a static BFD session.
The BFD session and the interface are exclusively associated with each other. That is, after an interface is associated with BFD session 1, the interface cannot be associated with other BFD sessions. Conversely, BFD session 1 cannot be bound to other interfaces.