- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Bad GSP on L2000?
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
Discussions
Discussions
Forums
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
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
тАО04-16-2004 02:22 AM
тАО04-16-2004 02:22 AM
====
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
Summary:
Service processor not responding
====
The machine's console is non-responsive, including trying CTRL-B. Both LEDs on (what I believe is) the GSP board are red.
Everything else seems fine. The server is up and all applications are running just fine, as far as I can tell.
My conclusion is that the GSP board (A6696A?) is bad.
My questions:
1. Is this conclusion likely correct?
2. What should I do? There is no HP support, there is no warranty. The server is scheduled to be decommissioned later this year. What's do I risk by just ignoring the problem?
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2004 03:43 AM
тАО04-16-2004 03:43 AM
Re: Bad GSP on L2000?
If the error is serious, then you may not be able to boot up in that state.
You should probably replace it, they are available through hp's parts store. go toL
http://partsurfer.hp.com/
and look up the a6696a in the top box,
then click the arrow next to 'list all parts' and you can order the appropriate parts from the window that pops up.
Josh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2004 03:55 AM
тАО04-16-2004 03:55 AM
Re: Bad GSP on L2000?
You'll have to enter the A6696A PN into the left box ("by model number or name"). Then click on the link for the name of the part.
Then click the link next to 'for all parts'
You can see that they no longer provide the a6696a, you will have to order the a6696b.
the part number that you need to order is A6144-69112.
Click on the 'order selected parts' dialog, and it will open up the hp parts store.
click on the link on the left side 'order parts', and enter the part in one of the boxes.
click 'check price and availability >>'.
Josh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2004 04:43 AM
тАО04-16-2004 04:43 AM
Re: Bad GSP on L2000?
Hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2004 05:07 PM
тАО04-16-2004 05:07 PM
SolutionI would check to make sure you are up to date on your firmware. For the B revision GSP the patch number is PF_CCANGSP0220. It has the following fix text in it:
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:
= 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
EMS Event Code 31 or 36
An EMS error event similar to the one below which
instructs the customer to reset the GSP or replace the
Platform Monitor or System Board. Note that you
will receive an EMS 36 event for a system with a
"platform monitor" (A-class and L-class) and an EMS
event 31 for a system with a "power monitor" (N-class)
---- Event Monitoring Service Event Notification ----<
Event Notification Time: Thu Feb 7 06:06:02 2002
jmcdb2 sent Event Monitor notification information:
= 1.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Thu Feb 7 06:06:02 2002
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 36
System..............: jmcdb2
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2004 05:13 AM
тАО04-19-2004 05:13 AM