Search the VMware Knowledge Base (KB)
View by Article ID

VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter (2140844)

  • 7 Ratings


After you upgrade to or perform a fresh installation of the Horizon 6.2 adapter and then restart the cluster, you experience these symptoms:

  • Horizon 6.2 Broker agent fails to pair with the Horizon 6.2 adapter.
  • In the C:\ProgramData\VMware\vRealize Operations for Horizon\Broker Agent\logs\v4-msgserver.log file, you see entries similar to:

    2015-12-10 18:38:11,523 DEBUG [Thread-3] com.vmware.vcops.adapters.v4common.communication.rmi.client.CertificateClient.pair - Failed to pair the certificates from the adapter and broker agent:
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <Operations Manager Node IP or FQDN>; nested exception is: Connection timed out: connect]
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        at javax.naming.InitialContext.lookup(
        at com.vmware.vcops.adapters.v4common.communication.rmi.client.CertificateClient.pair(
    Caused by: java.rmi.ConnectException: Connection refused to host: <Operations Manager Node IP or FQDN>; nested exception is: Connection timed out: connect
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(
        at sun.rmi.transport.tcp.TCPChannel.createConnection(
        at sun.rmi.transport.tcp.TCPChannel.newConnection(
        at sun.rmi.server.UnicastRef.newCall(
        at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        ... 3 more
    Caused by: Connection timed out: connect
        at Method)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


This issue occurs when the firewall rules on the VMware vRealize Operations Manager are incorrect, or are not updated by the Operations Manager for Horizon Broker Agent and Adapter 6.2.


To resolve this issue, update the firewall rules after you install the Horizon Adapter 6.2 and restart the cluster.

To update the firewall rules:
  1. Connect to the vRealize Operations Manager node through SSH.
  2. Back up the firewall configuration file by running this command:

    cp /opt/vmware/etc/vmware-vcops-firewall.conf  /tmp/vmware-vcops-firewall.conf

  3. Open the opt/vmware/etc/vmware-vcops-firewall.conf file using a text editor:
  4. Edit the entries specific to the v4V adapter ports to:

    v4V Adapter specific ports

    TCPPORTS="$TCPPORTS 3091:3095"
    TCPPORTS="$TCPPORTS 3099:3101"

  5. Save and close the file.
  6. Restart the firewall by running this command:

    /etc/init.d/vmware-vcops-firewall restart
Note: You must perform these steps on all the nodes in a cluster.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 7 Ratings