Initial Configuration › Configure CA Network Flow Analysis to Work with CA Performance Center › Verify That Data Is Received › Verify That Data Is Collected › Verify Data File Collection in a Distributed Configuration

Verify Data File Collection in a Distributed Configuration

To verify that the appropriate data files are collected in a distributed configuration, make sure that .tbn, .nfa, and .rpr files are present.

Follow these steps:

1. Make sure that valid Time BIN (.tbn) files are collected:
   1. Locate the following directory on the installation server: <NFA_install_path>\Netflow\datafiles\HarvesterWork.
   2. Verify that the HarvesterWork directory contains files that are named <numeric_value>-9995.tbn.inc and that the files are larger than 0 KB.

      The directory may contain additional files with a .tmp extension.

   You know that a Harvester is receiving flow data when you see .tbn files that are larger than 0 KB.

2. Make sure that valid NetFlow archive (.nfa) files are collected:
   1. Locate the following directory on each Harvester installation server: <NFA_install_path>\Netflow\datafiles\HarvesterArchive.
   2. Verify that the HarvesterArchive directory contains valid NetFlow archive files--that is, .nfa files that are larger than 0 KB in size.
3. If you do not find valid flow archive files, complete the following troubleshooting tasks:
   • Verify that the Harvester service is running, as described in Service Management.
   • Review the harvester-wrapper.log files in the following directory: <NFA_install_path>\NetFlow\Logs.

     To change the logging level for the harvester-wrapper.log, modify the harvester.properties file, which is located at <NFA_install_path>\Netflow\bin. Change enableDebugLogging=false to enableDebugLogging=true.

4. Make sure that valid Reaper (.rpr) files are collected:
   1. Locate the following directory on each Harvester installation server: <NFA_install_path>\Netflow\datafiles\ReaperWork.
   2. Verify that the ReaperWork directory contains valid Reaper files--that is, .rpr files that are larger than 0 KB in size.

      Many of the rpr.cmp files are removed at 15-minute intervals.

5. If you do not find valid rpr.cmp files, perform the following troubleshooting tasks:
   • Verify that the Reaper service is running, as described in Service Management.
   • Review the Reaper log files (RealtimeReaperErrors<yyyy-mm-dd>.log files) in the <NFA_install_path>\NetFlow\Logs directory.

   The Reaper files are processed and picked up at 15-minute intervals.

6. If multiple sets of rpr files collect in the ReaperWork directory, review the reaper_logging_flags table under the harvester database.