ZakiYoussef asked a question.
Integration with VMware Vsphere can't detect a ESXI host.
Dears,
Integration between Snow and VMware Vsphere has been configured and all required data is retrieved to SLM, but in one of Data Centers it can detect all ESXI hosts except one ESXI host although it has the same configuration. does any one face the same issue before? how to troubleshoot this issue?
SIM : 5.28.0
SLM : 9.12.01
Regards,
Zaki
Is this one host part of a cluster in vCenter? or is it a standalone host.
If the latter then if you look in the SLM SMACC in basic settings for the Enable DCC setting you'll also see a minimum hosts setting below it. By default this is set to 2 and should be lowered to 1 to catch any standalone hosts.
Hello Joe.
thanks for your answer, it is not a standalone host it is a part of a datacenter which All other hosts are visible to Snow but only this host can't not be retrieved although it is the same configuration.
Hi Zaki,
If Joe's answer above does not resolve it for you, then you need to focus on the SIM logs to see if the host is actually been inventoried.
I have seen a similar issue a number of times in the past. Each time I found in the SIM logs that there were 2 hosts reporting in and that one had been been renamed in the Vsphere client.
In VMware you can rename the host in the GUI, but that does not rename the underlying objects.
For example, let say you have a host called HOST10. This would show in Snow as HOST10
Then a few months later somebody builds a new host, and calls it HOST10 (by mistake)
Once they realise the duplicate names - they rename it in the VCenter and it looks ok in VMWare.
However this HOST will not show in Snow until it is fully renamed using the VMware solution mentioned below.
The Snow VMware Connector will always report the name of the underlying VM datastore objects, this name must exactly match with the HostName reported by the Windows agent.
This VMware KB article provides some resolution advice. If this is your issue
https://kb.vmware.com/s/article/1029513
BTW - this is a farily easy fix and does not require any HOST downtime.
Tom
Thank you Tom for your valuable information, but I confirmed from Data Center team that the the host name is unique and they didn't rename it or create a host with the same name before, I am surprised that the vCenter integrated with Snow has 15 hosts all are reporting normally except one although it is the same configuration.
Regards,
Zaki
Hi Zaki,
If that is the case you need to go through step by step and work out where it is going wrong.
Go through the SIM logs that I mentioned above, verify that the host is mentioned and that guests are being detected.
If it is NOT being inventoried , then you need to revisit why not in VMware.
If it is being inventoried, then you need to look at what is happening when that data reaches your Snow inventory server. That opens up so many more possibilities.
Let us know how you get on.
Tom
Hi Zaki,
Another reason could also be, the user that you use for connecting to Vcenter is restriced and cannot see all that hosts.
You could test this, when you open the URL configured in your SIM (without the /sdk) and user the userid and password you got from your colleagues.
Then you can see if all the expected hosts are available
And like Tom mentioned, check the SIM logs. But first you should increase the loglevel in SIM to "All", You can find this in SIM in Logging tab.
Then SIM Log then will write every detected host in C:\Program Files\Snow Software\Logs\Snow Integration Manager\*.log
sim_svc*.log are the logs created by the scheduled scan
sim_gui*.log are the logs created by SIM manual aggregation.