On Nov 25, 2012, at 6:39 PM, shashaankar reddy wrote:
> In order to make it work I commented it out following code, in l2_port_slicer:
> Code-Commented-1
> #group = self.port_groups.get(event.port)
> #if group is None:
> # log.debug("Dropping packets from non-grouped port %s.%i",
> # dpid_to_str(event.dpid), event.port)
> # drop(5)
> # return
>
> and
> Code-Commented-2
> # Send to all other ports in this group
> #for p in group:
> msg.actions.append(of.ofp_action_output(port = of.OFPP_FLOOD)) # (and
> made this change for flooding)
So the test I'd run is:
Leave all the code as original except switch to a single OFPP_FLOOD action (as
in your Code-Commented-2 block). Set the config file to have no port group so
that the component generates a single port group of all ports. Capture the
OpenFlow traffic using Wireshark or the openflow.debug component. Then do a
ping test. Be sure to wait for a few seconds after all switches connect before
doing the test.
Post the logs and pcap traces.
If that test doesn't work, comment out JUST the drop(5) and return from the
first code block and re-run it and post those logs and pcap traces too.
> I collected following logs when for different scenarios as described below:
> (It also includes few additional log messages for explanatory and debugging
> purpose)
Without seeing the code or knowing your topology, it's hard to extract meaning
from the additional logged info.
> Though I could not capture it i the above cases, I could also see the
> following log message:
> Dropping packets from non-grouped port..... when I included the code-1 in the
> script.
You should check these. If the port number is very large or negative, it's
probably fine. If it's a sane port number, this is a problem.
> Does any one have a clue which triggered this issue ?
The possibilities that spring to mind are:
1) It could be that your switch doesn't support sending the same buffer out
multiple ports. The OpenFlow 1.0 spec is murky on whether this is required or
not (earlier versions were clearer) -- the best way to find out now is probably
to check your switch's manual.
2) The switch is doing VLAN tagging which is messing things up.
Though it may well be something entirely different.
-- Murphy
