• Firmware resolves a data mismanagement issue associated with unaligned sequential write operations.

Problems Fixed for HPG3 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG3 (D):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• Firmware resolves a data mismanagement issue associated with unaligned sequential write operations.

Problems Fixed for HPG3 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG3 (D):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• ファームウェアは、非整列シーケンシャル書き込み操作に関連するデータ管理ミスの問題を解決します。

HPG3 (B)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• Firmware resolves a data mismanagement issue associated with unaligned sequential write operations.

Problems Fixed for HPG3 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

• Snoop Inquiry response spanning multiple scatter/gather elements.

• Snoop Inquiry response spanning multiple scatter/gather elements.

• Increase the driver login retry count to 30.

• Mark Data Integrity Field (DIF) errors from target as re-tryable errors.

• Reduced excessive debug print during 27xx fwdump.

• Avoid crashing on null cred pointer in exit_creds().

• Fixed mbx pointer error in classic fwdump.

• Added check for different type of Register State Change Notification (RSCN).

• Fixed improper fcport_count accounting.

• Corrected supported Fibre Channel (FC) speed for sysfs.

• Corrected supported Fibre Channel (FC) speed for Fabric Device Management Interface (FDMI) / Remote Desktop Protocol (RDP).

• Increase the driver login retry count to 30.

• Mark Data Integrity Field (DIF) errors from target as re-tryable errors.

• Reduced excessive debug print during 27xx fwdump.

• Avoid crashing on null cred pointer in exit_creds().

• Fixed mbx pointer error in classic fwdump.

• Added check for different type of Register State Change Notification (RSCN).

• Fixed improper fcport_count accounting.

• Corrected supported Fibre Channel (FC) speed for sysfs.

• Corrected supported Fibre Channel (FC) speed for Fabric Device Management Interface (FDMI) / Remote Desktop Protocol (RDP).

• This firmware update eliminates a data integrity risk when an unaligned WRITE and VERIFY command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written.

• This firmware update eliminates a data integrity risk when an unaligned WRITE and VERIFY command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written.

この製品は、パケットリストが空になっている間にドライバーが不適切にパケットを待っている場合、ウォッチドッグタイムアウトBSODにより引き起こされる問題を修復します。

このコンポーネントは、現在コンポーネントに含まれるドライバーと一致するHP NC551i Dual Port FlexFabric 10Gb を今後認識しません。

This product corrects an issue which results in a watchdog timeout BSOD when the driver is incorrectly waiting for packets while the packet list is empty.

This component no longer recognizes the HP NC551i Dual Port FlexFabric 10Gb Adapter, which is now consistent with the driver that the component contains.

• このファームウェアは、トラックリフレッシュアルゴリズムが正しく動作しないことによって引き起こされることがありえる回復不能エラーを修正します。

HPG7 (B)に対して修正された問題：

• コンポーネントが、HP Host Bus Adapter H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HP Host Bus Adapter H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• コンポーネントが、HP Smart Array P431の後ろに接続されたドライブのファームウェア更新に失敗します。コンポーネントは、ファームウェア更新が成功したことを報告します。しかし、電源再投入後、ファームウェアバージョンは変更されません。

• This firmware corrects possible unrecovered errors caused by the track refresh algorithm not working properly.

Problems Fixed for HPG7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component fails to update the firmware for drives connected behind an HP Smart Array P431 controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.

• このファームウェアは、トラックリフレッシュアルゴリズムが正しく動作しないことによって引き起こされることがありえる回復不能エラーを修正します。

HPG7 (B)に対して修正された問題：

• コンポーネントが、HP Host Bus Adapter H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HP Host Bus Adapter H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• コンポーネントが、HP Smart Array P431の後ろに接続されたドライブのファームウェア更新に失敗します。コンポーネントは、ファームウェア更新が成功したことを報告します。しかし、電源再投入後、ファームウェアバージョンは変更されません。

• This firmware corrects possible unrecovered errors caused by the track refresh algorithm not working properly.

Problems Fixed for HPG7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component fails to update the firmware for drives connected behind an HP Smart Array P431 controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where systems configured with a Honeywell LCNP4 card installed may stop responding during system boot.

Addressed an issue where the system may become unresponsive during system boot when an optional HPE Dual 8GB MicroSD USB device is installed with firmware version 202. This issue does not impact servers configured with an HPE Dual 8GB MicroSD USB device using revision of firmware 212 or later.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where systems configured with a Honeywell LCNP4 card installed may stop responding during system boot.

Addressed an issue where the system may become unresponsive during system boot when an optional HPE Dual 8GB MicroSD USB device is installed with firmware version 202. This issue does not impact servers configured with an HPE Dual 8GB MicroSD USB device using revision of firmware 212 or later.

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

• このファームウェアには、バッファー読み取りを通してのデバッグデータ回収など低水準メンテナンスの修正がいくつか含まれます。この修正には特殊なテスト環境で観測されたイベントが記載されており、顧客の使用は想定されていません。

• This firmware contains several low level maintenance fixes including debug data retrieval through read buffer.  The fixes addressed events observed in a specialized lab testing environment, and are not expected to be experienced in customer use case scenarios.

• このファームウェアには、バッファー読み取りを通してのデバッグデータ回収など低水準メンテナンスの修正がいくつか含まれます。この修正には特殊なテスト環境で観測されたイベントが記載されており、顧客の使用は想定されていません。

• This firmware contains several low level maintenance fixes including debug data retrieval through read buffer.  The fixes addressed events observed in a specialized lab testing environment, and are not expected to be experienced in customer use case scenarios.

• AMSは、より多くの非distroベンダー向けのRPMを記載するようになりました
• CPQNICiflogmapphysicaladアダプターは、ループバックインターフェイス向けにNullになっています
• CPQNICiflogadapterokcountは、リンクがない場合はゼロと等しくなります
• 10個以上のIPv6アドレスがインターフェイス上で構成されている場合のsegfaultを修正しました。

• AMS now lists RPMs for more non-distro vendors
• CPQNICiflogmapphysicaladapters is now null for Loopback Interfaces
• CPQNICiflogadapterokcount equals zero when there is no link
• Fixed a segfault when more than 10 IPv6 addresses are configured on an interface.

• This firmware corrects a potential issue where the data in the reserved tracks is not properly updated, eliminating the risk of a drive not finishing the boot process on power up.
• Other maintenance fixes and updates are also included with the new firmware.

• This firmware corrects a potential issue where the data in the reserved tracks is not properly updated, eliminating the risk of a drive not finishing the boot process on power up.
• Other maintenance fixes and updates are also included with the new firmware.

• This firmware corrects a potential issue where the data in the reserved tracks is not properly updated, eliminating the risk of a drive not finishing the boot process on power up.
• Other maintenance fixes and updates are also included with the new firmware.

• This firmware corrects a potential issue where the data in the reserved tracks is not properly updated, eliminating the risk of a drive not finishing the boot process on power up.
• Other maintenance fixes and updates are also included with the new firmware.

This product addresses an issue where adapters are not reporting the correct temperature in the Integrated Lights Out (iLO) webpage.

This product addresses an issue where the value set for Maximum Transmission Unit (MTU) setting wasn't preserved and instead gets reverted back to default value on system reboot.

This product addresses an issue where adapters are not reporting the correct temperature in the Integrated Lights Out (iLO) webpage.

This product addresses an issue where the value set for Maximum Transmission Unit (MTU) setting wasn't preserved and instead gets reverted back to default value on system reboot.

この製品は、ターゲットが16文字の複数のChallenge Handshake Authentication Protocol (CHAP)を用いて構成されている場合、iSCSIターゲットへの起動に失敗するという問題を修正します。

この製品は、異なるスロットおよびシステムに移動されたアダプターが‘Legacy BIOS Mode’で起動する場合、ネットワークアダプターのコンフィギュレーション設定がデフォルトにリセットされないという問題に対処します。

この製品は、単一のインターコネクトモジュール（ICM)がエンクロージャー内にインストールされ、論理インターコネクトグループ（LIG)の設定に使用されている場合に、システムのパワーオンセルフテスト(POST)の期間が延長されるという問題を修正します。

この製品は、HPE Synergy 3820C 10/20Gb Converged Network Adapterの設定がシステムリセット後にデフォルトの値に戻るという問題に対処します。

この製品は、複数のプラットフォームリブートにわたり、断続的にiSCSI ターゲットに失敗するという問題に対処します。

この製品は、OneViewがダウンリンクポートの状態をOSで使用不可能なネットワークアダプターに”リンク済み”と表示する問題に対処します。

この製品は、”segfault”エラーによりファームウェアのアップデートに失敗するという問題に対処します。

This product addresses an issue booting to an iSCSI target fails when the target is configured with a sixteen character long mutual Challenge Handshake Authentication Protocol (CHAP) secret.

This product addresses an issue where a network adapter’s configuration settings are not reset to defaults when the adapter is moved to a different slot and the system is booted in ‘Legacy BIOS Mode’.

This product addresses an issue where the system’s power-on self-test (POST) duration is extended when a single interconnect module (ICM) is installed in the enclosure and used to configure the logical interconnect group (LIG).

This product addresses an issue where the configuration settings of the HPE Synergy 3820C 10/20Gb Converged Network Adapter revert to the default values after a system restart.

This product addresses an issue where booting to an iSCSI target fails intermittently across multiple platform reboots.

This product addresses an issue where OneView displays the downlink port state as “Linked” for a network adapter that is disabled in the OS.

This product addresses an issue where a firmware update fails with a "segfault" error.

• Under rarely occurring conditions where a host error occurred during a write with 4K unaligned sectors, the write operation might result in stale data. Firmware HPx4 prevents the possibility of stale data occurring under these conditions.

Problems Fixed for HPG4 (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• Under rarely occurring conditions where a host error occurred during a write with 4K unaligned sectors, the write operation might result in stale data. Firmware HPx4 prevents the possibility of stale data occurring under these conditions.

Problems Fixed for HPG4 (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• 4Kのアラインされていないセクターへの書き込みの間にホストエラーが発生するというまれに起こる状況で、書き込み操作が古いデータとなることがあります。 ファームウェアHPx4は、このような状況で起発生する古いデータの可能性を防止します。

• Under rarely occurring conditions where a host error occurred during a write with 4K unaligned sectors, the write operation might result in stale data. Firmware HPx4 prevents the possibility of stale data occurring under these conditions.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the Embedded UEFI Shell restclient utility would not properly configure attributes for Network TLS (HTTPS) support.

Addressed an issue where the UEFI or Legacy Boot Order could still be modified after an incorrect Administrator Password was entered in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the embedded AHCI SATA controller would not show up properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no drives were attached to the controller.

Addressed an issue where saving a configuration setting from an optional device's configuration page in the System Utilities menu would not be saved properly.  This issue was seen with one Network Adapter card.

Addressed an issue where the system ROM would not correctly report a configuration error for the HPE Smart Battery storage subsystem when more devices were installed than could be supported by the installed battery.

Addressed an issue where a platform configured with direct attached NVMe hard drives may report the incorrect location (box and bay location) from the System Utilities page.

Addressed an issue where the System Utilities menu may not show the proper name for an optional PCIe Adapter.

Addressed an issue where the Integrated Lights Out (iLO) remote Console Keyboard and Mouse may not function properly when the system is configured for Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot Mode.

Addressed an issue where the HPE Jitter Performance feature settings could not be properly modified from the Integrated Lights Out web interface.

Addressed an issue where the system may report that the HPE Smart Battery is charging when in fact the battery has failed. It is recommended to flash to this system ROM if a system is reporting Smart Battery issues.

Addressed an issue where the Trusted Platform Module (TPM) option for TPM Visibility could not be configured through the RESTful API.

Addressed an issue where the system may become unresponsive when repeatedly typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.  This issue does not impact systems in UEFI Boot Mode or a system once the system boots into an operating system.

Addressed an issue where certain third party PCIe adapters, such as a Dialogic adapter, would not function properly due to the PCIe Maximum Payload size being incorrectly programmed.

Addressed an issue where certain NVMe devices may not be detected when the x16 slot PCIe Riser and three slot x8 riser are present in the server.

Addressed an issue where a Network Boot option would still show an entry  in the Legacy Boot Order when Network Boot was disabled on the device from the BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not affect systems configured for UEFI Boot Mode.

Addressed an issue where the system may become unresponsive when using the TAB key in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the BIOS would not properly identify and halt a system from booting with an invalid DIMM configuration.

Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy Efficient Turbo setting was "backwards".  When the configuration setting was set to enabled, the feature would actually be Disabled.  When configured to Disabled, the feature would actually be enabled.

Addressed an issue where the server might lockup and display a red screen when trying to repair a failed RAID volume off of an S100i SW RAID controller.

Addressed an issue where the RESTful API may report that BIOS settings were not applied properly even when they are properly configured.

Addressed an issue where the system may become unresponsive during boot after a warm reset, typically seen with a blank screen, when a Trusted Platform Module (TPM) is installed.  If reboot issues are seen with systems containing an optional TPM, it is highly recommended the System ROM be enabled to this revision or later.

Addressed an extremely rare issue where the system may incorrectly report a 413 Innovation Engine Authentication Error on a server reboot.

Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo disable functionality.

Removed the Platform Configuration (RBSU) Option to enable or disable the Embedded Diagnostics.  Embedded Diagnostics is not supported on this server and the menu option should not have been available and was not functional.

Removed Embedded Diagnostics support from System Utilities.

Removed support for the chipset firmware based Trusted Platform Module (TPM) known as Intel Platform Trust Technology (Intel PTT). This feature is no longer supported due to stability issues and Intel recommends not supporting this feature. Users should instead install a discrete HPE TPM option for this support.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the Embedded UEFI Shell restclient utility would not properly configure attributes for Network TLS (HTTPS) support.

Addressed an issue where the UEFI or Legacy Boot Order could still be modified after an incorrect Administrator Password was entered in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the embedded AHCI SATA controller would not show up properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no drives were attached to the controller.

Addressed an issue where saving a configuration setting from an optional device's configuration page in the System Utilities menu would not be saved properly.  This issue was seen with one Network Adapter card.

Addressed an issue where the system ROM would not correctly report a configuration error for the HPE Smart Battery storage subsystem when more devices were installed than could be supported by the installed battery.

Addressed an issue where a platform configured with direct attached NVMe hard drives may report the incorrect location (box and bay location) from the System Utilities page.

Addressed an issue where the System Utilities menu may not show the proper name for an optional PCIe Adapter.

Addressed an issue where the Integrated Lights Out (iLO) remote Console Keyboard and Mouse may not function properly when the system is configured for Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot Mode.

Addressed an issue where the HPE Jitter Performance feature settings could not be properly modified from the Integrated Lights Out web interface.

Addressed an issue where the system may report that the HPE Smart Battery is charging when in fact the battery has failed. It is recommended to flash to this system ROM if a system is reporting Smart Battery issues.

Addressed an issue where the Trusted Platform Module (TPM) option for TPM Visibility could not be configured through the RESTful API.

Addressed an issue where the system may become unresponsive when repeatedly typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.  This issue does not impact systems in UEFI Boot Mode or a system once the system boots into an operating system.

Addressed an issue where certain third party PCIe adapters, such as a Dialogic adapter, would not function properly due to the PCIe Maximum Payload size being incorrectly programmed.

Addressed an issue where certain NVMe devices may not be detected when the x16 slot PCIe Riser and three slot x8 riser are present in the server.

Addressed an issue where a Network Boot option would still show an entry  in the Legacy Boot Order when Network Boot was disabled on the device from the BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not affect systems configured for UEFI Boot Mode.

Addressed an issue where the system may become unresponsive when using the TAB key in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the BIOS would not properly identify and halt a system from booting with an invalid DIMM configuration.

Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy Efficient Turbo setting was "backwards".  When the configuration setting was set to enabled, the feature would actually be Disabled.  When configured to Disabled, the feature would actually be enabled.

Addressed an issue where the server might lockup and display a red screen when trying to repair a failed RAID volume off of an S100i SW RAID controller.

Addressed an issue where the RESTful API may report that BIOS settings were not applied properly even when they are properly configured.

Addressed an issue where the system may become unresponsive during boot after a warm reset, typically seen with a blank screen, when a Trusted Platform Module (TPM) is installed.  If reboot issues are seen with systems containing an optional TPM, it is highly recommended the System ROM be enabled to this revision or later.

Addressed an extremely rare issue where the system may incorrectly report a 413 Innovation Engine Authentication Error on a server reboot.

Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo disable functionality.

Removed the Platform Configuration (RBSU) Option to enable or disable the Embedded Diagnostics.  Embedded Diagnostics is not supported on this server and the menu option should not have been available and was not functional.

Removed Embedded Diagnostics support from System Utilities.

Removed support for the chipset firmware based Trusted Platform Module (TPM) known as Intel Platform Trust Technology (Intel PTT). This feature is no longer supported due to stability issues and Intel recommends not supporting this feature. Users should instead install a discrete HPE TPM option for this support.

Known Issues:

None

• HPG6 firmware improves drive reliability where disk drives are exposed to long periods of host inactivity which exceed 1 second.

• HPG6 firmware improves drive reliability where disk drives are exposed to long periods of host inactivity which exceed 1 second.

• このファームウェアは、HDDが、1秒を超える長時間ホストが作動していない状態にさらされる場合、HDDの信頼性を改善します。バージョンHPG4以前のHDDのファームウェアを使用している場合、HDDが応答しなくなることがあります。このファームウェアは、また、記録された後、修理されたセクターのステータスが誤って再割り当てされることを防ぐための変更が含まれます。

• This firmware improves HDD reliability when HDDs are exposed to long periods of host inactivity that exceed 1 second. HDDs may become unresponsive when using HDD firmware prior to version HPG4.  This firmware also contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

この製品は、ターゲットが16文字の複数のChallenge Handshake Authentication Protocol (CHAP)を用いて構成されている場合、iSCSIターゲットへの起動に失敗するという問題を修正します。

この製品は、異なるスロットおよびシステムに移動されたアダプターが‘Legacy BIOS Mode’で起動する場合、ネットワークアダプターのコンフィギュレーション設定がデフォルトにリセットされないという問題に対処します。

この製品は、単一のインターコネクトモジュール（ICM)がエンクロージャー内にインストールされ、論理インターコネクトグループ（LIG)の設定に使用されている場合に、システムのパワーオンセルフテスト(POST)の期間が延長されるという問題を修正します。

この製品は、NICパーティショニング（NPAR）が有効になっている場合、VMWare上のハイパーバイザーをロードすると、Purple Screen of Death (PSOD)が発生する問題を修正します。

この製品は、HPE Synergy 3820C 10/20Gb Converged Network Adapterの設定がシステムリセット後にデフォルトの値に戻るという問題に対処します。

この製品は、複数のプラットフォームリブートにわたり、断続的にiSCSI ターゲットに失敗するという問題に対処します。

この製品は、OneViewがダウンリンクポートの状態をOSで使用不可能なネットワークアダプターに”リンク済み”と表示する問題に対処します。

この製品は、”segfault”エラーによりファームウェアのアップデートに失敗するという問題に対処します。

This product addresses an issue booting to an iSCSI target fails when the target is configured with a sixteen character long mutual Challenge Handshake Authentication Protocol (CHAP) secret.

This product addresses an issue where a network adapter’s configuration settings are not reset to defaults when the adapter is moved to a different slot and the system is booted in ‘Legacy BIOS Mode’.

This product addresses an issue where the system’s power-on self-test (POST) duration is extended when a single interconnect module (ICM) is installed in the enclosure and used to configure the logical interconnect group (LIG).

This product addresses an issue where loading hypervisor on VMware causes pink screen of death (PSOD) when NIC Partitioning (NPAR) is enabled.

This product addresses an issue where the configuration settings of the HPE Synergy 3820C 10/20Gb Converged Network Adapter revert to the default values after a system restart.

This product addresses an issue where booting to an iSCSI target fails intermittently across multiple platform reboots.

This product addresses an issue where OneView displays the downlink port state as “Linked” for a network adapter that is disabled in the OS.

This product addresses an issue where a firmware update fails with a "segfault" error.

• Reliability enhancement for applications that write data to a narrow range of tracks.

• Reliability enhancement for applications that write data to a narrow range of tracks.

• HDDの長期使用後に電源の再投入後、ごくまれにデータを含むディスクの領域にドライブのヘッドが接触して、データの損失や機械的損傷を引き起こすことがあります。ファームウェア バージョンHPGDは、この状態を防ぐことができます。

HPGD (C)に対して修正された問題：

• Trusted Platform Module (TPM)が有効なサーバー上で、コンポーネントは/tpmbypassスイッチを使用している場合、ドライブファームウェアのフラッシュに失敗します。

HPGD (D)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• 長さ40文字を超える完全修飾ドメイン名を持つコンピューターで展開したとき、コンポーネントが例外エラーを引き起こします。

• After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPGD prevents this condition from occurring.

Problems Fixed for HPGD(C):

• The component would fail to flash drive firmware on a server with a Trusted Platform Module (TPM) enabled when using the /tpmbypass switch.

Problems Fixed for HPGD (D):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component would cause an exception error when deployed on a computer with a fully qualified domain name greater than 40 characters in length.

• HDDの長期使用後に電源の再投入後、ごくまれにデータを含むディスクの領域にドライブのヘッドが接触して、データの損失や機械的損傷を引き起こすことがあります。ファームウェア バージョンHPGDは、この状態を防ぐことができます。

HPGD (C)に対して修正された問題：

• Trusted Platform Module (TPM)が有効なサーバー上で、コンポーネントは/tpmbypassスイッチを使用している場合、ドライブファームウェアのフラッシュに失敗します。

HPGD (D)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• 長さ40文字を超える完全修飾ドメイン名を持つコンピューターで展開したとき、コンポーネントが例外エラーを引き起こします。

• After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPGD prevents this condition from occurring.

Problems Fixed for HPGD(C):

• The component would fail to flash drive firmware on a server with a Trusted Platform Module (TPM) enabled when using the /tpmbypass switch.

Problems Fixed for HPGD (D):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component would cause an exception error when deployed on a computer with a fully qualified domain name greater than 40 characters in length.

• HPS4 firmware release resolved a firmware timing issue which occurred during drive long self-test and resulted in a timeout condition that caused the drive to become unrecognized by the system.

Problems Fixed for HPS4 (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• HPS4 firmware release resolved a firmware timing issue which occurred during drive long self-test and resulted in a timeout condition that caused the drive to become unrecognized by the system.

Problems Fixed for HPS4 (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• HPS4 のファームウエアリリースは、ドライブの長いセルフテスト中にドライブがシステムにより認識されなくするタイムアウト状態を起こすというファームウエアのタイミングの問題を解決しました。

• HPS4 firmware release resolved a firmware timing issue which occurred during drive long self-test and resulted in a timeout condition that caused the drive to become unrecognized by the system.

• NVIDIA Tesla M2090 GPU で構成されたシステム上でのコンポーネントのインストール中、修正不能 PCIe エラーが発生する可能性があります。

• During component installation on a system configured with NVIDIA Tesla M2090 GPU, an uncorrectable PCIe error might occur.

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。 

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset. 

Known Issues:

• Enclosure in Unexpected status: Non-critical after restoring the Encl ID.

• Enclosure in Unexpected status: Non-critical after restoring the Encl ID.

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would not achieve maximum performance results when the BIOS/Platform Configuration (RBSU) Sub-NUMA Clustering option is enabled.  This option is not enabled by default.

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM.  This issue does NOT occur with the Version 1.00 System ROM.  Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor.  If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would not achieve maximum performance results when the BIOS/Platform Configuration (RBSU) Sub-NUMA Clustering option is enabled.  This option is not enabled by default.

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM.  This issue does NOT occur with the Version 1.00 System ROM.  Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor.  If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

None

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

• Network bonding changes now generate traps
• cpqSeTotalMemMB now shows correct value

• Network bonding changes now generate traps
• cpqSeTotalMemMB now shows correct value

• ネットワークボンディングの変更がトラップを生成しています。
• cpqSeTotalMemMBが正しい値を表示しています

• Network bonding changes now generate traps
• cpqSeTotalMemMB now shows correct value

• Remote Desktop Protocol (RDP) print out of speed capabilities.

• Fibre Channel (FC) driver not completing w32 driver install process with the Fibre Channel (FC ) storage connected.

• Windows unexpected termination on upgrading/downgrading Windows driver.

• Windows Memory Dump generated by Multipath Input/output (MPIO) configuration.

• Remote Desktop Protocol (RDP) print out of speed capabilities.

• Fibre Channel (FC) driver not completing w32 driver install process with the Fibre Channel (FC ) storage connected.

• Windows unexpected termination on upgrading/downgrading Windows driver.

• Windows Memory Dump generated by Multipath Input/output (MPIO) configuration.

• Added logic to check fabric priority bit in nvram for 16Gb & 32Gb host bus adapters

• Fixed synchronization for systems with large number of CPUs running IO on a Hyper-v VM and local server to prevent a Firmware dump

• Added fabric priority detection per target device to improve performance on tape devices

• Added login retries to Name Server, postponing processing Register State Change Notification (RSCN) if Name Server is logged out to prevent Path Loss issue with Brocade switch FOS upgrade

• Fixed 16G host bus adapter incorrectly reporting that it supports 32Gb

• Enabled Fabric Login (FLOGI) retry in firmware to better handle longer Fabric Login (FLOGI) link initialization (link up)

• Added logic to check fabric priority bit in nvram for 16Gb & 32Gb host bus adapters

• Fixed synchronization for systems with large number of CPUs running IO on a Hyper-v VM and local server to prevent a Firmware dump

• Added fabric priority detection per target device to improve performance on tape devices

• Added login retries to Name Server, postponing processing Register State Change Notification (RSCN) if Name Server is logged out to prevent Path Loss issue with Brocade switch FOS upgrade

• Fixed 16G host bus adapter incorrectly reporting that it supports 32Gb

• Enabled Fabric Login (FLOGI) retry in firmware to better handle longer Fabric Login (FLOGI) link initialization (link up)

12GB SAS HDDがエンクロージャー内に搭載されている場合、ディスクディスカバリをサポートするために、SAS エキスパンダーの設定を変更しました。 

Changed the settings in the SAS Expander to support disk discovery when 12Gb SAS HDDs are installed in the enclosure 

• もしmlx4_ibモジュールがロードされなかったとき、タイムアウト後の "ethtool" セルフテストが割り込みテストでしばしば失敗していました。
• まれな状況で、非同期のイベントハンドラーから呼ばれたmlx4_en_get_drvinfo() によって、システムリブートの間にカーネルパニックが発生することがありました。
• VF netdevsが開いている状態でSR-IOVを無効にしようとすると、オペレーションが失敗しました。

以下の問題が、バージョン3.3 (A)　で修正されました。

• インターフェースの名前を変更する際の "mlnx_interface_mgr.sh" スクリプトとudevフロー間の競合状態

以下の問題点がバージョン3.3で修正されました。

• SLES12 SP1でのドライバーロードの問題を修正するために互換性 ocrdma.koモジュールを追加しました。
• /sys/class/infiniband//ports// で発見されたエラーカウンターが、ConnectX-4 アダプターカード内で正しく機能しませんでした。
• TXキューカウンター形式を：xq_[tc]*[ring/channel]に変更しました。
• RDMA Sniffer機能の問題を修正しました。
• 仮想機能がethtoolファシリティで使用されている場合、エラーメッセージがログに出力されました。
• 物理リンクのダウン時、同じポート上での物理機能から、任意の仮想機能へのトラフィックが欠落していました。

バージョン3.2 (A) での修正：

• "infiniband support"グループにOS配布のRPMがすでにインストールされている場合、RoCEユーザースペースのライブラリーであるRPM "mlnx-ofa_kernel"でインストールに失敗しました。
• 以前のバージョンのMLNX-ENドライバーがすでにインストールされている場合、RoCEドライバーアップグレードが正しく動作しません。これは、Mellanox Ethernet ポートが動作しない原因となります。

バージョン3.2での修正：

• もっとも近い NUMA ノードを、受信側スケーリング用のデフォルトに設定します。
• GROが有効になったときに、プロキシVXLANインターフェイスが正しく処理されないARP要求パケット。

• "ethtool" self test used to fail on interrupt test after timeout if mlx4_ib module was not loaded.
• On rare occassions, kernel panic occured during system reboot caused by mlx4_en_get_drvinfo() called from asynchronous event handler.
• When attempting to disable SR-IOV while there are any VF netdevs open, the operation failed to succeed.

The following issues have been fixed in version 3.3(A):

• Race condition between "mlnx_interface_mgr.sh" script and udev flow, when renaming interfaces.

The following issues have been fixed in version 3.3:

• Added compatible "ocrdma.ko" module to fix driver loading issue with SLES12 SP1.
• The error counters found under /sys/class/infiniband/<mlx5_dev>/ports/<port>/ did not function properly in ConnectX-4 adapter cards.
• Changed TX queue counter format to: xq_[tc]*[ring/channel].
• RDMA sniffer functionality issues.
• Error messages were logged to dmesg when a Virtual Function used ethtool facilities.
• Traffic from Physical Function to any Virtual Function on the same port was dropped when the physical link was down.

Fixes in version 3.2 (A):

• The RoCE user-space library RPM "mlnx-ofa_kernel" failed to install when OS distribution RPMs in "infiniband support" group were already installed.
• The RoCE driver upgrade didnt work properly when a previous version of MLNX-EN driver was already installed. This resulted in Mellanox Ethernet ports not coming up.

Fixes in version 3.2:

• Set closest NUMA node as the default for Receive Side Scaling.
• ARP request packets destined for a proxy VXLAN interface were not handled correctly when GRO was enabled.

• Under rarely occurring conditions where a host error occurred during a write with 4K unaligned sectors, the write operation might result in stale data. Firmware HPD3 prevents the possibility of stale data occurring under these conditions.

• Under rarely occurring conditions where a host error occurred during a write with 4K unaligned sectors, the write operation might result in stale data. Firmware HPD3 prevents the possibility of stale data occurring under these conditions.

• このファームウェアは、HDDが、1秒を超える長時間ホストが作動していない状態にさらされる場合、HDDの信頼性を改善します。バージョンHPD2以前のHDDのファームウェアを使用している場合、HDDが応答しなくなることがあります。このファームウェアは、また、記録された後、修理されたセクターのステータスが誤って再割り当てされることを防ぐための変更が含まれます。

• This firmware improves HDD reliability when HDDs are exposed to long periods of host inactivity that exceed 1 second. HDDs may become unresponsive when using HDD firmware prior to version HPD2.  This firmware also contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

• このファームウェアには、バッファー読み取りを通してのデバッグデータ回収など低水準メンテナンスの修正がいくつか含まれます。この修正には特殊なテスト環境で観測されたイベントが記載されており、顧客の使用は想定されていません。

• This firmware contains several low level maintenance fixes including debug data retrieval through read buffer.  The fixes addressed events observed in a specialized lab testing environment, and are not expected to be experienced in customer use case scenarios.

• このファームウェアには、バッファー読み取りを通してのデバッグデータ回収など低水準メンテナンスの修正がいくつか含まれます。この修正には特殊なテスト環境で観測されたイベントが記載されており、顧客の使用は想定されていません。

• This firmware contains several low level maintenance fixes including debug data retrieval through read buffer.  The fixes addressed events observed in a specialized lab testing environment, and are not expected to be experienced in customer use case scenarios.

• トラックの狭い範囲にデータを書き込むアプリケーションの信頼性の向上。

• Reliability enhancement for applications that write data to a narrow range of tracks.

• トラックの狭い範囲にデータを書き込むアプリケーションの信頼性の向上。

• Reliability enhancement for applications that write data to a narrow range of tracks.

• Fixes a data integrity risk which could occur during 4k or greater unaligned writes while the device incurs a smart trip event. During these conditions there is a potential for data intended to be written directly to disk to fail to be written.
• Eliminates a data integrity risk when an unaligned Write and Verify command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written. 

• Fixes a data integrity risk which could occur during 4k or greater unaligned writes while the device incurs a smart trip event. During these conditions there is a potential for data intended to be written directly to disk to fail to be written.
• Eliminates a data integrity risk when an unaligned Write and Verify command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written. 

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

主要な NIC MACノードが示す場所は、エンクロージャーシャーシマネージャーに適切に報告されない場合があるという問題を処理しました。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the nodes primary NIC MAC address may not be properly reported to the enclosure chassis manager.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

ファームウェアの依存関係：

修正された問題点：

"Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000000, Bank 0x00000007, Status 0xEC0000C0'00010090, Address 0x00000000'02CD9B40, Misc 0x00000001'4042C200)""Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000000, Bank 0x00000003, Status 0xF2000000'00300151, Address 0x00000000'00000000, Misc 0x00000000'00000000)"

既知の問題点：

Firmware Dependencies:

Problems Fixed:

"Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000000, Bank 0x00000007, Status 0xEC0000C0'00010090, Address 0x00000000'02CD9B40, Misc 0x00000001'4042C200)""Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000000, Bank 0x00000003, Status 0xF2000000'00300151, Address 0x00000000'00000000, Misc 0x00000000'00000000)"

Known Issues:

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

バージョン100.18.2.64(A)に実施された変更:

• Service Pack for ProLiantをバージョン2017.07.0.へ
  注：システムが以前にドライバーバージョン100.18.2.64にアップデートされている場合、100.18.2.64(A)にアップデートする必要はありません。

バージョン100.18.2.64で解決した問題：

• 6/8TiBドライブでハングするサーバー
• SasGetDeviceAddressコマンドと関連するドライバー

Change implemented in version 100.18.2.64(A):

• Updated to support Service Pack for ProLiant version 2017.07.0.
  Note: If driver version 100.18.2.64 was previously installed, then it is not necessary to upgrade to version 100.18.2.64(A).

Issues resolved in version 100.18.2.64:

• Server hangs with 6/8TiB drives.
• Driver hangs with SasGetDeviceAddress command.

• このファームウェアは、HDDが、1秒を超える長時間のホスト非アクティビティ状態に陥ったときに、HDDの信頼性を改善します。バージョンHPG5以前のHDDのファームウェアを使用している場合、HDDが応答しなくなることがあります。  このファームウェアは、記録した修復されたセクターのステータスを誤って再割り当てされることを防ぐための変更も含みます。

• This firmware improves HDD reliability when HDDs are exposed to long periods of host inactivity that exceed 1 second. HDDs may become unresponsive when using HDD firmware prior to version HPG5.  This firmware also contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

• HDDパワーサイクルの後、Background Media Scan (BGMS)ポインターが2つめのBGMSルーチンを呼びだしLBA 0から開始し、2つめのBGMSが完了するまでパフォーマンスに影響を及ぼす問題。
• 開始後またはスタンバイから戻った後にHDDに入力する際、Non Volatile Cacheの問題が起こる可能性。

HPG3 (B)に対して修正された問題：

• コンポーネントが、HP Host Bus Adapter H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HP Host Bus Adapter H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• コンポーネントが、HP Smart Array P431の後ろに接続されたドライブのファームウェア更新に失敗します。コンポーネントは、ファームウェア更新が成功したことを報告します。しかし、電源再投入後、ファームウェアバージョンは変更されません。

• After HDD power cycle, the Background Media Scan (BGMS) pointer would invoke a second BGMS routine starting at LBA 0, which could affect  performance until the second BGMS has completed.
• When writing to the HDD after it entered or returned from a standby state, the potential existed for a Non Volatile Cache issue to occur..

Problems Fixed for HPG3 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component fails to update the firmware for drives connected behind an HP Smart Array P431 controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.

• Enclosure in Unexpected status: Non-critical after restoring the Encl ID.

• Enclosure in Unexpected status: Non-critical after restoring the Encl ID.

• This firmware implements the Firmware Security Log Page.

• This firmware implements the Firmware Security Log Page.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

• アラインされていない4K読み込みへのアクセスおよびデータ読み込みが顧客データの前にゼロ内容を持つとき、誤ったデータ読み込みが発生することがあります。(この問題の詳しい情報は、カスタマーアドバイザリc04650586から入手できます)

HPD1 (B)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• Incorrect data reads might occur when accessing unaligned 4k reads and the data read has zero content preceding customer data. (Additional information can be obtained for this issue in Customer Advisory c04650586)

Problems Fixed for HPD1 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

• This firmware implements a feature which performs a random seek after 100ms of host inactivity.

Problems Fixed for HPGI (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• This firmware implements a feature which performs a random seek after 100ms of host inactivity.

Problems Fixed for HPGI (B):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• HPGH ファームウェアは、ディスクドライブが1秒を超える長期間、ホスト非作動期間になった場合のドライブの信頼性を改善します。 その結果、ハードディスクは反応しなくなることがあります。

• HPGH firmware improves drive reliability where disk drives are exposed to long periods of host inactivity which exceed 1 second. As a result, hard disk drives may become unresponsive.

Fixed the following:

• Link down encountered during high traffic on 81E, 82E, 84E, LPe1205a

UEFI:

• Boot Device Order menu not displaying targets on HPE servers

16G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

16G/32G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

Fixed the following:

• Link down encountered during high traffic on 81E, 82E, 84E, LPe1205a

UEFI:

• Boot Device Order menu not displaying targets on HPE servers

16G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

16G/32G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

•     HPE Synergy 3530C 16Gbファイバーチャネルホストバスアダプター吸気温度だけが表示されていました。

•     HPE Synergy 3530C 16Gb Fibre Channel Host Bus Adapter inlet temperatures were only being displayed

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

• This firmware implements the Firmware Security Log Page.

• This firmware contains a change to prevent occasional command completion times in the 4-5 second window when command is received just as the drive is transitioning from active to Idle A.

• This firmware implements the Firmware Security Log Page.

• This firmware contains a change to prevent occasional command completion times in the 4-5 second window when command is received just as the drive is transitioning from active to Idle A.

• Fixes a data integrity risk which could occur during 4k or greater unaligned writes while the device incurs a smart trip event. During these conditions there is a potential for data intended to be written directly to disk to fail to be written.
• Eliminates a data integrity risk when an unaligned Write and Verify command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written. 

• Fixes a data integrity risk which could occur during 4k or greater unaligned writes while the device incurs a smart trip event. During these conditions there is a potential for data intended to be written directly to disk to fail to be written.
• Eliminates a data integrity risk when an unaligned Write and Verify command is sent to a bad sector. During these conditions there is a potential for data intended to be written to disk to fail to be written. 

この製品は、Active Haelth System (AHS) ダッシュボード上のNICファームウェアバージョンおよびシリアル番号の表示に不一致がある問題に対処しています。

This product addresses an issue where there is a discrepancy in the display of the NIC firmware version and serial number on the Active Health System (AHS) Dashboard.

• Service Pack for ProLiantをバージョン2017.07.0.へ
  注：システムが以前にコンポーネントバージョン2016.11.18にアップデートされている場合、2016.11.18(A)にアップデートする必要はありません。

バージョン2016.11.18で解決した問題:

• HPE ProLiantサーバーでは、VMware vSphere 6.0で以前にホットリムーブされたRAID 0ディスクを再挿入して再度アクティブ化すると、ボリュームがオンラインまたは準備完了の状態に戻らないことがあります。HPE Smartアレイ (HPSA) ドライバーは、アンプラグされたボリュームのオフライン状態がドライバーで認識されるのを防ぎ、ボリュームがSmart Storage Administrator (SSA) ユーティリティで物理的に再挿入されて再度アクティブ化されると、ボリュームがVMware vSAN環境でオフラインのままになります。

• Updated to support Service Pack for ProLiant version 2017.07.0.
  Note: If component version 2016.11.18 was previously installed, then it is not necessary to upgrade to version 2016.11.18(A).

Issues resolved in version 2016.11.18:

• On HPE ProLiant servers, reinserting and reactivating a previously hot-removed RAID 0 disk may cause the volume to fail to return to an online or ready state in VMware vSphere 6.0. The HPE Smart Array (HPSA) driver prevents the unplugged volume’s offline state from being recognized by driver and when the volume is physically reinserted and reactivated with the Smart Storage Administrator (SSA) utility, the volume status remains as offline in a VMware vSAN environment.

• ドライブがコントローラーへ06/29/04 (自主リセット)を報告した、ATI (Adjacent Track Interference)緩和時の自主リセット問題。コントローラーはドライブとのリンクを再確立し、コマンドを再送信します。
• ドライブパフォーマンスの劣化をもたらすサーボの計算ミス。

HPD3 (B)に対して修正された問題：

• Trusted Platform Module (TPM)が有効なサーバー上で、コンポーネントは/tpmbypassスイッチを使用している場合、ドライブファームウェアのフラッシュに失敗します。

HPD3 (C)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• 長さ40文字を超える完全修飾ドメイン名を持つコンピューターで展開したとき、コンポーネントが例外エラーを引き起こします。

• Self-initiated reset during ATI (Adjacent Track Interference) mitigation issue, where the drive reported a 06/29/04 (Self-Initiated Reset) to the controller.  Then the controller would re-establish link with the drive and resend the command.
• Servo miscalculations that resulted in degraded drive performance.

Problems Fixed for HPD3 (B):

• The component would fail to flash drive firmware on a server with a Trusted Platform Module (TPM) enabled when using the /tpmbypass switch.

Problems Fixed for HPD3 (C):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component would cause an exception error when deployed on a computer with a fully qualified domain name greater than 40 characters in length.

• ドライブがコントローラーへ06/29/04 (自主リセット)を報告した、ATI (Adjacent Track Interference)緩和時の自主リセット問題。コントローラーはドライブとのリンクを再確立し、コマンドを再送信します。
• ドライブパフォーマンスの劣化をもたらすサーボの計算ミス。

HPD3 (B)に対して修正された問題：

• Trusted Platform Module (TPM)が有効なサーバー上で、コンポーネントは/tpmbypassスイッチを使用している場合、ドライブファームウェアのフラッシュに失敗します。

HPD3 (C)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• 長さ40文字を超える完全修飾ドメイン名を持つコンピューターで展開したとき、コンポーネントが例外エラーを引き起こします。

• Self-initiated reset during ATI (Adjacent Track Interference) mitigation issue, where the drive reported a 06/29/04 (Self-Initiated Reset) to the controller.  Then the controller would re-establish link with the drive and resend the command.
• Servo miscalculations that resulted in degraded drive performance.

Problems Fixed for HPD3 (B):

• The component would fail to flash drive firmware on a server with a Trusted Platform Module (TPM) enabled when using the /tpmbypass switch.

Problems Fixed for HPD3 (C):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component would cause an exception error when deployed on a computer with a fully qualified domain name greater than 40 characters in length.

• もしmlx4_ibモジュールがロードされなかったとき、タイムアウト後の "ethtool" セルフテストが割り込みテストでしばしば失敗していました。
• まれな状況で、非同期のイベントハンドラーから呼ばれたmlx4_en_get_drvinfo() によって、システムリブートの間にカーネルパニックが発生することがありました。
• VF netdevsが開いている状態でSR-IOVを無効にしようとすると、オペレーションが失敗しました。

• "ethtool" self test used to fail on interrupt test after timeout if mlx4_ib module was not loaded.
• On rare occassions, kernel panic occured during system reboot caused by mlx4_en_get_drvinfo() called from asynchronous event handler.
• When attempting to disable SR-IOV while there are any VF netdevs open, the operation failed to succeed.

•     Corrects Activity LED behavior on HPE drive carrier.

•     Corrects Activity LED behavior on HPE drive carrier.

• This firmware contains a change to prevent a drive reset issue, which may affect performance.

• This firmware contains a change to prevent a drive reset issue, which may affect performance.

• このファームウェアは、HDDが、1秒を超える長時間ホストが作動していない状態にさらされる場合、HDDの信頼性を改善します。バージョンHPD5以前のHDDのファームウェアを使用している場合、HDDが応答しなくなることがあります。このファームウェアは、また、記録された後、修理されたセクターのステータスが誤って再割り当てされることを防ぐための変更が含まれます。

• This firmware improves HDD reliability when HDDs are exposed to long periods of host inactivity that exceed 1 second. HDDs may become unresponsive when using HDD firmware prior to version HPD5.  This firmware also contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ファームウェアの依存関係：

修正された問題点：

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Known Issues:

• トラックの狭い範囲にデータを書き込むアプリケーションの信頼性の向上。

既知の問題点：

• ファームウェアは、HPG4へのアップグレード後、HPG3へダウングレードすることはできません。

• Reliability enhancement for applications that write data to a narrow range of tracks.

Known Issues:

• Firmware cannot be downgraded to HPG3 after updating to HPG4.

• トラックの狭い範囲にデータを書き込むアプリケーションの信頼性の向上。

既知の問題点：

• ファームウェアは、HPG4へのアップグレード後、HPG3へダウングレードすることはできません。

• Reliability enhancement for applications that write data to a narrow range of tracks.

Known Issues:

• Firmware cannot be downgraded to HPG3 after updating to HPG4.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Fixed the following:

• Link down encountered during high traffic on 81E, 82E, 84E, LPe1205a

UEFI:

• Boot Device Order menu not displaying targets on HPE servers

16G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

16G/32G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

Fixed the following:

• Link down encountered during high traffic on 81E, 82E, 84E, LPe1205a

UEFI:

• Boot Device Order menu not displaying targets on HPE servers

16G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

16G/32G Firmware:

Fixed the following:

• Incorrect adapter showed up in PCI slot 1 in Dashboard and Static Networking

•    HPE Synergy 3530c 16Gbファイバーチャネルホストバスアダプター吸気温度だけが表示されていました。

•    HPE Synergy 3530C 16Gb Fibre Channel Host Bus Adapter inlet temperatures were only being displayed.

• このファームウェアは、予約コマンドが使用される、書き込みキャッシュされたマルチイニシエーター非整列書き込みが有効な環境での潜在的な不正データ問題を修正します。

HPD7 (B)に対して修正された問題：

• コンポーネントが、HP Host Bus Adapter H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HP Host Bus Adapter H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• コンポーネントが、HP Smart Array P431の後ろに接続されたドライブのファームウェア更新に失敗します。コンポーネントは、ファームウェア更新が成功したことを報告します。しかし、電源再投入後、ファームウェアバージョンは変更されません。

• This firmware fixes a potential incorrect data issue in write-cached enabled multi-initiator unaligned write environments, where reservation commands are used.

Problems Fixed for HPD7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component fails to update the firmware for drives connected behind an HP Smart Array P431 controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.

• このファームウェアは、予約コマンドが使用される、書き込みキャッシュされたマルチイニシエーター非整列書き込みが有効な環境での潜在的な不正データ問題を修正します。

HPD7 (B)に対して修正された問題：

• コンポーネントが、HP Host Bus Adapter H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HP Host Bus Adapter H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。
• コンポーネントが、HP Smart Array P431の後ろに接続されたドライブのファームウェア更新に失敗します。コンポーネントは、ファームウェア更新が成功したことを報告します。しかし、電源再投入後、ファームウェアバージョンは変更されません。

• This firmware fixes a potential incorrect data issue in write-cached enabled multi-initiator unaligned write environments, where reservation commands are used.

Problems Fixed for HPD7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.
• Component fails to update the firmware for drives connected behind an HP Smart Array P431 controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may have the system time incorrectly "shifted" to the incorrect time after the operating system has been running for an extended period of time. This issue was typically seen under Microsoft Windows when the Set Time Automatically option was enabled from the Windows Date and Time Settings configuration page.

Addressed an issue where the system may report an inaccurate error message in the Integrated Management Log (IML) when a memory training failure occurred. It is recommended that customers update to this version of the system ROM before replacing any DIMMs due to a training issue.

Addressed an issue where the system may experience an erroneous boot-time message and Integrated Management Log (IML) entry stating that Core Boost Technology is disabled due to a lack of an iLO Advanced License (531 - Core Boost Technology missing required iLO License) when using the Version 1.20 System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note that this IML entry is only valid for servers using the Intel Xeon Scalable 6143 processor. If the message and IML entry are received with any other processor model installed, the message is erroneous and can be ignored without any negative impact to the system.

Known Issues:

• Improved handling of IPV6 addresses

• Supports SLES12 SP3

• Improved handling of SATA drive temperatures

• Improved handling of IPV6 addresses

• Supports SLES12 SP3

• Improved handling of SATA drive temperatures

• This firmware corrects possible unrecovered errors caused by the track refresh algorithm not working properly.

Problems Fixed for HPG7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG7 (D):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• This firmware corrects possible unrecovered errors caused by the track refresh algorithm not working properly.

Problems Fixed for HPG7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG7 (D):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• このファームウェアは、トラックリフレッシュアルゴリズムが正しく動作しないことによって引き起こされることがありえる回復不能エラーを修正します。

HPG7 (B)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• This firmware corrects possible unrecovered errors caused by the track refresh algorithm not working properly.

Problems Fixed for HPG7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

• On rare occasions during UEFI boot cycles system got stuck while WinPE is loaded. (OS WinPE, system DL160).
• Single FTE that catches both untagged and prio-tagged packets (by giving an FTE with match_value.vlan_tag = 0 and match_value.vid = 0) is currently not supported.
• Flashing the firmware requires server reboot. Firmware cannot be flashed twice without server reboot after first flashing.
• If the vport state is DOWN and a packet is sent in local loopback, the sx_sniffer tool will not function.
• Fixed an issue causing bubbles to appear as symbol errors when link raised FDR 1x.
• When Clause 74 Fire-Code FEC is active, and there are FC corrected errors, both the FC_correctable counter and the FC_uncoreectable counter are increment.
• Some Port Control Register do not return to the default value after the last port owner host restarts the driver.
• Fixed an issue which caused RX to hang when the UDP packet had a reserved UDP destination port.
• Fixed DMAC reporting mapping per host.
• Fixed an EEH error from PCI which caused firmware to hang.
• Fixed the default value of the PCIe target_link_speed to Gen3 in link control2.
• Fixed an issue which prevented LEDs from blinking when the traffic was less than 0.1% of the link speed.
• Fixed an issue which caused the mlxconfig configuration of VF_LOG_BAR_SIZE to be ignored and to be set to 5 (32MB).
• Fixed an issues which occasionally caused the driver to hang during unload on some VLs when configuring the SM with a VL weight 0 and running traffic on it.
• A server getting into a Standby mode while Packet-Pacing is enabled might cause firmware to hang and driver call-trace.
• Fixed an issue which caused unexpected QoS functionality in case of multiple sources to single destination traffic transmission.
• Fixed an issue which occasionally caused the RX traffic to hang in DC when received a PCI error on WQE fetch.
• Fixed OOB connection issue during Intel's ITP inject errors test.
• Fixed an issue in IEEE Auto-Negotiation where 25G FireCode FEC and 25G Reed-Solomon FEC bits were reversed.
• Fixed an issue which caused RX to hang when a UDP packet with destination port of RoCE v2 arrived and the data matched the DC transport service.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE OCP card.
• Fixed an issue causing single port devices to query and write Physical Port TLVs to Port 2.
• Enabled mlxfwreset to work using the PCIe Secondary Bus Reset.
• Fixed an issue causing link flapping as a result, incorrect link settings.
• Fixed an issue causing wrong alignment markers to be used when running 50G with Clause91 FEC enabled.
• Reduced the default BAR size for VF (SR-IOV) from 5 (32 MB) to 1 (2MB).
• Added legacy interrupts support in FlexBoot.
• Modified the TX configuration to support EMI crossing margins in 16Ghz.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE and MFA1A00-Exxx for IB EDR).
• Fixed an issue which caused the device to hang when resetting qkey/pkey violation counter via port_info mad.
• Changed the MTU size in OCBB report. Now MTU size does not include the packet headers.
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of SwitchX cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.
• Fixed an issue which prevented Vport counters from counting local loopback packets. Packets now are filter by the self-loopback prevent
• Reported INTx as unsupported to allow PFs Passthrough on PowerKVM.
• SR-IOV Ethernet supports up to 18 VFs per port only.
• Fixed and incident what allowed local (internal) loopbacked packets to be counted by the Vport counters, although Vport counters should count only traffic that crosses the Vport.
• Fixed an issue preventing driver loading or TX traffic sending upon reboot, after ungraceful driver unload.
• Fixed casting of BMC MAC before steering API.
• Fixed the PCI write flow to take into consideration the PCI MTU. This fix eliminates the need for NOPs in the flow, which resulted from PPC larger PCI MTU.
  The single queue limitation for READ is due to a hardware limitation of the number of READ request in a given time.
• Fixed a case that caused FlexBoot to not work as expected with systems that run with "large bar" enabled (Above 4G Decoding) over Connect-IB or ConnectX-4 HCAs.
• Fixed PLDM support for single port NICs. Currently port’s relevant sensors/states are reported only for a single port.

• On rare occasions during UEFI boot cycles system got stuck while WinPE is loaded. (OS WinPE, system DL160).
• Single FTE that catches both untagged and prio-tagged packets (by giving an FTE with match_value.vlan_tag = 0 and match_value.vid = 0) is currently not supported.
• Flashing the firmware requires server reboot. Firmware cannot be flashed twice without server reboot after first flashing.
• If the vport state is DOWN and a packet is sent in local loopback, the sx_sniffer tool will not function.
• Fixed an issue causing bubbles to appear as symbol errors when link raised FDR 1x.
• When Clause 74 Fire-Code FEC is active, and there are FC corrected errors, both the FC_correctable counter and the FC_uncoreectable counter are increment.
• Some Port Control Register do not return to the default value after the last port owner host restarts the driver.
• Fixed an issue which caused RX to hang when the UDP packet had a reserved UDP destination port.
• Fixed DMAC reporting mapping per host.
• Fixed an EEH error from PCI which caused firmware to hang.
• Fixed the default value of the PCIe target_link_speed to Gen3 in link control2.
• Fixed an issue which prevented LEDs from blinking when the traffic was less than 0.1% of the link speed.
• Fixed an issue which caused the mlxconfig configuration of VF_LOG_BAR_SIZE to be ignored and to be set to 5 (32MB).
• Fixed an issues which occasionally caused the driver to hang during unload on some VLs when configuring the SM with a VL weight 0 and running traffic on it.
• A server getting into a Standby mode while Packet-Pacing is enabled might cause firmware to hang and driver call-trace.
• Fixed an issue which caused unexpected QoS functionality in case of multiple sources to single destination traffic transmission.
• Fixed an issue which occasionally caused the RX traffic to hang in DC when received a PCI error on WQE fetch.
• Fixed OOB connection issue during Intel's ITP inject errors test.
• Fixed an issue in IEEE Auto-Negotiation where 25G FireCode FEC and 25G Reed-Solomon FEC bits were reversed.
• Fixed an issue which caused RX to hang when a UDP packet with destination port of RoCE v2 arrived and the data matched the DC transport service.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE OCP card.
• Fixed an issue causing single port devices to query and write Physical Port TLVs to Port 2.
• Enabled mlxfwreset to work using the PCIe Secondary Bus Reset.
• Fixed an issue causing link flapping as a result, incorrect link settings.
• Fixed an issue causing wrong alignment markers to be used when running 50G with Clause91 FEC enabled.
• Reduced the default BAR size for VF (SR-IOV) from 5 (32 MB) to 1 (2MB).
• Added legacy interrupts support in FlexBoot.
• Modified the TX configuration to support EMI crossing margins in 16Ghz.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE and MFA1A00-Exxx for IB EDR).
• Fixed an issue which caused the device to hang when resetting qkey/pkey violation counter via port_info mad.
• Changed the MTU size in OCBB report. Now MTU size does not include the packet headers.
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of SwitchX cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.
• Fixed an issue which prevented Vport counters from counting local loopback packets. Packets now are filter by the self-loopback prevent
• Reported INTx as unsupported to allow PFs Passthrough on PowerKVM.
• SR-IOV Ethernet supports up to 18 VFs per port only.
• Fixed and incident what allowed local (internal) loopbacked packets to be counted by the Vport counters, although Vport counters should count only traffic that crosses the Vport.
• Fixed an issue preventing driver loading or TX traffic sending upon reboot, after ungraceful driver unload.
• Fixed casting of BMC MAC before steering API.
• Fixed the PCI write flow to take into consideration the PCI MTU. This fix eliminates the need for NOPs in the flow, which resulted from PPC larger PCI MTU.
  The single queue limitation for READ is due to a hardware limitation of the number of READ request in a given time.
• Fixed a case that caused FlexBoot to not work as expected with systems that run with "large bar" enabled (Above 4G Decoding) over Connect-IB or ConnectX-4 HCAs.
• Fixed PLDM support for single port NICs. Currently port’s relevant sensors/states are reported only for a single port.

• RSOD問題を修正しました。

• Fixed RSOD issue.

• NVIDIA Tesla M2090 GPU で構成されたシステム上でのコンポーネントのインストール中、修正不能 PCIe エラーが発生する可能性があります。

バージョン1.73(B)で修正された問題：

• コンポーネントインストーラーはHP ProLiant DL580 Gen9 Serverで構成されたときはHPE Express Bay Enablement Switch Cardを検出せず、ファームウェアアップデートを実行しませんでした。

バージョン1.73で修正された問題：

• サーバハードウェアインベントリがデバイスマネジャーに表示されたとき、NVMeドライブはリストに含まれません。

  ファームウェアバージョン1.73は、NVMeがサポートするすべてのドライブが認識され、サーバーハードウェアのインベントリリストに表示されることを可能にします。

• During component installation on a system configured with NVIDIA Tesla M2090 GPU, an uncorrectable PCIe error might occur.

Problems Fixed in version 1.73 (B):

• The component installer did not detect the HPE Express Bay Enablement Switch Card, when it was configured in an HP ProLiant DL580 Gen9 Server, and would not proceed with firmware update.

Problems Fixed in version 1.73:

• When the server hardware inventory was displayed in the Device Manager, the NVMe drives were not included in the lists.

  Firmware version 1.73 allows all NVMe supported drives to be recognized and displayed in the server hardware inventory lists.

•  Enabling ExpressLane on LUNs caused the LUN to become inaccessible

•  Enabling ExpressLane on LUNs caused the LUN to become inaccessible

• コントローラーノードのリセットでのIO劣化内のHostDIF結果の有効化

• Enabling HostDIF results in IO degradation on Controller Node Port Reset

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

主要な NIC MACノードが示す場所は、エンクロージャーシャーシマネージャーに適切に報告されない場合があるという問題を処理しました。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the nodes primary NIC MAC address may not be properly reported to the enclosure chassis manager.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

BIOS

• Incorrect processing of Command Line Processor (CLP)  ‘set netport’
• Improper display of Command Line Processor (CLP) Logical Unit Number (LUN)

UEFI

• Changed Operation Mode Human Interface Infrastructure (HII) strings. The new strings match the FastUTIL strings.
• Self-certification Test (SCT) 2.4B BlockIO2 Protocol bug.
• No response during Self-certification Test (SCT) 2.4B BlockIO2 Protocol test.
• Self-certification Test (SCT) 2.4B AdapterInfo Protocol bugs.

16Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Adapter connection mode to change (OS install related) when the Human Interface Infrastructure (HII) Link Speed field changed.

32Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Added code to start operational firmware early.

BIOS

• Incorrect processing of Command Line Processor (CLP)  ‘set netport’
• Improper display of Command Line Processor (CLP) Logical Unit Number (LUN)

UEFI

• Changed Operation Mode Human Interface Infrastructure (HII) strings. The new strings match the FastUTIL strings.
• Self-certification Test (SCT) 2.4B BlockIO2 Protocol bug.
• No response during Self-certification Test (SCT) 2.4B BlockIO2 Protocol test.
• Self-certification Test (SCT) 2.4B AdapterInfo Protocol bugs.

16Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Adapter connection mode to change (OS install related) when the Human Interface Infrastructure (HII) Link Speed field changed.

32Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Added code to start operational firmware early.

BIOS

• メンテナンスアップデート：

UEFI

• 3PARストレージアレイでWin2012を起動中、予期せぬビヘイビアを修正しました。

16Gbスタンドアップ &16Gbメザニン

BIOS

• FA_BLUNを有効化しているときに、直接接続されたLUNを構成するできるようにするコードを追加しました。

• PCIアドレスが正しくセットアップされていない場合のcheck_mem64ルーチンの予測不能な動作を修正しました。

• FlexAddressが失敗する原因となるバグを修正しました。

UEFI

• HP QMH2672 16Gb Fibre Channel Host BusアダプターのHIIロードデフォルトの問題を修正しました。HII Loadでは、既定で[Adapter Settings]メニューに項目を追加しなくなりました

• 3PARストレージアレイでWin2012を起動中、予期せぬビヘイビアを修正しました。

BIOS

• Maintenance updates

UEFI

• Fixed unexpected behavior during Win2012 boot on 3PAR storage array

16Gb Standup & 16Gb Mezzanine

BIOS

• Added code to allow direct connected LUN to be configured when FA_BLUN is enabled.

• Fixed unexpected behavior in check_mem64 routine where pci address was not setup correctly.

• Fixed bug that caused FlexAddress to stop

UEFI

• Fixed HII Load Defaults issue onHP QMH2672 16Gb Fibre Channel Host Bus Adapter . HII Load defaults no longer adds items to the Adapter Settings menu

• Fixed unexpected behavior during Win2012 boot on 3PAR storage array

Firmware Dependencies:

Problems Fixed:

Addressed an issue where systems configured with a Honeywell LCNP4 card installed may stop responding during system boot.

Addressed an issue where the system may become unresponsive during system boot when an optional HPE Dual 8GB MicroSD USB device is installed with firmware version 202. This issue does not impact servers configured with an HPE Dual 8GB MicroSD USB device using revision of firmware 212 or later.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where systems configured with a Honeywell LCNP4 card installed may stop responding during system boot.

Addressed an issue where the system may become unresponsive during system boot when an optional HPE Dual 8GB MicroSD USB device is installed with firmware version 202. This issue does not impact servers configured with an HPE Dual 8GB MicroSD USB device using revision of firmware 212 or later.

Known Issues:

ファームウェアの依存関係：

修正された問題点：

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

このドライバーは、最大FV割り当てに到達した後の物理機能から接続性が失われる問題に対処します。

このドライバーは、デバイスがget-netadaptervmqから不正な値を報告する可能性がある問題に対処します。

このドライバーは、HPE Ethernet 10Gb 2-port 562FLR-SFP+ アダプターがwake-on-lanに記載されることを回避する問題に対処します。

このドライバーは、HPE Ethernet 10Gb 2-port 562SFP+ アダプターの仮想機能に接続したときに、仮想マシンが予期せずにリブートする問題に対処します。

このドライバーは、無効化-有効化が複数の仮想機能で発行されたときにホストデバイスのyellow-bangにつながる問題に対処します。

このドライバーは、HPE Ethernet 10Gb 2-port 562SFP+アダプターまたはHPE Ethernet 10Gb 2-port 562FLR-SFP+アダプターが高いiSCSI負荷で動作している場合にネットワーク障害を引き起こす問題を解決します。

This driver addresses an issue which results in a loss of connectivity from a physical function after reaching max VF allocations.

This driver addresses an issue where the device may report an incorrect value from get-netadaptervmq.

This driver addresses an issue which prevents the HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter from listening for wake-on-lan.

This driver addresses an issue which results in a virtual machine unexpectedly rebooting when connected with a virtual function of an HPE Ethernet 10Gb 2-port 562SFP+ Adapter.

This driver addresses an issue which results in a yellow-bang in the host device when a disable-enable is issued over multiple virtual functions.

This driver addresses an issue which results in network outages when the HPE Ethernet 10Gb 2-port 562SFP+ Adapter or the HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter is operating under a heavy iSCSI load.

このドライバーは、最大FV割り当てに到達した後の物理機能から接続性が失われる問題に対処します。

このドライバーは、デバイスがget-netadaptervmqから不正な値を報告する可能性がある問題に対処します。

このドライバーは、HPE Ethernet 10Gb 2-port 562FLR-SFP+ アダプターがwake-on-lanに記載されることを回避する問題に対処します。

このドライバーは、HPE Ethernet 10Gb 2-port 562SFP+ アダプターの仮想機能に接続したときに、仮想マシンが予期せずにリブートする問題に対処します。

このドライバーは、無効化-有効化が複数の仮想機能で発行されたときにホストデバイスのyellow-bangにつながる問題に対処します。

This driver addresses an issue which results in a loss of connectivity from a physical function after reaching max VF allocations.

This driver addresses an issue where the device may report an incorrect value from get-netadaptervmq.

This driver addresses an issue which prevents the HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter from listening for wake-on-lan.

This driver addresses an issue which results in a virtual machine unexpectedly rebooting when connected with a virtual function of an HPE Ethernet 10Gb 2-port 562SFP+ Adapter.

This driver addresses an issue which results in a yellow-bang in the host device when a disable-enable is issued over multiple virtual functions.

BIOS

• Incorrect processing of Command Line Processor (CLP)  ‘set netport’
• Improper display of Command Line Processor (CLP) Logical Unit Number (LUN)

UEFI

• Changed Operation Mode Human Interface Infrastructure (HII) strings. The new strings match the FastUTIL strings.
• Self-certification Test (SCT) 2.4B BlockIO2 Protocol bug.
• No response during Self-certification Test (SCT) 2.4B BlockIO2 Protocol test.
• Self-certification Test (SCT) 2.4B AdapterInfo Protocol bugs.

16Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Adapter connection mode to change (OS install related) when the Human Interface Infrastructure (HII) Link Speed field changed.

32Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Added code to start operational firmware early.

BIOS

• Incorrect processing of Command Line Processor (CLP)  ‘set netport’
• Improper display of Command Line Processor (CLP) Logical Unit Number (LUN)

UEFI

• Changed Operation Mode Human Interface Infrastructure (HII) strings. The new strings match the FastUTIL strings.
• Self-certification Test (SCT) 2.4B BlockIO2 Protocol bug.
• No response during Self-certification Test (SCT) 2.4B BlockIO2 Protocol test.
• Self-certification Test (SCT) 2.4B AdapterInfo Protocol bugs.

16Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Adapter connection mode to change (OS install related) when the Human Interface Infrastructure (HII) Link Speed field changed.

32Gb Standup & 16Gb Mezzanine

UEFI

• Adapter not appearing in Health Summary page.
• Invalid Health message when link was down or driver was disabled.
• Added code to start operational firmware early.

BIOS

• メンテナンスアップデート：

UEFI

• 3PARストレージアレイでWin2012を起動中、予期せぬビヘイビアを修正しました。

16Gbスタンドアップ &16Gbメザニン

BIOS

• FA_BLUNを有効化しているときに、直接接続されたLUNを構成するできるようにするコードを追加しました。

• PCIアドレスが正しくセットアップされていない場合のcheck_mem64ルーチンの予測不能な動作を修正しました。

• FlexAddressが失敗する原因となるバグを修正しました。

UEFI

• HP QMH2672 16Gb Fibre Channel Host BusアダプターのHIIロードデフォルトの問題を修正しました。HII Loadでは、既定で[Adapter Settings]メニューに項目を追加しなくなりました

• 3PARストレージアレイでWin2012を起動中、予期せぬビヘイビアを修正しました。

BIOS

• Maintenance updates

UEFI

• Fixed unexpected behavior during Win2012 boot on 3PAR storage array

16Gb Standup & 16Gb Mezzanine

BIOS

• Added code to allow direct connected LUN to be configured when FA_BLUN is enabled.

• Fixed unexpected behavior in check_mem64 routine where pci address was not setup correctly.

• Fixed bug that caused FlexAddress to stop

UEFI

• Fixed HII Load Defaults issue onHP QMH2672 16Gb Fibre Channel Host Bus Adapter . HII Load defaults no longer adds items to the Adapter Settings menu

• Fixed unexpected behavior during Win2012 boot on 3PAR storage array

• Fixed a race between the firmware and the hardware during driver start which blocked outbound completions.
• Fixed an issue which caused the firmware not to send link_down event to the driver when running the close_port command.
• Fixed an issue where in rare cases the Auto Sense failed to detect the right protocol.
• Fixed signal integrity issue when connecting a WCS ConnectX4 mezz card to Pikes peak FPGA.
• Added the option to transmit corrupted DME pages for a very short period of time at the beginning of the Auto-Negotiation flow.
• Fixed an incorrect report of the PortRcvDataVLExtended/ PortXmitDataVLExtended counters by the firmware.
• Fixed a rare issue which caused firmware’s packet injector to cut off packets when the TX was congested.
• Fixed an issue that caused the response to TX requests to take up to 10 miliseconds in IEEE clause 72 Link Training.
• Fixed a race between 2 iriscs which caused a QP to get stuck in burst control limit state.
• When a QP was in error state, the firmware generated too many err CQEs at once, thus causing the cmdif responsiveness to be too slow. To prevent the above, the number of err CQEs was limited to 16 at a time.
• Fixed an issue that caused the MAC address that was set from the OS using ifconfig to be not reflected in the OCBB buffer.
• Fixed an issue where the ibdump got broken when running with loopback traffic.
• Fixed an issue where the firmware took QP to firmware ownership and then released it to the hardware ownership without checking if another firmware flow owns the same QP.
• Fixed an issue which occurred after disconnecting cable which showed the link type as IB even if the link type of the port is ETH.
• Fixed an issue related to the HCA PoerXmitWait counter on port 2 (connected to port 2 on Switch-IB) where it started counting and reached 0xFF's regardless of connection to switch.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed failure instances when initiating FLR inthe Physical Function.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed performance issues causing slow performance when running in NO-DRAM-NIC mode.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Prevented a Virtual Function from injecting pause frames into the network.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed a mistakenly dropped ETH packet with ethertype 0x600 by the NIC.
• Fixed a case preventing broadcast traffic from arriving to their destination after detaching high priority broadcast rule on a port where NC-SI was enabled.
• Fixed a failure to update RSS QP in steering rules.
• Fixed an issue where the port raised as SDR vs. InfiniScale IV QDR Switch.
• Fixed a rare case of completion Error with Bad Opcode sequence status which occurred when retransmitting read requests.
• Fixed a case where the actual bandwidth did not match the user settings in VM QoS.
• Fixed a case where on rare cases, communication to BMC was lost during driver initialization.
• Fixed an issue with cable reading, which caused the link not to raise.
• Set the maximum EQN number to 1024.
• Fixed a rare issue with VPD init flow which caused read failures.
• Fixed an issue with RX size counter not being reported.
• The first Read response was not treated as implicit ACK.
• Reduced a long 40GbE link up time with Cisco Nexus3064 and Arista-7050S.
• Fixed promiscuous mode compatibility with A0-DMFS steering.
• Fixed promiscuous mode compatibility when NC-SI is enabled and configured.
• Fixed sending/receiving OEM temp commands (set/get) with channel ID 0x1f failure.
• Fixed an issue which caused packets to drop on a port when changing the interface state of the other port.
• Fixed long management communication loss and SOL hang during reboot cycles.
• Fixed wrong processing of inbound traffic towards BMC which caused communication loss.
• Fixed management link loss upon closing port interface through the driver.
• Fixed a false indication in firmware of an expander presence causing delay in EEPROM reading.
• Fixed an issue which caused a link down on a port when the cable was removed from the other port.
• Fixed a rare case where packet with length zero got stuck in hardware queues.
• Fixed an issue which caused InfiniBand congestion control packet (CNP) to hang in hardware.
• Fixed an issue which caused AEN to be sent after channel reset.
• Fixed an issue which prevented the restoring of QoS setting to its default consequently causing bandwidth degradation.
• Fixed an occasional long link up time with 10GbE based devices.
• Fixed an issue preventing cable readings from i2c slave address 0x51.
• Fixed a possible deadlock in PM turnoff request transmission and ack acceptance flow.
• Fixed a rare case with alignments state machines which caused occasional width degradation.
• Fixed an issue where the transmit queues hanged while congestion control was enabled and operational (EQC/QCN).
• Fixed an unexpected work completion syndrome with vendor syndrome 0x77 received when running RDMA SEN/WRITE traffic with retransmissions.
• Fixed an issue which caused SetPortInfo to return a good status when receiving invalid LinkSpeedEnabled value.
• Fixed an issue which caused dual port SFPP module cards to be automatically mapped with expander. Fixed an issue where firmware overrides the steering mode that was chosen by the driver.
• Fixed invalid return sensing results occurred when the link was up.
• Fixed an issue causing the sensing result to be delayed when cable was unplugged.
• Fixed an issue causing the link type to be displayed as ETH when set to AUTO.
• Fixed 2us glitch in Wake Up signal.
• Fixed performance degradation when running IBDump.
• Occasionaly, a link training timeout occurred in EQ phase0 during disable/enable test.
• Improved strict bandwidth mode functionality.
• Fixed an issue with the PortRcvPkts counter always displaying zero value.
• Fixed an issue with processing GMP MADs with SET method in SecureHost mode.
• Fixed an issue causing a wrong usage of MCG size when configuring Global Multicast filter.
• Disabling the first port occasionally causes second port TX failure.
• Fixed a mismach in links status reported. The adapter reports links as down while the switch perceives them as up.
• Fixed an occasional 40GbE link failure with SCM5 Switch blade.
• Fixed a wrong FDR10 speed reporting in MAD.
• Fixed an issue preventing theports to to rise up when set to FDR10 vs QDR.
• Fixed an occasional link failure vs Arista switch.
• Retransmission started from the first PSN of message instead of the last acknowledged PSN.
• Firmware hangs when receiving GeneralInfoMad during inline firmware burning.
• L1 flow adjustments and threshold tuning.
• Fixed a rare hanging issue during PERST_ assertion.
• Wrong coefficients were reported during phase3.
• Fixed an issue causing wrong behavior due to reset timing.
• Fixed lack of steering options.
• Fixed long timeout issues.
• Fixed NVRAM write issues in driver-less mode.
• Fixed 40GbE link support in aux mode.
• Dropped commands with non-existing channel ID.
• Fixed issues in extended speed reporting.
• Fixed bad QP reporting in trap 257/8.
• Fixed an issue causing false bad q_key error messages.
• Fixed Pause Frame opcode mismatch.
• Fixed communication loss upon PCIe error detection.
• Fixed wrong channel value in the SELECT/ DESELECT PACKAGE commands.
• Fixed an issue caused response packet to include 4 extra bytes.
• Fixed wrong reason code value returned when using Set Link command with unsupported speed.
• Added protection from bad MAC address given by BMC. Removed false TX pulse after PERST_ deassertion.
• Fixed FLR capability bit inconsistency when SR-IOV is enabled.
• Fixed an issue with the device not reporting PCIe related errors.
• When a link is configured to DDR in a setup of ConnectX-3 to SX6036, SDR link is established instead.
• VXLAN used the wrong default UDP port. the UDP port number was changed to 4789.
• Fixed wrong setting of the UDP destination port for VXLAN.
• Fixed an internal error caused when moving to the DMS mode with IPMI/NC-SI enabled.
• In a back-to-back setup of FDR cards connected with a 0.5m FDR cable, a link may be established as FDR10 instead of FDR.
• Fixed issues related to working with PCI legacy interrupts.
• Wrong checksum calculation for short packets which are padded by the software.
• Reading PCIe configuration space after using the MFT flint tool caused the device to crash.
• Fixed occasional packet loss over IPMI.
• Fixed wrong values reported in the Eye opening MAD.
• Fixed occasional link width degrades during link negotiation and link transitions from L1 state.
• Fixed adjust signal detect thresholds.
• PortExtendedSpeedsCounters MAD counters were mistakenly increased while LLR was active.
• Lane reversal was not considered when configured TX parameters.
• Fixed ROL factory MAC usage when a Flex- Boot address was given.
• Fixed Pause frames factory MAC usage when FlexBoot address was given.
• The device did not different between WOL/ROL packets.
• Fixed a set of extended fields in PortInfo MAD which did not function.
• Adjusted LLR cell size according to the MLPN negotiation of ib_128b_llr.
• The max speed restriction was active in full power mode instead of standby mode only.
• The InfiniBand Path migration did not work with GRH. http://webdev01:8080/commit/ConnectX.git/a9c37ee4c31038f2c1179d4d9e79c9337e0ab5c7 
• Reading MGM after writing it returned wrong members count.
• Fixed corruption of the RSS hash key given by the driver.
• Fixed QoS rate limit BW offset.
• Fixed FDR10 speed_en reporting.
• Fixed long management link com loss.
• The command results reported both link types active at the same time. Fixed collision between forcing phy type and port sensing. Fixed a wrong core clock freq reporting in QUERY_HCA command.
• Fixeds occasional link failure when 56GbE is enabled.
• Fixed max eye margins to be per protocol.
• perfquery reported wrong error symbol on ConnectX©-3 VPI mode: IB, ETH.
• On ConnectX-3Pro dual-port QDR and FDR/FDR10 switch setups, symbol errors may occur with MC2207312-030 AOCs.
• Symbol errors occur on ConnectX-3Pro dualport QDR connected to FDR switches with MC2207126-004 copper cables.
• Driver restart required when switching from InfiniBand FDR link with LLR enabled to InfiniBand link w/o LLR (for example: between SwitchX® and GD4036).
• On rare occasions, the adapter card may fail to link up when performing parallel detect to 40GbE.
• Automatic Path Migration (APM) did not update the new MGIDs from the Alternate Path.

• Fixed a race between the firmware and the hardware during driver start which blocked outbound completions.
• Fixed an issue which caused the firmware not to send link_down event to the driver when running the close_port command.
• Fixed an issue where in rare cases the Auto Sense failed to detect the right protocol.
• Fixed signal integrity issue when connecting a WCS ConnectX4 mezz card to Pikes peak FPGA.
• Added the option to transmit corrupted DME pages for a very short period of time at the beginning of the Auto-Negotiation flow.
• Fixed an incorrect report of the PortRcvDataVLExtended/ PortXmitDataVLExtended counters by the firmware.
• Fixed a rare issue which caused firmware’s packet injector to cut off packets when the TX was congested.
• Fixed an issue that caused the response to TX requests to take up to 10 miliseconds in IEEE clause 72 Link Training.
• Fixed a race between 2 iriscs which caused a QP to get stuck in burst control limit state.
• When a QP was in error state, the firmware generated too many err CQEs at once, thus causing the cmdif responsiveness to be too slow. To prevent the above, the number of err CQEs was limited to 16 at a time.
• Fixed an issue that caused the MAC address that was set from the OS using ifconfig to be not reflected in the OCBB buffer.
• Fixed an issue where the ibdump got broken when running with loopback traffic.
• Fixed an issue where the firmware took QP to firmware ownership and then released it to the hardware ownership without checking if another firmware flow owns the same QP.
• Fixed an issue which occurred after disconnecting cable which showed the link type as IB even if the link type of the port is ETH.
• Fixed an issue related to the HCA PoerXmitWait counter on port 2 (connected to port 2 on Switch-IB) where it started counting and reached 0xFF's regardless of connection to switch.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed failure instances when initiating FLR inthe Physical Function.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed performance issues causing slow performance when running in NO-DRAM-NIC mode.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Prevented a Virtual Function from injecting pause frames into the network.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed a mistakenly dropped ETH packet with ethertype 0x600 by the NIC.
• Fixed a case preventing broadcast traffic from arriving to their destination after detaching high priority broadcast rule on a port where NC-SI was enabled.
• Fixed a failure to update RSS QP in steering rules.
• Fixed an issue where the port raised as SDR vs. InfiniScale IV QDR Switch.
• Fixed a rare case of completion Error with Bad Opcode sequence status which occurred when retransmitting read requests.
• Fixed a case where the actual bandwidth did not match the user settings in VM QoS.
• Fixed a case where on rare cases, communication to BMC was lost during driver initialization.
• Fixed an issue with cable reading, which caused the link not to raise.
• Set the maximum EQN number to 1024.
• Fixed a rare issue with VPD init flow which caused read failures.
• Fixed an issue with RX size counter not being reported.
• The first Read response was not treated as implicit ACK.
• Reduced a long 40GbE link up time with Cisco Nexus3064 and Arista-7050S.
• Fixed promiscuous mode compatibility with A0-DMFS steering.
• Fixed promiscuous mode compatibility when NC-SI is enabled and configured.
• Fixed sending/receiving OEM temp commands (set/get) with channel ID 0x1f failure.
• Fixed an issue which caused packets to drop on a port when changing the interface state of the other port.
• Fixed long management communication loss and SOL hang during reboot cycles.
• Fixed wrong processing of inbound traffic towards BMC which caused communication loss.
• Fixed management link loss upon closing port interface through the driver.
• Fixed a false indication in firmware of an expander presence causing delay in EEPROM reading.
• Fixed an issue which caused a link down on a port when the cable was removed from the other port.
• Fixed a rare case where packet with length zero got stuck in hardware queues.
• Fixed an issue which caused InfiniBand congestion control packet (CNP) to hang in hardware.
• Fixed an issue which caused AEN to be sent after channel reset.
• Fixed an issue which prevented the restoring of QoS setting to its default consequently causing bandwidth degradation.
• Fixed an occasional long link up time with 10GbE based devices.
• Fixed an issue preventing cable readings from i2c slave address 0x51.
• Fixed a possible deadlock in PM turnoff request transmission and ack acceptance flow.
• Fixed a rare case with alignments state machines which caused occasional width degradation.
• Fixed an issue where the transmit queues hanged while congestion control was enabled and operational (EQC/QCN).
• Fixed an unexpected work completion syndrome with vendor syndrome 0x77 received when running RDMA SEN/WRITE traffic with retransmissions.
• Fixed an issue which caused SetPortInfo to return a good status when receiving invalid LinkSpeedEnabled value.
• Fixed an issue which caused dual port SFPP module cards to be automatically mapped with expander. Fixed an issue where firmware overrides the steering mode that was chosen by the driver.
• Fixed invalid return sensing results occurred when the link was up.
• Fixed an issue causing the sensing result to be delayed when cable was unplugged.
• Fixed an issue causing the link type to be displayed as ETH when set to AUTO.
• Fixed 2us glitch in Wake Up signal.
• Fixed performance degradation when running IBDump.
• Occasionaly, a link training timeout occurred in EQ phase0 during disable/enable test.
• Improved strict bandwidth mode functionality.
• Fixed an issue with the PortRcvPkts counter always displaying zero value.
• Fixed an issue with processing GMP MADs with SET method in SecureHost mode.
• Fixed an issue causing a wrong usage of MCG size when configuring Global Multicast filter.
• Disabling the first port occasionally causes second port TX failure.
• Fixed a mismach in links status reported. The adapter reports links as down while the switch perceives them as up.
• Fixed an occasional 40GbE link failure with SCM5 Switch blade.
• Fixed a wrong FDR10 speed reporting in MAD.
• Fixed an issue preventing theports to to rise up when set to FDR10 vs QDR.
• Fixed an occasional link failure vs Arista switch.
• Retransmission started from the first PSN of message instead of the last acknowledged PSN.
• Firmware hangs when receiving GeneralInfoMad during inline firmware burning.
• L1 flow adjustments and threshold tuning.
• Fixed a rare hanging issue during PERST_ assertion.
• Wrong coefficients were reported during phase3.
• Fixed an issue causing wrong behavior due to reset timing.
• Fixed lack of steering options.
• Fixed long timeout issues.
• Fixed NVRAM write issues in driver-less mode.
• Fixed 40GbE link support in aux mode.
• Dropped commands with non-existing channel ID.
• Fixed issues in extended speed reporting.
• Fixed bad QP reporting in trap 257/8.
• Fixed an issue causing false bad q_key error messages.
• Fixed Pause Frame opcode mismatch.
• Fixed communication loss upon PCIe error detection.
• Fixed wrong channel value in the SELECT/ DESELECT PACKAGE commands.
• Fixed an issue caused response packet to include 4 extra bytes.
• Fixed wrong reason code value returned when using Set Link command with unsupported speed.
• Added protection from bad MAC address given by BMC. Removed false TX pulse after PERST_ deassertion.
• Fixed FLR capability bit inconsistency when SR-IOV is enabled.
• Fixed an issue with the device not reporting PCIe related errors.
• When a link is configured to DDR in a setup of ConnectX-3 to SX6036, SDR link is established instead.
• VXLAN used the wrong default UDP port. the UDP port number was changed to 4789.
• Fixed wrong setting of the UDP destination port for VXLAN.
• Fixed an internal error caused when moving to the DMS mode with IPMI/NC-SI enabled.
• In a back-to-back setup of FDR cards connected with a 0.5m FDR cable, a link may be established as FDR10 instead of FDR.
• Fixed issues related to working with PCI legacy interrupts.
• Wrong checksum calculation for short packets which are padded by the software.
• Reading PCIe configuration space after using the MFT flint tool caused the device to crash.
• Fixed occasional packet loss over IPMI.
• Fixed wrong values reported in the Eye opening MAD.
• Fixed occasional link width degrades during link negotiation and link transitions from L1 state.
• Fixed adjust signal detect thresholds.
• PortExtendedSpeedsCounters MAD counters were mistakenly increased while LLR was active.
• Lane reversal was not considered when configured TX parameters.
• Fixed ROL factory MAC usage when a Flex- Boot address was given.
• Fixed Pause frames factory MAC usage when FlexBoot address was given.
• The device did not different between WOL/ROL packets.
• Fixed a set of extended fields in PortInfo MAD which did not function.
• Adjusted LLR cell size according to the MLPN negotiation of ib_128b_llr.
• The max speed restriction was active in full power mode instead of standby mode only.
• The InfiniBand Path migration did not work with GRH. http://webdev01:8080/commit/ConnectX.git/a9c37ee4c31038f2c1179d4d9e79c9337e0ab5c7 
• Reading MGM after writing it returned wrong members count.
• Fixed corruption of the RSS hash key given by the driver.
• Fixed QoS rate limit BW offset.
• Fixed FDR10 speed_en reporting.
• Fixed long management link com loss.
• The command results reported both link types active at the same time. Fixed collision between forcing phy type and port sensing. Fixed a wrong core clock freq reporting in QUERY_HCA command.
• Fixeds occasional link failure when 56GbE is enabled.
• Fixed max eye margins to be per protocol.
• perfquery reported wrong error symbol on ConnectX©-3 VPI mode: IB, ETH.
• On ConnectX-3Pro dual-port QDR and FDR/FDR10 switch setups, symbol errors may occur with MC2207312-030 AOCs.
• Symbol errors occur on ConnectX-3Pro dualport QDR connected to FDR switches with MC2207126-004 copper cables.
• Driver restart required when switching from InfiniBand FDR link with LLR enabled to InfiniBand link w/o LLR (for example: between SwitchX® and GD4036).
• On rare occasions, the adapter card may fail to link up when performing parallel detect to 40GbE.
• Automatic Path Migration (APM) did not update the new MGIDs from the Alternate Path.

• ソフトウェアが、デバイスのMACアドレスのいずれかに等しいDMACを持つポーズフレームを送信しようとしたときに、パケット送信がスタックする原因となった問題を修正しました。
• QP代替コンテキストを処理する際に、ファームウェアの内部エラーの原因となった問題を修正しました。
• APMが、QPのポートマッピングを変更したときに、内部ファームウェアエラーの原因となった問題を修正しました。
• TLVに非有効な情報を満たしたときに、NVRAMがスタックする原因となった問題を修正しました。
• SR-IOV VPIでのIBトラフィックの不足の原因となった問題を修正しました。
• 重複した “read request from middle” の処理での競合を修正しました。
• セクターの数が1に設定され、セクターがゼロにされたときに、NVCONFIGが失敗する原因となった問題を修正しました。
• メッセージMTUサイズがQP.mtuより大きかったときに、TXトラフィックが停止する原因となった問題を修正しました。
• MLNX_OEMコマンドGET_TEMPが、max_tempフィールドに誤った値を返しました。
• IPv4トラフィックの上のRDPがドロップする原因となったデフォルトのハードウェア構成問題を修正しました。
• NO-DRAM-NICモードで実行するときに、パフォーマンスの低下を引き起こしたパフォーマンスの問題を修正しました。
• VLANのNC-SI の準拠を有効にするために、INI内のHigh Rate Steeringモードを無効にしました。
• 物理機能内でFLR を初期化する場合の失敗インスタンスを修正しました。
• ケーブルが接続されていない場合、ケーブル情報MAD内で誤って戻されたステータスを修正しました。
• UDPの長さの計算を修正しました。CNPパケット内の誤った UDP 長さは、ICRCの計算ミスの原因でした。
• ECN が有効な場合の完了エラーの問題を修正しました。ECNの使用は、完了キュー (CQ)の順序エラーの原因でした。

• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Fixed performance issues causing slow performance when running in NO-DRAM-NIC mode.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed failure instances when initiating FLR in the Physical Function.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).

• HPS4 のファームウエアリリースは、ドライブの長いセルフテスト中にドライブがシステムにより認識されなくするタイムアウト状態を起こすというファームウエアのタイミングの問題を解決しました。

• HPS4 firmware release resolved a firmware timing issue which occurred during drive long self-test and resulted in a timeout condition that caused the drive to become unrecognized by the system.

なし

ファームウェアの依存関係:

なし

修正された問題点：

内蔵UEFIシェルrestclientユーティリティがネットワーク TLS（HTTPS）サポートの属性を適切に構成しないという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）メニューに誤った管理者パスワードが入力された後もUEFIまたはレガシーブート順序が変更されるという問題に対処しました。

ドライブがコントローラーに接続されていないときに組み込みAHCI SATAコントローラーがBIOS/プラットフォーム構成（RBSU）PCIデバイスメニューに正しく表示されないという問題に対処しました。

システムユーティリティメニューで、オプションデバイス構成ページからの構成設定の保存が正しく保存されないという問題に対処しました。  この問題は、1つのネットワークアダプタカードで見られました。

取り付けられたバッテリでサポートできるよりも多くのデバイスが取り付けられている場合に、システムROMがHPE Smartバッテリストレージサブシステムの構成エラーを正しく報告しないという問題に対処しました。

