Network installation and provisioning

You must understand how the three networks are used during node deployment and grid configuration.

When you first deploy a node, you must attach the node to the Grid Network and ensure it has access to the primary Admin Node. If the Grid Network is isolated, you can configure the Admin Network on the primary Admin Node for configuration and installation access from outside the Grid Network. If the Grid Network has a gateway configured, it is the default gateway for the node during deployment. This allows grid nodes on separate subnets to communicate with the primary Admin Node before the grid has been configured.

Once the nodes have been deployed, the nodes register themselves with the primary Admin Node using the Grid Network. You can then use the Grid Manager, the configure-storagegrid.py Python script, or the Installation API to configure the grid and approve the registered nodes. During grid configuration, you can configure multiple grid subnets. Static routes to these subnets through the Grid Network gateway will be created on each node when you complete grid configuration. If necessary, subnets containing NTP servers or requiring access to the Grid Manager or API can also be configured as grid subnets.

During the node approval process, you can configure nodes to use the Admin Network, the Client Network, or both as desired. If a node is configured to use the Client Network, the default gateway for that node switches from the Grid Network to the Client Network when you complete the grid configuration steps.

Note: When using the Client Network, keep in mind that a node’s default gateway will switch from the Grid Network to the Client Network when you complete the grid configuration steps. For all nodes, you must ensure that the node does not lose access to external NTP servers when the gateway switches. For Admin Nodes, you must also ensure that browsers or API clients do not lose access to the Grid Manager. To maintain access, perform one of the following steps:
If you are creating... Behavior Recommended configuration
Grid Network only All Grid, Admin, and Client traffic flows over the Grid Network. The Grid Network gateway is the node default gateway.  
Grid Network and Admin Network Grid and Client traffic flows over the Grid Network. Administrative traffic flows over the Admin Network. The Grid Network gateway is the node default gateway.  
Grid Network and Client Network (no Admin Network) When a node is deployed, the Grid Network gateway is the node default gateway. Subnets providing access to the Grid Manager and NTP servers should be included as Grid Network subnets during configuration. When you complete the grid configuration steps, the Client Network gateway becomes the node default gateway. Allow NTP and installer client access through both the Grid and Client Network gateways.

or

Add the NTP or installer Client subnets, or both, as Grid Networks.

All three networks (Grid, Admin, and Client) When a node is deployed, the Grid Network gateway is the node default gateway. Subnets providing access to the Grid Manager and NTP servers should be included on the Grid Network subnets or as Admin Network subnets during configuration. When you complete the grid configuration steps, the Client Network gateway becomes the node default gateway. Allow NTP and installer client access through both the Grid and Client Network gateways.

or

Add the NTP or installer client subnets, or both, as Grid Networks (so explicit routes will be created).

or

Add NTP and installer client subnets to the Admin Network External Subnet List (AESL).

Client Network, but at a later time Subnets providing access to the Grid Manager and NTP servers should be included as Grid Networks or as Admin subnets. The Client Network gateway will become the node default gateway Allow NTP and installer client access through both the Grid and Client Network gateways.

or

Add the NTP or installer client subnets, or both, as Grid Networks (so explicit routes will be created).

or

Add NTP and installer client subnets to the AESL.