• unexpected behavior with incomplete path reporting that would cause an unexpectedly high number of dropped frames reported by the target and driver
•  driver abort request to properly abort ELS (Extended Link Services) command

• unexpected behavior with incomplete path reporting that would cause an unexpectedly high number of dropped frames reported by the target and driver
•  driver abort request to properly abort ELS (Extended Link Services) command

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

修正された問題点:

インテル XeonスケーラブルパフォーマンスBronzeおよびSilverプロセッサーで、システムで訂正不可能なメモリエラーまたは起動時のメモリトレーニングの問題が発生する可能性がある問題に対処しました。この問題はシステムROMバージョン2.00で最初に発生したものです。メモリに関する問題が発生しているお客様は、コンポーネントを交換する前に、このバージョンのシステムROMに直ちにアップデートすることを推奨します。この問題は、HPEサーバーに固有のものではありません。

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may experience a higher rate of Uncorrectable Memory errors or boot time Memory training issues with Intel Xeon Scalable Performance Bronze and Silver processors. This issue was first introduced with System ROM version 2.00. HPE recommends that any customer experiencing a memory issue immediately update to this version of the system ROM before replacing any components. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Kernel panic may occur during device discovery state.

• Kernel panic may occur during device discovery state.

この製品は、RSSおよびドライバー検証ツールが両方とも有効な場合に表示されるWindows停止エラー（BSOD）を修正します。

この製品は、RoCEv2を正しく接続できないという問題を修正します。

この製品は、コア数が256を超えるシステムでBSODが発生する問題を修正します。

この製品は、HPE Intel Ethernet 10Gb 562SFP+アダプターを含むシステムでジャンボフレームが有効になっていると、Windows Server 2016用のHPE Intel i40eaドライバーバージョン1.8.83.0または1.8.94.0が原因でiSCSIマウントボリュームのNTFSファイルが破損する問題に対処します。詳しくは、カスタマーアドバイザリ: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00074697en_usを参照してください。

This product corrects a Windows Stop Error (BSOD) seen when RSS and the driver verifier are both enabled.

This product corrects an issue which results in a failure to correctly set up ROCEv2 connections.

This product corrects an issue which results in a BSOD in systems with more than 256 cores.

This product addresses an issue where the HPE Intel i40ea Driver for Windows Server 2016, versions 1.8.83.0 or 1.8.94.0, causes NTFS file corruption to iSCSI mounted volumes when jumbo frames are enabled on systems containing the HPE Intel Ethernet 10Gb 562SFP+ Adapter. For more information see the Customer Advisory at https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00074697en_us.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ver. 2.72 (B)には、コンポーネントのパッケージングに対するアップデートが含まれており、機能的にver. 2.72と同等です。  ファームウェアをバージョン2.72にアップグレードするために以前のリビジョンのコンポーネントが使われた場合は、リビジョン(B)にアップグレードする必要はありません。

このシステムROMのリビジョンには、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング(MDS)と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMのリビジョンには、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング(MDS)と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  これらの問題は、HPEサーバーに固有のものではありません。 

既知の問題点:

なし

Ver. 2.72 (B) contains updates to the component packaging and is functionally equivalent to ver. 2.72.  It is not necessary to upgrade with Revision (B) if a previous component revision was used to upgrade the firmware to ver. 2.72.

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers. 

Known Issues:

None

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an intermittent issue where an optional PCIe device may not properly report its thermal data or other telemetry data as seen through the Integrated Lights-Out (iLO) interface. This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an intermittent issue where an optional PCIe device may not properly report its thermal data or other telemetry data as seen through the Integrated Lights-Out (iLO) interface. This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

ver. 2.72 (B)には、コンポーネントのパッケージングに対するアップデートが含まれており、機能的にver. 2.72と同等です。  ファームウェアをバージョン2.72にアップグレードするために以前のリビジョンのコンポーネントが使われた場合は、リビジョン(B)にアップグレードする必要はありません。

このシステムROMのリビジョンには、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング(MDS)と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMのリビジョンには、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング(MDS)と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  これらの問題は、HPEサーバーに固有のものではありません。

既知の問題点:

なし

Ver. 2.72 (B) contains updates to the component packaging and is functionally equivalent to ver. 2.72.  It is not necessary to upgrade with Revision (B) if a previous component revision was used to upgrade the firmware to ver. 2.72.

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Known Issues:

None

• New servo which prevents the drive from posting non-media errors
• A fix for an issue where the drive could become unresponsive after a hard reset

• New servo which prevents the drive from posting non-media errors
• A fix for an issue where the drive could become unresponsive after a hard reset

Firmware Dependencies:

Problems Fixed:

Addressed an issue where configuring memory to run at 2x refresh rate would still actually operate memory at 1x refresh rate. This issue was introduced with the v2.00 System ROM and did not impact earlier versions of the System ROM. This issue is not unique to HPE servers.

Addressed an issue where the NVMe PCIe Resource Padding option in BIOS/Platform Configuration (RBSU) would not properly allocated sufficient resources to support a NVMe hot add event. In certain configurations, an insufficient amount of resources would have been reserved and a reboot would have been required to detect the presence of the newly added drive.

Addressed an issue where the system would not boot to a USB drive when a non-bootable (non-formatted) drive was also present in the system. This issue only impacts systems configured in Legacy Boot Mode.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where configuring memory to run at 2x refresh rate would still actually operate memory at 1x refresh rate. This issue was introduced with the v2.00 System ROM and did not impact earlier versions of the System ROM. This issue is not unique to HPE servers.

Addressed an issue where the NVMe PCIe Resource Padding option in BIOS/Platform Configuration (RBSU) would not properly allocated sufficient resources to support a NVMe hot add event. In certain configurations, an insufficient amount of resources would have been reserved and a reboot would have been required to detect the presence of the newly added drive.

Addressed an issue where the system would not boot to a USB drive when a non-bootable (non-formatted) drive was also present in the system. This issue only impacts systems configured in Legacy Boot Mode.

Known Issues:

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

修正された問題点:

インテル XeonスケーラブルパフォーマンスBronzeおよびSilverプロセッサーで、システムで訂正不可能なメモリエラーまたは起動時のメモリトレーニングの問題が発生する可能性がある問題に対処しました。この問題はシステムROMバージョン2.00で最初に発生したものです。メモリに関する問題が発生しているお客様は、コンポーネントを交換する前に、このバージョンのシステムROMに直ちにアップデートすることを推奨します。この問題は、HPEサーバーに固有のものではありません。

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may experience a higher rate of Uncorrectable Memory errors or boot time Memory training issues with Intel Xeon Scalable Performance Bronze and Silver processors. This issue was first introduced with System ROM version 2.00. HPE recommends that any customer experiencing a memory issue immediately update to this version of the system ROM before replacing any components. This issue is not unique to HPE servers.

Known Issues:

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

• Fixed an issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode

Fixes submitted in version 14.24.9006:

• The HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter was not linking in AUX power mode.

Fixes submitted in version 16.24.9000 :

• Fixed an Active Health System(AHS) packet over PCIe interface issue

• Fixed an issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode

Fixes submitted in version 14.24.9006:

• The HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter was not linking in AUX power mode.

Fixes submitted in version 16.24.9000 :

• Fixed an Active Health System(AHS) packet over PCIe interface issue

• ファームウェアがalink_downイベントを検出することを妨げることで、IBボンドインターフェイスがフェイルオーバーモードになることを妨げる問題を修正しました。

バージョン12.23.8036 で提出された修正：

• tx_clk_phaseロックメカニズムを改善することにより、フェーズロックループ (PLL)のチューニングの問題を修正しました。
• リンク レイヤ検出プロトコル (LLDP): 一旦新しいアドレスを受信したら、マネジメントMAC 0のアドレスを削除
• ポートIDをポートのMACになるように設定します

バージョン14.23.8052で提出された修正：

• HPE Ethernet 25Gb 2ポート640FLR-SFP28アダプターがAUX電源モードでリンクされていません。

バージョン16.23.8036 で提出された修正：

• PCIeインターフェイス上のActive Health System (AHS)パケットの問題を修正しました

• Fixed an issue that prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode

Fixes submitted in version 12.23.8036 :

