Asentria SiteBoss 571 UserManual
Page 113
Types of Alarm Notices
When alarms are detected by the SiteBoss and a notification event is warranted, you have a choice of number of
different alarm methods. Specifically these are:
(requires wireless modem expansion card)
(requires dial-up modem expansion card)
The following section describes these messages and how to use them.
SNMP Traps
SNMP Traps are alarm notices which are sent using TCP/IP and which conform to the requirements of the SNMP
protocol. In essence, the SNMP Trap is a TCP/IP alarm message using the SNMP protocol, which contains a
number of name/value pairs in its payload. In this payload the “name” is an SNMP Object ID and the “value” is the
value of that OID.
In the case of the S571 product, there are two defined SNMP traps that you can choose from. These traps are
defined in the SNMP MIB, which is provided with the S571 product (or which is available through the Asentria
website or
The first trap is a ‘Standard’ SNMP trap. This is the original SNMP trap format supported by Asentria products. In
this trap there are two name/value pairs in the trap payload;
‘siteName’
which is the sitename of the device
sending the trap and
‘stockTrapString’
which is a string value, which is the standard concatenated alarm
message string used for this and other alarms messages in the S571.
The stockTrapString message format looks like this:
Date Time :: SiteName :: Sensor Pod/Bank name :: Sensor Point Name :: Alarm Alias
For example, the stockTrapString might actually look like this
10/24 06:43 :: San Diego Site #12 :: Sensor Pod 12 :: Cabinet Temp :: Temperature Very High
For users familiar with SNMP, the actual SNMP MIB definition of the Standard SNMP looks like this:
S571StockTempTrap TRAP-TYPE
ENTERPRISE S571
VARIABLES { siteName, stockTrapString }
DESCRIPTION
"A stock temperature trap is issued when a temperature event
happens."
::= 120
The other kind of SNMP trap which you can use is
what we call a ‘User Defined Trap’. In this trap we provide for a
series of traps which each have an individual “Trap number”. This can be easier to integrate with management
systems because the manager can have rules setup to kick in when you get “trap # 1000” or “trap # 1001” on.
When using User Defined Traps, the trap number to use is assigned as part of the Event Definition Setup. In the
case of User Defined Traps, the payload of the trap contains a number of OID variables, essentially anything that
might be relevant to the particular alarm being transmitted. If the variable is not relevant for the alarm being
transmitted then that variable is null.
For users familiar with SNMP, the actual trap definition in the SNMP MIB looks like this:
S571UserTrap1000 TRAP-TYPE
ENTERPRISE S571
VARIABLES { siteName, esIndex, esName, trapEventTypeNumber,
trapEventTypeName, esIndexPoint, esPointName, esID,
clock, trapIncludedValue, trapIncludedString,
