topic Re: Apiproxy and Vserver Tunneling? in Active IQ Unified Manager Discussions

Apiproxy and Vserver Tunneling?

mshearer — Thu, 05 Jun 2025 06:01:10 GMT

I am trying to run vserver api commands using the oncommand apiproxy api and when I do I get a credential issue, however I do not see a way within OnCommand to specify credentials for a Vserver or am I missing something?

Input

<?xml version="1.0" encoding="UTF-8"?>

<api-proxy>

<name>volume-get-language</name>

</request>

<target>clnas</target>

</api-proxy>

</netapp>

Output

<?xml version='1.0' encoding='UTF-8' ?>

<status>failed</status>

<reason>Skipped attempt due to lack of good credentials</reason>

</response>

</results>

</netapp>

Re: Apiproxy and Vserver Tunneling?

ELADSCONTINUITY — Tue, 30 Jul 2013 11:51:35 GMT

The dfm does not include the netApp username or password.

After you set the user/password in the configuration netapp host you will get the results.

BTW:

That the reasone you don't need to set the user and password of the proxy host inside the request.

Re: Apiproxy and Vserver Tunneling?

adaikkap — Tue, 30 Jul 2013 12:53:14 GMT

OnCommand Unified Manager does not talk to the vServer. It always talks to the cluster and get the details and information about each vServer.

This same as how we did for vFiler, we communicate only with physical filer and got all information related to vfiler.

Regards

adai

Re: Apiproxy and Vserver Tunneling?

ELADSCONTINUITY — Mon, 05 Aug 2013 13:44:33 GMT

Can you please show an example which return the vFiler information?

For example I used to invoke the command:

"nfs-exportfs-list-rules"

When trying to use the command with the API-PROXY there is version mismach.

<api-proxy>

<target>netapp7-2</target>

<name>nfs-exportfs-list-rules</name>

</request>

</api-proxy>

"java.lang.IllegalArgumentException: ONTAPI version must be at least 1.7 to send API to a vfiler"

Re: Apiproxy and Vserver Tunneling?

ELADSCONTINUITY — Sun, 25 Aug 2013 09:00:38 GMT

I found a work arround.. I used the system-cli command instead.

The following command allowed us to get the nfs shared list:

<api-proxy>

<target>hostname</target>

<name>system-cli</name>

<args>

<arg>vfiler</arg>

<arg>exportfs</arg>

</args>

</request>

</api-proxy>