perfSONAR

Monitoring architectural examples

Host with a Single Network Interface

The standard use case for a perfSONAR node is operate tests (either Bandwidth-based or Latency-based) on a single network interface card.  The speed of the card does not matter, and should reflect the desire of the operator. 

Testing both Bandwidth and Latency simultaneously on a single interface is possible, but has been shown to impact test accuracy.  To enable this feature, the operator must edit the /opt/perfsonar_ps/regular_testing/etc/regular_testing.conf file by hand. 

Host with Dual Network Interfaces

In versions 3.4 and above of the perfSONAR toolkit, there are options to enable simultaneous forms of testing when dual-homing the host to use two network interface cards.  The toolkit software will allow the operator to configure both network cards, and specify which interfaces will be used for a specific type of measurement.   

More information on this operational style can be found at http://docs.perfsonar.net/manage_dual_xface.html

Performance Beacon Deployment Use Case

The basic use case for perfSONAR is to make the node available for others to use.  This is referred to as the "beacon" use case.  By setting up the node, keeping it"open" (e.g. not imparting policy that would prevent the average user from initiating a test), and ensuring that it remains operational, networks can allow others the ability to learn what their end-to-end performance characteristics look like. 

Other sites can incorporate this node into their testing, by hand and by regular testing means. A beacon can be created using the perfSONAR toolkit ISO or bundled RPM install.  The former methods are preferred from a usability and maintainability standpoint. 

Performance "Island" Deployment Use Case

Similar to the case of the beacon, a "performance island" stands alone, but is configured to test to other beacons, islands, and mesh members by the maintainer

This method requires more maintenance to identify hosts to test with, and is able to store and produce graphs of the results of testing.  This instance can be created using the perfSONAR toolkit ISO or bundled RPM install.

"Mesh" Deployment Use Case

Establishing a performance "mesh" involves coordinating several nodes, potentially maintained in different networks, via a shared configuration file that describes a test.  This configuration is read by the tools, which then perform the tests and store the results in either a central location, or on each of the members. 

Software such as Maddash can be used to visualize the collective results. 

This instance can be created using the perfSONAR toolkit ISO or bundled RPM install.