...
Badrul (6/23/2014) is still awaiting hearing from his student (Abdulrahim Haroun Ali who is out of the country) on the paper on anomalies in PingER measurements and will update later once the paper ready. For the minute the paper is not ready. No update 8/20/2014, 10/16/2014.
Ridzuan and Ibrahim both requested for additional space. We require an infrastructure update for the cloud because the existing storage space is not enough, given a number of other users. The 5 Tera byte SAS along with some blade servers all have minimum 1Gig interfaces. We are in process of purchasing the switch to support the networking. Once available, we shall be able to provide the capacity for one instance of SLAC data.
UNIMAS
Pinger 2 Pinger2 (Raspberry Pi) has been running successfully since ran successfully from Sept 2nd . See ePingER project Malaysia for recent plots of data from pinger and pinger2.unimas.my (Raspberry Pi).
Traceroute server: Status unsolved. The problem is the same on Pinger2. Johari talked to the network administrator at the centre about this issues and he suggested to talk to the security manager to check whether the firewall is blocking the icmp packer from the traceroute command (to do list). No progress 9/17/2014.
to October 23. We have been unable to gather data since. It still responds to pings. The graphs below show the RTTs from SLAC to www, pinger and raspberry pi at UNIMAS. At first glimpse they are very similar. www & pi are probably closer together (more jitter and lower loss) in RTT performance than pinger. To quantify one would need to do a frequency analysis and possibly a Kolmogorov/Smirnov test.
It might be more instructive to look at the data from pinger and raspberry pi to Malaysia since the distances are shorter and the differences may show up better. For Sep-Oct 2014 when there was data measured from both Oct-Nov the averages for 20 paths was 52+-21ms (from pinger.unimas.my to 20 other Malaysian hosts) and 56+-21ms for raspberry pi to 20 other Malayisn hosts.
Traceroute server: Status unsolved. The problem is the same on Pinger2. Johari talked to the network administrator at the centre about this issues and he suggested to talk to the security manager to check whether the firewall is blocking the icmp packer from the traceroute command (to do list). No progress 9/17/2014.
...
After revision the FRGS proposal was submitted to RMC. It is under review, expect feedback at the end of October.
Saqib is updating the case study from time to time. It just need some formatting. He will send it out in the coming week. This is needed for the workshop.
pinger.fsktm.utm.my can't traceroute.pl or ping_data.pl
Saqib Saqib will see if he can modify pinger monitoring hop 6 of the traceroute.pl from UM to UNIMAS. He does have access to the pinger monitor at UM. We will be looking for whether there are any patterns for the big increases in RTT/congestion.
NUST
Dr. Arshad Ali (the Director General of SEECS) and the Rector of NUST visited SLAC. We discussed several issues including a graduate student for 6 months to work on high performance data transfer together with a start up company.
...
We are unable to ping (or get data from):
- buitms.seecs.edu.pk
- comsatsswl.seecs.edu.pk
- nuisb.pieas.edu.pk
- nukhimain.seecs.edu.pk
- Pinger.comsats.edu.pk
- pinger.nca.edu.pk
- pinger.uettaxila.edu.pk
- pingerisl-fjwu.pern.edu.pk
- pingerkhi.pern.edu.pk
- pinger.lhr.pern.edu.pk
- sau.seecs.edu.pk
The following are pingable but there is no data:
- ns3.pieas.edu.pk
- pingerusindh.edu.pk
- pingerkhi-cpsp.pern.edu.pk
- www.upesh.edu.pk
PingER at SLAC
The format of GeoIPTools (this provides country city, and lat long information of hosts) changed breaking some of PingER analysis scripts. This has been fixed.
...