By default, routes received from an internal BGP (iBGP) peer are not sent to another iBGP peer unless a full mesh configuration
is formed between all Boarder Gateway Protocol (BGP) devices within an autonomous system (AS). Configuring a route reflector
allows a device to advertise or reflect the iBGP learned routes to other iBGP speakers.
Ethernet VPN (EVPN) Autodiscovery supports BGP route reflectors. A BGP route reflector can be used to reflect BGP EVPN prefixes
without EVPN being explicitly configured on the route reflector. The route reflector does not participate in autodiscovery;
that is, no pseudowires are set up between the route reflector and the provider edge (PE) devices. A route reflector reflects
EVPN prefixes to other PE devices so that these PE devices do not need to have a full mesh of BGP sessions. The network administrator
configures only the BGP EVPN address family on a route reflector.
BGP uses the Layer 2 VPN (L2VPN) routing information base (RIB) to store endpoint provisioning information, which is updated
each time any Layer 2 virtual forwarding instance (VFI) is configured. The prefix and path information is stored in the L2VPN
database, which allows BGP to make decisions about the best path. When BGP distributes the endpoint provisioning information
in an update message to all its BGP neighbors, this endpoint information is used to configure a pseudowire mesh to support