MSA model. (GL=MSA 1040/2040; TS=P2000, M=MSA2000 G2)

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.

Added support for the following controllers:

In the Command Line Interface (CLI), the trust command is now more selective when user input is needed and more automated when it is not needed. When out-of-sync or partially reconstructed disks are required, the instructions and consequences are clearer.

Removed possible controller hang when mapping 12 or more hosts to the same volume.

Removed the OpenSSL CVE-2014-0160 (“Heartbleed”) vulnerability, and applied a newly issued SSL certificate to the array.

Replications scheduled with time constraints might not occur within the scheduled time, and the scheduler might expire before it reaches the desired number of replications.

The Storage Management Utility (SMU) erroneously reports successful deletion of a host with volume maps.

When you are logged in to SMU with Japanese locale, the table of contents for help text is not valid.

After you click Apply, the values of the SNMP Notification page are not updated correctly in the SMU.

You could set the start time of a one-time schedule to a time earlier than the current time.

The CLI command show frus might show an OK status for a RAID controller that is not installed.

Single-controller systems converted from dual-controller systems might show unhealthy components from the missing controller.

The user session is not terminated when the user is deleted.

After a firmware upgrade, the bundle version might not reflect all component versions of the bundle correctly.

When the system has an unwriteable cache, components of a firmware upgrade fail.

Online help text for a replication volume status of Offline indicates that the volume can be accessed.

When a system is configured as single-controller, controller B ports are also displayed in the output of CLI command show ports.

SMI-S Alert Indication for Power Supplies and Disks returns an invalid device ID in the AlertingManagedElement attribute.

Issue: The CLI, SMU, or SMI-S interfaces become slow or unresponsive.

Workaround: Restart the Management Controller from either the CLI or SMU on an operating controller.

Issue: In a single-controller configuration that includes disk enclosures, the IOMs that are not connected to the controller report bad health on their expansion ports.

Workaround: It is safe to ignore the health status of the non-connected IOMs.

Issue: Prior to the successful completion of a volume-related task, such as creating a snapshot, a volume copy, or replicating a volume, one or two ERROR events might be displayed.

Workaround: Examine the events. If the task action subsequently occurs, ignore the Scheduler: The specified volume was not found event.

Issue: When a disk is scrubbed using the background scrub utility, the How Used and Job % parameters in the CLI command show disks does not show the DRSC status (indicating the disk is being scrubbed) and the percent-complete values.

Workaround: None.

Issue: When several vdisks are deleted, a "ghost" vdisk with a serial number of all zeroes briefly appears.

Workaround: Wait a few minutes for the "ghost" vdisk to disappear on its own.

Issue: Event logs do not reflect the successful upgrade of disk enclosure firmware on the other controller even though the upgrade was successful.

Workaround: Use the CLI command show enclosures to ensure that the EMP versions are correct. In the SMU, refresh the browser session and check the EMP versions.

Issue: A phantom FC host briefly appears after hosts are renamed on iSCSI ports.

Workaround: None. The phantom FC host with an id of all zeroes will disappear shortly.

Issue: The CLI command show enclosures reports health is OK when it should be DEGRADED due to leftover drives.

Workaround: Use the CLI command show system to observe the correct health.

Issue: Deleting a replication set might affect other schedules related to the primary volume.

Workaround: When you delete a replication set, ensure that any other schedules or tasks related to the same primary volume are not adversely affected. If they are affected, re-configure the affected schedule or task to the intended configuration.

Issue: The Turn On LEDs tab cannot be enabled on the Vdisk Overview.

Workaround: None.

Issue: Current SSH users remain logged in after you disable the SSH protocol.

Workaround: Restart both Management Controllers after you enable or disable any protocols.

Issue: The Management Controller might reset if the passphrase is not supplied with the CLI command set fde-lock-key.

Workaround: Ensure that the passphrase is provided in the CLI command set fde-lock-key.

