Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

SnapCenter LUN creation fails when TLS 1.0 and 1.1 are disabled

Views:
103
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Server

Issue

Attempting to create or connect a LUN from the SnapCenter UI or PowerShell generates an error stating that no storage connection is set for the storage system.

In the SCW Debug log a similar entry is generated:
 
2019-10-23T15:33:49.3182483-06:00 Verbose SDW PID=[XXXX] TID=[XXXX] The client and server cannot communicate, because they do not possess a common algorithm
2019-10-23T15:33:49.3182483-06:00 Verbose SDW PID=[XXXX] TID=[XXXX]    at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
   at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
   at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
   at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
   at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
2019-10-23T15:33:49.3182483-06:00 Error SDW PID=[8968] TID=[10684] The underlying connection was closed: An unexpected error occurred on a receive.   at SnapDrive.Nsf.Common.Infrastructure.RestClient.Invoke[TReq,TRes](TReq request, String methodType, String remoteUrl, Boolean dataContractSerializer)
   at SnapDrive.Service.SDServiceManagerHelper.InitializeRBACCache()"

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support