You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

  1. Make a case study on network performance in Sarawak. Consider what you want to learn (e.g. which sites are using VSATs, how direct are connections, how reliable are the connections, which sites are congested, etc.). Identify hosts at representative (e.g. major town and cities, remote areas, educational and commercial network connections) working (i.e. rsepond to pings) sites in Sarawak. For comparison could add hosts at sites in Kalimantan, Sabah or other SE Asian countries. Add these to the monitoring site at UNIMAS. Make sure the sites are working. Gather the data for a a couple of months, meanwhile learn how to access the PingER data and use tools such as Excel to perform analysis on the data. Look at who the Internet Service Providers (e.g. by looking at traceroutes, may have to develop or adapt the SLAc tool for gathering traceroutes on a daily or more frequent basis)) are for the sites. Analyze the min-RTTs looking for VSATs, look for comparisons (commercial vs A&R sites), look at the traceroutes how direct are the connections (also look at the alpha directivity metrics from PingER). What are the impacts of day vs night weekend vs workday, holidays, are there any other events of interest (earthquakes, cable cuts), route changes.
  2. Deploy an ePingER at Bario in the Highlands. Also look at deploying a network of PingER monitoring sites in Malaysia.
  3. Look at anomalous event detection using PingER time series data, based on thresholds and how to extend, maybe adding plateau algorithm. Add as a package to RRD.
  4. There can be a paper about Pinger if we could just find the right conference. MCN, ICC and Globecomm do provide network monitoring topics. It could talk of the various metrics and their importance (in particular; MOS, Alpha, max RTT, min RTT), the lessons learnt from running such a worldwide infrastructure, the uses of the data etc.
  5. We can talk of GEO-Location experiences. For example within Pakistan it works fine, however as we go within regions or continents this gets worse. We can publish some stats on that for example. We can add the impact of changing alpha. We can also indicate the importance of landmark proximity. 
  6. Can we use max ping round trip times or something else to help identify buffer bloat
  7. Modularize all PingER analysis scripts.
  8. Migrate pinger data to perfsonar databases
  9. Fix PingER archiving/analysis package to be IPv6 conformant.
  10. Extend the NODEDETAILS data base to allow entry more carefully validate input.
  11. Improve the PingER2 installation procedures to make it more robust. This might be something for the person(s) in Pakistan or UNIMAS who are responsible for installing PingER2 at the Pakistani or Malaysian monitoring sites. Look at the FAQ, and ping_data.pl which has been improved to assist in debugging, could it be further improved.
  • No labels