NFA - Missing database columns after upgrading from legacy versions (e.g., 22.2.x) to newest releases

Products

• Network Observability
• Network Flow Analysis

Issue/Introduction

After upgrading DX NetOps Network Flow Analysis (NFA) from legacy versions (e.g., 22.2.x) to 25.4.7, flow data is not visible in the DX NetOps Portal or the NFA website. 

Additional observations may include:
- NFA Reaper service crashing due to out-of-memory errors.
- Corrupted `.bad` files accumulating in the Reaper input folder.
- NFA charts showing "No Data to Display" despite flow being received by the Harvester.

 

Environment

Upgrade from version 22.2.8 or earlier legacy versions.
DX NetOps Network Flow Analysis 25.4.x+

Cause

The issue is caused by missing database fields in the MySQL `harvester` database that were not properly created or migrated during a large-jump upgrade from legacy versions. Specifically, columns may be absent, preventing the Reaper service from processing flow data correctly.

Resolution

To resolve this issue, you must manually apply the missing database schema updates to the Harvester and Console databases.

Step 1: Apply SQL Scripts to Harvester
1. Log in to the NFA Harvester server.
2. Open a command prompt and navigate to the directory containing the SQL scripts (provided by Support).
3. Execute the following commands to update the `harvester` database:

mysql -uroot -p[password] harvester < AddSnmpPollingColumn.sql
mysql -uroot -p[password] harvester < ignoreHuaweiMib.sql

Step 2: Apply SQL Scripts to Console
1. Log in to the NFA Console server.
2. Apply the equivalent schema updates to the Console database as instructed by technical support.

Step 3: Restart Services
1. On the NFA Console, restart the **NetQoS ReporterAnalyzer Pump Service**.
2. On the NFA Harvester, restart the **CA NFA Reaper Service**.
3. Monitor the `pumplog*.log` on the Console and the Reaper logs on the Harvester to ensure files are processing without errors.