tdanner ✭✭✭✭✭

Error: True- if transfer end with error False if transfer end successfully NULL - if transfer still in progress Status: "Complete" – when transfer complete "Waiting" - when request is waiting for execution "Rejected due to previous operation in progress" - when transfer request is rejected and will not be executed…

Not too far off. The two arguments to AdministrativeShutdown are the NodeID (as an int) and a list of PortIDs (as an int array). So you can call it like this: $nodeID=137 $portIDs=@(1169) Invoke-SwisVerb $swis Orion.UDT.Port AdministrativeShutdown @( $nodeID, [int[]] $portIDs )

What does the Connect-Swis line in the script look like?

IPAM data is available through our standard API, which has both SOAP and REST variants. You should be able to figure out "next available unused IP" with a query or two through this API. However, we do not have an API for reserving/assigning a hostname to an IP address at this time; this will prevent you from automating…

You can get New-WebServiceProxy to ignore SSL errors by following the instructions in this post: http://www.poshpete.com/powershell/new-webserviceproxy-and-ssl. But you are better off with the Connect-Swis cmdlet we provide. I'm guessing you turned to New-WebServiceProxy to work around the issue you described in Orion SDK…

Yes, you can use specify your own date times. That data type is just .NET's ugly way to say "an optional datetime". There's a bit more information about alert suppression here: https://github.com/solarwinds/OrionSDK/wiki/Alerts#orionalertsuppression

You can change the IP address Orion uses to monitor a node by updating the "IP" property. In PowerShell, that looks like this: $swis = Connect-Swis # your connection details here $uri = 'swis://server/Orion/Orion.Nodes/NodeID=1' # Get the node's Uri from somewhere, maybe a query $newip = '10.1.2.3' # get the new monitoring…

With only NPM, your options are limited. If you can somehow query the service status over SNMP, you could use the “universal device poker” feature to monitor the status and build a dashboard around that. But really SAM is a better tool for this job. </sales>

Have you tried using the Discovery API to add the nodes? Discovery · solarwinds/OrionSDK Wiki · GitHub

You can just link directly to the images. Like this: CONCAT('/NetPerfMon/images/Event-',EventTypes.EventType,'.gif') as [_IconFor_Icon]

Could you explain what you want to do in more detail?

The SPLITSTRINGTOARRAY is only intended as an internal implementation detail of the AncestorDisplayNames and AncestorDetailsUrls properties and only works in the query structures used to implement those properties. It should not have been included in the documentation. I removed it recently. I recommend you find another…

Those web services should be considered internal to the Orion website. There's no documentation for them since they are not intended for customer use.

The REST API request/response formats for Orion are described here: REST · solarwinds/OrionSDK Wiki · GitHub

You just need two values: "ifIndex" and "Manageable":true. Without "Manageable":true, it will import the interface but not set up polling.

You are very close. You don't need to make a list out of the member definition object. This line should work: swis.invoke('Orion.Container', "AddDefinition", int(rid), {'Name': siteName, 'Definition': uri} )

Could you post the code you are using to add the node?

You need parenthesis around the second SELECT statement. Like this: select TimeStamp, NodeID, InterfaceIDRx, Port, SourceIP, DestinationIP, IngressBytes, protocolIDfrom Orion.Netflow.Flowswhere InterfaceIDRx = 917 and TimeStamp >= '2014.12.17 19:10:00' and TimeStamp < '2014.12.17 19:11:00'UNION ALL (select TimeStamp,…

The post body needs to be a json array containing the arguments for the verb. AddNodeToNCM takes one integer argument. Try this line: CURLOPT_POSTFIELDS => "[11985]",

We have a sample for doing this from PowerShell: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/DeployAgentViaVerb.ps1 We don't have a Python version of that sample, but here's a Python sample for calling a different verb:…

If you modify the original link to include "&Password=" at the end (that is, supply a blank password in the URL), does it work?

I can help with this, but I need some more information. Please post: 1. The version of NPM you are using. 2. Your perl script (with credentials or any other sensitive information removed, of course) 3. The screenshot referenced in the message above.

This has been fixed in NPM 12.4. ifAdminStatus and ifOperStatus are now reported correctly for DiscoverInterfacesOnNode.

This issue is tracked as NPM-6293. Unfortunately all you can really do is just add all the interfaces, wait for their first polling cycle, and then delete the ones with down status.

We can look at that. Are you looking for transactional behavior (all these operations succeed or none of them happen at all) or stop-on-first-error or just run them all one by one and return a list of results?

If you want to add a custom property interactively, just use the GUI (/Orion/Admin/CPE/Default.aspx). If you want to write a script to add custom properties programmatically, see this documentation: Creating Custom Properties · solarwinds/OrionSDK Wiki · GitHub .

Interesting. Please open a support ticket and include the diagnostics collected form the additional web server and we'll get you up and running. 

When you make an update call like that, there is no body in the response. The HTTP "200 OK" status is all you need. So I suspect output.json is empty, which is why your json parser is rejecting it.

I think the properties you are looking for are AlertMessage and TriggerTimeStamp. You can use SWQL Studio (which is installed with the Orion SDK) to try out queries and see if you are getting the results you need.

Here's an updated version of this script that works with NPM 10.6: Add-PSSnapin SwisSnapin $nodeProps = @{NodeID=6} $VolumeIndex = 31 $VolumeDescription = '/' $VolumeCaption = '/' $swis = Connect-Swis -Certificate $newVolProps = @{ NodeID=$nodeProps["NodeID"]; # NodeID on which the interface is working on…