Скачать драйвер для HP ProLiant MicroServer Gen8 iLO 4 Firmware 1.40

Important:
- Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The following issues are resolved in this firmware version:
- Server Auto Power-On might be triggered when iLO is reset through IPMI.
- Firmware updates that use USB Virtual Media might fail due to secure flash image corruption.
- SSH sockets might take 30 seconds to close.
- The GET_OA_INFO command output does not include the OA IPv6 address.
- The iLO 4 SNMP stack might become unresponsive to SNMP requests.
- The file upload section is not displayed on the iLO web interface Firmware page.
- The Integrated Remote Console (IRC) stops working when iLO is busy.
- The .NET Integrated Remote Console (IRC) fails to start in Chrome if a trusted certificate is not installed.
- Kerberos Keytab files cannot be added from the iLO web interface.
- An error occurs if you register for Remote Support with proxy settings, and then you delete the proxy settings.
- Directory settings information is not consistent between the iLO web interface and the scripting interfaces.
- The server shuts down when a user exits the system RBSU during an iLO reset.
- Kerberos Keytab files cannot be added when FIPS mode is enabled.
- A service event is not generated when a hard disk drive fails during boot.
- The Acquire dialog box is displayed when the remote console is started, but there is no active session to acquire.
- The status of a spare drive changes to inactive when the spare drive is in use.
- When the security override switch is enabled, long login names might fail.
- TPM status cannot be viewed by using XML scripts.
- The IPv6 default gateway might be saved as a static default gateway.
- When configured for FIPS mode/AES-DES the key exchange method ‘diffie-hellman group1 sha1’ should not be supported.
- The iLO clock fails to synchronize with NTP when a Primary Time Server is not entered.
- The iLO webserver unexpectedly quits after the NVRAM is cleared.
- The iLO DHCPv6/EBIPA address is not displayed in OA when OA is configured on an IPv6-only network.
- The Backup ROM date is displayed incorrectly on the Diagnostics page in the iLO web interface.
- The IPMI Get Sensor Reading command returns incorrect data for the Inlet Ambient sensor.
- Auto Power-On takes two minutes when the delay is set to 15, 30, 45, or 60 seconds.
- Some Power On Self Test (POST) errors might be truncated in the Integrated Management Log (IML).
- The output of the RIBCL GET_POST_STATE command shows the output for the HOST_POWER command.
- If the Shared Remote Console feature is not licensed, an error message should be displayed when a user clicks the Share button.
- iLO cannot be configured to propagate the NTP or OA time setting to the host.
- An SSH session is not logged out when AES/3DES is enabled or disabled by using the CLI.
- The iLO CLI and web interface have different length requirements for the FQDN.
- There is no warning message in the CLI when the power mode is set to OS control.
- The Login Security Banner does not work consistently between the iLO web interface and iLO scripts.
- The remote console displays multiple CD-ROM drives with the same drive letter.
- The SSH interface might freeze after multiple back-to-back connections.
- An iLO system with no installed certificates reports that the maximum number of certificates is reached.
- The temperature graph in the iLO web interface shows details for only one sensor when multiple sensors have the same coordinates.
- The SNTP settings are not displayed in the iLO web interface after a firmware update.
- An error occurs when the iLO firmware is updated by using the CLI.
- The CPU temperature is reported incorrectly.
- An event is not generated when the default language is changed by using scripts or the CLI.
- An error message is not displayed when an incorrect firmware URL is entered.
- The Integrated Management Log (IML) displays an error when a maintenance note is entered.
- An event is not generated when a power-on error occurs.
- The VLAN tag cannot be configured by using the iLO RBSU.
- The iLO firmware date is displayed incorrectly in the iLO RBSU.
- A warning message does not occur when the Local User Accounts setting is changed to Disabled for an iLO system that does not have a configured directory.
- The power-on delay options are inconsistent between the iLO web interface and the CLI.
- The Intelligent Provisioning version is not displayed on the iLO System Information > Firmware page.
- The Enterprise Secure Key Manager (ESKM) certificate is deleted if no certificate name is entered.
- The CLI labels a mismatched power supply with OK status.
- An event is not generated when a language pack update fails.
- An event is not generated when the Power Regulator settings are modified.
- WINDBG with port number 65535 cannot be enabled from the iLO CLI.
- Duplicate IP addresses are not detected.
- iLO 4 1.20 and later does not send ARP before replying to a ping request. This causes iLO 4 to be unreachable to pings from clients with teamed NICs.
- Solaris 10 and 11 cannot be installed by using Virtual Media
- The SNTP time zone offset is incorrectly applied to the time provided by the OA when c-Class blade servers are inserted into the enclosure or are e-fused.
- When the server serial number is updated in the BIOS, the system board FRU data is not updated.

This version adds support for the following features and enhancements:
- Insight Remote Support Direct Connect configuration is available in iLO 4 1.40 and later.
- iLO 4 1.40 and later supports the HP Enterprise Secure Key Manager ESKM 3.1 and later, which can be used in conjunction with HP Secure Encryption.
- Improved Java Integrated Remote Console (IRC)
- UEFI System Utilities support on the HP ProLiant DL580 Gen8 server.
- iLO Federation Management

NOTE:
- iLO Federation Management is supported on IPv4 and IPv6 networks on the iLO Dedicated Network Port. It is not supported on iLO Shared Network Port.


It is highly recommended to always use the most recent driver version available.

Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.

Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.

Примечание: Ссылка "скачать" может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.