The operating system is unable to communicate with the service processor

[Stano_1]

Hi everyone,

We are probably facing service processor / card problem. The following message is appearing in the syslog file every day:

------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/system/events/core_hw/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 174063619 -r /system/events/core_hw/core_hw -n 174063618 -a

Besides of that green LED is flashing on the server chassis and we also can see Link Up / Down alarms on the switch port where server's service card is connected.

Can anybody help? Thanks

Regards,
Stano

[Chan 007]

Stano,

Run the command
/opt/resmon/bin/resdata -R 174063619 -r /system/events/core_hw/core_hw -n 174063618 -a

See what is gives as o/p.

Also Better raise a call with HP

Chan

[Stano_1]

Thanks for reply!

This is output of the command:

CURRENT MONITOR DATA:

Event Time..........: Tue Jan 24 09:28:46 2006
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: XYZ
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...: 10.215.1.101
Event Id............: 0x43d5f34e00000000
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..: 1
Associated OS error log entry id(s):
0x43d5f34e00000000
Additional System Data:
System Model Number.............: 9000/800/L2000-44
EMS Version.....................: A.03.20
STM Version.....................: A.28.00
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)
Cannot decode any remaining physical location data.

[Fabio Ettore]

Hi,

I ma pretty sure that the event is 32:

http://docs.hp.com/en/diag/ems/dm_core_hw.htm

Event 32


Check the 'Cause/Action' part.

Basically you should try the reset of the Guardian Service Processor (GSP) and firmware.

HTH>

Best regards,
Fabio

[MarkSyder]

As Fabio says, you should reset the GSP. You don't say what server you are using, but on an RP2450 this is easy. There is a small recessed button on the back of the server which says "GSP reset". Unfold a paper clip and push it into the hole till it presses the reset button.

If you're using a different server and there isn't such a button, please tell us your server model and someone will tell you how to reset GSP.

Mark Syder (like the drink but spelt different)

[Stano_1]

Thanks Fabio,

According to http://docs.hp.com/en/diag/ems/dm_core_hw.htm#32:
the following command should executed:
# stty +resetGSP GSP reset succeeded.

So obviously RESET was successful. I'm just wondering how do I check a firmware version? If a possible firmware upgrade would help to solve this problem.

[Fabio Ettore]

Hi Stano,

in order to obtain GSP firmware revision, connect on console and CTRL+B:

GSP>HE

and you will see a line with Firmware Revision.

I think so: if the message happens just one time then a reset should solve it definitely. If you see it more times I would suggest you to consider to open a call by HP and consider to upgrade firmware revision:

"
If the service processor firmware version is less than A.01.09, schedule and update of the service processor firmware to version A.01.09 or a more recent version to prevent a reoccurrence of this problem.
"

HTH.

Best regards,
Fabio

[Stano_1]

I have viewed GSP logs using SL command. This seem to turn off flashing front panel LED as well.

My current GSP firmware version according HE command is:
Hardware Revision L5 Firmware Revision B.02.07 Oct 17 2001,14:49:35

So firmware upgrade doesn't seem to apply.

Any other ideas? (HP support case is always the last option)

Thanks.

[Andrew Rutter · Accepted solution]

hi,

by the information you have supplied this is an l2000 B rev system.

you do also have an old version of gsp firmware that is most likely causing the problem.

you need to upgrade to this newer version

http://www4.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CCANGSPB0220&context=firmware:cpu


This is an excert from the patch details which details your exact problem.

EMS Event Code 32

The main symptom is the following EMS error event which
instructs the customer to reset the GSP or replace the
system board. This EMS error may be a recurring event
(in the worst case being logged once daily).
The EMS error will show up with this wording:

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

Notification Time: Sun Dec 16 17:46:54 2001

niscit 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..........: Sun Dec 16 17:46:54 2001
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: niscit


upgrade to this version and then monitor the system for a short while.

Andy

[Fabio Ettore]

Stano, the B rev is different than A rev, so even if A.01.09 is not meaningful in your instance pls consider to upgrade the B rev at the latest one (as Andy too wrote).

Thanks and regards,
Fabio