• Fixed the issue with Insight Management WBEM override root\interop namespace for Hyper-V.

• 50% slow performance/backup issue with HP Ultrium/LTO polling issues.

• Tape backup fails randomly (irrespective of any server or controller/backup software) when HPE Insight Management WBEM Providers is upgraded to version 10.X.

•  Providers are causing spare drives to be spun up every few minutes.

• Fixed the issue with Insight Management WBEM override root\interop namespace for Hyper-V.

• 50% slow performance/backup issue with HP Ultrium/LTO polling issues.

• Tape backup fails randomly (irrespective of any server or controller/backup software) when HPE Insight Management WBEM Providers is upgraded to version 10.X.

•  Providers are causing spare drives to be spun up every few minutes.

• Corrected Echo Test by setting bit 15 in ECHO mailbox command

• Corrected BBCR to return correct number of status mailbox registers

• Changed Maximum read request size to 4K bytes

• 通过在 ECHO 邮箱命令中设置位 15 更正了回波测试

• 更正了 BBCR，使其返回正确的状态邮箱寄存器数

• 将最大读取请求大小更改为了 4K 字节

• Corrected Echo Test by setting bit 15 in ECHO mailbox command

• Corrected BBCR to return correct number of status mailbox registers

• Changed Maximum read request size to 4K bytes

• 通过在 ECHO 邮箱命令中设置位 15 更正了回波测试

• 更正了 BBCR，使其返回正确的状态邮箱寄存器数

• 将最大读取请求大小更改为了 4K 字节

• Corrected Echo Test by setting bit 15 in ECHO mailbox command

• Corrected BBCR to return correct number of status mailbox registers

• Changed Maximum read request size to 4K bytes

• 通过在 ECHO 邮箱命令中设置位 15 更正了回波测试

• 更正了 BBCR，使其返回正确的状态邮箱寄存器数

• 将最大读取请求大小更改为了 4K 字节

Server / Foundation Agents:

• VCA showing incorrect installed version of Advanced Power Capping
• Incorrect memory rank information displayed in SMH
• Agents reporting degraded events when cluster resource of Virtual Machine type is taken offline
• Hyphens are now allowed in SNMP community name
• "NVRAM space" field is missing in SMH iLO Self Test results
• Incorrect name of NIC cards displayed under PCI Devices in SMH
• RNVDIMM Technology is not displayed correctly in SMH
• Incorrect name of Mellanox adapters in PCI Devices
• CSRF vulnerabilities have been rectified in the SMH Settings tab
• SMH links which has Threshold settings feature are taking long time to load/refresh in UI Mode. This mode will use Java Runtime(JRE) and latest Java releases (7.x or later) is causing the delay. So, the UI Mode is disabled and now the Threshold settings will display in Text Mode only.
• Event Notifier Not Sending Email alert for storage system Power Supply failure trap.
• Dispalying rebranded name 'HPE' in Agents Control panel Applet
• On SMH Wrong OS name displaying for core OS installation
• cpqHeResMem2ModuleTechnology showing wrong values
• cpqHeFltTolPwrSupplyStatus showing wrong value .

Server / Foundation Agents:

• VCA showing incorrect installed version of Advanced Power Capping
• Incorrect memory rank information displayed in SMH
• Agents reporting degraded events when cluster resource of Virtual Machine type is taken offline
• Hyphens are now allowed in SNMP community name
• "NVRAM space" field is missing in SMH iLO Self Test results
• Incorrect name of NIC cards displayed under PCI Devices in SMH
• RNVDIMM Technology is not displayed correctly in SMH
• Incorrect name of Mellanox adapters in PCI Devices
• CSRF vulnerabilities have been rectified in the SMH Settings tab
• SMH links which has Threshold settings feature are taking long time to load/refresh in UI Mode. This mode will use Java Runtime(JRE) and latest Java releases (7.x or later) is causing the delay. So, the UI Mode is disabled and now the Threshold settings will display in Text Mode only.
• Event Notifier Not Sending Email alert for storage system Power Supply failure trap.
• Dispalying rebranded name 'HPE' in Agents Control panel Applet
• On SMH Wrong OS name displaying for core OS installation
• cpqHeResMem2ModuleTechnology showing wrong values
• cpqHeFltTolPwrSupplyStatus showing wrong value .

Agents Installation:

• IMA update returns an error in HPSUM when configure the SNMP paramaters
• IMA build failed after upgrading to new version of dependent modules

Server / Foundation Agents:

• Incorrect Power Supply Status displayed in SMH when the disonencted power cable is connected back
• Foundation Agents Enumerates Only One-Half of Logical Processors on Gen9 Servers
• Incorrect Description displayed for HP NCU card under Software Version in Windows SMH
• Incorrect Lower Threshold Description displayed for File System Space Used in Windows SMH
• Windows IMA provides Excessive logging when firewall is ON
• Incorrect name displayed for 561T card under PCI Devices in SMH.
• Incorrect Speed of Igloo Adapter under 'Operating System -> Network' in Windows SMH
• Incorrect Speed for Disconnected Igloo Port under 'Operating System -> Network'
• Incomplete ROM Version displayed under Firmware Version and System Board in Windows SMH
• Incorrect name displayed for HPE StoreFabric CN1100R in Windows SMH
• Unexpected error messages logged in eventvwr on fan removal in continue mode
• Incorrect Cooling status observed with fresh boot up on DL360e
• Event ID 1183 is not logged when an USB device is removed with IMA v10.00 and later
• snmpagnt.php in SPP is vulnerable to Code Execution
• snmpagnt.php in SPP is vulnerable to CSRF attack
• iLO self-test results displaying empty for 'NVRAM space' in SMH

• 安装

• IMA 更新在 HPSUM 中返回一个错误时配置 SNMP paramaters
• 升级至最新版本，而定模块后，无法执行 IMA build

服务器/基础代理：

• 错误 Power Supply Status disonencted 电源线重新连接时在 SMH 中显示
• Foundation Agents只枚举Gen9服务器上的一半逻辑处理器
• 在 Windows SMH 中的软件版本的 HP NCU 卡中的显示错误的说明
• Windows SMH中已用文件系统空间的阈值说明过低
• Windows IMA 提供 Excessive 记录时防火墙
• 在 SMH 中的 PCI 设备 561T 卡中的显示不正确的名称。
• 错误速度的 Igloo 适配器在 Operating System-& g t;网络在 Windows 中 SMH
• 在断开 Igloo 端口速度不正确 Operating System-& g t;网络
• 在固件版本和 Windows SMH 中的系统板下显示不完整的 ROM 版本
• 错误的 HPE StoreFabric CN1100R Windows SMH 中显示的名称
• 在中拆除风扇上的 eventvwr 中记录的意外的错误消息继续模式
• 出现新的启动向上 DL360e 上不正确的散热状态
• USB 设备取出 IMA v10.00 或更高版本时，不会记录 event ID 1183
• 在 SPP snmpagnt.php 易于受到代码执行
• - 在SPP CSRF中Cygwin易受Shellshock漏洞攻击。
• iLO 自检结果显示在 SMH 中的 NVRAM 空间为空

Server / Foundation Agents:

• VCA showing incorrect installed version of Advanced Power Capping
• Incorrect memory rank information displayed in SMH
• Agents reporting degraded events when cluster resource of Virtual Machine type is taken offline
• Hyphens are now allowed in SNMP community name
• "NVRAM space" field is missing in SMH iLO Self Test results
• Incorrect name of NIC cards displayed under PCI Devices in SMH
• RNVDIMM Technology is not displayed correctly in SMH
• Incorrect name of Mellanox adapters in PCI Devices
• CSRF vulnerabilities have been rectified in the SMH Settings tab.
• SMH links which has Threshold settings feature are taking long time to load/refresh in UI Mode. This mode will use Java Runtime(JRE) and latest Java releases (7.x or later) is causing the delay. So, the UI Mode is disabled and now the Threshold settings will display in Text Mode only.
• Event Notifier Not Sending Email alert for storage system Power Supply failure trap.
• Dispalying rebranded name 'HPE' in Agents Control panel Applet
• On SMH Wrong OS name displaying for WS2k16 Storage Server
• On SMH Wrong OS name displaying for core OS installation.
• cpqHeResMem2ModuleTechnology showing wrong values
• cpqHeFltTolPwrSupplyStatus showing wrong value .

Server / Foundation Agents:

• VCA showing incorrect installed version of Advanced Power Capping
• Incorrect memory rank information displayed in SMH
• Agents reporting degraded events when cluster resource of Virtual Machine type is taken offline
• Hyphens are now allowed in SNMP community name
• "NVRAM space" field is missing in SMH iLO Self Test results
• Incorrect name of NIC cards displayed under PCI Devices in SMH
• RNVDIMM Technology is not displayed correctly in SMH
• Incorrect name of Mellanox adapters in PCI Devices
• CSRF vulnerabilities have been rectified in the SMH Settings tab.
• SMH links which has Threshold settings feature are taking long time to load/refresh in UI Mode. This mode will use Java Runtime(JRE) and latest Java releases (7.x or later) is causing the delay. So, the UI Mode is disabled and now the Threshold settings will display in Text Mode only.
• Event Notifier Not Sending Email alert for storage system Power Supply failure trap.
• Dispalying rebranded name 'HPE' in Agents Control panel Applet
• On SMH Wrong OS name displaying for WS2k16 Storage Server
• On SMH Wrong OS name displaying for core OS installation.
• cpqHeResMem2ModuleTechnology showing wrong values
• cpqHeFltTolPwrSupplyStatus showing wrong value .

