dthvt

akhasheni‌, I think what cdoyle‌ is trying to direct you towards is Universal Device Pollers which are separate and distinct from "Custom Pollers" being discussed here. This video might help explain: Video Tutorial: Universal Device Poller in Orion NPM - Videos | SolarWinds

I personally found this to be a very annoying change. My NOC staff want to display the active alerts on a screen on the wall, but now the wall will only show the latest 5 alerts. This isn't particularly useful! A way to customize this or another "All Alerts" object that could be added to the view instead would be a huge…

Thanks fcaron!

cdoyle‌ the last two screenshots look like duplicates - is the final screenshot supposed to show something different? Cheers!

I'm very interested in getting to NPM 11.5 and SAM 6.2. I saw today that the GA release was on my customer portal, but when I checked SolarWinds Knowledge Base :: Compatibility of SolarWinds Orion Products for Installation and Upgrade to map out the upgrade path, I see that several of my other products do not list NPM 11.5…

Hmm, well, we're on NPM 11.5 and SAM 6.2 and still seem to have this problem. I was hoping there was a VMware fix that I didn't know about! Thanks

Thanks Jiri! Kind of troubling that the validation logic doesn't catch that, though...

As I suspected - thanks for the quick reply!

Could you clarify what upgrade fixed this for you?

If you're talking about Orion monitoring an application server protected by SRM (and I think you are?), then what you do is set the DNS TTL to a reasonably short interval and mark the node as "dynamic" is Orion. Orion then uses DNS to lookup the node name and will dynamically update the polling IP when it changes. We use…

I'm no NCM expert, but I believe you'll have to do a few things manually on the replacement switch to 1) get it on the network and 2) setup credentials for NCM. After NCM access is restored, you should be able to go to the switch node details page, configs tab, and find the Upload Config widget. I'd upload the last config…

Petr Pribyl this was fixed in IPAM 4.3 in case you weren't notified. Cheers!

There is a bug in the Server Clock Drift (Powershell) - Clock Drift NTP component. If you make the following changes it should work reliably, I think. Starting around line 24... ===== If ($remoteToSolarSkew) { $Skew = $remoteToSolarSkew.TotalSeconds - $ntpToSolarSkew; $stat=[math]::round($Skew,2);…