...

In order to federate and configure the cell member, run the following script on in the cell manager once per cell member - e.g. if you want to add twocell members, run the script .

For instance, to federate two cell members, the script should be run twice (in the cell manager) , - first time with the IP address of the first cell member, and second time with the IP address of the second cell managermember.

impotent Important: the command The script should be executed using the os "OS root" user user.

/app/scripts/configure_federated_cluster_manager.sh -a <internal IP address of the cell member> -g <external IP address of the cell member>
For example: /app/scripts/configure_federated_cluster_manager.sh -a 172.18.100.34 -g 172.17.100.33

Example for a

...

Successful Execution

TODO

Note that the script writes two log file, one in the cell manager and one in the cell member, the . The log file names are mentioned in the script's output.- TODO

Example for a

...

Failed Execution

TODO

In case of a failure, the script will try to rollback the configuration changes it made, so you can try to fix the problem and run can be fixed before rerunning it again. - TODO

Cell Member Federation Post Steps

...

DPOD cell member is using NUMA technology NUMA (Non-uniform memory access).Default cell manager configuration bound Uniform Memory Access) technology. The default cell member configuration binds DPOD's agent to CPU 0 and the Store's nodes to CPU 1.
If the server has 4 CPUs, the user should edit node 2-3 service file the service files of nodes 2 and 3 and change the bind CPU to 2 and 3 respectively.

...

Identifying NUMA

...

Configuration

To identify the amount of CPU CPUs installed on the server, use the NUMA utility:

numactl -s

Example output for 4 CPU server :

policy: default
preferred node: current
physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 
cpubind: 0 1 2 3
nodebind: 0 1 2 3
membind: 0 1 2 3

Alter

...

Store's

...

Node 2 and 3 (OPTIONAL - only if the server has 4

...

CPUs)

The services files are located on the directory /etc/init.d/ with the name  namea MonTier-es-raw-trans-Node-2 and MonTier-es-raw-trans-Node-3.

...

After a successful execution, you will be able to see the new federated cell member in the Manage → System → Nodes page, .
For example, if we added two after federating 2 cell members the page should look as follows:

Also, the new agents will be shown in the agents list in the Manage → Internal Health → Agents page.
For example, if we have one the cell manager with has two agents and one cell members with there is a federated cell member with additional four agents, the page will show six agents:

Configure

...

the Monitored Device to

...

the Federated Cell Member Agents

It is possible to configure entire monitored device to remote collector's agent or just a specific domain to the federated cell member's agents.

To configure monitored device / specific domain please follow instructions on Adding Monitored Devices.