Thanks Shuva! On Sun, Nov 27, 2016 at 9:26 AM, Shuva Jyoti Kar < [email protected]> wrote:
> Am glad could help you out. > > > > -Br,shuva > > > > *From:* Yrineu Rodrigues [mailto:[email protected]] > *Sent:* Sunday, November 27, 2016 7:22 PM > > *To:* Shuva Jyoti Kar > *Cc:* Jozef Bacigál; [email protected]; > [email protected]; Developers > *Subject:* Re: [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi Shuva, > > > > Thanks a lot for your support, now we're able to go ahead with our > features and tests. > > I'll update the NIC features. > > > > I really appreciate your attention. > > > > with regards, > > > > On Sun, Nov 27, 2016 at 9:19 AM, Shuva Jyoti Kar < > [email protected]> wrote: > > Hi Yrineu, > > > > The feature dependencies changed a bit. [1] describes it in details. Used > [2] as the feature list and saw[3] flows on the switch. > > Do let us know if the list[3] is correct in a working case. > > > > [1] https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_ > Plugin:FeatureTree > > [2] feature:install odl-openflowplugin-southbound > odl-openflowplugin-flow-services > odl-nic-core-mdsal odl-nic-listeners odl-nic-console > > [3] mininet> sh ovs-ofctl dump-flows -O Openflow13 s1 > > OFPST_FLOW reply (OF1.3) (xid=0x2): > > cookie=0x1, duration=7.382s, table=0, n_packets=0, n_bytes=0, > priority=10000,arp actions=CONTROLLER:65535,NORMAL > > cookie=0x1, duration=7.381s, table=0, n_packets=0, n_bytes=0, > priority=9500,dl_type=0x88cc actions=CONTROLLER:65535 > > mininet> > > > > Do let us know in case you want any help. > > > > Thanks, > > Shuva > > > > > > *From:* Yrineu Rodrigues [mailto:[email protected]] > *Sent:* Sunday, November 27, 2016 4:55 PM > > > *To:* Shuva Jyoti Kar > *Cc:* Jozef Bacigál; [email protected]; > [email protected]; Developers > *Subject:* Re: [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi Shuva, > > > > There's clearly something weird going on. Once I debug NIC Beryllium I can > capture "ofp_flow_mod" messages on Wireshark, but I got nothing running on > Boron. I noticed we're using some deprecated classes, such as NodeId. Is it > critical? Could you please point me to a snippet of flow creation on Boron? > I suspect something has changed and we didn't catch up. > > > > By the way, I have attached some log files. Once we install these three > features [1] we're supposed to have ARP and LLDP flows created and when we > run [2] on Karaf CLI we're supposed to create a flow entry with a L2 match > providing connectivity between hosts. > > > > > > [1] feature:install odl-nic-core-mdsal odl-nic-listeners odl-nic-console > > [2] intent:add -f 00:00:00:00:00:02 -t 00:00:00:00:00:01 -a ALLOW > > > Thanks, > > > > On Thu, Nov 24, 2016 at 5:23 AM, Shuva Jyoti Kar < > [email protected]> wrote: > > Hi Yrineu, > > > > The logs seem clean, could you please take a wireshark dump to see if the > flows are going over the wire and the switch is rejecting them ? > > Also > > 1. Are you installing multiple flows ? or a single flow? > > 2. What is the build against which you are testing? > > > > Thanks > Shuva > > *From:* Yrineu Rodrigues [mailto:[email protected]] > *Sent:* Wednesday, November 23, 2016 9:06 AM > > > *To:* Shuva Jyoti Kar > *Cc:* Jozef Bacigál; [email protected]; > [email protected]; Developers > *Subject:* Re: [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi Shuva, > > > > I debugged NIC using the log set, using OVS 2.4.0, NIC master branch and > two features installed: odl-nic-core-mdsal odl-nic-listeners. > > > > Looking at the logs I see that the handshake initially fails but > immediately succeeds in the next try. Apart of it, no errors or anything > suspicious. > > > > My mininet topology is: > > > > $ sudo mn --controller=remote,ip=192.168.0.12 --topo linear,2 --switch > ovsk,protocols=OpenFlow13 > > > > root@mininet-vm:~# ovs-vsctl show > > 018de162-474c-49f8-8f2d-9617d35a4195 > > Bridge "s2" > > Controller "ptcp:6635" > > Controller "tcp:192.168.0.12:6633" > > is_connected: true > > fail_mode: secure > > Port "s2" > > Interface "s2" > > type: internal > > Port "s2-eth1" > > Interface "s2-eth1" > > Port "s2-eth2" > > Interface "s2-eth2" > > Bridge "s1" > > Controller "tcp:192.168.0.12:6633" > > is_connected: true > > Controller "ptcp:6634" > > fail_mode: secure > > Port "s1-eth2" > > Interface "s1-eth2" > > Port "s1" > > Interface "s1" > > type: internal > > Port "s1-eth1" > > Interface "s1-eth1" > > ovs_version: "2.4.0" > > > > After everything installed nothing is added into the flow tables. As you > can see here: > > > > root@mininet-vm:~# ovs-ofctl -O OpenFlow13 dump-flows s1 > > OFPST_FLOW reply (OF1.3) (xid=0x2): > > > > Karaf logs: http://pastebin.com/ULanUH2s > > > > We appreciate any insight. > > > > On Tue, Nov 22, 2016 at 1:36 PM, Shuva Jyoti Kar < > [email protected]> wrote: > > Sure Yrineu, feel free to ping J > > > > *From:* Yrineu Rodrigues [mailto:[email protected]] > *Sent:* Tuesday, November 22, 2016 7:39 PM > *To:* Shuva Jyoti Kar > *Cc:* Jozef Bacigál; [email protected]; > [email protected]; Developers > > > *Subject:* Re: [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi Shuva, > > I'll test to answer your questions soon, thanks for your help. > > regards, > > > > On Tue, Nov 22, 2016 at 12:49 AM, Shuva Jyoti Kar < > [email protected]> wrote: > > Hi Yrineu, > > > > 0.4.0-Snapshot is the one for stable/Be and that hasnot been changed after > the stable/Be release. > > > > After Be, release the plugin model has changed, it’s the newer model now, > and all functionality remains same. I went through both of your code > snippets, and both look good!! > > > > Have a few questions though that would help us in drill down to the issue: > > > > 1. I assume that the flows are not going over the wire? Am I > correct? > > 2. Are you installing multiple flows ? or a single flow? > > 3. What is the build against which you are testing? > > 4. Are there any errors/exceptions that you see in the logs : if > not, could you please enable debug logs for openflowplugin as > > a. log:set DEBUG org.opendaylight.openflowplugin > > > > thanks > > Shuva > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Yrineu > Rodrigues > *Sent:* Tuesday, November 22, 2016 4:26 AM > *To:* Jozef Bacigál > *Cc:* [email protected]; > [email protected] > *Subject:* Re: [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi Jozef, > > > > Thanks for your fast response! On NIC project we have an OpenFlow renderer > to create basic firewall rules, ARP reply and others. > > Here's > <https://github.com/opendaylight/nic/blob/master/of-renderer/src/main/java/org/opendaylight/nic/of/renderer/impl/ArpFlowManager.java> > an example of 'FlowBuilder' for ARP flows, and here's > <https://github.com/opendaylight/nic/blob/master/of-renderer/src/main/java/org/opendaylight/nic/of/renderer/impl/AbstractFlowManager.java> > the implementation of 'writeDataTransaction()'. > > > > My question is: Something has changed at 'FlowBuilder' creation, after > 'Be' release? > > We need fill some new 'FlowBuilder' field, or change something at > 'writeDataTransaction()' method? > > > > At this current implementation something is wrong and the OF rule isn't > generated. > > > > Please, let me know if you need more info. > > > > Thanks in advance, > > > > On Mon, Nov 21, 2016 at 1:57 PM, Jozef Bacigál < > [email protected]> wrote: > > Hi Yrineu, > > > > can you provide more information what are you doing or trying to do. You > question is too generic so maybe more information would help us to identify > the problem you get and find together the best solution. > > > > Jozef > > > > *From:* Yrineu Rodrigues [mailto:[email protected]] > *Sent:* Monday, November 21, 2016 2:51 AM > *To:* [email protected] > *Cc:* [email protected] > *Subject:* [openflowplugin-dev] ODL: NIC - Issues to create basic > OpenFlow rules using OF Plugin > > > > Hi OpenFlow Plugin team, > > > > The NIC project is facing some issues when we try to create basic flows > rules using the version "0.4.0-SNAPSHOT", please, can someone help us to > understand the changes since Berillyum? > > Maybe some example to create a "FlowBuilder" applying the Boron/Carbon > changes would be helpful. > > > > Thanks in advance, > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > Jozef*Bacigál* > > Software Engineer > > > Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia > R&D centrum / Janka Kráľa 9 / 974 01 Banská Bystrica / Slovakia > +421 908 766 972 / [email protected] > reception: +421 2 206 65 114 / www.pantheon.sk > > [image: logo] > > > > > > > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > > > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > > > > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > > > > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > > > > > -- > > Yrineu Rodrigues > > Software Engineer > > *SERRO* | www.serro.com > > _______________________________________________ > nic-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/nic-dev > >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
