Dual-network deployment

Installation toolkit does not support the dual-network. Therefore, you need to configure the IBM Storage Scale dual network manually.

This section describes the recommended network configuration for CDP Private Cloud Base, HDFS Transparency and IBM Storage Scale cluster if more than one network is configured in the environment.

For example:
[root@c902f09x05 ~]# mmlscluster
GPFS cluster information
========================
  GPFS cluster name:         SS5022.gpfs.net
…………….
…………….
 Node  Daemon node name          IP address   Admin node name      Designation
-------------------------------------------------------------------------------
   1   c902f09x05-eth4.gpfs.net  128.20.1.26  c902f09x05.gpfs.net  quorum
   2   c902f09x07-eth4.gpfs.net  128.20.1.28  c902f09x07.gpfs.net  quorum
   3   c902f09x08-eth4.gpfs.net  128.20.1.29  c902f09x08.gpfs.net  quorum
   4   c902f09x06-eth4.gpfs.net  128.20.1.27  c902f09x06.gpfs.net

In the above example, the Daemon node name and IP address fields correspond to the Daemon network used for data traffic in IBM Storage Scale and the Admin node name corresponds to the network used for running IBM Storage Scale administration commands (such as mmlscluster, mmgetstate etc).

The Admin node name and Daemon node name can be changed by using the mmchnode command. For more information, see GPFS node adapter interface names in the IBM Storage Scale: Concepts, Planning, and Installation Guide.

In a dual network environment, there are two networks: Network 1 and Network 2. The following are the recommended network setup configuration options for the IBM Storage Scale cluster:
  1. Deploy Cloudera components, HDFS Transparency, CES IP/Hostname and IBM Storage Scale Admin network in a common network. For example, Network 1.

    The CDP Private Cloud Base service daemons (for example, Yarn ResourceManager) and HDFS Transparency daemons (for example, NameNode) should be in the same network to be able to communicate with each other over RPC.

  2. Deploy IBM Storage Scale daemon network on the other network. For example, Network 2. Usually this is the high-speed network for IBM Storage Scale data traffic.
The separation of IBM Storage Scale admin and daemon networks offers the following benefits:
  • If the cluster is busy with heavy I/O, using the same network for admin and daemon can cause administrative commands to run slower.
  • IBM Storage Scale Admin network requires passwordless-ssh from one central node to the other nodes. The daemon network does not require ssh. This can help to restrict ssh access to only one selected network to address security concerns.