[j-nsp] VRRP aware IGMP/PIM
Krasimir Avramski
krasi at smartcom.bg
Tue May 13 09:21:35 EDT 2014
Hello,
Why you use the hello-interval of 0 on PE1 PIM configuration?
While I'm not 100% sure this probably prevents sending hello messages on
segment so potentially PIM DR election is broken - there is possibility
both PE routers to believe they are DRs for the segment.(PE1 seeing P2'S
hellos elects himself because of highest IP address and PE2 not seeing
neighbor hellos elect himself as one and only pim router on segment)
HTH,
Krasi
On 13 May 2014 15:09, Misak Khachatryan <m.khachatryan at gnc.am> wrote:
> Hello,
>
> i have following scheme:
>
>
> PE1 -------- CE -------- PE2
> |
> Multicast Receiver
>
> PE1 - MX480
> PE2 - MX80
> CE - EX4200
>
> VLAN with IGMP snooping configured on CE. VRRP and VRF with NG-MVPN
> configured on PE1 and PE2. IGMP enabled on both CE facing interfaces.
>
> Now both PEs sending multicast streams to receiver, despite on that one
> VRRP peer is active, second - passive, which causes unpredicted results on
> receiver side. Disabling IGMP or interface from any side makes everything
> to work perfect.
>
> I think there should be a way to tell IGMP that it should accept register
> messages until router is not VRRP master, but I can't find it.
>
> Any thoughts?
>
> Config parts:
>
>
> misak at PE1# show interfaces ge-0/0/1 unit 3093
> description IPTV_Ashtarak_OLT1;
> vlan-id 3093;
> family inet {
> address 10.12.0.1/20 {
> vrrp-group 112 {
> virtual-address 10.12.0.1;
> priority 255;
> fast-interval 100;
> preempt;
> }
> }
> }
>
> misak at PE1# show protocols igmp interface ge-0/0/1.3093
> version 3;
>
> misak at PE1# show routing-instances IPTV
> instance-type vrf;
> interface ge-0/0/1.3093;
> interface vt-1/3/0.0 {
> multicast;
> }
> interface lo0.1;
> route-distinguisher 65500:3093;
> provider-tunnel {
> selective {
> group 239.255.0.0/24 {
> source 10.0.242.0/23 {
> ldp-p2mp;
> }
> }
> }
> }
> vrf-target target:65500:3093;
> vrf-table-label;
> forwarding-options {
> dhcp-relay {
> forward-snooped-clients all-interfaces;
> server-group {
> IPTV_DHCP {
> 10.0.237.2;
> }
> }
> group Abovyan {
> active-server-group IPTV_DHCP;
> relay-option-82 {
> circuit-id {
> use-interface-description logical;
> }
> }
> interface ge-0/0/1.3093 {
> overrides {
> allow-snooped-clients;
> always-write-giaddr;
> always-write-option-82;
> }
> }
> }
> }
> }
> protocols {
> pim {
> rp {
> local {
> family inet {
> address 10.0.238.6;
> }
> }
> }
> interface all {
> mode sparse;
> version 2;
> hello-interval 0;
> }
> }
> mvpn;
> }
>
> misak at PE2# show interfaces ge-1/0/9 unit 3093
> description IPTV_Ashtarak_OLT1;
> vlan-id 3093;
> family inet {
> address 10.12.0.9/20 {
> vrrp-group 112 {
> virtual-address 10.12.0.1;
> priority 100;
> fast-interval 100;
> }
> }
> }
>
> misak at PE2# show protocols igmp interface ge-1/0/9.3093
> version 3;
>
> misak at PE2# show routing-instances IPTV
> instance-type vrf;
> interface ge-1/0/9.3093;
> interface lo0.1;
> route-distinguisher 10.255.255.8:3093;
> vrf-target target:65500:3093;
> vrf-table-label;
> forwarding-options {
> dhcp-relay {
> forward-snooped-clients all-interfaces;
> server-group {
> IPTV_DHCP {
> 10.0.237.2;
> }
> }
> group Abovyan {
> relay-option-82 {
> circuit-id {
> use-interface-description logical;
> }
> }
> interface ge-1/0/9.3093 {
> overrides {
> allow-snooped-clients;
> always-write-giaddr;
> always-write-option-82;
> }
> }
> }
> }
> }
> protocols {
> pim {
> rp {
> static {
> address 10.0.238.6;
> }
> }
> interface all {
> mode sparse;
> version 2;
> }
> }
> mvpn {
> receiver-site;
> }
> }
>
> Junos version 12.3
>
> --
> Best regards,
> Misak Khachatryan,
> Network Administration and
> Monitoring Department Manager,
> GNC-Alfa CJSC.
> _______________________________________________
> 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