The community is undergoing maintenance and is in Read-Only mode. Click to learn more.

Software Development Kit (SDK) and API Discussions

nfs-stats-top-clients-list-iter-next, client-info output on 8.1P2 7-Mode

robinpeter

Any clue why "client-info" is reporting as "0.0.0.0" ? I believe this happen 8.1 onwards. 8.0.2P3 was reporting correct client IP

i try to use the apitest.pl from NMSDK4.0 NMSDK4.1 and NMSDK5.0, and results are same.

So i assume its the issue related to OnTap.

# ./apitest.pl -h netapp1 system-get-version

OUTPUT:

<results status="passed">

    <version>NetApp Release 8.1P2 7-Mode: Tue Jun 12 17:53:00 PDT 2012</version>

    <is-clustered>false</is-clustered>

</results>

# ./apitest.pl -h netapp1 nfs-stats-top-clients-list-iter-start

OUTPUT:

<results status="passed">

    <tag>159028935485547</tag>

    <records>20</records>

</results>

# ./apitest.pl -h netapp1 nfs-stats-top-clients-list-iter-next maximum 4 tag 159028935485547

OUTPUT:

<results status="passed">

    <records>4</records>

    <nfs-top>

        <nfs-top-info>

            <total-ops>301918</total-ops>

            <client-info>0.0.0.0</client-info>

            <getattr-ops>16939</getattr-ops>

            <lookup-ops>12651</lookup-ops>

            <readlink-ops>3386</readlink-ops>

            <read-ops>252611</read-ops>

            <write-ops>0</write-ops>

            <create-ops>0</create-ops>

            <remove-ops>0</remove-ops>

            <readdir-ops>227</readdir-ops>

        </nfs-top-info>

        <nfs-top-info>

            <total-ops>8622</total-ops>

            <client-info>0.0.0.0</client-info>

            <getattr-ops>5583</getattr-ops>

            <lookup-ops>1040</lookup-ops>

            <readlink-ops>90</readlink-ops>

            <read-ops>84</read-ops>

            <write-ops>0</write-ops>

            <create-ops>16</create-ops>

            <remove-ops>0</remove-ops>

            <readdir-ops>514</readdir-ops>

        </nfs-top-info>

        <nfs-top-info>

            <total-ops>7863</total-ops>

            <client-info>0.0.0.0</client-info>

            <getattr-ops>7189</getattr-ops>

            <lookup-ops>190</lookup-ops>

            <readlink-ops>3</readlink-ops>

            <read-ops>14</read-ops>

            <write-ops>0</write-ops>

            <create-ops>0</create-ops>

            <remove-ops>0</remove-ops>

            <readdir-ops>21</readdir-ops>

        </nfs-top-info>

        <nfs-top-info>

            <total-ops>7032</total-ops>

            <client-info>0.0.0.0</client-info>

            <getattr-ops>6775</getattr-ops>

            <lookup-ops>38</lookup-ops>

            <readlink-ops>14</readlink-ops>

            <read-ops>14</read-ops>

            <write-ops>0</write-ops>

            <create-ops>0</create-ops>

            <remove-ops>0</remove-ops>

            <readdir-ops>70</readdir-ops>

        </nfs-top-info>

    </nfs-top>

</results>

1 REPLY 1

amirm

Hello,

Yes it ONTAP related issue. Its a known bug (#364635). Its fixed in following releases:

    8.1.1RC1     FIXED

And in following 7.3.x releases:

    7.3.2        FIXED

    7.3.2RC1     FIXED

    7.3.3        FIXED

    7.3.3RC1     FIXED

    7.3.4        FIXED

    7.3.4RC1     FIXED

    7.3.5        FIXED

    7.3.5RC1     FIXED

    7.3.5.1      FIXED

    7.3.6        FIXED

    7.3.6RC1     FIXED

    7.3.7        FIXED

    7.3.7RC1     FIXED

Regards,

-Amir

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public