BGP neigbhor visible even if it`s not configured on device or visible in SNMP

Hello malisek 

Yes, this is a known thing on SolarWinds. It has something to do with how they remove the neighbors on the end device - but I am not an expert in that area, hence cant comment on the same.

To avoid this you will need to do 2 things:

1. Exclude BGP/OSPF Neighbors where Status is 'Not Available' from your Neighbor alerts - to avoid unwanted Neighbor alerts being sent out.

2. Clean them up occasionally in one shot - you will need to manually get rid of them from SolarWinds Database and this is how you do it.

Login into Database Manager from one of your SolarWinds pollers:

a. SELECT * FROM [dbo].[NPM_RoutingNeighbor] where IsDeleted='true' (this will list all neighbors that currently are in 'Not Available' status - what this means is it doesnt exist anymore).

b. DELETE FROM [dbo].[NPM_RoutingNeighbor] where IsDeleted='true' (this will help you in deleting them in one shot - but be very careful, one wrong/incorrect command on SolarWinds DB and lot of things can go wrong, hence you need to be very careful when you run DELETE commands on Database).

Hope this helps. 

Note: Point  2 is just a workaround to keep your SolarWinds environment intact, this is not a permanent fix.

__PRESENT

Hello,

Thank you, Point 2 works fine. I'm allway affraid to touch SQL DB this way so I created more specific query :

DELETE FROM [dbo].[NPM_RoutingNeighbor] WHERE [NodeID] = XXXX AND [NeighborID] = XXXX AND [IsDeleted] = 1  

 There were about 40 lines on 5-6 routers where we make a lot of routing changes. So I carefully deleted all this lines one by one to be sure that I did not make any harm to whole database.

 It is possible that all those records (and allarms finaly) were from old version of NPM , all these records were really old. I think that after update at least to 2024.x.x version are non existent BGP neighbors deleted correctly.  But we will check it further. 

I think i would be one of our maintenance procedures if  this non existent BGP neighbor occures again.

Thank you

thx, using this one too!