vSphere fails to connect to ESXi 5 Server

[domino]

I have started getting this message for the past week: Call "ViewManager.CreateListView" for object "ViewManager" on ESXi "[VMware server IP]" failed.

Can anyone point me to a log where we can diagnose and find out why vsphere can not connect? This happens often though sometimes I can connect to vmware server. But when I'm connected to the server, it kills the connection with another message. Any information is appreciated. Please see screen.

[vmroyale]

http://kb.vmware.com/kb/2004201 has the location of the ESXi 5 log files.

http://kb.vmware.com/kb/1003490 has the instructions to restart the management agents - sounds like that might need to happen.

[domino]

I had a problems connecting through shell (reset by peer) and vsphere (the same error message). I finally got on the server long enough to go on server maintenance mode and rebooted the server instead. After reboot, i'm still getting the same message as the screenshot, but not as often. I'm checking the logs but have no idea what i'm looking for.

[vmroyale]

Start with /var/log/vmkernel.log and /var/log/hostd.log and look for the usual suspects:
vmnic, TCP, connection, disconnect, etc

It might be worth getting the network admin involved too to see if he/she is seeing any errors or weirdness on that port.

[Gabrie1]

Check the load balancing policies in your netwerk config (on the vSwitch). If you're using IP Hash you need Etherchannels on your physical network. If you have a missmatch you could be getting these wierd networking issues.    

[ramkrishna1]

Hi domino

Welcome to the communites.

Will you please let us know its on same LAN or remote Server ?

If remote server please check if any one made any changes of firewall or router .

as we have to go step by step before proceeding .

"concentrate the mind on the present moment."

[domino]

Hey Gabrie. We do not run load blncing on our network. We think it might be an issue with the Cisco ASA5505 and are having it replaced soon.

[domino]

Hi Ram,

My vsphere client is from a remote location. It appears that all guests connected the server gets disconnected, but they do not see the error when remote using RDP. I am not getting disconnected evey 2-5 minutes.

Edit: no one has changed anything on the firewall. If they did, I should either be able to connect or not. I just don't know why I get dc'ed every 2-5 minutes. Mind boggling..

Thanks for for the input! I'm checking the logs today. And hopefully the replacement firewall comes in today also.

Added more info

[Gabrie1]

domino wrote:

Hey Gabrie. We do not run load blncing on our network. We think it might be an issue with the Cisco ASA5505 and are having it replaced soon.

Well, your ESX host DOES do load balancing.

Make sure that if you DONT have etherchannels (LACP) on your network, that you set the Load Balancing on your vSwitch to "Virtual Port ID".

[domino]

Yes, it's confirmed that Route based on the originating virtual port ID is chosen.

[domino]

I did a search and found a few warning and error that might be of consern. I only listed the warnings and errors. Also removed my originl IP address.

2013-02-04T16:14:19.793Z [73395B90 warning 'Proxysvc Req00654'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:14:34.613Z [FFEACA90 warning 'Proxysvc Req00660'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:14:35.193Z [735DEB90 warning 'Proxysvc Req00659'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:14:39.393Z [72E81B90 warning 'Proxysvc Req00664'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:14:52.733Z [7289CB90 warning 'Proxysvc Req00651'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:16:16.173Z [73417B90 warning 'Proxysvc Req00665'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:17:58.309Z [721C2B90 error 'Default'] SSLStreamImpl::BIORead (738e5688) timed out
2013-02-04T16:17:58.310Z [721C2B90 error 'Default'] SSLStreamImpl::DoServerHandshake (738e5688) SSL_accept failed with BIO Error
2013-02-04T16:17:58.310Z [721C2B90 warning 'Proxysvc'] SSL Handshake timedout for stream 112.209.xxx.xxx, blacklisting it for 3000 ms
2013-02-04T16:18:20.572Z [73048B90 warning 'Proxysvc Req00669'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection reset by peer)
2013-02-04T16:21:55.313Z [72F03B90 warning 'Proxysvc Req00662'] Error reading from client while waiting for header: N7Vmacore15SystemExceptionE(Connection timed out)
2013-02-04T16:30:17.861Z [7318DB90 warning 'PropertyCollector'] SetDone took 3262543 microSec

[Alim786]

Please double-check that the IP Configuration of your ESXi Server is correct :-

1. Static IP Address.

2. Correct Subnet Mask.

3. Correct Default Gateway.

4. Correct DNS Servers.

5. Check DNS record is correct.

6. Check Name Resolution from and to server is correct.