[EMAIL PROTECTED] wrote:
>
> I believe that I do not truly understand what causes a sensor event.
> For example, I have registered event handlers for both my discrete and
> threshold sensors using the proper relative event handler add
> functions. However, if I power down the remote unit that I’m
> monitoring, this does not generate an event. If I re-run the
> monitoring tool, it will see the problem when it “discovers” the
> sensor for the first time, so that part is functioning as I expected.
> Do I need to add additional event handlers other than just sensor
> event handlers? Or am I simply misunderstanding what they do?
>
> Thanks again,
>
> Jen
>
Events come out on an analog sensor when it goes outside the specified
thresholds, and then when it goes back into the given threshold minus
any hysteresis.

For discrete sensors, it happens when a specified bit changes.

In both cases, the following apply:

    * The sensor has to support events, and it has to support them on
      that specific threshold/bit. You have to query the sensor to be
      sure it supports events.
    * The sensor has to have events enabled for the specific
      threshold/bit enabled. Some sensors have a enable for the whole
      sensor, some have it on a per-bit basis, and some are always on
      (governed by the global enable).
    * There is the concept of a global enable on a MC; if the event
      receiver is not set then events are not sent. OpenIPMI sets this
      by default, so that shouldn't be a problem.
    * When a system is powered off, events are often disabled for many
      sensors as they don't make any sense. Voltage sensors, for
      instance, are generally disabled when the system is powered off.
      This is not in the spec, but seems to be common practice.
    * OpenIPMI will ignore all events that happened before it started.
      You can still scan the SEL to get them, and there are functions
      that allow them to be interpreted, but by default they are not
      delivered as "normal" events. This is when OpenIPMI starts, not
      the system being monitored, so this doesn't seem to apply to your
      scenario.


It's also possible that events are being delivered but cannot be
properly correlated to a sensor.

I'd recommend trying this out with openipmigui. You should be able to do
everything you need there to try this out, and I know it works. You
should be able to look at the SEL; the events will have the sensor
displayed if it can properly interpret them. You can cause the event and
it should appear in the SEL.

-corey

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to