Adding an existing cluster

Add an existing DataStax Enterprise cluster to manage using OpsCenter Monitoring. Install agents on the cluster nodes automatically.

Add an existing DataStax Enterprise cluster to manage within OpsCenter. After you add the cluster to OpsCenter, you can import the cluster into Lifecycle Manager to centrally manage the cluster topology and configuration.
Note: If configuration encryption is active, OpsCenter automatically encrypts the sensitive fields such as passwords and writes the encrypted values to the configuration files. Do not enter manually encrypted values in the password fields.

Procedure

  1. Click New Cluster from the OpsCenter Monitoring main menu.
    The New Cluster prompt appears.

  2. Click Manage Existing Cluster and Get Started.
    The Connect to Existing Cluster dialog appears.

    Collapsed view Connect to Existing Cluster dialog in OpsCenter Monitoring

  3. Enter at least one hostname or IP address for a node in the cluster.
    
    ec2-123-45-6-789.us-west-1.compute.amazonaws.com
    ec2-234-56-7-890.us-west-1.compute.amazonaws.com
    
  4. If applicable, change the JMX Port and Native Transport Port listen port numbers if you are not using the defaults.
  5. If applicable, click Add credentials to add or edit the user credentials (username and passwords) if the JMX or Native Transport ports require authentication.
  6. Optional: If applicable to your environment, select DSE security (kerberos) is enabled on my cluster and complete the fields.

    DSE security (Kerberos) enabled configuration settings for OpsCenter connections

    1. Enter the Service Name. For example, if the server principal on your nodes is dse/nodeX.example.com@EXAMPLE.COM, this field should be dse.
    2. Enter the Opscenterd Client Principal for the OpsCenter process/machine to use. Example: opscenterd@YOUR_REALM.
    3. Enter the location of the keytab OpsCenter machine in Opscenterd Keytab Location, which contains credentials for the opscenter_client_principal.
    4. Enter the client principal for the DataStax Agent process/machine to use in DataStax Agent Client Principal. Example: agent@YOUR_REALM.
    5. Enter the location of the keytab on the DataStax Agent machines in DataStax Agent Keytab Location, which contains credentials for the agent_client_principal. Example: /path/to/keytab.keytab.

    For more information, see Authenticating with Kerberos and the Kerberos tutorial in the DataStax Enterprise documentation.

  7. Optional: If applicable to your environment, select Client-to-node encryption is enabled on my cluster.

    Client-to-node encryption enabled connection settings for OpsCenter and Agents

    Note: For information about creating keystores and truststores, see Enabling client-to-node encryption in OpsCenter.
  8. Click Next.
    The Set Up Agents dialog appears.

    Install Agents automatically or manually dialog

  9. Install or start agents automatically is selected by default. Click Next.
    If your environment requires manual installation of agents, click Install agents manually. Click the link to access the instructions for manually installing agents.
    The Agents Credentials dialog appears.

    Agents Credentials dialog for connecting to nodes

  10. Enter SSH credentials to connect to the nodes:
    1. Required: Enter a Username. The user must have root or sudo privileges.
    2. Optional: A sudo password can be entered in the Password box.
    3. Optional: Enter a Private Key.
    Entered credentials information is not saved or stored.
  11. Click Submit.
    The Agents tab opens, starts installing the agents, and displays the progress of the agent installation. The agent services may go up and down during the installation process.

    Agent Status while installing

    When the install process successfully completes, the DataStax agents have been deployed and configured for each managed node in the DataStax Enterprise cluster.

    Agents tab for viewing agents status