ONTAP Discussions

LIF failover policy

Gbar333
Hi everybody,
I was wondering if system-defined failover policy won't migrate lifs to a HA partner even if there are only two nodes in a cluster which are in a HA pair.
I came to an understanding that this policy only migrates to local ports or ports on non-HA partner nodes. This is a default policy and sounds problematic in a one HA pair cluster...
Thanks in advance!
2 REPLIES 2

Gbar333
First of all thank you for replying!
Your comment doesn't state explicitly whether system defined policy would allow migrating lifs to ha partner in a one HA pair cluster. The valid ports for migration are a combination of the failover group and the restriction enforced by the policy. It is still not 100% clear to me if it would allow the migration stated above. I came to an understanding that this policy surely won't allow migration to a ha partner in a multinode cluster. It would help me greatly if anyone can find out if the above mentioned migration is possible.
Thanks in advance!

Sahana

Hi,

 

Please refer KB https://kb.netapp.com/app/answers/answer_view/a_id/1005606/loc/en_US (requires login)

The following command displays information about the failover targets for all LIFs in a two-node cluster. The Failover Targets row shows the (prioritized) list of node-port combinations for a given LIF.

cluster-1::> network interface show -failover
         Logical       Home                  Failover        Failover
Vserver  Interface     Node:Port             Policy          Group
-------- ------------- --------------------- --------------- ---------
Cluster
         node1_clus1   node1:e0a             local-only      Cluster
                       Failover Targets: node1:e0a,
                                         node1:e0b
         node1_clus2   node1:e0b             local-only      Cluster
                       Failover Targets: node1:e0b,
                                         node1:e0a
         node2_clus1   node2:e0a             local-only      Cluster
                       Failover Targets: node2:e0a,
                                         node2:e0b
         node2_clus2   node2:e0b             local-only      Cluster
                       Failover Targets: node2:e0b,
                                         node2:e0a
cluster1
         cluster_mgmt  node1:e0c             broadcast-domain-wide
                                                             Default
                       Failover Targets: node1:e0c,
                                         node1:e0d,
                                         node2:e0c,
                                         node2:e0d
         node1_mgmt1   node1:e0c             local-only      Default
                       Failover Targets: node1:e0c,
                                         node1:e0d
         node2_mgmt1   node2:e0c             local-only      Default
                       Failover Targets: node2:e0c,
                                         node2:e0d
vs1
         data1         node1:e0e             system-defined  bcast1
                       Failover Targets: node1:e0e,
                                         node1:e0f,
                                         node2:e0e,
                                         node2:e0f

Reference http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-nmg%2FGUID-964FE956-1687-4255-A5AE-71BB990F5BCF.html

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public