直接接続されたNVMeハードディスクドライブで構成されたプラットフォームがシステムユーティリティページから正しくない場所（ボックスおよびベイの場所）を報告するという問題に対処しました。

システムユーティリティメニューでオプションのPCIeアダプターの正しい名前が表示されないという問題に対処しました。

シャーシの電源装置情報が業界標準SMBIOSレコードから適切に報告されないという問題に対処しました。

シャーシのファームウェアリビジョンが、システム情報ページまたはIntegrated Lights Out（iLO）Webインターフェイスから正しく報告されないという問題に対処しました。

シャーシ情報のための業界標準SMBIOSタイプ3レコードがシャーシのシリアル番号を正しく報告しないという問題に対処しました。
 
システムがレガシーブートモードで構成された場合にIntegrated Lights Out（iLO）リモートコンソールキーボードとマウスが正しく機能しないという問題に対処しました。この問題は、UEFIブートモードに構成されたシステムには存在しません。

HPEジッターパフォーマンス機能の設定をIntegrated Lights Out Webインターフェイスから正しく変更できないという問題に対処しました。

バッテリが実際には故障しているときにHPE Smartバッテリが充電中だとシステムから報告される問題に対処しました。システムがSmartバッテリの問題点を報告している場合、このシステムROMをフラッシュすることをお勧めします。

