Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Warning

Note: The cell member federation in DPOD 1.0.22.0 has a bug which causes duplicate agent records in the manager.

It is highly recommended you wait for version 1.0.22.1 which will resolve this.

Cell Manager Installation

...

  • Make sure to meet the prerequisites listed at the top of this page.

  • Follow the procedure: Prepare Pre-Installed Operating System.

  • Physical servers should use RHEL or Rocky Linux as the operating system (and not CentOS).

  • The cell member server should contain disks according to the recommendations made in the sizing process with IBM Support Team, which includes disks for OS, install, and data (one for /data and 6 to 9 additional disks for /data2/3/4...).

  • Physical federated cell members with 4 CPU sockets and NVMe disks require special disks and mount points configuration to ensure performance. See Configuring Cell Members with 4 CPU Sockets and NVMe Disks.

  • Use Non-appliance Mode and follow the procedure: Non-Appliance Installation
    During installation, the four-letter Installation Environment Name should be identical to the one that was chosen during the Cell Manager installation.
    During installation, when prompted to choose the IP address for the Web Console, choose the IP address of the external network interface.

  • Make sure httpd service is running and can be restarted successfully. If an error is displayed during the service restart, please see if the following information helps in resolving it: https://access.redhat.com/solutions/1180103

...

Mount Points

Disks

/data2, /data22 and /data222 (if exists)

Disks connected to NUMA node 1

/data3, /data33 and /data333 (if exists)

Disks connected to NUMA node 2

/data4, /data44 and /data444 (if exists)

Disks connected to NUMA node 3

  • For all other types of federated cell members servers - you may map the mount points to any disk.

...

Code Block
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme0n1               259:2    0   2.9T  0 disk 
└─vg_data2-lv_data    253:0    0   2.9T  0 lvm  /data2
nvme1n1               259:5    0   2.9T  0 disk 
└─vg_data22-lv_data   253:11   0   2.9T  0 lvm  /data22
nvme2n1               259:1    0   2.9T  0 disk 
└─vg_data3-lv_data    253:9    0   2.9T  0 lvm  /data3
nvme3n1               259:0    0   2.9T  0 disk 
└─vg_data33-lv_data   253:10   0   2.9T  0 lvm  /data33
nvme4n1               259:3    0   2.9T  0 disk 
└─vg_data44-lv_data   253:8    0   2.9T  0 lvm  /data44
nvme5n1               259:4    0   2.9T  0 disk 
└─vg_data4-lv_data    253:7    0   2.9T  0 lvm  /data4

Cell Member Federation

Warning

Note: The cell member federation in DPOD 1.0.22.0 has a bug which causes duplicate agent records in the manager.

It is highly recommended you wait for version 1.0.22.1 which will resolve this.

In order to federate and configure the cell member, run the following script in the cell manager, once per cell member.

...