VMware Cloud Community
amb7
Contributor
Contributor
‎10-25-2016 08:54 PM

vCenter Server Connection

Hello-

I have two ESXi units running 5.1.0, 799733. One unit (unit A) has, among other vm's, vCenter Server appliance 5.1.0.5200 Build 880472. When I connect to the vCenter Server with vSphere Client I can add one ESX unit (unit B) with no issue. When adding the other (unit A) I get 88% of the way through before vSphere Client disconnects. When I reconnect to vCenter Server with vSphere client, unit B is connected but unit A is not and says disconnected. When I right click on it and select connect vSphere looses connection. After the lost connection dialog goes away I get this:

Screen Shot 2016-10-25 at 10.32.49 PM.png

Logging on the server when trying to reconnect is below. Of interest are the lines that look like:

2016-10-26T03:31:06.852Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 2 on host 10.1.10.242 - COULD NOT FIND IT

I have tried running vCenter Server on both unit A and B. Regardless of the appliance's location, it still fails to connect to unit A. This would eliminate any network issues. I have compared my settings on both ESX units and they are identical aside from hostname and IP.

Any thoughts?

Thanks in advance.

-Andrew

-------------

2016-10-26T03:30:54.063Z [7FEC56B25700 info 'commonvpxLro' opID=B25B57F6-0000009C-e] [VpxLRO] -- BEGIN task-284 -- host-183 -- vim.HostSystem.reconnect -- 6a69da40-c805-daa9-416f-c75f7ac28920(525e7277-6d6a-068b-e38e-dc515c113773)

2016-10-26T03:30:54.119Z [7FEC560C2700 info 'commonvpxLro' opID=B25B57F6-0000009E-7] [VpxLRO] -- BEGIN task-internal-237 --  -- vmodl.query.PropertyCollector.createFilter -- 6a69da40-c805-daa9-416f-c75f7ac28920(525e7277-6d6a-068b-e38e-dc515c113773)

2016-10-26T03:30:54.120Z [7FEC560C2700 info 'commonvpxLro' opID=B25B57F6-0000009E-7] [VpxLRO] -- FINISH task-internal-237 --  -- vmodl.query.PropertyCollector.createFilter --

2016-10-26T03:30:54.552Z [7FEC56B25700 info 'vpxdvpxdHostAccess' opID=B25B57F6-0000009C-e] Got VpxaCnxInfo over SOAP version vpxapi.version.version8 for host 10.1.10.242

2016-10-26T03:30:54.552Z [7FEC56B25700 info 'vmomi.soapStub[19]' opID=B25B57F6-0000009C-e] Resetting stub adapter for server <cs p:00007fec680b69e0, TCP:10.1.10.242:443> : Closed

2016-10-26T03:30:57.494Z [7FEC56B25700 info 'vpxdvpxdHostAccess' opID=B25B57F6-0000009C-e] Got VpxaCnxInfo over SOAP version vpxapi.version.version8 for host 10.1.10.242

2016-10-26T03:30:57.494Z [7FEC56B25700 info 'vmomi.soapStub[20]' opID=B25B57F6-0000009C-e] Resetting stub adapter for server <cs p:00007fec6860bc80, TCP:10.1.10.242:443> : Closed

2016-10-26T03:30:57.495Z [7FEC56B25700 info 'vpxdvpxdHostUpgrader' opID=B25B57F6-0000009C-e] [CheckVpxaCorrectVersion] Preinstalled vpxa bundle found: not installing

2016-10-26T03:30:57.521Z [7FEC56B25700 info 'vpxdvpxdHostAccess' opID=B25B57F6-0000009C-e] Got VpxaCnxInfo over SOAP version vpxapi.version.version8 for host 10.1.10.242

2016-10-26T03:30:57.521Z [7FEC56B25700 info 'vmomi.soapStub[21]' opID=B25B57F6-0000009C-e] Resetting stub adapter for server <cs p:00007fec68161660, TCP:10.1.10.242:443> : Closed

2016-10-26T03:30:57.524Z [7FEC56B25700 info 'vpxdvpxdInvtHostDb' opID=B25B57F6-0000009C-e] [VpxdInvtHost::SaveFieldsToDb] IPMI info of host 10.1.10.242 is not set

2016-10-26T03:30:57.556Z [7FEC56B25700 info 'vpxdvpxdHostUpgrader' opID=B25B57F6-0000009C-e] [VpxdHostUpgrader] Preinstalled bundle found: not installing