• Fixed a Phase-Locked Loop(PLL) tuning issue by improving the tx_clk_phase lock mechanism.
• The Link Layer Discovery Protocol(LLDP): Removed management MAC 0 address once a new address is received
• Set the Port ID to be the MAC of the port

Fixes submitted in version 14.23.8052:

• The HPE Ethernet 25Gb 2-port 640FLR-SFP28 Adapter was not linking in AUX power mode.

Fixes submitted in version 16.23.8036 :

• Fixed an Active Health System(AHS) packet over PCIe interface issue

- LinuxまたはESX上でhpiloドライバーを使用している場合、OSの例外またはメモリの破損につながる可能性があるシステムメモリ解放後の

   ファームウェア使用の可能性を修正しました。  Windows上では問題ありません。

 - 両方が100フルデュプレックスに設定されている場合、iLO 5がスイッチに接続できるように修正してください。

 - "ilorest -d serverlogs --selectlog = IML --clearlog rc 255"が成功しても失敗しないように

   REST呼び出しを修正しました。

- ログに記録されるべきではないときに"電力容量しきい値を超えた"ために誤ってIMLイベント

   ログ記録する問題を修正しました。

 - "アジア/台北"のタイムゾーン文字列を"北京、重慶、香港、ウルムチ、台北、パース"に変更

- 重要なIMLイベントについてのみ、リモートサポートタイプ1000のイベントを送信してください。

セキュリティの修正:

- HPESBHF03917

  最新のセキュリティ情報と、このバージョンで解決された脆弱性については、次のサイトを参照してください：

  https://support.hpe.com/hpesc/public/home

- Fix for potential firmware use of system memory after free, which could lead to an OS exception or

   memory corruption under Linux or ESX when using hpilo driver.  It was not an issue for Windows.

 - Fix so iLO 5 can connect to switch when both are set to 100 Full Duplex.

 - Fixed REST call so that "ilorest -d serverlogs --selectlog=IML --clearlog rc 255" does not fail when

   it should succeed.

- Fixed problem with erroneously logging an IML event for "exceeding power capacity threshold" when

   it should not be logged.

 - Modified time zone string for "Asia/Taipei" to "Beijing, Chongqing, Hong Kong, Urumqi, Taipei, Perth"

- Only send Remote Support type 1000 events for Critical IML events when they should be sent

SECURITY FIXES:

- HPESBHF03917

  For the latest security bulletins and vulnerabilities addressed in this version, please visit:

  https://support.hpe.com/hpesc/public/home

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

• Addressed an issue where Onboard Administrator is not reachable when the port speed changes from 100M to 1000M in auto-negotiation mode. This issue is described by Customer Advisory : https://support.hpe.com/hpsc/doc/public/display?sp4ts.oid=1844065&docLocale=en_US&docId=emr_na-c04866545
• Addressed an issue where the DHCPv6 service does not start after an Onboard Administrator reboots causing it to reboot again after 15 minutes.
• Addressed an issue related to ssl protocols enable or disable in the Onboard Administrator Command Line Interface (CLI) where proper error message is displayed. When the password entered is less than eight characters, the ambient temperature of the BL460c Gen10 blade is not displayed.
•  Addressed issues in Onboard Administrator GUI pages related to:
  1. Power management

  2. Front view display of BL460c Gen10 blade

  3. Login feature into linked enclosure and Two-factor authentication

• Addressed an issue where syslog messages were not added for dynamic dns setting and LDAP group access changes.
• Addressed an issue where SNMP GET for Onboard Administrator system description OID displays a wrong value.
• Addressed an issue where Blade Switch 6125G firmware version is not displayed after rebooting OA.
• Addressed an issue where Onboard Administrator responds to internal private IP ping requests from management interface.
• Addressed the issue of delay in the powering of the blades after an enclosure power cycle in a VCM managed enclosure.
• Addressed an issue in the SNMP where power supply OK traps are not sent out after an enclosure power cycle.
• Addressed the issues related to user certificate usage in the Onboard Administrator where the same certificate cannot be used for multiple users and checking the syntax of IPv6 address if used in the certificate.
• Addressed the issues present in the previous versions of the Onboard Administrator online help.
• Addressed an issue in FIPS ON mode where Onboard Administrator CLI will display information about the password requirements when an invalid password in entered by the user.
• Fixed an issue related to ambient temperature display of Gen10 blades in Command Line Interface (CLI).
• Fixed an issue in First Time Setup Wizard page in GUI where in FIPS ON mode, user will not able to set DEBUG to ON.
• Addressed an issue where messages are not logged in syslog when Device and Interconnects bay access are updated for a LDAP group.
• Fixed an issue related to Blade part number display in OA GUI and CLI.

Security

  The following security vulnerabilities are fixed:

• CVE-2018-0732- Addressed the issue where the possibility of a malicious server sending a large prime value to the client from DH (E) based ciphersuite during the key agreement in a TLS handshake resulting in the client to take a long time to generate a key with the prime and exploited in a Denial Of Service attack.
• CVE-2018-0737- Addressed the issue of vulnerability of the OpenSSL RSA Key generation algorithm to the cache timing side channel attack.

Issues and workarounds

Browsers

• OA GUI is not accessible in Chrome versions 43.0.2357.10 to 44.0.2383.The issue was caused by a “regression” in Chrome (or WebKit). Customers should use an alternative browser like Firefox or Internet Explorer or try a different version of Chrome.
• SSO-to-iLO connection from the OA using an iLO host name fails with Microsoft Internet Explorer11 on Windows 8. On a Windows 8 system with Internet Explorer 10 or Internet Explorer 11, if the OA web GUI session is loaded using a host name instead of an IP address, an attempt to open an iLO window using SSO from the OA web GUI might result in the iLO page loading in the OA web GUI window instead of the intended new window. This issue was determined to be a bug in Internet Explorer and is expected to be fixed in a future release or update for Internet Explorer. To work around this issue, either use an IP address to load the OA Web GUI, or turn off Protected Mode for the appropriate zone in Internet Explorer’s settings. This issue occurs only on Internet Explorer browsers.

FIPS

Certificates smaller than 2048 bits in size are not compliant with FIPS requirements as enforced by the OA firmware starting with OA 4.20. When the OA running OA firmware version 4.40 or greater is operating in FIPS Mode ON/DEBUG and is configured with a 1024-bit LDAP certificate that was installed when running a previous version of OA firmware, FIPS Mode ON/DEBUG is considered to be operating in a degraded state due to the presence of the non-compliant certificate. While operating in this FIPS-Degraded Mode operational state, attempts to set FIPS Mode OFF from the OA GUI Network Access>FIPS tab will fail and show the error message The selected FIPS mode is already enabled. When the non-compliant certificate is removed, the FIPS-Degraded operational status is cleared, FIPS Mode can then be successfully set to OFF from the GUI interface. Note that the OA CLI command SET FIPS MODE OFF can be successfully used to set FIPS Mode OFF even with non-compliant 1024-bit LDAP certificates installed in the OA.

IRC

Unable to open .net IRC console for Gen10 Blades, Gen9 Blades also have the same issue. The Java applet and Webstart however, loads but the virtual media mounting fails. The work around is to launch the IRC through IRC Application (HPE Lights-Out Stand Alone Remote Console) which is installed on terminal client.

EFM

To use EFM on Gen 10 Blades, please select options/filters “Make Bootable ISO file” and “Enclosure Firmware Management” while creating custom SPP ISO on HPE SUM 8.0.0. Please refer to HPE SUM 8.0.0 User guide for further details.

CAC

• In the CAC mode SSH, Telnet and XML Reply protocols will be disabled.
• Linked enclosure login will not work if the linked enclosure in CAC mode.
• If accurate Service account details are not provided, LDAP user login with certificate will fail.
• It is highly recommended to establish a recovery plan before getting started with CAC.  If something goes wrong with the OA configuration, the OA may be recovered through the serial port or Insight Display panel and USB KEY. Both methods require physical access to the OA.  However, if an LCD PIN has been configured (and forgotten) and local accounts have been disabled or CAC has been incorrectly configured then, the only way to recover is through a serial port. The two most common situations where OA recovery is needed are when LDAP has been configured incorrectly with local accounts disabled or when CAC has been configured without certificate access.

