PerfSonar Installation Notes.

Description

I've installed using rpm the following services in a local machine:

SNMP Measurement Archive
perfSONAR-BUOY
Lookup Service
Status Measurement Archive
PingER Services
LS Registration Daemon

If all your services are registering with the local Lookup Service ( http://access.sprace.org.br:9995/perfSONAR_PS/services/hLS ), that information should all be going to the right place. You'll need to make sure that the "ls_instance" in the configuration files all point to your local lookup service. If it's specified there, you can check the logs for the lookup service ( /var/log/perfsonar/lookup_service.log ) to verify that your services are all registering there. The lookup service will register that information into the "lookup service cloud" (note: this may take a few hours from when you first setup your services). Once the cloud knows about them, you can find your services by going to http://www.perfsonar.net/activeServices/

. This includes links to verify the data on the services. You can also install perl-perfSONAR_PS-perfAdmin to get a local copy of the software above. To add your bwctl/owamp/ndt/npad tools to a community, you can edit the ls registration daemon configuration file ( /opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf ), and add "site_project PROJECT_NAME" lines. e.g.

site_project         Internet2
site_project         LHC

and restart the ls registration daemon when you're done. Remember to configure your iptables rules to allow several ports to be used by, for example, bwctl or owamp . More informations at http://www.internet2.edu/performance/pS-PS/

Lookup Service

rpm --import http://software.internet2.edu/rpms/RPM-GPG-KEY-Internet2
 wget http://software.internet2.edu/Internet2-repo-0.1-2.noarch.rpm
 rpm -ivh Internet2-repo-0.1-2.noarch.rpm
 cd /etc/yum.repos.d/
 vim dries.repo
[dries]
name=Extra Fedora rpms dries - $releasever - $basearch
baseurl=http://ftp.belnet.be/packages/dries.ulyssis.org/redhat/el4/en/i386/dries/RPMS
 rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
 wget -c http://software.internet2.edu/Internet2-repo-0.1-2.noarch.rpm
 wget http://software.internet2.edu/rpms/i386/main/RPMS/perl-perfSONAR_PS-LookupService-3.1-8.pSPS.noarch.rpm
 yum localinstall perl-perfSONAR_PS-LookupService-3.1-8.pSPS.noarch.rpm
 vim /opt/perfsonar_ps/lookup_service/etc/daemon.conf
 /etc/init.d/lookup_service start
 tail -f  /var/log/perfsonar/lookup_service.log

SNMPMA service

wget http://software.internet2.edu/rpms/i386/main/RPMS/perl-perfSONAR_PS-SNMPMA-3.1-9.pSPS.noarch.rpm
 yum localinstall perl-perfSONAR_PS-SNMPMA-3.1-9.pSPS.noarch.rpm
 yum install rrdtool-devel perl-rrdtool
 yum install libxml2-devel
 vim /opt/perfsonar_ps/snmp_ma/etc/daemon.conf
 /etc/init.d/snmp_ma start
 tail -f /var/log/perfsonar/snmp_ma.log
 perl bin/client.pl http://access.sprace.org.br:9995/perfSONAR_PS/services/hLS etc/requests/EchoRequest.xml

The way our SNMP MA is configured, it is reporting the interfaces in the store.xml ( /var/lib/perfsonar/snmp_ma/store.xml ) to our LS instance. The default store.xml file has an example interface in it (localhost/127.0.0.1) , so when we lookup the data being exported, it shows that example interface. We needed to either specify a new set of interfaces in the store.xml file, similar to the one already in there, or we should need to configure the SNMP MA to make available an existing cacti, mrtg or cricket database.

In fact we had to install Cacti (http://access.sprace.org.br/cact/index.php) and configured a new device, sprace router with hostname 200.136.80.1 , using "Host Template" Cisco-Router . Just a note : ultralight as "SNMP Community".

OWAMP, BWCTL and LS registration daemon

 
 yum install owamp-client.i386 owamp-server.i386
 yum install bwctl-client bwctl-server
 wget http://software.internet2.edu/rpms/i386/main/RPMS/perl-perfSONAR_PS-LSRegistrationDaemon-3.1-3.pSPS.noarch.rpm
 yum localinstall perl-perfSONAR_PS-LSRegistrationDaemon-3.1-3.pSPS.noarch.rpm
 vim /opt/perfsonar_ps/ls_registration_daemon/
 vim /opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf
 /etc/init.d/ls_registration_daemon start
 yum install iperf
 wget http://www.lcp.nrl.navy.mil/nuttcp/stable/rpm/nuttcp-5.3.1-1.i386.rpm
 yum localinstall nuttcp-5.3.1-1.i386.rpm
 bwctld -c /etc/bwctld
 owampd -c /etc/owampd/
 /etc/init.d/ls_registration_daemon restart
 tail -f /var/log/perfsonar/ls_registration_daemon.log
wget http://software.internet2.edu/rpms/i386/main/RPMS/perl-perfSONAR_PS-Status-3.1-3.pSPS.noarch.rpm
yum localinstall perl-perfSONAR_PS-Status-3.1-3.pSPS.noarch.rpm
vim /opt/perfsonar_ps/status/etc/database.conf
vim /opt/perfsonar_ps/status/etc/service.conf
/etc/init.d/perfsonar-status-service start

PingER Service

Due a error on Catalyst perl module, we can't be able to make PingerGUI (a graphical interface for PingER configuration) works, since it crashed our http initialization service.

yum install mod_perl-devel
 yum install    perl-perfSONAR_PS-PingER-server
rm /etc/httpd/conf.d/pinger_gui.conf
/etc/init.d/PingER configure
/etc/init.d/PingER start

We configured a server to ping in our /opt/perfsonar_ps/PingER/etc/pinger-landmarks.xml with these lines %CODE{"html"}% <pingertopo:topology xmlns:pingertopo="http://ogf.org/ns/nmwg/tools/pinger/landmarks/1.0/" xmlns:nmtl2="http://ogf.org/schema/network/topology/l2/20070707/" xmlns:nmtl3="http://ogf.org/schema/network/topology/l3/20070707/" xmlns:nmtl4="http://ogf.org/schema/network/topology/l4/20070707/" xmlns:nmtb="http://ogf.org/schema/network/topology/base/20070707/" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"> pinger pinger.slac.stanford.edu 1000 10 1 255 60 0 134.79.240.30 %ENDCODE%

PerfSonarBUOY services

yum install perl-perfSONAR_PS-perfSONARBUOY-client
yum install perl-perfSONAR_PS-perfSONARBUOY-server
yum install db4 db4-devel db4-utils
cd /opt/perfsonar_ps/perfsonarbuoy_ma/
vim /opt/perfsonar_ps/PingER/etc/daemon.conf
vim etc/owmesh.conf
bin/owdb.pl -c etc -i root
bin/bwdb.pl -c etc -i root
/etc/init.d/perfsonarbuoy_ma start

There are other scripts that manage the measurement and collection of data:

- /etc/init.d/perfsonarbuoy_bw_master -- Script that performs BWCTL measurements
- /etc/init.d/perfsonarbuoy_bw_collector -- Script to collect and store BWCTL measurements
- /etc/init.d/perfsonarbuoy_owp_master -- Script that performs OWAMP measurements
- /etc/init.d/perfsonarbuoy_owp_collector -- Script to collect and store OWAMP measurements

Not configured yet. Actually it needs two additional nodes, running onl bwctl and owamp to act as beacons . To be done.

Updates

Fulano em dd/mm/aaaa

To manually start these services:

/etc/init.d/snmp_ma stop
/etc/init.d/PingER stop
/etc/init.d/perfsonar-status-service stop
/etc/init.d/ls_registration_daemon stop
/etc/init.d/lookup_service stop
/etc/init.d/bwctld stop
/etc/init.d/owampd stop
/etc/init.d/bwctld start
/etc/init.d/owampd start
/etc/init.d/lookup_service start
/etc/init.d/PingER start
/etc/init.d/perfsonar-status-service start
/etc/init.d/ls_registration_daemon start
/etc/init.d/snmp_ma start