<?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: failover-groups in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455522#M44024</link>
    <description>&lt;P&gt;If your node2 port e0e allows same vlans as node1 port e0e. You may add node2 port e0e to to same failover-group as node1 port e0e.&lt;/P&gt;</description>
    <pubDate>Tue, 01 Oct 2024 01:39:12 GMT</pubDate>
    <dc:creator>Sanaman</dc:creator>
    <dc:date>2024-10-01T01:39:12Z</dc:date>
    <item>
      <title>failover-groups</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455473#M44014</link>
      <description>&lt;P&gt;I have a problem with network interface failover-groups show There is a group that only sets node1 and the port is e0e, but there is node2 in other groups and uses the e0e port, I would like to ask if this is set correctly&lt;/P&gt;</description>
      <pubDate>Sun, 29 Sep 2024 14:09:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455473#M44014</guid>
      <dc:creator>chenguanghui</dc:creator>
      <dc:date>2024-09-29T14:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: failover-groups</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455474#M44015</link>
      <description>&lt;P&gt;If they are in the same layer 2 broadcast domain they should automatically merge together.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;you can try this first&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.netapp.com/us-en/ontap-cli/network-port-reachability-repair.html#description" target="_blank"&gt;https://docs.netapp.com/us-en/ontap-cli/network-port-reachability-repair.html#description&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;pick one of the ports, run the command and check again.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;you can also manually merge them together but that does not guarantee they will work correctly. Check the switch config and verify port configuration there.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;you may want to run&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;system node run -node * options cdpd.enable on&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;system node run -node * options LLDP.enable on&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;wait about three minutes then run:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;net device-discovery show -port e0e&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;m see if that matches what your network guy says&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;(of course if CDP and LLDP) are both disabled on the switches this won’t work.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;good luck. Let us know&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Sep 2024 14:37:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455474#M44015</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2024-09-29T14:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: failover-groups</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455522#M44024</link>
      <description>&lt;P&gt;If your node2 port e0e allows same vlans as node1 port e0e. You may add node2 port e0e to to same failover-group as node1 port e0e.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 01:39:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/failover-groups/m-p/455522#M44024</guid>
      <dc:creator>Sanaman</dc:creator>
      <dc:date>2024-10-01T01:39:12Z</dc:date>
    </item>
  </channel>
</rss>

