Asentria SiteBoss 530 User Manual
76
4. Every trap MLR and inform MLR has its last line be "END".
5. The entire MLR must conform to the following rules:
- The maximum size of a line is 160 bytes.
- The maximum number of lines allowed in an MLR is 12.
- The maximum total size for an MLR is 1200 bytes.
The unit ignores any varBinds which would cause it to break any of the above rules.
The unit stores notifications in the Event log depending on the Event Log storage settings (Setup -> Event Log
Settings -> Event Log menu). If Store Data Alarm Records is enabled (default is disabled), then all notification
MLRs are stored in the Event Log. Since notification MLRs are stored in the Event Log, the user can poll them by
any means of polling the Event Log (
TYPE EVENTS
command, FTP, or setup menu).
Setting Key
net.trapcap.enable
SNMP Informs
SNMP Inform requires a SMIv2 MIB. When loaded into an SNMP manager, the Asentria SMIv2 MIBs require an
associated MIB called Asentria-Root. Both are available from the Asentria website (
.
SNMP Inform support (that is, sending SNMP Informs) was added in S530 version 2.00.150.
Unlike SNMP Traps, which do not require acknowledgement from the receiving node, SNMP Informs do require
an acknowledgement, which provides confirmation that it was delivered.
Configuration
SNMP Informs are configured using the following Setting Keys:
net.snmp.ntfn.attempts
This is the number of attempts of sending a notification (trap/inform) per cycle (that is, the initial a
retries). If this is 0 then there is 1 infinite cycle.
net.snmp.ntfn.timeout
This is the number of seconds between 2 attempts to send an SNMP notification in the same cycle.
net.snmp.ntfn.cycles
A cycle is a set of notification attempts delimited by a successful action delivery or snooze period. This
setting is the maximum number of cycles to try per notification action, where one notification action
corresponds to one "inform" keyword in an action list for an event.
net.snmp.ntfn.snooze
The snooze period measures the time in minutes between two SNMP notification cycles for any one
notification action. That is, if you have two events generate informs, each inform will have its own
timeouts for retries and cycles, and its own snooze period.
Then set up an event which does an inform action to an SNMP manager or inform receiver. E.g.,
event.sched[1].actions
=inform(10.10.5.10).
An Asentria S530 with notification capture enabled can
serve as an inform receiver. Remember you can't just send an inform to anything: you must send it to a machine
capable of replying to the unit with an inform response. Only when the unit gets the inform response will it
consider the inform action a success.
Summary of Contents for SiteBoss 530
Page 6: ......
