UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Micro Focus Contributor
Micro Focus Contributor
771 views

(UCMDB Support Tip) - VMware vCenter Topology by VIM job has warnings and not finishing successfully

Issue:

While discovering 15 vCenters out of which 12 fail with warnings similar to the below message. Due to this, VMware ESX Servers and related CIs are not getting discovered.

Error details are below.

<< Progress message, Severity: Warning>>Warning processing results: Results contain ignored CIs. For details please check cmdb.reconciliation.log. There were ignored CIs: From Class [containment] 2 CIs were ignored due to Link with ignored end; From Class [usage] 2 CIs were ignored due to Link with ignored end; From Class [interface] 2 CIs were ignored due to Multiple Match; << Progress message, Severity: Warning>>Warning processing results: Results contain ignored CIs. For details please check cmdb.reconciliation.log. There were ignored CIs: From Class [containment] 94 CIs were ignored due to Link with ignored end; From Class [usage] 95 CIs were ignored due to Link with ignored end; From Class [interface] 95 CIs were ignored due to Multiple Match; << Progress message, Severity: Warning>>Job was running more than 900000 msec*** 

Workaround:

The issue is due to the fuse sizes being reached. The job is sending a very large number of CIs, that is causing this scenario.

From the VMware Virtual Center Topology by VIM job, it is collecting and creating LUN and iscsi information which is impacting the fuse.

A defect "#QCCR1H125480 Add a parameter reportLUN for VMware vCenter Topology by VIM job" is logged for this functionality.

In the meantime, please contact support for further workaround where underlying code can be commented if LUNs do not need to be discovered. 

https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM03351317

MICRO FOCUS Software Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

Please hit the Kudo botton, if you find this post useful.

6 Replies
Vice Admiral
Vice Admiral

Out of 12 vCenter, we are facing an issue for one of the vCenter appliance, where VMware VirtualCenter Topology job by VIM is not working. New VMs are not getting populated. Error thrown is "Job was running more than 2700000 msec"

We tried with default value 900000 msec but  it failed with Fatal Error "Job was running more than 900000 msec"

and then increased it to 1800000 (Max. execution time) on discovery adapter but again it failed with Fatal Error "Job was running more than 1800000 msec"

We again then increased Max. execution time to 2700000 on discovery adapter but again it failed with Fatal Error "Job was running more than 2700000 msec"

Any workaround to resolve the issue ?

0 Likes
Lieutenant Lieutenant
Lieutenant

As per the Self-Solve Knowledge Search article (Document ID KM03351317) that happens in version 10.33, but I am observing the same behaviour on 2019.2.

Someone already have the same issue? 

 

Thanks!

Ivan

0 Likes
Micro Focus Expert
Micro Focus Expert

@RohitSS, the error is generic and it may have different causes.
It would be interesting to see the Communication log with results on a newer CP version. The VMware discovery flow is quite active in the past 6-8 CPs and it's relevant to test with the latest version. 
Maybe the job finishes in a timely manner but we have some garbage data there. Maybe reconciliation is talking too long due to various reasons. 

Because this is a job which retrieves a lot of data, it's not that difficult to make it unstable. There are options and this can be handled on Support side.



Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Micro Focus Expert
Micro Focus Expert

The problem can be mostly in the CP version. The server version would be relevant only for the reconciliation part.


Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Vice Admiral
Vice Admiral

It would be really helpful if we can know how to tweak VMware Vcenter Topology by VIM to make sure all the VMs and ESXi server from that problematic VMware vCenter appliance are discovered.

0 Likes
Micro Focus Expert
Micro Focus Expert

A good strategy is to stay close to the latest CP version. Virtualization and Cloud discovery was very active in the past years.

 

Another easy tweak is to set JVMargs parameterto -Xms512m -Xmx4096m -XX:MaxMetaspaceSize=1024m -XX:-UseGCOverheadLimit

You need about 2-3GB of Heap memory for each 1k discovered VMs. It varies and we don't yet have a golden formula for it.



Kind regards,
Bogdan Mureșan
EMEA CMS 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.