Alarms and Events
Alarm and Event Types
The Main/Standby Solution generates alarms and events under certain conditions that are visible in the alarm and event list of any FOXMAN-UN client connected to the Main or the Standby Server. The following table lists all possible alarms and events, their raise conditions and on which server the corresponding alarm or event is visible:
Use Case | Alarm/Event Condition | Alarm/Event | Text | Visible on Server | Remark |
|---|---|---|---|---|---|
Standby Server periodically pings the Main Server. | Main Server not pingable. | Alarm: yes Event: yes | Switchover from Main server (hostname) to Standby server (hostname) due to a connectivity loss. Standby server is now active. | Standby | Will only be created on a Standby Server of type “Warm Standby” after its core services have automatically started up. |
Main Server periodically pings the Standby Server. | Standby Server not pingable. | Alarm: yes Event: yes | Standby server (hostname) is not reachable. | Main | Will only be created in case the core services of the Main Server are running. |
Both servers are running at the same time. | Core Services on Main and Standby Server are running. | Alarm: yes Event: yes | Main server (hostname) and Standby server (hostname) running both at the same time. | Main and Standby | Will only be created on the Main Server in case the core services of the Main Server are running. Will only be created on the Standby Server in case the core services of the Standby Server are running. |
Scheduled Database Backup on Main Server. | Scheduled Database Backup failed. | Alarm: yes Event: yes | Periodic backup to /$/periodicbackup-x.bck has failed. | Main | Will only be created in case the core services of the Main Server are running. |
Scheduled Database Backup on Standby Server. | Scheduled Database Backup failed. | Alarm: yes Event: yes | Periodic backup to /$/periodicbackup-x.bck has failed. | Standby | Will only be created in case the core services of the Standby Server are running. |
Standby Server copies latest scheduled Database Backup from Main Server. | Copy operation fails. | Alarm: yes Event: no | Transfer of Database Backup from Main server (hostname) to Standby server (hostname) has failed. | Main | Will only be created in case the core services of the Main Server are running. |
Standby Server imports latest copied Database Backup from Main Server. | Database import fails. | Alarm: yes Event: no | Import of Database Backup from Main server (hostname) on Standby server (hostname) has failed. | Main | Will only be created in case the core services of the Main Server are running and the core services on the Standby system are not running. |
Standby Server imports latest copied Database Backup from Main Server. | Database import fails. | Alarm: yes Event: no | Import of Database Backup from Main server (hostname) on Standby server (hostname) is not possible due to a running Standby system. | Main | Will only be created in case both the core services of the Main Server are running and the core services on the Standby system are running. |
Compatibility check between Main and Standby Server. | Server versions of Main and Standby Server do not match. | Alarm: yes Event: no | Server versions of Main server (hostname) and Standby server (hostname) are incompatible. | Main | Will only be created in case the core services of the Main Server are running. |