2eW4ZRB

The template makes it easy to apply P2MP characteristics to an LSP. Next, we move to the
routing instance configuration where we use that template:
user@mx80-23# show routing-instances NG-MVPN-1
instance-type vrf;
interface xe-0/0/1.1;
interface lo0.1;
route-distinguisher 192.168.36.23:36;
provider-tunnel {
rsvp-te {
label-switched-path-template {
inter-as-p2mp-template;
}
}
}
The provider-tunnel keyword means that traffic will be tunneled across the P2MP tunnel.
When configuring how the provider tunnel should work, remember that two possibilities exist:
• Inclusive: This is the simplest option. When a packet enters the tunnel, it is sent to all
the endpoints, meaning all the PEs receive the packet. However, this solution could
lead to an inefficient use of bandwidth because some PEs might not be connected to
any multicast receiver at that time.
• Selective: To increase efficiency, we can send packets only where necessary. A
selective tunnel works by making it possible to specify a subset of PEs that receive
those packets. So only some branches of the tree see traffic, while other branches
see none.
The configuration provided earlier is used for an inclusive tunnel, and that is what we are
using in this example.
8.3 MVPN Signaling
Let’s see how multicast VPN (MVPN) information is exchanged among PE routers.
Once again, we use BGP as routing protocol. This confirms how BGP can be effectively used
to transport “services.”
In Junos OS terms, in order to enable MVPN signaling, we have to configure a new family
when defining the EBGP sessions among PE routers. In this case, the new family is “Internet
MVPN signaling.”
user@mx80-23# show protocols bgp
group EBGP-MHOP {
type external;
multihop {
ttl 10;
}
local-address 192.168.36.23;
family inet-vpn {
unicast;
}
family inet-mvpn {
signaling;
}
peer-as 65538;
neighbor 192.168.38.24;
neighbor 192.168.38.1;
}
It is important to note that this family is necessary only for EBGP sessions between PEs.
When configuring IBGP sessions (PE-P or P-P), we don’t need it. If we decided to use the
expand-next-hop solution to build LSPs, we still have to configure the IBGP sessions.
Copyright (©) 2016 Juniper Networks. All Rights Reserved.
Page 40 of 53