Troubleshooting and Limitations – VMware vCenter Topology by VIM Job
Troubleshooting
-
Problem: The following error message is displayed when an operation cannot be performed due to lack of permissions:
User does not have required '<permission>' permission
Solution: Check that permissions are set as System.Read.
Problem: The following error message is displayed when credentials are not correct:
Invalid user name or password
Problem: The following warning message is displayed in the Communication log during discovery:
VM '<name>': powered off, VM is skipped
Solution: This message indicates that the discovery found a powered-off VM. By default, powered-off VMs are not reported, mainly because the configuration of such powered-off VMs may be outdated. This outdated information can impact the identification of the VMs, so the topology reported might be incorrect.
For example:
-
The MAC address of one of the interfaces might now be assigned to different VMs, yet still be listed for the powered-off VM.
-
The IP address might still be listed for the powered-off VM, but was reassigned to different machine by the DHCP server before discovery began.
If you still want powered-off VMs to be reported, set the topology job's reportPoweredOffVMs parameter to true.
Problem: The following warning message is displayed in the Communication log during discovery:
Host '<name>': cannot find UUID, Host is skipped
Solution: The UUID of the ESX server is a key attribute for the ESX server CI. It is not possible to report ESX server without a valid UUID. A UUID of the ESX server that consists of all zeros is also considered invalid. The message in the Communication log indicates that the specified ESX server was discovered but was skipped due to a missing or invalid UUID.
Problem: The following warning message is displayed in the Communication log during discovery:
VM '<name>': duplicate host key '<key>' found in another VM '<name>' which was preferred, VM is skipped
Solution: After all VMs are discovered, VMs containing duplicated host keys are filtered out. host_key is a key attribute of the VM, so it is not possible to report two VMs with the same host keys. The message in the Communication log indicates that there were duplicates found and one of the duplicated VMs was skipped.
If the reportPoweredOffVMs parameter is set to true, if the two VMs have different power statuses, the powered-on VM is preferred over the powered-off VM.