Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Some child nodes in Parent/Child Dependencies are not going into Unreachable State

Some child nodes in Parent/Child Dependencies are not going into Unreachable State

Created by Tiarnan Stacke, last modified by MindTouch on Jun 23, 2016

Views: 2,094 Votes: 0 Revisions: 3

Overview

Some child nodes in Dependencies are not going into Unreachable State. For nodes distributed across multiple polling engines, the nodes which are polled via an Additional Polling Engine show in a "Down" state instead of "Unreachable."

Environment

  • NPM 11.5
  • Multiple Polling Engines

Cause 

The cause of this can be a mismatch in the versions of the "Solarwinds Information Service v3" Service between the Main and Additional Polling Engine.

Resolution

Ensure that all of the same versions of the products are installed on the Main and Additional Polling Engine.

 

To check what versions are currently installed:

  1. RDP to the Main/Additional Polling Engine.
  2. Run > appwiz.cpl.
  3. Scroll down to "Solarwinds ...."
  4. Check the versions of the modules.
  5. If the versions do not match, download and install the relevant installers from the Customer Portal.
Last modified

Tags

Classifications

Public