Yeah, as I commented yesterday I am not able to reproduce the issues Selvakumar is facing. From the flows and UI snapshot he posted the issue could be in the host discovery. Please follow this steps: first check ALL switches get the ARP flow required for host discover. After you can test discover function: send traffic from one specific host (e.g. host2 ping X) and then check that host (e.g. host2) is in the UI, you can do this with all hosts of the topology. Finally if you get all hosts discovered, you can check you also get all the MAC2MAC flows in all the switches.
BR/Luis > On May 18, 2016, at 2:12 PM, Sai MarapaReddy <[email protected]> > wrote: > > Hi Selvakumar, > > I was able to ping. These are steps that i have followed, please let me know > any conflicts > > git clone l2switch project > git checkout master > cd l2switch/arphandler/config/src/main/resources/initial/ > change 54-arphandler.xml > cd l2switch/l2switch-main/config/src/main/resources/initial/ > change 58-l2switchmain.xml > cd l2switch > mvn clean install -DskipTests > i got success build > cd distribution/karaf/target/assembly/bin/ > ./karaf > Checking installed features :- > opendaylight-user@root>feature:list -i | grep l2 > odl-l2switch-switch | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-switch-rest | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-switch-ui | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-hosttracker | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: HostTracker > > odl-l2switch-addresstracker | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: > AddressTracker > odl-l2switch-arphandler | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: ArpHandler > > odl-l2switch-loopremover | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: LoopRemover > > odl-l2switch-packethandler | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: > PacketHandler > > > > > > You can download distribution project and install " odl-l2switch-switch-ui " > which is same. > > > Here are the output from mininet console where ping worked succesfully for > the second time (since reactive mode will be learning hosts during first time > ping won't succeed for the first time.) > http://pastebin.com/YHm2raXD <http://pastebin.com/YHm2raXD> > > > > Please let me know if you any questions further. > > Regards, > Sai MarapaReddy > Brocade Communications > > On Wed, May 18, 2016 at 2:09 PM, Sai MarapaReddy <[email protected] > <mailto:[email protected]>> wrote: > Hi Selvakumar, > > I was able to ping. These are steps that i have followed, please let me know > any conflicts > > git clone l2switch project > git checkout master > cd l2switch/arphandler/config/src/main/resources/initial/ > change 54-arphandler.xml > cd l2switch/l2switch-main/config/src/main/resources/initial/ > change 58-l2switchmain.xml > cd l2switch > mvn clean install -DskipTests > i got success build > cd distribution/karaf/target/assembly/bin/ > ./karaf > Checking installed features :- > opendaylight-user@root>feature:list -i | grep l2 > odl-l2switch-switch | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-switch-rest | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-switch-ui | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: Switch > > odl-l2switch-hosttracker | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: HostTracker > > odl-l2switch-addresstracker | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: > AddressTracker > odl-l2switch-arphandler | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: ArpHandler > > odl-l2switch-loopremover | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: LoopRemover > > odl-l2switch-packethandler | 0.4.0-SNAPSHOT | x | > l2switch-0.4.0-SNAPSHOT | OpenDaylight :: L2Switch :: > PacketHandler > > > > > > You can download distribution project and install " odl-l2switch-switch-ui " > which is same. > > > Here are the output from mininet console where ping worked succesfully for > the second time (since reactive mode will be learning hosts during first time > ping won't succeed for the first time.) > http://pastebin.com/YHm2raXD <http://pastebin.com/YHm2raXD> > > Attaching topology for easy reference. > > Please let me know if you any questions further. > > Regards, > Sai MarapaReddy > Brocade Communications > > > > > > > > > On Tue, May 17, 2016 at 11:03 PM, Selvakumar Murugasekaran > <[email protected] > <mailto:[email protected]>> wrote: > Hello Luis Gomez, > > Good day to you. > > Thank you for your information. > > I installed the feature "odl-l2switch-switch-ui" only without karaf clean > after the changes done(Only start the karaf). > > I did retest after that, still I am able to reproduce this ping problem in > mininet. Topology is available in GUI(Refer:Topology with 16 switch.jpg) > > I am using the mininet version - 2.2.0b1 and OVS version - 2.3.2(Refer:CPU > and RAM details.txt) > > Please find the attachment for details about CPU/RAM of controller PC. > > Let me know if you need any more information. > > > Thanks and Regards, > Selvakumar Murugasekaran. > > On 5/18/2016 4:59 AM, Luis Gomez wrote: >> I just tried with mininet 2.2.1 and ovs 2.3.1 and it so works good for me. >> Some comments on you mail: >> >>> On May 17, 2016, at 10:01 AM, Luis Gomez <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Which mininet/OVS version are you using for this test? I will try this >>> later today. Also cc-ing l2switch people. >>> >>> BR/Luis >>> >>> From: Selvakumar Murugasekaran >>> [mailto:[email protected] >>> <mailto:[email protected]>] >>> Sent: Tuesday, May 17, 2016 3:45 AM >>> To: Daniel Farrell >>> Cc: Luis Gomez; Luis Gomez; [email protected] >>> <mailto:[email protected]>; >>> [email protected] >>> <mailto:[email protected]> >>> Subject: Reg: Ping is not working in mininet with ODL controller reactive >>> mode. >>> >>> Hello Daniel Farrell, >>> >>> Good day to you. >>> >>> I am using mininet(version 2.2.0b1) and ODL beryllium >>> controller(distribution-karaf-0.4.0-Beryllium.tar.gz) >>> >>> Currently I am doing benchmarking draft test for "Reactive path >>> provisioning time & rate" of ODL beryllium controller using mininet. >>> >>> I executed the following commands in controller PC, >> >> How much CPU/RAM had the controller PC? >> >>> >>> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64 >>> export JAVA_MAX_MEM=2072M >>> tar -xvzf distribution-karaf-0.4.0-Beryllium.tar.gz >>> ./distribution-karaf-0.4.0-Beryllium/bin/karaf >>> feature:install odl-restconf-all odl-l2switch-switch odl-openflowplugin-all >>> odl-dlux-all odl-openflowplugin-flow-services-ui odl-l2switch-hosttracker >> >> Optional: Looking at the installed features It is enough to install >> odl-l2switch-switch-ui to achieve all the above >> >>> >>> Then I did the following changes to make the ODL controller in reactive >>> mode, >>> >>> Location: [ODL-folder]/etc/opendaylight/karaf >>> I changed <is-proactive-flood-mode> to false from true in file >>> 54-arphandler.xml. Also changed <is-install-dropall-flow> to false from >>> true in file 58-l2switchmain.xml. >>> >>> After that I did ./karaf clean following by installed the following >>> feature’s, >> >> Optional: You do not need to do karaf clean, you can just start karaf >> normally after changing the config, so you skip next step (install features >> again) >> >>> >>> "feature:install odl-restconf-all odl-l2switch-switch >>> odl-openflowplugin-all odl-dlux-all odl-openflowplugin-flow-services-ui >>> odl-l2switch-hosttracker" >>> >>> Then I executed the following commands in mininet PC, >>> >>> mn --controller=remote,ip=33.33.33.1 --topo=linear,16 >>> --switch=ovsk,protocols=OpenFlow13 --mac >>> pingall >> >> pingall command never works in this mode, you have to start individual >> host2host pings like you do below: >> >>> h1 ping h10 >>> h1 ping h2 >>> h1 ping 11 >>> h1 ping h16 >>> exit >>> >>> The h1 ping upto h8 is working fine. >>> >>> The pingall, h1 ping h10 & h1 ping h16 is not working in above commands. >>> >>> Could you please help me to rectify this problem? >>> >>> Could you please clarify whether any other controller configuration need >>> for reactive mode? >>> >>> Note: Sporadically sometime h1 ping h2 also not working. >> >> One thing you could do is to check if the topology is correct in the UI, you >> see all hosts and links between switches. >> >>> >>> Result of OVS dump: >>> ================ >>> root@admin1-PDSM4:~# ovs-ofctl dump-flows s11 -O openflow13 >>> OFPST_FLOW reply (OF1.3) (xid=0x2): >>> cookie=0x2b00000000000071, duration=44.030s, table=0, n_packets=19, >>> n_bytes=1653, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 >>> cookie=0x2b00000000000071, duration=44.030s, table=0, n_packets=0, >>> n_bytes=0, priority=1,arp actions=CONTROLLER:65535 >>> root@admin1-PDSM4:~# >>> root@admin1-PDSM4:~# ovs-ofctl dump-flows s1 -O openflow13 >>> OFPST_FLOW reply (OF1.3) (xid=0x2): >>> cookie=0x2a0000000000005e, duration=104.694s, table=0, n_packets=3, >>> n_bytes=294, idle_timeout=1800, hard_timeout=3600, >>> priority=10,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:0a >>> actions=output:2 >>> cookie=0x2a0000000000005f, duration=104.694s, table=0, n_packets=3, >>> n_bytes=294, idle_timeout=1800, hard_timeout=3600, >>> priority=10,dl_src=00:00:00:00:00:0a,dl_dst=00:00:00:00:00:01 >>> actions=output:1 >>> cookie=0x2b0000000000005d, duration=113.056s, table=0, n_packets=24, >>> n_bytes=2040, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 >>> cookie=0x2b0000000000005d, duration=113.056s, table=0, n_packets=20, >>> n_bytes=840, priority=1,arp actions=CONTROLLER:65535 >>> root@admin1-PDSM4:~# >>> root@admin1-PDSM4:~# ovs-ofctl dump-flows s16 -O openflow13 >>> OFPST_FLOW reply (OF1.3) (xid=0x2): >>> cookie=0x2b0000000000007b, duration=114.483s, table=0, n_packets=23, >>> n_bytes=2001, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 >>> cookie=0x2b0000000000007b, duration=114.483s, table=0, n_packets=0, >>> n_bytes=0, priority=1,arp actions=CONTROLLER:65535 >>> root@admin1-PDSM4:~# >>> >>> Let me know if you need any more information. >>> >>> >>> Thanks and Regards, >>> Selvakumar Murugasekaran. >>> >>> >>> >>> >>> >>> >>> >>> >> > > > -- > Thanks & Regards, > Selvakumar M > > _______________________________________________ > L2switch-dev mailing list > [email protected] > <mailto:[email protected]> > https://lists.opendaylight.org/mailman/listinfo/l2switch-dev > <https://lists.opendaylight.org/mailman/listinfo/l2switch-dev> > > >
_______________________________________________ L2switch-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
