If you’re upgrading from vSphere 5.1 to vSphere 5.5 and you ARE NOT using Custom CA SSL Certificates then you might run into an error. The error will be encountered during the upgrade of SSO, and specifically the Lookup Service, and only occurs in specific conditions, such as when using the default VMware Self-Signed Certificates. If you run into this problem your upgrade process will roll back, but leave behind some upgrade files that need to be cleaned up. This article will briefly touch on the recommended solution to this problem.
Recently I posted some updates to the supportability of Windows Server 2012 Clustering and SQL Server in particular in my articles titled Windows Server 2012 Failover Clustering Now Supported By VMware With Some Caveats and The Status of Microsoft Failover Clustering Support on VMware vSphere 5.1. VMware KB 1037959 Microsoft Clustering on VMware vSphere: Guidelines for Supported Configurations explains the configurations that are supported and provides guidelines. The reason for this article is because some people might think because these configurations are now supported on top of vSphere that somehow the configurations are also supported with vCenter and other VMware Products. Unfortunately this is not the case. In this article I’ll cover some background and where things are today.
This is just a quick article to let you know that VMware vSphere 5.1 now appears on the Microsoft SVVP list. There have been quite a few customers asking about this. It didn’t impact support of any customers that have a Microsoft Premier Support Agreement, but could have impacted customers that don’t have a Premier Support. Anyway, to cut a long story short VMware and Microsoft sorted out the holdup and now got the list updated. You can check out the new entry here – Windows Server Catalog – VMware vSphere 5.1.
[Updated 25/06/2013] A couple of people have mentioned that I haven’t explained in this was the Microsoft SVVP is. So here goes. SVVP stands for the Server Virtualization Validation Program. It’s basically Microsoft’s way of validating hypervisor technology with their server products. But as I’ve said above it’s only relevant if you don’t already have a Premier Support Agreement. So know you know what SVVP is.
This post first appeared on the Long White Virtual Clouds blog at longwhiteclouds.com, by Michael Webster +. Copyright © 2013 – IT Solutions 2000 Ltd and Michael Webster +. All rights reserved. Not to be reproduced for commercial purposes without written permission.
Upgrading to vSphere 5.1 has been a bit of a hot topic ever since it became a GA product in 2012. The problems some customers have experienced during the upgrade process to vSphere 5.1 have been well documented and VMware certainly received a lot of feedback which was taken on board. But many upgrades still went through without any major dramas at all. I completed a couple of small scale upgrades without any problem just after the GA. The real trouble was when you started to try and integrate into larger scale and more complex environments with more complex requirements. So is now the time to upgrade if you haven’t already?
A little while ago I wrote an article titled 5 Tips to Prevent 80% of Virtualization Problems. This article was all about storage and how to configure your storage and the dangers to watch out for. This is because problems in virtualized environments are predominantly caused by or related to storage in one way or another. In that article I explained the impact of queue depths on performance and also some of the dangers of making the HBA device queue depths too high. What I didn’t know at the time I wrote the previous article was that the default queue depth for QLogic HBA’s was changed between vSphere 4.1 and 5.x. This article will being you up to date on the changes and the impacts of the change in default values between vSphere 4.x and 5.x.
One of the most important documents for any vSphere administrator or architect has been released. The vSphere 5.1 Hardening Guide is now available. The guide was announced on the vSphere Blog by Mike Foley – vSphere 5.1 Hardening Guide – Official Release. I’d like to thank Mike and the rest of the VMware Security Team that was involved in putting this invaluable resource together. It has been reformatted from the previous version to make it easier to use. I think you’ll all like the new improvements.
The number of enquiries I’ve been receiving regarding Microsoft Failover Clustering, especially for Microsoft SQL Server Databases has skyrocketed in the past few weeks. I have been receiving a number of enquiries from customers and also from partners including cloud service providers. As a result I thought I’d write this article to help you understand what the current status is of support for Microsoft Failover Clustering on VMware vSphere 5.1 (GA) and with regard to some VMware products.
I’ve been getting feedback and questions from a number of different places of people wanting to disable Single Sign-on in vSphere 5.1 for various reasons (with vCenter). This is mainly due to difficulties around implementation of SSO in combination with other VMware solutions, such as VMware View, vCloud Director. My response to the questions is very simple. DON’T DO IT! At least not with vCenter itself. vSphere 5.1 and vCenter was not designed to run without SSO and this is definitely not supported and will likely result in a broken environment. This brief article will give you some tips on how you can be successful with SSO.
vCenter Heartbeat is the only supported and validated solution for providing high availability to vCenter Server, and can also protect the core components that go with it (such as SSO, VUM, Inventory Service etc). I strongly recommend vCenter Server Heartbeat be considered for environments where the management infrastructure availability is critical. I’ve used vCenter Server Heartbeat in a number of implementations. But it hasn’t always been easy to implement. The good news is that now thanks to the team at VMware and VMware KBTV we have a video that takes you through the installation and validation of vCenter Server Heartbeat in a vSphere 5.1 environment. In this article I’ll give you some insight into when you might want to deploy vCenter Server Heartbeat, and you can learn how by viewing the video.
The people in VMware Technical Marketing and Engineering have been very busy as usual and have recently published an excellent and deep paper on the VMware vSphere 5.1 CPU Scheduler. This paper is an update from previous papers that have been written about it. Getting the most out of your CPU’s and tuning the environment for peak performance from a CPU perspective starts here.