vROps Change Master Node IP
Changing Master Node IP address
In some cases I have found customers want to change their Master Node IP when moving from a Pilot to Production for example. This is supported from VMware but isn’t an easy task. Before we dig into this I also want to make sure it’s clear this isn’t changing the Master Node NAME. Changing the Master Node name isn’t supported and cannot be achieved by simply editing the CaSa script, * IT WILL BREAK YOUR CLUSTER *. There mentioning of changing the Master Node Name through an API call, but this is something you will need to call VMware’s GSS about. In a nutshell, it’s not support and you are better off following my Master Node Name change blog entry.
Two different methods exist where you could change the Master Node IP, both are complicated. You can’t simply login to the appliance and change the IP or change them from the properties window. roleState, Gemfire, and Persistence all need this new IP information updated. If you just need to change the IP address this blog entry will assist you in accomplishing such task (the first method). The second method I spoke about is following my blog entry regarding changing the Master Node Name. This entry talks about turning your single node cluster into an HA federation and have the Master Replica reflect the new IP and New node name you want and invoke a failure.
-
Master Node IP preparation steps
|
Special Note: |
|
It’s always better to be safe than sorry so don’t be a hero and take a snapshot on vROps virtual machine before you start. |
The first thing you need to do is to make sure you bring vROps cluster offline. This can be done via vROps admin UI at https://<your Master Node IP>/admin/
As a result of taking the cluster offline, the Master Node will be brought offline as well.
-
Change IP from the C# Client
Shutdown the Master Node VM and change its IP address. In vROps, this configuration is part of the VM properties.
 |
 |
Before powering on the VM, make sure to change any DNS A record you might have pointing to the old IP address.
Once the VM is up and running, open SSH console session.
-
Configuring the Master Node from console
Changing the IP in the VM properties is not enough, we also need to make sure the GemFire and the vROps cluster service are also aware of the change.
|
Note |
|
Press Alt-F1 to get into the shell of the virtual appliance. |
-
CaSA service changes
-
Stop the CaSA service
service vmware-casa stop
-
Edit the following file and update the old IP to the new IP:
/storage/db/casa/webapp/hsqldb/casa.db.script
|
Note |
|
If the IPs do not exist yet in casa.db.script, start then stop the CaSA service. |
-
Start the CaSA service
service vmware-casa start
-
ConfigureRoles script
Navigate to: /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin
Run the following script:
./vcopsConfigureRoles.py –-adminCS <Your New Master Node IP>
|
Note |
|
The above script command is two dashes, not one dash, i.e. <dash><dash>adminCS. |
-
Manually changing Script files
If you feel like manual process is your thing (or if you just want to validate the script did its job), edit the IP address in the following 3 configuration files:
/usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties
/usr/lib/vmware-vcops/user/conf/gemfire.properties
/usr/lib/vmware-vcops/user/conf/persistence/persistence.properties
roleState.properties modifications
roleState.properties
gemfire.properties modifications
gemfire.properties
persistence.properties modifications
persistence.properties
After the change has been made, all that is left is to login to the admin UI again (using the new IP address of course) and bring the cluster (and the Master Node for that matter) online again.
This should complete the steps needed to re-IP the appliance.
