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

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...

Looks like you are up for a Support ticket! :| Keep us posted, I'm curious!

Once you had the node monitored thru SNMP, do a Rediscover from the node details page, wait a minute and then click on List Ressources. You should see "Hardware Health Sensors" at the top of the list.

Have you validated that the "System Management Assistant" Service is enabled and started ?

If you have HA in your Orion environment, you need to run the upgrade on your active server. Otherwise, it will simply let you know that your is already up to date but it is not. For the Administration service, have you closed any running SW application on the server (i.e. Service Manager, trap viewer, etc...)? (also check…

Queries with spaces in column names works fine in SWQL Studio, but they break in 2020.2.5 dashboards. Simply removing spaces in columns (ie: like in [RELATED NODE] ) should fix it...

I was told by support that the Hardware Health on Gen10 servers requires and work only via SNMP at the moment. The SolarWinds Agent is basically a WMI proxy. I suggest you vote for the feature request so this is getting traction at the Product Manager level so it's implemented in a future release.

Yeah... the installer does not work properly on HA standby server. Thanks to you, I quickly found my issue :)

I had the same issue. I found somewhere else on Thwack that spaces in colums header like [ALERT TRIGGER TIME] was breaking everything. Try removing the spaces and you should be good to go...

Since it's only available thru SNMP, I've created a feature request so it can be polled using the SolarWinds Agent. Please vote here: https://thwack.solarwinds.com/product-forums/server-application-monitor-sam/i/feature-requests/allow-polling-hpe-dl380-gen10-from-windows-agent

I've created a Feature Request to request to be able to do it using the SNMP agent. Please vote so it gets the PM' attention https://thwack.solarwinds.com/product-forums/server-application-monitor-sam/i/feature-requests/allow-polling-hpe-dl380-gen10-from-windows-agent

Thanks! :)

Link does not work anymore :|

In our case, I want to be able to manage those discovery profile on a per site basis. Now i'm building a new network with over 500 sites... I feel a bit overpaid and undercafeinated to create those 500 profiles manually...

With the legacy syslog viewer there was a config flag to allow messages from unmonitored devices... I just learned from support it's not there anymore with OLV... I now have to revert to legacy trap and syslog viewer and find a solution until they completely removed the apps...

It's sad that the SQL update has to be done every time the Configuration Wizard is ran. We are running a communication network that uses multicast in it's core. It's more than normal behavior to have multicast groups with 0pps when there are no calls being made. We should have the ability to permanently disable this Event.

In fact, for us, just a Growl integration would be nice We are already using that on our admin PC for different scenarios and we love it. Why not put that as a result of an alert rule... Email, send a trap, alert with Growl In that Notify box, I would love to have a link that would bring me to that node or group page While…

I had the same issues, and was not able to communicate with the 2012 server. By creating the LocalAccountTokenFilterPolicy reg key (Description of User Account Control and remote restrictions in Windows Vista), it fixed my issue.

There's also confusion on RabbitMQ place into SW infrastructrure... Should the service be running on APE or only on Primary engine? how to check queuing and health from the APE or AWS point-of-view, etc... A Success center search does not provide that either Search - RabbitMQ