← Back to team overview

openstack team mailing list archive

Re: Issues with openvswitch agent on Quantum/network node

 

Hi,
What are the good to know tools and networking concepts for me to be able to debug connectivity issues inside Openstack VLAN mode of OVS?

Thanks,
Best Regards,
Rekha

From: Sreerekha Shenoy (sresheno)
Sent: Friday, June 14, 2013 2:23 PM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Issues with openvswitch agent on Quantum/network node

Hi,
I have a multi node grizzly setup using the following guide:
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
My network topology is as attached and is using GRE tunnel based VLAN.

I have VMs spawning on compute for cirros images.
However, inter-VM ping works (e.g. 50.50.1.4 can ping 50.50.1.5), but the following DON'T work:

a)      VM cannot ping 50.50.1.1

b)      VM cannot ping Compute ETH1 (data n/w) , 10.20.20.53

c)       VM cannot be reachable from IP Namespace either (ip netns exec qrouter-xxxx ping 50.50.1.4 does NOT work)

Apart from the same, my network node has the following issue AFTER a reboot:

·          On network node the following agent is not running i.e. "quantum-plugin-openvswitch-agent"

·         Logs of this agent indicates it needs the plugin upgrade....dont have the precise error log..

o   ovs-vswitchd.log indicates the following:

§  Apr 16 22:08:39|00482|netdev|WARN|Dropped 233 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate

§  Apr 16 22:08:39|00483|netdev|WARN|failed to get flags for network device qr-12091c58-8a: No such device

§  Apr 16 22:08:43|00484|netdev_linux|WARN|Dropped 35 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate

·         The version of OSK-plugin-ovs-agent is 2013.1.1-0ubuntu1

·         The result of the above being that "br-tun DOES NOT have gre-2 / gre-1 port on it" for both compute and network..

Please let me know what could be done to:

1.       get the ovs-agent running on compute

2.       have VMs pingable
================================================================================================================
compute Node output:
root@computenode:~# ovs-vsctl show
4aad5da2-861d-4190-a50b-37dfc5ca237a
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port "qvo47a58f32-be"
            Interface "qvo47a58f32-be"
        Port "qvo19e7cd4c-c0"
            tag: 1
            Interface "qvo19e7cd4c-c0"
        Port "qvobaa01ac1-69"
            tag: 1
            Interface "qvobaa01ac1-69"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "1.4.0+build0"

================================================================================================================

Network node output:

root@networknode:~# ovs-vsctl show
9e17bb8c-d69d-48ab-9333-b22447c0c268
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "qr-a7ab3f7c-8e"
            Interface "qr-a7ab3f7c-8e"
                type: internal
        Port "tap6a322215-f0"
            tag: 1
            Interface "tap6a322215-f0"
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-1d552cbd-a0"
            Interface "qg-1d552cbd-a0"
                type: internal
        Port "eth2"
            Interface "eth2"
    ovs_version: "1.4.0+build0"


Thanks and Regards,
Rashmi S N