Agents Installation:

• IMA update returns an error in HPSUM when configure the SNMP paramaters
• IMA build failed after upgrading to new version of dependent modules

Server / Foundation Agents:

• Incorrect Power Supply Status displayed in SMH when the disonencted power cable is connected back
• Foundation Agents Enumerates Only One-Half of Logical Processors on Gen9 Servers
• Incorrect Description displayed for HP NCU card under Software Version in Windows SMH
• Incorrect Lower Threshold Description displayed for File System Space Used in Windows SMH
• Windows IMA provides Excessive logging when firewall is ON
• Incorrect name displayed for 561T card under PCI Devices in SMH.
• Incorrect Speed of Igloo Adapter under 'Operating System -> Network' in Windows SMH
• Incorrect Speed for Disconnected Igloo Port under 'Operating System -> Network'
• Incomplete ROM Version displayed under Firmware Version and System Board in Windows SMH
• Incorrect name displayed for HPE StoreFabric CN1100R in Windows SMH
• Unexpected error messages logged in eventvwr on fan removal in continue mode
• Incorrect Cooling status observed with fresh boot up on DL360e
• Event ID 1183 is not logged when an USB device is removed with IMA v10.00 and later
• snmpagnt.php in SPP is vulnerable to Code Execution
• snmpagnt.php in SPP is vulnerable to CSRF attack
• iLO self-test results displaying empty for 'NVRAM space' in SMH

• 安装

• IMA 更新在 HPSUM 中返回一个错误时配置 SNMP paramaters
• 升级至最新版本，而定模块后，无法执行 IMA build

服务器/基础代理：

• 错误 Power Supply Status disonencted 电源线重新连接时在 SMH 中显示
• Foundation Agents只枚举Gen9服务器上的一半逻辑处理器
• 在 Windows SMH 中的软件版本的 HP NCU 卡中的显示错误的说明
• Windows SMH中已用文件系统空间的阈值说明过低
• Windows IMA 提供 Excessive 记录时防火墙
• 在 SMH 中的 PCI 设备 561T 卡中的显示不正确的名称。
• 错误速度的 Igloo 适配器在 Operating System-& g t;网络在 Windows 中 SMH
• 在断开 Igloo 端口速度不正确 Operating System-& g t;网络
• 在固件版本和 Windows SMH 中的系统板下显示不完整的 ROM 版本
• 错误的 HPE StoreFabric CN1100R Windows SMH 中显示的名称
• 在中拆除风扇上的 eventvwr 中记录的意外的错误消息继续模式
• 出现新的启动向上 DL360e 上不正确的散热状态
• USB 设备取出 IMA v10.00 或更高版本时，不会记录 event ID 1183
• 在 SPP snmpagnt.php 易于受到代码执行
• - 在SPP CSRF中Cygwin易受Shellshock漏洞攻击。
• iLO 自检结果显示在 SMH 中的 NVRAM 空间为空

This product addresses an issue which results in a system hang after configuration of VMQ adapters.

This product addresses an issue where a system crash occurs on a Virtual Machine after rebooting to recover a failing virtual function device.

This product addresses an issue which results in a system hang after configuration of VMQ adapters.

This product addresses an issue where a system crash occurs on a Virtual Machine after rebooting to recover a failing virtual function device.

This product addresses an issue which results in a system hang after configuration of VMQ adapters.

This product addresses an issue where a system crash occurs on a Virtual Machine after rebooting to recover a failing virtual function device.

This product addresses an issue which results in a system hang after configuration of VMQ adapters.

This product addresses an issue where a system crash occurs on a Virtual Machine after rebooting to recover a failing virtual function device.

The *NumaNodeID keyword has been changed to type "dword"(as per Microsoft documentation) to correctly support more than 8 NUMA nodes.

*NumaNodeID关键字已改为"dword"类型（根据Microsoft文档），以正确支持8个以上的NUMA节点。

This driver addresses an issue where PCI-e completion timeouts take longer than expected.

该驱动程序解决了PCI-e完成超时超过预期的问题。

The *NumaNodeID keyword has been changed to type "dword"(as per Microsoft documentation) to correctly support more than 8 NUMA nodes.

*NumaNodeID关键字已改为"dword"类型（根据Microsoft文档），以正确支持8个以上的NUMA节点。

This driver addresses an issue where PCI-e completion timeouts take longer than expected.

该驱动程序解决了PCI-e完成超时超过预期的问题。

The *NumaNodeID keyword has been changed to type "dword"(as per Microsoft documentation) to correctly support more than 8 NUMA nodes.

*NumaNodeID关键字已改为"dword"类型（根据Microsoft文档），以正确支持8个以上的NUMA节点。

This driver addresses an issue where PCI-e completion timeouts take longer than expected.

该驱动程序解决了PCI-e完成超时超过预期的问题。

This product addresses an issue where a yellow bang appears when the user chooses to create a virtual machine using an existing virtual hard disk.

本产品解决了用户使用现有虚拟硬盘创建虚拟机时，出现黄色爆炸状图形的问题。

This driver addresses an issue where Data Center Bridging (DCB) support is incorrectly advertised when the *QoS keyword is present.

This driver addresses an issue which can prevent the driver from loading when the adapter is configured for sideband management.

This driver addresses an issue where Data Center Bridging (DCB) support is incorrectly advertised when the *QoS keyword is present.

This driver addresses an issue which can prevent the driver from loading when the adapter is configured for sideband management.

This product addresses an issue where a yellow bang appears when the user chooses to create a virtual machine using an existing virtual hard disk.

本产品解决了用户使用现有虚拟硬盘创建虚拟机时，出现黄色爆炸状图形的问题。

This driver addresses an issue which prevents single root I/O virtualization (SR-IOV) functionality on Windows Server 2012.

This driver addresses an issue which can prevent the driver from loading when the adapter is configured for sideband management.

This driver addresses an issue which prevents single root I/O virtualization (SR-IOV) functionality on Windows Server 2012.

This driver addresses an issue which can prevent the driver from loading when the adapter is configured for sideband management.

This product addresses an issue where a yellow bang appears when the user chooses to create a virtual machine using an existing virtual hard disk.

本产品解决了用户使用现有虚拟硬盘创建虚拟机时，出现黄色爆炸状图形的问题。

This driver addresses an issue which results in a yellow-bang in the virtual function device in a virtual machine supplied by a Linux host.

This driver addresses an issue which results in virtual function errors when changing the number of virtual processors in a Windows guest virtual machine supplied by a VMWare host.

This driver addresses an issue which can prevent the driver from loading when the adapter is configured for sideband management.

该驱动程序解决了导致在 Linux 主机中的虚拟机的虚拟功能设备中出现黄色警告的问题。

该驱动程序解决了更改 VMWare 主机中的 Windows 客户虚拟机的虚拟处理器数量时，导致虚拟功能错误的问题。

该驱动程序解决了配置适配器以进行边带管理时阻止驱动程序加载的问题。

This driver corrects an issue with the Powershell setting of RDMA over Converged Ethernet (RoCE) mode when the machine has more than one Mellanox device installed.

This driver corrects an issue with the reporting of Network Virtualization using Generic Routing Encapsulation (NVGRE) capabilities to the operating system.

该驱动程序解决了当机器上已安装多个Mellanox设备时，采用Powershell在融合以太网（RoCE）模式中设置RDMA的问题。

此驱动程序解决了在操作系统中使用通用路由封装（NVGRE）功能进行网络虚拟化报告的问题。

This driver addresses a failure seen when calling Get-MlnxFirmwareIdentity when not all devices are enabled.

该驱动程序解决了并非所有设备都启用时，调用Get-MlnxFirmwareIdentity出现的故障。

This driver corrects an issue with the Powershell setting of RDMA over Converged Ethernet (RoCE) mode when the machine has more than one Mellanox device installed.

This driver corrects an issue with the reporting of Network Virtualization using Generic Routing Encapsulation (NVGRE) capabilities to the operating system.

该驱动程序解决了当机器上已安装多个Mellanox设备时，采用Powershell在融合以太网（RoCE）模式中设置RDMA的问题。

此驱动程序解决了在操作系统中使用通用路由封装（NVGRE）功能进行网络虚拟化报告的问题。

This driver addresses a failure seen when calling Get-MlnxFirmwareIdentity when not all devices are enabled.

该驱动程序解决了并非所有设备都启用时，调用Get-MlnxFirmwareIdentity出现的故障。

This driver corrects an issue with the Powershell setting of RDMA over Converged Ethernet (RoCE) mode when the machine has more than one Mellanox device installed.

This driver corrects an issue with the reporting of Network Virtualization using Generic Routing Encapsulation (NVGRE) capabilities to the operating system.

该驱动程序解决了当机器上已安装多个Mellanox设备时，采用Powershell在融合以太网（RoCE）模式中设置RDMA的问题。

此驱动程序解决了在操作系统中使用通用路由封装（NVGRE）功能进行网络虚拟化报告的问题。

This driver addresses a failure seen when calling Get-MlnxFirmwareIdentity when not all devices are enabled.

该驱动程序解决了并非所有设备都启用时，调用Get-MlnxFirmwareIdentity出现的故障。

• After hot adding a D2700 JBOD to the external port of an HP H221 HBA, a 0xD1 blue screen was encountered.

