HP P2000 G3 MSA Systems Controller Firmware TS230P008 Release Notes

Version: TS230P008


Firmware included in this package adds improvements and corrects issues found during use and additional qualification testing after initial product release.

This package includes both array controller firmware and approved companion versions of drive enclosure firmware. When installing array controller firmware, the process also updates firmware on attached drive enclosures.

IMPORTANT: TS230 merges firmware for all HP P2000 G3 MSA System controllers into the same firmware stream.

Update recommendation  Recommended


P2000 G3 MSA controller firmware versionP2000 G3 MSA controller model
TS230R044 and TS230P006, TS230P007All HP P2000 G3 MSA System controller models
TS220HP P2000 G3 1GbE iSCSI MSA
TS210HP P2000 G3 10GbE iSCSI MSA
TS201HP P2000 G3 FC or FC/iSCSI MSA
TS200HP P2000 G3 SAS MSA

Versioning key: AxxxByyy-zz

Where the following letters represent release information about the firmware version:


MSA model. (TS=P2000 G3, M=MSA2000 G2, J=MSA2000)


Firmware version. This value changes for major, scheduled releases. Depending on the MSA model, this number may also indicate model protocol.


Type of release. (R=Regular release, P=Planned update to a regular release, S=Special release)


Major release number.


Minor release number.

..Product models

HP P2000 G3 MSA System controllers:

  • HP P2000 G3 10GbE iSCSI MSA Array System Controller (P2000 G3 10GbE iSCSI MSA Controller)

  • HP P2000 G3 1GbE iSCSI MSA Array System Controller (P2000 G3 1GbE iSCSI MSA Controller)

  • HP P2000 G3 Fibre Channel/iSCSI Modular Smart Array Controller (P2000 G3 FC/iSCSI MSA Controller)

  • HP P2000 G3 Fibre Channel Modular Smart Array Controller (P2000 G3 FC MSA Controller)

  • HP P2000 G3 SAS MSA Array System Controller (P2000 G3 SAS MSA Controller)

..Additional devices supported

HP Drive Enclosures:

Drive enclosure modelSupported drive enclosure firmware
HP P2000 LFF Drive EnclosureS110P30
HP MSA2000 3.5-inch LFF Drive EnclosureO320B07
HP D2700 SFF Drive Enclosure0131
HP 70 Modular Smart Array2.28

..Operating systems

Supported operating systems in iSCSI connect environments:

  • Citrix Xen Server HP Enterprise Edition

  • Microsoft Windows 2003 (IA32, x64)

  • Microsoft Windows Server 2008 (IA32, x64, x64 Hyper-V)

  • Red Hat Enterprise Linux 4 (IA32, x64)

  • Red Hat Enterprise Linux 5 (IA32, x64)

  • Red Hat Enterprise Linux (x64)

  • SuSE Linux Enterprise Server 10 (IA32, x64)

  • SuSE Linux Enterprise Server 11 (IA32, x64)

  • VMware vSphere 4 (ESX4, ESXi)

  • VMware vSphere 4.1 (ESX4.1)

  • VMware vSphere Hypervisor (formerly ESXi)

Supported operating systems in Fibre Channel connect environments:

  • Citrix XenServer HP Enterprise Edition

  • HP OpenVMS IA64 8.3

  • HP OpenVMS IA64 8.3-1H1

  • HP OpenVMS IA64 8.4

  • HP-UX 11.23 IA

  • HP-UX 11.31 IA

  • Microsoft Windows 2003 (IA32, IA64, x64)

  • Microsoft Windows Server 2008 (IA32, IA64, x64, x64 Hyper-V)

  • Red Hat Enterprise Linux 4 (IA32, IA64, x64)

  • Red Hat Enterprise Linux 5 (IA32, IA64, x64)

  • Red Hat Enterprise Linux 6 (x64)

  • Solaris 10 (x86/x64)

  • SuSE Linux Enterprise Server 10 (IA32, IA64, x64)

  • SuSE Linux Enterprise Server 11 (IA32, IA64, x64)

  • VMware Infrastructure 2 (ESX3.5, ESXi)

  • VMware vSphere 4 (ESX4, ESXi)

  • VMware vSphere 4.1 (ESX4.1)

  • VMware vSphere Hypervisor (formerly ESXi)

