Network Management

Missing BGP and OSPF routing neighbors in Routing Neighbor resource view in NPM

This article describes how to determine missing routing neighbors for BGP and OSPF on the Routing Neighbors resource view. All routing neighbors are available when verified from the device via CLI or GUI.

First published date

11/13/2018 4:19 PM

Last published date

2/24/2026 4:40 PM

Overview

When monitoring routing neighbors in the SolarWinds platform, you may see the Routing Neighbors resource show no data when the device CLI and GUI is populated with OSPF and BGP routing neighbors. This article discusses how to troubleshoot such issues.

SolarWinds Platform Web Console view:

Device command line interface(CLI) 

image.png

 
 

Product section

Orion Platform

Cause

  1. Before BGP Neighbors can be shown on the Node Details page, the SolarWinds Platform has to assign BGP poller/s to the node. The Device will have to support the bgpVersion (OID: 1.3.6.1.2.1.15.1), by which system determines its support of BGP/OSPF routing neighbors collection.

  2. The SolarWinds Platform uses the following OIDs to poll for BGP/OSPF routing neighbors information:

    bgpPeerState1.3.6.1.2.1.15.3.1.2
    bgpPeerRemoteAddr1.3.6.1.2.1.15.3.1.7
    bgpPeerRemoteAs1.3.6.1.2.1.15.3.1.9
    ospfAdminStat1.3.6.1.2.1.14.1.2
    ospfNbrRtrId1.3.6.1.2.1.14.10.1.3
    ospfNbrIpAddr1.3.6.1.2.1.14.10.1.1
    ospfNbrState1.3.6.1.2.1.14.10.1.6
     
  3. Wrong SNMPv3 context

 

Resolution

Resolution 1
Using SolarWinds SNMP Walk: A new tool for collecting SNMP MIB walks, check and compare if the OIDs the SolarWinds Platform uses to poll for routing neighbor information are supported by your device.

Contact your device manufacturer and ensure the SNMP OIDs are supported.

Resolution 2
Check if the SNMPv3 context is correct and allows the device to share all the required OIDs.
Note: SolarWinds Platform does not support multiple contexts.