# changelog

author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.20-1.1
changelog:
  -     *Firmware Additions**
      
        * Added support for automatically restoring the Enclosure's Serial Number on a mid-plane replacement.  This feature requires that all the OA modules and fans be plugged back into the enclosure before power is applied.  Changing power supplies during the midplane service event will not impact this feature.
        * Added additional support for Utility Ready Blades (URB):
          * Added URB SMTP support.  Metered information can now be communicated either through https, SMTP or both.
          * Added an additional URB metering proxy - present power.
          * Added URB Integrity Blade support for Integrity iLO3 server blades.
        * Added Enclosure Serial Number to the Insight Display (LCD) Enclosure Info screen.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.20-1.1
changelog:
  -     *Important Notes:**
      
      > **Onboard Administrator FW version 3.20 is no longer available for download
      **
      
      >
      
      >> An issues was discovered in Onboard Administrator (OA) firmware version
      3.20 where the OA may become unresponsive if an HP Integrity BL870c Server
      Blade, HP Integrity BL860c Server Blade, or any Integrity or ProLiant Server
      Blade with a direct attach storage, PCI expansion, or graphics expansion blade
      is installed in the enclosure.
      
      >>
      
      >> OA 3.20 was pulled from the HP download site and will be replaced with OA
      3.21 in the near future to address this issue.  The permanent fix will be to
      upgrade the OA firmware to version 3.21.
      
      >>
      
      >> For customers that have installed OA 3.20 in an enclosure, HP recommends
      the user take one of the following actions to avoid this issue.
      
                * Customers using OA 3.11 or earlier should NOT upgrade to OA 3.20.
                * Customers who have upgraded an enclosure to OA 3.20 which contains an HP Integrity BL870c Server Blade, HP Integrity BL860c Server Blade or any Integrity or ProLiant Server Blade with a direct attach storage, PCI expansion, or Graphics expansion blade should downgrade to OA 3.11 immediately.
                * Customers who have OA 3.20 installed in an enclosure and do not meet either of the above two conditions can continue using OA 3.20.
      
      > **Enclosure Power Subsystem**
      
            * As of Onboard Administrator v2.60, the Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See customer advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>
      
      > **Enclosure Dynamic Power Cap**
      
            * **Caution**: If Enclosure Dynamic Power Cap is enabled, the changes in this feature in OA v3.10 may result in servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power", or the server may be unable to power on.   This condition can be a result of reducing the Enclosure Power Cap after all server blades are powered on.  If the enclosure Power Available is lower than the iLO Advanced report of Initial Power-On Request Value - then that server could encounter this issue.  The workaround is to increase the Enclosure Power Cap to provide more Power Available to the enclosure.
            * Power-on and reboot of server blades requires that the active Onboard Administrator determine that the server power request can be satisfied.  Changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade.  HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
      
      > **VLAN**
      
            * If the Enclosure VLAN feature is enabled:
              1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the OA modules.
              2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all OA modules.
              3. Ensure that all HP 3G SAS switches are configured with the same management VLAN ID as the OA modules in that enclosure.
      
      **Firmware Dependency:**
      
      > For firmware compatibility information, please see HP BladeSystem Firmware
      Maintenance, <http://www.hp.com/go/bladesystemupdates.>
      
      **Problems Fixed:**
      
      > **General**
      
            * Fixed an issue where the enclosure configuration changes are not saved if the following error messages are in the OA Syslog after a settings change:  
         CONFIG: dhclient.leases has wrong file permissions  
         CONFIG: Wrong file permissions detected.  Please reset to factory defaults.  
      The workaround is: Save the OA configuration using GUI or CLI before updating
      the firmware, then restore the configuration after updating the firmware to
      ensure that the configuration changes are not lost. (1001068477)
      
            * Fixed a memory leak issue which caused Onboard Administrator to restart every several days when there was a HP StorageWorks 3Gb SAS BL Switch installed with Firmware Version 2.2.x.x or later. (1001062396)
            * Fixed an issue where the Onboard Administrator continuously logged I/O module temperature alerts when a Cisco Catalyst Blade Switch 3020 for HP was installed in a BladeSystem c3000 Enclosure. (1001064683)
            * Fixed an issue where a blade's "enclosure health" status as displayed by iLO could be incorrectly reported as FAILED. (1001048717)
            * Fixed an issue where extra ports were incorrectly reported for CNA Mezz in slot 1 of any full-height server blade. (1001067813)
            * Fixed an issue where fans are shown as degraded and then OK after insertion. (1001080901)
            * Fixed an issue where a change alert was not properly sent to a blade on standby to active transition. (1001056792)
            * Fixed an issue where the Onboard Administrator would not obtain the original DHCP IP address after an Onboard Administrator reboot. (1001068477)
      
      > **CLI**
      
      >
      
      >   * Fixed an issue where the CLI would sometimes abruptly exit when changing
      Onboard Administrator network settings. (1000988480)
      
      >   * Fixed an issue where a SSH or Telnet session to the Onboard
      Administrator could be lost when changing the Onboard Administrator name on a
      VLAN enabled network. (1001078330)
      
      >   * Fixed an issue where an Onboard Administrator CLI to iLO connection was
      dropped when the Onboard Administrator received a string from iLO containing
      "Connection closed", though the user did not intend to exit the iLO
      connection. (1001055763)
      
      >
      
      > **Integrity Blades**
      
      >
      
      >   * Fixed an issue where the UUID and serial number was not always updated
      properly for conjoined HP Integrity SBL server blades. (1001071032)
      
      >   * Fixed an issue where the CPU core count was not always displayed
      properly for conjoined HP Integrity server SBL blades. (1001060037)
      
      >   * Fixed an issue where the iLO IP address link for HP Integrity SBL blades
      on the Device Summary page would produce an HTTP 404 error when clicked. The
      Web Administration link on the iLO page works correctly and can be used as a
      workaround for this issue. (1001068783)
      
      >
      
      > **EBIPA**
      
      >
      
      >   * Fixed an issue where the IP address of certain blades and interconnects
      would follow the device rather than the bay. (1001058328)
      
      >
      
      > **KVM**
      
      >
      
      >   * Fixed an Onboard Administrator KVM issue where it would intermittently
      lose connection to a G7 server blade. (1001059974)
      
      >   * Fixed an Onboard Administrator KVM issue where it would display invalid
      characters when connected to a G7 server blade in suspended video mode.
      (1001074312)
      
      >
      
      > **Virtual Connect**
      
      >
      
      >   * Fixed an issue where Virtual Connect may not detect server changes after
      changing the SBL on Integrity multi-blade servers. (1001059983)
      
      >   * Fixed an issue where the Onboard Administrator would not provide VC with
      the appropriate credentials if the Onboard Administrator was not in the
      default VLAN. (1001069812)
      
      >   * Fixed an issue where powering VC Switch On and Off from Onboard
      Administrator GUI could result in "Failed" Switch health status. (1001066785)
      
      >
      
      > **VLAN**
      
      >
      
      >   * Eliminated erroneous error message, "ifconfig: eth0.3: error fetching
      interface information: Device not found", displayed on the serial console
      during an OA restart. This message can be ignored on previous Onboard
      Administrator versions. (1001078094)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.21
changelog:
  -     *Important Notes:**
      
      > **Onboard Administrator FW Version 3.21 replaces Onboard Administrator FW
      Version 3.20**
      
      >
      
      >> Onboard Administrator (OA) with firmware version 3.20 may become
      unresponsive when certain Integrity server blades, StorageWorks server blades,
      and/or Workstation partner server blades are in a c-Class BladeSystem
      enclosure. The OA and its interfaces (web GUI, CLI, LCD, etc.) may become
      sluggish or unresponsive. This occurs because the OA Firmware Version 3.20
      does not properly handle Intelligent Platform Management Interface (IPMI)
      network traffic with the affected server blades. The intensity of the issue,
      lack of responsiveness in Onboard Administrator, is proportional to the number
      of affected blades in the enclosure.
      
      >>
      
      >> The following actions are recommended:
      
      >>
      
      >> If a c-Class BladeSystem enclosure has been upgraded to OA Firmware Version
      3.20 and the enclosure contains any of the following server blades, the
      enclosure OA firmware should be immediately upgraded to OA Firmware Version
      3.21.
      
      >>
      
      >>   * HP Integrity BL860c Server
      
      >>   * HP Integrity BL870c Server
      
      >>   * HP Integrity BL890c i2 Server Blade
      
      >>   * HP Integrity BL870c i2 Server Blade
      
      >>   * HP Integrity BL860c i2 Server Blade
      
      >>   * HP StorageWorks SB40c Storage Blade
      
      >>   * HP StorageWorks Ultrium Tape Blades
      
      >>   * HP ProLiant WS460c G6 Workstation series
      
      >>   * HP ProLiant xw460c Blade Workstation
      
      >>
      
      >> If OA Firmware Version 3.20 is present in an enclosure and the enclosure
      doesn't contain any of the above server blades, then updating to OA Firmware
      Version 3.21 is not necessary.  Although HP strongly recommends that you
      upgrade to OA Firmware Version 3.21 at your earliest convinence.
      
      > **Enclosure Power Subsystem**
      
            * As of Onboard Administrator v2.60, the Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See customer advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>
      
      > **Enclosure Dynamic Power Cap**
      
            * Caution: If Enclosure Dynamic Power Cap is enabled, the changes in this feature in OA v3.10 may result in servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power", or the server may be unable to power on.   This condition can be a result of reducing the Enclosure Power Cap after all server blades are powered on.  If the enclosure Power Available is lower than the iLO Advanced report of Initial Power-On Request Value - then that server could encounter this issue.  The workaround is to increase the Enclosure Power Cap to provide more Power Available to the enclosure. 
            * Power-on and reboot of server blades requires that the active Onboard Administrator determine that the server power request can be satisfied.  Changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade.  HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
      
      > **VLAN**
      
            * If the Enclosure VLAN feature is enabled: 
              1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the OA modules. 
              2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all OA modules. 
              3. Ensure that all HP 3G SAS switches are configured with the same management VLAN ID as the OA modules in that enclosure.
      
      **Firmware Dependency:**
      
      > For firmware compatibility information, please see HP BladeSystem Firmware
      Maintenance, <http://www.hp.com/go/bladesystemupdates.>
      
      **Problems Fixed:**
      
          * Onboard Administrator (OA) firmware version 3.20 may become unresponsive if Integrity BL860c,   
      BL870c, or partner blades are in the enclosure.
      
          * Fixed an issue where modifying the Scalable Blade Link configuration of an Integrity i2 (BL890c i2, BL870c i2, or BL860c i2) server could cause Virtual Connect to become unstable.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.30
changelog:
  -     *Important Notes:**
      
      > **Enclosure Power Subsystem**
      
            * As of Onboard Administrator v2.60, the Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See customer advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>
      
      > **Enclosure Dynamic Power Cap**
      
            * **Caution**: If Enclosure Dynamic Power Cap is enabled, the changes in this feature in OA v3.10 may result in servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power", or the server may be unable to power on.   This condition can be a result of reducing the Enclosure Power Cap after all server blades are powered on.  If the enclosure Power Available is lower than the iLO Advanced report of Initial Power-On Request Value - then that server could encounter this issue.  The workaround is to increase the Enclosure Power Cap to provide more Power Available to the enclosure.
            * Power-on and reboot of server blades requires that the active Onboard Administrator determine that the server power request can be satisfied.  Changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade.  HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
      
      > **VLAN**
      
            * If the Enclosure VLAN feature is enabled:
              1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the OA modules.
              2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all OA modules.
              3. Ensure that all HP 3G SAS switches are configured with the same management VLAN ID as the OA modules in that enclosure.
      
      **Firmware Dependency:**
      
      > For firmware compatibility information, please see HP BladeSystem Firmware
      Maintenance, <http://www.hp.com/go/bladesystemupdates.>
      
      **Problems Fixed:**
      
      > **General**
      
      >   * Fixed an issue where Utility Ready Blade feature would be inactive after
      restarting the OA if URB ENABLED command is set to anything other than HTTP.
      (1001106927)
      
      >   * Fixed an issue where the Onboard Administrator could reboot if an
      invalid character was logged to a remote syslog. (1001105269)
      
      >   * Fixed an issue where Onboard Administrator terminated following many
      back-to-back blade power on/off cycles. (1001093724)
      
      >   * Fixed an issue where the Onboard Administrator would report spurious
      blade "power release" messages when a blade e-fuse was reset. (1001088537)
      
      >   * Fixed an issue where the OA incorrectly reported SAS Storage Mezzanine
      ports connected to Ethernet devices as port mismatches. This condition is not
      an error as the SAS Mezzanine ports are dynamically enabled / disabled.
      (1001087627)
      
      >   * Fixed an issue where Onboard Administrator occasionally did not clear
      all state information after a blade was removed. (1001091970)
      
      >   * Fixed an issue where a false 'NVRAM unformatted/corrupted' error message
      was displayed when downgrading from an OA 3.xx version to an OA 2.xx version.
      (1001105398)
      
      >   * Fixed an issue where the OA was not initializing interconnect power
      states at initial OA startup. (1001062495)
      
      >   * Fixed an issue where the OA improperly initialized identification
      strings for ServerNet type switches to OA CLI. (1000836203)
      
      >   * Fixed an issue where interconnect modules and server blades may not
      receive an EBIPA IP address but may receive an IP from an external DHCP server
      after an OA restart when OA VLAN is enabled. (1001115755, 1001119766)
      
      >   * Fixed an issue where the OA would reboot when executing a "SHOW SERVER
      BOOT" CLI command on server blade that has more than 8 IPL Boot Order devices.
      (1001109561)
      
      >   * Upgraded from OpenSSH 5.1p1 to OpenSSH-5.6p1. (1001083338)
      
      >
      
      > **Integrity Blades**
      
      >
      
      >   * Fixed an issue where the OA would display the CPU max core frequency
      instead of the core base frequency for HP Integrity i2 server blades.
      (1001087678)
      
      >   * Fixed an issue where rebooting the OA in an enclosure with only one
      power rail powered-up could cause HP Integrity i2 server blades to go into a
      low power performance state. (1001088287)
      
      >   * Fixed issue where HP Integrity i2 server blades would remain in low
      power mode after AC redundant power loss and OA restart. (1001109496)
      
      >   * Fixed issue which causes LOM connectivity drops when iLO is reset
      affecting the following Integrity Server Blades BL860c i2, BL870c i2, and
      BL890c i2. (1001110798)
      
      >
      
      > **CLI**
      
      >
      
      >   * Fixed an issue where the OA CLI "CONNECT SERVER SERIAL" command would
      fail when connecting to a HP ProLiant G7 server blade. (1001099114)
      
      >
      
      > **KVM**
      
      >
      
      >   * Fixed an issue where the OA-KVM feature appears to hang with the message
      "Header Received" when connecting to a G7/ILO3 blade. (1001115107)
      
      >
      
      > **IPv6**
      
      >
      
      >   * Fixed an issue where a "cannot create tmp-.conf" error message would be
      displayed if an operator attempted to change IPv6 settings. (1001104365)
      
      >   * Fixed an issue where an IPv4 connection would be lost after modifying
      IPv6 settings. (1001084431)
      
      >
      
      > **LCD**
      
      >
      
      >   * Fixed an issue where someone logged in with "Operator" privileges could
      set LCD Pin Protection Number through the Onboard Administrator browser.
      (1001090344)
      
      >   * Fixed an issue where the LCD Health Summary continues to report "missing
      server" on a full-height blade with an adjacent storage blade installed in an
      incorrect bay - after the storage blade has been removed. (1001104695)
      
      >
      
      > **Virtual Connect**
      
      >
      
      >   * Fixed an issue where the Onboard Administrator would improperly report a
      Virtual Connect Interconnect module's status if the modules E-fuse were
      tripped. (1001088267)
      
      >   * Fixed an issue where Virtual Connect 24-Port FC Interconnect Firmware
      Version information sometimes didn't appear in Onboard Administrator GUI or
      CLI output. (1001101280)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.31
changelog:
  -     Users with configurations or which are experiencing issues outlined in the
      release notes should update to this version at their earliest convenience,
      otherwise this update is optional.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.31
changelog:
  -     *Important Notes:**
      
      > **HP SIM Support**
      
      >   * If you are running HP SIM v6.1 or 6.2, please do not update to OA 3.30
      until you've applied all patches available for your HP SIM version, or upgrade
      your HP SIM to v6.3 prior to upgrading your OA environment.  If running
      versions of HP SIM prior to v6.1, you must upgrade to a HP SIM v6.3 prior to
      upgrading to OA 3.30.
      
      >
      
      > **Enclosure Power Subsystem**
      
      >
      
      >   * As of Onboard Administrator v2.60, the Onboard Administrator detects
      power supplies within the scope of Customer Advisory c01519680 and flags them
      with a "Red X" critical error condition and displays the message: "HP strongly
      recommends replacing power supply #X at the customer's earliest possible
      convenience pursuant to Customer Advisory c01519680." Flagged power supplies
      continue to function and the enclosure remains operational. See customer
      advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport
      /TechSupport/Document.jsp?objectID=c01519680>
      
      > **Enclosure Dynamic Power Cap**
      
            * **Caution**: If Enclosure Dynamic Power Cap is enabled, the changes in this feature in OA v3.10 may result in servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power", or the server may be unable to power on.   This condition can be a result of reducing the Enclosure Power Cap after all server blades are powered on.  If the enclosure Power Available is lower than the iLO Advanced report of Initial Power-On Request Value - then that server could encounter this issue.  The workaround is to increase the Enclosure Power Cap to provide more Power Available to the enclosure.
            * Power-on and reboot of server blades requires that the active Onboard Administrator determine that the server power request can be satisfied.  Changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade.  HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
      
      > **VLAN**
      
            * If the Enclosure VLAN feature is enabled:
              1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the OA modules.
              2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all OA modules.
              3. Ensure that all HP 3G SAS switches are configured with the same management VLAN ID as the OA modules in that enclosure.
      
      **Firmware Dependency:**
      
      > For firmware compatibility information, please see HP BladeSystem Firmware
      Maintenance, <http://www.hp.com/go/bladesystemupdates.>
      
      **Problems Fixed:**
      
      > **General**
      
      >   * Fixed an issue where false Link status may be indicated when the certain
      NIC adapters are mapped to an HP 1 Gb Ethernet Pass-Thru Module even when no
      cable is attached (as described in the Customer Advisory c02473928). OA 3.31
      contains the corrected 1Gb Ethernet Pass-Thru PIC Firmware version 3.0.3. PIC
      Firmware upgrade procedure is shown below.
      
      >
      
      >> **Detailed Description:** HP NC550m, NC551m, NC552m, or NC553i 10GbE Server
      Adapters may indicate a false link status when mapped to an HP 1 Gb Ethernet
      Pass-thru module even if there is no cable attached from the Pass-thru module
      to the switch. Even if a cable is either not connected or becomes
      inadvertently unplugged, and therefore no network connectivity is present, the
      server blade front panel NIC LED status will be illuminated green, indicating
      link. In addition, the operating system will display a message similar to,
      "Local area connection is now connected." This can also cause Network teaming
      and configuration issues because the NIC will always report that there is
      link.
      
      >>
      
      >> In addition, the HP System Management Homepage (SMH) NIC status is
      displayed incorrectly when a NIC cable is unplugged under any Linux operating
      system.
      
      >>
      
      >> This only occurs with the 1 Gb Pass-thru module. 10 Gb Pass-thru and 1/10Gb
      switches do not exhibit this issue.
      
      >>
      
      >> **Resolution:** for the applicable configurations described above, upgrade
      the OA Firmware to 3.31, and follow the procedure below for all 1 Gb Pass-thru
      modules in the enclosure:
      
      >>
      
      >>   1. Log into the OA CLI interface as an Administrator
      
      >>   2. OA> show update  
      This will show current and available firmware versions for programmable
      devices. OA 3.31 will indicate the newly available Pass-Thru PIC Firmware
      3.0.3.
      
      >>   3. OA> update device icbay <bay number | all>  
      This will update the specified interconnect bay, note that bay1 is 1A, etc.,
      as shown in the previous command
      
      >>   4. OA> show update  
      Run this again to confirm that the versions now match
      
            * Fixed an issue where upgrading from Onboard Administrator (OA) 3.11 to OA 3.20, 3.21 or 3.30, under defined circumstances, may cause Virtual Connect (VC) to disconnect its Fibre Channel (FC) connections.  This is limited to systems using a HP ProLiant or Integrity Blade with a FlexFabric Adapter (Mezzanine or LOM) and either a
              * Fibre Channel over Ethernet (FCoE) connection to a VC FlexFabric module or a
              * FC connection from a FC Mezzanine to a VC FC module
      
      > > **Detailed Description:** OA firmware revisions 3.20, 3.21, and 3.30
      identify the capabilities of the embedded G7 FlexFabric Adapter LOM or
      FlexFabric Adapter Mezzanine differently than OA firmware 3.11.  If a VC
      profile had previously been created and assigned to a blade using OA firmware
      3.11, then the newer OA firmware will detect a VC profile mismatch. This
      mismatch may cause Virtual Connect to disconnect the blade FC or FCoE SAN
      connections after a VC firmware upgrade or when a user issues a VC Manager
      (VCM) reset command.
      
      >>
      
      >> **_All_** the following must be true to be exposed to this condition on a
      VC firmware upgrade or VCM reset:
      
      >>
      
      >>   * A VC profile with a SAN fabric must have been assigned to that blade
      with OA firmware version 3.11
      
      >>   * A blade must have at least one HP FlexFabric Adapter (including LOM or
      Mezzanine)
      
      >>   * The current version of OA firmware is OA 3.20, 3.21, or 3.30
      
      >>   * The blade has not been removed/reinserted, nor the OA CLI Reset Server
      command run, nor had its profile reassigned, since the OA firmware was
      upgraded to OA 3.20 or later.
      
      >>
      
      >> Note that VC profiles assigned to a blade using OA version 3.20 or later
      are not impacted.  
      Note that OA firmware version 3.11 is the first OA version to support
      FlexFabric Adapters.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.32
changelog:
  -     *Important Notes:**
      
      > **HP SIM Support**
      
      >   * If you are running HP SIM v6.1 or 6.2, please do not update to OA 3.30
      until you've applied all patches available for your HP SIM version, or upgrade
      your HP SIM to v6.3 prior to upgrading your OA environment.  If running
      versions of HP SIM prior to v6.1, you must upgrade to a HP SIM v6.3 prior to
      upgrading to OA 3.30.
      
      >
      
      > **Enclosure Power Subsystem**
      
      >
      
      >   * As of Onboard Administrator v2.60, the Onboard Administrator detects
      power supplies within the scope of Customer Advisory c01519680 and flags them
      with a "Red X" critical error condition and displays the message: "HP strongly
      recommends replacing power supply #X at the customer's earliest possible
      convenience pursuant to Customer Advisory c01519680." Flagged power supplies
      continue to function and the enclosure remains operational. See customer
      advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport
      /TechSupport/Document.jsp?objectID=c01519680>
      
      > **Enclosure Dynamic Power Cap**
      
      >
      
      >   * **Caution**: If Enclosure Dynamic Power Cap is enabled, the changes in
      this feature in OA v3.10 may result in servers halted in POST after a reboot
      and status Degraded due to "Insufficient Enclosure Power", or the server may
      be unable to power on.   This condition can be a result of reducing the
      Enclosure Power Cap after all server blades are powered on.  If the enclosure
      Power Available is lower than the iLO Advanced report of Initial Power-On
      Request Value - then that server could encounter this issue.  The workaround
      is to increase the Enclosure Power Cap to provide more Power Available to the
      enclosure.
      
      >   * Power-on and reboot of server blades requires that the active Onboard
      Administrator determine that the server power request can be satisfied.
      Changes to power supplies, input power feeds, power redundancy mode, power
      capping, power limit and the power state of other blades and devices in the
      enclosure may affect the ability to power on a server blade or reboot a server
      blade.  HP recommends testing a fully configured enclosure from a completely
      powered-off state before finalizing the enclosure power settings.
      
      > **VLAN**
      
      >
      
      >   * If the Enclosure VLAN feature is enabled:
      
      >     1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC
      interconnect modules are configured with the same management VLAN as the OA
      modules.
      
      >     2. Ensure all enclosures with Virtual Connect multi-enclosure domains
      have the same management VLAN configuration for all VC interconnects and all
      OA modules.
      
      >     3. Ensure that all HP 3G SAS switches are configured with the same
      management VLAN ID as the OA modules in that enclosure.
      
      **Firmware Dependency:**
      
      > For firmware compatibility information, please see HP BladeSystem Firmware
      Maintenance, <http://www.hp.com/go/bladesystemupdates.>
      
      **Problems Fixed:**
      
      > **General**
      
      >   * Fixed a customer reported issue.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.50
changelog:
  -      OA 3.50 is required for HP Gen8 server blades.  Please update you enclosures with OA 3.50 _**before**_ inserting a Gen8 server blade into the enclosure.
        * For all other configurations OA 3.50 is recommended.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.50
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware Support**
          * HP ProLiant BL460c Gen8 Server Blade
        * **Firmware Additions**
          * Active Health System (AHS) - Provides a log of historical information and the most recent states and events for ProLiant servers for the last 24 hours or longer. This information is intended to provide a service advantage when diagnosing and repairing servers, as well as for debug of customer issues.
          * Intelligent Power Discovery (IPD) - Added IPD support to the Onboard Administrator.
          * NIC display enhanced to correlate server NIC labels between the OA, iLO and VC
          * Increased the private key size used for security from 1024 bits to 2048 bits.
          * Updated OA to use the June 27, 2011 time zone data files.  The list of newly supported time zones includes: 
            * America\Argentina\Salta
            * America\Bahia_Banderas
            * America\Kralendijk
            * America\Lower_Princes
            * America\Matamoros
            * America\Metlakatla
            * America\North_Dakota\Beulah
            * America\Ojinaga
            * America\Santa_Isabel
            * America\Sitka
            * Antarctica\Macquarie
            * Asia\Kathmandu
            * Asia\Novokuznetsk
            * Pacific\Chuuk
            * Pacific\Pohnpei


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.50
changelog:
  -     *Important Notes:**
      
        * **HP Gen8 Blade Support**
          * HP ProLiant Gen8 server blades require updating the Onboard Administrator to version 3.50 or later and Virtual Connect to version 3.51 or later _**before**_ inserting your ProLiant Gen8 server blade into an enclosure.
        * **HP SIM Support**
          * If you are running HP SIM v6.1 or 6.2, please do not update to OA 3.30 until you've applied all patches available for your HP SIM version, or upgrade your HP SIM to v6.3 prior to upgrading your OA environment. If running versions of HP SIM prior to v6.1, you must upgrade to a HP SIM v6.3 prior to upgrading to OA 3.30.
        * **Enclosure Power Subsystem**
          * As of Onboard Administrator v2.60, the Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See customer advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>
        * **Enclosure Dynamic Power Capping**
          * **Caution: **Onboard Administrator v3.10 or later: Enabling Enclosure Dynamic Power Capping may result in:
          * Servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power"  
      or
      
          *  A server may be unable to power on  
      This condition can be a result of reducing the Enclosure Power Cap after all
      server blades are powered on. If the enclosure Power Available is lower than
      the iLO Advanced report of Initial Power-On Request Value from a server blade
      - then that server blade could encounter this issue. The workaround is to
      increase the Enclosure Power Cap to provide more power available to the
      enclosure.
      
          * Power-on and reboot of server blades requires that the active Onboard Administrator determines that the server power request can be satisfied. Changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade. HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
        * **VLAN**
          * If the Enclosure VLAN feature is enabled:
        1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the Onboard Administrator modules.
        2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all Onboard Administrator modules.
        3. Ensure that all HP 3G SAS switches are configured with the same management VLAN ID as the Onboard Administrator modules in that enclosure.
      
      **Firmware Dependency:**
      
        * For firmware compatibility information please see HP BladeSystem Firmware Maintenance, <http://www.hp.com/go/bladesystemupdates>.
      
      **Problems Fixed:**
      
        * **General**
          * Fixed an issue where an Enclosure IP failure could cause the OA to be inoperable for a short period of time during a transition from Standby to Active.
          * Fixed an issue where both OAs claim to be active resulting in network loop flooding at OA startup.
          * Fixed an issue where the CLI command UPDATE DEVICE TRAY would not execute the update.
          * Fixed an issue where Single Sign On to iLO failed.
          * Fixed an issue where the Onboard Administrator occasionally displayed incorrect DIMM memory total for a blade.
          * Fixed an issue where only one OA is accessible after upgrading redundant OAs from OA 3.21 to OA 3.30 where the OA continues to reboot for 30 minutes due to internal error.
          * Fixed an issue where some third party PCIe option cards could prevent the PCI Expansion blade from powering up properly. The PCI Expansion blade firmware must be upgraded to version 2.26 which is contained within OA 3.50.
          * Fixed an issue where an OA that had been up for a very long time might restart due to an out of memory condition.
          * Fixed an issue where the OA would improperly set an interconnect module health status to OK when the interconnect module had an internal fault.
          * Fixed an issue where any interconnect bay between 5 and 8 were not showing in "Show All/Show Config".
          * Fixed an issue where OA would lose its "Enclosure IP mode" during repeated failovers.
          * Fixed an issue where the OA could possibly drop HTTP packets under heavy loads.
          * Fixed an issue where under rare circumstances the OA would hang at boot step [7/16] and never recover even after flash disaster recovery.
          * Fixed an issue where some server blades would not initially power on when enclosure power cap was enabled.
          * Fixed a rare condition where the OA would clear a server blade's Virtual Serial Number and Virtual UUID during an iLO communication drop-out.
          * Fixed an issue where under rare circumstances the OA could experience a segmentation fault after midplane replacement.
          * Fixed an issue where under rare circumstances the OA LCD service could cause a segmentation fault and reboot.
        * **CLI**
          * Fixed an issue where the OA CLI Show Enclosure Temp command does not always display temps for G7 server blades.  If no server blade temps are shown then the OA incorrectly displays the enclosure ambient temperature instead.
        * **GUI**
          * Fixed an issue with the power meter graphical view which caused Firefox timeout issues.
        * **KVM**
          * Set KVM default minimum video resolution to 800 x 600 pixels.
        * **DVD**
          * Fixed an issue where the SET SERVER DVD CONNECT command would occasionally not take effect.
        * **Network**
          * Fixed an issue where NTP can be enabled or disabled from Standby OA.
          * Fixed an issue where the OA could display stale or incorrect IP information for DHCP setting.
          * Fix an issue where the OA enabled for remote logging becomes unresponsive due to a DNS server outage.
        * **VLAN**
          * Fixed an issue where the OA GUI would not display error messages if an error occurred while saving VLAN configuration settings.
          * Fixed an issue where the OA may lose communication with an iLO under the following condition: VLAN is enabled, the blade's iLO is assigned a non-default VLAN ID different than that of the OA's VLAN ID, and an OA failover is performed.
        * **SNMP**
          * Fixed an issue where the standby OA's ping responses slow down over time and the OA could reboot due to out of memory (after approximately a month) when SNMP is enabled.
        * **LDAP**
          * Fixed an issue where the LDAP Test page (and TEST LDAP CLI command) did not properly handle a directory server at an IPv6 address.
          * Fixed an issue where the OA's LDAP server IP address was incorrectly set during a configuration upload operation.
          * Enhance LDAP certificate validation to also consider the Subject Alternative Name field.
          * Enhance LDAP certificate validation to enforce Valid Before/After date limits on the server certificate.
          * Enhance LDAP certificate validation to enforce CN matches when FIPS mode is enabled.
          * Enhance LDAP Certificate Authority signature checking to observe some Ext3 flags.
        * **Thermals**
          * Fixed display of Ambient Temperature Sensor on some G7 and later blades.
          * Fixed an issue where quickly removing and inserting fans could cause the OA to get out of sync with the actual fans present in the chassis.
          * Fixed an issue where a fan's status would randomly indicate a degraded or failed status and then immediately return to an OK status.
          * Fixed an issue where the "update show fan" command would not always display the correct fan slot in a c3000 enclosure.
          * Fixed an issue that caused critical fan failures when relocating mismatched fans on a c3000 enclosure.
          * Fixed an issue where OA would unnecessarily ramp fan speeds due to a temporary loss of communication with iLO.
        * **VC**
          * Fixed an issue where the OA failed to display the Flex NICs properly after a VC failover, Active VC IP address change or a VC domain name change.
          * Fixed an issue where back-to-back switchovers of the OA could result in a corrupted VC/OA configuration.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.55
changelog:
  -     *Important Notes**
      
        * **HP Gen8 Blade Support**
          * OA 3.30, OA 3.31 and OA 3.32 will correctly power up and perform the initial configuration of Gen8 Server Blades.  However, when used with Virtual Connect, subsequent configuration changes to the network and storage profiles may not be handled properly resulting in incorrect port configurations.  OA 3.50 is required for use with Virtual Connect and Gen8 blades.  For more details, refer to the Customer Advisory (ID= c03246192) Onboard Administrator and Virtual Connect - HP ProLiant Gen8 Server Blades Require Onboard Administrator Firmware Version 3.50 (or Later) and Virtual Connect Firmware Version 3.51 (or Later): <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03246192>.
          * Correct configuration of HP ProLiant Gen8 server blades requires updating the Onboard Administrator to version 3.50 or later and Virtual Connect to version 3.51 or later before inserting your ProLiant Gen8 server blade into an enclosure. Failure to upgrade the OA before inserting a Gen8 blade in the enclosure will result in a profile pending status with Virtual Connect.
          * Versions of the OA prior to OA 3.30 will not properly configure Gen8 server blades and should _not _be used.  
        * **HP SIM Support**
          * Version 6.1 and 6.2 of HP SIM do not discover and associate enclosures running OA versions 3.30 or later.  If you are running HP SIM v6.1 or 6.2, please do not update to OA 3.30 or later until you've applied all patches available for your HP SIM version, or upgrade your HP SIM to v6.3 prior to upgrading your OA environment. If running versions of HP SIM prior to v6.1, you must upgrade to HP SIM v6.3 or later prior to upgrading to OA 3.50 or later. 
        * **Enclosure Power Subsystem**
          * Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See Customer Advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>.
        * **Enclosure Dynamic Power Capping**
          * **Caution:** Onboard Administrator v3.10 or later: Enabling Enclosure Dynamic Power Capping may result in one of the following: 
            * Servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power"
            * A server may be unable to power on
      This condition can be a result of reducing the Enclosure Dynamic Power Capping
      after all server blades are powered on. If the enclosure Power Available is
      lower than the iLO Advanced report of Initial Power-On Request Value from a
      server blade - then that server blade could encounter this issue. The
      workaround is to increase the Enclosure Dynamic Power Capping to provide more
      power available to the enclosure devices.
      
          * With Enclosure Dynamic Power Capping enabled, changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade. HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
        * **VLAN **
          * If the Enclosure VLAN feature is enabled: 
            1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the Onboard Administrator modules.
            2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all Onboard Administrator modules.
            3. Ensure that all HP SAS Switches are configured with the same management VLAN ID as the Onboard Administrator modules in that enclosure.
      
      **Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General**
          * OA 3.50 does not support SSO (single sign on) to iLO 2 (ProLiant G6, G5 or G1 server blades) when LDAP authentication is used with the syntax of <domain>\<user>. The syntax works correctly with OA 3.55.  See Customer Advisory c03234658for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03234658>.
          * When LDAP-based authentication is used to access the OA, if the user name syntax contains a "," (comma), Single Sign-On (SSO) to any iLOs will fail after several attempts. An example of such syntax is:  CN=smith,CN=users,DC=domain,DC=com  Once this issue is encountered, all other users (local users, LDAP users with syntaxes without a comma, or users accessing the OA via HP-SIM) are also impacted (those users will not be able to SSO to any iLO's). The syntax works correctly with OA 3.55.
          * OA 3.50 (or prior) EBIPA page does not refresh the Management IP address for CBS 3020 Interconnect Modules (Cisco Catalyst Blade Switch) if the Switch firmware is upgraded from version 12.2(55)SE4 (or earlier) to version 12.2(58)SE1 (or later) without resetting the OA or the switch. OA 3.55 refreshes the correct IP address automatically.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.56
changelog:
  -     Updating to OA 3.56 is optional, though if you are experiencing security
      issues outlined in the release notes or thermal issues with a HP BL460c Gen8
      server blade then you should consider updating to OA 3.56.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.56
changelog:
  -     *Important Notes**
      
        * **HP Gen8 Blade Support**
          * OA 3.30, OA 3.31 and OA 3.32 will correctly power up and perform the initial configuration of Gen8 Server Blades.  However, when used with Virtual Connect, subsequent configuration changes to the network and storage profiles may not be handled properly resulting in incorrect port configurations.  OA 3.50 is required for use with Virtual Connect and Gen8 blades.  For more details, refer to the Customer Advisory (ID= c03246192) Onboard Administrator and Virtual Connect - HP ProLiant Gen8 Server Blades Require Onboard Administrator Firmware Version 3.50 (or Later) and Virtual Connect Firmware Version 3.51 (or Later): <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03246192>.
          * Correct configuration of HP ProLiant Gen8 server blades requires updating the Onboard Administrator to version 3.50 or later and Virtual Connect to version 3.51 or later before inserting your ProLiant Gen8 server blade into an enclosure. Failure to upgrade the OA before inserting a Gen8 blade in the enclosure will result in a profile pending status with Virtual Connect.
          * Versions of the OA prior to OA 3.30 will not properly configure Gen8 server blades and should _not _be used.  
        * **HP SIM Support**
          * Version 6.1 and 6.2 of HP SIM do not discover and associate enclosures running OA versions 3.30 or later.  If you are running HP SIM v6.1 or 6.2, please do not update to OA 3.30 or later until you've applied all patches available for your HP SIM version, or upgrade your HP SIM to v6.3 prior to upgrading your OA environment. If running versions of HP SIM prior to v6.1, you must upgrade to HP SIM v6.3 or later prior to upgrading to OA 3.50 or later. 
        * **Enclosure Power Subsystem**
          * Onboard Administrator detects power supplies within the scope of Customer Advisory c01519680 and flags them with a "Red X" critical error condition and displays the message: "HP strongly recommends replacing power supply #X at the customer's earliest possible convenience pursuant to Customer Advisory c01519680." Flagged power supplies continue to function and the enclosure remains operational. See Customer Advisory c01519680 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01519680>.
        * **Enclosure Dynamic Power Capping**
          * **Caution:** Onboard Administrator v3.10 or later: Enabling Enclosure Dynamic Power Capping may result in one of the following: 
            * Servers halted in POST after a reboot and status Degraded due to "Insufficient Enclosure Power"
            * A server may be unable to power on
      This condition can be a result of reducing the Enclosure Dynamic Power Capping
      after all server blades are powered on. If the enclosure Power Available is
      lower than the iLO Advanced report of Initial Power-On Request Value from a
      server blade - then that server blade could encounter this issue. The
      workaround is to increase the Enclosure Dynamic Power Capping to provide more
      power available to the enclosure devices.
      
          * With Enclosure Dynamic Power Capping enabled, changes to power supplies, input power feeds, power redundancy mode, power capping, power limit and the power state of other blades and devices in the enclosure may affect the ability to power on a server blade or reboot a server blade. HP recommends testing a fully configured enclosure from a completely powered-off state before finalizing the enclosure power settings.
        * **VLAN **
          * If the Enclosure VLAN feature is enabled: 
            1. Ensure that all HP Virtual Connect Ethernet and Virtual Connect FC interconnect modules are configured with the same management VLAN as the Onboard Administrator modules.
            2. Ensure all enclosures with Virtual Connect multi-enclosure domains have the same management VLAN configuration for all VC interconnects and all Onboard Administrator modules.
            3. Ensure that all HP SAS Switches are configured with the same management VLAN ID as the Onboard Administrator modules in that enclosure.
      
      **Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General**
          * HP ProLiant BL460c Gen8 server blades not properly cooled after a BIOS firmware upgrade. See Customer Advisory c03365221 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03365221>.
          * Security enhancements. See Security Bulletin c03315912 for more information: <http://h20566.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c03315912>.
          * Beginning with version 3.50, the OA could optionally generate 2048-bit keys for use with SSH and SSL. However, on upgrade the OA would retain existing 1024 bit keys to avoid disrupting ongoing communication. To switch from 1024-bit to 2048-bit keys you needed to first reset the OA configuration to factory defaults which would cause the generation of new keys. Beginning with version 3.56, a new CLI command "GENERATE KEY" can be used to force new keys to be generated at any time, i.e. without first resetting to factory defaults. For more information, refer to the section on new features.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.60
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware Support**
          * HP ProLiant WS460c Gen8 Workstation Blade
          * HP ProLiant BL660c Gen8 Server Blade
          * HP Virtual Connect Flex-10/10D Module for c-Class BladeSystem
        * **Firmware Additions**
          * Enclosure Firmware Management (EFM) allows administrators to define a single firmware baseline (SPP version) for the G5, G6, G7 and Gen8 Server Blades in a c-Class enclosure.  The administrator can have the firmware updated to the baseline on server insertion, during a pre-defined maintenance window, or manually.  The Onboard Administrator maintains logs of the EFM firmware updates, and reports on compliance with the established baseline. 
            * EFM supports HP Service Pack for ProLiant (HP SPP) 2011.09 or newer.  Please review the HP Service Pack for ProLiant (HP SPP) documentation and release notes for issues and information about supported firmware components, <http://www.hp.com/go/spp>.
            * Enclosure Firmware Management (EFM) is not supported on the following OA Hardware Modules: 
              * HP BladeSystem c3000 Onboard Administrator (PN# 448589-B21, 461514-B21)
              * HP BladeSystem c7000 Onboard Administrator (PN# 412142-B21)
          * Administrators can now define a custom Login Banner.  This can be used, for example, to display your specific Terms of Service (TOS) when logging in to the OA.
          * The OA IPv6 setting on the Enclosure TCP/IP Settings Page->IPv6 Settings tab now enables IPv6 traffic for all the devices in the enclosure (IPv6, RA, DHCPv6). 
            * The OA will display IPv6 addresses assigned to the iLO
            * You must have IPv4 infrastructure to retain complete manageability through the OA; e.g. virtual media, single sign on, Enclosure Firmware Management.
          * Insight Remote Support enables health and inventory data for the enclosure to be collected by HP to expedite resolution of your issues.  Examples of data that is collected include: 
            * Enclosure name
            * Enclosure product name
            * Enclosure part number
            * Enclosure serial number
            * Enclosure manufacturer name
            * Onboard Administrator firmware version
            * Onboard Administrator IP and MAC addresses
          * New CLI command SET SERIAL BAUD "<Baud Rate>" configures the baud rate settings for the OA serial console port. Valid Baud Rate values are:  9600, 19200, 38400, 57600, and 115200.
          * New SHOW HEALTH CLI command provides a summary of the health/status of all components in the enclosure.
          * Beginning with iLO 3 (G7 server blades) firmware version 1.50 and iLO 4 (Gen8 server blades) firmware version 1.05 a change in the server status reported by the Onboard Administrator will be observed in cases where a server attempts to power on but power on is delayed or denied.  In addition to the diagnostic status information indicating the cause of the power delay or denial, an additional diagnostic status indication will now be reported by the Onboard Administrator indicating that the server blade is reporting an internal degraded status.  This is an intentional behavior change.
          * Enhanced the HPONCFG CLI command to allow variable substitution. HPONCFG sends a RIBCL script to the specified HP ProLiant server blades with the access level and privilege of the current user. Command syntax is as follows:  
              HPONCFG [NOAUTOLOGIN] [SUBSTITUTE [TEST] {<variable>="value" [,<variable>="value"[,]]}] {ALL | <bay number> [{ , | - } <bay number>]} {<< <end marker> | <from_url> [<to_url>]}  
      To use variable substitution, specify the token SUBSTITUTE followed by a list
      of variable assignments. Variable name and its value can include spaces,
      numbers, or any printable characters. Up to 25 variables are supported. The
      maximum length of variable name is 48 characters.  Specify TEST to review the
      RIBCL script that will be sent to the iLO without executing the script.  e.g.
      The following command line would replace the string "%NAME%" in the RIBCL
      script that gets executed with "MY_NAME":  
              HPONCFG SUBSTITUTE NAME="MY_NAME"
          * Updated OA SNMP to support the CPQRACK-MIB version 1.16.  Please see the HP Systems Insight Manager MIB Kit v9.20 for more details on the CPQRACK-MIB, <http://h18013.www1.hp.com/products/servers/management/hpsim/mibkit.html>.
          * A new warning message, "Mixing different power supply models is not supported. The power supply in bay #X must be replaced with the proper part number.", is issued and the Power sub-system is degraded when different types of power supplies are mixed in c3000 enclosures.
          * With previous versions of the OA, packet flooding conditions on the management network could cause the OA to stop processing incoming packets.  Once triggered, this condition would persist until the OA was restarted.  The current version of the OA is more resilient to this condition, and will resume normal packet processing once the packet flooding conditions have cleared.  HP continues to strongly recommend that OA network ports be separate from your production network.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.60
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General **
          * Previous versions logged transient network link status changes for the OA, servers and interconnects.  For example:  
      Apr 30 06:48:17 OA: Network link to server 6 is down  
      Apr 30 06:49:02 OA: Network link to server 6 is up
      
        * **Thermals**
          * OA 3.5x firmware versions track cumulative fan communication errors during continuous OA uptime.  Once a default threshold of cumulative errors is exceeded, the fan is marked as failed.  Some Active Cool 200 fans experience intermittent fan communication failures that will trigger this failure typically within 3 months of continuous operation, although the fans are otherwise operating normally.  Version 3.60 implements a different algorithm that avoids marking false failures with this generation of fans.  See Customer Advisory c03395857 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03395857>.
        * **IPv6**
          * Alertmail now works with IPv6.
          * The DHCPv6 lease was reset each time the OA network was restarted by an OA reboot or other network configuration changes. This resulted in the OA inadvertently failing to request its existing IPv6 address when attempting to renew its IPv6 address via DHCP and typically receiving a different IPv6 address each renewal.
          * Under some conditions, users were unable to add a second IPv6 static address or to remove static IPv6 addresses thru the WEB GUI.
          * When the user specified both the Standby IPv6 DNS Server 1 and IPv6 DNS Server 2 thru the OA WEB GUI, the information for IPv6 DNS Server 1 was inadvertently discarded.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.70
changelog:
  -     *Enhancements/New Features:**
      
        * **Firmware Additions**
          * **FIPS**
            * FIPS, or _Federal Information Processing Standards_, is a set of publications that document standards for implementing security. More information can be found on "National Institute of Standards and Technology" website <http://csrc.nist.gov/publications/PubsFIPS.html>. OA 3.70 provides a user selectable FIPS Mode of operation wherein: 
              * only FIPS 140-2 approved algorithms such as AES, 3DES and SHA are permitted,
              * strong passwords are enforced,
              * integrity self-tests are performed whenever encryption services are used (Known Answer Tests - KATs),
              * and partition integrity checks on boot are performed.
            * Enabling FIPS mode on an OA module or redundant pair of OA modules automatically forces the OA module(s) to be reset to factory defaults due to FIPS requirements. Please configure the OA module(s) for FIPS mode operation prior to performing any other enclosure or OA configuration including configuration of Virtual Connect.
            * Some features are permanently disabled in FIPS mode for compliance reasons: 
              * Telnet access
              * Enclosure IP mode
              * SNMP
              * OA Firmware downgrades
              * Set Factory Defaults
              * Upload support dumps
              * Disable strong passwords
              * Disable LCD PIN protection
            * The default security settings in OA 3.70 have been upgraded and are now equivalent to prior version's "Enforce Strong Encryption" setting. The "Enforce Strong Encryption" setting has been removed from OA 3.70.
            * Upon changing FIPS modes, all security related data is cleared from the OA, including certificates, keys, and other critical security parameters. Please refer to the security section in the Onboard Administrator user guide for more information.
            * FIPS is not supported on the following OA Hardware Modules: 
              * HP BladeSystem c3000 Onboard Administrator (PN# 448589-B21, 461514-B21)
              * HP BladeSystem c7000 Onboard Administrator (PN# 412142-B21)
          * **GUI**
            * Internet Explorer 10 (IE 10) is supported in compatibility mode only.  The IE 10 "Windows 8 - Style UI Mode" is not supported.
            * OA GUI Management Console now allows login to 6Gb SAS Interconnect module Interfaces if VLANs are defined for the Interconnect modules.
          * **IPv6**
            * OA 3.70 adds a group box in the Management Processor Information tab on the iLO - Device Bay page, where a radio button is displayed to allow selection of the current IPv4 address and all IPv6 addresses assigned to the iLO.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.70
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General **
          * If using OA 3.6x, HP BladeSystem c3000 Enclosures containing both of the following power supply models show the power subsystem degraded, with one or more power supplies being marked as mismatched. See Customer Advisory c03509204 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03509204>. 
            * HP 1200W Common Slot Silver Hot Plug Power Supply Kit 
              * Part number 437572-B21
              * Spare part number 441830-001
            * HP 1200W Common Slot Silver Hot Plug Power Supply Kit 
              * Part number 500172-B21
              * Spare part number 498152-001


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.71
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General **
          * The power subsystem might be reported as degraded and the HP 1200W Common Slot-48VDC Hot Plug Power Supply DC power supplies (HP part number: 437573-B21) as failed due to a device mismatch when running OA firmware 3.6x or 3.70 in a c3000 enclosure. See Customer Advisory c03571787 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03571787>.
          * Intermittent  issue where server name was reset to default after power cycle.
          * Intermittent issue that would incorrectly reflect the HP 6120XG Ethernet Blade Switch and the HP ProCurve 6120G/XG Blade Switch status after the switch was rebooted or after a switch firmware update was performed.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.72
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **Authentication **
          * When the OA is enabled for TFA and the certificate chain contains more than 2 CA certificates previous versions of the OA would not establish an SSL Connection.  The OA now accepts a max depth of 7 CA Certificates.
        * **Integrity Server Blades**
          * Under rare circumstances an HP Integrity BL8x0c i2 or BL8x0c i4 Server Blade configured with Virtual Connect may momentarily lose its network connection during an OA failover. See Customer Advisory c03613140 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03613140>.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.73
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware**
          * Added support for the "HP 2650W HE PSU" power supply for the HP BladeSystem c7000 Enclosure.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.73
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * In the HP BladeSystem c3000 Enclosure with at least one Cisco Catalyst Blade Switch 3020 for HP c-Class BladeSystem installed, OA enclosure thermal management may not provide sufficient cooling to allow some blade configurations to operate at optimal performance under heavy workloads.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.01
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware Additions**
          * HP 2650W HE PSU power supply for the HP BladeSystem c7000 Enclosure.
          * Brocade 16Gb/16 SAN Switch for HP BladeSystem c-Class
          * Brocade 16Gb/28 SAN Switch for HP BladeSystem c-Class
          * Brocade 16Gb/28 SAN Switch Pwr Pk+ for HP BladeSystem c-Class
          * HP 6125XLG Blade Switch
          * HP FlexFabric 10Gb 2-port 534FLB Adapter
          * HP FlexFabric 10Gb 2-port 534M Adapter
          * HP QMH2672 16Gb FC HBA for BladeSystem c-class
        * **Features Additions and Changes**
          * IPv6 support to EBIPA (Enclosure Bay IP Addressing) for interconnect modules and server blades
          * Language Pack Support to allow for Japanese and Chinese GUI interfaces
          * SNMP3 support
          * Enhanced the UPDATE ILO CLI commandto to support server blades with the Trusted Platform Module (TPM) enabled
          * The sender's email address for alertmail notifications
          * Monitoring of status of battery on OA module(s) with low battery level indication reported as OA diagnostic status.  When a low battery level status indication is encountered, the spare battery kit (HP p/n 708907-001) should be used for replacement of the battery as soon as possible as enclosure configuration settings may be lost if the OA loses power.
          * Two-Factor Authentication user certificates no longer require the "sslclient" property to be set.
          * Removed support "diffie-hellman-group1-sha1" as supported SSH key exchange option by default.  This may impact the ability of older SSH clients which do not support more contemporary and secure SSH key exchange options to connect to OA modules running OA 4.01.  This can be re-enabled via the "SET SECURESH SERVER KEX DHG1" CLI command.
        * **Browser Support**
          * Updated web browser support as follows: 
            * Microsoft Internet Explorer 8, 9, and 10
            * Mozilla Firefox ESR 17
            * Google Chrome


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.01
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General**
          * Partnering alert on HP BladeSystem Insight Display LCD may not be cleared. See Customer Advisory c03801002 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03801002>.
          * When running OA firmware versions 3.6x or 3.7x with the OA deployed in a large, flat management network topology, the OA reboots after logging an OA system log similar to the following: 
            * Nov 11 22:04:54 Kernel: Out of Memory: Kill process 10562 (iptables) score 822 and children.
          * KVM connections to iLO 2 server blades would fail if the default Remote Control Telnet port was changed in iLO.
          * HP Insight Management does not properly report partnered blades installed in lower slots when associated with a full height blade such as the HP ProLiant BL680c. This issues does not occur when the partner blade is associated with a half height blade such as the HP ProLiant BL460c.
          * Insight Display reports a config error when HP Integrity BL890c i2, HP Integrity BL870c i2, or  HP Integrity BL860c i2 Server Blades are paired with a tape storage blade.
          * OA 'Link loss failover' does not function properly after performing OA FW SYNC.
          * Primary OA would stop responding to network requests with a "HTTP service is unresponsive" error message under certain management network configurations.
          * The OA firmware behavior related to downloading files via a URL specifying authenticated FTP as the protocol has changed.  This new behavior results in the home directory of the specified user being used as the relative root path in the URL.  A double "//" must now be specified at the beginning of the path specification within the URL in order to specify an absolute path that avoids the use of the specified user's home directory in the path.  For example: "ftp://user:password@host//path/to/file" will specify an absolute path of /path/to/file while "ftp://user:password@host/path/to/file" will specify a path to /home/user/path/to/file.
        * **Alertmail**
          * False alertmail messages are sent indicating the enclosures status as degraded followed by another message indicating the status has changed to OK.
        * **Authentication**
          * When the OA is enabled for Two-Factor Authentication (TFA) and the certificate chain contains more than 2 CA certificates, previous versions of the OA would not establish an SSL Connection.  The OA now accepts a max depth of 7 CA Certificates.
          * OA reboots with a segmentation violation when uploading a user certificate with an invalid certificate authority (CA) path.
        * **Enclosure Firmware Management (EFM)**
          * The OA EFM configuration would be improperly configured after restoring a previously saved OA configuration script.
          * When observing the EFM update process from a server blade console, note that manual user interaction with any user dialog screens presented can cause the EFM process for that server blade to fail.
        * **FIPS**
          * When FIPS mode has been enabled for the OA module(s) within an enclosure and a redundant OA which does not have FIPS mode enabled is later introduced into the enclosure, the current FIPS mode configuration will not be successfully synchronized to this newly introduced OA module.  To work around this issue, it is recommended that the OA module be reset to factory defaults prior to being introduced into a redundant OA configuration where FIPS mode has been enabled.
          * When FIPS mode is enabled for a redundant OA configuration, the automatic synchronization of FIPS mode configuration from the active to the standby OA module will trigger a reset of the standby OA module to factory defaults.  This operation will be incorrectly recorded in the OA syslog as having been performed by the "Insight Display" user.
        * **GUI**
          * Script error displayed on flashing OA 
            * Issue 1: An alert titled "Warning: Unresponsive script" may occur if connectivity to the OA is lost. This can be safely ignored, and the user can sign in after the connection is restored.
            * Issue 2: An alert titled "Internet Explorer Script Error" may occur on a remote GUI session when flashing the OA. This may be safely ignored.
        * **Integrity Server Blades**
          * Under rare circumstances, an HP Integrity BL8x0c i2 or BL8x0c i4 Server Blade installed in a HP BLc7000 Enclosure configured with Virtual Connect may momentarily lose its network connection during an OA failover.  See Customer Advisory c03613140 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03613140>
        * **Interconnects**
          * In the HP BladeSystem c3000 Enclosure with at least one Cisco Catalyst Blade Switch 3020 for HP c-Class BladeSystem installed, OA enclosure thermal management may not provide sufficient cooling to allow some blade configurations to operate at optimal performance under heavy workloads. 
          * Some BladeSystem interconnect modules may fail to connect or may experience excessive errors in certain scenarios after an I/O module is inserted into an enclosure that is already operating with OA firmware 3.6x/3.7x. See Customer Advisory c03811228 for more information: <http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03811228>
        * **LDAP**
          * Enhanced LDAP authorization to distinguish the same user name in different LDAP Groups.
        * **OA Upgrade**
          * The OA flash process completes successfully although 88% is the highest percentage reported.
        * **Power**
          * The OA would incorrectly display an 'AC Subsystem Overload' alert message due to a transient power condition related to the Dynamic Power Saving mode.
          * SHOW POWER CLI output does not immediately reflect power configuration changes made by SET POWER MODE
        * **SNMP**
          * The OA reboots with an out of memory condition due to many SNMP MIB Walk requests after being active for long periods of time.
          * SNMP not accessible from standby OA IP with OA 3.56 through OA 3.60.
        * **VLAN**
          * Slow OA and virtual media access with 3.60 and later when VLAN functionality is enabled.
          * OA firmware sync feature does not work when VLAN is enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed **
      
        * **General**
          * OA 4.02 includes fix for CVE 2014-0224. HPSBMU03058 rev.1 - HP BladeSystem c-Class Onboard Administrator (OA). 
          * In the HP BladeSystem c3000 Enclosure with at least one Cisco Catalyst Blade Switch 3020 for HP c-Class BladeSystem installed, OA enclosure thermal management may not provide sufficient cooling to allow some blade configurations to operate at optimal performance under heavy workloads.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.12
changelog:
  -     Users should update to OA 4.12 if their system is using OA 4.11.  
        
      **Optional** - Users should update to OA 4.12 if their system is using an OA version prior to OA 4.11 and is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.12
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware Additions**
          * HP LPe1605 16Gb FC HBA for BladeSystem c-Class.
          * HP Smart Array P230i Controller.
        * **Features Additions and Changes**
          * **Authentication**
            * Enhanced nested LDAP group support to include sub-tree search of the configured search contexts.
            * Enhanced nested LDAP group support to perform sub-tree search at specified search contexts.
          * **Enclosure iLO Federation**
            * In versions of OA firmware prior to OA 4.11, ILOs within an enclosure were not able to communicate in a peer-to-peer fashion.  If you wish to enable iLO Federation between blades in an individual enclosure, the Enable Enclosure iLO Federation Support configuration option in the OA must first be enabled. In addition to enabling this support for the enclosure, you must also enable the necessary support individually for any desired blades through the iLO user interfaces.  The Enable Enclosure iLO Federation Support configuration option is enabled by default. Please ensure that this setting is disabled if there are any concerns with enabling peer-to-peer communication between iLOs within the enclosure.  The configuration option can be displayed or modified via the Enclosure Information->Enclosure Settings->Network Access page in the OA GUI web console, or it can be displayed via the OA CLI interface using SHOW NETWORK command and modified using the ENABLE/DISABLE ENCLOSURE_ILO_FEDERATION_SUPPORT CLI commands.
          * **FIPS**
            * Cryptographic Known Answer Tests (KATs) now run on each OA reboot and/or power cycle irrespective of the FIPS mode setting.
          * **HP Insight Remote Support**
            * Added support for the Insight Remote Support Direct Connect configuration.
            * Added CLI and GUI interfaces for importing a self-signed certificate from an Insight RS Hosting Device into the OA. This certificate is used to validate the signing authority of the Insight RS Hosting Device, which is required to allow communication with the Hosting Device when the OA is in FIPS mode.
          * **IPv6**
            * The OA supports DDNS for IPv6 addresses.
            * Added support for displaying IPv6 addresses for the associated enclosure devices for the SHOW INTERCONNECT, SHOW TOPOLOGY and SHOW SERVER commands.
          * **Security**
            * Added support for TLS 1.1 and TLS 1.2 as a secure communication protocol.
            * Enabled "diffie-hellman-group1-sha1" as a supported SSH key exchange option by default. Support for "diffie-hellman-group1-sha1" as a supported SSH key exchange option was disabled in OA 4.01 by default. This can be disabled via the "SET SECURESH SERVER KEX DHG1" CLI command if required. Note that updating to OA 4.11 will not change the current setting but resetting the OA factory default settings will result in"diffie-hellman-group1-sha1" key exchange being enabled. Any saved OA configuration scripts should be updated appropriately.
        * **Browser Support**
          * Updated web browser support as follows: 
            * Microsoft Internet Explorer 8, 9, 10, and 11.
            * Mozilla Firefox ESR 17 and ESR 24.
            * Google Chrome.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.12
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
        * **General**
          * ****Disabled support for OpenSSL TLS heartbeat extension. CVE-2014-0160 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160>, HPSBMU02994 - [HP BladeSystem c-Class Onboard Administrator (OA) running OpenSSL, Remote Disclosure of Information](http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/action.process/public/kb/docDisplay/?javax.portlet.action=true&spf_p.tpst=kbDocDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_kbDocDisplay=wsrp-interactionState%3DdocId%253DZW1yX25hLWMwNDIzNjA2Mg%2525253D%2525253DhPsCeNc%257CdocLocale%253Den_US%257CcalledBy%253DSearch_Result&javax.portlet.endCacheTok=com.vignette.cachetoken) \- Document ID: c04236062  (Currently Rev 1)
          * The OA CLI command RESET ILO fails to successfully reset the specified iLO with a response indicating "No iLO link detected" when executed on HP ProLiant BL2x220c G5, G6, and G7 Server Blades in bays 1-8.
          * Reset to factory defaults fails for redundant OA modules. See the Customer Advisory [c04116279 ](http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04116279)for more information.
          * OA displays FCoE functionality associated with incorrect physical function (PF) for HP FlexFabric 10Gb 2-port 526FLB Adapter.
          * On initial insertion into the enclosure, the asset tag data for a server blade may not be populated or may be displayed as "[Unknown]" in the "Server Device Bay Information" tab of the web GUI or after executing the "SHOW SERVER INFO" command from the CLI.
          * After making network configuration-related changes to the OA, the following message may be logged to the configured remote syslog server from the standby, "OA: Remote Syslog: Unable to open enclosure configuration file. Exiting".
          * OA v4.01 may hang when booting if the Alertmail Sender Name string includes space characters and is either 39 or 40 characters long.
          * OA 'Link loss failover' does not function properly after performing OA FW SYNC.
        * **EFM**
          * Inability to power on all blades within an enclosure due to insufficient enclosure power after running EFM update process on blades with the "Forced Power Off" EFM configuration option enabled.
        * **GUI**
          * The GUI cannot complete the loading process on linked enclosures for USER or OPERATOR accounts without OA bay access enabled. This behavior was only exhibited in OA 4.01 firmware.
        * **Integrity Blade Servers**
          * The OA fails to update the IP address of a HP Integrity BL860c or BL870c Server Blade after enabling an EBIPA address for the blade. OA commands such as CONNECT SERVER will fail until either the OA is restarted or the blade's iLO is reset.
        * **IPv6**
          * The CONNECT SERVER CLI command fails in IPv6-only network environment.
          * The HTTP service for IPv6 may become unresponsive configuring the OA with an IPv6 address and enabling IPv6 support through the GUI or CLI within a very short time. See the Customer Advisory [c04012934 ](http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c04012934-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken)for more information.
        * **OA Redundancy**
          * When an OA forced failover is initiated from either the CLI or the GUI and the management network is under an extreme load, a kernel panic and reboot of the new standby module may be observed.
        * **Power**
          * Spurious enclosure power supply insertion and subsequent removal events logged for unpopulated power supply bays in a c3000 Enclosure.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.13
changelog:
  -     *Recommended** \- Users should update to OA 4.13 if their system is using OA 4.12.  
        
      **Optional** - Users should update to OA 4.13 if their system is using an OA version prior to OA 4.12 and is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.13
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed  
        
      **Onboard Administrator firmware version 4.13 resolved the following issue:****
      
        * **General**
          * OA 4.10 is no longer available on the web and has been replaced with OA 4.13.  OA 4.13 includes fix for CVE 2014-0224 and also includes fix provided in OA 4.12 for CVE 2014-0160. HPSBMU03058 rev.1 - HP BladeSystem c-Class Onboard Administrator (OA).  
      
      ****The following issues were resolved in Onboard Administrator firmware version 4.12 and are included in version 4.13:  ** **
      
        * **General**
          * ****Disabled support for OpenSSL TLS heartbeat extension. CVE-2014-0160 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160>, HPSBMU02994 - [HP BladeSystem c-Class Onboard Administrator (OA) running OpenSSL, Remote Disclosure of Information](http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/action.process/public/kb/docDisplay/?javax.portlet.action=true&spf_p.tpst=kbDocDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_kbDocDisplay=wsrp-interactionState%3DdocId%253DZW1yX25hLWMwNDIzNjA2Mg%2525253D%2525253DhPsCeNc%257CdocLocale%253Den_US%257CcalledBy%253DSearch_Result&javax.portlet.endCacheTok=com.vignette.cachetoken) \- Document ID: c04236062  (Currently Rev 1)
          * The OA CLI command RESET ILO fails to successfully reset the specified iLO with a response indicating "No iLO link detected" when executed on HP ProLiant BL2x220c G5, G6, and G7 Server Blades in bays 1-8.
          * Reset to factory defaults fails for redundant OA modules. See the Customer Advisory [c04116279 ](http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04116279)for more information.
          * OA displays FCoE functionality associated with incorrect physical function (PF) for HP FlexFabric 10Gb 2-port 526FLB Adapter.
          * On initial insertion into the enclosure, the asset tag data for a server blade may not be populated or may be displayed as "[Unknown]" in the "Server Device Bay Information" tab of the web GUI or after executing the "SHOW SERVER INFO" command from the CLI.
          * After making network configuration-related changes to the OA, the following message may be logged to the configured remote syslog server from the standby, "OA: Remote Syslog: Unable to open enclosure configuration file. Exiting".
          * OA v4.01 may hang when booting if the Alertmail Sender Name string includes space characters and is either 39 or 40 characters long.
          * OA 'Link loss failover' does not function properly after performing OA FW SYNC.
          * Installing HP SSO certificates from multiple OA clients simultaneously may result in the corruption of one or more of the SSO certificates. 
        * **EFM**
          * Inability to power on all blades within an enclosure due to insufficient enclosure power after running EFM update process on blades with the "Forced Power Off" EFM configuration option enabled.
        * **GUI**
          * The GUI cannot complete the loading process on linked enclosures for USER or OPERATOR accounts without OA bay access enabled. This behavior was only exhibited in OA 4.01 firmware.
        * **Integrity Blade Servers**
          * The OA fails to update the IP address of a HP Integrity BL860c or BL870c Server Blade after enabling an EBIPA address for the blade. OA commands such as CONNECT SERVER will fail until either the OA is restarted or the blade's iLO is reset.
        * **IPv6**
          * The CONNECT SERVER CLI command fails in IPv6-only network environment.
          * The HTTP service for IPv6 may become unresponsive configuring the OA with an IPv6 address and enabling IPv6 support through the GUI or CLI within a very short time. See the Customer Advisory [c04012934 ](http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c04012934-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken)for more information.
        * **OA Redundancy**
          * When an OA forced failover is initiated from either the CLI or the GUI and the management network is under an extreme load, a kernel panic and reboot of the new standby module may be observed.
        * **Power**
          * Spurious enclosure power supply insertion and subsequent removal events logged for unpopulated power supply bays in a c3000 Enclosure.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.21
changelog:
  -     *Recommended** \- Users should update to OA 4.21 if their system is using OA 4.20. Users should updated to either OA 4.12 or OA 4.21 if their system is using OA 4.11.  
        
      **Optional** - Users should update to OA 4.21 if their system is using an OA version prior to OA 4.11 and is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.21
changelog:
  -     *Enhancements/New Features:**
      
        * **Features Additions and Changes**
          * **General**
            * **Disabled support for OpenSSL TLS heartbeat extension. ****CVE-2014-0160 ****<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160>****, HPSBMU02994 - ****[HP BladeSystem c-Class Onboard Administrator (OA) running OpenSSL, Remote Disclosure of Information**](http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/action.process/public/kb/docDisplay/?javax.portlet.action=true&spf_p.tpst=kbDocDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_kbDocDisplay=wsrp-interactionState%3DdocId%253DZW1yX25hLWMwNDIzNjA2Mg%2525253D%2525253DhPsCeNc%257CdocLocale%253Den_US%257CcalledBy%253DSearch_Result&javax.portlet.endCacheTok=com.vignette.cachetoken)** \- Document ID: c04236062  (Currently Rev 1)**
            * Added Fully Qualified Domain Name (FQDN) link support for accessing iLOs and Interconnects. 
          * **IPv6**
            * The OA fully supports operation in a mixed IPv4/IPv6 or IPv6-only management network including management of IPv6-capable enclosure infrastructure devices such as iLO and interconnect modules. To use IPv6 networking, you should review the  OA IPv6 settings and customize them as necessary for your specific IPv6 environment. Note that if routing between IPv6 management networks is required, the routing configuration of the OA and enclosure infrastructure devices may be performed either via external IPv6 router advertisements or, starting with OA 4.20, via static configuration of an IPv6 gateway. After completing the necessary IPv6 configuration of the OA, you may then access any IPv6-capable enclosure infrastructure devices via its supported user interfaces and perform management actions from the OA.
            * Modified factory default state of IPv6 enclosure level settings (IPv6, DHCPv6, and SLAAC) from "disabled" to "enabled" by default to better support default connectivity to the OA in IPv6-only management network environments. Note that updating to OA 4.20 will not change the configuration of these settings but any subsequent reset to factory defaults will result in these settings being enabled. Any previously saved OA configuration scripts should be updated appropriately.
            * Added support for configuration of a static IPv6 gateway as an addition to the previously existing static IPv6 network settings for the OA module.
            * Added support for configuration of an IPv6 gateway for blade server iLOs and interconnect modules via the Enclosure Bay IP Addressing for IPv6 feature.
          * **Interconnects**
            * Added two new CLI commands to support the "BLc SX1018HP" switch only: 
              * SET INTERCONNECT ADMIN_PASSWORD FACTORY [ <bay number> ] - resets the Interconnect management password back to the factory setting.
              * SET INTERCONNECT FACTORY [ <bay number> ] - performs a factory reset on the Interconnect.
          * **SNMP**
            * In some instances, SNMP changes successfully configured from the OA user interface can fail to be processed properly most notably resulting in the OA failing to send SNMP traps to configured SNMP alert destinations.  
      
      
        * **Browser Support **
          * Microsoft Internet Explorer 8, 9, 10, and 11.
          * Mozilla Firefox ESR 17 and ESR 24.
          * Google Chrome.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.21
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.22
changelog:
  -     *Recommended** \- Users should update to OA 4.22 if their system is using OA 4.20 or 4.21.  
      **Optional** - Users should update to OA 4.22 if their system is using an OA version prior to OA 4.12 and is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.22
changelog:
  -     Patched the support for SSL/TLS MITM Vulnerability CVE-2014-0224
      <http://www.openssl.org/news/secadv_20140605.txt>


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.23
changelog:
  -     Addressed an issue where OA-iLO communication breaks when OA 4.22 is used with
      ILO-2 2.27, ILO-3 1.82 and ILO-4 2.10. The versions of iLO listed were updated
      to address a security vulnerability CVE-2014-3566


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.30
changelog:
  -     *Enhancements/New Features:**
      
        * **Hardware Additions**
          * HP ProLiant BL460c Gen9 Server
          * Smart Array 12Gb SAS Controller
          * HP FlexFabric 20Gb 2-port 650FLB Adapter
          * HP FlexFabric 20Gb 2-port 650M Adapter
          * HP FlexFabric 10Gb 2-port 536FLB Adapter
          * HP Adapters QDR/EN 10Gb & FDR/EN 40Gb 544+M
          * HP 2650W High Voltage Power Supply
          * HP High Voltage Power Module
        * **Features Additions and Changes**
          * **General**
            * Support for configuration of boot order settings for UEFI-capable blades operating in UEFI boot mode.
            * Enhanced the existing RESET ILO OA CLI command to remotely perform a hardware-based reset of iLO.  This hardware-based reset is only supported on Gen9 server blades and is equivalent to the iLO reset that can be manually performed using the UID button on a Gen9 server blade.  Note that this iLO reset can be performed without impact to the operating state of the associated server.
          * **Enclosure Firmware Management (EFM)**
            * Support for clearing all existing EFM log data stored in the OA, including both the OA EFM log and the server-specific Firmware and Session logs.
          * **Security**
            * Support for customizing secure connection protocols and ciphers to be used by the OA when it is operating with FIPS Mode enabled. This configuration is only accessible and used by the OA when the OA is configured in either FIPS Mode ON or FIPS Mode DEBUG.
            * Support for configuration of the client request timeout settings on the OA web server. These settings are configurable using the new OA CLI SET HTTP REQUESTREADTIMEOUT command. 
          * **IPv6**
            * Support for a new **Enable Router Advertisements** enclosure-level IPv6 setting. Router Advertisements from the external management network are allowed onto the internal enclosure management network when this setting is enabled and blocked when it is disabled. 
            * Support for manual configuration of up to three static IPv6 network routes associated with the OA network interface.
            * Support on the Standby OA GUI **TCP/IP Settings>IPv6Settings** tab for configuring and reporting certain IPv6 settings.
          * **DNS **
            * Improved DNS server redundancy reporting on the Active OA and Standby OA GUI** TCP/IP Settings** screens  and via the CLI SHOW OA NETWORK and SHOW NETWORK commands.  Depending on how many DNS servers are configured, the Onboard Administrator can employ up to six DNS servers for lookups: two IPv4 DNS servers (either static or DHCP assigned, but not both) and four IPv6 DNS servers (static or DHCP assigned, or both). For more information, see the OA user guides.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.30
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **Problems Fixed**
      
      **General**
      
        * In rare cases, the OA may fail to successfully identify server blades that have been either physically inserted into the enclosure or have been reset by executing the OA CLI RESET SERVER command.  When this issue occurs, the affected server blades are misidentified as an unsupported blade type.
        * Restoring or configuring OA settings from a saved configuration script may fail to apply all network settings on the Standby OA module. The failing configuration script commands return the following error: "An error occurred while communicating with the other Onboard Administrator." 
        * The RSA key for SSH is not properly exchanged with the Standby OA during an OA failover event when Enclosure IP Mode is enabled. After an OA failover event, when logging into the OA, SSH clients using the Enclosure IP address to access the Active OA may display an RSA key fingerprint warning message or "man-in-the-middle" security breach warning message.  This issue only occurs on OA 4.1x or OA 4.2x versions of OA firmware when the OA has been factory reset or new SSH keys were manually generated.  
        * The OA periodically reboots with the following entry logged in the OA system log:"OA: DHCP Monitor: DHCPD or RADVD is not running. Restarting OA." 
        * In an IPv6-only management network environment with the VLAN feature enabled, the CONNECT SERVER OA CLI command fails to connect to the server blade serial console with an error displayed similar to the following: Connecting to bay 1 ... iLO failed to respond: Interrupted system call (4)
      **Browsers**
      
        * After logging in to the OA GUI via the Google Chrome browser (Chrome-v34.0.1847.116 m or greater), the OA web application fails to load properly. The OA GUI login screen may display the warning: "Your browser does not have the required functionality to run the application." 
        * When using Microsoft Internet Explorer 11, the results of a configuration script fail to load properly after uploading and executing a configuration script using a local file from the OA web GUI. This issue was seen only when more than one script was uploaded without refreshing the page
      **EBIPA**  
      
        * Enclosure devices (including interconnect modules) fail to be configured with the Link Local address corresponding to the IPv6 gateway specified in the EBIPA for IPv6 configuration settings.  This issue only occurs when an IPv6 other than the Link Local address of the gateway is specified in the EBIPA for IPv6 configuration settings and will only occur for certain gateway server devices.
      **Serial Console**  
      
        * When logging in to connect to the OA via the serial port, if a user enters the **@** key as part of the login user name or password, the entered line is erased. 
        * When the baud rate for the OA serial port is configured to a value greater than the default 9600, attempts to directly paste saved commands or text into an open OA serial console session results in truncation or corruption of the pasted data. 
      **SNMP**  
      
        * No response received to a UDP network request sent from a client to an enclosure device such as iLO or an interconnect module. This issue was specifically observed when an SNMP request was sent to an interconnect module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.31
changelog:
  -     *Enhancements/New Features:**
      
        * **Version 4.31 New Feature:**
          * Added support for HP OneView management of enclosure configurations that do not include HP Virtual Connect interconnect modules.  
      
      
        * **Version 4.30 Features Additions and Changes: **
          * **New Hardware Support:**
            * HP ProLiant BL460c Gen9 Server
            * Smart Array 12Gb SAS Controller
            * HP FlexFabric 20Gb 2-port 650FLB Adapter
            * HP FlexFabric 20Gb 2-port 650M Adapter
            * HP FlexFabric 10Gb 2-port 536FLB Adapter
            * HP Adapters QDR/EN 10Gb & FDR/EN 40Gb 544+M
            * HP 2650W High Voltage Power Supply
            * HP High Voltage Power Module
          * **General:**
            * Support for configuration of boot order settings for UEFI-capable blades operating in UEFI boot mode.
            * Enhanced the existing RESET ILO OA CLI command to remotely perform a hardware-based reset of iLO.  This hardware-based reset is only supported on Gen9 server blades and is equivalent to the iLO reset that can be manually performed using the UID button on a Gen9 server blade.  Note that this iLO reset can be performed without impact to the operating state of the associated server.
          * **Enclosure Firmware Management (EFM)**
            * Support for clearing all existing EFM log data stored in the OA, including both the OA EFM log and the server-specific Firmware and Session logs.
          * **Security**
            * Support for customizing secure connection protocols and ciphers to be used by the OA when it is operating with FIPS Mode enabled. This configuration is only accessible and used by the OA when the OA is configured in either FIPS Mode ON or FIPS Mode DEBUG.
            * Support for configuration of the client request timeout settings on the OA web server. These settings are configurable using the new OA CLI SET HTTP REQUESTREADTIMEOUT command. 
          * **IPv6**
            * Support for a new **Enable Router Advertisements** enclosure-level IPv6 setting. Router Advertisements from the external management network are allowed onto the internal enclosure management network when this setting is enabled and blocked when it is disabled. 
            * Support for manual configuration of up to three static IPv6 network routes associated with the OA network interface.
            * Support on the Standby OA GUI **TCP/IP Settings>IPv6Settings** tab for configuring and reporting certain IPv6 settings.
          * **DNS **
            * Improved DNS server redundancy reporting on the Active OA and Standby OA GUI** TCP/IP Settings** screens  and via the CLI SHOW OA NETWORK and SHOW NETWORK commands.  Depending on how many DNS servers are configured, the Onboard Administrator can employ up to six DNS servers for lookups: two IPv4 DNS servers (either static or DHCP assigned, but not both) and four IPv6 DNS servers (static or DHCP assigned, or both). For more information, see the OA user guides.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.31
changelog:
  -     *Firmware Dependency**
      
      For firmware compatibility information please see HP Service Pack for ProLiant
      Information Library, <http://www.hp.com/go/spp/documentation>.
      
      **No new issues were resolved in Version 4.31.  
        
      Problems Fixed in Version 4.30:**
      
      **General**
      
        * In rare cases, the OA may fail to successfully identify server blades that have been either physically inserted into the enclosure or have been reset by executing the OA CLI RESET SERVER command.  When this issue occurs, the affected server blades are misidentified as an unsupported blade type.
        * Restoring or configuring OA settings from a saved configuration script may fail to apply all network settings on the Standby OA module. The failing configuration script commands return the following error: "An error occurred while communicating with the other Onboard Administrator." 
        * The RSA key for SSH is not properly exchanged with the Standby OA during an OA failover event when Enclosure IP Mode is enabled. After an OA failover event, when logging into the OA, SSH clients using the Enclosure IP address to access the Active OA may display an RSA key fingerprint warning message or "man-in-the-middle" security breach warning message.  This issue only occurs on OA 4.1x or OA 4.2x versions of OA firmware when the OA has been factory reset or new SSH keys were manually generated.  
        * The OA periodically reboots with the following entry logged in the OA system log:"OA: DHCP Monitor: DHCPD or RADVD is not running. Restarting OA." 
        * In an IPv6-only management network environment with the VLAN feature enabled, the CONNECT SERVER OA CLI command fails to connect to the server blade serial console with an error displayed similar to the following: Connecting to bay 1 ... iLO failed to respond: Interrupted system call (4)
      **Browsers**
      
        * After logging in to the OA GUI via the Google Chrome browser (Chrome-v34.0.1847.116 m or greater), the OA web application fails to load properly. The OA GUI login screen may display the warning: "Your browser does not have the required functionality to run the application." 
        * When using Microsoft Internet Explorer 11, the results of a configuration script fail to load properly after uploading and executing a configuration script using a local file from the OA web GUI. This issue was seen only when more than one script was uploaded without refreshing the page
      **EBIPA**  
      
        * Enclosure devices (including interconnect modules) fail to be configured with the Link Local address corresponding to the IPv6 gateway specified in the EBIPA for IPv6 configuration settings.  This issue only occurs when an IPv6 other than the Link Local address of the gateway is specified in the EBIPA for IPv6 configuration settings and will only occur for certain gateway server devices.
      **Serial Console**  
      
        * When logging in to connect to the OA via the serial port, if a user enters the **@** key as part of the login user name or password, the entered line is erased. 
        * When the baud rate for the OA serial port is configured to a value greater than the default 9600, attempts to directly paste saved commands or text into an open OA serial console session results in truncation or corruption of the pasted data. 
      **SNMP**  
      
        * No response received to a UDP network request sent from a client to an enclosure device such as iLO or an interconnect module. This issue was specifically observed when an SNMP request was sent to an interconnect module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.40
changelog:
  -     Update to this firmware version if any documented fixes or enhanced
      functionality provided by this version would be useful to your system.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.40
changelog:
  -      **General**
        *     * Cipher suites are now configured and displayed using their RFC 5246 standardized names. 
        * **EFM**
          * The maximum valid length of the Firmware Management ISO URL has been increased to 511 characters. o   **FIPS** This version of the OA addresses FIPS 140-2 certification requirements and is in the In Process list located at <http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf>. Added support for FIPS 186-4 approved RSA key generation used in SSL/SSH keys and certificates    Added support for the cipher TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Upgrading to this version of OA will replace old DSA keys with 2048-bit RSA keys to meet FIPS 140-2 requirements 
          * Replaced the MD5 password hashing algorithm with the stronger SHA256 algorithm when the Onboard Administrator is operating in FIPS Mode ON or DEBUG.  As a result of this change, OA 4.40 supports a maximum of 21 local users in FIPS Mode ON or DEBUG.  
          * Prevention of 1024-bit SSH/SSL key generation.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.40
changelog:
  -     *General**
      
        * Devices with MAC addresses ending with "81:00" (such as f8:66:f2:6d:81:00) were unable to communicate with the OA. Some examples of the observed symptoms were:
      Attempts to ping the OA from the device fail The OA cannot use such a device
      as a gateway The OA GUI and CLI cannot be used from this device
      
        * The OA HTTP service would become unresponsive and communication to the OA would be lost after removing a local user account that had OA administrator level privileges.This problem only occurred when the removed user account had previously been used to configure network services on the OA module.    o   When running OA firmware 4.0x, 4.1x, or 4.2x, the OA could erroneously report fans and/or power supplies as missing or failed even though they were not physically removed or failed.  When this issue occurred, after a few seconds the affected fans and/or power supplies would reappear as normal. There are no known functional impacts associated with this issue other than associated brief status reporting anamolies.  o   When the CLI CONNECT SERVER command is issued to connect to the server as an LDAP user, the text console session opens successfully but the "wget: not an http,https or ftp url: http:/<IP Address> /xmldata?item=cpqkey" message is displayed.  o   In rare cases, the following message was logged in the Standby OA syslog during a redundancy role transition initiated by the CLI FORCE TAKEOVER command: "CERTS: Failed to open flash"
      This had no functional impact; the entry could be ignored.  
      **Documentation**
      
        * In the September 2014 (Edition 23) HP BladeSystem Onboard Administrator CLI User Guide for OA 4.30, within the description of the SET HTTP REQUESTREADTIMEOUT command, a command showing recommended values had the BODY MINRATE value as 50 instead of the correct value 500. The command with the correct recommended values is as follows: SET HTTP REQUESTREADTIMEOUT HEADER 3-8 MINRATE 500 BODY 5-10 MINRATE 500
      This error was corrected in the October 2014 (Edition 24) document.  
        **EFM**
      
        * In rare cases, the Active OA module would reboot expectedly during the update of the OA firmware on redundant OA modules.  When this issue occurred, the Active OA module would reboot during the transfer of the OA firmware image to the Standby OA module.  The OA firmware update would fail to complete successfully; a segmentation fault (SEGV) error would be logged in the Active OA system log.  This issue did not cause any firmware or data corruption, and the OA firmware update could be successful if retried following the occurrence of this issue. Note that this issue could only be encountered when updating OA modules running OA 4.30 firmware.  o   Attempts to update the firmware failed on an HP ProLiant Gen9 server blade configured in UEFI Boot Mode or UEFI Optimized Boot Mode. When this failure occurred, the firmware log for the blade server would indicate an error similar to the following for each update attempt, including the two automatic retries that occur on failure: Jul 15 09:34:19 Unable to detect ISOLINUX booting. A final status report similar to the following would also be issued:
      Jul 15 10:30:33 Firmware Management is incomplete on blade <bay number>.
      
        * When using an HP Firmware Management ISO image based on a URL that includes the HTTP port (for example, <http://10.226.36.35:8080/bp-151ilo-2014-08-26-1.iso>),  EFM failed to mount the image. The following error message would be displayed: Unable to mount ISO or validate version information. The URL or ISO is invalid.   CLI commands affected include those that depend on the URL specification via the SET FIRMWARE MANAGEMENT URL command (such as the UPDATE FIRMWARE SERVER command and the UPDATE IMAGE FW_ISO command).** ** o   The EFM firmware log would indicate "Firmware Management successfully completed on blade x" even if the iLO firmware update failed to complete successfully. 
       **IPv6**
      
        * Configuration scripts could not be applied to another OA properly when attempting to configure new EBIPA DNS IPv4/IPv6 addresses or IPv6 routes. Attempts to change the configurations could only add new addresses to those of the previous configuration. It was not possible to replace the existing addresses with the new ones. The following CLI commands now include the ALL keyword to allow clearing of all unwanted addresses or routes:
        * REMOVE EBIPA SERVER DNS ALL
        * REMOVE EBIPAV6 SERVER DNS ALL
        * REMOVE OA ROUTE IPV6 <ACTIVE|STANDBY> ALL
      A configuration script can now use these commands to clear the previous
      (unwanted) EBIPA DNS IP addresses and IPv6 static routes, and then add the new
      ones.  
        **KVM**
      
        * Pressing **Enter** four times consecutively on a keyboard attached to the c7000 Enclosure integrated KVM module would cause the highlighted blade server on the KVM screen to power off or on, depending on its current power state. This issue has been fixed by interchanging the **Ok**/**Confirm** and **Cancel** buttons on the **Confirm: Change Server Power** and **Change Server Power** screens so that the **Cancel** button is highlighted by default instead of the **OK** or **Confirm** button. The default focus is set on the **Cancel** button.
        **Security**
      
        * The following security vulnerabilities were fixed:   
        * CVE-2014-3511: A vulnerability could be exploited by launching man-in-the-middle attacks to force the use of TSL 1.0 instead of the intended later version of TLS. This is documented in HP Security Bulletin HPSBMU03104 ([https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04427546).](https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04427546\).# \(QXCR1001370888\))
        * CVE-2007-2242: A vulnerability could be exploited by launching denial-of-service attacks via crafted IPv6 type 0 router headers between two routers, resulting in network congestion. This is documented in HP Security Bulletin HPSBMU03104 (<https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04427546>).
        * CVE-2014-3567: A vulnerability can be exploited to cause a DOS denial-of-service (memory consumption) attack via crafted session tickets that triggers an integrity check-failure.
        * CVE-2014-3513: A vulnerability can be exploited to cause a denial of service (memory consumption) via a crafted handshake message.
        * CVE-2014-3513: SRTP Memory Leak - a memory leak in d1_srtp.c in the DTLS SRTP extension in OpenSSL 1.0.1 (before 1.0.1j) allows remote attackers to cause denial of service (memory consumption) via a crafted handshake message.
        * This release of the OA resolves this security vulnerability by compiling OpenSSl with OPENSSL_NO_SRTP (the OA does not use DTLS and SRTP). 
        * CVE-2014-0139: A vulnerability affecting SSL/TLS transactions that might allow a man-in-the-middle attacker to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certificate Authority.
        * [CVE-2014-0015](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0015): A vulnerability when more than one authentication method is enabled and NTLM connections are reused, which might allow context-dependent attackers to authenticate as other users via a request.
        * CVE-2014-0138: A vulnerability affecting certain LDAP connections that might allow context-dependent attackers to connect as other users via a request (similar to issue CVE-2014-0015).
        * [CVE-2014-2522](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-2522): A vulnerability when running on Windows and using an SChannel/Winssl TLS backend. When accessing a URL that uses a numerical IP address, curl does not verify that the server host name matches a domain name in the subject's CN or subjectAltName field of the X.509 certificate. This allows man-in-the-middle attackers to spoof servers via an arbitrary valid certificate. 
        * In addition, OpenSSL has been updated to version 1.0.1h to address multiple CVE fixes.
        
       **SSH/SSL keys**
      
        * With OA firmware later than 4.0x, attempts to add an SSH key using the OA CLI ADD SSH KEY command might fail. Intermittently, after issuing the command, the user received an error message ("The submitted file is not a valid SSH key."), in which case the command failed. 
        
      **SNMP** 
      
        * SNMP alerts (or traps) sent from the OA to an IPv6 SNMP alert destination are sent incorrectly to destination port 161 instead of port 162 (per RFC 1157) when no destination port is explicitly specified as part of an IPv6 SNMP alert destination configuration. 
          *  The OA HTTP service would become unresponsive and communication to the OA would be lost after removing a local user account with OA administrator level privileges.  This issue in only occurred when the removed user account had previously been used to configure network services on the OA module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.50
changelog:
  -     Onboard Administrator 4.50 provides support for the following enhancements:
      
        * **Hardware Additions**
          * Added support for HP 2650W PSU -US PLATINUM DC c7000 power supplies.
      
       Features Additions and Changes
      
        * **General**
          * Introduced a standardized code signing and validation mechanism to enhance the firmware image authenticity.
          * Enhanced the OA CLI SET FACTORY command to set the Administrator password to the factory default "toe tag" password. This helps customers reset the module to the factory defaults including the password.
      
       New CLI command: SET FACTORY [RESTORE_FACTORY_PASSWORD]
      
        * Enhanced the OA firmware to notify users when the network connectivity of the Standby OA is lost. This helps users restore the Standby OA's connectivity to maintain redundancy.
        * Added an option to allow selection of UEFI Target as a One Time Boot option for UEFI enabled blade servers. Now USB, UEFI_SHELL and UEFI_TARGET options have been added as One Time Boot options. The option has been added in both GUI and CLI.
        * The OA bay number is now indicated in the Enclosure TCP/IP Settings page so users can know which bay currently hosts the Active and Standby OA module. The bay number labels would be shifted based on the Active-Standby role transition
        * Added diagnostics for Enclosure management network flooding situations. Now, in the enclosure management network flooding situations, OA will report the top 5 IP addresses in the network that are contributing to the network flood. This will help the customers to identify the source of the flood and take appropriate action.
        * **Remote Support**
          * As an enhancement, SNMP traps for Insight Remote Support service event transmission failures have been added to enable users to monitor this specific trap to identify any service event transmission failures.
          * Added Insight Remote Support service event for indicating low OA RTC battery condition.The service event will give information on the OA module in which the battery is low or failed and the spare part for the replacement battery.
        * **EFM**
          * Added a feature to prevent the flashing of OA firmware while the EFM process is in progress, thereby preventing the devices from getting into an indeterminate state.
          * Enhancements in the EFM feature have been made to handle issues seen in servers that take a longer duration to boot up.
          * Added a syslog notification when the EFM ISO is changed as to indicate the change to users.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.50
changelog:
  -      **General**
        * Fixed an issue which was seen when connecting to the OA from HP SIM using a LDAP account with the user name containing an exclamation character (!) for the SSO.
        * Fixed an issue where LDAP search contexts are showing empty after firmware is upgraded in FIPS Mode.
        * Fixed an issue where a customer logging in to OA using AD/LDAP credentials as a member of both Domain Administrators and Domain Users groups, and where one enclosure is given Domain Administrators access to the full administrative rights of the enclosure, and the other is given Domain Users limited access
        * Corrected a display issue where iLO logs listed in OA shows the order of events sorted incorrectly when the events are more than a year old. The events are displayed sorted on the month and hence events that occurred in the same month in two different years are incorrectly displayed together. The sorting now considers the year also.
        * Fixed an issue where the Device Bay Information page does not show the Management Processor/iLO NIC details under the Server NIC Information table, when the server is powered down.
        * Fixed an issue where OA reports incorrect values for Caution and Critical temperature limits when a blade is in Telco Mode.
        * Addressed an issue where Connect Server Serial command used to fail when server
        * **FIPS**
          * Fixed an issue which prevented transition to FIPS mode OFF when the enclosure is in FIPS-Degraded state. The same failure was seen when the transition was performed on a linked enclosure which was in FIPS-Degraded state. The issue has been addressed and the FIPS mode transition is allowed.
        * **EFM**
          * Addressed issues that would result in EFM failure with the following error messages: 
            * Failed to boot ISO
            * Unable to Monitor HPSUM
        * **Security**
      
             The following security vulnerabilities were fixed:
      
        * CVE-2015-0204 - A remote server can supply a weak RSA temporary key for a non-export RSA key exchange cipher suite to downgrade the session security.
        * CVE-2015-0286 - A vulnerability in ASN1_TYPE_cmp function can be exploited to launch a DoS (Denial of Service) attack by causing a crash during certificate validation operation.
        * CVE-2015-3144 - A vulnerability can be exploited to allow remote attackers to cause a denial of service (out-of-bounds read or write and crash) or possibly have other unspecified impact.
        * CVE-2015-3153 - The default CURL configuration sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
        * CVE-2015-2922 - A vulnerability in the Linux kernel can be exploited by sending a crafted Router Advertisement message and setting a low IPV6 hop limit and in turn cause DoS (Denial of Service).
        * CVE-2015-1789 - A vulnerability in some OpenSSL versions allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted length field in ASN1_TIME data.
        * CVE-2015-1791 - A vulnerability in some OpenSSL versions allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspecified other impact by providing a NewSessionTicket during an attempt to reuse a ticket that had been obtained earlier.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.60
changelog:
  -     Onboard Administrator 4.60 provides support for the following enhancements:
      
        * **Hardware Additions**
          * None.
        *  **Features Additions and Changes**
          * **General**
            * GUI, CLI, Smart components, help files, URLs, Product Names rebranded to align with HPE branding guidelines.
            * Enhanced information reporting of Gen9 servers booted in UEFI mode.
            * Support the configuration of SNMP trap agent address when non-default VLAN is enabled on OA.
            * Enhanced syslog to show the flooding information when VLAN configured nodes flood the management network.
          * **Remote Support**
            * Modified to connect to the HPE remote support URL.
          * **EFM**
            * Enhanced error handling mechanism in EFM for servers in UEFI boot mode.
            * Enhanced EFM to display detailed name for smart array controllers .
            * EFM enhanced to identify more devices in the EFM report.
            * Enhanced the status reporting of EFM operations to align with HPSUM return codes


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.60
changelog:
  -     *General**
      
        * Addressed an issue where EFM was reporting success while firmware update of iLO 4 failed.
        * Fixed an issue where OA might lose its IP address after OA firmware upgrade when ENCLOSURE_IP_MODE was enabled .
        * Fixed an issue where all iLOs were reset after making EBIPA changes to an empty bay. Now only the specific iLOs are reset.
        * Resolved an issue where iLOs became inaccessible after OA failover occurs with iLOs configured in EBIPA for IPv6. This occurs when an external router in the management network is configured to send Router Advertisements.
        * Corrected the type mismatch of OID cpqRackCommonEnclosureManagerLocation which could cause failures in the SNMP clients. The definition is changed from STRING to INTEGER.
        * Resolved an issue where information on only the last server NIC port of a multiport adaptor was shown on GUI and CLI. Now details of all the server NIC ports are displayed.
        * Resolved an issue of time synchronization between active and standby OA when date and time settings were changed from "Manual" to "NTP".
        * Resolved EFM discovery/update failure when the server power policy in the EFM configuration is set to "must be off".
        * **Security**
      
      The following security vulnerabilities were fixed:
      
        * CVE-2016-2108 - Addressed a vulnerability in ASN.1 implementation in OpenSSL that can cause Denial Of Service via  any field in crafted serialized data
        * CVE-2015-8605 - UDP payload length not properly checked. Addressed a vulnerability where a badly formed packet with an invalid IPv4 UDP length field can cause a DHCP server, client, or relay program to terminate abnormally.
        * CVE-2012-3954 - Fixed a memory leak issue in DHCPv6 daemon that could result in out of memory condition in OA.
        * CVE-2016-0797 and CVE-2016-0799 - Addressed a vulnerability in OpenSSL that could enable security attacks by passing large amount of untrusted data to certain functions in OpenSSL.
        * CVE-2015-8605 - Addressed a vulnerability in IPv4 stack that can be exploited to cause a Denial Of Service via an invalid length field in a UDP IPv4 packet.
        * CVE-2015-3196 - Addressed a vulnerability in OpenSSL that results in Denial Of Service by remote servers via a crafted ServerKeyExchange message.
        * CVE-2015-3195 - Addressed a vulnerability in OpenSSL that can be exploited to obtain sensitive information from process memory by triggering a decoding failure in a PKCS#7 or CMS application.
        * CVE-2015-6564 - Addressed a vulnerability in OpenSSH that might allow local users to gain privileges by leveraging control of the sshd uid to send an unexpectedly early MONITOR_REQ_PAM_FREE_CTX request.
        * CVE-2015-6563 - Addressed a vulnerability in OpenSSH that allows local users to conduct impersonation attacks by leveraging any SSH login access in conjunction with control of the sshd uid.
        * CVE-2015-5621 - Addressed a vulnerability in Net-SNMP that causes a Denial Of Service and possibly allows execution of arbitrary code via a crafted packet.
        * CVE-2015-5364 and CVE-2015-5366 - Addressed a vulnerability in UDP stack that can be exploited in UDP flood scenario to cause Denial Of Service in the OA.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.70
changelog:
  -     Onboard Administrator 4.70 provides support for the following enhancements:
      
      **Hardware additions**
      
        * BL460c Gen 10.
        * HPE 10GbE Pass-Thru Module.
        * Qualified support for HPE Integrity BL8x0c i6 Server Blade.
      
      Features**: additions and changes**
      
      **General**
      
        * Added support for Gen 10 Server and iLO5 features.
        * Added support for the enhanced KVM functionality in iLO5
        * Added support for HTTP boot option in the server boot options
        * Add support for HPE 10GbE Pass-Thru interconnect module.
        * Added support for HPE Integrity BL8x0c i6 Server Blade.
        * GUI, CLI, Smart components, help files, URLs, and product names rebranded to align with HPE branding guidelines.
        * Added a new SNMP trap to indicate that the power redundancy is restored in the enclosure.
        * Enhanced "SHOW ENCLOSURE TEMP" command output, to display the temperature readings like Current, Caution and Critical temperature threshold values for interconnect modules.
        * Added a provision to make sysName field to be set to DNS host name for the traps sent from Onboard Administrator.
      
      ** Security **
      
        * Adding support for CNSA approved algorithms and a new security mode - TOP_SECRET.
        * Added the ability to Enable/Disable cipher/protocol in FIPS OFF mode.
        * Added support for secured communication between HPE Embedded Remote Support functionality and the HPE Support Datacenters with the use of SHA-2 certificates.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.70
changelog:
  -     *General**
      
        * Addressed an issue where OA "update iLO all" command fails in an enclosure with maximum Blades.
        * Addressed an issue where a Warning Alert  was wrongly sent when a fan is reseated in an enclosure
        * Addressed an issue where the port mapping information for 560M Izzy adapter Mezz controller was not displayed correctly.
        * Addressed an issue where Remote Syslog logging would fail when OA failover happened in an IPv6 only environment.
        * Enhanced OA to bring the server from a power throttled state back to normal power state upon an OA reboot to circumvent an unwarranted emergency brake.
        * Fixed an issue where the Active and Standby OAs can have the same IP address in some rare situations.
        * Resolved an issue where a Gen9 server's host name gets cleared when the blade is rebooted.
        * Addressed an issue where server blade Power ON will be delayed in enclosures with OA Firmware Version 4.60 and managed by HPE OneView, when the OA module is reset until OneView refreshes the servers.
      
      **Security**
      
      The following security vulnerabilities were fixed:
      
        * CVE-2016-5387- Addressed a vulnerability which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request.
        * CVE-2016-2183- Addressed a vulnerability against TLS ciphers with 64bit block size in which makes it easier for remote attackers to obtain cleartext data via an attack against a long-duration encrypted session
        * CVE-2016-6515 - Addressed a vulnerability in OpenSSH which did not limit password lengths for password authentication, which allows remote attackers to cause a denial of service via a long string.
        * CVE-2015-8215 - Addressed a vulnerability IPv6 stack which does not validate attempted changes to the MTU value, which allows context-dependent attackers to cause a denial of service.
        * Addressed issue where in Onboard Administrator was vulnerable to Buffer overflow.
        * Added the HSTS[HTTP strict transport security] support  in OA.
        * Addressed a memory corruption vulnerability in the post-authentication sshd process.
      
      **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.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.0.2
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      This is the initial version of the firmware.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.31
changelog:
  -      On rare occasions, incorrect data may be read or written while a controller is rebuilding a drive.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.31
changelog:
  -     *Enhancements/New Features:**
      
        * Firmware now reads the max link rate from the backplane NVRAM and sets the rate accordingly. The expander firmware will adjust the SAS links to the appropriate speed based on the backplane type. The firmware will not try to force slower backplanes to higher link rates.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.31
changelog:
  -     *Problems Fixed:**
      
        * Data Integrity issue while controller performed an array rebuild.
        * Disabled Edge-Buffering to address a rare data integrity issue seen with a drive that had bad blocks.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.80
changelog:
  -      A rare race condition in a system with SAS and SATA drives, where SATA drives were not discovered during server power-on.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.07
changelog:
  -      While performing a firmware upgrade on an HP 12Gb/s SAS Expander card, an issue infrequently occurred that caused the card to become unusable. HP 12Gb/s SAS Expander firmware version 2.07 resolved this issue.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.09
changelog:
  -      The HPE 12Gb/s SAS Expander firmware version 2.09 resolves an issue where an incorrect SAS address was returned by the Device Identification Inquiry for Vital Product Data page. As a result, applications using this information may report incorrect data about the storage system topology.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.10
changelog:
  -      Rebranded the controller information from HP 12G SAS Expander card to HPE 12G SAS Expander card.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.17
changelog:
  -      SATA hard disk drives connected to the HPE 12Gb/s SAS Expander card may not be detected when cold booting a HPE ProLiant server with a HPE Smart Array SR Gen10 controller


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02
changelog:
  -      Changed the Enclosure's Target and LUN address to the appropriate unique values. Previously these addresses would conflict with the SATA drive in bay #1 which interfered with software defined storage solutions such as Storage Spaces Direct.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.03
changelog:
  -      Please un-plug and re-plug the power cord to the server for firmware upgrade from version 1.03 or earlier to take effect.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.04
changelog:
  -      HP Apollo 45xx Gen9 Backplane Expander firmware version 1.04 provides enhanced functionality so that upgrades from version 1.04 to a later version no longer requires a power cycle/cold reboot of the server after the firmware is flashed.  
      NOTE: Upgrading from a firmware version older than version 1.04 to version
      1.04 or later still requires a power cycle/cold reboot to complete the upgrade
      process.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.73
changelog:
  -      When the server hardware inventory was displayed in the Device Manager, the NVMe drives were not included in the lists.
      
      Firmware version 1.73 allows all NVMe supported drives to be recognized and
      displayed in the server hardware inventory lists.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.73-2.1
changelog:
  -     *Problems Fixed in version 1.73 (B):**
      
        * The component installer did not detect the HPE Express Bay Enablement Switch Card, when it was configured in an HP ProLiant DL580 Gen9 Server, and would not proceed with firmware update.
      
      **Problems Fixed in version 1.73:**
      
        * When the server hardware inventory was displayed in the Device Manager, the NVMe drives were not included in the lists.
      
      Firmware version 1.73 allows all NVMe supported drives to be recognized and
      displayed in the server hardware inventory lists.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.73-3.1
changelog:
  -     *Problems Fixed in version 1.73 (C):**
      
        * During component installation on a system configured with NVIDIA Tesla M2090 GPU, an uncorrectable PCIe error might occur.
      
      **Problems Fixed in version 1.73 (B):**
      
        * The component installer did not detect the HPE Express Bay Enablement Switch Card, when it was configured in an HP ProLiant DL580 Gen9 Server, and would not proceed with firmware update.
      
      **Problems Fixed in version 1.73:**
      
        * When the server hardware inventory was displayed in the Device Manager, the NVMe drives were not included in the lists.
      
      Firmware version 1.73 allows all NVMe supported drives to be recognized and
      displayed in the server hardware inventory lists.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.73-4.1
changelog:
  -      Updated to support Service Pack for ProLiant version 2017.07.0
      
                **Note:** If any version 1.73 was previously installed, then it is not necessary to upgrade to version 1.73 (D).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.16
changelog:
  -     *Problems Fixed:**
      
        * Corrects PHY Link Error messages being posted in IML when attached to the following drives:
      
      **HP Model Number -**
      
      EF0300FATFD
      
      EF0450FATFE
      
      EF0600FATFF
      
      EG0300FBDBR
      
      EG0300FBVFL
      
      EG0450FBDBT
      
      EG0450FBVFM
      
      EG0600FBDBU
      
      EG0600FBVFP
      
      EG0900FBVFQ
      
      EG1200FCVBQ
      
      EG1200FDNJT
      
      EH0072FARWC
      
      EH0146FARWD
      
      EH0300JDYTH
      
      EH0450JDYTK
      
      EH0600JDYTL
      
      EH0600JDYTN
      
      EO0200JDVFA
      
      EO0400JDVFB
      
      EO0800JDVFC
      
      MB2000EBUCF
      
      MB2000ECWLP
      
      MB2000FBUCL
      
      MB2000FCZGH
      
      MB2000GBUPB
      
      MB2000GCWLT
      
      MB3000EBUCH
      
      MB3000ECWLQ
      
      MB3000FBUCN
      
      MB3000FCZGK
      
      MB3000GBUCK
      
      MB3000GCWLU
      
      MB4000ECWLR
      
      MB4000FCZGL
      
      MB4000GCWLV
      
      MB6000FEDAU
      
      MB6000GEBTP
      
      MB6000GEFFV
      
      MM1000FECVH
      
      MO0200JDVET
      
      MO0400JDVEU
      
      MO0800JDVEV


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.18
changelog:
  -     *Problems Fixed:**
      
        * Unable to change cache read/write ratio following a cold boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.34
changelog:
  -     *Problems Fixed:**
      
        * When a server was running and power was removed and then re-applied to an HP D3600/D3700, the controller would cease to function (POST Lockup 0xAB).
        * Following a reboot, SATA drives in Bay 1 and Bay 2 of an HP D3600/D3700 may fail to be discovered (leading to any configured LUN's using these bays to go into interim recovery mode).
        * When running HP SmartCache and doing repeated blackout/power loss write cache backups, the controller would cease to function (POST Lockup 0x13).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.34-2.1
changelog:
  -     *Problems Fixed:**
      
        * When a server was running and power was removed and then re-applied to an HP D6000, the controller may cease to function (POST Lockup 0xAB).
        * Following a reboot, SATA drives in Bay 1 and Bay 2 of an HP D6000 may fail to be discovered, leading to any configured LUN's using these bays to go into interim recovery mode.
        * If a power-outage or brownout occurs while running HP SmartCache, the controller may cease to function on the following boot (POST Lockup 0x13).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.14
changelog:
  -     *Enhancements/New Features:**
      
        * Servers now power up faster due to improvements in the UEFI controller driver.
        * Logical volume transformations are allowed on controllers without data preservation.
        * Drives can now be hot-added in a zoned configuration.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.14
changelog:
  -     *Problems Fixed:**
      
        * Critical issue for all UEFI systems using 2.2 TB or greater volumes configured with GPT partitions. For additional information please refer to the customer advisory # [c04602001](http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04602001)
        * When rebuilding a logical volume greater than 2TB in size, the controller might cease to function (POST Lockup 0xE0). Controller would report a POST Lockup 0xE0 error and cease to function, when the following conditions were met:
      
                       1) Encryption enabled and a re-key operation was in progress.  
                       2) While IO was in progress, physical drives failed in an Advanced Data Guarding (RAID6 or RAID60) volume, which caused the volume to go into a degraded state.  
                       3) Degraded Mode Performance Optimization was enabled via HP Smart Storage Administrator.
      
        * If a power outage or brownout occurred while running a volume expansion, the controller might cease to function on the following boot (POST Lockup 0x13).
        * HP D2600/D2700 Disk Enclosures might not show the correct box number on the LED display.
        * Controller might become unresponsive if a drive was re-inserted into encrypted LUN while performing IO on it.
        * When running IO with encryption turned on in remote mode and a local key cache enabled, changing the master key might result in encryption being disabled on the next power up.
        * Controller allowed encryption key changes even with locked volumes.
        * A key restore from an Enterprise Secure Key Manager could take a long time for large configurations.
        * Users were unable to install Red Hat Enterprise Linux 6 Update 5 to a logical volume on an HP P2000 MSA Array System if both an HP H241 and H240 Smart Host Bus Adapter were present in the system.
        * When HP D3700 Disk Enclosures were connected to an HP H240 Smart Host Bus Adapter, the maximum number of enclosures displayed in the boot menu was five, although a maximum of eight enclosures were supported.
        * When a volume expansion or encryption re-key operation was performed, and if multiple power losses or brownouts occurred, data might become inaccessible (POST Message 1769).
        * POST messages 1764, 1768, 1784, 1786, 1787, 1789, 1831 have been updated and/or corrected.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52
changelog:
  -      Improved performance by limiting Surface Scan frequency to once every 14 days
        * Increased performance for tape drives when using variable block sizes
        * Updated type and quantity of information logged to the Active Health System log
        * Added support for the following: 
          * Check for drive firmware update needed on hot-plugged devices
          * Non-disruptive online drive firmware updates for supported SATA drives
          * Microsoft Storage Spaces
          * HP MSA 1040 external RAID enclosure
          * Third party external RAID enclosures


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52
changelog:
  -      If an HP Smart Array controller is configured with HP SmartCache, upgrade the controller to firmware version 2.52 to avoid a possible lockup (POST lockup 0x13)
        * System fans might run at maximum speed
        * System might be unable to boot from volumes on HP MSA 2040 SAS enclosures
        * Physical drives might be repeated in the UEFI one-time boot menu
        * Installation of a custom Linux ISO might fail to boot with "error: can't allocate initrd"
        * Controller might stop responding at power up with encryption enabled (POST Lockup 0x13)
        * System might stop responding when sending high numbers of non-NCQ commands to SATA drives behind H-series cards (POST Lockup 0x13)
        * System might stop responding following the hot-removal of a drive from a fault tolerant volume (POST Lockup 0xAB)
        * System might be unable to downgrade controller firmware via UEFI flashing tool
        * If a Smart Array controller with firmware version 2.14 was running in HBA mode and the drives that were connected were previously configured in a LUN, an 1832 POST message was not displayed. Refer to Customer Advisory [c04635824](http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04635824) for additional information about this issue.
        * Certain POST messages displayed although the error conditions were not present. The Smart Array Controller firmware has been hardened to reduce the likelihood of these false error messages occurring: 
          * POST 1784, which indicated a logical drive failure
          * POST 1795, which indicated a write-back-cache error and disabled cache


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.00
changelog:
  -      Support booting from controllers in HBA-mode when running with legacy BIOS
      
        * Improved controller performance following a cold boot of the server


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.00
changelog:
  -      Controller might stop responding in the following situations:
      
          * During reboot or at power-up, if multiple Raw Device Mappings (RDM's) are configured under VMware
      
          * During reboot or at power-up, if multiple logical volumes are queued for rebuild, expansion, or transformation
      
          * When flashing SATA drive firmware on a system running a supported Windows OS, if a drive had previously been removed or failed (POST Lockup 0x13)
      
        * Drives reported as overheating when not above temperature limits


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.52
changelog:
  -      Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
        * Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
        * Detection of all direct-attached physical drives might fail if a single drive did not spin up
        * A physical drive configured as a spare drive might indicate predictive failure sooner than expected
        * Erroneous Critical message displayed in ADU: "Box Failure Due To Primary Io Module"


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 3.56
changelog:
  -      Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
        * Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
        * Detection of all direct-attached physical drives might fail if a single drive did not spin up
        * A physical drive configured as a spare drive might indicate predictive failure sooner than expected
        * Erroneous Critical message displayed in ADU: "Box Failure Due To Primary Io Module"
        * With SLES11 SP4 installed, the system may fail to boot to the OS after updating to 3.52 SmartArray controller firmware


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02
changelog:
  -      Improved controller performance.
      
        * Servers now power up faster due to improvements in the UEFI controller driver.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02
changelog:
  -      Flash-backed write cache might fail on embedded controllers following an unexpected power down event.
      
        * Detection of all physical drives behind the same expander might fail if a single drive did not spin up.
      
        * Server power up might take an extended amount of time if failed drives are present behind a controller running in HBA mode.
      
        * SATA drives might go offline during runtime.
      
        * Logical volumes might be disabled after flashing enclosure SEP device firmware.
      
        * Controller might stop responding when running IO with an attached Shared Storage enclosure (POST Lockup 0xAB).
      
        * Controller might stop responding when running Linux and an abort command is issued by the host.
      
        * An intermittent aborted IO request with attached SATA drives resulted in a LUN (Logical Unit Number) reset.
      
        * Incorrectly displayed drive failure message in HPESSA for rebuilding SSD.
      
        * Incorrectly displayed 0% progress message in HPESSA for sanitizing SSD.
      
        * Reduced likelihood of POST Lockup 0x13 occurrence due to intermittent memory errors.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02-2.1
changelog:
  -     *Problems Fixed in 4.02:**
      
        * Flash-backed write cache might fail on embedded controllers following an unexpected power down event.
        * Detection of all physical drives behind the same expander might fail if a single drive did not spin up.
      
        * Server power up might take an extended amount of time if failed drives are present behind a controller running in HBA mode.
      
        * SATA drives might go offline during runtime.
      
        * Logical volumes might be disabled after flashing enclosure SEP device firmware.
      
        * Controller might stop responding when running IO with an attached Shared Storage enclosure (POST Lockup 0xAB).
      
        * Controller might stop responding when running Linux and an abort command is issued by the host.
      
        * An intermittent aborted IO request with attached SATA drives resulted in a LUN (Logical Unit Number) reset.
      
        * Incorrectly displayed drive failure message in HPESSA for rebuilding SSD.
      
        * Incorrectly displayed 0% progress message in HPESSA for sanitizing SSD.
      
        * Reduced likelihood of POST Lockup 0x13 occurrence due to intermittent memory errors.
      
      **Problems Fixed in 4.02 (B):**
      
        * Component might fail to install firmware in a system configured with a shared storage enclosure. The following message would be reported - "Device appears more than once in tree."


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.02-3.1
changelog:
  -      The 4.02 (C) component will perform a deep power cycle after flashing the CPLD image to eliminate the need to manually remove power from the system for the new CPLD to take effect.
        * Improved controller performance.
      
        * Servers now power up faster due to improvements in the UEFI controller driver.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.08
changelog:
  -      P741m controller missing the embedded SmartCache license key.
      
        * System might stop responding in response to a rare error (POST Lockup 0x13).
      
        * Drives might not appear as HPE authentic drives when used in a zoning configuration.
      
        * Deferred drive firmware flashing might hang at POST with some models of drives.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.52
changelog:
  -      System fans might go to 100% if connected drives were spun down.
        * SATA SSD's were incorrectly marked as worn out.
        * Poor performance on the first logical volume with drive write cache enabled.
        * Controller might hang or show as failed in the IML with 20+ SATA SSD's configured in a RAID6 volume with Smart Path enabled and IO running.
        * System might hang at POST following a reboot.
        * System might lockup at POST following a reboot (POST Lockup 0x13)
        * Duplicate SCSI devices shown in Linux after issuing a bus rescan command.
        * Recovered paths were not restored when using a SmartArray P742m controller connected to an external drive enclosure and a shared storage external enclosure.
        * Smart Array P741m controller missing the embedded SmartCache license key.
        * System might stop responding in response to a rare error (POST Lockup 0x13).
        * Drives might not appear as HPE authentic drives when used in a zoning configuration.
        * Deferred drive firmware flashing might hang at POST with some models of drives.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.58
changelog:
  -      Fixes
      
      \- Kernel core dump using dump might not complete in Linux when using Smart
      Array Gen9 firmware version 4.52.
      
      \- Intermittent memory errors might cause the controller to stop responding.
      (POST Lockup 0x13)
      
      \- Physical slot location of SATA drives might not be returned correctly from
      an inquiry command.
      
      \- Drive LED's might be illuminated for the wrong drive and/or only illuminate
      momentarily.
      
      \- System fans might go to 100% if connected drives are spun down.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 4.60
changelog:
  -      P840/4GB controllers might fail data retention following an unexpected power event (POST message 1793 - Data in Write-Back Cache has been Lost)
        * Multiple direct attach SATA drives within a cluster might show the same WWN.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.04
changelog:
  -     HPE strongly recommends that this firmware update be performed in an offline
      environment.  If this firmware update is performed online, ensure a graceful
      shutdown or restart is performed in order to flush all data from the
      controller cache before the new firmware is activated.  Abruptly rebooting the
      system while there is data in cache might result in data loss.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.04
changelog:
  -      Added support to enable setting the controller boot order in Legacy BIOS Mode.
        * Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.04
changelog:
  -      Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
        * Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
        * System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
        * In rare cases, the controller might stop responding while running IO without displaying a lockup code.
        * Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
        * System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
        * Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
        * Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
        * Drive LED's might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
        * Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.04-1.1
changelog:
  -      Added support to enable setting the controller boot order in Legacy BIOS Mode.
        * Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.
        * Now installs on system running VMware vSphere 6.5 operation system.
      
                Note: if controller previously updated to firmware version 5.04, it is not necessary to upgrade to version 5.40(A).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.04-1.1
changelog:
  -      Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
        * Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
        * System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
        * In rare cases, the controller might stop responding while running IO without displaying a lockup code.
        * Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
        * System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
        * Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
        * Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
        * Drive LED's might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
        * Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
        * System fans might go to 100% if connected drives were spun down.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.52
changelog:
  -      Controller cache module might be marked as permanently disabled if the Smart Storage Battery is removed or failed while the system is online, even if SSA was previously used to enable write caching without a backup power source.
        * SATA drives might not be presented to the host in a Synergy system with a D3940 Disk Enclosure.
        * A hot-inserted replacement drive might show as a predictive failure if the original drive was identified as a predictive failure.
        * Port/box/bay identifier for physical drives might have an incorrect box number in zoned or multi-path configurations.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.02
changelog:
  -      Controller might hang at POST following an unexpected power event if there was data in the controller cache.
        * Controller might stop responding when running I/O to SATA drives. (POST Lockup 0x13)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.06
changelog:
  -      Under the following conditions, the controller might stop responding: 
          * During POST following an unexpected power event if there was data in the controller cache.
          * When running I/O to SATA drives. (POST Lockup 0x13)
          * When using a RAID configuration with strip size of 1024KiB. (POST Lockup 0x13)
          * When a WRITE SAME command is sent with a buffer size greater than 512 bytes. (POST Lockup 0x13)
        * In a multi-path environment with nested expanders, the active path to a device might be incorrect following a path failure or restoration.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.30
changelog:
  -     Fixes the following issues:
      
        * DDR cache could be randomly disabled after several boots
        * The controller could become unresponsive while in HBA mode during the creation of a partition/file system
      
      .


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.26
changelog:
  -      In rare circumstances after multiple, successive reboots, a system with 28 large form factor drives might become unresponsive. Firmware v1.26 resolves the issue.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.04-2.1
changelog:
  -      Customers who already have firmware version 1.04 installed do not need to update to 1.04 (B).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.04-2.1
changelog:
  -     *Version 1.04 (B)**
      
        * Added support for new models of HPE ProLiant servers: 
          * DL120 Gen10
      
      **Version 1.04**
      
        * Initial firmware release for HPE P/E-Class SR Gen10 controllers.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.34
changelog:
  -      Controller might stop responding while handling a drive error.  (POST Lockup 0x27006)
        * Controller might stop responding after a drive hot-removal or hot-insertion.  (POST Lockup codes 0x1EA or 0x15010)
        * Controller might stop responding during a volume expansion or rekey.  (POST Lockup code 0x1E30)
        * Controller might stop responding while performing heavy writes to a RAID 0 or RAID 1 logical drive that has a flash backed write cache enabled.  (POST Lockup 0x1BC0)
        * Various scenarios where drive LEDs might not be displayed correctly.
        * Drives might not be detected after a cold boot.
        * A hot-inserted drive might be immediately reported as failed.
        * A failed or charging HPE Smart Storage Battery might be reported as "missing" in SSA and iLO.
        * The RESTful management interface might be unable to detect physical drives or make configuration changes to the controller.
        * Option to enable "No Battery Write Cache" in SSA is not available if an HPE Smart Storage Battery is not installed.
        * Customer specified read/write controller cache ratio is not honored if "No Battery Write Cache" is enabled.
        * Controller cache might be displayed as temporarily disabled following an unexpected shutdown and subsequent reboot.
        * Unable to modify the controller cache read/write ratio following an unexpected shutdown and subsequent reboot.
        * The controller cache might become disabled when running VMware ESXi 6.0 if the controller and guest OS are configured to use PCI pass-through.
        * If multiple logical volumes are present on the same array, and one of the volumes is rebuilding, the others might be incorrectly marked as failed.
        * A drive at index 0 might incorrectly display as rebuilding if a logical volume on the controller is currently rebuilding.
        * System might hang during power-up or appear unresponsive during runtime if a logical volume composed of SSD's is created or rebuilding.
        * Negotiated link rate for drives might not be correct.
        * Storage enclosure information for direct attached drives might not be returned correctly in Windows.
        * The HPE SmartCache feature was not available by default on the P816i-a SR Gen10 controller.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.0.22.0
changelog:
  -      Fixed an issue where certain SAS and SATA SSD drives greater than 2 TB will not work in HPE Synergy D3940 Storage Module when attached to HPE Synergy 12Gb SAS Connection Module running firmware version 1.0.20.0


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.1.5.0
changelog:
  -      SATA drives are lost after LI create
        * Enhanced debug instrumentation and fault resilience in firmware.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.2.4.0
changelog:
  -      Fixed an issue where HPE OneView may time out or show stale information while creating a very large number of zone groups.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-26-2014
changelog:
  -     Added support for the HP Dynamic Smart Array B140i to allow the user to launch
      the HP Smart Storage Administrator (HPSSA) application from the System
      Utilities menu.
      
      Updated the HP RESTful API resources of type HpBiosAttributeRegistrySchema to
      schema version 1.1.0, adding additional meta-data for Immutable and Write-Only
      BIOIS attributes.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated help documentation for System Utilities and the UEFI Embedded Shell.
      
      Updated the HpBiosAttributeRegistry resources to match the latest
      BIOS/Platform Configuration options.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-26-2014
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where under extremely rare circumstances the server may
      become unresponsive during boot after experiencing a fatal system error. When
      this issue occurs, the Integrated Management Log (IML) will not have any
      indication of the error.
      
      Addressed an issue where the Administrator Password and Power-On Password were
      incorrectly allowed to be entered with a length of 32 characters with previous
      revisions of the System ROM. These passwords should support a maximum length
      of 31 characters. If a 32 character Administrator Password or Power-On
      Password had been configured in the server, updating to this revision of the
      System ROM will no longer allow entering these passwords. In this case, the
      user must set Switch 5 to the ON position to disable these passwords. The
      Administrator Password and Power-On Password must then be re-entered into the
      system with a maximum length of 31 characters.
      
      Addressed a rare intermittent issue where the F10 prompt to enter Intelligent
      Provisioning is not displayed. Note that the Integrated Lights-Out (iLO)
      Firmware had a similar issue. To address all cases of the F10 prompt not being
      displayed, also update the iLO Firmware to revision 2.02.
      
      Addressed an issue where selecting "Erase User Defaults" (to erase user
      defined defaults) in BIOS/Platform Configuration (RBSU) does not take effect
      if the user also selected Restore Default System Settings or Restore Default
      Manufacturing Settings.
      
      Addressed an issue where the Integrated Management Log (IML) or operating
      system log would report multiple error entries when an Non-Maskable Interrupt
      (NMI) occurs.
      
      Addressed an issue where the system may shutdown when a fatal error occurs in
      the pre-OS environment (such as the System Utilities or Embedded UEFI Shell)
      and not log any entry into the Integrated Management Log (IML).
      
      Addressed an issue where the server would become unresponsive during boot with
      DIMM configurations that include both when configured with 16GB and 32GB
      LRDIMMs.
      
      Addressed an issue where an HP Smart Array controller installed in a PCI
      Express Slot attached to Processor 2 may not be visible on the first boot
      after the server experiences an unexpected shutdown that requires using the HP
      Smart Storage Battery to backup storage data.
      
      Addressed an issue where the system would continue to run (server did not
      perform a Blue Screen or reset as expected) when a Non Maskable Interrupt
      (NMI) occurs when using Microsoft Windows 2008 or Microsoft Windows 2008 R2
      when Processor x2APIC Support is configured to Enabled (the default value).
      This issue does not impact other operating systems.
      
      Addressed an issue where optical drives were not properly reported in the
      server One Time Boot Menu when the HP Smart Array B140i Smart Array controller
      is enabled.
      
      Addressed an issue where the server could experience a Red Screen reported as
      a General Protection Error when a user-initiated driver recover/rebuild
      operation is issued to the HP Dynamic Smart Array B140i controller.
      
      Addressed a rare issue in which the user was not prompted or was not prompted
      correctly when exiting the UEFI System Utilities.
      
      Addressed an issue with the fwupdate Embedded UEFI Shell command that may
      cause the system to become unresponsive during some firmware updates.
      
      Addressed an issue with the sysconfig Embedded UEFI Shell command that may
      cause the system to become unresponsive when using "sysconfig -d get
      userdefaults all" when the user defaults have not been configured.
      
      Addressed an issue where changing the boot order using the HP RESTful
      Interface may result in the system not responding to key presses for F9
      (System Utilities) or F11 (Boot Menu) during subsequent system boot.
      
      Addressed an issue that resulted in incorrect association of PCI devices to
      BIOS Attributes in the HpBiosMappings resource of the HP RESTful Interface.
      
      Addressed an issue that could cause the server's Time Zone setting to be
      configured to an invalid value when non-volatile storage becomes corrupted due
      to a battery failure.
      
      Addressed an issue where HP Smart Array error messages are not logged to the
      Integrated Management Log (IML).
      
      Addressed an issue that can result in an inability to access the Virtual
      Install Disk volume from the Embedded UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.21_11-03-2014
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where systems may experience one of the following
      conditions: A "207 - Memory Initialization Error" message and Integrated
      Management Log (IML) event which results from one or more DIMMs not being
      initialized and in which not all installed memory will be available to the
      operating system; a performance degradation (caused by an excessive amount of
      corrected memory errors but which may not have any indication that this is the
      cause); or a Corrected Memory Error Threshold event logged to the IML. If a
      system experiences any of these conditions, the System ROM should be updated
      to this version or later before contacting service or replacing any hardware
      components.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.30_12-24-2014
changelog:
  -     Added support for a Generic USB Boot entry in the UEFI Boot Order list. This
      new entry is used as a place holder for any USB device that is bootable in
      UEFI. The user can set the boot priority of this Generic USB Boot entry, and
      retain this priority for use with USB devices that might be installed in the
      future. Attempting to boot from the Generic USB Boot entry will result in
      attempting all UEFI bootable USB devices that are available in the system. The
      user can still control the priority of the boot entries of individual USB
      devices in the UEFI Boot Order list. This new Generic USB Boot entry will now
      be visible by default in the UEFI Boot Order after updating to this System ROM
      release. This new option is applicable only in UEFI Boot Mode and might be
      configured from the HP RESTful API or the System Utilities BIOS/Platform
      Configuration (RBSU). Note: The system will attempt to boot all UEFI bootable
      USB devices in the order of the Generic USB Boot entry even if installed
      individual USB devices are configured lower in the boot order.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) Fibre
      Channel/FCoE Scan Policy menu that allows the user to select how the UEFI BIOS
      will scan for valid Fibre Channel (or boot from SAN) boot targets. By default,
      the system will now only scan for Fibre Channel boot targets that are
      configured in each adapter. In the past, the system would scan for all Fibre
      Channel or FCoE available targets, potentially resulting in long boot times
      and large number of entries in the UEFI Boot Order list. The boot targets for
      adapters can be configured using the adapter specific menu in the System
      Utilities, System Configuration menu, or using management software such as HP
      Virtual Connect or HP OneView. This setting is applicable only in UEFI Boot
      Mode. A firmware update of the fibre channel controller might also be required
      to take full advantage of this feature.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) NUMA Group
      Size Optimizations menu that allows the user to select how the platform will
      report processor grouping to the operating system. For some applications which
      cannot optimally handle high logical processor counts that are optimally
      divided into smaller groups, it might be necessary to change the default
      setting to get optimal performance.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) I/O Non-Posted
      Prefetching performance option that allows the user to configure how the
      chipset balances I/O traffic for PCI-e devices. Disabling this option has been
      shown to provide performance benefits in a very small subset of configurations
      including certain Infiniband configurations that require a balanced mix of
      read and write traffic as well as configurations with multiple x16 devices
      that utilize the max bandwidth of the PCI-e bus. Since disabling the option
      also has a negative impact on maximum I/O read bandwidth, the overwhelming
      majority of configurations will benefit from leaving this option at the
      default.
      
      Added support for Memory Mirroring Mode. This option can be selected from the
      Advanced Memory Protection Mode selection. This option provides enhanced
      memory availability and resiliency but requires additional memory be installed
      to achieve the same amount of memory available to the operating system.
      
      Added support for loading the Embedded UEFI Shell Auto-Startup script from the
      network in addition to physical/virtual media. The URL describing the network
      (HTTP or FTP) location of the startup script can be configured in the System
      Utilities /Platform Configuration (RBSU), under the Embedded Shell menu. This
      allows for using the Embedded UEFI Shell as a scriptable deployment
      environment without the need for physical or virtual media (on a bare metal
      system).
      
      Added support to Standard Format Output (SFO) to the SysConfig command in the
      Embedded UEFI Shell. This allows for easier parsing of the command output
      using Shell scripts.
      
      Added support for boot from URL (HTTP or FTP) functionality in UEFI Boot Mode.
      The network settings (DHCP or static IP) and boot file URL can be configured
      in the new System Utilities BIOS/Platform Configuration (RBSU) Pre-Boot
      Network settings menu. The file can either be a UEFI Network Boot Program
      (NBP), or an ISO image containing a UEFI bootable OS image. The Boot from ISO
      support is currently limited to operating systems that have a self contained
      OS image (such as WinPE, mini Linux, or VMware ESX installer). Booting Windows
      or Linux OS installation media is currently not supported.
      
      Added support for a webclient command in the Embedded UEFI Shell. The command
      can be used to download files from HTTP and FTP servers. It can also be used
      to download ISO CD/DVD images and mount them in memory as RAM disks.
      
      Added support for an FTP command in the Embedded UEFI Shell. The command can
      be used to download and upload files to/from FTP servers.
      
      Added support for a Compress command in the Embedded UEFI Shell. The command
      can be used to compress and decompress ZIP files.
      
      Added support for a SecBoot command in the Embedded UEFI Shell. The command
      can be used to display the Secure Boot keys and certificates.
      
      Enhanced the RamDisk command in the Embedded UEFI Shell to support FAT32 RAM
      disks, increasing the disk size limit from 512 MB to 2GB.
      
      Added support for the HP Dual 8GB MicroSD EM USB Kit. This device can be
      plugged into the internal USB port on the server to allow a mirrored MicroSD
      card solution.
      
      Added support to configure the BIOS Serial Console Baud Rate to 38400 from the
      System Utilities BIOS/Platform Configuration (RBSU).
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) Internal SD
      Card Slot menu located in USB Options that allows the user to disable boot
      from the embedded SD card.
      
      Added support for Intel Trusted eXecution Technology (TXT).
      
      Updated OpenSSL support to version 0.9.8zb to address potential issues that
      might impact the UEFI Secure Boot support.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the HP RESTful API HpBiosAttributeRegistrySchema to version 1.2.0,
      adding support for BIOS Attributes of type "Password". Also added a new
      GrayOut property that can be used to describe some dependency scenarios. Also
      updated enumDescriptions of all enum definitions in the schema.
      
      Updated the HP RESTful API HpBios, HpServerBootSettings, HpBiosMappsings
      schemas to version 1.1.0. Added support for self-links in these resources.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated help documentation for System Utilities and the Embedded UEFI Shell.
      
      Increased timeout values in Embedded UEFI Shell IfConfig command to reduce the
      chances of network DHCP configuration failing due to timeouts caused by delays
      on the network or slow response when trying to contact the DHCP server.
      
      Enhanced the UEFI Exception handler to provide extended debug and trace
      information when in a pre-OS environment.
      
      Added support for the HP BLc PCIe Expansion Blade and the HP D2220sb Storage
      Blade.
      
      Added support for the WS460c Gen9.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.30_12-24-2014
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the FwUpdate Embedded Shell Application and the
      Firmware Update pre-boot application could hang during a firmware update and
      not successfully flash the device.
      
      Addressed an issue where the system might become unresponsive during boot when
      an unsupported memory configuration is installed on processor 2. With this
      unsupported configuration, in this situation there is no user feedback on the
      monitor or in the Integrated Management Log (IML). With this revision of the
      System ROM, the system will properly display a message indicating the error
      and halt the boot process.
      
      Addressed an issue with some network devices name display in the System
      Utilities.
      
      Addressed an issue that would result in incorrect or corrupt UEFI boot order
      data, or malformed JSON output from the HP RESTFul API HpServerBootSettings
      resource. This also addresses an issue in configuring the server UEFI Boot
      Order using HP OneView and the HP RESTful API.
      
      Addressed an issue in accessing the file systems or booting to some RAID0
      logical volumes off HP Smart Array controllers. This includes accessing the
      file system on such drivers in the System Utilities menus and the Embedded
      UEFI Shell.
      
      Addressed an issue that might result in the BIOS Console Redirection support
      using the Virtual Serial Port to become non-functional.
      
      Addressed an issue with incorrect system time in Microsoft Windows operating
      systems when booted in Legacy BIOS Boot Mode. When the system time or time
      zone are changed, on reboot the system time might 'jump' by the current
      operating system time zone offset. This issue does not occur when booting in
      UEFI Boot Mode. The change also removes the System Utilities BIOS/Platform
      Configuration (RBSU) option for ACPI RTC Support.
      
      Addressed an issue where the system might experience a Machine Check Exception
      under heavy stress conditions when configured with an Intel Xeon E5-2609
      processor. This issue does not affect any other processor models.
      
      Addressed an issue where the server might become unresponsive after a user has
      repeatedly entered and incorrect Power-On or Administrator Password.
      
      Addressed an issue where the server might become unresponsive after looping
      through the UEFI Boot Order an extended amount of time when no valid boot
      targets are detected. This issue only effects the server when configured in
      UEFI Boot Mode.
      
      Addressed an issue where a server might not be able to properly boot Windows
      Server 2008 R2 when configured with an Optional Graphics Card or GPGPU.
      
      Addressed an issue where the industry standard SMBIOS tables would not
      properly indicate the number of active cores when Intel Hyperthreading is
      disabled. The number of active cores would not be reported properly by some
      utilities.
      
      Addressed an issue where Wake On LAN does not function if the system was
      shutdown prior to booting an operating system (such as during the boot process
      or from the Embedded UEFI Shell). Wake On LAN does function properly if the
      system had been shut down from an operating system.
      
      Addressed an issue where the server would boot slowly when BIOS Serial Console
      was enabled to the iLO Virtual Serial Port.
      
      Addressed an issue where the server could be configured for Online Spare
      Memory Mode when the DIMM configuration did not support this mode.
      
      Addressed an issue where a USB key was still bootable when the USB Boot
      Functionality was disabled from System Utilities BIOS/Platform Configuration
      (RBSU). This issue does not impact systems configured for UEFI Boot Mode.
      
      Address an issue where the SysConfig command from the Embedded UEFI Shell
      could not be used to configure Secure Boot even when the user had indicated
      physical presence when entering the Embedded UEFI Shell.
      
      Addressed various issues where network boot support options might not be
      applied properly from HP Virtual Connect or HP OneView.
      
      Addressed an issue where the Legacy Boot Order menu in the System Utilities
      BIOS/Platform Configuration (RBSU) might have incorrect port numbers when the
      server is configured in Legacy Boot Mode. This issue did not affect servers
      configured for UEFI Boot Mode.
      
      Addressed an issue where a server configured with a Trusted Platform Module
      (TPM) and Microsoft Windows 2012 R2 BitLocker might incorrectly prompt the
      user for a recovery password following a warm reset.
      
      Addressed an issue where messages displayed during the early boot process
      would not be displayed properly when viewed over BIOS Serial Console.
      
      Addressed an issue where the One Time Boot Menu includes network boot options
      for devices even when network boot is disabled for those devices.
      
      Addressed an issue where BIOS Serial Console redirection would not work
      properly when the terminal was configured in VT100+ mode and the server was
      configured for Legacy Boot Mode. This issue does not impact systems configured
      for UEFI Boot Mode.
      
      Addressed an issue where Linux dmesg might report a USB error message such as
      "EHCI: BIOS handoff failed" when the system was configured in Legacy Boot
      Mode. When this issue occurs, USB support still functions properly under the
      operating system and the error message is erroneous. This change only prevents
      the display of the erroneous message and does not impact USB functionality.
      
      Addressed several issues with the legacy USB support (USB support before the
      operating system loads) when the system is configured for Legacy Boot Mode.
      This includes addressing an issue where the system might log a 303/304
      Keyboard controller failure error when certain USB KVMs are attached to the
      system.
      
      Addressed an issue where the SATA port numbers reported in the System
      Utilities BIOS/Platform Configuration (RBSU) would not properly match the port
      numbers reflected by labels on the system.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-06-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      Addressed an issue where the HP BL c-Class Expansion blade may not function
      properly after flashing to v1.30 12/24/2014 System ROM until system defaults
      are restored from the ROM Based Setup Utility (RBSU).
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-06-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-06-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed.  The actual
      BIOS included with this revision is the same as ver. 1.32_03-06-2015.  It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-06-2015. Please refer to the
      Customer Advisory at <http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533> for additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      Addressed an issue where the HP BL c-Class Expansion blade may not function
      properly after flashing to v1.30 12/24/2014 System ROM until system defaults
      are restored from the ROM Based Setup Utility (RBSU).
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.33_04-03-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where SATA hard drives attached to the integrated chipset
      SATA controller may not be discovered periodically during a server reboot.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_05-06-2015
changelog:
  -     Added a Server Security BIOS/Platform Configuration (RBSU) option to Enable or
      Disable "Processor AES-NI Support". This option enables or disables the
      Advanced Encryption Standard Instruction Set. The option is enabled by default
      and was enabled automatically with previous revisions of the BIOS.
      
      Added support for UEFI iSCSI Software Initiator boot functionality. The iSCSI
      Software Initiator boot support can be enabled on any network card that is in
      Ethernet mode. The iSCSI network settings can be configured in the new System
      Utilities BIOS/Platform Configuration (RBSU) iSCSI Boot Configuration menu, as
      well as using the HP RESTful API HpiScsiSoftwareInititiator resource type.
      This option is only available in UEFI Boot Mode.
      
      Added a BIOS/Platform Configuration (RBSU) Network Option for VLAN
      Configuration. This option allows the user to configure Virtual LAN (VLAN)
      settings for all network devices present in the system. This option is only
      available in UEFI Boot Mode.
      
      Added a new System Utilities Embedded Applications Active Health System Log
      option. This option allows users to download Active Health System (AHS) Logs.
      
      Added support for additional Storage Options to BIOS/Platform Configuration
      (RBSU). These new options allow the user to configure the number of boot
      targets that are listed per storage controller in the UEFI Boot Order. This
      option can be used to limit the number of boot targets to simplify the UEFI
      boot order and decrease boot time. These options are only available in UEFI
      Boot Mode.
      
      Added pre-boot OHCI USB support. This will allow an optional PCIe USB
      controller, such as available on the Teradici PCoIP Zero Client card, to be
      functional in a pre-boot environment. This also adds support for booting from
      USB devices attached to optional PCIe OHCI USB controllers. Support for OHCI
      USB controllers should be available from operating system drivers when not in
      the pre-boot environment.
      
      Added support for a new partitions command in the Embedded UEFI Shell. This
      command can be used to view all available drive partitions.
      
      Added support for a new ahsdownload command in the Embedded UEFI Shell. This
      command can be used to download Active Health System (AHS) files.
      
      Added support for a new restclient command in the Embedded UEFI Shell. This
      command can be used to configure the server through the HP RESTful services.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the HPRESTful API support to report and set the default UEFI Boot
      Order settings using the HpServerBootOrder resource type.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API support for HpBios resource to rename "SecureBoot"
      property to "SecureBootStatus" to avoid conflict with the "SecureBoot"
      property in HpSecureBoot resource. This change will impact any scripts written
      with a dependency on the "SecureBoot" property in the HpBios resource.
      
      Updated the System Utilities BIOS/Platform Configuration (RBSU) Fibre
      Channel/FCoE Scan Policy option to default to Scan Configured Targets only.
      Previous revisions of the System ROM defaulted to scanning all targets.
      
      Enhanced the thermal solution to provide proper cooling for optional PCIe
      graphics and acceleration cards.
      
      Enhanced the System Utilities System Information and the Embedded UEFI Shell
      sysinfo command to provide additional details for the processor, memory, PCI
      subsections. In addition, added a new Firmware Information menu to System
      Information to provide a list of current firmware revisions for supported
      components.
      
      Reduced boot time when the Dynamic Smart Array B140i RAID is enabled.
      
      Added a new Server Availability BIOS/Platform Configuration (RBSU) Automatic
      Power On configuration option setting. This option allows the user to
      configure the power on policy of the server when power is first applied. The
      options are Enabled to allow the server to automatically power on when first
      installed into the enclosure or Disabled to allow the server to remain powered
      off when first installed into the enclosure.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_05-06-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the platform may become unresponsive during system
      boot when the server is configured for Legacy Boot Mode and the USB Boot
      Support has been disabled.
      
      Addressed an issue where the Intel NIC DMA Channels (IOAT) option could not be
      properly be configured from the Embedded UEFI Shell via the Sysconfig command.
      
      Addressed an issue where the +/- keys in the BIOS/Platform Configuration
      (RBSU) Boot Options menu were not functioning properly when configuring the
      server through a BIOS Serial Console Session.
      
      Addressed an issue where the fwupdate Embedded UEFI Shell command and the
      Firmware Update pre-boot application could hang during a firmware update and
      not successfully flash the device.
      
      Addressed an issue where the server may fail to boot properly to a Windows
      Deployment Server (WDS) when configured for IPv6 network boot mode.
      
      Addressed an issue where an optional PCIe adapter's legacy Expansion ROM may
      not run properly or the Expansion ROM's Setup Utility may not run properly
      when the server is configured for Legacy Boot Mode. This issue was seen with a
      Seagate storage adapter but may impact other devices.
      
      Addressed an issue where the Administrator Password would not be properly
      configured from the Embedded UEFI Shell Sysconfig command.
      
      Addressed an issue where a system could become unresponsive when booting to
      Linux Operating when serial output was enabled from the operating system and
      the iLO Virtual Serial Port was the only enabled UART.
      
      Addressed various issues with webclient and ftp commands in the Embedded UEFI
      Shell.
      
      Addressed an issue in which an Interphase audio streaming PCI-express
      expansion card may not achieve optimal performance resulting in dropped
      packets when streaming data. A similar issue could be seen with other PCI-
      express expansion cards implemented with a PCI device behind a PLX PCIe-to-PCI
      bridge. This type of PCI-express card implementation is more common with older
      PCI-express expansion cards.
      
      Addressed an issue where the system may experience a Linux kernel panic when
      booting from a SATA optical drive attached to the embedded SATA controller
      when the SATA controller is configured for Dynamic Smart Array B140i support.
      
      Addressed an issue where the system health LED would remain blinking RED
      (indicating a failed state) due to a power supply failure after the power
      supply had been replaced. Once the power supply is replaced, the system health
      LED should have returned to the blinking GREEN state. With previous revisions
      of the System ROM, the system health LED would not return to GREEN until after
      a reboot when a failed power supply is replaced.
      
      Addressed an issue where the system health LED would remain blinking AMBER
      (indicating a degraded state) due to an installed power supply not being
      plugged in after the power supply had been plugged in. Once the power supply
      is plugged in, the system health LED should have returned to the blinking
      GREEN state. With previous revisions of the System ROM, the system health LED
      would not return to GREEN until after a reboot when an unplugged power supply
      is plugged in.
      
      Addressed an issue where a system may become unresponsive when launching a
      guest operating system under a Hypervisor operating system such as Citrix or
      VMware when VT-d is enabled. This issue is NOT unique to HP servers.
      
      Addressed a possible issue where the platform may become unresponsive during
      POST when the user selects the Simplified Chinese language in System
      Utilities.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.50_07-21-2015
changelog:
  -     Added a Date and Time BIOS/Platform Configuration (RBSU) option to configure
      the Time Format. This option controls how the system date and time is stored
      in the Real Time Clock and presented to the operating system. By default, the
      time is formatted for Coordinated Universal Time (UTC). The users may
      optionally change the time format to Local Time which removes the use of the
      time zone. This option may be used to work around interaction issues between
      the system and Microsoft Windows operating systems running in legacy boot mode
      that can result in the time to be incorrect.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) IPv6 DHCP
      Unique Identifier menu that allows the user to select how the UEFI BIOS will
      use the DHCP Unique Identifier (DUID) for IPv6 PXE Boot. By default, the
      system will use the server's Unique Universal Identifier (UUID). The user can
      now optionally select to use the DUID-LLT as the unique identifier for PXE
      Boot. This setting applies when the server is configured to UEFI Boot Mode.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.50_07-21-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience Machine Check Exceptions or
      unexpected reboots under heavy load and high temperature. This issue is NOT
      unique to HP servers. HP recommends that users experiencing these issues
      update to this revision of the System ROM before replacing any hardware
      components.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) Dynamic Power Savings Mode Response Option when configured for Slow
      Mode may not efficiently switch processor performance modes resulting in lower
      than expected performance.
      
      Addressed an issue where the system may not properly respond to error events
      from devices attached to certain PCI Express root ports.
      
      Addressed an issue where the Channel Interleaving option in the ROM Based
      Setup Utility (RBSU) did not function when configured for Disabled. Even when
      this option was configured to Disabled, Channel Interleaving would be enabled.
      
      Addressed an issue where a server configured for UEFI boot mode may become
      unresponsive during boot when configured with an optional graphics controller
      that does not support UEFI boot mode. This issue does not affect systems
      configured in Legacy Boot Mode.
      
      Addressed an issue in the HP RESTful API data model with the reporting of
      "EmbSasXBoot" and "SlotXStorageBoot" properties in the HpBiosMappings
      resource. The properties were not associated with the correct PCI devices for
      the embedded and optional storage controllers.
      
      Addressed an issue where the server may become unresponsive during boot when
      configured with a very large number of disks such as fibre adapters.
      
      Addressed an issue in the HP RESTful API BIOS support that resulted in
      internal HTTP sessions between BIOS and iLO left open during boot. This can
      result in the iLO Event Log indicating multiple events for HTTP session
      logins.
      
      Addressed an issue where the system would become unresponsive during boot and
      display a NMI error when configured with an optional PCI Express device
      supporting older versions of the PCI Express specification.
      
      Addressed an issue where the system would not reset configuration settings to
      defaults when using the Embedded UEFI Shell Sysconfig -d command.
      
      Addressed an issue where the HP RESTful API and Embedded UEFI Shell
      description of the storage controller may begin with an instance of 2 instead
      of 1 when only one storage controller was installed in the server.
      
      Addressed an issue where the system may fail to boot a Linux Operating System
      when using serial console redirection when the physical Serial Port is
      disabled and the iLO Virtual Serial Port is enabled.
      
      Addressed an issue where a system configured for Legacy Boot Mode may become
      unresponsive during boot and display a NMI error when the Virtual Install Disk
      is enabled.
      
      Addressed an issue where a system configured for UEFI Boot Mode with an
      optional PCI Express based USB 3.0 controller installed may not be able to
      properly load the USB driver under the operating system. This issue does not
      affect systems configured in Legacy Boot Mode.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.52_09-24-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience Machine Check Exceptions or
      unexpected reboots under heavy load and high temperature. This issue is NOT
      unique to HP servers. HP recommends that users experiencing these issues
      update to this revision of the System ROM before replacing any hardware
      components.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) Dynamic Power Savings Mode Response Option when configured for Slow
      Mode may not efficiently switch processor performance modes resulting in lower
      than expected performance.
      
      Addressed an issue where the Channel Interleaving option in the ROM Based
      Setup Utility (RBSU) did not function when configured for Disabled. Even when
      this option was configured to Disabled, Channel Interleaving would be enabled.
      
      Addressed an issue where a server configured for UEFI boot mode may become
      unresponsive during boot when configured with an optional graphics controller
      that does not support UEFI boot mode. This issue does not affect systems
      configured in Legacy Boot Mode.
      
      Addressed an issue in the HP RESTful API data model with the reporting of
      "EmbSasXBoot" and "SlotXStorageBoot" properties in the HpBiosMappings
      resource. The properties were not associated with the correct PCI devices for
      the embedded and optional storage controllers.
      
      Addressed an issue where the server may become unresponsive during boot when
      configured with a very large number of disks such as fibre adapters.
      
      Addressed an issue in the HP RESTful API BIOS support that resulted in
      internal HTTP sessions between BIOS and iLO left open during boot. This can
      result in the iLO Event Log indicating multiple events for HTTP session
      logins.
      
      Addressed an issue where the system would become unresponsive during boot and
      display a NMI error when configured with an optional PCI Express device
      supporting older versions of the PCI Express specification.
      
      Addressed an issue where the system would not reset configuration settings to
      defaults when using the Embedded UEFI Shell Sysconfig -d command.
      
      Addressed an issue where the HP RESTful API and Embedded UEFI Shell
      description of the storage controller may begin with an instance of 2 instead
      of 1 when only one storage controller was installed in the server.
      
      Addressed an issue where the system may fail to boot a Linux Operating System
      when using serial console redirection when the physical Serial Port is
      disabled and the iLO Virtual Serial Port is enabled.
      
      Addressed an issue where a system configured for Legacy Boot Mode may become
      unresponsive during boot and display a NMI error when the Virtual Install Disk
      is enabled.
      
      Addressed an issue where a system configured for UEFI Boot Mode with an
      optional PCI Express based USB 3.0 controller installed may not be able to
      properly load the USB driver under the operating system. This issue does not
      affect systems configured in Legacy Boot Mode.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.00_12-28-2015
changelog:
  -     Added support for Intel Xeon E5-2600 v4 series processors.
      
      Added support for an optional Trusted Platform Module (TPM) 2.0.
      
      Added support to detect and log when memory performance may be degraded due to
      a high rate of correctable memory errors. When this condition is detected, a
      new Integrated Management Log (IML) message will be logged indicating a "High
      rate of corrected memory errors, performance may be degraded".
      
      Added support to the Embedded UEFI Shell to allow the user to export Secure
      Boot certificates to a file.
      
      Added support to automatically initialize the Trusted Platform Modules (TPM)
      nonvolatile storage when the TPM is first installed on a platform. This
      feature helps avoid issues where a TPM may be locked out from use to an
      operating system and requires the user to manually clear the TPM setting from
      the BIOS/Platform Configuration (RBSU) menus when first installed.
      
      Updated branding during the boot process and in the pre-boot System Utilities
      from HP to Hewlett Packard Enterprise. No branding changes were made that
      could impact software running on the system. Industry standard SMBIOS tables
      were NOT updated to reflect Hewlett Packard Enterprise branding.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Added support for the industry standard SMBIOS Type 2 baseboard record.
      
      Added support to the HP RESTful API to allow the user to configure the UEFI
      boot order when the system is configured for Legacy Boot Mode.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.00_12-28-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the user may not be able to properly download an
      Active Health Systems (AHS) file from System Utilities or the Embedded UEFI
      Shell when certain date ranges were used.
      
      Addressed an issue where a system configured with a Trusted Platform Module
      (TPM) may improperly measure an extra EV_SEPARATOR into the TPM PCR7.
      
      Addressed an issue where the Active Health System (AHS) file could not be
      downloaded to the embedded SD card from the Embedded UEFI Shell.
      
      Addressed issues with USB support in the pre-boot environment when the system
      is configured in Legacy Boot Mode. These issues did not affect systems
      configured in UEFI Boot Mode.
      
      Addressed an issue where certain optional PCIe video adapters would fail to
      work properly when using a Linux operating system.
      
      Addressed an issue where industry standard SMBIOS Type 9 entries for PCIe
      Slots attached to a not installed processor did not exist.
      
      Addressed an issue where the UEFI iSCSI Boot Configuration may not work
      properly when configuring these options through the HP RESTful Interface. This
      issue does not affect systems where the UEFI iSCSI Boot Configuration is
      configured through the System Utilities BIOS/Platform Configuration (RBSU).
      
      Addressed an issue where the drives attached to an HP Smart Array controller
      may not be detected on the first boot after switching from UEFI Boot Mode to
      Legacy Boot Mode.
      
      Addressed an issue where the PXE Boot Policy does not function properly when
      the Network VLAN Configuration option is enabled. When Network VLAN
      Configuration is enabled, the server would always attempt to boot both iPV4
      and iPV6 regardless of the PXE Boot Order Policy setting.
      
      Addressed an issue where the server would display a Red Screen error and
      become unresponsive when exiting the System Utilities Embedded User
      Diagnostics when configured for Legacy Boot Mode. This issue does not impact
      systems configured for UEFI Boot Mode.
      
      Addressed an issue where the HP ProLiant Dynamic Power Regulator would not
      function properly when configured for Slow Mode. In rare cases, this could
      cause the system to not optimally switch processor power states.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive from the Embedded UEFI Shell when interrupting the ping command
      via a CTRL-C key press.
      
      Addressed an issue where the system may report a 335-HP RESTful API error
      after setting the BIOS Administrator password through the HP RESTful API.
      
      Addressed an issue where the Date and Time may be set incorrectly when using
      the Date and Time option from the BIOS/Platform Configuration (RBSU) when the
      Daylight Savings Time option is enabled.
      
      Addressed an issue where the server may display a Red Screen error and become
      unresponsive during boot when more than 256 hard drives are attached to a
      storage controller. The UEFI BIOS will now limit the enumeration of bootable
      devices to 256 entries.
      
      Addressed an issue where video is not displayed when using the embedded video
      controller with certain newer monitors, such as the HP E190i, which do not
      properly operate in native resolutions such as 1280x1024.
      
      Addressed an issue with the incorrect version of the HpServerBootSettings
      schema in the HP RESTful API.
      
      Addressed an issue where the server could become unresponsive during boot or
      from the Embedded UEFI Shell when a Block I/O device such as a USB key or hard
      drive has a corrupt FAT32 file system.
      
      Addressed an issue where an erroneous 312 - HP Smart Battery error message
      would be displayed and logged to the Integrated Management Log (IML) on the
      first boot after the system battery was removed from the server.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the system may become unresponsive and experience a
      Machine Check Exception or NMI under heavy stress conditions when configured
      with Intel Xeon E5-2600 v3 processors and 64GB LRDIMMs in a 3 DIMM Per Channel
      configuration. This issue does not impact systems configured with other memory
      configuration including 64GB LRDIMM with less than 3 DIMMs Per Channel. This
      System ROM revision should be considered the minimum revision required for use
      with 64 GB LRDIMMs in systems with any memory channels containing 3 DIMMs.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive during boot when the Embedded User Partition or Virtual Install
      Disk are enabled or if a USB storage device is installed when the server is
      configured for Legacy Boot Mode. This issue does not impact systems configured
      for UEFI Boot Mode.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016
changelog:
  -     Added support for Intel Xeon E5-1600 v4 series processors.
      
      Enhanced PCIe resource allocation so that systems configured with multiple
      PCIe expansion devices may in some cases no longer report a "276 Option Card
      Configuration Error" during system boot due to not having enough I/O resources
      to support what is requested by the installed devices. This BIOS revision
      allows a wider range of PCIe configurations that request large amounts of I/O
      to be configured properly.
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft. This includes the latest list of revoked
      certificates.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Increased the default timeout value of the iSCSI UEFI Software Initiator boot
      to 20 seconds. This may help resolve issues of intermittent connection drop
      during an iSCSI boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system that experiences an HPE Smart Storage
      Battery failure may become unresponsive when configured with iLO Firmware
      2.40.Note there is an issue wherea system configured with Integrated
      Lights-Out (iLO) Firmware version 2.40 may experience an intermittent and
      false HPE Smart Storage Battery failure, logged in the Integrated Management
      Log (IML).Due to the BIOS issue addressed in this revision, the false HPE
      Smart Storage Battery failure may result in the system becoming unresponsive.
      This issue does not impact systems that are not configured with an HPE Smart
      Storage Battery or systems configured with iLO Firmware 2.30 or earlier.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) USB Boot Options setting may not properly allow the server to boot from
      the internal SD card before a USB key when SD is higher in the priority list.
      This issue only affects servers configured in Legacy Boot Mode.
      
      Addressed an issue where the ambient temperature reported by the system during
      server boot may report incorrectly. This issue also requires an iLO firmware
      version update to a revision later than 2.4x which will be released later this
      year. This issue has no impact on the thermal operation of the server and is
      simply an issue with the temperature displayed during boot. While updating to
      this revision of the BIOS will not address this issue unless the iLO FW
      revision is later than 2.4x, there are no issues caused by updating the BIOS
      without updating iLO FW.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the server health LED may remain set in a degraded or
      failed state after an error event was resolved during server operation.
      Previously, a server reset may have been needed to clear the health LED event.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) option for Embedded UEFI Shell Auto Startup Script Network Location
      does not accept an NSH file name containing upper case characters.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may become unresponsive during boot when
      configured with a HPE Dual microSD device when one of the microSD devices is
      failed or missing.
      
      Addressed an issue where the server may assign incorrect ACPI NUMA proximity
      allocations for servers configured with two or more processors and with memory
      only attached to a single processor socket potentially leading to non-optimal
      performance. This issue does not impact servers with memory configured on
      multiple processors.
      
      Addressed an issue where the Automatic Server Recovery (ASR) setting may not
      be configured properly through the HP RESTful API.
      
      Addressed an issue where the internal SD card would remain active after the
      user has disabled the SD slot from System Utilities BIOS/Platform
      Configuration (RBSU) option. This issue only affects systems configured in
      Legacy Boot Mode.
      
      Addressed an issue where the server may become unresponsive when using the
      PING command from the Embedded UEFI Shell.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may fail to boot from existing UEFI iSCSI
      Software Initiator boot options if the user changed the iSCSI Target IP
      address.
      
      Addressed an issue where the system may fail to boot from UEFI iSCSI Software
      Initiator boot options that has iSCSI Initiator or Target configured using
      static IPv6 addresses.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot option IPv6
      address cannot be configured using the HP RESTful API.
      
      Addressed an issue that may result in losing the existing UEFI iSCSI Software
      Initiator boot options if any of the connection parameters (LUN, Remote Port,
      IP address, login credentials) change.
      
      Addressed an issue in reporting the incorrect PCIe slot number in the error
      messages of failed iSCSI boot attempts.
      
      Addressed an issue of iSCSI boot configuration options not being available
      from the HP RESTful API when there are no network adapters in the system.
      
      Addressed an extremely rare issue where the server may become unresponsive due
      to a Non Maskable Interrupt (NMI) when performing a shutdown or startup from
      an Operating System.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.30_09-12-2016
changelog:
  -     Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft. This includes the latest list of revoked
      certificates.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.30_09-12-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed a rare issue where fatal system errors may not be logged to the
      Integrated Management Log (IML) when an error occurs on any processor other
      than Processor 1.
      
      Addressed an extremely rare issue where the system may receive a Red Screen
      error and become unresponsive during boot. This issue would not be seen if the
      ROM Based Setup Utility (RBSU) Option for Dynamic Power Calibration is set to
      Disabled (the default for this option is Auto which could result in this
      issue).
      
      Addressed an issue where the system would become unresponsive during boot and
      display a NMI error when configured with an optional PCI Express device
      supporting older versions of the PCI Express specification.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017
changelog:
  -     Updated the system thermal logic to support the latest adapters.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017-2.1
changelog:
  -     *Important Notes:**
      
      Version 2.40_02-17-2017 (B) contains updates to the component packaging and is
      functionally equivalent to version 2.40_02-17-2017.  It is not necessary to
      upgrade with Revision B if the system ROM was previously upgraded to version
      2.40_02-17-2017.
      
      SUM version 7.6.0  or earlier should be used for deployment of 2.40_02-17-2017
      (B).
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.42_06-14-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      Added support for the NVIDIA Quadro P6000 Graphics Card with the HPE ProLiant
      WS460c Gen9.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     Added support for Trusted Platform Module (TPM) 2.0 Firmware flash updates.
      For systems configured with the optional TPM 2.0 device, this is the minimum
      revision of the System ROM required to update TPM firmware.
      
      Updated the HPE RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     *Important Notes:**
      
      This System ROM revision replaces the 2.50 revision. An issue was found with
      the 2.50 revision of the System ROM that may result in a system hang during
      boot with a messaging indicating "Memory Initialization - complete" with
      certain memory configurations. The 2.50 revision of the System ROM has been
      removed from the HPE Support Site. It is highly recommended that any customers
      using the 2.50 revision of the System ROM upgrade to the 2.52 revision or
      later.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where Processor Core Disable may not function properly,
      such as disabling the wrong number of cores, when Intel Xeon E5 v4 processors
      are installed in the system. This issue does not impact systems configured
      with Intel Xeon E5 v3 processors.
      
      Addressed an issue where systems configured with a Honeywell LCNP4 card
      installed may stop responding during system boot.
      
      Addressed an issue where the system may become unresponsive during system boot
      when an optional HPE Dual 8GB MicroSD USB device is installed with firmware
      version 202. This issue does not impact servers configured with an HPE Dual
      8GB MicroSD USB device using revision of firmware 212 or later.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.54_12-07-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.56_01-22-2018
changelog:
  -     *Important Notes:**
      
      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.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.42_06-14-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      Added support for the NVIDIA Quadro P6000 Graphics Card.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     *Important Notes:**
      
      This System ROM revision replaces the 2.50 revision. An issue was found with
      the 2.50 revision of the System ROM that may result in a system hang during
      boot with a messaging indicating "Memory Initialization - complete" with
      certain memory configurations. The 2.50 revision of the System ROM has been
      removed from the HPE Support Site. It is highly recommended that any customers
      using the 2.50 revision of the System ROM upgrade to the 2.52 revision or
      later.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where Processor Core Disable may not function properly,
      such as disabling the wrong number of cores, when Intel Xeon E5 v4 processors
      are installed in the system. This issue does not impact systems configured
      with Intel Xeon E5 v3 processors.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.60_10-29-2015
changelog:
  -     Added support for an optional Trusted Platform Module (TPM) 2.0.
      
      Added support to detect and log when memory performance may be degraded due to
      a high rate of correctable memory errors. When this condition is detected, a
      new Integrated Management Log (IML) message will be logged indicating a "High
      rate of corrected memory errors, performance may be degraded".
      
      Added support to the Embedded UEFI Shell to allow the user to export Secure
      Boot certificates to a file.
      
      Added support to automatically initialize the Trusted Platform Modules (TPM)
      nonvolatile storage when the TPM is first installed on a platform. This
      feature helps avoid issues where a TPM may be locked out from use to an
      operating system and requires the user to manually clear the TPM setting from
      the BIOS/Platform Configuration (RBSU) menus when first installed.
      
      Updated branding during the boot process and in the pre-boot System Utilities
      from HP to Hewlett Packard Enterprise. No branding changes were made that
      could impact software running on the system. Industry standard SMBIOS tables
      were NOT updated to reflect Hewlett Packard Enterprise branding.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Added support to the HP RESTful API to allow the user to configure the UEFI
      boot order when the system is configured for Legacy Boot Mode.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.60_10-29-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the user may not be able to properly download an
      Active Health Systems (AHS) file from System Utilities or the Embedded UEFI
      Shell when certain date ranges were used.
      
      Addressed an issue where a system configured with a Trusted Platform Module
      (TPM) may improperly measure an extra EV_SEPARATOR into the TPM PCR7.
      
      Addressed an issue where the Active Health System (AHS) file could not be
      downloaded to the embedded SD card from the Embedded UEFI Shell.
      
      Addressed issues with USB support in the pre-boot environment when the system
      is configured in Legacy Boot Mode. These issues did not affect systems
      configured in UEFI Boot Mode.
      
      Addressed an issue where certain optional PCIe video adapters would fail to
      work properly when using a Linux operating system.
      
      Addressed an issue where industry standard SMBIOS Type 9 entries for PCIe
      Slots attached to a not installed processor did not exist.
      
      Addressed an issue where the UEFI iSCSI Boot Configuration may not work
      properly when configuring these options through the HP RESTful Interface. This
      issue does not affect systems where the UEFI iSCSI Boot Configuration is
      configured through the System Utilities BIOS/Platform Configuration (RBSU).
      
      Addressed an issue where the drives attached to an HP Smart Array controller
      may not be detected on the first boot after switching from UEFI Boot Mode to
      Legacy Boot Mode.
      
      Addressed an issue where the PXE Boot Policy does not function properly when
      the Network VLAN Configuration option is enabled. When Network VLAN
      Configuration is enabled, the server would always attempt to boot both iPV4
      and iPV6 regardless of the PXE Boot Order Policy setting.
      
      Addressed an issue where the server would display a Red Screen error and
      become unresponsive when exiting the System Utilities Embedded User
      Diagnostics when configured for Legacy Boot Mode. This issue does not impact
      systems configured for UEFI Boot Mode.
      
      Addressed an issue where the HP ProLiant Dynamic Power Regulator would not
      function properly when configured for Slow Mode. In rare cases, this could
      cause the system to not optimally switch processor power states.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive from the Embedded UEFI Shell when interrupting the ping command
      via a CTRL-C key press.
      
      Addressed an issue where the system may report a 335-HP RESTful API error
      after setting the BIOS Administrator password through the HP RESTful API.
      
      Addressed an issue where the Date and Time may be set incorrectly when using
      the Date and Time option from the BIOS/Platform Configuration (RBSU) when the
      Daylight Savings Time option is enabled.
      
      Addressed an issue where the server may display a Red Screen error and become
      unresponsive during boot when more than 256 hard drives are attached to a
      storage controller. The UEFI BIOS will now limit the enumeration of bootable
      devices to 256 entries.
      
      Addressed an issue where video is not displayed when using the embedded video
      controller with certain newer monitors, such as the HP E190i, which do not
      properly operate in native resolutions such as 1280x1024.
      
      Addressed an issue with the incorrect version of the HpServerBootSettings
      schema in the HP RESTful API.
      
      Addressed an issue where the server could become unresponsive during boot or
      from the Embedded UEFI Shell when a Block I/O device such as a USB key or hard
      drive has a corrupt FAT32 file system.
      
      Addressed an issue where an erroneous 312 - HP Smart Battery error message
      would be displayed and logged to the Integrated Management Log (IML) on the
      first boot after the system battery was removed from the server.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the server may not properly detect the HPE c-Class
      PCI Expansion Blade.
      
      Removed the System Utilities BIOS/Platform Configuration (RBSU) Automatic
      Power-on Option for Restore Last Power State as this option is not supported
      by blade servers.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016
changelog:
  -     Added support for Intel Xeon E5-4600 v4 series processors.
      
      Added support for 128GB Load Reduced DIMMs (LRDIMM).
      
      Enhanced PCIe resource allocation so that systems configured with multiple
      PCIe expansion devices may in some cases no longer report a "276 Option Card
      Configuration Error" during system boot due to not having enough I/O resources
      to support what is requested by the installed devices. This BIOS revision
      allows a wider range of PCIe configurations that request large amounts of I/O
      to be configured properly.
      
      Updated the UEFI Secure Boot revocations list (DBX) with the latest copy from
      Microsoft.
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft. This includes the latest list of revoked
      certificates.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Increased the default timeout value of the iSCSI UEFI Software Initiator boot
      to 20 seconds. This may help resolve issues of intermittent connection drop
      during an iSCSI boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system that experiences an HPE Smart Storage
      Battery failure may become unresponsive when configured with iLO Firmware
      2.40.  Note there is an issue where a system configured with Integrated
      Lights-Out (iLO) Firmware version 2.40 may experience an intermittent and
      false HPE Smart Storage Battery failure, logged in the Integrated Management
      Log (IML).  Due to the BIOS issue addressed in this revision, the false HPE
      Smart Storage Battery failure may result in the system becoming unresponsive.
      This issue does not impact systems that are not configured with an HPE Smart
      Storage Battery or systems configured with iLO Firmware 2.30 or earlier.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) USB Boot Options setting may not properly allow the server to boot from
      the internal SD card before a USB key when SD is higher in the priority list.
      This issue only affects servers configured in Legacy Boot Mode.
      
      Addressed an issue where the ambient temperature reported by the system during
      server boot may report incorrectly. This issue also requires an iLO firmware
      version update to a revision later than 2.4x which will be released later this
      year. This issue has no impact on the thermal operation of the server and is
      simply an issue with the temperature displayed during boot. While updating to
      this revision of the BIOS will not address this issue unless the iLO FW
      revision is later than 2.4x, there are no issues caused by updating the BIOS
      without updating iLO FW.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the server health LED may remain set in a degraded or
      failed state after an error event was resolved during server operation.
      Previously, a server reset may have been needed to clear the health LED event.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) option for Embedded UEFI Shell Auto Startup Script Network Location
      does not accept an NSH file name containing upper case characters.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may become unresponsive during boot when
      configured with a HPE Dual microSD device when one of the microSD devices is
      failed or missing.
      
      Addressed an issue where the server may assign incorrect ACPI NUMA proximity
      allocations for servers configured with two or more processors and with memory
      only attached to a single processor socket potentially leading to non-optimal
      performance. This issue does not impact servers with memory configured on
      multiple processors.
      
      Addressed an issue where the Automatic Server Recovery (ASR) setting may not
      be configured properly through the HP RESTful API.
      
      Addressed an issue where the internal SD card would remain active after the
      user has disabled the SD slot from System Utilities BIOS/Platform
      Configuration (RBSU) option. This issue only affects systems configured in
      Legacy Boot Mode.
      
      Addressed an issue where the server may become unresponsive when using the
      PING command from the Embedded UEFI Shell.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may fail to boot from existing UEFI iSCSI
      Software Initiator boot options if the user changed the iSCSI Target IP
      address.
      
      Addressed an issue where the system may fail to boot from UEFI iSCSI Software
      Initiator boot options that has iSCSI Initiator or Target configured using
      static IPv6 addresses.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot option IPv6
      address cannot be configured using the HP RESTful API.
      
      Addressed an issue that may result in losing the existing UEFI iSCSI Software
      Initiator boot options if any of the connection parameters (LUN, Remote Port,
      IP address, login credentials) change.
      
      Addressed an issue in reporting the incorrect PCIe slot number in the error
      messages of failed iSCSI boot attempts.
      
      Addressed an issue of iSCSI boot configuration options not being available
      from the HP RESTful API when there are no network adapters in the system.
      
      Addressed an extremely rare issue where the server may become unresponsive due
      to a Non Maskable Interrupt (NMI) when performing a shutdown or startup from
      an Operating System.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.30_09-12-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed a rare issue where fatal system errors may not be logged to the
      Integrated Management Log (IML) when an error occurs on any processor other
      than Processor 1.
      
      Addressed an extremely rare issue where the system may receive a Red Screen
      error and become unresponsive during boot. This issue would not be seen if the
      ROM Based Setup Utility (RBSU) Option for Dynamic Power Calibration is set to
      Disabled (the default for this option is Auto which could result in this
      issue).
      
      Addressed an issue where the system would become unresponsive during boot and
      display a NMI error when configured with an optional PCI Express device
      supporting older versions of the PCI Express specification.
      
      Addressed an issue where the system may not perform optimally with certain
      memory intensive workloads when the BIOS Configurations/RBSU QPI Snoop
      Configuration option is configured for Cluster on Die mode with Intel Xeon
      E5-4600 v4 series processors. This issue does NOT impact systems configured
      with Intel Xeon E5-4600 v3 series processors or with other QPI Snoop
      configurations. This issue had a significant impact on the STREAM benchmark.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.42_04-05-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an extremely rare issue where the server may become unresponsive
      during POST when configured with memory configurations that are 6TB or larger.
      In some cases, this issue would be seen as a Red Screen with a General
      Protection Fault.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.42_04-05-2017-2.1
changelog:
  -     *Important Notes:**
      
      Version 2.42_04-05-2017 (B) contains updates to the component packaging and is
      functionally equivalent to version 2.42_04-05-2017.  It is not necessary to
      upgrade with Revision B if the system ROM was previously upgraded to version
      2.42_04-05-2017.
      
      SUM version 8.0.0 or later should be used for deployment of 2.42_04-05-2017
      (B).
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an extremely rare issue where the server may become unresponsive
      during POST when configured with memory configurations that are 6TB or larger.
      In some cases, this issue would be seen as a Red Screen with a General
      Protection Fault.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.50_10-01-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where Processor Core Disable may not function properly,
      such as disabling the wrong number of cores, when Intel Xeon E7 v4 processors
      are installed in the system. This issue does not impact systems configured
      with Intel Xeon E7 v3 processors.
      
      Addressed an issue where systems configured with a Honeywell LCNP4 card
      installed may stop responding during system boot.
      
      Addressed an issue where the system may become unresponsive during system boot
      when an optional HPE Dual 8GB MicroSD USB device is installed with firmware
      version 202. This issue does not impact servers configured with an HPE Dual
      8GB MicroSD USB device using revision of firmware 212 or later.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_11-08-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where systems configured with 128GB LRDIMMs may see a high
      rate of correctable memory errors, sometimes reported as a memory pre-failure
      event in the iLO Integrated Management Log (IML). This issue does not impact
      systems configured with other memory configurations. HPE recommends customers
      update to this version of the System ROM before replacing any memory
      components.
      
      Addressed an issue where Processor Core Disable may not function properly,
      such as disabling the wrong number of cores, when Intel Xeon E7 v4 processors
      are installed in the system. This issue does not impact systems configured
      with Intel Xeon E7 v3 processors.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     Added support for Dynamic Power Capping. This support requires Power
      Management Controller Firmware version 1.0.4 and Integrated Lights-Out (iLO)
      Firmware version 1.15 or later.
      
      Added support for the HPE Core Boost Technology. This feature requires HPE
      Innovation Engine Firmware 0.1.2.6 or later.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for LLC Dead Line Allocation. When running certain applications,
      modifying this setting from its default value may improve system performance.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for Stale A to S. When running certain applications, modifying this
      setting from its default value may improve system performance.
      
      Added support to detect and report unbalanced memory configurations that may
      result in non-optimal performance. Please consult the Memory Population
      Guidelines for more information on memory population rules and
      recommendations.
      
      Added a new Auto option for the XPT Prefetcher in the BIOS/Platform
      Configuration (RBSU) menu that will default the XPT prefetcher to disabled
      based on a current Intel sighting processor issue.  Enabling this option (via
      setting this option for Force Enable) may improve latency performance, but
      Intel has indicated rare stability issues may occur if XPT Prefetcher is
      enabled.
      
      Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated the system thermal logic to support the latest GPU adapters.
      
      Updated the RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the language translations (non-English modes) for System Utilities.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the Embedded UEFI Shell restclient utility would not
      properly configure attributes for Network TLS (HTTPS) support.
      
      Addressed an issue where the UEFI or Legacy Boot Order could still be modified
      after an incorrect Administrator Password was entered in the BIOS/Platform
      Configuration (RBSU) menus.
      
      Addressed an issue where the embedded AHCI SATA controller would not show up
      properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no
      drives were attached to the controller.
      
      Addressed an issue where saving a configuration setting from an optional
      device's configuration page in the System Utilities menu would not be saved
      properly.  This issue was seen with one Network Adapter card.
      
      Addressed an issue where the system ROM would not correctly report a
      configuration error for the HPE Smart Battery storage subsystem when more
      devices were installed than could be supported by the installed battery.
      
      Addressed an issue where a platform configured with direct attached NVMe hard
      drives may report the incorrect location (box and bay location) from the
      System Utilities page.
      
      Addressed an issue where the System Utilities menu may not show the proper
      name for an optional PCIe Adapter.
      
      Addressed an issue where the Integrated Lights Out (iLO) remote Console
      Keyboard and Mouse may not function properly when the system is configured for
      Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot
      Mode.
      
      Addressed an issue where the HPE Jitter Performance feature settings could not
      be properly modified from the Integrated Lights Out web interface.
      
      Addressed an issue where the system may report that the HPE Smart Battery is
      charging when in fact the battery has failed. It is recommended to flash to
      this system ROM if a system is reporting Smart Battery issues.
      
      Addressed an issue where the Trusted Platform Module (TPM) option for TPM
      Visibility could not be configured through the RESTful API.
      
      Addressed an issue where the system may become unresponsive when repeatedly
      typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.
      This issue does not impact systems in UEFI Boot Mode or a system once the
      system boots into an operating system.
      
      Addressed an issue where certain third party PCIe adapters, such as a Dialogic
      adapter, would not function properly due to the PCIe Maximum Payload size
      being incorrectly programmed.
      
      Addressed an issue where certain NVMe devices may not be detected when the x16
      slot PCIe Riser and three slot x8 riser are present in the server.
      
      Addressed an issue where a Network Boot option would still show an entry  in
      the Legacy Boot Order when Network Boot was disabled on the device from the
      BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not
      affect systems configured for UEFI Boot Mode.
      
      Addressed an issue where the system may become unresponsive when using the TAB
      key in the BIOS/Platform Configuration (RBSU) menus.
      
      Addressed an issue where the BIOS would not properly identify and halt a
      system from booting with an invalid DIMM configuration.
      
      Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy
      Efficient Turbo setting was "backwards".  When the configuration setting was
      set to enabled, the feature would actually be Disabled.  When configured to
      Disabled, the feature would actually be enabled.
      
      Addressed an issue where the server might lockup and display a red screen when
      trying to repair a failed RAID volume off of an S100i SW RAID controller.
      
      Addressed an issue where the RESTful API may report that BIOS settings were
      not applied properly even when they are properly configured.
      
      Addressed an issue where the system may become unresponsive during boot after
      a warm reset, typically seen with a blank screen, when a Trusted Platform
      Module (TPM) is installed.  If reboot issues are seen with systems containing
      an optional TPM, it is highly recommended the System ROM be enabled to this
      revision or later.
      
      Addressed an extremely rare issue where the system may incorrectly report a
      413 Innovation Engine Authentication Error on a server reboot.
      
      Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo
      disable functionality.
      
      Removed the Platform Configuration (RBSU) Option to enable or disable the
      Embedded Diagnostics.  Embedded Diagnostics is not supported on this server
      and the menu option should not have been available and was not functional.
      
      Remove Embedded Diagnostics support from System Utilities.
      
      Removed support for the chipset firmware based Trusted Platform Module (TPM)
      known as Intel Platform Trust Technology (Intel PTT). This feature is no
      longer supported due to stability issues and Intel recommends not supporting
      this feature. Users should instead install a discrete HPE TPM option for this
      support.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.22_09-29-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the system would not achieve maximum performance
      results when the BIOS/Platform Configuration (RBSU) Sub-NUMA Clustering option
      is enabled. This option is not enabled by default.
      
      Addressed an issue where the system may have the system time incorrectly
      "shifted" to the incorrect time after the operating system has been running
      for an extended period of time. This issue was typically seen under Microsoft
      Windows when the Set Time Automatically option was enabled from the Windows
      Date and Time Settings configuration page.
      
      Addressed an issue where the system may report an inaccurate error message in
      the Integrated Management Log (IML) when a memory training failure occurred.
      It is recommended that customers update to this version of the system ROM
      before replacing any DIMMs due to a training issue.
      
      Addressed an issue where the system may experience an erroneous boot-time
      message and Integrated Management Log (IML) entry stating that Core Boost
      Technology is disabled due to a lack of an iLO Advanced License (531 - Core
      Boost Technology missing required iLO License) when using the Version 1.20
      System ROM. This issue does NOT occur with the Version 1.00 System ROM. Note
      that this IML entry is only valid for servers using the Intel Xeon Scalable
      6143 processor. If the message and IML entry are received with any other
      processor model installed, the message is erroneous and can be ignored without
      any negative impact to the system.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.26_11-14-2017
changelog:
  -     Added support for HPE 16GB NVDIMM-N Persistent Memory. Support for this
      feature also requires Innovation Firmware Version 0.1.3.2. This version of
      System ROM and Innovation Engine Firmware 0.1.3.2 are the minimum supported
      Firmware for this feature.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.26_11-14-2017
changelog:
  -     *Important Notes:**
      
      This revision of the System ROM enables flash support for Innovation Engine
      (IE) Firmware revision 0.1.4.4 and later. It must be installed prior to
      updating to IE FW 0.1.4.4. Attempting to update to IE FW 0.1.4.4 or later
      without this revision of the System ROM or later will result in the flash
      operation not occurring. This revision of the BIOS, along with IE FW 0.1.4.4
      and SPS FW 04.00.04.288, provide a solution to mitigate security vulnerability
      CVE-2017-5706 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5706)
      and CVE-2017-5709 (http://www.cve.mitre.org/cgi-
      bin/cvename.cgi?name=2017-5709) with Intel's SPS FW. It is anticipated that
      details regarding these security vulnerabilities will be published to these
      links on November 20,2017. These security vulnerabilities are not unique to
      HPE servers. Note that IE FW 0.1.4.4 must be installed prior to updating to
      SPS FW 04.00.04.288.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      This revision of the System ROM enables flash support for Innovation Engine
      (IE) Firmware revision 0.1.4.4 and later. It must be installed prior to
      updating to IE FW 0.1.4.4. Attempting to update to IE FW 0.1.4.4 or later
      without this revision of the System ROM or later will result in the flash
      operation not occurring. This revision of the BIOS, along with IE FW 0.1.4.4
      and SPS FW 04.00.04.288, provide a solution to mitigate security vulnerability
      CVE-2017-5706 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5706)
      and CVE-2017-5709 (http://www.cve.mitre.org/cgi-
      bin/cvename.cgi?name=2017-5709) with Intel's SPS FW. It is anticipated that
      details regarding these security vulnerabilities will be published to these
      links on November 20,2017. These security vulnerabilities are not unique to
      HPE servers. Note that IE FW 0.1.4.4 must be installed prior to updating to
      SPS FW 04.00.04.288.
      
      Addressed an issue where the High Performance Event Timer (HPET) may not
      function properly under an Operating System. This was typically seen under a
      Windows Operating System where the HPET was reported as not functioning
      properly in Windows Device Manager.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.28_12-11-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version.
      
      Addressed an issue where the system may experience an erroneous boot-time
      message and Integrated Management Log (IML) entry stating that Core Boost
      Technology is disabled due to a lack of an iLO Advanced License (531 - Core
      Boost Technology missing required iLO License) when using the Version 1.20
      System ROM. This issue does NOT occur with the Version 1.00 or Version 1.22
      System ROM. Note that this IML entry is only valid for servers using the Intel
      Xeon Scalable 6143 processor. If the message and IML entry are received with
      any other processor model installed, the message is erroneous and can be
      ignored without any negative impact to the system.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.36_02-14-2018
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the UEFI Boot Order would not get reset to a default
      value when loading a default configuration. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an issue where the High Performance Event Timer (HPET) may not
      function properly under an Operating System. This was typically seen under a
      Windows Operating System where the HPET was reported as not functioning
      properly in Windows Device Manager.
      
      Addressed an issue where the Embedded Serial Port option could not be properly
      configured through the RESTful Interface.
      
      Addressed an issue where the PCI Express I/O Proximity values were not
      properly allocated in the ACPI System Locality Information Table (SLIT). This
      change may help provide a performance benefit in applications and
      configurations that are sensitive to PCIe Device I/O NUMA awareness.
      
      Addressed a rare issue where the system may become unresponsive when a SAS
      drive was inserted with the HPE Smart Array S100i SR Gen10 SW RAID enabled.
      This issue does not impact systems configured in AHCI mode.
      
      Addressed an issue where the system may experience an erroneous boot-time
      message and Integrated Management Log (IML) entry stating that Core Boost
      Technology is disabled due to a lack of an iLO Advanced License (531 - Core
      Boost Technology missing required iLO License) when using the Version 1.20
      System ROM. This issue does NOT occur with the Version 1.00 or Version 1.22
      System ROM. Note that this IML entry is only valid for servers using the Intel
      Xeon Scalable 6143 processor. If the message and IML entry are received with
      any other processor model installed, the message is erroneous and can be
      ignored without any negative impact to the system.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-19-2017
changelog:
  -     Added support for the HPE Core Boost Technology. This feature requires HPE
      Innovation Engine Firmware 0.1.2.6 or later.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for LLC Dead Line Allocation. When running certain applications,
      modifying this setting from its default value may improve system performance.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for Stale A to S. When running certain applications, modifying this
      setting from its default value may improve system performance.
      
      Added support to detect and report unbalanced memory configurations that may
      result in non-optimal performance. Please consult the Memory Population
      Guidelines for more information on memory population rules and
      recommendations.
      
      Added a new Auto option for the XPT Prefetcher in the BIOS/Platform
      Configuration (RBSU) menu that will default the XPT prefetcher to disabled
      based on a current Intel sighting processor issue.  Enabling this option (via
      setting this option for Force Enable) may improve latency performance, but
      Intel has indicated rare stability issues may occur if XPT Prefetcher is
      enabled.
      
      Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated the system thermal logic to support the latest GPU adapters.
      
      Updated the RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the language translations (non-English modes) for System Utilities.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-19-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the Embedded UEFI Shell restclient utility would not
      properly configure attributes for Network TLS (HTTPS) support.
      
      Addressed an issue where the UEFI or Legacy Boot Order could still be modified
      after an incorrect Administrator Password was entered in the BIOS/Platform
      Configuration (RBSU) menus.
      
      Addressed an issue where the embedded AHCI SATA controller would not show up
      properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no
      drives were attached to the controller.
      
      Addressed an issue where saving a configuration setting from an optional
      device's configuration page in the System Utilities menu would not be saved
      properly.  This issue was seen with one Network Adapter card.
      
      Addressed an issue where the system ROM would not correctly report a
      configuration error for the HPE Smart Battery storage subsystem when more
      devices were installed than could be supported by the installed battery.
      
      Addressed an issue where a platform configured with direct attached NVMe hard
      drives may report the incorrect location (box and bay location) from the
      System Utilities page.
      
      Addressed an issue where the System Utilities menu may not show the proper
      name for an optional PCIe Adapter.
      
      Addressed an issue where the Integrated Lights Out (iLO) remote Console
      Keyboard and Mouse may not function properly when the system is configured for
      Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot
      Mode.
      
      Addressed an issue where the HPE Jitter Performance feature settings could not
      be properly modified from the Integrated Lights Out web interface.
      
      Addressed an issue where the system may report that the HPE Smart Battery is
      charging when in fact the battery has failed. It is recommended to flash to
      this system ROM if a system is reporting Smart Battery issues.
      
      Addressed an issue where the Trusted Platform Module (TPM) option for TPM
      Visibility could not be configured through the RESTful API.
      
      Addressed an issue where the system may become unresponsive when repeatedly
      typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.
      This issue does not impact systems in UEFI Boot Mode or a system once the
      system boots into an operating system.
      
      Addressed an issue where certain third party PCIe adapters, such as a Dialogic
      adapter, would not function properly due to the PCIe Maximum Payload size
      being incorrectly programmed.
      
      Addressed an issue where certain NVMe devices may not be detected when the x16
      slot PCIe Riser and three slot x8 riser are present in the server.
      
      Addressed an issue where a Network Boot option would still show an entry  in
      the Legacy Boot Order when Network Boot was disabled on the device from the
      BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not
      affect systems configured for UEFI Boot Mode.
      
      Addressed an issue where the system may become unresponsive when using the TAB
      key in the BIOS/Platform Configuration (RBSU) menus.
      
      Addressed an issue where the BIOS would not properly identify and halt a
      system from booting with an invalid DIMM configuration.
      
      Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy
      Efficient Turbo setting was "backwards".  When the configuration setting was
      set to enabled, the feature would actually be Disabled.  When configured to
      Disabled, the feature would actually be enabled.
      
      Addressed an issue where the server might lockup and display a red screen when
      trying to repair a failed RAID volume off of an S100i SW RAID controller.
      
      Addressed an issue where the RESTful API may report that BIOS settings were
      not applied properly even when they are properly configured.
      
      Addressed an issue where the system may become unresponsive during boot after
      a warm reset, typically seen with a blank screen, when a Trusted Platform
      Module (TPM) is installed.  If reboot issues are seen with systems containing
      an optional TPM, it is highly recommended the System ROM be enabled to this
      revision or later.
      
      Addressed an extremely rare issue where the system may incorrectly report a
      413 Innovation Engine Authentication Error on a server reboot.
      
      Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo
      disable functionality.
      
      Removed the Platform Configuration (RBSU) Option to enable or disable the
      Embedded Diagnostics.  Embedded Diagnostics is not supported on this server
      and the menu option should not have been available and was not functional.
      
      Removed Embedded Diagnostics support from System Utilities.
      
      Removed support for the chipset firmware based Trusted Platform Module (TPM)
      known as Intel Platform Trust Technology (Intel PTT). This feature is no
      longer supported due to stability issues and Intel recommends not supporting
      this feature. Users should instead install a discrete HPE TPM option for this
      support.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_05-06-2015
changelog:
  -     Added a Server Security BIOS/Platform Configuration (RBSU) option to Enable or
      Disable "Processor AES-NI Support". This option enables or disables the
      Advanced Encryption Standard Instruction Set. The option is enabled by default
      and was enabled automatically with previous revisions of the BIOS.
      
      Added support for UEFI iSCSI Software Initiator boot functionality. The iSCSI
      Software Initiator boot support can be enabled on any network card that is in
      Ethernet mode. The iSCSI network settings can be configured in the new System
      Utilities BIOS/Platform Configuration (RBSU) iSCSI Boot Configuration menu, as
      well as using the HP RESTful API HpiScsiSoftwareInititiator resource type.
      This option is only available in UEFI Boot Mode.
      
      Added a BIOS/Platform Configuration (RBSU) Network Option for VLAN
      Configuration. This option allows the user to configure Virtual LAN (VLAN)
      settings for all network devices present in the system. This option is only
      available in UEFI Boot Mode.
      
      Added a new System Utilities Embedded Applications Active Health System Log
      option. This option allows users to download Active Health System (AHS) Logs.
      
      Added support for additional Storage Options to BIOS/Platform Configuration
      (RBSU). These new options allow the user to configure the number of boot
      targets that are listed per storage controller in the UEFI Boot Order. This
      option can be used to limit the number of boot targets to simplify the UEFI
      boot order and decrease boot time. These options are only available in UEFI
      Boot Mode.
      
      Added pre-boot OHCI USB support. This will allow an optional PCIe USB
      controller, such as available on the Teradici PCoIP Zero Client card, to be
      functional in a pre-boot environment. This also adds support for booting from
      USB devices attached to optional PCIe OHCI USB controllers. Support for OHCI
      USB controllers should be available from operating system drivers when not in
      the pre-boot environment.
      
      Added support for a new partitions command in the Embedded UEFI Shell. This
      command can be used to view all available drive partitions.
      
      Added support for a new ahsdownload command in the Embedded UEFI Shell. This
      command can be used to download Active Health System (AHS) files.
      
      Added support for a new restclient command in the Embedded UEFI Shell. This
      command can be used to configure the server through the HP RESTful services.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the HPRESTful API support to report and set the default UEFI Boot
      Order settings using the HpServerBootOrder resource type.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API support for HpBios resource to rename "SecureBoot"
      property to "SecureBootStatus" to avoid conflict with the "SecureBoot"
      property in HpSecureBoot resource. This change will impact any scripts written
      with a dependency on the "SecureBoot" property in the HpBios resource.
      
      Updated the System Utilities BIOS/Platform Configuration (RBSU) Fibre
      Channel/FCoE Scan Policy option to default to Scan Configured Targets only.
      Previous revisions of the System ROM defaulted to scanning all targets.
      
      Enhanced the thermal solution to provide proper cooling for optional PCIe
      graphics and acceleration cards.
      
      Enhanced the System Utilities System Information and the Embedded UEFI Shell
      sysinfo command to provide additional details for the processor, memory, PCI
      subsections. In addition, added a new Firmware Information menu to System
      Information to provide a list of current firmware revisions for supported
      components.
      
      Reduced boot time when the Dynamic Smart Array B140i RAID is enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.60_01-04-2016
changelog:
  -     Added support for an optional Trusted Platform Module (TPM) 2.0.
      
      Added support to detect and log when memory performance may be degraded due to
      a high rate of correctable memory errors. When this condition is detected, a
      new Integrated Management Log (IML) message will be logged indicating a "High
      rate of corrected memory errors, performance may be degraded".
      
      Added support to the Embedded UEFI Shell to allow the user to export Secure
      Boot certificates to a file.
      
      Added support to automatically initialize the Trusted Platform Modules (TPM)
      nonvolatile storage when the TPM is first installed on a platform. This
      feature helps avoid issues where a TPM may be locked out from use to an
      operating system and requires the user to manually clear the TPM setting from
      the BIOS/Platform Configuration (RBSU) menus when first installed.
      
      Updated branding during the boot process and in the pre-boot System Utilities
      from HP to Hewlett Packard Enterprise. No branding changes were made that
      could impact software running on the system. Industry standard SMBIOS tables
      were NOT updated to reflect Hewlett Packard Enterprise branding.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Added support for the industry standard SMBIOS Type 2 baseboard record.
      
      Added support to the HP RESTful API to allow the user to configure the UEFI
      boot order when the system is configured for Legacy Boot Mode.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.60_01-04-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the user may not be able to properly download an
      Active Health Systems (AHS) file from System Utilities or the Embedded UEFI
      Shell when certain date ranges were used.
      
      Addressed an issue where a system configured with a Trusted Platform Module
      (TPM) may improperly measure an extra EV_SEPARATOR into the TPM PCR7.
      
      Addressed an issue where the Active Health System (AHS) file could not be
      downloaded to the embedded SD card from the Embedded UEFI Shell.
      
      Addressed issues with USB support in the pre-boot environment when the system
      is configured in Legacy Boot Mode. These issues did not affect systems
      configured in UEFI Boot Mode.
      
      Addressed an issue where certain optional PCIe video adapters would fail to
      work properly when using a Linux operating system.
      
      Addressed an issue where industry standard SMBIOS Type 9 entries for PCIe
      Slots attached to a not installed processor did not exist.
      
      Addressed an issue where the UEFI iSCSI Boot Configuration may not work
      properly when configuring these options through the HP RESTful Interface. This
      issue does not affect systems where the UEFI iSCSI Boot Configuration is
      configured through the System Utilities BIOS/Platform Configuration (RBSU).
      
      Addressed an issue where the drives attached to an HP Smart Array controller
      may not be detected on the first boot after switching from UEFI Boot Mode to
      Legacy Boot Mode.
      
      Addressed an issue where the PXE Boot Policy does not function properly when
      the Network VLAN Configuration option is enabled. When Network VLAN
      Configuration is enabled, the server would always attempt to boot both iPV4
      and iPV6 regardless of the PXE Boot Order Policy setting.
      
      Addressed an issue where the server would display a Red Screen error and
      become unresponsive when exiting the System Utilities Embedded User
      Diagnostics when configured for Legacy Boot Mode. This issue does not impact
      systems configured for UEFI Boot Mode.
      
      Addressed an issue where the HP ProLiant Dynamic Power Regulator would not
      function properly when configured for Slow Mode. In rare cases, this could
      cause the system to not optimally switch processor power states.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive from the Embedded UEFI Shell when interrupting the ping command
      via a CTRL-C key press.
      
      Addressed an issue where the system may report a 335-HP RESTful API error
      after setting the BIOS Administrator password through the HP RESTful API.
      
      Addressed an issue where the Date and Time may be set incorrectly when using
      the Date and Time option from the BIOS/Platform Configuration (RBSU) when the
      Daylight Savings Time option is enabled.
      
      Addressed an issue where the server may display a Red Screen error and become
      unresponsive during boot when more than 256 hard drives are attached to a
      storage controller. The UEFI BIOS will now limit the enumeration of bootable
      devices to 256 entries.
      
      Addressed an issue where video is not displayed when using the embedded video
      controller with certain newer monitors, such as the HP E190i, which do not
      properly operate in native resolutions such as 1280x1024.
      
      Addressed an issue with the incorrect version of the HpServerBootSettings
      schema in the HP RESTful API.
      
      Addressed an issue where the server could become unresponsive during boot or
      from the Embedded UEFI Shell when a Block I/O device such as a USB key or hard
      drive has a corrupt FAT32 file system.
      
      Addressed an issue where an erroneous 312 - HP Smart Battery error message
      would be displayed and logged to the Integrated Management Log (IML) on the
      first boot after the system battery was removed from the server.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the system may become unresponsive and experience a
      Machine Check Exception or NMI under heavy stress conditions when configured
      with Intel Xeon E5-4600 v3 processors and 64GB LRDIMMs in a 3 DIMM Per Channel
      configuration. This issue does not impact systems configured with other memory
      configuration including 64GB LRDIMM with less than 3 DIMMs Per Channel. This
      System ROM revision should be considered the minimum revision required for use
      with 64 GB LRDIMMs in systems with any memory channels containing 3 DIMMs.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016-2.1
changelog:
  -     Added support for Intel Xeon E5-4600 v4 series processors.
      
      Enhanced PCIe resource allocation so that systems configured with multiple
      PCIe expansion devices may in some cases no longer report a "276 Option Card
      Configuration Error" during system boot due to not having enough I/O resources
      to support what is requested by the installed devices. This BIOS revision
      allows a wider range of PCIe configurations that request large amounts of I/O
      to be configured properly.
      
      Updated the UEFI Secure Boot revocations list (DBX) with the latest copy from
      Microsoft.
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft. This includes the latest list of revoked
      certificates.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Increased the default timeout value of the iSCSI UEFI Software Initiator boot
      to 20 seconds. This may help resolve issues of intermittent connection drop
      during an iSCSI boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.30_09-12-2016
changelog:
  -     Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft. This includes the latest list of revoked
      certificates.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Added support HPE SmartMemory 128 GB LRDIMMs.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.30_12-25-2014
changelog:
  -     Added support for a Generic USB Boot entry in the UEFI Boot Order list. This
      new entry is used as a place holder for any USB device that is bootable in
      UEFI. The user can set the boot priority of this Generic USB Boot entry, and
      retain this priority for use with USB devices that might be installed in the
      future. Attempting to boot from the Generic USB Boot entry will result in
      attempting all UEFI bootable USB devices that are available in the system. The
      user can still control the priority of the boot entries of individual USB
      devices in the UEFI Boot Order list. This new Generic USB Boot entry will now
      be visible by default in the UEFI Boot Order after updating to this System ROM
      release. This new option is applicable only in UEFI Boot Mode and might be
      configured from the HP RESTful API or the System Utilities BIOS/Platform
      Configuration (RBSU). Note: The system will attempt to boot all UEFI bootable
      USB devices in the order of the Generic USB Boot entry even if installed
      individual USB devices are configured lower in the boot order.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) Fibre
      Channel/FCoE Scan Policy menu that allows the user to select how the UEFI BIOS
      will scan for valid Fibre Channel (or boot from SAN) boot targets. By default,
      the system will now only scan for Fibre Channel boot targets that are
      configured in each adapter. In the past, the system would scan for all Fibre
      Channel or FCoE available targets, potentially resulting in long boot times
      and large number of entries in the UEFI Boot Order list. The boot targets for
      adapters can be configured using the adapter specific menu in the System
      Utilities, System Configuration menu, or using management software such as HP
      Virtual Connect or HP OneView. This setting is applicable only in UEFI Boot
      Mode. A firmware update of the fibre channel controller might also be required
      to take full advantage of this feature.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) NUMA Group
      Size Optimizations menu that allows the user to select how the platform will
      report processor grouping to the operating system. For some applications which
      cannot optimally handle high logical processor counts that are optimally
      divided into smaller groups, it might be necessary to change the default
      setting to get optimal performance.
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) I/O Non-Posted
      Prefetching performance option that allows the user to configure how the
      chipset balances I/O traffic for PCI-e devices. Disabling this option has been
      shown to provide performance benefits in a very small subset of configurations
      including certain Infiniband configurations that require a balanced mix of
      read and write traffic as well as configurations with multiple x16 devices
      that utilize the max bandwidth of the PCI-e bus. Since disabling the option
      also has a negative impact on maximum I/O read bandwidth, the overwhelming
      majority of configurations will benefit from leaving this option at the
      default.
      
      Added support for Memory Mirroring Mode. This option can be selected from the
      Advanced Memory Protection Mode selection. This option provides enhanced
      memory availability and resiliency but requires additional memory be installed
      to achieve the same amount of memory available to the operating system.
      
      Added support for loading the Embedded UEFI Shell Auto-Startup script from the
      network in addition to physical/virtual media. The URL describing the network
      (HTTP or FTP) location of the startup script can be configured in the System
      Utilities /Platform Configuration (RBSU), under the Embedded Shell menu. This
      allows for using the Embedded UEFI Shell as a scriptable deployment
      environment without the need for physical or virtual media (on a bare metal
      system).
      
      Added support to Standard Format Output (SFO) to the SysConfig command in the
      Embedded UEFI Shell. This allows for easier parsing of the command output
      using Shell scripts.
      
      Added support for boot from URL (HTTP or FTP) functionality in UEFI Boot Mode.
      The network settings (DHCP or static IP) and boot file URL can be configured
      in the new System Utilities BIOS/Platform Configuration (RBSU) Pre-Boot
      Network settings menu. The file can either be a UEFI Network Boot Program
      (NBP), or an ISO image containing a UEFI bootable OS image. The Boot from ISO
      support is currently limited to operating systems that have a self contained
      OS image (such as WinPE, mini Linux, or VMware ESX installer). Booting Windows
      or Linux OS installation media is currently not supported.
      
      Added support for a webclient command in the Embedded UEFI Shell. The command
      can be used to download files from HTTP and FTP servers. It can also be used
      to download ISO CD/DVD images and mount them in memory as RAM disks.
      
      Added support for an FTP command in the Embedded UEFI Shell. The command can
      be used to download and upload files to/from FTP servers.
      
      Added support for a Compress command in the Embedded UEFI Shell. The command
      can be used to compress and decompress ZIP files.
      
      Added support for a SecBoot command in the Embedded UEFI Shell. The command
      can be used to display the Secure Boot keys and certificates.
      
      Enhanced the RamDisk command in the Embedded UEFI Shell to support FAT32 RAM
      disks, increasing the disk size limit from 512 MB to 2GB.
      
      Added support for the HP Dual 8GB MicroSD EM USB Kit. This device can be
      plugged into the internal USB port on the server to allow a mirrored MicroSD
      card solution.
      
      Added support to configure the BIOS Serial Console Baud Rate to 38400 from the
      System Utilities BIOS/Platform Configuration (RBSU).
      
      Added a new System Utilities BIOS/Platform Configuration (RBSU) Internal SD
      Card Slot menu located in USB Options that allows the user to disable boot
      from the embedded SD card.
      
      Added support for Intel Trusted eXecution Technology (TXT).
      
      Updated OpenSSL support to version 0.9.8zb to address potential issues that
      might impact the UEFI Secure Boot support.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the HP RESTful API HpBiosAttributeRegistrySchema to version 1.2.0,
      adding support for BIOS Attributes of type "Password". Also added a new
      GrayOut property that can be used to describe some dependency scenarios. Also
      updated enumDescriptions of all enum definitions in the schema.
      
      Updated the HP RESTful API HpBios, HpServerBootSettings, HpBiosMappsings
      schemas to version 1.1.0. Added support for self-links in these resources.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated help documentation for System Utilities and the Embedded UEFI Shell.
      
      Increased timeout values in Embedded UEFI Shell IfConfig command to reduce the
      chances of network DHCP configuration failing due to timeouts caused by delays
      on the network or slow response when trying to contact the DHCP server.
      
      Enhanced the UEFI Exception handler to provide extended debug and trace
      information when in a pre-OS environment.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-06-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-06-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-06-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed. The actual
      BIOS included with this revision is the same as ver. 1.32_03-06-2015. It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-06-2015. Please refer to the
      Customer Advisory at [http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533 ](http://h20564.www2.hp.com/portal/site/hpsc/p
      ublic/kb/docDisplay/?docId=emr_na-c04634533 for additional details.)for
      additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_05-05-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Address an issue where a system that experiences an HPE Smart Storage Battery
      failure may become unresponsive when configured with iLO Firmware 2.40.Note
      there is an issue where a system configured with Integrated Lights-Out (iLO)
      Firmware version 2.40 may experience an intermittent and false HPE Smart
      Storage Battery failure, logged in the Integrated Management Log (IML).Due
      to the BIOS issue addressed in this revision, the false HPE Smart Storage
      Battery failure may result in the system becoming unresponsive.This issue
      does not impact systems that are not configured with an HPE Smart Storage
      Battery or systems configured with iLO Firmware 2.30 or earlier.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) USB Boot Options setting may not properly allow the server to boot from
      the internal SD card before a USB key when SD is higher in the priority list.
      This issue only affects servers configured in Legacy Boot Mode.
      
      Addressed an issue where the ambient temperature reported by the system during
      server boot may report incorrectly. This issue also requires an iLO firmware
      version update to a revision later than 2.4x which will be released later this
      year. This issue has no impact on the thermal operation of the server and is
      simply an issue with the temperature displayed during boot. While updating to
      this revision of the BIOS will not address this issue unless the iLO FW
      revision is later than 2.4x, there are no issues caused by updating the BIOS
      without updating iLO FW.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots. This could cause
      such issues as an inability to boot using the PCIe adapter. This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the server health LED may remain set in a degraded or
      failed state after an error event was resolved during server operation.
      Previously, a server reset may have been needed to clear the health LED event.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) option for Embedded UEFI Shell Auto Startup Script Network Location
      does not accept an NSH file name containing upper case characters.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may become unresponsive during boot when
      configured with a HPE Dual microSD device when one of the microSD devices is
      failed or missing.
      
      Addressed an issue where the server may assign incorrect ACPI NUMA proximity
      allocations for servers configured with two or more processors and with memory
      only attached to a single processor socket potentially leading to non optimal
      performance. This issue does not impact servers with memory configured on
      multiple processors.
      
      Addressed an issue where the Automatic Server Recovery (ASR) setting may not
      be configured properly through the HP RESTful API.
      
      Addressed an issue where the internal SD card would remain active after the
      user has disabled the SD slot from System Utilities BIOS/Platform
      Configuration (RBSU) option. This issue only effects systems configured in
      Legacy Boot Mode.
      
      Addressed an issue where the server may become unresponsive when using the
      PING command from the Embedded UEFI Shell.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may fail to boot from existing UEFI iSCSI
      Software Initiator boot options if the user changed the iSCSI Target IP
      address.
      
      Addressed an issue where the system may fail to boot from UEFI iSCSI Software
      Initiator boot options that has iSCSI Initiator or Target configured using
      static IPv6 addresses.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot option IPv6
      address cannot be configured using the HPE RESTful API.
      
      Addressed an issue that may result in losing the existing UEFI iSCSI Software
      Initiator boot options if any of the connection parameters (LUN, Remote Port,
      IP address, login credentials) change.
      
      Addressed an issue in reporting the incorrect PCIe slot number in the error
      messages of failed iSCSI boot attempts.
      
      Addressed an issue of iSCSI boot configuration options not being available
      from the HPE RESTful API when there are no network adapters in the system.
      
      Addressed an extremely rare issue where the server may become unresponsive due
      to a Non Maskable Interrupt (NMI) when performing a shutdown or startup from
      an Operating System.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017-2.1
changelog:
  -     *Important Notes:**
      
      Version 2.40_02-17-2017 (B) contains updates to the component packaging and is
      functionally equivalent to version 2.40_02-17-2017.  It is not necessary to
      upgrade with Revision B if the system ROM was previously upgraded to version
      2.40_02-17-2017.
      
      SUM version 7.6.0  or earlier should be used for deployment of 2.40_02-17-2017
      (B).
      
      **Firmware Dependencies:**
      
      None  
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     *Important Notes:**
      
      This System ROM revision replaces the 2.50 revision. An issue was found with
      the 2.50 revision of the System ROM that may result in a system hang during
      boot with a messaging indicating "Memory Initialization - complete" with
      certain memory configurations. The 2.50 revision of the System ROM has been
      removed from the HPE Support Site. It is highly recommended that any customers
      using the 2.50 revision of the System ROM upgrade to the 2.52 revision or
      later.  
      
      
      **Firmware Dependencies:**
      
      None
      
      
      
      **Problems Fixed:**
      
      Addressed an issue where Processor Core Disable may not function properly,
      such as disabling the wrong number of cores, when Intel Xeon E5 v4 processors
      are installed in the system. This issue does not impact systems configured
      with Intel Xeon E5 v3 processors.
      
      
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.54_12-07-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.56_01-22-2018
changelog:
  -     *Important Notes:**
      
      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.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-05-2015
changelog:
  -     Enhanced the thermal solution to provide proper cooling for optional PCIe
      graphics and acceleration cards.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-05-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-05-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed. The actual
      BIOS included with this revision is the same as ver. 1.32_03-05-2015. It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-05-2015. Please refer to the
      Customer Advisory at [http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533 ](http://h20564.www2.hp.com/portal/site/hpsc/p
      ublic/kb/docDisplay/?docId=emr_na-c04634533 for additional details.)for
      additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.52_11-10-2015
changelog:
  -     Added support for the NVIDIA M60 GPU.
      
      Added support to configure the system to bifurcate PCIe Slot 1 on the DL360
      Gen9 or PCIe Slot 2 on the DL380 Gen9.
      
      Added support for the latest Intel Trusted Execution Technology (TXT)
      Authenticated Code Module (ACM) and Secure Initialization (SINIT).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.52_11-10-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system configured with a Trusted Platform Module
      (TPM) may improperly measure an extra EV_SEPARATOR into the TPM PCR7.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots.  This could cause
      such issues as an inability to boot using the PCIe adapter.  This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.00_12-27-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the user may not be able to properly download an
      Active Health Systems (AHS) file from System Utilities or the Embedded UEFI
      Shell when certain date ranges were used.
      
      Addressed an issue where the Active Health System (AHS) file could not be
      downloaded to the embedded SD card from the Embedded UEFI Shell.
      
      Addressed issues with USB support in the pre-boot environment when the system
      is configured in Legacy Boot Mode. These issues did not affect systems
      configured in UEFI Boot Mode.
      
      Addressed an issue where certain optional PCIe video adapters would fail to
      work properly when using a Linux operating system.
      
      Addressed an issue where industry standard SMBIOS Type 9 entries for PCIe
      Slots attached to a not installed processor did not exist.
      
      Addressed an issue where the UEFI iSCSI Boot Configuration may not work
      properly when configuring these options through the HP RESTful Interface. This
      issue does not affect systems where the UEFI iSCSI Boot Configuration is
      configured through the System Utilities BIOS/Platform Configuration (RBSU).
      
      Addressed an issue where the drives attached to an HP Smart Array controller
      may not be detected on the first boot after switching from UEFI Boot Mode to
      Legacy Boot Mode.
      
      Addressed an issue where the PXE Boot Policy does not function properly when
      the Network VLAN Configuration option is enabled. When Network VLAN
      Configuration is enabled, the server would always attempt to boot both iPV4
      and iPV6 regardless of the PXE Boot Order Policy setting.
      
      Addressed an issue where the server would display a Red Screen error and
      become unresponsive when exiting the System Utilities Embedded User
      Diagnostics when configured for Legacy Boot Mode. This issue does not impact
      systems configured for UEFI Boot Mode.
      
      Addressed an issue where the HP ProLiant Dynamic Power Regulator would not
      function properly when configured for Slow Mode. In rare cases, this could
      cause the system to not optimally switch processor power states.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive from the Embedded UEFI Shell when interrupting the ping command
      via a CTRL-C key press.
      
      Addressed an issue where the system may report a 335-HP RESTful API error
      after setting the BIOS Administrator password through the HP RESTful API.
      
      Addressed an issue where the Date and Time may be set incorrectly when using
      the Date and Time option from the BIOS/Platform Configuration (RBSU) when the
      Daylight Savings Time option is enabled.
      
      Addressed an issue where the server may display a Red Screen error and become
      unresponsive during boot when more than 256 hard drives are attached to a
      storage controller. The UEFI BIOS will now limit the enumeration of bootable
      devices to 256 entries.
      
      Addressed an issue where video is not displayed when using the embedded video
      controller with certain newer monitors, such as the HP E190i, which do not
      properly operate in native resolutions such as 1280x1024.
      
      Addressed an issue with the incorrect version of the HpServerBootSettings
      schema in the HP RESTful API.
      
      Addressed an issue where the server could become unresponsive during boot or
      from the Embedded UEFI Shell when a Block I/O device such as a USB key or hard
      drive has a corrupt FAT32 file system.
      
      Addressed an issue where an erroneous 312 - HP Smart Battery error message
      would be displayed and logged to the Integrated Management Log (IML) on the
      first boot after the system battery was removed from the server.
      
      Addressed an issue where the system may become unresponsive and experience a
      Machine Check Exception or NMI under heavy stress conditions when configured
      with Intel Xeon E5-2600 v3 processors and 64GB LRDIMMs in a 3 DIMM Per Channel
      configuration. This issue does not impact systems configured with other memory
      configuration including 64GB LRDIMM with less than 3 DIMMs Per Channel. This
      System ROM revision should be considered the minimum revision required for use
      with 64 GB LRDIMMs in systems with any memory channels containing 3 DIMMs.
      
      Addressed an issue where the system may display a Red Screen error and become
      unresponsive during boot when the Embedded User Partition or Virtual Install
      Disk are enabled or if a USB storage device is installed when the server is
      configured for Legacy Boot Mode. This issue does not impact systems configured
      for UEFI Boot Mode.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_06-02-2016
changelog:
  -     Added support for Intel Xeon E5-1600 v4 series processors.
      
      Enhanced PCIe resource allocation so that systems configured with multiple
      PCIe expansion devices may in some cases no longer report a "276 Option Card
      Configuration Error" during system boot due to not having enough I/O resources
      to support what is requested by the installed devices.  This BIOS revision
      allows a wider range of PCIe configurations that request large amounts of I/O
      to be configured properly.
      
      Updated to the latest support modules for Intel Trusted eXecution Technology
      (TXT) including the Intel Authenticated Code Module (ACM) and Intel Secure
      Initialization (SINIT) module.
      
      Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the UEFI Secure Boot Key Database revocations list (DBX) with the
      latest version from Microsoft.  This includes the latest list of revoked
      certificates.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Increased the default timeout value of the iSCSI UEFI Software Initiator boot
      to 20 seconds. This may help resolve issues of intermittent connection drop
      during an iSCSI boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.20_06-02-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system that experiences an HPE Smart Storage
      Battery failure may become unresponsive when configured with iLO Firmware
      2.40.  Note there is an issue where a system configured with Integrated
      Lights-Out (iLO) Firmware version 2.40 may experience an intermittent and
      false HPE Smart Storage Battery failure, logged in the Integrated Management
      Log (IML).  Due to the BIOS issue addressed in this revision, the false HPE
      Smart Storage Battery failure may result in the system becoming unresponsive.
      This issue does not impact systems that are not configured with an HPE Smart
      Storage Battery or systems configured with iLO Firmware 2.30 or earlier.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) USB Boot Options setting may not properly allow the server to boot from
      the internal SD card before a USB key when SD is higher in the priority list.
      This issue only affects servers configured in Legacy Boot Mode.
      
      Addressed an issue where the ambient temperature reported by the system during
      server boot may report incorrectly. This issue also requires an iLO firmware
      version update to a revision later than 2.4x which will be released later this
      year.  This issue has no impact on the thermal operation of the server and is
      simply an issue with the temperature displayed during boot.  While updating to
      this revision of the BIOS will not address this issue unless the iLO FW
      revision is later than 2.4x, there are no issues caused by updating the BIOS
      without updating iLO FW.
      
      Addressed an issue where the UEFI or Legacy Option ROM for a PCIe adapter may
      not be properly executed when installed in certain slots.  This could cause
      such issues as an inability to boot using the PCIe adapter.  This issue was
      seen with a Brocade network adapter but could be seen with other adapters.
      
      Addressed an issue where the server health LED may remain set in a degraded or
      failed state after an error event was resolved during server operation.
      Previously, a server reset may have been needed to clear the health LED event.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) option for Embedded UEFI Shell Auto Startup Script Network Location
      does not accept an NSH file name containing upper case characters.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may become unresponsive during boot when
      configured with a HPE Dual microSD device when one of the microSD devices is
      failed or missing.
      
      Addressed an issue where the server may assign incorrect ACPI NUMA proximity
      allocations for servers configured with two or more processors and with memory
      only attached to a single processor socket potentially leading to non-optimal
      performance. This issue does not impact servers with memory configured on
      multiple processors.
      
      Addressed an issue where the Automatic Server Recovery (ASR) setting may not
      be configured properly through the HP RESTful API.
      
      Addressed an issue where the internal SD card would remain active after the
      user has disabled the SD slot from System Utilities BIOS/Platform
      Configuration (RBSU) option. This issue only affects systems configured in
      Legacy Boot Mode.
      
      Addressed an issue where the server may become unresponsive when using the
      PING command from the Embedded UEFI Shell.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot options may
      become invalid if the DHCP server provides a new IP Address to a previously
      configured iSCSI boot option.
      
      Addressed an issue where the system may fail to boot from existing UEFI iSCSI
      Software Initiator boot options if the user changed the iSCSI Target IP
      address.
      
      Addressed an issue where the system may fail to boot from UEFI iSCSI Software
      Initiator boot options that has iSCSI Initiator or Target configured using
      static IPv6 addresses.
      
      Addressed an issue where the UEFI iSCSI Software Initiator boot option IPv6
      address cannot be configured using the HP RESTful API.
      
      Addressed an issue that may result in losing the existing UEFI iSCSI Software
      Initiator boot options if any of the connection parameters (LUN, Remote Port,
      IP address, login credentials) change.
      
      Addressed an issue in reporting the incorrect PCIe slot number in the error
      messages of failed iSCSI boot attempts.
      
      Addressed an issue of iSCSI boot configuration options not being available
      from the HP RESTful API when there are no network adapters in the system.
      
      Addressed an extremely rare issue where the server may become unresponsive due
      to a Non Maskable Interrupt (NMI) when performing a shutdown or startup from
      an Operating System.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.22_07-18-2016
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system that experiences an HPE Smart Storage
      Battery failure may become unresponsive when configured with iLO Firmware
      2.40.  Note there is an issue where a system configured with Integrated
      Lights-Out (iLO) Firmware version 2.40 may experience an intermittent and
      false HPE Smart Storage Battery failure, logged in the Integrated Management
      Log (IML).  Due to the BIOS issue addressed in this revision, the false HPE
      Smart Storage Battery failure may result in the system becoming unresponsive.
      This issue does not impact systems that are not configured with an HPE Smart
      Storage Battery or systems configured with iLO Firmware 2.30 or earlier. The
      original version of the release notes for the v2.20 System ROM inadvertently
      indicated that this issue was addressed when it was not.  
      
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.42_04-25-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      Added thermal support for the latest PCIe expansion cards.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     Added support for Trusted Platform Module (TPM) 2.0 Firmware flash updates.
      For systems configured with the optional TPM 2.0 device, this is the minimum
      revision of the System ROM required to update TPM firmware.
      
      Updated the HPE RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the system thermal logic to support the NIVIDIA P4000 GPGPU.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-05-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-05-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed.  The actual
      BIOS included with this revision is the same as ver. 1.32_03-05-2015.  It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-05-2015. Please refer to the
      Customer Advisory at <http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533> for additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     Added support for Trusted Platform Module (TPM) 2.0 Firmware flash updates.
      For systems configured with the optional TPM 2.0 device, this is the minimum
      revision of the System ROM required to update TPM firmware.
      
      Updated the HPE RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Enhanced the system thermals to provide improved acoustics when the server is
      configured with no hard drives attached to the chipset SATA Controller.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-07-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      Addressed an issue where the system may become unresponsive or power off under
      certain conditions including high system load. When this error occurs, a
      Server Critical Fault (Service Information: Runtime Fault, Memory) or Server
      Critical Fault (Service Information: Runtime Fault, Processor) message is
      logged in the Integrated Management Log (IML).
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-07-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-07-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed.  The actual
      BIOS included with this revision is the same as ver. 1.32_03-07-2015.  It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-07-2015. Please refer to the
      Customer Advisory at <http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533> for additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      Addressed an issue where the system may become unresponsive or power off under
      certain conditions including high system load. When this error occurs, a
      Server Critical Fault (Service Information: Runtime Fault, Memory) or Server
      Critical Fault (Service Information: Runtime Fault, Processor) message is
      logged in the Integrated Management Log (IML).
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_05-06-2015
changelog:
  -     Added a Server Security BIOS/Platform Configuration (RBSU) option to Enable or
      Disable "Processor AES-NI Support". This option enables or disables the
      Advanced Encryption Standard Instruction Set. The option is enabled by default
      and was enabled automatically with previous revisions of the BIOS.
      
      Added support for UEFI iSCSI Software Initiator boot functionality. The iSCSI
      Software Initiator boot support can be enabled on any network card that is in
      Ethernet mode. The iSCSI network settings can be configured in the new System
      Utilities BIOS/Platform Configuration (RBSU) iSCSI Boot Configuration menu, as
      well as using the HP RESTful API HpiScsiSoftwareInititiator resource type.
      This option is only available in UEFI Boot Mode.
      
      Added a BIOS/Platform Configuration (RBSU) Network Option for VLAN
      Configuration. This option allows the user to configure Virtual LAN (VLAN)
      settings for all network devices present in the system. This option is only
      available in UEFI Boot Mode.
      
      Added a new System Utilities Embedded Applications Active Health System Log
      option. This option allows users to download Active Health System (AHS) Logs.
      
      Added support for additional Storage Options to BIOS/Platform Configuration
      (RBSU). These new options allow the user to configure the number of boot
      targets that are listed per storage controller in the UEFI Boot Order. This
      option can be used to limit the number of boot targets to simplify the UEFI
      boot order and decrease boot time. These options are only available in UEFI
      Boot Mode.
      
      Added pre-boot OHCI USB support. This will allow an optional PCIe USB
      controller, such as available on the Teradici PCoIP Zero Client card, to be
      functional in a pre-boot environment. This also adds support for booting from
      USB devices attached to optional PCIe OHCI USB controllers. Support for OHCI
      USB controllers should be available from operating system drivers when not in
      the pre-boot environment.
      
      Added support for a new partitions command in the Embedded UEFI Shell. This
      command can be used to view all available drive partitions.
      
      Added support for a new ahsdownload command in the Embedded UEFI Shell. This
      command can be used to download Active Health System (AHS) files.
      
      Added support for a new restclient command in the Embedded UEFI Shell. This
      command can be used to configure the server through the HP RESTful services.
      
      Updated the HP RESTful API HP BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the HPRESTful API support to report and set the default UEFI Boot
      Order settings using the HpServerBootOrder resource type.
      
      Updated the language translations (non-English modes) for System Utilities.
      
      Updated the HP RESTful API support for HpBios resource to rename "SecureBoot"
      property to "SecureBootStatus" to avoid conflict with the "SecureBoot"
      property in HpSecureBoot resource. This change will impact any scripts written
      with a dependency on the "SecureBoot" property in the HpBios resource.
      
      Updated the System Utilities BIOS/Platform Configuration (RBSU) Fibre
      Channel/FCoE Scan Policy option to default to Scan Configured Targets only.
      Previous revisions of the System ROM defaulted to scanning all targets.
      
      Enhanced the thermal solution to provide proper cooling for optional PCIe
      graphics and acceleration cards.
      
      Enhanced the System Utilities System Information and the Embedded UEFI Shell
      sysinfo command to provide additional details for the processor, memory, PCI
      subsections. In addition, added a new Firmware Information menu to System
      Information to provide a list of current firmware revisions for supported
      components.
      
      Reduced boot time when the Dynamic Smart Array B140i RAID is enabled.
      
      Added support for the new HP PCIe x16, FlexibleLOM x8 Riser (HP Part Number
      804165-B21).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_05-06-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the platform may become unresponsive during system
      boot when the server is configured for Legacy Boot Mode and the USB Boot
      Support has been disabled.
      
      Addressed an issue where the Intel NIC DMA Channels (IOAT) option could not be
      properly be configured from the Embedded UEFI Shell via the Sysconfig command.
      
      Addressed an issue where the +/- keys in the BIOS/Platform Configuration
      (RBSU) Boot Options menu were not functioning properly when configuring the
      server through a BIOS Serial Console Session.
      
      Addressed an issue where the fwupdate Embedded UEFI Shell command and the
      Firmware Update pre-boot application could hang during a firmware update and
      not successfully flash the device.
      
      Addressed an issue where the server may fail to boot properly to a Windows
      Deployment Server (WDS) when configured for IPv6 network boot mode.
      
      Addressed an issue where an optional PCIe adapter's legacy Expansion ROM may
      not run properly or the Expansion ROM's Setup Utility may not run properly
      when the server is configured for Legacy Boot Mode. This issue was seen with a
      Seagate storage adapter but may impact other devices.
      
      Addressed an issue where the Administrator Password would not be properly
      configured from the Embedded UEFI Shell Sysconfig command.
      
      Addressed an issue where a system could become unresponsive when booting to
      Linux Operating when serial output was enabled from the operating system and
      the iLO Virtual Serial Port was the only enabled UART.
      
      Addressed various issues with webclient and ftp commands in the Embedded UEFI
      Shell.
      
      Addressed an issue in which an Interphase audio streaming PCI-express
      expansion card may not achieve optimal performance resulting in dropped
      packets when streaming data. A similar issue could be seen with other PCI-
      express expansion cards implemented with a PCI device behind a PLX PCIe-to-PCI
      bridge. This type of PCI-express card implementation is more common with older
      PCI-express expansion cards.
      
      Addressed an issue where the system may experience a Linux kernel panic when
      booting from a SATA optical drive attached to the embedded SATA controller
      when the SATA controller is configured for Dynamic Smart Array B140i support.
      
      Addressed an issue where the system health LED would remain blinking RED
      (indicating a failed state) due to a power supply failure after the power
      supply had been replaced. Once the power supply is replaced, the system health
      LED should have returned to the blinking GREEN state. With previous revisions
      of the System ROM, the system health LED would not return to GREEN until after
      a reboot when a failed power supply is replaced.
      
      Addressed an issue where the system health LED would remain blinking AMBER
      (indicating a degraded state) due to an installed power supply not being
      plugged in after the power supply had been plugged in. Once the power supply
      is plugged in, the system health LED should have returned to the blinking
      GREEN state. With previous revisions of the System ROM, the system health LED
      would not return to GREEN until after a reboot when an unplugged power supply
      is plugged in.
      
      Addressed an issue where a system may become unresponsive when launching a
      guest operating system under a Hypervisor operating system such as Citrix or
      VMware when VT-d is enabled. This issue is NOT unique to HP servers.
      
      Addressed a possible issue where the platform may become unresponsive during
      POST when the user selects the Simplified Chinese language in System
      Utilities.
      
      Addressed an issue where the system does not report the condition where all
      installed power supplies are not of the same type.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the nodes primary NIC MAC address may not be properly
      reported to the enclosure chassis manager.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017-2.1
changelog:
  -     *Important Notes:**
      
      Version 2.40_02-17-2017 (B) contains updates to the component packaging and is
      functionally equivalent to version 2.40_02-17-2017.  It is not necessary to
      upgrade with Revision B if the system ROM was previously upgraded to version
      2.40_02-17-2017.
      
      SUM version 7.6.0  or earlier should be used for deployment of 2.40_02-17-2017
      (B).
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the nodes primary NIC MAC address may not be properly
      reported to the enclosure chassis manager.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-05-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-05-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed. The actual
      BIOS included with this revision is the same as ver. 1.32_03-05-2015. It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-05-2015. Please refer to the
      Customer Advisory at [http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533 ](http://h20564.www2.hp.com/portal/site/hpsc/p
      ublic/kb/docDisplay/?docId=emr_na-c04634533)for additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.40_02-17-2017-2.1
changelog:
  -     *Important Notes:**
      
      Version 2.40_02-17-2017 (B) contains updates to the component packaging and is
      functionally equivalent to version 2.40_02-17-2017.  It is not necessary to
      upgrade with Revision B if the system ROM was previously upgraded to version
      2.40_02-17-2017.
      
      SUM version 7.6.0  or earlier should be used for deployment of 2.40_02-17-2017
      (B).
      
      **Firmware Dependencies:**
      
      None  
      
      **Problems Fixed:**
      
      Addressed an issue where the system may become unresponsive during system boot
      when a third party USB 3.0 XHCI adapter card is installed in the server.
      
      Addressed an issue where the system may properly indicate that a DIMM has
      experienced a high rate of corrected memory errors in the Integrated
      Management Log (IML), but the DIMM's status may incorrectly be reported in the
      iLO GUI as healthy. The iLO GUI will now report the DIMM's status as degraded.
      
      Addressed an issue where the nodes primary NIC MAC address may not be properly
      reported to the enclosure chassis manager.
      
      Addressed an issue where the system may become unresponsive during system boot
      when a USB-based UPS is attached to the server USB ports. This issue only
      impacted a system when configured for legacy boot mode.
      
      Addressed an issue where the system may not properly report and log errors to
      the Integrated Management Log (IML) detected on the optional HPE Dual SD Card
      option. This issue only impacted logging when the system performed a warm
      reset.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.32_03-05-2015-2.1
changelog:
  -     *Important Notes:**
      
      Ver. 1.32_03-05-2015 (B) addresses a flashing issue that only impacted servers
      which shipped from HP with a Windows operating system installed. The actual
      BIOS included with this revision is the same as ver. 1.32_03-05-2015. It is
      not necessary to upgrade with Revision B if the previous Revision was used to
      upgrade the system ROM to version 1.32_03-05-2015. Please refer to the
      Customer Advisory at [http://h20564.www2.hp.com/portal/site/hpsc/public/kb/doc
      Display/?docId=emr_na-c04634533 ](http://h20564.www2.hp.com/portal/site/hpsc/p
      ublic/kb/docDisplay/?docId=emr_na-c04634533 for additional details)for
      additional details.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience a high rate of corrected
      memory errors that result in significant performance degradation. While this
      issue is rare, once it occurs, the server will continue to experience a high
      rate of corrected errors until the server is rebooted. This issue is NOT
      unique to HP servers. HP recommends that users experiencing a performance
      issue or experiencing corrected memory error threshold events update to this
      revision of the System ROM before replacing any hardware components.
      
      Addressed an issue where a system running a hypervisor-based operating system
      may become unresponsive when a guest operating system executes certain debug
      commands.
      
      Addressed an issue where a system configured for UEFI Boot Mode with multiple
      GPUs may not be able to properly start the GPUs under the operating system.
      This could result in one or more of the GPUs experiencing a "Yellow Bang"
      under a Microsoft operating system. This issue does not impact systems
      configured in Legacy Boot Mode.
      
      Addressed an extremely rare issue where the system may experience a "266-Non-
      Volatile Memory Corruption Detected" message and Integrated Management Log
      (IML) event after being powered down from a momentary power button press. This
      issue would only occur in a pre-operating system environment such as in the
      UEFI Shell.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.52_10-25-2017
changelog:
  -     Added support for Trusted Platform Module (TPM) 2.0 Firmware flash updates.
      For systems configured with the optional TPM 2.0 device, this is the minimum
      revision of the System ROM required to update TPM firmware.
      
      Updated the HPE RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.50_07-20-2015
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the server may experience Machine Check Exceptions or
      unexpected reboots under heavy load and high temperature. This issue is NOT
      unique to HP servers. HP recommends that users experiencing these issues
      update to this revision of the System ROM before replacing any hardware
      components.
      
      Addressed an issue where the System Utilities BIOS/Platform Configuration
      (RBSU) Dynamic Power Savings Mode Response Option when configured for Slow
      Mode may not efficiently switch processor performance modes resulting in lower
      than expected performance.
      
      Addressed an issue where the system may not properly respond to error events
      from devices attached to certain PCI Express root ports.
      
      Addressed an issue where the Channel Interleaving option in the ROM Based
      Setup Utility (RBSU) did not function when configured for Disabled. Even when
      this option was configured to Disabled, Channel Interleaving would be enabled.
      
      Addressed an issue where a server configured for UEFI boot mode may become
      unresponsive during boot when configured with an optional graphics controller
      that does not support UEFI boot mode. This issue does not affect systems
      configured in Legacy Boot Mode.
      
      Addressed an issue in the HP RESTful API data model with the reporting of
      "EmbSasXBoot" and "SlotXStorageBoot" properties in the HpBiosMappings
      resource. The properties were not associated with the correct PCI devices for
      the embedded and optional storage controllers.
      
      Addressed an issue where the server may become unresponsive during boot when
      configured with a very large number of disks such as fibre adapters.
      
      Addressed an issue in the HP RESTful API BIOS support that resulted in
      internal HTTP sessions between BIOS and iLO left open during boot. This can
      result in the iLO Event Log indicating multiple events for HTTP session
      logins.
      
      Addressed an issue where the system would become unresponsive during boot and
      display a NMI error when configured with an optional PCI Express device
      supporting older versions of the PCI Express specification.
      
      Addressed an issue where the system would not reset configuration settings to
      defaults when using the Embedded UEFI Shell Sysconfig -d command.
      
      Addressed an issue where the HP RESTful API and Embedded UEFI Shell
      description of the storage controller may begin with an instance of 2 instead
      of 1 when only one storage controller was installed in the server.
      
      Addressed an issue where the system may fail to boot a Linux Operating System
      when using serial console redirection when the physical Serial Port is
      disabled and the iLO Virtual Serial Port is enabled.
      
      Addressed an issue where a system configured for Legacy Boot Mode may become
      unresponsive during boot and display a NMI error when the Virtual Install Disk
      is enabled.
      
      Addressed an issue where a system configured for UEFI Boot Mode with an
      optional PCI Express based USB 3.0 controller installed may not be able to
      properly load the USB driver under the operating system. This issue does not
      affect systems configured in Legacy Boot Mode.
      
      Addressed an issue where thermal and inventory data may not be available for
      all DIMMs in the system when certain processors, such as the Xeon E5-2667 v3,
      are installed in the server.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_08-08-2017
changelog:
  -     Added support for the HPE Dynamic SmartArray B140i Option in the BIOS/Platform
      Configuration (RBSU) Configuration Menu.
      
      Added support for Cluster Model and On-Package High-Bandwidth Memory Cache
      Size menus to the Memory Options in the BIOS/Platform Configuration (RBSU)
      Configuration Menu.
      
      Added support for Intel Xeon Phi processors with Integrated Intel Omni-Path
      Fabric.
      
      Added support for XL2x260w Server.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.40_08-08-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an extremely rare issue where the system may become unresponsive on
      a subsequent boot after an uncorrectable Machine Check Error.
      
      Addressed an issue where the system may experience correctable memory errors
      on some boots. It is recommended that users seeing a high rate of corrected
      memory errors update to this version of the System ROM before replacing any
      hardware.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.50_09-25-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where a system may experience unpredictable system behavior
      when the embedded memory (MCDRAM) is configured in Cache or Hybrid Memory
      modes. This issue does not impact systems configured in Flat Memory mode. This
      issue is not unique to Hewlett Packard Enterprise systems.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.60_01-22-2018
changelog:
  -     *Important Notes:**
      
      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.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 2.44_07-20-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      Added thermal support for the NVIDIA P4, NVIDIA V100, and AMD MI25 Graphics
      Cards.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.02_06-14-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Enhancements/New Features:**
      
      Added support for HPE ProLiant DL380 Gen10 servers using the 2 SFF Premium HDD
      front NVMe/SAS/SATA Kit (Part Number 826687-B21). This is the minimum ROM
      revision required to support servers using this option. If utilizing an
      earlier revision of the System ROM with this option, PCIe Slot 1 will not
      function and any devices installed in that slot will not be visible to the
      system.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     Added support for Dynamic Power Capping. This feature can be enabled from the
      BIOS/Platform Configuration (RBSU) Boot Time Optimizations Menu. This support
      requires Power Management Controller Firmware version 1.0.4 and Integrated
      Lights-Out (iLO) Firmware version 1.15 or later.
      
      Added support for the HPE Core Boost Technology. This feature requires HPE
      Innovation Engine Firmware 0.1.2.6 or later.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for LLC Dead Line Allocation. When running certain applications,
      modifying this setting from its default value may improve system performance.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for Stale A to S. When running certain applications, modifying this
      setting from its default value may improve system performance.
      
      Added support to detect and report unbalanced memory configurations that may
      result in non-optimal performance. Please consult the Memory Population
      Guidelines for more information on memory population rules and
      recommendations.
      
      Added a new Auto option for the XPT Prefetcher in the BIOS/Platform
      Configuration (RBSU) menu that will default the XPT prefetcher to disabled
      based on a current Intel sighting processor issue.  Enabling this option (via
      setting this option for Force Enable) may improve latency performance, but
      Intel has indicated rare stability issues may occur if XPT Prefetcher is
      enabled.
      
      Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated the system thermal logic to support the latest GPU adapters.
      
      Updated the RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the language translations (non-English modes) for System Utilities.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the Embedded UEFI Shell restclient utility would not
      properly configure attributes for Network TLS (HTTPS) support.
      
      Addressed an issue where the UEFI or Legacy Boot Order could still be modified
      after an incorrect Administrator Password was entered in the BIOS/Platform
      Configuration (RBSU) menus.
      
      Addressed an issue where the embedded AHCI SATA controller would not show up
      properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no
      drives were attached to the controller.
      
      Addressed an issue where saving a configuration setting from an optional
      device's configuration page in the System Utilities menu would not be saved
      properly.  This issue was seen with one Network Adapter card.
      
      Addressed an issue where the system ROM would not correctly report a
      configuration error for the HPE Smart Battery storage subsystem when more
      devices were installed than could be supported by the installed battery.
      
      Addressed an issue where a platform configured with direct attached NVMe hard
      drives may report the incorrect location (box and bay location) from the
      System Utilities page.
      
      Addressed an issue where the System Utilities menu may not show the proper
      name for an optional PCIe Adapter.
      
      Addressed an issue where the chassis power supply information would not be
      properly reported from the Industry Standard SMBIOS records.
      
      Addressed an issue where the Integrated Lights Out (iLO) remote Console
      Keyboard and Mouse may not function properly when the system is configured for
      Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot
      Mode.
      
      Addressed an issue where the HPE Jitter Performance feature settings could not
      be properly modified from the Integrated Lights Out web interface.
      
      Addressed an issue where the system may report that the HPE Smart Battery is
      charging when in fact the battery has failed. It is recommended to flash to
      this system ROM if a system is reporting Smart Battery issues.
      
      Addressed an issue where the Trusted Platform Module (TPM) option for TPM
      Visibility could not be configured through the RESTful API.
      
      Addressed an issue where the system may become unresponsive when repeatedly
      typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.
      This issue does not impact systems in UEFI Boot Mode or a system once the
      system boots into an operating system.
      
      Addressed an issue where certain third party PCIe adapters, such as a Dialogic
      adapter, would not function properly due to the PCIe Maximum Payload size
      being incorrectly programmed.
      
      Addressed an issue where certain NVMe devices may not be detected when the x16
      slot PCIe Riser and three slot x8 riser are present in the server.
      
      Addressed an issue where a Network Boot option would still show an entry  in
      the Legacy Boot Order when Network Boot was disabled on the device from the
      BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not
      affect systems configured for UEFI Boot Mode.
      
      Addressed an issue where the system may become unresponsive when using the TAB
      key in the BIOS/Platform Configuration (RBSU) menus.
      
      Addressed an issue where the BIOS would not properly identify and halt a
      system from booting with an invalid DIMM configuration.
      
      Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy
      Efficient Turbo setting was "backwards".  When the configuration setting was
      set to enabled, the feature would actually be Disabled.  When configured to
      Disabled, the feature would actually be enabled.
      
      Addressed an issue where the server might lockup and display a red screen when
      trying to repair a failed RAID volume off of an S100i SW RAID controller.
      
      Addressed an issue where the RESTful API may report that BIOS settings were
      not applied properly even when they are properly configured.
      
      Addressed an issue where the system may become unresponsive during boot after
      a warm reset, typically seen with a blank screen, when a Trusted Platform
      Module (TPM) is installed.  If reboot issues are seen with systems containing
      an optional TPM, it is highly recommended the System ROM be enabled to this
      revision or later.
      
      Addressed an extremely rare issue where the system may incorrectly report a
      413 Innovation Engine Authentication Error on a server reboot.
      
      Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo
      disable functionality.
      
      Removed support for the chipset firmware based Trusted Platform Module (TPM)
      known as Intel Platform Trust Technology (Intel PTT). This feature is no
      longer supported due to stability issues and Intel recommends not supporting
      this feature. Users should instead install a discrete HPE TPM option for this
      support.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.26_11-14-2017
changelog:
  -     Added support for HPE 16GB NVDIMM-N Persistent Memory. Support for this
      feature also requires Innovation Firmware Version 0.1.3.2. This version of
      System ROM and Innovation Engine Firmware 0.1.3.2 are the minimum supported
      Firmware for this feature.
      
      Added support for HPE Scalable Persistent Memory. Support for this feature
      also requires Innovation Firmware Version 0.1.3.2. This version of System ROM
      and Innovation Engine Firmware 0.1.3.2 are the minimum supported Firmware for
      this feature.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     Added support for Dynamic Power Capping. This feature can be enabled from the
      BIOS/Platform Configuration (RBSU) Boot Time Optimizations Menu. For proper
      operation, please ensure that Power Management Controller Firmware version
      1.0.4 and Integrated Lights-Out (iLO) Firmware version 1.15 are updated on the
      server.
      
      Added support for the HPE Core Boost Technology. This feature also require HPE
      Innovation Engine Firmware 1.2.4 to be updated on the system to properly
      function.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for LLC Dead Line Allocation. When running certain applications, it may
      be necessary to change this parameter for optimal system performance.
      
      Added a new BIOS/Platform Configuration (RBSU) Power and Performance Tuning
      option for Stale A to S. When running certain applications, it may be
      necessary to change this parameter for optimal system performance.
      
      Added support to detect and report unbalanced memory configurations that may
      result in non-optimal performance. Please consult the Memory Population
      Guidelines for more information on memory population rules and
      recommendations.
      
      Added a new Auto option for the XPT Prefetcher in the BIOS/Platform
      Configuration (RBSU) menu that will default the XPT prefetched to disabled
      based on a current Intel sighting. It is recommended that users leave this
      setting in Auto mode and do not Force Enable the option due to potential
      stability issues.
      
      Added support for HPE 128GB SmartMemory Load Reduced DIMMs (LRDIMMs).
      
      Updated the system thermal logic to support the latest adapters.
      
      Updated the RESTful API HPE BIOS Attribute Registry resources to match the
      latest BIOS/Platform Configuration options.
      
      Updated the language translations (non-English modes) for System Utilities.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the Embedded UEFI Shell restclient utility would not
      properly configure attributes for Network TLS (HTTPS) support.
      
      Addressed an issue where the UEFI or Legacy Boot Order could still be modified
      after an incorrect Administrator Password was entered in the BIOS/Platform
      Configuration (RBSU) menus.
      
      Addressed an issue where the embedded AHCI SATA controller would not show up
      properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no
      drives were attached to the controller.
      
      Addressed an issue where the chassis power supply information would not be
      properly reported from the Industry Standard SMBIOS records.
      
      Addressed an issue where saving a setting from an Optional Devices
      configuration page, such as a Network Adapter, in the System Utilities menu
      would not be saved properly.
      
      Addressed an issue where the system ROM would not correctly report a
      configurations error for the HPE Smart Battery storage subsystem when more
      devices were installed than could be supported by the installed battery.
      
      Addressed an issue where a platform configured with direct attached NVMe hard
      drives may report the incorrect location (box and bay location) from the
      System Utilities page.
      
      Addressed an issue where the System Utilities menu may not show the proper
      name for an optional PCIe Adapter.
      
      Addressed an issue where the SMBIOS Type 3 record for chassis information may
      not properly report the chassis serial number.
      
      Addressed an issue where the Integrated Lights Out (iLO) remote Console
      Keyboard and Mouse may not function properly when the system is configured for
      Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot
      Mode.
      
      Addressed an issue where the chassis firmware revision would not be reported
      properly from the System Information page or Integrated Lights Out (iLO) web
      interface.
      
      Addressed an issue where the HPE Jitter Performance feature settings could not
      be properly modified from the Integrated Lights Out web interface.
      
      Addressed an issue where the system may report that the HPE Smart Battery is
      charging when in fact the battery has failed. It is recommended to flash to
      this system ROM if a system is reporting Smart Battery issues.
      
      Addressed an issue where the Trusted Platform Module (TPM) option for TPM
      Visibility could not be configured through the RESTful API.
      
      Addressed an issue where the system may become unresponsive when repeatedly
      typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.
      This issue does not impact systems in UEFI Boot Mode or a system once the
      system boots into an operating system.
      
      Addressed an issue where certain third party PCIe adapters, such as a Dialogic
      adapter, would not function properly due to the PCIe Maximum Payload size
      being incorrectly programmed.
      
      Addressed an issue where certain NVMe devices may not be detected when the x16
      slot PCIe Riser and three slot x8 riser are present in the server.
      
      Addressed an issue where a Network Boot option would still show an entry in
      the Legacy Boot Order when Network Boot was disabled on the device from the
      BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not
      affect systems configured for UEFI Boot Mode.
      
      Addressed an issue where the system may become unresponsive when using the TAB
      key in the BIOS/Platform Configuration (RBSU) menus.
      
      Addressed an issue where the BIOS would not properly identify and halt a
      system from booting with an invalid DIMM configuration.
      
      Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy
      Efficient Turbo setting was backwards.
      
      Addressed an issue where the server might lockup and display a red screen when
      trying to repair a failed RAID volume off of a S100i SW RAID controller.
      
      Addressed an issue where the server might become unresponsive during boot when
      trying to repair a failed RAID volume off of a S100i SW RAID controller.
      
      Addressed an issue where the RESTful API may report that BIOS settings were
      not applied properly even when they are properly configured.
      
      Addressed an issue where the system may become unresponsive during boot after
      a warm reset, typically seen with a blank screen, when a Trusted Platform
      Module (TPM) is installed.
      
      Addressed an extremely rare issue where the system may incorrectly report a
      413 Innovation Engine Authentication Error on a server reboot.
      
      Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo
      disable functionality.
      
      Removed the Platform Configuration (RBSU) Option to enable or disable the
      Embedded Diagnostics. Embedded Diagnostics is not supported on this server and
      the menu option should not have been available and was not functional.
      
      Removed support for the Chipset based Firmware Trusted Platform Module (Intel
      PTT). This feature is no longer support due to stability issues. Users should
      instead install a discrete HPE TPM option for this support.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.02_06-14-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the incorrect drive LED could be lit on a drive
      notification event with the embedded HPE SmartArray s100i controller when
      using a Microsoft Windows operating system. This issue does not impact systems
      configured for SATA AHCI Mode.
      
      Removed the Platform Configuration (RBSU) Option to enable or disable the
      Embedded Diagnostics. Embedded Diagnostics is not supported on this server and
      the menu option should not have been available and was not functional.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.20_08-18-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Addressed an issue where the Embedded UEFI Shell restclient utility would not
      properly configure attributes for Network TLS (HTTPS) support.
      
      Addressed an issue where the UEFI or Legacy Boot Order could still be modified
      after an incorrect Administrator Password was entered in the BIOS/Platform
      Configuration (RBSU) menus.
      
      Addressed an issue where the embedded AHCI SATA controller would not show up
      properly in the BIOS/Platform Configuration (RBSU) PCI Devices menu when no
      drives were attached to the controller.
      
      Addressed an issue where saving a configuration setting from an optional
      device's configuration page in the System Utilities menu would not be saved
      properly.  This issue was seen with one Network Adapter card.
      
      Addressed an issue where the system ROM would not correctly report a
      configuration error for the HPE Smart Battery storage subsystem when more
      devices were installed than could be supported by the installed battery.
      
      Addressed an issue where a platform configured with direct attached NVMe hard
      drives may report the incorrect location (box and bay location) from the
      System Utilities page.
      
      Addressed an issue where the System Utilities menu may not show the proper
      name for an optional PCIe Adapter.
      
      Addressed an issue where the chassis power supply information would not be
      properly reported from the Industry Standard SMBIOS records.
      
      Addressed an issue where the chassis firmware revision would not be reported
      properly from the System Information page or Integrated Lights Out (iLO) web
      interface.
      
      Addressed an issue where the Industry Standard SMBIOS Type 3 record for
      chassis information may not properly report the chassis serial number.  
        
      Addressed an issue where the Integrated Lights Out (iLO) remote Console
      Keyboard and Mouse may not function properly when the system is configured for
      Legacy Boot Mode. This issue does not exist on systems configured in UEFI Boot
      Mode.
      
      Addressed an issue where the HPE Jitter Performance feature settings could not
      be properly modified from the Integrated Lights Out web interface.
      
      Addressed an issue where the system may report that the HPE Smart Battery is
      charging when in fact the battery has failed. It is recommended to flash to
      this system ROM if a system is reporting Smart Battery issues.
      
      Addressed an issue where the Trusted Platform Module (TPM) option for TPM
      Visibility could not be configured through the RESTful API.
      
      Addressed an issue where the system may become unresponsive when repeatedly
      typing characters, such as DIR, in Legacy Boot Mode from a pre-OS environment.
      This issue does not impact systems in UEFI Boot Mode or a system once the
      system boots into an operating system.
      
      Addressed an issue where certain third party PCIe adapters, such as a Dialogic
      adapter, would not function properly due to the PCIe Maximum Payload size
      being incorrectly programmed.
      
      Addressed an issue where certain NVMe devices may not be detected when the x16
      slot PCIe Riser and three slot x8 riser are present in the server.
      
      Addressed an issue where a Network Boot option would still show an entry  in
      the Legacy Boot Order when Network Boot was disabled on the device from the
      BIOS/Platform Configuration (RBSU) Network Options Menu. This issue does not
      affect systems configured for UEFI Boot Mode.
      
      Addressed an issue where the system may become unresponsive when using the TAB
      key in the BIOS/Platform Configuration (RBSU) menus.
      
      Addressed an issue where the BIOS would not properly identify and halt a
      system from booting with an invalid DIMM configuration.
      
      Addressed an issue where the BIOS/Platform Configuration (RBSU) Energy
      Efficient Turbo setting was "backwards".  When the configuration setting was
      set to enabled, the feature would actually be Disabled.  When configured to
      Disabled, the feature would actually be enabled.
      
      Addressed an issue where the server might lockup and display a red screen when
      trying to repair a failed RAID volume off of an S100i SW RAID controller.
      
      Addressed an issue where the RESTful API may report that BIOS settings were
      not applied properly even when they are properly configured.
      
      Addressed an issue where the system may become unresponsive during boot after
      a warm reset, typically seen with a blank screen, when a Trusted Platform
      Module (TPM) is installed.  If reboot issues are seen with systems containing
      an optional TPM, it is highly recommended the System ROM be enabled to this
      revision or later.
      
      Addressed an extremely rare issue where the system may incorrectly report a
      413 Innovation Engine Authentication Error on a server reboot.
      
      Removed support for the BIOS/Platform Configuration (RBSU) Power On Logo
      disable functionality.
      
      Removed support for the chipset firmware based Trusted Platform Module (TPM)
      known as Intel Platform Trust Technology (Intel PTT). This feature is no
      longer supported due to stability issues and Intel recommends not supporting
      this feature. Users should instead install a discrete HPE TPM option for this
      support.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.26_11-14-2017
changelog:
  -     *Important Notes:**
      
      This revision of the System ROM enables flash support for Innovation Engine
      (IE) Firmware revision 0.1.4.4 and later. It must be installed prior to
      updating to IE FW 0.1.4.4. Attempting to update to IE FW 0.1.4.4 or later
      without this revision of the System ROM or later will result in the flash
      operation not occurring. This revision of the BIOS, along with IE FW 0.1.4.4
      and SPS FW 04.00.04.288, provide a solution to mitigate security vulnerability
      CVE-2017-5706 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5706)
      and CVE-2017-5709 (http://www.cve.mitre.org/cgi-
      bin/cvename.cgi?name=2017-5709) with Intel's SPS FW. It is anticipated that
      details regarding these security vulnerabilities will be published to these
      links on November 20,2017. These security vulnerabilities are not unique to
      HPE servers. Note that IE FW 0.1.4.4 must be installed prior to updating to
      SPS FW 04.00.04.288.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      This revision of the System ROM enables flash support for Innovation Engine
      (IE) Firmware revision 0.1.4.4 and later. It must be installed prior to
      updating to IE FW 0.1.4.4. Attempting to update to IE FW 0.1.4.4 or later
      without this revision of the System ROM or later will result in the flash
      operation not occurring. This revision of the BIOS, along with IE FW 0.1.4.4
      and SPS FW 04.00.04.288, provide a solution to mitigate security vulnerability
      CVE-2017-5706 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5706)
      and CVE-2017-5709 (http://www.cve.mitre.org/cgi-
      bin/cvename.cgi?name=2017-5709) with Intel's SPS FW. It is anticipated that
      details regarding these security vulnerabilities will be published to these
      links on November 20,2017. These security vulnerabilities are not unique to
      HPE servers. Note that IE FW 0.1.4.4 must be installed prior to updating to
      SPS FW 04.00.04.288.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 1.28_12-11-2017
changelog:
  -     *Important Notes:**
      
      None
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      Updated the Intel processor microcode to the latest version
      
      Addressed an issue where the system may experience an erroneous boot-time
      message and Integrated Management Log (IML) entry stating that Core Boost
      Technology is disabled due to a lack of an iLO Advanced License (531 - Core
      Boost Technology missing required iLO License) when using the Version 1.20
      System ROM. This issue does NOT occur with the Version 1.00 or Version 1.22
      System ROM. Note that this IML entry is only valid for servers using the Intel
      Xeon Scalable 6143 processor. If the message and IML entry are received with
      any other processor model installed, the message is erroneous and can be
      ignored without any negative impact to the system.
      
      **Known Issues:**
      
      None


