[rhos-list] quantum network_vlan_ranges

[Robert Kukura]

On 07/23/2013 02:59 PM, Chen, Hao wrote:
> Thanks all for the help.
> 
> When configuring a Provider Network, the following error occurred. 
> 
> [root at cloud1 ~(keystone_admin)]# quantum router-interface-add 7f5823a5-5a41-4c00-affe-4062b54445f9 2a8743f4-fd25-4b9f-8c12-987e23a4cbdc
> Bad router request: Router already has a port on subnet 2a8743f4-fd25-4b9f-8c12-987e23a4cbdc
> 
> In log file:
> ...
> 2013-07-22 17:06:25    ERROR [quantum.api.v2.resource] add_router_interface failed
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/quantum/api/v2/resource.py", line 82, in resource
>     result = method(request=request, **args)
>   File "/usr/lib/python2.6/site-packages/quantum/api/v2/base.py", line 147, in _handle_action
>     body, **kwargs)
>   File "/usr/lib/python2.6/site-packages/quantum/db/l3_db.py", line 363, in add_router_interface
>     subnet['cidr'])
>   File "/usr/lib/python2.6/site-packages/quantum/db/l3_db.py", line 302, in _check_for_dup_router_subnet
>     raise q_exc.BadRequest(resource='router', msg=msg)
> BadRequest: Bad router request: Router already has a port on subnet 2a8743f4-fd25-4b9f-8c12-987e23a4cbdc
> ...
> 
> Tried to use "quantum router-interface-delete ..." then the response was "... has no interface on subnet ..." Other than this error, everything else looked fine. Any suggestions?

Is it possible that you've already added this subnet's network as a
gateway with "quantum router-gateway-set ..."? The same network/subnet
cannot be connected to a router as both a gateway and as an interface.

-Bob

> 
> Thanks,
> Hao
> 
> -----Original Message-----
> From: Robert Kukura [mailto:rkukura at redhat.com] 
> Sent: July 22, 2013 11:47
> To: Chen, Hao
> Cc: rhos-list at redhat.com
> Subject: Re: [rhos-list] quantum network_vlan_ranges
> 
> On 07/22/2013 02:14 PM, Chen, Hao wrote:
>> Hi,
>>  
>> I am working on "3. Setting the Plug-in" in 9.4. Configuring the 
>> Networking Service.
>>  
>> If flat or vlan networking is chosen, my question is how to set the 
>> value of the network_vlan_ranges configuration key.
>> Following the example "physnet1:1000:2999, physnet2:3000:3999", 
>> "physnet1/2" is the name of the physical network. Does the name of the 
>> physical network have to be an existing physical network name?
> 
> Hi Hao,
> 
> The physical network names don't need to match anything existing outside quantum. They just need to match across the three places they are used within quantum:
> 
> 1) network_vlan_ranges in the openvswitch or linuxbridge plugin configuration
> 2) bridge_mappings in the openvswitch agent configuration or physical_interface_mappings in the linuxbridge agent configuration
> 3) the provider:physical_network attribute of the network resource in the API
> 
> Each distinct value names a distinct physical network. So if you are using VLANs, each is a different VLAN trunk - i.e. VLAN 1000 on physnet1 is a different isolated L2 network than VLAN 1000 on physnet2. They'd each typically correspond to a different network switch.
> 
> On the compute and network nodes, each physical network is mapped to a different physical network interface and bridge.
> 
>> I am using 10.2.0.0/24 and 10.3.0.0/24, how do I set these values:
>> NAME:START:END?
> 
> The subnets are not directly related to the physical networks. You could use these subnets on the same or different physical networks (different VLANs of the same physical network most likely).
> 
> The NAME is just an identifier matched between the three places physical_network names are used. The NAME must be listed in network_vlan_ranges (1) for it to be used in the L2 agent's mappings (2) or in the provider API (3).
> 
> If you include :START:END after NAME, and tenant_network_type = vlan, then the specified set of VLANs on that physical_network are added to the pool of VLANs to be allocated as tenant networks.
> 
> Hope this helps,
> 
> -Bob
> 
> 
>>  
>> Thanks in  advance,
>> Hao
>>  
>>  
>>
>>
>> _______________________________________________
>> rhos-list mailing list
>> rhos-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rhos-list
>>
>