Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
287 views

VirtualCenter Topology by VIM

I'm getting the following error message when attempting to run the VCenter Topology by VIM job.  The host has already completed a Host Connection by Shell and and Inventory Scanner job but appears to be some reconciliation info.  Any ideas are appreciated.

FAILED!! [ID=1993955302] [Customer ID=1] [Changer=UCMDBDiscovery: MZ_VCenter Remediation_Inventory_InventoryDiscoveryWizard_Inventory Discovery by Scanner Probe: ITAM-027] [total= 0.795   , manipulation= 0.015   , identification= 0.718   , identification.query= 0.718   , identification.match= 0.000   , merge= 0.015   ]  [durations: identify= 0.718 dataIn= 0.015] [Ignore From Cmdb-  0 Ignore From Bulk-  0 Merge Operations-  0 Merged CIs-    0 Type Changes-    0 Max Topology Level- 1] [Datas to update-  620] [Referenced Data-    0] addOrUpdate    :  [Objects For Update- graphics_adapter(3) file_system_export(18) nt(3) logical_volume(6) winosuser(3) cpu(5) ip_address(4) interface(14) inventory_scanner(3) network_adapter(5) printer_driver(3) node(1) file_system(6) disk_device(14) memory_unit(136) installed_software(59) iscsi_adapter(3) physicalvolume(2) hardware_board(11)] [Links For Update- containment(8) composition(291) dependency(8) usage(3) membership(6) realization(5)] [Referenced Objects-] [Referenced Links-] Message:  level [1]! Object [$TempObject30ec66b93983d94223345bcf19800c0b] was not identified to itself (in bulk). Probably the reconciliation data is missing.'

Thanks,

0 Likes
5 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: VirtualCenter Topology by VIM

Object [$TempObject30ec66b93983d94223345bcf19800c0b] was not identified to itself (in bulk). 

This means that CI TempObject30ec66b93983d94223345bcf19800c0b is referenced somewhere in the bulk with its ID but never defined/present in the vector with its attributes.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: VirtualCenter Topology by VIM

Ok, so any hints at how to resolve?  I just tried deleting the node and rediscovering.  I'm hoping that a fresh discovery of the device will help.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: VirtualCenter Topology by VIM

You can manipulate a little bit the job parameters, this could help. It depends on the topology in the result vector.

I would use the CommLog with results to model the vector in the OSHV tool, it's an internal tool. There, with some patience, we could see what's the problematic CI.

 

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: VirtualCenter Topology by VIM

HOw do we get a hold of the OSHV tool? 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: VirtualCenter Topology by VIM

You get hired as a Support or RnD engineer. It's an internal tool. 
Strange enough, not one customer raised an ER for such a tool. If so, maybe it would have been developed to be customer available.

It's very useful in visualizing the vector in a graphical representation with the option to push CIs to a UCMDB.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.