search cancel

Overcommitted resources within ESXi may result in high memory usage or high CPU usage status within ATP UI

book

Article ID: 162684

calendar_today

Updated On:

Products

Symantec Products

Issue/Introduction

Overcommitted resources within ESXi may result in high memory usage or high CPU usage status within the user interface (UI) of Advanced Threat Protection (ATP) Virtual Edition (VE).

  • At the UI of the ATP Management Server, the System Health status for the ATP VE device may reflect high CPU or high memory usage.
  • Within messages log, you may see messages such as “kernel: BUG: soft lockup - CPU#0 stuck for 23s!” or "Memory Usage is Very High, Take Some Action".

 

Other Symptoms:

  • The system may appear to idle for long periods and you may receive high memory usage messages in the log files.

 

Cause

When running ATP in a virtual environment, errors can occur if your physical resources are over-committed.

Resolution

Make certain system memory and other resources are reserved in your virtual environment for the virtual machine running your ATP appliances. See the Symantec Advanced Threat Protection Installation Guide for a complete list of system requirements and see your VMware documentation for more information about reserving system resources.

 

To confirm whether the ATP guest has enough memory reserved to meet system requirements

  1. Within the VMWare Integration Client (vic), click Inventory
  2. In the left pane, navigate to the host where the ATP VE guest resides and click it.
  3. In the left pane, click the ATP VE guest.
  4. On the right pane, on the Resource Allocation tab, in the Memory section, confirm that Reservation: contains the same number as Configured:
  5. If Configured: is less than 32GB for ATP version 2.0, more configured memory is required.
  6. If Reservation: is less than 32GB for ATP version 2.0, more reserved memory is required.
  7. If Reservation: is less than Configured:, more reserved memory is required.

 

Before adding memory, check with the adminstrator of the host where ATP VE resides to ensure that the needed memory is available both within the host where ATP VE resides and within the resource pool where ATP VE resides.