Page History

There are two significant type of maintenance issues when we talk about TULIP. The problems we need to address are location change of landmarks and their uptime. The problem with the landmarks being available is discussed in landmarks laundering which is child to TULIP analysis page. The other significant problem is the location update of landmarks. We are getting the location of Planet Lab landmarks using the geoiptool, PingER landmark locations are provided by the site hosts and are manually added to Node Detail database.  We intend to run a nightly cron job to check if there is any host which has changed its position. The script is currently deployed at

 /afs/slac/package/pinger/tulip/maintainPL.pl

We have also discovered problems with geoiptool in some of the hosts. One of the challenging problems were two hosts(planetlab1.pop-mg.rnp.br,planetlab2.pop-rs.rnp.br) in Brazil . We did a ping between the host and got a response of 25~30 ms. Geoip tool showed that the hosts are at the same location which is about the center of brazil. We then inquired further and found the case interesting as the traceroute to both of them was going through different routes i.e. traversing different routers to reach the destination.After confirming the actual latititde and longitude from thier websites we updated the database manually. To cater for the problems like these the hash named errltln(Error in lat/long in geoiptool) contains the host which are not updated in the database with this script. The sample code is given below

#Error in lat/long in geoiptool
 my %errltln = (
 'planet01.hhi.fraunhofer.de' => '1',
 'planet02.hhi.fraunhofer.de' => '1',
 'planet-lab1.ufabc.edu.br' => '1',
 'cs-planetlab3.cs.surrey.sfu.ca' => '1',
 'planetlab1.pop-mg.rnp.br' => '1',
 'planetlab2.pop-rs.rnp.br' => '1',
 'csplanet02.cs-ncl.net' => '1'
 );