Auto-derived RD in services with multiple BGP families

A single RD is used per service and not per BGP family or protocol. On the 7210 SAS, BGP-AD is not supported with BGP-EVPN.

The following rules apply:

• The VPLS RD is selected based on the following precedence:

  • Manual RD always takes precedence when configured.

  • If no manual-rd configuration exists, the RD is derived from the bgp-evpn>evi.

  • If no manual-rd or bgp-evpn>evi configuration exists, there is no RD and the service fails.

• The selected RD (see the preceding selection criteria) is displayed by the Oper Route Dist field of the show service id bgp command.

• The service supports dynamic RD changes; for example, the manual RD can be updated dynamically, even if it is currently in use as the service RD.

  Note: When the RD changes, the active routes for that VPLS are withdrawn and re-advertised with the new RD.

• If one of the mechanisms to derive the RD for a specified service is removed from the configuration, the system selects a new RD based on the preceding rules. For example, if the manual RD is removed form the configuration, the routes are withdrawn, the new RD is selected from the EVI, and the routes re-advertised with the new RD. See Auto-derived RD in services with multiple BGP families for more information about rules governing the RD selection.

  Note: The reconfiguration fails if the new RD already exists in a different VPLS or Epipe service.