Home > Storage > ObjectScale and ECS > Product Documentation > ECS General Best Practices > IP addressing and Dynamic Host Configuration Protocol
A minimum of one customer-provided IP address is required for each node. Use of local or global load balancers requires additional IP addresses. If hosts will retrieve IP addresses from a Dynamic Host Configuration Protocol (DHCP)’ server, record DHCP server IP addresses and names. In addition, if traffic separation is used, additional IP addresses might have to be reserved. A sufficient number of IP addresses or subnets must be identified and reserved for deployment. If a separate network team exists, planners should consult that team early during the planning and design phase. Network teams are instrumental in deciding which deployment model works best for each site and allocating and reserving 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 many addresses.
Putting DHCP in a DMZ, which might not be part of the traditional model, is a common requirement for cloud-based storage. Begin this conversation early to give ample time for all involved to plan accordingly.
DHCP best practices |
Note:
|