[c-nsp] ASR920 Netflow ifIndex Value (dpidx)

[Nigel Hendrickse]

Hi,

TAC came back with:

>> Please note that this match interface input does NOT point to ifindex and we do NOT support SNMP MIBs in netflow. This input interface exported to the collector points to the
>> dpidx of the interface. Dpidx can be obtained using the command - sh platform hardware pp active interface all

Using 'match interface input' or 'match interface input snmp' in the router flow record configuration doesn't change anything - the 'dpidx'  value instead of SNMP ifIndex is exported in the netflow data for both options (confirmed via Wireshark captures). If anyone has come up with any solutions for this please give me a shout.

Thanks,
Nigel

-----Original Message-----
From: Gert Doering [mailto:gert at greenie.muc.de] 
Sent: Monday, 24 October 2016 10:18 AM
To: Nigel Hendrickse <nigel.hendrickse at paratustelco.com>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ASR920 Netflow ifIndex Value (dpidx)

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                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de