Deciding which LIF failover policy to use
Decide whether to use the recommended, default failover policy or whether to change it based on your LIF type and environment.
Failover policy decision tree
- Is this a NAS data LIF?
- Yes: go to step 2.
- No: use the default failover policy for your LIF type.
- Do you have a four-node or larger cluster?
- Yes: go to step 3.
- No: use the default failover policy.
- Are all nodes connected to the same data subnets?
- Yes: go to step 4.
- No: use the broadcast-domain-wide failover policy.
- Consider the following to choose the failover policy:
- Choose the default system-defined failover policy to optimize node and cluster survivability, but risk not being able to fail over to more than one other node.
- Choose the broadcast-domain-wide failover policy to optimize LIF survivability beyond two failed nodes, but risk cascading node failures.
Default failover policies by LIF type
LIF type | Default failover policy | Description |
---|---|---|
BGP LIFs | disabled | LIF doesnot fail over to another port. |
Cluster LIFs | local-only | LIF fails over to ports on the same node only. |
Cluster-mgmt LIF | broadcast-domain-wide | LIF fails over to ports in the same broadcast domain, on any and every node in the cluster. |
Intercluster LIFs | local-only | LIF fails over to ports on the same node only. |
NAS data LIFs | system-defined | LIF fails over to one other node that is not the HA partner. |
Node management LIFs | local-only | LIF fails over to ports on the same node only. |
SAN data LIFs | disabled | LIF does not fail over to another port. |
Note
The sfo-partner-only failover policy is deprecated. Do not use the sfo-partner-only failover policy.
Give documentation feedback