ttl ✭✭✭✭✭

newkidd2 wrote: To my knowledge, Orion does not use the ${Status} variable that is in the Subject line. It merely uses it for displaying the status of the interface at the time the alert was generated. I concur with my fellow Thwackers who stated that Orion probably that the problem may be with the alert as it has been…

Thanks for the help!

I think perhaps "solved" is not the right word, since the problem exists again with the exact same symptoms.

We have IVIM version 1.5.0 (if this is what you mean), but still have this problem.

The errors occur twice in one second, every 21 seconds or so. We have a daily NS job that runs once a day, but it doesn't run on the network where the IP lives.

350355

Here is the errorlog... it appears to be having trouble creating a table?

This isn't working for me... while the Custom Poller returns a value of 56, I only get a value of 1 from the Alert testing: switch1 (192.168.0.1) reports Critical temperature issue. Current temp degrees C: 1

Where would I do this? We're using the built-in Scheduled Task monitor that shows up in the node. The node polling options are only SNMP and WMI (we're using WMI).

It actually uses ${Status} in the Subject line, so that's apparently what NPM was reporting.

A real, physical interface certainly fits the bill then. So why doesn't it show up under SAM?

OK, I have set this up so that it's supposed to send us config changes in a separate HTML e-mail, and ONLY e-mail us otherwise if there is an error in the backup. However, we now receive TWO e-mails, one with the job completion (no errors) and one with the HTML e-mail!

Thanks!

My concern is actually that after having spent a decent amount of time learning to create Advanced Alerts fairly quickly, there is now a learning curve where I have to get back up to speed, which is going to slow me down. We have dozens (probably closer to 100) alerts, so going through all of them to ensure that they're…

Thanks Roman, I really appreciate the help, but some of these files have IP addresses and hostnames that I can't really post up in a public forum. Can this be done via private message?

I even opened a ticket with Solarwinds Support (ticket 578821) and was to that that option "is not yet available even on the latest version of NPM", even though it seems to partly work. If I can get support for this that would be great, since you say it's supposed to work now... ?

For one that's having a problem, the Current Value says NULL. However, within both the UnDP application on the NPM server and within the assigned poller in the NPM Web interface, the value is 163.

Now I'm getting some really bizarre behavior. The rule has reset itself to 1 event every 30 seconds with a response window of 1 second. The criteria I defined (in fact, all criteria within the Advanced Thresholds) is gone. If I re-set it and Apply or even save, it makes no difference, it doesn't take. Guess it's time to…

That's why I'm installing 9.4.2 -- the release notes say that one of its fixes is that it goes great with Server 2012 R2.

Sure. I have a thread about it here: http://thwack.solarwinds.com/message/226457#226457 The function works on some OIDs and Nodes, and not others. Screenshot

Agreed... I think that's one of the only movies I've seen him in where he wasn't like a cheese grater to the elbow...

Perfect, thanks!

Irfanview (free and awesome graphics viewer) > Image > Effects > Explosion (they also have Pixelise which does a nice job of obfuscation.)

Thanks!

Original ticket was 640090. New case is 710716.

Where are you finding HF3? I'm logged into the Customer Portal under Downloads, Service Packs & Hotfixes and I don't see anything for NPM.

cahunt ... I'm curious why it sounds like you're reprimanding me, when a) I never said that support was only for me, and b) you've had the same problems. As of this writing, we HAVE been on the phone with SW Support for hours; and that isn't the problem either... it's that when we had the problem, nobody answered. They…

Yes. They contend that this is Cisco's problem, even after I mentioned that I didn't have this problem for quite some time until I updated to NPM 10.3. No polling logs were ever requested, no packet captures, just an old link to a Cisco Community discussion that ends with a post reporting that the "fix" in the thread…

We had the problem happen once more some time after the fix, but it hasn't happened again since. The fact that it happened again though implies that the fix isn't actually The Fix .

So what is the solution if the IP address in question isn't even a monitored node in NPM? We've gotten hundreds / thousands of them for one unmonitored IP.