Configurable SSH Port Number                                               

If a Standby OA is running firmware version less than 4.85 and it is updated to firmware version greater than or equal to 4.85 using synchronize firmware feature from Active OA, after the firmware update and reboot of the Standby OA, SSH port will not open in the configured port number. The work around is to reboot the Standby OA and SSH port will open in the configured port in next boot. This issue will not occur in the case where SSH port is configured to default port 22 in the Active OA.

• Addressed an issue where Onboard Administrator is not reachable when the port speed changes from 100M to 1000M in auto-negotiation mode. This issue is described by Customer Advisory : https://support.hpe.com/hpsc/doc/public/display?sp4ts.oid=1844065&docLocale=en_US&docId=emr_na-c04866545
• Addressed an issue where the DHCPv6 service does not start after an Onboard Administrator reboots causing it to reboot again after 15 minutes.
• Addressed an issue related to ssl protocols enable or disable in the Onboard Administrator Command Line Interface (CLI) where proper error message is displayed. When the password entered is less than eight characters, the ambient temperature of the BL460c Gen10 blade is not displayed.
•  Addressed issues in Onboard Administrator GUI pages related to:
  1. Power management

  2. Front view display of BL460c Gen10 blade

  3. Login feature into linked enclosure and Two-factor authentication

• Addressed an issue where syslog messages were not added for dynamic dns setting and LDAP group access changes.
• Addressed an issue where SNMP GET for Onboard Administrator system description OID displays a wrong value.
• Addressed an issue where Blade Switch 6125G firmware version is not displayed after rebooting OA.
• Addressed an issue where Onboard Administrator responds to internal private IP ping requests from management interface.
• Addressed the issue of delay in the powering of the blades after an enclosure power cycle in a VCM managed enclosure.
• Addressed an issue in the SNMP where power supply OK traps are not sent out after an enclosure power cycle.
• Addressed the issues related to user certificate usage in the Onboard Administrator where the same certificate cannot be used for multiple users and checking the syntax of IPv6 address if used in the certificate.
• Addressed the issues present in the previous versions of the Onboard Administrator online help.
• Addressed an issue in FIPS ON mode where Onboard Administrator CLI will display information about the password requirements when an invalid password in entered by the user.
• Fixed an issue related to ambient temperature display of Gen10 blades in Command Line Interface (CLI).
• Fixed an issue in First Time Setup Wizard page in GUI where in FIPS ON mode, user will not able to set DEBUG to ON.
• Addressed an issue where messages are not logged in syslog when Device and Interconnects bay access are updated for a LDAP group.
• Fixed an issue related to Blade part number display in OA GUI and CLI.

Security

  The following security vulnerabilities are fixed:

• CVE-2018-0732- Addressed the issue where the possibility of a malicious server sending a large prime value to the client from DH (E) based ciphersuite during the key agreement in a TLS handshake resulting in the client to take a long time to generate a key with the prime and exploited in a Denial Of Service attack.
• CVE-2018-0737- Addressed the issue of vulnerability of the OpenSSL RSA Key generation algorithm to the cache timing side channel attack.

Issues and workarounds

Browsers

• OA GUI is not accessible in Chrome versions 43.0.2357.10 to 44.0.2383.The issue was caused by a “regression” in Chrome (or WebKit). Customers should use an alternative browser like Firefox or Internet Explorer or try a different version of Chrome.
• SSO-to-iLO connection from the OA using an iLO host name fails with Microsoft Internet Explorer11 on Windows 8. On a Windows 8 system with Internet Explorer 10 or Internet Explorer 11, if the OA web GUI session is loaded using a host name instead of an IP address, an attempt to open an iLO window using SSO from the OA web GUI might result in the iLO page loading in the OA web GUI window instead of the intended new window. This issue was determined to be a bug in Internet Explorer and is expected to be fixed in a future release or update for Internet Explorer. To work around this issue, either use an IP address to load the OA Web GUI, or turn off Protected Mode for the appropriate zone in Internet Explorer’s settings. This issue occurs only on Internet Explorer browsers.

FIPS

Certificates smaller than 2048 bits in size are not compliant with FIPS requirements as enforced by the OA firmware starting with OA 4.20. When the OA running OA firmware version 4.40 or greater is operating in FIPS Mode ON/DEBUG and is configured with a 1024-bit LDAP certificate that was installed when running a previous version of OA firmware, FIPS Mode ON/DEBUG is considered to be operating in a degraded state due to the presence of the non-compliant certificate. While operating in this FIPS-Degraded Mode operational state, attempts to set FIPS Mode OFF from the OA GUI Network Access>FIPS tab will fail and show the error message The selected FIPS mode is already enabled. When the non-compliant certificate is removed, the FIPS-Degraded operational status is cleared, FIPS Mode can then be successfully set to OFF from the GUI interface. Note that the OA CLI command SET FIPS MODE OFF can be successfully used to set FIPS Mode OFF even with non-compliant 1024-bit LDAP certificates installed in the OA.

IRC

Unable to open .net IRC console for Gen10 Blades, Gen9 Blades also have the same issue. The Java applet and Webstart however, loads but the virtual media mounting fails. The work around is to launch the IRC through IRC Application (HPE Lights-Out Stand Alone Remote Console) which is installed on terminal client.

EFM

To use EFM on Gen 10 Blades, please select options/filters “Make Bootable ISO file” and “Enclosure Firmware Management” while creating custom SPP ISO on HPE SUM 8.0.0. Please refer to HPE SUM 8.0.0 User guide for further details.

CAC

• In the CAC mode SSH, Telnet and XML Reply protocols will be disabled.
• Linked enclosure login will not work if the linked enclosure in CAC mode.
• If accurate Service account details are not provided, LDAP user login with certificate will fail.
• It is highly recommended to establish a recovery plan before getting started with CAC.  If something goes wrong with the OA configuration, the OA may be recovered through the serial port or Insight Display panel and USB KEY. Both methods require physical access to the OA.  However, if an LCD PIN has been configured (and forgotten) and local accounts have been disabled or CAC has been incorrectly configured then, the only way to recover is through a serial port. The two most common situations where OA recovery is needed are when LDAP has been configured incorrectly with local accounts disabled or when CAC has been configured without certificate access.

Configurable SSH Port Number                                               

If a Standby OA is running firmware version less than 4.85 and it is updated to firmware version greater than or equal to 4.85 using synchronize firmware feature from Active OA, after the firmware update and reboot of the Standby OA, SSH port will not open in the configured port number. The work around is to reboot the Standby OA and SSH port will open in the configured port in next boot. This issue will not occur in the case where SSH port is configured to default port 22 in the Active OA.

• Onboard Administrator のフェイルオーバー後に送信されなかった SNMPトラップ cpqRackEnclosureManagerLinkUpの問題に対処します。

• Onboard Administratorの以前のバージョンに見られたオンラインヘルプのコンテンツの問題を解決します。

セキュリティ

   以下のセキュリティの脆弱性が修正されました：

• CVE-2017-8105 - バッファ オーバーフローにより起こるメモリ破損の脆弱性に対処しました。

• CVE-2016-10244 – リモートの攻撃者が細工されたファイルを介してサービス拒否を引き起こす可能性のある脆弱性に対処しました。

問題点および解決策

ブラウザー

• OA GUIはChromeのバージョン43.0.2357.10から44.0.2383ではアクセスできません。この問題は、Chrome（またはWebKit）の"回帰"によって発生しています。FirefoxやInternet Explorerなどの代わりのブラウザーを使用するか、別のバージョンのChromeを試す必要があります。
• iLOホスト名を使用したOAからのSSO-to-iLO接続は、Windows 8のMicrosoft Internet Explorer 11で失敗します。Internet Explorer 10またはInternet Explorer 11を備えたWindows 8システムでは、OA Web GUIセッションがIPアドレスの代わりにホスト名を使用してロードされている場合、OA Web GUIからSSOを使用してiLOウィンドウを開こうとすると、目的の新しいウィンドウではなくOA Web GUIウィンドウにiLOページが読み込まれる可能性があります。この問題はInternet Explorerのバグであると判断され、Internet Explorerの将来のリリースまたはアップデートで修正される予定です。この問題を回避するには、IPアドレスを使用してOA Web GUIをロードするか、Internet Explorerの設定で適切なゾーンの保護モードをオフにします。この問題はInternet Explorerブラウザーのみで発生します。

