<?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: mutiple routes with same destination and metric in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/mutiple-routes-with-same-destination-and-metric/m-p/132266#M28827</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ONTAP uses&amp;nbsp;source-address based routing in which the subnet matching the source is preferred route.&lt;/P&gt;&lt;PRE&gt;use subnet route of 20.20.20.0/24 to reach 
 destination 20.20.20.1.&lt;/PRE&gt;</description>
    <pubDate>Tue, 27 Jun 2017 08:03:28 GMT</pubDate>
    <dc:creator>Sahana</dc:creator>
    <dc:date>2017-06-27T08:03:28Z</dc:date>
    <item>
      <title>mutiple routes with same destination and metric</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mutiple-routes-with-same-destination-and-metric/m-p/131559#M28662</link>
      <description>&lt;P&gt;ONTAP 9.1RC1 on 6-node cluster&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just notice on my cluster, an SVM has the following routes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ntap01::&amp;gt; network route show&lt;BR /&gt;Vserver&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Destination&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Gateway&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Metric&lt;BR /&gt;------------------- --------------- --------------- ------&lt;BR /&gt;vs1&lt;BR /&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; 0.0.0.0/0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.25.0.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20&lt;BR /&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; 0.0.0.0/0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.87.1&amp;nbsp;&amp;nbsp;&amp;nbsp; 20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SVM has LIFs on these two subnets (one for data and the other for backup traffic). I am wondering the above routes pose any risks espeicially they both have same metric value. Is it smart enough to know that if the LIF is on 172.25.0.0 subnet, use the 1st route for outgoing traffic and&amp;nbsp;if the LIF is on 192.168.87.0 subnet, use the 2nd route?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:00:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mutiple-routes-with-same-destination-and-metric/m-p/131559#M28662</guid>
      <dc:creator>ACHOU_SIMG</dc:creator>
      <dc:date>2025-06-04T15:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: mutiple routes with same destination and metric</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mutiple-routes-with-same-destination-and-metric/m-p/132266#M28827</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ONTAP uses&amp;nbsp;source-address based routing in which the subnet matching the source is preferred route.&lt;/P&gt;&lt;PRE&gt;use subnet route of 20.20.20.0/24 to reach 
 destination 20.20.20.1.&lt;/PRE&gt;</description>
      <pubDate>Tue, 27 Jun 2017 08:03:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mutiple-routes-with-same-destination-and-metric/m-p/132266#M28827</guid>
      <dc:creator>Sahana</dc:creator>
      <dc:date>2017-06-27T08:03:28Z</dc:date>
    </item>
  </channel>
</rss>

