The following issues are resolved in iLO 4 version 2.61:

• Intermittent boot failures encountered when server boots from MicroSD card.
• Fixed problem with AHS download that might have unreadable data for the current day.
• iLO Web GUI sessions might not logoff at the end of timeout period.
• Incorrect information displayed for Power Supply Bay in AHS viewer.
• License hyperlink in Access Settings page of GUI leads to Page Not Found.
• Unable to login to iLO CLI after setting iLO to factory defaults, requiring an additional iLO reset.
• Unable to delete REST interface sessions with users having certain special characters.
• SNMP may become unresponsive over a period of time.

SECURITY: 

  For the latest security bulletins and vulnerabilities, please visit: 
  https://support.hpe.com/hpesc/public/home

Security bulletins:

• HPESBHF03866

Security best practices:

  Please refer to the HPE Integrated Lights-Out Security Technology Brief for the latest on security best practices at:
  http://www.hpe.com/support/iLO4_security_en
 

The following issues are resolved in iLO 4 version 2.61:

• Intermittent boot failures encountered when server boots from MicroSD card.
• Fixed problem with AHS download that might have unreadable data for the current day.
• iLO Web GUI sessions might not logoff at the end of timeout period.
• Incorrect information displayed for Power Supply Bay in AHS viewer.
• License hyperlink in Access Settings page of GUI leads to Page Not Found.
• Unable to login to iLO CLI after setting iLO to factory defaults, requiring an additional iLO reset.
• Unable to delete REST interface sessions with users having certain special characters.
• SNMP may become unresponsive over a period of time.

SECURITY: 

  For the latest security bulletins and vulnerabilities, please visit: 
  https://support.hpe.com/hpesc/public/home

Security bulletins:

• HPESBHF03866

Security best practices:

  Please refer to the HPE Integrated Lights-Out Security Technology Brief for the latest on security best practices at:
  http://www.hpe.com/support/iLO4_security_en
 

• 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

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:

Addressed an issue where early server video output, on a locally attached monitor, may not show correctly when the monitor is attached to the server through a KVM. This issue does not impact systems that are not using a KVM or video output through the iLO Remote Console application.

Addressed an issue where firmware flashing through the RESTful API could periodically fail and the task being marked with an exception in the iLO firmware page. This issue could impact flashing firmware such as the HPE Innovation Engine, Intel SPS Firmware or the optional HPE Trusted Platform Module (TPM).

Addressed an issue where a PCIe card would not properly train to its maximum speed when the PCIe Bifurcation option was enabled. This issue does not impact PCIe cards that do not require bifurcation.

Addressed an extremely rare issue where a system configured with an optional SATA DVD drive and an HPE SmartArray controller may become unresponsive during boot, usually with a Red Screen (RSOD), when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where an optional PCIe card's legacy option ROM may not properly display its legacy setup menu prompt during boot when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where early server video output, on a locally attached monitor, may not show correctly when the monitor is attached to the server through a KVM. This issue does not impact systems that are not using a KVM or video output through the iLO Remote Console application.

Addressed an issue where firmware flashing through the RESTful API could periodically fail and the task being marked with an exception in the iLO firmware page. This issue could impact flashing firmware such as the HPE Innovation Engine, Intel SPS Firmware or the optional HPE Trusted Platform Module (TPM).

Addressed an issue where a PCIe card would not properly train to its maximum speed when the PCIe Bifurcation option was enabled. This issue does not impact PCIe cards that do not require bifurcation.

Addressed an extremely rare issue where a system configured with an optional SATA DVD drive and an HPE SmartArray controller may become unresponsive during boot, usually with a Red Screen (RSOD), when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where an optional PCIe card's legacy option ROM may not properly display its legacy setup menu prompt during boot when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode

Known Issues:

• Kernel panic may occur during device discovery state.

