[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Blinking Red LEDs on ML350 G4 Server

Posted on 2009-04-02
7
Medium Priority
?
2,153 Views
Last Modified: 2012-05-06
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.
0
Comment
Question by:edform
7 Comments
 

Author Comment

by:edform
ID: 24054154
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
 
LVL 22

Expert Comment

by:65td
ID: 24055742
Is the Systems Management Home page installed?
Any events in the IML?
System event give any leads?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
LVL 26

Expert Comment

by:lnkevin
ID: 24062703
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
 
LVL 42

Expert Comment

by:Paul Solovyovsky
ID: 24070357
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
 
LVL 1

Expert Comment

by:NetPro70
ID: 24174497
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
 

Accepted Solution

by:
edform earned 0 total points
ID: 24220019
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

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn about cloud computing and its benefits for small business owners.
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question