[Openstack-operators] Neutron Documentation

Liu, Edward (NSN - CN/Cheng Du) edward.liu at nsn.com
Wed Jan 15 05:44:54 UTC 2014


Hi,

Does it mean the "SUBNET" parameter in interface-add command is not referring to the one which created previous for external network? 

Is it the "internal" subnet in the real deployment? Should we create the internal net and subnet accordingly also by commands "net-create and subnet-create", and thus using the internal subnet identifier returned in interface-add command ?  

Thanks
Br,Edward

-----Original Message-----
From: ext Steve Gordon [mailto:sgordon at redhat.com] 
Sent: Wednesday, January 15, 2014 11:06 AM
To: Alvise Dorigo
Cc: openstack-operators at lists.openstack.org; Summer Long
Subject: Re: [Openstack-operators] Neutron Documentation

----- Original Message -----
> From: "Alvise Dorigo" <alvise.dorigo at pd.infn.it>

> > 
> > Red Hat Enterprise Linux OpenStack Platform 3 is Grizzly based (hence the
> > documentation for that version still correctly refers to Quantum), 4 is
> > Havana based. Both are fully (and concurrently) supported.
> 
> Hi Steve, Sankarshan,
> 
> I'm following the guide "4" for Havana. For what concern Neutron, everything
> works smooth until the section 13.6 "Configuring an external provider
> network". I execute these steps as described there:
> 
> neutron net-create EXTERNAL_NAME --router:external True
> --provider:network_type TYPE --provider:physical_network PHYSICAL_NAME
> --provider:segmentation_id VLAN_TAG
> (OK)
> 
> neutron subnet-create --gateway GATEWAY --allocation-pool
> start=IP_RANGE_START,end=IP_RANGE_END --disable-dhcp EXTERNAL_NAME
> EXTERNAL_CIDR
> (OK)
> 
> neutron router-create NAME
> (OK)
> 
> neutron router-gateway-set ROUTER NETWORK
> (OK)
> 
> (of course I replaced the labels with the proper names, IPs, ID, etc...)
> 
> The last command of section 13.6 fails:
> 
> neutron router-interface-add myRouter dc8ea9c9-c737-4ab3-8abb-f62284b078f8
> 400-{u'NeutronError': {u'message': u'Bad router request: Router already has a
> port on subnet dc8ea9c9-c737-4ab3-8abb-f62284b078f8', u'type':
> u'BadRequest', u'detail': u''}}
> 
> 
> This is my net and subnet list:
> 
> bash-4.1$ neutron net-list
> +--------------------------------------+---------+-------------------------------------------------------+
> | id                                   | name    | subnets
> | |
> +--------------------------------------+---------+-------------------------------------------------------+
> | 6f0b45e1-143f-4c1c-acb4-414210e9dbb9 | esterna |
> | dc8ea9c9-c737-4ab3-8abb-f62284b078f8 192.168.120.0/24 |
> +--------------------------------------+---------+-------------------------------------------------------+
> bash-4.1$ neutron subnet-list
> +--------------------------------------+----------------+------------------+--------------------------------------------------------+
> | id                                   | name           | cidr             |
> | allocation_pools                                       |
> +--------------------------------------+----------------+------------------+--------------------------------------------------------+
> | dc8ea9c9-c737-4ab3-8abb-f62284b078f8 | subnet_externa | 192.168.120.0/24 |
> | {"start": "192.168.120.100", "end": "192.168.120.150"} |
> +--------------------------------------+----------------+------------------+--------------------------------------------------------+
> 
> I've never execute an interface-add for myRouter before, but it says that
> "Router already has a port".
> 
> What am I doing wrong ?
> 
> thanks,

Hi again,

Apologies for the delayed response - I believe the issue is that when you issue the "neutron router-gateway-set" command you connect the router to the external network and, implicitly, the subnet associated with it. 

It's then expected that when you issue the "neutron router-interface-add" command in 13.6 you are adding *additional* private subnets to the router (not the external subnet) - though admittedly this isn't immediately obvious.

Thanks,

Steve

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



More information about the OpenStack-operators mailing list