Asentria SiteBoss 530 User Manual
97
S530UserTrap1000 TRAP-TYPE
ENTERPRISE S530
VARIABLES { siteName, esIndex, esName, trapEventTypeNumber,
trapEventTypeName, esIndexPoint, esPointName, esID,
clock, trapIncludedValue, trapIncludedString,
trapEventClassNumber, trapEventClassName }
DESCRIPTION
"This user-defined trap is issued when an event happens that causes a
trap with specific trap type 1000."
::= 1000
Above there are various alarm values in this trap including the trapIncludedString referenced in the Standard Trap.
Email Alarms
Email alarms contain a concatenated alarm string, which follows the format of:
Date Time :: SiteName :: Sensor Pod/Bank name :: Sensor Point Name :: Alarm Alias
For example, a typical Email notification for a temperature alarm might look like the following. Note that the message
subject contains the same data as the message body, except it is truncated if necessary
Sent: Friday, September 25, 2009 3:59 PM
To: [email protected]
Subject: Event - -
09/24 15:59 :: San Diego Site #12 :: Sensor Pod 12 :: Cabinet Temp ::
Temperature Very High
09/24 15:59 :: San Diego Site #12 :: Sensor Pod 12 :: Cabinet Temp :: Temperature Very High
Asentria Alarms
Version 1.1 (default) for TCP
An Asentria Alarm sent via TCP is called a Notice. A notice is a piece of data formatted in printable ASCII: a set of
lines delimited by CRLF. Each line is of the format <field>: <data>CRLF. The first line has <field> = "ID" (without the
quotes). The last line has <field> = "TEXTx" (without the quotes, where x is some number between 1 and 30). The
particular format the describes the alarm, and is one of the actions that can be configured for each alarm. A notice that
rides on TCP/IP is called a "talert", short for "TCP alert". Talerts are delivered according the the Asentria Alarm
Protocol, which over TCP is just a specification of message format.
Notices ride on an IP network. The IP network is facilitated by broadband internet connection or PPP in this model.
When riding on a network from a unit to SitePath, it is assumed that a notice is normally tunneled over a VPN via a
VPNG. In situations where the VPN is unavailable, the notice rides on a PPP link to SitePath via the PPPG. When
riding on a network from a VPNG to the notice receiver (or on a network from a PPPG to the notice receiver), a notice
travels in plaintext (i.e., not encrypted).
The format below is common to all events that can trigger a notice:
<Answer string (i.e., the value of
sys.answer
)>
<Sitename (i.e., the value of
sys.sitename
)>
Asentria Alarm Notice ver. 1.1
ID : 00
Date : mm/dd/yy
Time : hh:mm:ss
TargetPort:
TargetName:
AlarmType :
AlarmMsg :
Severity : {as specified by class/severity}
AlarmNum : {the value of the trap number setting for the triggering event}
Threshold :
Summary of Contents for SiteBoss 530
Page 6: ......