Issue: In the Create Volume screen in the SMU, if the Volume size slider is moved all the way to the right, the Enable Snapshots checkbox is checked, and the Standard Policy button is selected, the maximum value in the size field might be greater than possible and the action will fail.

Workaround: Ensure that the size specified in the Create Volume screen does not exceed 80% of the vdisk available space.

Issue: After the firmware is updated on the array, the SMU might freeze or become nonresponsive.

Workaround: Restart the browser session.

Issue: SMI-S Indication subscription to the array fails.

Workaround: Run the CLI command reset smis-configuration both and then retry the operation. After running this command, any hosts registered via SMI-S need to be registered again.

Issue: SMI-S does not support default mapping.

Workaround: Use explicit mapping.

Issue: Saving disk performance statistics with a specific time range fails when you use the FTP interface.

Workaround: Use the Reset or Save Disk Performance Statistics panel of the SMU to collect statistics, or do not restrict the log to a specific time range.

Issue: The SMU online help seems not to load in Internet Explorer.

Workaround: The help will eventually load but might take minutes to complete the load. Wait for the help to load, or use Firefox or Chrome.

Issue: After explicitly mapping a LUN, other hosts that are not mapped to the LUN report seeing the Reported LUN Data Has Changed unit attention.

Workaround: No workaround is required. This will not affect data access on the other hosts.

Issue: A Vdisk going offline is reported as an Error-level event.

Workaround: To ensure that the event is sent to any software that is monitoring the array, configure the notifications to a minimum notification level of Error.

Issue: Network parameters that are set for the partner controller might not immediately be reflected on the partner controller.

Workaround: Either log into the partner controller and run any command, such as show system, to ensure that the Management Controller sees the change. Otherwise, change settings for each controller independently.

Issue: You are unable to delete users who have manage-level capabilities but do not have CLI access.

Workaround: From another manage-level user, enable CLI access for the user to be deleted and then delete the user.

Issue: If servers are connected to the array running SLES 11 SP3 and using Emulex FC HBAs, these servers might not correctly reinstate paths into the correct multipath device.

Workaround: Change the following in the multipath.conf file:

Issue: Changing the IP configuration on the other controller might cause a short disruption of connectivity to the Management Controller on which the command was run.

Workaround: None. The connection will return within 30 seconds.

Issue: When Internet Explorer 10 is used, the Provisioning Wizard might not display the available RAID levels correctly.

Workaround: Close and reopen the browser window, or use other supported browsers such as Firefox or Chrome.

Issue: During a firmware upgrade, Event 545 might be generated with an unknown error.

Workaround: After the upgrade is finished, power-cycle the storage system. Event 545 appears with a proper explanation.

Issue: In locales other than English, the Date, Time panel might not reflect the correct NTP settings.

Workaround: In the SMU, ensure that the NTP is set to the desired setting (enabled or disabled) each time any changes are made in the Date, Time panel. Otherwise, use the following CLI commands to correctly verify and set the NTP settings:

Issue: Event messages might include erroneous characters appended to the end of schedule or task names.

Workaround: Derive the real task or schedule name by ignoring the erroneous characters at the end of the string.

Issue: When Number of volumes to create is changed in the Provisioning Wizard, the corresponding Volume size slider value is updated but the text box is not updated.

Workaround: The volumes are created based on the calculation used to update the Volume size slider value. If you need a different Volume size than the slider calculation, move the slider to the appropriate size or manually update the text box with the size.

Issue: The SMU appears to be frozen if volume-identifying information contains illegal characters.

Workaround: Connect to the CLI and remove the illegal characters from the volume-identifying information.

Issue: Windows 2008 R2 SP1 Clustered Hyper-V VMs might experience loss of paths due to high load with a high number of LUNs assigned to the Cluster and VMs.

Workaround: Where possible, reduce the number of LUNs used on each cluster node or exposed VM. After any path loss situations, verify that the correct number of paths exist.

Issue: Deleting a vdisk might not delete all associated schedules.

Workaround: Delete the schedules manually.

Issue: After setting enclosure parameters, the settings might revert intermittently to previous values.