Trustetd Platform Module（TPM）ビジビリティのTPMオプションがRESTful APIを通じて構成できないという問題に対処しました。

OS起動前環境からレガシーブートモードでDIRなどの文字を繰り返し入力するとシステムが反応しなくなるという問題に対処しました。  この問題は、UEFIブートモードのシステムまたはオペレーティングシステムを起動したシステムには影響しません 。

PCIe最大ペイロードサイズが正しくプログラムされていないという理由で、Dialogicアダプターなどの特定のサードパーティPCIeアダプターが正しく機能しないという問題に対処しました。

x16スロットPCIeライザーおよび3スロットx8ライザーがサーバー内に存在するとき、特定のNVMeデバイスが検出されないという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）ネットワークオプションメニューからデバイス上のネットワークブートが無効にされたとき、ネットワークブートオプションが依然としてレガシーブート順序内にエントリを表示するという問題に対処しました。この問題は、UEFIブートモードに構成されたシステムには影響しません。

BIOS/プラットフォーム構成（RBSU）メニューでTABキーを使用する場合にシステムが反応しなくなるという問題に対処しました。

DIMM構成が無効な場合にBIOSが正しく識別せずシステムを停止するという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）エネルギー効率ターボ設定が"退行している"という問題を処理しました。  構成設定が有効に設定されている場合、機能は実際には無効になっていました。  無効に設定されている場合、機能は実際には有効になっていました。

S100i SW RAIDコントローラーから故障したRAIDボリュームを修理しようとすると、サーバーがロックアップして赤色の画面が表示されるという問題に対処しました。

BIOSが正しく構成されていても、RESTful APIでBIOS設定が正しく適用されていないと報告されるという問題に対処しました。

Trusted Platform Module（TPM）がインストールされているとき、システムがウォームリセット後のブート中に反応しなくなり、通常はブランク画面が表示されるという問題に対処しました。  オプションのTPMを含むシステムで再起動の問題が見られる場合は、このリビジョン以降へシステムROMを有効にすることを強くお勧めします。

サーバーの再起動時にシステムが413 Innovation Engine認証エラーを誤って報告するという非常にまれに生じる問題に対処しました。

BIOS/プラットフォーム構成（RBSU）の電源オンロゴの無効化機能のサポートを無効にしました。

Intel Platform Trust Technology（Intel PTT）と呼ばれるチップセットファームウェアベースのTrusted Platform Module（TPM）のサポートが削除されました。この機能は安定性の問題からサポートされなくなりました。Intelはこの機能のサポートを推奨していません。これをサポートするには、ユーザーは個別のHPE TPMオプションを代わりにインストールする必要があります。

既知の問題点：

なし

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the Embedded UEFI Shell restclient utility would not properly configure attributes for Network TLS (HTTPS) support.

Addressed an issue where the UEFI or Legacy Boot Order could still be modified after an incorrect Administrator Password was entered in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the embedded AHCI SATA controller would not show up properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no drives were attached to the controller.

Addressed an issue where saving a configuration setting from an optional device’s configuration page in the System Utilities menu would not be saved properly.  This issue was seen with one Network Adapter card.

Addressed an issue where the system ROM would not correctly report a configuration error for the HPE Smart Battery storage subsystem when more devices were installed than could be supported by the installed battery.

Addressed an issue where a platform configured with direct attached NVMe hard drives may report the incorrect location (box and bay location) from the System Utilities page.

Addressed an issue where the System Utilities menu may not show the proper name for an optional PCIe Adapter.

Addressed an issue where the chassis power supply information would not be properly reported from the Industry Standard SMBIOS records.

Addressed an issue where the chassis firmware revision would not be reported properly from the System Information page or Integrated Lights Out (iLO) web interface.

Addressed an issue where the Industry Standard SMBIOS Type 3 record for chassis information may not properly report the chassis serial number.
 
Addressed an issue where the Integrated Lights Out (iLO) remote Console Keyboard and Mouse may not function properly when the system is configured for Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot Mode.

Addressed an issue where the HPE Jitter Performance feature settings could not be properly modified from the Integrated Lights Out web interface.

Addressed an issue where the system may report that the HPE Smart Battery is charging when in fact the battery has failed. It is recommended to flash to this system ROM if a system is reporting Smart Battery issues.

Addressed an issue where the Trusted Platform Module (TPM) option for TPM Visibility could not be configured through the RESTful API.

Addressed an issue where the system may become unresponsive when repeatedly typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.  This issue does not impact systems in UEFI Boot Mode or a system once the system boots into an operating system.

Addressed an issue where certain third party PCIe adapters, such as a Dialogic adapter, would not function properly due to the PCIe Maximum Payload size being incorrectly programmed.

Addressed an issue where certain NVMe devices may not be detected when the x16 slot PCIe Riser and three slot x8 riser are present in the server.

Addressed an issue where a Network Boot option would still show an entry  in the Legacy Boot Order when Network Boot was disabled on the device from the BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not affect systems configured for UEFI Boot Mode.

Addressed an issue where the system may become unresponsive when using the TAB key in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the BIOS would not properly identify and halt a system from booting with an invalid DIMM configuration.

Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy Efficient Turbo setting was “backwards”.  When the configuration setting was set to enabled, the feature would actually be Disabled.  When configured to Disabled, the feature would actually be enabled.

Addressed an issue where the server might lockup and display a red screen when trying to repair a failed RAID volume off of an S100i SW RAID controller.

Addressed an issue where the RESTful API may report that BIOS settings were not applied properly even when they are properly configured.

Addressed an issue where the system may become unresponsive during boot after a warm reset, typically seen with a blank screen, when a Trusted Platform Module (TPM) is installed.  If reboot issues are seen with systems containing an optional TPM, it is highly recommended the System ROM be enabled to this revision or later.

Addressed an extremely rare issue where the system may incorrectly report a 413 Innovation Engine Authentication Error on a server reboot.

Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo disable functionality.

Removed support for the chipset firmware based Trusted Platform Module (TPM) known as Intel Platform Trust Technology (Intel PTT). This feature is no longer supported due to stability issues and Intel recommends not supporting this feature. Users should instead install a discrete HPE TPM option for this support.

Known Issues:

None

なし

ファームウェアの依存関係:

なし

修正された問題点：

