** CRITICAL ** HP 2000i Modular Smart Array controller firmware - HP Business Sup...

Page 1 of 5

Sign-in with HP Passport | Register Search:

United States-English

Contact HP

More options Business Support Center All of HP United States

** CRITICAL ** HP 2000i Modular Smart Array controller firmware

Business Support

Center

Subscribe to driver and support alerts

Sign up now for customized driver, security, patch, and support email alerts. Only receive updates on products you specify or own when you want them.

HP Passport Sign-in
User ID:

Password:
Register Learn more... Go

Type: Version: Operating System(s):

Tasks

Download drivers and software Troubleshoot a problem Setup, install, and configure Discover and use a product Perform regular maintenance Upgrade and migrate Recycle and dispose

Firmware - Storage Controller J212R10-03 (22 Dec 2011) Microsoft Windows Server 2003, Microsoft Windows Server 2003 for 64-bit Extended Systems, Microsoft Windows Server 2008 R2, Microsoft Windows Server 2008 W32, Microsoft Windows Server 2008 x64, Red Hat Enterprise Linux 4 (AMD64/EM64T), Red Hat Enterprise Linux 4 (x86), Red Hat Enterprise Linux 5 Server (x86), Red Hat Enterprise Linux 5 Server (x86-64), SUSE Linux Enterprise Server 10 (AMD64/EM64T), SUSE Linux Enterprise Server 10 (x86), SUSE Linux Enterprise Server 9 (AMD64/EM64T), SUSE Linux Enterprise Server 9 (x86), VMware ESX Server 3.0, VMware ESX/ESXi 4.0, VMware ESX/ESXi 4.1, VMware ESX/ESXi Server 3.5 neptunesw-J212R10-03.bin (11 MB)
Download

File name:

Description

Installation Instructions

Release Notes

Fixes

Revision History

Version: J212R10-03 (22 Dec 2011) Fixes Upgrade Requirement: Critical - HP requires users update to this version immediately. An issue exists on HP 2000 Modular Smart Array products running firmware versions J200P46, J210P22, or J300P22 that eventually causes controller configuration information to be lost, with subsequent loss of management capability from that controller. Array management, event messaging, and logging cease functioning, but host I/O continues to operate normally. This issue affects the ability to manage the array only from the affected controller; if a partner controller is available, the array can be managed through the partner controller. Because configuration information is stored in non-volatile memory, resetting or powering off the controller does not clear this error. If the issue occurs, the controller must be replaced. This failure mode is time sensitive and HP recommends immediately upgrading firmware on all MSA2000 controllers. This is not a hardware issue and proactive replacement of a controller is not a solution. To avoid this condition, you must upgrade your controller to the latest version of firmware. Versions of firmware that resolve this issue are in the following table. Product Corrected Firmware MSA2000 FC MSA2000 iSCSI MSA2000 SAS J202R10, J201R12, J201R09, J200P50 J212R10, J211R09, J210P23 J302R10, J301R09, J300P23 Affected Firmware J200P46 J210P22 J300P22

Resources Customer Self Repair Diagnose problem or Chat (HP Instant Support) Support Forums Guided troubleshooting Manuals Submit a support case See more... Help Site map HP Support Center

Some of the key fixes incorporated in J201R10, J212R10 and J302R10 are: Scrub caused controllers to halt. Identical vdisks created through the CLI and SMU report different volume sizes. Power Supply and I/O module statuses were reported differently on Controller A and Controller B. Controller halted when a vdisk expansion started. In dual-controller configurations, if one controller halted, the Fibre Channel host links did not failover to the surviving controller. Medium errors on drives in a RAID 6 vdisk caused another vdisk to report a critical state. The controller halted when clearing metadata of a leftover disk. Due to loss of heartbeat between the two controllers, one of the controllers halted.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=M... 1/30/2012

** CRITICAL ** HP 2000i Modular Smart Array controller firmware - HP Business Sup... Page 2 of 5

The event log was not updated when a drive was removed (or marked as down) while a utility, such as verify, was running. RAID 6 reconstruct caused partner controller to halt. Volumes became unaccessible when converting a master volume to a standard volume. Drives in non fault-tolerant vdisks did not report unrecovered media error as a warning. Heavy RSR load caused a controller to halt. Added year to the critical error log. Controller halted when utility timing was in conflict. Controller halted when, under heavy I/O loads, a RAID 6 vdisk had one or more failed drives. There were verification errors after an internal error recovery process completed. After a failover, an incorrect vdisk utility status was reported in the CLI and SMU. Host lost access when a large vdisk was being rebuilt. The spare drive was not activated when the vdisk passed into a critical state. Updated scrub utility for improved behavior. RAID 6 reconstruct reported incorrectly when an additional failure occurred. Drive LED behavior was inconsistent. Please refer to the Release Notes for a complete list of fixes, known issues and work-arounds and installation instructions.

