Attendees
Invitees: Anjum*, Kashif-, Johari23Johari, Nara?, Abdullah?, Badrul*+, Hanan?, Fidah12, Saqib*+, Les*+, Raja*+, Umar* + and Bebo* +
There were 3 choices:
- Leave the meeting time as is
- Move to Thursday 21 February 2013 7:30pm Pacific Daylight Time, Friday 22 February 2013 8:30am Pakistan time, Friday 22 February 2013 11:30am Malaysian time. Note the time change to accommodate prayers in Malaysia
- Move to Wednesday 27 February 2013 8:00pm Pacific Daylight Time, Thursday 28 February 2013 9:00am Pakistan time, Thursday 28 February 2013 12:00 noon Malaysian time.
I would prefer it if Johari/UNIMAS can attend. My preference is choice 3. However, I can make all 3 choices.
* can attend all 3 choices.
12 can attend choices 1 and 2
23 can attend choices 2 and 3
13 can attend choices 1 and 3
? Unable to attend any of the choices
- No response
+ attended. There was some trouble with Les understanding Skype at the start, so we missed connecting Raja who was available. In future if anyone is available but is not connected call rlacottrell and Les will add them to the existing call.
Chosen time:
Meeting time & date: Thursday 21 February 2013 7:30pm Pacific Daylight Time, Frida 22 February 2013 8:30am Pakistan time, Friday February 2013 11:30 am Malaysian time.
Actual attendees:
General
Johari is setting up a web landing site for the Malaysian collaboration. The start is at http://pinger.unimas.my/pinger. It will contain:
...
It would help to have an MoU between SLAC and the UTM UTM and possibly UM. Les has sent a request to his legal folks to ask how to proceed and whether he can share the UNIMAS MoU with UTM and UM. he He hopes to hear back in the coming 10 days. We will also need agreement to share from UNIMAS.
...
Apart from that, if we target a lot of academicians, then the best time would be during semester break, will get the dates for that.
*Should we set up a Doodle page, see http://doodle.com/?locale=en*. ?
Funding
Johari has submitted a proposal for FRGS (Fundamental Research Grant Scheme). There are 5 members of the proposal (5 is the max). Johari decided to get 2 more people from the group in UNIMAS to join the PingER project, thus we are unable to include our counterparts in UM and UTM (Dr Abdullah and Prof Hanan). We can go for a bigger project such as the eScience or LRGS (Long-term Research Grant Scheme) which can accommodate a larger number of people, more funding and encourage cross institutions collaboration.
...
traceroute -I www,cern.ch works which suggest the UDP probes to UDP ports 33434 - 33465 are being blocked. Saqib is working with the IT department to understand. The output is different from the web browser and the command line. The command line using traceroute www.cern.ch looks fine. The web server stops after the 4th hop. The web server issues the command traceroute -m 30 -q 3 137.138.144.168. The m is the max number of hops, the q is the number of probes per hop, 137.138.144.168 is the IP address of www.cern.ch. This also works from the command line. It could be a timeout problem (it would be good to time traceroute -m 30 -q 3 137.138.144.168 command). Also look in the webserver log for possible failure causes. Saqib has provided the web server logs and nothing stands out. It may be a timing issue, Saquib will try running traceroute.pl from the command line and timing it.
Anjum has postulated that there may a load balancer induced problem. Is the 4th hop at the load balancer?
The addresses assigned to the servers are:
physical ip : 161.139.68.188
external ip 1 : 161.139.146.158
external ip 2 : 161.139.194.158
Saqib is starting to look at Pingtable.pl anomalies as a start in a case study for Malaysia and S.E Asia. Progress?. 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.
UM
Dr Nor Badrul Anuar Jumaat has installedl 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 name and address of the server is pinger.fsktm.um.edu.my (202.185.107.238). The UM monitoring host has been added to the NODELIST PingER meta data base at SLAC a nd 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, "we" can start Badrul can work with some of his students to make a routing study similar to https://confluence.slac.stanford.edu/display/IEPM/Routing+from+UNIMAS.
...
Les met with Navaneethan Arjuman of USM at the TIP meeting in Hawaii. He seems interested in the research side of things. He is a researcher not an operations person and has been involved in network monitoring for 4 years. He talked of a tool they have developed called INFMON, if I heard right. He also is interested in a research proposal. He also strongly recommends we engage with MYREN. Les tried pinging www.usm.my but pings are blocked. He can ping nav6.usm.my. This host has been added to the hosts monitored from SLAC. Nava has provided an IPv6 address to monitor, however, SLAC has not enabled IPv6 yet.
NUST
From Arshad: Rector has agreed to support one person visit to SLAC. Raja has been nominated. He has sent a cv to Les and has filled out the DoE form. Les crafted the invitation and it has been sent to upper management for signature Dec 21, 2012.Les briefed the SLAC Cybersecurity person on 1/10/2013. He has also filled out another form for hosting visitors from sensitive nations. Les has taken and passed the training on hosting visitors from sensitive nations. Cybersecurity want more details on what Raja can access and Les has provided it. SLAC CyberSecurity say they do not approve or disapprove visitors so I have requested (2/8/2013) the CIO to sign and pass to the CEO for signature. Raja has completed his paperwork and is ready to submit. As soon as Les hears the letter has been signed by the CIO (and before it is sent to Raja), Les will get back to Raja to proceed. He has sent 2 reminders to the cybersecrity person and engaged the CIO in the latest.
Raja reports that the code is working fine now without any underestimates. The problem was that he was using Alpha values that were above 80% of the data points (in Alpha Analysis) for each RTT range but now I have changed that to 95%.
He tried to geolocated a landmark in Europe i.e.icfamon.dl.ac.uk using both a fixed Alpha value (0.55 in this case) that was 95% above overall and also using a set of Alpha values which were used as a function of the RTT value. For the fixed Alpha value case the error distance was 746KM where as for the variable Alpha case the error was 530KM. For this test case, using Alpha values as a function of RTT looks promising. In both cases however the Error of geolocation is significant, this is probably due to the fact the target was not in the Convex Hull of the landmarks that responded. It turns out we should exclude icfamon.dl.ac.uk since we uncertain to with 150 miles where it s located (near Oxford or near Liverpool). Raja will repeat and process for different targets and different regions and see how well that goes.
Raja also reports that there are a lot of PlanetLab landmarks being used by reflector in Europe that have the same Lat Long (51 , 9). The min RTT of these landmarks to the target varied from 20ms to 45ms which would imply that they are not at the same location? Shouldn't we avoid using servers as landmarks unless we know their exact location? We recommend not using any such sites or sites that have no digits after the decimal point.
Potential projects
...
Future meeting - Les
Next meeting Wednesday ? 6 March 2013 8:00pm Pacific Daylight Time, Thursday ? 7th March 2013 9:00am Pakistan time, Thursday ? 7th March 2013 12:00 noon Malaysian time.
...