ESX host disconnect

[julian2]

Hi,

I have a new build vSphere environment. It's vSphere Essentials Plus 4.1. If I connect to the ESXi host directly using the VIC, everything works fine. If I connect to the vC, the host is disconnected when I log in. I reconnect it, but within a minute it's disconnected again. I've restarted the mgmt agent on the ESXi host, rebooted vC and then rebooted the ESXi host. The problem still persists. I'm not seeing anything useful in the logs. Any ideas?

The hosts disconnects at about 11:33:20 or 21.

ESXi host - /var/log/vmware/vpx/vpxa.log

====

Could not translate vpxd counter 217, metric omitted.

HTTP Response: Complete (processed 1672 bytes)

-- FINISH task-internal-52 -- -- vpxapi.VpxaService.querySummaryStatistics -- 52faab34-644d-970c-f937-0d023d68a602

User agent is 'VMware-client/4.1.0'

HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength 129)

HTTP Response: Auto-completing at 129/129 bytes

Unexpected return result. Expect 1 sample, receive 2

Received callback in WaitForUpdatesDone

Applying updates from 131 to 132 (at 131)

HostChanged Event Fired, properties changed http://runtime.healthSystemRuntime

Received callback in WaitForUpdatesDone

Applying updates from 132 to 133 (at 132)

Received change notification from hostd ...

Got 1 updates from hostd

Got 1 property change for root pool

Got summary change for root pool

Change is within threshold, returning true

root capacity change is below threshold, returning

Unexpected return result. Expect 1 sample, receive 2

Unexpected return result. Expect 1 sample, receive 2

====

vCenter Server - vpxd-7.log

====

VM vim.VirtualMachine:vm-65: config changed, invalidating cache...

Marked 192.168.0.21 as dirty.

[2010-10-12 11:32:11.367 02292 info 'vmomi.soapStub Resetting stub adapter for server TCP:192.168.0.21:443 : Closed

-- FINISH task-67 -- host-61 -- vim.HostSystem.reconnect -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-394 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-394 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-395 -- -- vmodl.query.PropertyCollector.Filter.destroy -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-395 -- -- vmodl.query.PropertyCollector.Filter.destroy -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-396 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-396 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

Next switch time = 299992999ms later,

-- BEGIN task-internal-397 -- host-61 -- vim.HostSystem.acquireCimServicesTicket -- 44A585FB-8B98-46C7-8E15-8B596025B9BD(E2E9807E-D5BF-4A09-8844-82140F729B0F)

-- FINISH task-internal-397 -- host-61 -- vim.HostSystem.acquireCimServicesTicket -- 44A585FB-8B98-46C7-8E15-8B596025B9BD(E2E9807E-D5BF-4A09-8844-82140F729B0F)

-- BEGIN task-internal-398 -- host-61 -- VpxdInvtHostSyncHostLRO.Synchronize --

-- FINISH task-internal-398 -- host-61 -- VpxdInvtHostSyncHostLRO.Synchronize --

-- BEGIN task-internal-399 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-399 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-400 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-400 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-401 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-401 -- -- vmodl.query.PropertyCollector.retrieveContents -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-402 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-402 -- -- vim.LicenseAssignmentManager.queryAssignedLicenses -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- BEGIN task-internal-403 -- -- ScheduledTaskLRO --

-- FINISH task-internal-403 -- -- ScheduledTaskLRO --

-- BEGIN task-internal-404 -- -- vim.DiagnosticManager.queryDescriptions -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

-- FINISH task-internal-404 -- -- vim.DiagnosticManager.queryDescriptions -- 45A686CE-491D-424B-80BD-D6B9FFF8329D(7710AF85-ABBF-4D32-AB42-2C527CBA15EC)

2 threads doing remote collection

Next switch time = 299989999ms later,

====

TIA

Julian.

[julian2]

I've built a 2nd ESXi 4.1 host and added it to vCenter. It is showing as disconnected at the same time as the original ESXi host.

[julian2]

I've uninstalled vCenter, rebooted, reinstalled vCenter and rebooted and still have the same problem.

[athlon_crazy · Accepted solution]

Do you have firewall in beween?

Hope this KB can help you

[pcerda]

Hi,

Have you tried to reinstall the vCenter Agent on ESXi hosts and then add them again into vCenter?

Check out this link:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100371...




Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[dkraut]

Julian, please check DNS settings on the host and vcenter. Can you ping the Host by name from the vcenter server? Also, make sure vcenter is setup with a single NIC, or if dual NIC, make sure they are teamed properly.

[julian2]

Thank you all!

There is no discrete firewall between the vC and the nodes, but there is a Windows Firewall. The vC machine was a fresh build of W2008 Std 64bit and either one of the security updates or SP2 set the firewall to "Block incoming requests". After turning this option off, the environment has run all night without issue.

Your help is much appreciated!