[j-nsp] multicast questions

[Nilesh Khambal]

Do you know if Source is registered with the RP? SPT flag is set on (S,G) on
the RP so it must have but just in case check "show pim rps extensive" on
both source DR and RP. Does the SPT path from receiver DR to the Source DR
goes via RP or does it take an alternate path?

One more thing to check is, are there more than one PIM routers on the
receiver segments. Only the PIM DR on the segment would generate (S,G) join
towards the source. Check "show pim interface" for the receiver segment.

Also, check if Receiver DR can find rpf path towards the source DR to send
(S,G) join. Try "show multicast rpf <src DR IP>" on the receiver DR to check
this.

Thanks,
Nilesh.


On 4/19/10 5:02 PM, "snort bsd" <snortbsd at yahoo.com.au> wrote:

> Hi all:
> 
> I have an active multicast receiver looking for source 225.0.0.1:
> 
> -----------------------------------------------------
> user at hs3# run show pim join extensive
> Instance: PIM.master Family: INET
> 
> Group: 225.0.0.1
>     Source: *
>     RP: 10.100.3.4
>     Flags: sparse,rptree,wildcard
>     Upstream interface: so-0/1/0.0
>     Upstream neighbor: 10.100.2.10
>     Upstream state: Join to RP
>     Downstream neighbors:
>         Interface: fe-1/3/0.0
>             172.20.30.1 State: Join Flags: SRW  Timeout: Infinity
> 
>                                         <-------- Nothing here.
> 
> Instance: PIM.master Family: INET6
> ------------------------------------------------
> 
> from above data, it doesn't seem to find the source. but I took a look at RPS:
> 
> -----------------------------------------------------------
> user at RP# run show pim join extensive
> Instance: PIM.master Family: INET
> 
> Group: 225.0.0.1
>     Source: *
>     RP: 10.100.3.4
>     Flags: sparse,rptree,wildcard
>     Upstream interface: Local
>     Upstream neighbor: Local
>     Upstream state: Local RP
>     Downstream neighbors:
>         Interface: so-0/1/1.0
>             10.1000.2.9 State: Join Flags: SRW Timeout: 191
> 
> Group: 225.0.0.1
>     Source: 10.100.5.200
>     Flags: sparse,spt
>     Upstream interface: fe-0/0/2.0
>     Upstream neighbor: 10.100.4.18
>     Upstream state: Local RP, Join to Source
>     Keepalive timeout: 32               <----- No downstream neighbor
> 
> Instance: PIM.master Family: INET6
> -----------------------------------------------------
> 
> It seems that RP knows the source of group 225.0.0.1 but somehow the source
> and receiver just won't connect. Somehow RP doesn't work?
> 
> here is the RP config:
> 
> user at RR# show protocols pim
> rp {
>     bootstrap-priority 10;
>     local {
>         address 10.100.3.4;
>     }
> }
> interface fe-0/0/0.0 {
>     mode sparse;
> }
> interface fe-0/0/1.0 {
>     mode sparse;
> }
> interface fe-0/0/2.0 {
>     mode sparse;
> }
> interface fe-0/0/3.0 {
>     mode sparse;
> }
> interface so-0/1/0.100 {
>     mode sparse;
> }
> interface so-0/1/1.0 {
>     mode sparse;
> }
> 
> 
> any ideas?
> 
> 
> 
> 
> 
>       
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp