[j-nsp] PIM Sparse issues on EX4200

Mauritz Lewies mauritz at three6five.com
Wed Nov 21 13:27:54 EST 2012


Hi

I am having issues getting sparse mode PIM to work on a EX4200 that has been set up as the RP.

Here is the relevant Multicast config:
------------------------------------------------------------------------------------------
root at led-csw3> show configuration protocols 
igmp {
    interface all {
        version 2;
    }
}
pim {
    rp {
        local {
            address 10.172.12.14;
            group-ranges {
                224.0.0.0/4;
            }
        }
        static {
            address 10.172.12.14 {
                group-ranges {
                    224.0.0.0/4;
                }
            }
        }
    }
    interface all {
        mode dense;
    }
    interface me0.0 {
        disable;
    }
}
------------------------------------------------------------------------------------------

It's currently set to dense mode as this is the only way that clients are receiving traffic...

From the EX I can see that there are IGMP-snooping membership requests:
------------------------------------------------------------------------------------------
root at led-csw3> show igmp-snooping membership detail 
VLAN: IPTV_Clients Tag: 110 (Index: 2)
    Router interfaces:
        ge-0/0/0.0 dynamic Uptime: 02:04:32 timeout: 254
        ge-0/0/1.0 dynamic Uptime: 02:04:32 timeout: 250
   Group: 224.0.1.40
     ge-0/0/0.0 timeout: 125 Last reporter: 172.16.0.3 Receiver count: 1, Flags: <V2-hosts>
     ge-0/0/1.0 timeout: 251 Last reporter: 172.16.0.4 Receiver count: 1, Flags: <V2-hosts>
   Group: 224.0.1.60
     ge-0/0/1.0 timeout: 252 Last reporter: 172.16.6.153 Receiver count: 2, Flags: <V2-hosts>
     ge-0/0/0.0 timeout: 191 Last reporter: 172.16.4.178 Receiver count: 1, Flags: <V2-hosts>
   Group: 224.0.1.178
     ge-0/0/0.0 timeout: 127 Last reporter: 172.16.5.34 Receiver count: 1, Flags: <V2-hosts>
   Group: 224.0.124.124
     ge-0/0/0.0 timeout: 258 Last reporter: 172.16.1.52 Receiver count: 6, Flags: <V2-hosts>
     ge-0/0/1.0 timeout: 248 Last reporter: 172.16.1.149 Receiver count: 7, Flags: <V2-hosts>
------------------------------------------------------------------------------------------


There are multicast sources sending traffic:
------------------------------------------------------------------------------------------
root at led-csw3> show pim join extensive    
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Group: 239.250.0.110
    Source: 192.168.199.3
    Flags: dense
    Upstream interface: vlan.7
    Upstream neighbor: Direct
    Downstream interfaces:
        vlan.6

Group: 239.250.0.112
    Source: 192.168.199.3
    Flags: dense
    Upstream interface: vlan.7
    Upstream neighbor: Direct
    Downstream interfaces:
        vlan.6

Group: 239.250.0.120
    Source: 192.168.199.3
    Flags: dense
    Upstream interface: vlan.7
    Upstream neighbor: Direct
    Downstream interfaces:
        vlan.6
------------------------------------------------------------------------------------------

Yet there are no groups registered with the RP:
------------------------------------------------------------------------------------------
root at led-csw3> show pim rps extensive 
Instance: PIM.master
Address family INET

RP: 10.172.12.14
Learned via: static configuration
Time Active: 00:18:54
Holdtime: 0
Device Index: 26
Subunit: 32769
Interface: pimd.32769
Group Ranges:
        224.0.0.0/4

Address family INET6

{master:0}
------------------------------------------------------------------------------------------

As a result when I change to Dense mode everything breaks...

Has any one seen this before?

In addition there are now some Cisco switches hanging off the juniper with igmp-snooping set up and it is handling the sending of traffic to hosts that actually need it...

Mauritz 


More information about the juniper-nsp mailing list