tdanner ✭✭✭✭✭

This is a product bug - see How to get inteface status before adding it? . The fix is in the current NPM beta.

It could just be using the Node Details view instead of the ESX Details view. Check under Admin > Account Views and see if your account's node details view is set for "By Device Type".

I recommend using the JSON/REST API for SWIS. There are a number of REST clients available for PHP. If you are familiar with one, try using that. If not, "Guzzle" came up as the first hit on Google and appears to be a wrapper for cURL, which is quite powerful and works fine with the SWIS REST API. Let us know how it goes!

Previous values are not available in SWQL queries, as they only make sense for a change event. Alerting based on change events is available for many entity types in Orion, but not custom pollers.

Right - the alert engine is not "poller aware", so it will process alerts for nodes assigned to any poller. You only need one.

In SWQL Studio you can generate a SELECT query for all attributes of an entity by just double-clicking on the entity. Does that fetch the data you are looking for?

The API has added a JSON option. The XML option has not been removed and still works the same way it has in the past. New entities and verbs are supported in both formats. I have been steering new users to the JSON endpoint as it is generally easier to work with, but the XML version is still present and we have no plans to…

1 and 2 are both great ideas. I can't promise anything, but I'll argue for including both of these in the next version. Unfortunately, there's no way to just hack these features into the shipping code. Your workaround is clever, but I can see how your users wouldn't be thrilled. One thing that might help a little is that…

You can query Orion.StatusInfo to get the list of all possible values of the numeric status and the display name of each one. Note that not all of these status apply to nodes - some are specific to interfaces, applications, or other objects. Let me know if you have questions about the semantics of any of them.

I'm not sure you how want to sort and group the data, but this SWQL query should get you started: SELECT FlapId, NodeId, RouteDestinationGUID, RouteDestination, CIDR, DateTime, Ip_Address_Type, Ip_Version, RouteNextHop, Description, VrfIndex FROM Orion.Routing.RoutingTableFlap

I'm afraid I need more context to help you out here. I hadn't seen EnumerableRowCollection before, so I googled it. MSDN says "This API supports the .NET Framework infrastructure and is not intended to be used directly from your code," so you may want to reconsider that part. Can you show the GetInterfaces and Tabulate…

Your curl command looks right to me: curl -k -u user: -X POST -H "Content-Type: application/json" -d @"unmanage.txt" "https://x:17778/Solarwinds/InformationService/v3/json/Invoke/Orion.SEUM.Transactions/Unmanage" ["T:2","04-26-2017 12:00:00 PM","04-27-2017 02:00:00 PM","false"] And it did not return an error. Are you…

Try "RWPrivacyMethod".

SWQL is safe against SQL injection. This was designed in and has been carefully tested to verify. However, using query parameters in your SWQL queries is also a good idea. For one thing, it helps with reusing SWQL query plans which is good for response time and SWIS memory usage. To use a parameterized query in PowerShell,…

InterfaceID is Orion's ID for each monitored network interface. If you are using ICMP for monitoring nodes, then you are not monitoring any interfaces on those nodes. If I understand correctly what you are trying to do, you can just remove that line from your script.

What version of NCM?

AddInterfacesOnNode is really intended to be called using the (possibly filtered) output of DiscoverInterfacesOnNode. But if you get the XML right, it should work fine when you build the "DiscoveredInterfaces" XML from scratch. If you have a working script using AddInterfacesOnNode, I recommend you dump the XML from that…

Could you show us the query you have so far and tell us what issues you are running into?

What is the context? Where are you using this query/macro?

Inside the <item> element, add a <value> element whose text content is the new value to set.

Depends on a few things. I've seen some devices (Cisco 3700?) with that report the speed of auto-negotiate ports with nothing connected as 10 MB. Then when you connect a 100 MB or 1 GB device to the port, the router starts reporting the port speed as 100 MB or 1 GB. So that could be what you're seeing.

The node name and description are in different entities, so you need to use joins. Like this: SELECT N.DisplayName, N.Description, E.LastDiscovery, E.FirstDiscovery, E.Missing, E.Type, E.ContainedIn, E.EntityClass, E.Position, E.HardwareRevision, E.FirmwareRevision, E.SoftwareRevision, E.Serial, E.Manufacturer, E.Model,…

If this report is otherwise doing what you want and you just need it to display only the WAN interfaces, just add this clause right before the ORDER BY at the end: WHERE Interfaces.interface_type2='WAN'

In general, there's no way to combine a set of rows into a single row. Also, I think you may be misreading the "CASE ... END" syntax. In SWQL it works the same way as in SQL.

You need one more argument: a boolean that specifies whether the second time argument should be treated as an absolute datetime or an offset relative to the start datetime. I would just always pass False for that. Also, you should use the ISO format for dates. Try this: swis.invoke("Orion.NPM.Interfaces", "Unmanage",…

That is strange. What is in $newNodeProps when this happens?

Starting in 9.0, Orion can tell the difference between garden-variety net-snmp linux boxes and VMware ESX boxes. They get different values for Vendor and Machine Type now, assuming the SNMP on ESX is set up right.

Could there have been any changes to the permissions of the account used to connect? Does that same account see data normally in the IPAM web interface?

Can you build the report you want using the normal Orion reporting interface?

The verb does accept multiple children. I just tested it again (using NPM 12.3, though I don't think this has changed recently) to be sure. If you are sure it is not adding the subsequent members, you could check the SWIS log for any relevant errors.…