...
- Login to tulip database (username and password available in escrow -c iepm iepmacct)
- Change the database to tulip by cmd
| Code Block |
|---|
mysql> use tulip;
|
- Now update the value of enabled using the following sql cmd; in this instance we are using ipv4Addr = 141.22.213.35; generally ipv4Addr is the primary key but we can also use hostName as an identifier to disable landmarks
| Code Block |
|---|
update landmarks set enabled = '0' where ipv4Addr = '141.22.213.35';
|
- Update Sites.xml so that it can now use the updated landmarks using follwing cmd
| Code Block |
|---|
create_sites-xml.pl > /afs/slac/www/comp/net/wan-mon/tulip/sites.xml
|
...
Reflector.pl creates two log files /tmp/reflector.log-enabled and /tmp/reflector.log-disabled which can be reviewed. They are stored on the host that ran reflector.pl (usually pinger.slac.stanford.edu)
To review reflector.log-disabled on pinger@slac.stanford.edu you may want to use
Code Block >grep transmitted /tmp/reflector.log-disabled Landmark(2)=http://206.117.37.4:3355, Client=134.79.104.80, target=134.79.18.188,\ ability=0, 10 packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 9.485/9.6527/10.007<br> Landmark(2)=http://pinger.cern.ch/cgi-bin/traceroute.pl?target=134.79.18.188&function=ping, Client=134.79.104.80, ability=0,\ 5 packets transmitted, 5 received, 0% packet loss, rtt min/avg/max = 171.147/171.627/172.808<br> Landmark(2)=http://204.178.4.164:3355, Client=134.79.104.80, target=134.79.18.188, ability=0, 10 packets transmitted,\ 10 received, 0% packet loss, rtt min/avg/max = 86.906/106.1068/154.922<br>To review reflector.log-enabled on pinger@slac/stanford.edu you may want to use
Code Block >grep failed /tmp/reflector.log-enabled Landmark(1)=http://192.42.83.252:3355, Client=134.79.104.80, target=134.79.18.188, ability=1,\ failed to connect response code 200 <br> Landmark(1)=http://138.238.250.157:3355, Client=134.79.104.80, target=134.79.18.188, ability=1,\ failed to connect response code 200 <br> >grep transmitted /tmp/reflector.log-enabled Landmark(2)=http://pinger-ncp.ncp.edu.pk/cgi-bin/traceroute.pl?target=134.79.18.188&function=ping,\ Client=134.79.104.80, ability=1, 5 packets transmitted, 5 received, 0% packet loss,\ rtt min/avg/max = 316.461/316.685/316.896<br>
...
It (tulip-tuning.pl) is run twice nightly (see the trscrontab) once to disable non working landmarks (those enabled landmarks that have fallen below 20% success), once to enable landmarks that are now working again (those disabled landmarks that now have success above 50%).
| Code Block |
|---|
/afs/slac/package/pinger/tulip/tulip-tuning.pl -d 1 -a disabled
|
...
A copy of the analyzed Tulip log is also saved at /afs/slac/package/pinger/tulip/analyzedump_[enabled|disabled]
You can run
| Code Block |
|---|
tulip-tuning.pl -d 1 -a disabled --debug 0
|
...
You can run it manually from here:
| Code Block |
|---|
/afs/slac/package/pinger/tulip/tulip-dup.pl
|
...
To generate the sites xml files it is necessary to run:
| Code Block |
|---|
/afs/slac/package/pinger/tulip/create_sites-xml.pl > /afs/slac/www/comp/net/wan-mon/tulip/sites.xml #Takes 2 seconds
/afs/slac/package/pinger/tulip/create_sites-xml.pl --ability 0 > /afs/slac/www/comp/net/wan-mon/tulip/sites-disabled.xml
|
They take a few seconds to run.
They set up the lists of enabled and disabled landmarks. These are needed by reflector.cgi.
It may also be necessary to run /afs/slac/package/pinger/tulip/generatePL.pl to get the country, region and lat/long of the PlanetLab sites and add them to the Tulip database.
Then run:
| Code Block |
|---|
/afs/slac/package/pinger/tulip/generatexmlnodes.pl
|
...
The spreadsheet indicates the duplicate landmarks that can be disabled in a red background
Site Contacts/Owners
perfSONAR sites
As a development effort the perfSONAR developers seldom contact owners of deployed perfSONAR machines. Thus we reach out to them directly representing SLAC/PingER (i.e. not representing the developers, and without a to CC). We note we are researchers that want access to the measurements, and things aren't working. You can find the contact information for a given note on it's home page, or you can use the LS infrastructure.
PingER sites
The site owner can be found in the NODEDETAILS database.
Access to Tulip MySQL DataBase
...