Workaround: Attempt the set enclosure-parameters command again.

Issue: Attempts to enable the identification LED on a D2700 enclosure do not work.

Workaround: None.

Issue: In the SMU, mapping a volume to a LUN results in a generic Error: Command failed response.

Workaround: Verify that the LUN number is not already in use for that host, or in the case of default mapping, that the LUN number is not already in use on that port.

Issue: When using Internet Explorer, if you attempt to upload a firmware image where the path contains a dot (.), the upload fails with an error that the file is the wrong type.

Workaround: Ensure that the file path does not contain a dot (.), or use another supported browser.

Issue: In the SMU, the Full Disk Encryption (FDE) passphrase does not accept a phrase that contains spaces.

Workaround: If spaces are required in the passphrase, use the CLI commands to set the passphrase.

Issue: In the SMU Full Disk Encryption Settings panel, the action buttons might not become active immediately after you enter required information on the page.

Workaround: Use the Tab key on the keyboard, or click any white space on the screen to change the focus, which enables the buttons.

Issue: The confirmation response to the CLI command set disk repurpose shows an incorrect disk number.

Workaround: The confirmation response message is incorrect, and the command will repurpose the disk specified.

Issue: After repurposing a drive in the SMU, the Repurpose Disk List might take a longer time than expected to refresh the information.

Workaround: Refresh the browser, or log out and log back into the browser.

Issue: Using Internet Explorer 9, you are unable to apply setting changes in Configuration > Advanced Settings > Disk, because the EMP Polling Rate is blank.

Workaround: Select a valid value from the EMP Polling Rate drop-down rather than leaving it blank, and click Apply. The system default EMP Polling Rate is 5 seconds.

Issue: The HP Integrity Smart Array P411 SAS Controller only brings up one PHY when connected to the array, which causes the array to show the port as degraded.

Workaround: None.

Issue: The SMU might not allow a snap-pool to be deleted if master volumes associated with that snap-pool are deleted while the vdisk containing the snap-pool is offline, such as after a multi-disk raid failure.

Workaround: Use the CLI delete snap-pool command to delete the snap-pool.

Issue: The Install License menu item, and other features such as Create Snapshot, might not appear in the SMU.

Workaround: Refresh the web browser. If the problem persists, clear the browser cache and restart the browser.

Issue: The values of the SNMP Notification page are not updated correctly in the SMU after clicking Apply.

Workaround: Refresh the browser.

Issue: Modifying the start time of an existing one-time schedule to earlier than the current time causes the schedule not to run at the scheduled time.

Workaround: When modifying a schedule, do not set the start time of a one-time schedule to earlier than the current time.

Issue: The CLI command show frus might show an OK status for a RAID controller that is not installed.

Workaround: None.

Issue: Single-controller systems converted from dual-controller systems might show unhealthy components from the missing controller.

Workaround: Restart the management controller.

Issue: The user session is not terminated when the user is deleted.

Workaround: After deleting the user, immediately restart both management controllers.

Issue: Some of the mapping panels in the SMU might default the access mode to no-access while others default to read-write.

Workaround: Always ensure that the access mode for mapping is set as desired before clicking Apply.

Issue: Unable to create a weekend suspend task on a weekend day in the SMU.

Workaround: Use the CLI to schedule a suspend task.

Issue: After a firmware upgrade, the bundle version might not reflect all component versions of the bundle correctly.

Workaround: Reload the firmware bundle.

Issue: When the system has an unwriteable cache, components of a firmware upgrade fail.

Workaround: Ensure that there is no unwriteable cache, and reload the firmware bundle.

Issue: Online help text for a replication volume status of Offline indicates that the volume can be accessed.

Workaround: Online help should read, Offline: the volume cannot be accessed and is unusable due to an error.

Issue: When you are logged in to WBI with Japanese locale, the Table of Contents for help text is not valid.

Workaround: None.

Issue: When a system is configured as single-controller, controller B ports are also displayed in the output of CLI command show ports.

