<?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: Network Interface e0a and e0b cannot be reached. in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116172#M24769</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you list the output of the command "&lt;STRONG&gt;ifconfig -a&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2016 08:41:49 GMT</pubDate>
    <dc:creator>hariprak</dc:creator>
    <dc:date>2016-02-23T08:41:49Z</dc:date>
    <item>
      <title>Network Interface e0a and e0b cannot be reached.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116165#M24768</link>
      <description>&lt;P&gt;HI,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I just want to ask what is the reason why e0a and e0b cannot be ping from the network or is there any reason for this issue? The solution I did is to&amp;nbsp;down the port and up it for it to be ping and reach in the LAN.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Is there any reason why this happend?&lt;BR /&gt;&lt;BR /&gt;Thank you!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:59:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116165#M24768</guid>
      <dc:creator>SCOTT_V_RONTALE</dc:creator>
      <dc:date>2025-06-04T21:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Network Interface e0a and e0b cannot be reached.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116172#M24769</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you list the output of the command "&lt;STRONG&gt;ifconfig -a&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 08:41:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116172#M24769</guid>
      <dc:creator>hariprak</dc:creator>
      <dc:date>2016-02-23T08:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: Network Interface e0a and e0b cannot be reached.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116173#M24770</link>
      <description>&lt;P&gt;netapp1&amp;gt; ifconfig -a&lt;BR /&gt;e0a: flags=0x1f4c867&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM&amp;gt; mtu 1500&lt;BR /&gt;inet 192.168.100.91 netmask 0xffffe000 broadcast 192.168.127.255&lt;BR /&gt;partner inet 192.168.100.93 (not in use)&lt;BR /&gt;ether 00:a0:98:3b:fe:78 (auto-1000t-fd-up) flowcontrol full&lt;BR /&gt;e0b: flags=0x1f4c867&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM&amp;gt; mtu 1500&lt;BR /&gt;inet 192.168.100.92 netmask 0xffffe000 broadcast 192.168.127.255&lt;BR /&gt;partner inet 192.168.100.94 (not in use)&lt;BR /&gt;ether 00:a0:98:3b:fe:79 (auto-1000t-fd-up) flowcontrol full&lt;BR /&gt;e0c: flags=0x170c866&amp;lt;BROADCAST,RUNNING,MULTICAST,TCPCKSUM&amp;gt; mtu 1500&lt;BR /&gt;ether 00:a0:98:3b:fe:7a (auto-unknown-down) flowcontrol full&lt;BR /&gt;e0d: flags=0x170c866&amp;lt;BROADCAST,RUNNING,MULTICAST,TCPCKSUM&amp;gt; mtu 1500&lt;BR /&gt;ether 00:a0:98:3b:fe:7b (auto-unknown-down) flowcontrol full&lt;BR /&gt;e0M: flags=0x2b0c866&amp;lt;BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT&amp;gt; mtu 1500&lt;BR /&gt;ether 00:a0:98:3b:fe:7d (auto-100tx-fd-up) flowcontrol full&lt;BR /&gt;e0P: flags=0x2b4c867&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT&amp;gt; mtu 1500&lt;BR /&gt;inet 192.168.3.34 netmask 0xfffffc00 broadcast 192.168.3.255 noddns&lt;BR /&gt;ether 00:a0:98:3b:fe:7c (auto-100tx-fd-up) flowcontrol full&lt;BR /&gt;lo: flags=0x1b48049&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM&amp;gt; mtu 8160&lt;BR /&gt;inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1&lt;BR /&gt;ether 00:00:00:00:00:00 (VIA Provider)&lt;BR /&gt;losk: flags=0x40a400c9&amp;lt;UP,LOOPBACK,RUNNING&amp;gt; mtu 9188&lt;BR /&gt;inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 08:46:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Network-Interface-e0a-and-e0b-cannot-be-reached/m-p/116173#M24770</guid>
      <dc:creator>SCOTT_V_RONTALE</dc:creator>
      <dc:date>2016-02-23T08:46:25Z</dc:date>
    </item>
  </channel>
</rss>

