The simplest answer is, in this case, the correct answer: You will no longer be able to get firmware updates for HP equipment which is not (a) under its original factory warranty, or (b) covered by an active support contract with HP.
This has a number of implications, chief among them:
As a sysadmin you will have to ensure that you have an HP support ...
Upgrading the HP SAS expander is possible using Linux and a SAS HBA.
Note: Flashing firmware to a SAS expander will likely not work when the expander is connected to a SAS RAID controller because that controller might hide all devices behind it from the OS. An example of a SAS HBA is Supermicro SAS2LP-MV8.
In case you haven't got Linux, you can use a Linux ...
HP had a pretty awful initial set of firmware releases for the ILO3 management interface. See the massive changelog documenting the evolution of the product. I was working for a firm that deployed a large number of ProLiant DL380 G7 servers and had to deal with the pain of managing the buggy feature set.
In your case, you're trying to move from a very old ...
You are a bit confused, I will try and keep this simple:
DOS is an operating system mainstreamed by Microsoft.
BIOS is an operating system (arguably) of very limited nature, that is typically stored as firmware on a motherboard. It is far less functional and complex, it just to "get things going" with relation to the hardware inside a computer, before ...
HP's Intelligent Provisioning was a hot mess. The version of the Intelligent Provisioning that shipped with most of the servers in the past year or two did not perform the automated firmware upgrade process properly, hence the errors you see.
Chicken and egg...
The Intelligent Provisioning firmware is not handled by the standard firmware upgrade process ...
As per an updated blog post from HP
The firmware access changes we are making on February 19, 2014 apply to HP ProLiant servers only. Specifically, within ProLiant, we are not putting entitlement requirements on iLO, I/O, or controller firmware; we are only entitling ProLiant system ROM and complex programming logic devices (CPLD) firmware.
If this ...
If you have the HP Management Agents installed, the hpacucli utility, part of the Array Configuration Software will provide all of the controller information you need. For Windows 2003, download this package for command-line tool or this, for the GUI.
The ctrl all show config detail directive will output something like:
=> ctrl all show config detail
You don't have an option to do this through your RAID controller. In practice, I don't update SSD firmware unless it's fully vendor-integrated (Like Fusion-io or HP-branded and Dell-branded Sandisk enterprise disks).
If you DO need to update the firmware, you will need to connect directly to a SATA port and use the manufacturer's utility.
For Ubuntu there is no available firmware installer. Select the one for RedHat. You will get an .scexe file, which you can unpack:
$ chmod 740 CP022551.scexe
$ ./CP022551.scexe --unpack=/tmp/iLO3
$ ls -l /tmp/iLO3
There you have it: a ilo3_180.bin which you can upload with your iLO 3 web interface.
Hit my head against the wall (a lot) on this. For me, solved it by:
Formatting the USB as freedos (using Rufus) - https://www.all4os.com/windows/create-a-bootable-ms-dos-or-freedos-usb-drive.html
Downloading the Shell_full.efi, renaming to shellx64.efi, and putting it on the root of the drive - https://svn.code.sf.net/p/edk2/code/trunk/edk2/EdkShellBinPkg/...
The firmware for that server is located on HP's website.
Here's where to get it.
Don't assume that a system this old has any recent firmware updates.
Here's your BIOS download.
Here's your ILO download.
Here's your RAID controller download.
There are two ways to do this:
It is possible to a programatically view information about the BMC in your machine. However, in my experience the tools don't provide useful information.
I tried ipmitool bmc info and it returns some information. From here, you'd need a way to map the ID numbers to something which humans can understand:
Manufacturer ID ...
Remove power from the server. Unplug the cables. Let the machine sit for a few minutes. Plug the cables back in and power on.
If this doesn't work, you'll want to reset NVRAM.
Take a look at the HP ProLiant DL360p Gen8 Server Maintenance and Service Guide
You have to clear the CPU errors... Try the sequence detailed here.
If you have ...
The Dell PowerEdge R710 is a standard mainline manufacturer server platform. You can install whatever you wish on it. It's supported by Linux, Windows, VMware, etc., as the drivers are standard.
You won't have any problems managing firmware, updates and drivers if you run Linux on this system. Be sure to install the Dell management agents for Linux on the ...
Necessary - no, advisable - yes.
It's because the updates are generally there to fix bugs, one bug that might be fixed might screw you over doing what you want to do - thus by upgrading you're reducing the risk of the work you're doing somewhat.
Online ROM Flash Component for Windows - HP Integrated Lights-Out 3
(changelog is here)
Download from HP and extract to your PC. You'll see a .bin file in the resulting directory. You can upload that to the ILO firmware page.
You can update all of the system firmware using the HP Service Pack for ProLiant (HP SPP) DVD download. You can update ILO firmware ...
You don't even need the ILO for this.
If you have access to the operating system, you don't actually need to do this through the ILO.
You can download the HP Service Pack for ProLiant DVD .ISO to the server and run it, following the instructions along the way.
You can download the individual firmware updates for that platform piecemeal from the ML370 G5 ...
It's always a good idea to take a look at the dd-wrt forums. The "Router Database" on the main page is borked and alway suggests very outdated versions. This is a known problem, don't use it.
What version to use depends on the hardware you got. The forums discuss new releases and people report problems. There are also threads like "Best version for hardware ...
You haven't provided good information about your hardware situation, so I'm going to make some assumptions...
In your comments, you mention an HP Smart Array P212 controller. Let's assume you're using an HP ProLiant server of some sort.
If using an HP server, you'd typically use HP-branded disks. If you're not using HP disks, there's very little reason to ...
Note, the 8.0.4.b version of the firmware has been removed by Oracle. Download patch 145668-05 to get the 8.0.4.d firmware.
The install docs do not detail any requirements like previous firmware version to install.
"NASware" is just WD marketing speak for drive firmware they claim to have optimized for use in NAS devices. There is no specific action you need to take beyond just using the drive normally. However, you may wish to create your zpool with ashift=12 to ensure that it is aligned on 4K sector boundaries.
It's a bug in the package. The bug was already reported. The files were just missing, a patch is available in the bug report.
It works like this:
echo deb http://deb.debian.org/debian buster-backports main contrib non-free > /etc/apt/sources.list.d/buster-backports.list
wget -P /lib/firmware/bnx2x/ https://git.kernel.org/pub/scm/...
No mainboard uses DOS as a firmware. What you mean is the BIOS. It's gradually replaced by EFI, which I would consider a mixed blessing.
Non X86-Mainboards use/used entirely different system like OpenFirmware.
Dell/Equallogic actually recommends increasing the iSCSI "LoginTimeout" value to 60 seconds for each Equallogic group IP accessed by each ESX host.
The steps below detail the recommended method, though you can also perform this globally on the iSCSI initiator as a whole (applies to all groups/iSCSI SANs being accessed).
Log in to the vSphere Client and ...
While struggling with the same problems on HP's website I too found it incredibly difficult to find a specific .bin version. I was going to create a library of bin files, but someone else beat me too it. This site is hosting .bin files for several ilo versions.
* other than using that page myself I'm not ...