Powered by Blogger.
Showing posts with label syslog configuration on cisco routers. Show all posts
Showing posts with label syslog configuration on cisco routers. Show all posts

Syslogs Part III


Now we are going to configure our SYSLOG server and will enable the router to send logs, upto severity level 7, to our SYSLOG server:




Great, now we can see the log messages coming to our SYSLOG server:






Isn't it interesting, that all the changes, critical warnings are available to you on a nice looking NMS interface. Such things are really useful in a Network Operations Center. This NMS can also be configured to send email to a group in case some warning arrives that match to our define thresholds. The kiwi SYSLOG manager is another good tool to monitor the log messages on an NMS. We will end our discussion by showing you all the stored logs in buffer on R1 by issuing the following command:






As can bee seen, all the log messages of our router are stored in the router buffer, we can track the history of any critical issue/outage and other many things from these SYSLOGS. 


Syslogs Part II


SYSLOG server Configuration in GNS3:

We are going to configured R1 in GNS3, and using the WhatsUp Gold SYSLOG manager to collect all the logging information from R1. WhatsUP gold SYSLOG manager is a free tool and you can download it after a brief registration on WhatsUP Gold website.  






















We are using below mentioned topology for our LAB:























First of all, we enable logging severity level 7 on our router (R1):

R1(config)#Logging console 7

This will enable all sorts of logging on the router. Now let's store all this logging information in our logging buffer:

R1(config)#Logging buffered 7

It's better to specify logging buffer size too. Okay, one other thing, I would like to show you here , is the logging options available on Cisco routers:






















( more stuff will be coming soon :) ) 


SYSLOGs


SYSLOG or system logging is one of many interesting concepts in Cisco world. Log messages monitoring and audit is one of the main parts of a network engineer life. Log messages are displayed in real time on the route, once we make some changes in the network, or if any issue happens to our network devices. We can also send these log messages from the router to a centralized NMS for monitoring in a Network Operations Center.  IOS can log messages to :

  • Console
  • Monitor (VTY, AUX) usually enabled via terminal monitor command in global config mode.
  • Buffer
  • Trap (SYSLOG) to send logs to an NMS


One important thing to understand is the concept of logging levels. Logging levels simply specify the type of log messages we want to send to our desired logging buffer/terminal/server.  Different logging levels can be set via logging console command:



Let understand severity level concept:


Severity level 3 means 0, 1 , 2, 3 ( severity level  0/1/2/3 enabled), and the router will send all corresponding severity level log messages to our desired destinations.
If we don’t want to mention the severity level # , we can specifity the name of the logging severity, for which we want the router to send all updates, for example if we want to send all Critical Condition logs, we can enable it via the following command :

R1(config)#logging console critical

The severity level command comes in handy, when we want to enable different types of logging in one go. 

In the second part of this article, i will discuss the practical implementation of SysLog in GNS3.