<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 28, 2016, at 11:36 PM, Remo Mattei wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>is this a multi deployment air?</div></blockquote><div><br></div><div>"multi deployment air"?</div><br><blockquote type="cite"><div>Did you check if you can ping each other if in a multi?</div></blockquote><div><br></div><div>"in a multi"?</div><div><br></div><div><br></div><div>If you mean, can I ping the Controller via eth0 and</div><div>vise versa, without the traffic going through eth1,</div><div>then yes:</div><div><br></div><div>bladeA03b:~# ping -c2 10.99.0.1<br>PING 10.99.0.1 (10.99.0.1) 56(84) bytes of data.<br>64 bytes from 10.99.0.1: icmp_seq=1 ttl=64 time=1.19 ms<br>64 bytes from 10.99.0.1: icmp_seq=2 ttl=64 time=0.357 ms<br><br>--- 10.99.0.1 ping statistics ---<br>2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br>rtt min/avg/max/mdev = 0.357/0.774/1.191/0.417 ms<br>bladeA03b:~# traceroute -n 10.99.0.1<br>traceroute to 10.99.0.1 (10.99.0.1), 30 hops max, 60 byte packets<br> 1 10.99.0.1 1.044 ms 1.040 ms 1.024 ms</div><div><br></div><div>In this case, I'm pinging Controller/eth0 from the Compute</div><div>(connected to the same Cisco switch, no VLAN tagging).</div><br><blockquote type="cite"><div> What does the ovs-vsctl show output is?</div></blockquote><div><br></div><div>bladeA03b:~# ovs-vsctl show</div><div>5e1ec384-b926-4148-9bfd-cbf7db56cfa2<br> Bridge br-physical<br> Port "eth1"<br> Interface "eth1"<br> Port br-physical<br> Interface br-physical<br> type: internal<br> Bridge br-tun<br> fail_mode: secure<br> Port patch-int<br> Interface patch-int<br> type: patch<br> options: {peer=patch-tun}<br> Port br-tun<br> Interface br-tun<br> type: internal<br> Bridge br-provider<br> fail_mode: secure<br> Port "qvo6a866c7f-2b"<br> tag: 1<br> Interface "qvo6a866c7f-2b"<br> Port patch-tun<br> Interface patch-tun<br> type: patch<br> options: {peer=patch-int}<br> Port br-provider<br> Interface br-provider<br> type: internal<br> Port phy-br-provider<br> Interface phy-br-provider<br> type: patch<br> options: {peer=int-br-provider}<br> Port "eth0"<br> Interface "eth0"</div><div> Port int-br-provider<br> Interface int-br-provider<br> type: patch<br> options: {peer=phy-br-provider}<br> Port "qvob15ee1e9-8a"<br> tag: 1<br> Interface "qvob15ee1e9-8a"<br> ovs_version: "2.3.0"</div><div><br></div><blockquote type="cite"><div> The UI/Dashboard sometimes show it’s down but it really</div></blockquote><blockquote type="cite"><div>it’s not and it works fine.</div></blockquote><div><br></div><div>Ok, good. That's what it seems like here. Except the</div><div>"external" port (the one on the "physical" network).</div><div><br></div><div>However, looking at the router interfaces (screen shot</div><div>included), all it's ports are "Down" :(.</div><br><blockquote type="cite"><div> It’s a bad case where this is a very common issue when</div></blockquote><blockquote type="cite"><div>people are looking at the UI and that state is marked as</div></blockquote><blockquote type="cite"><div>down and it works!<br><br>Eventually it will show active. <br></div></blockquote><div><br></div>Perfect, thanx!</div><div>--</div><div>You know, boys, a nuclear reactor is a lot like a woman.<br>You just have to read the manual and press the right buttons<br>- Homer Simpson</div><img id="2dd866a9-008b-44e0-9fb3-748899a6ff42" height="222" width="741" apple-width="yes" apple-height="yes" src="cid:00B0DF34-00E3-4A28-87FA-83F37AB6CD5E@bayour.com"></body></html>