Adding a node

Add nodes to a datacenter to manage install and configuration jobs from Lifecycle Manager.

Add nodes to a datacenter to manage install and configuration jobs from Lifecycle Manager.
Note: Lifecycle Manager does not currently support managing DSE Multi-Instance nodes (also referred to as dense nodes).


  • Add a cluster.
  • Add a datacenter.
  • If you need a configuration profile specialized at the node level, define a node-specific configuration profile.
  • If you need an SSH Credential to specify access and privileges at the node level, add an SSH credential for that purpose.
  • Install a version of Python 2.6 through 2.7 on the target nodes. LCM does not automate the installation of Python, and install jobs fail if Python is not installed.
Note: Repositories are inherited from the cluster.


  1. Click Clusters in the Lifecycle Manager navigation menu.
  2. Select the cluster and datacenter to which you want to add a node.
  3. Click the plus sign icon above the Nodes pane.
    The Add Node dialog displays. Several fields display the default values that are used if no values are entered.

    LCM Add Node dialog

  4. Enter a Name for the node.
    The node name must be unique per datacenter ID.
  5. Enter the name of the rack in the Rack field if you do not want to accept the default of rack1.
    Tip: Type a value or use the down arrow key to select any previously entered rack names for a datacenter.
  6. Enter the SSH IP Address.
  7. Consult the following table for assistance with completing the fields and overriding their defaults:
    Table 1. Node fields
    Field Description
    Name* Enter a name for the node. Nodes names must be unique within a datacenter. Required.
    Rack* Enter the name of the rack. If a rack is not entered, the rack name default is rack1. Example: rack3. Any previously entered rack names for a datacenter are available for selection.
    SSH IP Address* Default: SSH IP Address specified for the cluster. Required.
    SSH Management Port Enter a port value if you do not want to inherit the value from the datacenter. Default value for the SSH port at the cluster level is 22.
    SSH Credentials Select an SSH credential to apply at the node level to override inheriting the credentials from the datacenter level.
    Config Profile Select a configuration profile to apply at the node level, which overrides inheriting the configuration profile from the cluster or datacenter levels. Defaults to the datacenter config profile.
    Listen Address Default: SSH IP Address. The IP address or hostname that Cassandra binds to for connecting to other Cassandra nodes.
    Broadcast Address Default: Listen Address. The broadcast address is the IP address a node tells other nodes in the cluster to contact it by. A broadcast address allows public and private addresses to be different. For example, use the broadcast address in topologies where not all nodes have access to other nodes by their private IP addresses.
    Native Transport (formerly RPC) Address Default: SSH IP Address.
    • For DSE versions 6.0 and later, enter the IP for native_transport_address.
    • For DSE 5.1, enter the IP for rpc_address.
    Native Transport (formerly RPC) Broadcast Address Default: Native Transport (formerly RPC, non-broadcast) Address.
    • For DSE versions 6.0 and later, enter the IP for native_transport_broadcast_address.
    • For DSE 5.1, enter the IP for broadcast_rpc_address.
    Comment Enter an optional comment about the node.
    Seed Node Select a seed node option:
    • Automatically choose: (Default) Allow Lifecycle Manager to select a seed node. LCM designates one seed per rack in each datacenter. If only a single rack is defined, the first two nodes in each datacenter will be designated as seed nodes. If only a single datacenter is defined, the first three nodes in the cluster will be designated as seeds.
    • Make this a seed node: Select to designate the node as a seed node used by gossip for bootstrapping new nodes joining a cluster.
      Warning: When adding a node to an existing datacenter that has already been converged (that is, an install job has already been run) in LCM, a tooltip warning appears: New nodes that list themselves as seeds will fail to bootstrap and will require immediately running a repair on the node. DataStax recommends designating the node as a seed after the node has bootstrapped into the cluster.

      Adding a node to an existing datacenter seed node warning

    • Do not make this a seed node: Select to explicitly exclude the node from seed node designation, such as the scenario described in the previous warning.

    After adding a node but before running a job, the Node Details displays the status as not a seed node. The true seed node status is not displayed until after running an install job.

    Note: It is a best practice to designate more than one seed node per datacenter (ideally two per datacenter). However, do not make all nodes seed nodes. See Internode communications (gossip).
  8. Click Save.
    The newly added node displays in the Nodes pane of the Clusters page. The Node Details display in the details area next to the cluster model panes.

What's next

  1. Continue adding nodes to the datacenter until done. Repeat the steps in this procedure.
  2. Run an installation job.