Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where under complex micro-architectural conditions, executing X87 or AVX or integer divide instructions may results in unpredictable system behavior. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where under complex micro-architectural conditions, executing X87 or AVX or integer divide instructions may results in unpredictable system behavior. This issue is not unique to HPE servers.

Known Issues:

This product fixes an issue where configuring the Maximum Transmission Unit (MTU) for a Virtual Function fails on a guest OS.

This product addresses an issue where a link is lost on a Virtual Machine when hypervisor is restored from low-power state, such as freeze or suspend.

This product fixes an issue where configuring the Maximum Transmission Unit (MTU) for a Virtual Function fails on a guest OS.

This product addresses an issue where a link is lost on a Virtual Machine when hypervisor is restored from low-power state, such as freeze or suspend.

• 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.5056:

• Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device.

• 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.5056:

• Fixed an issue that resulted in reading from invalid I/O address on handover from UEFI boot to OS boot, when a port was configured as InfiniBand on a VPI adapter device.

• 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.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.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.

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

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2.76_10-21-2019 (B)  contains updates to the component packaging and is functionally equivalent to ver. 2.76_10-21-2019.  It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the system ROM to version 2.76_10-21-2019.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Ver. 2.76_10-21-2019 (B)  contains updates to the component packaging and is functionally equivalent to ver. 2.76_10-21-2019.  It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the system ROM to version 2.76_10-21-2019.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

• Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher.
• High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed.
• The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled.
• The desched_threshold field did not work properly.
• The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again.

Following issues have been fixed in firmware version 14.27.4000:

• The device hung while running the sw reset flow under heavy stress and with many open resources.
• Low PXE performance observerd while using the VSC to trigger the send_ring_doorbells.
• IPoIB and DC would not work together.
• DC funtionality issues.

• Although the effective BER (after FEC) was expected to meet the design targets (e.g. 10e-14 or lower), occasionally it was higher.
• High BER occured when connecting cables of type 0.5/1m DAC to an HDR speed.
• The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled.
• The desched_threshold field did not work properly.
• The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again.

Following issues have been fixed in firmware version 14.27.4000:

• The device hung while running the sw reset flow under heavy stress and with many open resources.
• Low PXE performance observerd while using the VSC to trigger the send_ring_doorbells.
• IPoIB and DC would not work together.
• DC funtionality issues.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the serial port would not function properly when the iLO CLI serial interface was also enabled on the platform. This could lead to the serial BAUD rate not being configured properly and the serial output from the host would be corrupted or no output would be seen.

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the serial port would not function properly when the iLO CLI serial interface was also enabled on the platform. This could lead to the serial BAUD rate not being configured properly and the serial output from the host would be corrupted or no output would be seen.

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

None

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

None

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Where Host Bus Adapters reporting address NACKs (No Acknowledgements) from external temperature sensors.

Where Host Bus Adapters reporting address NACKs (No Acknowledgements) from external temperature sensors.

This product fixes a issue where configuring the Maximum Transmission Unit (MTU) on a Virtual Function fails on a guest OS.

This product fixes a issue where configuring the Maximum Transmission Unit (MTU) on a Virtual Function fails on a guest OS.

• After a packet drop, the Rx page was not replenished. In certain rare scenarios, the same page fragment was mistakenly assigned to two different Rx descriptors for Write.
• ibsim was missing after OFED installation.
• ucx-kmem was missing after OFED installation.
• A dependency issue between systemd and RDMA-Core was fixed.
• Adding hairpin flows using Traffic Class (TC) tool was not allowed.
• Work Queue (WQ) flushing was not handled properly in the event of Enhanced Error Handling (EEH).
• When exiting an application that uses Reliable Message Passing Protocol (RMPP) mads intensively ,the kernel crashed.
• perftest applications (ib_read_*, ib_write_* and others) supplied with MLNX_OFED v5.0 and above did not work correctly if corresponding applications on another side of client-server communication were supplied with previous versions of MLNX_OFED due to an interoperability issue.
• When AER/slot reset is in done in parallel to user space commands execution, the kernel crashed.
• Missing Explicit Congestion Notification (ECN) configuration under sysfs for Physical Functions (PFs) in SwitchDev mode.

