ljenkins1

I know the feeling. One of the fools... I mean engineers previous to me used /16's for some of our networks... Networks with 50ish computers. The price on the IPX is frankly a bit insane for someone with about 1500-2000 nodes on the network.

Thanks, worked like a champ

I've turned the prompt detection all the way down to 5 seconds. I submitted the upload job to a few more devices. What is the session trace you are looking for? Is that the results button that comes up when the job eventually does complete? Or should I be looking somewhere else?

I had a support ticket open for a different issue, but that solution seems to have fixed this as well. Thanks

It shouldn't really be any different from inserting variables into e-mails. Here's a command I use in a script: c:\curl-7.19.5\curl.exe --basic --user "user:password" --data-ascii "status=Reset: ${NodeName} is now ${Status}. Outage lasted from ${TimeOfOutage} to ${DateTime}." "http://twitter.com/statuses/update.json" All…

I don't know if this is what you want, but I use a custom field called "TimeOfLastOutage" and have a basic alert fill that in, then the advanced alerts just reference that variable. It's always worked well for me.

Basically the same as jbaulsir's response, I use a custom property called 'DeviceClass'. And my advanced alerts look like Trigger alert when all of the following apply * Node status is equal to down * DeviceClass is equal to core And so on for all the different groups of devices.

Two possible solutions... I only turn on monitoring for interfaces that should always be up (servers and uplinks). This works well for me although I have to go and manually add the new interfaces when I want to monitor something new. Otherwise, interfaces that are down trigger a "node with problems", but interfaces that…