Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

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: 868 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