[j-nsp] Multicast - interop with Cisco
Bikram Singh
sbikram at live.com
Tue Dec 11 03:49:26 EST 2012
check if your mt- tunnel is up between these 2 PEs
show pim neighbors instance iptv
and also please check the reachability issues in the vrf as its in vpn
-B
.
> Date: Mon, 10 Dec 2012 18:14:43 +0100
> From: pederbach at gmail.com
> To: stacy at acm.org
> CC: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Multicast - interop with Cisco
>
> Thanks! It works :-)
>
>
> Should this also work in the vrf?
>
>
> Global:
>
> peder at ar100.nn# run show pim rps
> Instance: PIM.master
>
> address-family INET
> RP address Type Mode Holdtime Timeout Groups Group prefixes
> 10.224.0.255 auto-rp sparse 181 175 1 224.0.0.0/4
>
>
> peder at ar100.nn> show pim rps instance iptv
> Instance: PIM.bynett
>
> address-family INET
>
> address-family INET6
>
> We should get another RP.
>
>
> [edit routing-instances iptv]
> peder at ar100.nn# show
> instance-type vrf;
> interface ge-0/0/0.0;
> interface lo0.1;
> route-distinguisher 65339:50;
> provider-tunnel {
> pim-asm {
> group-address 239.1.1.1;
> }
> }
> vrf-target target:65339:50;
> vrf-table-label;
> protocols {
> pim {
> dense-groups {
> 224.0.1.39/32;
> 224.0.1.40/32;
> }
> vpn-tunnel-source 10.224.0.96;
> vpn-group-address 239.1.1.1;
> rp {
> auto-rp discovery;
> }
> }
> interface lo0.1 {
> mode sparse-dense;
> }
> interface ge-0/0/0.0 {
> mode sparse-dense;
> }
> }
> }
>
>
> > Add this to your config:
> >
> > [edit protocols pim]
> > user at host# set dense-groups 224.0.1.39/32
> > user at host# set dense-groups 224.0.1.40/32
> >
> > Further info can be found here:
> > http://www.juniper.net/techpubs/en_US/junos12.2/topics/topic-map/mcast-pim-auto-rp.html
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list