Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Changing the server name now results to multiple primary pollers

Changing the server name now results to multiple primary pollers

Created by Leif Amland, last modified by Rodim Suarez on Jun 23, 2016

Views: 843 Votes: 0 Revisions: 3

Updated

Overview

If you change the name of your Orion server after an upgrade, you will notice multiple primary polling engines in the Engines table. They need to be cleared out and the nodes reassigned to the correct polling engine.

Environment

  • NPM 11.x
  • NPM 12.x

Cause 

Changing the name of a server during the upgrade caused multiple entries in the Engines table to be incorrect.

Resolution

  1. Stop all Orion Services using the Orion Service Manager.
  2. Open the Database Manager and load the default server.
  3. Navigate to the Engines table, right click and query table. At the top center window hit Execute.
  4. If you only have one Primary Polling Engine, there should only be one entry here.
  5. Enable Table editing at the top and remove the false entries.
  6. Start all Orion Services.

If you need to change the polling engine for the nodes, please see the following articles:

How to change polling engines without a SQL query

How to change polling engines using Database Manager

 

Last modified

Tags

Classifications

Public