内蔵UEFIシェルrestclientユーティリティがネットワーク TLS（HTTPS）サポートの属性を適切に構成しないという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）メニューに誤った管理者パスワードが入力された後もUEFIまたはレガシーブート順序が変更されるという問題に対処しました。

ドライブがコントローラーに接続されていないときに組み込みAHCI SATAコントローラーがBIOS/プラットフォーム構成（RBSU）PCIデバイスメニューに正しく表示されないという問題に対処しました。

システムユーティリティメニューで、オプションデバイス構成ページからの構成設定の保存が正しく保存されないという問題に対処しました。  この問題は、1つのネットワークアダプタカードで見られました。

取り付けられたバッテリでサポートできるよりも多くのデバイスが取り付けられている場合に、システムROMがHPE Smartバッテリストレージサブシステムの構成エラーを正しく報告しないという問題に対処しました。

直接接続されたNVMeハードディスクドライブで構成されたプラットフォームがシステムユーティリティページから正しくない場所（ボックスおよびベイの場所）を報告するという問題に対処しました。

システムユーティリティメニューでオプションのPCIeアダプターの正しい名前が表示されないという問題に対処しました。

シャーシの電源装置情報が業界標準SMBIOSレコードから適切に報告されないという問題に対処しました。

シャーシのファームウェアリビジョンが、システム情報ページまたはIntegrated Lights Out（iLO）Webインターフェイスから正しく報告されないという問題に対処しました。

シャーシ情報のための業界標準SMBIOSタイプ3レコードがシャーシのシリアル番号を正しく報告しないという問題に対処しました。
 
システムがレガシーブートモードで構成された場合にIntegrated Lights Out（iLO）リモートコンソールキーボードとマウスが正しく機能しないという問題に対処しました。この問題は、UEFIブートモードに構成されたシステムには存在しません。

HPEジッターパフォーマンス機能の設定をIntegrated Lights Out Webインターフェイスから正しく変更できないという問題に対処しました。

バッテリが実際には故障しているときにHPE Smartバッテリが充電中だとシステムから報告される問題に対処しました。システムがSmartバッテリの問題点を報告している場合、このシステムROMをフラッシュすることをお勧めします。

Trustetd Platform Module（TPM）ビジビリティのTPMオプションがRESTful APIを通じて構成できないという問題に対処しました。

OS起動前環境からレガシーブートモードでDIRなどの文字を繰り返し入力するとシステムが反応しなくなるという問題に対処しました。  この問題は、UEFIブートモードのシステムまたはオペレーティングシステムを起動したシステムには影響しません 。

PCIe最大ペイロードサイズが正しくプログラムされていないという理由で、Dialogicアダプターなどの特定のサードパーティPCIeアダプターが正しく機能しないという問題に対処しました。

x16スロットPCIeライザーおよび3スロットx8ライザーがサーバー内に存在するとき、特定のNVMeデバイスが検出されないという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）ネットワークオプションメニューからデバイス上のネットワークブートが無効にされたとき、ネットワークブートオプションが依然としてレガシーブート順序内にエントリを表示するという問題に対処しました。この問題は、UEFIブートモードに構成されたシステムには影響しません。

BIOS/プラットフォーム構成（RBSU）メニューでTABキーを使用する場合にシステムが反応しなくなるという問題に対処しました。

DIMM構成が無効な場合にBIOSが正しく識別せずシステムを停止するという問題に対処しました。

BIOS/プラットフォーム構成（RBSU）エネルギー効率ターボ設定が"退行している"という問題を処理しました。  構成設定が有効に設定されている場合、機能は実際には無効になっていました。  無効に設定されている場合、機能は実際には有効になっていました。

S100i SW RAIDコントローラーから故障したRAIDボリュームを修理しようとすると、サーバーがロックアップして赤色の画面が表示されるという問題に対処しました。

BIOSが正しく構成されていても、RESTful APIでBIOS設定が正しく適用されていないと報告されるという問題に対処しました。

Trusted Platform Module（TPM）がインストールされているとき、システムがウォームリセット後のブート中に反応しなくなり、通常はブランク画面が表示されるという問題に対処しました。  オプションのTPMを含むシステムで再起動の問題が見られる場合は、このリビジョン以降へシステムROMを有効にすることを強くお勧めします。

サーバーの再起動時にシステムが413 Innovation Engine認証エラーを誤って報告するという非常にまれに生じる問題に対処しました。

BIOS/プラットフォーム構成（RBSU）の電源オンロゴの無効化機能のサポートを無効にしました。

Intel Platform Trust Technology（Intel PTT）と呼ばれるチップセットファームウェアベースのTrusted Platform Module（TPM）のサポートが削除されました。この機能は安定性の問題からサポートされなくなりました。Intelはこの機能のサポートを推奨していません。これをサポートするには、ユーザーは個別のHPE TPMオプションを代わりにインストールする必要があります。

既知の問題点：

なし

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the Embedded UEFI Shell restclient utility would not properly configure attributes for Network TLS (HTTPS) support.

Addressed an issue where the UEFI or Legacy Boot Order could still be modified after an incorrect Administrator Password was entered in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the embedded AHCI SATA controller would not show up properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no drives were attached to the controller.

Addressed an issue where saving a configuration setting from an optional device’s configuration page in the System Utilities menu would not be saved properly.  This issue was seen with one Network Adapter card.

Addressed an issue where the system ROM would not correctly report a configuration error for the HPE Smart Battery storage subsystem when more devices were installed than could be supported by the installed battery.

Addressed an issue where a platform configured with direct attached NVMe hard drives may report the incorrect location (box and bay location) from the System Utilities page.

Addressed an issue where the System Utilities menu may not show the proper name for an optional PCIe Adapter.

Addressed an issue where the chassis power supply information would not be properly reported from the Industry Standard SMBIOS records.

Addressed an issue where the chassis firmware revision would not be reported properly from the System Information page or Integrated Lights Out (iLO) web interface.

Addressed an issue where the Industry Standard SMBIOS Type 3 record for chassis information may not properly report the chassis serial number.
 
Addressed an issue where the Integrated Lights Out (iLO) remote Console Keyboard and Mouse may not function properly when the system is configured for Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot Mode.

Addressed an issue where the HPE Jitter Performance feature settings could not be properly modified from the Integrated Lights Out web interface.

Addressed an issue where the system may report that the HPE Smart Battery is charging when in fact the battery has failed. It is recommended to flash to this system ROM if a system is reporting Smart Battery issues.

Addressed an issue where the Trusted Platform Module (TPM) option for TPM Visibility could not be configured through the RESTful API.

Addressed an issue where the system may become unresponsive when repeatedly typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.  This issue does not impact systems in UEFI Boot Mode or a system once the system boots into an operating system.

Addressed an issue where certain third party PCIe adapters, such as a Dialogic adapter, would not function properly due to the PCIe Maximum Payload size being incorrectly programmed.

Addressed an issue where certain NVMe devices may not be detected when the x16 slot PCIe Riser and three slot x8 riser are present in the server.

Addressed an issue where a Network Boot option would still show an entry  in the Legacy Boot Order when Network Boot was disabled on the device from the BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not affect systems configured for UEFI Boot Mode.

Addressed an issue where the system may become unresponsive when using the TAB key in the BIOS/Platform Configuration (RBSU) menus.

Addressed an issue where the BIOS would not properly identify and halt a system from booting with an invalid DIMM configuration.

Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy Efficient Turbo setting was “backwards”.  When the configuration setting was set to enabled, the feature would actually be Disabled.  When configured to Disabled, the feature would actually be enabled.

Addressed an issue where the server might lockup and display a red screen when trying to repair a failed RAID volume off of an S100i SW RAID controller.

Addressed an issue where the RESTful API may report that BIOS settings were not applied properly even when they are properly configured.

Addressed an issue where the system may become unresponsive during boot after a warm reset, typically seen with a blank screen, when a Trusted Platform Module (TPM) is installed.  If reboot issues are seen with systems containing an optional TPM, it is highly recommended the System ROM be enabled to this revision or later.

Addressed an extremely rare issue where the system may incorrectly report a 413 Innovation Engine Authentication Error on a server reboot.

Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo disable functionality.

Removed support for the chipset firmware based Trusted Platform Module (TPM) known as Intel Platform Trust Technology (Intel PTT). This feature is no longer supported due to stability issues and Intel recommends not supporting this feature. Users should instead install a discrete HPE TPM option for this support.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

2.40_02-17-2017 (B)にはコンポーネントパッケージのアップデートが含まれており、機能的にはバージョン2.40_02-17-2017と同等です。  以前のコンポーネントのRevision がROMシステムから2.40_02-17-2017へアップグレードするために使用されていた場合は、Revision Bにアップグレードする必要はありません。

SUM バージョン7.6.0またはそれ以前のバージョンの場合は、2.40_02-17-2017 (B)の配置に使用されなければいけません。

ファームウェアの依存関係:

なし

修正された問題点：

サードパーティのUSB 3.0 XHCI アダプターカードがサーバーにインストールされる時に、システムブート間にシステムが反応しなくなるという問題を解決しました。

システムが、DIMMがIntegrated Management Log (IML)に高い率での修正されたメモリエラーを経験したことを適切に示しているが、DIMMのステータスはiLO GUIでは正常であると誤って報告されるという問題を処理しました。 iLO GUIはDIMMのステータスは劣化だと報告します。

主要な NIC MACノードが示す場所は、エンクロージャーシャーシマネージャーに適切に報告されない場合があるという問題を処理しました。

USB-ベースのUPSがサーバーUSBポートに装着されている時に、システムブート間にシステムが反応しなくなるという問題を解決しました。 この問題は、システムがレガシブートモードに設定されている場合にのみ発生します。

システムが適切な報告を行わず、 Integrated Management Log (IML)に対するログエラーがオプションのHPE デュアル SD カード上に検出される問題を解決しました。 この問題はシステムがウォームリセットを実行する際にはログのみに影響します。

既知の問題点：

なし

Version 2.40_02-17-2017 (B) contains updates to the component packaging and is functionally equivalent to version 2.40_02-17-2017.  It is not necessary to upgrade with Revision B if the system ROM was previously upgraded to version 2.40_02-17-2017.

SUM version 7.6.0  or earlier should be used for deployment of 2.40_02-17-2017 (B).

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.

Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.

Addressed an issue where the nodes primary NIC MAC address may not be properly reported to the enclosure chassis manager.

Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.

Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.

Known Issues:

None

• このファームウェアは、予約コマンドが使用される、書き込みキャッシュされたマルチイニシエーター非整列書き込みが有効な環境での潜在的な不正データ問題を修正します。

HPD7 (B)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• This firmware fixes a potential incorrect data issue in write-cached enabled multi-initiator unaligned write environments, where reservation commands are used.

Problems Fixed for HPD7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

• このファームウェアは、予約コマンドが使用される、書き込みキャッシュされたマルチイニシエーター非整列書き込みが有効な環境での潜在的な不正データ問題を修正します。

HPD7 (B)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• This firmware fixes a potential incorrect data issue in write-cached enabled multi-initiator unaligned write environments, where reservation commands are used.

Problems Fixed for HPD7 (B):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

• This firmware contains a change to prevent occasional command completion times in the 4-5 second window when command is received just as the drive is transitioning from active to Idle A.

• This firmware contains a change to prevent occasional command completion times in the 4-5 second window when command is received just as the drive is transitioning from active to Idle A.

• リングサイズを8192に設定した後、アダプターカードがダウン状態から動けなくなる問題を修正しました。

• Fixed an issue which caused the adapter card to get stuck in Down state after setting the ring size to 8192.

• Fixes a rare but potential data integrity error during low 5v drive voltage and specific sequential data streaming conditions, which could result in data written to incorrect sectors.

Problems Fixed for HPG5 (C):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG5 (E):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• Fixes a rare but potential data integrity error during low 5v drive voltage and specific sequential data streaming conditions, which could result in data written to incorrect sectors.

Problems Fixed for HPG5 (C):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

Problems Fixed for HPG5 (E):

• When attempting to update drive firmware in a VMware vSphere 6.5 environment, the update would fail and the event was logged as a segmentation fault error.

• データが誤ったセクターに書かれる可能性があった、低い5v駆動電圧と特定の順次データストリーミング状態の間のまれではあるが潜在的なデータ整合性エラーを修正します。

HPG5 (C)に対して修正された問題：

• コンポーネントが、HP ホストバスアダプター H22xへ取り付けられている2つ以上の外部ドライブエンクロージャーで構成されるシステム内で、ドライブ表示用のドライブファームウェアのインストールに失敗しました。「ドライブがツリー内に数回表示されています」というメッセージがコンポーネントログファイルに報告されました。ドライブファームウェアインストールの失敗は、HPホストバスアダプター H22xへ取り付けられている1つの外部ドライブエンクロージャーがある構成内では見られませんでした。

• Fixes a rare but potential data integrity error during low 5v drive voltage and specific sequential data streaming conditions, which could result in data written to incorrect sectors.

Problems Fixed for HPG5 (C):

• Component would fail to install drive firmware for drives present in a system configured with two or more external drive enclosures attached to an HP Host Bus Adapter H22x. The following message would be reported in the component log file - “Device appears more than once in tree”. The drive firmware installation failure was not observed in configurations having only one external drive enclosure attached to an HP Host Bus Adapter H22x.

• HPE Dynamic Smart アレイB320i RAIDコントローラーで構成されたHPE ProLiant BL420c Gen8サーバーが、起動に失敗してPower-On Self-Test (POST)の間にシステムが止まりました。いくつかのインスタンスで、"1783 Driver Array Controller Failure"というメッセージが表示されました。詳細については、HPEカスタマーアドバイザリc05317927 (英語)を参照してください。

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

This product addresses a system panic seen when enabling Single-Root Input/Output Virtualization (SR-IOV).

This product addresses a PHY stack trace and system panic seen when creating and/or allocating a Virtual Function (VF).

This product addresses an issue where a Media Access Control Virtual Local Area Network (MAC-VLAN) cannot be set if the MAC is set by a Physical Function (PF) that has an associated trusted Virtual Function (VF).

This product addresses a system panic seen when enabling Single-Root Input/Output Virtualization (SR-IOV).

This product addresses a PHY stack trace and system panic seen when creating and/or allocating a Virtual Function (VF).

This product addresses an issue where a Media Access Control Virtual Local Area Network (MAC-VLAN) cannot be set if the MAC is set by a Physical Function (PF) that has an associated trusted Virtual Function (VF).

