Last week i have not been successful in upgrading the VMware environment from 5.5 to 5.5U1. Initial installation went fine, configured the first ESXi host and created a host profile. So far so good, no major issues. When installing the remainder of the 5 other blade servers and applying the host profile all seems to be working well whereas things went sideways when the entire environment was shutdown and restarted.
Te setup looks as following:
Dell 1955 blade center servers (6x)
Cisco 3030 switches connected to the blades
vCenter server as a VM on the ESXi cluster
vCenter upgrade manager as a VM
Distributed Virtual Switch configured
During the shutdown procedure i move all the vCenter components to a single host before powering down the vCenter server (Windows 2008). Then i shutdown the ESXi host using the management client as vCenter is no longer available.
Power up cycle is to start this ESXi host first, connect to it and then powerup the vCenter components. Once all is running DRS and Power management is configured to automatic after which the simulation VM's are started.
With 5.5 all was working well and no issues at all. When i installed 5.5 U1 i could no longer connect to the ESXi server and it gave an error 503 when connecting to it. Going through the log files showed that components on the file system could not be found after which i decided to do a clean install.
After reinstalling the whole lot i connected to a ESXi host and enabled the network and added the iScsi adapter. At that stage the system becomes unresponsive and the session between the ESXi host and the client is disconnected.
Running several tests i concluded that something must be wrong with the virtual disk system components, iScsi or vSan. 5 of the 6 hosts will be rolled back to vmware 5.5 as vmware 5.5U1 is not stable...
Can use some help troubleshooting this issue as i will leave 1 server in the current state it is to identify the root cause as i'm stuck at the moment. Later on i will post some log file sections with the errors i identified. (Restarting the hostd does not resolve the problem)