Snapdrive connection to CDOT SVM: unable to modify or add transport protocol.

[mdvillanueva]

An attempt to the lsit the vservers on the storage system failed.

Storage System Name = <ip address>

Hi Experts,

Any of you seen this error before. I am trying to connect to my SVM.

I have an SVM with a LIF for management, a LIF for ISCSI.

Whenever i try to establish the transport protocol settings to the management IP address, I get the message above.

ONTAP 8.3.1

Thanks,

MV

[venkat3]

Hi MV,

welcome to communities.

Can you please post a screenshot of the exact error (to help you better)

if i understood..while connecting to SVM it is throwing an error - unable to list vservers?

i would check for the below things...

1.pinging the management lif ipaddress should pass.

2.Is the firewall ports enabled? (or firewall stopped)

3.is nslookup for the svm management lif ip pointing to SVM name.

thanks

SR

[mdvillanueva]

I was able to resolve it. I check the interoperability checklist and it turned out my snapdrive version (7.0.2P2) is not compatible with CDOT 8.3.1. After upgrade to SDW 7.1.1 it works. This is actually the first time that the interoperability served me well. Thanks, MV

[venkat3]

Glad to know its resolved.

Thanks for feedback on IMT tool.Nice to know it helped.

-SR

[khalidAnwar · Accepted solution]

Hi All,

I have a similar issue while connecting the snapDrive to iSCSI SVM. getting an error: unable to modifying or add transport protocol.Failed to get Data ONTAP version running on the specific storage system. The version string has an unrecognized format.

ONTAP version -9.1.0

SnapDrive version - 7.1.4

host window : 2012

> ping to SVM management IP works.

> nslookup is also fine.

> No firewall blocking.

> can open putty using SVM mgmt IP.

Regards,

Khalid Anwar

[WillFulmer]

Experiencing the same issue here

ONTAP 9.1

AFF200A

SnapDrive 7.1.4

Host OS - Windows 2012 and Windows 2016

[khalidAnwar]

Did you get that resolved?

[khalidAnwar]

Hi ,

I got this resolved 🙂

Follow below procedure to resolve this.

Make a tweak file to update windows registry  with below lines.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SWsvc\Parameters\DataOntapVersion]

"DNS name of SVM mgmt IP"="NetApp Release 9.1"
"10.140.120.98"="NetApp Release 9.1"

Regards,

Khalid Anwar

+918867969445

[WillFulmer]

Fixed our issue here as well.

With ONTAP 9.x, there is a requirement for a dedicated LIF with Manangement Access and NO data protocols enabled on that LIF.

After adding an additional interface on the SVM, this works properly.

[khalidAnwar]

That is great to hear ! 🙂