Hock

There are a number of internal modules that stil require TLS 1.0. It seem though that NPM 12.1 will fully support TLS1.2. Keeping my finger crossed

Is this extended to NPM? Due to PCI requirements, we need to disable TLS 1.0 and 1.1

Not everyone use Active Directory. It will be great if NPM web interface is able to authenticate against an existing RADIUS server.

up for some love.

ok. Just want to be sure NPM 12.1 support disabled TLS 1.0. The last time I log an issue on NPM 12, thwack seem to have a better update than Solarwinds case ticket. Update: Raised Case #1167445 and was informed that, You have to enable the TLS 1.0 on the orion because it is still a requirement. Refer on the link below.…

Connection per sec/min is useful to troubleshoot abnormality in the application as well as for general capacity planning. For example, the usual traffic is x connnections per min/hour/day, if it spike or drop by a lot, you will know that something is going on. On multiple circuits running the same application, it can be…

Great! This mean that 12.1 will support TLS1.2 only option?

After upgrading to 12.1 and disabling TLS1.0, NPM web interface is still not displaying properly. Am I missing something? My datacenter team enforced the TLS1.2 only using IIS Cryto tool.

Finally, NPM 12.2 is able to work without TLS1.0 and 1.1 cobrien​

Yes. Linux support please

How is it possible Solarwinds have tools to support PCI DSS 3.1 but their own software cannot run only on TLS 1.2? Confirmed that NPM 12.1 web interface is not able to work after TLS1.0 and 1.1 is turn off in the server.

Finally, NPM 12.2 is unable to work without TLS1.0 and 1.1

Can someone who have installed 12.2(BETA or GA) confirmed if TLS 1.2 only(with TLS1.0/TLS1.1 disabled) is working?

There is already option available to customize the cpu, memory, node details. Custom Reboot OID should be available in the pollers option.

Up for awareness and TLS1.2 only still does not work for NPM 12.1

Update: According to Solarwinds' developer(Case #1167445), NPM 12.1 does not support TLS 1.2 only. Any idea why?

Here's the list of modules and versions that we are running on Windows 2008 R2 machine.

Hope this get implemented even though it seem quite unlikely given its already 3 year since the request. A main polling address and at least 1 secondary polling IP will be good.

I dont have NCM so dont really know. But there is another thread which mentioned that it is still not supported.

This is very useful for situation where there are mutiple IP on the node for monitor and no loopback address.

Bump to indicate interest still on-going.

Any targeted timeframe for this to be added?

Is this enhancement available?

Makes complete sense, this is an open enhancement request to control polling at a different interval for UnDP's vs. other polling I would like to be able to also control the UnDP polling interval separately. Ideally, we can have different polling time for different OID. :) I check through the settings that it seem that the…

The web loading seem excessive slow with even the login page. Has it got to do with the UDP issue that will be fixed in SP2?

Thanks for the advise. Will do that once I sort all any issue with the existing upgrade.

Is there a way to add this function as a right click selection on NPM Gui?

I have a slightly different issue. I have only manage to upgrade 1 machine to v8.5.1 and the other one is still on v7 but the license for v8 is gone. Now there is only two v9 license in the customer portal(SW66841).

If your SERVER do not support TLS1.2 and the client does, do you think it will work?

thanks, Brandon. I have open a support ticket and attached the lastest mibs. Will workaround the issue by copying the OID directly.