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
2019-02-05T00:00:48.244727 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 153 is not implemented yet, skipping
2019-02-05T00:00:48.244733 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.244738 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 10 is not implemented yet, skipping
2019-02-05T00:00:48.244744 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 208 is not implemented yet, skipping
2019-02-05T00:00:48.244749 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 145 is not implemented yet, skipping
2019-02-05T00:00:48.244755 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245245 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-02-05T00:00:48.245256 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245262 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
the error output from /var/log/openbmpd.log like this:
2019-03-05T03:38:13.161599 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 211 is not implemented yet, skipping
2019-03-05T03:38:13.161602 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161605 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161609 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161612 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161615 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161618 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 210 is not implemented yet, skipping
2019-03-05T03:38:13.161635 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161643 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161648 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161652 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161657 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161661 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 209 is not implemented yet, skipping
2019-03-05T03:38:13.161666 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161671 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161699 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161704 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161708 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161734 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 208 is not implemented yet, skipping
2019-03-05T03:38:13.161737 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161741 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161744 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161748 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.244727 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 153 is not implemented yet, skipping
2019-02-05T00:00:48.244733 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.244738 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 10 is not implemented yet, skipping
2019-02-05T00:00:48.244744 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 208 is not implemented yet, skipping
2019-02-05T00:00:48.244749 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 145 is not implemented yet, skipping
2019-02-05T00:00:48.244755 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245245 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-02-05T00:00:48.245256 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245262 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
hey, buddy:
Can I ask what vendor and model of your router or switch ? Mine is "H3C S6800-54QF", the version is "H3C Comware Software, Version 7.1.070, Release 2612P02", maybe the switch upload wrong messages when interact with openbmp server, I guess.
On Mon, Mar 4, 2019 at 9:52 PM Dong Zhao ***@***.***> wrote:
docker exec openbmp_aio tail -f /var/log/openbmpd.log
2019-02-05T00:00:48.244727 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 153 is not implemented yet, skipping
2019-02-05T00:00:48.244733 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.244738 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 10 is not implemented yet, skipping
2019-02-05T00:00:48.244744 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 208 is not implemented yet, skipping
2019-02-05T00:00:48.244749 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 145 is not implemented yet, skipping
2019-02-05T00:00:48.244755 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245245 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-02-05T00:00:48.245256 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-02-05T00:00:48.245262 | INFO | parseNlriData | 192.168.0.1: EVPN ROUTE TYPE 0 is not implemented yet, skipping
hey, buddy:
Can I ask what vendor and model of your router or switch ? Mine is "H3C
S6800-54QF", the version is "H3C Comware Software, Version 7.1.070, Release
2612P02", maybe the switch upload wrong messages when interact with openbmp
server, I guess.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<OpenBMP/obmp-docker#19 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APoRy34cLGiOEpxJIiT1imUmcKx2ZxUrks5vTgYwgaJpZM4aiTFs>
.
Run docker 'openbmp/ui', find 'AS View' in the left column.
I test this function, it works fine about the public as searching and the private as searching are not.
I think you should fill the right information about private as into openbmp database first, and try again.
And the asn table is "gen_whois_asn".
Activity
NetprogDong commentedon Mar 5, 2019
I have the same problem when running the aio docker, and the docker will stop in seconds since it starts.
NetprogDong commentedon Mar 5, 2019
the error output from /var/log/openbmpd.log like this:
2019-03-05T03:38:13.161599 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 211 is not implemented yet, skipping
2019-03-05T03:38:13.161602 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161605 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161609 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161612 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161615 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161618 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 210 is not implemented yet, skipping
2019-03-05T03:38:13.161635 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161643 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161648 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161652 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161657 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161661 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 209 is not implemented yet, skipping
2019-03-05T03:38:13.161666 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161671 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161699 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161704 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161708 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 33 is not implemented yet, skipping
2019-03-05T03:38:13.161734 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 208 is not implemented yet, skipping
2019-03-05T03:38:13.161737 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161741 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 5 is not implemented yet, skipping
2019-03-05T03:38:13.161744 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
2019-03-05T03:38:13.161748 | INFO | parseNlriData | 10.110.3.3: EVPN ROUTE TYPE 0 is not implemented yet, skipping
NetprogDong commentedon Mar 5, 2019
hey, buddy:
Can I ask what vendor and model of your router or switch ? Mine is "H3C S6800-54QF", the version is "H3C Comware Software, Version 7.1.070, Release 2612P02", maybe the switch upload wrong messages when interact with openbmp server, I guess.
mmihir82 commentedon Mar 5, 2019
NetprogDong commentedon Mar 5, 2019
Run docker 'openbmp/ui', find 'AS View' in the left column.
I test this function, it works fine about the public as searching and the private as searching are not.
I think you should fill the right information about private as into openbmp database first, and try again.
And the asn table is "gen_whois_asn".