Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Additional Polling Engine and the web console > Configure an Additional Polling Engine

Configure an Additional Polling Engine

Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Feb 02, 2017

Views: 67 Votes: 0 Revisions: 2

Configuration typically occurs after an initial installation, but it may also be required when a non-standard configuration change is made or when a module is added to your Additional Polling Engine. In general, the steps to configure an Additional Polling Engine are the same as those required to configure a primary SolarWinds UDT polling engine, with the following additional considerations:

  • If you are using custom properties to monitor your network, you must copy related schema (*.schema) and configuration (*.config and *.cfg) files from your primary Server to the server hosting your Additional Polling Engine.

    By default, *.schema files are located on your primary SolarWinds server in C:\Program Files\SolarWinds\Orion\Schemas\; *.config and *.cfg files are located in C:\Program Files\SolarWinds\Orion\.

  • If you are using any basic alerts to monitor your network, you must make copies of all basic alert definitions in your Orion Platform database, and then assign the copies to your Additional Polling Engine.
  • If you want to use any Orion Platform products for monitoring or managing any devices polled with an Additional Polling Engine, you must install the Additional Polling Engine version of the module you want to use on the server hosting your Additional Polling Engine.

For more information about optimizing an additional polling engine configuration, see Manage SolarWinds UDT polling engines.

During configuration, the Additional Polling Engine shutdowns temporarily with the result that if you are actively polling, you may lose some data. SolarWinds recommends configuring polling engines during off-peak hours.

Change polling engine node assignments

Reassigning nodes to new polling engines may be required in the following situations:

  • Moving or renaming your UDT server
  • Merging two or more Servers

If these or any other conditions present the need for reassignment, complete the following procedure to reassign nodes to a new polling engine.

  1. Log in to the Orion Web Console as an administrator.
  2. Click Settings in the top right of the Web Console.
  3. Click Manage Nodes in the Node & Group Management grouping of the Orion Website Administration page.
  4. Locate the node to manage using either of the following methods:

    • Use the search tool above the node list to search your Orion Platform database for the device you want to manage.
    • Select a Group by criteria, and then click the appropriate group including the node to manage.
  5. Check the node for which you want to change the polling engine.
  6. Click More Actions, and then click Change Polling Engine.
  7. Select the new polling engine, and then click Change polling engine.

The current number of Assigned Objects is listed for each available polling engine. This number is updated with each automatic polling engine synchronization. Updates to the Assigned Objects count can only be completed for polling engines that are operationally up.

Last modified
21:50, 1 Feb 2017