Proper shutdown sequence for Network Flow Analysis

Document ID : KB000056908
Last Modified Date : 14/02/2018
Show Technical Document Details


What is the proper shutdown sequence for a scheduled/intentional power down of an entire distributed Network Flow Analysis system?


Minimum Safe Shutdown Stop the MySQL and CA/NetQoS services on all boxes and power down in this order: harvester, master console, and DSAs.

Cleanest Safe Shutdown:

On the NFA harvesters, stop the harvester service only.  Make sure the Reaper service is still running.  Let the reaper process the rest of the files in <Install path>\Netflow\datafiles\ReaperInput.  Once this directory is empty, wait for <Install path>\Netflow\datafiles\ReaperWork to empty as well. Make sure there are no .rpr files in <Install path>\netflow\datafiles\NFMInput.  If there are, wait until they are processed. Stop MySQL and all other CA/NetQoS services on harvesters.  You can now power them down.  

On NFA console, make sure all of the sub-directories of <Install path>\reporter\datashare\data\<IP-of-DSA> are empty in case of a 3-tier system that includes the DSA.  If not, wait a minute or so until they are processed. Stop the MySQL service and all CA/NetQoS services, and power down.

If the system contains the NFA DSAs, stop the MySQL and CA/NetQoS services and power down.