Network Management

Duplex mismatch Alert on an Unmanaged Node

This article explains what happens when you get a Duplex mismatch alert on an unmanaged node and how to stop the alert from being triggered.

First published date

10/23/2018 2:33 PM

Last published date

2/4/2022 11:14 PM

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. 

Product section

Orion Platform

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):

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.
 

  • 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)