Hi all,
I had the following configuration:
ovs-vsctl show
Bridge br-ex
Port "eth0"
Interface "eth0"
Port br-ex
Interface br-ex
type: internal
eth0 being the eth device who's IP was migrated over to br-ex. The OVS
version used here was 2.0
I downloaded the OVS 2.3.1 tar ball and did an install following the
INSTALL doc.
I hadn't cleaned up the DB before doing so. Post the upgrade - I was able
to successfully start the ovsdb-server but the ovs-vsctl output didn't
have the older config. (It was a blank output)
eth0 appeared without the IP address and the ifconfig command doesn't list
br-ex anymore. I modified the ifcfg files to have the IP over on the eth
device eth0.
Post this too, the system was unreachable. I switched off the OVS process
and after a reboot - the machine became reachable however, now everytime i
start the ovsdb-server/ovs-vswitchd, the host becomes unreachable.
Any clues on why this might be happening? I have tried dumping the
database, but unfortunately couldn't find the right command without the
ovs-vsctl utility which always ends up showing empty tables.
>From the ovs-vswitchd.log file - these lines could be seen:
|00067|netdev_linux|WARN|br-ex: obtaining netdev stats via vport failed
(No such device)
|00068|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on br-ex device failed: No
such device
|00069|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on br-ex device failed: No
such device
So i am wondering if the old DB entries are still somehow left over...Is
there a way to clean them up?
Regards,
Sudipto Biswas
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
