Beruflich Dokumente
Kultur Dokumente
No part of this document may be reproduced by any means nor modified, decompiled, disassembled,
published or distributed, in whole or in part, or translated to any electronic medium or other means
without the written consent of SolarWinds. All right, title, and interest in and to the software and
documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
The SOLARWINDS and SOLARWINDS & Design marks are the exclusive property of SolarWinds Worldwide,
LLC and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or
pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be
common law marks, registered or pending registration in the United States or in other countries. All other
trademarks mentioned herein are used for identification purposes only and may be or are trademarks or
registered trademarks of their respective companies.
page 2
Table of Contents
LEM installation overview 6
How LEM works 7
Audit reports 7
Overview 8
Sizing criteria 18
page 3
INSTALLATION GUIDE: LOG & EVENT MANAGER
Download LEM 26
Antivirus recommendations 35
To configure the LEM Agent as a Mac OS X service and set it to start automatically 40
Run the LEM Remote Agent Installer non-interactively for large Windows deployments 41
Run the LEM Local Agent Installer non-interactively for large Windows deployments 43
Installation notes 43
page 4
Create a setup file for the Local Agent Installer 44
Install the LEM reports application provided in the LEM distribution package 49
Install the LEM reports application files downloaded from the Customer Portal 49
page 5
INSTALLATION GUIDE: LOG & EVENT MANAGER
• How LEM works 7
page 6
How LEM works
SolarWinds LEM collects log data in your corporate network from two resources:
l Agents – An Agent is a software application that collects and normalizes log data before it is sent to
the LEM Manager.
l Non-Agent devices – These are devices that send log data directly to the LEM Manager for
normalization and processing.
After normalization, LEM Manager processes the data. The LEM Manager policy engine correlates the data
based on user-defined rules and local alert filters, and initiates the associated actions when applicable.
These actions can include:
You can install Agents on workstations, servers, and other network devices. Agents can send log data from
security products (such as antivirus software and network-based intrusion systems) on each device to the
LEM virtual appliance. If you cannot install an Agent on a device (such as firewalls and routers), you can
configure the device to send log data to the LEM Manager for normalization and processing. If your change
management process does not permit adding any additional syslog servers to the network device
configurations, you can leverage your existing syslog servers.
Audit reports
You can generate reports against your Log & Event Manager database using the LEM reports console
installed on a supported server. Using the console, you can schedule and execute over 300 audit reports. If
your corporate security policy restricts access to sensitive reports, you can configure your LEM Appliance to
restrict access to the console by IP address. During the 30-day evaluation period, you can install the
console on any server or workstation that can access port 9001 in the LEM Manager. You can also export
reports to multiple formats, including TXT, PDF, CSV, DOC, XLS, and HTML.
LEM uses additional data collection tools such as Web Services and SNMP traps. Contact Customer
Service for more information about integrating LEM into your corporate enterprise.
page 7
INSTALLATION GUIDE: LOG & EVENT MANAGER
• Overview 8
Overview
The following illustration shows the software components, log files, and network protocols in a typical
SolarWinds LEM deployment.
page 8
A complete LEM installation includes the following components:
l The LEM Manager (or LEM VM), which collects and processes log and event information. This
component is installed first.
l The desktop software or web client (not shown) that allows you to view LEM information from a
desktop or laptop computer.
The LEM documentation uses the term virtual machine (or VM) to refer to the LEM virtual appliance
that runs on the hypervisor.
The LEM Manager collects and processes log and event information. It includes the following systems and
services:
l Hardened Linux® OS
l Syslog Server and SNMP Trap Receiver
l High compression, search-optimized database
l Web server
l Correlation engine
You can also use the LEM Agent with devices that support syslog. The Agent transmits syslog messages
over TCP to the LEM Manager. TCP is preferred over UDP because TCP ensures messages arrive intact.
page 9
INSTALLATION GUIDE: LOG & EVENT MANAGER
LEM accepts device input using the TCP and UDP protocols:
l Network devices use TCP or UDP to send syslog events to the LEM Manager.
l LEM Agents installed on servers and workstations use TCP to push data to the LEM Manager.
l SolarWinds Orion/VMan server instances (including NPM and SAM) send SNMP traps over UDP to the
LEM Manager.
page 10
LEM deployment examples
This section will help get you started planning your LEM architecture. The examples show different LEM
deployment options.
page 11
INSTALLATION GUIDE: LOG & EVENT MANAGER
The syslog server receives logs on port 514 and saves the data in the LEM Manager /var/log file
partition. Log file names vary based on the target facility configured on the network device.
The LEM Manager relies on routers, firewalls, and switches to transmit syslog messages to the
syslog server running on the LEM Manager. If your log sources are located behind firewalls, see
SolarWinds LEM port and firewall information to open the necessary ports. For a list of all ports
required to communicate with LEM, see the SolarWinds Port Requirements for SolarWinds
Products Guide at: https://support.solarwinds.com/Success_Center/Network_Performance_
Monitor_(NPM)/Port_requirements_for_all_SolarWinds_products
Instead of using the syslog server built in to the LEM Manager component, this design calls for one syslog
server per location. When using a detached syslog server, you need to install a LEM Agent on each
detached server, and then enable the appropriate connectors on the LEM Agent. Following configuration,
the LEM connectors normalize raw log messages into LEM events.
If you cannot add new logging hosts on your network devices due to restrictive change management
processes, consider implementing this multi syslog server deployment example to leverage your
existing syslog servers.
page 12
Complex deployment example with multiple LEM VMs
To increase performance, you can divide LEM's workload across multiple LEM VMs. Each VM can be
configured to provide dedicated processing for tasks such as:
Although multi-VM LEM installations are possible, 98% of all LEM deployments perform well as a
single appliance that you can scale up by dedicating additional resources from the virtual host.
Each LEM VM can specialize and provide dedicated processing for one or more of the following:
The following diagram shows four LEM VM instances. One each for the LEM Manager, syslog collection, the
normalized data store, and an optional original data store.
Deploying each LEM VM on separate hardware increases performance. You can also deploy multiple
VMs on the same hardware host with minimal negative performance impacts.
page 13
INSTALLATION GUIDE: LOG & EVENT MANAGER
LEM allows you to assign resources in different ways based on your organization's needs. For example, you
can deploy two LEM Managers, each on a separate VM if your organization has logical divides in
management and/or monitoring responsibilities.
In the above example a single LEM console provides a consolidated, real-time search and management
view across two LEM VMs.
See also:
page 14
Choose a licensing method for your LEM deployment
This section explains how LEM licenses are assigned. It also discusses how to transition from an evaluation
version of LEM to a fully-functional production version.
For more information, see the following topics in the LEM Administrator Guide:
l The number of universal nodes. Universal nodes include non-agent devices, such as switches,
routers, and firewalls, and systems running either a Windows Server or Unix operating system.
l The number of workstation nodes. Workstation nodes include desktop systems that run
Windows and the LEM Agent.
For example, a LEM deployment that has a LWE250 for LEM30 license can add 250 Windows workstation
nodes and 30 universal nodes.
If you have not purchased and provided a license key after 30 days, the application will stop collecting
event logs from your syslog and Agent devices. You can continue using Log and Event Manager in this
mode and access your saved logs. Applying a license reactivates event log collection and you can continue
monitoring all events in your deployment. If you need to extend your evaluation period, contact Customer
Sales.
You can upgrade to a fully-functional production version by purchasing a new license from Customer Sales
and downloading the license key from the Customer Portal. After you install the new license key, you can
access all features within the LEM appliance.
page 15
INSTALLATION GUIDE: LOG & EVENT MANAGER
You cannot upgrade your license using the SolarWinds License Manager.
page 16
LEM 6.3.1 system requirements
Use the following tables to plan your Log & Event Manager deployment to suit your network environment.
• Sizing criteria 18
l Number of nodes and network traffic. Consider event throughput and performance degradation
when planning the size of your deployment. As the number of nodes and network traffic increase,
the size of your deployment will need to grow with it. For example, if you are running a small
deployment and begin to notice performance degradation at 300 nodes, move to a medium
deployment.
l Storing original (raw) log messages in addition to normalized log messages. If you will be
storing original log messages, increase the CPU and memory resource requirements by 50%. See
your hypervisor documentation for more information.
page 17
INSTALLATION GUIDE: LOG & EVENT MANAGER
Sizing criteria
Use the following table to determine if a small, medium, or large deployment is best suited to supporting
your environment.
SIZING
SMALL MEDIUM LARGE
CRITERIA
Number of Fewer than 500 Between 300 and 2,000 nodes More than 1,000 nodes in the
nodes nodes in the in the following combinations: following combinations:
following
combinations: l 10 – 25 security devices l 25 – 50 security devices
l 200 – 1,000 network l 250 – 1,000 network devices,
l 5 – 10 devices, including including workstations
security workstations l 500 – 1,000 servers
devices l 50 – 500 servers
l 10 – 250
network
devices,
including
workstations
l 30–150
servers
page 18
LEM VM hardware requirements
See "Allocate CPU and memory resources to the LEM VM" in the LEM Administrator Guide for
information about how to manage LEM system resources.
HARDWARE
ON THE VM SMALL MEDIUM LARGE
HOST
If you will be storing original log messages in addition to normalized log messages,
increase the CPU and memory resource requirements by 50%.
Hard drive 250GB, 15k hard 500GB, 15K hard drives (RAID 1TB, 15k hard drives (RAID
storage drives (RAID 1/mirrored settings) 1/mirrored settings)
1/mirrored
settings)
page 19
INSTALLATION GUIDE: LOG & EVENT MANAGER
SOFTWARE REQUIREMENTS
Hypervisor One of the following:
(required on the VM
host) l VMware vSphere ESX 4.0 or ESXi 4.0 and later
l Microsoft Hyper-V Server 2016, 2012 R2, 2012, or 2008 R2
page 20
LEM Agent hardware and software requirements
l IBM AIX
l Linux
l Mac OS X 10.7 or later
l Oracle® Solaris
l Windows (10, 8, 7, Vista)
l Windows Server (2016, 2012, 2008)
The requirements specified below are minimum requirements. Depending on your deployment,
you may need additional resources to support increased log-traffic volume and data retention.
page 21
INSTALLATION GUIDE: LOG & EVENT MANAGER
HARDWARE
AND REQUIREMENTS
SOFTWARE
Operation The LEM reports application is Windows only. The following Windows versions are
System (OS) supported:
SolarWinds recommends using a computer with 1 GB of RAM or more for optimal reports
performance.
Other Install the LEM reports application on a system that runs overnight. This is important
requirements because the daily and weekly start time for these reports is 1:00 AM and 3:00 AM,
respectively.
page 22
LEM port requirements
If your log sources are located behind firewalls, see "SolarWinds LEM Port and Firewall Information" at the
following location to open the necessary ports: https://support.solarwinds.com/Success_Center/Log_
Event_Manager_(LEM)/SolarWinds_LEM_Port_and_Firewall_Information
See the "SolarWinds Port Requirements for SolarWinds Products Guide" at the following location for a list
of all ports required to communicate with SolarWinds products:
http://www.solarwinds.com/documentation/Orion/docs/SolarWindsPortRequirements.pdf
page 23
INSTALLATION GUIDE: LOG & EVENT MANAGER
• Download LEM 26
l Verify that system requirements are met, all required software is installed, and required roles and
features are enabled.
l Gather the information required to complete the installation.
1. Review system Make sure that your environment meets the hardware and software
requirements requirements for your installations. Hypervisor software should be installed
prior to installing LEM. VMware vSphere and Microsoft Hyper-V are both
supported. The hypervisor software provides the virtual environment that hosts
your LEM deployment.
2. Select a Determine if your architecture will include one or more syslog servers.
deployment
See "LEM deployment examples" on page 11 for details.
architecture
3. Review release Review the Log & Event Manager release notes and available documentation in
notes the Success Center: https://support.solarwinds.com/Success_Center.
page 24
Prepare the server environment
Prepare the server where you will install the LEM VM.
1. Build the Prepare the servers based on your deployment size and system requirements.
environment Install either VMware vSphere or Microsoft Hyper-V.
By default, Log & Event Manager deploys with 8GB RAM and 2CPUs on
both hypervisor platforms.
2. Run all OS Before installation, check for and run all OS updates on all servers.
updates
3. Open ports If your log sources are located behind firewalls, see "SolarWinds LEM Port and
according to Firewall Information" at the following location to open the necessary ports:
requirements https://support.solarwinds.com/Success_Center/Log_Event_Manager_
(LEM)/SolarWinds_LEM_Port_and_Firewall_Information
page 25
INSTALLATION GUIDE: LOG & EVENT MANAGER
Download LEM
SolarWinds provides separate installation packages for Hyper-V and VMware vSphere, so be sure to
download the correct version.
1. Download LEM Download the LEM installer from the SolarWinds customer portal, or download a
free trial version from www.solarwinds.com/log-event-manager.
The trial version provides unlimited access to all product features for 30
days. See "Licensing an evaluation version of LEM" on page 15 for more
information.
Next steps:
page 26
Install LEM on the hypervisor
In this section:
page 27
INSTALLATION GUIDE: LOG & EVENT MANAGER
1. Extract the files Double-click the evaluation EXE file that you downloaded previously.
This step will extract the required files and tools to a folder on your
desktop.
2. Complete the 1. In the navigation pane of Hyper-V Manager, select the
following steps to computer running Hyper-V.
import the Virtual 2. Click Action > Import Virtual Machine. Click Next if the "Before
Machine. You Begin" screen displays.
page 28
3. On the Locate Folder screen, navigate to the folder that
matches your version of Windows Server. For example:
%USERPROFILE%\Desktop\SolarWinds Log and
Event Manager\SolarWinds Log & Event
Manager\Virtual Machines 2012 R2
3. Connect to the LEM Select the newly added VM, and then click Action > Connect on the
VM. main Hyper-V Manager window.
4. Start LEM. Click Action > Start in the virtual console window.
page 29
INSTALLATION GUIDE: LOG & EVENT MANAGER
After LEM starts, write down the IP Address of the VM. You will
be able to change the IP address later during the
configuration phase.
5. Set up your new See "Setting up a new LEM installation" in the LEM Administrator
LEM installation. Guide.
Following installation, the default LEM host name is swi-lem. To change the default host name and
IP address settings, see "Run the activate command to secure LEM and configure network settings"
in the LEM Administrator Guide.
page 30
Install SolarWinds LEM on VMware vSphere
These instructions provide steps for installing the Log & Event Manager VM on VMware vSphere.
SolarWinds provides separate installation packages for Hyper-V and VMware vSphere, so check that you
downloaded the correct version.
1. Extract the files Double-click the evaluation EXE file that you downloaded previously.
This step will extract the required files and tools to a folder on your
desktop.
2. Complete the 1. Start the VMware vSphere Client and log in with VMware
following steps to administrator privileges.
deploy LEM. 2. Deploy the open virtualization format (OVF) template.
page 31
INSTALLATION GUIDE: LOG & EVENT MANAGER
3. Open the SolarWinds Log & Event Manager folder located on
your desktop and double-click:
Deploy First—LEM Virtual Appliance.ova
4. Complete the setup wizard.
When prompted, select the Thin Provisioned disk format.
3. Start LEM. 1. Select the SolarWinds Log and Event Manager virtual appliance
and click Play.
2. Click the Console tab.
After LEM starts, write down the IP Address of the VM. You will
be able to change the IP address later during the
configuration phase.
4. Set up your new LEM See "Setting up a new LEM installation" in the LEM Administrator
installation. Guide.
Following installation, the default LEM host name is swi-lem. To change the default host name and
IP address settings, see "Run the activate command to secure LEM and configure network settings"
in the LEM Administrator Guide.
page 32
Install LEM Agents to protect servers, domain
controllers, and workstations
In this section:
page 33
INSTALLATION GUIDE: LOG & EVENT MANAGER
See "About the LEM Agent" on page 9 to learn about the role the LEM Agent plays in a typical LEM
deployment.
l Option 1: You can use the Remote Agent Installer to deploy LEM Agents to computers non-
interactively.
See "Run the LEM Remote Agent Installer non-interactively for large Windows deployments" on
page 41 for more information.
l Option 2: Use the Local Agent Installer with either software distribution policies or local logon scripts
to deploy the LEM Agent non-interactively. This method is an alternative to the Remote Agent
Installer option for large deployments.
See "Run the LEM Local Agent Installer non-interactively for large Windows deployments" on
page 43 for more information.
page 34
LEM Agent pre-installation checklist: Prepare to deploy LEM
Agents
Complete the following tasks before installing the LEM Agent. See "Deploying the LEM Agent" on the
previous page to learn more about installing LEM Agents.
• Antivirus recommendations 35
1. Review system See "LEM Agent hardware and software requirements" on page 21 for
requirements details.
2. Gather credentials Verify that you have administrative access to the servers and
workstations you plan to monitor with the Agent. Windows-based
systems require Domain or Local administrative privileges; Linux or Unix
systems require root-level access.
3. Review the LEM See "Deploying the LEM Agent" on the previous page for installation
Agent installation information, and information about unattended Agent installations.
overview
Antivirus recommendations
page 35
INSTALLATION GUIDE: LOG & EVENT MANAGER
2. After installation, add Set an exception in your antivirus or anti-malware scanning software
an exception to your for the ContegoSPOP folder where the LEM Agents will be installed.
antivirus or anti- The alerts are kept in queue files, which change constantly as they
malware software for are normalized and encrypted.
the LEM Agent folder.
If you are using a trial version of LEM, download the LEM Agent installer from the LEM console, or
contact SolarWinds for assistance.
Next steps:
l "Install the LEM Agent on Linux and Unix" on the facing page
l "Install the LEM Agent on Mac OS X 10.7 and later" on page 39
l "Run the LEM Remote Agent Installer non-interactively for large Windows deployments" on page 41
l "Run the LEM Local Agent Installer non-interactively for large Windows deployments" on page 43
page 36
Install the LEM Agent on Linux and Unix
This topic describe how to install Agents locally on a variety of Linux and Unix operating systems. Once
installed, the LEM Agent automatically starts and connects to the LEM Manager.
See "LEM Agent pre-installation checklist: Prepare to deploy LEM Agents" on page 35 for Agent
download information and a pre-install checklist.
1. Extract the contents of the installer ZIP, and then copy setup.bin to a local or network location.
2. cd to the folder that contains the installer.
3. Enter chmod +x setup.bin to convert the installer into an executable application.
4. Run setup.bin as root.
5. Press Enter to start the installer.
6. Press Enter to page through the End User License Agreement, and then enter y to accept the terms
if you agree.
7. Enter a custom installation path, or press Enter to accept the default (recommended).
8. Enter the hostname of your LEM Manager.
Use the fully qualified domain name for your LEM Manager when you deploy LEM Agents on a
different domain. For example, enter LEMhostname.example.com.
9. Press Enter twice to accept the default port values, and then press Enter again to proceed.
10. Review the Pre-Installation Summary, and then press Enter to proceed.
11. Once the installer finishes, press Enter to exit the installer.
page 37
INSTALLATION GUIDE: LOG & EVENT MANAGER
The LEM Agent begins sending alerts to your LEM Manager immediately. To configure the LEM Agent to
start automatically on boot, add /etc/init.d/swlem-agent to your list of startup scripts.
Next steps:
l See "Verify the LEM Agent connection" on page 46 to test that the Agent connected to the LEM
Manager.
page 38
Install the LEM Agent on Mac OS X 10.7 and later
See "LEM Agent pre-installation checklist: Prepare to deploy LEM Agents" on page 35 for Agent
download information and a pre-install checklist.
1. Extract the contents of the installer ZIP file to a local or network location.
2. Run setup.app, and then click Next to start the installation wizard.
3. Accept the End User License Agreement if you agree, and then click Next.
4. Enter the hostname of your LEM Manager in the Manager Name field and click Next. Do not change
the default port values.
Use the fully-qualified domain name of the LEM Manager when you deploy LEM Agents on a
different domain. For example, enter: LEMhostname.example.com
5. Confirm the Manager Communication settings, and click Next.
page 39
INSTALLATION GUIDE: LOG & EVENT MANAGER
6. Confirm the settings on the Pre-Installation Summary, and click Install.
7. After the installer finishes, click Done to exit the installer.
Ignore the error message that says some errors occurred during the install.
Next steps:
l See "Verify the LEM Agent connection" on page 46 to test that the Agent connected to the LEM
Manager.
The LEM Agent continues running on your computer unless you uninstall or manually stop it. It begins
sending alerts to the LEM Manager immediately.
page 40
Run the LEM Remote Agent Installer non-interactively for
large Windows deployments
The Remote Agent Installer allows you to install the LEM Agent on multiple Windows computers without
the need to step through an installation wizard. Once installed, the LEM Agent automatically starts and
connects to the LEM Manager.
See "LEM Agent pre-installation checklist: Prepare to deploy LEM Agents" on page 35 for Agent
download information and a pre-install checklist.
To install the LEM Agent unattended on non-Windows systems, see "Run the LEM Local Agent Installer
non-interactively for large Windows deployments" on page 43
32-bit C:\Windows\system32\ContegoSPOP
64-bit C:\Windows\sysWOW64\contegoSPOP
l If you are installing LEM Agents on the far end of a WAN link, copy the Remote Agent Installer
executable to the end of the WAN link and run it there. This will avoid using your WAN bandwidth to
copy LEM Agents multiple times.
l A reboot is not required
page 41
INSTALLATION GUIDE: LOG & EVENT MANAGER
1. Extract the contents of the installer ZIP file to a local or network location.
2. Run setup.exe.
3. Click Next to start the installation wizard.
4. Accept the End User License Agreement if you agree, and then click Next.
5. Enter the hostname of your LEM Manager in the Manager Name field, and then click Next. Do not
change the default port values.
Use the fully qualified domain name for your LEM Manager when you deploy LEM Agents on a
different domain. For example, enter LEMhostname.example.com.
6. Confirm the Manager Communication settings, and then click Next.
7. Specify whether or not you want to install USB-Defender with the LEM Agent, and then click Next.
The installer will include USB-Defender by default. To omit this from the installation, clear the Install
USB-Defender option box.
8. Confirm the settings on the Pre-Installation Summary, and then click Install.
9. Once the installer finishes, it will start the LEM Agent service when you click Next.
10. Inspect the Agent Log for any errors, and then click Next.
11. Click Done to exit the installer.
The LEM Agent continues running on your computer unless you uninstall or manually stop it. It begins
sending alerts to your LEM Manager immediately.
Next steps:
l See "Verify the LEM Agent connection" on page 46 to test that the Agent connected to the LEM
Manager.
page 42
Run the LEM Local Agent Installer non-interactively for large
Windows deployments
The Local Agent Installer allows you to install the LEM Agent without the need to step through an
installation wizard. This option is only available for Windows systems.
• Installation notes 43
You can run the Local Agent Installer non-interactively using software distribution policies or local logon
scripts. This method is an alternative to the Windows-only Remote Agent Installer in large deployment
scenarios.
This procedure only works with the local installer. Do not use the Remote Agent Installer for this
task.
Installation notes
See "LEM Agent pre-installation checklist: Prepare to deploy LEM Agents" on page 35 for Agent
download information and a pre-install checklist.
There are three steps to using the Local Agent Installer to install the LEM Agent non-interactively. Each
step is described in detail in the sections below.
1. Create the setup.* installer file for the operating system running on the computer hosting the
LEM Agent. The installer file extension is unique for each Windows operating system.
2. Configure a custom installer.properties file that contains your environmental variables.
3. Run the Local Agent Installer non-interactively.
See "Run the LEM Remote Agent Installer non-interactively for large Windows deployments" on page 41
for more information about installing the SolarWinds LEM Agent.
page 43
INSTALLATION GUIDE: LOG & EVENT MANAGER
Be sure you download the Local Agent Installer. You cannot use the Remote Agent
Installer for this task.
2. Extract the contents of the installer ZIP file to a local or network location.
3. Copy setup.* to a known location.
A blank line with a carriage return after the INSTALL_USB_DEFENDER entry is required for
the file to work correctly.
3. Save the file as installer.properties in the same folder as the setup.* file.
page 44
Run the Local Agent Installer non-interactively
1. Verify that setup.* and installer.properties are located in the same folder.
2. Run the command, setup -i silent using the active resource directory that matches the folder
that contains the two installer files. The command immediately returns to the command prompt.
The LEM Agent starts automatically and continues running until you uninstall or manually stop the
Agent. It begins sending alerts to your LEM Manager immediately. The LEM Agent should also appear
in Add/Remove Programs.
Next steps:
l See "Verify the LEM Agent connection" on the next page to test that the Agent connected to
the LEM Manager.
page 45
INSTALLATION GUIDE: LOG & EVENT MANAGER
1. Open the LEM console. See "Log in to the LEM web console" or "Log in to the LEM desktop console" in
the LEM Administrator Guide for steps.
2. Click Manage > Nodes.
3. In the Nodes grid, ensure that all connected nodes include a green status indicator.
For help troubleshooting LEM Agents, see "Troubleshoot LEM Agents and network devices" in
the LEM Administrator Guide.
Next steps:
l "Configure LEM Agents after they are installed" in the LEM Administrator Guide.
l If you have similar LEM Agents installed, see "Create connector profiles to manage and
monitor LEM Agents" in the LEM Administrator Guide.
page 46
Install the LEM 6.3.1 optional add-on applications
In this section:
page 47
INSTALLATION GUIDE: LOG & EVENT MANAGER
See "LEM reports application hardware and software requirements " on page 22 for additional
requirements.
page 48
Install the LEM reports application
The LEM reports application requires the free Crystal Reports runtime application. There are two ways to
install the LEM reports application:
l You can run the reports application installer included in the SolarWinds Log and Event Manager
distribution package. The installer installs Crystal Reports and the LEM reports application together.
l You can download Crystal Reports and the LEM reports application individually from the
SolarWinds Customer Portal. You will need to install each application one at a time. This may be
necessary if your Windows security settings prevent you from running the other installer.
Install the LEM reports application provided in the LEM distribution package
This installer also installs the Crystal Reports Runtime.
1. If necessary, copy the SolarWinds Log and Event Manager installation folder to a local drive and open
the folder.
2. Right-click the file "Install Next - LEM Reporting Software.exe" and choose "Open."
A dialog box that says "Do you want to allow this app to make changes to your device?" opens.
3. Click Yes to continue.
The Welcome screen opens.
4. Click Next, and review the Requirements for Installation.
5. Click Next, and then click "Begin Install" to start the installation process.
The installer installs the required applications.
6. Click Close when the Installation Complete dialog displays.
Install the LEM reports application files downloaded from the Customer Portal
Complete these steps if you were not able to install the LEM reports application using the installer
included in the SolarWinds Log and Event Manager distribution package.
Before you begin: Download the LEM reports application and the Crystal Reports Runtime installers from
the SolarWinds Customer Portal (https://customerportal.solarwinds.com).
1. Run the Crystal Reports Runtime installer and complete the installation steps.
2. Run the LEM reports application installer and complete the installation steps.
3. When the installation is complete, click Close.
Before you begin: You will need the IP address of the LEM VM and your LEM console login credentials.
page 49
INSTALLATION GUIDE: LOG & EVENT MANAGER
1. Right-click the Reports application icon on your desktop and select Run as administrator.
4. Enter the hostname or IP address of your LEM appliance in the Manager Name field.
Whenever you see Manager in reference to LEM, it usually refers to the IP address or
hostname of your virtual appliance.
5. Enter the username and password used to log in to the LEM console.
You can audit users accessing the reporting server running on the LEM VM. Only users with
admin, auditor, or reports roles can run reports on the LEM database.
6. (Optional) Select the Use TLS connection check box to use the transport layer security protocol for a
secure connection.
page 50
7. Click Test Connection to verify the connection between the LEM database server and the LEM reports
application.
The reports application pings the LEM database and verifies the connection. If the ping is successful,
Ping Successful displays in the dialog box.
8. Click to add the IP address to your LEM Manager list, and then click Yes to confirm.
9. Click Close.
The reports application is connected to your LEM database and displays on your screen.
page 51
INSTALLATION GUIDE: LOG & EVENT MANAGER
The desktop console requires that you install the free Adobe AIR Runtime for Windows on your
computer.
1. Download Adobe Air Runtime for Windows from the SolarWinds Customer Portal
(https://customerportal.solarwinds.com),or from the Adobe AIR website:
https://get.adobe.com/air/
2. Extract the contents of the ZIP file and double-click the installer.
3. Follow the instructions to complete the installation.
page 52
Configure the LEM desktop console after you install it
1. If you did not instruct the console to open after the installation, open the desktop console.
2. Accept the End User License Agreement if you agree, and click OK.
3. Enter the IP address or hostname of the LEM VM, and then click Connect.
The computer running the LEM console must be able resolve the hostname of the LEM VM
using either DNS, or a manual entry in the Windows hosts file. See "Resolve the Hostname"
below for more information.
See also:
Configure forward and reverse DNS entries (a HOST and PTR record) for the LEM VM on your DNS server.
When you create the DNS entries, use the default hostname or the hostname you specified when you
installed the VM. If you cannot configure DNS directly on your DNS server, configure a hosts file on the
computer by editing the Windows\system32\drivers\etc\hosts file in a text editor and adding a
line with the LEM virtual machine IP address and host name, separated by a space or tab character.
page 53