Best practices for, logging traps on switches,Routers,Firewalls.

I am setting up a network consisting of a firewall, 7 switches, and two routers...I am just finishing up the config and wanted to do sysloging to a central server. My question is, when setting up the severity of the trap (warnings,errors,debug...etc) what would be a good starting point for setup, w/o being too chatty?  thanks
LVL 1
uncle_hoAsked:
Who is Participating?
 
JFrederick29Connect With a Mentor Commented:
If Informational is too chatty, I would go with Warnings (4) on the less critical devices (access switches) but stick with Informational in the core or on critical devices to provide as much info as necessary when troubleshooting.
0
 
JFrederick29Commented:
I set the syslog level to Informational.  Since you don't have that many devices, disk space shouldn't be an issue.  You can use a tool like Agent Ransack (free download) to parse through the log files....

If you go with the professional edition of Kiwi Syslog (for example), you can dump syslog messages from each device into a seperate folder/file which makes it easier to search the logs as well and filter out messages you don't want to see.
0
 
uncle_hoAuthor Commented:
Currently I am using kiwi syslog and I set it up to dump to a sql database. But what I am looking to do is be able to view the syslog on my desktop, to look for anything that might raise a alarm and not have to scroll real quick to see what it was.  I am also using kiwi to get traps from my prod server farm.
0
 
JFrederick29Commented:
You can setup Kiwi rules to send emails based on an event or severity level.  So, if any Critical alerts came in, they could be emailed to you as well as being logged to the database.
0
 
uncle_hoAuthor Commented:
I am currently doing that for any firewall/loadbalancer issues that are critical...what I am looking for is a logging level that is not too chatty, but still might give good into.
0
All Courses

From novice to tech pro — start learning today.