White Papers

VRTX Alert Management
OEM Event Data 1
[7:6] - 00b = unspecified in byte 2
01b = previous state and/or severity in byte 2
10b = OEM code in byte 2
11b = reserved
[5:4] - 00b = unspecified byte 3
01b = reserved
10b = OEM code in byte 3
11b = reserved
[3:0] - Offset from Event/Reading Type Code
Event Data 2
[7:4] - Optional OEM code bits or offset from ‘Severity’ Event/Reading
Type Code. (0Fh if unspecified).
[3:0] - Optional OEM code or offset from Event/Reading Type
Code for
previous event state. (0Fh if unspecified).
Event Data 3 Optional OEM code. FFh or not present or unspecified.
Table 2 - Event Data Field Contents
Types of Alerting Techniques
CMC has the following Alert Management interfaces Email, SNMP, and Remote Syslog.
Email Alert
SMTP is a protocol and set of requirements that allows CMC to transmit email over the Internet. CMC
is designed to use SMTP for communication purposes when sending email, and is only used for
outgoing messages. When chassis events have been configured to send Email based alerts, the
corresponding SMTP (Email) Server address has to be configured in the Chassis Overview > Alerts >
Email Alert Settings page. There are two other protocols―POP3 and IMAP, which are used for
retrieving emails on the Management station.
SMTP is the protocol defined for email communication between systems. The protocol has a defined
format of sending messages across a network, which comprises of a sender, recipient, message body,
and title. The message is broken down to the standard format which the receiver understands. The
message format is transformed into key value pairs, which can be decoded by the receiver on the
basis of encoding, and can be separated to different sections before sending. The email server at the
receiving end is designed to receive the message, decode, and reorganize based on each recipient’s n.