Supported operating systems in SAS connect environments:

  • Citrix XenServer HP Enterprise Edition

  • Microsoft Windows Server 2003 (IA32, x64)

  • Microsoft Windows Server 2008 (IA32, x64, x64 Hyper-V)

  • Red Hat Enterprise Linux 4 (IA32, x64)

  • Red Hat Enterprise Linux 5 (IA32, x64)

  • Red Hat Enterprise Linux 6 (x64)

  • Solaris 10 (IA32, x64)

  • SuSE Linux Enterprise Server 10 (IA32, x64)

  • SuSE Linux Enterprise Server 11 (IA32, x64)

  • VMware vSphere 4 (ESX4, ESXi)

  • VMware vSphere 4.1 (ESX4.1)

  • VMware vSphere Hypervisor (formerly ESXi)

Supported operating systems when installing the Smart Component firmware package:

  • Microsoft Windows Server 2003 (x86, x64, IA64)

  • Microsoft Windows Server 2008 (x86, x64, IA64)

  • Red Hat Enterprise Linux 4 and 5 (x86, x64, IA64)

  • SuSE Linux Enterprise Server 10 and 11 (x86, x64, IA64)


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.


The following fix was incorporated in TS230P008:

  • It was possible to access an encrypted user password file.

The following fix was incorporated in TS230P007:

  • Adjusted a parameter to ensure compatibility between all versions of hardware components used in P2000 enclosures. This was necessitated by a hardware component change on P2000 G3 MSA System controllers and on P2000 drive enclosure I/O modules.

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:

    • A power cycle was required after updating firmware.

    • Update did not complete.