FIPS

2048ビット未満のサイズの証明書は、OA 4.20以降のOAファームウェアによって強制されるFIPS要件に準拠していません。OAファームウェアバージョン4.40以降を実行しているOAがFIPSモードON/DEBUGで動作し、以前のバージョンのOAファームウェアを実行しているときにインストールされた1024ビットのLDAP証明書で構成されている場合、非準拠の証明書が存在するためにFIPSモードON/DEBUGは劣化状態で動作しているとみなされます。このFIPS-劣化モードで動作している間に、OA GUIのネットワークアクセス>FIPSタブからFIPSモードをオフに設定しようとすると失敗し、選択したFIPSモードが既に有効になっているというエラーメッセージが表示されます。非準拠の証明書が削除されると、FIPS-劣化モードの動作ステータスはクリアされ、FIPSモードはGUIインターフェイスから正常にOFFに設定できます。OA CLIコマンドSET FIPS MODE OFFを使用すると、OAにインストールされている非準拠の1024ビットLDAP証明書を使用しても、FIPSモードをオフに設定できます。

IRC

Gen10 Blade用の.net IRCコンソールを開くことができない、Gen9 Bladeも同じ問題があります。JavaアプレットとWebstartはロードされますが、仮想メディアのマウントは失敗します。回避策として、ターミナルクライアントにインストールされているIRCアプリケーション（HP Lights-Outスタンドアロンリモートコンソール）を使用してIRCを起動することです。

EFM

Gen 10 BladeでEFMを使用するには、HPSUM 8.0.0でカスタムSPP ISOを作成する際にオプション/フィルター"Make Bootable ISO file"と"Enclosure Firmware Management"を選択してください。詳細については、HPSUM 8.0.0ユーザーガイドを参照してください。

CAC

• CACモードのSSHでは、TelnetおよびXML応答プロトコルは無効になります。
• リンクされたエンクロージャーがCACモードになっている場合、リンクされたエンクロージャーのログインは動作しません。
• サービスアカウントの詳細を正確に指定しないと、証明書を使用したLDAPユーザーのログインは失敗します。
• CACの使用を開始する前にリカバリプランを立てることを強くお勧めします。  OA設定で問題が起こった場合、OAをシリアルポートまたはInsight DisplayパネルおよびUSB KEYからリカバリできる場合があります。いずれの方法もOAへの物理アクセスが必要です。  ただし、LCD PINが設定されている（または忘れた）場合、およびローカルアカウントが無効になっているかCACが正しく設定されていない場合、リカバリする唯一の方法はシリアルポート経由です。OAの復旧が必要な最も一般的な状況を2つ挙げると、LDAPが無効なローカルアカウントで誤って設定されている場合と、CACが証明書にアクセスしないよう設定されている場合です。

設定可能なSSHポート番号                                               

スタンバイOAが4.85未満のファームウェアバージョンを実行していて、アクティブOAのファームウェア同期機能を使用してファームウェアバージョンが4.85以上に更新した場合、ファームウェアのアップデートおよびスタンバイOAの再起動後、SSHポートは構成されたポート番号で開きません。回避策は、スタンバイOAを再起動することです。SSHポートは、次回起動時に設定されたポートで開きます。SSH ポートがアクティブOAのデフォルトポート22で構成されている場合は、この問題が発生しません。

• Addressed an issue where SNMP trap cpqRackEnclosureManagerLinkUp was not sent after an Onboard Administrator failover.

• Addressed online help content issues seen in the previous version of Onboard Administrator.

Security

   The following security vulnerabilities were fixed:

• CVE-2017-8105 - Addressed a memory corruption vulnerability caused by a buffer overflow.

• CVE-2016-10244 – Addressed a vulnerability which might allow a remote attacker to cause denial-of-service via a crafted file.

Issues and workarounds

Browsers

• OA GUI is not accessible in Chrome versions 43.0.2357.10 to 44.0.2383.The issue was caused by a “regression” in Chrome (or WebKit). Customers should use an alternative browser like Firefox or Internet Explorer or try a different version of Chrome.
• SSO-to-iLO connection from the OA using an iLO host name fails with Microsoft Internet Explorer11 on Windows 8. On a Windows 8 system with Internet Explorer 10 or Internet Explorer 11, if the OA web GUI session is loaded using a host name instead of an IP address, an attempt to open an iLO window using SSO from the OA web GUI might result in the iLO page loading in the OA web GUI window instead of the intended new window. This issue was determined to be a bug in Internet Explorer and is expected to be fixed in a future release or update for Internet Explorer. To work around this issue, either use an IP address to load the OA Web GUI, or turn off Protected Mode for the appropriate zone in Internet Explorer’s settings. This issue occurs only on Internet Explorer browsers.

FIPS

Certificates smaller than 2048 bits in size are not compliant with FIPS requirements as enforced by the OA firmware starting with OA 4.20. When the OA running OA firmware version 4.40 or greater is operating in FIPS Mode ON/DEBUG and is configured with a 1024-bit LDAP certificate that was installed when running a previous version of OA firmware, FIPS Mode ON/DEBUG is considered to be operating in a degraded state due to the presence of the non-compliant certificate. While operating in this FIPS-Degraded Mode operational state, attempts to set FIPS Mode OFF from the OA GUI Network Access>FIPS tab will fail and show the error message The selected FIPS mode is already enabled. When the non-compliant certificate is removed, the FIPS-Degraded operational status is cleared, FIPS Mode can then be successfully set to OFF from the GUI interface. Note that the OA CLI command SET FIPS MODE OFF can be successfully used to set FIPS Mode OFF even with non-compliant 1024-bit LDAP certificates installed in the OA.

IRC

Unable to open .net IRC console for Gen10 Blades, Gen9 Blades also have the same issue. The Java applet and Webstart however, loads but the virtual media mounting fails. The work around is to launch the IRC through IRC Application (HP Lights-Out Stand Alone Remote Console) which is installed on terminal client.

EFM

To use EFM on Gen 10 Blades, please select options/filters “Make Bootable ISO file” and “Enclosure Firmware Management” while creating custom SPP ISO on HPSUM 8.0.0. Please refer to HPSUM 8.0.0 User guide for further details.

CAC

• In the CAC mode SSH, Telnet and XML Reply protocols will be disabled.
• Linked enclosure login will not work if the linked enclosure in CAC mode.
• If accurate Service account details are not provided, LDAP user login with certificate will fail.
• It is highly recommended to establish a recovery plan before getting started with CAC.  If something goes wrong with the OA configuration, the OA may be recovered through the serial port or Insight Display panel and USB KEY. Both methods require physical access to the OA.  However, if an LCD PIN has been configured (and forgotten) and local accounts have been disabled or CAC has been incorrectly configured then, the only way to recover is through a serial port. The two most common situations where OA recovery is needed are when LDAP has been configured incorrectly with local accounts disabled or when CAC has been configured without certificate access.

Configurable SSH Port Number                                               

If a Standby OA is running firmware version less than 4.85 and it is updated to firmware version greater than or equal to 4.85 using synchronize firmware feature from Active OA, after the firmware update and reboot of the Standby OA, SSH port will not open in the configured port number. The work around is to reboot the Standby OA and SSH port will open in the configured port in next boot. This issue will not occur in the case where SSH port is configured to default port 22 in the Active OA.

Ver. 1.60(B) contains updates to the component packaging and is functionally equivalent to ver. 1.60. It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the firmware to version 1.60.

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

Ver. 1.60(B) contains updates to the component packaging and is functionally equivalent to ver. 1.60. It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the firmware to version 1.60.

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for Variant 2 of the Side Channel Analysis vulnerability, also known as Spectre. The revision of the microcode included in this System ROM does NOT have issues with more frequent reboots and unpredictable system behavior which impacted the previous Intel microcode which was part of the Spectre Variant 2 mitigation. Additional information is available from Intel’s Security Exploit Newsroom, https://newsroom.intel.com/press-kits/security-exploits-intel-products/.

Firmware Dependencies:

None

