Open Stack

On Jun 28, 2016, at 11:36 PM, Remo Mattei wrote:

> is this a multi deployment air?

"multi deployment air"?

> Did you check if you can ping each other if in a multi?

"in a multi"?


If you mean, can I ping the Controller via eth0 and
vise versa, without the traffic going through eth1,
then yes:

bladeA03b:~# ping -c2 10.99.0.1
PING 10.99.0.1 (10.99.0.1) 56(84) bytes of data.
64 bytes from 10.99.0.1: icmp_seq=1 ttl=64 time=1.19 ms
64 bytes from 10.99.0.1: icmp_seq=2 ttl=64 time=0.357 ms

--- 10.99.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.357/0.774/1.191/0.417 ms
bladeA03b:~# traceroute -n 10.99.0.1
traceroute to 10.99.0.1 (10.99.0.1), 30 hops max, 60 byte packets
 1  10.99.0.1  1.044 ms  1.040 ms  1.024 ms

In this case, I'm pinging Controller/eth0 from the Compute
(connected to the same Cisco switch, no VLAN tagging).

> What does the ovs-vsctl show output is?

bladeA03b:~# ovs-vsctl show
5e1ec384-b926-4148-9bfd-cbf7db56cfa2
    Bridge br-physical
        Port "eth1"
            Interface "eth1"
        Port br-physical
            Interface br-physical
                type: internal
    Bridge br-tun
        fail_mode: secure
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-provider
        fail_mode: secure
        Port "qvo6a866c7f-2b"
            tag: 1
            Interface "qvo6a866c7f-2b"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-provider
            Interface br-provider
                type: internal
        Port phy-br-provider
            Interface phy-br-provider
                type: patch
                options: {peer=int-br-provider}
        Port "eth0"
            Interface "eth0"
        Port int-br-provider
            Interface int-br-provider
                type: patch
                options: {peer=phy-br-provider}
        Port "qvob15ee1e9-8a"
            tag: 1
            Interface "qvob15ee1e9-8a"
    ovs_version: "2.3.0"

> The UI/Dashboard sometimes show it’s down but it really
> it’s not and it works fine.

Ok, good. That's what it seems like here. Except the
"external" port (the one on the "physical" network).

However, looking at the router interfaces (screen shot
included), all it's ports are "Down" :(.

> It’s a bad case where this is a very common issue when
> people are looking at the UI and that state is marked as
> down and it works!
> 
> Eventually it will show active. 

Perfect, thanx!
--
You know, boys, a nuclear reactor is a lot like a woman.
You just have to read the manual and press the right buttons
- Homer Simpson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160629/6ef52a09/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2016-06-28 23.59.59.png
Type: image/png
Size: 44558 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160629/6ef52a09/attachment.png>