Jan_Pelousek ✭✭✭✭✭

Hi, discussed with co-workers, this may be potential problem with your schemafiles (maybe not upgraded correctly or something else). Not sure. Issue is quite weird and internally not reproducible. Could you, please check if the attached OrionSchema.xml (default storage c:\Program Files (x86)\SolarWinds\Orion\Information…

The performance effect will be the same as when you will create the dependencies manually. We just added instrumentation for scripting, which doesn't add any kind of increase on performance. The hit will depend on character of the dependencies. I mean e.g. Dependency between two interfaces won't be as heavy as between two…

Yes, this should regenerate that as well. DB maintenance (by default running nightly) executes stored procedures, deleting the orphaned data, but I'm not sure if it covers all the cases for this way of deletion.

The relationships info is stored in SWIS schemas shipped with Orion, which is exposed by the entity Metadata.Relationship. I'm sure query "SELECT Name, BaseType, SourceType, TargetType, SourcePrimaryKeyNames, SourceForeignKeyNames FROM Metadata.Relationship" will provide you all the info you need (relationship names, Type…

Hi Iross, Orion is by default reaching the monitored device via IP address defined during add node or discovery procedure. In case your device's IP is dynamic (assigned by DHCP, etc.), or you need to define the hostname (in your case full FQDN), go to the Node details or Node management and go to edit node section. Then…

Hi nand78, at this time is already released NPM 10.4 which should be available at your Customer portal. There were several changes in CW which might resolve your issue. Are you planning to upgrade? In case it doesn't help, please create ticket on SW support.

Hi Charles, I think I have your ticket. I'm not aware of any change at this field between NPM 10.7 and NPM 11, but here are some facts (valid for some years). - For historical reasons the property Description=MachineType (has the same storage in DB). Because of this you can use only one of them in the Node property bag…

There's quite weird issue with that history. I don't have very deep knowledge of that area, but as far as I know the AlertHistory table should be ~equivalent to the old AlertLog and it's logging should work fine (of course there may occur bad situations, when isn't). To the second question: Backward migration New -> old…

The ContainerMemberSnapshots are being updated so often, how you set the refresh frequency when creating the container (the first screen when adding/editing the group). It's by default set to 1 minute, so basicaly this means, that each minute there's evaluated the group membership ("Dynamic query" conditions + Static…

Which tool button do you reffer to? I'm about this one

Well guys, I could only advise you to raise your hands and create IPAM support tickets with feature requests on the IPAM API supportability. I believe it could be achieved this way if more people show they need it. Things are usually being implemented based on customer needs, but it's good to know about it. Regards, Honza

it should work fine, however if you're affraid of disaster, you can reduce the scope of deletion by using the TOP clause... E.g. Get-SwisData $swis "SELECT TOP 1 uri from Orion.Volumes where caption like '/run%' or caption like '/sys%' order by VolumeID asc" | Remove-SwisObject $swis than always the one volume with lowest…

Or this way. Excellent;-) Have a nice day

Or use Custom query resource (although there are some restrictions, simple queries should work) ar the web report by using custom SWQL query datasource

Looks like we nailed the issue with UDT discovery plugin. I'll now do some testing to confirm the findings and let you know then. However I'm glad you can import now, although it's about workarounds :-(

OK... Here are few minor uncertain things, which are maximally important :-) You wrote you uninstalled your Active server while the HA was disabled - when HA pool is disabled, HA pool is not established or HA is globally disabled, it's the same situation as if you won't have HA at all. Now depends on which server you…

Richard, what you mentioned is implemented on the product side (IPAM/UDT). SDK just provides interface for working with CRUD, Verbs, etc... New SDK versions are mostly about bug fixes, documentation updating and new implementation for product needs (e.g. new types of parameters, connections, ...). As well as the the verbs,…

Hi yangj, the CPU and Memory pollers are Vendor specific. Use the last chapter of the Orion SDK documentation (Orion SDK.pdf) to find out the correct pollers for your devices. Working with charts is the same as for regularly added/discovered nodes.(How to add Nodes and pollers you can find e.g. in the Orion SDK sample…

Hello, this looks like the issue with registration of the SDK libraries. Typically this might happen when you install th Orion SDK under non-administrative account. To register the SWIS PowerShell snapin on 32-bit Windows computers: Run the following command, all on one line.…

This may be caused by various things. Make sure, that: - Hostnames of the target machine and the primary machine are resolvable to IP (e.g. you can ping each other by ping) - Ports 17777 and 17778 are opened between machines in both directions (firewalls, antiviruses and similar blocking stuff) - System time on both…

When installing the APE you just need to contact some of the active servers to get installed product set, so on initial screen just put some IP where the primary is currently reachable. In the configuration wizard just point this server to the orion database (should be already prefilled by installer, so eventually you'll…

It's still there. Just the shortcut has been removed from the Start menu (or metro). It's purpose was to point at the Web based solution. You can still find it in the installation folder (by default c:\Program Files (x86)\SolarWinds\Orion\) as AlertManager.exe and if needed create your own shortcut.

I'm glad you resolved it. Unfortunately # character is one of the unsafe characters, which shouldn't be used in URL at all without encoding. I found some documentation here and here .

That's not true... aggregated data won't cause appearance of the dots... It's matter of the chart sample interval

Hi, you get the uri exactly as I written - by query against SolarWinds Information Service V3 (use some scripting language or SWQL studio, bundled with Orion SDK). You won't find uri in DB in those tables as it's in-memory generated unique identifier (consisting from information like hostname, namespace, name of entity and…

I can imagine, that some properties are still initialized as NULL, however I believe, that when the correct pollers are assigned, that those should be initialized to current value the latest after first rediscovery (by default 30 minutes or can be forced by click on "Rediscover"). Is that still problem after rediscovery?…

You can mark your unmanaged devices by Custom property (when assigning that, just group them by status), then unmanage the rest and when remanaging them you can use that custom property for grouping in the Node Management. Complete "Stop polling" is currently not implemented as from the functionality perspective this means…

Sure... It's quite different way of Orion management, but might be very powerful. Just noting, that you don't need to have the SDK directly on the Orion machine, but this can be random machine, which is able to reach the SolarWinds Information Service v3 through ports 17777 and 17778

I'd say it's because of configuration of the discovery import phase, where aren't by default e.g. selected interfaces that are down and also some volumes (mainly removable). Are you talking about some specific resource type? Regards, Honza

Some time ago I found this mightn't work under PowerShell 2.0. Please try to upgrade the PowerShell to version 3.0+ e.g. from http://www.microsoft.com/en-us/download/details.aspx?id=34595