AlarmEventsType returns Alarm Message even in Normal State

[sesa180961_brid]

I obtain alarms (AlarmEventsType) from SBO using EWS Client's GetAlarmEvents() or GetUpdatedAlarmEvents() method.

I am interested in the "Message" property of the AlarmEventsType object.

I am assuming that "Message" is going to be:

• "Alarm Message" property of the alarm in SBO if the alarm is in Alarm state and
• "Reset Message" if the alarm is in Normal state of the alarm in SBO.

When I obtained alarms that are in active state, the Alarm Message looks appropriate.

But the "Message" of the Normal alarm in still the "Alarm Message". It is not the Reset Message.

I am using EwsClient v2.2.108.0 and SBO is v1.8.

Source Id	Source Name	Acknowledgable State	State	Type	Message
02/IAD36/Power Manager Data/IAD36_H106/PDU106A-5/Alarms/Critical_AlmR	Critical_AlmR	No	Normal	IAD36_H106_CriticalAlarm	IAD36 H106 PDU106A-5 Critical Alarm is in Alarm
02/IAD36/Power Manager Data/IAD36_H106/PDU106B-1/Alarms/Critical_AlmR	Critical_AlmR	No	Normal	IAD36_H106_CriticalAlarm	IAD36 H106 PDU106B-1 Critical Alarm is in Alarm

Has anyone faced the same issue?

[JeffBowman]

Hi Maneesh,

When you say AlarmEventType, you don't mean the 'IAD36_H106_CriticalAlarm' value right?

In any case, what you are expecting should be the case, but I am not sure why SBO does not do this.. I am wondering if it is a defect for SBO.. Can you show some screenshots of this issue? (and your SBO config)

Regards,

-Jeff

[sesa180961_brid]

When I said AlarmEvents Type, I meant the AlarmEvents from SBO.

The issue I am seeing is that when the alarm is in normal state, EWS returns the the same Message.

See the column "Message" in the above table I copied.

For example, when an alarm returns to normal state, I would like to see the Reset Message not the Alarm Message.

I will add more info tomorrow.

[sesa180961_brid]

Hi Jeff,

I think I found the workflow.

Here is the alarm in alarm state:

In SBO,  there is no problem if an alarm goes from Alarm -> Normal -> Acknowledged, then the alarm message is the Reset message.

But if an alarm goes from Alarm -> Acknowledged -> Normal, then the alarm message is still the Alarm message.

Hope this helps you understand the issue I am having.

Please let me know if you need more details.

[JeffBowman]

Hi Maneesh,

After seeing what you found, what you are seeing is exactly the behavior I would expect to happen.

This is because the alarm in the second scenario NEVER goes into the 'Reset' alarm state. The 'Reset' alarm state only ever occurs when an Alarm that is in the 'Alarm' state, goes back to 'Normal' without first being 'Acknowleged'. Which is exactly what you see in the first scenario (that's why it works as you expect.)

Perhaps you are a bit confused when it comes to 'Reset' vs 'Normal'. 'Reset' only occurs like I mentioned above. 'Normal' occurs in really 3 occasions:

1. The alarm has NEVER been activated.
2. When an Alarm in the 'Alarm' state is acknowledged into the 'Acknowledged' state and then the value returns to normal.
3. When an Alarm in the 'Alarm' state returns to 'Normal' (this is the 'Reset') state and is then acknowledged. When the alarm is acknowledged in this case, it does not go to the 'Acknowledged' state, but goes back to 'Normal' instead.

Regards,

-Jeff

[sesa180961_brid]

Hi Jeff,

If an alarm is in Alarm state and a user acknowledged it. After acknowledgement, the alarm returned to Normal.

Now the alarm is in Normal state but the alarm text or message is Alarm message.

The end user is seeing that the alarm state is normal but the alarm message show that the alarm is in alarm state.

What is the work around for this?

Do I have to check it in my program? Is there a way for me to get the Normal/Reset message so that I can check in my program to see that the alarm is in Normal state and I sent the end user the Normal/Reset message?

[JeffBowman · Accepted solution]

I believe there really is no 'Work around' for this. As SBO doesn't have a concept of 'Normal' message. It just reuses the previous message that it was when it returned to normal. So this could be the Alarm message, or the Reset message.

As far as retrieving the messages ahead of time (which I guess techincally is a workaround, if you have some logic around this as you said.) Try this:

If the alarm item id is '02/Server 1/MyAlarm'

If you do a GetValues on '12/Server 1/MyAlarm/ResetMessage'. This should give you a response like:

      <EWSv121:GetValuesResponse version="1.2">

         <EWSv121:GetValuesItems>

            <EWSv121:ValueItem>

               <EWSv121:Id>12/BigDataES/Change of State Alarm/ResetMessage</EWSv121:Id>

               <EWSv121:State>0</EWSv121:State>

               <EWSv121:Value>I'm The Reset Message</EWSv121:Value>

            </EWSv121:ValueItem>

         </EWSv121:GetValuesItems>

         <EWSv121:GetValuesErrorResults/>

      </EWSv121:GetValuesResponse>

Regards,

-Jeff

[sesa180961_brid]

Will try this. Thanks Jeff!