After some more debugging and testing packet outs are being forwarded to both controllers and hosts when added to a bundle. I've tested with 2 controllers, 3 switches and 4 hosts with controllers sending packet outs to each other and pinging between hosts with pingall from mininet. How "good enough" is this from your perspective? I know I still need to write appropriate tests.
Then I tried grouping a PortMod and a PacketOut together in the same bundle to test how enabling or disabling a port affects PacketOut validations. However, I'm not being able to set a port to "up" from the controller. I can put it "down" with a PortMod config=1 mask=1. but when I try to send a PortMod with config=1 mask=0, the port stays down. In wireshark I see the config=1 and mask=0 but in ovs-ofctl snoop it says config:0 mask:0. I can set the port down with ovs-ofctl mod-port so maybe I'm doing something wrong? Ben Pfaff <b...@ovn.org> escreveu no dia quinta, 3/03/2016 às 23:31: > It should still work, if you use ovs-ctl while testing. Usually, > though, when I'm testing, I just run ovs-vswitchd from the command-line, > and in that case you can just invoke "valgrind ovs-vswitchd ...". > > OVS_CTL_OPTS is just an environment variable so you can define it > wherever that is convenient. > > On Thu, Mar 03, 2016 at 10:51:24PM +0000, André Mantas wrote: > > Looks like what I need. What's the quickest way to enable valgrind? > > > > I found this: > http://openvswitch.org/pipermail/discuss/2013-May/010113.html > > > > Does it still apply to today? Where can I define OVS_CTL_OPTS? > > > > Ben Pfaff <b...@ovn.org> escreveu no dia quinta, 3/03/2016 às 18:16: > > > > > On Thu, Mar 03, 2016 at 05:54:42PM +0000, André Mantas wrote: > > > > Hi again. > > > > > > > > For now, I'm testing the implementation with a floodlight controller > that > > > > opens a bundle, adds a packet_out message and tries to commit the > bundle. > > > > I'm using mininet to start a simple topology with 1 switch and 2 > hosts > > > and > > > > connect the switch to the remote controller. I followed INSTALL.md to > > > start > > > > ovs before running the mininet script. > > > > > > > > Everything works like before if the controller does not send a > packet_out > > > > in a bundle. However, when I try to send the packet_out to the > bundle, > > > the > > > > switch disconnects from the controller after the commit request > message > > > is > > > > sent and all ovs-ofctl commands fail on that bridge. > > > > > > > > To debug, I added some VLOG_INFO calls in handle_bundle_add and > > > > do_bundle_commit functions. The prints (found in /var/log/syslog) are > > > below > > > > together with the output of "ovs-ofctl snoop s1" > > > > > > > > Looks like adding the message to the bundle and committing the > bundle is > > > ok > > > > but something happens afterwards? > > > > Where would be a good place to look for the problem? > > > > > > Usually when I get an unexpected connection close while debugging, it > > > means that ovs-vswitchd crashed. I recommend enabling core dumps and > > > then running GDB on the core. "valgrind" is also a good approach. > > > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
