[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring the Routing Instance on the PE1 Router

Configure the routing instance (VPN-A) for the Layer 3 VPN on router PE1. As part of the configuration, you need to establish the PIM instance for the VPN. Use the vpn-group-address statement at the [edit routing-instances routing-instance-name protocols pim] hierarchy level to specify the VPN group address, which is needed for multicast over a Layer 3 VPN configuration.

Set the RP configuration for the VRF instance at the [edit routing-instances routing-instance-name protocols pim] hierarchy level. The RP configuration within the VRF instance provides explicit knowledge of the RP address, so that the (*,G) state can be forwarded.

For Release 5.5 or later, configure an additional unit on the loopback interface of the PE router at the [edit interfaces] hierarchy level, and assign an address from the VPN address space. Then add the newly created loopback interface in two places:

Routing instance (VPN-A) at the [edit routing-instances routing-instance-name] hierarchy level.
Routing instance (VPN-A) at the [edit routing-instances routing-instance-name protocols pim] hierarchy level.

Also, add the loopback interface to the IGP and Border Gateway Protocol (BGP) policies to advertise the interface in the VPN address space. For more information about how to configure a logical unit on a loopback interface, see the JUNOS VPNs Configuration Guide.

In multicast Layer 3 VPNs, the multicast PE routers must use the primary loopback address (or router ID) for sessions with their internal BGP peers. If the PE routers use a route reflector with next-hop self configured, Layer 3 multicast over VPN will not work because PIM cannot transmit upstream interface information for multicast sources behind remote PEs into the network core. Multicast Layer 3 VPNs require the BGP next-hop address of the VPN route to match the BGP next-hop address of the loopback VRF instance address.



routing-instances {


VPN-A {
instance-type vrf;
interface t1-1/0/0:0.0;
interface lo0.1;
route-distinguisher 10.255.71.46:100;
vrf-import VPNA-import;
vrf-export VPNA-export;


protocols {


ospf {
export bgp-to-ospf;


area 0.0.0.0 {
interface t1-1/0/0:0.0;
interface lo0.1;
}


}




pim {
vpn-group-address 239.1.1.1;


rp {


static {
address 10.255.245.91;
}


}




interface t1-1/0/0:0.0 {
mode sparse;
version 2;


interface lo0.1 {
mode sparse;
version 2;
}


}


}


}


}




interfaces {


lo0 {
description "unit 1 has the important PIM address";


unit 0 {


family inet {
address 192.168.27.13/32;
primary;
address 127.0.0.1/32;
}


}




unit 1 {


family inet {
address 10.10.47.101/32;
}


}


}


}


}

Note: Multicast Layer 3 VPNs require the BGP next-hop address of the VPN route to match the BGP next-hop address of the loopback VRF instance address.

[Contents] [Prev] [Next] [Index] [Report an Error]