Today I am going to share you the process on how to reboot VRA nodes which are in production with no downtime for the customer.
In my demo environment, I have created the below set up:-
1) VRA Master Node - 10.0.0.2 - VRA1 (DNS Name of the First Node)
2) VRA Replica Node - 10.0.0.3 - VRA2 (DNS Name of the First Node)
3) NSX (Load Balancer) - 10.0.0.5
Task:- We need to reboot both the VRA nodes without any downtime for the customer.
1) Take the snap-shot of both the VRA nodes from the VC without memory.
2) Login on to VAMI page of both the VRA nodes
VRA1 - https://10.0.0.2:5480
VRA2 - https://10.0.0.3:5480
Now click on VRA Settings and click on Database.
3) Make a note of the current VRA master and replica node.
In my case, VRA1 (10.0.0.2) is the current master node and the other VRA node - VRA2 (10.0.0.3) is the replica node.
Hence we can reboot the VRA2 node as it is replica node.
Before rebooting the VRA2 node we will need to disable it in the NSX Load balancer.
Hence login to the VC and go to the path:- Home-Networking and Security.
Click on NSX Edges on the Left Pane. Now double click on the edge which is configured as a load balancer for your environment.
Click On Manage and Choose Load Balancer in the top menu.
Click On Pools and Choose the pool configured for VRA where both the VRA nodes are added.
Select the VRA Web pool and click on Edit and click members.
Now select the VRA replica node which is VRA2 (10.0.0.3) in my current scenario.
Select the VRA node - VRA2 (10.0.0.3) and click on Edit.
Now change the state of VRA2 node to disable from the present Enable state.
Once the replica node - VRA2 (10.0.0.3) is disabled in NSX, we will proceed with the reboot of it.
4) In order to reboot the VRA2 node login into the VRA2 appliance (SSH to the appliance) and type in reboot and press Enter.The VRA2 node - 10.0.0.3 will reboot now.
6) Once the VRA2 node is rebooted, login on to the VAMI page of the VRA2 node - 10.0.0.3.
Click on Services and check for all the registered services.
Please make sure that all the services and showing as registered under the services tab.
Also please make sure that the VRA nodes under VRA setings - Database are showing as UP.
VRA1 - 10.0.0.2
VRA2 - 10.0.0.3
As the VRA2 node is rebooted, hence VRA2 node will show in down state.
Hence we need to wait untill the VRA2 node (10.0.0.2) is showing in UP state. It might take 15-40 minutes for it to show in UP state.
7) Once the VRA2 node is up and all the VRA services are registered, we will need to enable it in the NSX Load Balancer Pool.
8) Please follow the step 3 to enable the state of the VRA2 node to enable.
9) Once the VRA2 node is enabled in NSX Load Balancer Pool, we will now perform the failover of the VRA,
Hence in order to perform the failover, login on the VAMI portal of the master node which is VRA1 (10.0.0.2) now.
So click on VRA Settings and click on Database on the VAMI page of VRA1 node - 10.0.0.2.
In the VRA1 node VAMI page, click on promote option which is next to the VRA2 node (10.0.0.3).
Once the VRA2 (10.0.0.3) node is promoted to the master node, the node VRA1 (10.0.0.2) will become the replica node.
10) Now disable the VRA1 node (10.0.0.2) in the NSX load balancer pool.
Follow the steps in Step3 to disable the VRA1 node in NSX load Balancer.
11) Once the VRA1 node is disabled in NSX load balancer.We will reboot the VRA1 node.
12) Please follow the same steps done in Step 4 to reboot the VRA node.
13) Once the VRA1 node is up after reboot, please make sure that all the VRA services are registered and VRA1 node is showing in UP state in the VRA VAMI page.
14) Please enable the VRA1 node to enable state in the NSX Manager.