tdanner ✭✭✭✭✭

In general, anything you can do with the SOAP API should work with the REST API as well. To diagnose your "400 Bad Request" error, I would need to see more details about how you are making the request. But my first guess is that you are putting the SWQL query in the URL query string and not URL-encoding the "%" character…

CSClient is one of the samples installed with the Orion SDK. To get started, I recommend you just make a copy of that directory and implement your logic in the Main() method in Program.cs. I'm curious - what's your motivation for moving from PowerShell to C#? For SDK programming, I find PowerShell to be much more…

Is your system heavily loaded? Is the web console slow in general? It might be helpful to look at when in the request/response sequence the delay is occurring. curl with verbose output could help. Like this: curl -k -v -u "myusername:mypassword"…

What process is using the CPU? The high disk queue length could well be a bigger performance drag than the CPU.

One way to see if is working would be to install a .NET 3.5-using application and see if it works. Like Orion. You could also do a pre-emptive repair of .NET 3.5 and see if you get the error during that process.

When I get no output from curl, my next step is always to add "-v" to the command line so I can see everything that happens, including the TLS details all of the request and request and response headers. Try that and see if it helps.

That syntax error looks to be due to a missing "WHERE" before the (DateTime BETWEEN ...) part. Adding that highlights the next problem which is that you should only use the namespace qualifier ("Orion." or "Orion.NPM.") when referencing an entity after FROM or JOIN, not in the SELECT, ON, WHERE, or other clauses. In those…

Ok, it looks like when you have literal xml that you need to pass to a SOAP method, you wrap it in SOAP::Data->type('xml' => ...). So your call would look like this: my $groupId = $swis->Invoke("Orion.Container", "CreateContainer", ["S".$store, "Core", "60", 0, "Test", "true", SOAP::Data->type('xml' =>…

The problem is that it will wind up passing that xml as a string rather than an object. I need to figure out the syntax for perl to pass an object through Invoke. It might require an update to InformationService.pm.

Looks like I guessed wrong. What SolarWinds product is this related to? Could you post a link?

You can programmatically clone a view using the Orion.Views.CloneView verb (two parameters: the ViewID of the view to clone and the title for the new cloned view; returns the ID of the new cloned view). But there's currently no API for changing the object targeted by a Custom Object Resource.

That's not a very helpful error. Add the "-v" flag to curl and you should get more information.

That's odd. You can download it from Microsoft: http://www.microsoft.com/downloads/en/details.aspx?FamilyId=860EE43A-A843-462F-ABB5-FF88EA5896F6&displaylang=en

This query is using SolarWinds Query Language (SWQL) syntax. It is similar to SQL, but there are differences. If you send this query to SQL Server directly (such as via the Database Manager tool or SQL Management Studio) you would get an error like this. Use SWQL Studio or one of the API endpoints to run it.

This line is wrong: $poller["NetObjectID"] = $nodeid; It should be this: $poller["NetObjectID"] = $volumeID; 

I passed your message to an IPAM expert. He's out of the office until Tuesday though.

Mystery solved! I think a clearer message on the page for getting the MST could help future users avoid this trouble.

Adding the data via directly inserting it to the database is not something SolarWinds will support. As you found, it kind of works but then gets deleted/overwritten on the next polling cycle. Adding the data via the SDK is not supported either - this time in the sense of it is just not implemented.

No. You can choose which users get access to node management, but not which features (unmanage vs. delete, etc.) they get. Note that website account limitations do apply to node management, so you can restrict which nodes a user can see.

Let's see if there is a clue in the SWIS log. Please trigger the "must declare scalar variable" error again, then look at the end of C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log for a matching error with stack trace.

Glad it's working now!

Yes, you can use SNMPv2 and v3 in the same discovery profile. Just add both types of credentials to the credential collection.

No, I don't know of an existing Python module for querying the SOAP interface for SWIS. Would upgrading be an option? NCM added SWISv3 support in 7.3. And it's up to 7.5 now - there are a lot of improvements since the version you are running.

Does this happen for any password you use for the new user? Try a few variations and let me know whether you get this error for everything or just certain patterns.

This is a bug in NPM 11.5.0 and 11.5.1. It was fixed in 11.5.2. I recommend you upgrade if possible (current version is 12.0.1). If that is not possible, this thread describes how to work around this custom property issue by fixing up the database after adding a node through the API: Upgrade from NMP 11.0.1 to 11.5 breaks…

What version of IPAM are you using? Recent releases have significantly improved the range of tasks that can be handled through the API. IPAM 4.5.x API · solarwinds/OrionSDK Wiki · GitHub IPAM 4.6 API · solarwinds/OrionSDK Wiki · GitHub

SWQL Studio is a useful tool for building and testing queries. When you are happy with the query, copy/paste it into your code.

Close. The body for AddInterfacesOnNode should look like this: [ 256, [ { "ifIndex": 83886080, "Caption": "mgmt0 · MGMT:descriptionText", "ifType": 6, "ifSubType": 0, "InterfaceID": 0, "Manageable": true, "ifSpeed": 0 },{ "ifIndex": 335544419, "Caption": "loopback99 · Failover mechanism", "ifType": 24, "ifSubType": 0,…

Sorry, martian monster​ - I lost track of this thread and forgot to follow up. It's been a few weeks. Where are you with this now?

Edit, later: this only applies to Orion NPM 10.1. Try this: Edit C:\Program Files\SolarWinds\Orion\Information Service\2.0\SolarWinds.InformationService.Service.exe.config. Find the line near the top that looks like this: <add key="InformationServiceBaseAddressHttps" value="">localhost:17778/.../InformationService" />…