Blinking Red LEDs on ML350 G4 Server

A client's server shut itself off today with the fans running at high speed and both internal system health and External system health leds blinking red. The machine has a single Pentium P4, 3Gig processor and a single power supply. There is no sign of overheating anywhere in the machine but the room in which it lives was at 76 degrees Fahrenheit. Shutting down and restarting brought it back up but it shut down again about 2 hours later and now shuts down after a few minutes. I'm going to have to build them a new server overnight with a spare Fujitsu Seimens machine I have, but I  need to get this machine diagnosed and repaired asap.
What should I be looking at? And what software tools can I use?
I'm putting a lot of points on this because the situation is critical and I cannot find anything that describes these symptoms on the HP websites.
edformAsked:
Who is Participating?
 
edformConnect With a Mentor Author Commented:
The cause of this problem was a power supply on the point of failure! I eventually looked at that aspect of the machine because several commentators on the web said - When and ML350 G4 goes wrong it's always the PSU.
0
 
edformAuthor Commented:
Yes the machine is fully up to date and has run perfecly for some years. Today was obviously a bad day for some part of its makeup. I'm going to try checking over the power supply backplane because that gets mentioned in connection with the External health LED blinking red, but apart from that I'm stumped. - I have no swappable bits to do an isolation excercise with either.
Ed Form
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
65tdCommented:
Is the Systems Management Home page installed?
Any events in the IML?
System event give any leads?
0
 
lnkevinCommented:
Insert Proliant Support Pack CD (comes with the server) and boot it up. Follow the wizard and run HP Insight hardware diagnostic. Check the report to see if there is any failed part. You can download it here if you don't have it (the second part)

For 2003 OS:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3716247&prodTypeId=18964&prodSeriesId=3716246&swLang=13&taskId=135&swEnvOID=1005#78221

All other OSs:
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3716247&lang=en&cc=us&taskId=135&prodTypeId=18964&prodSeriesId=3716246

K
0
 
Paul SolovyovskySenior IT AdvisorCommented:
If you have the ILO username/password this may be the easiest way to check the hardware/logs since the machine doesn't need to be powered on  but needs to be plugged in.  Once you're logged in you should be able to browse hardware and check what failed.  The G4s have ILO2 so you should be set, if you don't know the password you may need to open up the case and find Switch1 and put ILO into the off position and reboot. Once you do this the username/password should be reset to blank and it should pick up an IP address via DHCP.
0
 
NetPro70Commented:
Disconnect power cable from power supply for at least 1 minute. This first of all resets LED fault status. Check if red LED comes up again after reboot.

Check IML (integrated management log) via HP SMH (System Management Homepage) for the cause of the error.

Make sure latest firmware (HP Firmware Maintenance CD) and PSP (ProLiant Support Pack) for your OS is installed. Latest version is 8.20. Install VCRM (Version Controll Repository Manager, download from hp.com) on one of your ProLiant servers and let the VCA (version control agent, comes with PSP) of all your servers point to your VCRM. Doing so you will be informed about latest software versions automatically in the future. Note that SNMP service with configured community strings is required for SMH and agents.
0
All Courses

From novice to tech pro — start learning today.