Hi Paul,
Thanks for the reply!
I updated the kernel using the latest build version (v1.20 Build 20180621_5).
Indeed, openvswitch (and tools like ovs-vsctl or ovs-ofctl) comes pre-installed in this version. However, the OVS switch that is running (called ovslan), has a pre-configured controller IP address (192.168.1.136). I assigned this address (and other addresses on the same subnet) to our ODL controller, but it seems like the OVS switch does not connect properly to the controller. I can see on the controller that a new switch is connected, but the flows do not appear on the switch.
I assume the controller and the ovslan should be on the same subnet. Because when I set the controller on a different subnet than the ovslan, I can't access the switch anymore on 192.168.1.0/24.
Any ideas where the issue might be?
Cheers,
Omar