• After hot adding a D2700 JBOD to the external port of an HP H221 HBA, a 0xD1 blue screen was encountered.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Server hangs with 6/8TiB drives.
• Driver hangs with SasGetDeviceAddress command.

• Server hangs with 6/8TiB drives.
• Driver hangs with SasGetDeviceAddress command.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

• Operating system becomes unresponsive when server is configured with > 512 GB of memory and Smart Path is enabled.
• Windows blue screen can occur for HPE Smart Array controllers configured with RAID volumes if the operating system performs a LUN reset after encountering an I/O timeout.

Change implemented in version 100.18.2.64(A):

• Updated to support Service Pack for ProLiant version 2017.07.0.
  Note: If driver version 100.18.2.64 was previously installed, then it is not necessary to upgrade to version 100.18.2.64(A).

Issues resolved in version 100.18.2.64:

• Server hangs with 6/8TiB drives.
• Driver hangs with SasGetDeviceAddress command.

Change implemented in version 100.18.2.64(A):

• Updated to support Service Pack for ProLiant version 2017.07.0.
  Note: If driver version 100.18.2.64 was previously installed, then it is not necessary to upgrade to version 100.18.2.64(A).

Issues resolved in version 100.18.2.64:

• Server hangs with 6/8TiB drives.
• Driver hangs with SasGetDeviceAddress command.

If an unexpected power outage occurred, the system might stop operating during Power-On Self Test

Controller could stop responding when Smart Cache is performing a read operation

Version 4.10(A)

Modified component installer to detect if the Windows HPCISSS3.sys driver version 100.18.2.64, 6.18.2.64 or 6.18.2.32 is installed.  With these HPCISSS3.sys driver versions, a Windows blue screen could occur during installation of the controller firmware. HPCISSS3.sys driver must be updated to versions as follow:

• 100.18.2.64 to 100.20.0.64
• 6.18.2.64 to 6.20.0.64 
• 6.18.2.32 to 6.20.0.32 

Also, the Windows operating system must be restarted before attempting to install this component.

If an unexpected power outage occurred, the system might stop operating during Power-On Self Test

Controller could stop responding when Smart Cache is performing a read operation

Version 4.10(A)

Modified component installer to detect if the Windows HPCISSS3.sys driver version 100.18.2.64, 6.18.2.64 or 6.18.2.32 is installed.  With these HPCISSS3.sys driver versions, a Windows blue screen could occur during installation of the controller firmware. HPCISSS3.sys driver must be updated to versions as follow:

• 100.18.2.64 to 100.20.0.64
• 6.18.2.64 to 6.20.0.64 
• 6.18.2.32 to 6.20.0.32 

Also, the Windows operating system must be restarted before attempting to install this component.

If an unexpected power outage occurred, the system might stop operating during Power-On Self Test

Controller could stop responding when Smart Cache is performing a read operation

Version 4.10(A)

Modified component installer to detect if the Windows HPCISSS3.sys driver version 100.18.2.64, 6.18.2.64 or 6.18.2.32 is installed.  With these HPCISSS3.sys driver versions, a Windows blue screen could occur during installation of the controller firmware. HPCISSS3.sys driver must be updated to versions as follow:

• 100.18.2.64 to 100.20.0.64
• 6.18.2.64 to 6.20.0.64 
• 6.18.2.32 to 6.20.0.32 

Also, the Windows operating system must be restarted before attempting to install this component.

If an unexpected power outage occurred, the system might stop operating during Power-On Self Test

Controller could stop responding when Smart Cache is performing a read operation

Version 4.10(A)

Modified component installer to detect if the Windows HPCISSS3.sys driver version 100.18.2.64, 6.18.2.64 or 6.18.2.32 is installed.  With these HPCISSS3.sys driver versions, a Windows blue screen could occur during installation of the controller firmware. HPCISSS3.sys driver must be updated to versions as follow:

• 100.18.2.64 to 100.20.0.64
• 6.18.2.64 to 6.20.0.64 
• 6.18.2.32 to 6.20.0.32 

Also, the Windows operating system must be restarted before attempting to install this component.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• 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 HP Host Bus Adapter H220 connected to SATA SSD or HDD drives.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• Modified the component installer to update both the HPE Dynamic Smart Array B320i RAID Controller firmware and the H2xx HBA Option ROM firmware when the HPE Dynamic Smart Array B320i RAID Controller is enabled in the server’s ROM-Based Setup Utility.  Previous versions of the component only updated the HPE B320i controller firmware which would result in customers running older H2xx HBA Option ROM firmware if the controller was switched from RAID mode to HBA mode by disabling the HPE Dynamic Smart Array B320i RAID Controller in the server’s ROM-Based Setup Utility.

• Modified the component installer to update both the HPE Dynamic Smart Array B320i RAID Controller firmware and the H2xx HBA Option ROM firmware when the HPE Dynamic Smart Array B320i RAID Controller is enabled in the server’s ROM-Based Setup Utility.  Previous versions of the component only updated the HPE B320i controller firmware which would result in customers running older H2xx HBA Option ROM firmware if the controller was switched from RAID mode to HBA mode by disabling the HPE Dynamic Smart Array B320i RAID Controller in the server’s ROM-Based Setup Utility.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• HPE ProLiant BL420c Gen8 server configured with HPE Dynamic Smart Array B320i RAID controllers, failed to boot and the system stopped responding during Power-On Self-Test (POST). In some instances, the message, "1783 Driver Array Controller Failure" was displayed. Please refer to HPE Customer Advisory c05317927 for details.

• Modified the component installer to update both the HPE Dynamic Smart Array B320i RAID Controller firmware and the H2xx HBA Option ROM firmware when the HPE Dynamic Smart Array B320i RAID Controller is enabled in the server’s ROM-Based Setup Utility.  Previous versions of the component only updated the HPE B320i controller firmware which would result in customers running older H2xx HBA Option ROM firmware if the controller was switched from RAID mode to HBA mode by disabling the HPE Dynamic Smart Array B320i RAID Controller in the server’s ROM-Based Setup Utility.

• Modified the component installer to update both the HPE Dynamic Smart Array B320i RAID Controller firmware and the H2xx HBA Option ROM firmware when the HPE Dynamic Smart Array B320i RAID Controller is enabled in the server’s ROM-Based Setup Utility.  Previous versions of the component only updated the HPE B320i controller firmware which would result in customers running older H2xx HBA Option ROM firmware if the controller was switched from RAID mode to HBA mode by disabling the HPE Dynamic Smart Array B320i RAID Controller in the server’s ROM-Based Setup Utility.

Changed the settings in the SAS Expander to support disk discovery when 12Gb SAS HDDs are installed in the enclosure 

改变SAS扩展器中的设置，以便当机柜中安装12Gb SAS硬盘时，支持磁盘发现 

Changed the settings in the SAS Expander to support disk discovery when 12Gb SAS HDDs are installed in the enclosure 

改变SAS扩展器中的设置，以便当机柜中安装12Gb SAS硬盘时，支持磁盘发现 

• Few drives moved to Not Available state after power cycle.
• False positive in sherlock: Pcfg file JBOD ID and reported ID from JBOD do not match - but there were no mismatch in logs.

• Few drives moved to Not Available state after power cycle.
• False positive in sherlock: Pcfg file JBOD ID and reported ID from JBOD do not match - but there were no mismatch in logs.

• Fixed an issue causing fan speed to run at the maximum level due to a false error indication reported on early production hardware.

• 解决了导致风扇因早期版本软件报告的错误指示而在最大速度下运行的问题。

• Few drives moved to Not Available state after power cycle.
• False positive in sherlock: Pcfg file JBOD ID and reported ID from JBOD do not match - but there were no mismatch in logs.

• Few drives moved to Not Available state after power cycle.
• False positive in sherlock: Pcfg file JBOD ID and reported ID from JBOD do not match - but there were no mismatch in logs.

-Fixed an issue causing fan speed to run at the maximum level due to a false error indication reported on early production hardware.

-解决了导致风扇因早期版本软件报告的错误指示而在最大速度下运行的问题。

StoreEver LTO-6 Ultrium 6250 SAS Tape Drive

  Drive firmware version 35BD
  Supersedes 353D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-6 Ultrium 6650 SAS Tape Drive

  Drive firmware version O5DD
  Supersedes O53D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-5 Ultrium 3000 SAS Tape Drive

  Drive firmware version Z6ED
  Supersedes Z64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

StoreEver LTO-5 Ultrium 3280 SAS Tape Drive

  Drive firmware version X6ED
  Supersedes X64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

StoreEver LTO-6 Ultrium（傲群）6250 SAS 磁带机

  驱动器固件版本35D
替代353D

• 降低一类写故障 （0x5093） 事件的发生。
• 解决了磁带驱动器可能会报告了以下罕见情况读取 POSITION 命令后错误最后一个逻辑对象位置到主机。
• 解决了在 Inquiry Page CCh 报告产品 Id。

StoreEver LTO-6 Ultrium（傲群）6650 SAS 磁带机

  驱动器固件版本O5DD
  替代O53D

• 降低一类写故障 （0x5093） 事件的发生。
• 解决了磁带驱动器可能会报告了以下罕见情况读取 POSITION 命令后错误最后一个逻辑对象位置到主机。
• 解决了在 Inquiry Page CCh 报告产品 Id。

StoreEver LTO-5 Ultrium（傲群）3000 SAS 磁带机

  驱动器固件版本Z6ED
  替代Z64D

• 可能的驱动器重置 （assert） 在以前代码版本中引入的由于其他写入位置的 off-track 事件检查后。

