Sunday, May 19, 2013

No SAN ... No Problem! VMware VSA @ work


VMware has announced vSphere Storage Appliance for more than a year now. For whatever reason you might not have looked at the product, this post is to make a point that VSA is a great product; works well and in its latest iteration it has addressed a lot of the shortcomings of the previous releases.

Let's take a look at what the product is targeted at. It is a really good fit for SMB where getting even an entry level SAN is cost prohibitive. The architecture of a VSA cluster includes the physical servers that have local hard disks, ESXi as the operating system of the physical servers, and the vSphere Storage Appliance virtual machines that run clustering services to create volumes that are exported as the VSA datastores via NFS.

Benefits:     
  • No SAN needed
  • Simple to implement
  • Low Cost
  • Licensed with vSphere Essentials Plus Kit
  • Can add disks to expand the capacity of cluster (ver. 5 feature)
  • Can be deployed in brownfield or greenfield implementation (brownfield ver. 5 feature)

Shortcomings:
  • Comes in a two node and three node (hosts) version only
  • Once implemented you cannot add  a node (host) to add compute at future date
  • Needs a physical box for vCenter to hold the quorum in a two node deployment

There is a very good evaluation guide written by Cormac Hogan. Rawlinson Rivera has done some commendable work over here explaining details surrounding brownfield deployments. This would be very helpful for people who already have existing VMs in the environment on individual hosts.

In summary, you get all the enterprise level features (vMotion and High Availability) at a relatively low cost. Moreover no SAN and SAN management skills needed.

Sunday, May 12, 2013

Network Performance Throughput Testing in Virtualized or Physical Environments using iperf


Dropped packets should not occur on any network because they typically indicate congestion in the network or an issue possibly with hardware. One percent dropped packets in either direction can significantly throttle overall throughput.

Dropped packets in vSphere can be monitored by selecting the ESXi host and clicking the Performance tab. Select Advanced > Network > Real Time, and select None in Counters. Select Receive packets dropped and Transmit packets dropped.

Iperf is a network testing tool that can create a TCP or UDP data stream between two virtual or physical nodes. Iperf is open source software available for both Linux and Windows at http://sourceforge.net/projects/iperf/.

To test the maximum throughput of the network interfaces for 200 seconds:

On the server node, execute the following command:

$ iperf -s -i 5

On the client node, execute the following command:

$ iperf -c <server-name> -t 200 -i 5 –m

During one of my future posts I will be posting the demo of the utility in action in a VMware ESXi environment.

Saturday, May 11, 2013

vCenter Single Sign-On failure after changing SQL Server port

Working on one of the systems recently on which SQL Express was installed locally on the same VM as vCenter (hence the default SQL port was dynamic), I had to create a database for another application for a remote system and in order for the communication to happen, I changed the dynamic SQL Server port to the standard 1433.

Guess what? After the change, the single sign-on service would refuse to start. Upon research, I was taken to a VMware KB 2033516. The explanation and some screenshots based on the KB are depicted below.

Step 1. Modify the SSO Setting.




Step 2. Make the port modification in the config file.







Step 3. That's it. Restart SSO and vCenter Service and you are back in business.

Please note that the password values and hostnames are cleared from the config file screenshots.