Frr: Missing IPv6 peers in BGPd SNMP output

Created on 1 Jun 2018  路  13Comments  路  Source: FRRouting/frr

I'm using the upstream BGP4-MIB but only get v4 peers.

Also the S/AFI information is missing, they dont say what kind of peer it is (should be v4.unicast etc)

Are we missing the support or is it the wrong MIB?

enhancement

Most helpful comment

I'd be interested in trying to get the CISCO-BGP-MIBv2 implented instead of the current BGP4-MIB, which would provide all these features. Of course I would keep the current MIB to stay backwards-compatible.

Does anyone have some objections against using that specific MIB? The 'officially revised' IETF BGP-MIB is dead and in draft since years, so AFAIK the Cisco MIB is kinda common when talking about SNMP monitoring solutions.

Happy to hear other opinions on that specific topic.

All 13 comments

Adding to Feature Request Page

I'd be interested in trying to get the CISCO-BGP-MIBv2 implented instead of the current BGP4-MIB, which would provide all these features. Of course I would keep the current MIB to stay backwards-compatible.

Does anyone have some objections against using that specific MIB? The 'officially revised' IETF BGP-MIB is dead and in draft since years, so AFAIK the Cisco MIB is kinda common when talking about SNMP monitoring solutions.

Happy to hear other opinions on that specific topic.

I think the CISCO-BGP-MIBv2 is a good choice. It's widely used already and supports all the objects we'd want.

I see no reason to not pick something people want and work towards that implementation.

Yes. It's a pity that the IETF BGP MIB effort got stuck. I'll try to contact the (former) authors and point them here.

@sleinen Thanks for the comment. There's an interesting mailing list post from 2017 on gt.nsp.juniper, which can be found here: https://lists.gt.net/nsp/juniper/61006

Jeff Haas, the author of the IETF draft for that MIB, says some interesting things about the development/process that was involved. The most critical statement is probably:

Note that the draft is long expired. It was impossible to get vendors to want to implement it.聽

Out of curiosity: I've actually started working on getting the CISCO-BGP-MIBv2 (IMHO the most implemented MIB in other toolsets) integrated into FRR. Do you also think this is probably our best bet or would you have any other preferences?

I'd say the use of the CISCO-BGP-MIBv2 MIB would be fine, its unfortunate that the IETF RFC didn't come of the ground but its good to stick with what has been widely implemented.

Does this new MIB support also solve getting information from BGP peers within a VRF?

Currently I am unable to get this information, by walking the SNMP tree I do not get information from a VRF.

Any updates on this? We also only see IPv4 Peers by using BGP4-MIB.

Hi, still no news?

Any updates on this? I also can't see it listed on the feature request page as @donaldsharp posted 18 months ago.

Still no update? :/

any update please @donaldsharp

Was this page helpful?
0 / 5 - 0 ratings