tdanner ✭✭✭✭✭

The bug number is 348041 if you want to check on status in the future.

I think I see what the problem is. Orion needs the VolumeDescription property to exactly match the value in the hrStorageDescr OID (1.3.6.1.2.1.25.2.3.1.3). The reason for this is that the index for volumes can change over time and Orion uses this hrStorageDescr value to keep the volume connected with its history even when…

What product versions are you using?

Unclear question. I meant the NPM version, not the SDK version.

Do you get any output from the curl command alone without the | awk ... part?

Quick question: what browser versions are you guys using?

I tested the functionality of adding &AccountID=account&Password=password to the URL. It still works in 8.5, but unfortunately it's more complicated than it was in 8.1. In 8.1, if you included the AccountID and Password in the query string, you just got the page or image with no fuss. In 8.5, as you observed, you get…

You should probably open a support ticket for this. The next step in troubleshooting this issue would be to collect the diagnostics from both machines. It's easier to track that through the ticket system.

You don't have to install 8.5.1 on the new server and upgrade it to 9.0. You could just shut down the 8.5.1 server, install 9.0 on the new server, and tell the configuration wizard to use the old database. This will upgrade the database to the 9.0 schema. (After doing this, you can't use 8.5.1 with that database anymore,…

I opened CORE-11690 to track this. You could also create a feature request on thwack for voting.

Yes, it's the order they are tried. If you don't care, just increment the order for each one (you'll get an error if you have duplicate values for order). But with that many credentials your discovery will complete faster if you can put the most commonly used ones first.

Thanks for asking, but I have no progress to report here. This feature did not make it into NPM 11.5.

Have you tried using the PowerShell snapin instead of Invoke-RestMethod? PowerShell · solarwinds/OrionSDK Wiki · GitHub

Same story as before.

'Counter' is for when the device is reporting something like "number of X since last boot" or similar. With a 'Counter'-type poller, UnDP will sample the value and record the rate of change. 'Rate' is for when the device is reporting a number that UnDP should record directly, without doing the rate of change computation.

Oh, and the issue with limitations being ignored when computing summarized status color will be fixed in the next major release.

I posted a fix in your other thread: http://thwack.solarwinds.com/thread/58606

I just checked and found that this verb is only supported in v3. Sorry for the confusion - I thought that verb was one of the ones supported in both v2 and v3.

Yes, basic alerts will still be processed normally. The Alerting Engine service only handles Advanced Alerts.

Are you emailing a single Top 10 resource or the whole Top 10 View? We don't have a way to get a printable version of a whole view, but if you just want to send a single resource, you could use the "detached" version. Just click on the title of the resource and it will pop out into its own browser window. Copy the URL from…

Close. The last parameter for Invoke-SwisVerb is a list of the argument values to send to the verb. You provided a single int, which PowerShell has helpfully wrapped into a list of one int. Since the verb expects an array of ints, an error is thrown when a single int is provided. This should work: $alertid =…

Are you using a Windows/AD account or an Orion database account? You could also look in the information service log for more error details: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log

What's happening is that SWIS is (correctly) authenticating "user" as "domain\user" and granting access accordingly. However, it is passing the user context to other permission checkers (IPAM has a custom permission checking plugin to apply its own hierarchical permissions model) as the client (SWQL Studio in your…

It looks like you are missing NodeDescription. Add something like this to $nodeProps and the Node Details resource should be happy: NodeDescription="my description";

Those tables are where Orion stores incoming SNMP Traps. You can use the Trap Viewer application on the Orion server to configure how long those traps are retained and set up the rules that govern which traps get stored in the database and which ones are simply discarded. Since you have already hit the 4GB limit, changing…

The Orion Module Engine service is, among other things, a helper for the website. The website communicates with the Module Engine on port 17777. You don't want IIS listening on 17777 - that would interfere with the Module Engine claiming that port. At this point, I think you would probably be best served by opening a…

Here's one thing you can do. In \Inetpub\Solarwinds\Orion\styles\MainLayout.css, line 76 is this: background-color: transparent; (that's in the #pageHeader section) If you change the "transparent" to #474747, the white bar will instead be a color that matches the bottom of the gradient in the header. If you just want to…

Ok, the use case is clear now. Unfortunately I don't know of any better way to accomplish this than duplicating the alerts. With the discontinuation of Alert Central, SolarWinds does not have another solution for you.

Unfortunately swis.update is not going to work for NCM.NodeProperties for the same reason that swis.read doesn't. NCM has another API you can use to set the device template and various other properties, a verb called Cirrus.Nodes.UpdateNode. It takes one object, an NCM Node. In JSON it looks like this: { "NodeID":…

Yes, the quoting rules are different on linux. Assuming you are using bash, it would look like this: curl -k -u admin:xxxxx -H "Content-Type: application/json" -d [\"N:1\"] https://orionserver:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.Nodes/Remanage