Dot Hill AssuredSAN 3004, 4004, 6004 Series Release Notes for Software Version G222R050

Part Number: 83-00006718-25-01

Published: September 2017

---

Copyright © 2015, 2017 Dot Hill Systems Corp.

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.

Acknowledgements

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

---

---

Version: Rev. A

· Controller firmware: G222R050

Description

This package delivers firmware for AssuredSAN 3000 Series, 4000 Series, and 6000 Series RAID controllers and AssuredSAN drive enclosures.

IMPORTANT: For a list of supported companion drive enclosure firmware, see “Additional devices.”

Versioning key:

AxxxByyy-zz

The following letters represent firmware version release information:

Firmware version	Description
A	AssuredSAN model.
xxx	Firmware version. This value changes for major, scheduled releases. Depending on the AssuredSAN model, this number may also indicate model protocol.
B	Type of release. (R=Regular release, P=Planned update to a regular release, S=Special release)
yyy	Major release number.
-zz	Minor release number.

Update recommendation

This is a recommended firmware update for 3000 series, 4000 series, and 6000 series products.

Supersedes

· Controller firmware: G222P012, G222P007, G222R003, GL210R006, GL205R007, GL200P002, GL200R007, GL105R005, GL105P002-02, GL105P002-03

Product models

AssuredSAN 3004 Controllers

· AssuredSAN 3004 FC Controller

· AssuredSAN 3004 1G iSCSI Controller

· AssuredSAN 3004 10G iSCSI Controller

· AssuredSAN 3004 SAS 12G 2-port Controller

AssuredSAN 4004 Controllers

· AssuredSAN 4004 Controller

· AssuredSAN 4004 SAS Controller

AssuredSAN 6004 Controllers

· AssuredSAN Ultra48 Controller

· AssuredSAN Ultra48 SAS Controller

· AssuredSAN Ultra56 Controller

· AssuredSAN Ultra56 SAS Controller

Operating systems

Supported operating systems include:

· Microsoft Windows Server 2008

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2008 Hyper-V

· Microsoft Windows Server 2012

· Microsoft Windows Server 2012 R2

· Microsoft Windows Server 2012 Hyper-V

· Red Hat Enterprise Linux 5

· Red Hat Enterprise Linux 6

· Red Hat Enterprise Linux 7

· SuSE Linux Enterprise Server 11

· SuSE Linux Enterprise Server 12

· VMware ESXi 5.0/5.1/5.5

· Apple Mac OS X Mavericks 10.9.0 and 10.9.2 (Fibre Channel only)

Additional devices

AssuredSAN 3004, 4004, 6004 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 J6G12 and J6G24 (3120, 3130, 4120, and 4130) drive enclosures	S200B38
AssuredSAN 4124 and 4134 drive enclosures	S200B38
AssuredSAN J6G48 48-drive SFF enclosure (4000 series)	A420R03
AssuredSAN J6G56 56-drive LFF enclosure (4000 series)	A420R03
AssuredSAN J6X48 48-drive SFF enclosure (6000 series)	X520R03
AssuredSAN J6X56 56-drive LFF enclosure (6000 series)	X520R03

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.

Security considerations

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.

The following issues were fixed in G222R050

· Fixed atomic metadata update on disks.

· Populate drive-related information if SMART errors are detected during probe.

· Fixed uninitialized variable related to scrub processing.

· Added entries to debug log for "drain I/O stuck" scenarios.

· Corrected event information (manual/auto dequarantine event).

· Fixed RAID-5/6 parity errors on power cycle.

· Fixed an issue to avoid writing/committing the metadata directory for the volumes if the vdisk is quarantined.

· Handled container buffer log for mirror vdisks.

· SEAVE/CRIER: Computed XOR using CPU for parity error LBA detected using HW XOR.

· Prevented controller crash upon drive pull during RAID-6 verify.

· Recovered RAID invalid metadata for a particular corner case.

· Prevented a data-loss issue that occurred when vdisks owned by one controller had a flush/restore failure.

