Subscribe
Accepted Solution

nmsdk 5.0 to 5.4 upgrade

Hi,

 

I recently upgraded my setup with nmsdk 5.4 version.

This sdk is talking to a 8.1.1 7mode filer.

 

After upgrade I am seeing that I am no longer able to connect to the 7mode filer over "https" port.

Earlier, before upgrade i.e 5.0 nmsdk version, I was able to connect to the 7mode filer successfully using "https" port.

 

So is there any changes within the sdk that has caused this issue ?

 

Also is 5.4 compatible with 7mode ?

Re: nmsdk 5.0 to 5.4 upgrade

Hi @jayesh_rao

 

As of SDK 5.3.1 (I think) the SDK only supports TLS due to the sslv3/TLS session renegotiation vulnerability.  For cDOT TLS is enabled by default but for 7-mode you have to enable it manually:

 

filer> options tls.enable on

If there is no tls.enable option on your DOT release then you can either (a) upgrade your Data ONTAP to a release that does have TLS support or (b) stay with SDK 5.3 or older which allowed ssl v3 connections.

 

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO

 

 

 

Re: nmsdk 5.0 to 5.4 upgrade

Thanks Madden for the reply.

Also is it safe to assume that 5.4 is more compatible with Cmode ?

Because I see that in C mode TLS is enabled by default.

 

Re: nmsdk 5.0 to 5.4 upgrade

Hi @jayesh_rao,

 

Every SDK release has more features, bug fixes, and tested compatibility with the latest Data ONTAP release.  In the SDK release documentation you should see a mention of new releases supported by it.

 

For example http://mysupport.netapp.com/NOW/download/software/nmsdk/5.3/description.shtml the 5.3 SDK says "Perl API Bindings for Data ONTAP 8.2.2 and 8.3"

while

http://mysupport.netapp.com/NOW/download/software/nmsdk/5.4/description.shtml the 5.4 SDK says "Perl API Bindings for Data ONTAP 8.2.3 and 8.3.1"

 

That is not to say that an old SDK won't work with a new release, but rather that compatibility is not guaranteed and bindings for newly introduced APIs won't be there.

 

Hope that helps!

 

 

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO