> > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > auto eth0 > iface eth0 inet dhcp > > # The virtualization network interface > auto eth1 > allow-ovsbr0 eth1 > iface eth1 inet manual > ovs_bridge ovsbr0 > ovs_type OVSPort > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down > > auto ovsbr0 > allow-ovs ovsbr0 > iface ovsbr0 inet manual > ovs_type OVSBridge > ovs_ports ovsbr0 > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down > > auto ovsbr1 > allow-ovs ovsbr1 > iface ovsbr1 inet manual > ovs_type OVSBridge > ovs_ports ovsbr1 > pre-up ifconfig $IFACE up > post-down ifconfig $IFACE down
The code has been written in a way that bridges are created when "/etc/init.d/openvswitch-switch start" is called. And deleted when "/etc/init.d/openvswitch-switch stop" is called. Can you run them manually to see if you see bridges getting deleted and created? The o/p of 'ovsdb-tool -mm show-log' is confusing me. * I see the bridges getting deleted as soon as openvswitch starts. (record 9 comes up when OVS starts, record 10 within a second deletes a bridge.) * A little later: record 20 and record 22 deletes the bridges again and I do not see the signs of either the server shutting down (which is when it should happen) because record 23 has a manual addition of bridge usign ovs-vsctl. You can look at /var/log/openvswitch/ovs-ctl.log to see the timestamps of someone calling 'start' or 'stop' Are there third-party scripts here that use OVS (like openstack?) and call its start up scripts or have added their own in /etc/init or /etc/init.d ? Have you added things to rc.local etc to force OVS to start early etc? _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