• Kernel panic may occur during device discovery state.

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

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and hypervisor updates, provides mitigation for the L1 Terminal Fault – OS/SMM (CVE-2018-3620) and L1 Terminal Fault – VMM (CVE-2018-3646) security vulnerabilities.  These vulnerabilities may allow unauthorized disclosure of information residing in the L1 data cache to an attacker with local user access via a side-channel analysis.  These security vulnerabilities are not unique to HPE servers and impact any servers utilizing impacted processors.  Note that this server is NOT vulnerable to L1 Terminal Fault – SGX (CVE-2018-3615), also known as Foreshadow, because this server does NOT support SGX. 

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for the Speculative Store Bypass (also known as Variant 4) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3639. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

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 hypervisor updates, provides mitigation for the L1 Terminal Fault – OS/SMM (CVE-2018-3620) and L1 Terminal Fault – VMM (CVE-2018-3646) security vulnerabilities.  These vulnerabilities may allow unauthorized disclosure of information residing in the L1 data cache to an attacker with local user access via a side-channel analysis.  These security vulnerabilities are not unique to HPE servers and impact any servers utilizing impacted processors.  Note that this server is NOT vulnerable to L1 Terminal Fault – SGX (CVE-2018-3615), also known as Foreshadow, because this server does NOT support SGX. 

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for the Speculative Store Bypass (also known as Variant 4) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3639. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

None

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

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system and hypervisor updates, provides mitigation for the L1 Terminal Fault – OS/SMM (CVE-2018-3620) and L1 Terminal Fault – VMM (CVE-2018-3646) security vulnerabilities.  These vulnerabilities may allow unauthorized disclosure of information residing in the L1 data cache to an attacker with local user access via a side-channel analysis.  These security vulnerabilities are not unique to HPE servers and impact any servers utilizing impacted processors.  Note that this server is NOT vulnerable to L1 Terminal Fault – SGX (CVE-2018-3615), also known as Foreshadow, because this server does NOT support SGX. 

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for the Speculative Store Bypass (also known as Variant 4) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3639. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

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 hypervisor updates, provides mitigation for the L1 Terminal Fault – OS/SMM (CVE-2018-3620) and L1 Terminal Fault – VMM (CVE-2018-3646) security vulnerabilities.  These vulnerabilities may allow unauthorized disclosure of information residing in the L1 data cache to an attacker with local user access via a side-channel analysis.  These security vulnerabilities are not unique to HPE servers and impact any servers utilizing impacted processors.  Note that this server is NOT vulnerable to L1 Terminal Fault – SGX (CVE-2018-3615), also known as Foreshadow, because this server does NOT support SGX. 

This revision of the System ROM includes the latest revision of the Intel microcode which, in combination with operating system updates, provides mitigation for the Speculative Store Bypass (also known as Variant 4) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3639. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

None

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

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

• Traps for Fibre Channel and Events are now correctly logged to the iLO IML

• Traps for Fibre Channel and Events are now correctly logged to the iLO IML

Firmware Dependencies:

Problems Fixed:

Addressed an issue where early server video output, on a locally attached monitor, may not show correctly when the monitor is attached to the server through a KVM. This issue does not impact systems that are not using a KVM or video output through the iLO Remote Console application.

Addressed an issue where firmware flashing through the RESTful API could periodically fail and the task being marked with an exception in the iLO firmware page. This issue could impact flashing firmware such as the HPE Innovation Engine, Intel SPS Firmware or the optional HPE Trusted Platform Module (TPM).

Addressed an issue where a PCIe card would not properly train to its maximum speed when the PCIe Bifurcation option was enabled. This issue does not impact PCIe cards that do not require bifurcation.

Addressed an extremely rare issue where a system configured with an optional SATA DVD drive and an HPE SmartArray controller may become unresponsive during boot, usually with a Red Screen (RSOD), when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where an optional PCIe card's legacy option ROM may not properly display its legacy setup menu prompt during boot when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where early server video output, on a locally attached monitor, may not show correctly when the monitor is attached to the server through a KVM. This issue does not impact systems that are not using a KVM or video output through the iLO Remote Console application.

Addressed an issue where firmware flashing through the RESTful API could periodically fail and the task being marked with an exception in the iLO firmware page. This issue could impact flashing firmware such as the HPE Innovation Engine, Intel SPS Firmware or the optional HPE Trusted Platform Module (TPM).

Addressed an issue where a PCIe card would not properly train to its maximum speed when the PCIe Bifurcation option was enabled. This issue does not impact PCIe cards that do not require bifurcation.

