Known Issues

This section describes the known issues and workaround, if any:
nfa1000
This section describes the known issues and workaround, if any:
Known Issue in release 10.0.5
Filter and OrderBy system queries do not work for custom properties in NFA OData API
Symptom:
Filter and OrderBy system queries do not work for custom properties in NFA OData API.
Solution:
No known solution as of now.
There are no other known issues in the current release. Password Reset issue and DBPasswordUtils is not working in windows 2012/2016 harvester issue can be found while upgrading, this occurs when the password has been changed and upgrading to 10.0.5.
Known Issue in release 10.0.4
DBPasswordUtils is not working in windows 2012/2016 harvester
Symptom:
The utility gets hanged and the passwords cannot be changed.
Solution:
Replace the ReporterAnalyzer.ini file from console and copy to the harvester machine and rerun the DBPasswordUtils.
There are no other known issues in the current release. Password Reset issue can be found while upgrading, this occurs when the password has been changed and upgrading to 10.0.4.
Known Issue in release 10.0.3
There are no new known issues in the current release. Password Reset issue can be found while upgrading from 10.0.2 version. This occurs when the password has been changed and upgrading to 10.0.3.
Known Issue in release 10.0.2
Password reset to default password on upgrade from 10.0.1 to 10.0.2 on SB.
Symptom:
NFA Services are down.
Solution:
Re-run the password utility after the upgrade.
This known issue in Network Flow Analysis 10.0.2 is applicable to the releases 10.0.2 and later. This issue occurs when upgrading from 10.0.x to 10.0.2 and later versions.
Reaper service does not start on Linux
Symptom:
Reaper service is down.
Solution:
Navigate to
<NFA_HOME>/DBUsers/
directory and run the
dos2unix ReporterAnalyzer.ini
command. Start the Reaper service.
Known Issue in release 10.0.1 and Previous Release
Application Failed While Creating Response from the Data
Symptom:
Expand queries gives an error for olingo v4.1.0 when XML is the output format.
Solution:
No known solution as of now.
Pump Service Fails to Start after Upgrade
Symptom:
The pump service fails to start after upgrade.
Solution:
Verify the connection errors in the pump log. Ensure all the services are up and running and restart the pump service.
If you notice any exception that is related to “Invalid file format”, delete the content in
$INSTALL_DIR/REPORTER/datafiles/input/Staging
and start the pump service.
Report Service Does not Start after Upgrade
Symptom:
The Report service fails to start after upgrade.
Solution:
If you notice any MySqlException exception in the Report Service log, restart the Report service.
Delay in Display of AWS VPC Flow Data
Symptom:
The AWS VPC flow data does not show up immediately in the CA NFA console.
Solution:
There is a delay of ten minutes to display the AWS VPC Flow data received from CA VNA.
Known Issue in release 9.5.0
The known issues that were identified in
DX NetOps
9.5.0 are applicable to the current release too. For more information, see the Known Issues 9.5.0 page.