tdanner ✭✭✭✭✭

It looks like you are in the UTC-8 (US Pacific) time zone. The LastBoot time shown in your query is exactly 8 hours before the "rebooted at" time in the Message Center event. The "date time" field for the event is when the event was recorded (i.e., when Orion noticed that the reboot had occurred). In this case it looks…

Use the "Orion (v3)" server types in the SWQL Studio connection window.

We are not currently planning any changes to REST API auth. Could you elaborate on what you are looking for?

Normally, "latest version of NPM" would be clear enough, but NPM 10.6 is currently available as a Release Candidate. Could you clarify whether you are seeing this error with 105 or 10.6 RC?

The real problem is with the Connect-Swis line. That command actually only creates a connection object - the connection is not opened until you try to use it. There is some problem with authentication, but you aren't finding out until Set-SwisObject tries to open the connection. Which authentication method did you go with?…

Sure. If you create a subnet like this: swis.invoke('IPAM.SubnetManagement', '10.199.3.0', '24') Then you can find the Uri of the new subnet like this: results = swis.query('SELECT Uri FROM IPAM.Subnet WHERE Address=@addr AND CIDR=@cidr', addr='10.199.3.0', cidr=24) uri = results['results'][0]['Uri']

This plan sounds fine to me, with one limitation: at this time CBQOS polling is not tracked in the Pollers table. Hardware health is. There are several hardware health poller types for different hardware vendors, but they all have names that start with "N.HardwareHealthMonitoring".

Where are you getting the alert url from? That will guide how best to get the ActiveObjectID instead.

I'm sorry - that KB is incorrect. This facility is specific to Alert Central. We are not prepared to support customers using it. I'm working on getting the KB corrected.

AddInterfacesOnNode will take care of adding the pollers for those interfaces. You don't need to do that separately.

Oops - I've been thinking too much about Orion website logins. I didn't realize you meant just general windows login failure. This has nothing to do with IIS then. In that case, I would recommend our Windows Event Forwarder. You should be able to get it from the additional components section on your customer portal. If you…

You also need to add pollers to your new node. See this script for an example: orionsdk-python/add_node.py at master · solarwinds/orionsdk-python · GitHub . ​ Note that the set of pollers you need depends on the type of node (vendor) you are adding.

Without getting into specifics, improved API support for alerting configuration is something we are working on as part of a general round of alerting improvements. See What we're working on post-NPM 10.7 and NPM 12.0 Beta1 Now Available. Modifying the table via SQL is not something we endorse or support.

This is still the case. You can use an API call to start a discovery ​now​, but not to schedule one for later.

How about this? SELECT S.Interface.DisplayName, S.InterfaceID, S.Enabled, S.LastTime, S.CBQoSEnabled, S.CBQoSLastTime, S.AutoDetectedSamplingRate FROM Orion.Netflow.Source S

Let me refer that question to IPAM's product manager, cvachovecj‌.

That's interesting. Do these exceptions take down the application? Or does it just log them and recover? If it is logging them and recovering, I don't think it really makes sense to mark the application as down in SAM. On the other hand, if they do take down the application, then you should be able to use one of the normal…

These HP servers are running the standard Windows SNMP service? We do correctly average out the CPU load for that agent. (As far as I know, we do this properly for all of them, but I know about that one in particular.)

With those versions, I'm afraid your only automatable option would be to load your data into the database directly. The API was just too immature then. I understand that you have constraints that prevent you from upgrading, though.

You can create subnets through the API (https://github.com/solarwinds/OrionSDK/wiki/IPAM-API#crud-operations-for-subnets ) but not supernets or groups.

This difference is due to time zone translation. SWIS attempts to present a consistent UTC format for all datetime values going in or out, even though some columns in the Orion database are stored in local time (generally the system time zone for the polling engine that stored them) and some are stored in UTC. The…

When you call Orion.Discovery.StartDiscovery, the return value is the value of Orion.DiscoveryProfiles.ProfileID. You can query "SELECT ProfileID FROM Orion.DiscoveryProfiles WHERE ProfileID=123" (replacing 123 with the actual ProfileID for the current run) to see if it is still running. Assuming you have set…

Yes, AgentStatus/ConnectionStatus are the way to go. I added them to https://github.com/solarwinds/OrionSDK/wiki/Agents to help the next one who needs them. After some investigation, here's what I learned about TestWithEngine: The purpose of TestWithEngine is to check whether an agent can communicate with a different…

Sorry it has taken me so long to reply to this thread. I'm working on an example script for you. Our existing examples for discovery are kind of all over the place - some perl, some powershell. I need a little more time to finish writing and testing a new one. I'll post it here when it is done.

I just took a closer look at your URL - the problem is the trailing '/'. When I add that, I get the same error you do.

The next place to look for an error would be the IPAM service log at C:\ProgramData\SolarWinds\Logs\IPAM\IPAM.BusinessLayer.log

Since this thread has been revived, let me add a link to the newer API for this function added in NCM 7.4: NCM Config Transfer · solarwinds/OrionSDK Wiki · GitHub

Using curl, it would look like this: curl -k -u admin: -X POST -H "Content-Type: application/json" https://localhost:17778/SolarWinds/InformationService/v3/Json/Invoke/Cirrus.ConfigArchive/Download -d @download.json Where download.json contains something like this: [ ["ef324766-a202-4438-81bf-2c8cbf527743"], "Running",…

The url should be https://SERVERNAME:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.Nodes/PollNow And the POST body should be: ['N:100']

That gave me the clue I needed to figure this one out. Here's the problem. XML element names are case sensitive, and your script has the casing wrong on one of them: IPAddress should be IpAddress. When I changed this line: $build = $build + "<IPAddress><Address>$block</Address></IPAddress>" To this: $build = $build +…