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
i get this logs on the collector :
docker exec openbmp_collector tail -f /var/log/openbmpd.log
2020-08-16T13:05:20.284831 | INFO | handleInitMsg | Init message type 2 and length 2 parsed
2020-08-16T13:05:20.284838 | INFO | handleInitMsg | Init message type 2 = R2
2020-08-16T13:05:20.284845 | INFO | ReadIncomingMsg | Router ID hashed with hash_type: 1
2020-08-16T13:05:20.285037 | INFO | ReadIncomingMsg | 192.168.245.202: PEER UP Received, local addr=10.1.2.2:54512 remote addr=10.1.2.1:179
2020-08-16T13:05:20.506180 | INFO | ReadIncomingMsg | 192.168.245.202: Caught: ERROR: Unsupported BMP message version
2020-08-16T13:05:20.663553 | INFO | ClientThread | 192.168.245.202: Thread for sock [0] ended normally
i have connected a vMX routers version 19.1...
attached files of what i see in grafana , and my netowrk topology ... all rest of dash boards are empty
*192.168.245.202 - this is the ip of my juniper router.
The text was updated successfully, but these errors were encountered:
hi
this issue was seen in juniper 19.x .... but when i moved back to juniper 17.x all starting to work !
so i guess some thing has changed in the BMP protocol itself / juniper change some thing related to this...
also tried to run it on CSR1000v - also many fields empty with many issues.
any how - if u are running in production version MX ver 17.x ... this should work for u , in my case i run : 17.4R1.16
hi guys ,
i get this logs on the collector :
docker exec openbmp_collector tail -f /var/log/openbmpd.log
i have connected a vMX routers version 19.1...
attached files of what i see in grafana , and my netowrk topology ... all rest of dash boards are empty
*192.168.245.202 - this is the ip of my juniper router.
The text was updated successfully, but these errors were encountered: