Configuring a TCP/IP network (Linux)

The topics in this section detail how to configure a Transmission Control Protocol/Internet Protocol over Ethernet (TCP/IP) network.

No additional hardware, firmware, or software is required to install DB2® pureScale® Feature on a TCP/IP network. The only requirement is to have a network that is accessible by all the hosts. The hosts must be able to access each other, and all hosts must be on the same subnet.

It is a best practice that your TCP/IP network is 10 Gb or higher. However, if your workload has only modest network usage requirements, to avoid the DB2 product from blocking a network slower than 10 Gb, enable the registry variable DB2_SD_ALLOW_SLOW_NETWORK.

You set up your TCP/IP network as you normally would, set up all hosts on the same subnet, and test the host name resolution and connectivity.

For a geographically dispersed DB2 pureScale cluster (GDPC), if multiple adapter ports are assigned to each member or CF, ensure those network interfaces are bonded so that only the bonded interface is specified as the NETNAME column in the db2instance -list output. All NETNAME listed in the output should be in the same IP subnet.. This single IP subnet is mandatory to setup GPFS described in Getting the cluster installed and running in a GDPC environment