L-class leds flashing

[Abdulrahman Mohd Sheday]

some time on l-class on the front panel flashing light appear ,
on the GSP
alert level 2 : non-urgent operator attention required
source 6 : platform
source details : 7 power monitor
source ID :0
Proplem Details :4 Internal failure
caller activity :2 : operation status : F
caller subactivity :00 :unspecified reporting entity type :2
Power Monitor
Reporting Entity ID : 00

[Steve Steel]

Hi


Look at

http://forums1-qa2.mayfield.hp.com/cm/QuestionAnswer/1,,0x85e8ff77de2bd611abd50090277a778c,00.html


nice info



Steve Steel

[melvyn burnard]

I have edited the subject to be something understandable, an dmoved this to the Server->9000 forum

[Zeev Schultz]

Before I even start - strongly reccomended to
consult HP Support about this.
A brief analysis points to the 'platform
monitor' failure - the card , connected to the
system board and monitors fans and power supplies.Now,it can also act in the simmilar way in case of fan / powersupply replace and in this case the Platform monitor is ok.Again,
open a hardware call in the local HP Response
center,take all recent GSP alerts and describe
the problem.

[John Payne_2]

Have you rebooted this machine recently. This could be an indication of a reboot. Generally, the errors are not 'necessarily' a problem unless the alert level is higher than 6. A level 2 alert is pretty much telling you that at some point, the power to a component went down. (like during a reboot.) You can always call HP to ask about it, though.

Hope it helps.

John

[Ross Martin]

The kind of message you got is an indication that someone most likely removed power from the L-Class by pulling the plug, rather than an orderly shutdown or using the GSP command 'PC' to power off the system.

Firmware can get confused when the plug is pulled and these kinds of errors can be intermittently experienced.

It is an EXTERNAL_READ_ERROR, so an outside influence has induced the message. The 'internal error' means that it was confused and wasn't able to identify the source of the problem at the time of failure.

If it persists, you may want to have hardware look at the firmware revision to make sure you are current.

Hope that helps.

Ross Martin