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

Configuring Draft-Rosen Multicast VPN Autodiscovery

To configure draft-rosen VPN autodiscovery for provider tunnels operating in SSM mode, include the mvpn statement:




mvpn { 



autodiscovery { 

inet-mdt;
}


}

You can include this statement at the following hierarchy levels:

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

To enable autodiscovery as described in Multicast over Layer 3 Draft-Rosen VPNs, include the inet-mdt statement.

Note: When you configure draft-rosen multicast VPNs with provider tunnels operating in source-specific mode and using the vrf-export statement to specify the export policy, the policy must have a term that accepts routes from the vrf-name.mdt.0 routing table. This term ensures proper PE autodiscovery using the inet-mdt address family.

When you configure draft-rosen multicast VPNs with provider tunnels operating in source-specific mode and using the vrf-target statement, the VRF export policy is automatically generated and automatically accepts routes from the vrf-name.mdt.0 routing table.

To configure the BGP-based MVPN control plane to provide signaling only for autodiscovery and not for PIM operations, include the autodiscovery-only statement:




autodiscovery-only { 



intra-as { 

inclusive;
}


}

You can include this statement at the following hierarchy levels:

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

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