The following fixes were incorporated in TS230R044:

  • In dual-controller configurations, communications between the controllers has been improved to prevent the controllers from becoming unresponsive and requiring that they be re-seated (removed and reinstalled) to reactivate them.

  • Removed a situation that caused a controller to become unresponsive.

  • If parity errors are found during a RAID 50 vdisk scrub, a verify is now automatically started.

  • Changed the reporting of a Compact Flash failure. It is now reported as an Error event, not an Informational event.

  • In SMI-S environments, creating a subscription using the HP SIM client now works as expected.

  • CIM_ObjectManager and CIM_Namespace class instances now return only the properties requested.

  • HP P2000 G3 iSCSI MSA Systems no longer provide FCTargetPorts registered profile instances.

  • Added hostname and namespace details to the value of AlertingManagedElement property of CIM_AlertIndication instances.

  • There was a value mismatch between CIM_StorageSetting and CIM_StorageCapabilities classes.

  • There was an association issue between the classes CIM_ConcreteExtent and CIM_ConcretePool.

  • Improved the response time for associators related to CIM operations.

  • There was an invalid CIM_ProtocolControllerForUnit association between Volume and iSCSI ProtocolController instances.

  • When using SMI-S, values for key properties of the Indication Profile are no longer empty.

  • When using SMI-S in HP-UX environments, the ElementSettingData association now works as expected.

  • Added RAID value in the pool capabilities class instance.

  • All time zones are now supported.

  • Corrected disk quarantine behavior so that, when a system is power cycled, invalid Leftover drives are not detected as Leftover or considered as valid vdisk members.

  • Improved firmware updating logic to ensure that the Expander Controller (EC) is updated as expected.

  • Improved messaging about power cycling the array during a firmware update.

  • HP brand and naming is now properly displayed.

  • When a vdisk expansion is requested, the confirmation response has been modified to recommend that the user access online help for more information. Online help also includes directions for how to obtain the HP P2000 G3 MSA Best Practices – Technical White Paper, available on the HP P2000 G3 MSA website at http://www.hp.com/go/p2000. To locate the paper, in the gray selection box, under “Product Information,” click Resource library and scroll through the display.

  • Email addresses are limited to 31 characters by the user interfaces and are now enforced. Because this limit was not enforced previously, it caused the Management Controller to reboot if more than 31 characters were attempted.

  • For the Japanese locale, “create replication” caused a JavaScript error.

  • Removing and installing a drive in a cascaded MSA70 drive enclosure is now reported as expected.

  • Online help in both the SMU and CLI has been updated to better describe disk status meanings and recommended actions.

  • SCSI reservations were dropped when repeated Test Unit Ready commands were sent.

  • Results of the “verify links” command were made more stable.

  • Can now expand vdisks that contain single-ported SATA disks. For information about best practices regarding vdisk expansion, see the HP P2000 G3 MSA Best Practices – Technical White Paper, available on the HP P2000 G3 MSA website at http://www.hp.com/go/p2000.

  • Online help was updated for the SMU verify link task and CLI verify remote–link command.

  • Scheduled operations did not fail over properly when an MC was rebooted.

  • Added informational messages to the SMU and CLI regarding the Export Snapshot task. It is important to note that, if a snap pool becomes critical, all snapshots may be deleted, even an exported snapshot with data that is connected to a host.

  • When a snap pool reaches 100%, Media Write Protect errors were returned on writes. The snap pool critical threshold was changed from 99% to 98%, to handle the time required for the deletion of snapshots, if that policy is employed, and reduces the likelihood of returning Media Write Protect errors.

  • The title or subject of several events was changed from "BAD EVENT DECODE" to now include descriptive text.

  • Modified the Volume Copy schedule With Modified Data checkbox, so that schedule modification works as follows: when modifying the Volume Copy schedule for a volume, the checkbox is disabled; when modifying the Volume Copy schedule for a snapshot, the checkbox is enabled.

  • Updated snapshot schedule to show the correct status and time of the next scheduled snapshot.

  • Snap pools showed as available, but the master-volume showed as "SP Not Accessible."

  • The following fixes are specific to Remote Snap:

    • If verify link fails due to CHAP authentication failure, the user is now provided with an event or notification.

    • A duplicate replication set identifier or snapshot identifier can no longer be specified for a replication set.

    • Scheduled replications now start and stop correctly; all date constraints are now working properly.

    • Updated calculation and display so that, after 24 hours have passed for replication, the timer is correct.

    • If a partner controller is restarted during replication, settings in the Scheduler are maintained; no extraneous replication images are created.

    • Replication schedules no longer cause the SMU to time out and become unresponsive.

    • Improved the messaging when attempting to detach a secondary replication volume and an initial replication has not occurred.

    • When creating replication sets, if network settings are configured incorrectly, the correct error message is now displayed.

    • Snapshot sync points are now displayed correctly.

    • No snapshots are taken after the schedule has expired.

    • The controller no longer hangs when trying to add an invalid Remote Snap destination-volume.

  • The following fixes are specific to the Storage Management Utility (SMU):

    • In the Configure Host Interface page, the Apply button was incorrectly displayed for SAS Controllers.

    • The Provisioning wizard now permits a vdisk to be created with 128 volumes.

    • On the Add Remote System page, the Password field could be left blank. A valid entry is now required.

    • Reworded the message displayed for the Rename Host task.

    • Online help was updated to reflect that no progress bar or message is displayed when a roll back is in progress.

    • Single-ported SATA drives installed in cascaded HP D2700 drive enclosures now show the correct status information; they are no longer displayed as “degraded.”

    • Corrected name and fan information displayed for D2700 drive enclosures.

    • When running the Verify Vdisk utility, the Abort Verify Vdisk button is no longer grayed-out.

  • The following fixes are specific to the Command Line Interface (CLI):

    • For scripted CLI, removed an issue that caused the controller to crash and generate communication errors.

    • set cache-parameters command: If the command syntax is correct, the “An invalid device was specified” message is no longer displayed.

    • create vdisk command: The assigned-to parameter is now ignored when in single-controller mode.

    • set cli-parameters command: Is now recorded in the specified locale language, not the previous locale language.

    • set cli-parameters and show cli-parameters commands: Corrected wording inconsistency in the online help.

    • create volume-set command: Updated online help.

    • vdisk shutdown command: A vdisk that has been stopped now displays the Status as STOP, and the Health as Unknown.

    • set advanced settings command: The following parameter settings are now recognized: enable, enabled, disable, and disabled.

    • show controllers command: Corrected the display to remove the possibility of a rare display of an unclear error message.

    • show replication-volumes command: Corrected the display.

    • create user command: If conflicting base and storage-size-base parameters are both set, an error message is now displayed.

    • map and unmap commands: If the host parameter is incorrectly entered in double quotation marks, the quotation marks are now ignored.

    • delete snapshot command: The delete-rolloff-snapshot parameter was removed. Use the delete-volume-copy-snapshot parameter instead.

    • delete snapshot command: If this command is run with the cleanup, delete-priority standard-snapshot, and force parameters specified, the snapshot and snap pool are now deleted as expected, including that the Master Volume is converted to a Standard Volume.

    • clear disk-metadata command: Corrected online help to show that the parameter is disk-metadata, not disk metadata, which implied that disk was a valid parameter.

    • Removed a possibility of unauthorized access to the CLI.

    • reset controller-statistics command: Disk and host port statistics have been separated from controller statistics, to improve accuracy of rates.

..Important firmware notes

  • If you intend to use Windows Dynamic Disk (software RAID) on top of your hardware RAID, there are some cautions to be considered. For more information, see the section "Real World: Dynamic versus Basic Disks" in 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.

  • 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 external-view volume of a replication set, do so from the destination system first, then perform the change on the source system.

  • MSA70 disk enclosures are supported for use with P2000 G3 arrays running TS230 or later firmware, but must have firmware 2.28 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 60/70 Modular Smart Array Enclosure Firmware 2.28 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.

..Installation instructions

