proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-08-08 09:30:30 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

bgpd: Clarify what NHT error message means

Browse Source 
When waiting on a path to reach the peer, modify the debug/show
output to give a better understanding to the operator about what
they should be looking for.

Signed-off-by: Donald Sharp <sharpd@nvidia.com>
This commit is contained in:
Donald Sharp 2022-10-27 09:21:41 -04:00
parent d5850a1b6a
commit 6029afbc10
1 changed files with 37 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
bgpd/bgp_fsm.c
View File

@ -627,7 +627,7 @@ const char *const peer_down_str[] = {"",
"BFD down received", "BFD down received",
"Interface down", "Interface down",
"Neighbor address lost", "Neighbor address lost",
"Waiting for NHT", "No path to specified Neighbor",
"Waiting for Peer IPv6 LLA", "Waiting for Peer IPv6 LLA",
"Waiting for VRF to be initialized", "Waiting for VRF to be initialized",
"No AFI/SAFI activated for peer", "No AFI/SAFI activated for peer",
@ -1880,7 +1880,8 @@ int bgp_start(struct peer *peer)
if (!bgp_peer_reg_with_nht(peer)) { if (!bgp_peer_reg_with_nht(peer)) {
if (bgp_zebra_num_connects()) { if (bgp_zebra_num_connects()) {
if (bgp_debug_neighbor_events(peer)) if (bgp_debug_neighbor_events(peer))
zlog_debug("%s [FSM] Waiting for NHT", zlog_debug(
"%s [FSM] Waiting for NHT, no path to neighbor present",
peer->host); peer->host);
peer->last_reset = PEER_DOWN_WAITING_NHT; peer->last_reset = PEER_DOWN_WAITING_NHT;
BGP_EVENT_ADD(peer, TCP_connection_open_failed); BGP_EVENT_ADD(peer, TCP_connection_open_failed);