vSphere losing connectivity to ESXi 4.1

I have a HP Proliant DL380 G7 running ESXi 4.1

As of yesterday I have been experiencing the following problem:
From the vSphere Client, when I click Login I get an error stating
vSphere Client could not connect to "192.168.4.10".
A connection failure occured (Unable to connect to the remote server)
I can still ping 192.168.4.10 and get a response.
When I got to the machine and run "Test Management Network" the pings there all fail (it pings the default gateway and primary and secondary DNS servers)
Then I select "Restart Management Network", the network restarts and I'm able to log in via vSphere.
However, after anywhere from 1 - 10 minutes, I'll get an error message stating
The request failed becuase the server '192.168.4.10' closed the connection. (The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.)
Error Stack
Call "PropertyCollector.CreateFilter" for object "ha-property-collector" on ESXi "192.168.4.10" failed.
And at this point if I close vSphere and reopen I'm given the original error message when I attempt to log in.

The server is configure w/ a static ip.  And the NIC I'm running through is an HP NC382i (which I belive is on the hardware compatibility list)

I'm leaving for the day, but I'll gladly try any suggestions tomorrow morning.  Pleas let me know if there are any useful logs I can provide.
LVL 1
cgilletAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
bgoeringConnect With a Mentor Commented:
You might post /var/log/messages for the time period when you restart the agents and when it fails.

Also if it is plugged into a managed switch take a look at the logging there and see if you are seeing anything.
0
 
alexandermortulevCommented:
I had the same problem when I try to move vSphere vCenter server to one of ESXi HA Cluster ESXi hosts.
vCentre server role, better, install to separate host.
In my case, I made one more virtual Windows Server 2003 machine on previously used Linux/VMware Server 2 and problem was resolved.
If you have a lot of ESX hosts to control (>10), you will need to separate vCenter server and SQL database to different servers for better peformance.
0
All Courses

From novice to tech pro — start learning today.