<?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: Obtaining per-interface network information from Data ONTAP 7.3.1 in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15492#M19124</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only way to accomplish this with older filers via ZAPI is to use the unsupported system-cli call. In Java, this would look something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;NaElement api = new NaElement("system-cli");&lt;/P&gt;&lt;P&gt;NaElement argsElement = new NaElement("args");&lt;/P&gt;&lt;P&gt;api.addChildElem(argsElement);&lt;/P&gt;&lt;P&gt;argsElement.addNewChild("arg", "ifconfig");&lt;/P&gt;&lt;P&gt;argsElement.addNewChild("arg", "-a");&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NaElement output = server.invokeElem(api);&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then write some code to parse out the results via regex. This approach is not with out it's drawbacks. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-ryan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Jan 2012 21:53:23 GMT</pubDate>
    <dc:creator>ryanc</dc:creator>
    <dc:date>2012-01-06T21:53:23Z</dc:date>
    <item>
      <title>Obtaining per-interface network information from Data ONTAP 7.3.1</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15487#M19123</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have an application that's based on NetApp Manageability SDK 4.0 that I've been using to extract information from filers running Data ONTAP 7.3.3.&lt;/P&gt;
&lt;P&gt;I recently needed to extract the same information from older filers, running Data ONTAP 7.3.1. Pointing my application at the older filers, all of the SDK&lt;/P&gt;
&lt;P&gt;calls seem to work, except one, that being &lt;STRONG&gt;net-ifconfig-get&lt;/STRONG&gt;. I'm using this method to get ip-addresses and aliases for each network interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My question is this: is there another method or mechanism I can use to obtain this ip-address information, that is compatible with Data ONTAP 7.3.1 filers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:38:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15487#M19123</guid>
      <dc:creator>rich_oliveri</dc:creator>
      <dc:date>2025-06-05T06:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: Obtaining per-interface network information from Data ONTAP 7.3.1</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15492#M19124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only way to accomplish this with older filers via ZAPI is to use the unsupported system-cli call. In Java, this would look something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;NaElement api = new NaElement("system-cli");&lt;/P&gt;&lt;P&gt;NaElement argsElement = new NaElement("args");&lt;/P&gt;&lt;P&gt;api.addChildElem(argsElement);&lt;/P&gt;&lt;P&gt;argsElement.addNewChild("arg", "ifconfig");&lt;/P&gt;&lt;P&gt;argsElement.addNewChild("arg", "-a");&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NaElement output = server.invokeElem(api);&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then write some code to parse out the results via regex. This approach is not with out it's drawbacks. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-ryan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 21:53:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15492#M19124</guid>
      <dc:creator>ryanc</dc:creator>
      <dc:date>2012-01-06T21:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: Obtaining per-interface network information from Data ONTAP 7.3.1</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15500#M19125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ryan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply. I think I've found another way to accomplish this as well. I used the ONTAP snmp-get and snmp-get-next methods to extract the information from the filer's MIB.&lt;/P&gt;&lt;P&gt;It helps if you have a MIB browser, to determine the needed OIDs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This works on older filers, and it also seems to work even when SNMP isn't enabled (I guess because going through the ONTAP API).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jan 2012 18:08:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Obtaining-per-interface-network-information-from-Data-ONTAP-7-3-1/m-p/15500#M19125</guid>
      <dc:creator>rich_oliveri</dc:creator>
      <dc:date>2012-01-12T18:08:10Z</dc:date>
    </item>
  </channel>
</rss>