Problems Fixed:

Updated the Intel processor microcode to the latest version.

Known Issues:

None

Ver. 1.0.9(J) contains updates to the component packaging and is functionally equivalent to ver. 1.0.9. It is not necessary to upgrade with Revision J if a previous component Revision was used to upgrade the firmware to version 1.0.9.

Firmware Dependencies:

None

Problems Fixed:

Addresses an issue in which the minimum power capping value was incorrectly being calculated on certain systems. This fix increases the accuracy of the minimum capping value set during POST.

Known Issues:

None

Ver. 1.0.9(J) contains updates to the component packaging and is functionally equivalent to ver. 1.0.9. It is not necessary to upgrade with Revision J if a previous component Revision was used to upgrade the firmware to version 1.0.9.

Firmware Dependencies:

None

Problems Fixed:

Addresses an issue in which the minimum power capping value was incorrectly being calculated on certain systems. This fix increases the accuracy of the minimum capping value set during POST.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Sending Work Requests (WRs) with multiple entries where the first entry was less than 18 bytes used to fail.
• When the interface was down, ethtool counters ceased to increase. As a result, RoCE traffic counters were not always incremented.
• Compilation errors of MLNX_OFED over kernel when CONFIG_PTP_1588_CLOCK parameter was not set.
• System used to hang when trying to allocate multiple device memory buffers from different processes simultaneously.

• Sending Work Requests (WRs) with multiple entries where the first entry was less than 18 bytes used to fail.
• When the interface was down, ethtool counters ceased to increase. As a result, RoCE traffic counters were not always incremented.
• Compilation errors of MLNX_OFED over kernel when CONFIG_PTP_1588_CLOCK parameter was not set.
• System used to hang when trying to allocate multiple device memory buffers from different processes simultaneously.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Added a fix for changing the order of write buffer modes in the flash engine.

Firmware version HPG3 addresses the following issues:

• Corrects the potential for drives to become unresponsive. For details about this issue, refer to HPE Customer Bulletin: HPE ​Solid ​State ​Drives ​(SSD) ​- ​SSD ​FIRMWARE ​UPGRADE ​REQUIRED ​to ​Prevent ​a ​Higher ​Than ​Expected ​Failure ​Rate ​Noted ​on ​Certain ​Model ​SSD ​Drives: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00048133en_us.   
• Improves drive reliability by including the latest firmware maintenance updates.
   
  After HPG3 firmware is downloaded to the drive, the new HPG3 firmware will be active on the drive. The new drive bootloader code will be activated after the next drive power cycle.

• Added a fix for changing the order of write buffer modes in the flash engine.

Firmware version HPG3 addresses the following issues:

• Corrects the potential for drives to become unresponsive. For details about this issue, refer to HPE Customer Bulletin: HPE ​Solid ​State ​Drives ​(SSD) ​- ​SSD ​FIRMWARE ​UPGRADE ​REQUIRED ​to ​Prevent ​a ​Higher ​Than ​Expected ​Failure ​Rate ​Noted ​on ​Certain ​Model ​SSD ​Drives: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00048133en_us.   
• Improves drive reliability by including the latest firmware maintenance updates.
   
  After HPG3 firmware is downloaded to the drive, the new HPG3 firmware will be active on the drive. The new drive bootloader code will be activated after the next drive power cycle.

Transceiver with part number 5700-0077 requires a minimum of 10ms after a write operation before reading it back. But the current Firmware is not waiting long enough, manifests as an intermittently incomplete to connect to Fabric

For more details please go through the document titled "HPE StoreFabric Host Bus Adapters - During A Server Power-On Sequence, A SN1100Q Or SN1600Q Fibre Channel Adapter With A Specific 16GB Transceiver Will Intermittently Fail To Connect To All FC Switches At Both The UEFI And OS Levels" at the following link:
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00078768en_us

Transceiver with part number 5700-0077 requires a minimum of 10ms after a write operation before reading it back. But the current Firmware is not waiting long enough, manifests as an intermittently incomplete to connect to Fabric

For more details please go through the document titled "HPE StoreFabric Host Bus Adapters - During A Server Power-On Sequence, A SN1100Q Or SN1600Q Fibre Channel Adapter With A Specific 16GB Transceiver Will Intermittently Fail To Connect To All FC Switches At Both The UEFI And OS Levels" at the following link:
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00078768en_us

• Hisense SFPは、書き込み操作から読み取り操作の間に最低10msを必要とします。しかし、現在のファームウェアは十分に長く待機しておらず、ファブリックへの接続が断続的に不完全であることを示しています

• Hisense SFP requires a minimum of 10ms after a write operation before reading it back. But the current Firmware is not waiting long enough, manifests as an intermittently incomplete to connect to Fabric

• mlxconfig tool reported all possible expansion ROM images, instead of presenting only the existing images.
• Modifying VMQoS rate limiter parameters during traffic caused transmission failure.
• Aligned the default tuning type in PHY TEST MODE to the device protocol.
• When a device is operating in Safe Mode state, and the user issues the mlxfwreset command, the device might fail to come-up correctly after the reset.
  Note: Do not run mlxfwreset when operating in a Safe Mode state.
• Fixed an issue related to PCIe "Surprise link down" event reporting capability.
• Fixed an issue that resulted in the link partner experiencing false active linkup when plugging in a base-T cable to a closed port.

Fixes in version 12.24.1000:

• Fixed an issue that caused the max_qp_retry_freq_exceeded counter (including a CQE with error syndrome 0x97, and the QP moving to error state) to be activated only after exceeding the NIC Vport context max_qp_retry_limit, and not when reaching it.

Fixes in version 16.24.1000:

• PCIe bifurcation issue.
• Deadlock in RX related to the “send-invalidate” flow, resulted in RX getting stuck.
• Rare errors in RX that resulted in double completion.

• mlxconfig tool reported all possible expansion ROM images, instead of presenting only the existing images.
• Modifying VMQoS rate limiter parameters during traffic caused transmission failure.
• Aligned the default tuning type in PHY TEST MODE to the device protocol.
• When a device is operating in Safe Mode state, and the user issues the mlxfwreset command, the device might fail to come-up correctly after the reset.
  Note: Do not run mlxfwreset when operating in a Safe Mode state.
• Fixed an issue related to PCIe "Surprise link down" event reporting capability.
• Fixed an issue that resulted in the link partner experiencing false active linkup when plugging in a base-T cable to a closed port.

Fixes in version 12.24.1000:

• Fixed an issue that caused the max_qp_retry_freq_exceeded counter (including a CQE with error syndrome 0x97, and the QP moving to error state) to be activated only after exceeding the NIC Vport context max_qp_retry_limit, and not when reaching it.

Fixes in version 16.24.1000:

• PCIe bifurcation issue.
• Deadlock in RX related to the “send-invalidate” flow, resulted in RX getting stuck.
• Rare errors in RX that resulted in double completion.

• まれに、受信側のエレクトリックアイ幅が狭い場合に、10^-12よりも低いBERでリンクが発生することがあります。
• LROタイムアウト構成が定義済みの静的な値ではなく、TLV構成から取得されるようになりました。
• モジュール温度の読み取りが-40°Cよりも低い場合と125°Cよりも高い場合に無視するフィルターを追加しました。
• Ackがメモリにスキャッターことなく送信するのを防ぐために、高速切断フローの一環としてvportをクローズしました。
• PERST#のアサーション解除が特定の重要な期間に到着した、まれなシナリオが処理されました。
• 温度正規化関数の計算問題。純粋整数ではないケーブルゲインが考慮されるようになりました。
• 応答で異なる構造の原因になっていたASNのオブジェクト0x8の解析。
• HCAがFLRを実行している間、MSIX割り込みが失われた問題が処理されました。
• ファームウェアのブートプロセスとPCIeからのMSIXアクセスの間で競合状態が発生し、これによってMSIXベクトルへの書き込みが失われた問題が修正されました。

