Configuring the host network

After completing the Linux installation on your hosts, you might need to perform some additional configuration to prepare a set of network interfaces on each host that are suitable for mapping into the StorageGRID Webscale nodes you will deploy later.

Before you begin

You have reviewed “Networking requirements” and “Node migration requirements” in this document. These topics contain information that might affect how you choose to accomplish this task.

Attention: If you are using VMs as hosts, you must allow all interfaces to receive and transmit data for MAC addresses other than the ones assigned by the hypervisor. This capability is typically referred to as promiscuous mode. Promiscuous mode is disabled by default for OpenStack and VMware hypervisors.
Note: If you are using VMs as hosts, you should select VMXNET 3 as the virtual network adapter. The VMware E1000 network adapter has caused connectivity issues with StorageGRID Webscale containers deployed on certain distributions of Linux.

About this task

Grid nodes must be able to access the Grid Network and, optionally, the Admin and Client Networks. You provide this access by creating mappings that associate the host's physical interface to the virtual interfaces for each grid node. When creating host interfaces, use friendly names to facilitate deployment across all hosts, and to enable migration.

You can use the same host network interface to provide the Grid Network interface for all StorageGRID Webscale nodes on the host; you can use a different host network interface for each node; or you can do something in between. However, you would not typically provide the same host network interface as both the Grid and Admin Network interfaces for a single node, or as the Grid Network interface for one node and the Client Network interface for another.

You can complete this task in many ways. For example, if your hosts are virtual machines and you are deploying one or two StorageGRID Webscale nodes for each host, you can simply create the correct number of network interfaces in the hypervisor, and use a 1-to-1 mapping. If you are deploying multiple nodes on bare metal servers for production use, you can leverage the Linux networking stack’s support for VLAN and LACP for fault tolerance and bandwidth sharing. The following sections provide detailed approaches for both of these examples. You do not need to use either of these examples; you can use any approach that meet your needs.