Version: J211R09-01 (3 Feb 2011) Fixes Upgrade Requirement: Critical - HP requires users update to this version immediately. Critical - for HP StorageWorks 2000 Modular Smart Array products running firmware versions J200P46, J210P22, or J300P22 An issue exists on HP StorageWorks 2000 Modular Smart Array products running firmware versions J200P46, J210P22, or J300P22 that will eventually cause controller configuration information to be lost, with subsequent loss of management capability from that controller. Array management, event messaging, and logging will cease functioning, but host I/O will continue to operate normally. This issue affects the ability to manage the array from the affected controller only; if a partner controller is available, the array can be managed through the partner controller. Because configuration information is stored in non-volatile memory, resetting or powering off the controller will not clear this error. If the issue occurs, the controller must be replaced. This failure mode is time sensitive and HP recommends immediately upgrading firmware on all MSA2000 controllers. This is not a hardware issue and proactive replacement of a controller is not a solution. To avoid this condition, you must upgrade your controller to the latest version of firmware. Recommended - for HP StorageWorks 2000 Modular Smart Array products running any other firmware versions

Here are some of the fixes that were introduced in J201R09, J211R09, and J301R09 firmware: A drive that was hot plugged into an enclosure reported an inadvertent check condition. Each controller in the enclosure reset the other as it was starting up, causing a ping-pong effect. The host port did not respond after a cable was pulled. SATA drives dropped out of the SAS map during failover or failback. The maximum number of drives being seen by the system was being limited to 56. A misbehaving phy caused excessive background activity. A rare XOR error caused the controller to crash. Drive count in a vdisk was reported incorrectly when spare was added. A RAID 50 vdisk with one drive missing was listed as down. Data logs from a RAID 6 volume were running slower than necessary. A RAID 6 vdisk went offline when one controller was stopped by the other controller. A vdisk was not reported as fault tolerant during online initialization. Removing multiple drives while running I/O led to a loss of IP address information. Enclosure voltages were reported incorrectly. When a drive from a different array was added to the local array, dynamic sparing did not recognize it as an available spare.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=M... 1/30/2012

** CRITICAL ** HP 2000i Modular Smart Array controller firmware - HP Business Sup... Page 3 of 5

Host ports on a replacement controller came up as L-port and caused the controller to be disabled. Status messaging on a vdisk was incorrect. A drive was downed without an event being posted to the log. A controller would stall during a firmware upgrade, due to buffer overrun issues. The storage controller reported a communication error with the other controller during a shutdown and restart. In SAS and iSCSI models, reporting of Point-to-Point connections in the event log and in SNMP messages was incorrect. During a firmware upgrade, one controller was held down by its partner controller. The controller reboots repeatedly during a firmware upgrade. A data integrity issue occurred during a controller failure. A duplicate vdisk was available after a controller failover. Restore Default Settings caused DHCP settings to be set to an invalid value. vdisks were marked as offline after upgrading to P2000 G3 controllers. I/O failed when there was a loss of the path between enclosures.
Please refer to the full Release Notes for a complete listing of fixes, known issues and work-arounds and installation instructions. Enhancements

The following enhancements were introduced in J201R09, J211R09, and J301R09 firmware: Enhanced controller debug logs to include logs from the expander controller. Updated internal components to be the latest tested versions. Standardized events in the Fibre Channel libraries. Enhanced the expander-status command to differentiate between A-side and B-side ports. Improved logging when doing a background scrub that was started manually. Improved error handling used by the RAID I/O system and disk drives. Improved handling of quarantined vdisks. Improved firmware update behavior.
Version: J210P2302 (7 Aug 2010) Fixes Upgrade Requirement: Critical - HP requires users update to this version immediately. An issue exists on HP StorageWorks 2000 Modular Smart Array products running firmware versions J200P46, J210P22, or J300P22 that will eventually cause controller configuration information to be lost, with subsequent loss of management capability from that controller. Array management, event messaging, and logging will cease functioning, but host I/O will continue to operate normally. This issue affects the ability to manage the array from the affected controller only; if a partner controller is available, the array can be managed through the partner controller. Because configuration information is stored in non-volatile memory, resetting or powering off the controller will not clear this error. If the issue occurs, the controller must be replaced. This failure mode is time sensitive and HP recommends immediately upgrading firmware on all MSA2000 controllers. This is not a hardware issue and proactive replacement of a controller is not a solution. To avoid this condition, you must upgrade your controller to the latest version of firmware.

The following fixes apply to all product models listed in these release notes:

Fixed an issue that will eventually cause the controller to fail and become unrecoverable. For more information, see the explanation about this Mandatory Update recommendation. When SNMP is used, fixed an issue that not all values were set to the current community string when it was changed from PUBLIC. Improved the handling of a partner controller's interconnect so that an erroneous PICe link failure is not reported and the controller is not inappropriately shutdown. Fixed a problem where the MC stopped responding when deleting a spare from a vdisk.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=M... 1/30/2012

** CRITICAL ** HP 2000i Modular Smart Array controller firmware - HP Business Sup... Page 4 of 5

Fixed controller failover behavior in Active/Active configurations. If one of the controllers stops communicating with its on-board SAS expander, the controller will now fail. Fixed an issue where a power supply failure went undetected by the array. If a failure of the first power supply went undetected and the second power supply subsequently failed, the entire array abruptly powered off. Fixed a timing problem where a super-capacitor failure was erroneously reported during start up. Fixed inconsistent quarantine behavior and automatic health verification with parity error check on RAID 10 vdisks with missing members. Fixed inconsistent behavior when moving disk drives from one disk enclosure to another. A vdisk will no longer be quarantined if the vdisk is offline due to drives marked as failed. Fixed inconsistent location information about power supplies in log entries. Fixed an issue where both controllers shutdown with an OSMEnterDebugger. Corrected an issue where reconstruction of a vdisk appeared to be stopped at 0%. Prevent premature rescan following a reset. Correct display of the Expander Status in the logs. Prevent data about a deleted vdisk being orphaned in controller cache during a firmware update. If there are minor errors on multiple disk drives in a vdisk, the behavior will allow reconstruct to continue. Removed a critical notification message after firmware upgrades and disk scrubs. This was a message used during product development and testing that is misleading and is not needed in customer installation. Removed erroneous display of "Unknown event (234)". Corrected available free space values displayed for a vdisk. In the SMU, in the "Volume Mapping" page, fixed volume mapping information displayed for a LUN. In the CLI, for the show enclosure-status command, fixed erroneous marking of the power supply as Absent. In the CLI, for the show version command, fixed the occasional display of a blank page. The following fixes apply only to the MSA2012i G1 (vJ210P22): Corrected an issue where iSCSI port speed was reported incorrectly.
Enhancements The following enhancements apply to all product models and firmware streams listed in these release notes:

Enhanced controller replacement logic. Configuration data is no longer reset to manufacturer's default settings when controller A is replaced. Improved the Disk Firmware Update procedure so that it stops processing further drives if an error is encountered while updating. Enhanced performance of front panel fault LED. In dual I/O module configurations, this LED will now illuminate when one of the two I/O modules becomes unresponsive. Removed unnecessary check of SNMP version to stop reporting unhelpful messages to error logs. Enhanced the models of disk drives supported by the array. Improved failover time in certain configurations. Improved event log reporting to include older entries from the event buffer in the log. Added vdisk expansion information to bootup logs. Increased temperature threshold tolerance of internal components on the backplane. Improved snapshot performance for some configurations.
Version: J210P1902 (11 Feb 2010) Fixes

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=M... 1/30/2012

** CRITICAL ** HP 2000i Modular Smart Array controller firmware - HP Business Sup... Page 5 of 5

Upgrade Requirement: Critical - HP requires users update to this version immediately.

Fixes: Fixed an issue where the expander status was reporting incorrectly. Fixed an issue where the logs from controller A and controller B were not the same. Fixed an issue where a rebuild was not started even when a global spare was available.Fixed an issue where a write cache error during Vdisk creation would lead to a parity scrub error. Fixed issues for CIM and SMI-S involving certain classes and associations to be correct and appropriately populated. Fixed an issue where some unattached snapshots could not be deleted. Fixed an issue to include the snap pool threshold values being incorrectly reported. Fixed issues that resulted in PCIE link failures, debug exceptions, or OSMEnterDubber errors causing a controller to shutdown. Enhancements Enhancements: Added the ability to change the public and private SNMP Community names Enhanced the default behavior of the disk scrub utility so that it does not run constantly.

Content feedback To help us improve our content, please provide your feedback below. 1. How does the software on this page help you? very helpful somewhat helpful not helpful

2. Was it easy to find this software? easy not easy

3. If you selected not easy for question 2, in which section did you expect to find it?

- select one 4. Comments:

Submit

- Your feedback will be used to improve our content. Please note this form is for feedback only, so you will not receive a response. - Contact HP if you need technical assistance.

Printable version

Privacy statement

Using this site means you accept its terms

Feedback to webmaster

2012 Hewlett-Packard Development Company, L.P.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=M... 1/30/2012