StoreEver LTO-5 Ultrium（傲群）3280 SAS 磁带机

  驱动器固件版本X6ED
  替代X64D

• 可能的驱动器重置 （assert） 在以前代码版本中引入的由于其他写入位置的 off-track 事件检查后。

StoreEver LTO-6 Ultrium 6250 SAS Tape Drive

  Drive firmware version 35BD
  Supersedes 353D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-6 Ultrium 6650 SAS Tape Drive

  Drive firmware version O5DD
  Supersedes O53D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-5 Ultrium 3000 SAS Tape Drive

  Drive firmware version Z6ED
  Supersedes Z64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

StoreEver LTO-5 Ultrium 3280 SAS Tape Drive

  Drive firmware version X6ED
  Supersedes X64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

StoreEver LTO-6 Ultrium 6250 SAS Tape Drive

  Drive firmware version 35BD
  Supersedes 353D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-6 Ultrium 6650 SAS Tape Drive

  Drive firmware version O5DD
  Supersedes O53D

• Reduced the occurrence of a class of write failure (0x5093) events.
• Fixed a rare case where the tape drive could report an incorrect LAST LOGICAL OBJECT POSITION to the host after a READ POSITION command.
• Corrected the reporting of product IDs on Inquiry Page CCh.

StoreEver LTO-5 Ultrium 3000 SAS Tape Drive

  Drive firmware version Z6ED
  Supersedes Z64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

StoreEver LTO-5 Ultrium 3280 SAS Tape Drive

  Drive firmware version X6ED
  Supersedes X64D

• Possibility of a drive reset (assert) after an off-track event due to additional write position checks introduced in previous code release.

• Masked out errant failures due to charging of storage battery.
• Implemented cell voltage separation pre-failure warning for storage battery.
• iLO RESTful API output might display incorrect power supply information.
• iLO Federation group authentication errors might occur if you repeatedly add and remove groups during a query.
• An iLO RESTful API event subscription might be lost when DELETE and CREATE subscriptions occur at the same time that the transmitter waits to retry an action.
• During CAC smartcard authentication, the iLO RESTful API returns a session URI that incorrectly contains uppercase letters.
• In certain conditions, the Rest server becomes unavailable during a GET of the IELs.
• The iLO web interface language pack redirects to English.
• The iLO RESTful API output text represents upper threshold values as lower thresholds.
• The Linux openipmi driver does not poll the receive message queue if KCS host irq not enabled.
• The iLO RESTful API EthernetInterfaces link should be under the system/1 root resource, and not in the OEM section.
• SNMPv3 Engine Boot is not getting incremented on iLO reset.
• IPMI FRU read returns incorrect completion code for response too long.
• IPMI Get PEF Capabilities returns the number of valid table entries instead of the total number of table entries.  
• IPMI Set Boot Options for one time change for boot mode UEFI/Legacy fixed.  
• iLO restserver suspends when patching bad payload to external provider array.
• iLO REST API returned 500 internal error for a GET of systems/1/ leading to failed One View Profile Apply.
• iLO RESfulT API events are sending incorrect "Host" header when using IPv6.
• iLO time becomes Unset after update from 2.50 or prior to 2.54.

• Resolved an issue where in some cases iLO configuration data could be reset to default values after an iLO firmware upgrade (only affects Gen8 servers).
• Improved the mechanism to reset communication to the non-volatile storage (NAND) upon a warm reboot of the server (to reset an inaccessible NAND)
• NOTE: If the NAND is inaccessible when upgrading to iLO 4 2.54 firmware, an AC power pull may be necessary to reset an inaccessible NAND.

The following issues are resolved in version 2.53 (replaced by 2.54):

• Fixed an issue that led to POST Error: 333-iLO RESTful API Error - Unable to communicate with the iLO firmware when an SD card is was installed.
• Fix handling of logical drive indexing, found in cases where logical drives are not contiguous.
• Power loss occurs when hot-plugging RPS backplane during runtime.
• High fan noise occurs during ML110 Gen9 server system startup.
• IPMI Drive fault is incorrectly mapped to “In Failed Array” on drive sensors.
• Target node iLO is unavailable when an HPE OneView server profile is applied.
• The iLO RESTful API Software Inventory is incomplete when compared to the iLO web interface.
• The iLO RESTful API does not return complete version strings for all software components.
• Unable to use IPMI to “Set Serial Number” and “Set Product ID”.
• Fan failure and server shutdown occur on SL230s Gen8 servers.
• Reverse Address Translate returns bad values when called with hponcfg.
• The iLO RESTful API does not return the exact PCI device location for PCIe components.
• An incorrect device type is reported for the embedded SATA controller.
• Performing a NAND format may leave the REST provider registration in an unstable state.
• Solid state drives are intermittently reported as hard disk drives.   
• Fixed SNMP configuration read failure issue due to wrong FQDN trap destination configuration.  
• Fixed an issue that could lead to distorted video after setting boot mode to UEFI via RIBCL.
• False Self-Test error on USB port may be reported when an HPE ProLiant Gen8-Series server is powered Off (Advisory found at: http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-a00007681en_us)
• Improved error handling of option card AHS data that could result in excessive descriptor growth resulting in large AHS data files.

• Masked out errant failures due to charging of storage battery.
• Implemented cell voltage separation pre-failure warning for storage battery.
• iLO RESTful API output might display incorrect power supply information.
• iLO Federation group authentication errors might occur if you repeatedly add and remove groups during a query.
• An iLO RESTful API event subscription might be lost when DELETE and CREATE subscriptions occur at the same time that the transmitter waits to retry an action.
• During CAC smartcard authentication, the iLO RESTful API returns a session URI that incorrectly contains uppercase letters.
• In certain conditions, the Rest server becomes unavailable during a GET of the IELs.
• The iLO web interface language pack redirects to English.
• The iLO RESTful API output text represents upper threshold values as lower thresholds.
• The Linux openipmi driver does not poll the receive message queue if KCS host irq not enabled.
• The iLO RESTful API EthernetInterfaces link should be under the system/1 root resource, and not in the OEM section.
• SNMPv3 Engine Boot is not getting incremented on iLO reset.
• IPMI FRU read returns incorrect completion code for response too long.
• IPMI Get PEF Capabilities returns the number of valid table entries instead of the total number of table entries.  
• IPMI Set Boot Options for one time change for boot mode UEFI/Legacy fixed.  
• iLO restserver suspends when patching bad payload to external provider array.
• iLO REST API returned 500 internal error for a GET of systems/1/ leading to failed One View Profile Apply.
• iLO RESfulT API events are sending incorrect "Host" header when using IPv6.
• iLO time becomes Unset after update from 2.50 or prior to 2.54.

• Resolved an issue where in some cases iLO configuration data could be reset to default values after an iLO firmware upgrade (only affects Gen8 servers).
• Improved the mechanism to reset communication to the non-volatile storage (NAND) upon a warm reboot of the server (to reset an inaccessible NAND)
• NOTE: If the NAND is inaccessible when upgrading to iLO 4 2.54 firmware, an AC power pull may be necessary to reset an inaccessible NAND.

The following issues are resolved in version 2.53 (replaced by 2.54):

• Fixed an issue that led to POST Error: 333-iLO RESTful API Error - Unable to communicate with the iLO firmware when an SD card is was installed.
• Fix handling of logical drive indexing, found in cases where logical drives are not contiguous.
• Power loss occurs when hot-plugging RPS backplane during runtime.
• High fan noise occurs during ML110 Gen9 server system startup.
• IPMI Drive fault is incorrectly mapped to “In Failed Array” on drive sensors.
• Target node iLO is unavailable when an HPE OneView server profile is applied.
• The iLO RESTful API Software Inventory is incomplete when compared to the iLO web interface.
• The iLO RESTful API does not return complete version strings for all software components.
• Unable to use IPMI to “Set Serial Number” and “Set Product ID”.
• Fan failure and server shutdown occur on SL230s Gen8 servers.
• Reverse Address Translate returns bad values when called with hponcfg.
• The iLO RESTful API does not return the exact PCI device location for PCIe components.
• An incorrect device type is reported for the embedded SATA controller.
• Performing a NAND format may leave the REST provider registration in an unstable state.
• Solid state drives are intermittently reported as hard disk drives.   
• Fixed SNMP configuration read failure issue due to wrong FQDN trap destination configuration.  
• Fixed an issue that could lead to distorted video after setting boot mode to UEFI via RIBCL.
• False Self-Test error on USB port may be reported when an HPE ProLiant Gen8-Series server is powered Off (Advisory found at: http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-a00007681en_us)
• Improved error handling of option card AHS data that could result in excessive descriptor growth resulting in large AHS data files.

This product addresses a security issue reported on the following network adapters:

• HP Ethernet 10Gb 2-port 562SFLR-FP+ Adapter
• HP Ethernet 10Gb 2-port 562SFP+ Adapter

See the security bulletin HPSBHF03695 for more information.

This product addresses an issue where expected network devices don't appear in the Legacy BIOS Boot Order menu.

This product corrects an issue where UEFI FCoE boot path sends incorrect notification to Management Firmware (MFW) about a virtual function link change, which eventually results in a deadlock with virtual link down.

This product corrects an issue where the fallback Boot from SAN fails even though each port is mapped to a different Virtual Connect Bay and only one of the bays is powered off.

This product corrects an issue where the Smartlink function does not work properly in FCoE SAN boot environment when server 'Boot Mode' is 'Legacy BIOS Mode.'

