<?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: Unable to resolve failover redundancy alert in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460228#M44904</link>
    <description>&lt;P&gt;hello：&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Then the failover policy of LIF can be changed from local only to disabled.&lt;/P&gt;&lt;P&gt;network interface modify -vserver &amp;lt;vserver&amp;gt; -lif &amp;lt;lif_name&amp;gt; -failover-policy disabled&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Tue, 22 Apr 2025 09:20:21 GMT</pubDate>
    <dc:creator>chenguanghui</dc:creator>
    <dc:date>2025-04-22T09:20:21Z</dc:date>
    <item>
      <title>Unable to resolve failover redundancy alert</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460215#M44902</link>
      <description>&lt;P&gt;I received this error: "&lt;SPAN&gt;vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 2 LIFs...&lt;/SPAN&gt;This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The error applies to the node management LIFs on the two nodes (node1_mgmt, node2_mgmt) and also the two custom replication LIFs I created (node1_replication, node2_replication). The replication LIFs are talking to a NetApp in a different datacenter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are the failover settings for the node management LIFs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Logical&amp;nbsp; &amp;nbsp; &amp;nbsp;Home&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Failover&amp;nbsp; &amp;nbsp; Failover&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Vserver&amp;nbsp; &amp;nbsp;Interface&amp;nbsp; &amp;nbsp;Node:Port&amp;nbsp; Policy&amp;nbsp; &amp;nbsp; &amp;nbsp; Group&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;--------&amp;nbsp; ----------&amp;nbsp; ---------&amp;nbsp; ----------&amp;nbsp; ---------------&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Clus&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;node1_mgmt&amp;nbsp; node1:e0M&amp;nbsp; local-only&amp;nbsp; Management&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Failover Targets: node1:e0M&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; node2_mgmt&amp;nbsp; node2:e0M&amp;nbsp; local-only&amp;nbsp; Management&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Failover Targets: node2:e0M&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The replication LIFs have a similar config:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Logical&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Home&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Failover&amp;nbsp; &amp;nbsp; Failover&lt;BR /&gt;Vserver&amp;nbsp; Interface&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Node:Port&amp;nbsp; &amp;nbsp; &amp;nbsp; Policy&amp;nbsp; &amp;nbsp; &amp;nbsp; Group&lt;BR /&gt;-------&amp;nbsp; ---------------&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;-------------&amp;nbsp; ----------&amp;nbsp; ---------------&lt;BR /&gt;Repl&amp;nbsp; &amp;nbsp; &amp;nbsp;node1_replication_dcpn&amp;nbsp; node1:e0e-202&amp;nbsp; local-only&amp;nbsp; Repl_VLAN_202&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Failover Targets: node1:e0e-202&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;node2_replication_dcpn&amp;nbsp; node2:e0e-202&amp;nbsp; local-only&amp;nbsp; Repl_VLAN_202&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Failover Targets: node2:e0e-202&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are the failover group settings:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Vserver&amp;nbsp; Group&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Targets&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;-------&amp;nbsp; ----------&amp;nbsp; &amp;nbsp; &amp;nbsp;--------------------------------------------&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Clus&amp;nbsp; &amp;nbsp; &amp;nbsp;Management&amp;nbsp; &amp;nbsp; &amp;nbsp;node1:e0M, node2:e0M&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Repl&amp;nbsp; &amp;nbsp; &amp;nbsp;Repl_VLAN_202&amp;nbsp; node1:e0e-202, node2:e0e-202&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as I can tell, the error is occurring because "Failover Targets" shows only one target for each LIF — the LIF's home port.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something I've missed here? Something I need to do to tell it that it can failover those LIFs to the corresponding ports on the other node?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Or, looking at it a different way: is it even possible for management and replication (i.e. intecluster) LIFs to failover? If not, then is there something I need to change so that this alert condition will ignore these LIFs?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Apr 2025 18:49:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460215#M44902</guid>
      <dc:creator>HUX20002000</dc:creator>
      <dc:date>2025-04-21T18:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to resolve failover redundancy alert</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460226#M44903</link>
      <description>&lt;P&gt;The easy fix is to set the failover policy to disabled&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;net int modify -vserver Clus -lif *mgmt -failover-policy disabled&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;net int modify -vserver Repl -lif *repl* -failover-policy disabled&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;the node management don’t have anywhere to failover so it’s fine to set them to disable.&amp;nbsp;&lt;BR /&gt;for the repl lifs if they are in fact on a port channel then disabling the failover on those is ok. &amp;nbsp;Intercluster lifs can only fail over to the same node. &amp;nbsp;Since there is a port channel, failover should be built in&lt;/P&gt;</description>
      <pubDate>Mon, 21 Apr 2025 23:36:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460226#M44903</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2025-04-21T23:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to resolve failover redundancy alert</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460228#M44904</link>
      <description>&lt;P&gt;hello：&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Then the failover policy of LIF can be changed from local only to disabled.&lt;/P&gt;&lt;P&gt;network interface modify -vserver &amp;lt;vserver&amp;gt; -lif &amp;lt;lif_name&amp;gt; -failover-policy disabled&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2025 09:20:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Unable-to-resolve-failover-redundancy-alert/m-p/460228#M44904</guid>
      <dc:creator>chenguanghui</dc:creator>
      <dc:date>2025-04-22T09:20:21Z</dc:date>
    </item>
  </channel>
</rss>

