tdanner ✭✭✭✭✭

The release I mentioned above has now entered the RC stage.

Sorry about that. It looks like the documentation generator is not listing the inherited properties. The "Status" property is defined on System.ManagedEntity, which is the base type for Orion.Nodes (and Orion.NPM.Interfaces and Orion.APM.Application, and so on). I'll get that fixed for the next SDK release. Until then, the…

Yes, this was added several versions ago. Docs here: NPM Universal Device Pollers · solarwinds/OrionSDK Wiki · GitHub

There's a bug in this Edit page. Whatever you put in the "filter" text box gets validated using a query that is different than the one used to fetch data for the actual pie chart. The result is that any filter that passes the edit page's validation won't actually work. And a filter that would work won't pass the…

The "has changed" condition in Advanced Alerts promises much more than it can actually deliver. We only support "has changed" for Last Boot, IOS Version, and IOS Image Family. Not very helpful, I know, but it does explain why it hasn't been working for you.

No time frame I can share.

FYI - IPAM 4.5 just hit Release Candidate. This version adds an API for many IP management tasks. See docs at https://github.com/solarwinds/OrionSDK/wiki/IPAM-API If you are an IPAM customer with active maintenance you can try it out.

That's a good idea. I'll include that.

Oh, I see. Your plan makes a lot more sense now. Have your script write the data to a CSV file in a fixed location. Then have a SAM script monitor read find the data for the current node in that file and return it as the component status/statistic data. If you are working in PowerShell, the Import-Csv cmdlet makes this…

I have the logs - I'm looking at this now.

Proxy.aspx is definitely the cause. A workaround would be to hit Back until you get to the version of the page that doesn't have Proxy.aspx in the URL. The next service release will have some extra tricks to fix some cases that are exposing Proxy.aspx.

We didn't have plans for a DATEADD function yet, but that's a very reasonable thing for us to include. I opened a feature request for it. 308248 is the internal case number.

I reread your question and realized this might be trickier than I thought. You can set the https address for the Information Service to anything you want, even something that won't resolve locally. But you can only set it to one thing - there isn't a way to use different hostnames in the WSDL for different clients…

The issue with Web Node Management failing when WebUserSettings references a non-existent custom property is fixed in 9.1.

Then you need to call this verb on SWISv3, not v2.

The error from NPM 12 should be fixed in 12.1. Could you post more details about exactly what error you are seeing and what triggers it?

I added a powershell sample for discovery that should give you a head start: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/DiscoverSnmpV3Node.ps1

As a matter of fact, there are some new API features for account management in NPM 12 (actually Orion Platform 2016.1, on which NPM 12 is based). See the bottom section of http://solarwinds.github.io/OrionSDK/schema/Orion.Accounts.html. What's your use case?

That's my fault - I left out the switch name in the Set-SwisObject line. Here's a fixed version: $swis = Connect-Swis -Hostname $hostname -Username $username -Password $password $CustomPropertyUpdate =@{ Environment = "QA"; } $uris = Get-SwisData $swis "SELECT uri FROM Orion.Nodes WHERE ip_address LIKE '10.1.%" $uris |…

That's correct.

Like you, I think this error message is unrelated. If you look at the bottom of the stack trace you can see that this is netpath failing to look up BGP AS ownership information: SolarWinds.NetPath.Bgp.Statistics.StatisticsClient.RipeStatClient. There's no one unique cause for "An error occurred when verifying security for…

I think we can bang something together for that. The key trick is that the normal report page (/NetPerfMon/Report.asp) will take a net object in the URL if one is present. So if you build a report like Caroline described, you can get it to do macro replacement (like ${NodeName} or ${NodeID}) for a specific node by adding…

Which box is ticked? Have you copied the report files to the web server?

Looks like I misread the script. You are already adding all of the appropriate pollers. You correctly identified the problem with AppStack when you said, "Even though I am setting the VolumeTypeID to "4", it shows as "0" in the database manager. " I went through the code to figure out why your VolumeTypeID property value…

We are getting burned (again) by PowerShell's implicit conversion of single-item lists to just items. We can force PowerShell to make $nodeuri a list by wrapping the expression in @( ... ). Like this: $nodeuri = @( $nodeuri |ForEach-Object {[string]$_} ) The example script (exactly as written) doesn't have this issue…

Go back to the query you had on Monday: $swis = Connect-Swis -username '' -password '' -hostname '' $Nodeid=Get-SwisData $swis "SELECT NodeID FROM Orion.Nodes WHERE SysName LIKE 'Nodename'" Does that work now? (assuming you fill in the username, password, and SolarWinds server hostname)

It is not enough to call Connect-Swis - you need to save the connection object that it creates to a variable and then use it with the other swis cmdlets. Like this: $swis = Connect-Swis -username '' -password '' -hostname '' $Nodeid=Get-SwisData $swis "SELECT NodeID FROM Orion.Nodes WHERE SysName LIKE 'Nodename'" (I am…

Sure enough - there it is in the original post. I hope nobody else gets tripped up by that. A lot of languages with similar "." syntax for calling methods do allow for whitespace between the object reference and the method call, but apparently PowerShell doesn't like that.

Answered in your other post - Re: Orion SDK with PowerShell - manage/unmanage multiple nodes. Use [DateTime]::UtcNow.

To query, POST to https://server:17778/SolarWinds/InformationService/v3/Json/Query with a body like this: { "query": "SELECT NodeID FROM Orion.Nodes WHERE SysName LIKE @pattern", "parameters": { "pattern": "MyServerName%" }} To unmanage a node, POST to…