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

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.

A PE router with sites in a specific multicast VPN must determine whether a received automatic discovery route is from a sender site or receiver site based on the following:

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 VPNs Configuration Guide.

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



[edit]
routing-instances {


vpn-a {


protocols {


mvpn {


route-target {


export-target { # Export target for multicast VPN AD routes.
Overrides default # VRF export target if "export-target unicast" is
not configured. 
target target-community; 

unicast; # Apply the VRF export target and multicast VPN
export route 
# target to multicast VPN AD routes.
apply-groups group-name; # Groups
from which to inherit
# configuration data.
apply-groups-except group-name; #
Do not inherit configuration data from 
# these groups.
}




import-target { # Import target for multicast VPN AD routes.
Overrides 
# default VRF import target if "import-target
unicast" is not configured.


target target-value { # Target community.
receiver target-value; # Target community
used when importing receiver # site routes.
sender target-value; # Target community
used when importing sender # site routers.
}




unicast { #Apply the default VRF import target or multicast
VPN 
# route-target to multicast VPN AD routes.
receiver;
sender;
}


apply-groups group-name;
apply-groups-except group-name;
}


}


}


}


}


}

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 policy qualifier protocol. The workaround is to relax the policy to not reflect routes based on the protocol type or to use additional multicast-VPN-specific configuration.

If the vrf-import policy does not import bgp routes, multicast VPN routes of type 1, 2, 3, or 5 imported by BGP will be rejected. There are two workarounds:

You can add a term to allow routes from protocol bgp 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 will be 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 will not be exported. This is because JUNOS does not support a policy qualifier for protocol multicast VPN. The workaround is to configure an export target under multicast VPN without configuring unicast:protocol mvpn { export-target { target target:2:2; } } }

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