Try figuring out where your ping packets are getting dropped, if they are not going to the controller as a packet_in. Maybe on the source switch you can watch the packet counters to get an idea.
I've CC'd the l2-switch dev list in case they have some other ideas. Thanks, JamO On 01/09/2018 07:09 PM, S hj wrote: > > > Thank you for your reply. I installed nitrogen. > > In the scenario I am working on, there are only three wireless nodes running > OVS. My goal is to connect these three nodes as > SDNswitches together ( a line topology, s1---s2---s3). > > I followed the packets exchanged between switches and the controller to see > what happens. > > Based on openflow1.3, all messages exchanged correctly between switches and > the controller. Also, I can see the correct > discovered topology in ODL CLI. > > But, when for example "s1 ping s2", s1 doesn't send any packet_in message to > the controller to get the flow rules. Do you > have any suggestion? > > Thank you > > > > > > On Wed, Jan 3, 2018 at 3:17 PM, Jamo Luhrsen <jluhr...@gmail.com > <mailto:jluhr...@gmail.com>> wrote: > > Hi, > > Just a note that Beryllium is pretty old at this point. Our latest > release is nitrogen [0] if you want to work with something newer. > > I just checked our l2switch CSIT job [1] and it's passing, so I assume > that > l2switch features are ok there. Those jobs are using mininet to simulate > nodes/network. What does your setup look like? you mentioned ovs 2.6.1, > but > what kind of nodes are connected? how many switches in the network? > > btw, l2switch is not providing some kind of l3 routing service. It's > supposed > to implement spanning tree, afaik. > > You can debug a little more by looking at the flow tables on your > switches. > > Thanks, > JamO > > [0] > https://www.opendaylight.org/technical-community/getting-started-for-developers/downloads-and-documentation > > <https://www.opendaylight.org/technical-community/getting-started-for-developers/downloads-and-documentation> > [1] > https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-all-carbon > > <https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-all-carbon> > > On 01/03/2018 09:07 AM, S hj wrote: > > > > > > Hello, > > > > I installed l2switch feature. However, nodes still cannot ping each > other. I am using openvswitch 2.6.1 and Opendaylight > > Beryllium. > > > > I check the feature as: "*feature:info odl-l2switch-switch*" > > > > the result is: > > *Description:* > > * OpenDaylight :: L2Switch :: Switch* > > *Feature has no Configuration* > > *Feature configuration files: * > > * etc/opendaylight/karaf/58-l2switchmain.xml* > > *Feature depends on:* > > * odl-l2switch-hosttracker 0.3.0-Beryllium* > > *Feature contains followed bundles: * > > * mvn:org.opendaylight.l2switch.main/main-impl/0.3.0-Beryllium* > > *Feature has no conditionals.* > > * > > * > > * > > * > > In addition, I check the feature as: "*feature:info > odl-l2switch-switch-ui*" > > the result is: > > *Feature odl-l2switch-switch-ui 0.3.0-Beryllium* > > *Description:* > > * OpenDaylight :: L2Switch :: Switch* > > *Feature has no Configuration* > > *Feature ** has no **configuration files* > > *Feature depends on:* > > * odl-l2switch-switch-rest 0.3.0-Beryllium* > > * odl-mdsal-apidocs 1.3.0-Beryllium* > > * odl-mdsal-xsql 1.3.0-Beryllium* > > * odl-dlux-core 0.3.0-beryllium* > > *Feature has no bundles.* > > *feature has no conditionals.* > > * > > * > > Should I configure the features to see that nodes can ping each other? > > > > Thank you > > > > > > > > On Fri, Dec 15, 2017 at 2:27 PM, Jamo Luhrsen <jluhr...@gmail.com > <mailto:jluhr...@gmail.com> > <mailto:jluhr...@gmail.com <mailto:jluhr...@gmail.com>>> wrote: > > > > Hi, > > > > you can try l2switch (CC'd that dev list) application to see if > connectivity between > > switches will work. Once it's loaded and working properly, you > should start > > seeing links show up in the dlux topology view. > > > > the feature name is "odl-l2switch-all" > > > > Thanks, > > JamO > > > > > > On 12/15/2017 10:35 AM, S hj wrote: > > > > > > Hello, > > > > > > I am new to Opendaylight controller. I am trying to connect > three wireless nodes running openvswitch to > > Opendaylight(Beryllium). > > > > > > When I open the ODL delux, I can see the correct topology; > however, nodes cannot ping each other. Also, it shows > > the flow > > > tables are empty but when I check the flow tables in > openvswitches there are some drop-action rules. I have some > > questions > > > about this issue. > > > > > > Is there any default routing service in ODL to help these > three nodes to ping each other? Should I activate some > > features in > > > ODL for this routing? or I have to write my own module? > > > Also, there are a lot of links and tutorial for ODL and I do > not know how to start learning. Could you please > guide > > me how to > > > start learning ODL? > > > > > > > > > Thank you > > > > > > > > > _______________________________________________ > > > controller-dev mailing list > > > controller-dev@lists.opendaylight.org > <mailto:controller-dev@lists.opendaylight.org> > <mailto:controller-dev@lists.opendaylight.org > <mailto:controller-dev@lists.opendaylight.org>> > > > https://lists.opendaylight.org/mailman/listinfo/controller-dev > <https://lists.opendaylight.org/mailman/listinfo/controller-dev> > > <https://lists.opendaylight.org/mailman/listinfo/controller-dev > <https://lists.opendaylight.org/mailman/listinfo/controller-dev>> > > > > > > > > > > > _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
