Data Backup and Recovery Discussions

SnapCenter 4.0 - No storage connection is set for StorageSystem : <Fully Qualified Domain Name>

Dear all,

 

I'm currently facing an issue while adding Shared Disks to one of our Microsoft Failover Clusters in our testing environment.

 

A few hours earlier, I was able to add LUNs to another Microsoft Failover Cluster that was setup using the exact same procedure. All of a sudden, I now recieve the following error:

 

 

Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com

 

The only change that was made in between both the succesfull and failed tries is the SnapCenter server's Fully Qualified Domain Name.

 

 

Troubleshooting Steps I've taken so far:

 

  • Verified the Storage Virtual Machine is correctly registered in DNS; both forward lookup (A Record) as well as reverse lookup (PTR Record).

 

> svm03-mgmt.example.com
Server:  dc01.example.com
Address:  10.0.0.1

Name:    svm03-mgmt.example.com
Address:  10.0.0.130

> 10.0.0.130
Server:  dc01.example.com
Address:  10.0.0.1

Name:    svm03-mgmt.example.com
Address:  10.0.0.130

 

  • Verified the "Storage Systems" Page in SnapCenter contains the Storage Virtual Machine.

 

  • Verified the credentials on the "Storage Systems" Page in SnapCenter.

 

  • Reviewed the Job Log in SnapCenter.
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Cannot retrieve storage connection setting from SMS server.
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Failed to provision disk
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com at SnapDrive.Nsf.Core.DiskProvisioningHelper.PreProcessandValidateCreateRequest(SDProvisionCreateStorageRequest request, DiskOperationContext context, HostDetails& host) at SnapDrive.Nsf.Core.DiskProvisioningManager.SDProvisionCreateStorage(SDProvisionCreateStorageRequest request, DiskOperationContext context)
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3119889+02:00 Error SDW PID=[1608] TID=[2060] ManagementException : Not supported

 

  • Verified the SnapCenter server is correctly registered in DNS; both forward lookup (A Record) as well as reverse lookup (PTR Record).
> snapcenter.example.com
Server:  dc01.example.com
Address:  10.0.0.1

Name:    snapcenter.example.com
Address:  10.0.0.221

> 10.0.0.221
Server:  dc01.example.com
Address:  10.0.0.1

Name:    snapcenter.example.com
Address:  10.0.0.221

 

Please note I'm currently using SnapCenter Build 4.0.0.809 installed on Windows Server 2012 R2 with all available HotFixes applied.

 

Has anyone had a simmilar issue? Anyone an idea on how further investigate the root cause for this issue?

 

Thank you in advance!

 

Kind regards,

Pieter-Jan Rijmenants

2 REPLIES 2

Re: SnapCenter 4.0 - No storage connection is set for StorageSystem : <Fully Qualified Domain Nam

Hi

 

the log snippet you poested are coming from the exchange server.

did you check if that server has the proper connectivity to the storage?

you can try to "bypass" the DNS and add the hostname (not the FQDN) to the hosts file and check if something changes

 

let us know..

bye

 

Re: SnapCenter 4.0 - No storage connection is set for StorageSystem : <Fully Qualified Domain Nam

Dear @matte,

 

We are talking about a test environment over here. Since I stumbled upon another issue on our Domain Controller I have been focussing on that in the past days. Furthermore, I quit testing the specific SnapCenter case in which I ran into the issue I initially posted.

 

Maybe I'll try to reproduce the issue in the (near) future. Although, I'm not sure of it at the moment.

 

Nevertheless, thank you for your response!

 

Kind regards,

Pieter-Jan Rijmenants

Forums