Installation notes and best practices

WARNING! Do not cycle power 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 system 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.

Before installing this firmware, note the following:

  • The firmware package must be downloaded from the HP website and saved to the local filesystem.

  • FTP and telnet must be enabled on the arrays being updated.

  • It is a recommended best practice to ensure that you have a full backup prior to any firmware upgrade.

  • Schedule an appropriate time to perform an online upgrade:

    • For single domain systems, I/O must be halted.

    • For dual domain systems, because the online firmware upgrade is performed while host I/Os are being processed, I/O load can impact the upgrade process. Select a period of low I/O activity to ensure the upgrade completes as quickly as possible and avoid disruptions to hosts and applications due to timeouts.

  • When planning for a firmware upgrade, allow sufficient time for the update.

    • In single-controller systems, it takes approximately 30 minutes for the firmware to load and for the controller to automatically restart. Depending on the environment, it may take as long as one hour to complete.

    • In dual-controller systems, the second controller takes approximately an additional 30 minutes to update, but may take as long as one hour, depending on the environment.

  • During the installation process, monitor the system to determine update status and know when the update is complete.

  • After the installation process is complete and all controllers have automatically restarted, verify system status in the SMU or CLI and confirm that the new firmware version is displayed as running on all controllers.

  • Updating array controller firmware may result in new event messages that are not described in earlier versions of documentation. For comprehensive event message documentation, see the most current version of the HP P2000 G3 MSA System Event Descriptions Reference Guide.

  • The Smart Component update process logs messages to \CPQSYSTEM\Log\cpqsetup.log on the system drive in Windows and /var/cpq/Component.log in Linux.

  • The Smart Component update process manages the FTP & Partner Firmware Update (PFU) enable/disable settings.

Installing firmware using Smart Components—Windows environments

This is a self-extracting executable module. You can execute this module from the Windows graphical user interface (GUI) or the command line interface (CLI).

GUI option

  1. Place the downloaded firmware package in a temporary directory.

  2. Using Windows Explorer, navigate to the directory containing the download.

  3. Double-click the executable file.

  4. Follow onscreen instructions.

    NOTE: When prompted for logon information, enter credentials for an account with management access rights.

CLI option

Execute the Smart Component by entering the following command: CPxxxxxxx.exe /target <ip_address> /user <username> /passwd <password> /s


  • ip_address is the management IP address of the array controller

  • username is the username account with management rights

  • password is the password for username

Instead of command line parameters you can use the following DOS environment variables:

  • oa_address: set this variable for the IP address of array controller

  • oa_username : set this variable for the username of array controller

  • oa_password : set this variable for the password of array controller

NOTE: When prompted for logon information, enter credentials for an account with management access rights.

Installing firmware using Smart Components—Linux environments

  1. Place the downloaded firmware package in a temporary directory.

  2. Open a Linux command console.

  3. From the directory containing the downloaded file, enable execute access to this model by entering chmod +x CPxxxxxx.scexe, where CPxxxxxx.scexe represents the downloaded file.

  4. Execute the Smart Component by entering a command similar to the following: ./CPxxxxxx.scexe --target <ip_address> --user <username> --passwd <password>


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

  5. Follow onscreen instructions.

    NOTE: When prompted for logon information, enter credentials for an account with management access rights.

Installation troubleshooting

If you experience issues during the installation process, do the following:

  1. When viewing system version information in the SMU System Overview panel, if an hour has elapsed and the components do not show that they were updated to the new firmware version, refresh the web browser. If version information is still incorrect, proceed to the next troubleshooting step.

  2. If version information does not show that the new firmware has been installed, even after refreshing the browser, restart all system controllers. For example, in the CLI, enter the restart mc both command. After the controllers have restarted, one of three things happens:

    • Updated system version information is displayed and the new firmware version shows that it was installed.

    • The Partner Firmware Update process automatically begins and installs the firmware on the second controller. When complete, the versions should be correct.

    • System version information is still incorrect. If system version information is still incorrect, proceed to the next troubleshooting step.

  3. Verify that all system controllers are operating properly. For example, in the CLI, enter the show disks command and read the display to confirm that the information displayed is correct.

    • If the show disks command fails to display the disks correctly, communications within the controller have failed. To reestablish communication, cycle power on the system and repeat the show disks command. (Do not restart the controllers; cycle power on the controller enclosure.)

    • If the show disks command from all controllers is successful, perform the firmware update process again.

..Known issues and workarounds

Issue: The P2000 G3 SAS MSA array shows that it is degraded when connected to a host via a Smart Array P411 Controller.

Workaround: Disregard this degraded host port state on the ports connected to a Smart Array P411 Controller.

