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...

We use syslog-ng as our syslog collector and distribute from it to the various systems that need to receive syslog messages. We have configured syslog-ng to forward the CONFIG_I messages to NetMRI. However, NetMRI uses the source IP address in the incoming syslog packet to determine the system that is...

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...

Check out the NetMRI General Discussion Forum

In order to build a custom Issue and generate a notification on a NetMRI, the device has to be one of the devices that NetMRI is currently collection SNMP information. There are several steps to run through to get this setup. 1. 1. Change the device Type of the device to a Type that NetMRI will generate...