The information contained herein is subject to change without notice. The only warranties for Dot Hill products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Dot Hill shall not be liable for technical or editorial errors or omissions contained herein.
Controller firmware: GL210R006-08
This package delivers firmware for AssuredSAN 3004, 4004, Ultra48 and Ultra56 RAID controllers and AssuredSAN drive enclosures.
|
IMPORTANT: For a list of supported companion drive enclosure firmware, see Additional devices. | |
The following letters represent firmware version release information:
AssuredSAN 3004 Controllers
AssuredSAN 3004 FC Controller
AssuredSAN 3004 1G iSCSI Controller
AssuredSAN 3004 10G iSCSI Controller
AssuredSAN 3004, 4004, Ultra48, and Ultra56 array controller enclosures support the cascading of drive enclosures. The following table lists supported drive enclosure models and firmware versions.
| Cascaded drive enclosure model | Recommended drive enclosure firmware |
| AssuredSAN 4124 and 4134 drive enclosures | S200B38 |
| AssuredSAN 4120 and 4130 drive enclosures | S200B38 |
| AssuredSAN 3120 and 3130 drive enclosures | S200B38 |
| AssuredSAN J6G48 48-drive SFF enclosure | A400R64 |
| AssuredSAN J6G56 56-drive LFF enclosure | A400R64 |
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 from Dot Hill's Customer Resource Center at http://crc.dothill.com. | |
This firmware contains security updates. After any security update is applied to your array, changing user passwords is recommended.
This version of firmware disables unsecured web access by default. This setting is applied on new controllers from the factory, or after using the CLI restore defaults command. Use secured web access (HTTPS) to avoid access issues.
Added support for a 2-port 3004 12G SAS model supporting both standard and fan-out cables.
Improved performance and fixed kills for heartbeat loss when very large volumes or very large pools with many allocated pages are used.
Added Storage Management Console and RAIDar translation support for Russian, Arabic, and Brazilian Portuguese locales.
Improved event criticality for certain events.
Enabled dynamic spare feature by default.
User is encouraged to change community strings for SNMP.
Creating an SNMP v3 user disables SNMP v1 and SNMP v2.
Disabled SSH v1.
Regenerate SSL certificates on demand.
Enhanced total drive usage information to include drives not currently in use.
Added warning prompts for configuration changes using the CLI that may result in data unavailability or data loss.
Added additional information when reporting SCSI reservations.
Display the licensing serial number for the CLI show license command.
Updated OpenSSL updated to 1.0.1m.
Disabled SSL 3.0 to mitigate CVE-2014-3566.
Increased the size of maximum supported paged storage pools to 300TiB per pool and 600TiB per system. Once storage pools are resized to be larger than the previous limits, downgrading to a previous release requires direct guidance by customer support personnel.
Added support for the AssuredSAN Ultra56 RAID enclosure, Ultra56 SAS RAID enclosure, and Ultra56 J6G56 56-drive LFF drive enclosure.
A new Sector Format property has been added to support 512-byte native sector size (512n) disks, 512-byte emulated sector size (512e) disks, or a mix of those sector formats. For best performance, all disks should use the same sector format.
PFU (Partner Firmware Update) functionality was enhanced to be more robust.
Updated OpenSSL to version v1.0.1l.
Added virtualized storage capabilities including read cache, thin provisioning, automatic tiering, wide striping, and snapshots of snapshots.
Added new Storage Management Console v.3 to manage virtualized storage as well as traditional storage which includes topic-based navigation, advanced sort and filter capability, and increased ease of use capabilities.
Added new feature to turn off the power on an empty disk slot.
Improved iSCSI performance on 4004 platforms.
Added support for the following controllers:
AssuredSAN 3004 FC
AssuredSAN 3004 1G iSCSI
AssuredSAN 3004 10G iSCSI
Added support for the following RAID enclosures:
AssuredSAN Ultra48
AssuredSAN SAN
Ultra48 SAS
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.
Single-controller configurations are supported for AssuredSAN 3004 systems.
Ensured the midplane serial number is set correctly on the partner expansion controller.
Provided the SCSI initiator the ability to read the firmware of the active expansion controller and update the firmware on the partner expansion controller and all attached drive enclosure I/O modules.
Improved the detection and resolution of incompatibility between firmware and hardware versions of the active and partner expansion controllers.
Improved arbitration between the active and partner expansion controllers.
1024 unmanaged initiators per port and 64 managed initiators per port are now supported.
Fixed an issue where stripe breadth was calculated incorrectly for a customer's one-button feature.
Fixed an issue where dropped telnet sessions were not cleaned up, which caused a persistent max session limit state.
Fixed an issue where the MC stalled due to an unreadable boot sector.
Fixed an issue where the MC stalled when there were too many MC logins.
Fixed an issue where, when using the Storage Management Console in Internet Explorer and gathering log files, the Save pop-up window necessary to save the file did not appear. It may be necessary to wait two minutes after requesting the logs before the pop-up window is displayed.
Corrected an issue where the Storage Manager Console's help window did not display text when using Internet Explorer.
Fixed an issue where a user could not map volumes using the Storage Management Console when no host connections are present.
Enabling the CLI spin-down command and setting spin-down-delay to zero resulted in the delay being set to the default value of 15 minutes.
An incorrect error message was displayed when trying to delete disk groups from a pool.
The host did not receive a pool threshold event from Pool B.
Improved Microsoft Windows Server 2012 integration stability.
Improved updating array configuration in Microsoft Windows Server 2012 when array configuration was modified using array management.
The CLI, Storage Management Console, or SMI-S interfaces became slow or unresponsive.
Added SMI-S associations that were missing.
Improved stability of SCVMM integration.
Improved snap pool management operation functionality in Windows Server 2012.
A vdisk going offline was reported as an “error” level event.
Improved SMI-S indication functionality.
Uninstallation of host software could unintentionally remove software in use.
In the Storage Management Console the online help for all locales except English did not show that NRAID, RAID-0 and RAID-3 vdisks could only be created using the CLI.
A blank Replicate Volume description pane for single controller system was displayed in the Storage Management Console when selecting Replicate Volume from the Volume Provisioning menu.
Performance statistics could show a value of 0 if one controller was in a shutdown state.
The CLI show provisioning command did not display correct information if the ports parameter was used and the volumes were mapped using symmetric port assignment.
Host group mapping was very slow with more than 192 initiators.
In the performance tab, the sample period was referred to in seconds but the data was shown in milliseconds.
Some panes and drop down menus might not display correctly in locales other than English.
Help was not available for step 8 of 9 of the Configuration Wizard.
N/A. This was the initial release of new firmware to support a new product rather than an update of previous firmware for existing products.
A controller may fault occasionally during remote replication.
Controllers may fault occasionally during regular array operation.
In some cases, a firmware update from GL105 to GL200 may fail to report unwritable cache.
Missing a few steps in Storage Management Console v3 Help for Configuration Wizard.
Unable to make changes to mapping from host port to volume in RAIDar.
Scrub errors seen occasionally with RAID 10 disk groups.
Some display texts in non-English locales are displayed in English.
Changing email notification settings using the CLI set email-parameters command enabled Include Logs unless the "include-logs" parameter was specifically set to disabled.
Erroneous events sent for USB flash drive.
Erroneously showed PSU status as OK when the PSU fan had failed.
Unable to delete replication snapshot as per retention setting on remote system.
A disk was erroneously reported as unsupported when it failed.
A 314 event did not occur for unknown drive failures.
Changing vdisk ownership did not warn of possible data loss or unavailability if volumes in the vdisk were mapped to hosts.
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.
The Usage property in the CLI show disks command is not showing DRSC when a disk is being scrubbed using the background scrub utility.
Current SSH users remain logged in after disabling the SSH protocol.
The Management Controller may reset if the passphrase is not supplied with the CLI set fde-lock-key command.
Setting network parameters for the partner controller may not immediately be reflected on the partner controller.
Changing the IP configuration on the other controller may cause a short disruption of connectivity to the Management Controller that the command was run on.
When Internet Explorer 10 is being used, the Provisioning Wizard may not display the available RAID levels correctly.
During a firmware upgrade, Event 545 may be generated with an unknown error.
RAIDar appears to be frozen if a volume identifying information contains illegal characters.
Deleting a vdisk may not delete all associated schedules.
Intermittently after setting enclosure parameters, the settings may revert to previous values.
The confirmation response to the CLI set disk repurpose command shows an incorrect disk number.
Resolved the following Common Vulnerabilities and Exposures (CVE) security issues:
CVE-2014-0224 - SSL/TLS MITM vulnerability
CVE-2014-3508 - Information leak in pretty printing functions
CVE-2014-3511 - OpenSSL TLS protocol downgrade attack
CVE-2014-3512 - SRP buffer overrun
CVE-2014-3567 - Session Ticket Memory Leak
Allowed fallback to SSL 3.0; now blocks the ability for a man-in-the-middle attacker to force a protocol downgrade.
Loss of ETH port access due to loss of IP.
In configurations with more than 12 initiators mapped to a single LUN, RAIDar crashed and the MC rebooted while mapping.
Prevent controller crash when creating NRAID and RAID1 vdisks.
Always check mid-plane type in fan control and default to using drive temps if it is not set.
Stagger user-initiated FDE CLI commands (secure, repurpose, set lock key, and set import key) in order to fix a power issue related to Atlas drawer hardware.
While processing many duplicates, one controller kills the other for a heartbeat timeout.
Correctly handle a controller that has hung while shutdown.
Fix drive overtemp power-down bug.
Array device element status reported as NOT INSTALLED after drawer master/slave transition.
Drives powered on too late after a slave EC failed over and became master due to an EC code load or IOM pull.
When a drive is removed the PHY is disabled and, when installed, the drive is enabled.
Ensured that the surviving I/O module is active when the partner I/O module is "slow inserted."
Enabled auto reset of expansion controller firmware after successful firmware installation.
Ensured the expansion controller reports correct event log size.
The "RAD" bit in the SAS expander element that indicates firmware has been successfully downloaded and is ready to be installed is only set if expansion controller firmware is loaded.
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.
RAIDar erroneously reports successful deletion of a host with volume maps.
When you are logged in to RAIDar 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 RAIDar.
You could set the start time of a one-time schedule to a time earlier than the current time.
The CLI show frus command 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 unwritable cache, components of a firmware upgrade fail.
When a system is configured as single-controller, controller B ports are also displayed in the output of the CLI show ports command.
SMI-S Alert Indication for Power Supplies and Disks returns an invalid device ID in the AlertingManagedElement attribute.
Windows Server 2012 management integration:
Dot Hill recommends that you update the Windows cache by using the cmdlet Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName> manually, after attempting any storage provision operations that use the AssuredSAN management interface (RAIDar or the Command Line Interface).
Dot Hill recommends that you use the AssuredSAN management interface to modify volume mappings, delete volumes, or modify volume names. Manually update Windows cache by using the cmdlet Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName>.
Windows Server 2012 management and System Center VMM integration:
Dot Hill recommends that you disable Windows Indication subscription, if SCVMM or Windows Server 2012 manages only AssuredSAN systems and not any other arrays. To disable the Indication subscription, modify the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Storage Management\EnableIndications value from 1 to 0 and restart Windows Standards Based Storage Management Service.
If you want to enable the Indication subscription at Windows Server 2012, Dot Hill recommends that you configure the Indication based on the instructions provided at http://blogs.technet.com/b/filecab/archive/2013/05/22/using-indications-with-the-windows-standards-based-storage-management-service-smi-s.aspx.
The AssuredSAN 4004 contains an embedded SMI-S provider for use by SMI-S client applications. The embedded provider is designed to support AssuredSAN 4004 configurations with up to 24 hard drives and up to 250 mapping paths. A mapping path is defined as an AssuredSAN 4004 volume presented through an AssuredSAN 4004 target port to a host initiator.
When changing a replication set (e.g., adding or removing a replication volume or deleting the replication set), do so from the source system; when aborting, suspending, or resuming a replication, do so from the destination system.
When changing the primary volume of a replication set, do so from the destination system first, then, perform the change on the source system.
When using Windows Dynamic Disk (software RAID) on top of a hardware RAID, cautions must be considered. For more information, see the section "Real World: Dynamic versus Basic Disks" on the topic at http://technet.microsoft.com/en-us/library/dd163558.aspx.
Failover and failback times are affected by the number of system volumes; the more volumes there are on the system, the more time is required for failover and failback to complete.
Removing controllers from 3004 or 4004 systems and inserting them into Ultra48 systems or Ultra56 is not supported and will result in unexpected behavior.
Removing controllers from Ultra48 systems or Ultra56 and inserting them into 3004 or 4004 systems is not supported and will result in unexpected behavior.
Removing controllers from Ultra48 systems and inserting them into Ultra56 systems is not supported and will result in unexpected behavior.
Removing controllers from Ultra56 systems and inserting them into Ultra48 systems is not supported and will result in unexpected behavior.
Although Ultra48 systems support the use of 4124 drive enclosures that are physically similar to 4124 drive enclosures used with 3004 and 4004 systems, the drive enclosures require different firmware (see Additional Devices above). It is necessary when ordering your drive enclosure to choose the SKU that is appropriate for your system. Do not remove a 4124 drive enclosure that is connected to a 3004 or 4004 system and connect it to an Ultra48 system. Do not remove a 4124 drive enclosure that is connected to an Ultra48 system and connect it to a 3004 or 4004 system.
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 re-programming. | |
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. | |
Create a backup of system data (a full backup is strongly recommended).
Schedule an appropriate time to install the firmware:
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.
Allocate sufficient time for the update:
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, the 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. 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.
Verify system status in the system's management utility, and confirm that the new firmware version is listed as installed.
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 AssuredSAN Event Descriptions Reference Guide.
Obtain the firmware package, and save it to a temporary directory. Firmware for all Dot Hill products is available from the Dot Hill Customer Resource Center website at http://crc.dothill.com.
Locate the firmware file in the downloaded/extracted folder. The firmware filename is in the following format: GLxxxRyyy-zz.bin.
In single-domain environments, stop all I/O to vdisks in the enclosure before starting the firmware update.
Log in to RAIDar and, in the Configuration View panel, right-click the system, and then select Tools > Update Firmware.
A table is displayed that shows currently installed firmware versions.
Wait for the installation to complete. During installation, each updated module automatically restarts.
In the Storage Manager Console or RAIDar display, verify that the expected firmware version is installed on each module.
Obtain the firmware package, and save it to a temporary directory. Firmware for all Dot Hill products is available from the Dot Hill Customer Resource Center website at http://crc.dothill.com.
Locate the firmware file in the downloaded/extracted folder. The firmware filename is in the following format: GLxxxRyyy-zz.bin.
Using RAIDar, prepare to use the FTP:
In single-domain environments, stop I/O to vdisks in the enclosure before starting the firmware update.
Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory containing the firmware file to load.
Wait for the installation to complete. During installation, each updated module automatically restarts.
If needed, repeat these steps to load the firmware on additional modules.
Verify that the expected firmware version is installed on each module.
If you experience issues during the installation process, do the following:
When viewing system version information In the RAIDar 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 version information is still incorrect, proceed to the next troubleshooting step.
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.
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 displayed information is correct.
If the show disks command fails to display the disks correctly, communications within the controller have failed. To re-establish 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.
The following is a cumulative list of known issues and workarounds:
Issue: Configuring multiple iSCSI ports causes a failure to mount LUN in SCVMM. Workaround: Configure a single iSCSI port. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When using telnet in a Linux environment, while logged in as manage, a Ctrl+left arrow or Ctrl+right arrow keystroke combination freezes the telnet session. Workaround: Do not use a Ctrl+left arrow or Ctrl+right arrow keystroke combination in Linux. Type the tilde character ~ to return control to telnet, use a Windows telnet client, or start a start a new telnet session and avoid the keystroke combination that causes the problem. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Modifying user roles in the Storage Management Console is disabled. Workaround: Use RAIDar or the CLI to modify user roles. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, Topics are not accessible on screen resolutions less than 1024x768. Workaround: Use a resolution of 1024x768 or higher. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Images for IOMs are not displayed for JBODs in the Rear System View of the Storage Management Console. Workaround: Information for JBODs can be gathered by other means in the CLI or RAIDar. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In RAIDar, online help specifies a host name character limit of 32, but the System will only allow 15 characters. Workaround: The user will need to limit host names to 15 characters. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The characters * and . are special characters and are not allowed in the name field for linear volumes In the Storage Management Console. Workaround: Create linear volumes In the Storage Management Console without special characters. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In a system downgraded to GL105, there is a system limit of 4 snap pools per system. Workaround: Issue a Restore Defaults after downgrading to GL105; this will cause the snap pool limit to change from 4 to 128. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to de-quarantine the vdisk during vdisk expansion. Workaround: Follow best practices when performing vdisk expansion. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console help does not specify the limitations of disks for disk-group expansion. Workaround: Consult the About RAID Levels topic in the RAIDar online help for linear vdisk expansion limits. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When expanding a volume from the Storage Management Console the remaining space in the vdisk is inconsistent with the corresponding value shown if the volume is expanded from the Storage Management Console or CLI. Workaround: None, the size is minimally different. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Context sensitive Help pages may not pop up correctly. Workaround: Use the Help topics to navigate to the correct topic. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, the formatting of the settings in step 9 of 9 in the Configuration Wizard is misaligned. Workaround: None; this is a display issue only. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Field validation on pop-ups in the Storage Management Console may occur prior to field data being entered. Workaround: Enter the field data and the validation errors will disappear. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The user is unable to abort the background media scrub from the Storage Management Console or RAIDar. Workaround: Using the CLI, abort the background media scrub. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, the Snapshot schedule prefix has a maximum length of 24 bytes instead of 26 bytes as stated in the online help. Workaround: Limit the Snapshot prefix length to 24 bytes using the Storage Management Console, RAIDar or the CLI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: During volume-copy, the default new volume name for the first volume copy appends C02 In the Storage Management Console. Workaround: Manually modified name as desired. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Forward slashes are replaced by spaces in the Storage Management Console and RAIDar in the Set System Information page. Workaround: Set the fields through the CLI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Hover panels may not refresh automatically. Workaround: Navigate away and navigate back to refresh the hover panel. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, in step 7 of 9 of the Configuration Wizard, there is no error message when invalid characters are entered in the Sender Domain field. Workaround: Use only valid characters in the Sender Domain field. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When performing a volume copy and the destination volume already exists, the error message shows the source volume rather than the destination volume. Workaround: Provide a unique destination volume name. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console User Management Page, the copy option does not copy all fields. Workaround: Verify all fields of the newly created user. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When setting pool thresholds in the Storage Management Console, an error message may be displayed if the mid threshold is set below the low threshold. Workaround: Ensure that the mid threshold is higher than the low threshold. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Licensing Version Number shows Not Found when the system is in Fail Over. Workaround: Install the license when the system is not in a failover state. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, setting the New Volume Prefix field is ineffective in the schedule for Copy Volume. Workaround: Use the default fields or set the fields through the CLI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console or RAIDar may incorrectly display volume creation sizes with base 10 instead of base 2. Workaround: Verify volume size from the host after creating a volume. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In-port and out-ports are displayed as "In 0 and out 0" for all enclosures in RAIDar & Storage Management Console. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The host-group name cannot be changed in the Storage Management Console or RAIDar if the host-group was created or modified in the CLI with an * in its name. Workaround: Do not use the * character in host-group names. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The snap pool name cannot be changed in the Storage Management Console or RAIDar if the snap pool was created or modified in the CLI with an > in its name. Workaround: Do not use the > character in snap pool names. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console allows the user to add volumes with different mappings than those in the volume group. Workaround: Verify all mappings are consistent within a volume-group. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the CLI, a snapshot name with special characters in its name may not work correctly. Workaround: Do not include special characters in snapshot names. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When using the Provisioning wizard to create volumes, volume size may not be correct. Workaround: Verify volume sizes after using the Provisioning wizard. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: VAAI XCOPY performance may be reduced. Workaround: Verify that all paths to storage are functional. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI show pool-statistics historical count n command shows statistics for n-1 count. Workaround: Increase the count parameter by one. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In RAIDar, when changing the SNMP user's locale from non-English to English, the previous locale may be retained. Workaround: Verify the locale and use Storage Management Console, RAIDar or the CLI to update the locale. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: After successfully creating a user in the Storage Management Console or RAIDar, the user may get an error message about the user name and password. Workaround: None; this is a display issue only. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to create a replication set from GL105 to GL2xx when a storage pool exists on the secondary system. Workaround: Use the CLI and supply the WWN or IP addresses of the primary and secondary systems to create the replication set successfully. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Replication image status or progress information of the primary system is not displayed in RAIDar. Workaround: View the status from the secondary system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, the 'Add disk-group' page may be blank in single controller mode. Workaround: Refresh the browser in the Storage Management Console or retry the operation in CLI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Attempting to create new pools with the same name as offline pools fails. Workaround: Don't include invalid characters in volume group names in the Storage Management Console. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue:In RAIDar, saving disk performance statistics may fail. Workaround: Adjust the timeframe and retry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In SNMP, if the notification level is set to None, then no test event is sent. Workaround: Set the SNMP notification level to Informational. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, the forward > button doesn't work to navigate through help topics online help. Workaround: Use the online help table of contents to navigate through the help. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Invalid replication images may exist in the secondary system if the replication set is deleted when the secondary vdisk is in shutdown state. Workaround: Convert the secondary volume to a primary volume and delete the replication set. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Password creation for a user may fail if single quote characters are used. Workaround: Do not use single quotes in passwords. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Events with event ID 551, 552, 553, 554 and 557 are generated without the severity icon. Workaround: Event severity can be viewed using the CLI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, after creating user with manage and monitor roles, only the manage role will be displayed for that user. Workaround: None, monitor role is implied with manage role. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI set volume command with no actionable settings will return a successful message. Workaround: Use the CLI set volume command with appropriate settings. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: An unexpected pop-up window with an erroneous error message is displayed when attempting to save logs from RAIDar or the Storage Management Console. Workaround: Ignore that error message and proceed with downloading logs. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, the user is unable to change the encryption status of SMI-S from the Configuration Wizard. Workaround: Change SMI-S encryption status outside of the Configuration Wizard. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Disk performance statistics are inaccurate when a scrub is in progress. Workaround: Get performance statistics after the scrub has completed. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Formatting and display issues exist in locales other than English. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Creating and scheduling a replication set command fails if a volume name contains a space. Workaround: Don't use a space in the volume name. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Global Spares count may be incorrect when displayed on the Home page in Korean locale. Workaround: Validate spare count from the System page. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In rare cases, PFU may fail to update the partner controller. Workaround: Verify the firmware versions and restart the controller with the correct firmware version. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: SCVMM R2 may not accurately display available virtual pool capacity. Workaround: Verify virtual pool capacity using the Storage Management Console. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Event viewer in locale other than English may output in XML format. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, negative values may be displayed in the Capacity Utilization¨Reserve column. Workaround: Use the CLI to display the correct values. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console, SSD spares may not be displayed in the global spares information panel. Workaround: Use CLI to check SSD spares. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: English strings are seen in other locales. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Failed to set date and time through the Storage Management Console v3 system > Configuration > System Settings > Date, Time panel. Workaround: If neither the Enabled or Disabled NTP radio button is selected, select one setting and then set the date and time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to change mapping in locales other than English. Workaround: Choose a new Access type, which will appear in English in the drop-down for all locales. Once an English value is selected, the mapping can occur. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Replication wizard help is not displayed for step 3 of 5 in locales other than English. Workaround: Read the help in the English locale or reference the Storage Management Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Configuration Wizard help is not displayed for step 7 of 9 and 8 of 9 in locales other than English. Workaround: Refer to appropriate language version of the Storage Management Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Creating a new virtual disk-group when existing linear disk-groups exist that are named A, B, a, or b causes the virtual disk-group to be unmanageable. Workaround: Change the name of existing linear disk-groups to something other than A, B, a, or b, and remove and re-add the virtual disk-group. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI set prompt command is not allowing & to be set as a prompt. Workaround: Use another prompt in place of &. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In Internet Explorer, when the Help button is clicked in RAIDar or the Storage Management Console, it can take a couple of minutes for the Help window to be populated with content. Workaround: Eventually the Help window will be populated; it may take a couple of minutes. Or use a different supported browser. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The create volume/volume-set page highlights an access parameter in red (only once per volume). Workaround: Click on the access drop-down menu and select an appropriate value. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In RAIDar or Storage Management Console popups, buttons aren't enabled until clicking outside of the data entry fields or pressing the Tab key. Workaround: Select the Tab key or click outside of the entry fields in order to enable the buttons. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When trying to create a virtual disk-group larger than 64 TB, an error is displayed and the disk-group is not created. Workaround: Create virtual disk-groups of 64 TB or smaller to add to pools. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: After swapping controllers in the same array enclosure, both controllers may show the same management IP. Workaround: Correct the IP for each management port one at a time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When the SNMP community string is left blank in the Storage Management Console, the previous value is used. Workaround: Do not leave the SNMP community string blank. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Error disabling Drive Spin Down with a non-zero delay. Workaround: When disabling the drive spin down feature, you must also set the delay to zero. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: If the code load health checker determines that firmware should not be loaded, no event will be logged. Workaround: Determine code load health by running the CLI check firmware-upgrade-health command. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: There is no option to turn on/off LEDs through the Storage Management Console. Workaround: Use the CLI or RAIDar to turn on/off LEDs. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The RAID type description is not displayed in hover help in the Storage Management Console using Internet Explorer. Workaround: Lookup the RAID type through help, or use another supported browser. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: There can be a discrepancy between the replication image count in volume and snap-pool properties. Workaround: Use the snap-pool properties to verify the counts. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Interface changes may not occur when using the modify user panel in the Storage Management Console. Workaround: Use the CLI to change interface settings. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: the Storage Management Console Home Page graphical representation on the bottom left side of the page shows the system health as OK for two controllers when there is a single controller in the system. Workaround: Use the system tab to determine health of the installed controller. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Storage Management Console a volume with less than 500 GB rounds to 0 TB when snapshots are enabled. Workaround: Use the CLI if you require snapshots of smaller volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Some initiator entries may remain when deleting large number of initiators using RAIDar. Workaround: Retry deleting the remaining initiators. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The login page displays a warning message that the system is currently unavailable when the partner controller is shutting down. Workaround: Allow the partner controller to shutdown and failover completely and then retry accessing the system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: After completing the Storage Management Console configuration wizard, date and time changed events are generated even though no modification to date and time was done. Workaround: Enable NTP on the array. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When the health is degraded, the information can be truncated when hovering over the system health on the Storage Management Console v3 Home Page. Workaround: Use the System Topic to investigate the health of the components. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The system table view refreshes automatically, going back to the first pages after 10-15 seconds. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Transfer rate is not shown in the Storage Management Console v3 when selecting a disk in the system topic. Workaround: Transfer rate can be found using the CLI detail option to the show disks command, or in RAIDar under the enclosures. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Mapping a large set of linear disk-group based volumes may take longer in the Storage Management Console v3 interface than when using RAIDar. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: SNMP community strings use the disk-group terminology in place of vdisk. Workaround: Disk-groups should be considered as synonymous with vdisks. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Attempting to map volumes above the limit of the controller can produce an invalid LUN error message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI reset all-statistics command didn't reset the pool and disk statistics. Workaround: Reset the pool and disk statistics independently. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: the Storage Management Console v3 Home Page does not display the units in "MB" when a user's "unit preference" is changed to "MB." Workaround: The Home Page automatically scales based on the sizes in use. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Thin provisioning notification may not be sent when a virtual pool is smaller than 500 GB. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Browse button fails to open the file selection pop up in the license screen. Workaround: Refresh the browser. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The error message for setting or creating a host name does not list \ as an unallowed character. Workaround: Do not use a \ character in the host-name. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Remote replication fails to create a remote volume when the locale of the remote system is set to something other than English. Workaround: Ensure that the remote system is set to English locale. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console v3 Create Virtual Volume panel uses Copies terminology instead of Number Of Volumes. Workaround: Copies should be considered as synonymous with Number Of Volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: An incomplete error message stating that a space is included is displayed when invalid characters are used in the Sender name for email notifications. Workaround: Check the help to find the invalid characters. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The output of the CLI show disks detail command returns Drive Spin Down Count as 1 for SSDs. Workaround: Ignore the Drive Spin Down Count for SSDs. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Related Snapshots shown in the Volumes Pane in Storage Management Console v3 does not list all the descendant snaps of the volume. Workaround: Select each descendant snapshot to see the related snapshots. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When creating a task to reset a virtual volume snapshot, an error message incorrectly states that the specified volume was not found. Workaround: The message should state that this operation is not supported for virtual volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI displays invalid pool details for virtual disk groups temporarily. Workaround: This is a temporary state that will resolve itself. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Attempting to modify an existing replication schedule displays an error message that the start date/time cannot be set to earlier than the current date/time. Workaround: Enter a data/time in the future for the new Start time for modified schedule. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The filter of Severity is truncated if there are two events in the event list. Workaround: If the event list has been filtered down to only one or two events and the filter menu is truncated, close the event list dialog and reopen it. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console v3 is not rendering several elements properly in Internet Explorer 10 and 11. Workaround: Disable Compatibility View in IE 10 and IE 11. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Mapping over 500 volumes at the same time in Storage Management Console v3 may not complete all mappings. Workaround: If possible, perform large number of volume mappings in chunks to avoid timeout and other errors. When mapping a large number of volumes from the Storage Management Console, avoid refreshing the browser while the operation is in progress. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Thin provisioning information reported in Storage Management Console v3 and the CLI may not be in sync. Workaround: Use the CLI to immediately track size data. Allocated and available storage has a 3-5 minute delay in the Storage Management Console. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Partner Firmware Update can fail if there is a health issue in the system. Workaround: Determine array upgrade health by running the CLI check firmware-upgrade-health command. Address the health issue and reload the code on the controller | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: the Storage Management Console v3 Create Initiator window shows a message in red text. Workaround: The initial validation error message does not affect functionality. Proceed with entering the ID and name and the initiator will be created. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: After creating a new volume, the volumes table is not updated for multiple seconds. Workaround: The table will be updated after a short time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console v3 help does not show internal IP addresses in use by the array. Workaround: Use the CLI help set network-parameters command to view internal IP addresses in use by the array. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Using an initiator nickname of "all" is incorrectly allowed and will delete all initiators if the nickname is used in the delete initiators command. Workaround: Do not create an initiator with a nickname of "all." If a nickname of "all" has been used, delete the initiator using the unique identifier. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The profile for an initiator is not shown in Storage Management Console v3. Workaround: Use the CLI to view the profile of the initiator. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Initiator profiles cannot be set in Storage Management Console v3. Workaround: Use the CLI to modify initiator information. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In rare circumstances after creating virtual disk groups, one or more may appear in the wrong pool in the Storage Management Console v3 Pools Topic. Workaround: Refresh the browser window to display the disk groups in their proper pools. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: If an error occurs during virtual disk group creation it may not be possible to remove it through the Storage Management Console v3 interface. Workaround: Use the CLI to remove a disk group that cannot be removed through Storage Management Console v3. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console Install License Panel refers to temporary license functionality, but this functionality is not available. Workaround: Request temporary licensing from your vendor. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: After adding disk-groups the performance charts displayed in the Storage Management Console v3 show incorrect data. Workaround: Gather disk statistics using the CLI or reset the performance statistics. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to create a snapshot using now or schedule options after creating a schedule on another volume when using Internet Explorer 11. Workaround: Use a different supported browser or refresh the browser session. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to change the End Schedule details from a modify scheduled snapshot when using Internet Explorer 11. Workaround: Use a different supported browser or refresh the browser session. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Strings are truncated in some cases in Storage Management Console v3 when locales other than English are used. Workaround: Use the CLI for the functionality or the English locale in Storage Management Console v3. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In non-English locales the Storage Management Console v3 does not reflect the NTP-enabled state when it has been enabled using the CLI. Workaround: Use the CLI to determine whether NTP is enabled. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Some panes and drop-down menus may not display correctly in locales other than English. Workaround: Use the CLI to complete operations or use the English locale. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: A remote replication schedule fails to create if system time minutes are greater than the scheduled start time minutes. Workaround: Use the CLI to set the SNMPv3 Privacy Type. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to select SNMPv3 Privacy Type in locales other than English in Storage Management Console v3. Workaround: Use the CLI to set the SNMPv3 Privacy Type. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: English strings are seen in other locales. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In RAIDar, events are not sorted in either ascending or descending order when the code column is clicked in the system events. Workaround: The codes are sorted alphabetically, so 100 will appear before 2 in the list. Manually search for the desired code. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In RAIDar, the turn on LEDs option is disabled in the vdisk overview¨disks panel. Workaround: Perform the function in the enclosure view. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Removing a controller from the remote system can cause a condition where the remote system object cannot be deleted. Workaround: Add back the missing controller so that it is a dual controller system again. If using a replacement controller, ensure that both controllers have the same software version. Wait up to three minutes and retry delete remote-system. In the rare case that it does not work, restart both systems and retry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When creating a second replication set using an Internet Explorer 11 browser, the Apply button does not work. Workaround: Refresh the browser. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to enable or disable encrytped SMI-S using the configuration wizard in Storage Management Console v3. Workaround: Use the CLI, RAIDar, or the Storage Management Console system services panel to enable or disable encrypted SMI-S. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The Storage Management Console v3 does not send managed log email when the gateway is 0.0.0.0. Workaround: Set an appropriate gateway address. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to finish the configuration wizard in Storage Management Console v3 if an invalid iSNS address is supplied in step 8 of the wizard even if the value is corrected. Workaround: To get out of the configuration wizard, click on cancel or uncheck the enable iSNS option, and then apply the correct iSNS. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: No error message is displayed when an incorrect date/time is entered through configuration wizard step 2 of 9. Workaround: If the next button is not enabled on step 2 of the configuration wizard, check that the date/time is correct. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Snapshot schedules didn't begin until a MC restart or taskless schedules are deleted. Workaround: Remove the taskless schedules and restart the MC. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When adding large number of hosts to a host group, the command may fail. Workaround: Add hosts to the host group in smaller increments. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: The CLI, RAIDar, or SMI-S interfaces become slow or unresponsive. Workaround: Restart the Management Controller from RAIDar or the CLI on an operating controller. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 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 show enclosures command to ensure that the EMP versions are correct. In RAIDar, 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 show enclosures command reports health is OK when it should be DEGRADED due to leftover drives. Workaround: Use the CLI show system command 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, reconfigure the affected schedule or task to the intended configuration. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the Create Volume screen in RAIDar, 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, RAIDar might freeze or become nonresponsive. Workaround: Restart the browser session. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: SMI-S Indication subscription to the array fails. Workaround: Run the CLI reset smis-configuration both command 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 RAIDar Reset or Save Disk Performance Statistics panel to collect statistics, or do not restrict the log to a specific time range. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: 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: In locales other than English, the Date, Time panel might not reflect the correct NTP settings. Workaround: In RAIDar, 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: 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: In RAIDar, 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 RAIDar, 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 RAIDar 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: After repurposing a drive in RAIDar, 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: RAIDar 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 RAIDar. 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 RAIDar after clicking the Apply button. 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 show frus command 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 RAIDar 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 the Apply button. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: Unable to create a weekend suspend task on a weekend day in RAIDar. 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 unwritable cache, components of a firmware upgrade fail. Workaround: Ensure that there is no unwritable 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 the CLI show ports command. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: If the auto-write-back setting is disabled using the CLI set auto-write-through-trigger 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 restart sc both command) 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 RAIDar. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: In the RAIDar 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 login 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: RAIDar 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 Internet Explorer 9 in compatibility mode to access RAIDar, 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 RAIDar events log. Workaround: Reset the controller date and time to be current, and restart the management controller. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: RAIDar 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 RAIDar 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: When creating a volume in RAIDar, 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 RAIDar or CLI to modify the volume name. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: When you click Configuration → Remove User in RAIDar, 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: 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 RAIDar, / (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: 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 RAIDar, even if they are spun down using the drive spin-down feature. Workaround: None. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: On the Configuration → Advanced Settings → 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 USB device driver for the mini-USB CLI port. This driver is available for download in the Software Downloads section for your product on the Dot Hill Customer Resource Center website at http://crc.dothill.com. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue: There is no indication that a LUN has failed-over to the other controller. Workaround: Using RAIDar, 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 RAIDar, 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 RAIDar 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 CLI show events command to identify the failed device. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Firmware version | AssuredSAN 3004, 4004, Ultra48, and Ultra56 | Release date |
|---|---|---|
| GL210R006-08 | All | August 2015 |
| GL205R007 | Ultra56 | April 2015 |
| GL200P002 | AssuredSAN 3004, 4004, Ultra48 | March 2015 |
| GL200R007 | AssuredSAN 3004, 4004, Ultra48 | December 2014 |
| GL105P002-03 | AssuredSAN 3004, 4004, Ultra48 | July 2014 |
| GL105P002-02 | AssuredSAN 3004, 4004, Ultra48 | June 2014 |
| GL105R005 | AssuredSAN 4004, Ultra48 | April 2014 |
| GL101R001 | AssuredSAN 4004 | November 2013 |