• After a packet drop, the Rx page was not replenished. In certain rare scenarios, the same page fragment was mistakenly assigned to two different Rx descriptors for Write.
• ibsim was missing after OFED installation.
• ucx-kmem was missing after OFED installation.
• A dependency issue between systemd and RDMA-Core was fixed.
• Adding hairpin flows using Traffic Class (TC) tool was not allowed.
• Work Queue (WQ) flushing was not handled properly in the event of Enhanced Error Handling (EEH).
• When exiting an application that uses Reliable Message Passing Protocol (RMPP) mads intensively ,the kernel crashed.
• perftest applications (ib_read_*, ib_write_* and others) supplied with MLNX_OFED v5.0 and above did not work correctly if corresponding applications on another side of client-server communication were supplied with previous versions of MLNX_OFED due to an interoperability issue.
• When AER/slot reset is in done in parallel to user space commands execution, the kernel crashed.
• Missing Explicit Congestion Notification (ECN) configuration under sysfs for Physical Functions (PFs) in SwitchDev mode.

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

These drivers have been recompiled with a build setting that allows SUM to identify them correctly for installation on systems they support.

These drivers have been recompiled with a build setting that allows SUM to identify them correctly for installation on systems they support.

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

• Enabled Bar configuration bytewise by applying the write_en bitmask.
• Low PXE performance while using the VSC to trigger the send_ring_doorbells.
• Fragmented IP packets were getting dropped.
• Firmware burning after PHY-less reset is expected to be significantly slow.
• PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr were not reporting port icrc errors.
• PortXmitWait HW counter was incrementing when not expected due to an inaccuracy in the counter.

• Enabled Bar configuration bytewise by applying the write_en bitmask.
• Low PXE performance while using the VSC to trigger the send_ring_doorbells.
• Fragmented IP packets were getting dropped.
• Firmware burning after PHY-less reset is expected to be significantly slow.
• PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr were not reporting port icrc errors.
• PortXmitWait HW counter was incrementing when not expected due to an inaccuracy in the counter.

• CWDM4(Coarse Wavelength Division Multiplexing) Acousto Optical Modulator(AOM) cable was not supported.
• Links between ConnectX-6 adapter cards and Spectrum-2 SN3700 switch systems did not come up when using Cisco BiDi module at 100GbE link speed.
• Occasionally, the link was not raised when working with split 2x100 mode with Optical cables.
• The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled.
• The desched_threshold field did not work properly.
• The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again.
• Aligned the User Memory page to 2, e.g., the user should use 8k aligned (like 0, 8k, 16k etc., instead of 0, 4k, 12k etc.).
• NRZ (non-return-to-zero) and PAM4 (Pulse amplitude modulation) Limitations in 100GbE adapter cards:
  • The default configuration was NRZ speeds in Auto-Neg mode.
  • PAM4 speeds had to be set manually (using the MFT tool – mlxlink).
  • PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x.
  • 200G_4x optical cables (including 200G_4x splitter cable) would raise link only after manual configuration of PAM4 speeds (50G_1x or 100G_2x).
• NRZ and PAM4 Limitations in 200GbE adapter cards:
  • The default configuration was 200G_x4 in Force mode.
  • NRZ speeds had to be set manually. Configuration could include multiple NRZ speeds (using the MFT tool – mlxlink).
  • PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x or 200G_4x.
• In Ethernet mode, at 25/50/100GbE speeds, only RS-FEC in Force mode was supported. Other user configurations were overridden.

