Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Implement routing protocol monitoring in a bit more advanced way

Implement routing protocol monitoring in a bit more advanced way

BGP monitoring is currently done as node sensor monitoring which is not the way it should be.

First of all, we need to have possibility to select whether we would like to monitor BGP or not, irrespective of CPU, memory and buffer monitoring.

Second, we must be able to select whether to perform fault or performance monitoring on BGP sessions.

Last, but not at least, we must be able to enable/disable BGP sessions monitoring based on parameters like neighbor description, neighbor AS, neighbor IP address, VRF. Also, these parameters must be available as CIAs so we can set incident severity, priority and actions based on them.

Next step would be to implement OSPF and IS-IS monitoring.

Eventually, I would expect to have a separate section in Node monitoring settings screen (and default settings one as well) that enables/disables fault and/or performance monitoring on various routing protocols.

Routing protocol statuses should be organized in a separate tab in node form and we would also expect routing protocol performance tab in the node analysis pane.

Inventory table view with all routing protocol neighborships is also essential as well as respective monitoring table view and performance analysis view.

 

Best regards,

Vesselin.

3 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at a later stage. We expect the community to help prioritize the idea with comments and community support (votes/kudos)

 

Valued Contributor.. ThibaudA Valued Contributor..
Valued Contributor..

Hello,

I am really surprised to see that a network monitoring tool is not yet capable in 2019 of monitoring basic routing protocols like OSFP. In particular, the RFC OSPF V2 was released in April 1998. So 20 years after the publication of the RFC, NNM is not able to monitor basic protocols.
This feature is especially important for WAN networks.

What information do you need?
for the OSPF MIB, the OIDs to be monitored are:
ospfNbrIpAddr 1.3.6.6.1.1.2.1.1.14.10.1.1.1
ospfNbrState 1.3.6.6.1.1.2.1.1.14.10.10.1.6
or
ospfVirtNbrIpAddr 1.3.6.6.1.2.2.1.14.11.1.3
ospfVirtNbrState 1.3.6.6.1.1.2.1.1.14.11.1.5

Translated with www.DeepL.com/Translator

 

Acclaimed Contributor.. AndyKemp Acclaimed Contributor..
Acclaimed Contributor..

There was an extension that monitored protocols in an advanced manner (Route Analytics Management Engine or RAMS an OEM version of Packet Design's Route Explorer)  but it had a low adoption rate. Packet Design has subsequently been purchased by  Cienna and is part of their Blue Planet product. 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.