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

rp7420 unexpected reboot see ts99 attached

 

rp7420 unexpected reboot see ts99 attached

This appears to point to a cpu fault any help would be appreciated.
4 REPLIES 4

Re: rp7420 unexpected reboot see ts99 attached

Hello Ian,
I check the ts99. Do you got some I/O errors at OLDsyslog.log? If no, you have an problem with cellboard at Cell1.

Regards
Mirko

Re: rp7420 unexpected reboot see ts99 attached

Thanks
No Errors in Log.
We were thinking of changing the second CPU on Cell One as this is deconfigured but was configured on TS98.
Do you know of any problems we may encounter whilst doing this?

Re: rp7420 unexpected reboot see ts99 attached

Hello Ian,
I found this at ts99:
[.....]
Cell: 1
CPU: 0
CPU is present and not deconfigured.
Cell: 1
CPU: 2
CPU is present and deconfigured. <- ?!
Cell: 1
CPU: 3
CPU is present and deconfigured. <- ?!
Cell: 1
CPU: 4
CPU is present and not deconfigured.
Cell: 1
CPU: 5
CPU is present and not deconfigured.
Cell: 1
CPU: 6
There is no CPU in the slot.
Cell: 1
CPU: 7
There is no CPU in the slot.
[.....]
Whats with CPU3 at Cell1?
If CPU3 was ok before the crash and its deconfigured now you have an problem at the cellboard or with the CellController (CC)
(see attachted doc.)

If you wnats to replace the defective parts work with normal precautions and take care with electrostatic.

I hope it helps you.
Regards
Mirko

PS: dont forget the points, and if you give me your mail I send more informations about the system
Sameer_Nirmal
Honored Contributor

Re: rp7420 unexpected reboot see ts99 attached

Hi,

I would suspect a problem with CPU dual-core module 2 (CPU 2&3) as they are being shown as "deconfigured".

It looks like those CPUs state (either invalid/malfunctioning) caused the HPMC causing system reboot. Similarly cell board recofiguration was done excluding those two CPUs. I would take a look at FPL
MP -> SL -> FP

I don't see any issue in removing the CPU module 2 as the server has already booted successfully after "de-configuring" those problematic CPUs.