perfSONAR Deployment Guide for DOE Labs
ESnet has deployed perfSONAR services at over 28 locations, and recommends that ESnet sites each deploy
at least 1 perfSONAR host as well.
You should deploy a perfSONAR host on the same subnet as the end systems that you want to monitor.
You may also want to deploy a perfSONAR host just inside your side firewall to help test and debug
firewall performance issues.
For more details see the DOE Site PerfSONAR Recommendation Guide.
The easiest way to install perfSONAR is to use the
Performance Toolkit
bootable CD distribution.
Instructions for installing the perfSONAR Linux-based LiveCD are
here. We recommend DOE SC Labs configure thier NPToolkit hosts to use
"DOE-SC-LAB" as the "community string".
perfSONAR Host Hardware Recommendations
perfSONAR Firewall Rules
We classify perfSONAR deployments into 3 "levels":
- Level 1: Run a bwctl server that is registered in the ESnet Lookup Service. This allows your remote
collaborators to locate your bwctl server and run incoming tests to your site.
- Level 2: Configure "perfSONAR Buoy" to run regularly scheduled throughput tests to/from your host.
This allows you to establish a performance baseline, and to determine when performance changes.
- Level 3: Full set of perfSONAR services deployed (everything on the pS-Performance Toolkit bootable CD).
This includes latency testing, and collection and publication of utilization, error, and drop counters
from key site routers.
HOWTO Guides
"Level 1" Howto Guide
"Level 2" Howto Guide (coming soon)
"Level 3" Howto Guide
Sample perfSONAR clients and queries
pS-Performance Toolkit FAQ
For more information see:
psps.perfsonar.net and
www.perfsonar.net.
