2eW4ZRB

There are seven different messages:
• Type 1 and Type 2 messages are similar and are used to exchange information about
membership to a particular MVPN. This information is useful when building the P2MP
because we know which PEs need to be reached.
• Type 3 messages are used when there is the intention to build a selective tree. In
response to this message, egress routers can reply with a Type 4 message,
indicating interest in a particular source and group.
• Type 5 messages are generated when a source is discovered. It is important to notice
that before this message is created, a pure PIM message is generated. PE routers
receive that message and translate its content into a Type 5 MVPN signaling
message.
• Type 6 and 7 MVPN signaling messages are similar to Type 5 and are sent when an
egress router receives a PIM shared-tree join or a PIM source-tree join message.
Those messages are translated, and Type 6 or Type 7 MVPN signaling messages
are sent. Type 7 messages are also sent in response to a Type 5 route
announcement received from an ingress PE.
8.4 CE Configuration
The first thing to configure is the PIM protocol running between the CE and the PE.
user@mx80-1# show protocols pim
pim {
rp {
local {
family inet {
address 192.168.100.1;
}
}
}
interface lo0.1;
interface xe-0/0/1.1;
interface xe-0/0/3.0;
}
Then we have to define the EBGP session with the PE router:
user@mx80-23# show protocols bgp
bgp {
group EBGP {
type external;
export MCAST-SRC;
peer-as 65536;
neighbor 10.136.1.1;
}
}
8.5 PE Configuration
Now let’s look at all the different protocols we have to configure on the PE router. The PE
needs to configure a routing instance, and inside the instance we also configure all the
necessary protocols, such as PIM, EBGP for a session with the CE, and support for NG
MVPN.
user@mx80-23# show vrf
instance-type vrf;
interface xe-0/0/1.1;
interface lo0.1;
Copyright (©) 2016 Juniper Networks. All Rights Reserved.
Page 42 of 53