Hi, On Mon, Oct 24, 2016 at 07:46:50AM +0000, Nigel Hendrickse wrote: > It turns out that the ifIndex value embedded in the Netflow data is not the > SNMP ifIndex (which our collector expects) but a 'dpidx' value which seems to > be a Cisco-proprietary value generated by the platform. Has anyone else > encountered this? Is there a tweak/workaround available to fix it?
No ASR920 here, but that sounds like a bug to me... all platforms I've
laid my hands on so far have exported SNMP ifIndex (and the netflow specs
might even document this as such).
"dpix" sounds like "the internal hardware port index" or such, which, if
there are strong reasons to make it different from the snmp ifIndex (there
could) should go through a mapping on export...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
signature.asc
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
