Dynamic SmartConnect zones require a greater number of IP addresses than the number of nodes at a minimum to handle failover behavior. In the following example, the formula used to calculate the number of IP addresses required is N*(N-1), where 'N' is the number of nodes. The formula is used for illustration purposes only to demonstrate how IP addresses, and in turn, clients, move from one node to another, and how this could potentially lead to an imbalance across nodes. Every workflow and cluster is unique, and this formula is not applicable to every scenario.
This example considers the same four-node cluster as the previous example, but now following the rule of N*(N-1). In this case, 4*(4-1) = 12, equaling three IPs per node, as shown in the following figure.
![This graphic illustrates the Dynamic Allocation: 4 node cluster with 3 IP addresses per node.](/static/media/9198938f-8c47-5a0e-82d9-6db6a62cd3f7/DAM-63763235-f568-4099-99c2-d75ec9af2242/out/NFS-4-node-cluster-3-IP-per-node=GUID-876E04A8-4AB9-421F-A475-EF0876F7F736=1=en-us=Low.png)
When the same failure event as the previous example occurs, the three IP addresses are spread over all the other nodes in that SmartConnect zone. This failover results in each remaining node having 200 clients and four IP addresses. Although performance may degrade to a certain degree, it may not be as drastic as the failure in the first scenario, and the experience is consistent for all users, as shown in the following figure.
![This graphic illustrates the Dynamic Allocation: 4 node cluster with 3 IP addresses per node, 1 node offline.](/static/media/9198938f-8c47-5a0e-82d9-6db6a62cd3f7/DAM-63763235-f568-4099-99c2-d75ec9af2242/out/NFS-4-node-cluster-3-IP-per-node-1-node-offline=GUID-F494B7CA-03F2-4BE2-BFCC-AC28F6158346=1=en-us=Low.png)