Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Additional polling engine/HA server cannot connect to the main polling engine

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

Created by Sean.Nyhan, last modified by Magdalena.Markova on Jun 13, 2018

Views: 372 Votes: 0 Revisions: 6

Updated: April 4, 2018


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.


  • Orion Platform products installed with a scalability engine (additional polling engine, additional web server or high availability)


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


Make sure that all required ports are open and that you have excluded required ports and folders from antivirus protection.

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.
  3. Add a manual record in the DNS at a later stage.




Suggested Tags:  APE, Additional poller to main poller connectivity issue, DNS, FQDN


A reason for rework or Feedback from Technical Content Review:



Last modified