tdanner ✭✭✭✭✭

Hi Bill, I'm looking into this.

Try this: ["afa454bb-9ca6-4194-9bf1-c34940eeda58", "119221", "Routing Neighbors", "Beavis was here! (and added this note)"]

My script works through the Orion API, not the database. The entities in the API do not always correspond directly to database tables.

Ok, that's a known issue with SAM 6.2 and NPM 11.5. It's fixed in SAM 6.2.1/NPM 11.5.2.

The product creates a self-signed certificate at install time. All browsers and most other tools will warn about it.

The function of "AddNodeToNCM" is to take a node that is already in Orion (in the Nodes table) and enable it for config/NCM monitoring. From the way you describe your setup, it sounds like you have three Orion databases - two with just NPM and one with just NCM. Is that accurate?

Since this was written, we do have a better API for adding interfaces to monitor. See the SDK documentation for Orion.NPM.Interfaces.DiscoverInterfacesOnNode. This still doesn't cover everything that can be done from the List Resources UI, but it does cover network interfaces.

I get no error message just that it can't fine the server that it is installed on... Everything else works fine. AFter reading this thread. I decided to re-install, same result. Could you give more details about this? Where are you seeing this message and what is the exact text?

I was able to reproduce this problem on some machines but not others. I'm still investigating, but I found a possible workaround for you: installing .NET 4.5 on the Orion server seems to make it work. I hope to find a fix that does not require .NET 4.5, but in the mean time you could try that unless you are using Window…

Unfortunately we don't have an API equivalent for the "List Resources" screen.

Use Computer Management to see if any of the SolarWinds services are Disabled.

See this answer in an older thread: Re: Volumes not being polled

I just realized that my test earlier wasn't really valid. The 30-second timeout you are seeing is happening at the SQL Server level, but in my test I induced a delay in SWIS so I didn't hit the SQL timeout. I don't see any way to override this timeout from SWQL Studio. If you switch your testing over to PowerShell, you can…

What product and version are you using? What kind of configuration file are you trying to download? What method are you using to perform this download? How is it failing?

Still no.

Basically, we don't support it. Here's a more concrete reason: in ASP.NET, pages and controls are compiled at load time and they reference everything in the bin and App_Code directories (and some other stuff). When we update the products, we add to or change the contents of these directories. Before we release, we test all…

C:\ProgramData\Solarwinds\Logs\SwqlStudio.log should tell us why it is crashing. Could you attach it to a message in this thread? Also, what version of NPM are you using?

This is a bug. To avoid putting the actual community string on the web, we replace it with a randomly generated GUID. The Toolset tools will prompt you for the actual community string the first time, then remember the association between the GUID and the string you type in so they don't need to prompt you again (for that…

This script will test whether each line in the file exists as a node in orion. It will print all the ones it does not find. $names = get-content .\nodes.txt $swis = Connect-Swis -UserName admin $names |? { (Get-SwisData $swis "SELECT 1 AS ok FROM Orion.Nodes WHERE Caption=@name" @{name=$_}) -ne 1 }

You can get a list of types that support Create with this query: SELECT FullName FROM Metadata.Entity WHERE CanCreate=true

Are you looking at C:\ProgramData on the Orion server? That's where Orion.InformationService.log will be.

It appears that pattern-type account/view limitations containing operators such as OR, AND, etc. are broken in 8.5. This has been entered into our bug system and will be fixed for 8.5.1.

A single version of the SDK can connect to NPM 10.1 and 11.5.1, but you would need a script that knows the mapping between the poller names used by those two versions. Have you considered just cloning the 10.1 database and upgrading it? That might be easier than script-based data migration.

Ok, in that case you will probably find it under CustomProperties. Like this: SELECT N.NodeID FROM Orion.Nodes N WHERE N.CustomProperties.prod_state = 'production' I recommend you use the SWQL Studio application to work out your query, then update the program.

I was able to reproduce the behavior you are seeing by changing how I supply the credentials to the powershell script. If I give it a username in the form of "domain\user" then it works correctly. But if I use the "user@domain" syntax, then I get the same error you do: it authenticates correctly, but seems to think I am…

NPM 12 is currently at the Release Candidate 3 stage. Release is imminent.

Nodes.CPULoad is a nullable field in the database, and it looks like the code in the popup is not correctly handling the case where that field is null. Orion normally uses "-2" as a value to indicate that CPULoad data when not available. I recommend you add setting CPULoad=-2 to your script for adding ICMP-only nodes.…

No problem. I like the easy ones. :)

CORE-7540 is not marked as fixed in 12.1. I'm not aware of any issues in doing more than one discovery at once.

I believe what you are suggesting is to set IsAutoImport to True? Oops! Yes, that's what I meant. for some reason DiscoveredInterfaces isn't available in SWIS It is, but it is in a different namespace: Orion.NPM.DiscoveredInterfaces.