Alarms and events - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide

Product name
SNE10 Network Engine
SNE11 Network Engine
SNE22 Network Engine
SNE Supervisory Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active

Each SNE stores alarm and event messages generated by the SNE and the connected field trunk devices. You can configure an SNE to send alarm and event notifications through the SNE DDAs to email destinations and SNMP devices.

DDAs are agents that route and deliver alarm and event messages to destinations such as email addresses, Syslog servers, and SNMP management systems.

If the site has an ADS/ADX, each SNE can forward alarm and event information to the ADS/ADX for centralized notification and long-term storage.

Important:

To avoid a loss of notification if the repository becomes full, the Metasys system manages the SNE repositories according to the following criteria :

  • Events forwarded to an ADS Event Repository are always removed before events that are not forwarded.
  • The lowest priority event with the oldest time stamp and Acknowledge Required flag set to false is replaced first.
  • If the event about to be created is of a higher priority than at least one event in the repository, the event with the oldest time stamp and the lowest priority is replaced.
  • If all events are of the same priority, the event with the oldest time stamp is replaced.
  • If the event about to be created is of a lower priority than all other events in the Event Repository, no event is replaced and the new event is discarded.

A loss of alarm emailing can result if the SNE is not commissioned with strict adherence to these criteria. To avoid managing events in this way, move ADS/ADX and the notification DDAs to the server.

You can designate multiple alarm and event sources in an SNE and in the connected equipment devices, and then configure the conditions that trigger those alarms or events. You can also define multiple notification types and multiple notification destinations for each alarm or event.

The SNE also has several pre-configured internal diagnostic features that are factory set to generate alarms. SNE device diagnostic features with factory-set default alarm values include those listed in the following table.

Table 1. Default Network Engine Alarm Values

Audit Rate

Event Rate

BACnet Broadcast Receive Rate

Flash Usage

COV Rcv Rate

Memory Usage

CPU Temperature

Samples Lost

CPU Usage

Sample Rate

Events Lost

Transfer Buffer Full

You can check the status of these diagnostic features on the Diagnostic tab.

Refer to the Introduction to Alarm and Event Management in the Metasys SMP Help (LIT-1201793) for more information.

Note: After an alarm is generated, anyone who acknowledges the alarm clears that alarm notification for all other users. If an ADS/ADX is the Site Director, you can set the ADS/ADX to deliver alarm and event notifications to a network printer.