Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Unable to perform discovery from Additional poller because cannot resolve hostname of the primary server

Unable to perform discovery from Additional poller because cannot resolve hostname of the primary server

Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 21 Votes: 0 Revisions: 6

Overview

Unable to perform a discovery on Additional poller because you cannot resolve the hostname of the primary server.

Environment

All NPM versions

Resolution

  1. Ping both the hostname and IP address of your primary Orion server from the Additional Polling Engine server.
  2. Ensure that all the required ports are open and Windows Firewall are not blocking to and from the Additional Polling Engine and primary Orion server.
  3. Navigate to the hosts file on the Additional Polling Engine at \Windows\System32\drivers\etc.
  4. Open the hosts file in a text editor.
  5. Add the IP address and hostname of your primary Orion server, as indicated in the comments within the hosts file. 
Last modified

Tags

Classifications

Public