[NETVIRT-1306] IPV6 subnet association to Router shoud Fail in Dual stack if IPv4 network already associated to Network Created: 11/Jun/18  Updated: 13/Jun/18  Resolved: 13/Jun/18

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

Type: Bug Priority: Medium
Reporter: RajaRajan Manickam Assignee: Karthikeyan Krishnan
Resolution: Won't Do Votes: 0
Labels: VPNV6
Remaining Estimate: 0 minutes
Time Spent: 1 day
Original Estimate: Not Specified

Priority: High

 Description   

IPV6 address not appearing in FIB when IPv6 subnet created and associated with existing IPv4 Network

  1. Create Network, Subnet(IPv4), Create Port and Boot VM.
  2. Create VPN
  3. Associate Network to VPN and check FIB entries observed -->PASS
  4. Create Subnet2(IPv6) in same network
  5. ** Create Router and Add S2 to Router à Openstack/ODL should not allow this scenario.
  6. Create Port and Boot VM.
  7. Check IPV6 Entries appearing in FIB.

ceebackup@cic-1:/root$ nova list
---------------------------------------------+------------------------------------------------------------------------------------

ID                                   Name     Status Task State Power State Networks                                            

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

5e24a52b-c60c-4055-813e-9474fd40c743 myhost11 ACTIVE -          Running     mynet1=2001:db8:1111:0:f816:3eff:fe4b:3d7c, 10.1.1.3
06e8df09-e3e2-493d-9ae1-b80301494ae5 myhost12 ACTIVE -          Running     mynet1=10.1.1.5, 2001:db8:1111:0:f816:3eff:fe9a:db25
ae7875a1-4c9b-4068-8d78-a731a8f427f6 myhost21 ACTIVE -          Running     mynet1=2001:db8:1111:0:f816:3eff:feba:6be3, 10.1.1.4
f84a874e-722b-4fe6-bbd2-37e08f7b1ca4 myhost22 ACTIVE -          Running     mynet1=2001:db8:1111:0:f816:3eff:fe10:aec3, 10.1.1.6

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

 

cli>display fib

   RD       Prefix                NextHop               Label    Origin
   -------------------------------------------------------------------
   100:1    10.1.1.4/32           192.168.115.114       103012   l
   100:1    10.1.1.0/24           192.168.115.114       103013   c
   100:1    10.1.1.3/32           192.168.115.113       103014   l
   100:1    10.10.1.20/32         192.168.115.56        786432   b
   100:1    10.1.1.5/32           192.168.115.113       103015   l
   100:1    10.1.1.6/32           192.168.115.114       103016   l

cli>

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

This is not a valid use-case.

 When a network is attached to a BGP-VPN, another subnet (Dual Stack Network Case) on that network cannot be attached to a router.

If you need L3 connectivity in this case, you will have to attach both the subnets to one router.

It is mandatory for all IPv6 subnets to be attached to the router.

Valid Single Stack Scenario for L3BPG-VPN:

==============================

Network > Subnet (IPv6 Address Family) > Neutron Router >L3BGP-VPN

 

Valid Dual Stack Network Scenario for L3BGP-VPN:

=====================================

Network > IPv4 Subnet, IPv6 Subnet -> Attach both the subnets to neutron router -> Associate L3BG-VPN to router.

 

 

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