HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

HP Server HP-PRC-HP N4000 DOWN

 
SOLVED
Go to solution
Rhonda Lott
Occasional Contributor

HP Server HP-PRC-HP N4000 DOWN

I RECEIVED THE FOLLOWING MESSAGE BEFORE THE SERVER HUNG: My question is does this Alert Level 13 mean anything and is it pointing toward processor 1? Thx pls see below:

-- DATE: 06/13/2006 TIME: 03:25:57
-- ALERT LEVEL: 13 = System hang detected via timer popping
-- REASON FOR ALERT
-- SOURCE: 1 = processor
-- SOURCE DETAIL: 1 = processor general SOURCE ID: 0
-- PROBLEM DETAIL: 4 = timeout
-- LEDs: RUN ATTENTION FAULT REMOTE POWER
-- ON OFF OFF OFF ON
LED State: System running normally.
-- 0x78E000D41100F000 00000003 00000000 - type 15 = Activity Level/Timeout
-- 0x58E008D41100F000 00006A05 0D031939 - type 11 = Timestamp 06/13/2006 03:25:57


4 REPLIES 4
JASH_2
Trusted Contributor
Solution

Re: HP Server HP-PRC-HP N4000 DOWN

Rhonda,

Looks like it could be a problem with a processor. At the console do a cntl b and then sl and then e to examine your error logs in MP main menu. This will give you more of an idea of any problems. If you can see the front of your machine, does it have any lights on, or look at the VFP (virtual front panel) screen on the MP menu. If it has the fault light (red) on, then there is a major problem, if it has the flashing amber light, then there is an error message that needs to be read, but it is not terminal.

Hope this helps and you do not have a major problem.

Regards,

JASH
If I can, I will!
Michael Steele_2
Honored Contributor

Re: HP Server HP-PRC-HP N4000 DOWN

From the GSP > sl > e and paste in anything above alert level 6, for example your alert level 13.

From /var/tombstones/ts99 check for any HPMC's and paste in that information. Note the PDC version as you'll have to verify if you're current. Use an attachment please.

You may have to also TOC / reset the machine and get a crash dump of the core. But doing it now after the crash may be pointless. So first check to see if one was taken in /var/adm/crash, and if not, try getting one from the command line:

# savecrash -v [-r] -t

Here's a link to savecrash:

http://docs.hp.com/en/B2355-60103/savecrash.1M.html
Support Fatherhood - Stop Family Law
Sameer_Nirmal
Honored Contributor

Re: HP Server HP-PRC-HP N4000 DOWN

The alert messages indicates a watchdog timer of 3 minutes is expired on account of system hung. It is given by CPU 0 which is "monarch" cpu in the server.

AS said above,check following to see if any error messages pertaining to system hang logged.
GSP -> SL -> E
/var/tombstones/ts99 and ts98
/var/adm/syslog/OLDsyslog.log
/var/adm/crash for crash dump

Re: HP Server HP-PRC-HP N4000 DOWN

Hello Rhonda,

this is not associated with any true CPU hardware problem.
CPU1 was active and messaged this error.
Is this the first occurrence of this problem / system hung?
The reason for this is the GSP himself.
There are problems between GSP-Firmeware and Diagnostics. The communication between HP-UX and GSP is broken for a few sec. and the system went to Timeout and Hung, in worst case. But only with older Gsp-FW like B-02.0x and old Diagnostics like A.2x.00.

I think that you got EMS messages from system before this systemhung.
Check:
# /var/opt/resmon/log/event.log
Search:
Event #.............: 32
Summary:
Service processor not responding

Solution:
- Update GSP-FW to last version
- Update to new Diagnosticversion in dependency of your OS-Version

Checkout the current versions:
- Diagnostics:
start # cstm and you get Version A.xx.xx
- GSP-FW:
go to GSP with " Control b "
set " he " and you get the Version B.xx.xx

!Note: if you got GSP-FW like A.xx.xx I think the GSP-Card is not ok.

The from me described problem occures only with GSP-FW B.xx.xx

I hope it helps you

Regards
Mirko

PS: Also you can call HP for more help.