3par Storage Snapshots fail after upgrade to 3Par 3.3.1 MU3

[splatt]

I've just run into this, avoided MU3 as per this post but did critical patches to the 3PAR P51,P52, P60,P76 and P78, this broke snapshots for Veeam version 9.5 update3a.
Had to upgrade to 4a and this worked without another intervention.

[Regnor]

FYI; we had problems after installing 3.3.2 MU3 at one site.
Veeam couldn't connect to the 3PAR any longer (certificate and SSL/TLS error) and WSAPI was also not accessible via Internet Explorer.
The solution was to enable certain SSL/TLS ciphers which were missing on the Veeam Backup Server (Windows Server 2019).

[dcolpitts]

Regnor - by any chance you recall which SSL/TLS ciphers those were?

[Regnor]

Hi Dean, these are the ciphers which I've found in the wsapi devolper guide:

Supported TLS 1.2 security ciphers For a more secure TLS connection, the WSAPI tls_strict policy supports TLS 1.2 with the following set of cyphers. With HTTPS enbaled, WSAPI accepts TLS 1.2 connections with secure ciphers only:
DHE-RSA-AES256-GCM-SHA384
DHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA384
ECDHE-RSA-AES256-SH

[Mehiko]

Hi Regnor

I have same situation.

Where is right place to enable these ciphers in Windows 2019, I have tried in registry, but no luck.

[Regnor]

I always use this tool: https://www.nartac.com/Products/IISCrypto/

[ejenner]

looks handy