SOX AM NEC OpenFlow switch

[Fei Yeh]

Hello,

I'm using Floodlight to control a sliver on the SOX AM NEC Openflow Switch through the foam https://foam.sox.net:3626/foam/gapi/2

We do not have any experience using Floodlight with NEC switch before, and we are not able to see any flows in the Floodlight UI on this NEC switch [/143.215.216.11:41490 DPID[00:01:34:40:b5:03:14:00]]

We use the same set-up on the SL-AM switch (a Pica8 3290), and we are able to push flows into it and see it appear in the UI.

Is there any way for us to verify that we have flows set up on this switch?

Fei

[Nicholas Bastin]

On May 23, 2014 2:20 PM, "Fei Yeh" <nufe...@gmail.com> wrote:
> I'm using Floodlight to control a sliver on the SOX AM NEC Openflow Switch through the foam https://foam.sox.net:3626/foam/gapi/2

There is a bug in the version of flowvisor in use of sox that makes retrieving stats basically impossible.

--
Nick

[Fei Yeh]

Does this mean that I won't be able to see if a flow is created on the SOX switch with a NOX controller with a console either?

[Tim Upthegrove]

I think the nature of the FV bug is that it sets some kind of last-flow-in-stats-reply bit on the first flow it sees in the flow stats reply, even though it does send more flow stats after that.  You can see more at https://github.com/OPENNETWORKINGLAB/flowvisor/issues/244 if you are curious.

I think you might be able to see all flow stats if you take a control plane packet capture and find the stats reply, but any controller that is working correctly will display stats for at most one flow.  That isn't ideal, but I think it can help you move forward.

--
GENI Users is a community supported mailing list, so please help by responding to questions you know the answer to.
 
If this is your first time posting a question to this list, please review http://groups.geni.net/geni/wiki/GENIExperimenter/CommunityMailingList
---
You received this message because you are subscribed to the Google Groups "GENI Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geni-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

 

Tim Upthegrove

[Nicholas Bastin]

On Tue, May 27, 2014 at 12:00 PM, Fei Yeh <nufe...@gmail.com> wrote:

Does this mean that I won't be able to see if a flow is created on the SOX switch with a NOX controller with a console either?

You can only guarantee receiving a single flow entry back from a stats request.  If your match would return more than 1 entry, I'm not sure there's any deterministic order in which the "first" one is returned.  (It returns them all, but fails to set the "more data" bit in the first packet, so no controller will handle these packets).

--

Nick 

[Fei Yeh]

I took a capture of the control plane packets on the controller, limiting to the packets between the controller and the SOX flowvisor.  Then I opened the capture file on a computer with Wireshark. However, the captured packets just display as generic "Data" in Wireshark with OpenFlow plugin, instead of "OpenFlow Protocol".  How do you find the stats reply in a captured packet file?

[Nicholas Bastin]

On May 28, 2014 10:31 AM, "Fei Yeh" <nufe...@gmail.com> wrote:
>
> I took a capture of the control plane packets on the controller, limiting to the packets between the controller and the SOX flowvisor.  Then I opened the capture file on a computer with Wireshark. However, the captured packets just display as generic "Data" in Wireshark with OpenFlow plugin, instead of "OpenFlow Protocol".  How do you find the stats reply in a captured packet file?

You have to right click on one of the openflow data packets (as its using a nonstandard port) in the connection and select "decode as..." and then tell wireshark it is openflow (possibly OFP, depending on your wireshark version).

--
Nick

[Fei Yeh]

Ok the packets are listed as OFP 1.0 now, but the Data tree is gone, and not replaced by a "OpenFlow" tree as expected.  It's just empty...

What have you used to look at OFP packets?  Wireshark?  tcpdump?  What version and on what kind of platform?

Nick, I saw that you have a "download" section under "openflow-dissector" in Bitbucket as linked to in one of your posts somewhere else.  I signed up for an account but then I get an "Access denied" when I try to go to the page.  If this is a wireshark dissector plugin that you know works , please let me know what version of Wireshark I should be using for it.

[Nicholas Bastin]

On Thu, May 29, 2014 at 3:18 PM, Fei Yeh <nufe...@gmail.com> wrote:

Ok the packets are listed as OFP 1.0 now, but the Data tree is gone, and not replaced by a "OpenFlow" tree as expected.  It's just empty...

That is a little bit odd, but I'm not sure what version of wireshark and what dissector you have.

 

What have you used to look at OFP packets?  Wireshark?  tcpdump?  What version and on what kind of platform?

Typically wireshark on MacOS X or Linux.

 

Nick, I saw that you have a "download" section under "openflow-dissector" in Bitbucket as linked to in one of your posts somewhere else.  I signed up for an account but then I get an "Access denied" when I try to go to the page.  If this is a wireshark dissector plugin that you know works , please let me know what version of Wireshark I should be using for it.

What OS are you using?  I maintain the original 1.0 dissector at:

https://bitbucket.org/barnstorm/of-dissector

But you will need to build it (which is a pain) - the only thing in downloads is built for MacOS X for an old version of wireshark.  If you let me know what platform and version of wireshark you are using, I can post one there (pre-built) for your environment.

--

Nick 

[Fei Yeh]

Thanks for the offer Nick.  Once I realized that the Wireshark was defective I found a different system to run it on and it works on this other Ubuntu 12 OS just fine.