VMware vCenter Topology by vim Job is not pulling network CITs or license CITs from vCenter

[Diabolos]

We are currently at uCMDB version 10.01 CUP2.145, Content Pack 12.0.825. The vCenter environment is 5.0

Below are the VMware CI Types we are receiving.

VMware Cluster

VMware DAS Config

VMware Datastore

VMware ESX Server

VMware Host Resource

VMware VirtualCenter

Below is the snippet from the communication log. There are of course no authentication errors in the log and the VMware team assures me the service account we are using has system.read and global.licenses permissions.

 <log start="15:36:58" severity="debug">Connected to VMware server, type VirtualCenter, version 5.0, client type JAX_WS</log>
 <log start="15:36:58" severity="debug">Found 1 datacenter</log>
 <log start="15:36:58" severity="debug">Datacenter 'datacenter'</log>
 <log start="15:36:58" severity="debug"> ... Cluster 'Cluster ProdQA'</log>
 <log start="15:36:59" severity="debug"> ...... 3 hosts</log>
 <log start="15:37:00" severity="debug"> ......... VMs total = 28, powered off = 0, no host key = 0, skipped = 0</log>
 <log start="15:37:00" severity="debug"> ...... 28 virtual machines</log>
 <log start="15:37:00" severity="debug"> ... Cluster 'Cluster PCI'</log>
 <log start="15:37:01" severity="debug"> ...... 2 hosts</log>
 <log start="15:37:01" severity="debug"> ......... VMs total = 3, powered off = 0, no host key = 0, skipped = 0</log>
 <log start="15:37:01" severity="debug"> ...... 3 virtual machines</log>
 <log start="15:37:01" severity="debug"> ... Cluster 'Cluster DMZ'</log>
 <log start="15:37:01" severity="debug"> ...... 2 hosts</log>
 <log start="15:37:01" severity="debug"> ......... VMs total = 10, powered off = 1, no host key = 0, skipped = 1</log>
 <log start="15:37:01" severity="debug"> ...... 9 virtual machines</log>
 <log start="15:37:01" severity="debug"> ... 3 clusters</log>
 <log start="15:37:01" severity="debug"> ...... 7 datastores</log>
 <log start="15:37:01" severity="warn">Query returned no result</log>
 <log start="15:37:01" severity="warn">Query returned no result</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'ProdQA-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'ProdQA-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'ProdQA-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'PCI-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'PCI-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'DMZ-VDS'</log>
 <log start="15:37:02" severity="warn">Cannot find DVS by name 'DMZ-VDS'</log>
 <log start="15:37:02" severity="debug"> -- Sending vector of 429 objects</log>
 <log start="15:37:03" severity="debug"> -- Sending vector of 5 objects</log>
 <DISCONNECT start="15:37:03" duration="8" CMD="client_disconnect" RESULT="" IS_NULL="Y" type="vmware" credentialsId="31_1_CMS" />

Any ideas?

[Dima Gomel]

Could you please leaborate on the problem and/or your expectations? 

[Diabolos]

Hello Dima,

The VMware vCenter Topology by VIM Job is not discovering the following CI Types. reportBasicTopology is set to false. We would like to obtain this information.

Licence Feature

License Reservation

License Server

VMware DRS Config

VMware Distributed Virtual Switch

VMware Networking Policy

VMware Port Group

VMware Resource Pool

VMware Uplink

VMware Virtual Switch

[Dima Gomel]

Hi,

Take a look at attached document on p.208.

It will help you to find what you could expect from the discovery job.

Existence of specific CIT not always meaning all of them will be populated with discovery.

After setting expectations, please run discovery against destination where you could expect discoverign of specific CIs (according to VMware admins).

Set Create communication log on the pattern for "Always" and Include Results to Yes (see attached screenshot).

After you could rerun the job for specific vCenter and analyse communication log.

It will contains both commands that were sent to vCenter and answers that were received back.

You could after analyse the results with your VMware admin.

If you still think you have a problem, please raise the support case.

PLease be aware that Update packages for CP12 have several fixes in VMware area. It mostly related to discovery of VMware 5.1 but could be benefitials for you as well.

Hope thi shelps.

[Dima Gomel]

UD Content Pack 12 Update 3 for UCMDB 10.01 CUP 2(or higher CUP)