Just a quick heads up for anyone running vSphere 5.0/5.1 with the Isilon NAS-VAAI plugin for vSphere/OneFS 7.0.
If you are planning to upgrade to vSphere 5.5, there are a couple things to know. The plugin does not work in 5.5 (new or upgraded) installations.
I built a new vSphere 5.5 installation, and the plugin loaded fine. But… When attempting to configure the credentials for the OneFS 7.0 cluster you are connecting to, the authorization tool fails to operate properly.
In a new vSphere 5.1 installation, the error is not present.
I upgraded a vSphere 5.1 host to 5.5 to determine if I would retain functionality. Maybe the authorization piece (auth_gen) was the only part affected. On this host that had successfully used the plugin, it no longer worked after the upgrade to 5.5.
In vSphere 5.5, the libssl.so shared library is libssl.so.1.0.1, while in vSphere 5.1, it is libssl.so.0.9.8.
I reached out to the team responsible for the plugin, and have confirmed they are aware of the issue, and working on a resolution.
At VMworld US in San Francisco last week, VMware had quite a few different announcements around the 5.5 release of vSphere.
Announcements around the vCenter Server Appliance really hit home for me in the Federal space.
Ready for Prime-time
In vSphere 5.5, the vCenter Server Appliance limitations have been extremely raised when using the vCenter Server Appliance:
Previous to vSphere 5.5, the limits were:
- 5 vSphere Hosts
- 50 Virtual Machines
With vSphere 5.5, the limits are now:
In short the vCenter Server Appliance now has the horsepower to run in many, if not most vSphere Environments – even in the Fed space.
That’s right, that time of year is approaching… VMworld US 2013.
For the past 4 years, EMC has sponsored a v0dgeball (Translated Dodgeball for people with a virtual affinity) tourney at the US VMworld Conference.
In those 4 years, v0dgeball participants, spectators, & contributors have raised over $30,000 in donations for the Wounded Warrior Project. Not too shabby, but we can do better. So here we are again with EMC’s 5th Annual v0dgeball Tourney.
A quick recap from last year:
- 11 Teams Played including
- Over 60 Spectators (looked like it was more than that)
- 1,143 #v0dgeball Tweets
- 8,041 Tweetvite Views (http://v0dgeball.com)
- 1st Place Winners – Arista
- 2nd Place Winners – Brocade
- Over $13,000 raised for the Wounded Warrior Project
Categories: Military, Storage, Virtualization Arista, Brocade, Cisco, EMC, Juniper, NetApp, v0dgeball, VCE, VMware, VMworld
Isilon OneFS 7.0 has been out for a couple months. OneFS 7.0 has brought some additional features to Isilon, particularly toward VMware vSphere support.
I blogged about VASA support in another article: Configuring the EMC Isilon VASA Provider.
This article is going to focus on how to configure the NFS VAAI Plugin for Isilon when used with VMware vSphere 5.
Here are the basic technical requirements to get the plugin working:
- An Isilon cluster running OneFS 184.108.40.206 or higher
- VMware vSphere 5.0
- I have used vSphere 5.1 without issue
- *I have heard of several situations where 5.0 does not work successfully
until upgraded to 5.0 Update 2
- **I have not seen this work with vSphere 5.5 (as of early September 2013)
- A SmartConnect zone configured for the presented datastores
- NFS mounted datastores being presented from the Isilon cluster using the SmartConnect zone name (can be short or FQDN)
- All IP addresses in the Isilon pool must be “Allowed IP addresses” in the NFS Client settings in ESXi
The installation process is not 100% straight forward according to the Release Notes, which require a support.emc.com login to get to. I’ll try to provide a little clarification here.
I saw Ivo Beerens’ blog post about using BGInfo and VMware View: Display the protocol used on the VMware View desktop background and it made me think of some of the scripts I’ve used. I figured I would share them.
I’ve used BGInfo for years, and have collected several scripts that I have used for various pieces of info that isn’t always the easiest to get from either the Windows registry or other places. When I worked for a Service Provider, it wasn’t uncommon to have systems spread across different Windows versions, multiple time zones, 64 or 32 bit, etc.
Here are some of the scripts I regularly used when I was an Administrator.
System Type – Displays the Hardware Manufacturer & Model Type
Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20
'*** Connect to this PC's WMI Service
Set objWMI = GetObject("winmgmts:\\.\root\CIMV2")
'*** Query WMI for Hardware
Set items = objWMI.ExecQuery("SELECT * FROM Win32_ComputerSystemProduct", _
"WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly)
For Each item In items
strSystemType = item.Vendor & " " & item.Name 'What we're after
If Len(strSystemType) = 0 Then strSystemType = "Not Found in WMI"