Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA Flow Storage Database/NTA Collector down after HA (High Availability) failover occurs

NTA Flow Storage Database/NTA Collector down after HA (High Availability) failover occurs

Updated February 14, 2017

Overview

The NTA Flow Storage Database and subsequently, the NTA Collector services go down after a successful HA (High Availability) failover occurs when the NTA Flow Storage Database resides on either the Primary Polling Engine or an Additional Polling Engine.

 

If the NTA Flow Storage Database resides on the Primary Polling Engine, this service failure occurs when the failover switches the active server from the Primary to the Secondary.  If the NTA Flow Storage Database resides on the Additional Polling Engine, the opposite conditions will apply.

Environment

All Orion High Availability environments with NTA

 

Cause 

This is caused by the normal functioning of HA (High Availability).  Thus, the migration of the NTA Flow Storage Database to a dedicated server as detailed below is required.

 

Resolution

Please use the links below to plan the migration or installation of the NTA Flow Storage Database on a dedicated server:

 

Last modified
20:30, 26 Mar 2017

Tags

Classifications

Public