• In rare cases, where the width of the receiver's electrical eye is narrow, the link might raise with BER lower than 10^-12.
• LRO timeout configuration is now taken from the TLV configuration instead of the static defined values.
• Added a filter to ignore module temperature reads below -40C and above 125C.
• Closed the vport as part of the fast teardown flow, to prevent Ack to be sent without been scatter to memory.
• A rare scenario where the PERST# de-assertion arrived at a specific critical time period was handled.
• Temperature normalization function calculation issue. Now the cable gain that is not pure integer is taken into account.
• The parser of object 0x8 in ASN that caused different structure in response.
• An issue that caused MSIX interrupt lost while the HCA performed an FLR was handled.
• An issue that caused a race condition between the firmware boot process and the MSIX access from the PCIe, which resulted in lost writes into the MSIX vector was fixed.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• ホットプラグ再起動中およびI/Oシステムが重い状態では、チェックサムエラーが返されることがあります。
• システムがI/Oの完了に失敗したときにシステムがPurple Screen Of Death（PSOD）を返す原因となるデータの一貫性の問題が発生する可能性があります。 詳しくは、カスタマーアドバイザリa00071158en_usを参照してください。
• TMF要求がタイムアウトしたときにPSODの可能性
• タスク管理機能（TMF）で障害が発生するときにI/Oタグが使い果たされる可能性がある問題を修正しました。
• Lunリセットがサービス応答障害で完了するときにPSODの可能性
• AIO TaskManagementの誤ったキュー選択ロジックによるPSODの可能性
• pqiリセット中に未処理のIOがあるためにコントローラーが応答を停止することがありました。
• デバイス検出中に問い合わせコマンドが失敗する可能性があります
• VMware vSAN環境での使用方法の詳細、およびSynergy環境におけるSynergy Core SPPの最小要件については、カスタマーアドバイザリa00071158en_usを参照してください。

• During hotplug reinsertion and while under heavy I/O system can return a checksum error.
• Customer could encounter a data coherency issue that will cause the system to return a Purple Screen Of Death (PSOD) when system fails to complete I/O's. Please reference Customer Advisory a00071158en_us for more details.
• Possible PSOD when a TMF request timed out
• Fixed an issue where I/O tags could get exhausted when Task Management Function (TMF) fails.
• Possible PSOD while Lun reset completes with service response failure
• Possible PSOD due to incorrect queue selection logic for AIO TaskManagement
• Controller could stop responding due to outstanding IO during pqi reset.
• Inquiring command could potentially fail during device discovery
• Refer to the Customer Advisory  a00071158en_us for details for use in the VMware vSAN environment as well as minimal Synergy Core SPP requirements for Synergy environments.

• ホットプラグ再起動中およびI/Oシステムが重い状態では、チェックサムエラーが返されることがあります。
• システムがI/Oの完了に失敗したときにシステムがPurple Screen Of Death（PSOD）を返す原因となるデータの一貫性の問題が発生する可能性があります。
• TMF要求がタイムアウトしたときにPSODの可能性
• タスク管理機能（TMF）で障害が発生するときにI/Oタグが使い果たされる可能性がある問題を修正しました。
• Lunリセットがサービス応答障害で完了するときにPSODの可能性
• AIO TaskManagementの誤ったキュー選択ロジックによるPSODの可能性
• pqiリセット中に未処理のIOがあるためにコントローラーが応答を停止することがありました。
• デバイス検出中に問い合わせコマンドが失敗する可能性があります

• During hotplug reinsertion and while under heavy I/O system can return a checksum error.
• Customer could encounter a data coherency issue that will cause the system to return a Purple Screen Of Death (PSOD) when system fails to complete I/O's
• Possible PSOD when a TMF request timed out
• Fixed an issue where I/O tags could get exhausted when Task Management Function (TMF) fails.
• Possible PSOD while Lun reset completes with service response failure
• Possible PSOD due to incorrect queue selection logic for AIO TaskManagement
• Controller could stop responding due to outstanding IO during pqi reset.
• Inquiring command could potentially fail during device discovery

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

既知の問題点:

なし

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

This issue is only encounter when upgrading to version 2018.10.18 (5.5.0.66-1). All other versions are not affected.

This issue is only encounter when upgrading to version 2018.10.18 (5.5.0.66-1). All other versions are not affected.

• Enabled-ClusterS2Dコマンドは、D3610ディスクエンクロージャー内のSATAドライブ上で実行すると正常に完了するようになりました。

このファームウェアに関する修正のリスト、拡張、既知の問題および回避方法については、リリースノートを参照してください。

• The Enabled-ClusterS2D command now completes successfully when executed on a SATA drive within a D3610 disk enclosure.

Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

• Revビルド1.11.000から0412.000へのアップグレード中のTLB例外を修正しました。

• NVRAMタグ（製品名）がないためエラーコード0xB1がコンソールに表示されて失敗するエキスパンダーのブートストラップタスクを修正しました

• Enabled-ClusterS2DコマンドがD3610のSATAドライブで完了しない

このファームウェアに関する修正のリスト、拡張、既知の問題および回避方法については、リリースノートを参照してください。

• Fixed TLB exception during upgrade from Rev build 1.11.000 to 0412.000

• Fixed expander bootstrap task which failed with 0xB1 error code appearing in the console due to missing NVRAM tag - Product Name

• Enabled-ClusterS2D command that does not complete with SATA drive in D3610

Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.

• Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order.
• Microsoft Windows Server 2012 R2 Hyper-V Storage Area Network (SAN) Disconnect.
• Link lost with firmware version 11.2.1263.19
• "FW not responding” message seen on card when creating Virtual Function (VF) in loop for HPE StoreFabric CN1200E-T 10GBASE-T Converged Network Adapter [NIC+ iSCSI] in Gen10 server.
• HP FlexFabric 20Gb 2-port 650FLB Adapter - Loss of access to storage after Virtual Connect (VC) login redistribution
• HP StoreFabric CN1200E Dual Port Converged Network Adapter does not complete to boot in Legacy Mode on Gen 9 Server
• Emulex Peripheral Component Interconnect (PCI) slot Network Interface Connector (NIC) reported as device path instead of product name
• Unable to disable shared memory feature in Human Interface Infrastructure (HII) menu
• 650M Adapter has some info in Chinese and Japanese show garbled code under Human Interface Infrastructure (HII) Form

• Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order.
• Microsoft Windows Server 2012 R2 Hyper-V Storage Area Network (SAN) Disconnect.
• Link lost with firmware version 11.2.1263.19
• "FW not responding” message seen on card when creating Virtual Function (VF) in loop for HPE StoreFabric CN1200E-T 10GBASE-T Converged Network Adapter [NIC+ iSCSI] in Gen10 server.
• HP FlexFabric 20Gb 2-port 650FLB Adapter - Loss of access to storage after Virtual Connect (VC) login redistribution
• HP StoreFabric CN1200E Dual Port Converged Network Adapter does not complete to boot in Legacy Mode on Gen 9 Server
• Emulex Peripheral Component Interconnect (PCI) slot Network Interface Connector (NIC) reported as device path instead of product name
• Unable to disable shared memory feature in Human Interface Infrastructure (HII) menu
• 650M Adapter has some info in Chinese and Japanese show garbled code under Human Interface Infrastructure (HII) Form

この製品は、16個のigbnデバイスポートが存在する場合に16番目のポートで正しくロードするようになりました。

This product now correctly loads on the 16th port when 16 igbn device ports are present.

This product now correctly loads on the 16th port of a 16-port device.

This product now correctly loads on the 16th port of a 16-port device.

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with rare occurrences of unpredictable system behavior. This issue is NOT unique to HPE servers and would impact any systems using AMD EPYC 7001 Series processors that do not contain latest AMD microcode. Note: this does not address any security vulnerability mitigations.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with rare occurrences of unpredictable system behavior. This issue is NOT unique to HPE servers and would impact any systems using AMD EPYC 7001 Series processors that do not contain latest AMD microcode. Note: this does not address any security vulnerability mitigations.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• このファームウェアには、パフォーマンスに影響を与える可能性のあるドライブリセットの問題を回避するための変更が含まれています。

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

• Brcmfcoe installer script does not install driver on SUSE Linux Enterprise Server 12 Service Pack 3(SLES 12 SP3) with Message “running kernel not supported".
• Brcmfcoe incorrectly blacklists lpfc driver when FibreChannel boards are installed.

• Brcmfcoe installer script does not install driver on SUSE Linux Enterprise Server 12 Service Pack 3(SLES 12 SP3) with Message “running kernel not supported".
• Brcmfcoe incorrectly blacklists lpfc driver when FibreChannel boards are installed.

