[j-nsp] MS-DPC export flows have 0 as dest interface

[Luca Tosolini]

Jim,
in my experience, the destination interface ifIndex can be 0 in the
following cases:
- traffic dropped
- traffic destined locally
- multicast
Thanks,
Luca.


On Tue, 2010-08-10 at 16:06 -0700, Jim Devane wrote:
> RAS,
> 
> 10.0R2 
> I opened a case and we will see what happens. I have zero issue with moving to new code if it will solve the issue. This router doesn't do a whole lot (and even less without correct flow reporting)
> 
> Thanks,
> Jim
> 
> 
> -----Original Message-----
> From: Richard A Steenbergen [mailto:ras at e-gerbil.net] 
> Sent: Tuesday, August 10, 2010 4:04 PM
> To: Jim Devane
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] MS-DPC export flows have 0 as dest interface
> 
> On Tue, Aug 10, 2010 at 01:01:48PM -0700, Jim Devane wrote:
> > 
> > However, The Juniper is not reporting the dest interface and instead 
> > putting in a zero. This is confusing our flow collector (Peakflow SP) 
> > Arbor takes the dest intf and source interface both being zero as a 
> > drop. The traffic is not in fact being dropped, however.
> > 
> > Has anyone dealt with this particular or type of problem? I was trying 
> 
> What code are you running? We had a similar issue a while back, infact 
> we had a case open on it for over a year before it finally got fixed, 
> but I'm pretty sure our version of the issue has been fixed for a couple 
> years now.
>