[NETVIRT-1026] L3VPN traffic is not working after recreating the VM Created: 23/Nov/17  Updated: 06/Apr/18  Resolved: 06/Apr/18

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

Type: Bug Priority: Highest
Reporter: Madhusmita Pany Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive PING_TR_LOG.zip    

 Description   

Hi,

L3VPN traffic is not working after nova deletion and recreation of VMs across L3VPN.

ODL build used : https://nexus.opendaylight.org/content/repositories/autorelease-2028/org/opendaylight/integration/karaf/0.7.1/karaf-0.7.1.zip
Openstack = stable/newton

Followed the below steps :
1. Created network NET1,NET2 and brought ip 4 VNFs from each network.
VM11 VM12 VM21 VM22 - in DPN1
VM13 VM14 VM23 VM24 - in DPN2
2. Created router RTR1 [added Interface NET1, NET2 to RTR1]
3. Created L3VPN from CSC with L3VNI ID and RD [100:2], RTs
4. BGP neighbourship is established between CSC and DCGW
5. Associated RTR1,NET1,NET2 to L3VPN. - Association is successful
6. CSC fib is populated with all the VMs and subnet routes
7. Non-stop ping is working between the VMs
8. Vms are deleted one by one. VM is deleted from the CSC. FIB is removed for that VM
9. After Nova delete , recreated the same VMs one by one
10. Topology created and Tunnel between CSS is UP, Open Flow channel is established between VSwitches and CSC
11. 8 VMs are up with IP, VMs are added to routers and they can communicate within router
12. But now VMs are not reachable between each other :
VM11[DPN1]<-> VM23[DPN2] -> is not pinging
VM12 [DPN1] <-> VM24 [DPN2] -> is not pinging

VMs with same networks are reachable across the DPNs
L3VPN is working fine.

I have attached all the dump flows log of two DPNs, karaf log,vpn logs, restcall log with this mail.
Please check the logs and let me know what could be the issue.

Thanks,
Madhusmita
.


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