Subscribe

Unable to set vserver default route via ontapi and latest SDK on CDOT 8.3.1

[ Edited ]

I am scripting vserver creation via ontapi and the latest SDK 5.4P1 and some 8.3 specific things are still not supported  :

 

<results status="failed" errno="13005" reason="Unable to find API: net-routes-create"></results>

 

net-routes-create made it in Zedi in Ontapi version 1.31 but Ontap 8.3.1 has no support for it

 

It's a bit strange that API and CLI are not on par.... any insight ?     How do I find which CDOT ontap verions matches ontapi versions ?

 

thanks for any info

 

Re: Unable to set vserver default route via ontapi and latest SDK on CDOT 8.3.1

Hello!

 

NMSDK compatibility with ONTAPI versions is documented in the IMT.  For NMSDK 5.4 here is the list:

 

NetApp ONTAPI 1.30
NetApp ONTAPI 1.21
NetApp ONTAPI 1.20
NetApp ONTAPI 1.19
NetApp ONTAPI 1.17
NetApp ONTAPI 1.15
NetApp ONTAPI 1.14
NetApp ONTAPI 1.13
NetApp ONTAPI 1.12
NetApp ONTAPI 1.11
NetApp ONTAPI 1.9
NetApp ONTAPI 1.8
NetApp ONTAPI 1.7
NetApp ONTAPI 1.6
NetApp ONTAPI 1.5
NetApp ONTAPI 1.4
NetApp ONTAPI 1.3
NetApp ONTAPI 1.2
NetApp ONTAPI 1.1
NetApp ONTAPI 1.0

It also lists ONTAP versions, which 8.3.1 is listed as supported...ONTAPI 1.30 was released with 8.3.0 and 1.31 was released with 8.3.1, so it's not 100% clear which is accurate.

 

That being said, NMSDK is primarily an enabler for accessing ONTAPI/ZAPI, so it *should* still work.  For the API you're specifying, are you executing against the Vserver/SVM, or against the cluster?  "net-routes-create" should be directed at the SVM.

 

Hope that helps.

 

Andrew

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

Re: Unable to set vserver default route via ontapi and latest SDK on CDOT 8.3.1

Ah ! You were right about net-routes-create.... I was at the cluster API.  It does work at the vserver level.

 

So that works but there is still other 8.3 stuff I can't set now.   I.e.  Creating the NFS policy for that vserver,  most attributes are supported but the newer ones like showmount and udp:

 

cmd4 = NaElement("nfs-service-create")
cmd4.child_add_string("is-nfs-access-enabled","true")
cmd4.child_add_string("is-nfsv2-enabled","false")
cmd4.child_add_string("is-nfsv3-enabled","true")
cmd4.child_add_string("is-nfsv40-enabled","false")
#cmd4.child_add_string("is-udp-enabled","false")
#cmd4.child_add_string("is-showmount-enabled","true")
cmd4.child_add_string("is-nfsv41-enabled","false")
xo4 = call_api(d,cmd4)

 

These 2 attributes would result in API error for extra arg. 

 

Re: Unable to set vserver default route via ontapi and latest SDK on CDOT 8.3.1

Looking at ZAPI itself, I don't see anything UDP related in 1.30, 1.31, or 1.32.  Can you tell me where you're seeing that as being an option?

 

The showmount option is simply "showmount"...

 

cmd4 = NaElement("nfs-service-create")

# enable NFS
cmd4.child_add_string("is-nfs-access-enabled","true")

# but only NFS v3
cmd4.child_add_string("is-nfsv2-enabled","false")
cmd4.child_add_string("is-nfsv3-enabled","true")
cmd4.child_add_string("is-nfsv40-enabled","false")
cmd4.child_add_string("is-nfsv41-enabled","false")

# enable showmount
cmd4.child_add_string("showmount","true")

# make it so
xo4 = call_api(d,cmd4)

Andrew

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