Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IPV6 - Anjum and Ghulam (this has been de-prioritized until new database PingER is working)

Le4s Les has the passwords for the IPv6 host at SEECS. He still has to try it.

...

Joun and Ghulam have arranged to archive the status of Pakistani hosts in http://pinger.seecs.edu.pk/daily-report. It appears future copies be saved there*. There is a link from the PingER web site (http://www-iepm.slac.stanford.edu/pinger/site.html)

The IPs which start with 111.68.96.xxx are routed in such a way that the data can go out but it cannot come back to Pakistan. They will change the IP of all POP nodes. This arrangement was done for NCP. Only 0.5 MB of that link is provided to other universities. Any node that is having the IP as 111.68.96.xxx will be given a new IP.

...

...

Bilal will be delivering three tasks in this week ending 3/7/2012:

  1. Trying stress testing with reflector instead of reflex. Results are available at Target Data for reflector tier all. The results also have  a comparison of reflex and reflector error in terms of distance. Repeat this for Europe. We understood and fixed the problem with reflex missing most of the landmarks. It is much faster.
  2. By the next week Bilal will be submitting report on Australia using reflex. He will also try reflector for Europe. Australia report using reflex can be found at: https://confluence.slac.stanford.edu/display/IEPM/Stress+Testing+for+Australia
    1. Les has provided Bilal with a way to get the lat longs of more hosts in Australia. This required a minor change to HostSearcher.plBilal needs to add the number of landmarks in the region for the EXcel Spreadsheet. This will be useful for his paper, i.e. reporting typical accuracy as a function of landmarks in region.
  3. Bilal will be sending the tulip draft paper by the end of this month. 

There is interest from Northwestern University in using Tulip. The version at SLAC still needs the MatLab license  so we recommend they use the SEECS version, e.g. for http://203.99.52.38/cgi-bin/tulip-viz.cgi?target=132.206.6.88. It does not look like the SEECS version uses reflex.pl. Bilal had a chat with the person from Northwestern University explaining him how Tulip and CBG works.

  1. February. 

It appears Sadia is right about SLAC needing to spend ~ $4K to get the full toolkit needed by CBG. Thus we will not implement at SLAC. Sadia will make sure TULIP art SLAC works for TULUP without CBG. Progress

Stress testing for Australia region is completed using reflex but not reflector. North America is completed with reflector and reflex. However we got to know this week that reflex was having lesser landmarks because PlanetLab landmarks weren't added. Bilal will rerun the stress testing of North America using new reflex.

Bilal is writing a report with stress testing results of all of the regions. He will be sharing it when it completes.

With the upgrading of the pinger.slac.stanford.edu host from RHEL4  to RHEL6 the mysql databases got lost. Sadia has worked with Fahad to recover the Tulip data base from the recovered sites.xml file. This is almost done.

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.
  • Wiki Markup
    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.  Wiki MarkupExtend 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. *Amber is working on this*
  • 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. Amber is looking at.

...