This product corrects an issue where the FCoE UEFI driver is unable to find LUNs when multiple FCoE VLANs are enabled.

The firmware in this product addresses a system crash seen when enabling NPAR with SRIOV enabled.

The firmware in this product addresses an issue where a "NIC Initialization error" message is observed when PXE boot is attempted multiple times.

The firmware in this product addresses an issue where the NCSI pass-through does not function when configured for DHCP IP.

The firmware in this product addresses an issue where PXE boot fails in legacy boot mode.

Ths firmware in this product addresses an issue where the system PXE boots when PXE boot is disabled on the port.

Fixed reporting asynchronous events related to link transitions via the ATIO queue with the "Enable Asynchronous Event to Immediate Notify IOCB" option.

Fixed firmware system error (8002h) that occurred during target mode cleanup.

Fixed firmware system error that occurred during target mode cleanup with the presence of outstanding REC exchanges associated with SCSI exchanges.

Fixed login collision that occurred in private loop topology.

• unexpected behavior in which ProLiant Gen 9 c-class server blades equipped with 650FLB or 650M adapters may not complete Power-On Self Test (POST)
• unexpected behavior which occurred after upgrading firmware to 11.1.183.23, resulting in network ports losing connections
• unexpected behavior in which 650FLB network ports were inadvertently assigned the same MAC address, resulting in network packets being sent to the incorrect ports.
• behavior in which Microsoft Windows terminates unexpectedly

• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed failure instances when initiating FLR in the Physical Function.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).

Fixes in 14.14.2204:

• Fixed an issue which prevented MAC address changes by to driver to be reflected in the OBCC and NC-SI interfaces.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE cards.
• Fixed an issue which caused a link down in Port 2 when unplugging the cable from Port 1.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE).
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Enabled RoCE IPv4 Multicast. This prevents MCG command from failing when an IPv4 is mapped to an IPv6 address.
• If the PF driver or the tool (e.g. ethtool) use PAOS DOWN command (e.g. by ifconfig down or ip link set down), loopback traffic is blocked for all functions on this port (PF<->VFs / VF<->VF) In Multihost loopback, the traffic will be blocked once the firmware receives the PAOS down command from all PFs. However, the loopback traffic will not be blocked when the port is down  due to the physical link (for example: cable plugged out, switch port down).
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of eSwitch cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.

• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed failure instances when initiating FLR in the Physical Function.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).

Fixes in 14.14.2200:

• Fixed an issue which prevented MAC address changes by to driver to be reflected in the OBCC and NC-SI interfaces.
• Added protection from IOPX thermal diode destabilization to prevent UEFI IPv6 PXE boot failure on ConnectX-4 Lx 25GE cards.
• Fixed an issue which caused a link down in Port 2 when unplugging the cable from Port 1.
• In some cases, a Bit Error Rate is not optimal on 10G/40G links.
• Instability of Link Training Flow occurs during 100G Auto-Negotiation.
• Fixed a rare issue which caused the command to hang when moved the QP to RESET and back to RTS.
• Improved RDMA READ bandwidth under packet lost scenario.
• Added support for pnat = 1 in HCA access_reg command as required by the ibdiagnet tool.
• Fixed the LLDP OCBB response: return value is now ascii.
• Fixed a very rare NMI issue during PXE cycles.
• Increased the steering hash tables static size from 128 to a maximum of 32K entries.
• Prevented miscalculation of module temperature when using 100Gb/s cables (OPN: MFA1A00-Cxxx for 100GbE).
• Reduced one hop for Unicast RX steering, steering pipes balancing.
• Non-volatile configuration of Port Type TLV more than 50 times might cause system hang.
• Enabled RoCE IPv4 Multicast. This prevents MCG command from failing when an IPv4 is mapped to an IPv6 address.
• If the PF driver or the tool (e.g. ethtool) use PAOS DOWN command (e.g. by ifconfig down or ip link set down), loopback traffic is blocked for all functions on this port (PF<->VFs / VF<->VF) In Multihost loopback, the traffic will be blocked once the firmware receives the PAOS down command from all PFs. However, the loopback traffic will not be blocked when the port is down  due to the physical link (for example: cable plugged out, switch port down).
• Fixed a 25G and 50G link issue when Clause 91 RS FEC was active.
• Added a missing invalidation of eSwitch cache upon FLR which caused the upcoming driver load to either fail or not to be able to transmit.

• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.
• Fixed performance issues causing slow performance when running in NO-DRAM-NIC mode.
• Disabled High Rate Steering mode in the INI to enable its compatibility with NC-SI over VLAN.
• Fixed failure instances when initiating FLR in the Physical Function.
• Fixed a wrong returned status in cable info MAD when the cable was not connected.
• Fixed the length calculation of UDP. The incorrect UDP length in the CNP packet caused miss-calculation of the ICRC.
• Fixed a completion error issue when ECN was enabled. The ECN usage caused ordering errors in completion queues (CQ).

• Fixed an issue which caused packet transmission to get stuck when the software tried to send pause frames with dmac equal to one of the device's MAC addresses.
• Fixed an issue which caused a firmware internal error when handling QP alternative context.
• Fixed an issue which caused an internal firmware error when APM changed the QPs port mapping.
• Fixed an issue which caused NVRAM to get stuck when it filled non-valid information in TLV.
• Fixed an issue which caused lack of IB traffic on SR-IOV VPI.
• Fixed a race in handling a duplicated “read request from middle”.
• Fixed an issue which caused NVCONFIG to fail when the number of sector was set to 1 and the sector was zeroed.
• Fixed an issue which caused TX traffic to stop when the message MTU size was larger than QP.mtu.
• MLNX_OEM command GET_TEMP returned a wrong value in the max_temp field.
• Fixed a default hardware configuration issue which caused RDP over IPv4 traffic to be dropped.

• Fixed an issue with the SAS connector element which reported invalid connector type/physical link for disabled PHYs.
• Fixed the Logical Link Rate because the Rate was not set properly when PHY is disabled.

Problems Fixed in version 3.30(B):

• When attempting to install firmware under Microsoft Windows Server 2012 R2, the firmware installation would fail resulting in an APPCRASH exception error.

• 修复SAS连接单元为禁用的物理层报告无效的连接器类型/物理连接的问题。
• 修复禁用物理层时，因逻辑链路速率未正确设置导致的问题。

3.30(B)版本解决的问题：

• 尝试在Microsoft Windows Server 2012 R2下安装固件时失败，导致APPCRASH异常错误。

• Fixed an issue with the SAS connector element which reported invalid connector type/physical link for disabled PHYs.
• Fixed the Logical Link Rate because the Rate was not set properly when PHY is disabled.

• 修复SAS连接单元为禁用的物理层报告无效的连接器类型/物理连接的问题。
• 修复禁用物理层时，因逻辑链路速率未正确设置导致的问题。

• Fixed an issue with the SAS connector element which reported invalid connector type/physical link for disabled PHYs.
• Fixed the Logical Link Rate because the Rate was not set properly when PHY is disabled.

• Fixed an issue with the SAS connector element which reported invalid connector type/physical link for disabled PHYs.
• Fixed the Logical Link Rate because the Rate was not set properly when PHY is disabled.

• Fixed an issue with the SAS connector element which reported invalid connector type/physical link for disabled PHYs.
• Fixed the Logical Link Rate because the Rate was not set properly when PHY is disabled.

• 修复SAS连接单元为禁用的物理层报告无效的连接器类型/物理连接的问题。
• 修复禁用物理层时，因逻辑链路速率未正确设置导致的问题。

Ver. 2016.03.07 (B) provides the same system ROM image as ver. 2016.03.07. The new ver. 2016.03.07 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2016.03.07 (B) if the system has been previously flashed with System ROM ver. 2016.03.07.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with AMD Opteron 6300 series processors in which the processor may experience unpredictable system behavior in virtualized environments due to an issue with the revision of the AMD microcode included in the 09/03/2014 and 11/02/2014 revisions of the System ROM. Only the 09/03/2014 and 11/02/2014 revisions of the System ROM is impacted by this issue. This revision of the System ROM contains an updated version of AMD's microcode that addresses this issue. This issue is NOT unique to HPE ProLiant servers and could impact any system utilizing affected processors with the affected AMD microcode. Due to the potential severity of the issue addressed in this revision of the System ROM, it is highly recommended that the System ROM be upgraded for impacted systems.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2016.03.07 (B) provides the same system ROM image as ver. 2016.03.07. The new ver. 2016.03.07 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2016.03.07 (B) if the system has been previously flashed with System ROM ver. 2016.03.07.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with AMD Opteron 6300 series processors in which the processor may experience unpredictable system behavior in virtualized environments due to an issue with the revision of the AMD microcode included in the 09/03/2014 revision of the System ROM. Only the 09/03/2014 revision of the System ROM is impacted by this issue. This revision of the System ROM contains an updated version of AMD's microcode that addresses this issue. This issue is NOT unique to HPE ProLiant servers and could impact any system utilizing affected processors with the affected AMD microcode. Due to the potential severity of the issue addressed in this revision of the System ROM, it is highly recommended that the System ROM be upgraded for impacted systems.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2014.11.03 (B) provides the same system ROM image as ver. 2014.11.03. The new ver. 2014.11.03 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.11.03 (B) if the system has been previously flashed with System ROM ver. 2014.11.03.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where systems configured with Integrated Lights-Out (iLO) Firmware version 2.00 or later may not be able to properly configure the platform properly through HP Virtual Connect. This issue is not seen with earlier versions of iLO firmware.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2015.06.01 (B) provides the same system ROM image as ver. 2015.06.01. The new ver. 2015.06.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.06.01 (B) if the system has been previously flashed with System ROM ver. 2015.06.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where systems configured with the ATI S4000x GPU adapter may experience unexpected shutdowns due to a thermal event.

