I had a use case I wanted to investigate in regards to the new VCHA that is part of VMware vCenter Server 6.5. One thing I noticed, is when you have VCHA configured, there is no way to know which node of the HA cluster you are connecting to without being logged on.
Welcome to my post about upgrading your VMware vCenter Server Appliance (VCSA) to 6.0 U1b.
So I am in the process of doing some vSphere 6 testing and needed to test a redeployment of one of my VCSA’s. The problem is when I went to redeploy it I got the following error.
ESXi 6.0 Update 1a has been released. If you have been following KB2124669 in regards to the the NETDEV WATCHDOG issue causing an ESXi host to hang. The update is now available.
So I am in the midst of setting up a vSphere 6 POC and it has been a bit since I played with it. I came across a problem I thought i would document and share.
Today vSphere 6.0 U1 is released. This is normally the update everyone waits for before upgrading their production environments to the latest version. I think the first time in awhile, a lot of people will wait.
So one thing I have come across with a few VCSA6 installs was the inability to use login with current credentials via the Web client or vSphere client.