Skip to main content
NetApp Knowledge Base

SnapCenter fails to run SnapVault update due to timeout on status request to CVO

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

Applies to

  • SnapCenter Server
  • SnapCenter Plug-in for Windows (SCW)
  • Cloud Volumes ONTAP (CVO)

Issue

The SnapVault update is never run with the following errors seen:
Unable to find SnapMirror destination(s). Error: No SnapMirror relationships were found. Resolution: Please make sure that secondary storage systems are registered and host can resolve them correctly.
 
Looking deeper into the log, the SAL_<JOB_ID>.log (SAL = Storage Abstraction Layer) shows the following:
Invoking Connect-NcController ...
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Connection to SVM_IP_ADDR on port 443 for protocol HTTPS timed out.
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at SnapDrive.Nsf.Core.Storage.StorageConnection.InitializeONTAP(SDStorageSystemId storageSystemId)
 
Also evident from the logs, due to the time indications on the lines, is that the error comes after either the default 60 seconds, or what is set on the SVM timeout setting in Storage Connections.

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device