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?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
JFrederick29Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.