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

Configuring Multicast for Virtual Routers

You can configure PIM for the virtual-router routing instance type as well as for the vrf instance type. The virtual-router instance type is similar to the vrf instance type used with Layer 3 VPNs, but is used for non-VPN-related applications.

The virtual-router instance type has no VRF import, VRF export, VRF target, or route distinguisher requirements. The virtual-router instance type is used for non-Layer 3 VPN situations, for example, to allow the use of IP Security (IPSec) tunnels within VPNs.

When PIM is configured under the virtual-router instance type, the VPN configuration is not based on RFC 2547, BGP/MPLS VPNs, so PIM operation does not comply with the Internet draft draft-rosen-vpn-mcast-07.txt Multicast in MPLS/BGP VPNs. For more information about multicast draft support, see IP Multicast Standards. In the virtual-router instance type, PIM operates in a routing instance by itself, forming adjacencies with PIM neighbors over the routing instance interfaces as the other routing protocols do with neighbors in the routing instance.

To configure PIM for a virtual-router instance type, include both the pim statement and the instance-type statement, specifying the virtual-router instance type:



instance-type virtual-router;
protocols {


pim {
...pim-configuration...

}


}

You can include these statements at the following hierarchy levels:

[edit routing-instances routing-instance-name]
[edit logical-systems logical-system-name routing-instances routing-instance-name]

Do not include the vpn-group-address statement for the virtual-router instance type.

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