At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
Teaming nic's on Proliant DL 585 G2 and Proliant DL380 G2 using Win2003x32 and x64connects then drops after re-boot. Teaming and nic's show connected but I cant ping the DG or hit the internet on other servers on same subnet. Tried using the onboard nics as well as some intel 7170 PCI nic's, same issue. I have updated to the lated nic drivers and teaming software. We have not had this issue on any of the older 585's or 380's.
I have a HP DL380 G4, I have a similar problem, when I team the onboard dual nics using 802.3ad (switched assisted load balancing). The NIC teaming works just fine, but as soon as I reboot the server the team nic looses it configuration and no longer can communicate with other computes. The icon on the lower right hand corner of my desktop indicates that it is acquiring an IP address, If I open the properties of the teamed interface, it shows the static IP address information, but if I use IPCONFIG from the command prompt it shows that there is not IP address. I can fix the problem by disabling and enabling back the teaming interface.
I called HP and they had me try all kinds of settings as well as different version of the NIC driver and NCU. At the end they said that it was a known issue with windows OS (I am running 2003) where the TCPI stack loads before the interface is ready, causing it to loose the IP address. The patch that they recommend applying did not work as it said that the version of the installed patch was newer that the patch I was trying to install.
Reloading the OS is not much of an option for me as this is a production (exchange) server. So far nothing has worked. I have a HP DL380 G4, I have a similar problem, when I team the onboard dual nics using 802.3ad (switched assisted load balancing). The NIC teaming works just fine, but as soon as I reboot the server the team nic looses it configuration and no longer can communicate with other computes. The icon on the lower right hand corner of my desktop indicates that it is acquiring an IP address, If I open the properties of the teamed interface, it shows the static IP address information, but if I use IPCONFIG from the command prompt it shows that there is not IP address. I can fix the problem by disabling and enabling back the teaming interface.
I called HP and they had me try all kinds of settings as well as different version of the NIC driver and NCU. At the end they said that it was a known issue with windows OS (I am running 2003) where the TCPI stack loads before the interface is ready, causing it to loose the IP address. The patch that they recommend applying did not work as it said that the version of the installed patch was newer that the patch I was trying to install.
Reloading the OS is not much of an option for me as this is a production (exchange) server. So far nothing has worked.
You can't post conmments that contain an email address.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Please first make sure that you are using the proper startup boot disk for the server before entering the CD ROM option from the boot menu. Also, check the front panel of the SCSI drives for any errors or blinking LEDS that correspond to an error code. You can run a diagnostics CD/DVD that arrived with the manufacturer's pack to detect any raid issues on startup.
If you are still facing difficulties with booting up the server, you can find a video for replacement of the appropriate scsi drive here if you are still facing any issues of your scsi drive. Try a different hard disk or check the relevant diagnostics to verify whether is the controller or the drive that complicates the booting of the server
I have the same problem and have seen two possible options for resolution...try updating the NIC's firmware and it could be a motherboard problem that needs to be replaced by hp. If either of the options provides the solution, let me know. I'm in the midst of it. (I've tried updating the drivers, swapping network cables, even feeding the NIC a known connection that gives 1Gbps.) http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=407733&prodTypeId=329290&prodSeriesId=407731&swLang=8&taskId=135&swEnvOID=1005#2995
Make sure you have turned on the USB Boot in the BIOS of the os. Once this is done, select the order you would like for the server to locate boot files. (Hard Drive, USB, CD/DVD, etc.) Once complete, insert the USB and reboot the server.
We had the same problem with a G5 version of the dl380, no video at boot or OS boot. This model fortunately had another video out on the front panel that worked. However, I believe that the G4 does not have that option coupled with using the Rage XL's from ATI for video. Have you tried installing another video card into the expansion slots for video? If you are able to, you may find that when you run your smartstart and load/reload the OS your video will work with the onboard.
The amber clearly states there are some problems with the hardware. Either with the power module, CPU or memory. Try contacting the vendor and get it repalced.
First of all, Dl380 is an hP product. Secondly your ghost version seems a bit old as ghost 14 is the latest version. Having said that the problem could be at two ends. 1. At the ghost side where your version doesnot contain NIC drivers for PXE boot and HDD drivers for imaging. To fix this you can try manually adding the drivers to the network boot or floppy boot diskette. You can get the drivers from HP website or the PSP CD that came with the server.
Alternatively you can upgrade to RDP instead of GHOST, RDP is Symantec's offering sold by HP for imaging it's servers.
2. There's some problem with your NIC settings or card if you are trying to PXE boot. If you are using a floppy drive/ usb HDD, check from BIOS if it is detected.
Teaming nic's on Proliant DL 585 G2 and Proliant DL380 G2 using Win2003x32
I have a HP DL380 G4, I have a similar problem, when I team the onboard dual nics using 802.3ad (switched assisted load balancing). The NIC teaming works just fine, but as soon as I reboot the server the team nic looses it configuration and no longer can communicate with other computes. The icon on the lower right hand corner of my desktop indicates that it is acquiring an IP address, If I open the properties of the teamed interface, it shows the static IP address information, but if I use IPCONFIG from the command prompt it shows that there is not IP address. I can fix the problem by disabling and enabling back the teaming interface.
I called HP and they had me try all kinds of settings as well as different version of the NIC driver and NCU. At the end they said that it was a known issue with windows OS (I am running 2003) where the TCPI stack loads before the interface is ready, causing it to loose the IP address. The patch that they recommend applying did not work as it said that the version of the installed patch was newer that the patch I was trying to install.
Reloading the OS is not much of an option for me as this is a production (exchange) server. So far nothing has worked.
×