NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

General Discussion

WWN Not showing or not being able to connect to VCENTER 6.5 with Snapdrive 7.x

EdwinBrokx
2,467 Views

Hi there,

 

After upgrade to VCenter 6.5 we were not able to see the WWN when trying to connect a LUN. After removing the VCenter credentials from SnapDrive we were not able to connect to the VCenter again. The error we had is: Cannot connect to "vCenter_Name on port 443". The underlying connection was closed.

 

I could not find a solutions on the Netapp site but i did found a solution and wanted to share:

 

https://kb.vmware.com/s/article/2137109

 

You need to make adjustments to the registry. Something changed in TLS on the VCenter and in order for Snapdrive to work with that you need to add a dword value.

 

 

Solution

To enable communication between PowerCLI and vCenter Server systems that use the TLSv1.1 or TLSv1.2 protocols, you must edit the Windows registry.
 
Note: You must use PowerCLI 6.0 R1 or later. Earlier versions of PowerCLI work with versions of the .NET Framework that cannot use the TLSv1.1 and TLSv1.2 protocols by editing the registry.
  • For 32-bit processes, change the following registry key value to 1.

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\[.NET_version]
    Value: SchUseStrongCrypto (DWORD)

  • For 64-bit processes, in addition to the above registry key, change the following registry key value to 1.

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\[.NET_version]
    Value: SchUseStrongCrypto (DWORD)

Regards,

 

Edwin

 

 

1 REPLY 1

AlexDawson
2,430 Views

Thanks for your contribution!

Public