· Prevented allocation of space on virtual disk groups that aren't fully initialized.

· Fixed an issue where a pool went offline due to unreadable metadata (BLPT error) caused by partial allocation of cache resources for paged metadata updates.

· Allow background operation on vdisk if disk-group removal from pool fails due to insufficient space.

· Fixed a case where a controller killed its partner due to heartbeat loss in a paged-storage system.

· Increased the auto-stall recovery timeout to support a large paged-storage configuration.

· Reduced possible heartbeat loss kills with large, very sparsely allocated volumes.

· Avoid paged-storage metadata integrity issues when there is a power failure or controllers are killing each other.

· Fixed an issue where the VDRAIN operation was taking too long to complete, affecting performance.

· Prevented deletion of a paged-storage component when its pool is in a faulty state.

· Fixed a case where an offline component of a pool caused a data integrity issue by preventing paged-storage metadata update.

· Prevent hang during page moves if a controller is killed due to heartbeat loss.

· Fixed controller crash by improving resource handling of paged storage for shared pages.

· Fixed an issue where the overcommit calculation for a virtual pool was inaccurate.

· Prevented paged storage resource leak.

· Fixed an issue where the event log showed the wrong reason for replication suspension.

· Fixed an issue that prevented creating a peer connection after deleting a previous peer connection.

· Fixed an issue where a controller was killed due to heartbeat loss when a virtual replication operation was resumed after being suspended.

· Fixed a replication-set failure that occurred when the large-pools option was enabled.

· Fixed a problem that prevented creating a replication set for a volume group between a single-controller system and a dual-controller system.

· Fixed an issue where the secondary log doesn't contain logs of suspended replication.

· Fixed an issue where virtual replication was suspended by the system due to a communication issue with the peer.

· Fixed an issue where a controller was killed due to a PCIe link recovery failure related to virtual snapshot functionality.

· Fixed an issue where the CPLD version could not be read during certain boot operations.

· When recovery is in progress in one controller, if shutdown/reboot is issued to that controller then reject it.

· Fixed an issue where the WBI did not display disks and vdisks correctly if the disk list had an entry with an empty serial number.

· Fixed a dual-controller crash that resulted in vdisks being quarantined.

· Enhanced error reporting to help debug issues such as PCIe link errors.

· Fixed a bug in IPC link recovery.

· Fixed an issue where a pool disappeared after failover from a PCIe link recovery failure.

· Fixed an issue where both controllers continuously crashed with a page fault.

· Fixed a case where data integrity issues were observed during fail-unfail with replication.

· Fixed an issue of not being able to write files to a mounted LUN after an unsafe trust operation.

· Fixed polling logic to reduce CPU% when the system is otherwise idle while VSS app is monitoring via in-band CAPI.

· Fixed an issue where the system prevented users from deleting hosts.

· Fixed an issue that caused a controller to crash with a page fault during linear replication.

· Fixed a problem that caused malformed SCSI packets during conversion of a standard volume to a master volume.

· Fixed an issue related to an invalid LBA that led to a controller crash when using linear replication.

· Fixed an issue that caused a dual-controller crash when an I/O error occurred during linear replication.

· Fixed a corner case of a linear-replication metadata integrity issue and controller crash (page fault) that occurred when a new controller was inserted.

· Fixed an issue that caused a controller to crash due to an abort of management I/O.

· Fixed an issue where after a clean shutdown and restart of both controllers, one controller’s vdisks had QTOF status.

· Fixed an issue where a controller killed its partner with reason “Message to other failed” during disk firmware update.

· Fixed a controller kill at shutdown time by implementing a dynamic auto-stall recovery limit for paged-storage failovers.

· Fixed an issue of controller crash when “Sync Cache Mode” is set to “Flush to Disk”.

· Fixed an issue of “Dirty Cache” elements and missing virtual disk group from a pool.

· Fixed DDR port degradation to prevent a hang issue.

· Fixed an issue where low cache resource in the DMS failover path caused a dual-controller crash.

· Fixed an issue where a LUN became inaccessible after I/O timeout messages appeared.