Workaround: None.

Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in RHEL 5 operating systems.

Workaround: Use the rescan volumes command on the /proc subsystem of the cciss driver to force a rescan of the cciss driver, and then update multipath. For example:

echo "rescan volumes" > /proc/driver/cciss/cciss1

multipath -v 0

Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in SLES 11 SP2 and SP3 operating systems.

Workaround: Use the hpacucli or hpssacli utility to force the SmartArray to rescan for LUNs. Do this by issuing a command for the utility to list the logical drives from the SmartArray that is connected to the MSA storage.

Issue: When you use explicit LUN mapping, 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; 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: RedHat Enterprise Linux Server 5 that uses the P711m, P712m, and P721m SmartArray adapters connected to a MSA 2040 SAS array might not create all multipath (mpath) partitions correctly, after rebooting the client when the array is under heavy load and there are a large number of multipath devices.

Workaround: After booting the server, scan for new multipath partitions by running the command, multipath -v 0. If the partitions are still not created, try flushing the multipath devices and recreating the devices by issuing the command multipath -F followed by multipath -v 0.

Issue: All paths might not be reinstated correctly after a failback condition occurs, when a c-Class BladeSystem is connected via the SmartArray P711m, P712m, or P721m to a MSA 2040 SAS array in an ESX 5.x environment. A failback condition can occur due to cable replacement, SAS switch zoning changes, controller replacement, controller shutdown and reboot, or firmware upgrades.

Workaround: Force a rescan of all paths in the vSphere client, CLI, or PowerShell utilities. Consult VMWare documentation on the correct procedure.

Issue: If the auto-write-back setting is disabled using the set auto-write-through-trigger CLI command, the controller reboots into write-through mode.

Workaround: Manually set the cache parameters to write-back and re-enable auto-write-back setting as applicable.

Issue: When the controller is in write-through mode, snap-pool space is not freed for some time after snapshots are deleted.

Workaround: Set the cache parameters to write-back on the controller to allow space to free more quickly.

Issue: Storage controller restart (for example, the CLI command restart sc both) causes the management controller to restart.

Workaround: None.

Issue: Replications scheduled with time constraints might not occur within the scheduled time, and the scheduler might expire before it reaches the desired number of replications.

Workaround: Do not use the scheduler with time or date constraints.

Issue: If you remove controllers from a chassis that is running manual IP configuration, and if you install those controllers in a chassis that is configured for DHCP and then return them to the original chassis, the controllers retain the DHCP configuration instead of the Manual IP configuration saved in the chassis midplane.

Workaround: If you move controllers between chassis, verify the IP configuration.

Issue: When direct-attached to an Emulex FC HBA, a link might not be established.

Workaround: Ensure that all affected array and HBA ports are using auto or loop topology. For the array, this must be accomplished using the CLI.

Issue: Controller temperature Event 307 occurs without a sensor location.

Workaround: None.

Issue: FTP code load is unsuccessful.

Workaround: Restart the management controller.

Issue: When a background media scrub is run on the spares, vdisk spares are displayed as vdisk members in the SMU.

Workaround: None.

Issue: In the SMU in the Enclosure Overview screen, a spare disk that is performing disk scrub displays DRSC appended to How Used in the properties table, causing an undescribed value of VDISK SPDRSC.

Workaround: None.

Issue: An SNMP log-in is created that uses privacy type but no authentication type.

Workaround: If either the privacy type or authentication type is supplied, provide both parameters.

Issue: SMU erroneously reports successful deletion of a host with volume maps.

Workaround: Remove the host mappings and verify that the host was deleted.

Issue: After you attempt a firmware update, controllers revert to the old version.

Workaround: Do not make configuration changes during firmware updates.

Issue: When using IE9 in compatibility mode to access the SMU, a message appears on the login page that states the browser is unsupported.

Workaround: Disable IE9 compatibility mode.

Issue: A newly installed drive reports errors.

Workaround: Replace the drive.

