On Fri, Oct 26, 2012 at 10:01 AM, Denis Iskandarov wrote: > 2. i will continue investigation as well. NOTE: order of components start at boot /etc/rc.d/rc3.d/S09openvswitch /etc/rc.d/rc3.d/S10network
reverse at shutdown. So possible for a restart of all the stack you could run something like this in a unique command if you are not directly at console # service network stop; service openvswitch stop; service openvswitch start; service network start BTW: you could find the config I'm using in this thread: http://openvswitch.org/pipermail/discuss/2012-August/007845.html This is the output of the command above on my system (after the line regarding shutdown of bond0 there is one minute before you see on terminal all the other lines) Shutting down interface bond0: [ OK ] Shutting down interface bond1: [ OK ] Shutting down interface br0: [ OK ] Shutting down interface eth2: [ OK ] Shutting down interface eth3: [ OK ] Shutting down loopback interface: [ OK ] Killing ovs-brcompatd (2107) [ OK ] Killing ovs-vswitchd (2074) [ OK ] Killing ovsdb-server (2065) [ OK ] /usr/share/openvswitch/scripts/ovs-ctl: line 177: ulimit: core file size: cannot modify limit: Invalid argument Starting ovsdb-server [ OK ] Configuring Open vSwitch system IDs [ OK ] Starting ovs-vswitchd [ OK ] Starting ovs-brcompatd [ OK ] iptables already has a rule for gre, not explicitly enabling. Bringing up loopback interface: [ OK ] Bringing up interface bond0: [ OK ] Bringing up interface bond1: [ OK ] Bringing up interface br0: [ OK ] Bringing up interface brvlan65: [ OK ] Bringing up interface brvlan66: [ OK ] Bringing up interface eth2: [ OK ] Bringing up interface eth3: [ OK ] HIH, Gianluca _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
