Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Orion Platform > Duplex mismatch Alert on an Unmanaged Node

Duplex mismatch Alert on an Unmanaged Node

Updated September 21, 2017

Overview

This article explains what happens when you get a Duplex mismatch alert on an unmanaged node and how to remove the reason why the alert was triggered. 

Environment

  • Orion, all versions

Cause

Unmanaging nodes means we stop polling and running jobs on the node. This mean data in the database is no longer is updated for the node. 

The duplex mismatch alert looks for mismatching topology data. What happened was the topology changed on another node we are still polling. The alert was triggered because in our database the corresponding values for each interface were different. 

As an example and what can happen:

int x on node1  connected to int y on node2
int x.duplex  =  half    int y.duplex = half

Node1 goes unmanaged.

int y.duplex  changes to full

Duplex mismatch occurs in our database. An alert is triggered because of the following in the database:


int x on node1  connected to int y on node2
int x.duplex !=  int y.duplex 

Resolution

Option 1:

  • Mute alerts on the unmanaged node if you are on NPM12.1 or later.

 

Option 2 (if it's only one node):

  • delete  FROM [dbo].[TopologyConnections] where SourceNodeid = $nodeid or MappedNodeId = $nodeid
    • be sure to substitute both  $nodeid for the nodeid of the unmanaged node triggering the alert 

 

Option 3 (if it's on many nodes):

  • Warning - This will delete all Topology connections for all unmanaged nodes
  • delete  FROM [dbo].[TopologyConnections] where SourceNodeid in (select nodeid from nodesdata where unmanaged = 1)
  • delete  FROM [dbo].[TopologyConnections] where MappedNodeId in (select nodeid from nodesdata where unmanaged = 1)

 

 

Last modified

Tags

Classifications

Public