Introduction

We wanted to verify whether the sharing cretaed by running on a virtual machine made any statistical difference to the PingER results. Thus we compare the results from PinGER running on a bare metal machine (pinger.slac.stanford.edu) vs running on a VM.

Installation of PingER Measurement Agent (MA pinger2.pl)

Spin up the virtual machine.

• Its nickname is pingervm
• It is called dhcp-nebula-124.26.slac.stanford.edu (134.79.124.66)
• Install Apache
  • yum install -y httpd

Install pinger2.pl

• You need a writeable /usr/local (SLAC uses AFS 
  • Get root access (sudo -s)
  • Set usrlocal=local in /etc/taylor.opts
  • sudo taylor everything to make the change take effect (example)
  • Install lynx (example), XML::Simple (example)
    • It also needs ping (usually pre-installed in /bin/ping), ping6 (usually pre-installed in /bin/ping6), dig (usually pre-installed in /usr/bin/dig), and mail (usually pre-installed in /bin/mail)

• Follow the instructions at:  Installation Overview
  • tar xzf pinger-2.0.3.tar.gz
  • cd pinger-2.0.3
  • ./configure (example)
  • make test_prereqs
  • make (example)
• Then 
  • make install (example)
  • make install_cron (example)

Verify installation

• To see if the cronjob is running look at the dates on the files /usr/local/share/pinger/pingerCronStat.stdout and /usr/local/share/pinger/pingerCronStat.stderr, they should be withing the last 30 mins (example)
•  Examine the above files (in particular the stderr file) to verify pinger2.pl is properly configured (an example of a typical error in the stderr file). If all is well then the stderr file will be empty. Example of a normal stdout file.

Installation of traceroute.pl and ping_data.pl