Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Reimage a Node and Add the Node Back with the Same IP Address

date_range 15-Apr-24

Perform the following procedure to reimage a node and add the node back with the same IP address when the primary database node in the Disaster Recovery (DR) cluster goes down:

  1. Reset the DR when the primary database node goes down on the active site.
  2. Delete the node that is down by selecting to transfer its role to other JBoss node in the cluster.
  3. Reimage the new Virtual Machine (VM) with the IP address of the deleted node and add it back to the cluster.
  4. When the setup goes into maintenance mode, cluster formation stops. To create the cluster again, perform the following:
    Note:

    You must create the cluster formation between the JBoss VIP node and the node that took the primary database role in Step 2.

    1. Run the following command on the initial Virtual IP address (VIP) node before addition of nodes:

      content_copy zoom_out_map
      pcs cluster stop --force 
      pcs cluster destroy 
      
    2. Run the following command on the VIP node:

      content_copy zoom_out_map
      /usr/bin/systemctl start corosync
      pcs cluster setup jmp-CLUSTER <node-hostname>
      
    3. Run the following command to authorize the host on both VIP node and the node that took the primary database role in step 2:

      content_copy zoom_out_map
      pcs host auth <other node's hostname>.
      Username: hacluster 
      Password: 
      jnpr123! pcs cluster start --all 
      pcs cluster enable
      
    4. Run the following command to check pcs cluster status:

      content_copy zoom_out_map
      pcs cluster status 
      Now On other node: 
      pcs cluster start
      

      Check the pcs cluster status on both VIP node and the node that took the primary database role in step 2. Both the nodes must be in active status.

    5. To add a Virtual IP address, run the following command:

      content_copy zoom_out_map
      pcs resource create virtual_ip ocf:heartbeat:IPaddr2 ip=<ip address> cidr_netmask=<subnet> nic=eth0:0 op monitor interval=30s
      pcs resource create before_vip lsb:beforeSwitchingVIP
      
    6. To start the pacemaker, run the following command:

      content_copy zoom_out_map
      /usr/bin/systemctl start pacemaker
    7. Run the following command when the pcs resource status for the VIP stops:

      content_copy zoom_out_map
      pcs property set stonith-enabled=false
      Chk ifconfig for VIP association on all nodes
      
    8. To remove a node from the cluster, run the following command:

      content_copy zoom_out_map
      pcs cluster node remove <node-hostname>
    9. You may need to restart the services. Use the following command to restart services on all the nodes:

      content_copy zoom_out_map
      systemctl stop jmp-watchdog 
      systemctl stop jboss 
      systemctl stop jboss-dc
      
    10. Check for the https services on the VIP node. If the service is down, bring it up.

      The cluster is now up and running.

    11. Configure and start the DR.

footer-navigation