<?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 Data and Management on the same subnet in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Data-and-Management-on-the-same-subnet/m-p/452355#M43569</link>
    <description>&lt;P&gt;I remember reading years ago that it was best practice to not have your management ports (ie e0M) on the same subnet as your data LIFs to prevent traffic inadvertently being routed over e0M and impacting performance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After searching this board and the KB database, I can't seem to find that recommendation anymore. Is this no longer an issue with modern versions of ONTAP?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:38:37 GMT</pubDate>
    <dc:creator>Ron_Brinker</dc:creator>
    <dc:date>2025-06-04T09:38:37Z</dc:date>
    <item>
      <title>Data and Management on the same subnet</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Data-and-Management-on-the-same-subnet/m-p/452355#M43569</link>
      <description>&lt;P&gt;I remember reading years ago that it was best practice to not have your management ports (ie e0M) on the same subnet as your data LIFs to prevent traffic inadvertently being routed over e0M and impacting performance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After searching this board and the KB database, I can't seem to find that recommendation anymore. Is this no longer an issue with modern versions of ONTAP?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:38:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Data-and-Management-on-the-same-subnet/m-p/452355#M43569</guid>
      <dc:creator>Ron_Brinker</dc:creator>
      <dc:date>2025-06-04T09:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: Data and Management on the same subnet</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Data-and-Management-on-the-same-subnet/m-p/452356#M43570</link>
      <description>&lt;P&gt;You cannot run data on e0M.&amp;nbsp;&lt;BR /&gt;if you have lifs using the same ip network range, the best thing I’ve found to do is to use good old failover groups instead of broadcast domains&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You still setup the broadcast domains and include everything where it’s supposed to go (mixing e0M and say a0a for instance).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;but instead of using the broadcast domain as a failover group, create an actual failover group that includes only the lifs you need/want. Apply that to the lifs&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;then you don’t get errors/warnings about multi reach broadcast domains. And ONTAP still does what you need it to&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 20:43:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Data-and-Management-on-the-same-subnet/m-p/452356#M43570</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2024-04-26T20:43:22Z</dc:date>
    </item>
  </channel>
</rss>