Known Issues:

None

None

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where systems configured with the ATI S4000x GPU adapter may experience unexpected shutdowns due to a thermal event.

Known Issues:

None

Ver. 2015.12.01 (B) provides the same system ROM image as ver. 2015.12.01. The new ver. 2015.12.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.12.01 (B) if the system has been previously flashed with System ROM ver. 2015.12.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where systems configured with certain 32GB LR-DIMMs could intermittently experience an issue where memory would not train properly and be unavailable to the operating system.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2014.08.02 (B) provides the same system ROM image as ver. 2014.08.02. The new ver. 2014.08.02 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.08.02 (B) if the system has been previously flashed with System ROM ver. 2014.08.02.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

Ver. 2014.08.02 (C) provides the same system ROM image as ver. 2014.08.02 (B). The new ver. 2014.08.02 (C) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.08.02 (C) if the system has been previously flashed with System ROM ver. 2014.08.02.

This System ROM update is recommended to ensure that the system cooling is operating at maximum efficiency. Ver. 2014.08.02 (B) contains updates to the customer release notes and is functionally equivalent to ver. 2014.08.02.  It is not necessary to upgrade with Revision B if the previous Revision was used to upgrade the system ROM to version 2014.08.02. PLease refer to the Customer Advisory at http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04619916 for additional details.

Firmware Dependencies:

None

Problems Fixed:

Addressed a rare issue where systems configured with Intel Xeon E5 2600 v2 processors and Registered DIMMs (RDIMMs) in a 2 DIMM per Channel or 3 DIMM per Channel configuration may experience a 207 - Memory Initialization error message where certain DIMMs may not be initialized properly. This issue is seen intermittently after a system reboot.

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

None

This System ROM update is recommended to ensure that the system cooling is operating at maximum efficiency. Ver. 2014.08.02 (B) contains updates to the customer release notes and is functionally equivalent to ver. 2014.08.02.  It is not necessary to upgrade with Revision B if the previous Revision was used to upgrade the system ROM to version 2014.08.02. PLease refer to the Customer Advisory at http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04619916 for additional details.

Firmware Dependencies:

None

Problems Fixed:

Addressed a rare issue where systems configured with Intel Xeon E5 2600 v2 processors and Registered DIMMs (RDIMMs) in a 2 DIMM per Channel or 3 DIMM per Channel configuration may experience a 207 - Memory Initialization error message where certain DIMMs may not be initialized properly. This issue is seen intermittently after a system reboot.

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

None

Ver. 2015.07.01 (B) provides the same system ROM image as ver. 2015.07.01. The new ver. 2015.07.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.07.01 (B) if the system has been previously flashed with System ROM ver. 2015.07.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where a device interrupt may not be handled properly and result in a lost interrupt or an uncorrectable machine check exception. This issue is NOT unique to HP servers. HP recommends that users experiencing these issues update to this revision of the System ROM before replacing any hardware components.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2015.07.01 (B) provides the same system ROM image as ver. 2015.07.01. The new ver. 2015.07.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.07.01 (B) if the system has been previously flashed with System ROM ver. 2015.07.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where a device interrupt may not be handled properly and result in a lost interrupt or an uncorrectable machine check exception. This issue is NOT unique to HP servers. HP recommends that users experiencing these issues update to this revision of the System ROM before replacing any hardware components.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2015.07.01 (B) provides the same system ROM image as ver. 2015.07.01. The new ver. 2015.07.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.07.01 (B) if the system has been previously flashed with System ROM ver. 2015.07.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where a device interrupt may not be handled properly and result in a lost interrupt or an uncorrectable machine check exception. This issue is NOT unique to HP servers. HP recommends that users experiencing these issues update to this revision of the System ROM before replacing any hardware components.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2014.08.02 (B) provides the same system ROM image as ver. 2014.08.02. The new ver. 2014.08.02 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.08.02 (B) if the system has been previously flashed with System ROM ver. 2014.08.02.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Known Issues:

Ver. 2015.07.01 (B) provides the same system ROM image as ver. 2015.07.01. The new ver. 2015.07.01 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.07.01 (B) if the system has been previously flashed with System ROM ver. 2015.07.01.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where a device interrupt may not be handled properly and result in a lost interrupt or an uncorrectable machine check exception. This issue is NOT unique to HP servers. HP recommends that users experiencing these issues update to this revision of the System ROM before replacing any hardware components.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2014.08.03 (B) provides the same system ROM image as ver. 2014.08.03. The new ver. 2014.08.03 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.08.03 (B) if the system has been previously flashed with System ROM ver. 2014.08.03.

Firmware Dependencies:

None

Problems Fixed:

Addressed a rare issue where systems configured with Intel Xeon E5 2600 v2 processors and Registered DIMMs (RDIMMs) in a 2 DIMM per Channel or 3 DIMM per Channel configuration may experience a 207 - Memory Initialization error message where certain DIMMs may not be initialized properly. This issue is seen intermittently after a system reboot.

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Addressed an extremely rare issue where the server may experience an unexpected shutdown, usually seen as a power fault in the iLO Integrated Management Log (IML), when configured with certain Intel Xeon E5-4600 series processors.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where the server may become unresponsive during POST when an optional Video card is installed.

Addressed an issue where certain option cards that request very large amounts of non-prefetchable memory will not function properly. This issue only impacts a very small number of non-HP option cards.

Addressed an extremely rare issue where the server may experience an unexpected shutdown, usually seen as a power fault in the iLO Integrated Management Log (IML), when configured with certain Intel Xeon E5-4600 series processors.

Known Issues:

Ver. 2014.03.28 (B) provides the same system ROM image as ver. 2014.03.28. The new ver. 2014.03.28 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2014.03.28 (B) if the system has been previously flashed with System ROM ver. 2014.03.28.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where servers using the 03/08/2014 revision of the System ROM caused a problem with a Trusted Platform Module (TPM) operating system certification test. This issue has no known impact with TPM functionality under normal operating system environments. This problem only affects servers with the 03/08/2014 revision of the System ROM.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2015.04.02 (B) provides the same system ROM image as ver. 2015.04.02. The new ver. 2015.04.02 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.04.02 (B) if the system has been previously flashed with System ROM ver. 2015.04.02.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue with excessively loud fan noise when either SATA AHCI support is enabled in the Embedded SATA Configuration menu in RBSU (ROM-Based Setup Utility) or when Dynamic HP Smart Array B120i RAID Support is enabled in the Embedded SATA Configuration menu in RBSU (ROM-Based Setup Utility) and the Dynamic HP Smart Array B120i RAID operating system driver is not loaded.

Addressed an issue where a system under heavy stress could experience an uncorrectable machine check. This issue is not unique to HP. It is recommended that customers experiencing this issue update to this version of the System ROM before replacing any hardware components.

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Addressed an issue where a system under heavy stress could experience an uncorrectable machine check. This issue is not unique to HP. It is recommended that customers experiencing this issue update to this version of the System ROM before replacing any hardware components.

Known Issues:

Ver. 2016.01.18 (B) provides the same system ROM image as ver. 2016.01.18. The new ver. 2016.01.18 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2016.01.18 (B) if the system has been previously flashed with System ROM ver. 2016.01.18.

Firmware Dependencies:

None

Problems Fixed:

Addressed an issue where incorrect threshold values of CPU temperature sensors were reported in HP System Management Homepage (SMH).

Known Issues:

None

Firmware Dependencies:

Problems Fixed:

Known Issues:

Ver. 2013.08.16 (D) provides the same system ROM image as ver. 2013.08.16 (C). The new ver. 2013.08.16 (D) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2013.08.16 (D) if the system has been previously flashed with System ROM ver. 2013.08.16.

Component packaging has been updated; no impact to product’s functionality.

Firmware Dependencies:

None

Problems Fixed:

Resolved an issue where the IRQ setting could not be changed in the ROM-Based Setup Utility (RBSU) for the BL110i SATA RAID device.

Removed the Removable Flash Media Boot Sequence option in the ROM-Based Setup Utility (RBSU) as the HP ProLiant ML10 does not support an internal SD card slot.

Updated text (for non-English modes) in the ROM-Based Setup Utility (RBSU).

Known Issues:

None

Problems Fixed:

Removed the Removable Flash Media Boot Sequence option in the ROM-Based Setup Utility (RBSU) as the HP ProLiant ML10 does not support an internal SD card slot.

Updated text (for non-English modes) in the ROM-Based Setup Utility (RBSU).

Known Issues:

Ver. 2015.01.26 (B) provides the same system ROM image as ver. 2015.01.26. The new ver. 2015.01.26 (B) adds support to perform the Online ROM Flash with Microsoft Windows Server 2016.  The user does not need to flash the system ROM with ver. 2015.01.26 (B) if the system has been previously flashed with System ROM ver. 2015.01.26.

The firmware for the System Programmable Logic Device must be upgraded in addition to the System ROM. Please see the Firmware Dependencies section below.

Firmware Dependencies:

System Programmable Logic Device version 0x15 or later is required. The System Programmamable Logic Device firmware is available for download at the following links:

