Highlighted
Absent Member.. Absent Member..
Absent Member..
156 views

Discovering VMWARE Infrastructure

Hi, we are trying to discover the infrastructure and most possible information related to a VMWARE.

 

1) We configured the VMWARE Vim credentials and received connection successful when we tested it (had to modify the timed out to make it work).

2) Created the management zone.

3) Created an Infrastructure Discovery activity and added the VMWare Vim credentials.

4) Created a Virtualization Discovery activity and added the VMWare Vim credentials.

5) Run both jobs without success.

 

What are we missing?

 

Best regards,

Damian.

 

0 Likes
7 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Discovering VMWARE Infrastructure

Isnt it still a prerequisite to add the Vmware .jar files to the probe?

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Discovering VMWARE Infrastructure

Hello Damian , 

 

I hope you are doing well .

 

This guide will help you when you need information of the VMWARE :

 

https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00642633

 

In this guide we can find this link : 

https://developercenter.vmware.com/web/sdk/5.5.0/vcloud-java

 

Best Regards , 

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Discovering VMWARE Infrastructure

 Both vim.jar and vim25.jar were added into the discovery job. Whats strange is that nothing is displayed into discovery status, like it doesnt exist.

 

Regards,

Damian

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Discovering VMWARE Infrastructure

The VMware jobs trigger CI is VMware VirtualCenter. Check that you have these CI's and if not use the Host connection by Shell or Manual VMware VIM Connection job to create these CI's.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Discovering VMWARE Infrastructure

Hi, i tried with the manual discovery and i get the following error:

 

Is it an issue with the vim.jar and vim25.jar? The downloaded file is VMware-vSphere-SDK-5.0.0-429209

 

 

<execution jobId="Manual VMware VIM Connection" destinationid="264cc3445ba96088cb04d8c6627abfac" max_store_sent_results="2147483647">
    <destination>
        <destinationData name="id">264cc3445ba96088cb04d8c6627abfac</destinationData>
        <destinationData name="ip_address">10.4.xx.xx</destinationData>
    </destination>
    <protocol name="vmware" cm_credential_id="15_1_CMS">
        <object id="f957987006f1ac7e51de6c6e0a7c7310" id_type="CmdbObjectID" class="vmwareprotocol" isReference="false" is_anchor="false">
            <attribute name="protocol_netaddress" type="String">DEFAULT</attribute>
            <attribute name="user_label" type="String">ucmdb vmware .75</attribute>
            <attribute name="protocol_timeout" type="String">200000</attribute>
            <attribute name="protocol_index" type="Integer">1</attribute>
            <attribute name="protocol_in_use" type="Boolean">false</attribute>
            <attribute name="protocol_port" type="Unknown" />
            <attribute name="cm_credential_id" type="String">15_1_CMS</attribute>
            <attribute name="protocol_username" type="String">ucmdb</attribute>
            <attribute name="protocol_type" type="String">vmwareprotocol</attribute>
            <attribute name="vmwareprotocol_use_ssl" type="String">false</attribute>
        </object>
    </protocol>
    <params>
        <param param_name="remoteJVMClasspath" param_value="%minimal_classpath%;../lib/axis.jar;../lib/axis-jaxrpc.jar;../lib/axis-wsdl4j.jar;../runtime/probeManager/discoveryResources/vmware/vim.jar;../runtime/probeManager/discoveryResources/vmware/vim25.jar" />
        <param param_name="maxThreadRuntime" param_value="900000" />
        <param param_name="runInSeparateProcess" param_value="true" />
        <param param_name="JOB_ID" param_value="Manual VMware VIM Connection" />
    </params>
    <log start="17:50:04" severity="debug">Connecting by URL: https://10.4.xx.xx/sdk</log>
    <CONNECT start="17:50:34" duration="29475" CMD="client_connect" RESULT="success" type="vmware" credentialsId="15_1_CMS">
        <ClientProperties>
            <prop name="protocol_timeout" value="200000" />
            <prop name="protocol_netaddress" value="DEFAULT" />
            <prop name="credentialsId" value="15_1_CMS" />
            <prop name="protocol_type" value="vmwareprotocol" />
            <prop name="connection_url" value="https://10.4.1.75/sdk" />
            <prop name="user_label" value="ucmdb vmware .75" />
            <prop name="protocol_username" value="ucmdb" />
            <prop name="vmwareprotocol_use_ssl" value="false" />
            <prop name="protocol_in_use" value="false" />
            <prop name="protocol_port" value="" />
            <prop name="cm_credential_id" value="15_1_CMS" />
            <prop name="protocol_version" value="2.5" />
            <prop name="protocol_index" value="1" />
        </ClientProperties>
    </CONNECT>
    <DISCONNECT start="17:50:34" duration="7" CMD="client_disconnect" RESULT="" IS_NULL="Y" type="vmware" credentialsId="15_1_CMS" />
    <log start="17:50:34" severity="debug">
Traceback (most recent call last):
  File "vmware_vim", line 428, in discover
  File "vmware_vim", line 497, in _fillInSuccessContext
  File "vmware_vim", line 179, in getVmwareModuleByApiVersion
ValueError: Cannot find VMware module corresponding to API version '5.5'
</log>
    <log start="17:50:35" severity="debug">VMware VIM: Internal error. Details:
Traceback (most recent call last):
  File "vmware_vim", line 428, in discover
  File "vmware_vim", line 497, in _fillInSuccessContext
  File "vmware_vim", line 179, in getVmwareModuleByApiVersion
ValueError: Cannot find VMware module corresponding to API version '5.5'
</log>
</execution>

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Discovering VMWARE Infrastructure

What version of UCMDB are you using?

It looks like you are using the VMware 5.0 SDK but need the VMware 5.5 SDK and the vim25.jar from that download.

 

Download Link for VMware 5.5 SDK

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Discovering VMWARE Infrastructure

Hi, I downloaded the sdk 5.5, replaced the vim25.jar file from inventory scanner and rerun that job. Also, I modified the vim25.jar from probe path (...\DataFlowProbe\runtime\probeManager\discoveryResources\vmware).

There're no vim.jar, I copied the vim25.jar file from (\VMware-vSphere-SDK-5.5.0-1284541\SDK\vsphere-ws\java\JAXWS\lib).

 

Thanks in advance,

Damian

 

</CONNECT>
<DISCONNECT start="10:36:17" duration="4" CMD="client_disconnect" RESULT="" IS_NULL="Y" type="vmware" credentialsId="15_1_CMS" />
<log start="10:36:17" severity="debug">
Traceback (most recent call last):
File "vmware_vim", line 428, in discover
File "vmware_vim", line 497, in _fillInSuccessContext
File "vmware_vim", line 179, in getVmwareModuleByApiVersion
ValueError: Cannot find VMware module corresponding to API version '5.5'
</log>
<log start="10:36:18" severity="debug">VMware VIM: Internal error. Details:
Traceback (most recent call last):
File "vmware_vim", line 428, in discover
File "vmware_vim", line 497, in _fillInSuccessContext
File "vmware_vim", line 179, in getVmwareModuleByApiVersion
ValueError: Cannot find VMware module corresponding to API version '5.5'
</log>
</execution>

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.