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

N4000 Alert Level 2

 
Simon Cox_3
Occasional Advisor

N4000 Alert Level 2

Hi. Our N4000 logs the following chassis code on every boot-up.
System performance seems to be unnaffected and no other errors have been logged.
This seems to have followed on since a memory & internal disk upgrade.

Can anyone tell me what the chassis code specifically means please?




Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 11/25/2004 TIME: 14:20:22
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 0
PROBLEM DETAIL: B = parity error

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 33 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x7000102B82006332 00000000 00571800 type 14 = Problem Detail
0x5800182B82006332 0000680A 190E1416 type 11 = Timestamp 11/25/2004 14:20:22
7 REPLIES 7
Ranjith_5
Honored Contributor

Re: N4000 Alert Level 2

As per HPs chasis code details for N4000 there is no FRU failure in your machine.

As per the table points there should be a parity error on the newly added module.You can remove the modules you have added to the server recently and see what happens. See whether the logs are generated again.

Also view the chasis codes through GSP once.

I am attaching the IO chasis code table with this.


Other docs will be attached with my next mesg.

Regards,
Syam
Ranjith_5
Honored Contributor

Re: N4000 Alert Level 2

Chasis code details.

Find the attached PDF.

Regards,
Syam
Ranjith_5
Honored Contributor

Re: N4000 Alert Level 2

Chasis code Interpretation.
Find the attached PDF.

Regards,
Syam
Jim Thomas_5
Advisor

Re: N4000 Alert Level 2

Actually, this sort of chassis code is possible if power-on self test experiences a correctable memory error during testing of the I/O hardware. I suspect that you have a memory DIMM problem that is causing rather consistent single bit memory errors. I suggest checking the memory error logs and the PDT logs via STM. Replace any memory DIMM(s) that show pseudo-solid single bit errors and this Alert Level 2 event during selftest should go away.
Simon Cox_3
Occasional Advisor

Re: N4000 Alert Level 2

Many thanks for your help.