- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Found event 32 in EMS Event
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2007 05:09 PM
08-03-2007 05:09 PM
Found event 32 in EMS Event
I am 1 of the user of HP-UX 11 running on HP rp2470. Recently we received a lot of message from syslog as following:
------ 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 161742850 -r /system/events/core_hw/core_hw -n 161742849 -a
After execute the above command, here is the detail of the error message:
CURRENT MONITOR DATA:
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
Summary:
Service processor not responding
Description of Error:
The operating system is unable to communicate with the service processo
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 hun
(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 the
select "R", use the HP-UX command `stty +resetGSP press the service processor reset button. If this solves the prob
(if the I2C access test now works) and the system is an N-Class,
rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the servi
processor firmware revision using the service processor command "H
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
that the service processor responds to commands. If the service
processor has failed, contact your HP support representative to ch
the core I/O board.
There could be a problem with the system board.
Contact your HP support representative to check the system board i
necessary.
Additional Event Data:
Event Id............: 0x46b2e72200000000
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):
0x46b2e72100000000
Additional System Data:
System Model Number.............: 9000/800/A500-7X
OS Version......................: B.11.11
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
I reported to HP support & they come onsite to replace the GSP board with firmware version C.02.14.
But the the message above is come back again after 4 days later.
I am still can't figure out what is wrong with our server ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2007 11:33 PM
08-03-2007 11:33 PM
Re: Found event 32 in EMS Event
Also consider updating to a later rev of diagnostics, your rev is now out of date and unsupported.
-denver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2007 10:12 PM
08-05-2007 10:12 PM
Re: Found event 32 in EMS Event
You are seeing a known problem with that release of the OnlineDiags on A, L and N-class systems. You should upgrade to the current version, A.57.00, which should fix that problem.
Download from http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE
Version table: http://www.docs.hp.com/en/diag/stm/stm_upd.htm#table
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2007 10:48 PM
08-05-2007 10:48 PM
Re: Found event 32 in EMS Event
It does seem like a diagnositics problem and not a problem with the GSP card.
The card works? You can connect to it, right?
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 03:34 PM
08-21-2007 03:34 PM
Re: Found event 32 in EMS Event
Sorry for too late to reply here. I will try every approach which is suggested by anyone of you.
Thanks for your help.
Further questions:
1. How to get PDC firmware version?
2. Do I need to reboot the server during OnlineDiags upgrade process?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 03:41 PM
08-21-2007 03:41 PM
Re: Found event 32 in EMS Event
I think the GSP board is working fine, I can logon to GSP command thru console.
In fact HP engineer have replaced the GSP board for 2 times, but still not resolve the problem above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 07:52 PM
08-21-2007 07:52 PM
Re: Found event 32 in EMS Event
You don't need to upgrade the firmware to fix this problem, but you should consider updating it if it's not the latest version.
Installing the OnlineDiags does not require a reboot (unless there's a dependency on a kernel fileset, but I don't think there is).
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 11:13 PM
08-21-2007 11:13 PM
Re: Found event 32 in EMS Event
As mentioned before, this is a known problem with the diagnostics, not the GSP board. Download and install the latest diagnostics:
http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE
It will require a reboot after installing the diagnostics.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 11:21 PM
08-21-2007 11:21 PM
Re: Found event 32 in EMS Event
Andrew