EMS Event Notification: Event 32

[Consuelo Sierra]

I get in the root mail the Event 32 from EMS. In contact with HP support they advise me to upgrade the GPS firmware to A.01.10 version. I have donde it but the message is still appearing. Anyone of you know what can I do to the message disappear? The message that appear in the root mail is the following:

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

Notification Time: Wed Jul 17 23:57:54 2002

fscp1 sent Event Monitor notification information:

/system/events/core_hw/core_hw is >= 3.
Its current value is SERIOUS(4).



Event data from monitor:

Event Time..........: Wed Jul 17 23:57:53 2002
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: fscp1

Summary:
Service processor not responding


Description of Error:

The operating system is unable to communicate with the service processor.

Probable Cause / Recommended Action:

The support bus which connects the system processors, the service
processor and the Power Monitor or Platform Monitor may have become hung.
(The support bus can be tested by issuing the service processor command
"XD", and selecting the I2C access test).
To reset the bus, issue the service processor command "XD" and then
select "R", use the HP-UX command `stty +resetGSP press the service processor reset button. If this solves the problem
(if the I2C access test now works) and the system is an N-Class,
rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the service
processor firmware revision using the service processor command "HE".
If the service processor firmware version is less than A.01.09,
schedule an update of the service processor firmware to version
A.01.09 or a more recent version to prevent a reoccurrence of this
problem.

There could be a problem with the service processor.
Verify that the service processor appears to be operating normally.
This can be done by typing a B at the console and verifying
that the service processor responds to commands. If the service
processor has failed, contact your HP support representative to check
the core I/O board.

There could be a problem with the system board.
Contact your HP support representative to check the system board if
necessary.

Additional Event Data:
System IP Address...: 1.1.1.1
Event Id............: 0x3d35e86100000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_core_hw.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 4
Associated OS error log entry id(s):
0x3d35e86100000000
Additional System Data:
System Model Number.............: 9000/800/N4000-44
OS Version......................: B.11.00
STM Version.....................: A.31.00
EMS Version.....................: A.03.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_core_hw.htm#32

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


FRU Physical Location: 0xffffffffffffff00
FRU Source = 0 (unknown, no source stated)
Source Detail = 0 (unknown, no source stated)

[Pete Randall]

From the link provided in your message:

Cause / Action:
For N-Class, rp7400, L-Class, rp5400, rp5430, rp5450 and rp5470 systems:
The support bus which connects the system processors, the service processor and the Power Monitor or Platform
Monitor may have become hung. (The support bus can be tested by issuing the service processor command "XD",
and selecting the I2C access test). To reset the bus, issue the service processor command "XD" and then select
"R", use the HP-UX command `stty +resetGSP There could be a problem with the service processor. Verify that
the service processor appears to be operating normally. This can be done by typing a B at the console and
verifying that the service processor responds to commands. If the service processor has failed, contact your HP
support representative to check the core I/O board.
There could be a problem with the system board. Contact your HP support representative to check the system
board if necessary.


I think I'd follow that advice and contact HP support.

Pete