These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
]]>The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
]]>Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO.
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO.
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 15 service pack 1 and SuSE Linux Enterprise Server 15 service pack 2 has to be performed using --reinstall option
Example: rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --reinstall
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 15 service pack 1 and SuSE Linux Enterprise Server 15 service pack 2 has to be performed using --reinstall option
Example: rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --reinstall
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
# rpm -Uvh kernel-mft-mlnx-kmp-default-4.16.0_k4.12.14_195-1.sles15sp1.x86_64.rpm mft-4.16.0-105.sles15sp1.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
# rpm -Uvh kernel-mft-mlnx-kmp-default-4.16.0_k4.12.14_195-1.sles15sp1.x86_64.rpm mft-4.16.0-105.sles15sp1.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter(P25960-B21) | 22.29.1016 | MT_0000000437 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter(P25960-B21) | 22.29.1016 | MT_0000000437 |
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe or chmod +x CPXXXXX.vmexe64 (for ESXi7.0)
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe or chmod +x CPXXXXX.vmexe64 (for ESXi7.0)
Release Version and/or Date:
5.02(A)
Last Recommended or Critical Version:
5.02
Previous Version of Firmware:
5.02
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.02(A)
Last Recommended or Critical Version:
5.02
Previous Version of Firmware:
5.02
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
# ./CP033363.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-46a4d957a7-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
# ./CP033363.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-46a4d957a7-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
8.32
Last Recommended or Critical Version:
8.00
Previous Version of Firmware:
8.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
System can potentially stop responding with no lockup code due to livelock condition where the RAID Stack thread is polling a queue for a completion to be returned by the base code firmware
Known Issues:
None
Release Version and/or Date:
8.32
Last Recommended or Critical Version:
8.00
Previous Version of Firmware:
8.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
System can potentially stop responding with no lockup code due to livelock condition where the RAID Stack thread is polling a queue for a completion to be returned by the base code firmware
Known Issues:
None
Updating firmware without installing rpm:
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
]]>Updating firmware without installing rpm:
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
]]>| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d8000-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d8000-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
# ./ CP034973.scexe in the '/usr/lib/i386-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/i386-linux-gnu/firmware-nvmepic-gen9-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
# ./ CP034973.scexe in the '/usr/lib/i386-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/i386-linux-gnu/firmware-nvmepic-gen9-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>Commands can also be executed from outside the SSA CLI console using the syntax: ssacli
Type "ssacli help" or type "help" at the CLI prompt for usage details.
]]>
Commands can also be executed from outside the SSA CLI console using the syntax: ssacli
Type "ssacli help" or type "help" at the CLI prompt for usage details.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
选择“安装”，开始提取至硬盘的临时位置。
点击“安装”按钮执行服务安装。
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the service installation.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability.
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue during unaligned write commands, only found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability.
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Online HDD/SSD Flash Component for Windows (x64) - EG0300FCSPH, EG0450FCSPK, EG0600FCSPL and EG0900FCSPN Drives
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Online HDD/SSD Flash Component for Windows (x64) - EG0300FCSPH, EG0450FCSPK, EG0600FCSPL and EG0900FCSPN Drives
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Additional Information:
Additional Information:
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware without installing the rpm:
Additional Information:
Updating firmware without installing the rpm:
Additional Information:
| NIC | EEPROM/NVM Version | OROM Version | NVM Version |
|---|---|---|---|
| HPE Ethernet 10Gb 2-port SFP+ OCP3 X710-DA2 Adapter | 80009837 | 1.2829.0 | 8.10 |
| HPE Ethernet 10Gb 2-port SFP+ X710-DA2 Adapter | 800093DD | 1.2829.0 | 8.10 |
| Intel I350-T4 Ethernet 1Gb 4-port BASE-T Adapter | 80001099 | 1.2839.0 | N/A |
| Intel I350-T4 Ethernet 1Gb 4-port BASE-T OCP3 Adapter | 80001097 | 1.2839.0 | N/A |
| Intel(R) I350 Gigabit Network Connection (2-port) | 8000108E | 1.2839.0 | N/A |
| Intel(R) I350 Gigabit Network Connection (4-port) | 8000108F | 1.2839.0 | N/A |
The combo image v1.2829.0 includes: Boot Agent: I40E - v1.1.18& UEFI Drivers: 40GbE - v4.4.12.
The combo image v1.2839.0 includes: Boot Agent: 1GbE - v1.5.88 & UEFI Drivers: 1GbE - v9.4.06.
]]>| NIC | EEPROM/NVM Version | OROM Version | NVM Version |
|---|---|---|---|
| HPE Ethernet 10Gb 2-port SFP+ OCP3 X710-DA2 Adapter | 80009837 | 1.2829.0 | 8.10 |
| HPE Ethernet 10Gb 2-port SFP+ X710-DA2 Adapter | 800093DD | 1.2829.0 | 8.10 |
| Intel I350-T4 Ethernet 1Gb 4-port BASE-T Adapter | 80001099 | 1.2839.0 | N/A |
| Intel I350-T4 Ethernet 1Gb 4-port BASE-T OCP3 Adapter | 80001097 | 1.2839.0 | N/A |
| Intel(R) I350 Gigabit Network Connection (2-port) | 8000108E | 1.2839.0 | N/A |
| Intel(R) I350 Gigabit Network Connection (4-port) | 8000108F | 1.2839.0 | N/A |
The combo image v1.2829.0 includes: Boot Agent: I40E - v1.1.18& UEFI Drivers: 40GbE - v4.4.12.
The combo image v1.2839.0 includes: Boot Agent: 1GbE - v1.5.88 & UEFI Drivers: 1GbE - v9.4.06.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired components to be updated in the directory, \packages on the USB key. To use with HPE SUM 7.6.0 or earlier, place the components in \hp\swpackages on the USB Key.
Update the firmware and software in the usual manner.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired components to be updated in the directory, \packages on the USB key. To use with HPE SUM 7.6.0 or earlier, place the components in \hp\swpackages on the USB Key.
Update the firmware and software in the usual manner.
To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
Red Hat Enterprise Linux 6 Server (x86-64) FCoE/FC Driver Kit for HPE Qlogic CNAs, HBAs and mezzanine HBAs, version 8.07.00.42.06.0-k1
Red Hat Enterprise Linux 7 Server FCoE/FC Driver Kit for HPE QLogic CNAs, HBAs and mezzanine HBAs and CNAs, version 8.07.00.42.07.0-k1
SUSE Linux Enterprise Server 11 (AMD64/EM64T) FCoE/FC Driver Kit for HPE Qlogic CNAs, HBAs and mezzanine HBAs, version 8.07.00.42.11.3-k
SUSE Linux Enterprise Server 12 FCoE/FC Driver Kit for HPE QLogic CNAs, HBAs and mezzanine HBAs and CNAs version 8.07.00.42.12.0-k1
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
Red Hat Enterprise Linux 6 Server (x86-64) FCoE/FC Driver Kit for HPE Qlogic CNAs, HBAs and mezzanine HBAs, version 8.07.00.42.06.0-k1
Red Hat Enterprise Linux 7 Server FCoE/FC Driver Kit for HPE QLogic CNAs, HBAs and mezzanine HBAs and CNAs, version 8.07.00.42.07.0-k1
SUSE Linux Enterprise Server 11 (AMD64/EM64T) FCoE/FC Driver Kit for HPE Qlogic CNAs, HBAs and mezzanine HBAs, version 8.07.00.42.11.3-k
SUSE Linux Enterprise Server 12 FCoE/FC Driver Kit for HPE QLogic CNAs, HBAs and mezzanine HBAs and CNAs version 8.07.00.42.12.0-k1
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>
# rpm -e hpe-qlogic-smartsan-enablement-<version>.noarch.rpm
This is a configurable component. It requires a configuration file in order to enable/disable Smart SAN functionality. If no configuration is performed, the current Smart SAN status is stated and the execution is complete. No further action is taken.
For detailed information about configurable components, see the Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
1. Login as the system administrator (root).
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install, type the following command at the prompt:
# rpm -ivh hpe-qlogic-smartsan-enablement-kit-<version>.x86_64.rpm
Example: # rpm -ivh hpe-qlogic-smartsan-enablement-kit-3.3-3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Installation complete
# rpm -e hpe-qlogic-smartsan-enablement-<version>.noarch.rpm
This is a configurable component. It requires a configuration file in order to enable/disable Smart SAN functionality. If no configuration is performed, the current Smart SAN status is stated and the execution is complete. No further action is taken.
For detailed information about configurable components, see the Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
1. Login as the system administrator (root).
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install, type the following command at the prompt:
# rpm -ivh hpe-qlogic-smartsan-enablement-kit-<version>.x86_64.rpm
Example: # rpm -ivh hpe-qlogic-smartsan-enablement-kit-3.3-3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Installation complete
To update the driver using VMware tools:
To update the driver using VMware tools:
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]> # rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
# rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = SUSE Linux Enterprise Server 15
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = SUSE Linux Enterprise Server 15
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
To get the list of all dependency files for hp-smh-templates type:
rpm –qp –-requires hp-smh-templates-<version>.rpm
]]>To get the list of all dependency files for hp-smh-templates type:
rpm –qp –-requires hp-smh-templates-<version>.rpm
]]>To install the package type:
rpm -ivh hp-smh-templates-<version>.rpm
To check whether the package is installed type:
rpm –q hp-smh-templates
Additional help is available by typing:
man hp-smh-templates
]]>To install the package type:
rpm -ivh hp-smh-templates-<version>.rpm
To check whether the package is installed type:
rpm –q hp-smh-templates
Additional help is available by typing:
man hp-smh-templates
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
Check dependency failed.（检查依赖关系失败。）
Current version:（当前版本：） iLOx x.xx
Minimum version required:（所需的最低版本：） iLO4 2.20
本系统中不能安装该软件，因为系统中不存在所需的硬件，或者该软件或固件不适用于本系统
]]>Check dependency failed.
Current version: iLOx x.xx
Minimum version required: iLO4 2.20
The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn't apply to this system
]]>To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
]]>
Release Version and/or Date:
1.78 (B)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.78
Firmware Dependency:
None
Enhancements/New Features:
Added VMware vSphere 6.7 OS support
Problems Fixed in version 1.78:
None
Known Issues:
None
]]>
Release Version and/or Date:
1.78 (B)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.78
Firmware Dependency:
None
Enhancements/New Features:
Added VMware vSphere 6.7 OS support
Problems Fixed in version 1.78:
None
Known Issues:
None
]]>
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>
http://www.hpe.com/storage/spock/
The OOB NIC driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
Additional requirements:
The target environment must have the libsysfs or sysfsutils package installed prior to the installation of the firmware update kit. If not already present, the libsysfs or sysfsutils package can be obtained from the operating system installation media.
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex HBAs/CNAs
Environment must be running the syslog daemon for the flash engine to run
Note: To enable the FCoE/iSCSI protocol on devices that support it, please install the appropriate Emulex FCoE/iSCSI driver. The FCoE protocol also requires the HPE Emulex FCoE Enablement Kit be installed. The drivers and enablement kit are also available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FCoE Driver Kit, reboot, and then install the Enablement Kit.
]]>http://www.hpe.com/storage/spock/
The OOB NIC driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
Additional requirements:
The target environment must have the libsysfs or sysfsutils package installed prior to the installation of the firmware update kit. If not already present, the libsysfs or sysfsutils package can be obtained from the operating system installation media.
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex HBAs/CNAs
Environment must be running the syslog daemon for the flash engine to run
Note: To enable the FCoE/iSCSI protocol on devices that support it, please install the appropriate Emulex FCoE/iSCSI driver. The FCoE protocol also requires the HPE Emulex FCoE Enablement Kit be installed. The drivers and enablement kit are also available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FCoE Driver Kit, reboot, and then install the Enablement Kit.
]]> 2. cd to the appropriate location for your system, and update the firmware by executing ./.setup
When the firmware installation completes, you may remove the firmware installation tool from your system using the rpm -e command: rpm -e <rpm_package_name>.
2. cd to the appropriate location for your system, and update the firmware by executing ./.setup
When the firmware installation completes, you may remove the firmware installation tool from your system using the rpm -e command: rpm -e <rpm_package_name>.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Updating firmware with rpm installed:
# ./ CP042957.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-40023de47f-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>Updating firmware with rpm installed:
# ./ CP042957.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-40023de47f-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>Updating firmware with rpm installed:
# ./ CP043314.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-b368ad032e-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
Updating firmware with rpm installed:
# ./ CP043314.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-b368ad032e-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant :
Additional Information:
To use Smart Update Manager from the Service Pack for ProLiant :
Additional Information:
Release Version and/or Date:
1.00(B)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.00(B)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Release Version and/or Date:
1.78 (A)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.50(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.78 (A)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.50(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
In addition, the System Management Homepage (SMH) component (version 7.2.2.9 or later) is required for a single server web-based user interface.
Make sure to apply all updates needed for the OS on the system by running Windows Update. Incomplete Windows Update may cause the HPE WBEM Providers installation failures.
]]>
In addition, the System Management Homepage (SMH) component (version 7.2.2.9 or later) is required for a single server web-based user interface.
Make sure to apply all updates needed for the OS on the system by running Windows Update. Incomplete Windows Update may cause the HPE WBEM Providers installation failures.
]]>
]]>
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
HPK3
Previous Version of Firmware:
HPK3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
HPK3
Previous Version of Firmware:
HPK3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Last Recommended or Critical Version:
3.21
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Last Recommended or Critical Version:
3.21
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]>Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]>iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
http://www.hpe.com/storage/spock/
The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>http://www.hpe.com/storage/spock/
The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: When disk enclosures are cascaded, I/O module A of one enclosure is connected to I/O module A of the subsequent enclosure. During a firmware update, I/O module A in the cascaded disk enclosures is automatically updated.
In dual-domain configurations, both I/O modules of the target disk enclosure and cascaded disk enclosures are automatically updated during the firmware installation process.
All firmware flash progress messages are logged to /var/cpq/Component.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: When disk enclosures are cascaded, I/O module A of one enclosure is connected to I/O module A of the subsequent enclosure. During a firmware update, I/O module A in the cascaded disk enclosures is automatically updated.
In dual-domain configurations, both I/O modules of the target disk enclosure and cascaded disk enclosures are automatically updated during the firmware installation process.
All firmware flash progress messages are logged to /var/cpq/Component.log.
]]>Updating firmware with rpm installed:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/hp-firmware-d2600-d2700-<version>-*' location
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
Online:
Special installation instructions for single-domain environments:
In a single domain configuration, I/O module A (top module) is connected to a SmartArray controller and I/O module B (bottom module) is unused. Even though the bottom I/O module is unused, both modules must have the same firmware version installed. Do the following to make sure that BOTH I/O modules are updated:
NOTES:
Installation Notes and Best Practices:
Updating firmware with rpm installed:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/hp-firmware-d2600-d2700-<version>-*' location
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
Online:
Special installation instructions for single-domain environments:
In a single domain configuration, I/O module A (top module) is connected to a SmartArray controller and I/O module B (bottom module) is unused. Even though the bottom I/O module is unused, both modules must have the same firmware version installed. Do the following to make sure that BOTH I/O modules are updated:
NOTES:
Installation Notes and Best Practices:
]]>
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port MCX653106A-ECAT QSFP56 x16 Adapter(P23666-B21) | 20.29.1016 | MT_0000000453 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port MCX653106A-ECAT QSFP56 x16 Adapter(P23666-B21) | 20.29.1016 | MT_0000000453 |
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4.When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4.When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Click the Install button to proceed with the installation.
]]>Click the Install button to proceed with the installation.
]]>| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter (P25960-B21) | 22.29.1016 | MT_0000000437 |
| Mellanox MCX623105AS-VDAT Ethernet 200Gb 1-port QSFP56 Adapter for HPE (P10180-B21) | 22.29.1016 | MT_0000000435 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter (P25960-B21) | 22.29.1016 | MT_0000000437 |
| Mellanox MCX623105AS-VDAT Ethernet 200Gb 1-port QSFP56 Adapter for HPE (P10180-B21) | 22.29.1016 | MT_0000000435 |
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>For detailed information about configurable components, see the Smart Update Manager User Guide at https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00106063en_us.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>For detailed information about configurable components, see the Smart Update Manager User Guide at https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00106063en_us.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
Enhancements/New Features:
Problems Fixed:
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>在该硬盘目录中，执行下载的文件。
点击“安装”按钮进行安装。
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPGA
Previous Version of Firmware:
HPGA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPGA
Previous Version of Firmware:
HPGA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added Support for Windows Server 2019
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later, SUM will not detect SSD as applicable for Firmware update for deployment with iLO version older than v2.30
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added Support for Windows Server 2019
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later, SUM will not detect SSD as applicable for Firmware update for deployment with iLO version older than v2.30
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA2 Ethernet 10/25Gb 2-port SFP28 OCP3 Adapter | 800059DE | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA2 Ethernet 10/25Gb 2-port SFP28 OCP3 Adapter | 800059DE | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None.
]]>Please refer the following advisory for more details about the python dependency on SLES15SP1.
https://si.houston.hpecorp.net/si/DocumentationRequests/details.aspx?DRId=SID5293&slim=yes&offset=0
Please refer the following advisory for more details about the python dependency on SLES15SP1.
https://si.houston.hpecorp.net/si/DocumentationRequests/details.aspx?DRId=SID5293&slim=yes&offset=0
To install or upgrade the driver:
If using 4.12.14-195-default kernel or any future errata:
# rpm -Uvh mlnx-ofa_kernel-5.2-OFED.5.2.1.0.4.1.sles15sp1.x86_64.rpm mlnx-ofa_kernel-kmp-default-5.2_k4.12.14_195-OFED.5.2.1.0.4.1.sles15sp1.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
To install or upgrade the driver:
If using 4.12.14-195-default kernel or any future errata:
# rpm -Uvh mlnx-ofa_kernel-5.2-OFED.5.2.1.0.4.1.sles15sp1.x86_64.rpm mlnx-ofa_kernel-kmp-default-5.2_k4.12.14_195-OFED.5.2.1.0.4.1.sles15sp1.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Problems Fixed:
Known Issues:
None
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FC Driver Kit, reboot, and then install the Enablement Kit.
Additional requirements:
Environment must be running the syslog daemon for the flash engine to run
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex Host Bus Adapters(HBAs)
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FC Driver Kit, reboot, and then install the Enablement Kit.
Additional requirements:
Environment must be running the syslog daemon for the flash engine to run
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex Host Bus Adapters(HBAs)
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
Additional Information:
Additional Information:
| NIC | Boot Code Version | PXE Version | NCSI Version | UEFI Version | CCM Version |
| HPE Ethernet 1Gb 2-port 330i Adapter (22BD) | 2.10 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
| HPE Ethernet 1Gb 4-port 331i Adapter (22BE) HPE Ethernet 1Gb 4-port 331FLR Adapter HPE Ethernet 1Gb 4-port 331T Adapter |
1.46 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
| HPE Ethernet 1Gb 2-port 332i Adapter (22E8) HPE Ethernet 1Gb 2-port 332T Adapter |
1.40 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
| NIC | Boot Code Version | PXE Version | NCSI Version | UEFI Version | CCM Version |
| HPE Ethernet 1Gb 2-port 330i Adapter (22BD) | 2.10 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
| HPE Ethernet 1Gb 4-port 331i Adapter (22BE) HPE Ethernet 1Gb 4-port 331FLR Adapter HPE Ethernet 1Gb 4-port 331T Adapter |
1.46 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
| HPE Ethernet 1Gb 2-port 332i Adapter (22E8) HPE Ethernet 1Gb 2-port 332T Adapter |
1.40 | 21.6.0 | 1.5.27 | 21.6.12 | 218.0.10.0 |
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>
http://www.hpe.com/storage/spock/
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
]]>http://www.hpe.com/storage/spock/
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 12 service pack 4 and SuSE Linux Enterprise Server 12 service pack 5 has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --force --nodeps
rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --replacepkgs --nodeps
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 15 service pack 1 and SuSE Linux Enterprise Server 15 service pack 2 has to be performed using --reinstall option
Example: rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --force --nodeps
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 12 service pack 4 and SuSE Linux Enterprise Server 12 service pack 5 has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --force --nodeps
rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --replacepkgs --nodeps
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 15 service pack 1 and SuSE Linux Enterprise Server 15 service pack 2 has to be performed using --reinstall option
Example: rpm –Uvh HPE-CNA-FC-hpeqlgc-Enablement-Kit-<version>.noarch.rpm --force --nodeps
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use HP Smart Update Manager from the Service Pack for ProLiant :
To use HP Smart Update Manager from the Service Pack for ProLiant :
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media..
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media..
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>在该硬盘目录中，执行下载的文件。
点击“安装”按钮进行安装。
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Additional Information:
Additional Information:
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
HPK2
Previous Version of Firmware:
HPK2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
HPK2
Previous Version of Firmware:
HPK2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]> # rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
# rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied Emulex driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Emulex driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
None
Known Issues:
None.
]]>Problems Fixed:
None
Known Issues:
None.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows Server 2019
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows Server 2019
Problems Fixed:
None
Known Issues:
None
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Release Version and/or Date:
15.10.10.00 (C)
Last Recommended or Critical Version:
15.10.10.00 (D)
Previous Version of Firmware:
15.10.10.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
15.10.10.00 (C)
Last Recommended or Critical Version:
15.10.10.00 (D)
Previous Version of Firmware:
15.10.10.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO.
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO.
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Online HDD/SSD Flash Component for VMware ESXi - MB006000GWKGR Drive
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Online HDD/SSD Flash Component for VMware ESXi - MB006000GWKGR Drive
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
Reboot your system for the update to take effect immediately.
Reboot your system for the update to take effect immediately.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
~# esxcli software vib install -v <path><filename.vib>
]]>~# esxcli software vib install -v <path><filename.vib>
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
NOTE: During the flash operation, the message "No Adapter Found!" may appear in the logs. These messages do not indicate a problem with the firmware flash operation and may be ignored.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
NOTE: During the flash operation, the message "No Adapter Found!" may appear in the logs. These messages do not indicate a problem with the firmware flash operation and may be ignored.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPS1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPS1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Firmware Dependency:
None
Enhancements/New Features:
Added support to the RDE-Alerts feature
Problems Fixed:
None
Known Issues:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support to the RDE-Alerts feature
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 12 service pack 4 and SuSE Linux Enterprise Server 12 service pack 5 has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --force --nodeps
rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --replacepkgs --nodeps
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Rewrite of same Enablement kit version on SuSE Linux Enterprise Server 12 service pack 4 and SuSE Linux Enterprise Server 12 service pack 5 has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --force --nodeps
rpm –Uvh HPE-CNA-FC-Emulex-Enablement-Kit-<version>.<OS>.<architecture>.rpm --replacepkgs --nodeps
For more information please refer the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problem Fixed:
Known Issues:
None
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problem Fixed:
Known Issues:
None
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
点击安装按钮继续执行安装。
]]>
Click the Install button to proceed with the installation.
]]>
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
]]>
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
1.78 (A)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.50(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.78 (A)
Last Recommended or Critical Version:
1.78
Previous Version of Firmware:
1.50(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
Additional Information:
Additional Information:
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP Ethernet 10Gb 2-port 530SFP+ Adapter HP Ethernet 10Gb 2-port 530T Adapter |
7.16.03 | 7.14.13 | 8.8.2 | n/a | n/a | 7.14.4 | 7.12.25 |
|
HP Ethernet 10Gb 2-port 533FLR-T Adapter |
7.16.03 | 7.14.13 | 8.8.2 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP Ethernet 10Gb 2-port 530SFP+ Adapter HP Ethernet 10Gb 2-port 530T Adapter |
7.16.03 | 7.14.13 | 8.8.2 | n/a | n/a | 7.14.4 | 7.12.25 |
|
HP Ethernet 10Gb 2-port 533FLR-T Adapter |
7.16.03 | 7.14.13 | 8.8.2 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD6
Previous Version of Firmware:
HPD6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD6
Previous Version of Firmware:
HPD6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-CQDA2 Ethernet 100Gb 2-port QSFP28 OCP3 Adapter | 800059D4 | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-CQDA2 Ethernet 100Gb 2-port QSFP28 OCP3 Adapter | 800059D4 | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
Additional Information:
Additional Information:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 2-port QSFP56 PCIe4 x16 OCP3 MCX653436A-HDAI Adapter (P31348-B21) | 20.29.1016 | MT_0000000593 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 2-port QSFP56 PCIe4 x16 OCP3 MCX653436A-HDAI Adapter (P31348-B21) | 20.29.1016 | MT_0000000593 |
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
When the installation is complete, run command prompt environment and navigate to %programfiles%\MR Storage Administrator\StorCLI\bin folder and execute Storcli64.exe utility
For e.g: Storcli64.exe /c0 show
]]>Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
When the installation is complete, run command prompt environment and navigate to %programfiles%\MR Storage Administrator\StorCLI\bin folder and execute Storcli64.exe utility
For e.g: Storcli64.exe /c0 show
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: When disk enclosures are cascaded, I/O module A of one enclosure is connected to I/O module A of the subsequent enclosure. During a firmware update, I/O module A in the cascaded disk enclosures is automatically updated.
In dual-domain configurations, both I/O modules of the target disk enclosure and cascaded disk enclosures are automatically updated during the firmware installation process.
All firmware flash progress messages are logged to %systemdrive%\CPQSYSTEM\Log\D2000.log and flash summary is logged to %systemdrive%\CPQSYSTEM\Log\cpqsetup.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: When disk enclosures are cascaded, I/O module A of one enclosure is connected to I/O module A of the subsequent enclosure. During a firmware update, I/O module A in the cascaded disk enclosures is automatically updated.
In dual-domain configurations, both I/O modules of the target disk enclosure and cascaded disk enclosures are automatically updated during the firmware installation process.
All firmware flash progress messages are logged to %systemdrive%\CPQSYSTEM\Log\D2000.log and flash summary is logged to %systemdrive%\CPQSYSTEM\Log\cpqsetup.log.
]]>GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use HP Smart Update Manager from the HP Service Pack for ProLiant :
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Special installation instructions for single-domain environments:
In a single domain configuration, I/O module A (top module) is connected to a SmartArray controller and I/O module B (bottom module) is unused. Even though the bottom I/O module is unused, both modules must have the same firmware version installed. Do the following to make sure that BOTH I/O modules are updated:
Installation Notes and Best Practices:
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use HP Smart Update Manager from the HP Service Pack for ProLiant :
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Special installation instructions for single-domain environments:
In a single domain configuration, I/O module A (top module) is connected to a SmartArray controller and I/O module B (bottom module) is unused. Even though the bottom I/O module is unused, both modules must have the same firmware version installed. Do the following to make sure that BOTH I/O modules are updated:
Installation Notes and Best Practices:
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver:
If using 4.12.14-120-default kernel or any future errata:
# rpm -Uvh mlnx-ofa_kernel-5.2-OFED.5.2.1.0.4.1.sles12sp5.x86_64.rpm mlnx-ofa_kernel-kmp-default-5.2_k4.12.14_120-OFED.5.2.1.0.4.1.sles12sp5.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
To install or upgrade the driver:
If using 4.12.14-120-default kernel or any future errata:
# rpm -Uvh mlnx-ofa_kernel-5.2-OFED.5.2.1.0.4.1.sles12sp5.x86_64.rpm mlnx-ofa_kernel-kmp-default-5.2_k4.12.14_120-OFED.5.2.1.0.4.1.sles12sp5.x86_64.rpm
Setup is now complete. Reboot your computer for the driver to take effect.
Updating firmware with rpm installed:
# ./ CP037723.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-nvmebackplane-gen10-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
# ./ CP037723.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-nvmebackplane-gen10-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
When the installation is complete, run command prompt environment and navigate to %programfiles%\MR Storage Administrator\StorCLI\bin folder and execute Storcli64.exe utility
For e.g: Storcli64.exe /c0 show
]]>Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
When the installation is complete, run command prompt environment and navigate to %programfiles%\MR Storage Administrator\StorCLI\bin folder and execute Storcli64.exe utility
For e.g: Storcli64.exe /c0 show
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>For detailed information about configurable components, see the HP Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>For detailed information about configurable components, see the HP Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>
Update the firmware and software in the usual manner.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
In conjunction with the Smart Update Manager found on the SPP, the component can be used to deploy the firmware to the HPE BladeSystem c-Class Virtual Connect module.
Firmware extracted from the component can be deployed using the Virtual Connect Support Utility for the HPE BladeSystem c-Class Virtual Connect modules.
Installation Notes for using the component with Smart Update Manager and SPP
Installation Notes for using the firmware extracted from the component
Extract the firmware binary out of the component.
Place the firmware image file onto a system on the same network as the HPE BladeSystem c-Class Virtual Connect module.
Start the Virtual Connect Support Utility and deploy the firmware.
HPE requires using the HPE BladeSystem c-Class Virtual Connect Support Utility version 1.15.0 (or higher) to install the HPE VC FlexFabric-20/40 F8 version 4.85, HPE VC Flex-10/10D version 4.85, HPE VC FlexFabric 10Gb/24-port version 4.85, HPE VC 8Gb 24-Port FC version 4.20, HPE VC 16Gb 24-Port FC version 4.20, and HPE VC 8Gb 20-Port FC version 2.25 firmware. Please read the HPE BladeSystem c-Class Virtual Connect Support Utility release notes.
Please be advised of a serious issue that could cause network outage when upgrading directly from VC 2.xx release version to VC 4.85 release in Multi-Enclosure environment. Please upgrade from VC 2.xx to VC 3.70 or VC 4.10 first and then upgrade from VC 3.70 or VC 4.10 to VC 4.50 then upgrade from VC 4.50 to VC 4.85 in a Multi-Enclosure setup.
To update HPE VC 8Gb 24-Port FC module(s) from Virtual Connect firmware 4.31 or lower to Virtual Connect 4.85 or higher, these module(s) must first be updated with either Virtual Connect firmware version 4.4x or version 4.50 (Recommended version is 4.50) before they can be updated with Virtual Connect 4.85 or higher.
The USB Key Utility is used to copy the SPP onto a portable USB key storage device. Please note that the latest version (v2.0.0.0) of the utility is now 64-bit only. If the 32-bit application is needed, please use version 1.8, however, this version will not work on an ISO image greater than 4GB.
Note: Please read the Important note section of the Release Notes for firmware upgrade instructions.
]]>In conjunction with the Smart Update Manager found on the SPP, the component can be used to deploy the firmware to the HPE BladeSystem c-Class Virtual Connect module.
Firmware extracted from the component can be deployed using the Virtual Connect Support Utility for the HPE BladeSystem c-Class Virtual Connect modules.
Installation Notes for using the component with Smart Update Manager and SPP
Installation Notes for using the firmware extracted from the component
Extract the firmware binary out of the component.
Place the firmware image file onto a system on the same network as the HPE BladeSystem c-Class Virtual Connect module.
Start the Virtual Connect Support Utility and deploy the firmware.
HPE requires using the HPE BladeSystem c-Class Virtual Connect Support Utility version 1.15.0 (or higher) to install the HPE VC FlexFabric-20/40 F8 version 4.85, HPE VC Flex-10/10D version 4.85, HPE VC FlexFabric 10Gb/24-port version 4.85, HPE VC 8Gb 24-Port FC version 4.20, HPE VC 16Gb 24-Port FC version 4.20, and HPE VC 8Gb 20-Port FC version 2.25 firmware. Please read the HPE BladeSystem c-Class Virtual Connect Support Utility release notes.
Please be advised of a serious issue that could cause network outage when upgrading directly from VC 2.xx release version to VC 4.85 release in Multi-Enclosure environment. Please upgrade from VC 2.xx to VC 3.70 or VC 4.10 first and then upgrade from VC 3.70 or VC 4.10 to VC 4.50 then upgrade from VC 4.50 to VC 4.85 in a Multi-Enclosure setup.
To update HPE VC 8Gb 24-Port FC module(s) from Virtual Connect firmware 4.31 or lower to Virtual Connect 4.85 or higher, these module(s) must first be updated with either Virtual Connect firmware version 4.4x or version 4.50 (Recommended version is 4.50) before they can be updated with Virtual Connect 4.85 or higher.
The USB Key Utility is used to copy the SPP onto a portable USB key storage device. Please note that the latest version (v2.0.0.0) of the utility is now 64-bit only. If the 32-bit application is needed, please use version 1.8, however, this version will not work on an ISO image greater than 4GB.
Note: Please read the Important note section of the Release Notes for firmware upgrade instructions.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To use Smart Update Manager from the Service Pack for ProLiant:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.22
Previous Version of Firmware:
4.22
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.22
Previous Version of Firmware:
4.22
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
To use Smart Update Manager from the Service Pack for ProLiant :
Windows:
Windows:
Updating firmware with rpm installed:
# ./ CP042622.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-b249e2e715-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
Updating firmware with rpm installed:
# ./ CP042622.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-b249e2e715-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
Click the Install button to proceed with the installation.
]]>Click the Install button to proceed with the installation.
]]>| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
# ./ CP039413.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/hp-firmware-smartarray-112204add8-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
# ./ CP039413.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/hp-firmware-smartarray-112204add8-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
5.02
Last Recommended or Critical Version:
4.54(B)
Previous Version of Firmware:
4.10
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.02
Last Recommended or Critical Version:
4.54(B)
Previous Version of Firmware:
4.10
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
None
Known Issues:
None
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5 on vibsdepot.hpe.com.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5 on vibsdepot.hpe.com.
]]>The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also includes emergency power off improvements.
Known Issues:
None
Click the "Install" button to perform the driver installation.]]>
Click the "Install" button to perform the driver installation.]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added Support for RHEL 8.2
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added Support for RHEL 8.2
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later
To update the driver using VMware tools:
To update the driver using VMware tools:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Integrated Lights-Out 5 (iLO 5) Firmware version 1.40 and System ROM version 1.20 or later are required for HPE Gen10 servers.
]]>Integrated Lights-Out 5 (iLO 5) Firmware version 1.40 and System ROM version 1.20 or later are required for HPE Gen10 servers.
]]>Update the firmware and software in the usual manner.
Update the firmware and software in the usual manner.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]> # rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
# rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired components to be updated in the directory, \hp\swpackages on the USB key.
Update the firmware and software in the usual manner.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired components to be updated in the directory, \hp\swpackages on the USB key.
Update the firmware and software in the usual manner.
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
IMPORTANT UPDATE: SSA (GUI) for Linux can now be run without requiring the System Management Homepage. SSA now supports a Local Application Mode for Linux. The System Management Homepage is still supported, but no longer required to run the SSA GUI.
To invoke, enter the following at the command prompt:
ssa -local
The command will start SSA in a new Firefox browser window. When the browser window is closed, SSA will automatically stop. This is only valid for the loopback interface, and not visible to external network connections.
IMPORTANT UPDATE: SSA (GUI) for Linux can now be run without requiring the System Management Homepage. SSA now supports a Local Application Mode for Linux. The System Management Homepage is still supported, but no longer required to run the SSA GUI.
To invoke, enter the following at the command prompt:
ssa -local
The command will start SSA in a new Firefox browser window. When the browser window is closed, SSA will automatically stop. This is only valid for the loopback interface, and not visible to external network connections.
]]>
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
点击“安装”按钮继续执行驱动程序安装。]]>
Click the "Install" button to perform the driver installation.]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
In conjunction with the Smart Update Manager found on the SPP, the component can be used to deploy the firmware to the HPE BladeSystem c-Class Virtual Connect module.
Firmware extracted from the component can be deployed using the Virtual Connect Support Utility for the HPE BladeSystem c-Class Virtual Connect modules.
Installation Notes for using the component with Smart Update Manager and SPP
Installation Notes for using the firmware extracted from the component
Extract the firmware binary out of the component.
Place the firmware image file onto a system on the same network as the HPE BladeSystem c-Class Virtual Connect module.
Start the Virtual Connect Support Utility and deploy the firmware.
HPE requires using the HPE BladeSystem c-Class Virtual Connect Support Utility version 1.15.0 (or higher) to install the HPE VC FlexFabric-20/40 F8 version 4.85, HPE VC Flex-10/10D version 4.85, HPE VC FlexFabric 10Gb/24-port version 4.85, HPE VC 8Gb 24-Port FC version 4.20, HPE VC 16Gb 24-Port FC version 4.20, and HPE VC 8Gb 20-Port FC version 2.25 firmware. Please read the HPE BladeSystem c-Class Virtual Connect Support Utility release notes.
Please be advised of a serious issue that could cause network outage when upgrading directly from VC 2.xx release version to VC 4.85 release in Multi-Enclosure environment. Please upgrade from VC 2.xx to VC 3.70 or VC 4.10 first and then upgrade from VC 3.70 or VC 4.10 to VC 4.50 and then upgrade from VC 4.50 to VC 4.85 in a Multi-Enclosure setup.
To update HPE VC 8Gb 24-Port FC module(s) from Virtual Connect firmware 4.31 or lower to Virtual Connect 4.85 or higher, these module(s) must first be updated with either Virtual Connect firmware version 4.4x or version 4.50 (Recommended version is 4.50) before they can be updated with Virtual Connect 4.85 or higher.
The USB Key Utility is used to copy the SPP onto a portable USB key storage device. Please note that the latest version (v2.0.0.0) of the utility is now 64-bit only. If the 32-bit application is needed, please use version 1.8, however, this version will not work on an ISO image greater than 4GB.
Note: Please read the Important note section of the Release Notes for firmware upgrade instructions.
]]>In conjunction with the Smart Update Manager found on the SPP, the component can be used to deploy the firmware to the HPE BladeSystem c-Class Virtual Connect module.
Firmware extracted from the component can be deployed using the Virtual Connect Support Utility for the HPE BladeSystem c-Class Virtual Connect modules.
Installation Notes for using the component with Smart Update Manager and SPP
Installation Notes for using the firmware extracted from the component
Extract the firmware binary out of the component.
Place the firmware image file onto a system on the same network as the HPE BladeSystem c-Class Virtual Connect module.
Start the Virtual Connect Support Utility and deploy the firmware.
HPE requires using the HPE BladeSystem c-Class Virtual Connect Support Utility version 1.15.0 (or higher) to install the HPE VC FlexFabric-20/40 F8 version 4.85, HPE VC Flex-10/10D version 4.85, HPE VC FlexFabric 10Gb/24-port version 4.85, HPE VC 8Gb 24-Port FC version 4.20, HPE VC 16Gb 24-Port FC version 4.20, and HPE VC 8Gb 20-Port FC version 2.25 firmware. Please read the HPE BladeSystem c-Class Virtual Connect Support Utility release notes.
Please be advised of a serious issue that could cause network outage when upgrading directly from VC 2.xx release version to VC 4.85 release in Multi-Enclosure environment. Please upgrade from VC 2.xx to VC 3.70 or VC 4.10 first and then upgrade from VC 3.70 or VC 4.10 to VC 4.50 and then upgrade from VC 4.50 to VC 4.85 in a Multi-Enclosure setup.
To update HPE VC 8Gb 24-Port FC module(s) from Virtual Connect firmware 4.31 or lower to Virtual Connect 4.85 or higher, these module(s) must first be updated with either Virtual Connect firmware version 4.4x or version 4.50 (Recommended version is 4.50) before they can be updated with Virtual Connect 4.85 or higher.
The USB Key Utility is used to copy the SPP onto a portable USB key storage device. Please note that the latest version (v2.0.0.0) of the utility is now 64-bit only. If the 32-bit application is needed, please use version 1.8, however, this version will not work on an ISO image greater than 4GB.
Note: Please read the Important note section of the Release Notes for firmware upgrade instructions.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
| NIC | Boot Code Version | PXE Version | UEFI Version | iSCSI Version | FCoE Version | CCM Version | L2 Version |
| HP FlexFabric 10Gb 2-port 534M Adapter HP FlexFabric 10Gb 2-port 536FLB Adapter HP FlexFabric 20Gb 2-port 630FLB Adapter HP FlexFabric 20Gb 2-port 630M Adapter |
7.15.80 | 7.14.13 | 8.8.0 | 7.14.0 | 7.14.3 | 7.14.4 | 7.12.25 |
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe (or) chmod +x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe (or) chmod +x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
]]>Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
Reboot your system for the update to take effect immediately.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPGA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPGA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Problems Fixed:
Known Issues:
None
Problems Fixed:
Known Issues:
None
To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>On the Web-based Management Device Homepage, under "options", "Anonymous Access" should be enabled when using SSA.
When clicking on a controller that is currently being configured in a different SSA session, a message will appear which allows you to override the other SSA session or cancel. If you choose to override the other SSA session, any unsaved changes in the other session will be discarded.
To uninstall SSA, use Add/Remove Programs located in the Control Panel on Windows Systems.
To run SSA in local application mode on Windows, Internet Explorer must be the default browser.
The following are known issues:
On the Web-based Management Device Homepage, under "options", "Anonymous Access" should be enabled when using SSA.
When clicking on a controller that is currently being configured in a different SSA session, a message will appear which allows you to override the other SSA session or cancel. If you choose to override the other SSA session, any unsaved changes in the other session will be discarded.
To uninstall SSA, use Add/Remove Programs located in the Control Panel on Windows Systems.
To run SSA in local application mode on Windows, Internet Explorer must be the default browser.
The following are known issues:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPK3
Last Recommended or Critical Version:
HPK2
Previous Version of Firmware:
HPK2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPK3
Last Recommended or Critical Version:
HPK2
Previous Version of Firmware:
HPK2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
Additional Information:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Last Recommended or Critical Version:
6.88
Previous Version of Firmware:
6.60(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Last Recommended or Critical Version:
6.88
Previous Version of Firmware:
6.60(B)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA2 Ethernet 10/25Gb 2-port SFP28 Adapter | 800059DF | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA2 Ethernet 10/25Gb 2-port SFP28 Adapter | 800059DF | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
# rpm -ivh elx-nvmefc-connect-<version>.noarch.rpm
To upgrade the elx-nvmefc-connect RPM use the following command:
# rpm -Uvh elx-nvmefc-connect-<version>.noarch.rpm
]]># rpm -ivh elx-nvmefc-connect-<version>.noarch.rpm
To upgrade the elx-nvmefc-connect RPM use the following command:
# rpm -Uvh elx-nvmefc-connect-<version>.noarch.rpm
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port QSFP56 PCIe4 x16 OCP3 MCX653435A-HDAI Adapter(P31323-B21) | 20.29.1016 | MT_0000000592 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port QSFP56 PCIe4 x16 OCP3 MCX653435A-HDAI Adapter(P31323-B21) | 20.29.1016 | MT_0000000592 |
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional Information:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional Information:
Release Version and/or Date:
1.00(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.00(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The libibverb package must be installed on the target system prior to the installation of the RoCE library. If not already present, the libibverb package can be obtained from the operating system installation media.
]]>The libibverb package must be installed on the target system prior to the installation of the RoCE library. If not already present, the libibverb package can be obtained from the operating system installation media.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>
The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant :
To use Smart Update Manager from the Service Pack for ProLiant :
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
None
Problems Fixed:
Known Issues(refer to Customer Bulletin for workarounds):
None
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues(refer to Customer Bulletin for workarounds):
None
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>Click the "Install" button to perform the driver installation.]]>
Click the "Install" button to perform the driver installation.]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
For NFC agent to work seamlessly, the following ports are required to be enabled on firewall:
nvme-cli package is part of this rpm and it may conflict with preinstalled nvme-cli, hence it is recommended to uninstall the default nvme-cli package before installing this rpm.
NVMe-Rdma Drivers are required to be installed for NFC agent to work seamlessly.
]]>
For NFC agent to work seamlessly, the following ports are required to be enabled on firewall:
nvme-cli package is part of this rpm and it may conflict with preinstalled nvme-cli, hence it is recommended to uninstall the default nvme-cli package before installing this rpm.
NVMe-Rdma Drivers are required to be installed for NFC agent to work seamlessly.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
2.50
Last Recommended or Critical Version:
2.08
Previous Version of Firmware:
2.08
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
2.50
Last Recommended or Critical Version:
2.08
Previous Version of Firmware:
2.08
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Click the Install button to proceed with the installation.
]]>Click the Install button to proceed with the installation.
]]>| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To get the list of all dependency files for hp-health, type:
rpm –qp –requires hp-health-< version >.rpm
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>To install the package type:
rpm -ivh hp-health-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-health status
Additional help is available by typing:
man hp-health
or
man hp_mgmt_install
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for VMware 7.0 U1
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for VMware 7.0 U1
Problems Fixed:
None
Known Issues:
Requires iLO5 v2.30 or later
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
]]>
Remote Online:
To update the driver using VMware tools:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fix
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fix
None
Known Issues:
None
The libibverb package must be installed on the target system prior to the installation of the RoCE library. If not already present, the libibverb package can be obtained from the operating system installation media.
]]>The libibverb package must be installed on the target system prior to the installation of the RoCE library. If not already present, the libibverb package can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library on SUSE Linux Enterprise Server 15.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library on SUSE Linux Enterprise Server 15.
]]>To install or upgrade the driver type:
# rpm -Uvh hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
To install or upgrade the driver type:
# rpm -Uvh hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Red Hat Enterprise Linux 7 Server
Red Hat Enterprise Linux 6 Server (x86-64)
SUSE Linux Enterprise Server 12
Check dependency failed.
Current version: iLOx x.xx
Minimum version required: iLO4 2.20
The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn't apply to this system.
]]>Red Hat Enterprise Linux 7 Server
Red Hat Enterprise Linux 6 Server (x86-64)
SUSE Linux Enterprise Server 12
Check dependency failed.
Current version: iLOx x.xx
Minimum version required: iLO4 2.20
The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn't apply to this system.
]]>To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Added support for Windows Server 2019.
Problems Fixed:
None
]]>Enhancements/New Features:
Added support for Windows Server 2019.
Problems Fixed:
None
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>To install or upgrade the driver type:
# rpm -Uvh kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
To install or upgrade the driver type:
# rpm -Uvh kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
HPE Storage Fibre Channel Adapter Kit for the x64 Emulex Storport Driver v11.1.145.16 cp030886.exe
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
HPE Storage Fibre Channel Adapter Kit for the x64 Emulex Storport Driver v11.1.145.16 cp030886.exe
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>For detailed information about configurable components, see the Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>For detailed information about configurable components, see the Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter (P25960-B21) | 22.29.1016 | MT_0000000437 |
| Mellanox MCX623105AS-VDAT Ethernet 200Gb 1-port QSFP56 Adapter for HPE (P10180-B21) | 22.29.1016 | MT_0000000435 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 2-Port QSFP56 MCX623106AS-CDAT Adapter (P25960-B21) | 22.29.1016 | MT_0000000437 |
| Mellanox MCX623105AS-VDAT Ethernet 200Gb 1-port QSFP56 Adapter for HPE (P10180-B21) | 22.29.1016 | MT_0000000435 |
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Release Version and/or Date:
1.00 (E)
Last Recommended or Critical Version:
1.00 (D)
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.00 (E)
Last Recommended or Critical Version:
1.00 (D)
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To get the list of all dependency files for hp-snmp-agents type:
rpm –qp –-requires hp-snmp-agents-<version>.rpm
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>To install the package, type:
rpm -ivh hp-snmp-agents-<version>.rpm
To check whether the package is loaded properly type:
/etc/init.d/hp-snmp-agents status
Additional help is available by typing:
man hp-snmp-agents
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue during unaligned write commands, found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability.
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue during unaligned write commands, found in supplier ongoing lab testing.Includes additional fixes to improve error handling and reliability.
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
# esxcli software vib install -d=<path><componet_bundle> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]># esxcli software vib install -d=<path><componet_bundle> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>http://www.hpe.com/storage/spock/
The HPE supplied Emulex driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Emulex driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>在该硬盘目录中，执行下载的文件。
点击“安装”按钮进行安装。
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Release Version and/or Date:
1.56(D)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.56(D)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed
None
Known Issues:
None
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Release Version and/or Date:
2.00 (B)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
2.00 (B)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
iLO 5 v1.20 or later
]]>iLO 5 v1.20 or later
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
]]>HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Linux which is integrated into the standard Linux kernel.
]]>Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO except for Edgeline blades which are not supported by the Service Pack for ProLiant (SPP) ISO
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO except for Edgeline blades which are not supported by the Service Pack for ProLiant (SPP) ISO
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
If the server contains only CNA adapters and lpfc driver is already been installed, post the new driver update, please remove the lpfc driver using the following command:
#esxcli software vib remove lpfc
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Additional Information:
Additional Information:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Online NVMe SSD Flash Component for VMware ESXi - LO0400KEFJQ, LO0800KEFJR, LO1600KEFJT, LO2000KEFJU, LT0800KEXVA, LT1600KEXVB, and LT2000KEXVC Drives
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Online NVMe SSD Flash Component for VMware ESXi - LO0400KEFJQ, LO0800KEFJR, LO1600KEFJT, LO2000KEFJU, LT0800KEXVA, LT1600KEXVB, and LT2000KEXVC Drives
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
To use HPE Smart Update Manager from the Service Pack for ProLiant :
]]>
To use HPE Smart Update Manager from the Service Pack for ProLiant :
]]>
Problems Fixed:
Known Issues:
None
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Offline:
Remote Online:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]>Offline:
Remote Online:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]>iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
To update firmware from Linux operating system on target server:
Updating firmware without installing the rpm
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system.
HP recommends for remote deployment of this package that you obtain the most recent version of the Service Pack for ProLiant (SPP) and follow these steps:
To update firmware from Linux operating system on target server:
Updating firmware without installing the rpm
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system.
HP recommends for remote deployment of this package that you obtain the most recent version of the Service Pack for ProLiant (SPP) and follow these steps:
Enhancements/New Features for FW version 4.3.6.0 (B):
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features for FW version 4.3.6.0 (B):
Problems Fixed:
None
Known Issues:
None
The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media..
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media..
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
T
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
T
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG7
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the Install button to proceed with the installation.
]]>Click the Install button to proceed with the installation.
]]>| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 2-port QSFP56 PCIe4 x16 MCX653106A-HDAT Adapter(P31324-B21) | 20.29.1016 | MT_0000000594 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 2-port QSFP56 PCIe4 x16 MCX653106A-HDAT Adapter(P31324-B21) | 20.29.1016 | MT_0000000594 |
]]>
http://www.hpe.com/storage/spock/
The OOB NIC driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
Additional requirements:
The target environment must have the libsysfs or sysfsutils package installed prior to the installation of the firmware update kit. If not already present, the libsysfs or sysfsutils package can be obtained from the operating system installation media.
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex HBAs/CNAs
Environment must be running the syslog daemon for the flash engine to run
Note: To enable the FCoE/iSCSI protocol on devices that support it, please install the appropriate Emulex FCoE/iSCSI driver. The FCoE protocol also requires the HPE Emulex FCoE Enablement Kit be installed. The drivers and enablement kit are also available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FCoE Driver Kit, reboot, and then install the Enablement Kit.
]]>http://www.hpe.com/storage/spock/
The OOB NIC driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
Additional requirements:
The target environment must have the libsysfs or sysfsutils package installed prior to the installation of the firmware update kit. If not already present, the libsysfs or sysfsutils package can be obtained from the operating system installation media.
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex HBAs/CNAs
Environment must be running the syslog daemon for the flash engine to run
Note: To enable the FCoE/iSCSI protocol on devices that support it, please install the appropriate Emulex FCoE/iSCSI driver. The FCoE protocol also requires the HPE Emulex FCoE Enablement Kit be installed. The drivers and enablement kit are also available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FCoE Driver Kit, reboot, and then install the Enablement Kit.
]]> 2. cd to the appropriate location for your system, and update the firmware by executing ./.setup
When the firmware installation completes, you may remove the firmware installation tool from your system using the rpm -e command: rpm -e <rpm_package_name>.
2. cd to the appropriate location for your system, and update the firmware by executing ./.setup
When the firmware installation completes, you may remove the firmware installation tool from your system using the rpm -e command: rpm -e <rpm_package_name>.
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
NOTE: During the flash operation, the message "No Adapter Found!" may appear in the logs. These messages do not indicate a problem with the firmware flash operation and may be ignored.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
NOTE: During the flash operation, the message "No Adapter Found!" may appear in the logs. These messages do not indicate a problem with the firmware flash operation and may be ignored.
It is advised to provide read-write permissions on /var/tmp folder. Firmware deployment via Service Pack for ProLiant(SPP) might be unsuccessful in some cases , if read-write(rw) permissions are not enable on /tmp or /var/tmp directories.
From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version
]]>
From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version
]]>
| InfiniBand Card Type | Firmware Version | PSID |
| HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter (843400-B21) | 12.28.1002 |
HPE2920111032 |
| HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter (872723-B21) | 16.29.1016 | HPE0000000017 |
| HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter (872725-B21) | 16.29.1016 | HPE0000000008 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter (843400-B21) | 12.28.1002 |
HPE2920111032 |
| HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter (872723-B21) | 16.29.1016 | HPE0000000017 |
| HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter (872725-B21) | 16.29.1016 | HPE0000000008 |
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None.
]]>Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant :
To use Smart Update Manager from the Service Pack for ProLiant :
Release Version and/or Date:
2.00 (B)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
2.00 (B)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
在运行 VMware ESXi 操作系统的目标服务器上更新固件：
To update firmware from VMware ESXi operating system on target server:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Filesystem or application might read old data when SmartCache configurations that encounter intermittent write I/O errors to a primary logical drive.
Known Issues:
None
]]>
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Filesystem or application might read old data when SmartCache configurations that encounter intermittent write I/O errors to a primary logical drive.
Known Issues:
None
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
]]>
]]>
~# esxcli software vib install -v=<path><filename.vib> --no-sig-check
~# esxcli software vib remove -n=<filename.vib>
]]>~# esxcli software vib install -v=<path><filename.vib> --no-sig-check
~# esxcli software vib remove -n=<filename.vib>
]]># esxcli software vib install -v=<path><filename.vib> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]># esxcli software vib install -v=<path><filename.vib> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]>Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D3000.log and flash summary is logged to /var/cpq/Component.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D3000.log and flash summary is logged to /var/cpq/Component.log.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
Download the SCEXE file to a client running a Linux operating system. Execute: sh CP0xxxxx.scexe --unpack=directory
This command will unpack the ilo4_1XX.bin into a user specified "directory". If the directory does not exist, the unpacker will attempt to create it.
To use HPE Smart Update Manager on the Firmware Maintenance CD:
Place the Firmware Maintenance CD on a USB key using the HPE USB Key Creator Utility.
Copy CP0xxxxx.scexe to /compaq/swpackages directory on the USB Key.
Follow HPE Smart Update Manager steps to complete firmware update.
Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]> To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
Download the SCEXE file to a client running a Linux operating system. Execute: sh CP0xxxxx.scexe --unpack=directory
This command will unpack the ilo4_1XX.bin into a user specified "directory". If the directory does not exist, the unpacker will attempt to create it.
To use HPE Smart Update Manager on the Firmware Maintenance CD:
Place the Firmware Maintenance CD on a USB key using the HPE USB Key Creator Utility.
Copy CP0xxxxx.scexe to /compaq/swpackages directory on the USB Key.
Follow HPE Smart Update Manager steps to complete firmware update.
Upgrade Requirement: Lowering the severity of the upgrade requirement to Recommended as per the HPE Product Security Policy. It is based on the CVE score for this security vulnerability (7.3), assessment of the impact and the probability of occurrence. So upgrade requirement has been revised to ‘Recommended’ upgrade.
]]>iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant :
To use Smart Update Manager from the Service Pack for ProLiant :
Problems Fixed:
Over-temp issue was a false IML due to a >=60C threshold, modified the threshold to >65C in new version.
Known Issues:
None
Problems Fixed:
Over-temp issue was a false IML due to a >=60C threshold, modified the threshold to >65C in new version.
Known Issues:
None
From that drive and directory, execute the downloaded file.]]>
From that drive and directory, execute the downloaded file.]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
To update the driver using VMware tools:
]]>
Remote Online:
To update the driver using VMware tools:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
Linux FC Driver Kit for HPE Branded Emulex FC HBAs and mezz cards, version 11.1.183.21(minimum version supported) for RedHat 7, RedHat 8 and Novell SUSE 12, SUSE 15
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>
http://www.hpe.com/storage/spock/
The HPE supplied fibre channel driver must be installed prior to this enablement kit component if you want to enable Smart SAN functionality. The driver is available on the HPE.com website at www.hpe.com.
Linux FC Driver Kit for HPE Branded Emulex FC HBAs and mezz cards, version 11.1.183.21(minimum version supported) for RedHat 7, RedHat 8 and Novell SUSE 12, SUSE 15
However, if a Smart SAN enabled driver is not installed at execution time, the component will land the enablement kit files for future use after the driver has been installed.
]]>
# rpm -e hpe-emulex-smartsan-enablement-<version>.noarch.rpm
This is a configurable component. It requires a configuration file in order to enable/disable Smart SAN functionality. If no configuration is performed, the current Smart SAN status is stated and the execution is complete. No further action is taken.
For detailed information about configurable components, see the HP Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
1. Login as the system administrator (root).
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install, type the following command at the prompt:
# rpm -ivh hpe-emulex-smartsan-enablement-kit-<version>.x86_64.rpm
Example: # rpm -ivh hpe-emulex-smartsan-enablement-kit-1.0.0.0-1.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Installation complete
]]>
# rpm -e hpe-emulex-smartsan-enablement-<version>.noarch.rpm
This is a configurable component. It requires a configuration file in order to enable/disable Smart SAN functionality. If no configuration is performed, the current Smart SAN status is stated and the execution is complete. No further action is taken.
For detailed information about configurable components, see the HP Smart Update Manager User Guide at http://www.hpe.com/support/HP_SUM_UG_en.
Component execution outside of HPE Service Pack for Proliant:
1. Login as the system administrator (root).
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install, type the following command at the prompt:
# rpm -ivh hpe-emulex-smartsan-enablement-kit-<version>.x86_64.rpm
Example: # rpm -ivh hpe-emulex-smartsan-enablement-kit-1.0.0.0-1.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Installation complete
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Release Version and/or Date:
HPGB
Last Recommended or Critical Version:
HPG7
Previous Version of Firmware:
HPG7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Microsoft SNMP Service must be enabled, if SMA (System Management Assistant) is enabled.
]]>Microsoft SNMP Service must be enabled, if SMA (System Management Assistant) is enabled.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the service installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the service installation.
]]>1. Restart the AMS service (type 'net stop ams' followed by 'net start ams' in a command prompt) ...OR...
2. Create a new DWORD registry value named PollInterval in registry's HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hpeams\Parameters and set its value to higher than decimal 300. This value will determine how often (in seconds) AMS reads data from WMI.
]]>1. Restart the AMS service (type 'net stop ams' followed by 'net start ams' in a command prompt) ...OR...
2. Create a new DWORD registry value named PollInterval in registry's HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hpeams\Parameters and set its value to higher than decimal 300. This value will determine how often (in seconds) AMS reads data from WMI.
]]>Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = Red Hat Enterprise Linux 8
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = Red Hat Enterprise Linux 8
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port MCX653105A-HDAT QSFP56 x16 Adapter (P23664-B21) | 20.29.1016 | MT_0000000451 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port MCX653105A-HDAT QSFP56 x16 Adapter (P23664-B21) | 20.29.1016 | MT_0000000451 |
]]>
http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) host bus adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) host bus adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update the driver using VMware tools:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
For NFC agent to work seamlessly, the following ports are required to be enabled on firewall:
nvme-cli package is part of this rpm and it may conflict with preinstalled nvme-cli, hence it is recommended to uninstall the default nvme-cli package before installing this rpm.
NVMe-Rdma Drivers are required to be installed for NFC agent to work seamlessly.
]]>For NFC agent to work seamlessly, the following ports are required to be enabled on firewall:
nvme-cli package is part of this rpm and it may conflict with preinstalled nvme-cli, hence it is recommended to uninstall the default nvme-cli package before installing this rpm.
NVMe-Rdma Drivers are required to be installed for NFC agent to work seamlessly.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied Emulex NIC driver must be installed prior to this firmware component being identified by SUM for deployment. The latest driver is available on the HPE.com website at http://www.hpe.com/.
The FCoE/iSCSI OOB driver and FCoE enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>http://www.hpe.com/storage/spock/
The HPE supplied Emulex NIC driver must be installed prior to this firmware component being identified by SUM for deployment. The latest driver is available on the HPE.com website at http://www.hpe.com/.
The FCoE/iSCSI OOB driver and FCoE enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>The downloaded file is a self-extracting executable with a filename based on the Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
The downloaded file is a self-extracting executable with a filename based on the Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG8
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features for:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG8
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features for:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
HPS2
Previous Version of Firmware:
HPS2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPS4
Last Recommended or Critical Version:
HPS2
Previous Version of Firmware:
HPS2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
In addition, the System Management Homepage (SMH) component is required for a single server web-based user interface.
]]>
In addition, the System Management Homepage (SMH) component is required for a single server web-based user interface.
]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
Note: If HPE System Insight Manager support is required, install the latest Service Pack for ProLiant and
lsi-mpt2sas-kmp-X.X.X.X-X.sles12spN.x86_64.rpm after the OS has completed its installation process and system has rebooted.
Note: If HPE System Insight Manager support is required, install the latest Service Pack for ProLiant and
lsi-mpt2sas-kmp-X.X.X.X-X.sles12spN.x86_64.rpm after the OS has completed its installation process and system has rebooted.
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
4ICDHPK1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
4ICDHPK1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>To install the package type:
rpm -ivh hp-ams-<version>.rpm
To check whether the package is loaded properly type:
systemctl status hp-ams
Additional help is available by typing:
man amshelper
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Verify that the HPE iLO 4 is talking to SNMP from a Linux system with net-snmp utilities installed:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.1.1
Verify that HPE AMS is operating on the Server:
snmpwalk -t 60 -v 2c -Ox -c iLO4_configured_community_string iLO4_IP_Address 1.3.6.1.4.1.232.5.1
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
Known Issues(refer to Customer Bulletin for workarounds):
Enhancements/New Features:
Problems Fixed:
Known Issues(refer to Customer Bulletin for workarounds):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Release Version and/or Date:
1.3.2.215
Last Recommended or Critical Version:
1.3.2.215
Previous Version of Firmware:
1.3.2.212
Firmware Dependency:
None
Enhancements/New Features:
None.
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
1.3.2.215
Last Recommended or Critical Version:
1.3.2.215
Previous Version of Firmware:
1.3.2.212
Firmware Dependency:
None
Enhancements/New Features:
None.
Problems Fixed:
Known Issues:
None
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant
]]>
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant
]]>
Release Version and/or Date:
2.50
Last Recommended or Critical Version:
2.08
Previous Version of Firmware:
1.50
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
2.50
Last Recommended or Critical Version:
2.08
Previous Version of Firmware:
1.50
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
]]>
]]>
Updating firmware without installing rpm:
Updating firmware without installing rpm:
| OPA HFI Adapter Type | Firmware Version | SSID |
| HPE 100Gb 1-Port OP101 QSFP28 x8 OPA Adapter | 1.9.2.0.0 | E7 |
| HPE 100Gb 1-Port OP101 QSFP28 x16 OPA Adapter | 1.9.2.0.0 | E8 |
| HPE Apollo 100Gb 1-port Intel Omni-Path Architecture 860z Mezzanine FIO Adapter | 1.9.2.0.0 | 21C |
| OPA HFI Adapter Type | Firmware Version | SSID |
| HPE 100Gb 1-Port OP101 QSFP28 x8 OPA Adapter | 1.9.2.0.0 | E7 |
| HPE 100Gb 1-Port OP101 QSFP28 x16 OPA Adapter | 1.9.2.0.0 | E8 |
| HPE Apollo 100Gb 1-port Intel Omni-Path Architecture 860z Mezzanine FIO Adapter | 1.9.2.0.0 | 21C |
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D6020.log and flash summary is logged to /var/cpq/Component.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D6020.log and flash summary is logged to /var/cpq/Component.log.
]]>Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d6020-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d6020-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
]]>From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
Note: In order to upgrade/downgrade CX5 network adapter firmware from 16.21.1xxx or 16.22.1xxx (and earlier) to 16.26.1xxx (and later), use 16.23.1xxx or 16.24.1xxx or 16.25.1xxx as intermediate firmware version.
]]>| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand EDR/Ethernet 100Gb 1-port 840QSFP28 Adapter (825110-B21) | 12.28.1002 | HP_2180110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 840QSFP28 Adapter (825111-B21) | 12.28.1002 | HP_2190110032 |
| HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (872726-B21) | 16.29.1016 | HPE0000000009 |
| HPE InfiniBand FDR/Ethernet 40/50Gb 2-port 547FLR-QSFP Adapter (879482-B21) | 16.29.1016 | HPE0000000022 |
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
0.37
Last Recommended or Critical Version:
0.37
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Initial Release
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPK1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Release Version and/or Date:
HPK1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>
点击“安装”按钮进行安装。]]>
Click the "Install" button to proceed with the installation.]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
NOTE: When using ESXi6.0 you must be at upgrade 3 or newer. The required SmartPQI driver is not present in earlier versions of the OS
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
]]>
NOTE: When using ESXi6.0 you must be at upgrade 3 or newer. The required SmartPQI driver is not present in earlier versions of the OS
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HP Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
]]>
Release Version and/or Date:
2.00 (C)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
2.00 (C)
Last Recommended or Critical Version:
2.00
Previous Version of Firmware:
2.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]> NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
http://www.hpe.com/storage/spock/
The HPE supplied Emulex NIC driver must be installed prior to this firmware component being identified by SUM for deployment. The latest driver is available on the HPE.com website at http://www.hpe.com/.
The FCoE/iSCSI OOB driver and FCoE enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>http://www.hpe.com/storage/spock/
The HPE supplied Emulex NIC driver must be installed prior to this firmware component being identified by SUM for deployment. The latest driver is available on the HPE.com website at http://www.hpe.com/.
The FCoE/iSCSI OOB driver and FCoE enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>The downloaded file is a self-extracting executable with a filename based on the Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
The downloaded file is a self-extracting executable with a filename based on the Component Number.
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –force or --replacepkgs with nodeps option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –force or --replacepkgs with nodeps option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Last Recommended or Critical Version:
7.00(C)
Previous Version of Firmware:
7.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Last Recommended or Critical Version:
7.00(C)
Previous Version of Firmware:
7.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = SUSE Linux Enterprise Server 12 SP2
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = SUSE Linux Enterprise Server 12 SP2
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
None
Known Issues:
None.
]]>Problems Fixed:
None
Known Issues:
None.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use HP Smart Update Manager from the Service Pack for ProLiant :
To use HP Smart Update Manager from the Service Pack for ProLiant :
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d3000-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Updating firmware with rpm installation:
# ./CP0xxxxx.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-d3000-<version>-*' location
NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Offline:
Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+M Adapter (764282-B21) | 2.42.5000 | HP_1350110023 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+M Adapter (764283-B21) | 2.42.5056 | HP_1360110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+QSFP Adapter (764284-B21) | 2.42.5056 | HP_1370110017 |
| HPE InfiniBand FDR/Ethernet 10Gb/40Gb 2-port 544+FLR-QSFP Adapter (764285-B21) | 2.42.5700 | HP_1380110017 |
| HPE InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter (764286-B21) | 2.42.5000 | HP_1390110023 |
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.22
Previous Version of Firmware:
4.22
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.22
Previous Version of Firmware:
4.22
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The management interface driver must be installed on the server.
Microsoft .Net Framework 2.0 or later is required to launch HPONCFG GUI.
]]>The management interface driver must be installed on the server.
Microsoft .Net Framework 2.0 or later is required to launch HPONCFG GUI.
]]>Place Component to a directory in a temporary directory on your hard drive. Double-click it to run.
Click on the install button to install the utlility on the server. This does not require a reboot.
The utility will be installed in the program files under the directory HewlettPackardEnterprise\HPONCFG\
A shortcut for the graphical interface of the utility will be provided in "Start Menu > Programs > HPE System Tools > HPE Lights-Out Online Configuration Utility".
]]>Place Component to a directory in a temporary directory on your hard drive. Double-click it to run.
Click on the install button to install the utlility on the server. This does not require a reboot.
The utility will be installed in the program files under the directory HewlettPackardEnterprise\HPONCFG\
A shortcut for the graphical interface of the utility will be provided in "Start Menu > Programs > HPE System Tools > HPE Lights-Out Online Configuration Utility".
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
http://www.hpe.com/storage/spock/
The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>http://www.hpe.com/storage/spock/
The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG8
Last Recommended or Critical Version:
HPG6
Previous Version of Firmware:
HPG6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG5
Previous Version of Firmware:
HPG5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
The management interface driver and management agents must be installed on the server.
For iLO 5, openssl v1.0.x or later is required in addition to above packages.
Customers who manually compile and install openssl or intentionally relocate /usr/bin/openssl, need to set PATH environment variable to direct HPONCFG to the right/intended openssl.
The management interface driver and management agents must be installed on the server.
For iLO 5, openssl v1.0.x or later is required in addition to above packages.
Customers who manually compile and install openssl or intentionally relocate /usr/bin/openssl, need to set PATH environment variable to direct HPONCFG to the right/intended openssl.
If a previous version of the Hponcfg utility has been installed, it must be removed before this package can be installed. To remove the previous version of the package, type the following :
To install the package, type:
After installation, the executable for hponcfg utility can be found under the directory /sbin.
]]>If a previous version of the Hponcfg utility has been installed, it must be removed before this package can be installed. To remove the previous version of the package, type the following :
To install the package, type:
After installation, the executable for hponcfg utility can be found under the directory /sbin.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
在该硬盘目录中，执行下载的文件。]]>
From that drive and directory, execute the downloaded file.]]>
Updating firmware with rpm installed:
# ./ CP042871.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-2e20068436-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
Updating firmware with rpm installed:
# ./ CP042871.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
# ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-2e20068436-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
]]>
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Problems Fixed:
Known Issues:
None
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Added support for RHEL 8.3
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.93
Previous Version of Firmware:
4.93
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.08
Last Recommended or Critical Version:
4.93
Previous Version of Firmware:
4.93
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D8000.log and flash summary is logged to /var/cpq/Component.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D8000.log and flash summary is logged to /var/cpq/Component.log.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
• Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
• Added support for RHEL 8.3
Problems Fixed:
Known Issues:
None
A REBOOT is required for your computer when the setup is complete.
Note: If HPE System Insight Manager support is required, install the latest ProLiant Support Pack and kmod-mpt2sas-X.X.X.X-X.rhel7uN.x86_64.rpm after the OS has completed its installation process and system has rebooted.
]]>A REBOOT is required for your computer when the setup is complete.
Note: If HPE System Insight Manager support is required, install the latest ProLiant Support Pack and kmod-mpt2sas-X.X.X.X-X.rhel7uN.x86_64.rpm after the OS has completed its installation process and system has rebooted.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Release Version and/or Date:
2.50 (A)
Last Recommended or Critical Version:
2.50
Previous Version of Firmware:
2.50
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
2.50 (A)
Last Recommended or Critical Version:
2.50
Previous Version of Firmware:
2.50
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Integrated Lights-Out 5 (iLO 5) Firmware version 1.40 and System ROM version 1.20 or later are required for HPE Gen10 servers.
]]>Integrated Lights-Out 5 (iLO 5) Firmware version 1.40 and System ROM version 1.20 or later are required for HPE Gen10 servers.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>To use Smart Update Manager from the Service Pack for ProLiant :
To use Smart Update Manager from the Service Pack for ProLiant :
Release Version and/or Date:
15.10.10.00 (E)
Last Recommended or Critical Version:
15.10.10.00 (D)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
15.10.10.00 (E)
Last Recommended or Critical Version:
15.10.10.00 (D)
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.1, 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.1 is 5.0.3.9.
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5, and 5.1 on vibsdepot.hpe.com.
]]>The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.1 is 5.0.3.9.
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
HPE 3PAR HostExplorer smart component will be installed only if the host has connectivity to HPE 3PAR StoreServ.
]]>HPE 3PAR HostExplorer smart component will be installed only if the host has connectivity to HPE 3PAR StoreServ.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Release Version and/or Date:
1.52(A)
Last Recommended or Critical Version:
1.52
Previous Version of Firmware:
1.52
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
1.52(A)
Last Recommended or Critical Version:
1.52
Previous Version of Firmware:
1.52
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-CQDA2 Ethernet 100Gb 2-port QSFP28 Adapter | 800059DB | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-CQDA2 Ethernet 100Gb 2-port QSFP28 Adapter | 800059DB | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>application through HTTPS (HTTP packets exchanged over an SSL/TLS-encrypted session).
The OA web interface requires an XSLT-enabled browser with support for JavaScript 1.3 or the equivalent.
Supported browsers include:
• Microsoft Internet Explorer 11
• Mozilla Firefox 67.0.4(64-bit)
• Google Chrome 77.0.3865.90 (Official Build) (64-bit)
]]>
application through HTTPS (HTTP packets exchanged over an SSL/TLS-encrypted session).
The OA web interface requires an XSLT-enabled browser with support for JavaScript 1.3 or the equivalent.
Supported browsers include:
• Microsoft Internet Explorer 11
• Mozilla Firefox 67.0.4(64-bit)
• Google Chrome 77.0.3865.90 (Official Build) (64-bit)
]]>
Installation Notes for using the component as a standalone component
This SCEXE component is a self-extracting executable. The SCEXE file unpacks itself, flashes the firmware on the HPE BladeSystem c-Class Onboard Administrator, and cleans up.
The general command line syntax for this smart component is
sh cpxxxxxx.scexe -target <netAddress> -user <username> -passwd <password> [-s[ilent]] [-f[orce]] [-logdir <path>]
where cpxxxxxx.scexe represents the filename of the component
NOTE: All arguments and information enclosed in brackets are optional. If required arguments are not included on the command line, you will be prompted to provide the input.
To flash the firmware:
The return codes are:
Installation Notes for using the component with HPE Smart Update Manager and the SPP
Installation Notes for using the firmware extracted from the component
The user guide for the Onboard Administrator is located here.
The user guide for the Onboard Administrator command line interface is located here.
Installation Notes for using the component as a standalone component
This SCEXE component is a self-extracting executable. The SCEXE file unpacks itself, flashes the firmware on the HPE BladeSystem c-Class Onboard Administrator, and cleans up.
The general command line syntax for this smart component is
sh cpxxxxxx.scexe -target <netAddress> -user <username> -passwd <password> [-s[ilent]] [-f[orce]] [-logdir <path>]
where cpxxxxxx.scexe represents the filename of the component
NOTE: All arguments and information enclosed in brackets are optional. If required arguments are not included on the command line, you will be prompted to provide the input.
To flash the firmware:
The return codes are:
Installation Notes for using the component with HPE Smart Update Manager and the SPP
Installation Notes for using the firmware extracted from the component
The user guide for the Onboard Administrator is located here.
The user guide for the Onboard Administrator command line interface is located here.
HPE BladeSystem c-Class OA Firmware
Release Version
Version 4.97
Previous Version of Firmware
Version 4.96
Firmware Dependency
For firmware compatibility information,see the HPE Service Pack for ProLiant Information Libraryat:
https://www.hpe.com/servers/spp/documentation
Important Notes
Starting OA 4.50 release, a standardized code signing and validation mechanism has been introduced to enhance the firmware image authenticity.
For customers using Firmware ROM image to upgrade OA:
For OA with firmware version less than 3.50, first update to OA 3.50 and then continue updating to OA 4.50 or above.
For customers using Smart Components to upgrade OA:
OA firmware update mechanisms which rely on HPE Smart Components (example: EFM), will not be affected by this change. The Smart Component will automatically perform the intermediate upgrade to OA 3.50 before performing the OA 4.50 or above upgrade.
Flash Disaster Recovery to a version of firmware 4.50 or above issupported. The behavior is seen due to the implementation of a new firmware image signing mechanism in OA firmware version 4.50 and above, which causes the FDR mechanism to see the firmware image as an invalid image.
The workaround for this is to use Flash Disaster Recovery procedure to recover to a version of firmware prior to 4.50 and then do a firmware upgrade to the intended version (4.50 or later).
The OA only supports SPP ISO images that are less than 4GB in size, whether hosted directly via the Enclosure DVD feature or an attached USB key, or mounted remotely via a specified URL. If an ISO image exceeds 4 GB, the CLI SHOW FIRMWARE MANAGEMENT command displays ISO URL Status as “Invalid URL.”
If an SPP ISO image exceeds 4 GB, it is necessary to create a custom ISO image that excludes components unnecessary to the OA EFM blade firmware update process. At a minimum, the custom ISO must contain the firmware components for HPE ProLiant BL servers. (When using HPE SUM to create the custom ISO image, select Firmware as the Component Type, and select HPE ProLiant BL Series as the Server Type.) For information about creating a custom ISO image compatible for OA EFM functionality, see the HPE BladeSystem Onboard Administrator User Guide. More HPE SUM information can be found via HPE Smart Update Manager online help or at the HPE Smart Update Enterprise Information Library (http://www.hpe.com/info/hpsum/documentation).
Onboard Administrator 4.71 is FIPS certified as referenced in the 140-2 In Process list located at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf.
When the Enable DHCPv6, Enable Router Advertisements, or Enable SLAAC enclosure IPv6 settings are disabled on the Onboard Administrator, the respective DHCPv6 or SLAAC addresses of the iLOs in the enclosure are retained until these addresses expire automatically based on their respective configurations. A manual reset of the iLO releases these addresses immediately.
]]>HPE BladeSystem c-Class OA Firmware
Release Version
Version 4.97
Previous Version of Firmware
Version 4.96
Firmware Dependency
For firmware compatibility information,see the HPE Service Pack for ProLiant Information Libraryat:
https://www.hpe.com/servers/spp/documentation
Important Notes
Starting OA 4.50 release, a standardized code signing and validation mechanism has been introduced to enhance the firmware image authenticity.
For customers using Firmware ROM image to upgrade OA:
For OA with firmware version less than 3.50, first update to OA 3.50 and then continue updating to OA 4.50 or above.
For customers using Smart Components to upgrade OA:
OA firmware update mechanisms which rely on HPE Smart Components (example: EFM), will not be affected by this change. The Smart Component will automatically perform the intermediate upgrade to OA 3.50 before performing the OA 4.50 or above upgrade.
Flash Disaster Recovery to a version of firmware 4.50 or above issupported. The behavior is seen due to the implementation of a new firmware image signing mechanism in OA firmware version 4.50 and above, which causes the FDR mechanism to see the firmware image as an invalid image.
The workaround for this is to use Flash Disaster Recovery procedure to recover to a version of firmware prior to 4.50 and then do a firmware upgrade to the intended version (4.50 or later).
The OA only supports SPP ISO images that are less than 4GB in size, whether hosted directly via the Enclosure DVD feature or an attached USB key, or mounted remotely via a specified URL. If an ISO image exceeds 4 GB, the CLI SHOW FIRMWARE MANAGEMENT command displays ISO URL Status as “Invalid URL.”
If an SPP ISO image exceeds 4 GB, it is necessary to create a custom ISO image that excludes components unnecessary to the OA EFM blade firmware update process. At a minimum, the custom ISO must contain the firmware components for HPE ProLiant BL servers. (When using HPE SUM to create the custom ISO image, select Firmware as the Component Type, and select HPE ProLiant BL Series as the Server Type.) For information about creating a custom ISO image compatible for OA EFM functionality, see the HPE BladeSystem Onboard Administrator User Guide. More HPE SUM information can be found via HPE Smart Update Manager online help or at the HPE Smart Update Enterprise Information Library (http://www.hpe.com/info/hpsum/documentation).
Onboard Administrator 4.71 is FIPS certified as referenced in the 140-2 In Process list located at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf.
When the Enable DHCPv6, Enable Router Advertisements, or Enable SLAAC enclosure IPv6 settings are disabled on the Onboard Administrator, the respective DHCPv6 or SLAAC addresses of the iLOs in the enclosure are retained until these addresses expire automatically based on their respective configurations. A manual reset of the iLO releases these addresses immediately.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
A REBOOT is required for your computer when the setup is complete.
]]>A REBOOT is required for your computer when the setup is complete.
]]>From that drive and directory, execute the downloaded file.
]]>From that drive and directory, execute the downloaded file.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
“Setup is unable to load a setup DLL（安装无法加载setup DLL）”
Check dependency failed.（检查依赖关系失败。）
Current version:（当前版本：） iLOx x.xx
Minimum version required:（所需的最低版本：） iLO4 2.20
本系统中不能安装该软件，因为系统中不存在所需的硬件，或者该软件或固件不适用于本系统。
]]>“Setup is unable to load a setup DLL”
Check dependency failed.
Current version: iLOx x.xx
Minimum version required: iLO4 2.20
The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn't apply to this system.
]]>To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
To update firmware from Windows operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant :
]]>
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
A REBOOT is required for your computer when the setup is complete.
]]>A REBOOT is required for your computer when the setup is complete.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>This is a self extracting executable module. One can execute this module via the command line console or from Windows graphical user interface.
GUI Option:
CLI Option:
Execute the Smart Component by entering the following command: CP0xxxxx.exe /s
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Online:
NOTES: OPTIONS for in band enclosure flash:
Parameter Description
-----------------------------------------------------------------------------
/h,/? Displays command line usage help(dialog box)
/s Installs without user interaction
The following command is applicable only with /s:
/f Allow a downgrade or reinstall if already up to date
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
]]>
]]>
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.
]]>
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware with rpm installed:
# ./CP032706.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/firmware-nvdimm-16gb-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Updating firmware with rpm installed:
# ./CP032706.scexe in the '/usr/lib/x86_64-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/x86_64-linux-gnu/firmware-nvdimm-16gb-*' location
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use HP Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Linux:
VMWare:
Linux:
VMWare:
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4.When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4.When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh elx-lpfc-kmp-default-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 1-port QSFP28 PCIe3 x16 MCX515A-CCAT Adapter(P31246-B21) | 16.29.1016 | MT_0000000591 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 100Gb 1-port QSFP28 PCIe3 x16 MCX515A-CCAT Adapter(P31246-B21) | 16.29.1016 | MT_0000000591 |
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD6
Previous Version of Firmware:
HPD6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD6
Previous Version of Firmware:
HPD6
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
T
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
T
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 200Gb 1-port QSFP56 MCX623105AS-VDAT Adapter (P10180-B21) | 22.29.1016 | MT_0000000435 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 200Gb 1-port QSFP56 MCX623105AS-VDAT Adapter (P10180-B21) | 22.29.1016 | MT_0000000435 |
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]> To use Smart Update Manager from the Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
1.79(A)
Last Recommended or Critical Version:
1.79
Previous Version of Firmware:
1.79
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Drive may show up missing after a system reboot.
Known Issues:
None
Release Version and/or Date:
1.79(A)
Last Recommended or Critical Version:
1.79
Previous Version of Firmware:
1.79
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Drive may show up missing after a system reboot.
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Refer to VMware documentation for information on the esxcli commands
]]>Refer to VMware documentation for information on the esxcli commands
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Reboot your system for the update to take effect immediately.
Reboot your system for the update to take effect immediately.
点击“安装”按钮继续执行驱动程序安装。]]>
Click the "Install" button to perform the driver installation.]]>
]]>
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>http://www.hpe.com/storage/spock/
The HPE supplied Qlogic driver must be installed prior to this firmware component being identified by SUM for deployment. The OOB driver is available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download/
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
To update the driver using VMware tools:
To update the driver using VMware tools:
If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
]]>If local system doesn't configure any network interface for the adapter that are necessary to create the network config file to bring up interface.
- For example in sles15sp1, To create ifcfg-ethX files under /etc/sysconfig/network/.
]]>
Updating firmware without installing the rpm:
Additional Information:
Updating firmware without installing the rpm:
Additional Information:
| NIC | EEPROM/NVM Version | OROM Version | Single NVM Version |
|---|---|---|---|
| HPE Ethernet 1Gb 2-port 361i Adapter | 8000106F | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 361T Adapter | 80000F91 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 363i Adapter | 80000D00 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366i Communication Board | 80000EBF | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366i Adapter | 8000105E | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366FLR Adapter | 80001060 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366T Adapter | 8000105F | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 368i Adapter | 800027FA | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 368FLR-MMT Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 369i Adapter | 800027FB | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 560FLR-SFP+ Adapter | 80000838 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 560SFP+ Adapter | 80000835 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 561T Adapter | 80000636 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 561FLR-T Adapter | 800005B6 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568i Adapter | 800027FC | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568FLR-MMSFP+ Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568FLR-MMT Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 563i Adapter | 800035C0 | 1.1375.0 | N/A |
| HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter | 80009655 | 1.2836.0 | 10.54.7 |
| HPE Ethernet 10Gb 2-port 562FLR-T Adapter | 8000137D | 1.2836.0 | 10.54.4 |
| HPE Ethernet 10Gb 2-port 562SFP+ Adapter | 800095AA | 1.2836.0 | 10.54.7 |
| HPE Ethernet 10Gb 2-port 562T Adapter | 8000137C | 1.2836.0 | 10.54.4 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
The combo image v1.1375.0 includes: Boot Agent: 1GbE - v1.5.72, 10GbE - v2.3.46, 40GbE - v1.0.21 & UEFI Drivers: 1GbE - v6.9.13, 10GbE - v5.0.20, 40GbE - v1.5.14
Single NVM Version is new firmware format which represent an unified version in place of the previously used EEPROM/NVM Version or OROM version.
]]>| NIC | EEPROM/NVM Version | OROM Version | Single NVM Version |
|---|---|---|---|
| HPE Ethernet 1Gb 2-port 361i Adapter | 8000106F | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 361T Adapter | 80000F91 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 363i Adapter | 80000D00 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366i Communication Board | 80000EBF | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366i Adapter | 8000105E | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366FLR Adapter | 80001060 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 366T Adapter | 8000105F | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 368i Adapter | 800027FA | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 2-port 368FLR-MMT Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 1Gb 4-port 369i Adapter | 800027FB | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 560FLR-SFP+ Adapter | 80000838 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 560SFP+ Adapter | 80000835 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 561T Adapter | 80000636 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 561FLR-T Adapter | 800005B6 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568i Adapter | 800027FC | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568FLR-MMSFP+ Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 568FLR-MMT Adapter | 800027F8 | 1.2836.0 | N/A |
| HPE Ethernet 10Gb 2-port 563i Adapter | 800035C0 | 1.1375.0 | N/A |
| HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter | 80009655 | 1.2836.0 | 10.54.7 |
| HPE Ethernet 10Gb 2-port 562FLR-T Adapter | 8000137D | 1.2836.0 | 10.54.4 |
| HPE Ethernet 10Gb 2-port 562SFP+ Adapter | 800095AA | 1.2836.0 | 10.54.7 |
| HPE Ethernet 10Gb 2-port 562T Adapter | 8000137C | 1.2836.0 | 10.54.4 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
The combo image v1.1375.0 includes: Boot Agent: 1GbE - v1.5.72, 10GbE - v2.3.46, 40GbE - v1.0.21 & UEFI Drivers: 1GbE - v6.9.13, 10GbE - v5.0.20, 40GbE - v1.5.14
Single NVM Version is new firmware format which represent an unified version in place of the previously used EEPROM/NVM Version or OROM version.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5 on vibsdepot.hpe.com.
]]>1. The "HPE ProLiant iLO 3/4 Channel Interface Driver” (CHIF) must be installed and running.
The minimum iLO version for ESXi 5.5 and ESXi 6.0 and ESXi 6.5 is 1.4. The minimum iLO version for ESXi 6.7 is 10.1.0.
2. The “Compaq ROM Utility Driver” (CRU) must be installed and running
The minimum CRU version for ESXi 5.5 is 5.5.4.1.
The minimum CRU version for ESXi 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools. The drivers are also available from the OS specific “HPE Agentless Management Service Offline Bundle” for VMware vSphere 6.7, 6.5, 6.0, 5.5 on vibsdepot.hpe.com.
]]>The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
The minimum CRU version for 5.5 is 5.5.4.1.
The minimum CRU version for 6.0 is 6.0.8.
The minimum CRU version for 6.5 is 6.5.8.
The minimum CRU version for 6.7 is 6.7.10.
Offline:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
HPG4
Previous Version of Firmware:
HPG4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
application through HTTPS (HTTP packets exchanged over an SSL/TLS-encrypted session).
The OA web interface requires an XSLT-enabled browser with support for JavaScript 1.3 or the equivalent.
Supported browsers include:
• Microsoft Internet Explorer 11
• Mozilla Firefox 67.0.4(64-bit)
• Google Chrome 77.0.3865.90 (Official Build) (64-bit)
]]>application through HTTPS (HTTP packets exchanged over an SSL/TLS-encrypted session).
The OA web interface requires an XSLT-enabled browser with support for JavaScript 1.3 or the equivalent.
Supported browsers include:
• Microsoft Internet Explorer 11
• Mozilla Firefox 67.0.4(64-bit)
• Google Chrome 77.0.3865.90 (Official Build) (64-bit)
]]>Installation Notes for using the component as a stand alone component
This smart component is a self-extracting executable. The smart component unpacks itself, flashes the firmware on the HPE BladeSystem c-Class Onboard Administrator, and cleans up.
The general command line syntax for this smart component is
cpxxxxxx.exe /target <netAddress> /user <username> /passwd <password> [/s[ilent]] [/f[orce]] [/logdir <path>]
where cpxxxxxx.exe represents the filename of the component
NOTE: All arguments and information enclosed in brackets are optional. If required arguments are not included on the command line, you will be prompted to provide the input.
To flash the firmware:
The return codes are :
Installation Notes for using the component with HPE Smart Update Manager and the SPP
Installation Notes for using the firmware extracted from the component
The user guide for the Onboard Administrator is located here.
The user guide for the Onboard Administrator command line interface is located here.
Installation Notes for using the component as a stand alone component
This smart component is a self-extracting executable. The smart component unpacks itself, flashes the firmware on the HPE BladeSystem c-Class Onboard Administrator, and cleans up.
The general command line syntax for this smart component is
cpxxxxxx.exe /target <netAddress> /user <username> /passwd <password> [/s[ilent]] [/f[orce]] [/logdir <path>]
where cpxxxxxx.exe represents the filename of the component
NOTE: All arguments and information enclosed in brackets are optional. If required arguments are not included on the command line, you will be prompted to provide the input.
To flash the firmware:
The return codes are :
Installation Notes for using the component with HPE Smart Update Manager and the SPP
Installation Notes for using the firmware extracted from the component
The user guide for the Onboard Administrator is located here.
The user guide for the Onboard Administrator command line interface is located here.
HPE BladeSystem c-Class OA Firmware
Release Version
Version 4.97
Previous Version of Firmware
Version 4.96
Firmware Dependency
For firmware compatibility information,see the HPEService Pack for ProLiant Information Libraryat:
https://www.hpe.com/servers/spp/documentation
Important Notes
Starting OA 4.50 release, a standardized code signing and validation mechanism has been introduced to enhance the firmware image authenticity.
For customers using Firmware ROM image to upgrade OA:
For OA with firmware version less than 3.50, first update to OA 3.50 and then continue updating to OA 4.50 or above.
For customers using Smart Components to upgrade OA:
OA firmware update mechanisms which rely on HPE Smart Components (example: EFM), will not be affected by this change. The Smart Component will automatically perform the intermediate upgrade to OA 3.50 before performing the OA 4.50 or above upgrade.
Flash Disaster Recovery to a version of firmware 4.50 or above issupported. The behavior is seen due to the implementation of a new firmware image signing mechanism in OA firmware version 4.50 and above, which causes the FDR mechanism to see the firmware image as an invalid image.
The workaround for this is to use Flash Disaster Recovery procedure to recover to a version of firmware prior to 4.50 and then do a firmware upgrade to the intended version (4.50 or later).
The OA only supports SPP ISO images that are less than 4GB in size, whether hosted directly via the Enclosure DVD feature or an attached USB key, or mounted remotely via a specified URL. If an ISO image exceeds 4 GB, the CLI SHOW FIRMWARE MANAGEMENT command displays ISO URL Status as “Invalid URL.”
If an SPP ISO image exceeds 4 GB, it is necessary to create a custom ISO image that excludes components unnecessary to the OA EFM blade firmware update process. At a minimum, the custom ISO must contain the firmware components for HPE ProLiant BL servers. (When using HPE SUM to create the custom ISO image, select Firmware as the Component Type, and select HPE ProLiant BL Series as the Server Type.) For information about creating a custom ISO image compatible for OA EFM functionality, see the HPE BladeSystem Onboard Administrator User Guide. More HPE SUM information can be found via HPE Smart Update Manager online help or at the HPE Smart Update Enterprise Information Library (http://www.hpe.com/info/hpsum/documentation).
Onboard Administrator 4.71 is FIPS certified as referenced in the 140-2 In Process list located at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf.
When the Enable DHCPv6, Enable Router Advertisements, or Enable SLAAC enclosure IPv6 settings are disabled on the Onboard Administrator, the respective DHCPv6 or SLAAC addresses of the iLOs in the enclosure are retained until these addresses expire automatically based on their respective configurations. A manual reset of the iLO releases these addresses immediately.
]]>HPE BladeSystem c-Class OA Firmware
Release Version
Version 4.97
Previous Version of Firmware
Version 4.96
Firmware Dependency
For firmware compatibility information,see the HPEService Pack for ProLiant Information Libraryat:
https://www.hpe.com/servers/spp/documentation
Important Notes
Starting OA 4.50 release, a standardized code signing and validation mechanism has been introduced to enhance the firmware image authenticity.
For customers using Firmware ROM image to upgrade OA:
For OA with firmware version less than 3.50, first update to OA 3.50 and then continue updating to OA 4.50 or above.
For customers using Smart Components to upgrade OA:
OA firmware update mechanisms which rely on HPE Smart Components (example: EFM), will not be affected by this change. The Smart Component will automatically perform the intermediate upgrade to OA 3.50 before performing the OA 4.50 or above upgrade.
Flash Disaster Recovery to a version of firmware 4.50 or above issupported. The behavior is seen due to the implementation of a new firmware image signing mechanism in OA firmware version 4.50 and above, which causes the FDR mechanism to see the firmware image as an invalid image.
The workaround for this is to use Flash Disaster Recovery procedure to recover to a version of firmware prior to 4.50 and then do a firmware upgrade to the intended version (4.50 or later).
The OA only supports SPP ISO images that are less than 4GB in size, whether hosted directly via the Enclosure DVD feature or an attached USB key, or mounted remotely via a specified URL. If an ISO image exceeds 4 GB, the CLI SHOW FIRMWARE MANAGEMENT command displays ISO URL Status as “Invalid URL.”
If an SPP ISO image exceeds 4 GB, it is necessary to create a custom ISO image that excludes components unnecessary to the OA EFM blade firmware update process. At a minimum, the custom ISO must contain the firmware components for HPE ProLiant BL servers. (When using HPE SUM to create the custom ISO image, select Firmware as the Component Type, and select HPE ProLiant BL Series as the Server Type.) For information about creating a custom ISO image compatible for OA EFM functionality, see the HPE BladeSystem Onboard Administrator User Guide. More HPE SUM information can be found via HPE Smart Update Manager online help or at the HPE Smart Update Enterprise Information Library (http://www.hpe.com/info/hpsum/documentation).
Onboard Administrator 4.71 is FIPS certified as referenced in the 140-2 In Process list located at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf.
When the Enable DHCPv6, Enable Router Advertisements, or Enable SLAAC enclosure IPv6 settings are disabled on the Onboard Administrator, the respective DHCPv6 or SLAAC addresses of the iLOs in the enclosure are retained until these addresses expire automatically based on their respective configurations. A manual reset of the iLO releases these addresses immediately.
]]>Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
1.56(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.56(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>Click the "Install" button to proceed with the installation. The utility will automatically be installed.
]]>ssaducli -f adu-report.zip
To generate a SmartSSD Wear gauge report, enter the following command:
ssaducli -ssdrpt -f ssd-report.zip
More options can be found by "ssaducli -help".
Additional Notes
----------------
Both the diagnostic and SmartSSD wear gauge reports are generated in compressed
(ZIP) format.
The diagnostic report output archive contains the following files:
* ADUReport.txt => Diagnostic report in text format
* ADUReport.xml => Diagnostic report in XML format
* ADUReport.htm => HTML viewer for diagnostic report
* report.checksum => checksum file
* SlotX.txt (SlotX.old) => Controller serial output log
Note: The serial output log file(s) are only available if the "HP Smart
Array SAS/SATA Event Notification Service" is installed and running.
To view the diagnostic report in a browser, extract the ADUReport.htm. Open
ADUReport.htm in the browser.
The SmartSSD wear gauge report output archive contains the following files:
* SmartSSDWearGaugeReport.txt => SmartSSD wear gauge report in text format
* SmartSSDWearGaugeReport.json => SmartSSD wear gauge report in JSON format
* SmartSSDWearGaugeReport.htm => HTML viewer for the JSON wear gauge report
To view the SmartSSD wear gauge report in a browser, extract the
SmartSSDWearGaugeReport.json, SmartSSDWearGaugeReport.htm files to a
directory (both files must reside in the same directory). Open
SmartSSDWearGaugeReport.htm in the browser.
Known Issues
------------
* When installing the 32-bit version of SSADUCLI on a system that has a
64-bit (x64) version of SSADUCLI installed, please uninstall the 64-bit
version first. Failing to uninstall the 64-bit version will cause the 32-bit
installation to fail.
ssaducli -f adu-report.zip
To generate a SmartSSD Wear gauge report, enter the following command:
ssaducli -ssdrpt -f ssd-report.zip
More options can be found by "ssaducli -help".
Additional Notes
----------------
Both the diagnostic and SmartSSD wear gauge reports are generated in compressed
(ZIP) format.
The diagnostic report output archive contains the following files:
* ADUReport.txt => Diagnostic report in text format
* ADUReport.xml => Diagnostic report in XML format
* ADUReport.htm => HTML viewer for diagnostic report
* report.checksum => checksum file
* SlotX.txt (SlotX.old) => Controller serial output log
Note: The serial output log file(s) are only available if the "HP Smart
Array SAS/SATA Event Notification Service" is installed and running.
To view the diagnostic report in a browser, extract the ADUReport.htm. Open
ADUReport.htm in the browser.
The SmartSSD wear gauge report output archive contains the following files:
* SmartSSDWearGaugeReport.txt => SmartSSD wear gauge report in text format
* SmartSSDWearGaugeReport.json => SmartSSD wear gauge report in JSON format
* SmartSSDWearGaugeReport.htm => HTML viewer for the JSON wear gauge report
To view the SmartSSD wear gauge report in a browser, extract the
SmartSSDWearGaugeReport.json, SmartSSDWearGaugeReport.htm files to a
directory (both files must reside in the same directory). Open
SmartSSDWearGaugeReport.htm in the browser.
Known Issues
------------
* When installing the 32-bit version of SSADUCLI on a system that has a
64-bit (x64) version of SSADUCLI installed, please uninstall the 64-bit
version first. Failing to uninstall the 64-bit version will cause the 32-bit
installation to fail.
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh elx-lpfc-kmp-default-11.2.xxx.x_3.0.76_0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e elx-lpfc-<kerneltype><version>.<OSupdate>.x86_64
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features for :
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features for :
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.]]>
From that drive and directory, execute the downloaded file.]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver type:
# rpm -Uvh hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
To install or upgrade the driver type:
# rpm -Uvh hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e hpdsa-kmp-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
点击安装按钮继续执行安装。
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later
The "iLO 5 Channel Interface Driver” (CHIF) for Windows which is available from Service Pack for ProLiant (SPP).
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO except for Edgeline blades which are not supported by the Service Pack for ProLiant (SPP) ISO
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system for the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using the Service Pack for ProLiant (SPP) ISO except for Edgeline blades which are not supported by the Service Pack for ProLiant (SPP) ISO
Option1:
Option 2:
Note that this mechanism can be scripted through iLO for performing updates to multiple servers.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>This method works if this component is already installed on the ESXi host and is running in the Auto mode.
Refer Server updates through iLO 5 in SUM User Guide
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>This method works if this component is already installed on the ESXi host and is running in the Auto mode.
Refer Server updates through iLO 5 in SUM User Guide
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
To update the driver using VMware tools:
Remote Online:
To update the driver using VMware tools:
To update firmware from Windows operating system on target server:
HP recommends for remote deployment of this package that you obtain the most recent version of the Service Pack for ProLiant (SPP) and follow these steps:
To update firmware from Windows operating system on target server:
HP recommends for remote deployment of this package that you obtain the most recent version of the Service Pack for ProLiant (SPP) and follow these steps:
Enhancements/New Features for FW version 4.3.6.0 (C):
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features for FW version 4.3.6.0 (C):
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D6020.log and flash summary is logged to /var/cpq/Component.log.
]]>WARNING! Do not power cycle or restart during the firmware update as this can result in loss of capabilities for this unit. It typically takes several minutes for the firmware to load.
NOTE: All firmware flash progress messages are logged to /var/cpq/D6020.log and flash summary is logged to /var/cpq/Component.log.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>NOTES:
OPTIONS for in band enclosure flash
| -d, --discover <absolute path to file> | Dumps discovery information in XML format to <file> |
| -e, --reflash | Flash even if the device is already up to date |
| -f, --force | Always flash applicable devices (same as -e -g) |
| -g, --downgrade | Flash if the device has a later firmware |
| -s, --silent | Do not display any text and no user interaction required |
To use Smart Update Manager (SUM) from the Service Pack for ProLiant (SPP):
Remote Online:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
To update the driver using VMware tools:
To update the driver using VMware tools:
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
None
Problems Fixed:
Known Issues:
None
This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>This pre-compiled RPM package may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG5
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete, the following message displays:
Setup is now complete. Please REBOOT your computer NOW!!
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –reinstall option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –reinstall
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Known Issues:
None
To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To update firmware from VMware ESXi operating system on target server:
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>To update the driver using VMware tools:
To update the driver using VMware tools:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
1.00(C)
Last Recommended or Critical Version:
1.00(B)
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.00(C)
Last Recommended or Critical Version:
1.00(B)
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 546SFP+ Adapter (779793-B21) | 2.42.5044 | HP_1200111023 |
| HPE Ethernet 10Gb 2-port 546FLR-SFP+ Adapter (779799-B21) | 2.42.5044 | HP_2240110004 |
| HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter (817749-B21) | 14.29.1016 | HP_2690110034 |
| HPE Ethernet 25Gb 2-port 640SFP28 Adapter (817753-B21) | 14.29.1016 | HP_2420110034 |
| HPE Ethernet 100Gb 1-port 842QSFP28 Adapter (874253-B21) | 16.29.1016 | HPE0000000014 |
To update the driver using VMware tools:
To update the driver using VMware tools:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
]]>Enhancements/New Features:
Problems Fixed:
None
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe (or) chmod +x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe (or) chmod +x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
<full path> is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To use HP Smart Update Manager from the HPE Service Pack for ProLiant :
]]>
To use HP Smart Update Manager from the HPE Service Pack for ProLiant :
]]>
Release Version and/or Date:
5.02
Last Recommended or Critical Version:
4.54(A)
Previous Version of Firmware:
4.10
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
5.02
Last Recommended or Critical Version:
4.54(A)
Previous Version of Firmware:
4.10
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
None
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]> # rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
# rpm -e hp-fc-enablement-<version>.noarch.rpm
To install the hp-CNA-fc-enablement RPM use the following command:
# rpm -ivh HP-CNA-FC-Broadcom-Enablement-Kit-<version>.<OS>.<architecture>.rpm
This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
http://www.hpe.com/storage/spock/
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD7
Previous Version of Firmware:
HPD7
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
在该硬盘目录中，执行下载的文件。]]>
From that drive and directory, execute the downloaded file.]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
Network connectivity may stop during the upgrade process and may need to be restarted after completion.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
This component can only be executed on Windows x64.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
Note: Per Microsoft kb #2031031(https://support.microsoft.com/en-us/kb/2931031), users cannot remove/unmount a USB until after the install has finished.
]]>Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>如要通过 HP ProLiant服务包 使用 HP智能升级管理器 ：
]]>
To use HP Smart Update Manager from the Service Pack for ProLiant :
]]>
Release Version and/or Date:
8.32 (C)
Last Recommended or Critical Version:
8.32
Previous Version of Firmware:
8.32
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
8.32 (C)
Last Recommended or Critical Version:
8.32
Previous Version of Firmware:
8.32
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Select "Install" to start extracting to a temporary location on the hard drive.
Click the "Install" button to perform the driver installation.
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD3
Last Recommended or Critical Version:
HPD1
Previous Version of Firmware:
HPD1
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh brcmfcoe-kmp-default-11.2.xxxx.x_3.0.76._0.11-1.sles11sp3.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e brcmfcoe-<kerneltype><version>.<OSupdate>.x86_64
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>The libibverb and rdma-core package must be installed on the target system prior to the installation of the RoCE library. If not already present, the packages can be obtained from the operating system installation media.
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>Use --force or --replacefiles options while installing or updating the HPE Broadcom RoCE library which may conflict with inbox library
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD9
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD9
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager 8.0.0 or later, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPD8
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
Known Issues:
None
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA4 Ethernet 10/25Gb 4-port SFP28 Adapter | 800059D9 | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>| NIC | EEPROM ID | OROM Version | NVM Version |
|---|---|---|---|
| Intel E810-XXVDA4 Ethernet 10/25Gb 4-port SFP28 Adapter | 800059D9 | 1.2839.0 | 2.24 |
The combo image v1.2839.0 includes: Intel(R) Boot Agent ICE v2.2.01 & UEFI x64 100 gigabit driver v2.2.07.
]]>Updating firmware without installing rpm:
Updating firmware without installing rpm:
| InfiniBand Card Type | Firmware Version | PSID |
| HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter (843400-B21) | 12.28.1002 |
HPE2920111032 |
| HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter (872723-B21) | 16.29.1016 | HPE0000000017 |
| HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter (872725-B21) | 16.29.1016 | HPE0000000008 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE Apollo A10 InfiniBand EDR (100Gb) 2-port Adapter (843400-B21) | 12.28.1002 |
HPE2920111032 |
| HPE Apollo InfiniBand EDR 100Gb 2-port 841z Mezzanine Adapter (872723-B21) | 16.29.1016 | HPE0000000017 |
| HPE InfiniBand EDR 100Gb 1-port 841QSFP28 Adapter (872725-B21) | 16.29.1016 | HPE0000000008 |
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]> NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
NOTE: Updated utilities and system libraries are required to support the iLO
HighSecurity, FIPS, and CNSA security states. The HPONCFG Windows utility
does not currently support the CNSA security state.
To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
Download the SCEXE file to a client running a Linux operating system. Execute: sh CP0xxxxx.scexe --unpack=directory
This command will unpack the ilo5_XXX.bin into a user specified "directory". If the directory does not exist, the unpacker will attempt to create it.
To use HP Smart Update Manager on the Firmware Maintenance CD:
Place the Firmware Maintenance CD on a USB key using the USB Key Creator Utility.
Copy CP0xxxxx.scexe to /compaq/swpackages directory on the USB Key.
Follow HP Smart Update Manager steps to complete firmware update.
To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
Download the SCEXE file to a client running a Linux operating system. Execute: sh CP0xxxxx.scexe --unpack=directory
This command will unpack the ilo5_XXX.bin into a user specified "directory". If the directory does not exist, the unpacker will attempt to create it.
To use HP Smart Update Manager on the Firmware Maintenance CD:
Place the Firmware Maintenance CD on a USB key using the USB Key Creator Utility.
Copy CP0xxxxx.scexe to /compaq/swpackages directory on the USB Key.
Follow HP Smart Update Manager steps to complete firmware update.
iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
iLO 5 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
http://www.hpe.com/info/ilo-docs
Select your lights-out product, then support & documents, then manuals.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port 548SFP+ Adapter (P11338-B21) | 14.29.1016 | HPE0000000038 |
Update the firmware and software in the usual manner.
]]>Update the firmware and software in the usual manner.
]]>1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Updating firmware without installing the rpm:
Additional Information:
Updating firmware without installing the rpm:
Additional Information:
| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>| NIC | EEPROM/NVM Version | OROM Version |
|---|---|---|
| HPE Ethernet 10Gb 2-port 560FLB Adapter | 800008F0 | 1.2836.0 |
| HPE Ethernet 10Gb 2-port 560M Adapter | 8000083D | 1.2836.0 |
The combo image v1.2836.0 includes: Boot Agent: 1GbE - v1.5.88, 10GbE - v2.4.44, 40GbE - v1.1.18 & UEFI Drivers: 1GbE - v9.4.06, 10GbE - v7.8.13, 40GbE - v4.4.12
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>Beginning with software release 11.2, Fibre Channel (LightPulse) adapters and Converged Network adapters (OneConnect) have independent software kits.
It is highly recommended that you review the Broadcom Software Kit Migration User Guide for more detailed information regarding this change.
To obtain the guide:
This document provides special instructions and considerations for using the driver kits for FC and CNA adapters.
Special cases include those in which pre-11.2 (original) drivers and applications are replaced by the new 11.2 drivers and applications, and cases in which inbox drivers are replaced by the new 11.2 out-of-box (OOB) drivers.
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
]]>This version of the enablement kit does not provide the additional functionality of rebuilding the ram disk or setting driver parameters as the previous versions had done. Please refer to the “Additional setup” section of the Native Linux Device-Mapper Multipath for HPE StorageWorks Arrays reference guide for instructions on how to perform these functions. The reference guide is available at the following link:
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>Click the Install button to proceed with the installation.
]]>| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE Ethernet 10Gb 2-port SFP+ MCX4121A-XCHT Adapter (P21930-B21) | 14.29.1016 | MT_0000000414 |
| HPE Ethernet 10Gb 2-port SFP+ MCX4621A-ACAB OCP3 Adapter (P11341-B21) | 14.29.1016 | MT_0000000238 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX512F-ACHT Adapter (P13188-B21) | 16.29.1016 | MT_0000000416 |
| HPE Ethernet 10/25Gb 2-port SFP28 MCX562A-ACAI OCP3 Adapter (P10112-B21) | 16.29.1016 | MT_0000000241 |
| HPE Ethernet 100Gb 2-port QSFP28 MCX516A-CCHT Adapter (P21927-B21) | 16.29.1016 | MT_0000000417 |
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
]]>
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
NA
Last Recommended or Critical Version:
NA
Previous Version of Firmware:
NA
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
A REBOOT is required for your computer when the setup is complete.
]]>A REBOOT is required for your computer when the setup is complete.
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPGE
Last Recommended or Critical Version:
HPGB
Previous Version of Firmware:
HPGB
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
]]>From that drive and directory, execute the downloaded file.
Click the Install button to proceed with the installation.
]]>| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>
To install this bundle using VMware tools:
Refer to VMware documentation for information on the esxcli commands
]]>amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = Red Hat Enterprise Linux 7.3 Errata 3.10.0.514.6.1
amsd only supported on HPE Gen10/Gen10 Plus Servers.
amsd provides information to the iLO 5 service providing SNMP support.
Requirements:
Minimum iLO 5 Firmware Version = 1.1
Minimum supported OS Versions = Red Hat Enterprise Linux 7.3 Errata 3.10.0.514.6.1
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
HPG2
Previous Version of Firmware:
HPG2
Firmware Dependency:
None
Enhancements/New Features :
Added support for Windows Server 2019.
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FC Driver Kit, reboot, and then install the Enablement Kit.
Additional requirements:
Environment must be running the syslog daemon for the flash engine to run
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex Host Bus Adapters(HBAs)
http://www.hpe.com/storage/spock/
The HPE supplied enablement kit must be installed prior to this firmware component being identified by SUM for deployment.
The OOB driver and enablement kit are available on the Service Pack for ProLiant (SPP) which is available at http://www.hpe.com/servers/spp/download.
The Enablement Kit requires that the target environment have the libHBAAPI package installed from your OS installation media.
Install the FC Driver Kit, reboot, and then install the Enablement Kit.
Additional requirements:
Environment must be running the syslog daemon for the flash engine to run
Environment must have 32-bit netlink library (libnl.so) installed for component to be able to discover Emulex Host Bus Adapters(HBAs)
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver type:
# rpm -Uvh kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
To install or upgrade the driver type:
# rpm -Uvh kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-hpdsa-<version>.<OSupdate>.x86_64.rpm
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
Download the appropriate SPP
Add the component to the SPP
Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated
Run SUM
Add the ESXi host to be updated as a remote target/node
Enter IP or DNS address of the ESXi host to be updated
Enter the ESXi host credentials (root or administrator username and password)
For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
Follow Smart Update Manager Steps to complete the firmware update
Refer to the SPP documentation for detailed instructions at: https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx
Note: While updating firmware using SUM, "View Devices" option on the review page does not list the exact name of the adapter. This is an expected behavior and does not affect the functionality of the component.
To use HPE Insight Control for vCenter:
Log in to the vSphere Client
Select a server or cluster in the inventory tree
Click the HPE Insight Management tab
Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
Enable SSH on the ESXi host.
Login as root. (You must be root in order to apply the update)
Place the Smart Component in a temporary directory
Check if the nmst module is loaded already: vmkload_mod -l | grep nmst
If module is not loaded, use the command to load the module: vmkload_mod nmst
From the same directory, execute the Smart Component. For example: unzip CPXXXXXX.zip; ./CPXXXXXX.vmexe
Follow the directions given by the Smart Component.
Logout.
Disable SSH on the ESXi host.
Reboot your system, if required, for the firmware update to take effect.
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
| InfiniBand Card Type | Firmware Version | PSID |
| HPE InfiniBand HDR/Ethernet 200Gb 1-port 940QSFP56 x16 Adapter (P06154-B21) | 20.29.1016 | HPE0000000034 |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port 940QSFP56 x16 Adapter (P06250-B21) | 20.29.1016 | HPE0000000035 |
| HPE InfiniBand HDR100/Ethernet 100Gb 2-port 940QSFP56 x16 Adapter (P06251-B21) | 20.29.1016 | HPE0000000036 |
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
1. Place the Component in a temporary directory.
2. From the same directory, run the Component by double-clicking it.
3. When the Component dialog window displays, click the Install button to initiate the firmware upgrade.
4. Reboot your system if you would like the update to take effect immediately.
Supplemental updates for supported ProLiant servers and options can be done by using Smart Update Manager, which is found on the Service Pack for ProLiant ISO.
Update the firmware and software in the usual manner.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe or chmod +x CPXXXXX.vmexe64 (for ESXi7.0)
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To use HPE Insight Control for vCenter:
To update firmware from VMware ESXi operating system on target server:
chmod +x CPXXXXXX.vmexe or chmod +x CPXXXXX.vmexe64 (for ESXi7.0)
Firmware Dependency:
None
Enhancements/New Features:
Added support for ESXi 7.0
Problems Fixed:
None
Known Issues:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for ESXi 7.0
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG4
Last Recommended or Critical Version:
HPG3
Previous Version of Firmware:
HPG3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
]]>
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Additional Information:
Updating firmware with rpm installed:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Additional Information:
Release Version and/or Date:
1.00(B)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.00(B)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD7
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
# esxcli software vib install -v=<path><filename.vib> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]># esxcli software vib install -v=<path><filename.vib> --no-sig-check
# esxcli software vib remove -n=<filename.vib>
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Online firmware update fails when drives are connected behind AHCI controller.
Known Issues:
None
Release Version and/or Date:
HPG6
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Corrects a potential data integrity issue caused by an in process write retry incorrectly starting at the wrong location. This issue was found during supplier ongoing reliability testing.
The firmware also corrects settings preservation after a code download, and includes emergency power off improvements.
Online firmware update fails when drives are connected behind AHCI controller.
Known Issues:
None
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
Release Version and/or Date:
HPD9
Last Recommended or Critical Version:
HPD8
Previous Version of Firmware:
HPD8
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None.
Known Issues:
None
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh kmod-qla2xxx-4.6.28-20.rhel6u1.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To update the driver using VMware tools:
To update the driver using VMware tools:
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
]]>
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod x CPXXXXXX.vmexe (or) chmod x CPXXXXXX.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD4
Last Recommended or Critical Version:
HPD2
Previous Version of Firmware:
HPD2
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>http://www.hpe.com/storage/spock/
NOTE:
On any HPE Gen 9 Servers running Linux with secure boot enabled, must install the HPE-DB-2016 secure-boot key in NVRAM in order to load this Driver. For more information please go through the support document with title "HPE Gen9 Servers with Secure Boot Enabled Must Install the New HPE Db Key to Update Drivers" available at the following link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00109772en_us.
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>2. Download the RPM to a directory on your hard drive and change to that directory.
3. To install or upgrade the driver, type the following command at the prompt:
# rpm -Uvh qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Example: # rpm -Uvh qlgc-qla2xxx-4.6.28-20.sles12sp2.x86_64.rpm
4. When the installation or upgrade is complete without any failure, please reboot the server for changes to take effect.
IMPORTANT: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
# rpm -e qlgc-qla2xxx-<version>.<OSupdate>.x86_64.rpm
Rewrite of same Driver version has to be performed using –force or --replacepkgs with --nodeps option
Example: rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –force --nodeps
rpm –Uvh kmod-qla2xxx-<version>.<OSupdate>.x86_64.rpm –replacepkgs --nodeps
For more information please refer to the Knowledge Base at: https://www.suse.com/support/kb/doc/?id=000019640
]]>To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
Release Version and/or Date:
HPD6
Last Recommended or Critical Version:
HPD5
Previous Version of Firmware:
HPD5
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
]]>
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
1. To flash this firmware package, use the following iLOrest command. See http://www.hpe.com/servers/resttool to download the latest version of the iLOrest tool.
localhost OS example:
ilorest flashfwpkg <file_name.fwpkg>
remote example:
ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>
2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).
Supplemental updates for supported ProLiant servers and options can be done by using SUM, which is found on the Service Pack for ProLiant (SPP) ISO.
Place the Service Pack for ProLiant on a USB key using the USB Key Creator Utility.
Place the desired firmware packages and components to be updated in the directory "\packages" on the USB key.
Update the firmware and software in the usual manner.
Reboot your system for the update to take effect immediately
3. Flash from iLO GUI
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port MCX653105A-ECAT QSFP56 x16 Adapter(P23665-B21) | 20.29.1016 | MT_0000000452 |
]]>
| Mellanox Ethernet Only Adapters | Firmware Version | PSID |
| HPE InfiniBand HDR100/Ethernet 100Gb 1-port MCX653105A-ECAT QSFP56 x16 Adapter(P23665-B21) | 20.29.1016 | MT_0000000452 |
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/NewFeatures :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG3
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/NewFeatures :
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant
]]>
To use Smart Update Manager from the Service Pack for ProLiant
]]>
Release Version and/or Date:
1.56(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
1.56(C)
Last Recommended or Critical Version:
1.00
Previous Version of Firmware:
1.00
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the Install button to proceed with the installation.
]]>
Click the Install button to proceed with the installation.
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD3
Previous Version of Firmware:
HPD3
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPD1
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Click the "Install" button to proceed with the installation.]]>
Click the "Install" button to proceed with the installation.]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
From that drive and directory, execute the downloaded file.
Click the "Install" button to proceed with the installation.
]]>
To update the driver using VMware tools:
To update the driver using VMware tools:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To update firmware from VMware ESXi operating system on target server:
Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Remote Online:
Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
To update firmware from VMware ESXi operating system on target server:
chmod +x CPxxxxxx.vmexe (or) chmod +x CPxxxxxx.vmexe64
Additional information to execute VIB file.
Commands required to execute VIB file on ESXi 7.0
Commands required to execute VIB file on ESXi 6. 7 and prior versions.
full path is the temporary directory path where zip file was unpacked CPxxxxxx.zip
]]>Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
Enhancements/New Features:
Problems Fixed:
None
Known Issues:
None
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To install or upgrade the driver type:
Setup is now complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command:
Enterprise Support
For support on Smart Array controllers, visit http://www.hpe.com/support
]]>
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features :
Problems Fixed:
None
Known Issues:
None
These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>These pre-compiled RPM packages may not install or function as expected on a different kernel (e.g. errata kernel). If you are not using a default inbox kernel, you should download the driver source package (i.e. <driver>.src.rpm) and compile a new driver for your target system from the driver source.
To find the location of the driver source RPM, execute the following command for the kernel module driver RPM: localhost> rpm -qpi <kernel module driver name>.rpm
Download README for any additional installation instructions.
]]>Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Remote Online, if the component is supported by SUM but is not yet part of an SPP:
To use HPE Insight Control for vCenter :
To update firmware from VMware ESXi operating system on target server:
]]>
Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Updating firmware by installing the rpm:
Updating firmware without installing the rpm:
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.
To use Smart Update Manager from the Service Pack for ProLiant:
Offline:
Online:
Follow the instructions on the screen.
]]>Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
Release Version and/or Date:
HPG2
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Problems Fixed:
None
Known Issues:
None
Problems Fixed:
None
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
Release Version and/or Date:
HPD5
Last Recommended or Critical Version:
HPD4
Previous Version of Firmware:
HPD4
Firmware Dependency:
None
Enhancements/New Features:
Problems Fixed:
This code corrects a potential data integrity issue related to unaligned write commands.This issue was only found in supplier ongoing lab testing.
Known Issues:
None
To use Smart Update Manager from the Service Pack for ProLiant:
To use Smart Update Manager from the Service Pack for ProLiant:
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None
Release Version and/or Date:
HPK4
Last Recommended or Critical Version:
None
Previous Version of Firmware:
None
Firmware Dependency:
None
Enhancements/New Features:
Added support for Windows 2019.
Problems Fixed:
None
Known Issues:
None