<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error in using API reason=&amp;quot;Vserver API missing vserver parameter.&amp;quot; in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Error-in-using-API-reason-quot-Vserver-API-missing-vserver-parameter-quot/m-p/131725#M2377</link>
    <description>&lt;P&gt;In cluster mode the are 2 sets of API, cluster APIs and Vservers API. Most of those CIFS APIs are driven to vserver.&lt;BR /&gt;&lt;BR /&gt;To have a better understanding I recommend you open the Zedi folder under NMSDK. In there you'll find the Zexplorer which is the documentation of APIs. I think after some play around you'll understand a little better. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;By the way you don't have to ask your user for the vserver, but your software will have to find out. I do this kind of operation using both sets. First calling cluster and then get the right vserver. If you'll do it for all vservers, just iterate through it.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2017 18:08:04 GMT</pubDate>
    <dc:creator>FelipeMafra</dc:creator>
    <dc:date>2017-06-14T18:08:04Z</dc:date>
    <item>
      <title>Error in using API reason="Vserver API missing vserver parameter."</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Error-in-using-API-reason-quot-Vserver-API-missing-vserver-parameter-quot/m-p/131722#M2376</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i am using ONTAP.9.0 SDK API to develop puppet library to integrate with ONTAP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am calling api like this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;?xml version='1.0' encoding='utf-8'?&amp;gt;&lt;BR /&gt;&amp;lt;!DOCTYPE netapp SYSTEM 'file:/etc/netapp_filer.dtd'&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;netapp version='1.15' xmlns='&lt;A href="http://www.netapp.com/filer/admin" target="_blank"&gt;http://www.netapp.com/filer/admin&lt;/A&gt;' nmsdk_version='5.6' nmsdk_platform='CentOS Linux release 7.0.1406 x86_64' nmsdk_language='Ruby' nmsdk_app='puppet_netapp_cmode'&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;cifs-domain-password-schedule-modify&amp;gt;&amp;lt;schedule-randomized-minute&amp;gt;100&amp;lt;/schedule-randomized-minute&amp;gt;&amp;lt;/cifs-domain-password-schedule-modify&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Response body from ONTAP&amp;nbsp;&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&amp;lt;?xml version='1.0' encoding='UTF-8' ?&amp;gt;&lt;BR /&gt;&amp;lt;!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'&amp;gt;&lt;BR /&gt;&amp;lt;netapp version='1.100' xmlns='&lt;A href="http://www.netapp.com/filer/admin" target="_blank"&gt;http://www.netapp.com/filer/admin&lt;/A&gt;'&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;results reason="Vserver API missing vserver parameter." status="failed" errno="13006"/&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;In result i am getting this errror in puppet program&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error: /Stage[main]/Main/Node[hnidhi-vsim1]/Netapp_vserver_cifs_domain_password_schedule[data_server]: Could not evaluate:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Executing api call cifs-domain-password-schedule-modify schedule-randomized-minute 100 failed: "Vserver API missing vserver parameter."&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;If we refer api for&amp;nbsp;&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;cifs-domain-password-schedule-modify&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;A href="#the_top" target="_blank"&gt;[top]&lt;/A&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;Modify the attributes of cifs-domain-password-schedule object.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Input&amp;nbsp;Name&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Range&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Type&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;is-schedule-enabled&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;boolean&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;optional&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Value of this field indicates whether domain account password change schedule is enabled or not. Value of true indicates schedule is enabled.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;schedule-day-of-week&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;A href="#cron-day-of-week" target="_blank"&gt;cron-day-of-week&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;optional&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;This field specifies the day of week when the scheduled domain account password change occurs&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;schedule-randomized-minute&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;[1..180]&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;integer&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;optional&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;This field specifies the minutes within which the scheduled domain account password start time can be randomized beginning schedule-time-of-day&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;schedule-time-of-day&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;A href="#time-of-day" target="_blank"&gt;time-of-day&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;optional&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;This field specifies the time in HH:MM:SS at which the scheduled domain account password change starts&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;schedule-weekly-interval&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;[1..52]&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;integer&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;optional&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;This field specifies the number of weeks after which the scheduled domain account password change must occur&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;Errno&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;E_CIFS_OPERATION_NOT_SUPPORTED_IN_WORKGROUP_MODE&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;My aim is - &amp;nbsp;&lt;/U&gt;&lt;/STRONG&gt;I want to change value of schedule_randomized_minutes in this command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;My query is&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1) API IS not asking for vserver name in its input Then why this error is coming?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2)If vserver has to be given in input , how do we give it ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;&lt;U&gt;Any kind of help in understanding this error response from server will be really helpful.!!!!!!&amp;nbsp;&lt;/U&gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:59:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Error-in-using-API-reason-quot-Vserver-API-missing-vserver-parameter-quot/m-p/131722#M2376</guid>
      <dc:creator>nidhimittal</dc:creator>
      <dc:date>2025-06-04T14:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: Error in using API reason="Vserver API missing vserver parameter."</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Error-in-using-API-reason-quot-Vserver-API-missing-vserver-parameter-quot/m-p/131725#M2377</link>
      <description>&lt;P&gt;In cluster mode the are 2 sets of API, cluster APIs and Vservers API. Most of those CIFS APIs are driven to vserver.&lt;BR /&gt;&lt;BR /&gt;To have a better understanding I recommend you open the Zedi folder under NMSDK. In there you'll find the Zexplorer which is the documentation of APIs. I think after some play around you'll understand a little better. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;By the way you don't have to ask your user for the vserver, but your software will have to find out. I do this kind of operation using both sets. First calling cluster and then get the right vserver. If you'll do it for all vservers, just iterate through it.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2017 18:08:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Error-in-using-API-reason-quot-Vserver-API-missing-vserver-parameter-quot/m-p/131725#M2377</guid>
      <dc:creator>FelipeMafra</dc:creator>
      <dc:date>2017-06-14T18:08:04Z</dc:date>
    </item>
  </channel>
</rss>

