<p dir="ltr">Why do you have two physical bridged networks on your compute node?</p>
<div class="gmail_quote">El 14/12/2014 22:51, "Gonzalo Aguilar Delgado" <<a href="mailto:gaguilar@aguilardelgado.com">gaguilar@aguilardelgado.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi Adrián, </div><div><br></div><div>In my case I learnt the bad way also. And now I purchased some Intel pci cards and add it to servers that have not much reliable cards. </div><div><br></div><div>I post my bridge config:</div><div><br></div><div> Bridge "br0"</div><div> Port "phy-br0"</div><div> Interface "phy-br0"</div><div> Port "br0"</div><div> Interface "br0"</div><div> type: internal</div><div> Bridge br-int</div><div> fail_mode: secure</div><div> Port "qvob27f1522-73"</div><div> tag: 1</div><div> Interface "qvob27f1522-73"</div><div> Port int-br-ex</div><div> Interface int-br-ex</div><div> Port br-int</div><div> Interface br-int</div><div> type: internal</div><div> Port "qvo9da5cf98-f1"</div><div> tag: 1</div><div> Interface "qvo9da5cf98-f1"</div><div> Port "int-br0"</div><div> Interface "int-br0"</div><div> Port "qvo377f7953-d2"</div><div> tag: 1</div><div> Interface "qvo377f7953-d2"</div><div> Port "eth0"</div><div> Interface "eth0"</div><div> Port "qvod1b2e6dc-7f"</div><div> tag: 1</div><div> Interface "qvod1b2e6dc-7f"</div><div> Bridge br-ex</div><div> Port br-ex</div><div> Interface br-ex</div><div> type: internal</div><div> Port phy-br-ex</div><div> Interface phy-br-ex</div><div> ovs_version: "2.0.2"</div><div><br></div><br>El dom, 14 de dic 2014 a las 10:41 , Adrián Norte Fernández <<a href="mailto:adrian@bashlines.com" target="_blank">adrian@bashlines.com</a>> escribió:<br>
<blockquote type="cite"><p dir="ltr">I had a similar problem because a cheap realtek card.</p>
<p dir="ltr">Do you have logs? Can you post the result of ovs-vsctl show command on compute node?</p>
<div class="gmail_quote">El 14/12/2014 22:36, "Gonzalo Aguilar Delgado" <<a href="mailto:gaguilar@aguilardelgado.com" target="_blank">gaguilar@aguilardelgado.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Adrian, <div><br></div><div>It's ubuntu trusty and network cards are intel, broadcom and marvell</div><div><br></div><div>Marvell Technology Group Ltd. 88SE912x </div><div>Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet</div><div>Intel Corporation 82574L Gigabit Network</div><div><br></div><div>But I don't think it's the problem. It seems more a problem on config or maybe a bug, since it doesn't fail on any other circumstances. And I'm running ceph! It needs reliable network. </div><div><br></div><div>What are you looking at?</div><div><br><br>El dom, 14 de dic 2014 a las 9:11 , Adrián Norte Fernández <<a href="mailto:adrian@bashlines.com" target="_blank">adrian@bashlines.com</a>> escribió:<br>
<blockquote type="cite"><p dir="ltr">Which SO and network cards are you using?</p>
<div class="gmail_quote">El 14/12/2014 19:35, "Gonzalo Aguilar Delgado" <<a href="mailto:gaguilar@aguilardelgado.com" target="_blank">gaguilar@aguilardelgado.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all, <div><br></div><div>Question is. Why I have to restart neutron-plugin-openvswitch-agent to recover networking from new machines?</div><div><br></div><div><br></div><div>I found a problem creating machines in a new node I've built. And realized that this happens on all my nodes of current version. </div><div><br></div><div>neutron 2.3.4</div><div>nova 2.17.0</div><div><br></div><div>My logs shows that neutron assign vlan 2 for the new machine and this causes the machine to not have connectivity. </div><div><br></div><div><div>---------------------------------------</div><div>2014-12-14 17:57:07.321 12501 INFO neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Assigning 2 as local vlan for net-id=727b0415-f066-40d9-8147-183e07dd7b23</div><div>20</div></div><div>---------------------------------------</div><div><br></div><div><br></div><div>If I shut down the machine and restart neutron plugin agent for ovs:</div><div><br></div><div>#> restart neutron-plugin-openvswitch-agent</div><div><br></div><div><br></div><div>---------------------------------------</div><div> ... assigning 1 as local vlan for net-id=727b0415-f066-40d9-8147-183e07dd7b23</div><div><br></div><div>---------------------------------------</div><div><br></div><div><br></div><div>And the machine recovers connectivity. </div><div><br></div><div>In the even of faillure (after creating it):</div><div><br></div><div>If I start the machine without ip and set it manually I can try to ping it. It says it's not reachable but after restating the plugin automatically recovers connectivity. So no restart or further configuration is made. </div><div><br></div><div><br></div><div>Maybe I have something wrong configured but it seems like a bug.</div><div><br></div><div><br></div><div>Can someone point me to the right place?</div><div><br></div><br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div>
</blockquote></div></blockquote></div>
</blockquote></blockquote></div>