Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Archive > 2018February09 - Redirects > SolarWinds LEM Quick Start and Deployment Guide > Reserve system resources in the virtual environment

Reserve system resources in the virtual environment

Created by Caroline Juszczak, last modified by Caroline Juszczak on Aug 05, 2016

Views: 1,541 Votes: 0 Revisions: 8

Ensure that the system resources in the virtual environment have ample virtual space and memory to support the Log & Event Manager software and incoming data traffic. For typical deployments, Log & Event Manager requires 250GB of system resources on the hypervisor. Large deployments may require 2TB of resources, which you can reserve on the VMware ESX(i) 4/5+ and Microsoft Hyper-V 2008 R-2/2012 hypervisors.

By default, LEM deploys with 8GB of RAM and 2 CPUs on the VMware ESX(i) and Microsoft Hyper-V platforms.

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.

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.

Viewing virtual appliance resources, reservations, and storage

You can view your virtual appliance resources, reservations, and storage in the Manage > Appliances view. The Appliances grid displays the virtual appliances and their corresponding details.


The Details pane displays information about your selected manager or appliance. This information includes the platform, CPU reservation, and memory allocation. To view the Details pane, click Manage and select Appliances. In the Appliances grid, select the manager or appliance you want to view. If the Details and Properties panes do not appear in the LEM Console, click the Appliances tab at the bottom of the screen.

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.


The current connection status of the selected manager or appliance.


The manager or appliance name.


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


The manager or appliance software version.

IP Address

The manager or appliance IP address.


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 the reservation settings using the vSphere client

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

  1. Log into vSphere.
  2. Select the LEM appliance from the list.
  3. Click the Summary tab to view the number of CPUs.

    The Provisioned Storage value in the Resource area is the total disk space that Log & Event Manager can use.

    At the bottom left, the CPU reservation displays 2.0 GHz.

  4. Set the limit to unlimited.
  5. Select the Resource Allocation tab.
  6. At the bottom right, set the memory reservation to 8MB and the limit to unlimited.

The Configured value must be at least the same value or higher than the reservation. You may see memory reservations as high as 256GB of RAM for customers over 150 million events per day.

Verify the reservations using the SSH client

You can also view your reservation settings using an SSH client (such as PuTTY). The SSH client requires the hostname of your LEM appliance.

  1. Open a PuTTY session.
    1. Click Session.
    2. In the Host Name field, enter the hostname of your LEM appliance.
    3. In the Port field, enter 32022 or 22.
    4. Click Open.

      After you log in, a session window displays.


  2. Enter the Manager menu.
  3. Type viewsysinfo and press Enter.
  4. View the CPU > Reservation and the Memory > Reservation settings and make adjustments as required.
  5. At the cmc> prompt, type exit to exit the CMC.

View the reservation settings in the Hyper-V client

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