· Fixed a data integrity issue caused on atomic-write volumes when the volume comes back online.

· Fixed an issue where a bug in Bad Block Recovery (BBR) handling caused a controller crash.

· Fixed an issue that prevented unlocking or repurposing a secured-locked disk.

· Modified events 55 and 314 to show the vendor and product ID for HDDs.

· Fixed excessive load/unload cycles for HDDs in a 4U56 enclosure.

· Fixed incorrect numbering of enclosure.

· Fixed an issue where a VMWare host received “cannot connect to storage” messages.

· Prevented setting an FDE import key before an FDE lock key.

· Fixed a failure-to-flush issue.

· Enhanced information about virtual pool thresholds shown by event 462.

· Fixed an issue that prevented background disk scrub from running.

· Added a check to prevent sending a CAPI request to the SC if no license is installed.

· Fixed an issue of OpenVMS Host Profile not being available.

· Fixed an issue of setting OpenVMS Host Profile in the WBI.

· Fixed an issue where linear storage is not the default type for disk-group creation in certain products.

· Modified event 314 (JBOD midplane FRU fault) SNMP traps to remove the slot number field, which is not applicable.

· Fixed an issue of intermixing OIDs of vendors while running snmpwalk.

· Fixed the truncated display of security certificate installation instructions in FTP help.

· Fixed a memory leak that could occur during firmware update.

· Fixed an issue where managed logs email attachments were not received after updating to a firmware version that supports TLS/SSL for email.

· Determined that the recommended upgrade path from GL105 to GL222 is to first upgrade from GL105 to either GL200 or GL210, and then to GL222.

· Fixed an issue where a firmware bundle did not load on the partner controller with PFU enabled.

· Fixed an issue where the MC didn't completely come up after a firmware update.

· Addressed WebServer Hanging issue which happens because of SSL.

· Enforced input validation for replication-set names to prevent an issue that caused creation of a replication set to time-out.

· Fixed an issue in taking a snapshot of a virtual volume.

· Removed duplicate “from” keyword from the confirmation message displayed after creating a virtual disk group in the CLI.

· Added string translation for Host profile keyword.

· Added OpenVMS profile translation for non-English language.

· Removed temporary files created during the firmware update process.

· Fixed deadlock issue that could occur while performing firmware update.

· Enforced input validation for host names to prevent an issue where hosts with invalid names could not be added to or removed from a host group.

· Fixed an issue where the CLI show inquiry command displayed a MAC address instead of a serial number.

· Fixed an issue with host mappings when user tries to modify an initiator which has mixed-case characters.

· Fixed an issue that caused the MC scheduler to stop running.

· Removed IPv6 support for controller module network ports. (IPv6 is supported for iSCSI host ports.)

· Provided a fix to avoid the error message reported when replication schedule got triggered.

· Fixed an MC deadlock issue that could occur after or during restart scenarios.

· Fixed an issue of no warning message during configuration if duplicate IP addresses are detected.

· For SSD errors, health recommendation text is enhanced to provide more information on the actual cause.

· Removed debug prints for command set replication-volume-parameters remote-address because it was causing APPSV to crash when volume is replicated using 8 port addresses and user is trying to change it to 4 ports.

· Fixed a DOM dataset exhaustion issue for a system comprised of 4U56 enclosures.

The following issues were fixed in G222P013

· Firmware upgrade/downgrade between GL210 and GL222 when volume read-ahead-size parameter was not set to the default.

· Data corruption observed during repetitive fail-unfail operations with replications running.

· Malformed Managed Logs e-mail message.

· Schedule error that occurred while deleting a remote snapshot.

· Logs from the Managed Logs feature were incomplete.

· Added support for SCSI Send Diagnostic command when in-band SES is disabled, so the command is not rejected for the default LUN.

· When using VMware, a controller crash might occur if the host operating system issues very large unmap commands to the controller.

· DMS issue that caused CAPI hang and I/O failures.

· Communication Down fault type remained on a controller after reboot.

· Dual-controller crash in an all-flash array system with multihost I/O and high queue-depth setting on HBAs.

· While deleting hundreds of snapshots, using Windows Disk Management to start a format on two volumes in pool A caused controller A to crash.

· Controller heartbeat loss caused a controller to be killed in a virtual-storage system.

· After a controller rebooted, the system reported degraded health for a period of minutes because a disk was using the alternate path.

· Fixed an issue found during repetitive failover/failback testing.

· The auto-stall recovery feature killed a controller that was incorrectly detected to be hung.

· Controller page fault found during failover/failback testing.

· In a system using virtual replication, a replication operation was suspended because communication could not be established with the peer.

· Crash caused when a system with large disk groups using a mix of HDDs and SSDs reached the maximum queue depth.

· Management Controller crashed when deleting a schedule.

· Adjusted queue depth for all-flash array systems using SAS SSDs.

The following issues were fixed in G222P007

· Problem with B2A configuration exchange.

The following issues were fixed in G222P006

· Limit read cache usage by shared page write to prevent deadlock.

The following issues were fixed in G222P005

· Source volume delete in a forwarded CAPI Volume Copy Abort command.

The following issues were fixed in G222P004

· Reverting trunk revisions 213165 and 212724.

The following features or enhancements were introduced in G222P003

· Fix data corruption due to small timing window when a write that was originally to a shared page becomes an unshared page write during its processing.

The following issues were fixed in G222P003

· Disable slot affinity by default for Customer.

· Fix Write Same U32 vs. LBA64 bug.

The following issues were fixed in G222P002

· New Replacement Controller with PFU changed array settings.

· CAPI hang after CacheWriteInternalContainer() stalls.

· Improve performance by inlining DLQUE and changing the way the io size histogram is logged.

· Move the HAL_POWER_CHECK macro out of the data path and into the exception path in order to increase write performance.

The following features or enhancements were introduced in G222P001-02

· Prevent possible incorrectly shared pages caused by controller failure during reset/rollback and controller I/O.

· Prevent pagetable corruption caused by overfilling Paged Storage metadata.

· Fix uninitialized debug value.

The following issues were fixed in G222P001-02

· Issue with MLIO IOs delaying failback.

· CAPI hang after shared page write failures, non-cache memory exhausted.

· Controller crashes with page fault and snappool deleted after powercycle.

· Corruption with simultaneous new writes & controller crash.

· For paged storage, use saved value for InFlight blpte in error handling of shared writes in Execute_IO actor.

· Set default OEMID.

The following features or enhancements were introduced in G222P001-01

· Clean up some problems with systems with mixed drive PI formats.

· Fix DC exposure with controller failure during shared page write update.

· Prevent possible incorrectly shared pages caused by controller failure during reset/rollback and controller I/O.

The following issues were fixed in G222P001-01

· Don't update the flash copy of the enclosure table if another thread owns the flash or config semaphores.

· Reset the internal HIO flag upon the destruction of an HIO object.

· Added some fixes to avoid crashes if some AR commands are issued when peer is missing.

· Missing CS metadata, TLPT Page Fault.

· Return an error if a CAPI_COMMAND_U_GET_CS_REPLICATION_SETS is received during failover or failback.

· ATS/XCOPY delays failover/failback.

· Allow child MLIOs through to local cache when failback is active.

· Enable replicate actor to handle DMAs executing out of order to perform I/O in the correct order.

· WBI pop-up occurs every couple of minutes saying codeload is in progress, inhibits use of WBI for several minutes at a time.

· Add InFlight Bit.

· Fixed DC exposure. Don't update BLPTs that point to pages that other shared page writes are still copying data to.

· Page faults seen when snapshots are used and virtual LBA space exceeds ~157TB.

· Decrease the Paged Storage unmap size to 1 page.

· Dynamic EC crash fix.

· Prevent internal write I/Os from hanging when the controller goes into write through.

The following features or enhancements were introduced in G222R003

· Added the following features for virtual storage:

· Asynchronous Replication.

· Volume Tier Affinity.

· Enhanced snap pool management.

· Enhanced volume copy.

· Added scheduler for virtual storage based snapshots.

· Added persistent SNMP alerts for critical events until the condition is cleared.

· Added capability for larger virtual pools.

· Server certificate is signed using SHA-256 algorithm.

· Updated OpenSSH to 7.1 to mitigate CVE-2015-5600, CVE-2015-5352, CVE-2014-2653, CVE-2014-2532, CVE-2014-1692, and CVE-2013-4548.

· Added additional information to FRU events.

· Added empty page reclamation information.

· Added hover tip to 3004 with Fan Out configuration to include Recommended Actions.

· Added new poolHealthReason to enhance the understanding of virtual pool health.

· Added the ability to de-quarantine linear disk-group from QTCR state when drives were removed/inserted during an expand operation.

· Deprecate non-optimal Disk Group chunk sizes.

· Disable RC4 cipher suite to mitigate CVE-2015-2808.

· Disabled 96-bit and MD5-based HMAC and CBC mode ciphers.

· Disabled SSL compression to mitigate CVE-2012-4929 and CVE-2012-4930.

· Disabled SSLv2.

· Disabled Telnet protocol by default.

· Disabled weak SSL ciphers.

· Enhanced accuracy of size shown in Storage Management Console for drives larger than 1 TB.

· Enhanced managed logs emails.

· Enhanced the severity for Event 571 in the case of allocated pages crossing the high threshold.

· Enhanced the wording for Event 573.

· Improved CLI error messaging.

· Improved SMI-S indication for events.

· Improved SMI-S indication support for FRUs.

The following issues were fixed in G222R003

· The Install License menu item, and other features such as Create Snapshot, might not appear in the Storage Management Console or the RAIDar v2 interface.

· In the RAIDar v2 interface, the turn on LEDs option is disabled in the Vdisk Overview>Disks panel.

· After the firmware is updated on the array, the Storage Management Console or the RAIDar v2 interface might freeze or become nonresponsive.

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

· In Internet Explorer, when the online help button is clicked in the Storage Management Console or the RAIDar v2 interface, it can take a couple of minutes for the online help window to be populated with content.

· The Create Volume/Volume-set page highlights Access field in red (only once per volume).

· In Storage Management Console or RAIDar v2 interface popups, buttons aren't enabled until clicking outside of the data entry fields or selecting Tab.

· Partner Firmware Update can fail if there is a health issue in the system. If the code load health checker determines that firmware should not be loaded, no event will be logged.

· The Storage Management Console's Create Virtual Volume panel uses Copies terminology instead of Number Of Volumes.

· Related Snapshots shown in the Volumes Pane in the Storage Management Console does not list all descendant snapshots of the volume.

· A message incorrectly states "The specified volume was not found" when creating a task to reset a virtual volume snapshot.

· The CLI displays invalid pool details for virtual disk groups temporarily.

· The filter of Severity is truncated if there are two events in the event list.

· The Storage Management Console is not rendering several elements properly in IE 10 and IE 11.

· Thin provisioning information reported in the Storage Management Console and the CLI may not be in sync.

· Storage Management Console or RAIDar v2 interface online help does not show internal IP addresses in use by the array.

· The profile for an initiator is not shown in the Storage Management Console.

· Initiator profiles cannot be set in the Storage Management Console.

· Unable to select SNMPv3 Privacy Type in locales other than English in the Storage Management Console.

· Text strings are truncated in some cases in the Storage Management Console when locales other than English are used.

· In non-English locales the Storage Management Console does not reflect the NTP enabled state when it has been enabled in the CLI.

· Snapshot schedules didn't begin until an MC restart, or schedules that had no associated tasks were deleted.

· The Storage Management Console or the RAIDar v2 interface might incorrectly display volume creation sizes with base 10 instead of base 2.

· In the RAIDar v2 interface, saving disk performance statistics might fail.

· Creating and scheduling a replication set command fails if a volume name contains a space.

· The global spares count may be incorrect on the Home page in Korean locale.

· SCVMM R2 may not accurately display available virtual pool capacity.

· In the Storage Management Console, SSD spares may not be displayed in the global spares information panel.

· Filter options are missing in the Event log viewer when a single event is listed in the viewer.

· Changes to email settings might show Include Logs as being enabled.

· Event logs show status of USB Drive that is not being used.

· Power Supply status shows OK when Fan is bad.

· Unable to set the partner controller IP address due to communication issue.

· A single controller configuration always indicates the chassis right ear fault LED is on.

· Power Supply SMI-S 314 Indication has WARNING severity.

· Controller crashed with NMI: NOCP Errors.

· An HTTPS web browser might not function correctly without a valid certificate. Certificate status is unknown.

· Controller crashed due to Critical Error OSMEnterDebugger CThr: mioL.

· Virtual disk-group drain stuck and will not complete.

· Invalid vdisks allowed for selection when creating a replication set in the RAIDar v2 interface.

· The Create snapshot command fails immediately after the execution of delete snap-shot with cleanup.

· Disk failure can cause data unavailability until a power cycle.

· Data is not draining from CRITICAL performance tier.

· Controller crash due to resources being exhausted.

· Host Port information popup does not show entire iSCSI initiator IQN.

· Virtual pool is read-only due to multiple failures and rare race condition.

· Rare management controller crash.

· MTU packet size not correctly documented.

· Controller crash due to PCI Link Recovery Stuck in a loop.

· The array was not working correctly in single controller mode.

· IE 11 browser can cause replication to fail when changing the scheduled replication.

· Cannot highlight or get hover tip for RAID-50 in the Storage Management Console.

· Text displayed for Hosts information is not clear in the Storage Management Console Home page.

· User session timeout is not displaying in the Storage Management Console.

· Event 8 Unknown Reason Drive failure does not create 314 event.

· Not sending an event and SNMP trap when available size is 0 MB.

· Drives that have failed previously due to SMART event should not be allowed to be added to a Vdisk or Disk Group.

· RAIDar v2 interface volume cache settings still contains Write Optimization.

· Creation of a performance tier disk group without a performance license generates Disk group offline event.

· Hard (non-media) errors reported during disk scrub due to illegal request command to disk.

· CompactFlash product ID does not include part number in notifications.

· Problems when using an HTML tag in the search text box on the Event Log Viewer.

· The Delete Volumes option is disabled for a snap of a snap.

· In the Storage Management Console or 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.

Installation instructions

The following sections discuss installing firmware:

· Installation notes and best practices

· Installing firmware using RAIDar or the Storage Management Console

· Installing firmware using FTP

· Installation troubleshooting

Installation notes and best practices

WARNING! Do not cycle power or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for 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.

Before installing this firmware:

· Create a backup of system data (a full backup is strongly recommended).

· Schedule an appropriate time to install the firmware:

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

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

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

During the installation process:

· Monitor the system display to determine update status and see when the update is complete.

After the installation process is complete and all systems have automatically restarted:

· Verify system status in the system's management utility, and confirm that the new firmware version is listed as installed.

· Review system event logs.

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

When reverting to a previous version of firmware:

· Ensure that both Ethernet connections are accessible before downgrading the firmware.

Installing firmware using RAIDar or the Storage Management Console

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

2. Locate the firmware file in the downloaded/extracted folder. The firmware filename is in the following format: GLxxxRyyy-zz.bin.

3. In single-domain environments, stop all I/O to vdisks in the enclosure before starting the firmware update.

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

5. Click Browse, and select the firmware file to install.

6. Click Install Controller-Module Firmware File.

7. Wait for the installation to complete. During installation, each updated module automatically restarts.

8. In the Storage Manager Console or RAIDar display, verify that the expected firmware version is installed on each module.

Installing firmware using FTP

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

2. Locate the firmware file in the downloaded/extracted folder. The firmware filename is in the following format: GLxxxRyyy-zz.bin.

3. Using RAIDar, prepare to use the FTP:

a. Determine the network-port IP addresses of system controllers.

b. Verify that the system FTP service is enabled.

