Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Connection to NTA Flow Storage Database has been lost

Connection to NTA Flow Storage Database has been lost

Created by Sterling Elliott, last modified by Andy Ng on May 09, 2017

Views: 100 Votes: 1 Revisions: 5

Updated: June 30, 2016

Overview

This article describes the issue when after installing NTA 4.2, you lose connection to the Fastbit or flow storage database.

 

Environment

NTA version 4.2

For scenario #2 - VMWare ESXi 6.0; SQL 2014 SP2 build 12.0.5000.0

Cause 

#1: The NTA module on the main NPM server is different then the one on the Fastbit or Flow storage DB.

 

#2: Performance issue on SQL and/or FSDB

Exceptions "NetFlowPacketWorkflowManager - Error flushing data" found in NTA.BusinessLayer.log

Resolution

#1: Upgrade the NTA module on NPM server to 4.2 using the same installer.

 

#2: To fix exceptions in NTA.BusinessLayer.log

-  Upgrade SQL Server from 2014 SP2 build 12.0.5000.0 to 2014 SP2 CU4 build 12.0.5540.0

- Backup Orion database (as an insurance)

- Stop Netflow service

- Run " TRUNCATE table dbo.NetFlowFastBitStringHeap" command in SQL Management Studio against Orion database,

- Start Netflow service,

 

Thereafter, optimize SQL:

a. Index defragmentation - here

b. SQL server optimization - here

c. On VMWare ESXi 6.0, it is well know to have dysfunction impacting FastBit remote flow storage.  Ensure that ESXi600-201509201-UG: Updates esx-base (2124716) applied on host of FSDB - details here

 

 

Last modified
19:50, 8 May 2017

Tags

Classifications

Public