Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. nwfpuet, uettaxila, uob are down for many days: see http://www-iepm.slac.stanford.edu/monitoring/checkdata/).
    1. There were to be future visits to the provinces of Balochistan and KP (Khyber Pakhtunkhwa). Did these happen? Dr. Anjum was going to  contact UOB and UETTAXILA about their problems.
    2. Kashif Sattar of SEECS is deploying and managing hosts and contacts. Muhammad Zeeshan will slowly be taking over from Kashif Sattar (who is leaving if he is not granted an extension by NUST). Update, Dr Anjum
    3. We will not give up on them. Only one person is installing nodes. It will take a visit to them. The server needs replacing at sites. UOB will be fixed in 1 months, then they will go there on the 27th. Anjum will check the status of the other two with Imran.
  2. There has never been any data from  pinger-itc.pu, aiou, hu (Hazara), kohat, nca,  pwr.mu, ustb, since though the hosts are in the NODEDETAILS database there is no dataserver entry for each of then in the database. Should there be? They are identified as monitors. -  Even if I guess at the URL for a dataserver, e.g.  http://pinger.hu.edu.pk/cgi-bin/ping_data.pl there is no such web page. Maybe the permissions have not been ste. Zafar looked at fixed pinger-itc, and aiou. But for Hazar, kohat, nca pwr, ustb, pinger-rcp cannot find web page, they need to be worked on. Zafar will politely remind Imran about checkdata. 
  3. UPesh problem:  See http://pinger.seecs.edu.pk/checkdata/ and "try to get data" for UPesh. UPesh is gathering data but there is "0" at the end of each entry which means that it didn't receive anything back. It can only ping itself. It was installed very differently, they have a private subnet/IP address, this may be not be cost effective to make it work.
  4. Dr. Anjum is verifying that table.pl at SEECS has all the known Pakistani monitors..
    1. UET, UOB, LSE, COMSATS do not have the full set of Pakistani beacons. See matrix. The Pakistani monitoring nodes are supposed to get the beacon list from SEECS. – Anjum said he has a student who can fix but need password so they can fix the nodes so they get the list from the SEECS server. They are fetching their beacons from SLAC. Anjum is requesting admins to fix. Working on it, but response from admins is not good. 
  5. There appears to be an anomaly in the RTTs to vle.iiu.edu.pk (AKA PK.IIU.EDU.N2) from the Pakistani monitors it is over 200ms while from SLAC as displayed in pingtable.pl it is 67ms. Yet if I do it from the command line it is ~ 310ms from pinger. The traceroute shows it as going via London and Singapore which suggests it is on its way to Pakistan. This needs investigating. Pingtable.pl is current as of yesterday so maybe something happened between then and when I pinged a few minutes ago. Also www.iiu.edu.pk has an RTT from SLAC of 177ms. TULIP shows it as in Europe.  Thus I have removed this host from the NODEDETAILS database since it is probably a proxy and not in Pakistan. We may be confused as to the name of the host (e.g. vle & www). Les will study further and email what he finds out.

...

  1. Extend the NODEDETAILS data base to allow entry support for whether the host is currenty pingable.
  2. Extend the PingER map (also use for Pakistani to Pakistani subsset map for the case study)
    1. This adds ping, traceroute, access to database etc.
    2. The advantage compared to other traceroute maps is that the laundering keeps only good servers.
    3. Faisal will work on this
  3. Wiki Markup
    *\[Pending by Faisal\]* *Dashboard for PingER management. Faisal will start correspondence with Amber.*
  4. Get the MatLab licsense at SEECS and put up a CGB server using it. Zafar can you provide progress at next meeting?

...