StorSimple System Requirements

Last modified

Part no. - 760-0015-0001-C

Last Updated: 12/19/2014

Overview

StorSimple’s 5000 and 7000 series are industry-leading cloud integrated enterprise storage systems.  This document outlines the software, high availability and networking requirements for your StorSimple solution.

The software requirements are for accessing StorSimple Web UI and for the storage clients accessing the StorSimple system. The high availability requirements are for your StorSimple storage system.

 

Software Requirements for StorSimple Web UI

The following table lists the software requirements such as supported browsers for accessing StorSimple Web UI.

 

Supported Browsers Version Requirements Details/Notes
Internet Explorer  v8, v9, v10 Ensure that the latest updates are installed for these versions.
Chrome

v34.0.1847.131 m or higher*

Ensure that the latest updates are installed for these versions.
FireFox v29 or higher Ensure that the latest updates are installed for these versions.

 

* Chrome version 42 or higher does not support NPAPI, which is required to provide Silverlight functionality. (The StorSimple Web UI uses the Microsoft Silverlight plug-in.) You can temporarily enable NPAPI and restore Silverlight functionality by following these steps:

  1. Open the Chrome browser.
  2. Enter this URL in the address bar: chrome://flags/#enable-npapi

    You will see the following entry in the resulting page:

    Enable NPAPI Mac, Windows
    Enables the use of NPAPI plugins. #enable-npapi
    Enable

  3. Click the underlined Enable link.

  4. Click the Relaunch Now button at the bottom of the Settings page.
    The Google Chrome browser will restart, and NPAPI and Silverlight will be enabled.

NOTE: In September 2015, NPAPI support will be permanently disabled in Chrome, and this workaround will no longer be available.

UpArrow.png

Software Requirements for Storage Clients

The following compatibility matrix lists software requirements for the storage clients accessing your StorSimple system.

 

Supported Operating System Version Requirements Details/Notes
Windows Server 2008 R2 SP1, 2012, 2012 R2 1. StorSimple iSCSI volumes are supported only for use in the following Windows disk types:
  • Simple volume on Basic Disk
  • Simple and mirrored volumes on Dynamic Disk

Use of SSDPC on Windows Server is required for backup/restore of Mirrored Dynamic Disks, and for any application-consistent backups.

2. SSDPC is only supported on Windows Server 2008 R2 SP1, Windows Server 2012 and 2012 R2. If using Window Server 2012 or 2012 R2, .NET 3.5 will need to be installed prior to SSDPC installation.

3. Windows Server 2012 Thin-provisioning and ODX features are supported when using a StorSimple iSCSI volume. The support is applicable for versions 2.1.1.386 or higher.

  • Performance Note: Reformatting a thin-provisioned volume may take a long time. It is recommended to delete the volume and create a new one instead of reformatting. If you still prefer to reformat a volume, apply the following command prior to the reformat to avoid space reclamation delays:

fsutil behavior set disabledeletenotify 1

Once the formatting is complete, apply the following command to re-enable space reclamation:

fsutil behavior set disabledeletenotify 0

  • Apply the Windows Server 2012 hotfix as described in KB2870270 to your Windows Server machine.

4. SSDO is only supported on Sharepoint 2010 and Sharepoint 2013. RBS requires SQL Server Enterprise Edition, version 2008 R2 and 2012.
 

Linux  SUSE Linux 11  
VMWare 4.1, 5.0, 5.1 VAAI-Block feature supported with VMware vSphere v5.1 on StorSimple systems with software version 2.1.1.341 or higher
RHEL/CentOS v5.x, v6.x, v6.5 Supported with Open-iSCSI initiator only

UpArrow.png

Networking Requirements for Your StorSimple System

This following table lists the ports that need to be opened on your StorSimple appliance including the inbound and the outbound ports. In this table, inbound refers to the direction from which incoming client requests, access your appliance. Outbound refers to the direction in which your StorSimple appliance sends data externally, beyond the deployment: for example, outbound to the Internet.

Important: It is essential that you use a dedicated 20 Mbps (or higher) internet connection for your StorSimple system. Sporadic or unreliable internet connection to the appliances including no internet connectivity altogether will result in an unsupported configuration.

 

Network Ports Used By Your StorSimple System
Port Scope1,4 Management (LAN) Cloud Access (Internet) iSCSI (SAN)
HTTP2,3 TCP: 80 inbound TCP: 80 outbound  
HTTPS3 TCP: 443 inbound TCP: 443 outbound  
SSH​2 TCP: 22 inbound    
DNS UDP: 53 outbound UDP: 53 outbound  
NTP UDP: 123 outbound UDP: 123 outbound  
iSCSI     TCP: 3260 inbound
LDAP​2 TCP: 389 outbound    
DPC     TCP: 7879 inbound
SMTP2 TCP: 25 outbound configurable    
SNMP2 UDP: 161 inbound UDP: 162 outbound  
1 - Port Scope reflects network being accessed (LAN, SAN, Internet). The system does not have any inbound ports that need to be open on public internet.
2 - Optional
3 - Outbound web proxy port configurable
4 - Multiple ports carry a gateway configuration, outbound routed traffic order will be: MGMT, DATA1, DATA2, DATA3

UpArrow.png

