The storage space has been a very exciting space over recent years. There have been so many new start-ups and new innovations, that it becomes difficult to keep track sometimes. More recently, there has been a lot of news around mergers, acquisitions and IPOs in the storage industry. It got me thinking about a lot of the changes we have seen over the past 3-4 years in the storage market. Just for my own interest, I went back over many of my blogs, and the various conversations I had with people at various VMworld events and VMUG meetings, and tried to see where a lot of these companies/products are now, and what they are currently doing. Now, I am not going to mention every single vendor here. I’m simply trying to highlight the ones that were acquired or merged or indeed IPO’ed (and in some cases are no longer with us) during this period.
There was a recent discussion on the forums around the supportability of quad port NICs when deploying the vSphere Storage Appliance. There is an error thrown by the installer when the ESXi host only has a quad port NIC. The error states that the VSA installer ‘Failed to configure network on host’ because it ‘Could not find 2 NICs on the system’. However there is a workaround to allow VSA to install when the ESXi host(s) only contain a single quad port NIC. This is only available on VSA 5.1.x.
I’ve been working with my colleague, Rawlinson Rivera, on documenting a few features around VSA deployments. Rawlinson is currently working on a new feature of VSA 5.1 called brownfield install, which basically allows you to deploy the VSA when you already have VMs running on your ESXi hosts.
I was asked recently to provide some assistance with a VSA installation problem. The issue which this person experienced is described in the release notes for VSA 5.1.1 .
VSA 5.1.1 installation fails with the Error 2896: Executing action failed message
This problem might occur when the location of the temp drive is set to a drive other than C:, where VSA Manager is to be installed.
Workaround: Make sure that the user and system TEMP and TMP variables point to a specified location on the C: drive.
Some changes have been made to the vSphere Storage Appliance (VSA) Cluster Service in version 5.1. Previously, the VSA Cluster Service was installed on the vCenter Server – there was no way to decouple it. However in VSA 5.1, the VSA Cluster Service is a stand-alone entity. It can still be deployed on the vCenter server, but it can also be deployed outside of it.
For those of you who are already using VSA 1.0, and are considering an upgrade to VSA 5.1, the following information will be of interest to you.