* RECOMMENDED * Online ROM Flash Component for Linux - HP P2000 G3 MSA Arrays By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee. | Type: | Firmware (Entitlement Required) - Storage Controller | | Version: | TS251P006-02(6 Aug 2014) | | Operating System(s): | | HP-UX 11.31 (IA) | | Microsoft Windows Server 2008 R2 | | Microsoft Windows Server 2008 R2 for Itanium-Based Systems | | Microsoft Windows Server 2008 W32 | | Microsoft Windows Server 2008 x64 | | Microsoft Windows Server 2012 | | Microsoft Windows Server 2012 R2 | | Red Hat Enterprise Linux 5 Server (Itanium) | | Red Hat Enterprise Linux 5 Server (x86) | | Red Hat Enterprise Linux 5 Server (x86-64) | | Red Hat Enterprise Linux 6 Server (x86) | | Red Hat Enterprise Linux 6 Server (x86-64) | | SUSE Linux Enterprise Server 10 (AMD64/EM64T) | | SUSE Linux Enterprise Server 10 (Itanium) | | SUSE Linux Enterprise Server 10 (x86) | | SUSE Linux Enterprise Server 11 (AMD64/EM64T) | | SUSE Linux Enterprise Server 11 (Itanium) | | SUSE Linux Enterprise Server 11 (x86) | | VMware ESXi 5.0 | | VMware vSphere 5.1 | | VMware vSphere 5.5 |
HP-UX 11.23 | | File name: | CP024173.scexe (40 MB) |
This package contains the firmware upgrade for HP P2000 G3 MSA storage arrays which includes array controller firmware and approved companion versions of drive enclosure firmware. When installing array controller firmware, the process will also update firmware on attached drive enclosures. This firmware can be installed from any computer running a supported Linux operating system with an Ethernet connection to the HP P2000 G3 MSA Storage Array. IMPORTANT: Beginning with TS230, firmware for all HP P2000 G3 MSA System controllers was merged into a common firmware stream, used on all protocols of P2000 G3 MSA controllers. Prerequisites:
NOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded. WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming. CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation. IMPORTANT: FTP and telnet interfaces must be enabled on the arrays being updated. NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable/disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value: | 722143e56f5572727447a7daf5dfe151f05eaf672a1369d44644e0d48622e9e6 | CP024173.scexe |
Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained. Installation:
Select and schedule an appropriate time to perform an online upgrade: For redundant controller systems, to ensure the success of an online upgrade, selecting the appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity will ensure the upgrade completes as quickly as possible, and will avoid disruptions to hosts and applications due to timeouts. As with any other firmware upgrade it is a recommended best practice to ensure that you have a full backup prior to the upgrade. When you download this module from the HP.com web site, you cannot double click on the link. You will need to right click the link and select 'save as' or similar option. This module is a SCEXE file. It is a self extracting executable module. This module only operates from the Linux command line. Linux Smart Component Installation Instructions Place the downloaded firmware package in a temporary directory. Open a Linux command console. From the directory containing the downloaded file, enable execute access to this module by entering chmod +x CPxxxxxx.scexe, where CPxxxxxx.scexe represents the downloaded file. Execute the Smart Component by entering a command similar to the following: ./CPxxxxxx.scexe --target <ip_address> --user <username> --passwd <password> - Follow onscreen instructions.
NOTES: - When prompted for logon information, enter credentials for an account with management access rights.
- Use the
-e or -f option when flashing a device, even if it is up to date. - Use the
-g option when downgrading. - For details on supported command options, see the online help by executing the command
./CPxxxxxx.scexe or ./CPxxxxxx.scexe -h. - If the user name or password contains an exclamation mark (!), enclose the string in single quotes or enter a backslash () before the exclamation point. For example,
'!manage' or !manage
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. End User License Agreements:
Hewlett-Packard End User License Agreement
Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. Important:
NOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded.
WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming.
CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.
IMPORTANT: FTP and telnet services must be enabled on the arrays being updated and the corresponding client interfaces enabled on the host system where the smart component is being executed.
NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Depending on the environment, it may take as long as one hour to complete. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable / disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). Notes:
Support for additional operating systems may be approved after release of this firmware.
For up-to-date, detailed operating system support information and known restrictions, see the HP Storage Single Point Of Connectivity Knowledge (SPOCK) website at http://www.hp.com/storage/spock. Enter your HP Passport account credentials and then, in the left pane, select View by Array. In the displayed table of arrays, on the MSA row, use the Refine and the Add to Selection options to display the list of supported operating systems for your controller model. Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. TS251P006-02 build includes the following components:| Component | Version | | Storage Controller Code | T251P08-01 | | Storage Controller Loader Code | 23.008 | | Memory Controller FPGA Code | F400R02 | | Management Controller Code | L251R005-11 | | CPLD Code | 22 | | Expander Controller Code | S200B28 (2028) |
Expansion Modules: - O320B13.bin (3213)
- S200B28.bin (2028)
Important Firmware Notes - The I/O module firmware version has been updated to S200B28. For the list of updates, refer to HP P2000 Large Form Factor Drive Enclosure I/O Module S200B28 Firmware Release Notes.
- The P2000 G3 contains an embedded SMI-S provider for use by SMI-S client applications. The embedded provider is designed to support P2000 configurations with up to 24 hard drives and up to 250 mapping paths. A mapping path is defined as a P2000 volume presented through a P2000 target port to a Host initiator.
- Some drive firmware Smart Components built before the TS240 release may not be compatible with TS240 firmware, causing the Smart Component to stall. HP recommends checking drive module firmware versions and upgrading them before upgrading controllers to TS240.
- Some drive firmware Smart Components may not be compatible with the current release and cause the Smart Component to stall. HP recommends extracting the Smart Component and using the .FLA or .LOD file with the SMU to update the drive firmware.
- In environments using replication, all HP MSA P2000 G3 controllers must have the same firmware version installed. Running different firmware versions among HP MSA P2000 G3 controllers might prevent replications from occurring.
- To replicate between an HP P2000 G3 MSA system and an HP MSA 1040 or an HP MSA 2040 SAN system, the secondary volume must be exactly the same size as the primary volume. To ensure that the size is exactly the same when creating the secondary volume manually, use the CLI replicate volume command as described in the HP P2000 CLI Reference Guide, the HP MSA 1040 CLI Reference Guide, and the HP MSA 2040 CLI Reference Guide.
- When changing a replication set (for example, adding or removing a replication volume, or deleting the replication set), do so from the source system. When aborting, suspending, or resuming a replication, do so from the destination system.
- When changing the primary volume of a replication set, do so from the destination system first, then perform the change on the source system.
- When using Windows Dynamic Disk (software RAID) on top of hardware RAID, there are some cautions to be considered. For more information, see the section 'Real World: Dynamic versus Basic Disks' on the topic at http://technet.microsoft.com/en-us/library/dd163558.aspx.
- Failover and failback times are affected by the number of system volumes. The more volumes there are on the system, the more time is required for failover and failback to complete.
- MSA70 disk enclosures are supported for use with P2000 G3 arrays running TS230 or later firmware, but must have firmware 2.28 or later installed. For more information on MSA70 firmware compatibility with different P2000 G3 array firmware versions, see the QuickSpecs for the MSA70 or P2000 G3, or see the HP 70 Modular Smart Array Enclosure Firmware Release Notes.
- For the FC/iSCSI MSA Controller, mapping a volume via iSCSI and FC to the same server is not a supported configuration. Many operating systems' multipath solutions will not correctly handle the multi-protocols. Do not map a LUN in this manner.
Supported Devices and Features:
This firmware is supported on the below MSA G3 devices:
- HP MSA2000 Single I/O 3.5 inch 12 Drive Enclosure
- HP MSA2000 Dual I/O 3.5 inch 12 Drive Enclosure
- HP P2000 G3 10GbE iSCSI MSA Dual Controller LFF Array System
- HP P2000 G3 10GbE iSCSI MSA Dual Controller SFF Array System
- HP P2000 G3 iSCSI MSA Dual Controller LFF Array System
- HP P2000 G3 iSCSI MSA Dual Controller SFF Array System
- HP P2000 G3 SAS MSA Dual Controller LFF Array System
- HP P2000 G3 SAS MSA Dual Controller SFF Array System
- HP P2000 G3 MSA FC Dual Controller LFF Modular Smart Array System
- HP P2000 G3 MSA FC Dual Controller SFF Modular Smart Array System
- HP P2000 G3 MSA FC/iSCSI Dual Combo Controller SFF Array
- HP P2000 G3 MSA FC/iSCSI Dual Combo Controller LFF Array
- HP P2000 Dual I/O LFF Drive Enclosure
Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following features were fixed in TS251P006: - Updated Open SSL library to remove security vulnerability.
- Corrected status reporting for power supplies and fans.
NOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded.
WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming.
CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.
IMPORTANT: FTP and telnet services must be enabled on the arrays being updated and the corresponding client interfaces enabled on the host system where the smart component is being executed.
NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Depending on the environment, it may take as long as one hour to complete. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable / disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). Version:TS252P005 (9 Feb 2017) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following issues were resolved in controller firmware TS252P005: - Controller ceased to operate due to the following error conditions:
- page fault occurred in mioL.
- non-specific page fault occurred.
- Transient error caused array to incorrectly report '314 ERROR' event in event logs.
- Replications stalled on primary volume due to issue with queue full condition.
- iSCSI controllers provided incorrect maximum transfer size in the Vital Product Data (VPD).
- Controller ceased to operate due to page fault in mioL.
- Custom OpenSSL certificate could not be used.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. The following features were added or enhanced in controller firmware TS252P005: - Upgraded OpenSSL to 1.0.2j.
- Added description and help text for the new quarantine event (590).
- Disabled in-band SCSI Enclosure Management Services (SES) protocol by default, alleviating controller issues in environments where SES devices were actively monitored.
- Added support for SCSI Send Diagnostic command when in-band SES is disabled.
- Improved HPE D2700 Disk Enclosure fan information in CLI.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. (1 Mar 2016) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following issues were fixed in controller firmware TS252P001: - MC NOT TALKING error message seen after doing multiple logins and logouts using scripts.
- Systems upgraded from TS251 to TS252R007 are prevented from replicating from a primary system running GL200 because of an inability to attach the target system.
- A drive with a low level hardware error requesting spin up results in loss of data access.
- Creating replication volume would fail in the SMU if a space exists in the source volume name.
- Both controllers ceased to operate while handling heavy XCOPY commands.
- FRU Event 314 for Power Supplies does not display the product ID or Serial Number.
- Event 401 is not logged when logs reach warning threshold.
- Uninstalling and reinstalling replication license file results in confusing digits in the license display.
- The vdisk was quarantined on one controller by the other controller when both controllers are shutdown within one second.
- Controller may cease operation during copy-on-write restart while a vdisk is being dequarantined.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
The following features were added or enhanced in controller firmware TS252P001: - Disabled the RC4 cipher to resolve CVE-2015-2808.
- Controller will automatically be restarted when it ceases operation due to a PCI communication problem.
- Disabled 96-bit and MD5-based HMAC and CBC mode ciphers.
- OpenSSL upgraded to 1.0.1q
- Disabled SSL compression to mitigate CRIME attacks (CVE-2012-4929 and CVE-2012-4930).
- Implemented fixes for CVE-2013-5600 and CVE-2013-4548.
- Disabled SSLv2
- Disabled weak SSL ciphers.
- Disabled TCP timestamp response.
- Certificate is signed using SHA-1 algorithm.
- Enhanced handling of aborted ATS commands.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
(6 Aug 2014) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following features were fixed in TS251P006: - Updated Open SSL library to remove security vulnerability.
- Corrected status reporting for power supplies and fans.
(2 Oct 2013) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following feature was fixed in TS250P003: - Disallow user creation using reserved user names.
The following issue was fixed in TS250P002: - Fixed the problem with aborting Atomic Test-andSet (ATS) commands.
- Fixed the hanging controller issue that is seen during several iterations of the VMware Site Recovery Manager (SRM) failover and failback process.
- Fixed the Atomic Test-and-Set logic that set the incorrect error state condition and subsequently crash the array controllers.
- A trust failure no longer clears the partially reconstructed state of a HDD.
- Partner Firmware Update (PFU) now functions properly when the new Management Controller (MC) version matches the old MC version.
- All events are now properly processed by HP SIM.
The following issue was fixed in TS250R023: - After installing TS250R021, the controller CompactFlash may be set to Write-Through mode, causing reduced system performance.
The following issues were fixed in TS250R021: - Alerts indicating that a disk channel has gone into a degraded state have been modified so that the normal reduction of channel speed due to intermittent noise should no longer generate a Warning alert.
- Preliminary reporting of a supercap overcharge failing condition was removed.
- When the array received a DHCP address from a DHCP server, it responded with a unique hostname, which displayed in the DHCP server. This unique hostname overwrote the hostname supplied by the DHCP server in option 012.
- Hyper-V servers could not be migrated to P2000 G3 storage systems. Support for Hyper-V Live Migration has been added.
- P2000 G3 storage systems were not discovered by Storage Essentials software.
- Controllers were unresponsive to CLI requests for up to 30 minutes after a firmware update.
- For SMI-S, inconsistent data was provided for the CIM_AuthorizedPrivilege instance.
- SMI-S queries might fail if Small Footprint CIM Broker daemons are restarted after a memory threshold limit is reached. After enabling either SMI-S protocol, the SMI-S service on the array will now consistently start.
Please refer to the Release Notes for more details. The following enhancement is added in the TS250P002 firmware release:
- Storage Management Utility (SMU) localization in Simplified Chinese, Chinese Traditional, Dutch, French, German, Italian, Korean, Spanish, and Japanese.
The following features were added or enhanced in the TS250R021 firmware release:- Added the ability to change the link speed (100Mbps, 10Mbps) and duplex (half, full) mode of the controller management port.
- After a reconstruction completes, an event is now logged that includes the number of unrecoverable errors, if any.
- When event 173 'An error was reported by a disk' is reported due to a vdisk being dequarantined, the message now includes the state of the vdisk and indicates whether the dequarantine was automatic or was requested manually.
- In the CLI, the trust command now indicates disks that are out-of-sync, the age of the disk to indicate how far out of sync it is, and disks that were used for reconstruction but where reconstruction did not complete. The user is given the choice to include the out-of-sync or partially reconstructed disks, to exclude them, or to abort. If no out-of-sync or partially reconstructed disks are present, the command continues without a prompt.
- The Clear Disk Metadata function of the SMU now prompts to confirm the operation, allowing the user a chance to reconsider the possibly destructive results of the operation.
- Included instructions for obtaining historical performance data in the FTP prompt.
- Fibre Channel soft loop IDs are now retained during controller failover and failback.
Please refer to the Release Notes for more details. (5 Apr 2013) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
IMPORTANT: HP P2000 G3 arrays running TS100 firmware cannot be directly upgraded to TS250 using this firmware package. Such arrays will have to be upgraded to TS230 firmware first before using this firmware package to upgrade them to TS250.
Supersedes:
| P2000 G3 MSA controller firmware version | P2000 G3 MSA controller model | | TS250R021 | All HP P2000 G3 MSA System controller models | | TS240 | All HP P2000 G3 MSA System controller models | | TS230 | All HP P2000 G3 MSA System controller models | | TS220 | HP P2000 G3 1GbE iSCSI MSA | | TS210 | HP P2000 G3 10GbE iSCSI MSA | | TS201 | HP P2000 G3 FC and FC/iSCSI MSA | | TS200 | HP P2000 G3 SAS MSA |
The following issue was fixed in TS250R023: - After installing TS250R021, the controller CompactFlash may be set to Write-Through mode, causing reduced system performance.
The following issues were fixed in TS250R021:
- Alerts indicating that a disk channel has gone into a degraded state have been modified so that the normal reduction of channel speed due to intermittent noise should no longer generate a Warning alert.
- Preliminary reporting of a supercap overcharge failing condition was removed.
- When the array received a DHCP address from a DHCP server, it responded with a unique hostname, which displayed in the DHCP server. This unique hostname overwrote the hostname supplied by the DHCP server in option 012.
- Hyper-V servers could not be migrated to P2000 G3 storage systems. Support for Hyper-V Live Migration has been added.
- P2000 G3 storage systems were not discovered by Storage Essentials software.
- Controllers were unresponsive to CLI requests for up to 30 minutes after a firmware update.
- For SMI-S, inconsistent data was provided for the CIM_AuthorizedPrivilege instance.
- SMI-S queries might fail if Small Footprint CIM Broker daemons are restarted after a memory threshold limit is reached. After enabling either SMI-S protocol, the SMI-S service on the array will now consistently start.
Please refer to the Release Notes for more details. The following features were added or enhanced in the TS250R021 firmware release: - Added the ability to change the link speed (100Mbps, 10Mbps) and duplex (half, full) mode of the controller management port.
- After a reconstruction completes, an event is now logged that includes the number of unrecoverable errors, if any.
- When event 173 'An error was reported by a disk' is reported due to a vdisk being dequarantined, the message now includes the state of the vdisk and indicates whether the dequarantine was automatic or was requested manually.
- In the CLI, the trust command now indicates disks that are out-of-sync, the age of the disk to indicate how far out of sync it is, and disks that were used for reconstruction but where reconstruction did not complete. The user is given the choice to include the out-of-sync or partially reconstructed disks, to exclude them, or to abort. If no out-of-sync or partially reconstructed disks are present, the command continues without a prompt.
- The Clear Disk Metadata function of the SMU now prompts to confirm the operation, allowing the user a chance to reconsider the possibly destructive results of the operation.
- Included instructions for obtaining historical performance data in the FTP prompt.
- Fibre Channel soft loop IDs are now retained during controller failover and failback.
Please refer to the Release Notes for more details. (2 Nov 2012) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
IMPORTANT: HP P2000 G3 arrays running TS100 firmware cannot be directly upgraded to TS240 using this firmware package. Such arrays will have to be upgraded to TS201 or TS230 firmware first before using this firmware package to upgrade them to TS240.
Supersedes:
| P2000 G3 MSA controller firmware version | P2000 G3 MSA controller model | | TS240P003 | All HP P2000 G3 MSA System controller models | | TS240P001 | All HP P2000 G3 MSA System controller models | | TS240R037 | All HP P2000 G3 MSA System controller models | | TS230 | All HP P2000 G3 MSA System controller models | | TS220 | HP P2000 G3 1GbE iSCSI MSA | | TS210 | HP P2000 G3 10GbE iSCSI MSA | | TS201 | HP P2000 G3 FC and FC/iSCSI MSA | | TS200 | HP P2000 G3 SAS MSA |
The following issues were fixed in TS240P004: - Remote Snap Replication (RSR) generated page fault errors in some configurations.
- RSR schedule modifications automatically advanced the Next Time field by 24 hours.
- In single-controller configurations with an attached drive enclosure, the health check returned incorrect information about the drive enclosure, the controller it is connected to, and the controller enclosure.
- In dual-controller configurations, under rare circumstances, SNMP operations halted on controller B.
- In the SMU, errors were displayed when changing Single Controller Mode settings.
Please refer to the Release Notes for the complete listing of fixes. The following features were added or enhanced in the TS240R037 firmware release: - Support for VMware vSphere Aware Storage API) (VASA). When the HP Insight Control for VMware vCenter Storage Module v7.0 (or higher) is installed, the VMware VASA API can be used to provide visibility into the physical storage infrastructure through vCenter. The Insight Control Storage Module can be downloaded from the HP Software Depot website (http://www.hp.com/go/softwaredepot).
- Performance Monitoring has been expanded to include:
- Disk performance statistics are collected every 15 minutes and retained for 6 months.
- Historical performance statistics can be graphed for either a single disk or for all disks in a vdisk in the SMU.
- Graphs show the latest 50 samples by default, but may be set for a different time period. If the specified time period includes more than 50 samples, the data is aggregated into 50 samples.
Please refer to Release Notes for complete list of enhancements.
(6 Jul 2012) Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.
This package is only required for customers wanting to downgrade from TS240 to TS230. This package contains the same firmware payload as TS230P008. The following fix was incorporated in smart component (upgrade installer): - In very rare scenarios, the smart component (upgrade installer) when terminated abruptly would not restore the FTP settings back to original values.
The following fix was incorporated in TS230P008:
The following fix was incorporated in TS230P007:
The following fixes were incorporated in TS230P006:
3 TB SAS drives failed to report media errors in the region above 2 TB. Creating a vdisk on 3 TB drives failed with an “invalid device was specified” message. During RAID5 partial stripe writes of a bad block recovery, parity data was not properly cached, causing the controller to halt. The Restore Factory Defaults option did not reset the IP addresses. WWN was case-sensitive (and should not be). In multipath (dual-domain) environments, during a failover and failback or shutdown and restart situation, SCSI registrations were over-allocated, which caused one of the I/O paths to not be recognized. A master volume could not be converted to a standard volume. When doing a rollback of a 2 TB Snapshot, there was a possibility that the controller would stall. Firmware updating issues:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.The following enhancement was incorporated in smart component (upgrade installer): - The smart component (upgrade installer) has been enhanced to support firmware downgrade from TS240. This does not involve any changes to the firmware payload.
The following enhancement was incorporated in TS230P006:
In the event logs, for messages about leftover drives, changed the Recommended Action portion of the Event and Health Reason fields to point to the HP MSA2000/P2000 Guided Troubleshooting Best Practices document.
The following enhancements were incorporated in TS230R044:
Remote snap operations are now supported on HP 1GbE iSCSI MSA and HP 10GbE iSCSI MSA System controllers. Remote snap operations and I/O can be processed simultaneously on HP 1GbE iSCSI MSA and HP 10GbE iSCSI MSA System controllers. A new tool was created to check the local system link. Added support for vStorage APIs for Array Integration (VAAI), to offload certain processing functions from the host to the array, which can greatly enhance performance. Improved handling of drives that are slow to spin up or are missing by quarantining the vdisk, rather than taking it offline, and automatically dequarantining the vdisk when sufficient drives become available.
| Type: | Firmware (Entitlement Required) - Storage Controller | | Version: | TS251P006-02(6 Aug 2014) | | Operating System(s): | | HP-UX 11.23 | | HP-UX 11.31 (IA) | | Microsoft Windows Server 2008 R2 | | Microsoft Windows Server 2008 R2 for Itanium-Based Systems | | Microsoft Windows Server 2008 W32 | | Microsoft Windows Server 2008 x64 | | Microsoft Windows Server 2012 | | Microsoft Windows Server 2012 R2 | | Red Hat Enterprise Linux 5 Server (Itanium) | | Red Hat Enterprise Linux 5 Server (x86) | | Red Hat Enterprise Linux 5 Server (x86-64) | | Red Hat Enterprise Linux 6 Server (x86) | | Red Hat Enterprise Linux 6 Server (x86-64) | | SUSE Linux Enterprise Server 10 (AMD64/EM64T) | | SUSE Linux Enterprise Server 10 (Itanium) | | SUSE Linux Enterprise Server 10 (x86) | | SUSE Linux Enterprise Server 11 (AMD64/EM64T) | | SUSE Linux Enterprise Server 11 (Itanium) | | SUSE Linux Enterprise Server 11 (x86) | | VMware ESXi 5.0 | | VMware vSphere 5.1 | | VMware vSphere 5.5 |
|
DescriptionThis package contains the firmware upgrade for HP P2000 G3 MSA storage arrays which includes array controller firmware and approved companion versions of drive enclosure firmware. When installing array controller firmware, the process will also update firmware on attached drive enclosures. This firmware can be installed from any computer running a supported Linux operating system with an Ethernet connection to the HP P2000 G3 MSA Storage Array. IMPORTANT: Beginning with TS230, firmware for all HP P2000 G3 MSA System controllers was merged into a common firmware stream, used on all protocols of P2000 G3 MSA controllers. Installation InstructionsPrerequisites:
NOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded. WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming. CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation. IMPORTANT: FTP and telnet interfaces must be enabled on the arrays being updated. NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable/disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value: | 722143e56f5572727447a7daf5dfe151f05eaf672a1369d44644e0d48622e9e6 | CP024173.scexe |
Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained. Installation:
Select and schedule an appropriate time to perform an online upgrade: For redundant controller systems, to ensure the success of an online upgrade, selecting the appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity will ensure the upgrade completes as quickly as possible, and will avoid disruptions to hosts and applications due to timeouts. As with any other firmware upgrade it is a recommended best practice to ensure that you have a full backup prior to the upgrade. When you download this module from the HP.com web site, you cannot double click on the link. You will need to right click the link and select 'save as' or similar option. This module is a SCEXE file. It is a self extracting executable module. This module only operates from the Linux command line. Linux Smart Component Installation Instructions Place the downloaded firmware package in a temporary directory. Open a Linux command console. From the directory containing the downloaded file, enable execute access to this module by entering chmod +x CPxxxxxx.scexe, where CPxxxxxx.scexe represents the downloaded file. Execute the Smart Component by entering a command similar to the following: ./CPxxxxxx.scexe --target <ip_address> --user <username> --passwd <password> - Follow onscreen instructions.
NOTES: - When prompted for logon information, enter credentials for an account with management access rights.
- Use the
-e or -f option when flashing a device, even if it is up to date. - Use the
-g option when downgrading. - For details on supported command options, see the online help by executing the command
./CPxxxxxx.scexe or ./CPxxxxxx.scexe -h. - If the user name or password contains an exclamation mark (!), enclose the string in single quotes or enter a backslash () before the exclamation point. For example,
'!manage' or !manage
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. Release NotesEnd User License Agreements:
Hewlett-Packard End User License Agreement
Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. Important:
NOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded.
WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming.
CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.
IMPORTANT: FTP and telnet services must be enabled on the arrays being updated and the corresponding client interfaces enabled on the host system where the smart component is being executed.
NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Depending on the environment, it may take as long as one hour to complete. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable / disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). Notes:
Support for additional operating systems may be approved after release of this firmware.
For up-to-date, detailed operating system support information and known restrictions, see the HP Storage Single Point Of Connectivity Knowledge (SPOCK) website at http://www.hp.com/storage/spock. Enter your HP Passport account credentials and then, in the left pane, select View by Array. In the displayed table of arrays, on the MSA row, use the Refine and the Add to Selection options to display the list of supported operating systems for your controller model. Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. TS251P006-02 build includes the following components:| Component | Version | | Storage Controller Code | T251P08-01 | | Storage Controller Loader Code | 23.008 | | Memory Controller FPGA Code | F400R02 | | Management Controller Code | L251R005-11 | | CPLD Code | 22 | | Expander Controller Code | S200B28 (2028) |
Expansion Modules: - O320B13.bin (3213)
- S200B28.bin (2028)
Important Firmware Notes - The I/O module firmware version has been updated to S200B28. For the list of updates, refer to HP P2000 Large Form Factor Drive Enclosure I/O Module S200B28 Firmware Release Notes.
- The P2000 G3 contains an embedded SMI-S provider for use by SMI-S client applications. The embedded provider is designed to support P2000 configurations with up to 24 hard drives and up to 250 mapping paths. A mapping path is defined as a P2000 volume presented through a P2000 target port to a Host initiator.
- Some drive firmware Smart Components built before the TS240 release may not be compatible with TS240 firmware, causing the Smart Component to stall. HP recommends checking drive module firmware versions and upgrading them before upgrading controllers to TS240.
- Some drive firmware Smart Components may not be compatible with the current release and cause the Smart Component to stall. HP recommends extracting the Smart Component and using the .FLA or .LOD file with the SMU to update the drive firmware.
- In environments using replication, all HP MSA P2000 G3 controllers must have the same firmware version installed. Running different firmware versions among HP MSA P2000 G3 controllers might prevent replications from occurring.
- To replicate between an HP P2000 G3 MSA system and an HP MSA 1040 or an HP MSA 2040 SAN system, the secondary volume must be exactly the same size as the primary volume. To ensure that the size is exactly the same when creating the secondary volume manually, use the CLI replicate volume command as described in the HP P2000 CLI Reference Guide, the HP MSA 1040 CLI Reference Guide, and the HP MSA 2040 CLI Reference Guide.
- When changing a replication set (for example, adding or removing a replication volume, or deleting the replication set), do so from the source system. When aborting, suspending, or resuming a replication, do so from the destination system.
- When changing the primary volume of a replication set, do so from the destination system first, then perform the change on the source system.
- When using Windows Dynamic Disk (software RAID) on top of hardware RAID, there are some cautions to be considered. For more information, see the section 'Real World: Dynamic versus Basic Disks' on the topic at http://technet.microsoft.com/en-us/library/dd163558.aspx.
- Failover and failback times are affected by the number of system volumes. The more volumes there are on the system, the more time is required for failover and failback to complete.
- MSA70 disk enclosures are supported for use with P2000 G3 arrays running TS230 or later firmware, but must have firmware 2.28 or later installed. For more information on MSA70 firmware compatibility with different P2000 G3 array firmware versions, see the QuickSpecs for the MSA70 or P2000 G3, or see the HP 70 Modular Smart Array Enclosure Firmware Release Notes.
- For the FC/iSCSI MSA Controller, mapping a volume via iSCSI and FC to the same server is not a supported configuration. Many operating systems' multipath solutions will not correctly handle the multi-protocols. Do not map a LUN in this manner.
Supported Devices and Features:
This firmware is supported on the below MSA G3 devices:
- HP MSA2000 Single I/O 3.5 inch 12 Drive Enclosure
- HP MSA2000 Dual I/O 3.5 inch 12 Drive Enclosure
- HP P2000 G3 10GbE iSCSI MSA Dual Controller LFF Array System
- HP P2000 G3 10GbE iSCSI MSA Dual Controller SFF Array System
- HP P2000 G3 iSCSI MSA Dual Controller LFF Array System
- HP P2000 G3 iSCSI MSA Dual Controller SFF Array System
- HP P2000 G3 SAS MSA Dual Controller LFF Array System
- HP P2000 G3 SAS MSA Dual Controller SFF Array System
- HP P2000 G3 MSA FC Dual Controller LFF Modular Smart Array System
- HP P2000 G3 MSA FC Dual Controller SFF Modular Smart Array System
- HP P2000 G3 MSA FC/iSCSI Dual Combo Controller SFF Array
- HP P2000 G3 MSA FC/iSCSI Dual Combo Controller LFF Array
- HP P2000 Dual I/O LFF Drive Enclosure
FixesUpgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following features were fixed in TS251P006: - Updated Open SSL library to remove security vulnerability.
- Corrected status reporting for power supplies and fans.
ImportantNOTE: Firmware upgrade must be performed from a supported Linux client (using the corresponding Linux smart component) that has network connectivity to the array being upgraded.
WARNING! Do not power cycle or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for reprogramming.
CAUTION: Before upgrading firmware, ensure that the storage system configuration is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In a single-controller system, updating firmware causes all disks to be temporarily inaccessible. Stop I/O to vdisks before performing this operation.
IMPORTANT: FTP and telnet services must be enabled on the arrays being updated and the corresponding client interfaces enabled on the host system where the smart component is being executed.
NOTE: Allow approximately 30 minutes for the firmware to load and for the automatic restart to complete on the controller you are connected to. Depending on the environment, it may take as long as one hour to complete. Wait for the progress messages to specify that the update has completed. In dual-controller systems with Partner Firmware Update enabled, allow an additional hour for the update to complete on the second controller. (Updating the second controller usually takes 30 minutes to complete, but may take as long as one hour.) All firmware flash progress messages are logged to /var/cpq/MSA2000_IP.log and flashing summary is logged to /var/cpq/Component.log. A final completion message will be displayed. The Smart Component will manage the FTP and Partner Firmware Update (PFU) enable / disable settings. NOTE: This Firmware Smart Component will not inter-operate with HP Smart Update Manager (HP SUM) or with the HP Smart Update Firmware DVD (formerly Firmware Maintenance CD). Revision HistoryVersion:TS252P005 (9 Feb 2017) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following issues were resolved in controller firmware TS252P005: - Controller ceased to operate due to the following error conditions:
- page fault occurred in mioL.
- non-specific page fault occurred.
- Transient error caused array to incorrectly report '314 ERROR' event in event logs.
- Replications stalled on primary volume due to issue with queue full condition.
- iSCSI controllers provided incorrect maximum transfer size in the Vital Product Data (VPD).
- Controller ceased to operate due to page fault in mioL.
- Custom OpenSSL certificate could not be used.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. The following features were added or enhanced in controller firmware TS252P005: - Upgraded OpenSSL to 1.0.2j.
- Added description and help text for the new quarantine event (590).
- Disabled in-band SCSI Enclosure Management Services (SES) protocol by default, alleviating controller issues in environments where SES devices were actively monitored.
- Added support for SCSI Send Diagnostic command when in-band SES is disabled.
- Improved HPE D2700 Disk Enclosure fan information in CLI.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware. (1 Mar 2016) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following issues were fixed in controller firmware TS252P001: - MC NOT TALKING error message seen after doing multiple logins and logouts using scripts.
- Systems upgraded from TS251 to TS252R007 are prevented from replicating from a primary system running GL200 because of an inability to attach the target system.
- A drive with a low level hardware error requesting spin up results in loss of data access.
- Creating replication volume would fail in the SMU if a space exists in the source volume name.
- Both controllers ceased to operate while handling heavy XCOPY commands.
- FRU Event 314 for Power Supplies does not display the product ID or Serial Number.
- Event 401 is not logged when logs reach warning threshold.
- Uninstalling and reinstalling replication license file results in confusing digits in the license display.
- The vdisk was quarantined on one controller by the other controller when both controllers are shutdown within one second.
- Controller may cease operation during copy-on-write restart while a vdisk is being dequarantined.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
The following features were added or enhanced in controller firmware TS252P001: - Disabled the RC4 cipher to resolve CVE-2015-2808.
- Controller will automatically be restarted when it ceases operation due to a PCI communication problem.
- Disabled 96-bit and MD5-based HMAC and CBC mode ciphers.
- OpenSSL upgraded to 1.0.1q
- Disabled SSL compression to mitigate CRIME attacks (CVE-2012-4929 and CVE-2012-4930).
- Implemented fixes for CVE-2013-5600 and CVE-2013-4548.
- Disabled SSLv2
- Disabled weak SSL ciphers.
- Disabled TCP timestamp response.
- Certificate is signed using SHA-1 algorithm.
- Enhanced handling of aborted ATS commands.
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.
(6 Aug 2014) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following features were fixed in TS251P006: - Updated Open SSL library to remove security vulnerability.
- Corrected status reporting for power supplies and fans.
(2 Oct 2013) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience. The following feature was fixed in TS250P003: - Disallow user creation using reserved user names.
The following issue was fixed in TS250P002: - Fixed the problem with aborting Atomic Test-andSet (ATS) commands.
- Fixed the hanging controller issue that is seen during several iterations of the VMware Site Recovery Manager (SRM) failover and failback process.
- Fixed the Atomic Test-and-Set logic that set the incorrect error state condition and subsequently crash the array controllers.
- A trust failure no longer clears the partially reconstructed state of a HDD.
- Partner Firmware Update (PFU) now functions properly when the new Management Controller (MC) version matches the old MC version.
- All events are now properly processed by HP SIM.
The following issue was fixed in TS250R023: - After installing TS250R021, the controller CompactFlash may be set to Write-Through mode, causing reduced system performance.
The following issues were fixed in TS250R021: - Alerts indicating that a disk channel has gone into a degraded state have been modified so that the normal reduction of channel speed due to intermittent noise should no longer generate a Warning alert.
- Preliminary reporting of a supercap overcharge failing condition was removed.
- When the array received a DHCP address from a DHCP server, it responded with a unique hostname, which displayed in the DHCP server. This unique hostname overwrote the hostname supplied by the DHCP server in option 012.
- Hyper-V servers could not be migrated to P2000 G3 storage systems. Support for Hyper-V Live Migration has been added.
- P2000 G3 storage systems were not discovered by Storage Essentials software.
- Controllers were unresponsive to CLI requests for up to 30 minutes after a firmware update.
- For SMI-S, inconsistent data was provided for the CIM_AuthorizedPrivilege instance.
- SMI-S queries might fail if Small Footprint CIM Broker daemons are restarted after a memory threshold limit is reached. After enabling either SMI-S protocol, the SMI-S service on the array will now consistently start.
Please refer to the Release Notes for more details. The following enhancement is added in the TS250P002 firmware release:
- Storage Management Utility (SMU) localization in Simplified Chinese, Chinese Traditional, Dutch, French, German, Italian, Korean, Spanish, and Japanese.
The following features were added or enhanced in the TS250R021 firmware release:- Added the ability to change the link speed (100Mbps, 10Mbps) and duplex (half, full) mode of the controller management port.
- After a reconstruction completes, an event is now logged that includes the number of unrecoverable errors, if any.
- When event 173 'An error was reported by a disk' is reported due to a vdisk being dequarantined, the message now includes the state of the vdisk and indicates whether the dequarantine was automatic or was requested manually.
- In the CLI, the trust command now indicates disks that are out-of-sync, the age of the disk to indicate how far out of sync it is, and disks that were used for reconstruction but where reconstruction did not complete. The user is given the choice to include the out-of-sync or partially reconstructed disks, to exclude them, or to abort. If no out-of-sync or partially reconstructed disks are present, the command continues without a prompt.
- The Clear Disk Metadata function of the SMU now prompts to confirm the operation, allowing the user a chance to reconsider the possibly destructive results of the operation.
- Included instructions for obtaining historical performance data in the FTP prompt.
- Fibre Channel soft loop IDs are now retained during controller failover and failback.
Please refer to the Release Notes for more details. (5 Apr 2013) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
IMPORTANT: HP P2000 G3 arrays running TS100 firmware cannot be directly upgraded to TS250 using this firmware package. Such arrays will have to be upgraded to TS230 firmware first before using this firmware package to upgrade them to TS250.
Supersedes:
| P2000 G3 MSA controller firmware version | P2000 G3 MSA controller model | | TS250R021 | All HP P2000 G3 MSA System controller models | | TS240 | All HP P2000 G3 MSA System controller models | | TS230 | All HP P2000 G3 MSA System controller models | | TS220 | HP P2000 G3 1GbE iSCSI MSA | | TS210 | HP P2000 G3 10GbE iSCSI MSA | | TS201 | HP P2000 G3 FC and FC/iSCSI MSA | | TS200 | HP P2000 G3 SAS MSA |
The following issue was fixed in TS250R023: - After installing TS250R021, the controller CompactFlash may be set to Write-Through mode, causing reduced system performance.
The following issues were fixed in TS250R021:
- Alerts indicating that a disk channel has gone into a degraded state have been modified so that the normal reduction of channel speed due to intermittent noise should no longer generate a Warning alert.
- Preliminary reporting of a supercap overcharge failing condition was removed.
- When the array received a DHCP address from a DHCP server, it responded with a unique hostname, which displayed in the DHCP server. This unique hostname overwrote the hostname supplied by the DHCP server in option 012.
- Hyper-V servers could not be migrated to P2000 G3 storage systems. Support for Hyper-V Live Migration has been added.
- P2000 G3 storage systems were not discovered by Storage Essentials software.
- Controllers were unresponsive to CLI requests for up to 30 minutes after a firmware update.
- For SMI-S, inconsistent data was provided for the CIM_AuthorizedPrivilege instance.
- SMI-S queries might fail if Small Footprint CIM Broker daemons are restarted after a memory threshold limit is reached. After enabling either SMI-S protocol, the SMI-S service on the array will now consistently start.
Please refer to the Release Notes for more details. The following features were added or enhanced in the TS250R021 firmware release: - Added the ability to change the link speed (100Mbps, 10Mbps) and duplex (half, full) mode of the controller management port.
- After a reconstruction completes, an event is now logged that includes the number of unrecoverable errors, if any.
- When event 173 'An error was reported by a disk' is reported due to a vdisk being dequarantined, the message now includes the state of the vdisk and indicates whether the dequarantine was automatic or was requested manually.
- In the CLI, the trust command now indicates disks that are out-of-sync, the age of the disk to indicate how far out of sync it is, and disks that were used for reconstruction but where reconstruction did not complete. The user is given the choice to include the out-of-sync or partially reconstructed disks, to exclude them, or to abort. If no out-of-sync or partially reconstructed disks are present, the command continues without a prompt.
- The Clear Disk Metadata function of the SMU now prompts to confirm the operation, allowing the user a chance to reconsider the possibly destructive results of the operation.
- Included instructions for obtaining historical performance data in the FTP prompt.
- Fibre Channel soft loop IDs are now retained during controller failover and failback.
Please refer to the Release Notes for more details. (2 Nov 2012) Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
IMPORTANT: HP P2000 G3 arrays running TS100 firmware cannot be directly upgraded to TS240 using this firmware package. Such arrays will have to be upgraded to TS201 or TS230 firmware first before using this firmware package to upgrade them to TS240.
Supersedes:
| P2000 G3 MSA controller firmware version | P2000 G3 MSA controller model | | TS240P003 | All HP P2000 G3 MSA System controller models | | TS240P001 | All HP P2000 G3 MSA System controller models | | TS240R037 | All HP P2000 G3 MSA System controller models | | TS230 | All HP P2000 G3 MSA System controller models | | TS220 | HP P2000 G3 1GbE iSCSI MSA | | TS210 | HP P2000 G3 10GbE iSCSI MSA | | TS201 | HP P2000 G3 FC and FC/iSCSI MSA | | TS200 | HP P2000 G3 SAS MSA |
The following issues were fixed in TS240P004: - Remote Snap Replication (RSR) generated page fault errors in some configurations.
- RSR schedule modifications automatically advanced the Next Time field by 24 hours.
- In single-controller configurations with an attached drive enclosure, the health check returned incorrect information about the drive enclosure, the controller it is connected to, and the controller enclosure.
- In dual-controller configurations, under rare circumstances, SNMP operations halted on controller B.
- In the SMU, errors were displayed when changing Single Controller Mode settings.
Please refer to the Release Notes for the complete listing of fixes. The following features were added or enhanced in the TS240R037 firmware release: - Support for VMware vSphere Aware Storage API) (VASA). When the HP Insight Control for VMware vCenter Storage Module v7.0 (or higher) is installed, the VMware VASA API can be used to provide visibility into the physical storage infrastructure through vCenter. The Insight Control Storage Module can be downloaded from the HP Software Depot website (http://www.hp.com/go/softwaredepot).
- Performance Monitoring has been expanded to include:
- Disk performance statistics are collected every 15 minutes and retained for 6 months.
- Historical performance statistics can be graphed for either a single disk or for all disks in a vdisk in the SMU.
- Graphs show the latest 50 samples by default, but may be set for a different time period. If the specified time period includes more than 50 samples, the data is aggregated into 50 samples.
Please refer to Release Notes for complete list of enhancements.
(6 Jul 2012) Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.
This package is only required for customers wanting to downgrade from TS240 to TS230. This package contains the same firmware payload as TS230P008. The following fix was incorporated in smart component (upgrade installer): - In very rare scenarios, the smart component (upgrade installer) when terminated abruptly would not restore the FTP settings back to original values.
The following fix was incorporated in TS230P008:
The following fix was incorporated in TS230P007:
The following fixes were incorporated in TS230P006:
3 TB SAS drives failed to report media errors in the region above 2 TB. Creating a vdisk on 3 TB drives failed with an “invalid device was specified” message. During RAID5 partial stripe writes of a bad block recovery, parity data was not properly cached, causing the controller to halt. The Restore Factory Defaults option did not reset the IP addresses. WWN was case-sensitive (and should not be). In multipath (dual-domain) environments, during a failover and failback or shutdown and restart situation, SCSI registrations were over-allocated, which caused one of the I/O paths to not be recognized. A master volume could not be converted to a standard volume. When doing a rollback of a 2 TB Snapshot, there was a possibility that the controller would stall. Firmware updating issues:
Please refer to the Release Notes for the complete listing of fixes, enhancements, known issues and work-arounds corresponding to this firmware.The following enhancement was incorporated in smart component (upgrade installer): - The smart component (upgrade installer) has been enhanced to support firmware downgrade from TS240. This does not involve any changes to the firmware payload.
The following enhancement was incorporated in TS230P006:
In the event logs, for messages about leftover drives, changed the Recommended Action portion of the Event and Health Reason fields to point to the HP MSA2000/P2000 Guided Troubleshooting Best Practices document.
The following enhancements were incorporated in TS230R044:
Remote snap operations are now supported on HP 1GbE iSCSI MSA and HP 10GbE iSCSI MSA System controllers. Remote snap operations and I/O can be processed simultaneously on HP 1GbE iSCSI MSA and HP 10GbE iSCSI MSA System controllers. A new tool was created to check the local system link. Added support for vStorage APIs for Array Integration (VAAI), to offload certain processing functions from the host to the array, which can greatly enhance performance. Improved handling of drives that are slow to spin up or are missing by quarantining the vdisk, rather than taking it offline, and automatically dequarantining the vdisk when sufficient drives become available.
|
|