High Availability Requirements for Your StorSimple System

The hardware platform that is included with the StorSimple solution has enterprise-grade availability and reliability features that provide a foundation for a highly-available, fault-tolerant storage infrastructure in your data center.  This section outlines information that must be considered to ensure the high availability of your StorSimple system. 

Failure to follow the requirements and procedures listed here could lead to the disruption of service or loss of data.

 

Component Requirements and Procedures
Power and Cooling Modules (PCMs) Appliances include redundant, hot-swappable PCMs.  Each PCM has enough capacity to provide service for the entire chassis.  Both PCMs must be installed to ensure high availability.
  • Connect PCMs to different power sources to provide availability should a power source fail
  • Should a PCM fail, request a replacement immediately
  • Remove a failed PCM only when you have the replacement and are ready to replace it 
  • Do not remove both PCMs concurrently. The PCM module includes the battery and hence removing both the PCMs will result in no battery protected shutdown
Controller Modules Appliances include redundant, hot-swappable controller modules.  StorSimple controller modules operate in an active/passive manner.  At any given time, one controller module is ‘active’ and providing service, whereas the other controller module is ‘standby'.  The ‘standby' controller module is powered on and becomes operational in the event of a failure or removal of the ‘active’ controller module.  Each controller module has enough capacity to provide service for the entire chassis.  Both controller modules must be installed to ensure high availability.
  • Ensure both controller modules are installed at all times
  • Should a controller module fail, request a replacement immediately
  • Remove a failed controller module only when you have the replacement and are ready to replace it
  • Ensure that the network connections to both controller modules are identical, and the connected network interfaces have an identical network configuration
  • Should a controller module fail or need replacement, ensure that the other controller module is in an ‘active’ state prior to replacing the failed controller module
  • Do not remove both controller modules concurrently
  • Should a controller failover be in progress, do not shutdown the standby controller module or remove it from the chassis
  • After a controller failover, wait at least five minutes before removing either controller module
Network Interfaces Appliance controller modules each have four Gigabit Ethernet network interfaces.  Three of these interfaces are labeled ‘DATA’ (for iSCSI and cloud access), and one interface is labeled ‘MGMT’ (for management).
  • Ensure that the network connections to both controller modules are identical, and the network interfaces the controller module interfaces are connected to have an identical network configuration
  • Deploy network connections across different switches when possible to ensure service availability in the event of a network device failure
  • Connect at least two DATA interfaces to the network from each controller module
  • Use MPIO on servers when possible to ensure servers can tolerate a link, network, or interface failure
  • It is mandatory for network cables to be connected to the switch from both the controllers. A configuration where network connectivity to switch is done to only one controller and the other controller is left un-connected, is not supported. 
SSDs and HDDs Appliances include solid state disks (SSDs) and hard disk drives (HDDs) that are RAID-protected using RAID-10, and a hot-spare is provided for the HDDs. Use of RAID-10 ensures that the appliance is able to tolerate the failure of one or more SSDs and HDDs.
  • Ensure that all SSD and HDD modules are installed
  • Should an SSD or HDD fail, request a replacement immediately
  • Should an SSD or HDD fail or require replacement, ensure that you only remove the SSD or HDD that requires replacement
  • Do not remove more than one SSD or HDD from the system at any point in time
  • During replacement, monitor the Hardware page in Web UI to get the status of SSDs and HDDs. A green status indicates that the disks are healthy, a yellow indicates they are recovering whereas red refers to a failed SSD or HDD. Do not  remove any SSD or HDD until there is an indication that the disks and the array are healthy
  • A failure of 2 or more disks of certain type (HDD, SSD) or consecutive failure within a short time frame may result in system malfunction and potential data loss. In such an event, contact technical support for assistance. It is also recommended that you configure Cloud Snapshots for all volumes which you need to protect in case of a system failure
EBOD Enclosure

Appliance model 7520 includes an EBOD Enclosure in addition to the head unit. These EBOD consists of EBOD enclosure controller modules and hard disk drives (HDDs) that are RAID-protected using RAID-10, and include a hot-spare for the HDDs. Use of RAID-10 ensures that the appliance is able to tolerate the failure of one or more HDDs. The EBOD enclosure is connected to the appliance unit through two redundant SAS cables.

  • Ensure that both EBOD enclosure controller modules, both SAS cables and all the hard disk drives are installed at all times
  • Should an EBOD enclosure controller module or a HDD fail, request a replacement immediately
  • Should an EBOD enclosure controller module fail, ensure that the other controller module is in 'active' state prior to its replacement
  • Should a HDD fail or require replacement, ensure that you only remove the HDD that requires replacement. Do not  remove a HDD until there is an indication that the disks and the array are healthy
  • Do not remove more than one HDD from the system at any point in time
  • During EBOD controller module or a HDD replacement, continuously monitor the status of the relevant component in the Web UI by accessing Manage Hardware
  • Should a SAS cable fail or require replacement (StorSimple support should be involved to make such a determination), ensure that you only remove the SAS cable that requires replacement
  • Do not remove both SAS cables concurrently from the system at any point in time

UpArrow.png

Page statistics
5334 view(s) and 18 edit(s)
Social share
Share this page?

Tags

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

Comments

You must to post a comment.

Attachments