Updating the Distributed DDNS Application Node - Adaptive Applications - BlueCat Gateway - 21.3

BlueCat Distributed DDNS Administration Guide
Locale
English
Product name
BlueCat Gateway
Version
21.3

Before you begin

You must redirect the database connection from the Distributed DDNS Application Node to the Distributed DDNS Data Node that will be upgraded last during the upgrade process to ensure that you can deploy changes to the new Data Node or Service Nodes. For example, if you have three Data Nodes and the order in which the Data Nodes are upgraded is node1, node2, then node3, the Distributed DDNS Application Node must be configured to use node3 as the database.

To redirect client connections from the Distributed DDNS Application Node to another Data Node, modify the root/gwdata/app/mariadb.yaml file on the Distributed DDNS Application Node so that the IP address of the Data Node is the last node to be updated.

To redirect the Application Node client connections
  1. Log in to the console of the BDDS of the Application Node in the cluster.
  2. Modify the /root/gwdata/app/mariadb.yaml file so that the host IP address points to another Data Node in the cluster.
  3. Log in to the Address Manager user interface.
  4. From the configuration drop-down menu, select a configuration.
  5. Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
  6. Under Servers, click the name of a BDDS where the Application Node is deployed. The Details tab for the server opens.
  7. Click the Diagnostics tab.
  8. From the Actions menu, select Restart Gateway Container and click Execute.

Once you have redirected the Distributed DDNS Application Node connections, you can stop the existing Distributed DDNS Application Node and install the updated Distributed DDNS Application Node version.

Stopping the Distributed DDNS Application Node
  1. Remove the Service Nodes and Data Nodes from the Distributed DDNS Application UI. This mitigates errors during the installation process. For more information on removing the Service Nodes and Data Nodes from the Distributed DDNS Application UI, refer to Service Node information and Database Node information.
    Note: Removing the nodes from the Distributed DDNS Application UI only removes the node data from the database. The nodes will continue to operate normally.
  2. Log in to the Address Manager user interface.
  3. From the configuration drop-down menu, select a configuration.
  4. Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
  5. Under Servers, click the name of the BDDS that the Distributed DDNS Application Node is deployed to. The Details tab for the server opens.
  6. Click the server name menu and select Service Configuration.
  7. From the Service Type drop-down menu, select BlueCat Gateway. Address Manager queries the server and returns the current values for the service settings.
  8. Under General Settings, uncheck the Enable Gateway Service check box.
  9. Click Update.

    After you click Update, the Gateway Service is disabled and the Distributed DDNS Application Node is stopped.

Updating the Distributed DDNS Application Node

Once it has successfully stopped, you can update the Distributed DDNS Application Node to a newer version. For more information on installing a newer version of the Distributed DDNS Application Node, refer to Installing the Distributed DDNS Application Node on a BDDS.