A BGP Route Distinguisher (RD) is a network identifier that

• uniquely distinguishes VPN routes to prevent conflicts,

• enables separate route tables for different VPNs, and

• supports scalable, secure, and efficient VPN route management.

In network design solutions where customer equipment is dual-homed and Fast Reroute is required, such as in EVPN and BGP Prefix Independent Convergence (PIC) Edge solutions, the RD associated with each VRF must be unique per Provider Edge (PE) router. In other design scenarios, while it isn’t mandatory for the RD to be unique per PE, it is highly recommended to make it unique. This practice facilitates easier transitions to dual-homed solutions in the future.

Ensuring unique RDs significantly enhances network scalability and security by maintaining distinct route tables for separate VPNs, which prevents routing conflicts and optimizes network performance. Additionally, it simplifies routing policies, making the configuration and management of large-scale networks more efficient and reliable.

To maintain unique RDs across the network, you can configure them either as automatic or static RDs under VRF or EVPN services such as EVI, VNI, or SRv6.

You can configure RD in these formats:

• IP:nn

  • IP is the BGP Router-ID configured on the router.

  • nn is the EVI, VNI, or SRv6, or a value selected from a pool if the default value is already in use.

• 2B:4B

  • 2B is the two byte administrator field.

  • 4B is the four byte assigned number field.

• 4B:2B

  • 4B is the four byte administrator field.

  • 2B is the two byte assigned number field.

The following table provides a comparison between static and automatic RD configurations in VRF and EVPN technologies.

These are the limitation for BGP RD:

• When you configure static RD in IP:nn format, make sure that it doesn't conflict with the IP:nn RD automatically generated value of another EVPN service such as EVI, VNI, or SRV6 in your network.

  If the configured static RD value matches the autogenerated RD in IP:nn format for this or another service, then:

  • The Cisco IOS XR software rejects the static RD configuration in the following scenario:

    • If the EVI is configured first under a bridge-domain or xconnect and

    • then, a matching static RD is configured under the EVI.

  • Cisco IOS XR software displays a system log message and doesn't reject the static RD in the following scenario:

    • The RD is configured first under the EVI and

    • then, the EVI is associated with a bridge-domain or xconnect.

• In a Data Center Interconnect (DCI) deployment, you must not use the same RD between the edge DCI gateway and the MPLS-VPN PE router, nor between the edge DCI gateway and the Leaf with Top of Rack (ToR) switch when you re-originate routes with a stitching route target (stitching-rt) for a specific Virtual Routing and Forwarding (VRF) instance.