Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

Table of Contents

 

Use Case

Setting up a distributed monitoring configuration between a branch location and the central location of our example company.

Note

Please see the Functional Principle article before setting up the environment for better understanding.

Example Setup

The instructions are based on the example setup as described below.

Satellite SONARPLEX

This is a branch location in cologne which is managed remotely.

LocationCologne
IP-Address172.16.0.100

Central SONARPLEX

This is the network operation center where all alerts are collected form the remote locations.

LocationLondon
IP-Address172.16.0.254
azeti Agent Port

4192

azeti Agent PasswordHow-ToDM

The satellite device should send its status

...

every 30 minutes

...

 and only HARD events should be sent.

The general procedure is as follows.

  1. Configure the Agent on

...

  1. the Central SONARPLEX
  2. Set the location identifier on

...

  1. the Satellite SONARPLEX
  2. Enable status and event delivery on the satellite
  3. Done.

Step-by-step guide

Follow these steps for

...

the Central SONARPLEX. First set the azeti Agent credentials.

  1. Open the in the administrative Web Interface (http://172.16.0.254:81) and

...

  1. choose Configuration :: Network
  2. Choose

...

  1.  Agent Configuration
  2. Set

...

  1.  Port to use: 4192
  2. Set

...

  1.  Agent Password: How-ToDM
  2. Click Image Modified to save the configuration

Now open the administrative web interface of

...

the Satellite

...

SONARPLEX and set the location identifier. 

...

  1. Choose Configuration :: My

...

  1. Properties and scroll down to the bottom
  2. Open the

...

  1. resource LOCATION

...

  1. Set Ressource Value: Cologne
  2. Click Image Modified to save the configuration

Now enable the status and event delivery on

...

the Satellite SONARPLEX.

...

  1. Choose Configuration :: Status Delivery Configuration for Distributed

...

  1. Monitoring and configure the settings like shown below.
Parameter NameSetting
Deliver Status at regular baseenable
Delivery Interval in Minutes (Heartbeat)30
Retry Frequency in Minutes5
Retry Attempts3
Deliver following Events immediately

Service Alerts

Host Alerts

Suppress SOFT State alerts

Deliver Performance Data

enable
Do not store performance data locallydisable
Destination Host (NOC)172.16.0.254 
Destination Agent Port4192
Destination Agent PasswordHowTo-DM 
Default service output upon transfer problemsMissing check result from satellite.
Default service state upon transfer problemsUNKNOWN
Retain state on outdated servicesenable
Debug LevelWARN

See the Status Delivery Configuration Reference

...

 article for a detailed explanation of the particular settings.

Verifying the Setup

Troubleshooting

Filter by label (Content by label)
showLabelsfalse
max5
spacesSPAG
sortmodified
showSpacefalse
reversetrue
typepage
labelsdistributed