perfSONAR

Locating other instances

perfSONAR Directory

The perfSONAR project maintains a graphical interface to the services directory of all perfSONAR nodes.  It can be found at this link:

http://stats.es.net/ServicesDirectory/

Interacting with this service can be done by scanning the map to find an instance where you may know a location, or by trying to search on specific terms.  As an example, a search for "es.net" will return hosts that have that domain:

Clicking on a host will bring up specific information about the software and hardware:

Searching the map after narrowing the results will place specific red beacons for each host:

Zooming into a region that has a larger red beacon will show where individual nodes are located:

Note that map functionality relies on accurate latitude and longitude information, that is entered when the machine is configured.  Machines that have inaccurate information will not be placed correctly. 

perfSONAR Lookup Service

The directory queries the perfSONAR Lookup Service directly, and it is possibly to grammatically interact with this service.  The following link has information on ways to interact with this service:

https://github.com/esnet/simple-lookup-service

perfSONAR Lookup Service Client

There is a Python client available for the sLS (simple lookup service) that offers basic query functionality.  Additionally, the sLS client comes with two wrapper functions:

  • find_ps_ma - a command line script that returns a list of MAs that have test results for given host.
  • sls_dig -  a script that is similar to "dig" tool. It retrieves information about a host registered in the sLS. 

It can be installed via easy_install

easy_install sls-client

(URL: https://pypi.python.org/simple/sls-client/)

The sls_dig and find_ps_ma scripts are located in /usr/bin/.

To run sls_dig just, run sls_dig <host-name>

sls_dig nettest.lbl.gov

To run find_ps_ma, run find_ps_ma -n <host-name>

find_ps_ma -n nettest.lbl.gov

Asking Sites to Deploy

If you are debugging an end-to-end problem crossing several domains, it is helpful to locate perfSONAR instances along this path.  More instances help to divide and conquer a problem more effectively. 

In the event that you are not able to locate a perfSONAR node in a domain, the following strategies can be used when dealing with the domain administrators:

  1. As the domain, via their NOC or helpdesk system, if they have a perfSONAR node available for testing. It may be the case that it is not publicly advertised.  
  2. Be prepared to send them your subnet information in the event the machine is protected by a firewall, and requires ACLs for access. 
  3. If they do not have a node, ask them to review this page, which explains possible deployment strategies.  In particular the beacon method, perhaps as a LiveCD/LiveUSB deployment, would work for a temporary debugging host.
  4. Engage the national Research and Education network (ESnet, GEANT eduPERT, Internet2) to act as a mediator for the request, and to track the outcome.