tdanner ✭✭✭✭✭

Yes.

The report builder doesn't really care what the query returns - it is just going to format it as a table and show it to you. But the alert builder needs the query output in a specific format because it is going to trigger an alert on the objects (nodes, in this case) that are identified by the query. What would you want…

I forwarded your question to the IPAM dev team in case they have some suggestion that would help you. The reference documentation should be on the start menu under "Schema Reference" where you installed the Orion SDK.

Can you share your script?

Community strings for SNMP v1/2 are added by their credential IDs, just like SNMP v3 credential sets. To set custom property values, you need to wait for the discovery job to complete, get the NodeID of the new node(s) and then update them like this: orionsdk-python/custom_property_update.py at master ·…

The POST body should look like this (whitespace added for readability): [ ["swis://server/Orion/Orion.Nodes/NodeID=1", "swis://server/Orion/Orion.Nodes/NodeID=2", "swis://server/Orion/Orion.Nodes/NodeID=3"], "2017-04-27T19:22:28.0148691Z", "2017-04-27T20:22:28.0148691Z"]

Yes, I would start form there. Especially for discovery - the complex objects used by the Orion discovery API are much easier to work with in JSON than SOAP/XML. This sample for calling discovery is in Python, but it may be helpful in illustrating the objects needed:…

Here's a query that returns the data you want. The formatting isn't ideal since Custom Query Resource doesn't give you a way to control the column span of the table cells. SELECT n.caption as Node, '/Orion/images/StatusIcons/Small-' + n.StatusLED AS [_IconFor_Node], n.ipaddress as IP_Address, n.ObjectSubType as…

Yes, this API is fairly complex. I wish I had a simpler one to offer you, but this is it. Another way to handle this would be to let discovery add all the interfaces and then delete the ones you don't want to monitor after it completes.

I think this is the proper link: http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2012/03/06/how-to-automate-the-creation-of-orion-platform-aka-core-nodes-from-the-api

Strange error. Could you post the full request that led to this?

There are a bunch of verbs. You can get a list with a query like: SELECT v.EntityName, v.Name, v.Arguments.Name, v.Arguments.Type FROM Metadata.Verb v

The string between "swis://" and "/Orion/" is the "system identifier". It is set at database creation time. For details see https://github.com/solarwinds/OrionSDK/wiki/Uris#system-identifier. Instead of constructing $uri like this: $uri = "swis://fmorn1pp01/Orion/Orion.Nodes/NodeID=$($nodeProps.NodeID)/CustomProperties";…

The command discussed in this thread is not PowerShell syntax. It's probably Python. To see how to access the Orion API from PowerShell, start here: https://github.com/solarwinds/OrionSDK/wiki/PowerShell

Sure.

The syntax of the query looks fine, so I suspect a problem specific to Orion.Netflow.Flows. I have forwarded your question to someone who knows more about that particular entity.

By default, Events get purged after 30 days (you can increase this in the Settings). So it might just be that these nodes have been down longer than that. A better version of the Outages resource could do an outer join to the Events table instead of an inner join. Then it could list all of the down nodes and only include…

Now I understand your goal. I have noted the feature request.

Exactly. If you use agent-initiated communication, when the agent starts up on the newly-cloned server it will contact the Orion server and finish provisioning as a unique agent. If you use server-initiated communication, then you would have to tell Orion when a new server is up and give it the address so it knows to go…

Perfect.

Orion 9.0 should have required you to install .net 3.5. Did it not?

You may be hitting this bug: https://github.com/solarwinds/OrionSDK/issues/92 . If you can post your code for adding the node, it will be more clear.

What does get-interface-status.py do?

I think your copy of the script has some strange characters in it. Possibly it is using typographic em dash characters instead of the normal hyphen character to indicate a command-line flag. Try retyping the New-SwisObject line instead of pasting it in.

Are you polling this Windows host from Orion using SNMP or WMI? My script above is for SNMP nodes. "How does SolarWinds link up the volume I've created with the SDK to an actual volume on the Windows host?" For SNMP, this works by matching up the VolumeIndex property with the corresponding SNMP volume index…

This method of setting NextRediscovery should work fine when the script is running on a machine with german locale. SwisSnapin for powershell uses the ISO 8601 format for date/time values (looks like this: 2013-09-19T04:21:44.2207002-05:00), which is unambiguous with respect to locale.

What version of the product are you using? Does it work if you use a regular Orion (sql) account instead of an AD account?

This line: $UserPassword = Get-Content $PasswordFile | ConvertTo-SecureString is probably where the problem is. password.txt contains the encrypted password. But this encryption is tied to your user account, so when the service account tries to use it, it fails.

The error message you received refers not to "SolarWinds VoIP Module Service" (this only need to run on your poller), but to "SolarWinds Orion Module Engine". Since you aren't installing a VoIP license on your main server, you should disable the VoIP Module Service on that server. Please check if the Orion Module Engine is…

The REST API is only supported in SWISv3. For SWISv2 (including NCM) you must use SOAP or PowerShell (use the -v2 option to Connect-Swis). NCM 7.3 moves that product from SWISv2 to SWISv3, so you can access data through the REST API. This version is now at the release candidate stage: SolarWinds NCM 7.3 Release Candidate…