Hello Jakub,
'default_not_initialized' is not an error, it's just an ambiguous string.
That sample output looks OK.
Do you see any 'vmman_scan_xxx.xml' files in '..\VMMAN\upload' folder ?
If so, do they have an <status>OK</status> ?
If you don't see any 'vmman_scan_xxx.xml' files conduct the following steps from command line :
vmman.<sh/bat> -stop
delete the "..\VMMAN\cache\status.xml" file
vmman.<sh/bat> -runwithoutservice
Check the '..\VMMAN\upload' folder...
At last, pls. upload the screenshot from 'Management: VM Managers' panel...
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message:
Sent: Fri March 15, 2024 07:07 AM
From: Jakub Kania
Subject: VMMAN tool gathering VMs only with default_not_initialized state
Hi,
We are using Local deployment of VMMAN version 9.2.34.
Connections to out VCenters retuns only VMs with State default_not_initialized. We cant see any Online ones. This creates Missing VM manager problem for all our online VMs.
Here is the sample of output returned by API.
<guest_layer>
<uuid>42304f91-c5af-3f98-6b54-3262f7b9d28e</uuid>
<vp_count>8</vp_count>
<state>default_not_initialized</state>
<virtual_technology>VSphere</virtual_technology>
</guest_layer>
In addition we have checked the VCenter Client console on the user configured in VMMAN tool and I can confirm that all VMs (including Online ones) are visible in VCenter client.
BR,
Jakub Kania
------------------------------
Jakub Kania
------------------------------