Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

Home > Success Center > Netflow Traffic Analyzer (NTA) > No data migrated when upgrading main and additional pollers to NTA 4.0

No data migrated when upgrading main and additional pollers to NTA 4.0

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 675 Votes: 0 Revisions: 8

Issue

After upgrading the main and additional pollers to NTA 4.0, user is unable to see them in his Orion Web Console after the upgrade. 

Cause

When upgrading main and additional pollers to NTA 4.0, the Configuration Wizard decides which poller will execute the migration. If the poller selected for executing the migration is not available (it has been turned off, removed or NTA has been uninstalled there), historical data are not migrated and you cannot see them in the Orion Web Console.

Note:

  • Check the NTA.BusinessLayer.log on all pollers to find out which one of them has been selected to do the migration. The NTA.BusinessLayer.log is usually located at
           %ProgramData%\Solarwinds\Logs\NTA\NTA.BusinessLayer.log.
  • If you find the message This receiver is not intended for the MS SQL To FastBit migration on all pollers, you need to specify an available poller which will perform the migration.

Resolution:

The first part of the resolution is all about migration.

  1. Find out which poller is responsible for the migration. To do so, execute the following SQL query:
    1. Start the SQL Management Studio and connect to your Orion SQL database server.
    2. Select your Orion SQL database and click New Query to execute the query in your Orion SQL database.
    3. Copy and paste the following code:
       

      select fe.* from FlowEngines fe

      join Engines e on e.ServerName = fe.ServerName

      where e.EngineID = (select Value from NetFlowGlobalSettings where KeyName = 'MigrateSqlFlows.MigratingEngine')

       
    4. Click Execute.

       
  2. Ensure that the returned ServerName poller is not used as NTA poller.

    Check the FlowCollectorKeepAlive column. If the time found there is older than 10 minutes, it means that the poller is not running any more. If the poller is not running and you do not want to use it any more, complete the following steps and remove the poller from the database.

    Warning: If the poller responsible for the migration is not running, but should be working, please contact support immediately. Completing the next steps deletes the poller from the Orion database and you would not be able to use it in NTA anymore.

  3. Ensure that the migration poller as NTA poller by removing the migration poller from the Orion database. 
    1. Start the SQL Management Studio and connect to your Orion SQL database server.
    2. Select your SQL database and click New Query to execute the query in the Orion SQL database.
    3. Copy and paste the following code:
       

      delete from FlowEngines where ServerName = (select ServerName from Engines where EngineID =

      (select Value from NetFlowGlobalSettings where KeyName = 'MigrateSqlFlows.MigratingEngine'))

      delete from NetFlowGlobalSettings where KeyName = 'MigrateSqlFlows.MigratingEngine'

       
    4. Click Execute.

  4. Log on to your main poller and start the Configuration Wizard in the SolarWinds Orion program folder.

  5. Select Database to reconfigure the database and select the option to migrate the database on the appropriate screen. The Configuration Wizard will automatically specify another poller to execute the migration.

  6. Complete the Configuration Wizard and find out which poller was selected to perform the migration by executing the following SQL Query:
     

    select fe.ServerName from FlowEngines fe

    join Engines e on e.ServerName = fe.ServerName

    where e.EngineID = (select Value from NetFlowGlobalSettings where KeyName = 'MigrateSqlFlows.MigratingEngine')

     

  7. To start the migration, log on to the selected migration poller and restart the NetFlow Service manually:

    1. Start the Orion Service Manager in the SolarWinds Orion program folder (SolarWinds Orion > Advanced Features > Orion Service Manager), select the SolarWinds NetFlow Service and click Restart.

  8. The migration starts as soon as the NetFlow Service is started. To check that the appropriate poller is responsible for the migration, go to the NTA.BusinessLayer.log on the poller (in %ProgramData%\Solarwinds\Logs\NTA\NTA.BusinessLayer.log) and check that the following message is available in the log: 

"This receiver is intended for the MS SQL To FastBit migration."

Applies to: NTA v4.0
Last modified
20:37, 22 Jun 2016

Tags

Classifications

Public