Documentation forSolarWinds Platform

Configure an Additional Polling Engine

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 NPM 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 SolarWinds Platform 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 SolarWinds Platform database, and then assign the copies to your Additional Polling Engine.
  • If you want to use any Orion modules 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 polling engines in the SolarWinds Platform.

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