Comments
-
IPAM does not currently provide these operations in a public API. The web service calls described in the thread you linked are not documented because they are not intended for use by anything other than the IPAM website.
-
I'd like to help you, but I need more information. What product and version? Where are you seeing this error? A screenshot might help as well.
-
It's the ifType enum from IANA. https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib
-
Here's a sample PowerShell script that shows setting a custom property value on a node and another one on an interface: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/CRUD.SettingCustomProperty.ps1 Orion doesn't have a built-in facility to pull custom property values from a CMDB, so you will need to…
-
My next step would be to take a look at the SWIS log file to see if it has any interesting errors. Run the script to trigger the error, then open C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log and see if it has any clues.
-
That has been the API endpoint since the release on NPM 10.4 in 2013. We have no plans to change it.
-
The current values for custom pollers are in Orion.NPM.CustomPollerStatus. Historical values are in Orion.NPM.CustomPollerStatistics. Are you looking for help writing the query or help writing a program to run a query and consume the output?
-
Run the script again and check the "Application" Windows Event Log on the Orion server. Do you see any related errors there?
-
SWQL doesn't support the CAST and CONVERT functions (except for a special case - SWQL has a ToString(stuff) function that works like CONVERT(nvarchar, stuff)), but I think you can work around this by adding 0, like this: ORDER BY 0+CPS.Status desc
-
There have been two versions of SWIS in Orion for the past couple of years: v2 and v3. You almost certainly want to be using v3 for everything at this point. The HTTPS URL for SWISv2 is this: https://servername:17778/SolarWinds/InformationService/OrionBasic (notice no "v2") The HTTPS URL for SWISv3 is this:…
-
> I have not yet been successful in having the Powershell Script select which interfaces to monitor. What do you mean by this? Are you getting an error? Or is your script just not behaving the way you expect?
-
In the current release, The Orion.Accounts.CreateAccount verb can only be used to create "system" accounts. These are only used for product-product integrations and can't log in to the website interactively, so this won't work for you. I expect this to be better supported in a future release.
-
When that post was written, the SWIS SOAP API (we weren't doing json back then) was the only thing using HTTPS on port 17778. Since then we have added other components that share that HTTPS port, most notably Orion agent communications, though also some traffic related to integration with Virtualization Manager. Better…
-
Can you post what you have working in powershell? I can help you translate that to rest calls.
-
> I want to pass a IP address to StartDiscovery and then point it to an already existing Discovery Profile, do not want to create one The problem is that this is not supported. What you want to do makes sense, but the API does not have a provision for editing an existing discovery profile or running and existing one with a…
-
Here's a PowerShell sample for setting a custom property value on an interface: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/CRUD.SettingCustomProperty.ps1 And a Python sample for setting a custom property value on a node:…
-
That sounds very doable, but let's tighten up the requirements a bit before we dive into writing a query. What all columns do you want in the output? Do you want one row per interface where each row summarizes the last month? Or 30 rows per interface where each row summarizes a day? Do you want all monitored interfaces…
-
You are providing a single Guid, but ExecuteScript is expecting a Guid[] - an array of Guids. Try something like this: $NCMID = 'c51a6a39-25aa-4ce1-8884-ff181f194746' $ids = @( $NCMID ) Invoke-SwisVerb -SwisConnection $SwisConn -EntityName Cirrus.ConfigArchive -Verb ExecuteScript ($ids, $TestScript, "admin")
-
That's strange. What type of views are they? (Summary, Node Details, Interface Details, etc.) All views, default or custom, should get the toolset right-click menu. I would open a support ticket for this. If you do that, please reference this thread.
-
Are you looking for this feature? PerfStack 2.0 - Real-Time Polling
-
Yes, you can talk to VMan from PowerShell. Like this: $vman = connect-swis -Soap12 https://vmanhost/swvm/services/InformationService -UserName guest -Password guest -IgnoreSslErrors
-
The way to add a note to one of these alerts is to use the Orion.AlertStatus.AddNote verb. In PowerShell, that looks like this: Invoke-SwisVerb $swis Orion.AlertStatus AddNote @('eb3cfefa-710f-4a20-818b-4bd27836b285','27','Node','This is my new note text.')
-
You could edit the \inetpub\solarwinds\NetPerfMon\MapView.asp file and remove the "<title><%=NetworkMap.Name%></title>" line. This change will be overwritten whenever you run the configuration wizard, so you'd need to remember to redo it after that.
-
No, we don't have an audit log for API login method. Consider open a feature request for this: Network Performance Monitor Feature Requests
-
The relevant user right is "Allow Account to Clear Events, Acknowledge Alerts and Syslogs". It's weird that you would get nothing in response when you use an account with insufficient rights. Try adding the -v option to curl and see what the response code and headers look like.
-
What pollers are you adding?
-
Yes. You can invoke the verb "Orion.Nodes.PollNow" to do this. It expects one argument, a NetObjectID. For a node, that looks like "N:123" where 123 is the NodeID value.
-
The LIKE operator only supports a single pattern. To match against two patterns, you would need something like this: swis.query('SELECT NodeID, Caption FROM Orion.Nodes WHERE Caption LIKE @capt1 OR Caption LIKE @capt2', capt1='SWITCH%', capt2='ROUTER%') Unfortunately this does not easily scale for an arbitrary number of…
-
Try reinstalling the Microsoft ASP.NET AJAX Extensions 1.0.
-
Which net.tcp endpoint are you using? For the AD account in question, is it a member of an AD group that has been set up in Orion? Do you get the same result for AD accounts that have been authorized as individual accounts in Orion?