cberg42

Bump. Same.

jearle, I pass all of the below: depUri = swis.create( 'Orion.Dependencies', Name=dep['Name'], ParentUri=dep['ParentUri'], ChildUri=dep['ChildUri'], AutoManaged=False, IncludeInStatusCalculation=True, EngineID=0, Category=0, ParentEntityType='Orion.Nodes', ParentNetObjectID=parent_net_obj, ChildEntityType='Orion.Nodes',…

This sounds like you are pretty close to your goal. I also wonder if you have looked into filters to dynamically add nodes to groups based on custom properties? The filter logic can get pretty deep and include AND/OR statements. You can also filter other node properties, not just custom ones.

Cfy33678, Were you able to create dependencies in python, using the python sdk, rather than in powershell? Does anyone know if this is currently possible?

Did this functionality change? I am able to successfully execute a discovery with an interface configuration plugin defined, however, no interfaces are auto imported. 

Did something change in this functionality? I am able to execute the discovery successfully, however, no interfaces are auto imported. 

Pankaj, I am missing the same OID as you are on ~ 100 nodes. Were you able to make any further progress? -Cuyler

Just have to say that I love this idea.

I have been having a hell of a time trying to do this manually through the manage nodes interface. Did you ever get a chance to look for any of those examples? Thank you

I am running NPM 12.2.5300.360 and am wondering if this 2100 group limitation is still relevant, as well as if the performance issues have been addressed. sorry for hitting an old thread. Thank you

Unfortunately, I really don't know about doing both at the same time, I've never done it. But I imagine that we would be able to put both those values, IpRanges and Subnets, in the corePluginContext. If not I know that you can have up to 6 of these discoveries running at the same time. Good Luck !!

I changed your join < JOIN Orion.NPM.Interfaces i ON i.NodeID = p.NodeID AND i.InterfaceIndex = p.IfIndex > to a left join (not dropping from the interfaces table) and discovered that there are a ton of interfaces which don't have a port type. Do you have any insight on this by chance? Thank you!

Did anyone ever find a root cause for this issue, I am experiencing it today and can't generate any heatmaps. T

I would make sure that the children nodes don't have another parent. My understanding is that from the perspective of SolarWinds objects with multiple parents are treated as having redundant paths. Essentially they are evaluated as an AND not an OR, so the node would only show as unknown if both parent A and parent B were…

Does anyone know if any why this is still the case given that the report is generated by comparing against NIST xml files, which include the dot releases?

Hi clarv02 ! I use something like this: if networks[network][3]: sub = { 'SubnetIP' : networks[network][0], 'SubnetMask' : networks[network][1] } corePluginContext = { 'Subnets' : [sub], 'Credentials' : snmpDiscoveryCreds, 'WmiRetriesCount' : 0, 'WmiRetryIntervalMiliseconds' : 1000, 'IsDiscoveryForVimEnabled' : False }…