[NETVIRT-1326] Nova VM is not getting IPv6 subport IP Created: 21/Jun/18  Updated: 17/Aug/18  Resolved: 17/Aug/18

Status: Resolved
Project: netvirt
Component/s: dhcpservice, ipv6service, neutronvpn
Affects Version/s: None
Fix Version/s: Oxygen-SR3, Fluorine

Type: Bug Priority: High
Reporter: Rajesh Babu Assignee: mahesh loni
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Priority: High

 Description   

VM is not getting IPv6 subport IP with the following nic configuration,

ens5.1000 Link encap:Ethernet HWaddr fa:16:3e:5c:5b:52
inet addr:5.1.1.3 Bcast:5.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe5c:5b52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10984 (10.9 KB) TX bytes:1818 (1.8 KB)

2. Configuration data
2.1. HW Configuration details
EBS, HP or DELL:
Number of subracks
Number of blades:
EMC (Yes or No):
Switches used (X670V, X770 or BD):
2.2. SW Configuration details
No of DPNs : 9 + 3
No of CICs : 3
No VMs : 144
No of Networks : 216
No of L3VPN : 72



 Comments   
Comment by Karthikeyan Krishnan [ 21/Jun/18 ]

The reported issue is already known(NETVIRT-1245) and fix is already available in oxygen SR3 release.

 Please check below gerrit fix is existing in your tested build.
 Stable/Oxygen: https://git.opendaylight.org/gerrit/#/c/71847/

Comment by Rajesh Babu [ 13/Aug/18 ]

The issue is still observed

Comment by Karthikeyan Krishnan [ 17/Aug/18 ]

Please attach all the IPv6 subnets including trunk port subnets and subport subnets to the neutron router. Since automatic IPv6 assignment is dependent on router advertisement (RA) packet which is sending from ODL controller on behalf of neutron router.

This configuration is valid for IPv6 subnets RA mode is SLAAC, DHCPv6 stateless and DHCPv6 statefull also.

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