[Mini-NDN] Interfaces went down in minindn
Lan Wang (lanwang)
lanwang at memphis.edu
Tue Apr 19 06:58:18 PDT 2016
Navdeep: I can’t think of any reason.
Ashlesh: please set up a video conference call with Navdeep so that you can see every step he takes. You can use Bluejeans (https://memphis.bluejeans.com/) provided by the university.
Lan
> On Apr 19, 2016, at 8:54 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu> wrote:
>
> Hi Lan,
>
> Thank you for the reply. I tried performing the experiment on virtual box but still I am facing the same issue. I even tried with the completely new setup but with no success.
> The data arrives for initial 20-25% of interests but after that no data packet arrives.
>
> OS: Ubuntu 14.04 LTS trusty
> VirtualBox: Version 5.0.18 r106667
> NFD version : 0.4.1
> Mini-NDN version : 0.1.1
> Mininet version : 2.2.1
>
>
>
> Best Regards,
> Navdeep Uniyal
>
>
> -----Original Message-----
> From: Lan Wang (lanwang) [mailto:lanwang at memphis.edu]
> Sent: Montag, 18. April 2016 16:58
> To: Navdeep Uniyal
> Cc: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu
> Subject: Re: [Mini-NDN] Interfaces went down in minindn
>
> We have not used openstack server. Can you use a Virtualbox VM (or no VM at all) and the setup we sent you to see if it works? If so, then the problem may be related to the openstack setup (and how mini-net works with it I suspect).
>
> Lan
>
>> On Apr 18, 2016, at 9:50 AM, Navdeep Uniyal <navdeep.uniyal at neclab.eu> wrote:
>>
>> Hi Lan,
>>
>> I am running the setup in an openstack server with 16GB RAM, 160GB Harddisk and 16 Virtual CPUs.
>>
>> Mini-NDN version : 0.1.1
>> Mininet version : 2.2.1
>>
>>
>> Best Regards,
>> Navdeep Uniyal
>>
>> -----Original Message-----
>> From: Lan Wang (lanwang) [mailto:lanwang at memphis.edu]
>> Sent: Montag, 18. April 2016 16:44
>> To: Navdeep Uniyal
>> Cc: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu
>> Subject: Re: [Mini-NDN] Interfaces went down in minindn
>>
>> Are you using a virtual machine? If so, what type? Also mininet version and mini-ndn version?
>>
>> Lan
>>
>>> On Apr 18, 2016, at 9:04 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu> wrote:
>>>
>>> Hi Ashlesh,
>>>
>>> Sorry to bother you again.
>>> The NFD version I am using is 0.4.0 (0.4.0-18-gffe8bbb).
>>> OS: Ubuntu 14.04 LTS trusty
>>> ndn-cxx: 0.4.1
>>>
>>> I tried your mini-ndn folder. Surprisingly it worked well for initial 4 round of experiments but again it went into the same issue of packet drop.
>>>
>>>
>>> Best Regards,
>>> Navdeep Uniyal
>>>
>>>
>>> -----Original Message-----
>>> From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu]
>>> Sent: Freitag, 15. April 2016 22:27
>>> To: Navdeep Uniyal; mini-ndn at lists.cs.ucla.edu
>>> Subject: RE: [Mini-NDN] Interfaces went down in minindn
>>>
>>> Hi
>>>
>>> I cannot reproduce the timeouts with your version of the files as well. I have made sure that nfd.conf is the one that you sent me with CS set to zero.
>>>
>>> I have attached my ndndump logs, my mini-ndn folder, traffic client and server logs.
>>> I don't see any timeouts in the ga-traffic-client-logs.
>>> Can you try with my mini-ndn folder?
>>>
>>> Also, please describe your environment (Machine, OS, Versions of ndn-cxx, NFD, etc).
>>>
>>> Ashlesh
>>> ________________________________________
>>> From: Navdeep Uniyal [Navdeep.Uniyal at neclab.eu]
>>> Sent: Friday, April 15, 2016 5:26 AM
>>> To: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu
>>> Subject: RE: [Mini-NDN] Interfaces went down in minindn
>>>
>>> Hi Ashlesh,
>>>
>>> Another observation, If we check the ndndump files, only one interface is showing traffic in both the directions while for others, only incoming interests can be seen for the whole duration.
>>>
>>>
>>> Best Regards,
>>> Navdeep Uniyal
>>>
>>> From: Mini-NDN [mailto:mini-ndn-bounces at lists.cs.ucla.edu] On Behalf
>>> Of Navdeep Uniyal
>>> Sent: Donnerstag, 14. April 2016 10:55
>>> To: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu
>>> Subject: Re: [Mini-NDN] Interfaces went down in minindn
>>>
>>> Hi Ashlesh,
>>>
>>> I tried the changes you suggested but I could find no improvement. Also, in the attached screenshot I could see a bit variance from the experiment I am trying to execute. The Name is different( In my case there are multiple files under the namespace "/ndn/nle") with different traffic percentage from yours. I have attached the traffic configuration files and nfd.conf file(as in NFD configuration CS Store size is zero). Please verify it once.
>>>
>>>
>>> Regards,
>>> Navdeep Uniyal
>>>
>>> From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu]
>>> Sent: Donnerstag, 14. April 2016 00:13
>>> 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
>>>
>>>
>>> Hi
>>>
>>>
>>>
>>> Can you try doing the following two things and see if you still get timeouts:
>>>
>>>
>>>
>>> 1) Comment the highlighted lines, as you already do this in setup
>>> def run(self):
>>> for host in self.net.hosts:
>>> if host.name == 'ga':
>>> #host.cmd("nfdc register /ndn/nle udp4://1.0.0.6")
>>> #host.cmd("nfdc register /ndn/nle udp4://1.0.0.10")
>>> #host.cmd("nfdc register /ndn/nle udp4://1.0.0.14")
>>> host.cmd("nfdc set-strategy /ndn/nle ndn:/localhost/nfd/strategy/best-rou$
>>> print("ga Done")
>>> elif host.name == 'sa':
>>> host.cmd("ndn-traffic-server -c 200000 /home/ashu/Desktop/ndn-src/ndn-tra$
>>> print("sa done")
>>>
>>> 2) Modify the traffic server line as follows (remember to use your own path, the traffic-server.conf):
>>>
>>> ndn-traffic-server -c 200000
>>> /home/ashu/Desktop/ndn-src/ndn-tradn-traffic-generator/ndn-traffic-se
>>> rver.conf.sample 2&> traffic-server-logs &")
>>>
>>>
>>>
>>> (This is just redirecting the output to a file - did this to trace the problem).
>>>
>>>
>>>
>>> After making these two modifications (don't know if the first one helped with anything) I cannot reproduce the timeouts no matter what.
>>>
>>> I even sent 100,000 interests with 1ms interval - 0% timeout.
>>>
>>>
>>>
>>> [cid:image001.png at 01D19711.FC01F540]
>>>
>>>
>>>
>>> Ashlesh
>>>
>>> ________________________________
>>> From: Navdeep Uniyal
>>> <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>>
>>> Sent: Wednesday, April 13, 2016 6:12:33 AM
>>> To: Ashlesh Gawande (agawande);
>>> mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>;
>>> nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>; Junxiao
>>> Shi;
>>> ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
>>> Subject: RE: [Mini-NDN] Interfaces went down in minindn
>>>
>>> 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<mailto:mini-ndn at lists.cs.ucla.edu>;
>>> nfd-dev at lists.cs.ucla.edu<mailto: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
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mini-NDN mailing list
>>> Mini-NDN at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>>
>
More information about the Mini-NDN
mailing list