Deploying the VMware I/O Analyzer Fling

VMware I/O Analyzer is a virtual appliance designed to provide storage performance in a virtual environment. It is offered as a SUSE appliance that provides a web GUI to interact with.

I deployed I/O Analyzer in my vSphere 6.0 environment to see the performance of VSAN 6 compared to my Synology NAS. With this post you should be able to deploy I/O Analyzer in its simplest form and perform performance testing on your storage.

Read more…

My Summary of VMworld 2015!

Whew! What a week VMworld 2015 was! I am now getting back into the groove since coming back home from VMworld 2015 in San Francisco, CA. This was my first year attending VMworld and I had a blast! I took quite a few pictures and wanted to make a quick post about my experience at VMworld 2015.

I can see why the Moscone Center was picked as the location as it is quite large to accommodate the over 23,000 attendees!

VMworld 2015 - Moscone West in San Francisco

Read more…

VMware Virtual SAN 6 – Requirements [Part 1]

VMware Virtual SAN (VSAN) is a hypervisor-converged storage solution for your vSphere environment. It was built to be extremely easy to use and administrator, high performance and expandable. In this post I will go over the requirements and how to prepare your environment for VSAN.

vBoring VSAN Series:

VMware VSAN Diagram

VSAN Requirements:

Here are the minimum requirements to build out a VSAN environment.

Refer to VMware KB article 2106708 for an in depth breakdown of all requirements.

  • Minimum of 3 ESXi 6.0 host that contribute storage
  • At least one SSD and one Hard Disk per host
  • Hosts need I/O controller supporting Pass Through or RAID 0 (prefer them to be on the VSAN Hardware Compatibility List)
  • VMkernel port configured for VSAN traffic
  • 1 GB network for small test/lab environment (VMware recommends 10GB)
  • If you are deploying VSAN in your test/dev/lab and the 60 day evaluation period isn’t enough check out the VMUG Advantage subscription for a 1 year license.

Read more…

Add Virtual Machine Templates (.VMTX) to Inventory using PowerShell

Here is a script that will scan a datastore for VM templates (.VMTX) and add them to inventory. This is a modified version of the Add Virtual Machines (.VMX) to Inventory script.

You must have VMware PowerCLI installed in order to have the cmdlets required for PowerShell to run the script.

Add VMTX (Virtual Machine Templates) to Inventory from a Datastore:

#####################################################################
# Load VMware Plugins and vCenter Connect #
#####################################################################

Add-PSSnapin vmware.vimautomation.core

connect-viserver -server ENTER VCENTER FQDN HERE
#####################################################################
# Add .VMTX (VM Templates) to Inventory from Datastore #
#####################################################################

# Variables: Update these to the match the environment
$Cluster = "ENTER CLUSTER NAME HERE"
$Datastore = "ENTER DATASTORE NAME HERE"
$VMFolder = "ENTER FOLDER NAME HERE"
$ESXHost = Get-Cluster $Cluster | Get-VMHost | select -First 1

foreach($Datastore in get-datastore $Datastore)
{
# Collect .vmtx paths of registered VMs on the datastore
$registered = @{}
Get-Template -Datastore $Datastore | ForEach-Object -Process {
$registered.Add($_.Name+'.vmtx',$true)
}

# Set up Search for .VMTX Files in Datastore(s)
$null = New-PSDrive -Name TgtDS -Location $Datastore -PSProvider VimDatastore -Root '\'
$unregistered = @(Get-ChildItem -Path TgtDS: -Recurse | `
Where-Object -FilterScript {
$_.FolderPath -notmatch '.snapshot' -and $_.Name -like '*.vmtx' -and !$registered.ContainsKey($_.Name)
}
)
Remove-PSDrive -Name TgtDS

#Register all .vmtx Files as VMs on the datastore
foreach($vmtxFile in $unregistered)
{
New-Template -Name $vmtxFile.Name -TemplateFilePath $vmtxFile.DatastoreFullPath -VMHost $ESXHost -Location $VMFolder -RunAsync
}
}

Let’s see it in action!

Read more…

Add Virtual Machines (.VMX) to Inventory using PowerShell

There are quite a few clicks to add a virtual machine from a datastore to inventory. If you were to consolidate an environment and had to add multiple virtual machines this would be quite a manual task. Easier solution? Script it! The below script makes scanning a datastore and registering all virtual machines with vCenter a breeze.

You must have VMware PowerCLI installed in order to have the cmdlets required for PowerShell to run the script.

Add VMX (Virtual Machines) to Inventory from a Datastore:

#####################################################################
# Load VMware Plugins and vCenter Connect #
#####################################################################

Add-PSSnapin vmware.vimautomation.core

connect-viserver -server ENTER VCENTER FQDN HERE
#####################################################################
# Add .VMX (Virtual Machines) to Inventory from Datastore #
#####################################################################

# Variables: Update these to the match the environment
$Cluster = "ENTER CLUSTER NAME HERE"
$Datastore = "ENTER DATASTORE NAME HERE"
$VMFolder = "ENTER FOLDER NAME HERE"
$ESXHost = Get-Cluster $Cluster | Get-VMHost | select -First 1

foreach($Datastore in $Datastore) {
# Searches for .VMX Files in datastore variable
$ds = Get-Datastore -Name $Datastore | %{Get-View $_.Id}
$SearchSpec = New-Object VMware.Vim.HostDatastoreBrowserSearchSpec
$SearchSpec.matchpattern = "*.vmx"
$dsBrowser = Get-View $ds.browser
$DatastorePath = "[" + $ds.Summary.Name + "]"

# Find all .VMX file paths in Datastore variable and filters out .snapshot
$SearchResult = $dsBrowser.SearchDatastoreSubFolders($DatastorePath, $SearchSpec) | where {$_.FolderPath -notmatch ".snapshot"} | %{$_.FolderPath + ($_.File | select Path).Path}

# Register all .VMX files with vCenter
foreach($VMXFile in $SearchResult) {
New-VM -VMFilePath $VMXFile -VMHost $ESXHost -Location $VMFolder -RunAsync
}
}

Let’s see it in action!

Read more…

Deployment of VMware vRealize Operations Manager

vRealize Operations Manager (vROM/vROPS) gives you visibility into the performance and health of your virtual infrastructure. The bad thing about virtualization is how easy it is to accumulate over-provisioned virtual machines. When your environment grows the numbers can really be staggering. With vROM you can find these VMs and really tweak your environment making it more lean and resource efficient. vROM also has the ability to ensure compliance with IT policies, regulatory requirements, and smart alerting. Basically vRealize Operations Manager will take your structure data like performance metrics and give you a unified interface of analytics. Here is my documented deployment of vRealize Operations Manager 6.0.1 in my lab environment.

vRealize Operations Manager Logo

Planning and Reading:

Read more…

Lost connectivity to the device backing the boot filesystem

One of our HP Gen 9 blades had the following configuration error:

Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem /vmfs/devices/disk/mpx.vmhba32:C0:T0:L0. As a result, host configuration changes will not be saved to persistent storage.

The boot filesystem is on an internal 8 GB SD Card. I logged into iLo, went to Diagnostics and found the system no longer saw the SD Card as mounted:

iLo 4 - Issue with media

We evacuated the host and reseated the SD Card. It mounted without issue but to be safe we went ahead and installed a replacement SD Card. Issue reoccurred. This is caused by the version of iLo running on the server.

iLo 4 - Issue Resolved

EDIT (9/14/2015): There seems to be a issue with the iLO firmware version 2.20 causing this issue. The firmware should be updated to version 2.22. HP should be releasing version 2.30 in the next few weeks that hopefully be a full fix for this issue! Big thanks to Mike B. for reporting his findings from HP!!!

EDIT (10/2/2015): The new HP Service Pack for Proliant (SPP) (dated version 2015.10.0) contains updated iLO firmware 2.30! We are rolling this through our environment over the next week.

EDIT (12/4/2015): The 5+ blades we upgraded to iLo 2.30 haven’t had the issue repeat.

 EDIT (12/10/2015): Multiple reports of the issue reoccurring on iLo 2.30 firmware have been received. Though 2.30 firmware seems to have helped the issue it isn’t a permanent fix. iLo firmware 2.22 should be used until we hear back from HP.

EDIT (2/5/2016):  Bjorn reports HP gave him iLo 2.40 firmware to load. Just checked HP Downloads and it isn’t available yet. Awaiting to read the release notes to see if it specifically addresses this issue.

EDIT (4/20/2016): HP released iLo 2.40 firmware on April 1st. Release notes do not specify this issue specifically, only IPv6 enhancements. We still have not had the issue reoccur on any of our blades running iLo 2.30 firmware. We are going to continue on 2.30 as the enhancements with 2.40 isn’t worth the gamble of a new version.

Deprecated VMFS volume(s) found on the host

One of my ESXi 6 hosts had the configuration issue message stating: “Deprecated VMFS volume(s) found on the host. please consider upgrading volume(s) to the latest version“. I only have two LUNs presented to my hosts and both are VMFS5:

Storage is VMFS

After some brief searching I found VMware KB article 2109735 which states the possible cause:

This issue occurs because at the time of initial detection, the version of the filesystem is not known. Therefore, comparing it against the list of valid filesystems does not return a match.

Looking through the hostd log I did find the entry mentioned in the KB article. It appears that after I renamed my StarWind LUN it did not report the filesystem to the host fast enough which caused the error to occur:

/var/log/hostd.log 

HOSTD Log Entry

The resolution was to restart the management agents on the host. I put the host in maintenance mode then restarted the management agents:

services.sh restart

services.sh restart

After the management services restarted the error cleared:

Error cleared

Leave comments below if you received this message and this KB article resolved your issue!

KB2109735:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109735&src=vmw_so_vex_sbori_1079

Upgrading Windows based vCenter 5.x to 6

For this post I will go through upgrading my Windows based vCenter from 5.5 to vCenter 6. VMware has really made the installer process lean. I would even go out on a limb and say “easy”! vCenter 6 introduces the Platform Services Controller which changes the architecture of vCenter down to two components. The graphic below shows my environment before the upgrade and after:

Upgraded Embedded Architecture

My setup is very simple as I have all vCenter 5.5 components on a single Server 2012 virtual machine. I have ran through the upgrade multiple times and have yet to run into anything major. To find what your environment will look like check out the VMware vCenter Server 6.0 Deployment Guide.

Read more…