planglois · Senior Advisor, RF Engineering · ✭✭✭✭✭

Dont be sorry, I love those Livecasts. In fact, the last one using the Orion Alerting Engine as an automation was an eye opening for me. I will probably move some of my group & custom properties cleanup task to the alerting engine instead of trying to maintain those script/cron jobs.

@"KMSigma.SWI", Have you had the chance to try it in your lab? Should I open a ticket on this or the chance of being told "API use is not supported" is too high?

Unfortunately, there is not much flexibility that you can apply there... Orion does not provide granular rules for custom properties. A way around that would be to make the Purchase Date field non-mandatory, and have a custom table on a page showing Non-VM nodes without a date... Another way would be to keep the Purchase…

When you create a node custom property, a field will be available for each node, but it does not means it has to be filled. If by "that only shows on certain nodes" you mean that it will show on your node detail page, only populated field should show.

Here's what I use on my Orion sumary... Simply create a new Custom ressource and use the following custom SWQL Query: -- REF: https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/33940/muted-nodes-resource/113375#113375 SELECT DISTINCT CASE WHEN [EntityUri] LIKE…

Good luck!

Unfortunately, you cannot export anything from MIB DB. At most, you would only be able to check if MIB OID is present in the database. Your best approach is to contact the vendor.. or sometime, look in the admin interface for a download link...

I had to anonymize the output, but it is representing what I got doing $GroupsToCreate | Export-Csv[View:/cfs-file/__key/communityserver-discussions-components-files/45/GroupsToCreate.csv:640:480] Thanks for looking into it, it is much appreciated!

I was unable to pre-stage from the standby MPE. I was getting the following error: doing it from the Active was ok, and I was able to pre-stage and start the install..

When using HA, starting the Centralized Upgrade on an Active server is mandatory or running it on a standby should have suffice?

@"apap" is not alone.. I had the same error message, while trying to install the HF on an MPE: All my modules ( NCM, NPM, NTA, SAM & UDT) are running 2020.2.6, from the same installer (isolated network, it would have been a pain to get a different build for that... I then realized that the MPE I was trying to start the…

Can you explain a bit more about the syslog and trap services issues?

Here's a post I made regarding batch deletion of volumes where I had to leverage the un-manage capabilities to ensure a proper status reset: PowerShell Script to cleanup Volumes inventory - Orion SDK - The Orion Platform - THWACK (solarwinds.com) I believe this should be easily adaptable to remove those linux mounts by…

Not as far as I know. It does not show up in the audit widget, and there's no reference in the [dbo].[DiscoveryProfiles], [dbo].[DiscoveryLogs] table nor in the related log folder (C:\ProgramData\SolarWinds\Discovery Engine). That would make a nice feature request!

To do my tests, I deleted a node and did a discovery only on that given server IP. I added my regex string, and let it do its magic. Once done, I went in the List Resources and only the expected interfaces were checked. I then went back to Scheduled Discovery Results, and it was showing my node, with an overall status of…

Thank you! Reading your comments and taking a step back helped. Since I was doing the discovery on a subnet that was already added in NPM, it confused me. So I ended up understanding the following: The non-highlighted lines are imported. The yellow lines were filtered out, but show as "new". This, to me, should be changed…

Live mode will auto-update your NetPath representation with the latest data as it comes in. When turned-off, new data will be stored but you will not automagically see it.

If we are facing issues with it, should we open a case to add to the list so it get hotfixed, or it wouldnt change anything?

I had a few "Unable to veriffy session" after my upgrade. It transposed in being unable to authenticate against AD using MSAPI... :|

This article details the registry keys were this information is stored. Make sure to follow steps, backup everything (DB and registry) before modifying anything. I would also check that the "InstallType" is "MainPoller" on that server. If it's not, you should open a support case before going any further.

Same here! Anyway, it's all sitting in isolated networks, and it should definitely stay that way

1.3.6.1.4.1.232.9.4.11 shows as "Compaq" although it's a brand new ILO (Integrated Lights-Out 5), although Compaq was bought by HP in 2002 ;)

Done! :) Open for voting: https://thwack.solarwinds.com/resources/thwack-command-center/i/feature-requests/sdk-related-content-exchange-space

Yes indeed! :) For the curious ones, I've posted the script that includes @"tony.johnson"suggested workaround here: thwack.solarwinds.com/.../powershell-script-to-cleanup-volumes-inventory

Thank you so much!!! :) I'll make sure to add the volume unmanage before deletion to the volume cleanup script. I'm glad you digged into this. Putting the word "API" in a support tickets often leads to a one-way discussion. 

I disabled HA and restarted the Orion services on the MPE. The node statuses stayed the same, even after 30 min... :(

KMSigma / aLTeReGo: Do you know who I should ask to see if the behavior I'm seeing is OK, or if it's a bug?

Forgot to mention, i'm running UDT, NCM, NPM, SAM, NTA: 2020.2.5

Same here. My current workaround is to use: $swis = Connect-Swis -trusted -Hostname FQDN_HERE Instead of providing -credential It is not elegant for our needs, but it work...

... As long you are expecting v2 traps. SNMPv3 Traps requires you to monitor the source device using SNMPv3 so it uses the same config (auth, priv, etc...) for processing those traps...