You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to have visibility in FRR logs when a BGP peer is connected/disconnected and the reason for disconnection. We tried using "bgp log-neighbor-changes" which logs the events as to when a peer has gone down or brought up. Is there any other configuration by which we can log the reason for BGP peer going down and identify if there is any issue in peering:-
2023/12/22 10:46:01 BGP: [V1CHF-JSGRR] %NOTIFICATION: sent to neighbor 24.2.1.103 6/4 (Cease/Administratively Reset) 0 bytes
2023/12/22 10:46:01 BGP: [VB567-F0EDJ] %ADJCHANGE: neighbor 24.2.1.103(j3chysr01stg06) in vrf er_vrf_1 Down User reset
2023/12/22 10:46:03 BGP: [V1CHF-JSGRR] %NOTIFICATION: sent to neighbor 24.2.1.103 6/7 (Cease/Connection collision resolution) 0 bytes
2023/12/22 10:46:03 BGP: [QTNRG-A0X1J] %ADJCHANGE: neighbor 24.2.1.103(j3chysr01stg06) in vrf er_vrf_1 Up
2023/12/22 10:46:04 BGP: [M59KS-A3ZXZ] bgp_update_receive: rcvd End-of-RIB for IPv4 Unicast from 24.2.1.103 in vrf er_vrf_1
Thanks and Regards,
Chinmaya Agarwal.
The text was updated successfully, but these errors were encountered:
Hi,
We would like to have visibility in FRR logs when a BGP peer is connected/disconnected and the reason for disconnection. We tried using "bgp log-neighbor-changes" which logs the events as to when a peer has gone down or brought up. Is there any other configuration by which we can log the reason for BGP peer going down and identify if there is any issue in peering:-
Thanks and Regards,
Chinmaya Agarwal.
The text was updated successfully, but these errors were encountered: