Today I was preparing a new blade chassis in an existing vCenter environment. After applying the predefined Critical Host Patches baseline (default task for new hosts), the hosts would not reconnect to vCenter.
Turns out VMware decided to disable SSLv3 for ESXi 5.5 Update 3b and higher, because of the POODLE vulnerability. The dependency is clearly stated in the release notes and in the VMware Product Interoperability Matrix below. (more…)
NetApp released Virtual Storage Console (VSC) version 5.0 last April. NetApp VSC for VMware vSphere is a tool that enables you to monitor, manage and provision your NetApp storage back-end from within VMware vCenter. The VSC 5.0 release only integrates with the vSphere web client, luckily so. If you still want to be able to use VSC with the desktop vSphere client, you are bound to VSC version 4.2.1.
By installing VSC, some predefined roles are implemented within vCenter. Utilizing VMware’s RBAC capabilities makes it possible to grant your vCenter administrators access rights to perform some basic storage tasks. By doing so, it relieves your storage team by not having to perform these administrative duties.
These basic storage tasks include:
Next to the tasks above, VSC can also be used to configure vSphere hosts with the recommended NFS settings and to deploy the VAAI plugin.
Another nice new feature is the VASA (VMware APIs for Storage Awareness) appliance with support for Clustered Data ONTAP. The VASA appliance will be the foundation for the much awaited virtual Volumes (vVOL). The VASA integration with vCenter depends on the VSC plugin, so make sure VSC is installed before you deploy and configure VASA.
(more…)
UPDATE: VMware announced the public beta for their new vSphere version!! Sign-up here: https://communities.vmware.com/community/vmtn/vsphere-beta
With the release of the latest vSphere 5.5 version (update 1) in March 2014, VMware once again took a major step in the development of it’s hypervisor and the supplementary software and tools. Finally the vCenter appliance took over from the Windows installed version as the primary choice for vCenter deployment. The Windows installed version now officially supports Windows Server 2012 R2.
In the first 5.5 release various improvements were made; SSO is enhanced, support for 62TB VMDK, 16Gb FC support to name a few. And of course VMware Virtual SAN (VSAN) is now included in the update 1 version!!
There are some features however still missing. I, for one, would very much like to see these missing features in the next major release of vSphere. Having said that, I don’t expect VMware to announce the release of vSphere 6 this year. I think the coming period will be used by VMware to further engage customers to adopt VSAN and NSX. It will be very interesting to see on what scale these technologies will thrive! !
When thinking of what I would like to see in the vSphere 6 line-up, I came up with the stuff listed below:
Let’s walk through my wish list…
<update 13 november 2014>
VMware does not support backing up the individual components and restoring them to a newly deployed appliance. Use of image-based backup and restore is the only solution supported for performing a full, secondary appliance restore (KB2034505).
Thank you, Feidhlim O’Leary (VMware), for pointing this out in the comments.
</update 13 november 2014>
Last week I was upgrading an old ESX 4.1 environment to ESXi 5.5 and the vCenter server needed to be replaced by the vCenter Server Appliance (vCSA). The new limitations on the 5.5 release should suffice for a lot of environments, the only downsides being no Heartbeat, Linked Mode, VUM and IPv6.
After deploying and configuring the appliance, I soon realized there wasn’t a single article that listed all the necessary post-installation backup tasks. Someone not as smart as you will eventually break your appliance, so make sure to perform all following tasks.