Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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:
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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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, 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, 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <file name>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <file name>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <file name>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <file name>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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:
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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:
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
Install the firmware using one of these options:
Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
Install the firmware using one of these options:
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
https://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:
https://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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, 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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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:
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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:
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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
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:
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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
https://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:
https://www.hpe.com/info/ilo
Select your lights-out product, then support & documents, then manuals.
Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
To update firmware from the Linux operating system on target server:
To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
To use Smart Update Manager on the Firmware Maintenance CD:
Visit the HPE Synergy Hotfixes – Compatibility & Support Guidelines page to determine applicable support.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00114641en_us
Instructions to apply this firmware as a Synergy Hotfix can be found in the HPE Synergy Hotfixes Technical Paper [https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00114984en_us] sections titled:
To update firmware from the Linux operating system on target server:
To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
To use Smart Update Manager on the Firmware Maintenance CD:
iLO 4 User Guide and Lights-Out Scripting Guide can also be found by following the links at:
https://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:
https://www.hpe.com/info/ilo
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:
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:
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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
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:
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
Update the firmware and software in the usual manner.
Verify the RPM signature using the following steps:
Download the HPE GPG 2048-bit Public Key (hpePublicKey2048_key1.pub), which is available from the HPE SDR web site: https://downloads.linux.hpe.com/keys.html
Import the public key while logged in as root by running the following command:
# rpm --import /path_to_the_key/file_name_of_the_key
example # rpm --import /path_to_the_key/26C2B797.pub
Verify the RPM:
Use the rpm --checksig command to validate and verify the digital signature of the signed file. The output from the command indicates the validity of the signature:
# rpm --checksig filename_of_the_rpm
example result # rpm --checksig <filename>.rpm
<filename>.rpm: digests signatures OK
If your file does not pass verification or you do not have the Hewlett Packard Enterprise Company public key installed, you may see an error:
# rpm --checksig sample_file.rpm
sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#s)
In this case then do not install the rpm. This means the file has been modified in some way since being released from Hewlett Packard Enterprise Company.
]]>
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 verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <file name>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <FileName>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the 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.
To verify the HPE SHA256 Authenticode digital signature, do the following steps:
1. Download <filename>.exe to a system running a supported version of Microsoft Windows Server OS. By downloading this file, you are agreeing to the license terms in HPE License Agreement v1.pdf, listed in the 'License' field.
2. Right-click the filename then select Properties
3. When the Properties window displays, click the Digital Signature tab
4. Select the first entry in the Signature List and click the Details button.
5. The signature status will display at the top of the Details dialog.
6. If the signature message states that “This digital signature is OK.”, then the firmware package is authenticated as an HPE package
7. If the message “This digital signature is not OK.” displays, then do the following:
a. Do not deploy the firmware.
b. Download firmware a second time and verify the signature again. If the signature is not OK, then contact HPE Technical Support.
To verify the SHA256 hash value, do the following steps:
1. Use Microsoft Windows CRC/SHA tool to calculate the SHA256 hash value for <filename>.exe.
2. Compare the calculated value with the SHA256 value displayed in the Installation Instruction tab of the HPE Support Center download page.
• If the values match, then the integrity of the downloaded file has been verified.
• If the values do not match, do not deploy the file or its contents.
• Download the file a second time and compare the new hash value.
• If the hash values do not match, then do not deploy the downloaded file and contact HPE Technical Support.
Execute the file <filename>.exe and follow onscreen instructions to finish the installation.
After the driver installaton is complete, please restart the server.
]]>
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:
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.
| cn | ja | ko | tw |
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.
| cn | ja | ko | tw |
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: