# changelog

author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3
changelog:
  -      ****Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.****
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.****


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3
changelog:
  -     *Problems Fixed:**   
      
        * This Firmware prevents a condition in which data failed to be written to media after the host issued a hard reset in a lab stress test environment with write cache enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5
changelog:
  -      ****Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.****
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, VMware ESXi, and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.****


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5
changelog:
  -     *Problems Fixed:**  
      
        * This firmware contains a change which causes the drive hardware to send one Identify frame instead of three for a link reset to mitigate potential speed negotiation issues.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD5 do not need to update to HPD5(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5-2
changelog:
  -     * Enhancements/New Features:**
      
        * Added support for UEFI (Universal Extensible Firmware Interface) based servers.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD8
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * **Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD8
changelog:
  -     *Problems Fixed:**
      
        * Prevents the potential for incorrect data from being "read from" or "written to" the drive under extremely rare circumstances where the drive experiences consecutive error recoveries during a background scan and the Error Correction Code (ECC) fails. This issue has only been observed in a rigorous test environment and has NOT been reported in a customer production environment.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD9
changelog:
  -     *Problems Fixed:**
      
        * Drives could become unresponsive due to unexpected responses from the serial port diagnostic debug connection.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD6
changelog:
  -     *Problem Fixed:**
      
        * After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPD6 prevents this condition from occurring.
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive. The WRITE SAME command may be used during RAID ARRAY parity initialization.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD6-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD6 do not need to update to HPD6(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD6-2
changelog:
  -     *Problem Fixed:**
      
        * After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPD6 prevents this condition from occurring.
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive. The WRITE SAME command may be used during RAID ARRAY parity initialization.
        * Flashing drives connected behind an HP H2xx Host Bus Adapter (HBA) no longer causes an interrupt resulting in drive firmware installation failures.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * **Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7
changelog:
  -     *Enhancements/New Features:**  
      
        * This firmware provides performance improvements for large transfer sequential write burst workloads.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7
changelog:
  -     *Problems Fixed:**   
      
        * This firmware prevents a condition in which data failed to be written to media after the host issued a hard reset in a lab stress test environment with write cache enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD7 do not need to update to HPD7(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7-2
changelog:
  -     *Enhancements/New Features:**  
      
        * This firmware provides performance improvements for large transfer sequential write burst workloads.
        * Added support for UEFI (Universal Extensible Firmware Interface) based servers.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG2
changelog:
  -     *Problems Fixed:**
      
        * Firmware HPG2 corrects an issue whereby the Solid State Drive (SSD) can falsely Smart Trip following power removal. When the SSD Smart Trips, it will report threshold exceeded and operate in low performance mode, most noticeably degraded WRITE performance.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG2-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPG2 do not need to update to HPG2(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG2-2
changelog:
  -     *Problems Fixed:**
      
        * Firmware HPG2 corrects an issue whereby the Solid State Drive (SSD) can falsely Smart Trip following power removal. When the SSD Smart Trips, it will report threshold exceeded and operate in low performance mode, most noticeably degraded WRITE performance.
        * Flashing drives connected behind an HP H2xx Host Bus Adapter (HBA) no longer causes an interrupt resulting in drive firmware installation failures.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG4
changelog:
  -     *Problems Fixed:**
      
        * Firmware version HPG4 resolved a wear-out issue which was caused by frequently issued PIO commands and resulted in a non-responsive drive.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGD-2.1
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPGD do not need to update to HPGD(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGD-2.1
changelog:
  -     *Enhancements/New Features:**
      
        * Frequency of Background Media Scans changed to reduce drive workload.
        * Improvement to allow drives to better handle sudden shock occurrences.
        * New features to enhance telemetry of drive related issues and workload statistics during failure analysis.
        * Added support for UEFI (Universal Extensible Firmware Interface) based servers.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGD-2.1
changelog:
  -     *Problems Fixed:**  
      
        * A correction to address failure to activate LED Activity which occurs during system boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGE
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGE
changelog:
  -     *Enhancements/New Features:**
      
        * Improvements have been made to enhance drive reliability, performance and handle sudden shock situations.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGF
changelog:
  -      **Online firmware flashing of drives attached to an HPE Smart Array controller running in Zero Memory (ZM) mode or an HPE ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * **Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGF
changelog:
  -     *Enhancements/New Features:**
      
        * HPGF firmware improves drive reliability during long periods of host inactivity or under certain workloads which may cause small range seeking for long periods of time.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGG
changelog:
  -     *Problems Fixed:**
      
        * HPGG firmware prevents the potential for incorrect data from being "read from" or "written to" the drive under extremely rare circumstances where the drive experiences consecutive error recoveries during a background scan and the Error Correction Code (ECC) fails. This issue has only been observed in a rigorous test environment and has NOT been reported in a customer production environment.
        * HPGG firmware improves drive reliability where disk drives are exposed to long periods of host inactivity or where drives are used under certain workloads which may cause the disk heads to seek for long periods of time in small ranges on the disk platters.  As a result, hard disk drives may become unresponsive.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> HPGH
changelog:
  -     *Problems Fixed:**
      
        * HPGH firmware improves drive reliability where disk drives are exposed to long periods of host inactivity which exceed 1 second. As a result, hard disk drives may become unresponsive.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG2
changelog:
  -     *Enhancements/New Features:**   
      
        * This firmware improves reliability by modifying the pivot bearing grease wear leveling algorithm, which if not implemented, could result in an increased drive failure rate for specific usage applications (e.g., very long periods of small range seeks).
        * Improvements in random read and write performance.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG2-2
changelog:
  -     *Enhancements/New Features:**   
      
        * This firmware improves reliability by modifying the pivot bearing grease wear leveling algorithm, which if not implemented, could result in an increased drive failure rate for specific usage applications (e.g., very long periods of small range seeks).
        * Improvements in random read and write performance.
        * Added support for UEFI (Universal Extensible Firmware Interface) based servers.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG3
changelog:
  -     *Enhancements/New Features:**
      
        * This firmware includes a performance improvement when drives are operating in an expander environment.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG5
changelog:
  -     *Problem Fixed:**
      
        * Fixes a rare but potential data integrity error during low 5v drive voltage and specific sequential data streaming conditions, which could result in data written to incorrect sectors.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 13.10.83.00
changelog:
  -     *Problems Fixed:**
      
        * Fixed an issue where SATA Spare drive may not spin back up after a Warm Boot.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 13.10.141.00
changelog:
  -     *Enhancements/New Features:**
      
        * Firmware version 13.10.141.0 includes only a version value change so that the version remains the same as the firmware supporting the HP H2xxx series HBA controllers. No functional changes were implemented in this release for the HP B320i controller**.**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 15.10.01.00
changelog:
  -     *Enhancements/New Features:**  
      Enhancements for this version of the firmware include the following support:
      
        * Turn on drive failure indicator anytime a drive fails to link
        * Logging drive link failures
        * The drive write cache can now be enabled, if required. The default setting for drive write cache is disabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 15.10.01.00
changelog:
  -     *Problems Fixed:**  
      The following issues are resolved in this version of the firmware:
      
        * Passthru command could be issued to a direct-attached SATA device before it is ready 
        * Reduced performance caused by detected memory errors
        * Drive health and locate indicators are sent to the incorrect drive bay for expander attached drives
        * Handling an I/O error returns a failed request in scenarios that could have been recovered
        * Installing or removing an expander attached drive is not reported to the BIOS or driver while the firmware is initializing


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 15.10.05.00
changelog:
  -     *Problems Fixed:**  
      The following issues are resolved in this version of the firmware:
      
        * Resolves the I/O errors and/or inability to access solid state drives (SSD) on systems using the HP Smart Array B320i RAID controller and certain SSDs.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 15.10.07.00
changelog:
  -     *Problems Fixed in version 15.10.07.00:**
      
        * Resolves POST error 'MPT BIOS Fault 13h'. If this error occurs, the system will not boot from any boot device attached to an HP Smart Array B320i RAID controller and will be unable to access data on drives attached to the HP Smart Array B320i RAID controller. The fault is triggered if the link between the HP Smart Array B320i RAID controller and the drives goes down during link tuning process. Updated firmware will no longer trigger this fault and the link is now allowed to re-establish itself. This issue is seen only with Solid State Drives (SSD).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 15.10.09.00
changelog:
  -     Firmware Version 15.10.09.00
      
        * Resolves a performance issue that was caused by a 90 msec timeout on all read/write operations when no Smart Carrier was present. This firmware reduces the read/write timeout to 2 msec.
        * Resolves a lockup issue during boot up on the HP ProLiant DL580 Gen8 Server when configured with the HPE Smart Array B320i RAID controller connected to SATA SSD or HDD drives


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.11
changelog:
  -     Firmware version 1.11 is the initial release supporting the HP D3600/D3700
      12Gb SAS Disk Enclosures. This release of I/O module firmware adds
      improvements and corrects issues found during use and additional qualification
      testing after initial product release.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.72
changelog:
  -     *The following fix is added in this version:-**
      
        * Fixed an issue causing fan speed to run at the maximum level due to a false error indication reported on early production hardware.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.72-1
changelog:
  -     Upgrade to D3600/D3700 firmware 1.72(A) is not necessary if the device is
      currently running 1.72 firmware.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.72-2
changelog:
  -     *The following fix is added in this version:-**
      
      -Fixed an issue causing fan speed to run at the maximum level due to a false error indication reported on early production hardware.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG1
changelog:
  -     *Problems Fixed:**
      
        * This maintenance firmware updates temperature reporting, Sanitize Block Erase and includes read performance improvements.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG1-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * **Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.**
        * **Customers who already installed firmware version HPG1 do not need to update to HPG1 (B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG1-2
changelog:
  -     *Problems Fixed: **
      
        * This maintenance firmware updates temperature reporting, Sanitize Block Erase and includes read performance improvements.
        
      
      **Problem fixed in HPG1(B):**
      
        * Linux Smart Component fails to update firmware on SATA drive connected behind a SATA HBA controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPG1-3
changelog:
  -     *Problems Fixed:**
      
        * This maintenance firmware updates temperature reporting, Sanitize Block Erase and includes read performance improvements.
      
      **Problem fixed in HPG1(B):**
      
        * Linux Smart Component fails to update firmware on SATA drive connected behind a SATA HBA controller. Component reports the firmware update was successful. However, after a power cycle, the firmware version remains unchanged.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3
changelog:
  -     *Problems Fixed:**
      
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive.  The WRITE SAME command may be used during RAID ARRAY parity initialization.
        * During a replacement drive rebuild process, a RAID Controller may create false errors. These false errors were improperly counted as true errors by the drive and resulted in a "SMART Imminent Failure" or "Predictive Failure" message. Firmware version HPD3 prevents the drive from counting these false errors and eliminates the unwarranted SMART "Imminent Failure" or "Predictive Failure" message.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD3 do not need to update to HPD3(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3-2
changelog:
  -     *Problems Fixed:**
      
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive.  The WRITE SAME command may be used during RAID ARRAY parity initialization.
        * During a replacement drive rebuild process, a RAID Controller may create false errors. These false errors were improperly counted as true errors by the drive and resulted in a "SMART Imminent Failure" or "Predictive Failure" message. Firmware version HPD3 prevents the drive from counting these false errors and eliminates the unwarranted SMART "Imminent Failure" or "Predictive Failure" message.
        * Flashing drives connected behind an HP H2xx Host Bus Adapter (HBA) no longer causes an interrupt resulting in drive firmware installation failures.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3-3
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD3 do not need to update to HPD3(C).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5
changelog:
  -     *Problems Fixed:**
      
        * HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD5 resolves this issue.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD4
changelog:
  -     *Enhancements/New Features:**
      
        * This microcode includes a change that improves drive performance during reserved area scans.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD6
changelog:
  -     *Problems Fixed:**  
      
        * This firmware improves background scans for media robustness, and also corrects a laboratory induced rare condition that could result in the disk not being updated with the latest cache data.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD8
changelog:
  -     *Problems Fixed:**
      
        * Drive self-test did not complete within the specified time.
        * During a fully cached workload, SMART would report incorrect temperature values.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD2
changelog:
  -     *Problems Fixed:**   
      
        * Resolved an intermittent issue where the drive would not report the progress of the sanitize command in return sense data.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD2-3
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD2 do not need to update to HPD2(C).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD2-3
changelog:
  -     *Problems Fixed:**
      
        * Resolved an intermittent issue where the drive would not report the progress of the sanitize command in return sense data.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD3
changelog:
  -     *Problems Fixed:**
      
        * This maintenance firmware fixes a rare occurrence where the drive would stop communicating with the HOST while recovering from an internal reset.  Due to the device being non-responsive the device was marked as failed by the controller.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD4
changelog:
  -     *Problems Fixed:**
      
        * HPD4 firmware corrects an issue where the drive may not flush user data to media if an internal reset occurs due to a device memory parity error.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD1
changelog:
  -     *Problems Fixed:**   
      
        * This firmware contains a change which causes the drive hardware to send one Identify frame instead of three for a link reset. When the drives are connected to a HP Smart Array E200 controller, the drive firmware must be updated to version HPD1 before the controller will detect the drives.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5
changelog:
  -      ****Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.****


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD5
changelog:
  -     *Enhancements/New Features:**
      
        * Added support for the: 
          * HP Smart Array B320i RAID controller
          * HP Smart Array B120i SATA RAID controller
          * HP HBA H221
          * HP HBA H220
          * HP HBA H222
          * HP HBA H220i
          * HP HBA H210i


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7
changelog:
  -     *Problems Fixed: **
      
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive.  The WRITE SAME command may be used during RAID ARRAY parity initialization.
        * After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPD7 prevents this condition from occurring.
        * During a replacement drive rebuild process, a RAID Controller may create false errors. These false errors were improperly counted as true errors by the drive and resulted in a "SMART Imminent Failure" or "Predictive Failure" message. Firmware version HPD7 prevents the drive from counting these false errors and eliminates the unwarranted SMART "Imminent Failure" or "Predictive Failure" message.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7-2
changelog:
  -     *Problems Fixed: **
      
        * This firmware prevents a rare condition that may occur during a WRITE SAME command sequence that may result in incorrect data being written to the hard drive.  The WRITE SAME command may be used during RAID ARRAY parity initialization.
        * After long term use of the HDD, a rare condition might occur following a power cycle where the drive heads may land on areas of the disk containing data, which could potentially cause data loss or mechanical damage. Firmware version HPD7 prevents this condition from occurring.
        * During a replacement drive rebuild process, a RAID Controller may create false errors. These false errors were improperly counted as true errors by the drive and resulted in a "SMART Imminent Failure" or "Predictive Failure" message. Firmware version HPD7 prevents the drive from counting these false errors and eliminates the unwarranted SMART "Imminent Failure" or "Predictive Failure" message.
        * Flashing drives connected behind an HP H2xx Host Bus Adapter (HBA) no longer causes an interrupt resulting in drive firmware installation failures.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD7-3
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD7 do not need to update to HPD7(C).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD8
changelog:
  -     *Problems Fixed:**
      
        * HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD8 resolves this issue.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD8
changelog:
  -     *Problems Fixed:**
      
        * This microcode corrects a potential command timeout issue, that could result from a possible rare occurrence of a servo stall condition.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD9-2
changelog:
  -      **Online firmware flashing of drives attached to an HP Smart Array controller running in Zero Memory (ZM) mode or an HP ProLiant host bus adapter (HBA) is NOT supported. Only offline firmware flashing of drives is supported for these configurations.**
        * ****Online drive firmware update available for Smart Array Controllers configured in systems running supported Linux, Microsoft Windows, and VMware environments. All other OSes would require an offline update using the SPP and HP SUM.****
        * **Customers who already installed firmware version HPD9 do not need to update to HPD9(B).**


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPDC
changelog:
  -     *Problems fixed:**   
      
        * Addressed an issue with an HP Smart Array E200 controller which could fail to discover a drive when more than one identify frame was provided during discovery.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.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.hp.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.hp.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.hp.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.hp.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.hp.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.hp.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.hp.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.hp.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.hp.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.hp.com> 3.0
changelog:
  -     *Important Notes:**
      
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware.  To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **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.hp.com> 3.0-2
changelog:
  -     *Important Notes:**
      
      Ver. 3.0(B) contains support for new server products. The Power Management
      Controller Firmware contained within ver. 3.0(B) is equivalent to the Firmware
      contained within ver. 3.0. Therefore, it is not necessary to upgrade with ver.
      3.0(B), if the Power Management Controller firmware version is 3.0.  
        
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware.  To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **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.hp.com> 3.1
changelog:
  -     *Important Notes:**
      
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware. To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **Firmware Dependencies:**  
        
      iLO 4 v1.20
      
      **Fixes:**
      
      Addressed an issue where power consumption increases to an unacceptable level
      while upgrading the Power Management Controller firmware.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 3.2
changelog:
  -     *Important Notes:**
      
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware. To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **Firmware Dependencies:**
      
      iLO 4 v1.20 and above
      
      **Problems Fixed:**
      
      Addressed an issue where the Power Management Controller firmware became
      unresponsive when it was upgraded.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 3.3
changelog:
  -     *Important Notes:**
      
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware. To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      This firmware update addresses the issue described in Customer Advisory
      c03885073. For a description of the issue and a list of affected platforms,
      please consult this advisory at http://h20000.www2.hp.com/bizsupport/TechSuppo
      rt/Document.jsp?locale=en_US&objectID;= c03885073.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 3.3-3
changelog:
  -     *Important Notes:**  
      Ver. 3.3(C) contains updates to the OS installation support for HP Smart
      Update Manager. The Power Management Controller Firmware contained within Ver.
      3.3(C) is Ver. 3.3. Therefore, it is not necessary to upgrade with ver.
      3.3(C)if the Power Management Controller firmware version is 3.3.
      
      If a server has a Dynamic Power Cap enabled, the server's performance may be
      significantly affected during the duration of the flash update of the Power
      Management Controller Firmware. To prevent the impact to performance, the
      Dynamic Power Cap can be disabled prior to the flash update process.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      This firmware update addresses the issue described in Customer Advisory
      c03885073.  For a description of the issue and a list of affected platforms,
      please consult this advisory at http://h20000.www2.hp.com/bizsupport/TechSuppo
      rt/Document.jsp?locale=en_US&objectID= c03885073.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 3.3-4
changelog:
  -     *Important Notes:**
      
      Ver. 3.3 (D) contains a change to the Firmware RPM install command name from
      "cpqsetup" to "hpsetup" and is functionally equivalent to ver. 3.3.  It is not
      necessary to upgrade with Revision D if a previous component revision was used
      to upgrade the firmware to version 3.3.
      
      **Firmware Dependencies:**
      
      None
      
      **Problems Fixed:**
      
      This firmware update addresses the issue described in Customer Advisory
      c03885073.  For a description of the issue and a list of affected platforms,
      please consult this advisory at http://h20000.www2.hp.com/bizsupport/TechSuppo
      rt/Document.jsp?locale=en_US&objectID= c03885073.
      
      **Known Issues:**
      
      None


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.50
changelog:
  -     *Problems Fixed:**   
      
        * An intermittent issue that can result in the system fans going to maximum speed during certain heavy IO loads.
        * An issue which prevented the configuration of a maximum size HP SmartCache.
        * The logging of an invalid Smart Array controller failure following a kdump or kexec.
        * Loss of redundant paths following an update of HP D2600/D2700 firmware.
        * An issue that prevented HP SSD SmartPath from being enabled in certain scenarios.
        * An issue that could lead to the controller's read/write cache being disabled in certain scenarios. 
        * An issue that prevented the spare drive Online LED from blinking if one data drive is failed during a RAID migration.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.62
changelog:
  -     *Enhancements/New Features:**
      
        * Enabled support for 4GB cache modules, which is an available option for the HP ProLiant DL580 Gen8 server .


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.62
changelog:
  -     *Problems Fixed:**  
      The following issues are resolved with firmware version 1.62:
      
        * Communication between the HP Integrated Lights-Out (iLO) and the HP Smart Array controller may be lost resulting in an IML entry indicating a failed controller.
        * In some cases, incorrect drive temperatures were reported in an HP D2220sb enclosure, resulting in a system shutdown.
        * VMware might hang when a VM with 2 or more RDMs used a Smart Array controller to access an HP P2000 G3 or HP MSA 2040 SAN storage device.
        * Improved RAID 1 performance for small block random write workloads on SSD configurations.
        * A controller lockup could occur if the controller was configured with a SmartCache smaller than 8GB.
        * On some power cycles, the supercap would always report that it was charging, even though charging had completed.
        * A self-test was revised to correct for false encryption engine failures.
        * Following a reboot, a 0x13 lockup error could occur while encrypting an existing logical volume.
        * When a Solid State Drive was hot-removed during IO and HP SmartPath was enabled, a 0xE3 lockup could occur.
        * Fixes for various POST messages that were displayed when an HP ProLiant DL580 Gen8 server was running UEFI have been implemented. Examples of the POST Messages that were displayed are: Uncorrectable memory error, Inconsistent Drive count message, and Legacy POST ASSERT with bootable HDD removed.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.04
changelog:
  -     *Problems Fixed in version 2.04:**  
      This firmware release resolved the following issues:  
                  **Smart Array controller:**
      
        * It is possible that a controller would become unresponsive when it was configured with a Smart Cache larger than 750MB.
        * Creating or deleting logical drives on a controller that has encryption enabled might cause the controller to halt with Lockup Code =  0xE3.
        * Performing split-mirror operations on encrypted logical drives might cause the controller to halt with Lockup Code =  0xE3.
        * Chkdsk was running slowly.
      
                  **HP ProLiant DL580 Gen8 Server:**
      
        * Server might not boot if it was rebooted while a logical drive transformation was being performed.
        * Server might not apply deferred hard disk drive firmware updates.
        * Server UEFI POST messages were improved. POST message issues included the following examples: 
          * Multiple 1784 or 1787 POST messages were displayed although only one was required.
          * 1789 POST message was not displayed for a degraded Smart Cache.
          * 1739 POST message was not displayed when an unsupported dual domain configuration was connected.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.32
changelog:
  -     *Enhancements/New Features:**
      
        *      Performance enhancement when a drive starts to degrade due to excessive recovered media errors.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.32
changelog:
  -     *Problems Fixed in version 2.32:**  
      This firmware release resolved the following issues:
      
        * With encryption enabled and a rekey operation taking place, if IO running is to Advanced Data Guarding (RAID6) volume and physical drives fail, causing the volume to go into a degraded state, and the customer enables Degraded Mode Performance Optimization via HPSSA, the controller may cease to function (POST Lockup 0xE0).
        * Controller may intermittently cease to function with POST lockup 0xE3 when HP Secure Encryption and large cache writes are enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.40
changelog:
  -      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)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.80
changelog:
  -      HP Smart Array Px3x controller with HP SmartCache enabled on boot volume could potentially encounter file corruption when booting the system if the Super-cap is not fully charged due to being replaced or being in a power down condition for several days (Example 7 days). File corruption is less likely to occur on non-boot volumes than on boot volumes. For additional information please refer to the customer advisory # [c04719000](http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04719000)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 5.44
changelog:
  -     *Problems Fixed:**
      
        * Fixed an issue when executing kdump, systems running in Zero Memory RAID (ZMR) mode may stop responding.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.00
changelog:
  -     *Problems Fixed in version 6.00:**  
      This firmware release resolved the following issues:
      
        * When executing kdump on systems running in Zero Memory RAID (ZMR) mode, the controller might halt.
        * When an HP Smart Array P420 controller was attached to both an expander backplane and non-expander backplane, the controller would not properly control SmartCarrier LEDs.
        * Chkdsk was running slowly.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.10
changelog:
  -     *Problems Fixed:**
      
        * The controller would report 0xE0 error to HP Smart Storage Administrator and would cease to function when set to RAID 6 mode.
        * Intermittent SSD SATA 6G drive failure in Bay 1 of the HP ProLiant BL465 Gen8 Server.
        * Uncorrectable ECC errors causing controller to hang (Lockup 0x13).  Smart Array firmware calculates the maximum controller memory bandwidth required to sustain streaming write operations with the current logical drive configuration and reduces the cache memory speed on configurations that do not require peak controller memory bandwidth.  When running at the slower memory speed, less power is consumed and performance degradation is expected to be negligible. For additional information, reference Customer Advisory c03755983 at the following URL: <http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c03755983>


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.34
changelog:
  -     *Enhancements/New Features:**
      
        * Improved error handling when hard disk drives generate a large number of recoverable errors.
        * Added support for non-hotplug disk drives.
        * Added support for HP ProLiant Gen9 servers: 
          * HP ProLiant BL460c Gen9 Server
          * HP ProLiant BL660c Gen9 Server


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.34
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 a controller was set to RAID6 mode and a large number of recoverable errors were generated by hard disk drives in the system, the controller might go into a degraded mode and cease to function. A 0x0E error message would display during POST on subsequent power cycle and in the Integrated Management Log (IML)
        * The controller would report 0xE0 error to HP Smart Storage Administrator (HP SSA) and would cease to function when set to RAID 6 mode
        * Intermittent SSD SATA 6G drive failures would occur when drive was configured in Bay 1 of HP ProLiant BL465 Gen8 Server
        * Uncorrectable ECC errors would cause the controller to stop responding (Lockup 0x13).  This version of Smart Array firmware properly calculates the maximum controller memory bandwidth required to sustain streaming write operations with the current logical drive configuration and reduces the cache memory speed on configurations that do not require peak controller memory bandwidth.  When running at the slower memory speed, less power is consumed and performance degradation is expected to be negligible. For additional information, reference Customer Advisory # [c03755983](http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c03755983)
        * The HP D2220sb Storage Blade is not recognized when configuring it with the HP ProLiant BL460c Gen9 Server Blade. For additional information please refer to the customer advisory # [c04602866](http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c04602866)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.64
changelog:
  -      An intermittent aborted IO request with attached SATA drives resulted in a LUN (Logical Unit Number) reset.
        * When using SATA drives with a Px2x controller, the server may stop responding or shut down after an extended period of time due to a controller lockup (POST Lockup 0xAB).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 6.68
changelog:
  -      HP Smart Array Px3x controller with HP SmartCache enabled on boot volume could potentially encounter file corruption when booting the system if the Super-cap is not fully charged due to being replaced or being in a power down condition for several days (Example 7 days). File corruption is less likely to occur on non-boot volumes than on boot volumes. For additional information please refer to the customer advisory # [c04719000](http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04719000)
      
        * I/O may halt when the drive write cache is enabled.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hpe.com> 7.02
changelog:
  -      A physical drive configured as a spare drive might indicate predictive failure sooner than expected.
        * Controller might stop responding during run-time (POST Lockup 0x13).
        * When drive write-cache is enabled, protocol errors are observed.
        * After hot-plug replacement of a hard disk drive, incorrect hard disk drive firmware version and upgrade recommendation were displayed by HP Smart Storage Administrator.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.38
changelog:
  -     *Problems Fixed:**
      
        * Resolved a temperature reporting issue that caused the fans in a Bladesystem c-Class enclosure to ramp up and down when the blade servers were powered on but idle (no I/O load).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.42
changelog:
  -     *Problems Fixed:**
      
        * A POST error message is now displayed if a supercap attached to a Gen8 Smart Array P-series (P420, P421, P222, etc) or B-series (B120i, B320i, etc) controller fails to charge.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44
changelog:
  -      Online firmware update available for systems running supported Linux and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44
changelog:
  -     *Problems Fixed:**
      
        * Prior to version 0.44, a cache module charging circuit failure would result in an incorrect POST 1705 error indicating the super-cap should be replaced. This firmware now detects cache module charging circuit failures and displays a new POST 1813 error that correctly instructs the user to replace the cache module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44-2
changelog:
  -      Online firmware update available for systems running supported Linux and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.
        * Customers who already installed firmware version 0.44 do not need to update to 0.44 (B).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44-2
changelog:
  -     *Problems Fixed in version 0.44(B):**
      
        * Resolved an issue where the Smart Component would hang during hardware discovery when an unknown device was present.
      
      **Problems Fixed in version 0.44:**
      
        * Prior to version 0.44, a cache module charging circuit failure would result in an incorrect POST 1705 error indicating the super-cap should be replaced. This firmware now detects cache module charging circuit failures and displays a new POST 1813 error that correctly instructs the user to replace the cache module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44-3
changelog:
  -      Online firmware update available for systems running supported Linux and Microsoft Windows environments. All other OSes would require an offline update using the SPP and HP SUM.
        * Customers who already installed firmware version 0.44 do not need to update to 0.44 (C).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.44-3
changelog:
  -     ***Problems Fixed in version 0.44(C):****
      
        * Fixed an issue where an HP Dynamic Smart Array controller without a cache module attached was being inadvertently detected by the smart component.
      
      **Problems Fixed in version 0.44(B):**
      
        * Resolved an issue where the Smart Component would hang during hardware discovery when an unknown device was present.
      
      **Problems Fixed in version 0.44:**
      
        * Prior to version 0.44, a cache module charging circuit failure would result in an incorrect POST 1705 error indicating the super-cap should be replaced. This firmware now detects cache module charging circuit failures and displays a new POST 1813 error that correctly instructs the user to replace the cache module.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.50
changelog:
  -     *Problems Fixed in version 0.50:**
      
        * In some cases, when the power was applied to the system, the Smart Array controller would report that the supercap was charging even though charging had completed. The supercap charging message would display in the following locations: 
          * POST
          * HP Smart Storage Administrator (HP SSA)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0.50-3
changelog:
  -     *Problems Fixed in version 0.50 (C):**
      
        * Improved integration with HP Smart Update Manager


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 1.98
changelog:
  -     *Problems Fixed: **  
      
        * Addressed a corner-case where multiple reboots of an HP 6Gb SAS BL Switch that is connected to an HP D6000 Disk Enclosure could cause the Smart Array P7xx controller to stop responding.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.38
changelog:
  -     *Problems Fixed:**  
      
        * Under rare circumstances, repeated rebooting of servers might cause loss of paths to the drives.
        * On rare occasions during server power on or hot-add/-removal of drives, the front panel Global Service Indicator (GSI) LED illuminated amber and the back panel seven-segment error display showed a value of 14. The error condition was caused by the error count not getting reset after a hot-plug event.
        * Online LED was not illuminated for configured drives.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.54
changelog:
  -     *Problems Fixed:**
      
        * Improved signal integrity settings to reduce the occurrence of PHY DWORD errors when using HP D6000 Disk Enclosures.
        * Resolves a Smart Array controller 0xAB lockup observed during SAS switch reboots in HP BladeSystem configurations.
        * Limits the SATA drive link rate to 3G, SAS drive link rates are still 6G.
        * Resolves SAS link errors that may occur with cascaded HP D6000 disk enclosures (limited support for cascading).


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 2.70
changelog:
  -     *Problems Fixed:**
      
        * In rare cases, the Smart Array controller would become inaccessible after multiple IO module resets were performed.  If a controller lockup occurred because of this issue, the error code 0xAB would display in the following locations after a subsequent server reboot: 
          * Server POST
          * System event log
          * ADU reports / HPSSA diagnostic reports


author: Sivakumar A <sivakumar.alagumalai@hp.com> 4.2.0-0
changelog:
  - v4.2.0 is mainly targeted for iLO4 1.30, iLO3 1.60 and iLO2 2.20
  - Created 32 bit and 64 bit RPM Packages to load shared library from hp-helth agent as libcpqci.so (in case of 32bit OS) and libcpqci64.so (in case of 64bit OS)


author: Hewlett-Packard Development Company, L.P. 7.1.0
changelog:
  - Improved trust mode during upgrade
   - Fixed group configuration management during Replicate Agents Settings (Severity: Serious)
   - Improved SMH service management
   - Fixed PHP files to avoid crash (Severity: Serious)
   - Improved webapp configuration files
   - Fixed SMH supporting DLLs to avoid version conflicts (Severity: Serious)
   - updated properties of SMH setup file
   - Updated secured handling of HTTP response
   - Updated Libxml2 to version 2.7.8
   - Updated PHP to version 5.3.10
   - Updated Curl library to version 7.24.0
   - Updated OpenSSL to version 1.0.0h
   - Updated SMH service runs with managed privileges
   - Enable support of Windows 2008 R2 Sp1 - Server Core
   - Enable support of Windows Server 8 (Beta)
   - Enable support of Windows Multipoint Server 2011 for x64
   - Enable support of Microsoft Windows Small Business Server 2011 for x64, Standard and Essentials
   - Updated usability of IP restrictions with SMH Command Line Interface
   - Updated information provided on webapp availability & loading statistics
   - Added support for Firefox 9.0 & 10.0

   * Thu Oct 13 2011 Hewlett-Packard Development Company, L.P. 7.0.0
   - Fixed SMH improperly displayed an invalid certificate warning when restarted, even on a fresh install. (Severity: Medium)
   - Added a command line option to modify the local and state information in the SMH PKCS (Public-Key Cryptography Standards) data
   - Added secured handling of HTTP request and response
   - Added support for Firefox 6.0, 7.0, 8.0 and Internet Explorer 9.0
   - clarified the log messages
   - Improved handling of command Line Interface options
   - Improved handling of IP fields
   - Improved handling of memory resources
   - Improved handling of revoked trusted certificate
   - Improved handling of SMH configuration file and settings
   - Improved CLI options, for easier management of SMH configurations
   - Updated the HTTP links
   - Updated Apache to version 2.2.21
   - Updated Curl library to version 7.21.7
   - Updated OpenSSL to version 1.0.0e
   - Updated PHP to version 5.3.8


author: Hewlett-Packard Development Company, L.P. 7.1.1
changelog:
  - On some Non-English Windows Operating Systems, user is not able to login into SMH 7.1.0. This version will solve this problem (Severity: Critical)
   - Improved security features of PHP (Severity: Critical)


author: Hewlett-Packard Development Company, L.P. 7.1.2
changelog:
  - Improved security features 
   - Improved logging on few Operating Systems
   - Enable support of Red Hat Client 5.8
   - Updated OpenSSL to version 1.0.1c (Severity: Critical)
   - Updated PHP to version 5.3.14 (Severity: Critical)
   - Improvement in RPM packaging


author: Hewlett-Packard Development Company, L.P. 7.2.0
changelog:
  - Updated Apache to version 2.4.3 (Severity: Critical)
   - Improved logging on few Operating Systems
   - Improvement in Certificate management
   - Added support for Firefox ESR 17.0 and Internet Explorer 10.0
   - Enable support for Transport Layer Security (TLS) protocol 1.1 / 1.2
   - Improved User Interface for Online Help
   - Improved CLI options for easier management of SMH configurations
   - Secured handling of HTTP communication


author: Hewlett-Packard Development Company, L.P. 7.2.2
changelog:
  - Updated PHP to version 5.4.11
   - Updated Curl to version 7.28.1
   - Enable support of SUSE Linux Enterprise Server 11 SP3


author: Hewlett-Packard Development Company, L.P. 7.3.0
changelog:
  - Enabled Simplified Chinese localization
   - Updated Apache to version 2.4.6
   - Updated Libxml2 to version 2.9.1
   - Updated OpenSSL to version 1.0.1e
   - Updated Curl to version 7.32.0
   - Updated PHP to version 5.5.2
   - Packaged zlib 1.2.8 with SMH


author: Hewlett-Packard Development Company, L.P. 7.3.1
changelog:
  - Enabled support of 2048 & 4096 bit certificate for Single Sign-On (SSO)
   - Enabled FQDN (Fully Qualified Domain Name) for the CN (Common Name) field in the self-signed certificate & CSR (Certificate Signing Request)


author: Hewlett-Packard Development Company, L.P. 7.4.0
changelog:
  - Enabled support for Red Hat Enterprise Linux 7 
  - Updated the following components 
  		PHP to version php-5.5.13 
  		curl to version curl-7.35.0
  		openssl to version openssl-1.0.1h
  - Improved SMH to use the system resources efficiently. 
  - SMH Plugin integration is modified. 
  - Enabled Japanese localization in SMH smart component installer
  - removed files related to Namazu
  - removed the checks for ZLIB installation


author: Hewlett-Packard Development Company, L.P. 7.4.1
changelog:
  - Updated the following components
    PHP to version php-5.5.18
    curl to version curl-7.38.0
    openssl to version openssl-1.0.1j
  - Disabled SSLv3 Protocol
  - SMH is been improvised with respect to security vulnerabilites


author: Ver:2.40-13.0
changelog:
  - Please refer to online documentation by searching for the 
  "HP Array Configuration Utility CLI" using the search box on
  http://www.hp.com. Then select the Download software link,
  select your operation system. Under the Enhancements tab is a 
  description of the changes. (Severity: Low)


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0070-1
changelog:
  -      Increased stack size for one of the threads to prevent an I/O module hang during firmware upgrades.
        * Fixed a problem when drive LEDs remained ON following a drive hot removal in some cases.
        * Updated the Japanese text descriptions inside the smart component framework.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0070-2
changelog:
  -     *Enhancements for Firmware version 0070**
      
        * Provide dual-domain support in server-connect environments using Smart Array firmware v3.30 or higher.
        * Added further enhancements to prevent NVRAM degradation that occurred in certain limited cases.
        * Incorporated general improvements for monitoring environmental conditions.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0070-2
changelog:
  -     *Fixes for Firmware version 0070**  
      
        * Increased stack size for one of the threads to prevent an I/O module hang during firmware upgrades.
        * Fixed a problem when drive LEDs remained ON following a drive hot removal in some cases.
      
      **Fixes for Smart Component 0070(B)**
      
        * Added HPSUM interoperability.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0103
changelog:
  -      Improve detection of bad SAS cables and I/O modules.
        * Provide capability for the enclosure to properly enter standby when controlling power supplies directly.
        * Add signal integrity settings for external connectors.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0103
changelog:
  -      Incorporate changes to properly initialize drive phys when leaving standby.
        * Incorporate new health monitor firmware for a new hardware chip.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0131
changelog:
  -     Server-attach environments installing D2600/D2700 I/O module firmware 0070 or
      later must update Smart Array controller firmware to v3.50 or higher before
      installing new firmware on the D2600/D2700 disk enclosure.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0131
changelog:
  -      Improved support for Solid State Drives.
      
        * Added support for drive-bay zoning.
      
        * Improved firmware updating processes to reduce installation time.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0131
changelog:
  -      Adjust warning and failure flags for ELMo temperature sensors. Warning is 64 and failure is 70.
      
        * Maintain OK for the element status field of array devices, even when bypassed.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> 0150-1
changelog:
  -     *The following fix is added in this version:-**
      
      -Removed action over FAULT_SENSED bit due to incorrect algorithm.


author: HP Linux Development <Linux_SWdeliverables@external.groups.hp.com> HPD9
changelog:
  -     *Problems Fixed:**
      
        * Prevents the potential for incorrect data from being "read from" or "written to" the drive under extremely rare circumstances where the drive experiences consecutive error recoveries during a background scan and the Error Correction Code (ECC) fails. This issue has only been observed in a rigorous test environment and has NOT been reported in a customer production environment.
        * There is also a change to prevent the drive from dwelling on a single track for an extended period.