• CWDM4(Coarse Wavelength Division Multiplexing) Acousto Optical Modulator(AOM) cable was not supported.
• Links between ConnectX-6 adapter cards and Spectrum-2 SN3700 switch systems did not come up when using Cisco BiDi module at 100GbE link speed.
• Occasionally, the link was not raised when working with split 2x100 mode with Optical cables.
• The PCIe Tx parameters did not load correctly when the speed was changed after the PCIe link was disabled.
• The desched_threshold field did not work properly.
• The "roce_adp_retrans" counter was presenting the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it would not be functional even after re-enabling it by running the "setpci" command again.
• Aligned the User Memory page to 2, e.g., the user should use 8k aligned (like 0, 8k, 16k etc., instead of 0, 4k, 12k etc.).
• NRZ (non-return-to-zero) and PAM4 (Pulse amplitude modulation) Limitations in 100GbE adapter cards:
  • The default configuration was NRZ speeds in Auto-Neg mode.
  • PAM4 speeds had to be set manually (using the MFT tool – mlxlink).
  • PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x.
  • 200G_4x optical cables (including 200G_4x splitter cable) would raise link only after manual configuration of PAM4 speeds (50G_1x or 100G_2x).
• NRZ and PAM4 Limitations in 200GbE adapter cards:
  • The default configuration was 200G_x4 in Force mode.
  • NRZ speeds had to be set manually. Configuration could include multiple NRZ speeds (using the MFT tool – mlxlink).
  • PAM4 speeds had to be configured as single speeds: 50G_1x or 100G_2x or 200G_4x.
• In Ethernet mode, at 25/50/100GbE speeds, only RS-FEC in Force mode was supported. Other user configurations were overridden.

• TBD
• TBD

• TBD
• TBD

• 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.
• Remove the redundant serial embedded and com ports
• Addressed IML message size limitation from 36 to 212 bytes
• Support for hp-health in OS security boot
• Added supporting “quote mark” in SET NAME command
• Enabled to set PXE as boot first 

• 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.
• Remove the redundant serial embedded and com ports
• Addressed IML message size limitation from 36 to 212 bytes
• Support for hp-health in OS security boot
• Added supporting “quote mark” in SET NAME command
• Enabled to set PXE as boot first 

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where under complex micro-architectural conditions, executing X87 or AVX or integer divide instructions may results in unpredictable system behavior. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where under complex micro-architectural conditions, executing X87 or AVX or integer divide instructions may results in unpredictable system behavior. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