• Fixed a race between the firmware and the hardware during driver start which blocked outbound completions.
• Fixed an issue which caused the firmware not to send link_down event to the driver when running the close_port command.
• Fixed an issue where in rare cases the Auto Sense failed to detect the right protocol.
• Fixed signal integrity issue when connecting a WCS ConnectX4 mezz card to Pikes peak FPGA..
• Added the option to transmit corrupted DME pages for a very short period of time at the beginning of the Auto-Negotiation flow.
• Fixed an incorrect report of the PortRcvDataVLExtended / PortXmitDataVLExtended counters by the firmware.
• Fixed a rare issue which caused firmware’s packet injector to cut off packets when the TX was congested.
• Fixed an issue that caused the response to TX requests to take up to 10 mili-seconds in IEEE clause 72 Link Training.
• Fixed a race between 2 iriscs which caused a QP to get stuck in burst control limit state.
• When a QP was in error state, the firmware generated too many err CQEs at once, thus causing the cmdif responsiveness to be too slow. To prevent the above, the number of err CQEs was limited to 16 at a time.
• Fixed an issue that caused the MAC address that was set from the OS using ifconfig to be not reflected in the OCBB buffer.
• Fixed an issue where the ibdump got broken when running with loopback traffic.
• Fixed an issue where the firmware took QP to firmware ownership and then released it to the hardware ownership without checking if another firmware flow owns the same QP.
• Fixed an issue which occurred after disconnecting cable which showed the link type as IB even if the link type of the port is ETH.
• Fixed an issue related to the HCA PoerXmitWait counter on port 2 (connected to port 2 on Switch-IB) where it started counting and reached 0xFF's regardless of connection to switch.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a wrong returned status in cable info MAD when the cable was not connected
• Fixed failure instances when initiating FLR in the Physical Function.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping. 
• Fixed an issue which caused a firmware internal error when handling QP alternative context. 
• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed a wrong reporting of section 5 event 8 - LSO support.
• Fixed a mistakenly dropped ETH packet with ethertype 0x600 by the NIC.
• Fixed a case preventing broadcast traffic from arriving to their destination after detaching high priority broadcast rule on a port where NC-SI was enabled.
• Fixed an issue where the port raised as SDR vs. InfiniScale IV QDR Switch
• Fixed a rare case of completion Error with Bad Opcode sequence status which occurred when retransmitting read requests
• Fixed a case where the actual bandwidth did not match the user settings in VM QoS.
• Fixed a case where on rare cases, communication to BMC was lost during driver initialization.
• Fixed an issue with cable reading, which caused the link not to raise.
• Set the maximum EQN number to 1024.
• Fixed a rare issue with VPD init flow which caused read failures.
• Fixed an issue with RX size counter not being reported.
• Fixed promiscuous mode compatibility with A0-DMFS steering.
• Fixed promiscuous mode compatibility when NC-SI is enabled and configured.
• Fixed sending/receiving OEM temp commands (set/get) with channel ID 0x1f failure.
• Fixed an issue which caused packets to drop on a port when changing the interface state of the other port.
• Fixed long management communication loss and SOL hang during reboot cycles.
• Fixed wrong processing of inbound traffic towards BMC which caused communication loss.
• Fixed management link loss upon closing port interface through the driver.
• Fixed a false indication in firmware of an expander presence causing delay in EEPROM reading.
• Fixed an issue which caused a link down on a port when the cable was removed from the other port.
• Fixed a rare case where packet with length zero got stuck in hardware queues.
• Fixed an issue which caused InfiniBand congestion control packet (CNP) to hang in hardware.
• Fixed an issue which caused AEN to be sent after channel reset.
• Fixed an issue which prevented the restoring of QoS setting to its default consequently causing bandwidth degradation.
• Fixed an occasional long link up time with 10GbE based devices.
• Fixed an issue preventing cable readings from i2c slave address 0x51
• Fixed a wrong parity bit calculation when transmitting PCIe TS1 packets.
• Fixed a possible deadlock in PM turnoff request transmission and ack acceptance flow.
• Fixed a rare case with alignments state machines which caused occasional width degradation.
• Fixed an issue where the transmit queues hanged while congestion control was enabled and operational (EQC/QCN)
• Fixed an unexpected work completion syndrome with vendor syndrome 0x77 received when running RDMA SEN/WRITE traffic with retransmissions.
• Fixed an issue which caused SetPortInfo to return a good status when receiving invalid LinkSpeedEnabled value.
• Fixed an issue which caused dual port SFPP module cards to be automatically mapped with expander.
• Fixed an issue where firmware overrides the steering mode that was chosen by the driver.
• Fixed invalid return sensing results occurred when the link was up.
• Fixed an issue causing the sensing result to be delayed when cable was unplugged.
• Fixed an issue causing the link type to be displayed as ETH when set to AUTO.
• Fixed an issue causing ARP not to reply when connected to Hyper-V vSwitch.

Fixes in 14.18.2030:

• On rare occasions during UEFI boot cycles system got stuck while WinPE is loaded. (OS WinPE, system DL160).
• Single FTE that catches both untagged and prio-tagged packets (by giving an FTE with match_value.vlan_tag = 0 and match_value.vid = 0) is currently not supported.
• Flashing the firmware requires server reboot. Firmware cannot be flashed twice without server reboot after first flashing
• If the vport state is DOWN and a packet is sent in local loopback, the sx_sniffer tool will not function.
• Fixed an issue causing bubbles to appear as symbol errors when link raised FDR 1x.
• When Clause 74 Fire-Code FEC is active, and there are FC corrected errors, both the FC_correctable counter and the FC_uncoreectable counter are increment.
• Some Port Control Register do not return to the default value after the last port owner host restarts the driver.
• Fixed an issue which caused RX to hang when the UDP packet had a reserved UDP destination port.
• Fixed DMAC reporting mapping per host.
• Fixed an EEH error from PCI which caused firmware to hang.
• Fixed the default value of the PCIe target_link_speed to Gen3 in link control2.
• Fixed an issue which prevented LEDs from blinking when the traffic was less than 0.1% of the link speed.
• Fixed an issue which caused the mlxconfig configuration of VF_LOG_BAR_SIZE to be ignored and to be set to 5 (32MB).
• A server getting into a Standby mode while Packet-Pacing is enabled might cause firmware to hang and driver call-trace.
• Fixed an issue which caused unexpected QoS functionality in case of multiple sources to single destination traffic transmission.
• Fixed an issue which occasionally caused the RX traffic to hang in DC when received a PCI error on WQE fetch.
• Fixed OOB connection issue during Intel's ITP inject errors test.
• Fixed an issue which prevented MAC address changes by to driver to be reflected in the OBCC and NC-SI interfaces.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE cards.
• Fixed an issue which caused a link down in Port 2 when unplugging the cable from Port 1.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE).
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Enabled RoCE IPv4 Multicast. This prevents MCG command from failing when an IPv4 is mapped to an IPv6 address.
• If the PF driver or the tool (e.g. ethtool) use PAOS DOWN command (e.g. by ifconfig down or ip link set down), loopback traffic is blocked for all functions on this port (PF<->VFs / VF<->VF) In Multihost loopback, the traffic will be blocked once the firmware receives the PAOS down command from all PFs. However, the loopback traffic will not be blocked when the port is down  due to the physical link (for example: cable plugged out, switch port down).
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of eSwitch cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.
• Fixed a UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GbE OCP card.
• Fixed an issue which prevented Vport counters from counting local loopback packets. Packets now are filter by the self-loopback prevention.
• Reported INTx as unsupported to allow PFs Passthrough on PowerKVM.
• SR-IOV Ethernet supports up to 18 VFs per port only.
• Fixed and incident what allowed local (internal) loopbacked packets to be counted by the Vport counters, although Vport counters should count only traffic that crosses the Vport.
• Fixed an issue preventing driver loading or TX traffic sending upon reboot, after ungraceful driver unload.
• Fixed casting of BMC MAC before steering API.
• Fixed the PCI write flow to take into consideration the PCI MTU. This fix eliminates the need for NOPs in the flow, which resulted from PPC larger PCI MTU.
  The single queue limitation for READ is due to a hardware limitation of the number of READ request in a given time.
• Fixed a case that caused FlexBoot to not work as expected with systems that run with "large bar" enabled (Above 4G Decoding) over Connect-IB or ConnectX-4 HCAs.
• Fixed an issue which prevented link creation when connected to IXIA 25G.

• Fixed a race between the firmware and the hardware during driver start which blocked outbound completions.
• Fixed an issue which caused the firmware not to send link_down event to the driver when running the close_port command.
• Fixed an issue where in rare cases the Auto Sense failed to detect the right protocol.
• Fixed signal integrity issue when connecting a WCS ConnectX4 mezz card to Pikes peak FPGA..
• Added the option to transmit corrupted DME pages for a very short period of time at the beginning of the Auto-Negotiation flow.
• Fixed an incorrect report of the PortRcvDataVLExtended / PortXmitDataVLExtended counters by the firmware.
• Fixed a rare issue which caused firmware’s packet injector to cut off packets when the TX was congested.
• Fixed an issue that caused the response to TX requests to take up to 10 mili-seconds in IEEE clause 72 Link Training.
• Fixed a race between 2 iriscs which caused a QP to get stuck in burst control limit state.
• When a QP was in error state, the firmware generated too many err CQEs at once, thus causing the cmdif responsiveness to be too slow. To prevent the above, the number of err CQEs was limited to 16 at a time.
• Fixed an issue that caused the MAC address that was set from the OS using ifconfig to be not reflected in the OCBB buffer.
• Fixed an issue where the ibdump got broken when running with loopback traffic.
• Fixed an issue where the firmware took QP to firmware ownership and then released it to the hardware ownership without checking if another firmware flow owns the same QP.
• Fixed an issue which occurred after disconnecting cable which showed the link type as IB even if the link type of the port is ETH.
• Fixed an issue related to the HCA PoerXmitWait counter on port 2 (connected to port 2 on Switch-IB) where it started counting and reached 0xFF's regardless of connection to switch.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a wrong returned status in cable info MAD when the cable was not connected
• Fixed failure instances when initiating FLR in the Physical Function.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping. 
• Fixed an issue which caused a firmware internal error when handling QP alternative context. 
• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed a wrong reporting of section 5 event 8 - LSO support.
• Fixed a mistakenly dropped ETH packet with ethertype 0x600 by the NIC.
• Fixed a case preventing broadcast traffic from arriving to their destination after detaching high priority broadcast rule on a port where NC-SI was enabled.
• Fixed an issue where the port raised as SDR vs. InfiniScale IV QDR Switch
• Fixed a rare case of completion Error with Bad Opcode sequence status which occurred when retransmitting read requests
• Fixed a case where the actual bandwidth did not match the user settings in VM QoS.
• Fixed a case where on rare cases, communication to BMC was lost during driver initialization.
• Fixed an issue with cable reading, which caused the link not to raise.
• Set the maximum EQN number to 1024.
• Fixed a rare issue with VPD init flow which caused read failures.
• Fixed an issue with RX size counter not being reported.
• Fixed promiscuous mode compatibility with A0-DMFS steering.
• Fixed promiscuous mode compatibility when NC-SI is enabled and configured.
• Fixed sending/receiving OEM temp commands (set/get) with channel ID 0x1f failure.
• Fixed an issue which caused packets to drop on a port when changing the interface state of the other port.
• Fixed long management communication loss and SOL hang during reboot cycles.
• Fixed wrong processing of inbound traffic towards BMC which caused communication loss.
• Fixed management link loss upon closing port interface through the driver.
• Fixed a false indication in firmware of an expander presence causing delay in EEPROM reading.
• Fixed an issue which caused a link down on a port when the cable was removed from the other port.
• Fixed a rare case where packet with length zero got stuck in hardware queues.
• Fixed an issue which caused InfiniBand congestion control packet (CNP) to hang in hardware.
• Fixed an issue which caused AEN to be sent after channel reset.
• Fixed an issue which prevented the restoring of QoS setting to its default consequently causing bandwidth degradation.
• Fixed an occasional long link up time with 10GbE based devices.
• Fixed an issue preventing cable readings from i2c slave address 0x51
• Fixed a wrong parity bit calculation when transmitting PCIe TS1 packets.
• Fixed a possible deadlock in PM turnoff request transmission and ack acceptance flow.
• Fixed a rare case with alignments state machines which caused occasional width degradation.
• Fixed an issue where the transmit queues hanged while congestion control was enabled and operational (EQC/QCN)
• Fixed an unexpected work completion syndrome with vendor syndrome 0x77 received when running RDMA SEN/WRITE traffic with retransmissions.
• Fixed an issue which caused SetPortInfo to return a good status when receiving invalid LinkSpeedEnabled value.
• Fixed an issue which caused dual port SFPP module cards to be automatically mapped with expander.
• Fixed an issue where firmware overrides the steering mode that was chosen by the driver.
• Fixed invalid return sensing results occurred when the link was up.
• Fixed an issue causing the sensing result to be delayed when cable was unplugged.
• Fixed an issue causing the link type to be displayed as ETH when set to AUTO.
• Fixed an issue causing ARP not to reply when connected to Hyper-V vSwitch.

Fixes in 14.18.2030:

• On rare occasions during UEFI boot cycles system got stuck while WinPE is loaded. (OS WinPE, system DL160).
• Single FTE that catches both untagged and prio-tagged packets (by giving an FTE with match_value.vlan_tag = 0 and match_value.vid = 0) is currently not supported.
• Flashing the firmware requires server reboot. Firmware cannot be flashed twice without server reboot after first flashing
• If the vport state is DOWN and a packet is sent in local loopback, the sx_sniffer tool will not function.
• Fixed an issue causing bubbles to appear as symbol errors when link raised FDR 1x.
• When Clause 74 Fire-Code FEC is active, and there are FC corrected errors, both the FC_correctable counter and the FC_uncoreectable counter are increment.
• Some Port Control Register do not return to the default value after the last port owner host restarts the driver.
• Fixed an issue which caused RX to hang when the UDP packet had a reserved UDP destination port.
• Fixed DMAC reporting mapping per host.
• Fixed an EEH error from PCI which caused firmware to hang.
• Fixed the default value of the PCIe target_link_speed to Gen3 in link control2.
• Fixed an issue which prevented LEDs from blinking when the traffic was less than 0.1% of the link speed.
• Fixed an issue which caused the mlxconfig configuration of VF_LOG_BAR_SIZE to be ignored and to be set to 5 (32MB).
• A server getting into a Standby mode while Packet-Pacing is enabled might cause firmware to hang and driver call-trace.
• Fixed an issue which caused unexpected QoS functionality in case of multiple sources to single destination traffic transmission.
• Fixed an issue which occasionally caused the RX traffic to hang in DC when received a PCI error on WQE fetch.
• Fixed OOB connection issue during Intel's ITP inject errors test.
• Fixed an issue which prevented MAC address changes by to driver to be reflected in the OBCC and NC-SI interfaces.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE cards.
• Fixed an issue which caused a link down in Port 2 when unplugging the cable from Port 1.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE).
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Enabled RoCE IPv4 Multicast. This prevents MCG command from failing when an IPv4 is mapped to an IPv6 address.
• If the PF driver or the tool (e.g. ethtool) use PAOS DOWN command (e.g. by ifconfig down or ip link set down), loopback traffic is blocked for all functions on this port (PF<->VFs / VF<->VF) In Multihost loopback, the traffic will be blocked once the firmware receives the PAOS down command from all PFs. However, the loopback traffic will not be blocked when the port is down  due to the physical link (for example: cable plugged out, switch port down).
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of eSwitch cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.
• Fixed a UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GbE OCP card.
• Fixed an issue which prevented Vport counters from counting local loopback packets. Packets now are filter by the self-loopback prevention.
• Reported INTx as unsupported to allow PFs Passthrough on PowerKVM.
• SR-IOV Ethernet supports up to 18 VFs per port only.
• Fixed and incident what allowed local (internal) loopbacked packets to be counted by the Vport counters, although Vport counters should count only traffic that crosses the Vport.
• Fixed an issue preventing driver loading or TX traffic sending upon reboot, after ungraceful driver unload.
• Fixed casting of BMC MAC before steering API.
• Fixed the PCI write flow to take into consideration the PCI MTU. This fix eliminates the need for NOPs in the flow, which resulted from PPC larger PCI MTU.
  The single queue limitation for READ is due to a hardware limitation of the number of READ request in a given time.
• Fixed a case that caused FlexBoot to not work as expected with systems that run with "large bar" enabled (Above 4G Decoding) over Connect-IB or ConnectX-4 HCAs.
• Fixed an issue which prevented link creation when connected to IXIA 25G.

• ソフトウェアが、デバイスのMACアドレスのいずれかに等しいDMACを持つポーズフレームを送信しようとしたときに、パケット送信がスタックする原因となった問題を修正しました。
• QP代替コンテキストを処理する際に、ファームウェアの内部エラーの原因となった問題を修正しました。
• APMが、QPのポートマッピングを変更したときに、内部ファームウェアエラーの原因となった問題を修正しました。
• TLVに非有効な情報を満たしたときに、NVRAMがスタックする原因となった問題を修正しました。
• SR-IOV VPIでのIBトラフィックの不足の原因となった問題を修正しました。
• 重複した “read request from middle” の処理での競合を修正しました。
• セクターの数が1に設定され、セクターがゼロにされたときに、NVCONFIGが失敗する原因となった問題を修正しました。
• メッセージMTUサイズがQP.mtuより大きかったときに、TXトラフィックが停止する原因となった問題を修正しました。
• MLNX_OEMコマンドGET_TEMPが、max_tempフィールドに誤った値を返しました。
• IPv4トラフィックの上のRDPがドロップする原因となったデフォルトのハードウェア構成問題を修正しました。
• VLANのNC-SI の準拠を有効にするために、INI内のHigh Rate Steeringモードを無効にしました。
• 物理機能内でFLR を初期化する場合の失敗インスタンスを修正しました。
• ケーブルが接続されていない場合、ケーブル情報MAD内で誤って戻されたステータスを修正しました。
• UDPの長さの計算を修正しました。CNPパケット内の誤った UDP 長さは、ICRCの計算ミスの原因でした。
• ECN が有効な場合の完了エラーの問題を修正しました。ECNの使用は、完了キュー (CQ)の順序エラーの原因でした。

14.14.2204での修正: