...
Ghulam has already left that is why we are not hearing anything from his side. He might not be coming back. Sadia might have to do this all at on her own.
Maggie is not working due to no disk space. This might be a reason for trace routes not working. Anjum suggests that deleting some of the files in the tmp folder will resolve the issue.Arshad is applying for his visa. Hopes to be here end May start June. Does Arshad need a new invitation? Anjum will ask Arshad.
Anjum has looked at the invitation letter and found that there is no date specified on the invitation letter, therefore we dont need a new invitation letter. Arshad will be visiting US by the end of June.
...
Anjum did not submit the full or summary HEC report this month. He will submit both reports this month, Amber and Imadullah will prepare the report when Amber gets back to SEECS.
Pakistani Hosts
Amber will notify Joun of non working nodes. Did this happen? There are some Pakistani nodes that are recorded as working from SEECS while they are not working from SLAC. This mismatch was recorded by Amber and Joun. Amber and Joun will get together and see if the problem still exists or not.
...
PingER Archive Site - Ghulam
Wiki Markup
Sadia has partially implemented the new schema so now awaits finalization
...
Bilal submitted S Asia. Though S. Asia as a whole looks bad, Pakistan looks good (i.e. CBG is way better than GeoIP). This may be since the landmarks are not excluding a measurement to themself.
For South Asia, quest.seecs.edu.pk has high RTT and a distance of 816km for Islamabad nodes which is because the node is in Nawabshah Karachi but has the DNS entry of SEECS. Similarly, sbkwu.seecs.edu.pk has high error and large distance because the node is in Quetta but DNS entry is of SEECS. As Anjum can see, all the nodes that are showing bad results are the ones that have unstable behavior (i.e either they are unreachable most of the time or they have high RTTs).
...
Bilal needs to add the number of landmarks in the region for his Excel Spreadsheest. This will be useful for his paper, i.e. reporting typical accuracy as a function of landmarks in region.unmigrated-wiki-markup
Another interesting study would be whether using different alphas (in distance\[km\]=alpha*min_RTT\[ms\]*100\[km/ms\]) based on the alphas found in PingER for the various regions (see for example[http://www-wanmon.slac.stanford.edu/cgi-wrap/pingtable.pl?file=alpha&by=by-node&size=100&tick=daily&year=2012&month=03&from=United+States&to=United+States&ex=none&only=all&dataset=new&percentage=any]) provides much benefit compared to the single current value of alpha. To facilitate this we have added PingER groups for N.AMERICA, EUROPE, AUSTRALASIA, S.ASIA, S.AMERICA.
Bilal will be sending the tulip draft paper before he leaves the job
...
- There can be a paper about Pinger if we could just find the right conference. MCN, ICC and Globecomm do provide network monitoring topics. It could talk of the various metrics and their importance (in particular; MOS, Alpha, max RTT, min RTT), the lessons learnt from running such a worldwide infrastructure, the uses of the data etc.
- We can talk of GEO-Location experiences. For example within Pakistan it works fine, however as we go within regions or continents this gets worse. We can publish some stats on that for example. We can add the impact of changing alpha. We can also indicate the importance of landmark proximity.
Wiki Markup - Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable.
- 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)? There are 2 students working on the PingER archive. Is this something they could work on?
- [Fix PingER archiving/analysis package to be IPv6 conformant|IEPM:Make PingER IPV6 compliant]. Will build a proposal for an IPv6 testbed. They will try various transition techniques. A proposal has been prepared and that has been submitted to PTA. Adnan is a co PI. It is being evaluated today. A small testbed has been established in SEECS and the plan to shift some of the network to IPv6. Bilal is part of 3 students involved with PingER and they will be involved with IPv6. They are porting the PingER archive site site to using a database. They have redeveloped the archive site using Umar's documentation. They have set up a small test archive site. They have gathering, archiving, analysis. They will design a new database. They will also try a port of PingER to IPv6.
- Look at RRD event detection based on thresholds and how to extend, maybe adding plateau algorithm. Umar's algorithm did not work in a predictable manner.
- Provide near realtime plots of current pinger data using getdata_all.pl/wget. It will work as a CGI script with a form to select the host, the ping size, and the time frame to plot. It will use wget or getdata_all.pl to get the relevant data and possibly RRD/smokeping to display the data.
...