Restart an Alarms Server

Runtime > Online Changes > Server Side Online Changes > Restart an Alarms Server

Restart an Alarms Server

The following fields are reloaded on alarms servers:

Digital alarms
Time stamped alarms
Analog alarms
Advanced alarms
Multi-digital alarms
Time stamped digital alarms
Time stamped analog alarms

The alarm category is not reloaded on the client side.

The following alarm category fields are used by the server and will be reloaded:

ON Action
OFF Action
ACK Action
Summary Device
Log Device, ON, OFF and ACK log devices

UNINTENDED EQUIPMENT OPERATION

On updating the Equipment Name or Equipment Item for an alarm, the update will not be reflected on the client side until the alarm servers have been restarted. The reload procedure will indicate a reload error on Runtime Manager. Reloadlog.dat and Syslog.dat of the server process will show the details of the unsupported changes. You can use this information to revert the changes, or restart all servers after deploying your updated project.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

The numbers of added, modified and deleted categories are recorded in the system log. Alarm categories are identified by their category numbers.

Added — Indicates how many categories with new category numbers have been added to the alarm server.
Modified — Indicates how many categories (of which the category number existed in the runtime before reloading) have been modified in the alarm server. If a user has defined a new category record, but its category number was used by an existing category, the category reload will count this situation as a modification of the category with this category number, rather than an addition. A category is shown as modified if any content in the category record is modified, including the case that only client side settings are modified. In this case, the reload does not change the state of this category in the memory, but it is still counted as one modified category.
Deleted —Indicates how many categories have been deleted from the alarm server. A category is defined as deleted if none of the other categories has the same category number as this category. In the case that two category records have the same category number, deleting the latter one in the table will instead increment the modify count, while delete the former one would not increment any count.

Two category records with the same category number are treated as one category in runtime, and the later one would be loaded.

When [Alarm]EnableErrorLogging is set to 1, an alarm server adds a syslog entry for errors from adding, modifying or deleting an alarm record or a category record. The errors can be due to category number out of range or category priority number out of range. Two new hardware alarms (520 and 523) have been introduced for those errors. See Cicode and General Errors for more details.

Reloading an alarm server will affect alarm property tags and may make them invalid (when an alarm is deleted) or make them available (when adding alarms).

To reload an alarm server:

Compile the project on main and standby servers.
Reload the standby alarm server using Cicode function ServerReload or the Runtime Manager. At this point the standby server loads the new RDB and indicates that the server is in "Prepared" state for synchronization. The database is not updated at this stage.
Reload the main alarm server. At this point the main server loads the new RDB and then updates the configuration data in its database. The database on the main alarm server then synchronizes with the database on the standby server.

Use the [Alarm]UseConfigLimits INI parameter to set whether on reload or restart the alarm property values are retrieved from the RDB or the alarm server side database.