On Sun, Mar 16, 2014 at 10:50 PM, Tim Wolf <[email protected]> wrote: > Hi all, > > I'm not sure, if I'm in the right forum, but I can't figure out, if my > problem on restarting the machine depends on Debian or Open vSwitch: > > Following configuration: > > Debian Wheezy > Open vSwitch 2.0.1 (selfbuilt packages, installation without errors) > > This is my "/etc/network/interfaces" with blanked out IPs: > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > auto br0 > allow-ovs br0 > iface br0 inet static > address 85.###.###.### > netmask 255.255.255.255 > network 85.###.###.### > broadcast 85.###.###.### > gateway 85.###.###.### > ovs_type OVSBridge > ovs_ports eth0 > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down > > auto eth0 > allow-br0 eth0 > iface eth0 inet manual > address 0.0.0.0 > ovs_bridge br0 > ovs_type OVSPort > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down Try removing the "auto". You mentioned that once the machine is up, the database is empty. So I presume "ovs-vsctl show" does not show any bridges/ports configured. In a situation like that, what happens when you run: ifup --allow=ovs br0
Does that create the bridge? > > > # The secondary network interface (over openvswitch) > auto br1 > allow-ovs br1 > iface br1 inet static > address 10.###.###.### > netmask 255.255.255.0 > network 10.###.###.0 > broadcast 10.###.###.255 > ovs_type OVSBridge > ovs_ports eth1 > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down > > auto eth1 > allow-br1 eth1 > iface eth1 inet manual > address 0.0.0.0 > ovs_bridge br1 > ovs_type OVSPort > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down > > up route add -net 10.48.0.0/16 gw 10.###.###.1 dev br1 > > # end of /etc/network/interfaces # > ################################## > > > Starting manually all works fine: > > # ovs-vsctl add-br br0 > # ovs-vsctl add-br br1 > # ovs-vsctl add-port br0 eth0 > # ovs-vsctl add-port br1 eth1 > # /etc/init.d/networking stop > # /etc/init.d/networking start > # route add -net 10.48.0.0/16 gw 10.###.###.1 dev br1 > > > But on booting the system, the ovs-database has "forgotten" its entries, > I think because of boot order, messages during boot are: > > # ovsdb-server is already running. > # ovs-vswitchd is already running. By any chance, do you have a custom script that starts Open vSwitch? The above is saying that someone has already started Open vSwitch. > # Enabling remote OVSDB managers. > # > # br0: ERROR while getting interface flags: No such device > # Failed to bring up br0. > # br1: ERROR while getting interface flags: No such device > # Failed to bring up br1. Also try this: /etc/init.d/openvswitch-switch stop "ovs-vsctl show" should fail. /etc/init.d/openvswitch-switch start What does "ovs-vsctl show" say? > > > Again, starting all things manually works! > > > Is anyone there, who's got a similar setup working? > > > Thanks and greetings, > > Berthold Humkamp > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
