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 > Plan your deployment > Single location deployment example

Single location deployment example

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

Views: 155 Votes: 0 Revisions: 1

This deployment example uses one syslog server based in one location to collect log data from your network devices in a local network. The syslog server is installed in a Windows-based system hosting the LEM Manager, which captures the syslog data from the network devices. You can use this deployment to collect syslog data from one location.

File:Success_Center/Reusable_content_-_InfoDev/LEM/LEMQuickStart/050/030/LEM_Architecture3_607x452.png

In this deployment, the network devices send syslog data to the LEM Manager over TCP or UDP. Workstations and servers hosting applications use LEM agents to initiate TCP connections and push syslog data to the LEM Manager running on a supported vSphere or Hyper-V hypervisor. The syslog server receives the logs on port 514 and saves the logs to the LEM Manager /var/log file partition. The log filename varies, based on the target facility configured on the network device.

If your log sources are located behind firewalls, see this KB article to open the necessary ports.

 

 
Last modified
12:08, 1 Aug 2016

Tags

Classifications

Public