The P2000 G3 SAS MSA array connected to the Smart Array P411 Controller is supported only on hosts running HP-UX 11.31. In this configuration, the Smart Array P411 Controller does not enable all four of the SAS PHYs, resulting in a degraded state on the host port of the P2000 G3 SAS MSA array. A warning similar to the following is generated on every reboot of a host connected to the P2000 G3 SAS MSA array via a Smart Array P411 Controller:

P2000 G3 SAS Array SN#00C0FFDABD8A Controller B WARNING Host SAS topology was changed. (host port: 1, 1 out of 4 PHYs are up, link speed: 6 Gbps)

Issue: When using the USB port of a personal computer or laptop connected to the server to initially configure an HP P2000 G3 MSA array, some computers or laptops may not properly connect to the array.

Workaround: Access and configure the MSA using the HP P2000/MSA2000 Device Discovery Tool for Windows. The Device Discovery Tool discovers MSA storage devices in the network, in the local subnet, and directly attached to a server. The following tasks can be performed using the Device Discovery Tool:

  1. Launch the Storage Management Utility (SMU) for a selected discovered MSA device.

  2. Launch the Command Line Interface (CLI) or FTP interface for the selected discovered MSA device.

  3. Schedule a recurring collection of MSA storage log files for the selected discovered MSA device.

  4. Generate an XML or text informational output report.

The Device Discovery Tool is available on the HP P2000/MSA2000 Software Support/Documentation DVD and HP MSA P2000 website.

Issue: When installing a firmware update using the Smart Component, the installation routine may incorrectly report that the upgrade was unsuccessful.

Workaround: If the Smart Component installation routine states that a firmware load was unsuccessful, verify which version of firmware is installed using an array management utility, such as the SMU or CLI. If the version listed is the old version, run the Smart Component again.

Issue: When creating a user or modifying user information in the SMU, there is no option to enable the SMI-S interface for the user.

Workaround: Add the SMI-S interfaces to the user using the set user interfaces CLI command, making sure to include all appropriate interfaces.

Issue: If the iSCSI IQN name is longer than 55 characters, the enumeration of CIM_StorageHardwareID fails.

Workaround: Modify the IQN name to be shorter than 55 characters

Issue: Manually creating a replication-prepared (secondary) volume and associating it with a primary volume originally created with pre-TS230 firmware can fail. Automatically created secondary volumes do not have this problem.


  • In the SMU, use the Replication Setup Wizard or the Replicate Volume task or, in the CLI, use the create replication set command to automatically create the secondary volume. (Preferred workaround)

  • Issue the following commands in the CLI to specify the block size of the manually created secondary volume, ensuring that it is exactly the same size as the source volume (Alternative workaround):

    1. In CLI API format, use the show volumes <volume-name> command to determine the size of the pre-T230 volume in blocks. This is displayed by the "size-numeric" property.

    2. Use the create volume command and specify the size in blocks (obtained in Step 1) to create the replication-prepared volume.

    3. Create a replication set that associates the two volumes.

Issue: During path failover events on systems with large LUN counts, Red Hat Enterprise Linux 4 iSCSI clients may report issues accessing devices.

Workaround: Increase the disk timeout to a minimum of 60 seconds.

Issue: When using both the primary and secondary paths on both ports of the Qlogic iSCSI HBAs, failover does not work correctly on cable pulls.

Workaround: When setting up the Qlogic iSCSI HBAs, set up only the primary path for both ports.

Issue: When creating a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array stops mapping volumes to LUNs, but creates the volumes as requested.

Workaround: Ensure that there are no LUN conflicts before creating the volume set with mapping or map the remaining volumes to LUNs after the conflict.

Issue: For HP P2000 G3 Fibre Channel MSA systems connected directly to the server, the QLogic 8 Gb FC driver version on Microsoft Windows Server 2008 R2 x64 does not see LUNs when the array is set up for point to point.

Workaround: Change the array host ports to loop mode.

Issue: For HP P2000 G3 SAS MSA systems, failover is slow when more then 128 LUNs are accessed from a Red Hat Enterprise Linux 4.x or SuSE Linux Enterprise Server 10 SP3 client.

Workaround: Map less then 128 LUNs to SAS clients.

Issue: In dual-controller systems, accessing the SMU of a controller does not display vdisks owned by the other controller.

Workaround: Restart the other controller.

Issue: In the CLI, the TakeSnapshot task returns the message: “Unable to validate retention limits. – The user is not recognized on this system.”

Workaround: Restart the controller accessed.

Issue: In the SMU, the Japanese version of some pages and some error messages displays English text.

Workaround: None.

