Network Management

Additional polling engine/HA server cannot connect to the main polling engine

When you install an additional polling engine and cannot connect it to the main polling engine in a different domain, use FQDN to enable hostname resolution.

First published date

3/18/2019 7:06 PM

Last published date

3/1/2022 9:31 PM

Overview

When you install an additional polling engine and cannot connect it to the main polling engine in a different domain, use FQDN to enable hostname resolution.

Product section

Orion Platform

Cause

The main polling engine and the additional polling engine are located on different domains so hostname resolution is not working. 

Resolution

Make sure that all required ports are open and that you have excluded required ports and folders from antivirus protection. (see Files and directories to exclude from antivirus scanning for Orion Platform products).

Use the fully qualified domain name (FQDN).

  1. Check and confirm both polling engines are in the same time zone and that the times are synchronized.
  2. Add an entry to the hosts files on the primary polling engine and on the additional polling engine so that they are able to communicate via the hostname. (See the Resolution for Additional polling engines are unable to connect to the SolarWinds server.)
  3. Add a manual record in the DNS at a later stage.
  4. User a Native Orion user instead of Windows