[Ndn-interest] [Mini-NDN] Interfaces went down in minindn

Navdeep Uniyal Navdeep.Uniyal at neclab.eu
Wed Apr 13 04:12:33 PDT 2016


Hi Junxiao,

Please if you can advise me on this. This issue is blocking our testing for a long time now and I am not able to rectify it.


Best Regards,
Navdeep Uniyal

From: Mini-NDN [mailto:mini-ndn-bounces at lists.cs.ucla.edu] On Behalf Of Navdeep Uniyal
Sent: Dienstag, 12. April 2016 12:29
To: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu; nfd-dev at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Interfaces went down in minindn

Hi Ashlesh,

Thank you for your help. I changed the experiment as you suggested and tested it again.


1.       I found interests moving from the host to the server but data not coming in.

2.       Yes the occurrence of error is after quitting minindn as you said and only after quitting miniNDN, requested data is coming in and is marked as unsolicited.

I could not find the issue why data generation suddenly stops as ndn dump and nfd logs could not provide proper clue.

I am attaching my configuration files, logs and dump files. Also, adding nfd-dev list to this mail if someone could help in this regard.

Steps to redo the experiment:

1.       Install experiment nletest.py on minindn using "install.sh -i"

2.       Copy topology file nectopo.conf to /{path to minindn}/ndn_utils/topologies

3.       Copy traffic generator server and client files "ndn-traffic-client.conf" and "ndn-traffic-server.conf" to /{path to ndn traffic generator}/ndn-traffic-generator/build.

4.       Run sudo minindn --experiment=icnle nectopo.conf

5.       On Mininet CLI> ga ndn-traffic -c 1000 -i 100 /home/mininet/mini-ndn/ndn-traffic-generator/build/ndn-traffic-client.conf



Best Regards,
Navdeep Uniyal


From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu]
Sent: Montag, 11. April 2016 22:08
To: Navdeep Uniyal; mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] Interfaces went down in minindn


Some observations:



1) I think the "interface went down" error appears when you quit Mini-NDN and NFD is killed.



2) When I tried interval as 1ms (count: 1000) - no loss for the first 4 tries,  on the 5th time I see the same problem.



3) I turned on ndndump and found that sa suddenly stops responding with data - not sure why. For some time, it seems, interest do reach sa without it responding.



Can you modify your experiment as below and trace interest/data and see if you can find where it fails:


    def setup(self):
       for host in self.net.hosts:
                for intf in host.intfNames():
                        ndnDumpOutputFile = "dump.%s_%s" % (intf, str(host.intf(intf).IP()))
                        host.cmd("sudo ndndump -f '.*nle.*' -i %s > %s &" % (intf, ndnDumpOutputFile))
                if host.name == 'ca':

Ashlesh
________________________________
From: Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>>
Sent: Monday, April 11, 2016 7:37:37 AM
To: Ashlesh Gawande (agawande)
Subject: RE: [Mini-NDN] Interfaces went down in minindn


Hi Ashlesh,



Please do let me know if there are some updates on the issue.



Best Regards,

Navdeep Uniyal



From: Navdeep Uniyal
Sent: Freitag, 8. April 2016 09:48
To: 'Ashlesh Gawande (agawande)'
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: RE: [Mini-NDN] Interfaces went down in minindn



Thank You Ashlesh,



The results are similar for me.



Best Regards,

Navdeep Uniyal



From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu]
Sent: Freitag, 8. April 2016 00:52
To: Navdeep Uniyal
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] Interfaces went down in minindn



Okay I looked at your experiment and modified my ndn-traffic-client/server appropriately.



Initially all the interest are answered correctly.

Then you start to see some timeouts.

Then all interests time out.

My total interest loss was ~25%.



I am looking into it further.



Ashlesh

________________________________

From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>
Sent: Thursday, April 7, 2016 5:12 PM
To: Navdeep Uniyal
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] Interfaces went down in minindn



Is this ndn-traffic-client.conf the default one?

Ashlesh

________________________________

From: Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>>
Sent: Thursday, April 7, 2016 2:58 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>; Lan Wang (lanwang)
Subject: RE: [Mini-NDN] Interfaces went down in minindn



Hi Ashlesh,



PFA the attached files I used for experiments.

"nectopo.conf" is the topology file

"nletest.py" is the experiment file





sudo minindn --experiment=icnle nectopo.conf

On Mininet CLI > ga ndn-traffic -c 1000 -i 10 /home/mininet/mini-ndn/ndn-traffic-generator/build/ndn-traffic-client.conf







Best Regards,

Navdeep Uniyal



From: Lan Wang (lanwang) [mailto:lanwang at memphis.edu]
Sent: Donnerstag, 7. April 2016 01:22
To: Navdeep Uniyal
Cc: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] Interfaces went down in minindn



Ashlesh,



Maybe Navdeep can give you his setup files and you repeat his experiment?

Lan



On Apr 6, 2016, at 10:32 AM, Navdeep Uniyal <navdeep.uniyal at neclab.eu<mailto:navdeep.uniyal at neclab.eu>> wrote:



Hi Ashlesh,



Thank you for the reply. The interest sending rate is 100/sec although I checked it with 10/sec. In both the cases I found similar results. Interesting is the data generation and arrival time. The data transfer behaves perfectly fine for initial few interests while after a certain time it just stops and the requested data then is arrives just after the interfaces goes down(I guess mostly when I am stopping the Mininet topology) and are marked as unsolicited data.

I could not get this behavior if it is because of link issues, NFD issue or NDN Traffic generator issue. I tried asking the solution on the other nfd-dev mailing list but could not get any response.





Best Regards,

Navdeep Uniyal



From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu]
Sent: Mittwoch, 6. April 2016 16:40
To: Navdeep Uniyal; mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: Interfaces went down in minindn



What is the rate of sending interests?

Can you try lowering it and see if interest drops are decreased?

Ashlesh

________________________________

From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>>
Sent: Wednesday, April 6, 2016 3:52 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] Interfaces went down in minindn



Hi everyone,



I have been running some experiments using minindn using NDN traffic generator for interest and data generation. I am facing a few issues as I am unable to get the data packets in response after a certain period of time. In my configuration I am making cs store size to be zero so that all interests can reach the producer. While investigating the issue of interest drops I found few errors in the nfd logs. Below are the few errors which I am getting in the log file:



1459932297.745268 ERROR: [EthernetTransport] [id=264,local=dev://sa-eth0,remote=ether://[01:00:5e:00:17:aa]] pcap_next_ex failed: The interface went down

1459932297.761311 ERROR: [EthernetTransport] [id=263,local=dev://sa-eth1,remote=ether://[01:00:5e:00:17:aa]] pcap_next_ex failed: The interface went down

1459932297.777269 ERROR: [EthernetTransport] [id=262,local=dev://sa-eth2,remote=ether://[01:00:5e:00:17:aa]] pcap_next_ex failed: The interface went down



Due to this, the interests are not getting satisfied. Attached are the nfd logs of the producer(similar errors are being observed on the other nodes as well). Please if someone can help me resolving the issue.







Best Regards,

Navdeep Uniyal



_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160413/4e06f075/attachment.html>


More information about the Ndn-interest mailing list