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

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
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:
java.net.ConnectException: Connection timed out: connect]
at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:122)
at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:128)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at com.vmware.vcops.adapters.v4common.communication.rmi.client.CertificateClient.pair(CertificateClient.java:126)
Caused by: java.rmi.ConnectException: Connection refused to host: <Operations Manager Node IP or FQDN>; nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:118)
... 3 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:211)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vRealize Operations Manager 6.1.x
VMware vRealize Operations Manager (Standalone) 5.8.x
VMware vRealize Operations Manager 6.2.x
VMware vRealize Operations Manager 6.0.x

Cause

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.

Resolution

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:

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

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

v4V Adapter specific ports

TCPPORTS="$TCPPORTS 3091:3095"
TCPPORTS="$TCPPORTS 3099:3101"
Save and close the file.
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.

Additional Information

适用于 Horizon 6.2 Broker Agent 的 VMware vRealize Operations Manager 未能与 Horizon Adapter 配对