Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > SolarWinds LEM Quick Start and Deployment Guide > Multi-location deployment example

Multi-location deployment example

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Aug 01, 2016

Views: 44 Votes: 0 Revisions: 1

This deployment example uses two syslog servers based in two locations to collect log data from your network devices in a wide area network (WAN). The syslog server is installed in two Windows-based systems hosting the LEM agent, which captures the syslog data from the network devices. You can use this deployment to collect syslog data from two remote locations.


This architecture detaches and distributes the syslog servers in separate locations, rather than using the Syslog server in the LEM Manager. Both locations include a local syslog server. The LEM connectors normalize the original log messages into LEM events. You can implement this scenario when your change management processes prevent you from adding new logging hosts on your network devices.

If you deploy a detached Syslog server (such as a Kiwi syslog server), install a LEM Agent on both syslog servers, and then enable the appropriate connectors on the LEM Agent.

Automatic log scanning does not apply to the LEM Agent. However, new nodes can be discovered by the enabled connectors.

If your log sources are located behind firewalls, see SolarWinds LEM port and firewall information to open the necessary ports or the SolarWinds Port Requirements for SolarWinds Products Guide for a list of all ports required to communicate with LEM.


Last modified
12:12, 1 Aug 2016


This page has no custom tags.