...
Saqib is starting to look at Pingtable.pl anomalies as a start in a case study for Malaysia and S.E Asia. MIU looks interesting.The normal RTT to Malayisan hosts from UM and UMT is a few tens of ms, but to MIU its is > 100ms. The route goes via Hong Kong which accounts for the delay. Why does the route go via HK? Saqib needs to start documenting what he is finding and his results (RTTs, min-Rtts, Directivity, traceroutes) and conclusions. Another anomaly might be why SWU in the Philippines has long RTTs from UTM & UNIMAS but not UM. Also why does UPSI have a long RTT from UNIMAS but not UM or UTM, is it simply the distance from Borneo to Peninula Malaysia, look at the Directivity.
UM
Dr Nor Badrul Anuar Jumaat has installed PingER on a cloud at UM. The machines are virtualized and running Ubuntu Linux. The name and address of the server is pinger.fsktm.um.edu.my (202.185.107.238). Anjum pointed out that at NUST they are having a problem with a virtual machine running pinger2.pl and the /tmp/ disk space filling up. Anjum is exploring this in more detail, so at the moment it is just a head's up. Johari has sent Kashif's workshop presentations to Dr. Nor. The UM monitoring host has been added to the NODELIST PingER meta data base at SLAC and the <HostList> for Malaysian and S.E Asian hosts has been added to the pinger.xml file at UM. We need to get the latest pinger2.pl installed. Since the traceroute is working, Badrul will work with some of his students to make a routing study similar to https://confluence.slac.stanford.edu/display/IEPM/Routing+from+UNIMAS. he plans to have something for the meeting in 2 weeks time
...