Here is a dump from OVS. Packet #1 is the TCP packet that fires off this change of events. The flow mods are at packet #2 and 3 and no error message comes after that. (This is what I'm hoping to see in the hardware setup).
Thanks, Aaron On Fri, Jun 24, 2011 at 2:16 PM, Aaron Rosen <aro...@clemson.edu> wrote: > Hi Rob, > > I set up a test environment using two OVS and a couple VM's and no > flowvisor. In this setup everything works perfectly and I do not get > that error message on the flowmod. > > When I move my code to a real OF switches where there is a flowvisor > is when I get this error message. > > Thanks, > > Aaron > > On Fri, Jun 24, 2011 at 1:26 PM, Ben Pfaff <b...@nicira.com> wrote: >> On Fri, Jun 24, 2011 at 12:46:52PM -0400, Aaron Rosen wrote: >>> Packet #18 in this trace is what fires off this series of events. Then >>> packet #19,20 are the corresponding flow mods to do this. Packet #23 >>> is the error message saying Specified buffer has already been used. >> >> I don't have the wireshark or tcpdump plugin for OpenFlow installed, >> so it's not easy for me to interpret this pcap file. >> >> If you turn OVS's vconn logging to the highest level (either starting >> ovs-vswitchd with -vvconn or running "ovs-appctl vlog/set vconn" after >> ovs-vswitchd has started), then it will log all of the OpenFlow >> messages in both directions. That would be easier to interpret. >> > > > > -- > Aaron O. Rosen > Masters Student - Network Communication > 306B Fluor Daniel > -- Aaron O. Rosen Masters Student - Network Communication 306B Fluor Daniel
ovs-dump.pcap
Description: application/cap
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss