Setting up a distributed monitoring configuration with several SONARPLEX devices. The instructions are based on the following example setup.
Satellite SONARPLEX
This is a branch location in cologne which is managed remotely.
Location | Cologne |
IP-Address | 172.16.0.100 |
Central SONARPLEX
This is the network operation center where all alerts are collected form the remote locations.
Location | London |
IP-Address | 172.16.0.254 |
azeti Agent Port | 4192 |
azeti Agent Password | How-ToDM |
The satellite device should send its status every 30 minutes and only HARD events should be sent.
The general procedure is as follows.
Follow these steps for the Central SONARPLEX. First set the azeti Agent credentials.
Now open the administrative web interface of the Satellite SONARPLEX and set the location identifier.
Now enable the status and event delivery on the Satellite SONARPLEX.
Parameter Name | Setting |
---|---|
Deliver Status at regular base | enable |
Delivery Interval in Minutes (Heartbeat) | 30 |
Retry Frequency in Minutes | 5 |
Retry Attempts | 3 |
Deliver following Events immediately | Service Alerts Host Alerts Suppress SOFT State alerts |
Deliver Performance Data | enable |
Do not store performance data locally | disable |
Destination Host (NOC) | 172.16.0.254 |
Destination Agent Port | 4192 |
Destination Agent Password | HowTo-DM |
Default service output upon transfer problems | Missing check result from satellite. |
Default service state upon transfer problems | UNKNOWN |
Retain state on outdated services | enable |
Debug Level | WARN |
See the Status Delivery Configuration Reference article for a detailed explanation of the particular settings.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.