I think you have to check RPF on R4. FE link is probably what is
causing RPF failure.
On Sat, Jun 12, 2010 at 4:33 PM, Raghav Bhargava
<raghavbhargava12_at_gmail.com> wrote:
> Hi Experts,
>
> Below is the output of one my router in Lab:
>
> R4#show ip pim interface count | b Address
> Address Interface FS Mpackets In/Out
> 10.1.34.4 Serial0/0.43 * 68/0
> 10.1.45.4 Serial0/1 * 0/0
> 4.4.4.4 Loopback0 * 0/0
>
> ***************************
>
> (2.2.2.2, 224.1.1.1), 00:01:33/00:01:26, flags: L
> Incoming interface: Null, RPF nbr 10.1.100.3
> Outgoing interface list:
> Serial0/0.43, Forward/Dense, 00:01:35/00:00:00
> Serial0/1, Forward/Dense, 00:01:35/00:00:00
> Loopback0, Forward/Dense, 00:01:35/00:00:00
>
> The topology is:
> _____ fe link___
> | |
> R2------R1- serial---R3--serial link----R4---- serial--R5------R6
>
> My source is R2 and all the other routers join the group 224.1.1.1
>
> Now the problem is that R4 is receiving the mcast packets from 101.34.3(R3)
> but it is not forwarding them out via serial0/1 to R5. Although in the
> mroute table i can see the outgoing interface. I have checked the
> configuration's and they look good to me. I am not able to identify what is
> prompting R4 not to send the mcast packets out via serial 0/1.
>
> I have checked the RPF for the source i.e R2 on R5 and my RPF is good. Did
> mtrace also and that also looks good.
>
> Please advise.
>
> --
> Warm Regards
> Raghav
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Sat Jun 12 2010 - 16:55:21 ART
This archive was generated by hypermail 2.2.0 : Sun Aug 01 2010 - 09:11:37 ART