Unable to connect to Virtual Center 6.x using the Vsphere client with PATROL for VMware vSphere KM

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    PATROL for VMware vSphere


    COMPONENT:

    PATROL for VMware vSphere


    APPLIES TO:

    PATROL for VMware vSphere



    QUESTION:

    Unable to configure the VSM KM connect to Virtual Center 6.x.  

    The following error message shows on the parameter annotation:

    Configuration Problem 
    --------------------- 
    Not able to connect due to connection error 
    Exception: java.rmi.RemoteException: VI SDK invoke exception:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake 

    Possible corrective actions: 
    -Check entered details by connecting to the vCenter via VMware web client. 
    -Internal error. If error persists, contact BMC Customer Support.

    The error below is found in the vsm log file:
    Apr 24, 2018 6:36:38 PM com.bmc.collector.vmware.Inventory run
    WARNING: vsphbccwprvctr1.office.adroot.bmogc.net: Could not complete Inventory : Status: Disconnected Apr 24, 2018 6:37:38 PM com.bmc.collector.vmware.Connect run
    WARNING: Connect failed:
    java.lang.Exception: java.rmi.RemoteException: VI SDK invoke exception:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.bmc.collector.vmware.VimCollector.connect(VimCollector.java:249)
    at com.bmc.collector.vmware.Connect.run(Connect.java:145)
    at com.bmc.collector.vmware.vmware.runRequestHandler(vmware.java:85)
    at com.bmc.patrol.common.CollectorContext.run(CollectorContext.java:661)
    Caused by: java.rmi.RemoteException: VI SDK invoke exception:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:183)
    at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:125)
    at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1409)
    at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:85)
    at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:69)
    at com.bmc.collector.vmware.VimCollector.connect(VimCollector.java:242)
    ... 3 more
     
    Apr 24, 2018 6:37:38 PM com.bmc.collector.vmware.Inventory run
    WARNING: Could not complete Inventory : Status: Disconnected

    OR
    TLS encryption for communication between KM and VCenter
     


    ANSWER:

    By default, the VSM KM uses TLS1.0.
    In VCenter 6.x, TLS1.0 may be disabled and  users can choose to enable TLS1.1 and TLS1.2 instead.
    Reference: https://kb.vmware.com/s/article/2145796

    Usersr can apply the following change to configure the VSM KM to use TLS1.1 or TLS1.2
    Note:
    1. Please make sure you are using JRE 1.7 or 1.8 for the VSM KM. To change the JRE setting you can push the following pconfig variable
    /VSM/Global/JAVA_HOME = <PATH till JRE directory>
    Eg.
    /VSM/Global/JAVA_HOME = C:\Program Files (x86)\Java\jre1.8.0_161

    2. Push the following pconfig variable to use TLS 1.2, by replacing  <VC_NAME> with the actual VC Name.

          
      
     
    3.Restart the PATROL Agent service.  
      

     


    Article Number:

    000152764


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles