1. Messages
  2. Cannot ping between instances (resolved)

Re: Cannot ping between instances (resolved)

alagalah <alagalah@...>
 

Turns out I needed to set of.address to my loopback (222.222.222.222) in the ODL config.ini.

I suspect the controller was using my local DHCP address (192.168.1.x) as the source address to speak to the OVS instances, hence the OVS instances ignored it, and by setting the of.address it uses 222.222.222.222...

I'll try and confirm with a wireshark trace but if someone can confirm the above, might be handy for someone if they scan these archives.

Thanks.
On 01/11/2014 11:05 AM, alagalah wrote:

Hi folks,

I'm currently running Fed19 devstack with Cisco's ML2 extensions.

I'm trying to ping between virtual machines but I'm getting these sorts of errors in the OSGI log:

2014-01-11 10:51:02.137 PST [pool-16-thread-1] ERROR o.o.o.n.provider.OF10ProviderManager - Failed to initialize Flow Rules for OVS|222.222.222.222:59420

And:
2014-01-11 10:54:36.315 PST [pool-16-thread-1] ERROR o.o.ovsdb.neutron.SouthboundHandler - Error fetching Interface Rows for node OVS|222.222.222.222:59415

I have attached my local.conf files.

From the devstack controller I can ping the instance running locally, but cannot ping the instance running on the compute node. My VXLAN tunnels are not being established. This is from a known working snapshot, so not sure where to look next.

Any pointers to logs I should be looking at greatly appreciated.

[fedora@fedora19-controller devstack]$ uname -a
Linux fedora19-controller 3.9.5-301.fc19.i686 #1 SMP Tue Jun 11 20:01:50 UTC 2013 i686 i686 i386 GNU/Linux
[fedora@fedora19-compute devstack]$ uname -a
Linux fedora19-compute 3.9.5-301.fc19.i686 #1 SMP Tue Jun 11 20:01:50 UTC 2013 i686 i686 i386 GNU/Linux


On my devstack controller:
[fedora@fedora19-controller devstack]$ sudo ovs-vsctl show
1112ab1d-b0b6-4f61-8805-c3df388c4dd2
    Manager "tcp:222.222.222.222:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:222.222.222.222:6633"
            is_connected: true
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "tap55e2aee1-5f"
            tag: 7
            Interface "tap55e2aee1-5f"
        Port "tap52e7c6a3-32"
            tag: 7
            Interface "tap52e7c6a3-32"
        Port "tap3f7930fe-1a"
            tag: 7
            Interface "tap3f7930fe-1a"
    Bridge br-ex
        Controller "tcp:222.222.222.222:6633"
            is_connected: true
        Port br-ex
            Interface br-ex
                type: internal
        Port "tap50e845e5-8b"
            Interface "tap50e845e5-8b"
    Bridge br-tun
        Controller "tcp:222.222.222.222:6633"
            is_connected: true
        Port br-tun
            Interface br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    ovs_version: "2.0.0"


and on the compute:
[fedora@fedora19-compute devstack]$ sudo ovs-vsctl show
be0041a6-2173-4d9f-a568-e1d335d58ff6
    Manager "tcp:222.222.222.222:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:222.222.222.222:6633"
            is_connected: true
        Port br-int
            Interface br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tapf35fbbb0-3b"
            tag: 7
            Interface "tapf35fbbb0-3b"
    Bridge br-tun
        Controller "tcp:222.222.222.222:6633"
            is_connected: true
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
    ovs_version: "2.0.0"
[fedora@fedora19-compute devstack]$



Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.