The first component of a good network management system is an event handling system. A basic event handling system can be easily implemented with open source tools like syslog-ng . Just watching the new events arrive can be very enlightening. Many network operations teams gain visibility into their network...

I've been doing some more reading about network event handling and found some interesting articles and a few facts that I'd like to share. I have my own ideas about handling network events, but am open to learning what other people do and why they prefer their approach. It helps me learn new...

I just finished posting a neat syslog summary script that was passed to me by Phil Koontz. He uses it every day to keep track of syslog events. You can download it from the Netcraftsmen website: http://www.netcraftsmen.net/Resources/Technical Articles/Syslog Summary Scripts . (While you're there...

I'm continuing the list of NMS event handling requirements. Unstable interfaces In the last post, Handling Event Data, Part 1, I talked about correlating interface up/down events. I would also like to know if an interface is unstable. This is where the interface is going up and down on a regular...

I've been examining the handling of event data and wanted to share what I see as common requirements. For the next few posts, I'll describe the requirements and why they are important. Syslog Summary My first requirement was addressed in the prior post about Syslog Summary Scripts (also see the...

I'm working on network management requirements for several customers and keep running into the same requirements. One of the key requirements is that of event reporting. Events typically take two forms: syslog and SNMP traps. In both cases, they are asynchronous notification of something happening...