It might be so, if the userid for an VM Manager is valid (ie it can be used to successfully login in to a vCenter), but does not have the rights to see the computers you need to have the information about.
That is why you should check what is in the vmman_scan_* files.
If they does not exists or are older then 12h, probably there is a problem with to connect.
But if the do exist, but not contain any of the UUID of you computers, then the userid for the VM Manager does not have the rights to see them.
Search all of the vmman_scan_* files for UUID’s that are flagged for no vm manager data.
(See https://www.ibm.com/support/knowledgecenter/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/admin/t_obtaining_the_list_of_virtual_machines_uuids.html how to obtain the UUID of your computers. If there are computers flagged for no vm data, there is a link in the Overview panel in th ILMT WebUI, and in one of the columns the will see a TLM_VM_xxxxxx value, where the xxxxxx is the UUID)
If not found, in any of the files, it will not be transported to ILMT, ie the WebUI.
The steps before ILMT knowns anything about the VM Manager is:
- The java process collects the information to vmman_scan_* files
- Every 12 hour all these files are zipped together and uploaded to the BigFix server
- At the next import (usually at midnight) the data is imported to the ILMT database and seen in the WebUI.
Check in the import log (from the WebUI) for some lines not far from the bottom:
2020-09-03 22:01:33 (+0:00:00.002) INFO: ETL Validate Central VM Manager Tool Remote ID: Start
2020-09-03 22:01:33 (+0:00:00.100) INFO: ETL Validate Central VM Manager Tool Remote ID: Success
2020-09-03 22:01:33 (+0:00:00.003) INFO: ETL from ImportVmManScans: Start
2020-09-03 22:01:49 (+0:00:16.498) INFO: [ILMTCore] (ImportThread) com.ibm.ilmt.core.ILMTCoreVMMan::printStatistics::STATISTICS: 164 files from 5 VM Managers were processed. Processed clusters: 368, skipped clusters: 3510, processed hosts: 962, skipped hosts: 6770, processed guests: 1064 (includes 0 guests without VM hierarchy changes and 1037 without any changes), skipped guests: 32983, duplicated guests: 0
2020-09-03 22:01:50 (+0:00:00.115) INFO: ETL from ImportVmManScans: Success
If there are no such lines, or no imported files/VM Managers, then step 2 did not work.
You can then try to run the fixlet that forces the VM Manager data upload, make a manual import.