Configuring Clusters

This section describes how to configure a Carbon Black EDR cluster that contains a primary node and minion nodes.

When configuring a Carbon Black EDR cluster, Carbon Black recommends that you refer to the Carbon Black EDR Server Operating Environment Requirements Guide, which describes performance and scalability considerations in deploying Carbon Black EDR.

The configuration process involves two generic Carbon Black EDR server installs, which initially have no client software configured on them. The goal is to create a Carbon Black EDR cluster with cb-primary as the primary node and cb-minion as the minion node.

You must execute the initial cbinit, which runs on the primary node.

If the node is a primary and the cluster has more than three nodes, add the following parameter to instruct the primary node not to store events:

--no-solr-events

Configure a Cluster

Perform the following procedure to configure a Carbon Black EDR cluster.

Prerequisites

The following instructions assume that you have installed the Carbon Black EDR RPM and have run the yum install cb-enterprise command on the primary node. The minion is simply a generic install of CentOS. For more information, see Installing and Initializing a Server.

Procedure

On the primary node, issue the cbinit command with the correct --no-solr-events flag defined, based on your installation. In this example, we instruct the primary node to not store events.

/usr/share/cb/cbinit --no-solr-events


Use the following Carbon Black EDR cluster management command-line tool options to initiate the cluster configuration: `[root@cb-‐primary~]# /usr/share/cb/cbcluster` Usage: `cbcluster COMMAND [CMD OPTIONS]` Available commands are: `help` – Display this help screen `start` – Start the cluster `stop` – Stop the cluster `status` – Get the running status of the cluster `add-node` – Add a minion node to the cluster `change-node` – Change parameters of the existing cluster node `remove-node` – Remove a minion node from the cluster

From cb-primary, run the following command to initiate the cluster configuration:
```
[root@cb-primary~]# /usr/share/cb/cbcluster add-node
```
Enter the following information :
- For the hostname or IP address of the remote node, enter the IP address of the server to become a minion node. For example: 172.xx.xxx.xxx .
- For the password of the server that will become a minion node, enter the root password for the server. Do not enter the Carbon Black EDR password.
The Carbon Black EDR software is now installed on each minion. The yum repo configuration used on the primary is used on each added node.
When all minion nodes have been configured, start the cluster services:
```
[root@cb-primary~]# /usr/share/cb/cbcluster start
```

Review the results in the config file:

[root@cb-primary~]# cd /etc/cb/
[root@cb-primary~]# less cluster.conf

############################################################################
#
# /etc/cb/cluster.conf:
# This file contains Carbon Black EDR server cluster configuration,
# which includes the list of participating nodes and Solr 
# shards present on every one of those nodes.
#
# NOTE: The contents of this file are being managed by
# /usr/share/cb/cbcluster command line tool and any changes
# made here may be overwritten next time that tool is used.
#
###########################################################################

[Cluster] 
NodeCount=2 
NextMinionAutoInc=2 

[Primary] 
Host=172.16.100.110
HasEvents=False
User=root

[Minion1] 
Host=172.16.100.111
HasEvents=True
User=root

Log into Carbon Black EDR.
Click Username >Settings > Server Nodes to view the cluster nodes.

Note: Starting with Carbon Black EDR version 7.7.0, the cluster.conf section names [Primary] and [Minion<n>] replace [Master] and [Slave<n>], respectively. The former section names still work for backward compatibility.