Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register 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