[BGPCEP-828] Odl doesn't advertise l3vpn route after recieving route-target argument Created: 19/Sep/18  Updated: 07/Nov/18  Resolved: 07/Nov/18

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

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 configure.py     File play.py     File send_route_from_play1.py     File send_route_from_play2.py     File start_play1.sh     File start_play2.sh    

 Description   

Overview:
Send l3vpn route from first ibgp through play.py.
Send route-target route with specific rt argument from previous route from second ibgp.
Expect l3vpn route on second ibgp.

Steps to reproduce:
1. Start odl with usual features:

feature:install odl-restconf odl-bgpcep-bgp odl-bgpcep-bgp-config-example

2. Configure 2 ibgp peers with 127.0.0.2 and 127.0.0.3 ips

./configure.py

3. Start play.py's

./start_play1.py
./start_play2.py

4. Send l3vpn route from first play, and than route-target route from second play

./send_route_from_play1.py
./send_route_from_play2.py

5. We should be able verify presence of l3vpn route on second ibgp (127.0.0.3) either in it's specific rib, or in play2.log there should be UPDATE message present.



 Comments   
Comment by Tomas Markovic [ 20/Sep/18 ]

Error in test concept

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