Issue: A warning about the coin battery was not displayed in the Storage Management Utility (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.

Workaround: None.

Issue: D2700 power supply information is incomplete in the SMU display.

Workaround: None.

Issue: SMU reports an error of input too long when you try 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 four characters to an image name if the replication occurs when the set is created. If replications are scheduled when the set is created, four characters are added as a prefix, and six characters are added for the unique snapshot name. In either case, five characters are added for the exported snapshot name.

Issue: During the drive firmware update, a message is returned stating that the disk is unsupported.

Workaround: The message is incorrect. Use the Hard Disk Drive (HDD) firmware (FW) Smart Component to update FW, if available.

Issue: When creating a volume in the SMU, if you change the units from GB to MB but do not change the volume size, the volume will be created in GB rather than 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 SMI-S modify volume name appears as non-supported in Windows Server Manager 2012.

Workaround: Use the SMU or CLI to modify the volume name.

Issue: When you select Configuration > Remove User in the SMU, the User Name field is not enabled, even though the asterisk indicates that it is required.

Workaround: Use the radio buttons to select the user from the list. The User Name field will be automatically completed.

Issue: The SMU might incorrectly display a warning status for a healthy power supply in a cascaded HP D2700 disk enclosure.

Workaround: Use the CLI show power-supplies command to verify the power supply status.

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 the CLI live output show vdisk-statistics command. This issue 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.

Workaround: None.

Issue: If a previously used drive is inserted in the enclosure, it might retain information about vdisks, volumes, and volume mappings from its previous use. However, the LUN numbers of these volume mappings might 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 necessary.

Issue: When you modify a vdisk name in the SMU, / (slash) is replaced by a space.

Workaround: None.

Issue: In the CLI, the show sensor-status command does not show warning levels or indicate fan status.

Workaround: None.

Issue: Power supply voltage readings for cascaded HP D2700 drive enclosures are not reported in the SMU.

Workaround: None.

Issue: If a vdisk becomes critical, the array might generate multiple events.

Workaround: None.

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.

Workaround: None.

Issue: A serial number was not generated for SMART drive Event 55.

Workaround: Identify the drive by using the enclosure and slot number.

Issue: In the CLI, the show master-volumes command includes a volume that has been converted to a standard volume.

Workaround: Log out, and log in again to the CLI.

Issue: Global spares have a status of Up in the SMU, even if they are spun down using the drive spin-down feature.

Workaround: None.

Issue: On the Configuration > Advanced Settings > Microsoft Windows Server 2008 R2 > System Utilities page, changing the Vdisk Scrub and Managed Logs settings at the same time might result in an error.

Workaround: Make these changes one at a time.

Issue: When you create 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: SLES 11 might 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: Under rare circumstances, some events from one controller are not seen on the other controller.

Workaround: Review the events from both controllers.

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

Workaround:

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 MSA 2040 support page.

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

Workaround: Using the Storage Manage Utility (SMU), open 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. Ensure 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 you detach the secondary volume, delete the replication set (which stops the vdisk), and restart the vdisk of the secondary volume. To correct this issue, reattach the secondary volume, set it as the primary volume, and delete the replication set.

Issue: A Controller Busy error message occurs while you create a replication set.

Workaround: Creating replication sets immediately one after the other might 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 might not have time to complete.

Issue: You are 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 might cause communications issues between the management controller and the storage controller.

Workaround: Cycle the 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 of the arrays involved in the tasks.

Issue: In a dual-controller system, the login to one of the controllers fails, but the login 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 might be lower or higher than expected for the workload.

Workaround: This is a reporting issue and not a performance issue. Calculate the correct values 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 might interpret a switch login as a host bus adapter (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 it, or use Disable Device Scan on switch ports connected to the array controller and restart the array controller.

Issue: SMI-S Alert Indication for Power Supplies and Disks returns an invalid device ID in the AlertingManagedElement attribute.

Workaround: Use the show events CLI command to identify the failed device.

All MSA 2040/1040

All MSA 2040

MSA 2040 SAN

MSA 2040 SAN