...
Pakistani case study – Zafar, Anjum
We need to make some progress on the Pakistani case study soon.
- aiou, lhr (never any data), nwfpuet, uettaxila, uob are down for many days: see http://www-iepm.slac.stanford.edu/monitoring/checkdata/).
- UOB is being worked on, by Amber who is in Quetta together Kashif Satar. Once they return from Quetta they will work on uetaxila and nwfpuet
- There has never been any data from pinger-rcp.pern, hu (Hazara), kohat, nca, pwr.nu, ustb, since though the hosts are in the NODEDETAILS database there is no dataserver entry for each of them in the database. Should there be? They are identified as monitors. Zafar looked at aiou. Email has been sent to all of them. If no reply will call them. Most of these people are cooperative. NCA have made contacts so expect progress. The last mile for Kohat is very poor, may be dialup.
- Dr. Anjum is verifying that table.pl at SEECS has all the known Pakistani monitors. Need to study improvements with pingtable.pl time series and the smokeping plots where we have them. If something has been recommended by our measurements and that has happened and made things better that is very important for the case study.
- UET, UOB, LSE, COMSATS do not have the full set of Pakistani beacons. See matrix. The Pakistani monitoring nodes are supposed to get the beacon list from SEECS. – Anjum said he has a student who can fix but need password so they can fix the nodes so they get the list from the SEECS server. They are fetching their beacons from SLAC. Anjum is requesting admins to fix. Working on it, but response from admins is not good.
- We need to understand the high ping losses for UAAR. Sadia please put together a case study. Zafar discussed with Sadia and she has started something and it will go in the HEC report. It seems to have cleared up in November.
- 111.68.102.40 = PK.LSE.EDU.N3 needs to have a name registered in DNS.
- Les fixed a problem in table.pl which was not counting nodes which only have an IP address.
HEC Peshawar
: pinger-rcp.pern.edu.pk
Same . Same status as conveyed earlier, contact person and admisnistration
there administration there need formal approval from DG IT HEC Islamabad
AIOU Islamabad
: pinger.aiou.edu.pk/
Node . Node seems to be down
have down have talked to contact person
emailed person emailed for getting feedback
Hazara University
its : its installation was not complete, added in pinger database earlier
talked earlier talked to contact person, they need system for deployemnt as per
previous per previous promise made in peshawar workshop
will workshop will take up this node as fresh deployment
FAST Lahore
: lhr-nu.edu.pk/
Node Node seems to be down
have down have talked to contact person
emailed person emailed for getting feedback
Kohat University
: pinger.kohat.edu.pk
unable . unable to contact on cell and ptcl
have ptcl have emailed for status
will status will track this as well
University of blochistan
balochistan: pinger.uob.edu.pk
node . node is down for the time beinghad discussed it during workshop in quetta
node quetta node will be UP sooner, we will take this up in quetta schedule
Despite the lack of progress on the above items there is enough valuable information to get going on the Pakistani case study. Sadia is working on statistcis for the HEC report which will be incorporated into the Pakistani case study. It will have a summary and Appendix. They are focusing on an inter-regional study. This will include routing paths and anomalies, with summary graphs.Tthey They are picking one or two nodes per region and then study from it to all other regions. They did not make the Nov 20th date due to Eids. That has been a problem that Anjum has managed to work around. The subsequent reports will be monthly on 15th of the month. Expect to finish by Wednesday next week. Zafar is trying to keep the report below 50 pages.
Sadia has unearthed a problem in smokeping at SEECS. Is anyone looking at it?. It has been fixed. She also unearthed a problem in table.pl which has also been Fixed. Well done Sadia in unearthing and reporting the problems.
Progress on ICFA Report 2011 - Zafar
Integrate into the report.
...
I have extended the African case study to add BGP prefixes and pinger metrics for Africa.
PingER
We added another monitoring host this time in Egypt.
PerfSONAR
Zafar has deployed bandwidth and latency. He believes they are working, but has not seen any graphs so far.
...
- Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable.
- Extend the PingER map (also use for Pakistani to Pakistani subset map for the case study) - Faisal has taken this on.
- This adds ping, traceroute, access to database etc.
- The advantage compared to other traceroute maps is that the laundering keeps only good servers
- Add in Viper capabilities (i.e. paths with coloring)
- Get the MatLab license at SEECS and put up a CGB server using it. They had a licenses, it had limited capability and it has expired. Zadar will talk to Ali Khayam to get another license. In the meantime Zafar has a matlab version to work with. Basically the client will call the reflector with the target. The reflector will return the landmarks and RTTs. These (landmarks and RTTs) will be passed to the CBG code that will look up the database for the lat/longs of the landmarks (alternatively the CBG could be passed just the lat/longs andnot need the database, however this may make debugging harder) and then using these lat/longs together with the RTTs find the target and errors. Zafar has 1 graduate (MS) student who can work on re-implementing CBG in Java. There are 2 students working on the PingER archive.
- All of our geolocation techniques are in Java and since there is no sort of a front-end back-end abstraction layer, best solution is to go with re-implementation.
- Since all of geolocation code is a single project, integrating CBG as a separate class will be better than trying to create a platform where CBG can talk to the rest of the infrastructure. This way in case of failure we will have just one point to deal with, instead of two. We won't be required to setup extra logging on the second machine running MatLab.
- Neither will there be communication overhead due to over-the-internet communication and nor will there be cross-platform issues.
- Extend Checkdata to provide emails automatically, see https://confluence.slac.stanford.edu/display/IEPM/Extend+checkdata+to+make+it+more+useful
- Add MOS to pingtable.pl see https://confluence.slac.stanford.edu/display/IEPM/Add+Mean+Opinion+Score+%28MOS%29+to+pingtable.pl+metrics is Radia interested, she will start work on it when done with HEC report, also she is working on her masters classes done, writing thesis.
- Improve the PingER2 installation procedures to make it more robust. This might be something for the person(s) in Pakistan who are responsible for installing PingER2 at the Pakistani monitoring sites. They probably have found where the failures occurs. Also look at the FAQ, and ping_data.pl which has been improved to assist in debugging, could it be further improved (e.g. provide access to the httpd.conf file so one can see if it properly configured)?
Future
Zafar's and Arshad's letters of invitation were sent 11/29/2010.
...