Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

route-distinguisher

Syntax

Hierarchy Level

Description

Specify an identifier attached to a route, enabling you to distinguish to which VPN or virtual private LAN service (VPLS) the route belongs. Each routing instance must have a unique route distinguisher (RD) associated with it. The RD is used to place bounds around a VPN so that the same IP address prefixes can be used in different VPNs without having them overlap. If the instance type is vrf, the route-distinguisher statement is required.

For Layer 2 VPNs and VPLS, if you configure the l2vpn-use-bgp-rules statement, you must configure a unique RD for each PE router participating in the routing instance.

For Ethernet VPN (EVPN), you must configure a unique RD for each PE router participating in the routing instance to ensure that the prefixes generated by different PEs are unique.

For other types of VPNs, we recommend that you use a unique RD for each provider edge (PE) router participating in specific routing instance. Although you can use the same RD on all PE routers for the same VPN routing instance, if you use a unique RD, you can determine the customer edge (CE) router from which a route originated within the VPN.

For Layer 2 VPNs and VPLSs, if you configure mesh groups, the RD in each mesh group must be unique.

CAUTION:

We strongly recommend that if you change an RD that has already been configured, or change the routing-instance type from virtual-router to vrf, make the change during a maintenance window, as follows:

  1. Deactivate the routing instance.

  2. Change the RD.

  3. Activate the routing instance.

This is not required if you are configuring the RD for the first time.

Options

as-number:number—as-number is an assigned AS number, and number is any 2-byte or 4-byte value. The AS number can be from 1 through 4,294,967,295. If the AS number is a 2-byte value, the administrative number is a 4-byte value. If the AS number is 4-byte value, the administrative number is a 2-byte value. An RD consisting of a 4-byte AS number and a 2-byte administrative number is defined as a type 2 RD in RFC 4364 BGP/MPLS IP VPNs.

Note:

In Junos OS Release 9.1 and later, the numeric range for AS numbers is extended to provide BGP support for 4-byte AS numbers, as defined in RFC 4893, BGP Support for Four-octet AS Number Space. All releases of Junos OS support 2-byte AS numbers. To configure an RD that includes a 4-byte AS number, append the letter “L” to the end of the AS number. For example, an RD with the 4-byte AS number 7,765,000 and an administrative number of 1,000 is represented as 77765000L:1000.

In Junos OS Release 9.2 and later, you can also configure a 4-byte AS number using the AS dot notation format of two integer values joined by a period: <16-bit high-order value in decimal>.<16-bit low-order value in decimal>. For example, the 4-byte AS number of 65,546 in the plain-number format is represented as 1.10 in AS dot notation format.

number:id—Number and identifer expressed in one of these formats: 16-bit number:32-bit identifier or 32-bit number:16-bit identifier.

ip-address:id—IP address (ip-address is a 4-byte value) within your assigned prefix range and a 2-byte value for the id. The IP address can be any globally unique unicast address.

  • Range: 0 through 4,294,967,295 (232 – 1). If the router you are configuring is a BGP peer of a router that does not support 4-byte AS numbers, you need to configure a local AS number. For more information, see Using 4-Byte Autonomous System Numbers in BGP Networks Technology Overview.

Note:

For Ethernet VPN (EVPN), an RD that includes zero as the id value is reserved for the default EVPN routing instance by default. Because the same RD cannot be assigned for two routing instances, using a ip-address:id RD for another routing instance (default-switch), where the id value is zero, throws a commit error.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.

Support at [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] hierarchy level introduced in Junos OS Release 11.2.

Support at [edit routing-instances routing-instance-name protocols l2vpn mesh-group mesh-group-name] hierarchy level introduced in Junos OS Release 13.2.

Support at the following hierarchy levels introduced in Junos OS Release 20.3R1 on QFX Series switches: [edit protocols evpn interconnect] and [edit routing-instances routing-instance-name protocols evpn interconnect].

Related Documentation