Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[mininet-discuss] [help] Mininet VM 2.2.1 Fully Support OpenFlow 1.3?

Qing Wang qw at g.clemson.edu
Mon May 11 18:49:44 PDT 2015


Hey Bob,

Thank you very much! I think this is what I need.

Could you give me a hint that where is the script "install.sh"? I tried a
while but I couldn't find it. Is this script inside the Mininet VM or
outside Mininet VM ?

Thanks!

Qing

On Mon, May 11, 2015 at 9:22 PM, Bob Lantz <rlantz at cs.stanford.edu> wrote:

> By default we use the distribution version of OVS.
>
> OVS 2.0.2 provides some support OpenFlow 1.3, but you need to use the
> protocols=OpenFlow13 argument
>
> If you wish, you may wish update to OVS 2.3.1, which supports OF 1.3
> without any options.
> You can do so with: install.sh -V 2.3.1
>
>
> On May 11, 2015, at 12:51 PM, Qing Wang <qw at g.clemson.edu> wrote:
>
> Hey there,
>
> I just wondering if Mininet VM 2.2.1 fully support OpenFLow 1.3 yet? I did
> couple things to try below, and I met couple problems.
>
> I used Floodlight V1.1 as my controller and Mininet VM 2.2.1 as testing
> experiment. The OVS version in Mininet VM is 2.0.2. And my current setup is
> default topology, nodes are c0, h1, h2, s1. Meaning a single controller
> case.
>
> Below is the command I set up my mininet topo:
> sudo mn --controller=remote,ip=130.127.39.226,port=6653 --switch
> =ovsk,protocols=OpenFlow13
>
> I can see Floodlight detect a new switch connected and shown switch's
> DPID.  The problem is:
> 22:37:11.901 ERROR [n.f.c.i.*OFSwitchHandshakeHandler:New* I/O worker
> #22] *OFBadRequestErrorMsgVer13*(xid=7392, code=BAD_TYPE,
> data=OFGroupDeleteVer13(xid=7392, groupType=ALL, group=all, buckets=[]))
> from switch OFSwitchBase DPID[00:00:00:00:00:00:00:01] in state
> net.floodlightcontroller.core.internal.OFSwitchHandshakeHandler$MasterState at 153ca5
> 22:37:11.901 WARN [n.f.c.i.Controller:New I/O worker #22] Unhandled OF
> Message: OFBadRequestErrorMsgVer13(xid=7392, code=BAD_TYPE,
> data=OFGroupDeleteVer13(xid=7392, groupType=ALL, group=all, buckets=[]))
> from OFSwitchBase DPID[00:00:00:00:00:00:00:01]
> 22:37:11.901 ERROR [n.f.c.i.OFSwitchHandshakeHandler:New I/O worker #22]
> OFBadRequestErrorMsgVer13(xid=7392, code=BAD_TYPE,
> data=OFGroupDeleteVer13(xid=7392, groupType=ALL, group=all, buckets=[]))
> from switch OFSwitchBase DPID[00:00:00:00:00:00:00:01] in state
> net.floodlightcontroller.core.internal.OFSwitchHandshakeHandler$MasterState at 153ca5
> 22:37:11.901 WARN [n.f.c.i.Controller:New I/O worker #22] Unhandled OF
> Message: OFBadRequestErrorMsgVer13(xid=7392, code=BAD_TYPE,
> data=OFGroupDeleteVer13(xid=7392, groupType=ALL, group=all, buckets=[]))
> from OFSwitchBase DPID[00:00:00:00:00:00:00:01]
>
>
> The error looks like to me is a problem happened on the initial OF
> handshake process. ( And the OF handshake process failed ). I already
> checked the controller role(MASTER, EQUAL and SLAVE) to make sure I dont
> accidentally set up a wrong role.  Both MASTER and EQUAL role will give me
> the error above, and SLAVE roles works fine. I think it makes sense because
> under SALVE mode the controller is nothing but a monitor.
>
> And if I tried to insert a flow( in MASTER or EQUAL ), the switch
> disconnected due to switch state error as expected:
> 23:12:45.314 INFO [n.f.c.i.OFChannelHandler:New I/O worker #23] New switch
> connection from /130.127.39.226:55568
> 23:12:45.342 ERROR [n.f.c.i.OFChannelHandler:New I/O worker #23]
> Disconnecting switch [? from 130.127.39.226:55568] *due to switch state
> error*: Switch: [[? from 130.127.39.226:55568]], State:
> [net.floodlightcontroller.core.internal.OFChannelHandler$WaitFeaturesReplyState at 35c242],
> received: [FLOW_MOD], details: Switch should never send this message in the
> current state
> 23:12:45.343 INFO [n.f.c.i.OFChannelHandler:New I/O worker #23] [[? from
> 130.127.39.226:55568]] Disconnected connection
>
> Once again, the mininet VM has OVS version 2.0.2. Does Mininet VM support
> OF 1.3 fully? Because I use the latest Floodlight V1.1 version which
> support OF 1.3. Maybe there is something not compatible that causing the OF
> handshake failed?
>
> If I tried to use OpenFlow 1.0 on mininet, it do solve the initial OF
> handshake problem. However, if I want to insert flow to switch, the switch
> state error shows again and switch automatically disconnected.
>
> Using OpenFLow 1.0 protocol:
> sudo mn --controller=remote,ip=130.127.39.226,port=6653 --switch
> =ovsk,protocols=OpenFlow10
>
> Here is what I did:
> dpctl add-flow tcp:130.127.39.226:6653 in_port=3,actions=output:3
>
> And the error is:
> 15:27:48.611 ERROR [n.f.c.i.OFChannelHandler:New I/O worker #23]
> Disconnecting switch [? from 130.127.39.226:34737] due to switch state
> error: Switch: [[? from 130.127.39.226:34737]], State:
> [net.floodlightcontroller.core.internal.OFChannelHandler$WaitFeaturesReplyState at 1c5a053],
> received: [FLOW_MOD], details: Switch should never send this message in the
> current state
> 15:27:48.611 INFO [n.f.c.i.OFChannelHandler:New I/O worker #23] [[? from
> 130.127.39.226:34737]] Disconnected connection
>
> I am not sure if anything else I should try. But I guess the first thing I
> need to confirm is:  does Mininet VM 2.2.1 is fully support OpenFlow 1.3?
> Or maybe there are some things I did was wrong?
>
> Thanks in advance!!
>
> Qing
>
>
>
>
>
> _______________________________________________
> mininet-discuss mailing list
> mininet-discuss at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/mininet-discuss
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/mininet-discuss/attachments/20150511/d73b0955/attachment.html>


More information about the mininet-discuss mailing list