Solved

vSphere losing connectivity to ESXi 4.1

Posted on 2010-09-14
2
9,261 Views
1 Endorsement
Last Modified: 2012-05-10
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.
1
Comment
Question by:cgillet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 28

Accepted Solution

by:
bgoering earned 500 total points
ID: 33678463
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
 

Expert Comment

by:alexandermortulev
ID: 33693427
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

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question