At a minimum one customer provided IP address is required for each node. Use of local and/or global load balancers require additional IP addresses. If hosts will retrieve IP addresses from a DHCP server, record DHCP server IP addresses and names. In addition, if traffic separation is used more IP addresses may need to be reserved. Sufficient IP addresses or subnets need to be identified and reserved for deployment. If a separate network team exists, planners should reach out to them early during the planning and design phase. They are instrumental in deciding which deployment model works best for each site and allocating and reserving of IP addresses or subnets.
DHCP is used for assigning IP addresses. Many customers choose to use static IP addresses, often with reservations in DHCP. For large scale out environments however DHCP could be leveraged to avoid hard-coding a large number of addresses.
Putting DHCP in a DMZ is a common requirement for cloud-based storage which may not be part of the traditional model. Begin this conversation early to give ample time for all involved to plan accordingly.
DHCP best practices