Skip to content

EVPN error not parsing #19

Open
Open

Description

@mmihir82

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

Activity

  1. NetprogDong commented on Mar 5, 2019

    @NetprogDong

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

  2. NetprogDong commented on Mar 5, 2019

    @NetprogDong

    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

  3. NetprogDong commented on Mar 5, 2019

    @NetprogDong

    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.

  4. mmihir82 commented on Mar 5, 2019

    @mmihir82
    Author
  5. NetprogDong commented on Mar 5, 2019

    @NetprogDong

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions