Discovery: After changing the IP addresses for cluster members, services will no longer start

Knowledge Article

Discovery: After changing the IP addresses for cluster members, services will no longer start
BMC Discovery
BMC Discovery
All Versions
BMC Discovery
BMC Discovery
All Versions
After changing the IP addresses for cluster members, services will no longer start.

 

First, verify that the IP addresses have been changed according to the documented instructions 

See Changing the address of a machine and The netadmin user 

If the cluster member VMs were created using VM cloning, and the IPs are now changed, run the command "tw_cluster_control --replace-vm-uuid" on each member to fix the UUID mismatch caused by cloning. Then, as the tideway user, perform the following steps on each cluster member:

1. Backup the /usr/tideway/etc/cluster.conf and /usr/tideway/etc/ds_cluster.conf files using these commands:

  • cp /usr/tideway/etc/cluster.conf /usr/tideway/etc/cluster.conf.backup
  • cp /usr/tideway/etc/ds_cluster.conf /usr/tideway/etc/ds_cluster.conf.backup

NOTE: Do not delete or move the ds_cluster.conf file. Use the above copy(cp) command to take a backup of this file and then follow these steps:

2. Edit the cluster.conf and ds_cluster.conf files to specify the new IP address. 

3. Use the article below to stop and restart the services
Discovery: How to start and stop services - INCLUDES VIDEO
BMC Discovery
BMC Discovery
All Versions
Attachment(s):