Uploaded image for project: 'bgpcep'
  1. bgpcep
  2. BGPCEP-783

Peer-id affecting topology content

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Fluorine
    • Fluorine
    • BGP
    • None

      Overview: After BGPCEP-782: The peer now always is in rib under exabgp's router-id. However these routes are not visible in example-ipv6-topology nor example-ipv4-topology. On Oxygen, Nitrogen, Carbon this works as expected.

      Note: I tested this with patch BGPCEP-782 where topology is empty, and an hour older patch where example-ipv6-topology is filled(peer-id in rib is ipv6 local-address)

      Steps to reproduce, pretty much the same as BGPCEP-782

      • start latest fluorine odl
      • run in karaf
        feature:install odl-restconf odl-bgpcep-bgp odl-bgpcep-bgp-config-example
        
      • run script to configure internal peer with ::1 address
        ./conf_peer.py
        
      • start exabgp with single ipv6 route, router-id: 1.2.3.4 and local-address: ::1
        env exabgp.tcp.port=1790 exabgp --debug default.cfg
        
      • check ipv6-topology with
        ./get_ipv6_topology.sh
        

        (At this point topology should be filled with one ipv6 route)

      there is also script to get full rib to see the peer, and log from local test with DEBUG logs.

        1. conf_peer.py
          1 kB
        2. default.cfg
          0.3 kB
        3. get_full_rib.sh
          0.1 kB
        4. get_ipv6_topology.sh
          0.2 kB
        5. log_ipv6_debug.log
          22 kB

            cdgasparini Claudio David Gasparini
            tomas.markovic Tomas Markovic
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: