On 3/12/11 12:06 AM, QDS - Leonard Siu wrote:
I am currently using InterMapper to map out devices which have the architecture
below:
InterMapper --> Master Device (1) --> Slave Devices (100s to thousands!)
There can be hundreds to thousands slave-devices. Some of these slave devices
are temperature and humidity sensors, which make sense to use the poll-method.
Others are event driven devices such as dry-contact and motion sensors.
The event-driven devices are where I am having issue.
I can create an SNMP trap to InterMapper, however, because all the device have
a single IP address, all of them will receive the SNMP message. This is an
issue, for example I have to binary (open/close) event device A and B and an
alarm occurs when it is in open state:
Let's start with both A and B in closed state hence no alarm.
- When A opens, traps sent to both A and B. Only A gets an alarm.
- When B opens, traps send to both A and B. B gets an alarm, but A's alarm will
get reset!
For this architecture, I would recommend looking first at Alarm Points.
Alarm Points are designed to handle trap notifications efficiently when
you have many sensors behind a single IP address.
With alarm points, the "break" feature will allow you to stop evaluating
the alarm point rules when you determine that the SNMP trap is from
another sensor. Thus, B's alarm won't reset A's existing alarm.
I can use the custom-snmp probe which will cause a query again, but with
thousands of devices to a single IP, I will trigger thousands of SNMP query
every time an event occurs.
You may be able to use a custom-snmp-trap probe. I am not sure if this
will help or not -- In your situation, it sounds like it is desirable to
disable the "trap-directed" polling feature.
--
Bill Fisher
Dartware, LLC
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: intermapper-talk-...@list.dartware.com
