Skip to main content
NetApp Knowledge Base

Connection loss between SnapCenter Plug-in and the SnapCenter Server with routed paths

Views:
1,182
Visibility:
Public
Votes:
1
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Server
  • SnapCenter Plug-in for SQL (SCSQL)
  • SnapCenter Plug-in for Exchange (SCE)
  • SnapCenter Plug-in for Oracle (SCO)

Issue

Randomly, the connection appears to be severed after some time, causing updates back to the SnapCenter Server to be missed, for example from SMCore log:

DEBUG SMCore_<JOB> PID=[<Process>] TID=[<Thread>] RemoteUrl: https://<SNAPCENTER_FQDN>:8146/BackupService.svc/DeleteBackup
ERROR SMCore_<JOB> PID=[<Process>] TID=[<Thread>] WebException Encountered, Response null
ERROR SMCore_<JOB> PID=[<Process>] TID=[<Thread>] Exception in method: Invoke.
System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was
closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException:
An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

The (in this case a backup deletion) request was sent, but the connection was severed after a little over two minutes.
This can be seen from time stamps on the "RemoteURL" line to the next line with the "Exception in method".

Another error that can be seen, for example in the Details View of a still "Running" verification job would be:

The underlying connection was closed: An unexpected error occurred on a receive.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.