c. Verify that the user login has permission to use the FTP interface and has manage access rights.

4. In single-domain environments, stop I/O to vdisks in the enclosure before starting the firmware update.

5. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory containing the firmware file to load.

a. Enter a command with the following syntax:

ftp <controller-network-address>. (For example: ftp 10.1.0.9)

b. Log in as an FTP user (user = ftp, password = !ftp).

c. Enter a command by using the following syntax:

put <firmware-file> flash

where <firmware-file> represents the binary firmware filename

6. Wait for the installation to complete. During installation, each updated module automatically restarts.

7. If needed, repeat these steps to load the firmware on additional modules.

8. Quit the FTP session.

9. Verify that the expected firmware version is installed on each module.

· In RAIDar, right-click the system in the Configuration View panel, and then select Tools > Update Firmware.

· In the Command Line Interface (CLI), execute the show version or the show enclosures command.

Installation troubleshooting

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

1. When viewing system version information in the RAIDar v2 interface's 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.

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

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

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

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

3. Verify that all system controllers are operating properly. For example, in the CLI, enter the show disks command, and read the display to confirm that the 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.

Known issues and workarounds

The following is a cumulative list of known issues and workarounds:

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: 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: 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: 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: 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: 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: 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 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: A very long user name will be partially hidden under the Sign Out button.

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: 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: 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: Firmware update status messages in the Storage Management Console or RAIDar v2 interface are not translated.

Workaround: None.

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: 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: In the Storage Management Console, Topics are not accessible on screen resolutions less than 1024x768.

Workaround: Use a resolution of 1024x768 or higher.

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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: The Browse button fails to open the file selection pop up in the license screen.

Workaround: Refresh the browser.

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: 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: 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: 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: 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: 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: 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:

1. Remove the uid_attribute ID_SERIAL entry in the defaults section if it exists.

2. Add the following to the defaults section:

getuid_callout /lib/udev/scsi_id --whitelisted --device=/dev/%n

3. Restart the multipath service.

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: 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:

Maximum IQN Character Length = (4083 / n) - 7 (Where n = number of hosts nodes explicitly mapped to a LUN on the array.)

NOTE: By specification, 223 is the maximum IQN length allowed.

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

Number of hosts explicitly mapped to a LUN and the maximum IQN character length		Number of hosts explicitly mapped to a LUN and the maximum IQN character length		Number of hosts explicitly mapped to a LUN and the maximum IQN character length
1-17	223	33	116	49	76
18	219	34	113	50	74
19	207	35	109	51	73
20	197	36	106	52	71
21	187	37	103	53	70
22	178	38	100	54	68
23	170	39	97	55	67
24	163	40	95	56	65
25	156	41	92	57	64
26	150	42	90	58	63
27	144	43	87	59	62
28	138	44	85	60	61
29	133	45	83	61	59
30	129	46	81	62	58
31	124	47	79	63	57
32	120	48	78	64	56

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

· Live values are calculated based on the vdisk as viewed from the controller cache perspective. In the live statistics, performance numbers are obtained by accounting when data is written from cache to disk or data is read from disk to cache.

· Historical data is obtained by using the summation of disk statistics for disks in the vdisk. The historical vdisk data shows transfers to and from the disks in the vdisk that include the overhead of any RAID transfers, as well as any host activity.

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: Global spares have a status of Up in RAIDar, even if they are spun down using the drive spin-down feature.

Workaround: None.

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

Supersedes history

Firmware version	AssuredSAN 3004, 4004, and 6004	Release date
G222P012	All	November 2016
G222R007	All	June 2016
G222R003	All	February 2016
GL210R006-08	All	August 2015
GL205R007	6004	April 2015
GL200P002	3004, 4004, 6004	March 2015
GL200R007	3004, 4004, 6004	December 2014
GL105P002-03	3004, 4004, 6004	July 2014
GL105P002-02	3004, 4004, 6004	June 2014
GL105R005	4004, 6004	April 2014
GL101R001	4004	November 2013

Effective date

September 2017