Addressed an extremely rare issue where a system configured with an optional SATA DVD drive and an HPE SmartArray controller may become unresponsive during boot, usually with a Red Screen (RSOD), when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where an optional PCIe card's legacy option ROM may not properly display its legacy setup menu prompt during boot when in legacy boot mode. This issue does not impact systems in UEFI Boot Mode.

Known Issues:

• Fixed unexpected behavior in Active Health System (AHS) logs show World Wide Node Name (wwnn) & World Wide Port Name (wwpn) in reverse order.
• Fixed unexpected behavior with HP FlexFabric 20Gb 2-port 650FLB Adapter, HP FlexFabric 20Gb 2-port 650M Adapter cards does not complete to boot to Linux SUSE Linux Enterprise Server 12 Service Pack 3(SLES12 SP3) Operating System (OS) when both adapter are enabled for Fibre Channel over Ethernet (FCoE) boot.
• 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.
• Fixed unexpected behavior with HP FlexFabric 20Gb 2-port 650FLB Adapter, HP FlexFabric 20Gb 2-port 650M Adapter cards does not complete to boot to Linux SUSE Linux Enterprise Server 12 Service Pack 3(SLES12 SP3) Operating System (OS) when both adapter are enabled for Fibre Channel over Ethernet (FCoE) boot.
• 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

• 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

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

• Traps for Fibre Channel and Events are now correctly logged to the iLO IML

• Traps for Fibre Channel and Events are now correctly logged to the iLO IML

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

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

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

• Kernel panic may occur during device discovery state.

• Kernel panic may occur during device discovery state.

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:

HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later

Problems Fixed:

Known Issues:

Firmware Dependencies:

HPE Gen10 Innovation Engine (IE) Firmware version 0.1.5.2 or later

Problems Fixed:

Known Issues:

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

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

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

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.

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

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

None

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

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

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

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

None

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

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue with NVMe drives becoming unavailable to an operating system when updating the backplane firmware.

Addressed a rare issue where NVMe drives may not be available to an operating system when installing two or more NVMe drives simultaneously.

Addressed an issue with the RBSU setting for AMD Core Performance Boost not being correctly applied in all instances.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue with NVMe drives becoming unavailable to an operating system when updating the backplane firmware.

Addressed a rare issue where NVMe drives may not be available to an operating system when installing two or more NVMe drives simultaneously.

Addressed an issue with the RBSU setting for AMD Core Performance Boost not being correctly applied in all instances.

Known Issues:

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

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.

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

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

• Expander may reset during heavy SSACLI polling
• SATA drives may take longer to spin up, not be initially detected, and then hot add later. This can prevent system boot or affect the logical drive status.

• Expander may reset during heavy SSACLI polling
• SATA drives may take longer to spin up, not be initially detected, and then hot add later. This can prevent system boot or affect the logical drive status.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

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

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

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the UEFI EDK2 support that provides mitigations for a variety of security vulnerabilities. The following vulnerabilities have been addressed in this System ROM release: CVE-2018-3613 CVE-2017-5731, CVE-2017-5732, CVE-2017-5733, CVE-2017-5734, CVE-2017-5735, CVE-2018-3630, CVE-2018-12178, CVE-2018-12179, CVE-2018-12180, CVE-2018-12181, CVE-2018-12182 and CVE-2018-12183. These security vulnerabilities are not unique to HPE servers.

This system ROM contains the latest Intel microcode that addresses an issue where the system may experience an Uncorrected Machine Check Exception in Bank 0 with Status containing 000F0150. This update may not address all Bank 0 machine check events with a Status containing 000F0150 but should be used before any other further service actions for issues resulting in this Integrated Management Log (IML) entry. This issue is not unique to HPE servers.

Addressed an issue in which the system may not properly boot to the HPE 8GB Dual microSD Flash USB Drive when an SD card is installed on the internal SD slot when the system is configured for Legacy Boot Mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where certain 3rd party USB drive keys may not function properly after a system reset when the system is configured in UEFI Boot Mode.

Addressed an issue where the HPE CN1000E-T adapter may not boot properly in Legacy Boot Mode. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where firmware updates staged through the HPE RESTful API may fail to properly execute on a subsequent boot and be marked with an exception in the iLO firmware installation queue.

Addressed an issue where iLO virtual media may not boot properly after setting the Boot on Next Reset option in the iLO Remote Console and Media - Virtual Media settings.

Addressed an issue where the AHS Download application from the System Utilities Embedded Applications or UEFI Shell may fail to work properly with iLO firmware 1.30 or later.

Addressed an issue where the UEFI Shell sysconfig command may fail to set an option or become unresponsive.

Addressed an issue where an optional SATA DVD drive may not unlock and allow media to be ejected after an operating system reboot.

Addressed an issue where the system may become unresponsive during boot and experience a Red Screen (RSOD) when booting in Legacy Boot mode with a SATA M.2 drive installed. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where a USB KVM, such as the HP AF611A KVM, may not function properly after a system reboot.

Known Issues:

This revision of the System ROM may result in a VMware PSOD (crash) when a system is configured with Intel Trusted eXecution Technology (TXT) enabled and the Trusted Platform Module (TPM) in TPM 1.2 Mode. This issue is only seen in certain memory configurations. Please consult the following HPE Customer Advisory for more details on this issue. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00065453en_us

None

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the UEFI EDK2 support that provides mitigations for a variety of security vulnerabilities. The following vulnerabilities have been addressed in this System ROM release: CVE-2018-3613 CVE-2017-5731, CVE-2017-5732, CVE-2017-5733, CVE-2017-5734, CVE-2017-5735, CVE-2018-3630, CVE-2018-12178, CVE-2018-12179, CVE-2018-12180, CVE-2018-12181, CVE-2018-12182 and CVE-2018-12183. These security vulnerabilities are not unique to HPE servers.

This system ROM contains the latest Intel microcode that addresses an issue where the system may experience an Uncorrected Machine Check Exception in Bank 0 with Status containing 000F0150. This update may not address all Bank 0 machine check events with a Status containing 000F0150 but should be used before any other further service actions for issues resulting in this Integrated Management Log (IML) entry. This issue is not unique to HPE servers.

Addressed an issue in which the system may not properly boot to the HPE 8GB Dual microSD Flash USB Drive when an SD card is installed on the internal SD slot when the system is configured for Legacy Boot Mode. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where certain 3rd party USB drive keys may not function properly after a system reset when the system is configured in UEFI Boot Mode.

Addressed an issue where the HPE CN1000E-T adapter may not boot properly in Legacy Boot Mode. This issue does not impact systems configured in UEFI Boot Mode.

Addressed an issue where firmware updates staged through the HPE RESTful API may fail to properly execute on a subsequent boot and be marked with an exception in the iLO firmware installation queue.

Addressed an issue where iLO virtual media may not boot properly after setting the Boot on Next Reset option in the iLO Remote Console and Media - Virtual Media settings.

Addressed an issue where the AHS Download application from the System Utilities Embedded Applications or UEFI Shell may fail to work properly with iLO firmware 1.30 or later.

Addressed an issue where the UEFI Shell sysconfig command may fail to set an option or become unresponsive.

Addressed an issue where an optional SATA DVD drive may not unlock and allow media to be ejected after an operating system reboot.

Addressed an issue where the system may become unresponsive during boot and experience a Red Screen (RSOD) when booting in Legacy Boot mode with a SATA M.2 drive installed. This issue does not impact systems in UEFI Boot Mode.

Addressed an issue where a USB KVM, such as the HP AF611A KVM, may not function properly after a system reboot.

Known Issues:

This revision of the System ROM may result in a VMware PSOD (crash) when a system is configured with Intel Trusted eXecution Technology (TXT) enabled and the Trusted Platform Module (TPM) in TPM 1.2 Mode. This issue is only seen in certain memory configurations. Please consult the following HPE Customer Advisory for more details on this issue. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00065453en_us

• 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

• 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

• The PortRcvPkts counter was prevented from being cleared after resetting it..
• System Time Out on the configuration cycle of the 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 hung and resulted in NMI (Non-maskable interrupt) when run-ning “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a differ-ent 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 (Host Channel Adapters), 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 could not go up after reboot.
• A rare issue caused the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. 
• NC-SI (Network Controller Sideband Interface) did not work when adding the disable_stat-ic_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes submitted in version 14.22.1414 :

• A temperature normalization function calculation issue. Now the cable gain that is not pure integer is taken into account was fixed.
• An issue related to the parser of object 0x8 in ASN that caused different structure in response was fixed.
• Added the option to avoid unintentionally powering off the backplane port cage upon reboot when in standby mode.
• An issue that caused the driver to return a wrong logical OR of the 2 physical ports, when querying the vport state when the LAG was enabled wre fixed.
• Increased the Full Wire Speed (FWS) threshold value to improve EDR link results.
• An issue that resulted in “Destroy LAG” command failure if a VFs received an FLR while its affinity QPs were open.
• When RoCE Dual Port mode is enabled, tcpdump is not functional on the 2nd port.

• The PortRcvPkts counter was prevented from being cleared after resetting it..
• System Time Out on the configuration cycle of the 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 hung and resulted in NMI (Non-maskable interrupt) when run-ning “mlxfwtop –d mt4103_pci_cr0” while restarting the driver in parallel (from a differ-ent 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 (Host Channel Adapters), 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 could not go up after reboot.
• A rare issue caused the PCIe configuration cycle that arrived during the time of sw_reset to generate 2 completions. 
• NC-SI (Network Controller Sideband Interface) did not work when adding the disable_stat-ic_steering_ini field in the ini file, due to memory allocation issue for this field in the scratchpad.

Fixes submitted in version 14.22.1414 :

• A temperature normalization function calculation issue. Now the cable gain that is not pure integer is taken into account was fixed.
• An issue related to the parser of object 0x8 in ASN that caused different structure in response was fixed.
• Added the option to avoid unintentionally powering off the backplane port cage upon reboot when in standby mode.
• An issue that caused the driver to return a wrong logical OR of the 2 physical ports, when querying the vport state when the LAG was enabled wre fixed.
• Increased the Full Wire Speed (FWS) threshold value to improve EDR link results.
• An issue that resulted in “Destroy LAG” command failure if a VFs received an FLR while its affinity QPs were open.
• When RoCE Dual Port mode is enabled, tcpdump is not functional on the 2nd port.

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

Firmware Dependencies:

Problems Fixed:

Addressed an issue with NVMe drives becoming unavailable to an operating system when updating the backplane firmware.

Addressed a rare issue where NVMe drives may not be available to an operating system when installing two or more NVMe drives simultaneously.

Addressed an issue with the RBSU setting for AMD Core Performance Boost not being correctly applied in all instances.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue with NVMe drives becoming unavailable to an operating system when updating the backplane firmware.

Addressed a rare issue where NVMe drives may not be available to an operating system when installing two or more NVMe drives simultaneously.

Addressed an issue with the RBSU setting for AMD Core Performance Boost not being correctly applied in all instances.

Known Issues:

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

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

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

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

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

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

Firmware Dependencies:

System ROM V1.26 or later  

Problems Fixed:

Addressed an issue where the Integrated Lights-Out (iLO) web interface may incorrectly report the Innovation Engine is running in a degraded state.

Addressed an issue where memory telemetry data may not be reported properly in the Integrated Lights-Out (iLO) web interface or through the HPE RESTful API.

Addressed an issue where the Innovation Engine Firmware flash would fail if a previous flash attempt was interrupted and not completed successfully.

Known Issues:

This flash component will report the Current Revision of the Innovation Engine FW as “n/a” when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates.

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

Firmware Dependencies:

System ROM V1.26 or later  

Problems Fixed:

Addressed an issue where the Integrated Lights-Out (iLO) web interface may incorrectly report the Innovation Engine is running in a degraded state.

Addressed an issue where memory telemetry data may not be reported properly in the Integrated Lights-Out (iLO) web interface or through the HPE RESTful API.

Addressed an issue where the Innovation Engine Firmware flash would fail if a previous flash attempt was interrupted and not completed successfully.

Known Issues:

This flash component will report the Current Revision of the Innovation Engine FW as “n/a” when updating the Innovation Engine FW. This does not affect the flash update or impact how the Innovation Engine FW operates.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

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

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Addressed an issue where uncorrectable Quick Path Interlink (QPI) errors would not be reported properly and logged to the Integrated Management Log. Previously, the system would become unresponsive during boot with no indication of a failure.

Addressed an issue where systems configured Intel Xeon E5-2600 v4 processors and 64GB LRDIMMs may experience a Machine Check Exception or NMI event when under heavy stress. This issue is not unique to HPE Servers.

Addressed an issue where the HPE RESTful settings for Software Initiator iSCSI may not be available in the resource registry.

Known Issues:

• 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

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

• 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

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Firmware Dependencies:

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis. This security vulnerability is not unique to HPE servers and impacts any systems utilizing impacted processors.

Known Issues:

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 addresses 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 addresses 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. 2.64(B) contains updates to the component packaging and is functionally equivalent to ver. 2.64. It is not necessary to upgrade with Revision B if a previous component Revision was used to upgrade the firmware to version 2.64.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

None

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

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue is not unique to HPE servers. Please consult the following advisory for additional details.   https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00060570en_us

Firmware Dependencies:

None

Problems Fixed:

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML). This issue only impacts systems configured with Intel Xeon 2600 v4 series processors. This issue is not unique to HPE servers.

This revision of the System ROM includes the latest revision of the Intel microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 microcode which addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. 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 addresses an issue where the system could experience an unexpected reset or shutdown with no errors logged to the Integrated Management Log (IML) when processor C-states are enabled. This issue does not exist when processor C-states are disabled. This issue is not unique to HPE servers.

Known Issues:

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

Firmware:

• Fix regression where the firmware returned Time Out error code under heavy load.

UEFI

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers

16Gb Standup & 16Gb Mezzanine

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Driver progress messages are no longer displayed on SuperDome servers.
• Corrected Driver Health string format on Gen10 servers.

16Gb/32Gb Standup

Firmware:

• Fix unexpected behavior related to Diagnostic Port and Link Diagnostics operations (loopback, echo etc)

UEFI:

• Corrected Driver Health string format on Gen10 servers.
• Driver progress messages are no longer displayed on SuperDome servers.
• Fixed QUIC (QUIC Protocol)
• Removed 8G Speed and Loop Only Options from 5830C Adapter

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

8Gb Standup & 8Gb Mezzanine

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Legacy BIOS (Basic Input Output System) Selectable Boot

16Gb Standup & 16Gb Mezzanine

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.
• Dropped FCP_CMD frame by a virtual port (VP index greater than 0) logged into the fabric via Fabric Login (FLOGI) while the primary adapter port (VP0) was disabled via Global VP (Virtual Port) Options bit 2 of Initialize Multi-ID Firmware MBC (0048h).

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure) fields now require a reboot after value change:
  Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot Logical Unit (LUN), Legacy BIOS (Basic Input Output System) Selectable Boot.

16Gb/32Gb Standup

Firmware

• Bring up up-link in 32G or 16G optical environment (FEC (Forward Error Correction) only) when connected with remote device that is not setting the SN bit to zero and TC bit to 1 at the same time during the speed negotiation phase and delays transmitting NOS during LQT phase.

UEFI

• Firmware Management Protocol now supports flashing older Multiboot versions.
• Firmware Management Protocol SetImage no longer displays dots on the screen.
• The following HII (Human Interface Infrastructure)  fields now require a reboot after value change:
  FC (Fibre Channel) Tape, Fabric Assigned WWPN (World Wide Port Name), Fabric Assigned Boot LUN (Logical Unit), Legacy BIOS (Basic Input Output System) Selectable Boot.
• Changed Legacy BIOS (Basic Input Output System) Selectable Boot HII (Human Interface Infrastructure) default to Enabled.

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

• Expander would reset due to excessive LED commands
• Some SATA drives were not initially detected due to spin up time taking too long. Drives would then appear later as a hot-added drive.

• Expander would reset due to excessive LED commands
• Some SATA drives were not initially detected due to spin up time taking too long. Drives would then appear later as a hot-added drive.

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

8Gb Standup & 8Gb Mezzanine