Controller firmware: TS251P006
I/O module firmware: S200B28
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.
NOTE: The latest, approved companion versions of P2000 and MSA2000 drive enclosure firmware are included in this firmware package. When firmware on P2000 G3 MSA array controller enclosures is updated using this firmware package, firmware on cascaded P2000 or MSA2000 drive enclosures is also updated. If D2700 or MSA70 drive enclosures are cascaded from the P2000 G3 MSA array, firmware for those enclosures must be obtained and updated individually.
For a list of supported companion drive enclosure firmware, see “Additional devices”.
Controller firmware: TS251P005
|Operating system||HP P2000 G3 MSA System controller model|
|Apple Mac OS||X||X[a]|
|Microsoft Windows Server 2008||X||X||X||X||X|
|Microsoft Windows Server 2012||X||X||X||X||X|
|Red Hat Enterprise Linux 5.x||X||X||X||X||X|
|Red Hat Enterprise Linux 6.x||X||X||X||X||X|
|SuSE Linux Enterprise Server 10||X||X||X||X||X|
|SuSE Linux Enterprise Server 11||X||X||X||X||X|
|VMware 4.x — not supported|
[a] Supported for FC connections only.
[b] Supported for FC connections only.
[c] Supported for FC connections only.
[d] Supported for FC connections only.
|HP P2000 G3 MSA array controller firmware||Cascaded drive enclosure model||Recommended drive enclosure firmware|
|TS251||HP P2000 Drive Enclosure||S200B28|
|HP MSA2000 Drive Enclosure||O320B13|
|HP D2700 Drive Enclosure||0149|
|HP 70 Modular Smart Array||2.28|
IMPORTANT: After updating array controller firmware or after connecting new drive enclosures to an existing controller enclosure, verify the firmware compatibility of all devices. If needed, obtain and install the supported controller or drive enclosure firmware. Firmware is available for download at http://www.hp.com/support/p2000G3msa.
For complete instructions on how to ensure that your ESXi/ESX5.x host is ready for upgrading to TS251P003, refer to http://www.hp.com/support/p2000G3msa/troubleshooting.
NOTE: Failure to correctly remove the HP MSA VAAI Plug-in and associated claim-rules will result in degraded performance and possible loss of access to datastores.
The following features were fixed in TS251P006:
Updated Open SSL library to remove security vulnerability.
Corrected status reporting for power supplies and fans.
The following features were fixed in TS251P002:
|Removed OpenSSL CVE-2014-0160 (“Heartbleed”) vulnerability, and a newly issued SSL certificate has been applied to the array.|
|Fixed controller crash when one drive is removed from a RAID0 vdisk.|
|Modified drive read error detection and repair in the event of a drive read error.|
The following features were added or enhanced in controller firmware TS251R004:
|Added functionality to avoid insure proper branding problem after FW downgrade to TS240/TS230.|
|Enhanced the hardware failure event alerting.|
|Allowed background drive scrubs from controller B.|
|Upgraded Linux kernel to 18.104.22.168.|
|Enhanced the user creation policy to prevent use of restricted user names.|
|Fixed vdisk reconstruction event message to correlate with the correct status.|
|Improved "Health" reporting for sub-components of the controller.|
|Improved the Trust process.|
|Improved the restart sc both CLI command address arrays with single controller.|
|Added support for T10-compliance for VAAI.|
|Improved logging to prevent reset after upgrade.|
|Changed the criticality of CAPI event 172 from a warning to an error.|
|Changed the event level to critical rather than the present warning level, if a vdisk becomes critical and no spares are configured.|
|Improved the event notification to handle the situation if replication fails due to a bad block on the source volume.|
|Upgraded OpenSSH to 6.3.|
|Improved password security.|
|Enhanced help for G3 to G4 replication.|
|Enhanced remote command security.|
|Enhanced the quarantine function.|
|Enhanced extended copy command for T10 compliance.|
|Added warning message about default volume mapping in online help in the CLI and SMU. Also, default mapping requires confirmation in the SMU.|
|Improved failed drive reporting during medium error.|
|Improved text for compact flash failure event 204.|
The following features were fixed in TS251R004:
|After detaching the secondary volume and deleting the replication set, accessing the secondary volume failed.|
|Logs produced 0kb store.log files.|
|ATS command improperly aborted.|
|LSI logic chip returned bad link.|
|Disk drive error counters were not cleared for slot when a disk drive was replaced.|
|Disk drive did not become ready following a disk firmware update.|
|Get logs via ftp crashed.|
|MC rebooted due to timeout.|
|Pulling the Management Ethernet cable reset the link settings.|
|Changed the failure alert to show the correct power supply when you receive a 314 error.|
|Scheduler did not honor the "Time Constraint" and "Date Constraint" of the schedule policy.|
|Reverse sequential IO's crashed the controllers.|
|Controller B did not perform event notification when the Ethernet cable of Controller A was unplugged.|
|Cache sync failed.|
|Slow insertion of a controller caused incorrect modification to vdisk metadata.|
|Default iSCSI host IP settings did not persist after SC reboot or power cycle, after being set via MC CLI command restore defaults factory.|
|Drive scrub error stats were incorrect.|
|Security issues have been addressed.|
|Modified the permissions interfaces for admin user.|
|Incorrect shutdown status of both controllers was shown.|
|SMU showed incorrect message when restarting partner MC.|
|Incorrect table of contents displayed for Japanese help.|
|RAID 10 vdisk automatically de-quarantined with a stale disk.|
|The iSCSI Host Interfaces accepted duplicate IP addresses.|
|Host with profile openvms accepted LUN 0 while mapping a volume to a host.|
|Unable to get logs without restarting MC.|
|Replication not re-established following move of replication array.|
|Controllers crashed on login.|
|Controller crashed due to iSCSI connection loss.|
|Controller crashed during failback while replication in progress.|
|Rebuild targets did not go to leftover state when a drive is pulled, while reconstruction and de-quarantine were in progress.|
|Array health status was not propagated correctly in RAID 10 and RAID 50 vdisks.|
|Replications were suspended.|
|Array obtained a duplicate IP address when the array was configured for DHCP.|
|Unable to delete remote systems.|
|Continued to use old node world-wide name after controller replacement.|
|Schedules did not run or ran before the modified start time when an expired schedule was modified.|
|FRU list did not show fault on PSU.|
|MC locking issues occurred.|
|SNMP Get Fails -- SNMP agent died.|
|The vdisk name appeared as "Unknown name" when a volume was unmapped.|
|Single controller showed P2000 add-on enclosure as degraded.|
|MC firmware on Controller A did not upgrade if firmware on Controller B was upgraded.|
|Errors occurred in SSL connection.|
|Users were disconnected in SMU and CLI when deleting their own accounts.|
|Show disk information intermittently was not returned when partner controller was physically removed.|
|Controller crashed when using Remote Snap and the master volume was offline.|
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 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.
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.
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 might become inoperative. If this occurs, contact technical support. The module might 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.
IMPORTANT: In dual-module enclosures, both controllers or both I/O modules must have the same firmware version installed. Running different firmware versions on installed modules may cause unexpected results.
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.
It takes approximately 45 minutes for the firmware to load and for the automatic restart to complete on the first controller module. When dual modules are installed, the full process time is approximately 90 minutes. If cascaded drive enclosures are also being updated, total process time may be as long as 180 minutes.
Set the Partner Firmware Update option so that, in dual-controller systems, both controllers are updated. (For SMU and FTP updates only; Smart Components automatically enable/disable the PFU settings as needed.) When the Partner Firmware Update option is enabled, after the installation process completes and restarts the first controller, the system automatically installs the firmware and restarts the second controller. If Partner Firmware Update is disabled, after updating software on one controller, you must manually update the second controller.
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.
When using a Smart Component firmware package, the process automatically disables Partner Firmware Update (PFU) and thens downgrade the firmware on each controller separately (one after the other) through the Ethernet ports.
Obtain the firmware package and save it to a temporary directory. Firmware is available for download at http://www.hp.com/support/p2000G3msa.
NOTE: Instead of command line parameters, you can use the following DOS environment variables:
Obtain the firmware package and save it to a temporary directory. Firmware for all HP products is available from the HP Business Support Center website at http://www.hp.com/support/downloads.
IMPORTANT: Using the SMU to install firmware is supported only when upgrading from TS230 or later firmware. When upgrading from older firmware versions, install the firmware using the Smart Component.
Obtain the firmware package and save it to a temporary directory. Firmware is available for download at http://www.hp.com/support/p2000G3msa.
IMPORTANT: Using FTP to install firmware is supported only when upgrading from TS230 or later firmware. When upgrading from older firmware versions, install the firmware using the Smart Component.
Obtain the firmware package and save it to a temporary directory. Firmware is available for download at http://www.hp.com/support/p2000G3msa.
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 browser. If the version information is still incorrect, proceed to the next troubleshooting step.
If the 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:
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.)
Issue: In the SMU Configuration > Services > SNMP Notification page and SMU Wizards > Configuration Wizard, Notification step, clicking on the Submit or Next button without explicitly providing the community strings will replace the community strings with an actual sequence of asterisks.
Workaround: Explicitly supply the community strings.
Issue: Firmware downgrade using Smart Components from TS251R004 or newer version to TS250R023 or previous version does not succeed.
Workaround: First, downgrade the firmware from TS251R004 or newer version to TS250P003. Then, downgrade from TS250P003 to the destination version.
Issue: The HP P2000 G3 FC MSA System User Guide describes the Cache LED on the rear panel in a way that might be confusing or misleading.
Workaround: Clarification of Cache Status LED details:
If the LED is blinking evenly, a cache flush is in progress. When a controller module loses power and the write cache contains data that has not been written to disk, the super-capacitor pack provides backup power to flush (copy) data from the write cache to the CompactFlash memory. When the cache flush is complete, the LED is no longer blinking.
Issue: Replications stop after a few iterations.
Workaround: Restart the management controller.
Issue: Newly installed drives reported errors.
Workaround: Replace the drive.
Issue: Historical data for a drive is cleared when a controller crashes.
Issue: A warning about the coin battery was not displayed in the SMU events log.
Workaround: Reset the controller date and time to be current and restart the management controller.
Issue: D2700 I/O module port status is not included in the SMU display.
Issue: D2700 and MSA70 power supply information is incomplete in the SMU display.
Issue: D2700 power supplies may report a status warning, when they are actually healthy.
Issue: SMU reports an error of "input too long" when trying to map a volume that is part of a replication image.
Workaround: Shorten the length of the Snapshot Name. Selecting defaults in the SMU adds 4 characters to an image name if the replication occurs when the set is created. If replications are scheduled when the set is created, 4 characters are added as a prefix, and 6 characters are added for the unique snapshot name. In either case 5 characters are added for the exported snapshot name.
Issue: When updating drive firmware, a message is returned stating that the disk is unsupported.
Workaround: None. The message is incorrect.
Issue: When creating a volume in the SMU, if the user changes the units from GB to MB but does not change the volume size, the volume will be created in GB not MB.
Workaround: Validate the volume size after creating a new volume. If the volume was created with the wrong units, delete and re-create the volume.
Issue: The controller may take longer than expected to respond to SSH and Telnet requests.
Workaround: Restart the management controller.
Issue: The SMI-S modify volume name shows up as non supported in Windows Server Manager 2012.
Workaround: Modify the volume name using the SMU or CLI.
Issue: An error message may be displayed when restarting the controller, even when the controller restarted successfully.
Issue: In the SMU Configuration > Remove User page, the User Name field is not enabled, even though the asterisk indicates it is required.
Workaround: Select the user from the list using the radio buttons. The User Name field will be automatically filled in.
Issue: The SMU may incorrectly report a healthy power supply in a cascaded HP D2700 disk enclosure with a Warning status.
Workaround: Use the CLI show power-supplies command to verify the power supply status.
Issue: Online LUN addition is not seen by clients using the P700m, P711m, P712m, or P721m controllers and the hp cciss driver in RHEL 5, SLES 10, and SLES 11 operating systems.
Workaround: Use the rescan volumes command on the /proc subsystem of the cciss driver to force a rescan of the cciss driver. For example:
echo "rescan volumes" > /proc/driver/cciss/cciss1 multipath -v 0
Issue: During firmware upgrade of the controller, events will be generated indicating a mismatch of the versions compared to the versions in the firmware bundle (Event 363, Severity Error). This is normal operation, as the checks are done during the management controller boot process. After the firmware upgrade is complete on both controllers, verify the versions are correct, and a new informational event the firmware versions match those in the firmware bundle (Event 363, Severity Informational).
Issue: Historical disk and vdisk performance data is not persistent across controller power events.
Issue: Vdisk Data Transferred and Data Throughput numbers appear to be much higher when using the CLI historical show vdisk-statistics [vdisk] historical command, compared to CLI live output show vdisk-statistics command. This is caused by the way that the historical and live values are calculated.
Because I/Os from the RAID engine are included, numbers for the historical data appear higher than the numbers for the live data.
Issue: Saving historical disk performance statistics from the SMU fails with an invalid time-range parameter.
Workaround: Change the start date/time of the time range. Make sure the start date/time is after the last reset and, for new systems, is after the system install time.
Issue: In environments using replication, if the controllers have different firmware versions installed, replications may be suspended.
Workaround: Ensure that all controllers in replicating systems have the same firmware version installed. When firmware on the controllers is the same version, suspended replications automatically resume.
Issue: When a previously used drive is inserted in the enclosure, it may retain information about vdisks, volumes and volume mappings from its previous use. However, the LUN numbers of these volume mappings may conflict with LUN numbers currently in use in volume mappings on the system. If this occurs, the system resolves those conflicts by removing the mappings.
Workaround: Remap the volumes as desired.
Issue: In the SMU, while trying to modify a vdisk name, / is replaced by a space.
Issue: In the CLI, the create volume-set command using the same basename parameter for more than 999 volumes generates an error.
Workaround: Do not exceed 999 when assigning the volume identifier number.
Issue: In the CLI, the show sensor-status command does not show warning levels or indicate fan status.
Issue: Power supply voltage readings for cascaded HP D2700 drive enclosures are not reported in the SMU.
Issue: When a vdisk becomes critical, the array may generate multiple events.
Issue: In event messages, power supplies are referred to by different terminology. Sometimes power supply 1 is reported as ”left” and sometimes reported as “1”. Likewise, power supply 2 is sometimes reported as “right” and sometimes reported as “2”.
Issue: A serial number was not generated for SMART drive event 55.
Workaround: Identify the drive using the enclosure and slot number.
Issue: In the CLI, the show master-volumes command, a volume that has been converted to a standard volume is still included in the display.
Workaround: Log out and then log back in to the CLI.
Issue: In the SMU, global spares have a status of Up even if they are spun down using the drive spin down feature.
Issue: In the CLI, the set prompt command allows you to enter more than 16 characters.
Issue: In the SMU, when logging in using an unsupported browser, the returned display does not show the correct list of which browsers are supported.
Workaround: Use only the following supported browsers:
Issue: On the Configuration > Advanced Settings > System Utilities page, changing the Vdisk Scrub and Managed Logs settings at the same time may result in an error.
Workaround: Make these changes one at a time.
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: 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.
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 22.214.171.124 on Microsoft Windows Server 2008 R2 x64 does not see LUNs when the array is set up for point to point.
Workaround: Upgrade to the latest driver version available from HP or 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 the SMU, the Japanese version of some pages and some error messages displays English text.
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 “255.255.255.255” 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: 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:
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:
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:
The following table provides the calculated values based on the number of hosts being explicitly mapped to a LUN on the array:
Issue: USB CLI becomes unusable after a Management Controller reboot in Windows environments.
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: 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: 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 primary volume and the secondary volume reside on the same system) with a single vdisk.
Workaround: Create a second vdisk for the secondary volume.
Issue: Deleting the replication set from the destination system fails.
Workaround: Delete the replication set from the source system (the system where the primary volume resides.)
Issue: A replication set is missing the primary volume and the replication set cannot be deleted.
Workaround: Set the remaining volume in the set to be the primary volume. 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: 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: 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.
Issue: During firmware upgrade, FTP is aborted from a Windows client after starting the upgrade.
Workaround: This is a client side FTP application issue. If this issue persists try updating from the SMU, use another client, or use another FTP application.
Issue: Upgrading firmware failed with the error, “Unwritable cache data present.”
Workaround: The controller is not in a state that can reliably perform an upgrade without losing data currently in cache. Resolve the unwritable cache issue and retry the upgrade.
Issue: While updating the array firmware via the Storage Management Utility, if the array must reboot the management controller the web page may not automatically log the user out completely resulting in a blank page.
Workaround: Refresh the browser window; if the login page is not displayed, close the browser and restart it to access the login page and complete the firmware update.
Issue: While performing a firmware update using the Storage Management Utility (SMU) to multiple arrays, the window showing the status of the upgrade may appear as a blank window.
Workaround: Updating multiple arrays at the same time can cause this issue. Perform one firmware update from one client at a time. Updating one array at a time from a client allows the window to refresh more accurately.
|Firmware version||P2000 G3 MSA model||Release date|
|TS230R044||All||July 2011 (updated notes to announce support for all P2000 G3 MSA System controllers)|
|P2000 G3 1GbE iSCSI MSA andP2000 G3 10GbE iSCSI MSA||June 2011|
|TS201P007||P2000 G3 FC MSA and P2000 G3 FC/iSCSI MSA||February 2011|
|TS201P004||2000 G3 FC MSA and P2000 G3 FC/iSCSI MSA||January 2011|
|TS220R004||P2000 G3 1GbE iSCSI MSA||November 2010|
|TS201R015||P2000 G3 FC MSA and P2000 G3 FC/iSCSI MSA||November 2010|
|TS201R014||P2000 G3 FC MSA and P2000 G3 FC/iSCSI MSA||September 2010|
|TS210R016||P2000 G3 10GbE iSCSI MSA||September 2010|
|TS200R021||P2000 G3 SAS MSA||June 2010|