...

In a nutshell, the script tries to Ping the primary server 3 times. If it does not get a response, then it checks for the existence of the  /var/lib/dbeacon/EUMET/failover.chk file. If it does not exist, then it creates the file with the contents Process Emails And Alarms. The existence of this file tells the Backup server that it needs to take control of the back-end monitoring.

...

In a nutshell, the script uses two MySQL tables dbeacon_cacti.MN_ANNOUNCEMENT_CHANNEL and the table name constructed of the table prefix MN, the two character country code and the circuit name, in the example above, the second table would be dbeacon_cacti.MN_DE_DFN-Primary. The script executes an SNMPGet on the router using the specified OID, it compares the value of the counter received from the SNMPGet with the value stored in the dbeacon_cacti.MN_ANNOUNCEMENT_CHANNEL table for the specific circuit name. It uses these values to calculate the circuit utilisation, and stores this value in the circuit specific MySQL table. In addition, it replaces the value of the counter in the dbeacon_cacti.MN_ANNOUNCEMENT_CHANNEL with the new value obtained from the SNMPGet.

If any errors occur, a log file is generated in the /tmp/eumetsat directory

...

MySQL Database Connections

The Eumetsat back-end processing connects to a MySQL database:

dbeacon_cacti database on eumetsat.geant.net using user eumetsat