Isolate the Component making API Calls to vCenter

  • Post category:VMware / Vmware vSphere
  • Post last modified:July 25, 2024

In Some cases you might need to find the Machine(IP Address) which is making Incorrect call to the vCenter Server.

  • For Example in the below example i can see API Calls for “queryCmmds” and “queryVsanStatistics” in VPXA Logs:
vpxa[2106080] [Originator@6876 sub=vpxLro opID=6e601d4d-8f] [VpxLRO] -- BEGIN lro-953323 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryCmmds -- 527d6ceb-cc40-77c1-8741-266051d8f986
vpxa[2104916] [Originator@6876 sub=vpxLro opID=3d8e3c5d-60] [VpxLRO] -- BEGIN lro-953334 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryVsanStatistics -- 527d6ceb-cc40-77c1-8741-266051d8f986
vpxa[2104930] [Originator@6876 sub=vpxLro opID=1d64eccf-e1] [VpxLRO] -- BEGIN lro-953335 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryVsanStatistics -- 527d6ceb-cc40-77c1-8741-266051d8f986
vpxa[2104914] [Originator@6876 sub=vpxLro opID=73a2be78-eb] [VpxLRO] -- BEGIN lro-953337 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryCmmds -- 527d6ceb-cc40-77c1-8741-266051d8f986
vpxa[2104910] [Originator@6876 sub=vpxLro opID=7feb0b11-df] [VpxLRO] -- BEGIN lro-953338 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryVsanStatistics -- 527d6ceb-cc40-77c1-8741-266051d8f986
vpxa[2106294] [Originator@6876 sub=vpxLro opID=bb10f60-40] [VpxLRO] -- BEGIN lro-953346 -- ha-vsan-internal-system -- vim.host.VsanInternalSystem.queryCmmds -- 527d6ceb-cc40-77c1-8741-266051d8f986
  • To get the session ID for these API Calls, you can initiate a search in vpxd-profiler.log using the below command:
grep -Ei 'queryCmmds|queryVsanStatistics' vpxd-profiler.log | grep -i threadstate
  • The output should be like this:
ThreadState/ThreadId/58192/State/Task::lro-62488727::ha-vsan-internal-system-2687::vim.host.VsanInternalSystem.queryVsanStatistics::52bd547c-a4c9-7d28-e6c1-fabb3fa83ad8(526cb8c5-bbf5-d8e8-0a82-1a3b8db2468f)/State/RPC::vim.host.VsanInternalSystem:ha-vsan-internal-system::[host name]::vim.host.VsanInternalSystem.queryVsanStatistics
  • In this example 52bd547c-a4c9-7d28-e6c1-fabb3fa83ad8 is the session ID
  • To get the IP Address of the Machine making this API Call run the below command:
grep 52bd547c-a4c9-7d28-e6c1-fabb3fa83ad8 vpxd-profiler-389.log | grep -i 'Session/Id'
  • The output should be like 
/SessionStats/SessionPool/Session/Id='52bd547c-a4c9-7d28-e6c1-fabb3fa83ad8'/Username='XXX'/ClientIP='10.122.1.164'
  • IP Address which were making the API Calls was ‘10.122.1.164’

Ashutosh Dixit

I am currently working as a Senior Technical Support Engineer with VMware Premier Services for Telco. Before this, I worked as a Technical Lead with Microsoft Enterprise Platform Support for Production and Premier Support. I am an expert in High-Availability, Deployments, and VMware Core technology along with Tanzu and Horizon.

Leave a Reply