Upgrading vCenter Operations Manager OS to SLES 11 SP2

With the release of vCenter Operations Manager 5.8 (now at 5.8.1), an upgrade to the appliance’s underlying OS also needs a bit of patch, which makes sense since SLES 11 has been out for a while (January 2013). It’s a pretty simple upgrade, but you have to do it from the OS itself, not the vC Ops admin console. Continue reading

Change Virtual Machine SCSI Controller Type in NexentaStor VSA

Before I say anything, I shouldn’t need to say this, but I will. This is not supported. Now, on to the fun!

The current release of NexentaStor (v3.1.4.1) is made available as an OVA to make it easy to import into VMware environments. Currently this only “works” in full blown vSphere hosts and not Fusion/Workstation/Player (“works”, because with some fenagling, you can get it running in Fusion – don’t have access to Workstation/Player at the moment). Ok, already getting off track. This OVA comes with the following hardware configuration:

1 vCPU
2GB RAM
1 x 8GB Hard Drive (syspool)
– this is configured with a VMware Paravirtual controller
1 Virtual Nic
– this is configured as a VMXNET3 device
Continue reading

Nexenta VAAI-NAS Beta Released, NFS Hardware Acceleration

Skip to Update 1

Along with the release of NexentaStor 3.1.4, Nexenta Systems today officially released the (very) Beta VAAI-NAS plugin for VMware vSphere 5.x via the community NexentaStor.org forums. VAAI-NAS is still not widely supported in the NAS world, and of those that do, not all support all the primitives.  You can search the VMware Compatibility Guide for vendors that are VAAI-NAS certified.

VAAI, to catch up, is the the suite of primitives (instructions) that allow vSphere to offload certain VM operations to the array. For NAS Hardware Acceleration, these are:

  • Full File Clone – Enables virtual disks to be cloned by the NAS device (but not ‘hot’, the VM must be powered off).
  • Native Snapshot Support – Allows creation of virtual machine snapshots to be offloaded to the array.
  • Extended Statistics – Shows actual space usage on NAS datastores (great for thin provisioning).
  • Reserve Space – Enables creation of thick virtual disk files on NAS.

Everything you wanted to know about VAAI (but were afraid to ask)
http://www.vmware.com/files/pdf/techpaper/VMware-vSphere-Storage-API-Array-Integration.pdf

At this point, all primitives are working (or supposed to, it’s beta, right?) save for the Native Snapshots.

Here’s a quick tutorial to install the agent in NexentaStor and the plugin in VMware Vsphere.

Continue reading

PowerCLI Mass Add Hard Disks to Virtual Machine

While doing some iSCSI LUN testing for a certain storage vendor, I was looking for a way to add multiple hard disks to a single VM across each iSCSI LUN whose name matched a certain pattern. In my case, all luns I was testing against had the full lun path in their name so the were similar to lun1.naa.600144f0dcb8480000005142553e0001 (thanks to Alan Renouf’s post “PowerCLI: Mass provision datastore’s” for guidance on  scripting datastore creation).

However, I do not have all luns mapped to every vSphere host. Easy enough to get around this in PowerCLI. The following script prompts for the Virtual Machine name, size and hard disk format. Then filters the datastores by that VM’s vSphere host and our common string in the datastore name.


$vmname = read-host "VM Name to add disks to"

$vm = get-vm $vmname

$size = read-host "Disk Size (GB)"

$format = read-host "Disk Format (thin, thick, EagerZeroedThick)"

$datastores = $vm | Get-VMHost | Get-Datastore | Where-Object {$_.name -like "lun*naa*"}

foreach ($item in $datastores){
$datastore = $item.name
write-host "Adding new $size VMDK to $vm on datastore $datastore"
New-HardDisk -vm $vm -CapacityGB $size -Datastore $datastore -StorageFormat $format
}

There are a lot of parameters for the New-HardDisk cmdlet that I don’t specify because the defaults were what I already wanted (e.g. Persistence, Controller, DiskType, etc.). Some, like StorageFormat which defaults to Thick Lazy Zeroed, I wanted to control.

In another case, I wanted to add multiple disks from one datastore to a vm.


### Get VM/Disk Count/Datastore information ###
$vmname = read-host "VM Name to add disks to"
$num_disks = read-host "number of disks to add"
$ds = read-host "Datastore to place the VMDK"
$format = read-host "Disk Format (thin, thick, EagerZeroedThick)"
$size = read-host "Disk Size (GB)"

$vm = get-vm $vmname
$datastore = get-datastore -name $ds
$x=0

### Add $num_disks to VM
while ($x -lt $num_disks){
write-host "Adding $size VMDK to $vm on datastore $datastore"
New-HardDisk -vm $vm -CapacityGB $size -Datastore $datastore -StorageFormat $format
$x++
}

You can read more about the New-HardDisk cmlet at:
http://www.vmware.com/support/developer/PowerCLI/PowerCLI51/html/New-HardDisk.html

VMs Grayed Out (Inaccessible) After NFS Datastore Restored

[Added new workaround]

While working with a customer last week with Mike Letschin, we discovered an issue during one of their storage tests. It wasn’t a test that I’d normally seen done, but what the heck, let’s roll.

“What happens to all the VMs hosted on an NFS datastore when all NFS connectivity is lost for certain period of time?”

Well, turns out, it depends on a couple things. Was the VM powered on? How long was the NFS datastore unavailable for?

Downgrade firmware on an Dell ESXi host

An issue has come up on one of my Dell PowerEdge R610 ESXi hosts that I wanted to attempt a downgrade of the firmware on my Broadcom BCM5709 network adapters for troubleshooting, but was not finding any easy way between the Server Update Utlities, OpenManage Essentials, etc.

This didn’t fix my issue, but it was a PITA to figure out the best/fastes/easiest way to get this done, that I thought it worthwile to share.

My first thought was to attempt to use the Firmware Upgrade wizard built into the Dell Management Plug-in for VMware vCenter because it offers an option to select an update executable from a CIFS share, but that, unfortunately, just threw me an error even though I was using a valid DUP file.

Failed sending update file: (NETW_FRMW_WIN_R299290.EXE) to iDRAC – Details: The update package (NETW_FRMW_WIN_R299290.EXE) is not supported via 1×1 update feature. Use the repository method to update this device. This error can also be seen if package is not named according to Dell naming standards.

So I decided to build my own repository and point the Plug-in to that, and here’s that process:

Continue reading

Dell Management Plug-in for VMware vCenter Update 1 Released

Today, Dell released Update 1 to the 1.0.1 version of their Management Plug-in for VMware vCenter. The biggest highlight among the fixes and changes would be the added support of ESX5 (vCenter 5). If you’re currently running the 1.0.1 plugin under a vCenter 5 environment (which ‘works’, just not in a supported kind of way), you’ll need to unregister and re-register the Dell Management Plugin after upgrading (see the Release Notes for all issues/resolutions).

One of the major changes from the original 1.0 to the 1.0.1 plug-in was the promise that updates to the appliance/software would come as an RPM patch and not tied to re-deploying another OVF. I’m glad to report that this worked wonderfully. You can find full instructions in the Dell Management Plug-in for VMware vCenter User Guide (page 41), but here’s the quick and dirty:

  1. Always backup your appliance. Always backup pre-upgrade. When? Always.
  2. Open up and log into the web admin portal (https://myApplianceHostname/)
  3. Click on ‘Appliance Management’ in the left menu
  4. Click ‘Upgrade’
    – This will boot you out of the portal, upgrade the software and reboot the VM (the User Guide makes no mention that it reboots the VM, so just know that it does).
    – I recommend opening up a VM Console so you don’t have to just sit and refresh the page to see if it’s back up or not
  5. Restart your vCenter Client (this might just be me because I was having some DNS issues at the time on my desktop)

The whole process took about 10 minutes for me. It took about 7 minutes before I saw the appliance reboot.

 

Happy upgrading.

 

Dell Management Plug-In for VMware vCenter Review

Ok, I’ve had the plug-in running for a few weeks and have gone through some of the primary functions of it (firmware updates, inventory, monitoring, warranty retrieval, create hardware profile for deployment)

I’m not going to go through the initial setup, that’s been covered pretty well on DellTechCenter.com.

Here are the claimed major functionalities with my notes as far as day to day usage as well as some miscellaneous thoughts at the end.

New Dell EqualLogic Arrays

Dell unveiled an update to 2 of their EqualLogic PS series array platforms today along with their first sub-$10k array. The new PS6100 and PS4100 series arrays are a refresh of their PS6000 and PS4000 units. The new boxes are being touted as having up to a 67% improvement in I/O performance. 

Here are the major new features for each:
PS41000
– shrinks down to 2U
– 24 x 2.5″ drives – up to 21.6TB
– 12 x 3.5″ drives – up to 32TB
– Now starting at under $10,000

PS6100
– 2U version with 24 x 2.5″ drives – up to 21.6TB
– New 4U design with 24 x 3.5″ drives – up to 72TB
– NEW Dedicated management port

Capture

Both arrays will ship with the latest 5.1 firmware and are certified for VMware’s vSphere 5.0 storage APIs (VASA, VAAI, etc.). The SSD options will go up to 400GB per drive, which I’m sure will be slightly over the $10,000 starting price in the PS4100. 

This may sound lame, but the addition of the dedicated management port on the PS6100 is something that I’m very excited about. I never understood why there was one on the PS4000 but not the PS6000. It was maddening to lose 25% of my total network throughput on an array if I needed to attach it to a dedicated management network.

Being in the market for a Sumo (Dell’s EqualLogic Monster PS6500 series array), I was hoping that those would get the same refresh, and even though I knew it wasn’t going to be refreshed yet, I’m still a bit bummed that I may have to purchase it just before it gets its own upgrade.

LA VMUG – vCenter Operations

The Los Angeles VMUG was held today at the DoubeTree Hotel at LAX and the primary topic was a product discussion and demo of vCenter Operations. Much of the time was dedicated to what needs and gaps it fills.

 

The dilemma now is that we have essentially 3 layers: Hardware, Hypervisor, OS/App. For each of those 3 layers there are a multitude of ways to monitor capacity, get health checks and gain deep visibility into performance metrics and bottlenecks. This is the goal of the vCenter Operations along with the promise of capacity planning, compliance checks and change management.

Continue reading