Online Flash Component for Linux - System Programmable Logic Device (HP ProLiant XL220a Gen8 v2) version 0x15: https://downloads.hpe.com/pub/softlib2/software1/sc-linux-fw/p1150180434/v103815

Online Flash Component for Win64 - System Programmable Logic Device (HP ProLiant XL220a Gen8 v2) version 0x15: https://downloads.hpe.com/pub/softlib2/software1/sc-windows-fw/p1281588026/v103857

Problems Fixed:

Addressed an issue where a system under heavy stress could experience an uncorrectable machine check. This issue will be reported in the Integrated Management Log with the following error details (Uncorrrectable Machine Check Exception: APIC ID 0x00000004, Bank 0x00000003, Status 0xF2000000'00800400, Address 0x00000000'00000000, Misc 0x00000000'00000000). This issue is not unique to HP. It is recommended that customers experiencing this issue update to this version of the System ROM before replacing any hardware components.

Addressed an issue where an uncorrectable machine check exception can cause the server to reboot continuously or stop responding. This solution requires the System Programmable Logic Device be upgraded to version 0x15 or later.

Known Issues:

None

The firmware for the System Programmable Logic Device must be upgraded in addition to the System ROM. Please see the Firmware Dependencies section below.

Firmware Dependencies:

System Programmable Logic Device version 0x15 or later is required. The System Programmamable Logic Device firmware is available for download at the following links:

Online Flash Component for Linux - System Programmable Logic Device (HP ProLiant XL220a Gen8 v2) version 0x15: https://downloads.hpe.com/pub/softlib2/software1/sc-linux-fw/p1150180434/v103815

Online Flash Component for Win64 - System Programmable Logic Device (HP ProLiant XL220a Gen8 v2) version 0x15: https://downloads.hpe.com/pub/softlib2/software1/sc-windows-fw/p1281588026/v103857

Problems Fixed:

Addressed an issue where a system under heavy stress could experience an uncorrectable machine check. This issue will be reported in the Integrated Management Log with the following error details (Uncorrrectable Machine Check Exception: APIC ID 0x00000004, Bank 0x00000003, Status 0xF2000000'00800400, Address 0x00000000'00000000, Misc 0x00000000'00000000). This issue is not unique to HP. It is recommended that customers experiencing this issue update to this version of the System ROM before replacing any hardware components.

Addressed an issue where an uncorrectable machine check exception can cause the server to reboot continuously or stop responding. This solution requires the System Programmable Logic Device be upgraded to version 0x15 or later.

Known Issues:

None

• Improved integration with HP Smart Update Manager

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

Problems Fixed in version 0.50(B):

• When attempting to install firmware under Microsoft Windows Server 2012 R2, the firmware installation would fail resulting in an APPCRASH exception error.

Problems Fixed in version 0.50 (C):

• Attempts to downgrade HP 512MB Flash Backed Write Cache for B-Series Smart Array controller firmware were reported to be successful by the deployment tool, but the installed firmware version remained the same. Now, using component version 0.50(B), if a firmware downgrade is attempted for an HP 512MB Flash Backed Write Cache for B-Series Smart Array  controller, then a message displays to indicate that downgrading firmware is not supported. For additional details see customer advisory c04725368.

Firmware Dependencies:

Problems Fixed:

Known Issues:

固件附属项：

已解决的问题：

已知问题：

Firmware Dependencies:

Problems Fixed:

Known Issues:

Firmware Dependencies:

Problems Fixed:

Known Issues:

• Addressed an issue where OA "update iLO all" command fails in an enclosure with maximum Blades.
• Addressed an issue where a Warning Alert  was wrongly sent when a fan is reseated in an enclosure
• Addressed an issue where the port mapping information for 560M Izzy adapter Mezz controller was not displayed correctly.
• Addressed an issue where Remote Syslog logging would fail when OA failover happened in an IPv6 only environment.
• Enhanced OA to bring the server from a power throttled state back to normal power state upon an OA reboot to circumvent an unwarranted emergency brake.
• Fixed an issue where the Active and Standby OAs can have the same IP address in some rare situations.
• Resolved an issue where a Gen9 server’s host name gets cleared when the blade is rebooted.
• Addressed an issue where server blade Power ON will be delayed in enclosures with OA Firmware Version 4.60 and managed by HPE OneView, when the OA module is reset until OneView refreshes the servers.

Security

The following security vulnerabilities were fixed:

• CVE-2016-5387– Addressed a vulnerability which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request.
• CVE-2016-2183- Addressed a vulnerability against TLS ciphers with 64bit block size in which makes it easier for remote attackers to obtain cleartext data via an attack against a long-duration encrypted session
• CVE-2016-6515 - Addressed a vulnerability in OpenSSH which did not limit password lengths for password authentication, which allows remote attackers to cause a denial of service via a long string.
• CVE-2015-8215 - Addressed a vulnerability IPv6 stack which does not validate attempted changes to the MTU value, which allows context-dependent attackers to cause a denial of service.
• Addressed issue where in Onboard Administrator was vulnerable to Buffer overflow.
• Added the HSTS[HTTP strict transport security] support  in OA.
• Addressed a memory corruption vulnerability in the post-authentication sshd process.

Issues and workarounds

Browsers

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

FIPS

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

IRC

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

EFM

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

• Addressed an issue where OA "update iLO all" command fails in an enclosure with maximum Blades.
• Addressed an issue where a Warning Alert  was wrongly sent when a fan is reseated in an enclosure
• Addressed an issue where the port mapping information for 560M Izzy adapter Mezz controller was not displayed correctly.
• Addressed an issue where Remote Syslog logging would fail when OA failover happened in an IPv6 only environment.
• Enhanced OA to bring the server from a power throttled state back to normal power state upon an OA reboot to circumvent an unwarranted emergency brake.
• Fixed an issue where the Active and Standby OAs can have the same IP address in some rare situations.
• Resolved an issue where a Gen9 server’s host name gets cleared when the blade is rebooted.
• Addressed an issue where server blade Power ON will be delayed in enclosures with OA Firmware Version 4.60 and managed by HPE OneView, when the OA module is reset until OneView refreshes the servers.

Security

The following security vulnerabilities were fixed:

• CVE-2016-5387– Addressed a vulnerability which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request.
• CVE-2016-2183- Addressed a vulnerability against TLS ciphers with 64bit block size in which makes it easier for remote attackers to obtain cleartext data via an attack against a long-duration encrypted session
• CVE-2016-6515 - Addressed a vulnerability in OpenSSH which did not limit password lengths for password authentication, which allows remote attackers to cause a denial of service via a long string.
• CVE-2015-8215 - Addressed a vulnerability IPv6 stack which does not validate attempted changes to the MTU value, which allows context-dependent attackers to cause a denial of service.
• Addressed issue where in Onboard Administrator was vulnerable to Buffer overflow.
• Added the HSTS[HTTP strict transport security] support  in OA.
• Addressed a memory corruption vulnerability in the post-authentication sshd process.

Issues and workarounds

Browsers

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

FIPS

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

IRC

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

EFM

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

• Addressed an issue where EFM was reporting success while firmware update of iLO 4 failed.
• Fixed an issue where OA might lose its IP address after OA firmware upgrade when ENCLOSURE_IP_MODE was enabled .
• Fixed an issue where all iLOs were reset after making EBIPA changes to an empty bay. Now only the specific iLOs are reset.
• Resolved an issue where iLOs became inaccessible after OA failover occurs with iLOs configured in EBIPA for IPv6. This occurs when an external router in the management network is configured to send Router Advertisements.
• Corrected the type mismatch of OID cpqRackCommonEnclosureManagerLocation which could cause failures in the SNMP clients. The definition is changed from STRING to INTEGER.
• Resolved an issue where information on only the last server NIC port of a multiport adaptor was shown on GUI and CLI. Now details of all the server NIC ports are displayed.
• Resolved an issue of time synchronization between active and standby OA when date and time settings were changed from “Manual” to “NTP”.
• Resolved EFM discovery/update failure when the server power policy in the EFM configuration is set to “must be off”.

The following security vulnerabilities were fixed:

• Security
• CVE-2016-2108 – Addressed a vulnerability in ASN.1 implementation in OpenSSL that can cause Denial Of Service via  any field in crafted serialized data
• CVE-2015-8605 - UDP payload length not properly checked. Addressed a vulnerability where a badly formed packet with an invalid IPv4 UDP length field can cause a DHCP server, client, or relay program to terminate abnormally.
• CVE-2012-3954 - Fixed a memory leak issue in DHCPv6 daemon that could result in out of memory condition in OA.
• CVE-2016-0797 and CVE-2016-0799 - Addressed a vulnerability in OpenSSL that could enable security attacks by passing large amount of untrusted data to certain functions in OpenSSL.
• CVE-2015-8605 - Addressed a vulnerability in IPv4 stack that can be exploited to cause a Denial Of Service via an invalid length field in a UDP IPv4 packet.
• CVE-2015-3196 - Addressed a vulnerability in OpenSSL that results in Denial Of Service by remote servers via a crafted ServerKeyExchange message.
• CVE-2015-3195 - Addressed a vulnerability in OpenSSL that can be exploited to obtain sensitive information from process memory by triggering a decoding failure in a PKCS#7 or CMS application.
• CVE-2015-6564 - Addressed a vulnerability in OpenSSH that might allow local users to gain privileges by leveraging control of the sshd uid to send an unexpectedly early MONITOR_REQ_PAM_FREE_CTX request.
• CVE-2015-6563 - Addressed a vulnerability in OpenSSH that allows local users to conduct impersonation attacks by leveraging any SSH login access in conjunction with control of the sshd uid.
• CVE-2015-5621 - Addressed a vulnerability in Net-SNMP that causes a Denial Of Service and possibly allows execution of arbitrary code via a crafted packet.
• CVE-2015-5364 and CVE-2015-5366 - Addressed a vulnerability in UDP stack that can be exploited in UDP flood scenario to cause Denial Of Service in the OA.

• 解决了固件更新iLO 4时出现故障，但EFM报告成功的问题。
• 解决了启用ENCLOSURE_IP_MODE时，当OA固件升级后，OA可能会丢失其IP地址的问题。
• 解决了完成对某个闲置托架的EBIPA更改后，重置所有iLO的问题。现在仅重置特定的iLO。
• 解决了在用于IPv6的EBIPA中配置iLO，当OA发生故障后，iLO变得无法访问的问题。在管理网络中的外部路由器被配置为发送路由器广播时出现此问题。
• 纠正了可能导致SNMP客户端故障的OID cpqRackCommonEnclosureManagerLocation类型不匹配的问题。定义从字符串改为整数。
• 解决了在GUI和CLI只显示多端口适配器的最后一个服务器NIC端口的问题。现在显示所有服务器NIC端口的详细信息。
• 解决了当日期和时间设置从"手动"更改为"NTP"时，活动和备用OA之间时间同步的问题。
• 解决了在EFM配置中，将服务器启动策略设置为“必须关闭”时，出现EFM发现/更新故障的问题。

已修复以下安全漏洞：

• 安全性
• CVE-2016-2108 – 修复了OpenSSL中ASN.1实施的一个漏洞，该漏洞会通过编造的序列数据中的任何字段造成拒绝服务
• CVE-2015-8605 - 未正确检查UDP有效载荷。修复了带无效IPv4 UDP长度字段的未正确形成的数据包导致DHCP服务器、客户端或中继程序异常终止的漏洞。
• CVE-2012-3954 - 修复了DHCPv6后台进程内存泄漏的问题，其可能造成OA内存不足。
• CVE-2016-0797 and CVE-2016-0799 - 修复了一个OpenSSL漏洞，其可通过向OpenSSL的某些函数传递大量不可信数据，从而启用安全攻击。
• CVE-2015-8605 - 修复了一个IPv4堆栈中的漏洞，可利用该漏洞通过UDP IPv4包中的一个无效长度字段造成拒绝服务。
• CVE-2015-3196 - 修复了OpenSSL中的一个漏洞，其可通过编造的ServerKeyExchange消息，利用远程服务造成拒绝服务。
• CVE-2015-3195 - 修复了OpenSSL中的一个漏洞，可利用该漏洞在PKCS#7或CMS应用程序中触发解码故障，从而从进程内存获得敏感信息。
• CVE-2015-6564 - 修复了OpenSSH中的一个漏洞，该漏洞利用对sshd uid的控制而发送一个意外的早期MONITOR_REQ_PAM_FREE_CTX请求，从而使本地用户获得特权。
• CVE-2015-6563 - 修复了OpenSSH中的一个漏洞，该漏洞利用任何SSH登录访问结合对sshd uid的控制，从而使本地用户进行身份模拟攻击。
• CVE-2015-5621 - 修复了Net-SNMP中的一个漏洞，该漏洞通过编造的数据包导致拒绝服务，还可能允许执行任意代码。
• CVE-2015-5364和CVE-2015-5366 - 修复了UDP堆栈中的一个漏洞，可利用该漏洞进行UDP洪水攻击，从而引起OA拒绝服务。

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPDK resolves this issue.

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

• This firmware contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

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

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• Minimum firmware required - HPD7. HPDA drive firmware will fail when downgrading to versions below HPD7.

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• This firmware corrects a condition seen on HP Gen8 smart carriers where drives used as Hot Spares continuously indicate drive activity, when the drive is actually in Hot Spare standby mode.

• This firmware reduces the possibility of the controller and drive not properly negotiating link signaling, resulting in the controller not being able to identify a drive attached to a particular port/slot during system boot up.  This firmware improves signal quality between the drive and the controller.

• This firmware reduces the possibility of the controller and drive not properly negotiating link signaling, resulting in the controller not being able to identify a drive attached to a particular port/slot during system boot up.  This firmware improves signal quality between the drive and the controller.

• HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD8 resolves this issue.

• HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD8 resolves this issue.

• Drives could become unresponsive due to unexpected responses from the serial port diagnostic debug connection.

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

• Drive self-test did not complete within the specified time.
• During a fully cached workload, SMART would report incorrect temperature values.

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

• This firmware reduces the possibility of the controller and drive not properly negotiating link signaling, resulting in the controller not being able to identify a drive attached to a particular port/slot during system boot up.  This firmware improves signal quality between the drive and the controller.

• This firmware reduces the possibility of the controller and drive not properly negotiating link signaling, resulting in the controller not being able to identify a drive attached to a particular port/slot during system boot up.  This firmware improves signal quality between the drive and the controller.

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD5 resolves this issue.

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

• Reliability enhancement for applications that write data to a narrow range of tracks.
• New SMART trip when device senses an abnormal change in the motor electric current.

• In previous firmware revisions when the solid state drive was issued a Report Support Operation Code (RSOC) command (A3h) and the reporting options field was set to 001 , the drive incorrectly responded with 05/24/00 indicating that the RSOC command was not supported. The error was logged in the system log files. The drive should have communicated non-support using the Command Data Parameter (CDP) format. The firmware now complies with the RSOC industry standard specification.

• This firmware corrects a condition where a supported coded operation returned a 05/24/00 error. This error was being improperly handled and resulted in the server returning a parameter that implied the server did not support the requested command.

• 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 HPGD prevents this condition from occurring.

• 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 HPGD prevents this condition from occurring.

• HPG5 firmware improves drive reliability where disk drives are exposed to long periods of host inactivity which exceed 1 second.

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

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

• ProLiant servers would power down due a hard drive over temperature condition that was falsely reported. HPD4 firmware resolves this issue.

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

• This firmware improves HDD reliability when HDDs are exposed to long periods of host inactivity that exceed 1 second. HDDs may become unresponsive when using HDD firmware prior to version HPDA. 

• This firmware also contains a change which prevents an incorrect reassign status of a repaired sector from being logged.

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

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

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

• This firmware contains general maintenance release and code improvement items. Drives built with or upgraded to hard drive firmware version HPG4 should not be downgraded to an earlier version of firmware due to hard drive manufacturing process changes.

• The drives’ media errors were not properly interpreted as invalid data which allows the invalid data to be used by applications. For additional information and a list of affected SATA hard drive models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446

• The system did not recognize some drives after a power-cycle. This is due to the drive initialization process being interrupted by a reset, causing the drive to take more time than allotted to report commands.

     This firmware corrects the following:

• Internal resets caused commands to time out which may have impacted performance.
• Internal drive DRAM handling that resulted in Unrecovered Read Errors.

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

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

• This firmware corrects a possible condition in which stale data might be written to the disk.  This results in unexpected data being returned in subsequent requests.  This data issue has been duplicated in laboratory firmware stress tests.

• The system did not recognize some drives after a power-cycle. This is due to the drive initialization process being interrupted by a reset, causing the drive to take more time than allotted to report commands.

     This firmware corrects the following:

• Internal resets caused commands to time out which may have impacted performance.
• Internal drive DRAM handling that resulted in Unrecovered Read Errors.

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

• 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 HPG6 prevents this condition from occurring.
• This firmware corrects “command timeouts” and seek errors which can result in poor performance or a Device Fault condition, the latter of which will result in the drive failed by the Controller or sub system.

• 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 HPG6 prevents this condition from occurring.
• This firmware corrects “command timeouts” and seek errors which can result in poor performance or a Device Fault condition, the latter of which will result in the drive failed by the Controller or sub system.

•      HP ProLiant servers would power down due a hard drive overtemp condition that was falsely reported. Hard disk drive firmware HPD9 resolves this issue.

• HP ProLiant servers would power down due a hard drive over temp condition that was falsely reported. Hard disk drive firmware HPGK resolves this issue.

• 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 HPGJ prevents this condition from occurring.

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

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

• HPD9 firmware prevents a condition in which data fails to be committed to disk after the host issues a hard reset in a lab stress test environment with write cache enabled.

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

• Corrected a medium level assert that can occur when the host issues resets after >250ms  of idle time. If a drive is affected by the issue, it might display reduced performance and possibly would cease to operate. A hot plug removal and insertion of the affected drive temporarily resolves this issue. Update to drive firmware version HPGE to resolve this issue.

• 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 HPGC prevents this condition from occurring.

• An issue was found where the drive responded with a format error if power-cycled multiple times while in the process of un-mapping Logical Block Addresses (LBA). HPD5 firmware adds additional protection during power-cycles to ensure that the drive can recover its LBA to Physical Memory map.

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

• This firmware corrects the possibility of the drive becoming unresponsive and requiring a power cycle following a soft system reboot. This behavior appears as if the drive is no longer attached to the system following the system soft reboot. It is most often observed during Operating System Installation but can occur following any system soft reboot.

• This firmware corrects the possibility of the drive becoming unresponsive and requiring a power cycle following a soft system reboot. This behavior appears as if the drive is no longer attached to the system following the system soft reboot. It is most often observed during Operating System Installation but can occur following any system soft reboot.