Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Problem running multiple L3 instances

Hello,

I've got a setup where two different external networks are presented to openstack instances. Since the external networks are on different interfaces and have different purposes, I've set up two different L3 agents, each configured to handle a specific external network following these directions: http://docs.openstack.org/admin-guide-cloud/content/adv_cfg_l3_agent_multi_floatip.html

With both agents running I can create routers (the namespaces do show correctly, including ip address assignment), but whenever I add a port to an internal subnet I get the following error on neutron-server.log:

2014-08-19 11:25:16.362 11934 WARNING neutron.plugins.ml2.managers [req-28d1ad31-8e08-4069-8804-98291964fb35 None] Failed to bind port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on host sonic-agent2

2014-08-19 11:25:16.366 11934 WARNING neutron.plugins.ml2.plugin [req-28d1ad31-8e08-4069-8804-98291964fb35 None] In _notify_port_updated(), no bound segment for port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on network cab446c7-d29f-462f-8a9d-e48604efc02c

2014-08-19 11:25:19.341 11934 WARNING neutron.plugins.ml2.rpc [req-8e138bb7-74fa-49d1-93a1-db1c72533a8a None] Device 222d22d0-e4c6-4af4-a9e1-94be80d18213 requested by agent ovsc81f66b95137 on network cab446c7-d29f-462f-8a9d-e48604efc02c not bound, vif_type: binding_failed

The configuration files for the agents are:

http://pastebin.com/0t6sQYPW - agent 1

http://pastebin.com/kHurF8FV - agent 2

My neutron.conf looks like this: http://pastebin.com/5Yinmfnz

Problem running multiple L3 instances

Hello,

I've got a setup where two different external networks are presented to openstack instances. Since the external networks are on different interfaces and have different purposes, I've set up two different L3 agents, each configured to handle a specific external network following these directions: http://docs.openstack.org/admin-guide-cloud/content/adv_cfg_l3_agent_multi_floatip.html

With both agents running I can create routers (the namespaces do show correctly, including ip address assignment), but whenever I add a port to an internal subnet I get the following error on neutron-server.log:

2014-08-19 11:25:16.362 11934 WARNING neutron.plugins.ml2.managers [req-28d1ad31-8e08-4069-8804-98291964fb35 None] Failed to bind port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on host sonic-agent2

2014-08-19 11:25:16.366 11934 WARNING neutron.plugins.ml2.plugin [req-28d1ad31-8e08-4069-8804-98291964fb35 None] In _notify_port_updated(), no bound segment for port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on network cab446c7-d29f-462f-8a9d-e48604efc02c

2014-08-19 11:25:19.341 11934 WARNING neutron.plugins.ml2.rpc [req-8e138bb7-74fa-49d1-93a1-db1c72533a8a None] Device 222d22d0-e4c6-4af4-a9e1-94be80d18213 requested by agent ovsc81f66b95137 on network cab446c7-d29f-462f-8a9d-e48604efc02c not bound, vif_type: binding_failed

The result is that instances inside the networks cannot reach the router (nor can I ping instances from inside the router namespace). The router's public address, however, works just fine.

The configuration files for the agents are:

http://pastebin.com/0t6sQYPW - agent 1

http://pastebin.com/kHurF8FV - agent 2

My neutron.conf looks like this: http://pastebin.com/5Yinmfnz

L2 agent plugin settings (ml2 using GRE): http://pastebin.com/mBFPbSEb

Problem running multiple L3 instances

Hello,

I've got a setup where two different external networks are presented to openstack instances. Since the external networks are on different interfaces and have different purposes, I've set up two different L3 agents, each configured to handle a specific external network following these directions: http://docs.openstack.org/admin-guide-cloud/content/adv_cfg_l3_agent_multi_floatip.html

With both agents running I can create routers (the namespaces do show correctly, including ip address assignment), but whenever I add a port to an internal subnet I get the following error on neutron-server.log:

2014-08-19 11:25:16.362 11934 WARNING neutron.plugins.ml2.managers [req-28d1ad31-8e08-4069-8804-98291964fb35 None] Failed to bind port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on host sonic-agent2

2014-08-19 11:25:16.366 11934 WARNING neutron.plugins.ml2.plugin [req-28d1ad31-8e08-4069-8804-98291964fb35 None] In _notify_port_updated(), no bound segment for port 222d22d0-e4c6-4af4-a9e1-94be80d18213 on network cab446c7-d29f-462f-8a9d-e48604efc02c

2014-08-19 11:25:19.341 11934 WARNING neutron.plugins.ml2.rpc [req-8e138bb7-74fa-49d1-93a1-db1c72533a8a None] Device 222d22d0-e4c6-4af4-a9e1-94be80d18213 requested by agent ovsc81f66b95137 on network cab446c7-d29f-462f-8a9d-e48604efc02c not bound, vif_type: binding_failed

The result is that instances inside the networks cannot reach the router (nor can I ping instances from inside the router namespace). The router's public address, however, works just fine.

The configuration files for the agents are:

http://pastebin.com/0t6sQYPW - agent 1

http://pastebin.com/kHurF8FV - agent 2

My neutron.conf looks like this: http://pastebin.com/5Yinmfnz

L2 agent plugin settings (ml2 using GRE): http://pastebin.com/mBFPbSEb

UPDATE: I have given up on the "host" parameter on the L3 agents. With this I do not have port binding errors but the agents occasionally stop responding until they are restarted.