tdanner ✭✭✭✭✭

This has been entered into our bug system, but the fix hasn't been released yet. If you want support to notify you when the fix is released, you can open a ticket. Mentioning bug #2416 will save time.

Yes.

What about including the "Z" suffix on the date time string? This indicates that it should be interpreted as UTC.

I recommend using SWQL Studio to explore the IPAM object model. You can download it from https://github.com/solarwinds/OrionSDK/releases/latest . You can also see an HTML dump of the schema for all Orion products at http://solarwinds.github.io/OrionSDK/schema/ . You probably want to start with IPAM.Subnet.

Are there any account limitations on the account used in production where you get the error?

There are a few references to "snmp" for settings like SnmpRetries and SnmpTimeoutMiliseconds. But if no SNMP credentials are included then these have no effect. If they bother you then you can probably just leave them out.

In the Universal Device Poller GUI, you can expand a node in the top left section and see the pollers assigned to it. If you select one of those, you can see what data has been returned. Is there anything there? If you go through the Assign Pollers wizard, you can test out your poller on various nodes and see what comes…

One clarification: you can combine poller results in this way, just like bleearg13 demonstrated, but only from pollers that are assigned to the same network object. You can't combine results for pollers assigned to two different nodes, for example.

The instructions at Troubleshooting · Plexxi/SolarWindsOrionREST Wiki · GitHub say that this error could result from an incorrect IP address. I suspect it could also be caused by a firewall blocking connections from wherever you are running the script to port 17778 on the Orion server. That wiki page also says, "you can…

Here's a SWQL query that will find the port where a given MAC address was most recently seen: SELECT TOP 1 P.NodeID, P.PortID, P.Node.Caption, P.Name, P.EndpointsHistory.LastSeen, P.EndpointsHistory.Endpoint.MACAddress FROM Orion.UDT.Port P WHERE P.EndpointsHistory.Endpoint.MACAddress='0123456789AB' ORDER BY…

See this page for background on how to work with SWIS from PowerShell: PowerShell · solarwinds/OrionSDK Wiki · GitHub In short, you need to run ​Install-Module -Name SwisPowerShell to get that script to work.

The AlertNotes field (not a great name for it) is used for some internal bookkeeping. I recommend you stick with the Notes field and plan on using a regular expression to pull your Ticket Reference ID out of the Notes field later. This will allow for your users to include their own text in the Notes field (through the web…

VoIP Monitor should be ok on the production server. It's not a CPU-heavy module.

You could do it using PowerShell: $x=Invoke-Sqlcmd -Database SolarWindsOrion -Query "SELECT CacheBlob FROM NodeListResourcesCache WHERE NodeID=12" -MaxCharLength 10e6 That sets the MaxCharLength to 10 MB.

The Trap and Syslog services behave the same on hot standby as on regular polling engines. So sure, you could turn them on on your hot standby and include it in the load balancing mix.

Is this issue specific to using AD accounts? In other words, do you have the same problem when using an Orion account? Check the SWIS log for errors at the time of these requests (C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log). Also check the "Application" windows event log on the Orion…

Oops - I was focused on the Set-SwisObject syntax and forgot to pay attention to which Uri you were using. Custom properties are not on Orion.Nodes - they are on a related entity. You need to modify the query a little bit: SELECT Nodes.CustomProperties.Uri FROM Orion.Nodes WHERE IP_Address LIKE '10.98.108.%'

Orion.Events.Acknowledge takes one argument: an array of EventID values to acknowledge. You are passing a single value, not an array of values. So the deserialization fails.

See my reply in the other thread.

Custom pollers are more complex. Could you give me a more detailed description of what you are trying to do? Are you trying to remove nodes? Or just custom poller assignments?

Here's what I think is happening: when you delete the node through the API, the agent record sticks around. When you reinstall the agent, it gets matched up with the existing record. Since there is an existing agent record, complete with NodeID, the agent management system does not create a new node. I don't know the…

Ok, I see. This is the python sample that was included in SDK 1.8. That sample had some problems that user Jay Swan helpfully fixed. The next SDK release will include his fixed version, but until then you can get it from here: swis.py

First, a curl tip - if you are not getting the results you want, add "-v" to the command line. By default, curl won't print anything except the server response body. With "-v" you will get a bunch more info, including the server response code. Next, curl is not the world's most friendly tool for sending complex post data…

In this case you are making a new entry for Orion.NodeSettings, so you should call swis.Create with those arguments, not swis.Update.

If you are working in Perl, you may find it easier to use the REST endpoint (REST · solarwinds/OrionSDK Wiki · GitHub) and so you can receive JSON and avoid dealing with the SOAP/XML stuff. For PowerShell, we provide cmdlets that handle all of the XML stuff for you. The query cmdlet (Get-SwisData) returns a collection of…

Once NPM runs rediscovery on the new node, it will have a bunch more properties.

We haven't tried running Orion on the SWsoft platform. Maybe someone in the community has?

It looks like some API in this area was added in SAM 6.8, released recently! But I am having trouble finding the public documentation that would actually explain how to use it. Let me check with the SAM team.

This does exist (search the forum for "ExecuteSQL"), but I would not recommend it for this purpose. The data collection services keep a bunch of in-memory state. Even if you updated the database directly, this state would be out of sync.

Truncating the Accounts table in the database would leave no account to log in! You could restore the default "admin" and "guest" accounts by running the Configuration Wizard, but that doesn't seem like a great solution. You can use the DeleteAccount verb to remove stale or unwanted accounts. This is the cleanup method I…