Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Missing BGP and OSPF routing neighbors in Routing Neighbor resource view

Missing BGP and OSPF routing neighbors in Routing Neighbor resource view

Updated July 5, 2017

Overview

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.

Environment

NPM 11.0 or later 

Cause 

Orion is polling the routing neighbor information for BGP using OID 1.3.6.1.2.1.15.3.1.1 and OSPF using OID 1.3.6.1.2.1.14.10. The device is not returning values for BGP and OSPF OIDs.

Resolution

  1. Make sure that the Routing Neighbors interface is selected and monitored under List Resources.
  2. Check the Routing Neighbors table in Orion Database Manager and see if routing neighbors are found.
  3. Run SNMPWalk on the device.
  4. Perform a search using the BGP neighbor table OID 1.3.6.1.2.1.15.3.1.1 and OSPF neighbor table OID 1.3.6.1.2.1.14.10.
  5. Locate the missing routing neighbor IP address. 
  6. If it is not found, then this is an issue with the device not returning a value for the SNMP request. Consult your device manufacturer about the missing routing neighbors.
 

 

Last modified

Tags

Classifications

Public