• An issue where injecting EEH (Extended Error Handlng) may cause extra Kernel prints, such as: “EEH: Might be infinite loop in mlx5_core driver” was fixed.
• RPM-based OSs with non-default kernels, using repositories after re-creating the installer (using --add-kernel-support) were resulting in improper installation of the drivers.
• A typo in perftest package where help messages wrongly displayed the conversion result between Gb/s and MB/s (20^2 instead of 2^20).
• When one of the LAG slaves went down, LAG deactivation failed, ultimately causing bandwidth degradation.
• The mlx5 driver maintains a subdirectory for every open eth port in /sys/kernel/debug/. For the default network namespace, the sub-directory name is the name of the interface, like "eth8". The new convention for the network interfaces moved to the non-default network namespaces is the interfaces name followed by "@" and the port's PCI ID. For example: "eth8@0000:af:00.3".
• "openibd" script load used to fail when esp6_offload module did not load successfully.
• Added dependency of package mpi-selectors on perl-Getopt-Long system package. On minimal installs of RPM-based OSs, installing mpi-selectros will also install the required system package perl-Getopt-Long.
• During certain rare scenarios, due to Rx page not being replenished, the same page fragment mistakenly became assigned to two different Rx descriptors.
• Driver load issue existed with Errata-kernel on SLES15 SP1.
• An issue in the Hairpin feature which prevented adding hairpin flows using TC tool was fixed.
• WQ (Work Queue) queue flushing was not handled properly in the event of EEH.
• A rare kernel crash scenario when exiting an application that uses RMPP mads intensively.
• A possible kernel crash scenario when AER/slot reset in done in parallel to user space commands execution.
• Added missing ECN (Explicit Congestion Notification) configuration under sysfs for PFs in SwitchDev mode.
• When firmware response time to commands became very long, some commands failed upon timeout. The driver may have then triggered a timeout completion on the wrong entry, leading to a NULL pointer call trace.
• Added driver support for kernels with the old XDP_REDIRECT infrastructure that uses the following NetDev operations: .ndo_xdp_flush and .ndo_xdp_xmit.
• Usage of --excludedocs Open MPI RPM option resulted in the removal of non-documentation related files.
• Disabled automated loading of some modules through udev triggers to preserve the startup process of previous MLNX_OFED versions.
• Reference count (refcount) for RDMA connection ID (cm_id) was not incremented in rdma_resolve_addr() function, resulting in a cm_id use-after-free access. A fix was applied to increment the cm_id refcount
• A race condition which caused kernel panic when moving two ports to SwitchDev mode at the same time.
• Allowed accessing sysfs hardware counters in SwitchDev mode
• Function smp_processor_id() is called in the RX page recycle flow to determine the core to run on. This is intended to run in NAPI context. However, due to a bug in backporting, the RX page recycle was mistakenly called also in the RQ close flow when not needed.
• Port link state was automatically changed (without admin state involvement) to "UP" after reboot.
• ConnectX-3 adapter cards froze when running over SLES 11 OS.
• RDMA CM (Remote Direct Memory Access Communation Manager) connection failed when port space was small.
• Traffic mirroring with OVS (Open VSwitch)offload and non-offload over VxLAN interface is now supported. Note: For kernel 4.9, make sure to use a dedicated OVS version.
• When working with VF LAG while the bond device is in active-active mode, running fwreset would result in unequal traffic on both PFs, and PFs would not reach line rate.
• When bond was created over VF (Virtuaal Function) netdevices in SwitchDev mode, the VF netdevice would be treated as representor netdevice. This caused the mlx5_core driver to crash in case it received netdevice events related to bond device.
• An issue where following a bad affinity occurrence in VF LAG mode, traffic was sent after the port went up/down in the switch.
• Added support for VLAN (Virtual Local Area Network) header rewrite on CentOS 7.2 OS.

• When configuring the Time-stamping feature, Completion Queue Events (CQE) compression would be disabled. This fix entailed the removal of a warning message that appeared upon attempting to disable CQE compression when it has already been disabled.
• Fixed the issue where software reset might have resulted in an order inversion of interface names.
• Server reboot might have resulted in a system crash.
• Virtual Function (VF) mirroring offload not supported issue have been fixed.
• The number of guaranteed counters per VF have been changed and now calculated based on the number of ports mapped to that VF. This allows more VFs to have counters allocated.

• When configuring the Time-stamping feature, Completion Queue Events (CQE) compression would be disabled. This fix entailed the removal of a warning message that appeared upon attempting to disable CQE compression when it has already been disabled.
• Fixed the issue where software reset might have resulted in an order inversion of interface names.
• Server reboot might have resulted in a system crash.
• Virtual Function (VF) mirroring offload not supported issue have been fixed.
• The number of guaranteed counters per VF have been changed and now calculated based on the number of ports mapped to that VF. This allows more VFs to have counters allocated.

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:

Resolved a memory initialization issue on systems configured with LRDIMMs and the v1.24 (04/29/2020) revision of the System ROM that could lead to an increased chance for Corrected Memory Threshold Errors or Uncorrected Memory Errors.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Resolved a memory initialization issue on systems configured with LRDIMMs and the v1.24 (04/29/2020) revision of the System ROM that could lead to an increased chance for Corrected Memory Threshold Errors or Uncorrected Memory Errors.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

None

