The document discusses an error when attempting to perform a SQL backup clone using SnapCenter 4.3 on a NetApp cDOT storage system using iSCSI. The error references SMB even though iSCSI was being used, because the SnapCenter storage connections were using the cluster management LIF instead of the data SVM management LIF, which is required for SAN protocols like iSCSI. The solution is to add the data SVM directly in SnapCenter using the SVM management LIF.

1. Can't Split Clone for SQL Backup on
NetApp SnapCenter 4.3
Environment: SnapCenter 4.3
Protocol: iSCSI
Storage NetApp cDOT
Error: Failed to get the SMB server for storage system: svm
Observation: It's wired to see the error reporting 'SMB' when the data communication protocol is
set to SAN (iSCSI).
Cause: NetApp storage connections in the SnapCenter were made using the Cluster Management
LIF.
Solution: Add the Data SVM directly in the SnapCenter using SVM Management LIF for SAN
Protocols.
Note: For SAN Protocols (iSCSI/FC) a dedicated SVM management LIF is required because data
protocols and management protocols cannot share the same LIF. SnapCenter must talk back to
Storage via SVM Management LIF for Management related ZAPI calls.
In case your SVM environment does not have SVM Management LIF already, you can create one
using the following command:
cluster::> network interface create -vserver <vserver-name> -lif SVM_mgmt_LIF_name -role data -
data-protocol none -address x.x.x.x -netmask x.x.x.x -home-node node_a_or_b -home-port e0M -
status-admin up
ashwinwriter@gmail.com
Jan, 2020