Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

‘The system may be experiencing loss of connectivity to vCenter…’ appears when preparing ESXi in Deep Security 9.0

    • Updated:
    • 21 May 2014
    • Product/Version:
    • Deep Security 9.0
    • Platform:
    • Linux - Red Hat RHEL 6 64-bit
    • Windows 2003 Enterprise
    • Windows 2008 Standard 64-bit
Summary
When preparing ESXi from the Deep Security Manager (DSM) console, you get the following error:
The system may be experiencing loss of connectivity to vCenter. Please ensure that vCenter is running properly.
Server0.log also shows the following exception:
May 05, 2014 12:58:11 PM com.thirdbrigade.manager.core.virtual.VirtualWorkerThread run
SEVERE: ThID:30|TID:0|TNAME:Primary|UID:-1|UNAME:|VirtualWorkerThread threw an exception,
waiting 600000 ms before re-initiating the monitor
com.thirdbrigade.manager.core.virtualization.vmware.exceptions.VirtualizationException:
java.net.UnknownHostException: sdk

at com.thirdbrigade.manager.core.virtualization.vmware.apputils.VersionUtil.getSupportedVersions
(VersionUtil.java:98)
at com.thirdbrigade.manager.core.virtualization.vmware.apputils.VersionUtil.getSupportedVersions
(VersionUtil.java:35)
at com.thirdbrigade.manager.core.virtual.VirtualWorkerThread$vCenterUpdateReceiver.run
(VirtualWorkerThread.java:2317)
Caused by: java.net.UnknownHostException: sdk
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618)
at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:378)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:473)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:270)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:327)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient
(AbstractDelegateHttpsURLConnection.java:191)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:931)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
(AbstractDelegateHttpsURLConnection.java:177)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at com.thirdbrigade.manager.core.virtualization.vmware.apputils.VersionUtil.getSupportedVersions
(VersionUtil.java:63)
... 2 more
Details
Public
The issue occurs when the vCenter hostname begins with "sdk". DSM reserves "sdk"in lowercase letters as a code parameter; using it for the hostname causes a DSM parsing exception.
To resolve the issue, change the vCenter hostname to the uppercase letters "SDK***".
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1103492
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.