I can say we've had nothing but pain in trying to get all the context-mapping stuff recognized by pretty much every tool we use. Because of how Cisco implemented this, even some of our inventory apps are confused and think we have 3x more Nexus chassis than we actually do because in their logic, each context-mapped VRF is a separate device.
IMHO, I -hate- the way Cisco has "updated" SNMP on the Nexus platform.
One workaround we've had to use is to use DNS names per L3 interface, so that we can refer to the vrf/device as say 'Nexus1_mgmt0.foo.com'(which is part of the 'management' vrf) & 'Nexus1_eth1-1.foo.com'(which is part of the 'vrf1' vrf). This way applications think of them as separate devices due to the hostname/IP differences.
-Chris
On 7/24/13 1:29 PM, Darius Seroka wrote:
Hi Rob,
I posted a similar comment a few weeks/months back but my problem was with c6500's. Indeed it was the way cisco describes the vrf's so only thing that can be done is getting them to do their oid's more uniformly across their product range. I was not able to open a support request with the c6500s so dont have any tickets to refer to.
Darius
-- Regards, Darius Jan Seroka dariusjs@gmail.com mailto:dariusjs@gmail.com
On Wed, Jul 24, 2013 at 12:33 PM, Rob VanHooren <rob_vanhooren@mac.com mailto:rob_vanhooren@mac.com> wrote:
it appears that (non-global) VRFs (esp. wrt. RIB OIDs) somehow are seen by OBS only in my ASR 1ks and horde of c3750x. comparing with a handful of v6.1 Nexii 7k (and their vdc's), along with some archaic-but-still-v15 c3560s, the returned set is null. q1) need for the ugliness of snmp context mapping per vrf? q2) if so, is OBS prepared to iterate over the multiple communities per device? curious, R. _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium