Troubleshooting - Performance issues on an agentless virtual machine

Applies to on-premise Deep Security software installations only

Cause: Limited resources

  1. Make sure that Deep Security Virtual Agent resource is reserved from settings.
  2. Ensure that the deployment has met the requirements specified in the installation instructions.

Cause: Anti-malware

  1. On Deep Security Manager, go to Computers.
  2. Double-click the protected computer.
  3. For Anti-Malware, select Off.

Cause: Network traffic

The thin driver exclusion is case-sensitive.

Cause: Policy

  • Change the policy setting for the virtual machine to None.

Cause: High CPU

  1. Identify which Deep Security Virtual Agent has high CPU usage.
    • Go to the vCenter console, click each Deep Security Virtual Agent and select Performance to identify the machine with high CPU usage.
  2. Run the hop tool to determine which process is consuming most of the CPU usage.
  3. Identify the high CPU process memory consumption.
    1. Execute the following to check the process memory status: #cat /proc/$PID/status(Replace $PID with your own PID.)
    2. Verify that the vmsize is reasonable.
    3. Export the content to a log file using this command:
    4. #cat /proc/$PID/status > /tmp/HighCPUProcessMemeory.txt

      #sudo lsof –p $PID > /tmp/HighCPUProcessOpenedFile.t

  4. Check if the Deep Security Virtual Agent has enough free memory.
    1. Run the command cat /proc/meminfo to identify the Deep Security Virtual Agent system free memory.
    2. Run the command cat /proc/meminfo > /tmp/DSVAMemory.txt to export the content to a log file.

Cause: Security Update

  1. Check the connection between the relay and its update source or proxy server.
    1. Verify if you need to use a proxy server or not.
    2. Log into the Deep Security, go to Administration > System Settings > Proxy, and confirm that the configuration settings are correct.
  2. Perform a ping test between the agent and the relay-enabled agent.
  3. Make sure that the relay port number is open by using telnet [relay IP] [port number].
  4. Test the DNS and check if the host name of the relay can be resolved.
  5. Check if any firewalls are blocking the communication and disable them if they are.
  6. Unassign the current policy and check if the issue still persists.