I made an update from ESXi 5.0 to the build mentioned in the topic.
Also a custom VIB was created and installed. After this I made an reboot of the ESXi host.
So far so good, ESXi is pingable, VMs are up and I can do a remote login into the guests.
However I can't login to the ESXi host via vSphere Client anymore.
I have got the german error message and will try to translate it into technical english
"The vSphere-Client could not establish a connection to "myhost".
An unknown error occured. (The server could not interpret the clientrequest. (The Remoteserver returned an error: (404) Not found.))
Connecting to the Port 80 via Browser redirects to port 443 which says forbidden (403)
The PowerCLI returned the following
These are the ports (standard, I guess):
PORT STATE SERVICE
22/tcp closed ssh
80/tcp open http
427/tcp open svrloc
443/tcp open https
902/tcp open iss-realsecure
5988/tcp closed wbem-http
5989/tcp open wbem-https
8000/tcp open http-alt
8100/tcp open xprint-server
8300/tcp closed tmi
I found this article here (http://vmtoday.com/2012/02/vsphere-5-networking-bug-2-affects-management-network-connectivity/) which says that the traffic goes over the wrong interface. (if I understood it correctly.)
Other sites say that it maybe because of double MAC or IP Addresses. But I found out, that the IP of the host (which is still pingable) has got the right MAC Address (found over arp).
Has anyone of you experienced this behaviour or knows a workaround? I have got remote hands which can restart the host but are not able to do stuff on the console. Any help will be appreaciated a lot!