[BGPCEP-783] Peer-id affecting topology content Created: 04/Apr/18  Updated: 12/Jul/18  Resolved: 13/Apr/18

Status: Verified
Project: bgpcep
Component/s: BGP
Affects Version/s: Fluorine
Fix Version/s: Fluorine

Type: Bug Priority: Medium
Reporter: Tomas Markovic Assignee: Claudio David Gasparini
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File conf_peer.py     File default.cfg     File get_full_rib.sh     File get_ipv6_topology.sh     File log_ipv6_debug.log    

 Description   

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.



 Comments   
Comment by Tomas Markovic [ 13/Apr/18 ]

it's passing now, which I didn't even notice at first between all those new failures

 https://jenkins.opendaylight.org/releng/user/cdgasparini/my-views/view/bgpcep-fluorine/job/bgpcep-csit-1node-userfeatures-all-fluorine/47/

Generated at Wed Feb 07 19:14:06 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.