proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-06-06 19:43:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #12212 from donaldsharp/clarify_issue

Browse Source 
bgpd: Clarify what NHT error message means
This commit is contained in:
Donatas Abraitis 2022-10-27 18:01:44 +01:00 committed by GitHub
commit 6535ba824b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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);