Appliance Release Notes v2.0.1

Last modified
<< PrevNext >>


Part no. -  765-0200-0000-B

Document attachment - Appliance v2.0.1 Release Notes

Thank you for purchasing StorSimple's Storage Appliance. This document provides release notes identifying open issues with the software version installed on your StorSimple Appliance. The document is broken into following sections:

Back to Top

New Features Introduced in Version 2.0.1

The following are the new features that have been included in version 2.0.1 (build 2.0.2-29).


Feature Name Description
Appliance Models 5020 and 7020

Appliance models 5020 and 7020 replace appliance models 5010 and 7010 via upgraded controllers. This action is mandatory to upgrade to v2.0 and free for all existing 5010 and 7010 customers. Local usable capacity, initial capacity license, and maximum capacity license remain the same in v2.0.

Industry-Leading Performance Extensive software and hardware optimization within the StorSimple appliance family improves performance by up to 50% compared to previous versions for both primary storage and backup.
Industry’s Most Robust Cloud Support StorSimple already has support for Microsoft Azure, Amazon S3, AT&T Synaptic, and EMC Atmos. The v2.0.1 introduces support for additional cloud providers such as Amazon S3 with Reduced Redundancy Storage (RRS), Rackspace, IIJ and Nifty. The v2.0.1 also allows you to specify the Amazon S3 region you wish to use for primary or backup data. Additionally, StorSimple now allows you to specify different cloud providers for primary and backup data.
Improved Monitoring This version provides improved monitoring granularity for capacity charts, hardware monitoring and backup statistics. Additionally, it supports SNMP v1/v2c with standard platform MIBs thus enabling integration into enterprise network monitoring tools.
Enterprise Manageability This version has enterprise-grade manageability features including integrated alerts, time-of-day QoS, network interface control, non-disruptive upgrade from v1.2 and online help and training videos.
Greater Security Integration StorSimple is introducing two new features Active Directory (AD) authentication and Secure web proxy support to help provide greater levels of security integration in customer networks.

Back to Top

Issues Resolved in Version 2.0.1

The following issues have been addressed in version 2.0.1 of StorSimple Appliance Software.


ID Summary
CSC-1335 While forcing multiple controller failovers in the system, one disk may be excluded from the active set. 
CSC-1371 In the Hardware Page, the "Enclosure Electronics Power" state of a controller is reported as "NOT AVAILABLE". 
CSC-1426 In the Hardware Page, the CPU and DIMM temperature sensors are reported as NOT PRESENT or FAILED. 
CSC-1538 In the Hardware Page, when the standby controller has been shut down or pulled out a different state is reported.
CSC-1644 In some rare circumstance, the appliance interfaces may not be usable. 
CSC-1738 The Web UI may not be accessible when the system encounters an error.
CSC-1740 The "Software Upgrade" page hangs after Upgrade, making the Web UI not accessible. This may also occur when pressing the "Restart Active Controller" or "Restart Appliance" buttons.
CSC-1919 Under very heavy iSCSI load, the controller may reboot.
CSC-1938 While forcing a continuous reboot of the active controller, access to the volume data could be lost permanently.
CSC-2090 Deleting a schedule policy which has a running job will cause such a job to get canceled.
CSC-2305 Changing Management IP address requires restart of active controller.
CSC-2495 A canceled or failed backup run will cause the snapshots and backup run to be left undeleted.
CSC-2568 The bytes read from the cloud may appear higher in the charts.
CSC-3144 The IP traffic is sent to a disconnected interface after a fail-over event.

Back to Top

Release Notes for Version 2.0.1

The following are the release notes for version 2.0.1 for the StorSimple Appliance Software.


ID Summary Comments and/or Workarounds
CSC-3238 Using invalid credentials for Web Proxy settings may result in a controller failover. If invalid credentials have been input in the Web Proxy Settings in Web UI, the active node will reboot and there will be a cluster failover. Ensure that valid credentials are applied for the Web Proxy settings.
CSC-3229 The controller date/time may not be updated during an upgrade process after the controller failover has occurred. After the upgrade is complete, ensure that the current time is displayed by navigating to Home Configure System Settings General Settings and verifying under Time Settings.
If the current time is not correct, click on the ‘Apply’ button under Time Settings and refresh the screen to see the correct time displayed.
CSC-3223 Web UI does not support Compatibility mode with IE 8 /IE 9. The Web UI does not work properly when compatibility mode is enabled with IE 8/IE 9. All pop-ups are non-functional and grayed out. Icons for Help and Video may disappear. Online Help Site does not work properly. The workaround is to disable the compatibility mode.
CSC-3206 Web UI Operations that take extended periods of time to complete such as creating a package, downloading or displaying reports, may prevent accessing the Web UI until the operation is complete. Wait for the operation to complete before accessing the Web UI from a different browser tab window.
CSC-3198 Web UI may render incorrectly on a restarted appliance. Accessing the Web UI on a new browser window will resolve the issue.
CSC-3196 A canceled Cloud Clone or Cloud Snapshot restore/clone job may resume after a controller failover.

