I’ve tried to enable logging in order to troubleshoot a BGP session to one of our peer by following these threads:
However, after enabling monitoring like suggested, our BGP service seems to crashed and all of our BGP sessions forcefully reestablished. I’ve look at our NMS to make sure whether enabling the monitoring impacts our router CPU and memory. So far I don’t find anything unusual for both utilization.
Is there any other way for me to troubleshoot this further? Any other persistent logs that I can check? How would I check journalctl for the BGP service?
We’re planning to upgrade to 1.5 rolling releases. Just that we’ve an urgent case to troubleshoot before upgrading. Did you have any idea to see BGP logs for 1.3? What about 1.5 also? Thanks
I’d suggest to try 1.3.8 first, if you can get it. Of course it depends on your specific configuration, but it has been quite stable in my experience (much better than 1.2.x), and I’m not sure if it is safe to skip so many versions at once (direct update from 1.3.3 to 1.5 rolling).