HADES MA Installation Guide

HADES MA

Installation Guide

Table of Contents

1 Before You Start 1

1.1 Supported Platform 1

1.2 Adding the GÉANT Repository 1

1.3 Prerequisite Software 2

2 Installing the HADES MA 3

3 Configuring the HADES MA 4

3.1 Testing your Deployment 6

4 Using the HADES MA 7

Table of Figures

Figure 1.1: Circuit tab 7

Figure 4.2: Define your service 9

1

Before You Start

The HADES MA uses the HADES central server component to present the data available on the server. Therefore the central server needs to be installed and configured before the HADES MA is installed. This process is documented separately in the central server documentation.

1.1

Supported Platform

The packages in the perfSONAR MDM repository are built for Red Hat Enterprise Linux 5. They have been tested on the latest OS version 5.7. No issues are expected for future minor versions; however they are not supported on the following major versions, like Red Hat Enterprise Linux 6 and higher.

1.2

Adding the GÉANT Repository

To install the HADES MA, it is recommended that you add the GÉANT repository to your host. This is described in the perfSONAR MDM Administrator’s Guide section called “Getting Started”1. Now you should have access to the HADES MA version 0.53 package. To test this package, execute the following command for Red Hat based systems:

# yum search perfsonar-oppd-ma-hades And for Debian based systems:

# apt-cache search perfsonar-oppd-ma-hades Now you should see the HADES MA package.

1 _{perfSONAR MDM Administrator’s Guide is available here:}

1.3

Prerequisite Software

The HADES MA on the machine installation requires the following software to be present:

 Hades central server Note: if it is a fresh installation and HADES central server is not present in the system yet then HADES MA installation process will install it automatically as a dependency.

2

Installing the HADES MA

If you are running a Linux operating system, you can install the HADES MA using RPM distributions. At the moment no Debian packages are available.

To install using RPM distributions:

1. Log on as root to the machine on which you want to host the HADES MA. 2. Check that you have installed all prerequisite software.

Note: The RPMs have dependencies for Perl modules which might not be part of your distribution. YUM informs you about missing dependencies, so you can complete your Perl environment properly. On Red Hat Enterprise Linux, the Perl modules may not be known to your standard yum repository. These packages can be found on RPMforge. See https://rpmrepo.org/RPMforge/Using for information on how to set up your system properly for using RPMforge packages.

3. If you are using a Red Hat distribution you can install the packages with: # yum install perfsonar-oppd-ma-hades.noarch

4. Or if you are using a Debian distribution you can install the packages with: # apt-get install perfsonar-oppd-ma-hades

3

Configuring the HADES MA

Before you can use the HADES MA, you need to configure it. You can find the configuration files at: /etc/oppd.conf

/etc/sysconfig/oppd /etc/oppd.d/hades.conf

/etc/oppd.d/hades-status.conf

HADES MA uses the oppd framework. The main configuration file is /etc/oppd.conf. Open the file with your favourite editor and have a look at the options. You can activate logging by going to the line ‘logfile’ and providing a path to a file. In the file, there is also an example for every option that can be set.

If you have a Red Hat based system, you can find this config file for all options to set for oppd in /etc/sysconfig/oppd.

To configure the HADES MA open hades.conf with your favorite editor. This file will look similar to this: 1. #

2. # Hades MA example configuration 3. #

4. <service MA/HADES/MYDOMAIN> 5. #

6. # Necessary parameters for module initialisation 7. #

8. module MA::Hades # Name of module to load 9. servicetype MA # Service type: MP or MA 10.

11. #

12. # Name, description, and keyword will be reported to Lookup Server 13. #

15. description "Measurement Archive for Hades (OWD, OWDV, Packet Loss) data \

16. from measurement points in my network (mydomain)" 17. keyword "project:mydomain"

18. 19. #

20. # Further parameters 21. #

22. metric "one way delay"

23. metric "one way delay variation" 24. metric "packet loss"

25. # Measurement metric(s). More than one element definition possible. 26. 27. # 28. # Module parameters 29. # 30. <module_param> 31. 32. config "/opt/hades/etc/hades-geant.conf"

33. # Hades domain for which data should be available via this service 34.

35. # You can add further Hades configuration parameters here. 36. # TODO: pointer to useful documentation

37. </module_param> 38.

39. </service MA/HADES/MYDOMAIN>

At first have a look at line 4. Here you can define the service name. Replace only MYDOMAIN with your domain. For example, this could look like this:

<service MA/HADES/GEANT> or <service MA/HADES/MDM>

Do this also in line 39. To get the HADES data, specify the path to the configuration file in the HADES server in line 32. Save and close this file. Then open the file hades-status.conf, which is the same as hades.conf file, and repeat the same steps. Now the HADES MA is configured.

3.1

Testing your Deployment

You can check if you have deployed the HADES MA correctly using the following command: 1. Login as root to your host.

2. Start the PerfSONAR daemon: On RPM based distribution:

# service oppd start On Debian based distribution:

# invoke-rc.d oppd start

4

Using the HADES MA

The best way to use the HADES MA is using perfSONARUI. The perfSONAR User Interface (UI) is a Java-based application designed to provide access to the network management and performance data from a range of perfSONAR services. The UI provides a utilisation summary for selected interfaces for an arbitrary time period, as well as an interface for on-demand TCP throughput tests. It also offers visual data on one-way delayIP delay variation and packet loss between measurement points. Additionally, it provides a looking glass for retrieving information from network devices in real time.

Figure 4.1: Circuit tab

The Circuits tab is used to display statistics for one-way delay, jitter and packet loss. This information is retrieved from Hades Measurement Archives (MA). Figure 1 presents the different sections into the tab’s window.

The required steps are as follow:

1. In the Query options section, click Select service addresses to display the Measurement archives dialog. Here you can select a Measurement Archive or define a new one. We will define the new installed server.

2. Click on the New button (see Figure 4.2), and fill in the information for your service:

URL

Enter the link to your host. This can look like this:

http://radagast.x-win.dfn.de:8090/services/MA/HADES/GEANT The URL has the form:

http://<YOURDOMAIN:<PORT>>/services/MA/HADES/<;MYDOMAIN>

The parameter MYDOMAIN is defined in the hades.conf configuration file which was described earlier. Please use the domain name which is defined in the service tag line 4 in the hades.conf file, otherwise your service will not be reachable.

Name

Use a name that describes your network, for example GÉANT or MDM.

Eventtype

You can define ippm_aggregated to get aggregated data (perfSONARUI uses aggregated data), but if you prefer raw data, use the Playground tab. There you can define you own request message.

Schema

Select ippm.

Supported eventtype

Select ippm_aggregated. 3. Close this window.

4. Use the calendar near the top left-hand corner of the screen to select the date from when you would like to view data.

Figure 4.2: Define your service

Once the data is retrieved, a traffic matrix is displayed in the top right-hand section of the screen. Each square in the matrix represents a particular source-destination pair. You can click on a square to display the measurements for that particular source-destination pair (see Figure 4.3).

On selecting a source-destination pair, the bottom half of the tab is populated with graphs showing:  IP Delay Variation (IPDV)

 One-Way Delay (OWD)  Loss / Duplicate packets  Routes

You can take a closer look at the data by zooming in (using right-clicking and dragging the mouse across the area towards the bottom right-hand corner of the screen).

The Routes graph provides information about the different routes the measurement packets took between the source and the destination points.