cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 11

Srm & Profiler

Jump to solution

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 ?

Labels (1)
0 Kudos
1 Solution
Level 11

Hi,

try following steps:

  1.     Log to STM machine
  2.     Go to STM install folder\conf folder  (usually c:\Program Files\SolarWinds\Storage Manager Server\conf\)
  3.     Open server.xml file for editing
  4.     Locate the “connector” element for port 8443 or the one that is used for SSL connections
  5.     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
  6.     Save the server.xml file
  7.     Restart "SolarWinds Storage Manager Web Services" service
  8.     Open SRM and try to integrate with STM

Regards

Lubo

View solution in original post

0 Kudos
3 Replies
Level 11

Hi,

try following steps:

  1.     Log to STM machine
  2.     Go to STM install folder\conf folder  (usually c:\Program Files\SolarWinds\Storage Manager Server\conf\)
  3.     Open server.xml file for editing
  4.     Locate the “connector” element for port 8443 or the one that is used for SSL connections
  5.     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
  6.     Save the server.xml file
  7.     Restart "SolarWinds Storage Manager Web Services" service
  8.     Open SRM and try to integrate with STM

Regards

Lubo

View solution in original post

0 Kudos

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

0 Kudos

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

0 Kudos