Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Srm & Profiler

Having a problem with the profiler disconnects and need to to know how to set up some monitoring and alerting when this happens?

Currently I noticed on the product licensing page the SRM license Lists an ERROR on unable to get license information.

Please help ?

Find more posts tagged with

Accepted answers

LubomirKrausko

Hi,

try following steps:

Log to STM machine
Go to STM install folder\conf folder (usually c:\Program Files\SolarWinds\Storage Manager Server\conf\)
Open server.xml file for editing
Locate the “connector” element for port 8443 or the one that is used for SSL connections
Remove below constants starting with TLS_DHE_ from “ciphers” attribute, usually there are two such constants: TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA
Save the server.xml file
Restart "SolarWinds Storage Manager Web Services" service
Open SRM and try to integrate with STM

Regards

Lubo

All comments

LubomirKrausko

Hi,

try following steps:

Log to STM machine
Go to STM install folder\conf folder (usually c:\Program Files\SolarWinds\Storage Manager Server\conf\)
Open server.xml file for editing
Locate the “connector” element for port 8443 or the one that is used for SSL connections
Remove below constants starting with TLS_DHE_ from “ciphers” attribute, usually there are two such constants: TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA
Save the server.xml file
Restart "SolarWinds Storage Manager Web Services" service
Open SRM and try to integrate with STM

Regards

Lubo

bharris1

LubomirKrausko What is the reason for removing these constraints? What caused STM to lose connection?

LubomirKrausko

Hi bharris,

I have not investigated this deeply, but what I have seen is the DHE (Diffie–Hellman key exchange - Wikipedia, the free encyclopedia) stops working for weak keys (maybe got deprecated - just a guess). The constraints above, that should be removed, allow tomcat server (used in STM) to use the DH key exchange with the weak keys. Thus the initial handshake of SSL connection between SRM and STM server could not be performed and connection could not be established.

Regards

Lubo