...
The UFRJ host is successfully running again.
UM
UM appears to be experiencing very high packet losses (>4%). We need help in understanding these. It does not look like simple congestion since the jitter and RTT is staying low. Saqib needs assistance from Badrul as part of his case study of Malaysia. Badrul writes: "UM is now currently changing the new policy regarding the bandwidth and connection. They are upgrading the switch and router to a new router - mostly every weekend they shut down the network. therefore we are now having some difficulty." Saqib has identified what appear to be losses starting at a JARING router in KL. Badrul will run some mtr traceorute/pings to various sites. No update 3/5/2014.
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.
Ridzuan successfully setup hadoop environment for the servers. He is now looking into how best to input the pinger data to the environment and type of analytics that can be done. Ridzuan is working through some issues due to lack of IPv4 addresses and the need to use IPv6.
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.
Ridzuan successfully setup hadoop environment for the servers. He is now looking into how best to input the pinger data to the environment and type of analytics that can be done. Ridzuan is working through some issues due to lack of IPv4 addresses and the need to use IPv6.
Ibrahim Abaker is planning to work on a topic initially entitled " leveraging pingER big data with a modified pingtable for event-correlation and clustering". Bebo & Les had a Skype meeting with Renan and Ibrahim to get an update and set Ibrahim Abaker is planning to work on a topic initially entitled " leveraging pingER big data with a modified pingtable for event-correlation and clustering", The purpose of this project is to make Pinger more efficient and more scalable to retrieve and analysis pingER raw data. Consequently it may improve pinger data store. He is planning to use key-value store model with high expandability and shorter query response time. The benefit of such project will help in the design of real time analysis and distributed pinger data across multiple servers for analysis. Les has sent him a pointer to documentation on the data flow at SLAC and also listings of pingtable.pl and associated script. He is currently writing a proposal, which will contain a problem statement, objectives, scope and the approach to tackle the problem. He asked: how much PingER data is captured and stored so far (~ 1TByte)? Is there a published paper (see http://www-iepm.slac.stanford.edu/paperwork/ieee/ieee.pdf)? Bebo & Les will set up a Skype meeting with Renan to get an update and see about setting up direct contact between Renan and Ibrahim. Ibrahim provided a copy of his proposal (see https://confluence.slac.stanford.edu/download/attachments/17162/leveraging%20pingER%20big%20data%20with%20a%20modified%20pingtable%20for%20event-correlation%20and%20clustering.docx).
UNIMAS
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. Badrul and Saqib need to try Johari provided information to Saqib on trying it out. How did it go?
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. 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
...