HPUX SFM event levels in System Event Analyzer (SEA)

[R Morgan]

Environment:

Managed System:

B.11.23 ia64 hp server rx3600

SysFaultMgmt B.07.03.02.01
LVMProvider R11.23.007 CIM/WBEM Provider for LVM
VMProvider A.01.20.69 WBEM Provider for Integrity VM
WBEMSvcs A.02.05.08 HP WBEM Services for HP-UX


Hosting Device:

Windows Server 2008

HP Remote Support Standard A.05.40
HP WBES 6.0


We recently had power problems at a remote site that caused the HVAC to fail.
The room temperature climbed quickly and the HPUX servers dutifully reported the temperature event and the machine check in the event log:

.
.
.
Minor 101011 System Firmware 2010-##-## ##:##:## System temperature is out of normal range.
.
.
Critical 4559 System Hardware 2010-##-## ##:##:## Machine Check initiated
.
.

The 'Machine Check initiated' event was picked up in System Event Analyzer (SEA), but the preceeding 'System temperature is out of normal range' event was not.

I'm concerned that the only indication I received through SEA (and email) was of an event that occured after the server was restared, with no SEA (or email) alert about the climbing temperature.

Does the WBES subscription used for SFM only look at 'critical' events?

I've been very confident in SEA up to this point with EVA monitoring, but I am very concerned that it is not as responsive and proactive when it comes to HPUX events.

Any advice and/or assistance is appreciated.

Robert

[Michael Leu]

AFAIK only events that are relevant for opening a case at HP get processed by SEA.

Just recently I had the same temperature warnings on a few HP-UX boxes (wihout MCA). These events were in visible in SIM as a minor WBEM event.

So you probably should configure SIM itself to send you a email. Go to 'Options -> Events -> Automatic Event Handling' and create a task.

[R Morgan]

Thank you. That makes sense.

We don't currently use SIM, only the System Management Homepage. I will look at the SIM installation and configuration.

Robert

[Michael Leu]

So you don't have a SIM?

The HP-UX system should also have sent a mail to root that looks like this:

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Tue Aug 24 02:52:24 2010

migzmd10 sent Event Monitor notification information:

/system/events/ia64_corehw/core_hw is >= 3.
Its current value is MAJORWARNING(3).



Event data from monitor:

Event Time..........: Tue Aug 24 02:52:19 2010
Severity............: MAJORWARNING
Monitor.............: ia64_corehw
Event #.............: 101011
System..............:

Summary:

System temperature is out of normal range.

Description of Error:

The system temperature is not within normal operating range. It is
higher than required operating range.