Issue: A failed drive becomes available when the vdisk that it was a member of is deleted.

Workaround: Do not use the drive.

Issue: The array incorrectly accepts a DNS name for the address of the NTP server in the Storage Management Utility. The array does not use DNS, and translates the name into an invalid “” IP address.

Workaround: Instead of a network name, enter the NTP server IP address.

Issue: In the Command Line Interface, the array incorrectly accepts a DNS name for the address for the SMNP, SMTP, and NTP servers. The array does not use DNS, and cannot connect to the server correctly.

Workaround: Instead of network names, enter the IP addresses for the servers.

Issue: In Windows configurations, the IQN shown by the NC551 card during POST may not match the IQN seen in the array controller. This occurs when the NC551 was set up in a boot-from-storage configuration. After an operating system is installed, the POST message shows the IQN that is supplied by the iSCSI Software Initiator, but the NC551 BIOS continues to use the IQN setup to boot the OS.

Workaround: Using the NC551 BIOS Utility, remove the boot settings and then log back into the array with the new IQN. If the volume used for mapping was explicitly mapped to the host, recreate the mapping for the new IQN.

Issue: When accessing more than 128 LUNs using a Qlogic iSCSI HBA in boot-from-storage configurations, the system may hang when a reset is issued on the array.

Workaround: Access 128 LUNs or less via the Qlogic iSCSI HBA when using the card in boot-from-storage configurations.

Issue: RHEL 4.8 may not discover all multipath devices and partitions during boot or reboot.

Workaround: This issue is addressed by applying the updated device-mapper-multipath package described in RedHat Bug Fix Advisory RHBA-2009:1524-1, available at http://rhn.redhat.com/errata/RHBA-2009-1524.html.

Issue: RHEL 5.4 may not discover all multipath devices and partitions during boot or reboot.

Workaround: This issue is addressed by applying the updated device-mapper-multipath package described in RedHat Bug Fix Advisory RHBA-2010:0255-1, available at https://rhn.redhat.com/errata/RHBA-2010-0255.html.

Issue: Under rare circumstances, some events from one controller are not seen on the other controller.

Workaround: Review the events from both controllers.

Issue: During a firmware upgrade, the firmware bundle version may show incorrectly.

Workaround: Wait until the firmware upgrade process is complete before checking the firmware bundle version.

Issue: Java script issues are seen when using Microsoft Internet Explorer in multi-byte language locales, resulting in truncated messaging and hung pop-up windows. These issues will be resolved in a future firmware release.

Workaround: This is a display problem only. When a pop-up window remains on screen with no update for a prolonged period, close and then re-open the browser. The Internet Explorer English locale and the Firefox browser do exhibit the issues.

Issue: In SLES 11 environments, when using the iSCSI initiator tools included in SLES 11, the host occasionally does not correctly log into the iSCSI array on reboot, even when set to automatically connect.

Workaround: Restart the iSCSI service on the SLES 11 host. This can be done by entering the following command: /etc/init.d/open-iscsi restart

Issue: SLES 11 may require multiple minutes (15+/-) to create all multipath devices during boot. This typically involves a system with a large number of LUNs and multiple LUN paths.

Workaround: None. Wait for the system to complete LUN and path discovery.

Issue: SLES 11 SP1 may not create all devices during boot. This typically involves a system with a large number of LUNs, multiple LUN paths, and the SLES 11 SP1 open-iscsi utilities.

Workaround: Do one of the following:

  • Install the following Novell patches:

    • kpartx-0.4.8-40.23.1.x86_64.rpm

    • libvolume_id1-128-13.11.4.x86_64.rpm

    • multipath-tools-0.4.8-40.23.1.x86_64.rpm

    • open-iscsi-2.0.871-0.22.1.x86_64.rpm

    • udev-128-13.11.4.x86_64.rpm

  • Run the /sbin/multipath -v 0 command to force multipathd to rescan all LUNs and paths and create any devices that were not correctly created before.

Issue: In rare conditions, the array controller may report that a supported 10 GbE SFP+, 10GbE Copper Cable, or 10GbE Direct Attach Cable is unsupported. This condition is most likely to occur when a SFP+, Copper Cable, or Direct Attach Cable is hot plugged into the controller while the controller is running. When this occurs, the following Warning message is recorded in the event logs: “An unsupported cable or SFP was inserted." At the same time, the host port does not show a status of "Down."

Workaround: Do the following:

  1. Verify that the SFP+, Copper Cable, or Direct Attach Cable is a supported component. For support information, see the P2000 G3 QuickSpecs on the P2000 G3 product page: http://www.hp.com/go/p2000.

  2. If the components are listed as supported models, remove and reinsert the SFP+, Copper Cable, or Direct Attach cable.

  3. If this does not correct the issue with the SFP+, Copper Cable, or Direct Attach Cable connected to the controller, either remove and reinsert the controller or power down and reapply power to the array.

