Convert Standalone Data Aggregator to Fault Tolerant Data Aggregator pair

Products

• Network Observability
• CA Performance Management

Issue/Introduction

How can we convert a standalone Data Aggregator (DA) to a Fault Tolerant (FT) DA pair?

Converting non-FT DA to FT DA

We are planning to install a non-FT DA while waiting on NFS mount issue resolutions for the share drive requirements.

At a later time, when the NFS issue is resolved, we would like to add the other DA to form the FT DA cluster.

Environment

All supported Network Observability DX NetOps Performance Management Data Aggregator releases

Cause

Environmental limitations prevent use of a FT DA cluster configurations

Resolution

Follow these steps to move from a single DA to a FT DA cluster.

The following refers to various documentation sections found within the overall Install Fault-Tolerant Data Aggregators documentation topic.

1. Ensure current DA is running and stable.
2. Ensure new DA and proxy host are set up to meet requirements
   • Must use the same release as existing DA and Portal installs.
   • Ensure the systems meet requirements found in the Prepare to Install the Data Aggregator documentation topic.
   • Ensure all required ports are open and available. See the Fault-Tolerant Data Aggregator Proxy Server requirements found in the overall DX NetOps Performance Management Connectivity documentation topic for additional details.
   • Ensure the shared data directory is properly set up, allowing read/write access for both DA's and the proxy host.
   • Ensure the new DA and the DC's have the correct communication channels open.
3. Install the new proxy server. Follow standard install docs here in the Install the Proxy Server documentation.
4. Move the current standalone DA to a FT DA.
   • This is done by running the DA install over the existing DA install that's in place.
   • Answer the questions to switch to a FT DA configuration.
     1. Enter the system name for the second DA, the name for the new proxy host, the shared filesystem location and certificates if using HTTPS.
   • Install the Fault-Tolerant Data Aggregator Pair documentation topic.
5. Install the new second DA as a FT DA.
   • Install the new second DA. Follow standard install steps in the Install the Fault-Tolerant Data Aggregator Pair documentation topic.
   • Enter the system name for the first DA, the name for the new proxy host, the shared filesystem location and certificates if using HTTPS.
6. Reinstall each Data Collector (DC) in the environment.
   • This is down using the same process used to upgrade a DC.
     • Download a new install.bin from the active DA and install it over the existing DC.
   • When installing over the existing DC install answer the questions to convert the DC to one aware of the new FT DA cluster pair. Provide it with correct FT DA names for use.
   • See the Prepare to Install the Data Collectors documentation topic for additional details
7. Edit the DA DS in Portal Manage Data Sources.
   1. Log into the Portal web UI and navigate to Administration -> Data Sources -> Data Sources.
   2. On the resulting Manage Data Sources page, select the DA Data Source (DS) and select to Edit it.
   3. Set proxy host as new host name and use the Test button to verify success.
   4. Save the change if the Test cycle returns a successful result.

Additional Information

• Install Fault-Tolerant Data Aggregators documentation topic
• Convert Fault Tolerant Data Aggregator to Standalone Data Aggregator due to environment issues KB article
• Rebuild a Fault Tolerant Data Aggregator pair when one server failed KB article
• If steps are done incorrectly or out of order, a new acl token may be required. This is done using the steps from the following KB article.
  • Fault Tolerant Data Aggregator proxy services fail