• Enhancements have been made to the firmware to prevent and better recover from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Address unexpected behavior when Fibre Channel adapters were simultaneously running traffic to an array which supports 3PAR Persistent Checksum AND another array which is running T10-PI (also known as T10-DIF) or no block checksum technology at all
• Fibre Channel adapter firmware versions were not showing up as expected in the AHS log.
• Port statistics counters would sometimes not update in the event of Loss of Signal or Loss of Sync
• link downs would occur during specific frame sequences used by the HPE XP8 array after array-side link loss

• Enhancements have been made to the firmware to prevent and better recover from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Address unexpected behavior when Fibre Channel adapters were simultaneously running traffic to an array which supports 3PAR Persistent Checksum AND another array which is running T10-PI (also known as T10-DIF) or no block checksum technology at all
• Fibre Channel adapter firmware versions were not showing up as expected in the AHS log.
• Port statistics counters would sometimes not update in the event of Loss of Signal or Loss of Sync
• link downs would occur during specific frame sequences used by the HPE XP8 array after array-side link loss

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode for Intel Pentium processors which provides mitigations for security vulnerabilities documented as CVE-2020-0543 as well as CVE-2020-0548 and CVE-2020-0549. These security vulnerabilities are documented in Intel Security Advisories INTEL-SA-00320 and INTEL-SA-00329. These issues are not unique to HPE servers. This update does not impact systems using Intel Xeon based processors.

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode for Intel Pentium processors which provides mitigations for security vulnerabilities documented as CVE-2020-0543 as well as CVE-2020-0548 and CVE-2020-0549. These security vulnerabilities are documented in Intel Security Advisories INTEL-SA-00320 and INTEL-SA-00329. These issues are not unique to HPE servers. This update does not impact systems using Intel Xeon based processors.

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-0543 as well as CVE-2020-0548 and CVE-2020-0549, also known as CacheOut.  These security vulnerabilities are documented in Intel Security Advisories INTEL-SA-00320 and INTEL-SA-00329.  These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for security vulnerabilities documented as CVE-2020-0528 and CVE-2020-0529.  These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00322.  These issues are not unique to HPE servers.

Addressed an issue where the serial port would not function properly when the iLO CLI serial interface was also enabled on the platform. This could lead to the serial BAUD rate not being configured properly and the serial output from the host would be corrupted or no output would be seen.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Addressed an issue where the server may become unresponsive during POST with a Red Screen Exception (RSOD) when the server was reset (restarted) at the same time that an iLO firmware reset was initiated.  Note that updating iLO firmware results in the reset of iLO firmware.

Addressed an issue where the System Utilities System Information data could not be successfully exported to an FTP (network) location. Previously the System Utilities would report the file was saved successfully but no actual information was saved on the network share.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigations for security vulnerabilities documented as CVE-2020-0543 as well as CVE-2020-0548 and CVE-2020-0549, also known as CacheOut.  These security vulnerabilities are documented in Intel Security Advisories INTEL-SA-00320 and INTEL-SA-00329.  These issues are not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel Reference Code which provides mitigations for security vulnerabilities documented as CVE-2020-0528 and CVE-2020-0529.  These security vulnerabilities are documented in Intel Security Advisory INTEL-SA-00322.  These issues are not unique to HPE servers.

Addressed an issue where the serial port would not function properly when the iLO CLI serial interface was also enabled on the platform. This could lead to the serial BAUD rate not being configured properly and the serial output from the host would be corrupted or no output would be seen.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Addressed an issue where the server may become unresponsive during POST with a Red Screen Exception (RSOD) when the server was reset (restarted) at the same time that an iLO firmware reset was initiated.  Note that updating iLO firmware results in the reset of iLO firmware.

Addressed an issue where the System Utilities System Information data could not be successfully exported to an FTP (network) location. Previously the System Utilities would report the file was saved successfully but no actual information was saved on the network share.

Known Issues:

None

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

• The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure.

• Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04.

