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. Decoding the error, I pretty much figured that the object already existed in the SSO database and I needed to delete the existing object. Here is how you do that. Log in as root to the appliance shell of the Platform Services Controller appliance with which the vCenter Server Appliance is registered.
ESXi 5.5 Update 3a and its associated patch have been released. If you have been following KB2133118 in regards to the the Snapshot Consolidation causing Virtual Machines to crash a fix is now available. If you are currently running ESXi 5.5 U3 you can use update manager to install the patch. If you are looking to install ESXi 5.5 U3 from scratch or update from a previous version you should make sure you update to 5.
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. If you are currently running ESXi 6.0/6.0U1 you can use update manager to install the update. If you are looking to install ESXi 6.0 U1 from scratch or update from a previous version you should make sure you update to use the latest ISO.
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. While trying to setup my Platform Service Controllers for HA. I was having issues sshing into the appliance. I kept on getting errors, that the packet sizes were too big or just authentication would fail.
I am actually pretty surprised this bug still exists. I came across this issue with my first deployment of vSphere 6. Now I am circling back around to do a POC and it still exists. When trying to join a Platform Services Controller to the domain via the vSphere Webclient I get the following error: “java.lang.reflect.invocationTargetException” There are currently two workarounds now with 6.0U1 I am aware of. The first method is to join to the domain using the CLI.
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. You see, VMware has had a bug KB2124669 since ESXi 6.0 that can cause an ESXi host to randomly lose connection, freeze and overall act really terrible. With the release of 6.0U1 it still exists.
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. Working with VMware support we were finally able to get it working with a few tweaks and there is a current pending KB that has not been published yet. (KB2113038) I have been told this affects both an embedded deployment (VCSA and PSC together) and external deployment (VCSA and PSC seperate.
After upgrading vCenter this functionality is no longer enabled by default. Please perform the following steps to enable rename of files upon successful Storage vMotion. Log into the vSphere Client as an Administrator Click Administration > vCenter Server Settings Click Advanced Settings Add this advanced parameter key: provisioning.relocate.enableRename Set the value to: true Click Add Click OK Restart the VMware VirtualCenter Server service for the changes to take effect
If you are configuring a cluster with less than 2 datastores, you will receive an HA warning “The number of heartbeat datastores for host is 1, which is less than required: 2” You can add an option to the HA Advanced Options to supress this warning. Log in to vCenter Server Right-click the cluster and click Edit Settings Click vSphere HA > Advanced Options Under Option, add an entry for das.
When setting up a cluster for testing you may not have 2 nics to use for management. to bypass the warning you can configure HA to not alert you for this issue. To perform the steps in the c# client. From the VMware Infrastructure Client, right-click on the cluster and click Edit Settings. Select vSphere HA and click Advanced Options. In the Options column, enter das.ignoreRedundantNetWarning In the Value column, type true Click OK.