Symptoms
vRealize Log Insight is version 4.5.1 or later.vRealize Operations Manager is behind a load balancer.Test Connection fails in the vRealize Operations integration when using the FQDN of vRealize Operations Manager's load balancer or master.The /storage/var/loginsight/vcenter_operations.log in vRealize Log Insight shows errors similar to:
[2018-05-15 09:51:02.621+0000] ["https-jsse-nio-443-exec-3"/10.205.73.139 INFO] [com.vmware.loginsight.vcopssuite.VcopsSuiteApiRequest] [Open connection to URL https://vrops.domain.com/suite-api/api/versions/current][2018-05-15 09:51:02.621+0000] ["https-jsse-nio-443-exec-3"/10.205.73.139 INFO] [com.vmware.loginsight.vcopssuite.VcopsSuiteApiRequest] [http connection, setting request method 'GET' and content type 'application/json; charset=utf-8'][2018-05-15 09:51:02.621+0000] ["https-jsse-nio-443-exec-3"/10.205.73.139 INFO] [com.vmware.loginsight.vcopssuite.VcopsSuiteApiRequest] [reading server response][2018-05-15 09:51:02.626+0000] ["https-jsse-nio-443-exec-3"/10.205.73.139 ERROR] [com.vmware.loginsight.vcopssuite.VcopsSuiteApiRequest] [failed to post resource to vRealize Operations Manager]javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name
Cause
vRealize Log Insight 4.5.1 added many updates to the Apache Struts, JRE, kernel-default, and other libraries to improve security.These updates libraries affect the SSL Handshake that takes place when testing the vRealize Operations Manager integration.
Resolution
To resolve this issue, add the FQDN of vRealize Operations Manager's load balancer or master as an alias to the apache2 config.Note: These steps will need to be re-run after upgrade of vRealize Operations Manager.
Log into the vRealize Operations Manager Primary node as root via SSH or Console.Open /usr/lib/vmware-vcopssuite/utilities/conf/vcops-apache.conf in a text editor.Find the ServerName ${VCOPS_APACHE_SERVER_NAME} line and insert a new line after it.On the new line enter the following:
ServerAlias vrops.domain.com
Note: Replace vrops.domain.com with the FQDN of vRealize Operations Manager's load balancer or master.Example: ServerAlias opsmanager.vmware.com
Save and close the file.Restart the apache2 service:
service apache2 restart
Repeat steps 1-6 on all nodes in the vRealize Operations Manager cluster.