<?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 fas 2040 network configuration issue in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33109#M2260</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i seem to have something wrong or i have missed out a step which i dont know .. we have a set of fas2040 on prod and dr site ... i have configured the network as below .. i can ping the outside world but i cant ping the mainvif from outside .. nor can i access the filer by any means .. the only way is via the rlm .. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hostname&amp;nbsp; XXXXX&lt;/P&gt;&lt;P&gt;vif create multi vif1 -b ip e0a e0b&lt;/P&gt;&lt;P&gt;vif create multi vif2 -b ip e0c e0d&lt;/P&gt;&lt;P&gt;vif create single mainvif vif1 vif2&lt;/P&gt;&lt;P&gt;ifconfig mainvif `hostname`-mainvif mediatype auto netmask 255.255.255.192 partner mainvif&lt;/P&gt;&lt;P&gt;ifconfig mainvif alias 169.41.6.147 netmask 255.255.255.192&lt;/P&gt;&lt;P&gt;route add default 169.41.6.128 1&lt;/P&gt;&lt;P&gt;routed on&lt;/P&gt;&lt;P&gt;options dns.domainname XXXXXX.com&lt;/P&gt;&lt;P&gt;options dns.enable on&lt;/P&gt;&lt;P&gt;options nis.enable off&lt;/P&gt;&lt;P&gt;savecore&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;XXXXX&amp;gt; ping 169.41.6.128&lt;/P&gt;&lt;P&gt;169.41.6.128 is alive&lt;/P&gt;&lt;P&gt;XXXXX&amp;gt; ping 169.52.85.61&lt;/P&gt;&lt;P&gt;169.52.85.61 is alive&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:46:54 GMT</pubDate>
    <dc:creator>VAMSINTAP</dc:creator>
    <dc:date>2025-06-05T06:46:54Z</dc:date>
    <item>
      <title>fas 2040 network configuration issue</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33109#M2260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i seem to have something wrong or i have missed out a step which i dont know .. we have a set of fas2040 on prod and dr site ... i have configured the network as below .. i can ping the outside world but i cant ping the mainvif from outside .. nor can i access the filer by any means .. the only way is via the rlm .. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hostname&amp;nbsp; XXXXX&lt;/P&gt;&lt;P&gt;vif create multi vif1 -b ip e0a e0b&lt;/P&gt;&lt;P&gt;vif create multi vif2 -b ip e0c e0d&lt;/P&gt;&lt;P&gt;vif create single mainvif vif1 vif2&lt;/P&gt;&lt;P&gt;ifconfig mainvif `hostname`-mainvif mediatype auto netmask 255.255.255.192 partner mainvif&lt;/P&gt;&lt;P&gt;ifconfig mainvif alias 169.41.6.147 netmask 255.255.255.192&lt;/P&gt;&lt;P&gt;route add default 169.41.6.128 1&lt;/P&gt;&lt;P&gt;routed on&lt;/P&gt;&lt;P&gt;options dns.domainname XXXXXX.com&lt;/P&gt;&lt;P&gt;options dns.enable on&lt;/P&gt;&lt;P&gt;options nis.enable off&lt;/P&gt;&lt;P&gt;savecore&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;XXXXX&amp;gt; ping 169.41.6.128&lt;/P&gt;&lt;P&gt;169.41.6.128 is alive&lt;/P&gt;&lt;P&gt;XXXXX&amp;gt; ping 169.52.85.61&lt;/P&gt;&lt;P&gt;169.52.85.61 is alive&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:46:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33109#M2260</guid>
      <dc:creator>VAMSINTAP</dc:creator>
      <dc:date>2025-06-05T06:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: fas 2040 network configuration issue</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33113#M2262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The obvious checks – both ports of each multivif are connected to the same switch (or switch stack) and switch ports are properly configured for static link aggregation; all four ports on switches are configured in the same VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addresses look very strange. 169.41.6.128 in a network with a mask 255.255.255.192 means host bits are all zero, which is not possible for a valid address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There could also be routing issues. Please show output of “netstat -rn”.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Sep 2011 18:49:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33113#M2262</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2011-09-04T18:49:30Z</dc:date>
    </item>
    <item>
      <title>fas 2040 network configuration issue</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33121#M2264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ifconfig mainvif `hostname`-mainvif mediatype auto netmask 255.255.255.192 partner mainvif&lt;/P&gt;&lt;P&gt;ifconfig mainvif alias 169.41.6.147 netmask 255.255.255.192&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What IP is in the /etc/hosts file for the hostname?&lt;/P&gt;&lt;P&gt;Why are you specifying an alias?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;man ifconfig:&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; alias&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Establishes an&amp;nbsp; additional&amp;nbsp; network&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; address for this network interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This&amp;nbsp; is&amp;nbsp; sometimes&amp;nbsp;&amp;nbsp; useful&amp;nbsp;&amp;nbsp; when&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; changing&amp;nbsp; network&amp;nbsp; numbers&amp;nbsp; and one&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; wishes to accept packets&amp;nbsp; addressed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to&amp;nbsp; the&amp;nbsp; old network interface.&amp;nbsp; It&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; is required when creating&amp;nbsp; IP&amp;nbsp; vir-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tual host addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; May&amp;nbsp; not&amp;nbsp; be&amp;nbsp; applied&amp;nbsp; to a network&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; interface which is part of a vif."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 07:30:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33121#M2264</guid>
      <dc:creator>rwelshman</dc:creator>
      <dc:date>2011-09-06T07:30:31Z</dc:date>
    </item>
    <item>
      <title>fas 2040 network configuration issue</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33126#M2266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the dflt gateway and subnet mask wasnt given to us correctly ...the df gateway as .129 and smask was 224 ... btw i am a newbie on network .. can you please help me how did you determine that the address was not valid from the sb mask and the gateway &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2011 18:37:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33126#M2266</guid>
      <dc:creator>VAMSINTAP</dc:creator>
      <dc:date>2011-09-14T18:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: fas 2040 network configuration issue</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33131#M2269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Convert netmask and IP address to base 2 representation. Part of IP address that corresponds to 1s in mask is network. Part of IP address that corresponds to 0s in mask is host. Host cannot be all 0 or all 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is highly unusual to have non-contiguous network part in address (if it is officially supported at all), so netmask is often written simply as number of bits in the beginning, like network 192.168.1.0/24 meaning netmask 255.255.255.0 (24 bits of 1s).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Sep 2011 05:22:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/fas-2040-network-configuration-issue/m-p/33131#M2269</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2011-09-15T05:22:06Z</dc:date>
    </item>
  </channel>
</rss>

