[EMAIL PROTECTED] wrote on 08/03/2007 11:21:30
AM:
> Hello,
>
> Someone knows how this behaviour could be possible? I'm using OpenHPI
2.8.1.
>
> I have a deamon running on one blade connected to my shelf manager.
> I have another deamon running on another blade connected to the same
> shelf manager. My DAT is populated like that:
>
> Blade 5:
> OpenHPI> dat
> (1) 2007-08-02 17:01:49 MAJOR - SENSOR 27/4097 0x10
> (2) 2007-08-02 17:01:49 MAJOR - SENSOR 27/4097 0x1
> No alarms in DAT.
> OpenHPI>
>
> Blade 10:
> OpenHPI> dat
> (1) 2007-08-02 13:53:50 MAJOR - SENSOR 27/4097 0x10
> (2) 2007-08-02 13:53:50 MAJOR - SENSOR 27/4097 0x1
> (74) 2007-08-02 15:49:28 MAJOR - SENSOR 40/6 0x2
> (76) 2007-08-02 16:38:42 MAJOR - SENSOR 39/128 0x1000
> No alarms in DAT.
> OpenHPI>
>
> Daemon on Blade 5 was restarted once in a while, it's always re-
> inserting alarms 1-2. Is Blade 10 missed the assertion false for
> alarm 74-76? Or Blade 5 is never receiving the assertion true?
Looks like alarms 1-2 are always in an asserted state and none of the
daemons is detecting otherwise.
One thing is that the DATs between HPI instances will not necessarily be
the same. It depends on whether both instances are receiving the same
events that you will then see the same DATs. It is possible that while
alarms 1-2 are detected on discovery of the resources, alarms 74/76 are not
necessarily detected during resource discovery but during normal event
polling. So if Blade 5 missed the events that would constitute alarms 74/75
because it was restarted, that would explain it.
>
> Also I noticed that when an alarm is inserted in one DAT, the same
> alarm could be described by a different AlarmId in another daemon
> DAT? How can I do a correlation of the Alarms if I'm using 2 daemons
> for high availability purpose? How can I use them so that I'm sure
> they will contain the same data?
The HPI specification does not require the implementation to keep multiple
instances in sync. It does require to keep multiple clients connecting to
the same HPI instance in sync. Ids can definitely be different across
instances and this is mentioned in the specification.
To correlate alarms across instances I would attempt to do a comparison on
the alarm condition by blanking out DomainId and ResourceId first. However,
HA issues with multiple HPI instances are left up to the user.
--Renier
>
> Regards,
>
> /jonathan-------------------------------------------------------------------------
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/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
