Page History

...

• There is case study on Mid east instability and effect on Internet connectivity. it is at https://confluence.slac.stanford.edu/display/IEPM/Internet+performance+seen+by+PingER+and+Mid-East+instability. Umar tried to get a link from ??

PingER

...

• Traceroute is working at Sarawak. Faisal has added it to TULIP. For PingER2.pl the pinger.xml page looks OK but it looks like teh cronjob is not running.
• PingER archive site: Final Year Project of Ghulam and Farhan.
  • Revised the schema according to Umar's recommendations.
  • Change in Nodes table of archive site database schema - included all information of nodes.cf file in Nodes table. Information of nodes comes in this table through NODEDETAILS table at SLAC.
  • Data from NODEDETAILS table is collected by a script node.pl and we changed this script to store data in Nodes table instead of nodes.cf file.
  • getdata.pl script has been changed to collect data from monitoring nodes and store it in to Ping_data table of archive site database instead of files.
  • Also changed getdata.pl script to collect nodes data from Nodes table instead of nodes.cf file because it will not be used in new architecture. The fields where sequence number or rtt is not present, NULL is used.
  • The main analysis script is analyze-hourly.pl which executes daily on archive site and does analysis. This script has also been changed to get input for analysis from ping_data table instead of files. Testing and optimizing this script.
  • The other scripts analyze-daily.pl, analyze-monthly.pl, analyze-allmonths.pl, analyze-allyears.pl will be changed to get nodes information from nodes table instead of nodes.cf file. Remember these scripts are using the same data that analyze-hourly.pl is inserting into the analysis table.
• have created two ERDs. One is a simple design (three tables, normalized to level 1) and another is a complex design (five tables, normalized to level 3, introduces some redundancy). They have created MySQL databases following both ERDs and have done some stress testing. The simple design is faster to insert data into and load data from.
  • Simple design takes 15.4 seconds to write data from 15 files and 12 seconds to read. Complex design takes 18 minutes and 57 seconds to write data from 15 files and 13 seconds to read.
  • Simple design is also space efficient. It takes 27 MB of space as compared to 30 MB taken by complex design for writing data from 15 files.
  • As suggested by Umar, we should run more analysis before finalizing this. Requested for detailed description on the ERDs in question.
  • Some changes suggested by Umar. Ghulam and Farhan will contact Umar and they'll work on the changes:
    • (1) The node table does not have NODEDETAILS.
    • (2) The data table has both unix epoch and date.
    • (3) The analysis/summary table should have ticks, instead it has month, day year etc, which I am not sure about... how would this work? I think its wrong. Instead of four columns there should be just one for the tick.
  • Ghulam and Farhan are modifying scripts to make them database compatible.
  • Les requested to see comparison (space and time complexity) with flat files.
  Faisal is working on a home page for PingER. (Paused)
• PingER Map (Feature Requests)
  • Chrome is showing lines in weird manner, use Firefox instead.
  • Assuming it is easy do not remove a box if one clicks on something else, leave that to be done manually by clicking on the x in the top RH corner
  • Add auto ranging
  • The ability to save a color range setting
  • Make it less browser dependent

TULIP

...

• With the move to the new host Faisal had to get a new cookie to allow scriptroute to run scripts on the PlanetLab infrastructure. Still needs testing.
• CBG Integration with TULIP: Final Year Project of Bilal.
  • TULIP and CBG are currently configured on
  maggie2. Reflector at SEECS is being used.
  • one machine. TULIP needs to be configured
  (requires root permission).Matlab server is being configured by Bilal for test-bed purposes. This will be on a separate machine to replicate the actual environment
  • to maggie2 (some configuration issues which will be resolved soon).
  • We changed TULIP code to write output in a file which will be used as input to the CBG code.
  • We transfer this file from TULIP to CBG through sockets.
    • Sockets are written in perl scripts to send and receive input and output files.
    • Perl script at MATLAB machine reads this file and runs CBG code with required parameters.
    • Next step will be to have CBG code generate results and save its output to a file.
    • This output file is again transferred to TULIP through perl scripts (Sockets).
    • At this time TULIP code is not running properly because only two landmarks are available and at least three active landmarks are required to run this code properly.

IPv6 activities at NUST SEECS, Pakistan

...