Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Remove orphaned standby High Availability servers

Remove orphaned standby High Availability servers

Updated: June 7, 2017

Overview

This article provides information and steps to resolve the issue when the NPM server High Availability (HA) Deployment Summary status shows as down with no obvious way to remove the server. The steps also resolve issues with inconsistencies in HA tables. 

 

 

Environment

NPM 12.0.1 and later

 

Cause 

The issues are caused by orphaned HA servers that can occur as a result of an incomplete cleanup of the SolarWinds Orion database.

Resolution

To resolve the issue, clean up HA tables.

  1. If the orphaned server is a part of a pool, delete the pool.
  2. Stop the High Availability service on the orphaned server.
  3. In the following code, provide the orphaned server hostname instead of ServerHostname, and run the script in SQL Management Studio or in the Database Manager:

    /****** Script for deleting obsolete pool members ******/

    DECLARE @HostnameToClear nvarchar(max)
    SET @HostnameToClear = 'ServerHostname' /*Update to the hostname of cleaned server*/
    DELETE FROM OrionServers WHERE HostName = @HostnameToClear
    DELETE FROM HA_PoolMembers WHERE HostName NOT IN (SELECT HostName FROM OrionServers)
    DELETE FROM HA_ResourcesInstances WHERE PoolMemberId NOT IN (SELECT PoolMemberId FROM HA_PoolMembers)
    DELETE FROM HA_FacilitiesInstances WHERE (RefId like '%' + @HostnameToClear + '%')
    DELETE FROM HA_PoolMemberInterfacesInfo WHERE PoolMemberId NOT IN (SELECT PoolMemberId FROM HA_PoolMembers)

    The script deletes references to the orphaned server from the database.

  4. If you want to continue using the server as a High Availability server, run the Configuration wizard on the server. The Configuration wizard provides information about the server into the OrionServers table.

You cannot see the orphaned server in HA any more, and all inconsistencies are resolved.

 

 

 

Last modified
03:02, 7 Jun 2017

Tags

Classifications

Public