Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
369 views

VMware Topology by VIM error

Jump to solution

Hello,

 

The both discoveries VMWare Topology by VIM (VMWare ESX Topology by VIM / VMWare vCenter Topology by VIM) is giving the error "... VMWare VIM: Internal error"

 

I have a ticket since august oppened and it wasn't fixed until now. Does anyone know how to solve this problem?

Started in the verion 10.33 and now it was updated to version 2019.05 and the problem still happening.

 

Thank you

Mariana

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: VMware Topology by VIM error

Jump to solution

It's a generic reconciliation error. I would guess that the identification map is empty because of excluded values.

What's the count from the JMX method retrieveExcludeValues ?

Either way, now discovery is running and you will have to figure out from the reconciliation logs why there is a bottleneck there. Support can help on this issue.

Also, from CP 2019.05 to CP 2019.11 we have 4 manjor code changes on the Vmware adapter. Maybe a CP upgrade would be useful. 

 

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success

View solution in original post

Tags (2)
67 Replies
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Dear Mariana,

Please share the communication logs for the job which is showing the internal error. That will help to find out exact issue you are facing.

Best Regards,

Rohit N.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: VMware Topology by VIM error

Jump to solution

Hello Mariana,

 

sharing Communication logs may not be wise as they can contain sensitive information.

What are the parameters used for the discovery jobs? Ițm particular interested in JVMargs.

Does it time out after 1800000ms?

 

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Hello,

The communicationLog is attached.

The sensitive information was changed.

 

Thank you for your help!

0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Hello,

I have no value set for this parameter, check the attached image attached.
The commLog is attached too.
 
Thank you.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: VMware Topology by VIM error

Jump to solution
This is a known issue and it was fixed in CP 2019.08 under the change request QCCR1H126581
File "vmware_vim", line 622, in onConnection
File "vmware_virtualcenter_topology_by_vim", line 44, in discoverVcenterTopology
File "_vmware_vim_base", line 1504, in discover
File "_vmware_vim_base", line 1317, in _discoverDatacenters
File "_vmware_vim_base", line 1554, in onDatacenter
File "_vmware_vim_base", line 2520, in reportManagedDatacenter
File "_vmware_vim_40", line 1023, in reportNetworking
File "_vmware_vim_base", line 2265, in reportNetworking
File "_vmware_vim_base", line 2242, in reportEsxNetworkingInComputeResource
File "_vmware_vim_base", line 2370, in reportConnectedSwitchPort
AttributeError: 'NoneType' object has no attribute 'getAttribute'

In adapter management search for the file modeling.py and remove the 2 lines around lines 962-963
else:
return None


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

Re: VMware Topology by VIM error

Jump to solution
As a good practice, try to use a value for JVMargs as it may crash due to insufficient memory resources
for JVMargs use
-Xms512m -Xmx4096m -XX:MaxMetaspaceSize=1024m -XX:-UseGCOverheadLimit


The general rule is Xmx to be 1GB for each 300-500 discovered VMs.
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Hello,

After delete the lines, I have another error, the commLog is attached.

 

Thank you for your help!!

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: VMware Topology by VIM error

Jump to solution
I see 2 vectors being sent log start="2019-11-18 10:16:59" severity="debug"> -- Sending vector of 23090 objects</log>
<log start="2019-11-18 10:17:04" severity="debug"> -- Sending vector of 14 objects</log>

The job ran succesfully. There is no problem on the latest provided CommLog.
It worked. What were your concerns?
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Hello,

Please, check the file attached, I explained the problem... the CIs that isn't appearing.

 

Thank you

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: VMware Topology by VIM error

Jump to solution
Hello Mariana,

May I presume that you are on CP 2019.05?
Splitting CIs based on datacenter was implemented only in CP 2019.08 so this means that the job will always send result in 2 bulks: the first is small (under 100 CIs) and the second will contain the VMware topology. The later one can crash due to the size of it, sometimes. From the past CommLog I see that it has 23k CIs so that shouldn't be a problem.

Did I udnerstood corectly that you are missing the virtualization_layer_software CIs?
Can you see how many candidates you have in the Remove ExecutionEnvironment links trigger TQL?
Can you see such CIs in the CommLog with results included?
If yes.can you rerun discovery after you cleared the results cache for the job?
As a best practice, please change the paraller thread count for this adapter to 1 (OOTB is blank and the probe value of 8 is used).


Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: VMware Topology by VIM error

Jump to solution

Yes, you're right, I'm on CP 2019.05.

Do you recommend upgrade to 2019.08?

 

I thought that the problem is virtualization_layer_software, if you check the doc that I sent, this CI is the connection between clusters, virtual machines and VMHosts, but I'm just telling what I'm seeing.

 

I didn't understand this comment "Can you see how many candidates you have in the Remove ExecutionEnvironment links trigger TQL?", because I have this option in the  Adapter Configuration with options "Auto Delete" and "Candidate for Deletion", how can I see how many have? I didn't find this option in TQLs (Modeling Studios) and Enrichment Manager. Could you explain me, please?

 

The threads that you are talking about is in the Execution Options in the Adapter Configuration? "As a best practice, please change the paraller thread count for this adapter to 1 (OOTB is blank and the probe value of 8 is used)."

 

Thank you so much for your help!!

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.