FRR logs missing neighbors going down

Started by michmoor, June 22, 2023, 03:19:13 AM

Previous topic - Next topic
I am running BGP and I typically send all syslogs to my collector where I will parase the logs to generate alerts.
I noticed that bgp flaps  are not producing any alerts in the logs
For example in my other system running pfsense here is the message i receive

<30>Jun 19 22:12:41 bgpd[73781]: %ADJCHANGE: neighbor 10.6.106.2(OPNsenseFW.moore.home) in vrf default Down Peer closed the session

I am expecting to see a similar message on OPNsense but noticed that type of log is not being generated at all. 
Does anyone know how to get this type of log to be created or if its being created ?


Yes the logging level has been changed to Emergency i believe and bouncing a neighbor doesnt produce any usable logs.
My question is, how should one monitor routing if there arent any good logging for it.

If you use, emergency then you are not going to get what you are looking for. Not sure what you are really asking if you know that what you like to see is only Emergency logs.

I was changing log levels as part of testing to see if the logs produced in pfsense would be/should be the same in opnsense
So for example as a BGP neighbor bounce i should see the following in the logs

<30>Jun 19 22:12:41 bgpd[73781]: %ADJCHANGE: neighbor 10.6.106.2(790-OPNsenseFW.moore.home) in vrf default Down Peer closed the session

No matter what log level i use i cant seem to find that log. Comparing frr.conf files between opnsense and my working pfsense box the configurations for logging are similar.