Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Option: Specifying Route Targets

Specifying route targets for sender and receiver sites is useful when there is a mix of sender only, receiver only, and sender and receiver sites. This is because a sender site’s routing table is used for exporting routes from a sender site and importing routes from a receiver site. A receiver site's routing table is used for exporting routes from a receiver site and importing routes from a sender site. A sender and receiver site does both. The route targets configured under multicast VPNs apply only to multicast VPN AD routes of type 1, 2, 3, and 5.

• If the PE router is configured to be only in a sender site, route targets are imported only from receiver sites. Imported automatic discovery routes must be from a receiver site.
• If the PE router is configured to be only in a receiver site, route targets are imported only from sender sites. Imported automatic discovery routes must be from a sender site.
• If the PE router is configured to be both in sender and receiver sites, the following guidelines apply:
  • Along with an import route target, you can optionally configure whether the route target is from a receiver or a sender site.
  • If a configuration is not provided, an imported automatic discovery route is treated as belonging to both the sender site and the receiver site.

For more information on route targets, see the Junos OS VPNs Configuration Guide.

In the following example, the export target is used for multicast VPN autodiscovery routes. It overrides the default VRF export target if the unicast statement is not included. The unicast statement applies the VRF export target and multicast VPN export route target to multicast VPN autodiscovery routes. The apply-groups statement specifies the groups from which to inherit configuration data. The apply-groups-except statement specifies the groups from which to not inherit configuration data. The import-target statement specifies the import target for multicast VPN autodiscovery routes. It overrides the default VRF import target if the unicast statement is not included.

To specify route targets, include the route-target statement at the [edit routing-instances routing-instance-name protocols mvpn] hierarchy level:

Existing VRF import or VRF export policies for importing and exporting VPN routes might prevent import or export of multicast VPN routes if the policies reflect routes based on the protocol type. The workaround is to change the policy to not reflect routes based on the protocol type or to use additional multicast VPN-specific configuration.

• You can add a term to allow routes from the BGP protocol with family inet-mvpn:
  term 2 {from {protocol bgp;family inet-mvpn;community vpn_blue;}then {accept;}}

  The customer can configure an import target under mvpn. The multicast VPN route of type 1, 2, 3, or 5 matching the configured target are imported.

  protocol mvpn {import-target {target target:2:2;}}
• If the VRF export policy uses a policy qualifier of type protocol to reject routes, the multicast VPN routes of type 1, 2, 3, or 5 are not exported. This is because Junos OS does not support a policy qualifier for MVPN. The workaround is to configure an export target under MVPN without including the unicast statement:
  protocol mvpn {export-target {target target:2:2;}}}