The display bfd troubleshooting command displays maintain-probe ping test results when a BFD session goes Down.
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bfd troubleshooting Total counts: 2 -------------------------------------------------------------------------------- Sequence Time Event Description -------------------------------------------------------------------------------- 1 2020-06-23 11:44:50 The BFD session (MD: 201) enters the AdminD own state. [Peer Ip: 2.2.2.2, Source Ip: 1. 1.1.1, Interface: -, VPN: -, CPU: 11%. Ping Results: 10 packets success, 0 packets tim eout, maximum delay 2 ms. Tracert Results: TTL: 1, IP Address: 2.2.2.2;] 2 2020-06-23 11:04:08 The BFD session (MD: 1) enters the AdminDow n state. [Peer Ip: 10.1.0.2, Source Ip: 10. 1.0.1, Interface: Ethernet0/1/16, VPN: -, CP U: 17%. Ping Results: 10 packets success, 0 packets timeout, maximum delay 4 ms. Trace rt Results: TTL: 1, IP Address: 10.1.0.2;] --------------------------------------------------------------------------------
Item | Description |
---|---|
Total counts | Total number of debugging events. |
Sequence | Sequence number. |
Time | Date and time when the BFD session went down. |
Event Description | Event Description. |
Peer Ip | Peer IP address. |
Source Ip | Source IP address. |
Ping Results | Maintain-probe ping test results. |
Tracert Results | Tracert test results. |
MD | Local discriminator. |
Interface | The interface to which the BFD session is bound. |
VPN | VPN name. |
CPU | CPU usage. |
TTL | TTL value. |