<?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: Odd networking behavior (OnTap 7.3.6) - arp ok, ping not okay in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33987#M3091</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Leading theory at this point is that there is a bad ASIC on the switch.&amp;nbsp; Data is headed outbound from the filer(s) to the switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Apr 2012 19:04:37 GMT</pubDate>
    <dc:creator>JIM_SURLOW</dc:creator>
    <dc:date>2012-04-06T19:04:37Z</dc:date>
    <item>
      <title>Odd networking behavior (OnTap 7.3.6) - arp ok, ping not okay</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33973#M3087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a situation where I have had a functional network for the filer - single vif, multiple vlans.&amp;nbsp; Now, hosts cannot mount off one of the subnet ranges off one of the vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought that this problem was occurring only with some initial testing that I did with ipspace and vfilers.&amp;nbsp; But, now the problem has occurred in our vFiler0 environment and default ipspace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the mounts were active, the filer has the MAC information in the arp table.&amp;nbsp; And since the filer is homed on the vlan with the NFS clients, there isn't any Layer 3 routing going on (I need to find out if for this latest case, if the NFS clients are on the same switch).&amp;nbsp; &lt;/P&gt;&lt;P&gt;I can ping the subnet gateway, but I cannot ping the NFS clients on the subnet (and of course, all of the NFS mount points are hung).&amp;nbsp; &lt;/P&gt;&lt;P&gt;Netstat shows me "syn_rcvd" (and not "established") for those NFS clients.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When this problem occured during my ipspace and vfiler testing, a packet trace showed that pings came in and responses went out (client didn't receive them) and outbound pings from the filer went out with no response.&amp;nbsp; I'm going to guess that I see similar behavior.&amp;nbsp; (In this initial case, I know that the filer is connected to one switch and the NFS clients were connected to a 2nd switch with an interconnect between the two Cisco switches).&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running OnTap 7.3.6 - didn't see any networking bugs similar to this in the 7.3.7RC1 bug fix list.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have any ideas or thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:30:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33973#M3087</guid>
      <dc:creator>JIM_SURLOW</dc:creator>
      <dc:date>2025-06-05T06:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: Odd networking behavior (OnTap 7.3.6) - arp ok, ping not okay</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33978#M3088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And DNS is not a factor here as the connectivity between server &amp;amp; client is all IP number-based, no names.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Apr 2012 04:51:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33978#M3088</guid>
      <dc:creator>JIM_SURLOW</dc:creator>
      <dc:date>2012-04-05T04:51:15Z</dc:date>
    </item>
    <item>
      <title>Re: Odd networking behavior (OnTap 7.3.6) - arp ok, ping not okay</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33983#M3089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Duplicated IP sounds like quite possible cause.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Apr 2012 05:35:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33983#M3089</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2012-04-05T05:35:16Z</dc:date>
    </item>
    <item>
      <title>Re: Odd networking behavior (OnTap 7.3.6) - arp ok, ping not okay</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33987#M3091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Leading theory at this point is that there is a bad ASIC on the switch.&amp;nbsp; Data is headed outbound from the filer(s) to the switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 19:04:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Odd-networking-behavior-OnTap-7-3-6-arp-ok-ping-not-okay/m-p/33987#M3091</guid>
      <dc:creator>JIM_SURLOW</dc:creator>
      <dc:date>2012-04-06T19:04:37Z</dc:date>
    </item>
  </channel>
</rss>