• If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online.

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

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

• The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure.

• Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04.

• If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online.

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

• 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.

• 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.

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

• Encapsulated RoCE traffic to drop when IB padding was required.
• PortXmitWait HW counter to count when not expected due to an inaccuracy in the counter.
• On dual-port device after Rx buffer modification the Physical Function on the second port got restored although no expected.  The Rx buffer changes when all Physical Functions resets over one port (through reboot /driver restart / FLR) while there were active Physical Functions over the second port.
• Previous Shared Buffer modifications being overrun after performing Shared Buffer modifications such as SBPR, SBPM, SBCM, the PFCC Flow Control).

• Encapsulated RoCE traffic to drop when IB padding was required.
• PortXmitWait HW counter to count when not expected due to an inaccuracy in the counter.
• On dual-port device after Rx buffer modification the Physical Function on the second port got restored although no expected.  The Rx buffer changes when all Physical Functions resets over one port (through reboot /driver restart / FLR) while there were active Physical Functions over the second port.
• Previous Shared Buffer modifications being overrun after performing Shared Buffer modifications such as SBPR, SBPM, SBCM, the PFCC Flow Control).

• Fixed an issue that caused packets to drop when using Post Office Protocol(POP) virtual LAN (VLAN)and decapsulation actions in the same flow table entry.
• Fixed an issue that prevented the load of the correct PCIe Tx parameters when the speed was changed after the PCIe link was disabled.
• Fixed an issue that caused the "roce_adp_retrans" counter to present the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it will not be functional even after re-enabling it by running the "setpci" command again.
• Updated the RDMA over Converged Ethernet (RoCE) Tx CNP's Backward Explicit Congestion Notification (BECN) value to be 1.
• Non-return-to-zero (NRZ) and Pulse Amplitude Modulation (PAM4)Limitations in 100GbE adapter cards:
  • The default configuration was NRZ speeds in Auto-Neg mode
  • PAM4 speeds should be set manually (using the MFT tool – mlxlink)
  • PAM4 speeds should be configured as single speeds: 50G_1x or 100G_2x
  • 200G_4x optical cables (including 200G_4x splitter cable) will raise link only after manual configuration of PAM4 speeds (50G_1x or 100G_2x)
• NRZ and PAM4 Limitations in 200GbE adapter cards:
  • The default configuration was 200G_x4 in Force mode
  • NRZ speeds should be set manually. Configuration can include multiple NRZ speeds (using the MFT tool –mlxlink)
  • PAM4 speeds should be configured as single speeds: 50G_1x or 100G_2x or 200G_4x

• Fixed an issue that caused packets to drop when using Post Office Protocol(POP) virtual LAN (VLAN)and decapsulation actions in the same flow table entry.
• Fixed an issue that prevented the load of the correct PCIe Tx parameters when the speed was changed after the PCIe link was disabled.
• Fixed an issue that caused the "roce_adp_retrans" counter to present the values of the "local_ack_timeout_err" counter.
• If Relaxed Ordering was disabled by running the "setpci" command, it will not be functional even after re-enabling it by running the "setpci" command again.
• Updated the RDMA over Converged Ethernet (RoCE) Tx CNP's Backward Explicit Congestion Notification (BECN) value to be 1.
• Non-return-to-zero (NRZ) and Pulse Amplitude Modulation (PAM4)Limitations in 100GbE adapter cards:
  • The default configuration was NRZ speeds in Auto-Neg mode
  • PAM4 speeds should be set manually (using the MFT tool – mlxlink)
  • PAM4 speeds should be configured as single speeds: 50G_1x or 100G_2x
  • 200G_4x optical cables (including 200G_4x splitter cable) will raise link only after manual configuration of PAM4 speeds (50G_1x or 100G_2x)
• NRZ and PAM4 Limitations in 200GbE adapter cards:
  • The default configuration was 200G_x4 in Force mode
  • NRZ speeds should be set manually. Configuration can include multiple NRZ speeds (using the MFT tool –mlxlink)
  • PAM4 speeds should be configured as single speeds: 50G_1x or 100G_2x or 200G_4x

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

• Input / Output (I/O) non- working messages would be observed if 3PAR Persistent checksum is disabled on an array while the host is still running.

• Input / Output (I/O) non- working messages would be observed if 3PAR Persistent checksum is disabled on an array while the host is still running.

• When the kernel was started with the command line parameter “pv6.disable=1”, amsHelper would experience memory leaks eventually causing  performance degradation on the server.

• When the kernel was started with the command line parameter “pv6.disable=1”, amsHelper would experience memory leaks eventually causing  performance degradation on the server.

• Enhancements have been made to the firmware to prevent and better recover from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Address unexpected behavior when Fibre Channel adapters were simultaneously running traffic to an array which supports 3PAR Persistent Checksum AND another array which is running T10-PI (also known as T10-DIF) or no block checksum technology at all
• Fibre Channel adapter firmware versions were not showing up as expected in the AHS log.
• Port statistics counters would sometimes not update in the event of Loss of Signal or Loss of Sync
• link downs would occur during specific frame sequences used by the HPE XP8 array after array-side link loss

• Enhancements have been made to the firmware to prevent and better recover from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Address unexpected behavior when Fibre Channel adapters were simultaneously running traffic to an array which supports 3PAR Persistent Checksum AND another array which is running T10-PI (also known as T10-DIF) or no block checksum technology at all
• Fibre Channel adapter firmware versions were not showing up as expected in the AHS log.
• Port statistics counters would sometimes not update in the event of Loss of Signal or Loss of Sync
• link downs would occur during specific frame sequences used by the HPE XP8 array after array-side link loss

Ver. 2.76_10-21-2019 (B)  contains updates to the component packaging and is functionally equivalent to ver. 2.76_10-21-2019.  It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the system ROM to version 2.76_10-21-2019.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Ver. 2.76_10-21-2019 (B)  contains updates to the component packaging and is functionally equivalent to ver. 2.76_10-21-2019.  It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the system ROM to version 2.76_10-21-2019.

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

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

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

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

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

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

• Temperature sensors logic inside gSEP model and SES database
• When an IOM is pulled the surviving IOM reports false critical temperatures

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

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest support for Intel Trusted eXecution Technology (TXT) which provides mitigation for CVE-2019-0151. This mitigation is only needed for systems that have TXT enabled (TXT is disabled by default). This issue is not unique to HPE servers.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel Reference Code support that provides mitigation for CVE-2019-11137. This issue is not unique to HPE servers.

Known Issues:

This product addresses an iSCSI discovery failure with VLAN.

This product addresses an issue where an iSCSI portal is discovered with invalid an VLAN ID.

This product addresses an iSCSI discovery failure with VLAN.

This product addresses an issue where an iSCSI portal is discovered with invalid an VLAN ID.

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• When the kernel was started with the command line parameter “pv6.disable=1”, amsHelper would experience memory leaks eventually causing  performance degradation on the server.

• When the kernel was started with the command line parameter “pv6.disable=1”, amsHelper would experience memory leaks eventually causing  performance degradation on the server.

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.

This product addresses an issue where the ixgben driver has high CPU overhead when an SFP+ module is absent.

This product addresses an issue where the ixgben driver has high CPU overhead when an SFP+ module is absent.

• Fixed false Solid State Disk Wear alert reported by the SmartArray WBEM provider

Agentless Management Service

• Fixed reporting of HPE QLogic NX2 driver components in the cpqHoSwVer MIB to resolve blank Installed driver versions displayed in SUM

• Fixed false Solid State Disk Wear alert reported by the SmartArray WBEM provider

Agentless Management Service

