The SYSLOG protocol is used to log the activities of a LANCOM device. This function is especially interesting for system administrators as it records a a complete history of all activities in the device. The information captured in the SYSLOG log can be viewed in different ways:
- SYSLOG messages can be sent to a central "collection point", a so-called SYSLOG client or
SYSLOG daemon. This option is useful, for example, when messages from a large number of
devices are to be logged.
- Logging under UNIX/Linux is generally performed by the SYSLOG daemon that is set up as standard in these operating systems. The daemon either establishes contact with the console or writes its log to an appropriate SYSLOG file. The file /etc/syslog.conf contains a definition of which facilities (more on this term later) 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.
- Syslog in the device memory.
- 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 2048 syslog messages. These internal syslogs can be viewed in various
ways:
- In the device statistics via the command line, e.g. with telnet
- In WEBconfig under /System information/Syslog
- LANmonitor additionally lets you export the syslog from the device and save it to a file. Simply click on the entry for the device with the right mouse button and select View Syslog from the context menu. A snapshot of the current status is displayed. Clicking on Refresh exports a copy of the current syslog and this is dispayed in the window. Save syslog... stores the current display to a file. The content of syslog files can be viewed with Load syslog....
Note: SYSLOG messages will only be written to the device's internal memory if the LANCOM was entered as a SYSLOG client with the loopback address 127.0.0.1.
Alternatively you can view the current SYSLOG messages on the first page of WEBconfig on the SYSLOG tab:
