Issue: Moving an LX controller from a low-density enclosure to a high-density enclosure initiates the dynamic EC code upgrade, but the controller might be killed by the primary controller due to a timeout.

Workaround: Remove and re-insert the downed controller. When the controller reboots, the EC code will be updated to the correct version.

Issue: Sending commands to retreive the associations of supercap via SMIS may cause an MC crash.

Workaround: MC will reboot. Retrieve information on the supercap through other interfaces.

Issue: In rare cases during a PFU, the EC might not update.

Workaround: Reloading code on the affected controller will update the EC to the appropriate version.

Issue: When swapping controllers between a high-density and low-density chassis, the appropriate EC might not be loaded automatically.

Workaround: Loading code on the affected controller will update the EC to the appropriate version.

Issue: In a low-density chassis, the CLI show expander-status command may incorrectly report the expander is in the "left drawer" although this chassis has no drawers.

Workaround: This is a display issue only and can be ignored. No workaround is necessary.

Issue: A controller crash might occur if the host operating system issues very large unmap commands to the controller.

Workaround: Reboot the crashed controller. Some operating system settings might be available to limit unmap commands to under 1GB.

Issue: In some cases, downgrading to an earlier firmware version might fail to downgrade the MC properly.

Workaround: Reload the desired firmware bundle.

Issue: Unable to create a peer connection after deleting a previous peer connection when using Asynchronous Replication .

Workaround: Reboot both SCs at the same time using the CLI restart SC both command. Or, from the WBI, choose Restart System from the pull-down menu under the version number at the top. Select Restart with Storage and select both controllers.

Issue: In some cases, when moving controllers from a high-density chassis to a low-density chassis the proper EC component might not be loaded.

Workaround: Loading code on the affected controller will update the EC to the appropriate version.

Issue: In a very rare case, after a controller failover. replication schedules might be removed.

Workaround: Manually recreate the replication schedule.

Issue: An aborted replication might show status as "Unsynchronized" rather than "Aborted."

Workaround: This is a display issue only and can be ignored. No workaround is necessary.

Issue: In the online help for the "Scheduling replications" task, some details are missing, including the permitted number of characters and which characters are invalid.

Workaround: The limitations on replication schedule names are the same as for replication set names. Refer to the Storage Management guide for limitations on replication names.

Issue: When trying to delete a pool with a replication set defined, this error message might display: Error: Command is not supported. - Failed to delete the virtual pool.

Workaround: Remove the replication set and then delete the pool.

Issue: Modifying the password for an SNMP v3 user might default the authentication type and privacy type to none.

Workaround: When modifying the password for an SNMP v3 user, also modify the authentication type and privacy type to the desired values.

Issue: Email notification for "Event 175: The network-port Ethernet link is up for a controller" might not be sent.

Workaround: Use the WBI or CLI to check the status of Ethernet links.

Issue : If a replication set has entered a suspended state, the events may be inconsistent between the peer systems with respect to the reason for suspension.

Workaround: Review the events on both peer systems.

Issue: CLI help for de-quarantine shows example of virtual disk groups, but virtual disk groups cannot be de-quarantined without support assistance.

Workaround: None.

Issue: If a replication is suspended by the system, the array with the secondary volume may incorrectly report an event that the replication was suspended by the user.

Workaround: None. On the first subsequent attempt to resume the replication, if the error condition still exists, the user will get an appropriate error message.

Issue: A very long user name will partially hide the session timer in the Storage Management Console.

Workaround: None.

Issue: The modify peer-connection section in the Storage Management Console online help incorrectly states that a new name can have 80 bytes.  The correct maximum number of bytes is 32 bytes for peer names. Anything over 32 bytes will be rejected.

Workaround: None.

Issue: The confirmation message received in the Storage Management Console Configuration Wizard does not clearly indicate which services are disabled when notifying the user that disabling an interface will disable the interface.

Workaround: None. The selected services are disabled. Verify services in the Storage Management Console.

Issue: After installing a license file in the RAIDar v.2 interface, the Browse button for installing a second license file may not allow changing locations.

Workaround: Refresh the browser session.

Issue: Downgrading firmware may fail due to enabled features that are only available in the latest firmware being unavailable in previous firmware versions.

Workaround: None.

Issue: After performing a trust command in the CLI, hosts may not be able to write to volumes.

Workaround: Perform a rescan from the CLI.

Issue: Operations are allowed in the primary system on a replication set when the same replication set is not available in secondary system.

Workaround: Review Events to identify if operations are successful.

Issue: The maximum number of characters that can be used in modify schedule is not included in the Storage Management Console online help.

Workaround: The maximum number of characters is limited to 26.

Issue: When trying to modify a peer with a remote address of a system for which another peer connection already exists, you get the error Error: The replication set was not found.

Workaround: Verify the remote system is part of the peer connection you are attempting to modify.

Issue: The amount of space reported as used in a snap-pool may be larger than the sum of all snapshot data contained in the snap-pool.

Workaround: None. The space calculation difference is due to allocation granularity differences in snapshots compared to the snap-pool.

