Start a Conversation

Unsolved

D

2 Intern

 • 

157 Posts

1927

October 27th, 2021 13:00

VNX1 discovery broken after update 4.6.0

Does anyone know what the fix would be to (sadly) re-enable tls10 in order for the collector to ssh into older VNX's?>>>ERROR: API initial connection to primary Control Station has failed with the following error: ssl-connect: command returned with a non-zero status (status: 5) ! javax.net.ssl.SSLHandshakeException: The server selected protocol version TLS10 is not accepted by client preferences [TLS12]

not having any nas metrics makes one

thanks

Moderator

 • 

7.6K Posts

October 28th, 2021 09:00

Hello downhill2,

Which vnx1 system do you have?

2 Intern

 • 

157 Posts

October 28th, 2021 11:00

ok well, this is due to tls10 being disabled in 4.6 apparently and no workaround for those of us still using those old arrays? Real nice. Maybe if the SRM developers had thought of a way to simply allow and override (exactly like what we need to do with Java to use Unisphere) that would have been nice, but no. They basically said boo to all of us with older machines. While I get it, sort of, they could have simply released code for those eVNX's, VMAXs, or VNX1's to support TLS1.+. Forced obsolescence yet again.

Probably why people dump SRM and use Grafana or Elastic to report on things. Point taken.

No Events found!

Top