The SYSLOG module

The SYSLOG module allows accessing of the device to be logged. This function is especially interesting for system administrators as it optionally records a complete history of all activities in the device.

A corresponding SYSLOG client or daemon is required to receive the SYSLOG messages. Logging under UNIX/Linux is generally performed by the SYSLOG daemon that is set up by default in these operating systems. The daemon either establishes contact with the CLI or writes its log to an appropriate SYSLOG file.

Under Linux, the file /etc/syslog.conf contains a definition of which facilities (service or component that issued the message) should be written to which log file. Please check your daemon's configuration to see if it explicitly listens to network connections.

Windows does not provide a corresponding system function. You require special software to provide the functionality of a SYSLOG daemon.

To extend the output of the SYSLOG information over an appropriate SYSLOG client, the most recent SYSLOG messages are stored in the device's RAM. Depending on the memory fitted, this can vary from 100 to 23,000 syslog messages. These internal syslogs can be viewed in various ways:
Important: SYSLOG messages will only be written to the device's internal memory if the device was entered as a SYSLOG client with the loopback address 127.0.0.1 or if boot-persistent storage is enabled. See Boot-persistent SYSLOG, event log and boot log.




Alternatively you can view the current SYSLOG messages on the first page of WEBconfig on the SYSLOG tab:





www.lancom-systems.com

LANCOM Systems GmbH | A Rohde & Schwarz Company | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E‑Mail info@lancom.de

LANCOM Logo