Skip to main content

vSphere 5.5 - End of General Support mean?

On September 19th, vSphere 5.5 exited its general support phase and moved into something called “Technical Guidance”. In response to this, many have already moved to a newer release of the vSphere 6.x line. Whether it be for compatibility concerns or a reasonable wariness of touching what’s not broken, there are several of us who are riding the wave to the very end. Let’s talk about what “End of General Support” really means for those still running vSphere 5.5.

Technical Guidance
First, let’s clear up a common misconception about Technical Guidance. Specifically, it does not mean that the product becomes instantly unsupported. I hear this word thrown around a lot for products out of the general support phase, but it’s misleading to do so. VMware Support will still help in the event of an issue in an environment running these products. There are, however, some serious limitations to how far this goes now that it is outside of General Support. Many times, these cases will end up requiring an upgrade anyway.

VMware’s Lifecycle Policy documentation does a pretty good job explaining what you get from support with products outside of general support. Here’s what it says:



“Technical Guidance is available primarily through the self-help portal and telephone support is not provided. Customers can also open a support request online to receive support and workarounds for low-severity issues on supported configurations only. During the Technical Guidance phase, VMware does not offer new hardware support, server/client/guest OS updates, new security patches or bug fixes unless otherwise noted. This phase is intended for usage by customers operating in stable environments with systems that are operating under reasonably stable loads.”

Pretty straightforward. No Severity 1 calls, and no patches for any issues found to be a product defect. This means security patches as well! You can still file web-based tickets and request help troubleshooting problems. The results of these will often consist of help identifying knowledge articles that describe known issues or environmental misconfigurations, along with configuration guidance or recommendations.

The Reality of Supporting vSphere 5.5

What’s not clear from the statement above are the less obvious effects of opening cases for outdated products. Support engineers are human just like our customers, and there are limitations to the knowledge that a team of technicians can maintain in its ranks.
vSphere 5.5 was released in 2013, and there have since been three more major releases of the product. Many Support Engineers came in during the 6.x era, and vSphere 5.5 volume has been steadily declining for years. This means that it can be difficult and time consuming to answer complex questions about the 5.5 product line. Furthermore, when vSphere 6.x released, it changed the game quite a bit in terms of architecture and troubleshooting techniques. This matters a great deal to what support becomes accustomed to seeing when they help customers, and as the volume of vSphere 5.5 cases drops, so does the overall knowledge of it within support.
It’s important to know that if you are upgrading from vSphere 5.5, VMware support is still here to help if a problem should arise. We are equipped to handle the Technical Guidance cases that come in, but it becomes harder to do so as we move deeper into the Technical Guidance period – and questions take longer to answer.

Letting Go

vSphere 5.5 was a great release, and I miss some of the ways it worked that changed in 6.x. With a lack of ongoing security patches, reduced supportability, and missing new features, however, it’s just not a good choice for production environments going forward. If you have not started planning a way to move to 6.x yet, now is the time to do so.


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Console Mouse Not Working in Windows 2012 VMs

I recently ran into some problems while deploying a Windows Server 2012 R2 VM in my vSphere 6.5 U2 lab. I’ve come to expect that the console mouse response is going to be terrible until VMware Tools is installed, but for some odd reason I had no mouse control whatsoever. Thinking it may be a quirk of the Web Console, I tried both the Remote Console and the HTML5 client to no avail. The VM appeared to be healthy and would register keyboard input, but the motion of the mouse cursor was erratic or the cursor would not move at all. Thinking that I just needed to battle on and get Tools installed, I attempted to use the keyboard for this purpose – what a chore. You think it would have been easy, but the installer kept losing focus and falling behind other open windows. Many of the windows keyboard shortcuts I’d normally use were not functioning because they register on my laptop – not in the console. I couldn’t RDP to the VM either because the NIC needed to be configured with a vali...
Post a Comment
Read more

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...
1 comment
Read more

vCenter Server Options on VxRail Appliance

In this post we will discuss the pros and cons of vCenter Server deployment on VxRail. During VxRail initialization we can choose two options for vCenter Server deployment, both options are “Deploy new vCenter Server Appliance (VCSA)” and “Join existing vCenter Server”. We should know its limitation before we choose the each option. You can find the details as below. If we choose the bundle vCenter Server deployment The vCenter Service Server Appliance (VCSA), vCenter Server Platform Services Controller (PSC) and vRealize Log Insight VM are already pre-loaded on each VxRail node. When VxRail initialization it can deploy these VMs automatically based on our business requirement. Pros The vCenter Server (VCSA) deployment is done automatically. When installing software package upgrade for the VxRail Manager, both VCSA and PSC includes the processing of package upgrade. VMware Log Insight is deployed automatically The vCenter license is bundled on VxRail Appliance. C...
1 comment
Read more