tdanner ✭✭✭✭✭

I tried your script in our lab. Here are the changes I needed to make to get it working: # Add two properties to the $swis->Create('Orion.Nodes', { ... }) call: 'NodeDescription'=>' ', 'EntityType' => 'Orion.Nodes', Add the "N.ResponseTime.ICMP.Native" and "N.Status.ICMP.Native" pollers. Note for future readers of this…

From looking over the relevant code, it looks like this error would come from missing the "WMICredential" entry in NodeSettings for this node. In the sample script (OrionSDK/CRUD.AddWMINode.ps1 at master · solarwinds/OrionSDK · GitHub), this entry is provided by these lines: #Adding NodeSettings$nodeSettings = @{…

The JSON API supports all of the same operations as the SOAP API. NPM supports some insert/import operations through the API. If you'll describe what you want to do I can let you know whether those specific cases are supported or not.

> can i export to xml then re-import Xml and use this method to bulk import Web based reports? Yes, that should work.

> What is the syntax for unmanaging interfaces? Answered in your other thread: What is the syntax for unmanage an interface in Python using swis.invoke() method? > where can I find the format of the invoke for various entities? In SWQL Studio, you can expand the entity nodes in the tree to see the verbs (listed after the…

Right - flip the order of the tables and reverse the join direction. So if you have: FROM x RIGHT JOIN y You can change it to: FROM y LEFT JOIN x

After you get the "object reference not set" error, please run this command and post the results here: $Error[0].Exception.ToString()

Just run "Install-Module SwisPowerShell" and let powershell handle downloading and installing it.

Pretty close. The body for an Invoke call is always an array. For Cirrus.ConfigArchive/Execute, the first argument is also an array. The "transfer ID" string uses the NCM NodeID (which is a GUID), not the integer NodeID, and the username segment is not wrapped in {braces} - that's just powershell string interpolation…

JSON strings use double-quote delimiters. From PowerShell you can also build up your body using powershell objects and use the ConvertTo-Json cmdlet to handle the json syntax for you. Like this: $args = @( 'N:1261' ) $json = ConvertTo-Json $args

A few months ago another user had a similar error. We didn't manage to run it to ground, unfortunately. The next troubleshooting steps are explained in this post: Re: http request was forbidden with client authentication scheme 'Basic' . Please follow the steps there to see if your symptoms match that user's and we'll…

Could be caused by a DirectLink account.

It's the load average. For Cisco devices, we use the 1 minute average (CISCO-PROCESS-MIB::cpmCPUTotal5min - 1.3.6.1.4.1.9.9.109.1.1.1.1.5) if your polling interval is less than 5 minutes, otherwise the 5 minute load average. For servers (Windows, Unix, Linux, etc.), we use HOST-RESOURCES-MIB::hrProcessorLoad…

That is correct. Note for the future: starting with Orion Platform 2018.4 (NPM 12.4), currently in the release candidate stage, SWIS will also accept verb arguments in json object format. In this format, the names matter but the order does not. The json array format will still be accepted. I think the json object format…

I forgot: NCM still only supports SWISv2. Try this: $swisv2 = Connect-Swis -Credential $credentials -v2 Invoke-SwisVerb $swisv2 Cirrus.Nodes AddNodeToNCM $nodeId

Right. The microsoft tool that generates a C# web service client from WSDL is generating bad code when consuming the SWISv2 WSDL. (This is somewhat odd, because this WSDL is generated by WCF, another microsoft framework, so you would expect them to work together.) The SWISv3 WSDL does not have this problem, and a client…

The PowerShell cmdlet API makes it really easy to collect values provided by the pipeline and commit all at once at the end. https://github.com/solarwinds/OrionSDK/blob/master/Src/SwisPowerShell/RemoveSwisObject.cs

The trap template specifies what OIDs should be in the trap Orion sends and what their values should be. Generally most of the values will actually be macro references that are resolved in context when the trap is actually sent. What is a Trap Template?

It looks like there is a bug in how SWIS deals with Uris for Update that prevents it from working with Databases. Basically, "swis://myserver.mydomain.realm/Orion/Orion.Nodes/NodeID=5555/Applications/ApplicationID=999" refers to an object of type Orion.APM.Application. That type does not have a "Databases" property - only…

That verb is only available in SWISv3. You will need to use a URL like this: https://$hostname:17778/SolarWinds/InformationService/v3/OrionBasic

Re: HTTP response codes. Looking at the code, it appears we are returning 401 Unauthorized for bad credentials, 403 Forbidden for good credentials but not allowed to perform requested operation, and 400 Bad Request for all other conditions. I agree that 404 would make sense in this case, and 500 would probably be a better…

The CustomPollerAssignmentID column in the database has a default constraint of "newid()". When you assign a custom poller through the UI, the product inserts a row into that table (this is not the only thing that happens!) and does not specify the CustomPollerAssignmentID value. SQL Server then generates one for us.

When using "Connect-Swis" you include the "-Trusted" option instead of "-Username xxx -Password yyy" or "-Credential zzz". Here's a screenshot:

The self-signed certificate situation in Orion is unchanged.

Here's an overview: Use Active Directory credentials for users in SolarWinds NPM - SolarWinds Worldwide, LLC. Help and Support

Interfaces is a navigation property. You need to specify which properties of the interfaces you want returned. Like this: SELECT N.NodeID, N.IPAddress, N.NodeName, N.Status AS NodeStatus, N.Interfaces.InterfaceID, N.Interfaces.Caption, N.Interfaces.Status AS InterfaceStatusFROM Orion.Nodes N On the side question:…

The internal bug is CORE-5972. (You can call support and ask them about it, but they won't keep the ticket open for a feature request.) The bug has links to this thread and others that have requested this. When the implementation ships, I'll go back and update those threads.

We've checked the basic stuff, so it's probably time to open a support ticket.

I asked Casey to look at your issue #1. He's travelling, so it will probably be tomorrow before he can get back to you.

I believe that you were able to get a connection working in another thread. Is that right?