Agenda for SEECS-SLAC Meeting October 12, 2011.

Upcoming

IP address has been assigned to IPV6 but machine has yet not been set up. IP will be active after 10th September. Is it active?

IPv6 things are still unclear at SLAC. I have an account on a dual stack host in Italy. A possible project would be to make traceroute.pl work on a dual stack IPv6 host (say to traceroute to ipv6.google.com). Will need to look at gethostbyname etc. 

Future & Publicity

• Amber has put together an email list of PingER contacts to send the video to.
  • We need to check the Internet users and Internet penetration figures (they may be missing for many countries). Once this is done we can announce.
• Explorer
  • Public Data Explorer next Gen Motioncharts is working, we need to add IDI and HDI in data explorer before announcing.
  • Documentation of PingER Data Explorer is available.

Pakistani case study - Amber, Anjum

1. Host count has reached 56 in Pakistan.
2. HEC report for September is sent. Any further requirements? What is the URL?

Status of Pakistani PingER hosts

As updated on 10/12/2011.

Responsible person: Joun Muhammad

PingER Management

Amber is managing PingER Nodes in readdressing or disabling the down ones (for > 120 days) and finding new hosts (using HostSearcher.pl) in the countries with <= 3 hosts.

Difference in Ping and TCP synack respose times

Sadia has made some measurements, analyzed the results and is/has putting/put together a report. read here

PingER traceroute archive site

• Folder having all the traceroutes gave error " file too large" for new traceroute collection. Need to break up the files into separate directories, one per day.

PingER archive site - FYP (Ghulam, Farhan, Zafar)

• The archive site based on relational database is complete adnd is ready to be deployed on the server.
• Some comparisons between flat files and relational database were made for daily , monthly and yearly analysis. Farhan will send these results to Zafar and Dr. Les.
• We need to see how the new pingtable.pl works
• Live IP has been provided. The node is internally accessible, however it is not accessible through live IP.
• Next step is to port to SLAC.
• Ghulam has sent sadia archive implementation report today.
• Ghulam needs to have a discussion with Zafar about analyzing the new archive site with respect to cpu cycles and memory.

Adding MOS and Alpha to pingtable.pl

• Analysis scripts to add Mean Opinion Score and Alpha, some things need to be correctly configured. It has been deployed athttp://pinger.seecs.edu.pk/cgi-bin/pingtable.pl for testing.
• Alpha and MOS to be implemented at SLAC site. Sadia will be doing this with the help of Zafar. Currently Ghulam and Farhan are working on synchronizing the SLAC and SEECS scripts.

TULIP

Zafar, Sadia, Bilal and Ghulam had a meeting regarding understanding TULIP on Saturday 24th September.TULIP and analysis archive progress was discussed too .Available at Meeting Minutes

Sadia and Bilal will be testing tulip on Monday.

CBG TULIP Integration -- FYP (Bilal)

• Bilal will have a stress testing before deploying it on SLAC. He will run the script for 310 hosts now and then compare it with the results he saved 4 months ago with 59 hosts.
• Matlab licence is going to be upgraded from standalone to network. We need to understand how to access MatLab from Tulip. We have a MatLab license. Can we use a Matlab script etc. Sadia?

PerfSONAR (Pakistan)

• PerfSONAR at SEECS: PerfSONAR throughput and latency nodes are now up and running at SEECS. Hostnames and corresponding IP adresses are:**  throughput measurement node: http://psbw.seecs.edu.pk/ (http:115.186.132.154/toolkit/) 
  • latency measurement node: http://psla.seecs.edu.pk/ (http://115.186.132.155/toolkit/)
• Select options under "Service Graphs" to view throughput or latency graphs. Added 5 Stratum 1 NTP servers to cater for clock delay and everything seems to work fine.
• There are some interesting one-way latency graphs at 115.186.132.155 (SEECS PerfSONAR Latency node). Dst to Src (e.g MIT to SEECS) latency is less than Src to Dst (e.g SEECS to MIT) latency. This might uncover some trends in outbound network traffic from Pakistan.

Possible projects

• There can be a paper kind of talking on Pinger if we could just find the right conference. MCN, ICC and Globecomm do provide network monitoring topics. We can talk of GEO-Location experiences. For example within Pakistan it works fine, however as we go within regions or continents this gets worse. We can publish some stats on that for example. We are yet not ready for Tulip paper.
• See [https://confluence.slac.stanford.edu/display/IEPM/Future+Projects].
• Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable. 
• Extend Checkdata to provide emails automatically, see [https://confluence.slac.stanford.edu/display/IEPM/Extend+checkdata+to+make+it+more+useful]. Many of the ideas in the script node-contacts.pl are a step in this direction.
• Improve the PingER2 installation procedures to make it more robust. This might be something for the person(s) in Pakistan who are responsible for installing PingER2 at the Pakistani monitoring sites. They probably have found where the failures occurs. Also look at the FAQ, and ping_data.pl which has been improved to assist in debugging, could it be further improved (e.g. provide access to the httpd.conf file so one can see if it properly configured)? There are 2 students working on the PingER archive. Is this something they could work on?
•  [Fix PingER archiving/analysis package to be IPv6 conformant|IEPM:Make PingER IPV6 compliant]. Will build a proposal for an IPv6 testbed. They will try various transition techniques. A proposal has been prepared and that has been submitted to PTA. Adnan is a co PI. It is being evaluated today.  A small testbed has been established in SEECS and the plan to shift some of the network to IPv6. Bilal is part of 3 students involved with PingER and they will be involved with IPv6. They are porting the PingER archive site site to using a database. They have redeveloped the archive site using Umar's documentation. They have set up a small test archive site. They have gathering, archiving, analysis. They will design a new database. They will also try a port of PingER to IPv6. 
• Look at RRD event detection based on thresholds and how to extend, maybe adding plateau algorithm. Umar's algorithm did  not work in a predictable manner. 
• Provide near realtime plots of current pinger data using getdata_all.pl/wget. It will work as a CGI script with a form to select the host, the ping size, and the time frame to plot. It will use wget or getdata_all.pl to get the relevant data and possibly RRD/smokeping to display the data. 

Future meeting time - Les

1. Next meeting on Wednesday 19th October at 8:00 pm in US and Thursday 20th October at 8:00am in Pakistan.