Home > Storage > PowerScale (Isilon) > Product Documentation > Cloud > APEX File Storage for AWS: Deployment Guide > IP range of cluster external network interfaces
During cluster deployment, you create a default cluster network pool named groupnet0.subnet0.pool0. Each node in the cluster is assigned one IP address from this pool. The IP addresses used in the pool groupnet0.subnet0.pool0 are the AWS primary IPv4 addresses, and cannot be moved from one node to another. Thus, the allocation type of this pool cannot be changed to dynamic.
You must have six contiguous IPs for the default network pool, to ensure that the cluster has enough IPs to expand to a maximum of six nodes.
The Externally Managed IPs feature in OneFS 9.7 introduces a limited form of DHCP for managing IP allocation in groupnet0.subnet0.pool0 and ensures that an IP in the OneFS network pool is assigned to the correct network interface of a node as the primary IP. To ensure the integrity of this process and mitigate potential security risks of a rogue DHCP server, it is recommended to add an inbound rule in the cluster external security group in AWS. See Table 5 for the details of the rule:
Setting | Value |
Rule name | For example, DHCP |
Type | Ingress |
From port | 67 |
To port | 68 |
Protocol | udp |
Allowed CIDR blocks | <cluster-gateway>/32 |
After a cluster is deployed, users are allowed to create additional network pools. These new pools can use static or dynamic allocation. Any unused IPs from the cluster external subnet CIDR range can be used to create pools. The IPs from additional network pools are assigned to cluster nodes as AWS secondary IPv4 addresses.
Note: APEX File Storage for AWS does not support IPv6.