Routing
Reply
Contributor
GeorgeKamel82
Posts: 20
Registered: ‎07-31-2011
0

Multicast rec is not geting any traffic

I am having the below  network set up with the three routers (routers are logical on an MX80 chassis) running pim protocol , R2 is acting as the RP and I have cnofigured static RP on R4 and R3 pointing  to the lo0 of R2 , I have also configured SAP and IGMP so it can act as a last hop router on R3. when I try to ping from R2 the group 224.1.1.1 I can see (S,G) on R4 (I know that sap effects the whole chassis not only the router on which I have configured it) but not on R3 . Not sure why ?

 

 

R2------R4-----------R3

 

 



set logical-systems R2 protocols pim family inet6 disable
set logical-systems R2 protocols pim traceoptions file Multi_R2
set logical-systems R2 protocols pim traceoptions flag packets detail
set logical-systems R2 protocols pim rp local address 172.27.255.2
set logical-systems R2 protocols pim interface all

 

 

set logical-systems R4 protocols pim family inet6 disable
set logical-systems R4 protocols pim rp static address 172.27.255.2
set logical-systems R4 protocols pim interface all


set logical-systems R3 protocols pim family inet6 disable
set logical-systems R3 protocols pim rp static address 172.27.255.2
set logical-systems R3 protocols pim interface all
set logical-systems R3 protocols sap listen 224.1.1.1
set logical-systems R3 protocols igmp interface ge-1/0/4.522 static group 224.1.1.1 (no real rec is connected to this interface but it is up )

 

 

 


xxx@xxx-1:R2> ping 224.1.1.1 bypass-routing  ttl 10
PING 224.1.1.1 (224.1.1.1): 56 data bytes
64 bytes from 172.27.0.6: icmp_seq=176 ttl=64 time=0.421 ms
64 bytes from 172.27.0.6: icmp_seq=177 ttl=64 time=0.423 ms
64 bytes from 172.27.0.6: icmp_seq=178 ttl=64 time=0.488 ms
64 bytes from 172.27.0.6: icmp_seq=179 ttl=64 time=0.431 ms
64 bytes from 172.27.0.6: icmp_seq=180 ttl=64 time=0.418 ms

 

 

 


xxx@xxx-1:R3> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Group: 224.1.1.1
Source: *
RP: 172.27.255.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/1/4.34

Group: 224.2.127.254
Source: *
RP: 172.27.255.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/1/4.34

Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

xxx@xxx-1:R3> show multicast usage

xxx@xxx-1:R3>

 

 

 

 


xxx@xxx-1:R4> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Group: 224.1.1.1
Source: *
RP: 172.27.255.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/0/4.42

Group: 224.1.1.1
Source: 172.27.0.5
Flags: sparse,spt
Upstream interface: ge-1/0/4.42

Group: 224.2.127.254
Source: *
RP: 172.27.255.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/0/4.42

Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard


xxx@xxx-1:R4> show multicast usage
Group Sources Packets Bytes
224.1.1.1 1 60 5040


Prefix /len Groups Packets Bytes
172.27.0.5 /32 1 60 5040

xxx@xxx-1:R4>

Contributor
GeorgeKamel82
Posts: 20
Registered: ‎07-31-2011
0

Re: Multicast rec is not geting any traffic

Hello guys , no body have have a clue he does not have to be right we can discuss it and reach a resolution .together

Juniper Employee
jstar
Posts: 22
Registered: ‎04-28-2008
0

Re: Multicast rec is not geting any traffic

1. Can you check if traffic is going out via ge-1/0/4.42 in R4
( do rapid ping and see interface statistics)
2. Try to keep igmp or SAP one at a time and see how behavoir changes
( to isolate what is causing issue)
3. Please provide "show multicast route group 224.1.1.1 extesive" and "show pim join extensive"
from both r3 and r4.

 

- Arun

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.