Connectivity issue after upgrading the ovs version to 2.5.9 and making it nsh aware

asked 2016-12-15 03:03:45 -0700

Anirudh gravatar image

Hi,

We have trying to create a SFC using Openstack Mitaka and ODL Boron.

But we are facing connectivity issue after upgrading the ovs version to 2.5.9 and making it nsh aware.

Setup Details :-

• Openstack Mitaka • Kernel version - 3.19.0-69-generic

Initially we had ovs version 2.5.0 installed on the machine.

In order to upgrade ovs and make it nsh aware, we have followed the following steps as per the link https://github.com/yyang13/ovsnshpatches :-

• Deleted all the bridges and assigned the IP to the eth0 and eth1 ports. • git clone https://github.com/yyang13/ovsnsh patches.git • git clone https://github.com/openvswitch/ovs.git • git reset --hard 7d433ae57ebb90cd68e8fa948a096f619ac4e2d8 • cp ../ovs nshpatches/ .patch ./ • git clone https://github.com/yyang13/ovs_nsh_pa... • cd ovs • git reset --hard 7d433ae57ebb90cd68e8fa948a096f619ac4e2d8 • cp ../ovs_nsh_patches/ .patch ./ • git config --global user.email "you@example.com" • git am *.patch • apt-get install build-essential fakeroot • dpkg-checkbuilddeps (to check the dependencies) • apt-get install graphviz autoconf automake automake1.10 debhelper dh-autoreconf libssl-dev libtool python-all python-twisted-conch (install all the dependencies) • dpkg-checkbuilddeps (empty output) • DEB_BUILD_OPTIONS='parallel=8 nocheck' fakeroot debian/rules binary • cd ../ • dpkg -i openvswitch-common2.5.90-1amd64.deb • dpkg -i openvswitch-switch2.5.90-1amd64.deb

ovs version 2.5.9 is shown in ovs-vsctl show.

Now, bridges are created and IP is assigned on them.

On Controller/Network Node :-

• ifconfig eth1 0 promisc up • ifconfig br-vlan 192.168.6.33 netmask 255.255.255.0 up • ifconfig eth0 0 promisc up • ifconfig br-ex 172.19.53.33 netmask 255.255.255.0 up • route add default gw 172.19.53.1 dev br-ex

On Compute Node :- • ifconfig eth1 0 promisc up • ifconfig br-vlan 192.168.6.34 netmask 255.255.255.0 up

After all this execution, the connectivity between the bridges got broken and there was no ping response

root@Controller-New:~# ping 192.168.6.34 PING 192.168.6.34 (192.168.6.34) 56(84) bytes of data. From 192.168.6.33 icmpseq=9 Destination Host Unreachable From 192.168.6.33 icmpseq=10 Destination Host Unreachable From 192.168.6.33 icmpseq=11 Destination Host Unreachable From 192.168.6.33 icmpseq=12 Destination Host Unreachable From 192.168.6.33 icmpseq=13 Destination Host Unreachable From 192.168.6.33 icmpseq=14 Destination Host Unreachable From 192.168.6.33 icmpseq=15 Destination Host Unreachable From 192.168.6.33 icmpseq=16 Destination Host Unreachable From 192.168.6.33 icmp_seq=17 Destination Host Unreachable

--- 192.168.6.34 ping statistics --- 18 packets transmitted, 0 received, +9 errors, 100% packet loss, time 17103ms pipe 3

However in order to confirm the issue, we reverted back the ovs version to 2.5.0.

After rebuilding, the ping between the bridges was successful and there was no connectivity break down.

The connectivity issue again came after building ovs 2.5.9 with nsh.

We are suspecting some issue in ... (more)

edit retag flag offensive close merge delete