•  Spectra Meltdown warning messages during driver update/installation.

•  Spectra Meltdown warning messages during driver update/installation.

This issue is only encounter when upgrading to version 2018.10.18 (5.5.0.66-1). All other versions are not affected

This issue is only encounter when upgrading to version 2018.10.18 (5.5.0.66-1). All other versions are not affected

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with rare occurrences of unpredictable system behavior. This issue is NOT unique to HPE servers and would impact any systems using AMD EPYC 7001 Series processors that do not contain latest AMD microcode. Note: this does not address any security vulnerability mitigations.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with rare occurrences of unpredictable system behavior. This issue is NOT unique to HPE servers and would impact any systems using AMD EPYC 7001 Series processors that do not contain latest AMD microcode. Note: this does not address any security vulnerability mitigations.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Servers do not complete the process to connect to OneConnectManager Management Host On Windows 2008/ 2012 and 2016

• Servers do not complete the process to connect to OneConnectManager Management Host On Windows 2008/ 2012 and 2016

• Servers do not complete the process to connect to OneConnectManager Management Host On Windows 2008/ 2012 and 2016

• Servers do not complete the process to connect to OneConnectManager Management Host On Windows 2008/ 2012 and 2016

• Brcmfcoe incorrectly blacklists lpfc driver when FibreChannel boards are installed.

• Brcmfcoe incorrectly blacklists lpfc driver when FibreChannel boards are installed.

•  Spectra Meltdown warning messages during driver update/installation.

•  Spectra Meltdown warning messages during driver update/installation.

• amsHelper no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsHelper
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli

• amsHelper no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsHelper
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

既知の問題点:

なし

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• addressed segfaults seen in the ahslog
• amsd no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsd
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli
• Corrected the cpqFcaHostCntlrFirmwareVersion for the HPE Synergy 5830C 32Gb FC Host Bus Adapter

• addressed segfaults seen in the ahslog
• amsd no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsd
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli
• Corrected the cpqFcaHostCntlrFirmwareVersion for the HPE Synergy 5830C 32Gb FC Host Bus Adapter

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

• amsHelper no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsHelper
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli

• amsHelper no longer segfaults when a NIC virtual function is created
• addressed an occasional segfault/system hang/NMI with amsHelper
• added support for the HPE Smart Array P824i-p storage controller in MRSA and Storcli

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

• All disks are opened RDONLY to send ioctl()’s to get drive information.
• Improved SATA channel determination for SATA drives.
• Corrected errors for lost memory allocations.

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

• Modified the loop initial values in hpasmcli from 2 to 0.
• Modifications to check the read and write variables to match RBSU in Legacy and UEFI mode
• Updated the hpasmcli check string to correctly report the impitool information

•  Snoop inquiry response atleast 168 bytes to determine proprietary DIF
•  Disable standard DIF for arrays advertising proprietary DIF.
•  Reset PROTECT bit only in standard INQUIRY response.
•  Check if the INQ response buffer is > 170 (instead of >=).
•  Fix invalid offset reference of inquiry response data.
•  set ql2xenabledif_tgt enabled by default.
•  Parameterize ql2xenabledif_tgt (defaulted to zero).
•  Mark DIF errors from target as re-tryable errors.
•  Do not turn off T10 DIF on a port reset.
•  Enable T10 DIF for reads as well.

•  Snoop inquiry response atleast 168 bytes to determine proprietary DIF
•  Disable standard DIF for arrays advertising proprietary DIF.
•  Reset PROTECT bit only in standard INQUIRY response.
•  Check if the INQ response buffer is > 170 (instead of >=).
•  Fix invalid offset reference of inquiry response data.
•  set ql2xenabledif_tgt enabled by default.
•  Parameterize ql2xenabledif_tgt (defaulted to zero).
•  Mark DIF errors from target as re-tryable errors.
•  Do not turn off T10 DIF on a port reset.
•  Enable T10 DIF for reads as well.

•  Spectra Meltdown warning messages during driver update/installation.

•  Spectra Meltdown warning messages during driver update/installation.

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

既知の問題点:

なし

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

この製品は、RBSUに誤ったネットワークコントローラー名が表示される問題を修正します。

この製品は、再起動中にアダプターのファームウェアが破損する問題を修正します。

この製品は、一方のポートでリンクがダウンしていると、もう一方のポートがダウンするという、オートネゴシエーション（AN）モードで見られる問題を修正します。

This product corrects an issue where an incorrect network controller name is displayed in the RBSU.

This product corrects an issue where adapter firmware is corrupted during reboot.

This product corrects an issue seen in Auto Negotiation (AN) mode where one of the ports goes down if the link is down on the other port.

This product corrects an issue where an incorrect device (Network Controller) name is displayed in the RBSU.

This product corrects an issue where adapters become Firmware corruption during rebooting.

This product corrects an issue where an incorrect device (Network Controller) name is displayed in the RBSU.

This product corrects an issue where adapters become Firmware corruption during rebooting.

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

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

なし

修正された問題点:

このシステムROMの改訂版には、オペレーティングシステムやハイパーバイザーの更新プログラムと組み合わせて、マイクロアーキテクチャデータサンプリング（MDS）と呼ばれる新しいグループのサイドチャネルの脆弱性に対する緩和策を提供する最新版のインテル製マイクロコードが含まれます。  これには、次の脆弱性を緩和するためのサポートが含まれます。  CVE-2018-12126 - マイクロアーキテクチャストアバッファデータサンプリング、CVE-2018-12130 - マイクロアーキテクチャフィルバッファデータサンプリング、CVE-2018-12127 - マイクロアーキテクチャロードポートデータサンプリング、およびCVE-2019-11091 - マイクロアーキテクチャデータサンプリングキャッシュ不可メモリ  これらの問題は、HPEサーバーに固有のものではありません。

既知の問題点:

なし

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and/or hypervisor updates, provides mitigation for a new group of side channel vulnerabilities known as Microarchitectural Data Sampling (MDS).  This includes support for mitigating the following vulnerabilities:  CVE-2018-12126 – Microarchitectural Store Buffer Data Sampling, CVE-2018-12130 – Microarchitectural Fill Buffer Data Sampling, CVE-2018-12127 – Microarchitectural Load Port Data Sampling, and CVE-2019-11091 – Microarchitectural Data Sampling Uncacheable Memory.  These issues are not unique to HPE servers.

Known Issues:

None

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

修正された問題点:

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Sync up information registered to switch for FDMI across all drivers.
• Continue with the logins in the scan loop despite seeing a login failure
• Send the GFO command in a separate thread then the fabric discovery.
• Eliminate the code to block I/O during small read operations of the flash.
• Ensure the target ID assigned to the WWPN on the physical port is the same on the NPIV port

• Sync up information registered to switch for FDMI across all drivers.
• Continue with the logins in the scan loop despite seeing a login failure
• Send the GFO command in a separate thread then the fabric discovery.
• Eliminate the code to block I/O during small read operations of the flash.
• Ensure the target ID assigned to the WWPN on the physical port is the same on the NPIV port

• Driver is selecting to run LB (Loopback) rather than echo for F_Port
• If the SNS (Storage Name Service) fabric login appears incomplete, it would not be retried.
• If switch domain controller continuously tries to login, there exists a window where driver database and firmware database can go out of sync causing fabric discovery incomplete, and the login retry count is exhausted.
• The driver does not report minimum speeds correctly for 16G and 32G adapters.
• Echo ELS (Extended Link Services) test using QCC (QLogic Converge Console) CLI (Command Line Interface) was incomplete with invalid WWPN (World Wide Port Name) status.
• Re-login is being triggered too fast.
• Inquiry response snooping does not take into account the possibility of multiple scatter gather elements.
• Target devices are temporarily not accessible when the link toggle occurs on one of the target device paths.
• Driver would not send the full RDP (Read Diagnostic Parameter) response with a switch port that was not in the logged in state.
• Driver was advertising 1G speed support for 8G adapters.
• FDMI (Fabric Device Management Interface) info showing incorrect supported speeds for 16G mezzanine adapters in FDMI (Fabric Device Management Interface).

