As soon as I'll experience the issue again, I'll do... Tks
> From: david....@orange.com > To: dim0...@hotmail.com; nkham...@juniper.net > CC: juniper-nsp@puck.nether.net > Date: Tue, 15 Jan 2013 09:19:47 +0100 > Subject: RE: [j-nsp] Multicast flow with "Wrong incoming interface > notifications" counter incrementing > > Could you send us the traces of "show multicast stat" 2 times separated with > 10 sec. > > Thank you > > > > > David Roy > IP/MPLS Support engineer - Orange France > Ph. +33 2 99 87 64 72 - Mob. +33 6 85 52 22 13 > david....@orange.com > > JNCIE-M&T/SP #703 - JNCIE-ENT #305 - JNCIP-SEC > > -----Message d'origine----- > De : juniper-nsp-boun...@puck.nether.net > [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Riccardo S > Envoyé : mardi 15 janvier 2013 09:14 > À : nkham...@juniper.net > Cc : juniper-nsp@puck.nether.net > Objet : Re: [j-nsp] Multicast flow with "Wrong incoming interface > notifications" counter incrementing > > > Having also a look to Juniper documentation says: > > 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-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 +0000 > > > > 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 need to > > change the iif on this (S,G) to a new iif (for e.g. if this leads to > > RPT to SPT cutover or if there is a change in the iif due to RPF > > interface change) > > > > If the counter increase consistently, then most likely you are not > > forwarding on that (S,G) if 100% of the incoming traffic on this (S,G) get > > discarded with iif mismatch. Alternately, you might be getting same (S,G) > > traffic on 2 different iifs and in this case one coming over correct iif > > gets forwarded and one over wrong iif gets discarded with iif mismatch > > counted against that (S,G). > > > > Thanks, > > Nilesh. > > > > -------------------------------- > > Sent from my mobile device > > > > On Jan 14, 2013, at 8:14 AM, "Riccardo S" <dim0...@hotmail.com> wrote: > > > > > > > > > > > > > > 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.1 > > > > > > > > > Source: 1.1.1.1/32 > > > > > > > > > Upstream interface: vlan.1 > > > > > > > > > Downstream interface list: > > > > > > vlan.100 > > > > > > > > > Session description: Unknown > > > > > > > > > Statistics: 3 kBps, 30 pps, 43340 packets > > > > > > > > > Next-hop ID: 131071 > > > > > > > > > Upstream protocol: PIM > > > > > > > > > Route state: Active > > > > > > > > > Forwarding state: Forwarding > > > > > > > > > Cache lifetime/timeout: 360 seconds > > > > > > > > > Wrong incoming interface notifications: 6960 > > > > > > > > > Uptime: 00:36:36 > > > > > > > > > > > > After 10 seconds: > > > > > > > > > > > > # run show multicast route group > > > 224.12.22.1 extensive > > > > > > Instance: master Family: INET > > > > > > > > > > > > Group: 224.12.22.1 > > > > > > > > > Source: 1.1.1.1/32 > > > > > > > > > Upstream interface: vlan.1 > > > > > > > > > Downstream interface list: > > > > > > vlan.100 > > > > > > > > > Session description: Unknown > > > > > > > > > Statistics: 2 kBps, 30 pps, 43491 packets > > > > > > > > > Next-hop ID: 131071 > > > > > > > > > Upstream protocol: PIM > > > > > > > > > Route state: Active > > > > > > > > > Forwarding state: Forwarding > > > > > > > > > Cache lifetime/timeout: 360 seconds > > > > > > > > > Wrong incoming interface notifications: 6974 > > > > > > > > > Uptime: 00:36:41 > > > Tks > > > > > > > > > > > > _______________________________________________ > > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete > altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages > that have been modified, changed or falsified. > Thank you. > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp