Implement routing protocol monitoring in a bit more advanced way

Idea ID 1677858

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.

12 Comments
Micro Focus Expert
Micro Focus Expert
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)

 

Commander Commander
Commander

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

 

Fleet Admiral Fleet Admiral
Fleet Admiral

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. 

I specially agree with this: "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."

turning BGP monitoring completely on or off is not an option. And filtering on BGP event message is not easy and does not scale.

I would like to have the possibility to create "BGP-Groups" with conditions, like Interface-Groups to monitor and fire or suppress events.

Any betther ideas?

Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

The design of Network Node Manager should be more advanced than just a fault monitoring only. We customized the BGP Monitoring with Custom Poller Configuration, but if you don't have any knowledge for the correct OID, it will be tedious as well. It would be helpful to enhance the more advanced capability rather than only fault monitoring like availability, Reach ability, component health, etc. Even the other products on the market, already able to get the information about complete routing route, routing protocol even VRF route. In NNMi, we still need to customize here and there to get this requirement done, and this is not only customization with simple click.

So, it would be very helpful to network admin to get more enriched view about the routing information.

Regards, Lenna

Commander Commander
Commander

I'm agree with you NSOC2 Daimler. NNMi suffers from a lack of network's functionality 

Cadet 3rd Class
Cadet 3rd Class

These are basic features must be adopted to provide advanced monitoring solution clients are expecting. We have had several queries around this especially for ISIS monitoring. Not sure why we lag so much to adopt advanced features unlike the competitors.

Commodore Commodore
Commodore

Hi Experts and Idea Team,

Please  support here to get more vote on this since customer requirement is to get few other protocols like OSPF, ISIS & CII on NNM UI with Inventory >> NodeSensor screen. 

Do we have supported method to expose please suggest or else please help to accept as idea.

Micro Focus Expert
Micro Focus Expert
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 this stage, and we expect the community to help prioritize the idea with comments and community support (votes/kudos).

Commodore Commodore
Commodore

Requested this about two years ago ...

https://community.microfocus.com/t5/NOM-Idea-Exchange/Implement-routing-protocol-monitoring-in-a-bit-more-advanced-way/idi-p/1677858

And I am pretty sure there is at least one more idea related to routing protocols monitoring ..

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.