Configure additional IP address for a new cluster node - After installing the Control Room in the cluster node, if you add new nodes in the cluster, you have to configure additional static IP addresses for all the nodes in the property file on each node in the cluster.

Automation 360

After installing the Control Room in the cluster node, if you add new nodes in the cluster, you have to configure additional static IP addresses for all the nodes in the property file on each node in the cluster.

Before you begin

To perform the task, you must have a Control Room administrator account with the required rights and permissions.

  • Ensure that you have a maintenance window, which requires complete downtime for the following:
    • All the user devices will be disconnected.
    • No schedules will run during maintenance.
    • Bot Agent and Automation Anywhere Control Room will not be accessible.
  • Complete the Control Room installation on any new node.

Procedure

Perform the following steps on each node in the cluster:
  1. Stop the following Automation Anywhere services on the Control Room node:
    1. Automation Anywhere Control Room Reverse Proxy
    2. Automation Anywhere Control Room Caching
    3. Automation Anywhere Control Room Service
    4. Automation Anywhere Elastic Search Service
    5. Automation Anywhere Bot Insight Elastic Search
    6. Automation Anywhere Control Room IQ Bot Service
    7. Automation Anywhere Control Room Robotic Interface Service
  2. Locate the cluster.properties file in your Control Room directory.
    For example, the default location is: C:\Program Files\Automation Anywhere\Enterprise\config\
    If the file does not exist in your Control Room directory, create the file.
  3. Add the following properties and configure the primary IP addresses as a static IP address for all the cluster nodes (including existing cluster nodes) in the cluster.properties file. 
    ignite.discovery.mode=static
ignite.discovery.static.ips=<primary ip addresses>
    For example: ignite.discovery.static.ips=10.0.11.153,10.0.11.13
  4. If the nodes have multiple IP addresses, also add the following property and configure a specific primary IP address on each node in the cluster: 
    ignite.local.static.ip=<primary ip address>
    For example: ignite.local.static.ip=10.0.11.153
  5. Save the cluster.properties file.
  6. Modify the elasticsearch.yml file for the new IP address:
    1. Locate the elasticsearch.yml file in the Control Room directory.
      For example, the default location is: C:\Program Files\Automation Anywhere\Enterprise\elasticsearch\config\elasticsearch.yml
    2. Update elastcissearch.yml with the new IP address using the following property: discovery.zen.ping.unicast.hosts:["ip1",”ip2”,”ip-new”]
    3. Save the elasticsearch.yml file.
    Note: Starting from Automation 360 v.28 release (Build 17593), the Elasticsearch service is replaced with OpenSearch service as the underlying technology for core product capabilities such as audit, Bot Insight, and so on.
  7. Start all the services that were stopped in Step 1 on each Control Room node.
    Note: Wait for an interval of 40 seconds before starting the next service.