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

Create a technical support case if you need further support.

Correcting packet issues in Deep Security Virtual Appliance (DSVA)

    • Updated:
    • 20 Aug 2014
    • Product/Version:
    • Deep Security 9.0
    • Deep Security 9.5
    • Platform:
    • N/A N/A
Summary
The symptoms when experiencing packet issues are not always the same in all cases, but all of them involve network problems. One possible symptom is a problem with the Intrusion Prevention System (IPS) causing the Remote Desktop Protocol (RDP) to fail.
Packet issues may occur if the VMX file of the affected DSVA is missing two important parameters that configure the fastpath to slowpath interface:
  • Name: ethernet2.filter0.name
    Value: dvfilter-faulter
  • Name: ethernet2.filter0.param0
    Value: dvfilter-dsa
These parameters should have been added automatically by the Deep Security Manager (DSM) during deployment of the appliance.
Details
Public
To resolve packet issues, configure the missing parameters:
  1. vMotion the VMs protected by DSVA to another ESX server before proceeding.
    Any VM protected by DSVA will become unprotected when the DSVA is shut down. vMotioning these VMs will ensure that they are protected by a DSVA on that ESX Server.
  2. In the vSphere Client, shut down (not power off) the DSVA.
  3. Right-click the DSVA and select Edit Settings.
    Edit DSVA settings
  4. In the Virtual Machine Properties window, click Options.
  5. Under the Advanced section, click General > Configuration Parameters.
    Edit advanced configuration settings
    Click image to enlarge.
  6. In the Configuration Parameters window, click Add Row and then add these two parameters:
    • Name: ethernet2.filter0.name
      Value: dvfilter-faulter
    • Name: ethernet2.filter0.param0
      Value: dvfilter-dsa
      Add the missing parameters in the DSVA VMX file
      Click image to enlarge.
  7. Click OK in the Configuration Parameters window.
  8. Click OK in the Virtual Machine Properties window. The change will be applied to the affected DSVA VMX file.
  9. Power on the DSVA.
  10. Return the VM you vMotioned in Step 1 to its original ESX server.
  11. Enable the Web Reputation Service (WRS) and browse the web on the affected VM to ensure that the problem is resolved.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1102356
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.