close
keyboard_arrow_left
Table of Contents
- play_arrow Introduction to Installing Network Insights
- play_arrow What's New in Network Insights
- play_arrow Real-time Threat Investigations with Network Insights
- play_arrow Installations
- play_arrow Configuration
- Network Insights Configuration
- Adding the Network Insights Appliance as a Managed Host
- play_arrow Appliance Configuration
- play_arrow Flow Sources
- play_arrow Flow Inspection Levels
list Table of Contents
keyboard_arrow_right
Flow data from the Network Insights does not Appear
date_range
14-Feb-23
SUMMARY Follow these steps to determine why the flow data from your Network Insights does not appear on the Network Activity tab.
Causes
This problem can be caused by a race condition, indicating that the system did not start in
proper sequence. This problem occurs when the following Napatech configuration file is
corrupted after
JSA
services are
restarted:
content_copy zoom_out_map
/opt/napatech3/config/ntservice.ini
Diagnosing the Problem
- Log in to the JSA Network Insights host by using an SSH session.
- Verify that flow data is not being received by typing the following
command:After the command is entered, a message displays similar to the following example:content_copy zoom_out_map
/opt/napatech3/bin/monitoring
ntservice not running
- Search for messages that show the bonding type of the adapter by typing the following
command:Messages similar to the following example indicate that the configuration file is corrupted. The corrupted file prevents thecontent_copy zoom_out_map
grep -i bonding /opt/napatech3/config/ntservice.ini
napatech3service from starting.content_copy zoom_out_mapBondingType = *Separate*
Resolving the Problem
Follow these steps to re-create the corrupted ntservice.ini configuration file.
You can save the corrupted file for investigation later.
- Log in to the JSA Network Insights appliance by using an SSH session.
- Move the ntservice.ini file to save it for
later:content_copy zoom_out_map
mv /opt/napatech3/config/ntservice.ini /root/
- Restart the Napatech service:content_copy zoom_out_map
systemctl restart napatech3
Note: The ntservice.ini configuration file is re-created when the service restarts.
- Test the service to confirm that it is now
working:You might see messages similar to the following examples:content_copy zoom_out_map
grep -i bonding /opt/napatech3/config/ntservice.ini
content_copy zoom_out_mapBondingType = Master BondingType = Slave - Rerun the following command to verify that the service is
running:content_copy zoom_out_map
/opt/napatech3/bin/monitoring
Results
The napatech3 service is started and flow data appears in
JSA
on the Network Activity tab.
If the service is still not running, open a case with Juniper Support.
