EMS event

[Shivkumar]

Dear Sirs;

I saw an alert form EMS event notification as below:

Message Group = EMS
Object =
Application = /USR/SBIN/SYSLOGD(1M) SYSLOG
Severity = WARNING

Message Text = E-Alert UXOS8004 ux EMS Event 14 21:21:17 Jasmine [4010]: ------ EMS Event Notification ------ Value: SERIOUS (4) for Resource: /system/events/core_hw/core_hw (Threshold: >= 3 )

What could be the reason for this ?

Thanks,
Shiv

[Joseph Loo]

hi shiv,

there should be some description of the event log.

this is warning message, so lest u r really worry, u may like to post it.

if it is CRITICAL, u may start to really worry.

regards.

[RAC_1 · Accepted solution]

In addition to the command, it will also ask you to execute a certain command to know more details. you seem to have problem GSP.

[Adisuria Wangsadinata_1]

Hi Shiv,

Check the file below :
/var/opt/resmon/log/event.log

Check the system log (SL) on GSP.

Check the system with 'ioscan -nf', make sure there's NO_HW status.

Check also whether the system giving the light on attention LED / fault LED.

Hope this information can help you.

Cheers,
AW

[morganelan]

I think this is caused by fans failure that raise air temperature in server location.

[morganelan]

Please post the output of command that follow this event notification to obtain event details, it should be like this:opt/resmon/bin/resdata -R 101056526 -r /system/events/core_hw/core_hw -n 101056539 -a

[Devender Khatana]

Hi,

The detailed error is reported in /var/opt/resmon/log/event.log. Edit the file and see the last entry. Or attach the file.

HTH,
Devender

[Alessandro Pilati]

Hi Shiv,
run the following command first:
/opt/resmon/bin/resdata -R -r /system/events/core_hw/core_hw -n -a

Where REQUEST_ID and NOTIFY_ID can be found in your syslog.log file, or in the output of "dmesg" command.

Check also /var/opt/resmon/log/event.log, where EMS messages are in full text explanation.

I need the Event ID, and I need your machine type, is it an HP9000? Cause as described in this document:
http://docs.hp.com/en/diag/ems/dm_core_hw.htm
the Event 14 is only an information message...

Take this guide for EMS error understanding...
http://docs.hp.com/en/4316/ems_quick.pdf

Let us know

Regards,
Alex

[Shivkumar]

Here is the outout of the command "/opt/resmon/bin/resdata -R 262799362 -r /system/events/core_hw/core_hw -n 262799362 -a":-

CURRENT MONITOR DATA:

Event Time..........: Wed Sep 14 21:21:17 2005
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: xxxxxx
Summary:
Service processor not responding

...
...
...



Additional Event Data:
System IP Address...: xxxxxxxxxxxxx
Event Id............: 0x4328f6bd00000000
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):
0x4328f6bd00000000
Additional System Data:
System Model Number.............: 9000/800/N4000-55
OS Version......................: B.11.11
STM Version.....................: A.38.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)

Thanks,
Shiv

[Alessandro Pilati]

Shiv,
as described in the EVENT Description document...:

you should enter in Service Processor Command line and launch the XD command and select the I2C access test.
Then do a reset of the bus using the XD command and then select R.

Then do again the I2C test: if the problem is resolved, check the service processor firmware revision using the service processor command "HE".

The version must be >= A.01.09, plan an upgrade if it is lower version.
Check the correct running of service processor typing ctrl-B at the console, and
if the problem persists, contact HP support because could be a problem on the system board...

Hope this helps,
Alex

[morganelan]

Event 32

* Severity: Serious
* Event Summary: Service processor not responding
* Event Class: System
* Problem Description:
The operating system is unable to communicate with the service processor.
* 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 CTRLB 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.
For SuperDome systems:
There could be a problem with the service processor. Verify service processor operation. If the service processor has failed, Contact your HP support representative to check the service processor.
* Automated Recovery: None
* Event Generation Threshold: 1 detection
* Fault Notifier Event Generation Threshold: 1 detection

[Fabio Ettore]

Hi Shiv,

I saw more times that message.
Here the possible actions to solve:

- launch
stty +resetGSP
- if after this command you see yet the event then update the GSP firmware accordingly (you can open a call by HP Hardware Response Center);

- if after two steps above yet the message is there then a check on core I/O board is requested (again open a call by HP).

Please let us know the end of the story and if our posts helped you.

Best regards,
Fabio

[Adisuria Wangsadinata_1]

Hi Shiv,

From the EMS, the EMS refer to you to :

1. restart the GSP card, this can be done from the OS by executing the command below (need to check with ioscan command for GSP device file) :

stty +resetGSP
OR from GSP prompt by issue the service processor command "XD" and then select "R"

2. check the version of your GSP firmware by using the service processor command "HE" on GSP prompt.

3. log a call to HP if the problem still persist after you follow the step 1 & 2.

Hope this information can help you.

Cheers,
AW

[Alessandro Pilati]

Shiv,
take these links to the exact management at Service processor level:

http://docs.hp.com/en/rx2600rx56xx_update/rx2600rx56xx_update.pdf

http://www.decus.de/slides/sy2004/20_04/1a06.pdf

Cheers,
Alessandro