<div dir="ltr"><div>For more details on this, here's the relevant text from the openvswitch FAQ:<br></div><div><div><br></div><div><<a href="http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD">http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD</a>><br>
</div><div><br></div><div><div>Q: I created a bridge and added my Ethernet port to it, using commands</div><div> like these:</div><div><br></div><div> ovs-vsctl add-br br0</div><div> ovs-vsctl add-port br0 eth0</div>
<div><br></div><div> and as soon as I ran the "add-port" command I lost all connectivity</div><div> through eth0. Help!</div><div><br></div><div>A: A physical Ethernet device that is part of an Open vSwitch bridge</div>
<div> should not have an IP address. If one does, then that IP address</div><div> will not be fully functional.</div><div><br></div><div> You can restore functionality by moving the IP address to an Open</div><div>
vSwitch "internal" device, such as the network device named after</div><div> the bridge itself. For example, assuming that eth0's IP address is</div><div> 192.168.128.5, you could run the commands below to fix up the</div>
<div> situation:</div><div><br></div><div> ifconfig eth0 0.0.0.0</div><div> ifconfig br0 192.168.128.5</div><div><br></div><div> (If your only connection to the machine running OVS is through the</div><div>
IP address in question, then you would want to run all of these</div><div> commands on a single command line, or put them into a script.) If</div><div> there were any additional routes assigned to eth0, then you would</div>
<div> also want to use commands to adjust these routes to go through br0.</div><div><br></div><div> If you use DHCP to obtain an IP address, then you should kill the</div><div> DHCP client that was listening on the physical Ethernet interface</div>
<div> (e.g. eth0) and start one listening on the internal interface</div><div> (e.g. br0). You might still need to manually clear the IP address</div><div> from the physical interface (e.g. with "ifconfig eth0 0.0.0.0").</div>
<div><br></div><div> There is no compelling reason why Open vSwitch must work this way.</div><div> However, this is the way that the Linux kernel bridge module has</div><div> always worked, so it's a model that those accustomed to Linux</div>
<div> bridging are already used to. Also, the model that most people</div><div> expect is not implementable without kernel changes on all the</div><div> versions of Linux that Open vSwitch supports.</div><div><br></div>
<div> By the way, this issue is not specific to physical Ethernet</div><div> devices. It applies to all network devices except Open vswitch</div><div> "internal" devices.</div><div><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Jan 2, 2014 at 9:45 AM, Narayan Desai <span dir="ltr"><<a href="mailto:narayan.desai@gmail.com" target="_blank">narayan.desai@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">I'm guessing that the installation instructions assume that you have different ethernet interfaces for the host and guests. <div><br></div><div>If you want the host to use the same interface that is in use as a bridge, you'll need to add a virtual interface to the bridge that has the host's IP. FWIW, this isn't an openstack issue; it is common to OVS and linux bridging, with even without a hypervisor in the mix.</div>
<div> -nld</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Thu, Jan 2, 2014 at 8:24 AM, Alvise Dorigo <span dir="ltr"><<a href="mailto:alvise.dorigo@pd.infn.it" target="_blank">alvise.dorigo@pd.infn.it</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div style="word-wrap:break-word">
Hi,<div>I'm configuring Neutron on a network node (a virtual machine) having two NICs:</div>
<div><br></div><div>eth0: 192.168.120.13</div><div>eth1: 10.0.0.13</div><div><br></div><div>I've followed the official Openstack guide:</div><div><br></div><div><a href="http://docs.openstack.org/havana/install-guide/install/yum/content/install-neutron.install-plug-in.ovs.html" target="_blank">http://docs.openstack.org/havana/install-guide/install/yum/content/install-neutron.install-plug-in.ovs.html</a></div>
<div><br></div><div>When I issue the command (step 4)</div><div><br></div><div>ovs-vsctl add-port br-ex eth0</div><div><br></div><div>the terminal I'm working on freezes, and the connection to 192.168.120.13 is definitely lost, and I can't reconnect to it anymore from any other host.</div>
<div><br></div><div>I suspect there's some inaccuracy in the installation instructions, and in addition I'm not an expert on bridge and interfaces stuff.</div><div><br></div><div>Can someone explain me what's wrong and if there's a better documentation for a complete Neutron installation and configuration ?</div>
<div><br></div><div>thank you very much,</div><div><br></div><div><span style="white-space:pre-wrap"> </span>Alvise</div></div><br></div></div>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Lorin Hochstein<br><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a></div>
</div>
</div></div></div></div>