Appliance Patch Release Notes v2.0.1 (2.0.2-84)

Last modified


Part no. - SS-Patch-2.0.1 (2.0.2-84)

Document attachment - Pdf format

Thank you for purchasing StorSimple’s Storage Appliance. This document addresses the issues resolved in the patch release for v2.0.1 (2.0.2-84).  The document is broken down into following sections:

Back to Top

Issues Resolved in v2.0.1 (2.0.2-84)

The following issues have been addressed in version 2.0.1 (2.0.2–84).





Setting up a proxy may result in system failovers.

Back to Top

Release Notes for v2.0.1 (2.0.2-84)

The following are the release notes for version 2.0.1 (2.0.2-84) for the StorSimple Storage Appliance. There are no issues reported in this specific version.  All the issues reported here have carried over from previous releases.




Comments and/or Workarounds


Web UI has issues when viewed in compatibility mode.

The compatibility mode needs to be disabled on a per-site basis when viewing the Web UI in IE.

This can be done by accessing Tools  Compatibility View and ensuring that the compatibility view is disabled. 

If you are in Local Intranet Zone, the compatibility mode needs to be disabled for the zone as a whole. This can be done by accessing Tools Compatibility View Settings and unchecking the 'Display Intranet Sites in Compatibility View' option. The user may need to clear the browser cache for the settings to take effect.

Note that disabling the compatibility mode for the entire zone could impact other internal websites that rely on the compatibility mode. This issue is slated for the next major software release.


Data protection monthly schedules configured in the Web UI are saved a day in advance of the configured one.



The issue is caused by an incorrect computation of the time zone offset from UTC. As a work-around, please setup the appliance to use UTC instead of the local time zone when configuring the data protection policies. The issue will be addressed in the next software release.
CSC-3391 10GigE interfaces may not be detected when the system is powered up.

As a work-around, reboot the active controller; the interfaces should be detected properly on the controller taking over the active role.

CSC-3390 When the StorSimple appliance is powered off and quickly powered on, some drives show up as missing.  This issue has been observed very sporadically when forcing a quick power off/on through a managed APC that would cut the power to the appliance for less than 1 second.
As a work-around, please ensure that the power is applied again a few seconds after the power-off (what is usually called a "delayed power-on" in a managed APC).
CSC-3381 Web UI becomes unresponsive when the standby controller is pulled out. As a work-around, please retry accessing Web UI after about 10 minutes.  The UI interface should be available again.
CSC-3360 When shutting down the active controller, the standby is shutdown as well. This happens in very sporadic situations due to a known platform issue. If this happens, bring up the standby controller by unplugging it and pushing it back into the system.
CSC-3358 A "Call Home" email is sent daily to StorSimple if the user selects "BCC StorSimple Support" for Alerts. The "Call Home" email should be sent only if the user explicitly selects the "Include usage statistics" in the Alerts page.
CSC- 3296 Cloud Snapshot Data in Dedup Ratio Chart is not calculated accurately. Cloud Snapshot capacity is estimated based on the number of Cloud Snapshot and the current amount of volume data stored in the appliance.
CSC-3282 Appliance failover is observed when the data read from the cloud is incorrect due to transient network issues. This known issue is being actively investigated in conjunction with the cloud providers. The StorSimple system is able to detect and recover from such a situation by performing a failover and never returns any incorrect data to the iSCSI initiator.
CSC-3253 In rare instances, on resetting the active controller, the Host I/Os may get aborted. In some high load scenarios, host I/Os are aborted because the appliance takes more than 20 seconds before completing the operation. The issue subsides after the load reduces.
As a workaround, a reduction in host load, and/or a failover of the controller is recommended.
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- 3224 In Firefox 3, while configuring QoS templates, the Save/View Timeline buttons may get disabled. This issue can be observed only in some specific sequences of operations involving deleting and creating multiple QoS templates. The issue can be overcome by refreshing the browser page and then attempting the configuration of the QoS template again.
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.


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


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- 3152 Any shutdown or restart operation on the active controller may cause the session to get stuck on the login screen. Refresh the screen and try to login again.
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.

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


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.


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.

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.

Microsoft iSCSI initiator doesn't support LUN ID 255.

Use a LUN ID of 0 to 254.


Back to Top

Contacting Technical Support

Please contact StorSimple technical support to create your support account, which will allow you 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:

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

Back to Top

Page statistics
649 view(s) and 13 edit(s)
Social share
Share this page?


This page has no classifications.