Issue: RHEL 5 Update 5 does not shutdown properly when using the iSCSI initiator utilities shipped in RHEL 5 Update 5 to access the array.

Workaround: See issue 583218 on the Red Hat Bugzilla bug-tracking system https://bugzilla.redhat.com/show_bug.cgi?id=583218 for the current status of the issue and possible workarounds.

Issue: When using explicit LUN mapping, using long IQN names for the iSCSI Initiator can cause the array to map the LUN incorrectly. A predefined area is used to store explicit LUN mapping information per LUN and, with longer IQN names, this area can be exhausted. This issue is not dependent on the number of paths to the LUN.

Workaround: Shorten the IQN name on the nodes.

The following formula is used to calculate the maximum IQN name length based on the number of hosts being explicitly mapped to a LUN on the array:

 Maximum IQN Character Length = (4083 / n) – 7
(Where n = number of hosts nodes explicitly mapped to a LUN on the array.)
 NOTE: By specification, 223 is the maximum IQN length allowed.

The following table provides the calculated values based on the number of hosts being explicitly mapped to a LUN on the array:

Number of hosts explicitly mapped to a LUN and the maximum IQN character length Number of hosts explicitly mapped to a LUN and the maximum IQN character length Number of hosts explicitly mapped to a LUN and the maximum IQN character length
1–17223 33116 4976
1821934113 5074
1920735109 5173
2019736106 5271
2118737103 5370
2217838100 5468
231703997 5567
241634095  5665
251564192 5764
261504290 5863
271444387 5962
281384485 6061
291334583 6159
301294681 6258
311244779 6357
321204878 6456

Issue: USB CLI becomes unusable after a Management Controller reboot in Windows environments.


  1. Close down the terminal application. (Example: HyperTerminal)

  2. Open Device Manager and disable the “Disk Array USB Port” under Ports (COM & LPT).

  3. Re-enable the “Disk Array USB Port.” If the problem persists, reboot the host.

Issue: The mini-USB CLI port on the array controller does not work.

Workaround: Install a device driver for the mini-USB CLI port. This driver is packaged as a Smart Component and is available for download on the P2000 G3 support page.

Issue: When using SMI-S, only partial support is provided for iSCSI Target Ports Subprofile.

Workaround: None.

Issue: When using SMI-S, the ExtentStatus property in StorageVolume is always set to “2.”

Workaround: None.

Issue: When creating a storage repository with Citrix 5.5 update 2 and attaching it to the server pool while the servers in the pool are on, the storage repository is only multipathed on the master server. This seems to happen only with the first storage repository created after rebooting the servers. If a second storage repository is created and attached (without rebooting the servers), that storage repository is correctly multipathed with all servers in the pool.

Workaround: Detach and reattach the storage repository. The storage repository is multipathed with all servers in the pool.

Issue: In HP-UX 11.23, I/O may take a long time to complete.

Workaround: Ensure that the primary path is the first path in the PV-Links configuration.

Issue: There is no indication that a LUN has failed over to the other controller.

Workaround: Using the Storage Manage Utility (SMU), open up system events and scan for failover events. When using the CLI, use the show events command.

Issue: When accessing the Command Line Interface (CLI), output from commands scroll by with no option to page through the output.

Workaround: Change the window height or scrollback value of the command window to a larger value and use the scroll bar on the command window to scroll through the CLI output.

Issue: A replication is initiated, but only a snapshot on the primary volume occurs, or the replication is queued.

Workaround: Ensure that all systems involved have valid replication licenses installed and that all volumes and vdisks involved in the replication have started, are attached, and are in good health, including vdisks that contain the snap pools for the volumes involved. A replication normally queues when a previous replication involving the same volumes is active.

Issue: A replication set was deleted, but is later shown with the primary volume status of “Offline” and the status-reason is record-missing.

Workaround: This generally occurs when the secondary volume is detached and its vdisk stopped when the replication set was deleted, and then the vdisk of the secondary volume restarted. To correct this issue, reattach the secondary volume, set it as the primary volume, and delete the replication set.

Issue: An error message indicating “controller busy” occurs while creating a replication set.

Workaround: Creating a replication set immediately following another replication set creation may result in "Controller Busy." This is expected behavior. Wait and try the operation again at a later time.

Issue: In the SMU, the Vdisk > Provisioning > Create Multiple Snapshots task allows a secondary volume to be selected, but fails the operation.

