Roll back the IP address of Control Room and Database servers - If connectivity or service issues occur after the change of Control Room and Database server IP addresses, revert the environment to the last known working configuration.

Automation 360

If connectivity or service issues occur after the change of Control Room and Database server IP addresses, revert the environment to the last known working configuration.

Before you begin

Ensure that you review the following considerations before making any IP address changes:
  • Record the existing Control Room server IP address, database server IP address, host names, and port configurations.
  • Back up all configuration files that will be modified during the procedure.
  • Create a snapshot or backup of the Control Room server and database server, if supported by your environment.
  • Verify that database backups are available and recoverable.
Note: If a virtual machine snapshot or infrastructure backup was created before implementation, you can use the snapshot restore process defined by your organization's disaster recovery procedures to return the environment to its pre-change state.

Procedure

  1. Stop all Automation Anywhere services on the Control Room.
  2. Restore the original configuration files that were backed up before the IP address change.
  3. Revert the Control Room and database server network settings to their previous IP addresses.
  4. Update DNS records or host file entries, if they were modified as part of the implementation.
  5. Verify the connectivity between the following components:
    • Control Room and database server.
    • Control Room and Bot Runner or Bot Creator devices.
    • Control Room and any load balancers, proxies, or external integrations.
  6. Restart Automation Anywhere services.
  7. Sign in to the Control Room and validate the following:
    • User authentication.
    • Automation deployment and execution.
    • Device connectivity.
    • Scheduled automation execution.
  8. Confirm that all services are functioning as expected before returning the environment to production use.

What to do next

After completing the rollback, review the following:
  • Verify that the Control Room is reachable using the original URL.
  • Confirm that all Automation Anywhere services are running.
  • Test a sample bot execution.
  • Review application and service logs for any remaining connectivity or configuration errors.