Support for these three network interfaces provides significant flexibility in the choice of network topologies for a wide range of single and multi-site deployments.
When you configure the Grid Network, you establish the host IP address, subnet mask, and Gateway IP address for the eth0 interface for each grid node. During configuration, you create a list of subnets called the Grid Network Subnet List (GNSL). This list contains the list of subnets in the Grid network and the external subnets interfacing to the Grid network. At installation, the Grid Network interface auto-generates static routing tables for all subnets in the GNSL and adds a default route if the Grid Network has a gateway and there is no Client Network.
The simplest network topology is created by configuring the Grid Network only. This topology is appropriate for single site deployments that are not externally available, and proof-of-concept or test deployments.
When you configure the Admin Network, you establish the host IP address, subnet mask, and Gateway IP address for the eth1 interface for each grid node. During configuration, you create a list of subnets called the Admin External Subnet List (A-ESL). This lists the subnets with external hosts that talk to grid nodes over the Admin Network. At installation of the Admin Network, a static route is generated automatically for all subnets in the A-ESL.
An example of Admin Network topology is a private (non-routed) Grid Network and a bounded Admin Network configured for each node.
When you configure the Client Network, you establish the host IP address, subnet mask, and Gateway IP address for the eth2 interface for every grid node connecting to the Client Network. At installation of the Client Network, the default route is generated automatically if the Client Network gateway is configured, and then the default network is removed, if present, from the Grid Network interface.
You can configure a network topology consisting of a private (non-routed) Grid Network and an open Client Network configured for all other connectivity.
You can configure all three networks into a network topology consisting of a private (non-routed) Grid Network, bounded site-specific Admin Networks, and open Client Networks. Options for load balancing and client traffic segregation can be implemented, such as using a third-party load balancer.
