Ask Your Question

How to setup neutron with provider network?

asked 2014-03-26 20:48:02 -0500

Yang Yu gravatar image

updated 2014-03-26 20:54:47 -0500

Hi All,

I had try to setup a environment of neutron provider network. I follow some instructions as belows. ( (

There are three nodes in my environment. cloud-t1 is the controller node and cloud-t2/cloud-t3 is the compute node. I use the ml2 plugin with OVS and VXLAN. The multi-host model used by L3 agent.

There are three networks. --> external --> managment --> internal

cloud-t1 (
cloud-t2 (
cloud-t3 (

Here is my configuration file: (

But I failed to get it work. I need your help.

  1. There are two error log occured when I try to create network.

The command:

neutron net-create ext-net --shared --provider:network_type=flat --provider:physical_network=phy-129   
neutron subnet-create ext-net --name=ext-129 --gateway= --enable_dhcp=True --allocation-pool start=,end=

The error log(neutron-server.log):

2014-03-26 20:12:33.914 17360 ERROR neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [-] **No DHCP agents are associated with network 'f1ae9157-a9e6-4c96-9dd3-2da0bb188e8c'.** Unable to send notification for 'network_create_end' with payload: {'network': {'status': 'ACTIVE', 'subnets': [], 'name': u'ext-net', 'provider:physical_network': u'phy-129', 'admin_state_up': True, 'tenant_id': u'a6d3748a7a474e3d96d98bfbea6e8273', 'provider:network_type': u'flat', 'shared': True, 'id': 'f1ae9157-a9e6-4c96-9dd3-2da0bb188e8c', 'provider:segmentation_id': None}}

2014-03-26 20:12:34.279 17360 ERROR neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [-] **No DHCP agents are associated with network 'f1ae9157-a9e6-4c96-9dd3-2da0bb188e8c'**. Unable to send notification for 'subnet_create_end' with payload: {'subnet': {'name': u'ext-129', 'enable_dhcp': True, 'network_id': u'f1ae9157-a9e6-4c96-9dd3-2da0bb188e8c', 'tenant_id': u'a6d3748a7a474e3d96d98bfbea6e8273', 'dns_nameservers': [], 'allocation_pools': [{'start': u'', 'end': u''}], 'host_routes': [], 'ip_version': 4, 'gateway_ip': u'', 'cidr': u'', 'id': '7f82c313-22a0-46da-8ecf-9e7c9c3cf60b

I check the agent list, the status of agent seems all right.

root@cloud-t1:~/alex_scripts# neutron agent-list

| id                                   | agent_type         | host         | alive | admin_state_up |  
| 2884d489-9e6c-446c-a680-877a17e14101 | DHCP agent         | | :-)   | True           |  
| 8aa2dab5-ece2-4722-a3e4-cd3691f712f6 | L3 agent           | | :-)   | True           |  
| 8ef1fdc8-ef45-447e-85d5-45a601f02c89 | Open vSwitch agent | | :-)   | True           |  
| ba2992ea-9184-4309-9d8b-02c98e5386ac | L3 agent           | | :-)   | True           |  
| e420aec4-5b47-470a-8d73-a82f65dc2c3d | Open vSwitch agent | | :-)   | True           |  
| ecf28e47-6569-4c84-ac51-c772bd0c06fe | DHCP agent         | | :-)   | True           |  
  1. After I created an instancne and attatached it to ext-net, the instance can't get an ip from dhcp and access the gateway. An error log also occured.

Error Log:

2014-03-26 20:15:00.476 17360 WARNING neutron.plugins.ml2.managers [-] Failed to bind port da0b40c4-7251-4e97-a59a-7f5d524c7221 on host cloud-t2

2014-03-26 20:15:02.314 17360 WARNING neutron.plugins.ml2.rpc [-] Device da0b40c4-7251-4e97-a59a-7f5d524c7221 requested by agent ovsaac14b4ea64f on network f1ae9157-a9e6-4c96-9dd3-2da0bb188e8c not bound, vif_type: binding_failed

I found ... (more)

edit retag flag offensive close merge delete



The first two warnings (About no DHCP agent for this network during the creation of the network) are fine. It only means that the network wasn't scheduled to a DHCP agent. It's scheduled during the first port creation on that network.

As for the port binding fail - That's the ticket. There must be something wrong in the configuration files, as the port of the VM isn't bound successfully to the L2 agent. The VLAN tag of 4095 on the 'qvo' device (Which is eventually connected to the VM's tap device) is an error-state VLAN.

You can take a look at the OVS agent log to hopefully find the root cause of the issue. My bet is on a configuration issue with the plugin.ini in either the controller node or the compute node, or both.

Assaf Muller gravatar imageAssaf Muller ( 2014-04-25 08:34:25 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-09-30 16:38:11 -0500

Seryio.Gonzalez gravatar image


Any luck?

I am running the very same issue.


edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-03-26 20:48:02 -0500

Seen: 1,955 times

Last updated: Mar 26 '14