[NETVIRT-672] [l3vpn_ecmp] Data traffic from DC-GW to VM stops working if we change the bgpvpn update from one rd to multiple rds. Created: 16/May/17  Updated: 02/Apr/19  Resolved: 03/Jul/17

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Jaya Priyadarshini Assignee: Manu B
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File Bug_8466_fail_log.txt     Text File ovs-vsctl_show.txt    
External issue ID: 8466

 Description   

Steps to repro
====================
1)Do the basic vxlan configuration for one CSS.
2)Configure mpls over gre.Check it is configured properly.
3)Form bgp neigborship between Controller and DC-GW and check check bgp neighborship.
4)Configure one VM on CSS-1 using nova command, configure bgvpn update with one rd.Check whether it is advertised to DC-GW.
5) Ping this VM from DC-GW, ping is successful.
6)Configure multiple VMs on CSS-1 using nova command, configure bgvpn update with one rd. Check whether it is advertised to DC-GW.
7)Ping these VMs from DC-GW, ping is successful.
8)Configure vxlan tunnel for CSS-2 now and check tunnel is up,
9)Configure mpls over gre for this Check it is configured properly.
10)Configure one VM on CSS-2 using nova command,
11)Unconfigure bgpvpn with one rd and configure it with two rds for two CSS.
Perform ping for this VM , fails.
Perform ping for previously working VMs, that also fails.



 Comments   
Comment by Jaya Priyadarshini [ 16/May/17 ]

Attachment ovs-vsctl_show.txt has been added with description: ovs-vsctl show output

Comment by Jaya Priyadarshini [ 16/May/17 ]

Attachment Bug_8466_fail_log.txt has been added with description: Log for ping fail

Comment by Manu B [ 03/Jul/17 ]

Fix for the update of bgpvpn is already provided in this review.
https://git.opendaylight.org/gerrit/#/c/55726/

Please check and let us know if issue is still seen

Generated at Wed Feb 07 20:22:10 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.