Syslog Tutorial
Syslog Tutorial
As an administrator of a network, you have just completed all the configuration and they are
working nicely. Now maybe the next thing you want to do is to set up something that can alert
you when something goes wrong or down in your network. Syslog is an excellent tool for
system monitoring and is almost always included in your distribution.
Note: If sent to a syslog server, messages are sent on UDP port 514.
By default, Cisco routers and switches send log messages to the console. We should use a
syslog server to contain our logging messages with the logging command. Syslog server is the
most popular place to store logging messages and administrators can easily monitor the
wealth of their networks based on the received information.
Syslog syntax
Note: You can remember the order above with the sentence: “Eventually All Critical Errors
Will Not Involve Damage”.
The highest level is level 0 (emergencies). The lowest level is level 7. To change the
minimum severity level that is sent to syslog, use the logging trap level configuration
command. If you specify a level, that level and all the higher levels will be displayed. For
example, by using the logging console warnings command, all the logging of emergencies,
alerts, critical, errors, warnings will be displayed. Levels 0 through 4 are for events that could
seriously impact the device, whereas levels 5 through 7 are for less-important events. By
default, syslog servers receive informational messages (level 6).
Syslog Configuration
The following example tells the device to store syslog messages to a server on 10.10.10.150
and limit the messages for levels 4 and higher (0 through 4):
Router(config)#logging 10.10.10.150
Router(config)#logging trap 4
Of course on the server 10.10.10.150 we have to use a syslog software to capture the syslog
messages sent to this server.