Cannnot connect to multicast on 7600 router - while other connections can

[tiki_turtle]

Hello everyone. I have a 7613 / Sup720 router that has at least 30 multicast connections successfully streaming data via pim sparse-mode across different interfaces toclients. It's a cookie cutter configuration for each client basically.

However, on this particular client once PIM is enabled on his interface I can only see him as PIM neighbor and if he tries to make a connection I don't even see a (*,G). I thought that maybe it's an ACL problem on his side so I added and igmp static statement on his interface to just forward the packets...I checked the mroute table for the feed - and all I saw was the other 15 clients currently on it subscribing. I then replaced the static statement with a join-group statement thinking it may jump start the connection...still nothing in my mroute table. I switched to dense-mode and voila - I see a (*,G)...and a (S,G) too (since we run sparse-mode natively). However, once I switch back...I don't see any feeds being streamed....anything I could be looking for? The client is running sparse-mode and has the rp information for our stream...but I guess that doesn't still explain why I cannot see a join when I add a 'static-group command to their interface. Thanks in advance for the help

[Giuseppe Larosa]

Hello Amin,

please provide

sh ip rpf source-ip-address

sh ip pim int typex/y

where typex/y is interface to troubled customer

sh run int typex/y

sh ip pim rp mapping

and what is the G group that the customer should join

Hope to help

Giuseppe

[tiki_turtle]

Thanks Guiseppe

R1#sh ip rpf 142.201.219.10

RPF information for ? (142.201.219.10)

RPF interface: Vlan2013

RPF neighbor: ? (142.201.52.229)

RPF route/mask: 142.201.219.0/24

RPF type: unicast (eigrp 5)

RPF recursion count: 0

Doing distance-preferred lookups across tables

========================================

R1#sh ip pim int g12/17

Address Interface Ver/ Nbr Query DR DR

Mode Count Intvl Prior

142.201.179.209 GigabitEthernet12/17 v2/S * 1 30 1 142.201.179.210

=====================================

interface GigabitEthernet12/17

description Client1

ip address 142.201.179.209 255.255.255.252

ip access-group acl_in in

ip nat outside

ip flow ingress

ip pim bsr-border

ip pim sparse-mode

ip multicast boundary yt_mcast_out

speed 100

duplex full

wrr-queue queue-limit 10 70 15

wrr-queue random-detect min-threshold 1 80 100 100 100 100 100 100 100

wrr-queue random-detect min-threshold 2 40 70 100 100 100 100 100 100

wrr-queue random-detect min-threshold 3 40 95 100 100 100 100 100 100

wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100

wrr-queue random-detect max-threshold 3 95 100 100 100 100 100 100 100

wrr-queue cos-map 1 1 1

wrr-queue cos-map 2 1 0

wrr-queue cos-map 2 2 2

wrr-queue cos-map 3 1 4

wrr-queue cos-map 3 2 3 6 7

no cdp enable

end

=========================================

R1#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s) 233.102.209.0/25

RP 142.201.52.1 (?), v2v1

Info source: 142.201.52.1 (?), elected via Auto-RP

Uptime: 5d19h, expires: 00:02:40

Group(s) 233.102.209.128/25

RP 142.201.52.45 (?), v2v1

Info source: 142.201.52.45 (?), elected via Auto-RP

Uptime: 16w5d, expires: 00:02:34

Group(s) 239.0.0.0/24

RP 142.201.52.1 (?), v2v1

Info source: 142.201.52.1 (?), elected via Auto-RP

Uptime: 5d19h, expires: 00:02:41

Group(s) 239.142.1.0/24

RP 142.201.52.1 (?), v2v1

Info source: 142.201.52.1 (?), elected via Auto-RP

Uptime: 5d19h, expires: 00:02:41

Group(s) 239.142.2.0/24

RP 142.201.52.45 (?), v2v1

Info source: 142.201.52.45 (?), elected via Auto-RP

Uptime: 16w5d, expires: 00:02:36

Group(s) 239.142.3.0/24

RP 142.201.52.1 (?), v2v1

Info source: 142.201.52.1 (?), elected via Auto-RP

Uptime: 5d19h, expires: 00:02:41

Group(s) 239.142.20.0/24

RP 142.201.52.1 (?), v2v1

Info source: 142.201.52.1 (?), elected via Auto-RP

Uptime: 5d19h, expires: 00:02:42

Acl: mcc_mcast_groups, Static-Override

RP: 142.201.52.45 (?)

Acl: activ_chi_mcast_groups, Static-Override

RP: 65.175.24.150 (?)

Acl: activ_ny_mcast_groups, Static-Override

RP: 65.175.24.22 (?)

Acl: nasdaq_mcast_groups, Static-Override

RP: 198.140.52.1 (?)

==================================

142.201.178.202, 239.142.2.1), 00:02:30/00:00:59, flags: T

Incoming interface: GigabitEthernet12/24, RPF nbr 0.0.0.0, RPF-MFD

Outgoing interface list:

GigabitEthernet12/48, Forward/Sparse, 00:02:30/00:03:17, H

GigabitEthernet13/27, Forward/Sparse, 00:02:30/00:00:29, H

GigabitEthernet1/5, Forward/Sparse, 00:02:30/00:00:29, H

GigabitEthernet13/24, Forward/Sparse, 00:02:30/00:02:34, H

GigabitEthernet12/7, Forward/Sparse, 00:02:30/00:00:29, H

GigabitEthernet12/47, Forward/Sparse, 00:02:30/00:00:29, H

There are more clients Guiseppe - but here are the ones that are connected...

Thanks very much

[Giuseppe Larosa]

Hello Amin,

this line may have an effect:

ip multicast boundary yt_mcast_out

see

http://www.cisco.com/en/US/docs/ios/ipmulti/command/reference/imc_03.html#wp1029655

what is the config of ACL yt_mcast_out ?

Hope to help

Giuseppe