• Driver is selecting to run LB (Loopback) rather than echo for F_Port
• If the SNS (Storage Name Service) fabric login appears incomplete, it would not be retried.
• If switch domain controller continuously tries to login, there exists a window where driver database and firmware database can go out of sync causing fabric discovery incomplete, and the login retry count is exhausted.
• The driver does not report minimum speeds correctly for 16G and 32G adapters.
• Echo ELS (Extended Link Services) test using QCC (QLogic Converge Console) CLI (Command Line Interface) was incomplete with invalid WWPN (World Wide Port Name) status.
• Re-login is being triggered too fast.
• Inquiry response snooping does not take into account the possibility of multiple scatter gather elements.
• Target devices are temporarily not accessible when the link toggle occurs on one of the target device paths.
• Driver would not send the full RDP (Read Diagnostic Parameter) response with a switch port that was not in the logged in state.
• Driver was advertising 1G speed support for 8G adapters.
• FDMI (Fabric Device Management Interface) info showing incorrect supported speeds for 16G mezzanine adapters in FDMI (Fabric Device Management Interface).

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

Fixes in version 2.42.5052:

• Fixed Uncorrectable Machine Check Exception issue. The internal resources for handling packets were not allowed to be flushed when the driver was brought down and occasionally caused Red Screen of Death (RSOD). The fix was applied to the ROM code only and has only external timing influences upon the driver’s teardown.

   

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

• PortRcvPkts counter was prevented from being cleared after resetting it.
• The system Timed Out on the configuration cycle of the Virtual Functions (VFs) when more than 10 Virtual Functions performed FLR and the completion Time Out value was configured to a range of less than 16 msec.
• The server hangs and results in NMI when running “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a different thread). In this case, the downstream bridge over the device reported completion timeout error.
• In flow_steering, BMC could not receive a ping over IPV6 after running bmc_reboot.
• While closing the HCA, the RX packet caused bad access to resources that did not exist, and consequently caused the QPCGW or the irisc to get stuck.
• The master SMLID and the LID was either 0 or 0xFFFF when the port was neither active nor armed.
• ibdump could not capture all MADs packets.
• link did not go up after reboot.
• Fixed a rare issue that cause the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions.
• Network Controller Sideband Interface (NC-SI) did not work when adding the disable_static_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes in version 2.42.5044:

• Fixed an issue that  prevented the firmware from detecting a link_down event thus preventing the IB bond interface from going to a failover mode 

• Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order.
• Microsoft Windows Server 2012 R2 Hyper-V Storage Area Network (SAN) Disconnect.
• Link lost with firmware version 11.2.1263.19
• "FW not responding” message seen on card when creating Virtual Function (VF) in loop for HPE StoreFabric CN1200E-T 10GBASE-T Converged Network Adapter [NIC+ iSCSI] in Gen10 server.
• HP FlexFabric 20Gb 2-port 650FLB Adapter - Loss of access to storage after Virtual Connect (VC) login redistribution
• HP StoreFabric CN1200E Dual Port Converged Network Adapter does not complete to boot in Legacy Mode on Gen 9 Server
• Emulex Peripheral Component Interconnect (PCI) slot Network Interface Connector (NIC) reported as device path instead of product name
• Unable to disable shared memory feature in Human Interface Infrastructure (HII) menu
• 650M Adapter has some info in Chinese and Japanese show garbled code under Human Interface Infrastructure (HII) Form

• Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order.
• Microsoft Windows Server 2012 R2 Hyper-V Storage Area Network (SAN) Disconnect.
• Link lost with firmware version 11.2.1263.19
• "FW not responding” message seen on card when creating Virtual Function (VF) in loop for HPE StoreFabric CN1200E-T 10GBASE-T Converged Network Adapter [NIC+ iSCSI] in Gen10 server.
• HP FlexFabric 20Gb 2-port 650FLB Adapter - Loss of access to storage after Virtual Connect (VC) login redistribution
• HP StoreFabric CN1200E Dual Port Converged Network Adapter does not complete to boot in Legacy Mode on Gen 9 Server
• Emulex Peripheral Component Interconnect (PCI) slot Network Interface Connector (NIC) reported as device path instead of product name
• Unable to disable shared memory feature in Human Interface Infrastructure (HII) menu
• 650M Adapter has some info in Chinese and Japanese show garbled code under Human Interface Infrastructure (HII) Form

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

修正された問題点:

インテル XeonスケーラブルパフォーマンスBronzeおよびSilverプロセッサーで、システムで訂正不可能なメモリエラーまたは起動時のメモリトレーニングの問題が発生する可能性がある問題に対処しました。この問題はシステムROMバージョン2.00で最初に発生したものです。メモリに関する問題が発生しているお客様は、コンポーネントを交換する前に、このバージョンのシステムROMに直ちにアップデートすることを推奨します。この問題は、HPEサーバーに固有のものではありません。

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may experience a higher rate of Uncorrectable Memory errors or boot time Memory training issues with Intel Xeon Scalable Performance Bronze and Silver processors. This issue was first introduced with System ROM version 2.00. HPE recommends that any customer experiencing a memory issue immediately update to this version of the system ROM before replacing any components. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where configuring memory to run at 2x refresh rate would still actually operate memory at 1x refresh rate. This issue was introduced with the v2.00 System ROM and did not impact earlier versions of the System ROM. This issue is not unique to HPE servers.

Addressed an issue where the NVMe PCIe Resource Padding option in BIOS/Platform Configuration (RBSU) would not properly allocated sufficient resources to support a NVMe hot add event. In certain configurations, an insufficient amount of resources would have been reserved and a reboot would have been required to detect the presence of the newly added drive.

Addressed an issue where the system would not boot to a USB drive when a non-bootable (non-formatted) drive was also present in the system. This issue only impacts systems configured in Legacy Boot Mode.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where configuring memory to run at 2x refresh rate would still actually operate memory at 1x refresh rate. This issue was introduced with the v2.00 System ROM and did not impact earlier versions of the System ROM. This issue is not unique to HPE servers.

Addressed an issue where the NVMe PCIe Resource Padding option in BIOS/Platform Configuration (RBSU) would not properly allocated sufficient resources to support a NVMe hot add event. In certain configurations, an insufficient amount of resources would have been reserved and a reboot would have been required to detect the presence of the newly added drive.

Addressed an issue where the system would not boot to a USB drive when a non-bootable (non-formatted) drive was also present in the system. This issue only impacts systems configured in Legacy Boot Mode.

Known Issues:

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

修正された問題点:

インテル XeonスケーラブルパフォーマンスBronzeおよびSilverプロセッサーで、システムで訂正不可能なメモリエラーまたは起動時のメモリトレーニングの問題が発生する可能性がある問題に対処しました。この問題はシステムROMバージョン2.00で最初に発生したものです。メモリに関する問題が発生しているお客様は、コンポーネントを交換する前に、このバージョンのシステムROMに直ちにアップデートすることを推奨します。この問題は、HPEサーバーに固有のものではありません。

既知の問題点:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the system may experience a higher rate of Uncorrectable Memory errors or boot time Memory training issues with Intel Xeon Scalable Performance Bronze and Silver processors. This issue was first introduced with System ROM version 2.00. HPE recommends that any customer experiencing a memory issue immediately update to this version of the system ROM before replacing any components. This issue is not unique to HPE servers.

Known Issues:

• OneViewの使用時に、ファームウェアをバージョン1.18から1.20にアップグレードする試みに失敗しました。

注：ターゲットデバイスがすでにファームウェアバージョン1.20にアップデートされている場合は、ファームウェアアップデート1.20(C) を適用する必要はありません。

• When using OneView, attempts to upgrade firmware from version 1.18 to 1.20 failed.

Note: If the target device was previously updated to firmware version 1.20, it is not necessary to apply firmware update 1.20(C).

• Sending Work Requests (WRs) with multiple entries where the first entry was less than 18 bytes used to fail.
• When the interface was down, ethtool counters ceased to increase. As a result, RoCE traffic counters were not always incremented.
• Compilation errors of MLNX_OFED over kernel when CONFIG_PTP_1588_CLOCK parameter was not set.
• System used to hang when trying to allocate multiple device memory buffers from different processes simultaneously.