HP Compaq ProLiant DL580 G4 (430811001) Server - Answered Questions & Fixed issues

Minimum Supported Red Hat Updates •Red Hat Enterprise Linux 5 Update 1 •Red Hat Enterprise Linux 4 Update 5 6-Core/4-Core Intel Xeon Processor 7400 Series •Red Hat Enterprise Linux 5.22 •Red Hat Enterprise Linux 4.7 Minimum Supported Novell Service Packs•SUSE LINUX Enterprise Server 10 SP1•SUSE LINUX Enterprise Server 9 SP31 6-Core/4-Core Intel Xeon Processor 7400 Series •SUSE LINUX Enterprise Server 10 SP23 •SUSE LINUX Enterprise Server 9 SP44

Check in server that server all fan is working or not. if some one fan not working then clean fan then check if same issue fan then replaced fan

update BIOS & Windows

Update server with Latest HP proliant ServicePack ,Reconfigure RAID & Fresh Install OS with sp 2 ( is mandatory )

Pending hard dive failure.

Start by checking your event logs.

Hello,

You may need to check your BIOS to make sure the multiple CPU function is enabled. Once it is, a reboot should correct this for you.

Good Luck
C2Solutions

The ProLiant DL380 G3 server requires that both primary and redundant fans exist in a specific configuration in order to perform optimally. Any deviation from the specified configuration will cause one of the above error messages to occur and the internal Health LED to illuminate. In a ProLiant DL380 G3 server without the redundant fan option, the server will shut down after the error message is displayed. In a server with the redundant fan option, the internal Health LED will illuminate and the appropriate error message regarding fan redundancy will be displayed. The purpose of this document is to detail the required configuration for both primary and redundant fans.
DETAILS Both primary and redundant fans in the ProLiant DL380 G3 server must be configured to meet specific requirements in order to avoid the error messages above and in some instances, subsequent shutdown of the server.
All primary fan locations (2, 4, 5, 6 and 7) must be populated with a fan before the redundant fan locations (1, 3, or 8) are populated. If a primary fan location is left unpopulated, the server will display one or more of the error messages shown above. In addition, the internal Health LED (the top LED on the front panel of the server) will display the status of the fans.
When the redundant fan option is used, all redundant fan locations must be populated. ProLiant servers do not support partial population of redundant fans. If any redundant fan location is populated without also populating all other redundant fan locations in the server, the fan system will not be fully redundant and one or more of the error messages above will be displayed.
Figure 1 below illustrates a ProLiant DL380 G3 server configured with all eight fans installed for fan redundancy. The server airflow is divided into three zones: processor, I/O and power supply. Shared fans 4 and 7 each provide airflow for two zones. If a shared fan fails, the failure is experienced in both zones.
Figure 1: ProLiant DL380 G3 server configured with all eight fans installed for fan redundancy
The internal Health LED (the top LED on the front panel of the server) indicates failed or missing components. The internal Health LED should be observed to determine the status of the fans as follows:
RED LED: A red LED indicates that the minimum fan requirements have not been met. Minimum fan requirements indicate that all primary fan slots must be populated with functioning fans.

• If the 1611 fan "x" is not present (where "x" is the fan location) error message is displayed at POST and the internal Health LED is red , then a primary fan is missing.
  
  
• If the 1611 fan "x" failure (where "x" is the fan location) error message is displayed at POST and the internal Health LED is red , then a primary fan has failed.

AMBER LED: An amber LED indicates that the minimum fan requirements have been met; however, requirements for redundant fan configuration have not been met. This means that all primary fan slots are populated with functioning fans, but at least one redundant fan has either failed or is missing.

• If the 1611 fan "x" is not present (where "x" is the fan location) error message is displayed at POST and the internal Health LED is amber , then a redundant fan is missing.
  
  
• If the 1611 fan "x" failure (where "x" is the fan location) error message is displayed at POST and the internal Health LED is amber , then a redundant fan has failed.
  

Note: In a redundant fan configuration, the error message fan system not fully redundant will also be displayed at POST if any redundant fan slot is left unpopulated or if a redundant fan has failed.

Go to the HP Web site www.hp.com

Are you using a 64 bit operating system?

A customer of mine had the same similar problem as you, although it was Win XP, it actually turned out to be a NTOS virus,

I don't think that you "enable" 64 bit processing, you buy a server with a 64 bit processor. Intel's Itanium is such one. You then install Windows Server 2003 x64 version.
That's pretty much it I think.

SP1 of what?

Is there any error message in the event logs?

Have you tried just disabling the NIC & re-enabling it?

Is there a second NIC onboard which you can switch to & see if it does it on that as well?

Try resetting TCP/IP with NETSH.

If all else fails, rather than spending hours on it (which presumably is expensive :), get an Intel server-grade Gb NIC (around £70 in the UK), install that & use it instead of the motherboard NICs which I'm guessing is what you're using now.

Try to update the drivers for the network controllers. Herem is the link

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3288122&prodTypeId=15351&prodSeriesId=1137825&swLang=8&taskId=135&swEnvOID=1005#11395

NO PC told at all and posted to Proliant server forum that is no PC and as such the OS is not allowed there w10 nor does it have sound chips, at all, its a server running in huge dark, no humans server farm..... so let me guess you posted to wrong forum and never told PC model sure. so windows sounds work in the test in control panel yes ! the, MP3 is complex, it can be from high data rate, source and will not play unless converted . one thing to try is use this free app called Audacity https://www.audacityteam.org/ then play it or convert it or buy a USB sound dac that can decode any sound file on earth or learn to test you PC first windows sounds work then in google type simple MP3 sound test https://file-examples.com/index.php/sample-audio-files/sample-mp3-download/ works good above so your MP3 is no good or wrong bit rate. if fails yours only , buy new DAC USB dongle now it plays them all if windows sounds are dead the sound driver is missing or on a server there is no sound chips oops. buy the DAC dongle. if only 1 MP3 fails out of 100's find a better one or buy a DAC.

Have you connected a CD drive to the machine via one of the SATA ports?

When you turn it on, does the fan come on? How about the hard drive? There is a serries of tests called POST. I amc4rying to find out what starts up and see where the problem is.

You need to be specific about the exact model of server that you're using. Features of the various generations of the HP iLO are accessed in different ways. BE SPECIFIC.

That drive has failed, is it set up with a RAID configuration? Do you have the Dell monitoring software installed? Is it set up with Hot Plug drives? If so replacing the drive with a new one will start the RAID rebuild. Otherwise one way to turn off the bleep is to reboot and go into the RAID controller configuration

It Indicating something Faulty, if you have something plugged in, remove, and reconnect, If unable to find, check device manager or event log for details, that should have some info.