Use CaseSetting up a distributed monitoring configuration between a branch location and the central location of our example company. Please see the Functional Principle article before setting up the environment for better understanding. |
Example SetupThe instructions are based on the example setup as described below. Satellite SONARPLEXThis is a branch location in cologne which is managed remotely. Location | Cologne | IP-Address | 172.16.0.100 |
Central SONARPLEXThis 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. - Configure the Agent on the Central SONARPLEX
- Set the location identifier on the Satellite SONARPLEX
- Enable status and event delivery on the satellite
- Done.
Step-by-step guideFollow these steps for the Central SONARPLEX. First set the azeti Agent credentials. - Open the in the administrative Web Interface (http://172.16.0.254:81) and choose Configuration :: Network
- Choose Agent Configuration
- Set Port to use: 4192
- Set Agent Password: How-ToDM
- Click to save the configuration
Now open the administrative web interface of the Satellite SONARPLEX and set the location identifier. - Choose Configuration :: My Properties and scroll down to the bottom
- Open the resource LOCATION
- Set Ressource Value: Cologne
- Click to save the configuration
Now enable the status and event delivery on the Satellite SONARPLEX. - Choose Configuration :: Status Delivery Configuration for Distributed Monitoring and configure the settings like shown below.
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. Verifying the SetupTroubleshootingRelated articlesRelated articles appear here based on the labels you select. Click to edit the macro and add or change labels. |