lerdalt ✭✭✭✭✭

We've just run into this as well, and not only should this be in settings, but possible to add on a per-device settting.

having the ability to have a primary/backup poller would be great. I've had instances where my additional polling engine has stopped and I might not know about it for too long. The ability for a backup or secondary poller to automatically take over for failover would be a great addition.

Can't vote this one up enough....

Not yet, since all of our scripting is done with Python from a remote system. But sounds like something I need to dive into more. Thanks.

Thanks, I've done some work with the API and Python to do assignments with success. Just hoping there might have been a better way within the platform to help manage it long term.

Cisco devices that still show up as a Machine Type of Cisco: CiscoCisco Identity Services Engine1.3.6.1.4.1.9.1.2786CiscoCisco Unified SIP Proxy running on NME1.3.6.1.4.1.9.1.2352

Possible to bump this again? Looks like it's been an ongoing concern for years now with plenty of demand. Or...is there anything we can be doing with our account teams to help bump this further?

not exactly the most helpful, but here is what I found: Search "pcu" (65 hits in 1 file) C:\ProgramData\SolarWinds\Logs\Orion\Core.BusinessLayer.log (65 hits) Line 477: 2019-11-25 15:37:12,722 [13] DEBUG SolarWinds.Orion.Core.BusinessLayer.JobSchedulerEventServicev2 - (null) Plugin…

Agreed...same problem here and hoping a solution exists.

I take that back, just found in Core.BusinessLayer.log *** Assembly SolarWinds.NCM.Discovery.Plugin, Version=2019.4.0.3834, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 *** 2019-11-25 14:53:53,912 [34] ERROR SolarWinds.Orion.Core.BusinessLayer.DiscoveryImportManager - (null) Exception occurred during…

Thanks, for now, I believe the inventory is being built dynamically. I just ran it again as a test to try and look at the information service logs, but unless I'm looking in the wrong spot, not really seeing anything of value there. I'm looking in: C:\ProgramData\SolarWinds\InformationService But I'm open to any and all…

Not yet. I had started down that path, but it looks like what I have in my notes is to invoke the Cirrus.Nodes AddConnectionProfile. But I don't have a working solution on this just yet.

Reset both server and services, ran repair on all the modules, configuration wizard, database maintenance....about everything I could think of. Discovery through network sonar does work successfully which is what really throws me off on it. Was hoping someone here might be able to help give some direction on where to look…

2020 now, any updates on if this is possible?

Also, curious about how the IpAddressV4 output is formatted. By that header, I would assume it to be IpV4 addressing, but I'm getting variants of integers, that do not resemble any sort of IP address

I recently just did something similar, but this should be the uber simplified line that you would be looking for to add a device for management into NCM: ncmNodeID = swis.invoke('Cirrus.Nodes', 'AddNodeToNCM', nodeid) You just need to know the NPM node Id to toggle adding the node into NCM.