• Fixed reporting of HPE QLogic NX2 driver components in the cpqHoSwVer MIB to resolve blank Installed driver versions displayed in SUM

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the system would become unresponsive with a Red Screen or hang when booting to FreeBSD R12.1 from a USB device when in Legacy Boot Mode. This issue did not impact systems configured for UEFI Boot Mode or when booting from other types of media.

Addressed an issue where a dual port networking device may show up in the System Configuration Utilities with two Port 1 names instead of properly being represented as Port 1 and Port 2. This did not impact any functionality to the device.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where UEFI Serial Debug output could inadvertently be seen over BIOS Serial Console. This issue would be seen periodically on server reboots. This issue was introduced with System ROM v2.30 and did not impact servers using previous versions of the System ROM.

Addressed an extremely rare issue where the system could become unresponsive in POST when configured in Legacy Boot Mode when a USB Mouse is attached. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where boot devices could disappear from the Boot Options menu in the BIOS/Platform Configuration (RBSU) when pressing the F10 or F12 key to save boot order changes.

Known Issues:

• One port of a Fibre Channel adapter could not complete to reconnect to storage after storage upgrade if the host system had been online for over 3 months
• Turning on 3PAR Persistent Checksum after the host operating system was running would not result in Persistent Checksum being enabled between the adapter and 3PAR array.
• Virtual Machines (VMs) could not access certain storage arrays when those arrays were attached to the VM using N-Port ID Virtualization (NPIV)

• One port of a Fibre Channel adapter could not complete to reconnect to storage after storage upgrade if the host system had been online for over 3 months
• Turning on 3PAR Persistent Checksum after the host operating system was running would not result in Persistent Checksum being enabled between the adapter and 3PAR array.
• Virtual Machines (VMs) could not access certain storage arrays when those arrays were attached to the VM using N-Port ID Virtualization (NPIV)

• TBD
• TBD

• TBD
• TBD

• Addressed memory leaks
• Corrected segfaults reported in ahslog
• Improved synchronization between iLO and amsd

• Addressed memory leaks
• Corrected segfaults reported in ahslog
• Improved synchronization between iLO and amsd

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

• Hosts booting from 3PAR arrays could unexpectedly reboot during 3PAR array node controller reboots with driver 10.01.00.57.xx.xx

• Improved adapter driver handling of and recovery from the unexpected behavior described in Customer Advisory titled: “HPE ProLiant, Synergy and Superdome Flex Host Bus Adapters (HBA) - Certain Fibre Channel HBA Firmware May Cause the Operating System to Halt and Potentially Compromise Filesystem Data Integrity" at the following link:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094722en_us

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

• The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure.

• Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04.

• If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online.

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

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

• The smart carrier, which is the drive case for SAS drives, now authenticates in the D3610/D3710 drive enclosure.

• Added new 7-segment error codes E0 and E1 to report issues with Fan modules A and B, respectively. These new codes only apply to the D3610/D3710 and only display when running firmware 5.04.

• If the storage enclosure processor within the I/O module fails, a hard reset (power down and then power up) is executed to ensure the processor comes back online.

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

• 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 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.

• Enabled Bar configuration bytewise by applying the write_en bitmask.
• Low PXE performance while using the VSC to trigger the send_ring_doorbells.
• Fragmented IP packets were getting dropped.
• Firmware burning after PHY-less reset is expected to be significantly slow.
• PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr were not reporting port icrc errors.
• PortXmitWait HW counter was incrementing when not expected due to an inaccuracy in the counter.

• Enabled Bar configuration bytewise by applying the write_en bitmask.
• Low PXE performance while using the VSC to trigger the send_ring_doorbells.
• Fragmented IP packets were getting dropped.
• Firmware burning after PHY-less reset is expected to be significantly slow.
• PortCounters.PortRcvErr / PPCNT.infiniband_counters.PortRcvErr were not reporting port icrc errors.
• PortXmitWait HW counter was incrementing when not expected due to an inaccuracy in the counter.