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

Create a technical support case if you need further support.

Unable to activate Deep Security Virtual Appliance (DSVA) servers and virtual machines from the Deep Security Manager (DSM) console

    • Updated:
    • 21 Oct 2015
    • Product/Version:
    • Deep Security 8.0
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
Summary

The DSM console shows the following error when activating a DSVA server or a virtual machine:

An error occurred in the Deep Security Manager to Deep Security Agent/Appliance protocol: SocketException: Network is unreachable: connect.

Details
Public

The issue occurs in environments using the IP range 169.0.0.0 - 169.255.255.255. This happens because the DSM’s heartbeat port, which is 4120 by default, filters communication to and from 169.xxx.xxx.xxx during the sync operation with vCenter. This is done to differentiate traffic for the VMKernel NIC IP, which uses 169.254.xxx.xxx.

 
This issue has been fixed in Deep Security 8.0 SP2 and 9.0. 

To resolve the issue, change the scheme used by DSM to communicate with the DSVA servers and virtual machines. Follow these steps to change the default communication scheme from "1" for IP address to "0" for hostname.

 
DNS or name resolution for the servers and virtual machines involved must be working properly within the environment.
  1. On the DSM server, open the Windows command prompt using elevated privileges.
  2. Go to the DSM program directory. For example: C:\Program Files\Trend Micro\Deep Security Manager.
  3. Run the following commands:

     
    These commands will restart the DSM services.
    • For DSVA servers:

      dsm_c -action changesetting -name configuration.connectionSchemeDSVA -value 0

      Sample result:

      C:\Program Files\Trend Micro\Deep Security Manager>dsm_c -action changesetting -name configuration.connectionSchemeDSVA -value 0
      Stopping Trend Micro Deep Security Manager...
      Setting: configuration.connectionSchemeDSVA saved.
      Starting Trend Micro Deep Security Manager...
      Complete

    • For virtual machines:

      dsm_c -action changesetting -name configuration.connectionSchemeVM -value 0

      Sample result:

      C:\Program Files\Trend Micro\Deep Security Manager>dsm_c -action changesetting -name configuration.connectionSchemeVM -value 0
      Stopping Trend Micro Deep Security Manager...
      Setting: configuration.connectionSchemeVM saved.
      Starting Trend Micro Deep Security Manager...
      Complete

The DSM will now use hostname as the communication scheme.

Premium
Internal
Rating:
Category:
Deploy
Solution Id:
1060908
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.