Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EVPN error not parsing #19

Open
mmihir82 opened this issue Feb 5, 2019 · 5 comments
Open

EVPN error not parsing #19

mmihir82 opened this issue Feb 5, 2019 · 5 comments

Comments

@mmihir82
Copy link

mmihir82 commented Feb 5, 2019

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
@NetprogDong
Copy link

I have the same problem when running the aio docker, and the docker will stop in seconds since it starts.

@NetprogDong
Copy link

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
Copy link

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.

@mmihir82
Copy link
Author

mmihir82 commented Mar 5, 2019 via email

@NetprogDong
Copy link

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants