Vcenter pulling NDI with localhost

[durgeshsingh]

Hi

Anyone has faced this issue while flexera is pulling vcenter inventory from beacon. Some host NDI are coming with localhost.

[Steffen]

yes, we also having this issue on FNMS 2022R2, I even have (only a few) VMs linked to a host with the name "localhost" - but lots other VMs listed as "does not have a host"

Is there any solution by Flexera?

[durgeshsingh]

No. Even no one responded in community as well from flexera. If case will increase , we will raise a support case.

[mfranz]

Were you able to check the vCenter WebUI to check the source data? Also, did you check the resulting NDIs? I think I have seen some occasions where some fields in vCenter were not populated properly, that might translate into the inventory files?

[durgeshsingh]

Yes, have seen in vcenter & it showing correct name. Even in NDi also, its showing the correct hostname of host.

[Steffen]

for me Im getting lost in the WebGUI (https://[vCenter-IP]/mob)

But I just downloaded latest esxQuery tool
(https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/VMware-stand-alone-inventory-agent-for-FlexNet-Manager-Suite/ta-p/114055)

and the vCenter itself comes in by IP, but the the other ndi files as "localhost"

(x.xxx.xxx.33 at 20230602T134334 (VMware).ndi
localhost at 20230602T134331 (VMware).ndi
localhost at 20230602T134332 (VMware).ndi
localhost at 20230602T134333 (VMware).ndi

The are all different in size and contain quite some data...

First line looks like:

<Inventory Tracker="18.3" Audience="Machine" UserName="system" Hardware="True" Software="False" DateTime="20230602T134331" Type="Full" Scope="localhost" ServiceProviders="VMware">

I will create a support case here soon

[ryanhardcastle0]

Hi @Steffen 

Did you ever get an answer for this from support or elsewhere?  I'm experiencing exactly the same issue.

Ryan

[Steffen]

Hi Ryan,

beacuse of priorities I never opend up a CASE here...we are just starting to evaluate new OnPremRelease 2023R2 and after that - if problem is still around ...we will see....

greetings

Steffen

[Steffen]

Hi all - just to let you know - I just opened up a case here - will give further feedback once Flexera updates me... (case: #02817576)

[alicja01]

yes, we also having this issue on FNMS 2022R2, I even have (only a few) VMs linked to a host with the name "localhost" - but lots other VMs listed as "does not have a host

[Steffen]

Hi, I received some feedback from Flexera - apparently this is down to a missing DNS config on the vCenter...

Here is an extract out of the case:

From your ndi's we can see this is using the DNSHostName under the VMWARE_NetworkAdapterConfiguration section
Scope="localhost"
Name="DNSHostName" Value="localhost"/>
"HostIdentifier" Value="meXXXXX3esx9"/>

The only way to get this to work correctly is configure DNS in your vmware

see if you can Edit the DNS and IP Address Settings of the vCenter
https://kb.vmware.com/s/article/2122383

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcsa.doc/GUID-56C3BA9A-234E-4D81-A4BC-E2A37892A854.html

Alternatively As a temporary workaround
If you cannot update the field in vCenter, you can try and manually change the value for Scope on line 4 of the vCenter NDIs.

I'm still investigating with low prio...

[Steffen]

So,

finally I got this topic resolved. Unfortunatly Flexera Support could not explain to me, how the "wrong" localhost is reteived - I was hoping to get some instructions for the vCenter mob interface to validate this - but I failed. If you want Flexera to have correct hostnames (not localhost) the DNS Config inside the vCenter must be correct.

In my case this config is not present:

A vCenter Admin can view the SourceData, Flexera is using here:

greetings - Steffen