Configure the Route Target

As part of the policy configuration for the VPN routing table, you must define a route target which defines which VPN the route is a part of. When you configure different types of VPN services (Layer 2 VPNs, Layer 3 VPNs, or VPLS) on the same PE router, be sure to assign unique route target values to avoid the possibility of adding route and signaling information to the wrong VPN routing table.

Include the target option in the community statement:

community name members target:community-id;

You can configure this statement at the following hierarchy levels:

• [edit policy-options]
• [edit logical-routers logical-router-name policy-options]

name is the name of the community.

community-id is the identifier of the community. You specify it in one of the following formats:

• as-number:number, where as-number is an autonomous system (AS) number (a 2-byte value) and number is a 4-byte community identifier. The AS number can be in the range 1 through 65,535. We recommend that you use an Internet Assigned Numbers Authority (IANA)-assigned, nonprivate AS number, preferably the Internet service provider's (ISP's) own or the customer's own AS number. The community identifier can be a number in the range 0 through 2³² - 1.
• ip-address:number, where ip-address is an Internet Protocol Version 4 (IPv4) address (a 4-byte value) and number is a 2-byte community identifier. The IP address can be any globally unique unicast address. We recommend that you use the address that you configure in the router-id statement, which is a nonprivate address in your assigned prefix range. The community identifier can be a number in the range 1 through 65,535.