ONTAP Discussions

Unable to resolve failover redundancy alert

HUX20002000
1,630 Views

I received this error: "vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 2 LIFs...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."

 

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.

 

Here are the failover settings for the node management LIFs:

 

          Logical     Home       Failover    Failover
Vserver   Interface   Node:Port  Policy      Group
--------  ----------  ---------  ----------  ---------------
Clus      node1_mgmt  node1:e0M  local-only  Management
            Failover Targets: node1:e0M
          node2_mgmt  node2:e0M  local-only  Management
            Failover Targets: node2:e0M

 

The replication LIFs have a similar config:

 

         Logical                 Home           Failover    Failover
Vserver  Interface               Node:Port      Policy      Group
-------  ---------------         -------------  ----------  ---------------
Repl     node1_replication_dcpn  node1:e0e-202  local-only  Repl_VLAN_202
           Failover Targets: node1:e0e-202
         node2_replication_dcpn  node2:e0e-202  local-only  Repl_VLAN_202
           Failover Targets: node2:e0e-202

 

Here are the failover group settings:

 

Vserver  Group          Targets
-------  ----------     --------------------------------------------
Clus     Management     node1:e0M, node2:e0M
Repl     Repl_VLAN_202  node1:e0e-202, node2:e0e-202

 

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.

 

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?

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?

1 ACCEPTED SOLUTION

TMACMD
1,586 Views

The easy fix is to set the failover policy to disabled


net int modify -vserver Clus -lif *mgmt -failover-policy disabled

net int modify -vserver Repl -lif *repl* -failover-policy disabled


the node management don’t have anywhere to failover so it’s fine to set them to disable. 
for the repl lifs if they are in fact on a port channel then disabling the failover on those is ok.  Intercluster lifs can only fail over to the same node.  Since there is a port channel, failover should be built in

View solution in original post

2 REPLIES 2

TMACMD
1,587 Views

The easy fix is to set the failover policy to disabled


net int modify -vserver Clus -lif *mgmt -failover-policy disabled

net int modify -vserver Repl -lif *repl* -failover-policy disabled


the node management don’t have anywhere to failover so it’s fine to set them to disable. 
for the repl lifs if they are in fact on a port channel then disabling the failover on those is ok.  Intercluster lifs can only fail over to the same node.  Since there is a port channel, failover should be built in

chenguanghui
1,558 Views

hello:

  Then the failover policy of LIF can be changed from local only to disabled.

network interface modify -vserver <vserver> -lif <lif_name> -failover-policy disabled

Best regards

Public