Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Question regarding Routing Neighbor fix on 2020.2.5 RC

I saw that you are the guy for 2020.2.5 question. Do you have additional information on the various fixed issues in this release?

I was curious what problem that the following fix resolved. We are seeing some issues with two nodes on the BGP routing resources.

Case 548902

Routing neighbor poller issues were addressed.

Find more posts tagged with

Accepted answers

aLTeReGo

The symptom was routing neighbor status showed as not available even though it is connected for certain IPs.

This was broken with a change introduced in the NPM 2019.4 release. If the HEX string format of the polled neighbor IP address did not contain characters A-F, then it was converted to the wrong IP address.

All comments

aLTeReGo

The release notes links are located in the customer portal

IPAM: https://www.solarwinds.com/documentation/kbloader.aspx?kb=IPAM_2020-2-5_release_notes

NTA: https://www.solarwinds.com/documentation/kbloader.aspx?kb=NTA_2020-2-5_release_notes

NCM: https://www.solarwinds.com/documentation/kbloader.aspx?kb=NCM_2020-2-5_release_notes

NPM: https://www.solarwinds.com/documentation/kbloader.aspx?kb=NPM_2020-2-5_release_notes

SAM: https://www.solarwinds.com/documentation/kbloader.aspx?kb=SAM_2020-2-5_release_notes

Orion Platform: Orion Platform 2020.2.5 Release Notes (solarwinds.com)

bharris1

Thanks for all of the Release Notes, but that is where I saw that line in the fixed issues. Do you have any info on what the actual problem is for neighbor poller issues than what it says in the release notes? What problem was addressed?

aLTeReGo

The symptom was routing neighbor status showed as not available even though it is connected for certain IPs.

bharris1

Thanks! I wanted to see if this fixed the issue we are seeing with a couple of our nodes, but it doesn't seem to describe our issue.