...
Invitees:
Anjum+, Hassaan Khaliq+, Kashif?, Raja+, Johari+, Nara, Abdullah, Badrul, Ridzuan-, Ibrahim, Hanan, Saqib+, Adib, Les+, Renan-, Bebo-
+ Confirmed attendance
- Responded but Unable to attend:
Kashif will be in Faisalbad, and will try to attend.
Actual attendees:
Anjum, Hassaan, Raja, Saqib, Les
Administration
Hassaan has been added to the pinger-my email list.
- UUM are interested to host a PingER workshop at UUM in 2014. However, they have two issues, one is the budget (they need to run this workshop on cost recovery basis); second is their commitment to MYIGF which is hosted by UUM (btw 12-13 august). There was no update 3/5/2014. We need an update. Adib was not on the 3/26/2014 meeting. Johari will try and contact Adib. It is not looking good for June/July time frame, maybe at the end of the year.
Renan
Renan realized that testing on Virtuoso is going to take longer than he thought because of the big number of triples. Any progress? No response 3/25/2013.
Renan completed writing the paper on Linked Open data access to PingER data. Bebo & Les have reviewed and commented. It was submitted to the Stanford conference March 1st, 2014. The deadline for the submission was extended from March 1st to March 15. The notification is May 1st, the final submission is May 9th, conference is May 27-31. Poster submissions are due April 4th, we might submit a poster just in case. The acceptance rate is very low. Information on the conference is at http://www.scienceengineering.org/ase/conference/2014/bigdata/sanjose/website/paper-submission/.We (Renan, Bebo, Ibrahim and Les) had a Skype meeting to introduce Renan and Ibrahim, go over strategy and also to discuss Ibrahim's work (see below).
The UFRJ host is successfully running again.
...
Badrul plans for his undergraduate student (Abdulrahim Haroun Ali) to have a draft paper on anomalies in PingER measurements to share for review by the end of semester (January). No update 3/5/2014, 3/26/2014.
Ridzuan is studying a new version of Apache Hadoop 2.0 which is able to perform processing of big data (both streaming and batch processing). They are suggesting a new framework that will adopt selected new modules in Hadoop 2.0 to detect anomalies in Malaysia internet traffic. They'll come out with a proposal first and will share it when it is ready.
...
No progress 2/19/2014. Johari was not on the call 3/5/2014.
The Raspberry Pi is at the data centre , but due to miscommunication, the public ip which was previously assigned to the rasp pi unit has been assigned to another server. So now Johari has to wait for the ip to be reassigned back to rasp pi unit and give new ip to the other server. They suggested a new ip for the rasp pi unit but Johari wanted to have the old one so that we do not have to update the record at slac for the archival process, etc
The tool to enable synchronizing Malaysian monitors is completed. It provides the ability to add, edit and delete nodes. Raja has tested and after a mod was made to replace a private IP address it is working well. Johari provided information to Saqib on trying it out. How did it go?
and has a public IP address. The private IP address works but not the public. Johari will pursue.
The tool to enable synchronizing Malaysian monitors is completed. It provides the ability to add, edit and delete nodes in the HostList. Raja has tested and after a mod was made to replace a private IP address it is working well. Johari provided information to Saqib on trying it out. Saqib successfully used tool and updated it. Johari will add an account for Badrul to use it. Saqib requested to add sorting the HostList by country, Johari will add this.
The traceroute server at The traceroute server at http://pinger2.unimas.my/cgi-bin/traceroute.pl has the same problem as before. They know (sort of) the problem but haven't got the chance to rectify it (mapping NAT address, needs to be added). There is no progress 12/4/2013, 1/8/2013, 1.22.2014, 2/5/2014, 3/26/2014. Now that the historical traceroutes are working for UM (see below) there is an extra incentive to get the reverse traceroute working at UTM and UNIMAS
...
Johari has a research Johari has a research student who finalized a proposal in order to officially apply for his masters. He will start in February. He is currently working on threshold/anomaly detection, and will extend to correlating performance over multiple routes. He will share the proposal with Les and others in the next 2 weeks to get reviewsApril.
UTMNo progress 2/19/2014
Saqib has received an official letter regarding the successful selection of research assistant-ship at UTM.
Saqib submitted an FRGS 2014 proposal for 36 months. Can we share it?
Saqib is working with the IT department in UTM to solve the problems of delays in traceroute. They have a new ISP. Now the pinger server is working with single static IP (161.139.68.188) both for intranet and internet. Previous internet IP 161.139.146.158 is removed. Again given the new historical traceroute facility (see below), it is important to get this working.
- No load balancing is involved as UTM is working with single ISP.
- Still the problem of the delay in traceroute is not solved. It appears to be due to the DNS lookup delay.
Saqib has started a case study of Malaysian hosts seen from Malaysian Monitors. The case study is identifying the need for the Malaysian monitors to collect traceroutes to their target hosts daily. SLAC has a script to facilitate this, for routes seen from SLAC, that could be adapted for other sites. The latest copy of the word file was shared with Badrul and Johari. No update 2/5/2014. We need an update.
UUM
Adib was unable to attend the meeting. He provided an update by email: "The PingER monitor will be up soon" . Update requested 3/21/2014.
NUST
("A Fundamental Active Internet Performance Monitoring Framework for Malaysian Research & Education Network") for 36 months. Proposes to submit another in ERGS or E-Science grants. He is in discussions with his PhD. superviser to get the requirements.
The new historical traceroute facility makes it important to get the traceroute server workling at UTM. No progress 3/26/2014.
Saqib has started a case study of Malaysian hosts seen from Malaysian Monitors. He has updated the remote host list on UTM Pinger (Malaysian & S.E Asia) and remote host xml tool. In the next two weeks, he will finish the case study of Malaysian hosts seen from Malaysian Monitors.
UTM pinger server is now running with an updated version of pinger.xml file using the tool provided by Dr. Johari. Saqib has updated the data on remote host management page with all S.E Asia nodes. Now UM and UNIMAS can synchronize their host list. The list is available here.
UUM
Update requested on the status of the PingER host at UUM, 3/21/2014, 3/24/2014. No response.
NUST
Kashif returns next week. Joun leaves soon for Saudi Arabia. Anjum will request Arshad to get a replacement, he is unsure if one will be forthcoming. In any case for some time there will only be Kashif at SEECS supporting PingER.
The PingER monitor at SEECS/NUST (maggie1) is being rebuilt on a different computer following a crash. There are 2 approaches thta can be tried in parallel:
- Rebuild from scratch. in the initial case Umar took 2-3 weeks. He wrote documentation, so this will be a test of the documentation. This could be valuable should Malaysia or another site decide to set up an archive. Kashif and Joun are ready to start on this.
- Dump and restore the database. This is much easier. However it requires the database password. Les will contact Umar to see if he can provide the password. Umar canot logon to maggie1 since it is blocked by the firewall.
- Umar & Les provided the root password, the database password can be derived from this. Update requested 3/21/2014.
They could not get the database password from anyone. However as a last option they cracked and made a dump of the database for backup. That machine (maggie1) is still infected and it is not possible to make it UP at its present state. Since Joun is leaving this job (family shifted to Saudi arabia) so the process of its trouble shooting will resume as Kashif returns to Islamabad.
As an alternate solution they prepared another machine as a monitoring node and gave it the IP & DNS of maggie1. Also they installed the Beacon list file in it at the required path which is accessible and downloadable from other monitoring nodes. With that, now nodes are being UP again one by one, by updating Beacon list from new maggie1 machine. So at least SLAC can ping and have data of Pakistani Monitoring Nodes in its database.
The BeaconLists at NUST and SLAC are out of sync. Raja compared the two pinger.xml files. It turns out NUST was not using the HostList for the non Beacons and so Pakistani monitors have an expanded BeaconList which was updated from SEECS. Raja has explained this to NUST and believe it will be easy to synchronize. Kashif asked about the definition of Beacons. Les updated the web page at http://www-iepm.slac.stanford.edu/pinger/beacon.html. Hopefully this helps. However, Anjum pointed out that due to restrictions imposed at the at the PERN PoPs (limit number of hosts monitored, do not allow monitoring of non Pakistani hosts, do not provide full access permissions to the monitor) they cannot use the standard SLAC based beacon list. Anjum will talk to Arshad. Maybe the PERN PoPs should use a different Beacon list kept at SEECSThe BeaconLists at NUST and SLAC are out of sync. Raja will compare the two pinger.xml files. It turns out NUST was not using the HostList for the non Beacons and so had an expanded BeaconList which was updated from SEECS. Raja has explained this to NUST and believe it will be easy to synchronize. Update requested 3/21/2014.
Hassaan reports that they have established contact with people in Bahawalpur. The contact person forwarded the request to higher authorities for approval of PingER deployment. Same status 3/5/2014PingER deployment. Bahawalpur are not responding. When Kashif returns SEECS will try again. Anjum has some contacts from Bahawalpur at UM who may be able to help. He will contact them before Monday.
The installation of PingER at Sahiwal is complete. It just needs the Beacon List. Update requested 3/21/2014 This awaits Kashif's return.
Quest.seecs.edu.pk has been restored to a working state
...
Anjum pointed out that there are working PingER monitors that SLAC appears unable to gather data from. An example is the Comsats host. Les discovered that SELInux needed to be disabled. it is working now. Are there other such hosts, update requested 3/21/2014?
TULIP - Raja
Raja has added the ability to insert a captured traceroute into VTrace to get its route visualized. Try it at http://www-wanmon.slac.stanford.edu/cgi-wrap/reflector.cgi?function=vtrace. We are looking to add a link to it from the perfSONAR home page.
...
We have sent a reminder email to Yahoo giving them an update on TULIP and how it might be extended to meet their needs. They have responded, they appear to be interested. We are trying to interest them in providing landmarks. No update 2/18/2013, 3/26/2014.
PingER at SLAC
Raja has also re-written the historical traceroute facility that takes nightly traceroutes and allows one to retrieve and compare them. He then extended it to use the reverse traceroute facility to provide histories for NUST, CERN, UM as well as SLAC. When the UNIMAS and UTM traceroutes work, we can include them. See for example http://www-wanmon.slac.stanford.edu/cgi-wrap/traceroutearchive.cgi
...
Anjum suggested Saqib, Badrul and Johari put together a paper on user experiences with using the Internet in Malaysia as seen from Malaysian universities. In particular round trip time, losses, jitter, reliability, routing/peering, in particular anomalies, and the impact on VoIP, throughput etc. It would be good to engage someone from MYREN.
Potential projects
Future meeting - Les
Next meeting Wednesday March 19th April 9th 2014 9:00pm Pacific Standard Time, Thursday March 20th April 10th 2014 9:00am Pakistan time, Thursday March 20thApril 10th, 2014 noon Malaysian time, Thursday March 20thApril 10th, 2014 02:00am Rio Standard Time.
...