Page History

...

• Anjum, Arshad, Zafar, Sadia, Zeeshan  and Amber met with PERN. Several suggestions were made:
  • Put all monitors on UPS with PERN's routers to provide reliability. PERN will assist in setting this up. For the time being this is not being done but this could be done. Umar disagrees with this idea as the nodes would then have 0% unreachability and it would not measure the user experience.
    • Anjum explains what Anwar Amjad wants: 1) Measure performance from PERN to PERN with UPS at both ends. 2) Measure performance from PERN to PERN with UPS at one end. 3) Measure performance from non-PERN/outside PERN to PERN network.
    • This needs to be carried out in phases.
    • Zafar, Amber and Sadia can add hosts to PERN/non-PERN.
  • Add the 15 POPS of HEC. Machines will be provided by SEECS by mid-March. PERN will assist in setting these up. Zeeshan is handling work from SEECS side and is mostly responsible for paper-work. Umar suggests giving someone from HEC this responsibility.
  • Separate the analysis presentation of the PERN from non PERN connected nodes. I have emailed some information on how to do this. Amber and Sadia are working on this.
  • Get an up to date map of PERN network topology. Anjum will get the current map.
  • PERN wants MOS further broken down by PERN and non PERN. Anwar Amjad wants an inter-city analysis. VoIP calls are relatively bad for inter-city links within Pakistan as compared to VoIP calls made outside of Pakistan (such as USA). Anwar Amjad is most interested in Islamabad to Quetta, Islamabad to Karachi and Islamabad to Lahore links. Umar mentions that it is completely fine doing this but asks whether HEC can provide us with statistics. Anjum says HEC is using fluke for measurements and they will share their data.
  • PERN does not understand/agree with throughput measurements. A more understanding of bandwidth and achievable throughput shall be put in the case study.
• Faisal has a new user interface with a Pakistan bias. It needs work to add a bar at the top with pull downs to pages in the various areas. Also the initial page is a bit bare until one scrolls left or right.
• Zafar has started taking and archiving traceroutes between Pakistani monitoring hosts on a daily bases. View these at <http://pinger.seecs.nust.edu.pk/cgi-bin/displayautotrace.cgi^{Image Removed}>. Some improvements are required to be made .. these will be made over time (diff among traceroutes from multiple dates - a table can be used to display day to day differences).
• Sadia has finished MOS for prm.pl. She is now working on adding alpha. She needs the lat/longs, Les  provided information on dbprac.pl and how it gets data such as lat/longs from NODEDETAILS. Zafar suggests using nodes.cf since it is updated more than once everyday. Moreover the lat/lons do not change automatically so database access is not really critical.

...

1. Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable. 

2. Wiki Markup
   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.

3. 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?*
4. [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. 
5. 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. 
6. 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. Adnan thinks one of the students working on the archive site may take this on
7. Provide analysis of the traceroutes in particular identifying changes
8. Provide support for affinity groups

Paper - Umar, Fida, Zafar

...