clubjuggle

No problem, thanks for the update!

I'm actually referring to alerts, not to the unmanage task. You don't want to delay the unmanage task. If you're not getting alerts about the unmanaged status of the remote location, you can ignore my last post.

You've got it.

I just checked with my coworker who checked on this earlier this morning. They have stopped, so it looks like that was it.

Any time a node goes from unmanaged to managed, it status will be unknown until the next poll (even if it's ICMP, the pings have to be sent). It can take a couple minutes until that happens, depending on the load on your poller. This is because the unmanaged device has not been checked for the duration of the unmanage…

Ah, gotcha. I wonder if maybe that's a SAM function then. I'm honestly not sure. Hopefully someone else will see this and can chime in.

Awesome. Thanks DanielleH!

I would create a special condition of Volume / Volume Percent Available / Is Greater than / 5. If you reset when the condition is no longer true, you will get a reset message if the percent available drops below 2%, which is likely not what you want (if it is, then you can use Condition is No Longer True).

No problem, good luck! Be sure to let us know in the morning how it worked out.

That makes sense then. For a static change like this I personally find the Configuration Management feature easier to use, because all you need to type in is the exact commands you would enter in the CLI. There's no additional overhead for the script. Your way isn't wrong, it's just different from where I assumed you were…

Sorry for the delay in getting back to you. It should be under Network Nodes/Current CPU and Memory, as below. Screen shot is from 2014.1.0 so I'm actually a version behind you.

That's what I was thinking. Unfortunately I can't speak to the mechanics of making this work, only that I had previously seen it as a suggestion. I personally go for the agents in this type of scenario, but recognize that may not be a viable option for you in the short term.

It looks like that was it. IPAM was scanning using the old credential. I'll know for sure by tomorrow morning. Feel free to poke me if I don't either respond back here or mark your answer correct.

That's perfect. Thanks Zack!

I'm not sure how to check for that. If I import the nodes in small batches, it works, but that's a very long process when you're trying to import 233 nodes.

You're correct. You do have them reversed.

Is the reliability concern on the Solarwinds-to-cloud leg, or the cloud-to-recipient leg?

Doesn't that delete all traps from the database? If so, I would think that would be an important thing to mention to the OP.

I'm pretty sure they're static. The IPs don't change in any case, so if they're not static they have reservations. The reverse DNS lookup works just fine. EDIT: Sorry, I just realized this reply wasn't to me.

No worries... thanks mrs.alterego‌ and maria.bungau‌ for your help!

It should be safe; it may be worth confirming that SNMP works to the target node from its assigned poller and that your firewall isn't blocking something you thought it was permitting. That having been said, if you have the option to permit ICMP traffic between the node and the poller, that will be more efficient and…

I narrowed the issue down to the fact that there were two (sanitized) http links in the sample error message I had posted. When I took them out, the content posted. It would be nice if the error message were more specific, or if the system would figure out that a level 9 Thwack user probably isn't a spammer.

If it's just happening with groups and not individual AD accounts, check out this thread. Apparently the method of doing AD authentication changed between versions 9 and 10, and that may be causing your issue: Windows Passthrough Authentication Not Working in NPM v10.1.3

We do have IPAM. Does IPAM use SNMP?

Clearly so we can mock the naive mistakes of our peers, all while downplaying our own.

Thanks. I'll give that report a shot. It sounds like we could also use a feature request for the import.

You need to manually open the Windows task scheduler after you create the CMD file and schedule the job from there.

Where are you doing this? This should be under the Configuration Management section. I don't even see a validation option there.

Your problem is almost certainly unrelated to the original post in this thread (from 2009), but if you can post your query, perhaps we can help.

No worries! I had to go double-check to be sure. :-)