If the user cancels the restore/clone job, and then triggers a controller fail-over or the system fails over automatically for some other reason, then a canceled job will resume unless the cancel action has been completely processed by the system.
To work-around this issue, the user needs to cancel the job again and ensure no more fail-overs are triggered until the cancel action has been fully processed by the system.

CSC-3180 Under rare circumstances a disk failure may cause the system to go offline. There are some corner case scenarios that may occur with a high stress read workload. When the StorSimple software detects a failure in a drive from which it cannot quickly and easily recover from, it intentionally brings down the system in order to protect the data integrity. Should such an event occur, please contact StorSimple support to address the issue and restore its full functionality.
CSC-3174 Restoring a backup fails with error "Multiple appliance volumes with specified VSN are online". This error can occur if a previous attempt to restore a backup against the same volume group also failed and the failure code displayed begins with "BE_BACKUP_RUN_RESTORE". The previous failure creates a temporary volume that must be removed before the volume group can be restored successfully.
As a workaround, use the Volumes page to locate and delete the temporary volume created by the previous restore failure. The name of the correct temporary volume will begin with the name of the volume being restored, followed by two timestamps. For example, if the name of the volume being restored is "SharePointBlobs", the name of the temporary volume will be "SharePointBlobs-S-[timestamp1]-CC-[timestamp2]", where timestamp1 and timestamp2 are 10-digit numbers in the form YYMMDDHHmm.
CSC-3169 A different state may be displayed on the serial console when the system is in recovery mode. In earlier releases, in the case of repeated controller fail-overs, the serial console on both controllers displayed the recovery console screen.
In this release, one controller may instead continue to display the management console screen, with the state shown as "OFFLINE".
CSC-3154 If one of the Web UI charts is kept open in Auto-refresh mode, the refresh may stop after some time. Normally this issue can be overcome by opening a new browser session and select the same chart display page again with Auto-refresh mode.
If the Web application fails to open, i.e. the login page does not come up; the issue can be worked around by forcing an active controller reboot.
CSC-3086 A controller may reboot or become unresponsive when the system is under extreme IO load. Under rare circumstances, and when an extreme load is applied to the system for a long duration of time, the controller may reboot or become unresponsive. In case the controller reboots, the applications should not observe any disruption as the system will ensure an automatic fail over. If the controller becomes unresponsive, please contact StorSimple support to restore full system functionality in a most effective manner.
CSC-3042, CSC-3067 The StorSimple Appliance controller reboots when an I/O to the internal disks takes an abnormally long time to complete.

Under extremely rare circumstances, an I/O to a drive (SSD or HDD) may take an abnormally long time. The StorSimple software detects such an incomplete operation and forces a controller fail over to ensure that the system can continue serving I/Os without causing application timeouts. StorSimple will provide any necessary fix through a software patch, nonetheless should an unforeseen hardware glitch occur such a fail over is the best course of action.

CSC-3029 The StorSimple appliance controller may decide to reboot or power off because it cannot monitor the battery status. The internal communication channel used by the controllers to monitor the health and status of the batteries that provide NVRAM support may become oversubscribed. As a result, the polling status messages could be lost. If this happens a few times in a row, then the controller will reboot or power off to prevent having a system running without the necessary memory protection. This issue occurs only when the communication channel is put under severe stress.
CSC-2896 Different rate limiting values on multiple cloud configurations are not honored. When multiple cloud configurations are setup and rate limiting is enabled in more than one, the overall throughput towards the cloud will converge over time to the smallest rate limiting value configured (as opposed to the sum of the configured rates).
CSC-2826 The Cloud Capacity chart as well as other cloud charts are not displayed for a specific cloud configuration. These charts can be displayed only if the "Enable Monitoring" checkbox has been checked for a specific cloud configuration. Please enable it and try again.
CSC-2593 An existing iSCSI session remains active even after disabling the iSCSI checkbox in the UI.

The "iSCSI Enabled" setting is effective only after a controller reboot/failover. The existing sessions are not altered, therefore:
• Existing iSCSI sessions from hosts remain active after disabling the checkbox
• New iSCSI sessions to a target are successful using the IP address of the interface which is unmarked as "iSCSI Enabled"
In order to overcome this issue, please reboot the active controller.  The automatic failover will ensure that the desired configuration is applied correctly from that point onwards.

CSC-2573 Active Directory domain user is able to login with old password after the password is changed in the domain. This is due to the old password being cached by the Domain Controller server that has been configured. This password remains available when authentication occurs. Since the StorSimple application cannot force a flush of the old passwords, please connect to the Domain Controller server and perform the necessary flush operation.
CSC-2381 Creating a new Volume Access Group using Mozilla Firefox might report a "Name already in use" error. Refresh the screen and verify that the newly created Volume Access Group already exists.
CSC-2335 Using the 'Printer friendly version" link in Firefox for the charts will result in a printed page with an empty white area instead of the chart. This issue is due to a Firefox limitation that doesn't render the content of the HTML "object" element during printing.

In order to overcome this limitation, please use a supported IE version to print charts.

CSC-2321 Performing a configuration restore from a saved xml file on an appliance that has a different Management IP than the one saved in the configuration file, may result in a "No Route to host" error on the Audit Logs screen. A controller failover would solve the issue.
CSC-2317 The ACG maps are lost when performing a configuration restore twice. This issue occurs when:
1. A DR configuration restore is performed from a previously created configuration file (e.g. config1.xml)
2. A new configuration file is created after the appliance is working again (e.g. config2.xml)
3. A new DR configuration restore is performed using the new configuration file (config2.xml)
In order to work around this issue, the user could selectively import the ACGs from the original configuration file (config1.xml) or brand new ACGs could be configured after the second configuration restore.
CSC-2300 When a configuration restore/import fails, the same cloud account may be configured multiple times. Upon configuration restore or import failures, in few rare circumstances some portions of the configuration are restored/imported. In case the restore or import operation is repeated again, the same cloud account might be configured multiple times. In order to work around this issue, please check the configuration after the failure and delete any partially imported information, especially the cloud account portion.
CSC-2255 Microsoft MPIO doesn't work as expected when defaults are altered. It is recommended to use default MPIO parameters for Microsoft MPIO DSM on a Windows host. To find the current parameters, traverse through Computer Manage Disk Management Disk x Properties MPIO tab Details (where "Disk x" is any of the StorSimple disks discovered by the host).
The default parameters are:
  Path Verify Period = 30
  Retry Count = 3
  PDO Remove Period = 20
  Retry Interval = 1
  Path Verify Enabled = Unchecked
Note: to enable MPIO on StorSimple volumes, add the "SSIMPLE Model" keyword in MPIO properties (Control Panel Administrative Tools MPIO).
CSC-1677 Configuring a single data port that is not plugged in will result in error messages such as, 'Invalid Hostname' or 'Invalid Credentials', when verifying a Cloud Account. In case of these error messages first check the validity of the credentials entered for Cloud Account. If valid, please verify on the Network Settings screen that the Data port configured is plugged in or configure and enable another data port that is plugged in. Once done with the Network Settings, reapply the Time Setting located on the same System Settings screen.
CSC-1644 In some rare circumstance, the appliance network interfaces may not be usable. While performing platform discovery, it has been seen in rare occasions that the MGMT and DATA interfaces are not detected properly during the power up sequence. Under such scenarios the Web UI and the iSCSI ports are not reachable. To restore the proper functionality in the appliance, reboot the appliance.
CSC-1549 Multiple failovers performed under heavy load may result in loss of iSCSI connection between the host and the appliance. Under heavy I/O, if there are failovers performed there is possibility of active controller reboot. This may result in loss of iSCSI connection between initiator and target. In order to restore the proper connectivity, reboot the appliance.
CSC-1538 In the Hardware Page the standby controller appears in a different state when it has been shut down or pulled out. This is a known issue in the underlying platform code that will be fixed in a future release. There are no negative side effects on the system behavior.
CSC-1492 The controller failover may exceed the application timeout. Under certain failure scenarios, the failover to the standby controller may take longer than the application SCSI timeout. This is a sporadic event. Once the failover has occurred, normally the application will automatically re-establish the connection and continue operations. If that doesn't happen automatically, restart the application or the connection manually.
CSC-1334 Under stress testing of the system failover, the host may lose access to the appliance volumes. When performing stress testing of the system failover, inducing continuous failures (artificially), a Windows host may lose access to the volumes. StorSimple is actively working with Microsoft to analyze the issue which may be a problem on the host side. In order to restore the volume access, please force an iSCSI rediscovery of the target or power cycle the host.
CSC-867 Microsoft iSCSI initiator doesn't support LUN ID 255. Use a LUN ID of 0 to 254.

Back to Top

Contacting Technical Support

Should you encounter any issues with your StorSimple Appliance Software, please do not hesitate to contact StorSimple Technical Support at:

Please contact StorSimple technical support to create your support account to allow access to product documentation and other resources including software images, technical reports, release notes, and other collateral using StorSimple’s File Transfer Protocol (FTP) server at:

Back to Top


Page statistics
1288 view(s) and 22 edit(s)
Social share
Share this page?


This page has no custom tags.
This page has no classifications.