Workaround: User initiated snapshots are not allowed on secondary volumes. Do not select a secondary volume.

Issue: A scheduled replication is missing or replications are queued, but do not complete.

Workaround: A best practice is to schedule no more than four volumes to start replicating at the same time and for those replications to recur no less than 30 minutes apart. If you schedule more replications to start at the same time or schedule replications to start more frequently, some scheduled replications may not have time to complete.

Issue: Unable to perform a local replication (a replication where the external view volume and the destination volume reside on the same system) with a single vdisk.

Workaround: Create a second vdisk for the destination volume.

Issue: Deleting the replication-set from the destination system fails.

Workaround: Delete the replication set from the source system (the system where the external view volume resides.)

Issue: A replication set is missing the primary volume and the replication set cannot be deleted.

Workaround: Set the primary volume to the remaining volume in the set. You should then be able to delete the replication set.

Issue: On rare occasions, deleting a vdisk when volumes are in the process of rolling back may cause communications issues between the management controller and the storage controller.

Workaround: Cycle power on the array to resolve the issue. To avoid this situation, allow the rollbacks to complete or delete the volumes before deleting the vdisk.

Issue: Scheduled tasks are not occurring, and there is no indication of a problem in the schedules or the tasks.

Workaround: Restart both management controllers (MC) of the array(s) involved in the tasks.

Issue: While mapping a drive using the SMU, all ports are selected by default; this may result in a volume being presented to the same host via both protocols, which is unsupported.

Workaround: When creating and mapping a volume using the default mapping in the SMU on a Combo controller system, you must de-select either the iSCSI or the FC ports as this could result in the same LUN being presented to the same host via both protocols. This is unsupported and most multipath software does not handle the paths to the LUN correctly.

Issue: Cannot schedule volume copy operations, or scheduled volume copy operations for snapshots and standard volumes do not occur.

Workaround: Perform the volume copy manually. Scheduled volume copies of master volumes should complete successfully if the schedule permits completion of the volume copy before the next occurrence.

Issue: A P2000 G3 iSCSI MSA System LUN which has been newly added to a Citrix XenServer 5.6 pool may not return to an active Storage Repository (SR) state following removal or replacement of an array controller.

Workaround: To recover to an active Storage Repository state, restart the iSCSI session by executing the following command: /etc/init.d/open-iscsi restart

Issue: Debug logs are incomplete.

Workaround: Determine if the logs are incomplete by unzipping the log file retrieved from the array and examining the last line of the store_YYYY_MM_DD__HH_MM_SS.logs file for the lines: End of Data ]]></LOG_CONTENT></RESPONSE>. If the file contains these two lines at the end of the file, it is complete and you can forward it to your service support organization for analysis. If the file does not contain these two lines at the end, it is incomplete and may not be useful. In this case, repeat the log collection process after a 5 minute delay. Should the second collection contain the above specified lines at the end of the file, send it to your service support organization for analysis along with the first set of logs. However, if the second file does not contain the above specified lines at the end of the file, reboot the system and try once more to collect the logs. Be sure to send all collected logs back to your service support organization with a brief note explaining the actions you took and the result.

Issue: In a dual controller system, log in to one of the controllers fails, but log in to the other controller succeeds.

Workaround: Log in to the other controller and restart the inaccessible management controller using the CLI restart mc command or the SMU Tools > Shut Down or Restart Controller page.

Issue: IOPs and Bytes per second may be lower or higher than expected for the workload.

Workaround: This is a reporting issue and not a performance issue. The correct values can be calculated by using the change in the Number of Reads and Number of Writes over time to determine IOPs, and the change in Data Read and Data Written over time to determine Bytes per second.

Issue: The array controller may interpret a switch login as an HBA login and erroneously present the switch port as a discovered host. This does not affect storage functionality.

Workaround: Either identify the erroneous host and do not attempt to use, or Disable Device Scan on switch ports connected to the array controller and restart the array controller.

..Supersedes history

Firmware versionP2000 G3 MSA modelRelease date
TS230P008All November 2011
TS230P007All November 2011
TS230P006All August 2011
TS230R044 All July 2011
(updated release notes to announce support for P2000 G3 FC, FC/iSCSI, and SAS MSA Systems)
P2000 G3 1GbE iSCSI MSA and
P2000 G3 10GbE iSCSI MSA
June 2011
TS201P007 P2000 G3 FC MSA and
February 2011
TS220R004P2000 G3 1GbE iSCSI MSA November 2010
RS210R016P2000 G3 10GbE iSCSI MSA September 2010
TS200R021P2000 G3 SAS MSA June 2010

..Effective date

November 2011

November 2011

5 edition

Part number: 659521-005