Required Resources

$3$ Routers $($Cisco $1941)$

$2$ Switches $($Cisco $2960+$ with Cisco IOS Release $15\mathrm{.}2(7)$ lanbasek$9$ image or comparable$)$

$3$ PCs $($Windows OS with a terminal emulation program, such as PuTTY or Tera Term installed$)$

$$ Cisco Packet Tracer Simulation Software

Objectives

$$ Configure routers to log messages to the syslog server.

Background $/$ Scenario

The Syslog Server will provide message logging in this activity. You will configure the routers to identify the remote host $($Syslog server$)$ that will receive logging messages.

You will need to configure timestamp service for logging on the routers. Displaying the correct time and date in Syslog messages is vital when using Syslog to monitor a network.

The routers have been pre$-$configured with the following passwords:

$$ Enable password: ciscoenpa$55$

$$ Password for vty lines: ciscovtypa$55$

Step $1$: Configure routers to timestamp log messages.

Configure timestamp service for logging on the routers.

R$1($config$)$# service timestamps log datetime msec

Step $2$: Configure the routers to identify the remote host $($Syslog Server$)$ that will receive logging messages.

R$1($config$)$# logging host $192\mathrm{.}168\mathrm{.}1\mathrm{.}6$

The router console will display a message that logging has started.

Step $3$: Examine logs of the Syslog Server.

From the Services tab of the Syslog Server$$s dialogue box, select the Syslog services button. Observe the logging messages received from the routers.

Step $4$: Configure the logging severity level on R$1.$

Logging traps can be set to support the logging function. A trap is a threshold that when reached, triggers a log message. The level of logging messages can be adjusted to allow the administrator to determine what kinds of messages are sent to the syslog server. Routers support different levels of logging$.$ The eight levels range from $0($emergencies$),$ indicating that the system is unstable, to $7($debugging$),$ which sends messages that include router information.

Define the level of severity for messages sent to the syslog server. To configure the severity levels, use either the keyword or the severity level number $(07).$

Severity Level Keyword Meaning

$0$ emergencies System is unusable

$1$ alerts Immediate action required

$2$ critical Critical conditions

$3$ errors Error conditions

$4$ warnings Warning conditions

$5$ notifications Normal but significant condition

$6$ informational Informational messages

$7$ debugging Debugging messages

Note: The severity level includes the level specified and anything with a lower severity number. For example, if you set the level to $4,$ or use the keyword warnings, you capture messages with severity level $4,3,2,1,$ and $0.$