So I decided to actually test this, and it works perfectly:

I added this config to my XR box:

! snmp-server vrf internet context bgpcontext snmp-server community *** RO MANAGEMENT snmp-server context bgpcontext snmp-server community-map *** context bgpcontext !

And then added the device. This device is already being monitored, but in the global SNMP context, so I added the device again, but used the FQDN of the host, instead of just the hostname, so now I have two of the same device, one in the global context and one in the vrf context. I guess this is the only way to get a second community polled for the same device, unless there’s something that I’m missing?

In the routing tab for this duplicate device with the vrf context config, it show all the BGP sessions inside the vrf ‘internet’.

Perfecto!

This is a pretty big box with lots of ports and lots of sensors, so I don’t want to duplicate polling for the same device twice, so for the duplicated device, I’ve disabled all the MIBs, Poller Modules, Ports polling options and Discovery modules except for anything related to BGP. I did it on one device, and whew, that’s a lot of stuff to disable. Is it possible to save that particular device is a template, or perhaps duplicate the device and then rename it so I can save myself all the clicky-clicky or do I have to manually go in and disable everything I want to disable from every device in question?

Thanks!

On Jun 8, 2015, at 10:41 PM, Jason Lixfeld jason@lixfeld.ca wrote:

Hi,

I understand that the current BGP MIB doesn’t support VRF contexts for pulling BGP session info for sessions that exist inside a VRF. I have IOS XR boxes that house my vrf BGP sessions, and apparently there is an snmp-context command that has proven to be able to work around the MIB limitations.

My question is whether or not anyone within the Observium community has tried to do this. From what I gather, it requires a separate SNMP community on the IOS XR box to perform the context mapping, but that would seem to imply that one needs to duplicates the node in question in Observium with the new community.

I haven’t actually tried any of this yet... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium