Skip to main content
A newer release of this product is available.

Subnet requirements

Contributors netapp-perveilerk
PDFs

Follow these requirements and guidelines for network subnets.

Note Each network must be connected to its own subnet that does not overlap with any other network on the node.

The following restrictions are enforced by the Grid Manager during deployment. They are provided here to assist in pre-deployment network planning.

  • The subnet mask for any network IP address can't be 255.255.255.254 or 255.255.255.255 (/31 or /32 in CIDR notation).

  • The subnet defined by a network interface IP address and subnet mask (CIDR) can't overlap the subnet of any other interface configured on the same node.

  • Do not use subnets that contain the following IPv4 addresses for the Grid Network, Admin Network, or Client Network of any node:

    • 192.168.130.101

    • 192.168.131.101

    • 192.168.130.102

    • 192.168.131.102

    • 198.51.100.2

    • 198.51.100.4

    For example, do not use the following subnet ranges for the Grid Network, Admin Network, or Client Network of any node:

    • 192.168.130.0/24 because this subnet range contains the IP addresses 192.168.130.101 and 192.168.130.102

    • 192.168.131.0/24 because this subnet range contains the IP addresses 192.168.131.101 and 192.168.131.102

    • 198.51.100.0/24 because this subnet range contains the IP addresses 198.51.100.2 and 198.51.100.4

  • The Grid Network subnet for each node must be included in the GNSL.

  • The Admin Network subnet can't overlap the Grid Network subnet, the Client Network subnet, or any subnet in the GNSL.

  • The subnets in the AESL can't overlap with any subnets in the GNSL.

  • The Client Network subnet can't overlap the Grid Network subnet, the Admin Network subnet, any subnet in the GNSL, or any subnet in the AESL.