Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Log & Event Manager (LEM) > LEM Administrator's Guide > Allocate CPU and memory resources to the LEM VM

Allocate CPU and memory resources to the LEM VM

Updated: September 15, 2017

By default, LEM deploys with 8GB of RAM and 2 CPUs on the VMware ESX(i) and Microsoft Hyper-V platforms. For LEM to work properly, you must allocate sufficient CPU and memory resources to the LEM VM. This topic describes how to check resource settings and make updates.

See LEM 6.3.1 system requirements in the LEM Installation Guide for hardware and software sizing requirements.

As of version 6.3.0, LEM can send SNMP version 3 alerts to SolarWinds Network Performance Manager (NPM). This configuration allows you to monitor CPU, memory, and other critical LEM components from the SolarWinds Orion Web Console.

Log & Event Manager collects data from a continuous stream of traffic that fluctuates based on user, server, and network activity. The type and volume of traffic varies based on the device sending the traffic and the audit and log settings on those devices.

About incoming data traffic

Log & Event Manager receives data from syslogs and traps using up to 500 connectors that receive data traffic from several supported network devices. These connectors translate (or normalize) the data into a readable and understandable format you can view in the LEM console.

The connectors display in the Monitor view, pass through the rules engine for specified actions, and move into a database for retrieval by the LEM Reports or nDepth search function. To process the data in real-time, Log & Event Manager requires system resource reservations from the virtual appliance host.

When the volume of traffic exceeds 15 million events per day, be sure to reserve additional system resources to support the additional data traffic.

Use the LEM console to view resource allocations and VM details

  1. Open the LEM console. See Log in to the LEM web console or Log in to the LEM desktop console for steps.

  2. Click Manage > Appliances.

    The Appliances grid lists the LEM VMs registered with the console and their corresponding details.

    File:Success_Center/Reusable_content_-_InfoDev/LEM/Log_and_Event_Manager_Administrator's_Guide/LEM_Administrator's_Guide/0230-Allocate_CPU_and_memory_resources_to_the_LEM_VM/lem_qsg_appliances_grid_728x70.png

    Below the Appliances grid, the Details pane lists information about the selected VM. (If the Details and Properties panes are not visible, click the Appliances tab at the bottom of the screen.)

    File:Success_Center/Reusable_content_-_InfoDev/LEM/Log_and_Event_Manager_Administrator's_Guide/LEM_Administrator's_Guide/0230-Allocate_CPU_and_memory_resources_to_the_LEM_VM/appliance-resource-details.png

     

Details pane descriptions
Field Description
Platform The Manager platform name, which can be Trigeo SIM, VMware vSphere, or Microsoft HyperV.
CPU Reservation The reserved CPU memory. Reserving CPU memory ensures enough system resources are available for the allocated CPUs.
Number of CPUs The number of processors allocated to the virtual appliance.
Memory Allocation The maximum amount of memory the Manager can use. Set this value at or above the reservation value. You can define this value in the VM configuration. Setting memory allocation to a greater value than the memory reservation has little effect on LEM performance.
Memory Reservation The amount of memory reserved for this system.

Status

The current connection status of the selected Manager or appliance.

Name

The Manager or appliance name.

Type

The appliance type (Manager, Database Server, nDepth Server, Logging Server, or Network Sensor).

Version

The Manager or appliance software version.

IP Address

The Manager or appliance IP address.

Port

The port number used by the LEM console to communicate with the Manager or appliance.

You can view your reservation settings using vSphere or an SSH client (such as PuTTY). See your VMware vSphere documentation for details about configuring resources, reservations, and storage on a vSphere virtual appliance.

View vSphere reservation settings for LEM

You can view reservation settings using the vSphere client. See your VMware vSphere documentation for details about configuring resources, reservations, and storage on a vSphere virtual machine.

  1. Log into vSphere and check the Settings/Reservations.

  2. Select LEM from the list (name listed may not be the host name), and view the Summary tab to find the number of CPUs (such as 2 vCPU).

    LEM requires at least two CPUs. The highest working setting for any LEM appliance is 16 CPUs.

  1. Provisioned Storage on the right side of the screen shows the total disk space LEM can use.

    • If LEM is set for thick provisioning, the used storage is always the total disk space.

    • Thin provisioning allows the used storage to grow to the total amount of storage allocated.

  2. On the Resource Allocation tab, note the CPU reservation on the left, and the memory reservations on the right.

  3. At the bottom left, check the CPU reservation. 2.0Ghz is LEM's minimum setting. To support higher speeds, see your VMware documentation for configuration information.

  4. See the Memory reservation at the bottom right. This reservation is normally set at 8 GB or higher. The Memory must be the same value or higher than the reservation. Memory reservations can be set as high as 64GB of RAM, which can support over 150 million events per day.

To change vSphere reservations for LEM

  1. Shut down the LEM VM. See Starting and Stopping LEM components for steps.
  2. Right-click the LEM VM to edit settings.

    Select the Hardware tab and change the allocated memory size.

  3. Select the Resources tab and change the CPU and memory settings.
    • Set the limit to unlimited for both CPU and memory reservations.
  4. Select OK to save the changes.
  5. Use the vSphere console to start the LEM VM.

View reservations settings using the CMC command-line

  1. Open the CMC command line. See Log in to the LEM CMC command line interface for steps.

  2. Type manager at the cmc> prompt.

  3. Type viewsysinfo and press Enter.

    The system returns memory and CPU information, as well as LEM version and license information.

  4. Type :q to return to the cmc::manager> prompt.
  5. Type exit to exit the manager menu.
  6. Type exit at the cmc> prompt to exit the CMC command line.

View Hyper-V reservation settings for LEM

Use the following tables to verify your Hyper-V client settings. For details about setting resources, reservations, and storage on a Hyper-V virtual appliance, see your Microsoft Hyper-V documentation.

Memory settings

Setting Value
Static RAM 8GB, 16GB, 24GB, 32GB, 64GB, 128GB, 256GB
Memory Weight High

CPU settings (Windows Server 2008)

Setting Value
Number of processors 2, 4, 6, 8, 10, 12, 14, 16
VM reserve CPU cycles 100%
Limit CPU Cycles 100%
Relative weight for CPU 100%

CPU settings (Windows Server 2012)

Setting Value
CPU memory details Click the Advanced tab and set the view and details
CPU Priority High
Reserve CPU cycle 100%
Limit CPU cycles 100%
Last modified

Tags

Classifications

Public