HPE 9000 and HPE e3000 Servers
1753474 Members
4774 Online
108794 Solutions
New Discussion юеВ

Re: rp3410 - no console, no boot

 
rlowsky
New Member

rp3410 - no console, no boot

Two identical systems, the MP system status on the non-functioning unit shows:

System Processor Status:

Monarch Processor: 0
Processor Module 0: Not Installed
Processor Module 1: Not Installed

The functioning system shows that Processor Module 0: Installed and Configured. Can anyone tell me if this indicates that there's a bad processor module? I've attached the event logs but was unable to be sure from them whether or not the CPU is the culprit.

Thanks,

Roger
4 REPLIES 4
rlowsky
New Member

Re: rp3410 - no console, no boot

Forgot to add that the Virtual Front Panel indicates that the system is executing non operating system code / diagnostics.
Stefan Stechemesser
Honored Contributor

Re: rp3410 - no console, no boot

Hello,

the chassis codes do not have valid timestamps, so we don't know if they are old or from the current boot.
I would suggest you do the following:
1.) delete all MP logs with the sl (then c) command
2.) power off the system by unplugging the power cables.
3.) after reconnecting power, power the system on with the MP CM> pe command
4.) in CM> menu also issue the commands
sysrev
df -nc -all
ps
ss
5.) after a while, capture the new forward progress log (we then know that it is from the last boot)
6.) post everything here or open a HP support call and present that data.

It is not nessecarily a CPU problem. It can also be that the MP has no contact to the rest of the system.

best regards

Stefan
rlowsky
New Member

Re: rp3410 - no console, no boot

Stefan,

Did as you said except that the CM command you gave me "pe" did not work (see the attached screen capture). Instead, since I am at a remote site I used the CM command to power cycle.

Thanks,

Roger
rlowsky
New Member

Re: rp3410 - no console, no boot

As I suspected, the CPU was indeed the reason for my problem. With two identical units I was able to swap CPUs and the problem followed the non-functional one.