How do I migrate the NFA Console or Harvester to a new server?

Products

• Network Flow Analysis
• Network Observability

Issue/Introduction

How do I migrate the NFA Console or Harvester to a new server?

Environment

Component : NQRPTA - REPORTERANALYZER

Resolution

The steps for migrating your NFA Console and/or Harvester servers to a new server can be found in the links below:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/24-3/upgrade-dx-netops/prepare-for-the-upgrade/prerequisites/plan-the-upgrade/plan-the-upgrade-for-flow-monitoring/verify-that-the-windows-servers-are-prepared/upgrade-to-microsoft-windows-server-2022.html

The work flow for doing this and some additional tips are below:

1. Install the same version of NFA on the new server, if possible to the same drive and directory path.

Before installing the Console on the new server, make sure you go through and install the prerequisites from the two links below:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/24-3/upgrade-dx-netops/prepare-for-the-upgrade/prerequisites/plan-the-upgrade/plan-the-upgrade-for-flow-monitoring/verify-that-the-windows-servers-are-prepared/upgrade-to-microsoft-windows-server-2022.html

 

2. Stop and disable all services on the current servers except the CA MySql Service. On the new servers, just stop all the services except CA MySql Service. 

 

3. If NFA is linked to PC, go into DX NetOps ->Administration->Data Sources  and Disable the NFA Data Source, DO NOT DELETE THE DATA SOURCE.

 

4. The guide says to back the full  \CA\NFA\Netflow\datafiles\ directory but you only need the directories below and copy over to the new server, this will take some time:

•  \CA\NFA\Netflow\datafiles\ReaperArchive15 - this is your historical 15 Minute Resolution data for up to the last 12+ months.  
•  \CA\NFA\Netflow\datafiles\ReaperArchive - this is your 1 minute data only retained for the last 30 days, so this is optional.
•  \CA\NFA\Netflow\datafiles\HarvesterArchive - (Do not move to new server) - this is only the last 24-48 hours of Flow Forensics data and is a huge amount of data, which we do not recommend moving.

 

5. Backup the MySql databases:

    Console: mysqldump -uroot -proot@123 reporter > D:/reporterbackup.sql
    Harvester: mysqldump -uroot -proot@123 harvester > D:/harvesterbackup.sql

 

6. Copy .sql files from the last step over to the new servers and restore them with the steps from the guide.

 

7. Restore the MySql databases:

    Console: mysql -uroot -proot@123 reporter < D:/reporterbackup.sql
    Harvester: mysql -uroot -proot@123 harvester < D:/harvesterbackup.sql

8. If you have installed to a new drive or directory path, follow step 10 of the article below, if not, skip this step:

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=29426

 

9. On your Harvesters Edit the D:/CA/NFA/DBUsers/ReporterAnalyzer.ini file to put the proper IP Address in where it says ReporterAnalyzer.host (not dbHost) and save the file.

 

10. On your NFA Console Edit the D:/CA/NFA/DBUsers/ReporterAnalyzer.ini file to put the proper IP Address in where it says ReporterAnalyzer.host (not dbHost) and save the file.

 

11. If the NFA Console is set up using HTTP and has a new IP addess you must run:

mysql -P3308 -D reporter -unetqos -pnetqos -t -e "update performance_center_properties set propvalue='x.x.x.x' where propname='NpcWebServiceHost' and priority = 2;
mysql -P3308 -D reporter -unetqos -pnetqos -t -e "update data_sources2 set consolehost='x.x.x.x';
mysql -P3308 -D reporter -unetqos -pnetqos -t -e "update data_sources2 set host='x.x.x.x';
mysql -P3308 -D reporter -unetqos -pnetqos -t -e "update parameter_descriptions set defaultvalue='x.x.x.x' where parameter='WatchdogPollingProxy';"

If you are running HTTPS, please run ApplyHTTPS: https://knowledge.broadcom.com/external/article/213529/nfa-applyhttps-tool.html

 

12. If the hostname has changed, go into DX NetOps ->Administration->Data Sources and EDIT the NFA Data Source with the new hostname.  DO NOT DELETE THE NFA DATA SOURCE.

 

13. Start all CA NFA* and NetQos* services on the servers.

 

14. If your Harvester IP addresses have changed, please go into DX NetOps ->Administration->Data Sources/Network Flow Analysis@...

 

Select Harvester and Edit the Harvester addresses.  DO NOT DELETE THE HARVESTERS, as this will cause a loss of all data for that Harvester.

 

15. Enable the NFA Data Source in the NetOps Portal Data Sources page.