Hp Ilo Firmware Dl380 G4
Abele Beardsley
I have an old HP DL 380 G5 server I got from work on which I have installed ESXi 6.0. I have a few different guest OSs running on it and am using it for testing several applications. I have increased the RAM on the server to 32 GB and it has been working reasonably well.
I am now thinking about upgrading the firmware(Raid controller, ILO, BIOs etc) on the server now and it seems the latest HP service pack doesn't support this specific model. I am not sure but I can't seem to get it to work.
Update: I know the hardware is not supported any more, I just wanted to know if any updates are available from the past which I can still install to fix known issues. The firmware on this server was never updated, even when it was in production, so I want to give it a shot and see what happens. That's the whole point of having an old server to play around with!
It would make sense to not make firmware changes unless it is absolutely required, for example you are hitting a boot time bug or incorrect fan operation or cpu is being throttled. Or in extreme cases if there is a known vulnerability against the firmware version. Botched firmware update can render the machine unusable and you will unnecessarily lose its functional benefit.
Booting the server, the ILO and so on all works fine. The server has a ILO advanced license and I can install stuff remotely. I first installed ESXi 6.0 using the HP Custom ISO, and it worked perfectly. I then tried installing Ubuntu Server 16.04 (instead of ESXi) and got stuck on the network interfaces. The Linux installation finds them, but cannot use them, DHCP fails, I cannot see any MAC address on the switch port it's connected to, but the interface is up. And it worked with ESXi. I tried Debian 8 and Ubuntu Server 12, same error (Debian says it need firmware for the Broadcom NICs though).
1. Is HP SUM something ment for large installations? AS I understand it the SUM ISO is just a tool and does not contain any firmware by itself? I tried to boot the ISO, but got the error message "No baseline found". Didn't investigate further.
2. Does firmware updates require an existing windows installation? When I look at what's available to download, pretty much everything is under the Windows section, and nothing under Linux or "OS independent".
We have two xxv710-2 cards in slots 4 and 6, HP reports that the fimware on the cards is 1.1747.0. We have two servers in different locations, one being the "main" server and the other as a failover in case the other fails).
The servers have RedHat Virtualisation (latest version) and runs a highly tuned Fortinet firewall as a VM (using 4 VF's, two from each card). The fortigates are not setup as HA, but are managed and the routing is changed when the manager observes that a server goes down. We are using one as the "main" server and since being setup in this manner, this one stays up, with the "fallback" server falling over at no particular predictable time. The servers have been swapped over at a point, and the one being the "main" server does not exhibit the failure (i.e. it is always the "fallback" that has the issue.
The symptoms we have is that the VM's are turned off and the server resets itself and reboots. We can see the same errors as in the linked post. As far as the OS goes we see no errors as the server has reset (i.e. powered off).
Any suggestions, is the firmware the latest as the numbers I have don't seem to relate to any numbers on the Intel Support site. Everything was built 2 months back with the latest and greatest versions.
1.) 2 System Support Utility logs of your system. One from the main server and one from the other server as a failover in case the main fails. This will allow us to check your Adapter details and configuration. Kindly refer to the steps below.
2.) Kindly provide the PBA and serial number of the adapters. You may refer to the link below on where to find the PBA number. You may also provide photos of the adapters focusing on the markings (white sticker) found on the physical card for us to double check on it. The PBA is consist of 6-digit number located at the last part of the serial number.
The server is RHEL 7.7 and therefore your ssu comes out with unsupported. The servers are in a remote datacentre so I cannot provide you with the serial numbers. The driver software was downloaded from Intel - iavf-3.7.53-1.x86_64.rpm is the package.
However altering your ssu script to accept the RH version I can get output, however the OS is not full blown RHEL - it is an appliance version - so normal Redhat packages will not install (such as ifconfig), so the output just details server info. What do you want me to do with the output?
I've just realised that the info above is not complete, the physical interfaces use the i40e driver (which has a driver version 2.8.10-k), the virtual functions use iavf (i40evf is removed and aliased to iavf). We are only using virtual functions of the card.
The firmware will be at the version it was delivered with although the HP SSU utility may have updated it - unfortunately I cannot get to the version number from the servers iLO so I would have to down the server to possibly get to the version number. I've not been able to find a link to the firmware - only to the driver. As it is an Intel card, can you share where the firmware can be downloaded from and how to update it?
Will you be able to identify if you are using a retail version of Intel Ethernet adapter or if it is an OEM version based on your place of purchase? The firmware that can be downloaded on our website is intended for retail version of Intel Ethernet adapter only. If you are using an OEM version, the firmware can be obtained thru your manufacturer.
We'd like to inform you that there are also OEM Ethernet adapters that can be purchased separately and the only way for us to identify if it is a retail one is thru the markings that can be seen on the white sticker of the physical adapter.
Using the nvmupdate64e linux utility on the system that isn't giving us problems (due to the VM we are running blocking access to the main PF on the machine that is), I can see that the NVM Version is 6.01 so we can update the firmware and that give me something to research.
I have also checked the NVM Update.zip to check if there is any information about the release, but it seems that there isn't any. With this, please give us some time to check this with our engineers. Rest assured that we will get back to you within 1-3 business days.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
A quick hipshot to Google showed up a promising result. My friend Andreas Lesslhumer from running-system.com just had this issue recently, so he created a blog post to help us others when we should encounter this issue too. In his post it was all about System ROM and iLO firmware versions and compatibility. It looks that the recent iLO firmware 2.50 (which is included in the HPE Service Pack for ProLiant April 2017) has some issues.
We then unplugged the storage completely and did also a complete storage shutdown. We also removed the power cables and let it spin down for a moment. After we bootet up the storage again, we checked if the server boots with each controller. And it did! Shutting down the storage and making it powerless helped!
We did some final test after all the firmware upgrades and were finally able to properly boot the servers and to get the domain controller and vCenter back up and running. After that we successfully bootet all other VMs without any issues.
Note: HPE and HPE ProLiant are registered trademarks or trademarks of Hewlett Packard Enterprise Company. All other brand names mentioned herein are for identification purposes only and may be the trademarks of their respective holder(s).
Software and Firmware Compatibility for DL3x0 Gen10 HPE ProLiant Servers
Before you image an HPE ProLiant server, make sure that the server is running the recommended firmware and software. Software and firmware are available as a service pack that you can download from the Hewlett Packard Enterprise Company website. Also, make sure that the versions of Nutanix Foundation, hypervisor, and other required software match the versions listed here.
Software and Firmware Compatibility for XL170r Gen10 HPE ProLiant Servers
Before you image an HPE ProLiant server, make sure that the server is running the recommended firmware and software. Software and firmware are available as a service pack that you can download from the Hewlett Packard Enterprise Company website. Also, make sure that the versions of Nutanix Foundation, hypervisor, and other required software match the versions listed here.
Software and Firmware Compatibility for DL3x0 Gen9 HPE ProLiant Servers
Before you image an HPE ProLiant server, make sure that the server is running the recommended firmware and software. Software and firmware are available as a service pack that you can download from the Hewlett Packard Enterprise Company website. Also, make sure that the versions of Nutanix Foundation, hypervisor, and other required software match the versions listed here.
In order to perform firmware upgrades of the HP DL 380 Gen10 series server, we first need to upgrade the bios, ilo and firmware versions to the current version. In HPE products, these processes are usually done through SPP (Service Pack for Proliant). In this SPP, there are necessary update and application packages belonging to many servers from the same series. If the server has a contract through your membership, you can download it or request it by registering from the HPE support line.
7fc3f7cf58