Junos
Junos

NG MVPN configuration

[ Edited ]
‎09-28-2019 11:41 AM

Hello people

I have been trying to set up ng mvpn on a lab environment with no luck as I could not get to triger type 7 routes on the bgp.mvpn.0 tables my setup is as such:

 

Receiver(Junos Olive)==PE1==P1==PE3==Sender(Junos Olive)

 

PE1, P1 and PE3 are vMXs running Junos 14.1R1.10

 

PE1 Configuration

 

routing-instances {
MCAST {
instance-type vrf;
interface ge-0/0/2.0;
route-distinguisher 100:1;
vrf-target target:100:1;
vrf-table-label;
protocols {
pim {
interface ge-0/0/2.0 {
mode sparse;
}
}
mvpn {
receiver-site;
}
}
}

 

PE3 configuration

routing-instances {
MCAST {
instance-type vrf;
interface ge-0/0/2.10;
route-distinguisher 100:1;
provider-tunnel {
rsvp-te {
label-switched-path-template {
default-template;
}
}
}
vrf-target target:100:1;
vrf-table-label;
routing-options {
static {
route 192.168.56.0/24 next-hop 10.10.10.2; # this is the subnet of the multicast souce
}
}
protocols {
pim {
interface ge-0/0/2.10 {
mode sparse;
}
}
mvpn {
sender-site;
}
}
}

 

Sender configuration

protocols {
pim {
interface em0.10 { # this is interface connecting to PE3
mode sparse;
}
}
}
 

 

Receiver configuration

protocols {
igmp {
interface em0.0 { # this is the interface connecting to PE1
static {
group 232.0.1.1 {
source 192.168.56.55;
}
}
}
}
pim {
interface all {
mode sparse;
}
}
}
 

 

To simulate multicast source on Sender I used

> ping 232.0.1.1 bypass-routing interface em0.10 source 192.168.56.55 ttl 64 interval 0.1

 

I could see the traffic on PE3

# run show multicast route instance MCAST extensive 
Instance: MCAST Family: INET
Group: 232.0.1.1
Source: 192.168.56.55/32
Upstream interface: ge-0/0/2.10
Number of outgoing interfaces: 0
Session description: Source specific multicast
Statistics: 0 kBps, 0 pps, 72741 packets
Next-hop ID: 0
Upstream protocol: PIM
Route state: Active
Forwarding state: Pruned
Cache lifetime/timeout: 346 seconds
Wrong incoming interface notifications: 0
Uptime: 02:28:31

 

However PIM source showed nothing on PE3

# run show pim source instance MCAST 
Instance: PIM.MCAST Family: INET
Instance: PIM.MCAST Family: INET6

 

The type 1 routes are propagated succesfully between PE1 and PE3 via P1 which acts as a route reflector. Please assit to point on what I may be doing wrong

2 REPLIES 2
Junos

Re: NG MVPN configuration

‎09-29-2019 02:39 AM

Hello,

There is a free Day1 JUNOS book on BGP NG-MVPN https://forums.juniper.net/t5/Day-One-Books/This-Week-Deploying-BGP-Multicast-VPNs-2nd-Edition/ba-p/... (from 2011 but still relevant)

Off-the-bat, I see few issues here:

1/ Your VMX version is really ancient, please update to supported one

2/ You are doing PIM-SM but no RP is defined in the configs You shared

3/ if Your mcast source is not directly connected to the Sender PE, You have to use "accept-remote-source" knob https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/accept-re...

HTH

Thx

Alex

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Junos

Re: NG MVPN configuration

‎09-30-2019 03:28 AM

I was able to partially fix the problem with below:

1. configuring the RP in the vrf on PE1 the RP ip was set to Sender IP on interface facing PE3

2. remove pim configuration on sender and used the ip on interface facing PE3 as source ip

3. configured sap on receiver

 

PE1 configuration

 

routing-instances {
    MCAST {
        instance-type vrf;
        interface ge-0/0/0.10;
        interface ge-0/0/2.0;
        route-distinguisher 100:1;
        vrf-target target:100:1;
        vrf-table-label;
        protocols {
            pim {
                rp {
                    static {
                        address 10.10.10.2;
                    }
                }
                interface ge-0/0/0.10 {
                    mode sparse;
                }
                interface ge-0/0/2.0 {
                    mode sparse;
                }
            }
            mvpn {
                receiver-site;
            }
        }
    }
}

Sender configuration

interfaces {
    em0 {
        vlan-tagging;
        unit 10 {
            vlan-id 10;
            family inet {
                address 10.10.10.2/30;
            }
        }
    }
}

Receiver configuration

protocols {
    sap {
        listen 224.2.127.254;
    }
}

 

From source

ping 224.2.127.254 bypass-routing interface em0.10 ttl 64 interval 0.1

 

I could not get the SSM group 232.0.1.1 to work so I used SAP multicsst group. Will do more research on this. Will go through the day1 book im pretty sure I will find the solution there