Just a follow-up.
It seems, beside of the fact that RPF seems not failing, that sometime the
mcast flow
is reached by another vlan and we get a kernel mismatch.
Thanks to David for the help.
Tks
___
juniper-nsp m
gt; Wrong incoming interface notifications = Number of times that the upstream
> interface was not available
>
> It doesn't sound as an RPF fail counter, isn't it ?
>
> Tks
>
> > From: nkham...@juniper.net
> > To: dim0...@hotmail.com
> > CC: juniper-n
et
> To: dim0...@hotmail.com
> CC: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Multicast flow with "Wrong incoming interface
> notifications" counter incrementing
> Date: Mon, 14 Jan 2013 17:14:42 +
>
> Iif mismatch means the multicast traffic rece
gt; CC: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Multicast flow with "Wrong incoming interface
> notifications" counter incrementing
> Date: Mon, 14 Jan 2013 17:14:42 +
>
> Iif mismatch means the multicast traffic received for this (S,G) has a
> different incoming
com
> CC: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Multicast flow with "Wrong incoming interface
> notifications" counter incrementing
> Date: Mon, 14 Jan 2013 17:14:42 +
>
> Iif mismatch means the multicast traffic received for this (S,G) has a
> different inco
Iif mismatch means the multicast traffic received for this (S,G) has a
different incoming interface than the one we programmed in the PFE (based on
RPF check).
Traffic would get discarded in this case and not forwarded. However, a
notification is sent to RPD/PIM on the RE to check if the we ne
Hi
What does means incrementing counter
“Wrong incoming interface notifications” in the following command ?
Is the following flow forwarded, as expected,
towards the receiver ?
# run show multicast route group
224.12.22.1 extensive
Instance: master Family: INET
Group: 224.12.22
7 matches
Mail list logo
