Destination Delivery Agents (DDA) - Metasys - LIT-12011832 - General System Information - Metasys System - 12.0

Metasys System Configuration Guide

Brand
Metasys
Product name
Metasys System
Document type
Configuration Guide
Document number
LIT-12011832
Version
12.0
Revision date
2024-03-25
Product status
Active
Language
English

DDAs are the method used for routing and delivering Metasys alarm extension event messages to destinations such as printers, email, and Network Management systems.

Site Management Portal (SMP) management of Server DDAs was removed at Release 10.1. Management of Server DDAs is available with the Remote Notifications feature in Metasys UI only. However, SMP management of Server DDAs is still available for Metasys for Validated Environments (MVE) sites.

The Metasys system uses an Email DDA, Syslog DDA, Printer DDA, and Simple Network Management Protocol (SNMP) DDA. The email DDA supports standard Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP), and Internet Message Access Protocol (IMAP). The Metasys Server can use any of these DDAs, but a network engine at Release 9.0.7 or later can only use the Email DDA, Syslog DDA, and SNMP DDA.

SNMP provides IP standard SNMP functionality in the Metasys system, enabling network administrators to manage Metasys network performance, find and resolve Metasys system-related issues, and plan for future growth of the Metasys system. SNMP functionality uses standard SNMP Versions 1, 2C, and 3 (excluding SNMP encryption and authentication support). The Metasys system allows delivery of unsecured SNMP traps for Metasys alarm events from all engines and servers to the facility owner’s Network Management System (NMS), and allows the NMS to execute SNMP Gets against engines. This version of SNMP support does not include the SNMP set commands.

Johnson Controls has developed a downloadable custom dynamic Management Information Base (MIB) that allows the NMS to monitor Metasys point objects, display attributes, and control sequence objects. The MIB is constructed to accurately reflect the additions and deletions of objects in the network engines as the changes occur. The custom MIB defines explicit traps and associated attributes that align with Metasys alarm messages, making data correlation (parsing/sorting) at the NMS straightforward and seamless.