Note that the StorSimple OVA model 1200 is incompatible with the StorSimple 8k series physical and virtual devices (8100, 8600, 8010, 8020). This means we cannot recover volumes from 8k device to a 1200 OVA device or vice versa.
1. Deploy ‘Virtual Device Series’ StorSimple Manager:
You cannot deploy an OVA under your ‘Physical Device Series’ StorSimple Manager service. To deploy a ‘Virtual Device Series’ StorSimple Manager follow these steps in the classic portal:
Uncheck the box at the bottom to create a Storage Account.
Note that OVA is available on the following Azure regions as of 20 October 2016:
- Australia East
- Australia Southeast
- Brazil South
- East Asia
- Southeast Asia
- East US
- West US
- Japan East
- Japan West
- North Europe
- West Europe
Enter a name for your StorSimple Manager service.
2. Create a Storage Account
I prefer to manually create a Storage Account instead of having one created automatically, to be able to give it a name that makes sense for the deployment, and becomes easy to identify and recognize later on.
Make sure the Storage Account is in the same Azure region as the StorSimple Manager service.
3. Download the OVA image file
Under the new StorSimple Manager service/devices/create virtual device:
You’ll see a page like:
Click the link under item #1 that corresponds to your hypervisor to download the OVA file. Copy the Registration Key at the bottom. It will be used later in step x to register the OVA with the StorSimple Manager service.
Extract the .ZIP file
4. Provision a VM for the OVA:
I’m using Hyper-V on Server 2012 R2 in this example. Minimum VM specs: 4 cores, 8 GB of RAM, 500 GB disk space for drive c: (system disk).
Gen 2 is supported and recommended when using VHDX image on Server 2012 R2
According to Microsoft, dynamic memory is not supported 😦
Connect to the Hyper-V switch of your choice. Use the downloaded disk:
Click Next and Finish. Go back the VM settings/Processor, and select to use 4 cores:
Add a second disk to the VM under the SCSI controller. Set it as 500 GB dynamically expanding disk.
Start the VM and login to it. This takes several minutes. The default user is StorSimpleAdmin and the default password is Password1. Login and change the password (8 character minimum). The OVA image has a Core version of Server 2012 R2, and if DHCP server is available it picks up an IP address:
An extremely limited set of commands is available:
However, Microsoft has made the support mode available without the need for a decryption tool:
This exposes the entire PowerShell capabilities for admins to manage the device.
This is really a good decision on Microsoft’s part. The current local web interface has many idiosyncrasies that can be frustrating for a device admin. Having the option to manage the device via PowerShell goes a long way towards faster device adoption and customer satisfaction in my opinion and experience.
Although not required, I recommend using a static MAC address for the OVA VM. To do so shut down the VM from Hyper-V Manager, then under settings\network\advanced, select static MAC:
Start the VM.
5. Configure the OVA via the local web interface
Browse to the OVA IP address, and bypass the local certificate warning in the browser. Login with the new password you created in the prior step.
Under configuration/network settings, I recommend using a static IPv4 address
- By default, the OVA will attempt to get IP address if there’s DHCP server in the environment.
- To view/change the IP address configuration in the local web interface, if you try to change the DNS server IP it will error out. A work around is to change it back to DHCP, apply, browse to the DHCP IP, login, change it back to static IP and make all the needed changes in one step. In other words, you must change IP address and DNS server address in one step or it fails to accept the changes’
- There’s no way to remove IPv6 information in the local web interface
Browse to the new IP address to continue. For this post I’m using the device as an iSCSI SAN. I settled on leaving the device in ‘workgroup’:
I was unable to join an on-premises AD domain:
and entered credentials as:
But got the error message “Domain does not exist”!!??
I attempted to use the NetBIOS names (sam1 domain and sam1\administrator user) but got the same error.
I verified connectivity between the DC and the OVA, running these commands on the DC:
I also verified that the DC is responding to DNS queries. I ran the following command from a 3rd computer:
I skipped Proxy settings, since I’m not using a proxy to get to the Internet in this environment.
Interestingly enough, Time Server settings accepted the local DC with no problem:
Finally, I registered the device with the StorSimple Manager Service by entering the Service Registration Key. This was my first device on this StorSimple Manager Service, so I recorded the Service Data Encryption Key received upon successful registration.
- If this is not the first device to be registered with this StorSimple Manager service, you’ll need the Service Data Encryption Key as well to be able to register the device
- You must have 3 green check marks at the Network, Device, and Time settings to be able to register the device under Cloud setting
6. Complete OVA configuration in Azure
In the classic portal (24 October 2016), click on your StorSimple Manager Service/Devices link and you should see the newly registered OVA
Click on that and click Complete Device Configuration
In the next screen, select a Storage Account. I recommend checking the box to Enable Cloud Storage Encryption, and entering a 32 character seed for at-rest encryption of data blocks that the device sends to the Azure Storage Account:
StorSimple Manager Services completes the following tasks: