<?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: SnapMirror traffic is being routed through e0M instead in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459651#M14108</link>
    <description>&lt;P&gt;Check the routing&lt;/P&gt;&lt;P&gt;Most probably you are facing with traffic egression&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_traffic_not_sent_or_sent_out_of_an_unexpected_interface_after_upgrade_to_9.2_due_to_elimination_of_IP_Fastpath" target="_blank"&gt;https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_traffic_not_sent_or_sent_out_of_an_unexpected_interface_after_upgrade_to_9.2_due_to_elimination_of_IP_Fastpath&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Mar 2025 11:02:04 GMT</pubDate>
    <dc:creator>Sergey_Osipov</dc:creator>
    <dc:date>2025-03-26T11:02:04Z</dc:date>
    <item>
      <title>SnapMirror traffic is being routed through e0M instead</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459643#M14107</link>
      <description>&lt;P&gt;While monitoring network port traffic, we observed that SnapMirror traffic is being routed through e0M instead of e0f and e3d (InterCluster LIF). Unified Manager indicates that e0M utilization has reached 100%, while e0f shows 0%.&lt;/P&gt;&lt;P&gt;Since e0f and e3d have been configured as the SnapMirror InterCluster LIFs, we expected the traffic to be routed through e0f.&lt;/P&gt;&lt;P&gt;I checked the Broadcast Domain, I found that only the e0f and e3d ports on both nodes are in the independent Broadcast Domain, no e0M in the Broadcast Domain group.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2025 06:58:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459643#M14107</guid>
      <dc:creator>georgewong2424</dc:creator>
      <dc:date>2025-03-26T06:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: SnapMirror traffic is being routed through e0M instead</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459651#M14108</link>
      <description>&lt;P&gt;Check the routing&lt;/P&gt;&lt;P&gt;Most probably you are facing with traffic egression&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_traffic_not_sent_or_sent_out_of_an_unexpected_interface_after_upgrade_to_9.2_due_to_elimination_of_IP_Fastpath" target="_blank"&gt;https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_traffic_not_sent_or_sent_out_of_an_unexpected_interface_after_upgrade_to_9.2_due_to_elimination_of_IP_Fastpath&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2025 11:02:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459651#M14108</guid>
      <dc:creator>Sergey_Osipov</dc:creator>
      <dc:date>2025-03-26T11:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: SnapMirror traffic is being routed through e0M instead</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459679#M14109</link>
      <description>&lt;P&gt;I would suggest to check the service policy of your inter-cluster lif if it is allowed for inter cluster traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 05:06:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapMirror-traffic-is-being-routed-through-e0M-instead/m-p/459679#M14109</guid>
      <dc:creator>Sanaman</dc:creator>
      <dc:date>2025-03-27T05:06:22Z</dc:date>
    </item>
  </channel>
</rss>

