How to keep monitoring the BGP log?

General questions
#1

I’m using VyOS 1.4.
I want to monitor the BGP log. Like Cisco’s “debug ip bgp”.

I set it to log by changing neighbors as follows.:

vyos@VyOS2:~$ sh conf c | match log-nei
set vrf name R13 protocols bgp parameters log-neighbor-changes

Please let me know if there is a good way.

#2

Hello @ZettaiNonSugar , the following command may be useful to you.

image
image1002×852 98.1 KB

#3

Rufat, thank you for your reply.

With the “monitor protocol bgp enable” command, I couldn’t see the log.
After enabling debugging, do I need to do anything else to see the results?

#4

@ZettaiNonSugar If you write the command in this form, the command is not complete.

SmartSelect_20220327-185303_Microsoft Remote Desktop
SmartSelect_20220327-185303_Microsoft Remote Desktop1418×308 92 KB

#5

I made it like an image capture, but the debug log is not displayed.
What’s wrong?

monitor_bgp
monitor_bgp792×232 9.9 KB

#6

you can look here. /var/log/messages

#7

It was possible with VyOS 1.3.0-rc6.
I can see the log with “tail -f / var / log / messages | grep bgpd”.
I was also able to see the log with “monitor protocol bgp background start”.

But “VyOS 1.4-rolling-202204020217” doesn’t work.

#8

Looks like the problem is still there also in VyOS 1.4-rolling-202205161133.

This my assumption is based on the following :
…
BGP debugging status:
BGP updates debugging is on (inbound)
BGP updates debugging is on (outbound)
BGP allow martian next hop debugging is on
…
…

vyos@vyos:/var/log$ show ip bgp neighbors 192.168.41.9 received-routes
BGP table version is 5, local router ID is 192.168.41.10, vrf id 0
Default local pref 100, local AS 64888
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop’s vrf id, < announce-nh-self
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path
*> 10.75.181.64/26 192.168.41.9 0 64880 i
*> 10.75.200.192/26 192.168.41.9 0 64880 i

Total number of prefixes 2
…

vyos@vyos:/var/log$ cat messages |grep bgp
May 16 16:24:52 localhost bgpd[1089]: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
May 16 16:25:08 vyos bgpd[1089]: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
May 16 16:25:08 vyos bgpd[1089]: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
May 16 16:39:32 vyos bgpd[1089]: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00

vyos@vyos:/var/log$ date
Wed 01 Jun 2022 01:47:58 PM UTC

Much probably the few entries on the 16th of May were logged when I still was on 1.3 … on that day I upgraded …

Any idea when this will be fixed ?

#9

In rolling release, the logs can be viewed using the journalctl and the VyOS operational command:

$ show log protocol bgp

journalctl -b | grep -i bgp