Issue: If NTP is enabled, using set controller-date in the CLI will not perform any validation of the date format.

Workaround: When setting the controller date with NTP enabled, ensure that you use a valid date format.

Issue: The CLI command show network-parameters shows ‘link-speed’ as ‘10mbps’ and ‘duplex-mode’ as ‘half’ when an Ethernet port is unplugged or a controller is uninstalled.

Workaround: No workaround is required; ignore invalid output.

Issue: The CLI command set volume is allowing the use of the invalid double-quote and comma characters.

Workaround: Do not use the double-quote or comma characters.

Issue: In the Storage Management Console the SNMP Read and Write community strings allow the use of the invalid single-quote character.

Workaround: Do not use the single-quote character.

Issue: The version of a failing FRU may not be in the event logs.

Workaround: Look at the label on the FRU for the version number.

Issue: In the save logs operation, if a single-quote character is used in any field, the retrieved logs will be empty.

Workaround: Do not include single quotes when using the save logs operation.

Issue: A very long user name will be partially hidden under the Sign Out button.

Workaround: None.

Issue: In the Storage Management Console or RAIDar v2 interface, the forward slash character may be replaced with a space character.

Workaround: Fields that require the use of a forward slash should be entered via the CLI.

Issue: The use of the angled brackets when creating vdisks names is erroneously allowed in the CLI.

Workaround: Do not use angled brackets when creating vdisks names in the CLI.

Issue: An erroneous event is generated when telnet is disabled or enabled in the Storage Management Console or RAIDar v2 interface.

Workaround: Ignore the erroneous event.

Issue: Minimal discovery information is retrieved from SNMP v1 when SNMP v3 is enabled.

Workaround: None.

Issue: The creation of CHAP records erroneously accepts names not in IQN format.

Workaround: Use only valid IQN formatted names.

Issue: Event Code 522 does not display the name of the volume when the show events command is run.

Workaround: None.

Issue: When using the RAIDar v2 interface, during the add replication set operation, an error message can be shown twice.

Workaround: Ignore the duplicated error message.

Issue: Cannot perform actions on multiple replication sets in the Storage Management Console or RAIDar v2 interface at the same time.

Workaround: Perform actions on replication sets one at a time.

Issue: Disk scrub status is not available when displaying disk information.

Workaround: Review event logs for disk scrub status.

Issue: Drives in LEFTOVER state may not illuminate the amber fault LED.

Workaround: Validate drive status in the user interfaces.

Issue: SMI-S will report the device ID of IOMs in disk enclosures as "0" for the B controller and "1" for the A controller.

Workaround: Use the ElementName to determine whether the A or B controller is in use.

Issue: The CLI show fans command displays fan status as up for a removed power supply.

Workaround: Use the CLI show power-supplies command to see the state of the power supplies.

Issue: The RAIDar v2 interface does not enable the option to set a volume as a primary volume for local replications.

Workaround: Use the CLI.

Issue: A controller crash may occur if backend cabling is misconfigured.

Workaround: Follow the documented cable configuration guidelines.

Issue: FDE Lock Key IDs may display inaccurately if reconfiguration of FDE features is attempted after clearing the Lock Key IDs and before power cycling the system.

Workaround: The system must be power cycled immediately after clearing the FDE Lock Keys.

Issue: Some 314 events are not being reported by SNMP trap for the partner controller.

Workaround: Register for events for both controllers.

Issue: The RAIDar v2 interface returns an error stating a value must be an unsigned integer when creating a volume set and the number of volumes is blank or not a number.

Workaround: Enter a valid number in the number of volumes field.

Issue: In step 4 of the RAIDar v.2 interface's provisioning wizard, the size field may not immediately update after entering the number of volumes.

Workaround: Press the TAB key twice to have the field updated.

Issue: The Storage Management Console or RAIDar v2 interface does not allow for all valid special characters to be used in an email notification sender name.

Workaround: Use the CLI command set email-parameters.

Issue: Messages are not translated while collecting logs.

Workaround: None.

Issue: In virtual storage remote replication, the secondary site could experience issues that could cause the replication to suspend.

Workaround: The replication will automatically resume in 10 minutes or the user can manually resume it.

Issue: In single controller mode, resetting all statistics can results in a message that the request cannot be completed because the other controller is not up. - Failed to reset controller statistics.

Workaround: Ignore the error message; all statistics that can be reset are reset.

Issue: Firmware update status messages in the Storage Management Console or RAIDar v2 interface are not translated.

Workaround: None.

Issue: The Add Initiator to Host panel in the Storage Management Console can display "no host" as an option.

Workaround: Ignore the erroneous option.

Issue: The CLI command clear disk-metadata shows a successful command stating that the command completed successfully, but the metadata was not cleared.

Workaround: Run the command again to clear the disk metadata.

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 v2 interface's 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: 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: 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: 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: 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: 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's 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: 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: 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: 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: 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: 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: 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: 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: 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: 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 v2 interface's 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: 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 v2 interface's 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 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: 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 v2 interface's 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 v2 interface's 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 v2 interface's 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.