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) > What happens to incoming log data when LEM is down?

What happens to incoming log data when LEM is down?

Table of contents

Updated May 2, 2017

Overview

This article describes what happens to log data when the LEM appliance is not accessible on the network.

Environment

All LEM versions

Detail

For all agent nodes (Windows, Linux, Unix, AIX, Macintosh systems) where an agent has been installed, the data is queued up within the agent folder while LEM is unreachable, and then sent to LEM over a secure TCP connection when it is back up. 

For syslog nodes (routers, switches, and firewalls, and possibly Unix or Linux devices without an agent), the data is sent over UDP on port 514 and will be lost if it is unable to reach LEM.

 

For SNMP data, LEM only uses a listening service, and trap traffic received from these devices uses port 161 or 162 (monitoring LEM on port 161 is not used in versions earlier than 6.3.x).


Review the following articles for further information about the communications between network nodes and LEM:

 

Last modified
21:54, 1 May 2017

Tags

Classifications

Public