EMS message question

[Alex Lavrov.]

Hello, I recieved this message from EMS:

" Communications between the processor dependent code (PDC) and the service processor has failed. Verify service processor operation. Enter chassis log manually with service processor commands."

I checked this link:
http://docs.hp.com/en/diag/ems/dm_core_hw.htm#E25
but there is no valueable info.

What are my next steps from here?


Thanx.

[Robert-Jan Goossens]

Hi Alex,

The only thing you can do is to login to the GSP and check the logs.

from console, press ctrl+b
GSP> sl
press 'e'
press 'n' (for filtering)
press 'q' (quit)
GSP> co (back to console)

Check the firmware version of your gsp and the diagnostics version.

Best regards,
Robert-Jan

[Rick Garland]

I remember encountering this issue on some L class systems.

Check logs, make sure all is OK.

Call HP to have firmware upgrade

[Scot Bean]

Quick fix may be to do manual reset of the GSP processor. Most server models have a button on the back or sometimes inside a side panel.

[Alex Lavrov.]

Thanx!
I'll try these things.

Regards.

[Andrew Merritt_2]

Rick's right; there is a known problem which causes this which should be fixed by the latest PDHC firmware.

Andrew

[Victor BERRIDGE]

Yep and till yu install the latest diags and update your firmware you can use this command:
stty +resetGSP ...
Here is what I went through some (quite) time ago:
PROBLEM
Trying to reset the GSP using the command:

stty +resetGSP < /dev/GSPdiag1

and gets the msg "This operation is not permitted"

The customer had manually created GSPdiag1 because the insf command would not
create it.


CONFIGURATION
HP-UX
L class
GSP version B.02.14




RESOLUTION

The revision of Gsp was B.02.14
The service notes for this firmware release state:

Insure operating system patches are installed to change the device drivers
prior to installing the firmware upgrade. These patches will also be required
for any future releases of firmware. The list below shows the patches required
for 11.11 and 11.00

11.00

Console Driver Patch [PHNE_27393/PACHRDME/English]

INSF Patch [PHCO_27370/PACHRDME/English]



11.11

Console Driver Patch [PHNE_26326/PACHRDME/English]

INSF Patch [PHCO_27243/PACHRDME/English]


After installing these patches the insf command created GSPdiag1 and the
stty +resetGSP < /dev/GSPdiag1 command ran fine.

This error can be created by igniting a system that has the B rev of GSP
firmware from an image taken from a system using the A rev of GSP firmware.
The A rev does not require the patches.


Good luck
All the best
Victor