2016-10-26T03:30:57.884Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vpxapi.VpxaService.retrieveChanges)

2016-10-26T03:30:57.886Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.createFilter)

2016-10-26T03:30:57.887Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:00.498Z [7FEC56144700 info 'vpxdvpxdVmomi' opID=SWI-472cd69b] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.10.10.242, vpxapi.VpxaService.fetchQuickStats)

2016-10-26T03:31:01.238Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:01.270Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:01.273Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:01.281Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:01.651Z [7FEC55C71700 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.waitForUpdates)

2016-10-26T03:31:01.665Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.Filter.destroy)

2016-10-26T03:31:01.667Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vmodl.query.PropertyCollector.cancelWaitForUpdates)

2016-10-26T03:31:01.669Z [7FEC56B25700 info 'vpxdvpxdMoLicenseManager' opID=B25B57F6-0000009C-e] [LicMgr] Downloading Dlfs for Host 'VMware ESX Server', Version: '5.0', File Version: '5.1.0.11', Dlf Directory Location: '/etc/vmware-vpx//licenses/site//VMware ESX Server/5.0/5.1.0.11'

2016-10-26T03:31:01.670Z [7FEC56B25700 info 'vpxdvpxdMoLicenseManager' opID=B25B57F6-0000009C-e] [LicMgr] Re-acquiring licenses for Host 'host-183'.Old Host Type: 'embeddedEsx', Old License Product Name: 'VMware ESX Server', Old Version: '5.1.0',Old License Product Version: '5.0', Old File Version: '5.1.0.11',New Host Type: 'embeddedEsx', New License Product Name: 'VMware ESX Server', New Version: '5.1.0',New License Product Version: '5.0', New File Version: '5.1.0.11'

2016-10-26T03:31:01.671Z [7FEC55EBA700 info 'vpxdvpxdMoLicenseDataManager' opID=B25B57F6-0000009C-e-SWI-1aeccd1b] [LicenseDataManager::Processor] Processed auto-assigned licenses for host 10.1.10.242

2016-10-26T03:31:05.506Z [7FEC56B25700 warning 'VpxProfiler' opID=B25B57F6-0000009C-e] ClientAdapterBase::InvokeOnSoap: (10.1.10.242, vpxapi.VpxaService.setServer) [SoapRpcTime] took 3834 ms

2016-10-26T03:31:05.506Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vpxapi.VpxaService.setServer)

2016-10-26T03:31:05.510Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vim.HostSystem.GetConfigManager)

2016-10-26T03:31:05.636Z [7FEC56B25700 info 'vpxdvpxdVmomi' opID=B25B57F6-0000009C-e] [ClientAdapterBase::InvokeOnSoap] Invoke done (10.1.10.242, vim.EnvironmentBrowser.queryProvisioningPolicy)

2016-10-26T03:31:06.491Z [7FEC56B25700 info 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::SetComputeCompatibilityDirty] Marked host-183 as dirty.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports EVC mode intel-merom.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports EVC mode intel-nehalem.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports EVC mode intel-penryn.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports EVC mode intel-sandybridge.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports EVC mode intel-westmere.

2016-10-26T03:31:06.514Z [7FEC56B25700 info 'vpxdvpxdMoTransEVCManager' opID=B25B57F6-0000009C-e] [MoTransEVCManager::GetMaxModeForHostCapabilities] 10.1.10.242 supports a maximum EVC mode of intel-sandybridge.

2016-10-26T03:31:06.801Z [7FEC56B25700 warning 'MoLock' opID=B25B57F6-0000009C-e] ***WARNING*** Lock domain-s181 mode EXCLUSIVE held for 1164 ms

2016-10-26T03:31:06.823Z [7FEC56B25700 warning 'MoLock' opID=B25B57F6-0000009C-e] ***WARNING*** Lock host-183 mode EXCLUSIVEALL held for 1187 ms

2016-10-26T03:31:06.841Z [7FEC55EBA700 info 'commonvpxLro' opID=B25B57F6-0000009C-e-de] [VpxLRO] -- BEGIN task-internal-238 --  -- update-localization-catalog --

2016-10-26T03:31:06.841Z [7FEC55EBA700 info 'Localization' opID=B25B57F6-0000009C-e-de] [VpxdUpdateLocaleLro::ProcessHostUpdate]Processing update for host

2016-10-26T03:31:06.841Z [7FEC55EBA700 info 'commonvpxLro' opID=B25B57F6-0000009C-e-de] [VpxLRO] -- FINISH task-internal-238 --  -- update-localization-catalog --

2016-10-26T03:31:06.841Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 2 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.841Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 3 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.841Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 4 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.842Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 2 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.842Z [7FEC56B25700 info 'vpxdvpxdInvtVm' opID=B25B57F6-0000009C-e] [VpxdInvtVm] Looking up vm ds:///vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Database/R2 Database.vmx by local cfgPath /vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Database/R2 Database.vmx

2016-10-26T03:31:06.843Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 3 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.850Z [7FEC56B25700 info 'vpxdvpxdInvtVm' opID=B25B57F6-0000009C-e] [VpxdInvtVm] Looking up vm ds:///vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Terminal Server/R2 Terminal Server.vmx by local cfgPath /vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Terminal Server/R2 Terminal Server.vmx

2016-10-26T03:31:06.851Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 4 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.852Z [7FEC56B25700 info 'vpxdvpxdInvtVm' opID=B25B57F6-0000009C-e] [VpxdInvtVm] Looking up vm ds:///vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/vCenter Server 5.1/vCenter Server 5.1.vmx by local cfgPath /vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/vCenter Server 5.1/vCenter Server 5.1.vmx

2016-10-26T03:31:06.852Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 2 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.853Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 3 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.853Z [7FEC56B25700 warning 'vpxdvpxdMoHost' opID=B25B57F6-0000009C-e] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 4 on host 10.1.10.242 - COULD NOT FIND IT

2016-10-26T03:31:06.900Z [7FEC56B25700 info 'vmcheckclusterChecker' opID=B25B57F6-0000009C-e] [CheckChangePropertiesInt] Property Modified config

2016-10-26T03:31:06.903Z [7FEC56B25700 warning 'utilvpxdDbSave' opID=B25B57F6-0000009C-e] [VpxdDbSave] Skipping PropertyPath: hardware.device.slotInfo.pciSlotNumber

2016-10-26T03:31:06.903Z [7FEC56B25700 warning 'utilvpxdDbSave' opID=B25B57F6-0000009C-e] [VpxdDbSave] Skipping PropertyPath: hardware.device.slotInfo.pciSlotNumber

4 Replies
brunofernandez1
Expert
Expert
‎10-26-2016 04:14 AM

I think I have found your problem Smiley Happy do you have a vm with a lot of snapshots?

vSphere Client fails when adding the ESX/ESXi host to vCenter Server Appliance (2034504) | VMware KB

------------------------------------------------------------------------------- If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards from Switzerland, B. Fernandez http://vpxa.info/
0 Kudos
amb7
Contributor
Contributor
‎10-26-2016 06:17 AM

Brunofernadez1-

Thank you for the response. I came a across that article but just checked one more time. Within the xml I have the 3 machines, which are all valid, and no snapshots. Here is the xml:

<ConfigRoot>

  <ConfigEntry id="0000">

    <objID>1</objID>

    <vmxCfgPath>/vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Database/R2 Database.vmx</vmxCfgPath>

  </ConfigEntry>

  <ConfigEntry id="0001">

    <objID>2</objID>

    <vmxCfgPath>/vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/R2 Terminal Server/R2 Terminal Server.vmx</vmxCfgPath>

  </ConfigEntry>

  <ConfigEntry id="0002">

    <objID>3</objID>

    <vmxCfgPath>/vmfs/volumes/4fcfab4a-03d27dc4-cfe4-9c8e994f0e70/vCenter Server 5.1/vCenter Server 5.1.vmx</vmxCfgPath>

  </ConfigEntry>

</ConfigRoot>

Looking at this again it has me thinking. Does the ID match the vmid that is in logging? From what I read, logging is failing to locate vmid 2,3 and 4 however there is no id's in the xml document for those. Is it possible vServer is looking for VM's that do not exist? Any ideas on how to check that?

0 Kudos
brunofernandez1
Expert
Expert
‎10-26-2016 06:31 AM

sorry can't check this because I don't have any VCSA environment to compare with...

------------------------------------------------------------------------------- If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards from Switzerland, B. Fernandez http://vpxa.info/
amb7
Contributor
Contributor
‎10-26-2016 06:43 AM

I also forgot to mention, I can use vSphere Client to connect directly to unit A without issue. It even says it's being managed by VCSA. I have tried to disassociate and start over with no luck.

0 Kudos