[NETVIRT-1143] Data path with IPv6 not working and wrong group flow configured Created: 08/Mar/18  Updated: 14/Jun/18  Resolved: 04/Apr/18

Status: Verified
Project: netvirt
Component/s: General
Affects Version/s: Oxygen
Fix Version/s: Oxygen

Type: Bug Priority: Highest
Reporter: RajaRajan Manickam Assignee: nithi thomas
Resolution: Done Votes: 0
Labels: VPNV6
Remaining Estimate: 0 minutes
Time Spent: 4 days
Original Estimate: Not Specified

Attachments: HTML File dump_flows     HTML File dump_groups     Text File jira-1143.txt     Text File karaf.log     Text File open-flows-1143.txt    
Priority: High

 Description   

Data path with IPv6 not working and wrong group flow configured

  1. Create N1 with Subnet1I(IPv4)Subnet2(IPv6)
  2. Create Router and add Subnet2(ipv6) to it.
  3. Boot VM and check data path. --> PASS
  4. Create N2 with Subnet3(IPv4) and Subnet4(IPv6)
  5. Associate IPv6 Subnet4(IPV6)to Router and check data path across all VMs.

 Comments   
Comment by Karthikeyan Krishnan [ 22/Mar/18 ]

As per the steps you mentioned in the JIRA ticket, I have followed the same steps in my local development environment and observed that IPv6 routing is working properly without failing.

Used ODL-Oxygen RC3 Build:
https://nexus.opendaylight.org/content/repositories/autorelease-2114/org/opendaylight/integration/karaf/0.8.0/karaf-0.8.0.zip

Tested data plane traffic for IPv6 Routing across networks:

stack@osc-pike-ubuntu16:/opt/stack/devstack$ openstack server list
------------------------------------------------------------------------------------------------------------------------------------+

ID Name Status Networks Image Flavor

------------------------------------------------------------------------------------------------------------------------------------+

90874c50-830a-4556-8043-aeaf749aebe5 VM10 ACTIVE network2=20.0.0.11, 2001:1111:0:9:f816:3eff:fe2e:319e cirros-0.3.5-x86_64-disk m1.tiny
15ffa2b3-e4cb-439e-b0c6-3529a77a25f9 VM2 ACTIVE network1=2001:db8:0:2:f816:3eff:fe42:fc2, 10.0.0.14 cirros-0.3.5-x86_64-disk m1.tiny
a662e406-4a5c-4977-bb0d-9ace8ed835fc VM1 ACTIVE network1=2001:db8:0:2:f816:3eff:fe02:b153, 10.0.0.7 cirros-0.3.5-x86_64-disk m1.tiny

------------------------------------------------------------------------------------------------------------------------------------+

$ ifconfig
eth0 Link encap:Ethernet HWaddr FA:16:3E:2E:31:9E

  • inet addr:20.0.0.11 Bcast:20.0.0.255 Mask:255.255.255.0
    inet6 addr: 2001:1111:0:9:f816:3eff:fe2e:319e/64 Scope:Global
    inet6 addr: fe80::f816:3eff:fe2e:319e/64 Scope:Link*
    UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
    RX packets:88 errors:0 dropped:7 overruns:0 frame:0
    TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:9634 (9.4 KiB) TX bytes:12596 (12.3 KiB)

$ ping6 2001:db8:0:2:f816:3eff:fe02:b153
PING 2001:db8:0:2:f816:3eff:fe02:b153 (2001:db8:0:2:f816:3eff:fe02:b153): 56 data bytes
64 bytes from 2001:db8:0:2:f816:3eff:fe02:b153: seq=0 ttl=64 time=101.925 ms
64 bytes from 2001:db8:0:2:f816:3eff:fe02:b153: seq=1 ttl=64 time=2.741 ms

$ ping6 2001:db8:0:2:f816:3eff:fe42:fc2
PING 2001:db8:0:2:f816:3eff:fe42:fc2 (2001:db8:0:2:f816:3eff:fe42:fc2): 56 data bytes
64 bytes from 2001:db8:0:2:f816:3eff:fe42:fc2: seq=0 ttl=64 time=2.681 ms
64 bytes from 2001:db8:0:2:f816:3eff:fe42:fc2: seq=1 ttl=64 time=1.561 ms

Comment by Karthikeyan Krishnan [ 22/Mar/18 ]

Reported issue is not reproducible with Stable/Oxygen RC3 build

Used ODL-Oxygen RC3 Build for validation:
https://nexus.opendaylight.org/content/repositories/autorelease-2114/org/opendaylight/integration/karaf/0.8.0/karaf-0.8.0.zip

As per the confirmation from the bug submitter issue is not re-producible with Stable/Oxygen RC3 build. Hence moving this issue to Fixed state.

Comment by RajaRajan Manickam [ 28/Mar/18 ]

Hi,

 

 This issue is reproducible. Data path with different subnet not working.

 

Thanks,

RajaRajan

Comment by nithi thomas [ 03/Apr/18 ]

Hi RajaRajan,

   I have tested in the latest oxygen-ODL build(karaf0.8.1 snapshot), data-path with different subnet is working fine.

I have followed the steps as mentioned in jira. I have attached the logs for referrence.

Regards

Nithi

 

 

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