BFD
BFD (Bidirectional Forwarding Detection) is configured in the Control Plane section of the task page. It rapidly detects link failures between neighboring devices and works with routing protocols such as BGP, OSPF, and IS-IS to accelerate failover to backup routes.
BFD is created as a separate instance in the protocol tree and then bound to an interface and/or an IGP/BGP adjacency. Make sure that the instance-id in the protocol matches the one in the interface binding.
Table — Basic BFD Parameters
| Name | Description | Value |
|---|---|---|
| Instance ID | BFD instance identifier | Unique within the task/agent |
| Local / remote address | IP addresses of the BFD session | Must match the testbed underlay |
| Desired Min TX Interval | Desired interval between Control packet transmissions | Microseconds or milliseconds, as shown in the UI |
| Required Min RX Interval | Minimum acceptable receive interval | Negotiated with the peer |
| Detect Multiplier | Failure-detection multiplier | Packet loss threshold = interval × multiplier |
| Multihop | Multihop session | Enable for BFD across multiple hops |
| Echo | Echo mode, if supported by the testbed | As required |
After starting the task, review session state on the Control Plane, Metrics, Events, and Logs tabs: Up/Down state, diagnostic codes, and correlation with BGP/OSPF/IS-IS adjacencies. If the session does not come up, first check L3 connectivity, the underlay VLAN/tunnel, and timer compatibility with the DUT.