Skip to content

Default Route Reflector#

Underlay Routing → DRDefault Route Reflectors

The DefaultRouteReflector resource is in many ways similar to the RouteReflector resource, but is deployed in the default VRF instead of the overlay. This means that it has support for more routing protocols, which are required to distribute overlay (service) routes.

BGP route reflectors are used to eliminate the need for a full-mesh iBGP peering network, where every router needs to establish an iBGP session with every other router in the network. Route reflectors re-advertise the routes they receive from the route reflector clients, removing the need for iBGP sessions between the clients.

EDA creates a derived DefaultBGPPeer for every DefaultRouteReflectorClient that the DefaultRouteReflector targets. This targeting is done by assigning labels to the DefaultRouteReflectorClient, and referencing this label in the DefaultRouteReflector.

Don't forget to use labels!

If no target label is specified in the ClientSelector property of the DefaultRouteReflector resource, the DefaultRouteReflector will create DefaultBGPPeer resources for every DefaultRouteReflectorClient and RouteReflectorClient.

Example:

In this example, RR1 will create 3 derived DefaultBGPPeer resources: one for each client. RR2 will create only 2 derived DefaultBGPPeer resources: one towards client1, and one towards client2. Client3 does not have label rr-label=client, and therefore is not selected as client for RR2.

To set up BGP route reflectors in router services, use RouteReflector instead.

Dependencies#

To configure this resource, the following resources must exist or be created alongside the DefaultRouteReflector

  • A DefaultBGPGroup that the DefaultRouteReflector will inherit settings from, such as local and remote AS numbers
  • An interface that the DefaultRouteReflector will use to establish the client sessions. This can either be a SystemInterface or a DefaultInterface

Referenced resources#

DefaultBGPGroup#

The DefaultBGPPeer resource that the DefaultRouteReflector creates towards each selected DefaultRouteReflectorClient is always linked to a single DefaultBGPGroup. These BGP peers share common parameters, such as BGP import and export policies, local and peer autonomous system numbers, and BGP timers. By specifying these parameters in a DefaultBGPGroup, the operator can change these settings in a single location for all client BGP peers.

SystemInterface#

To know which IP address is used to send BGP traffic, EDA must have a reference to a virtual interface. If this interface is a SystemInterface attached directly to the system address of the DefaultRouter, a reference to this resource needs to be provided when creating the DefaultRouteReflector.

DefaultInterface#

To know which IP address is used to send BGP traffic, EDA must have a reference to a virtual interface. If this interface is an DefaultInterface attached to a DefaultRouter, a reference to this resource needs to be provided when creating the DefaultRouteReflector.

Policy#

The DefaultBGPPeer resources that the DefaultRouteReflector creates towards each selected DefaultRouteReflectorClient inherit import/export policies from the assigned DefaultBGPGroup. This behavior can be overridden by specifying policies in the DefaultRouteReflector. Click here for more information on BGP import/export policies.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: DefaultRouteReflector
metadata:
  labels:
    rr-label: rr
  name: example-route-reflector
  namespace: eda
spec:
  clientSelectors:
    - rr-label=client
  clusterID: 10.100.0.1
  defaultBGPRRGroup: example-default-group
  interface: spine-1-loopback
  interfaceKind: DefaultInterface
  ipv4Unicast:
    enabled: true
cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: DefaultRouteReflector
metadata:
  labels:
    rr-label: rr
  name: example-route-reflector
  namespace: eda
spec:
  clientSelectors:
    - rr-label=client
  clusterID: 10.100.0.1
  defaultBGPRRGroup: example-default-group
  interface: spine-1-loopback
  interfaceKind: DefaultInterface
  ipv4Unicast:
    enabled: true

EOF

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.

DefaultRouteReflector

protocols.eda.nokia.com / v2

SPEC

DefaultRouteReflector enables the configuration of iBGP sessions to RouteReflectorClients. It includes settings for the DefaultInterface, BGP group, client selectors, and the Cluster ID. Additionally, it allows for the configuration of L2VPN EVPN settings and applies common BGP configuration settings to manage routing efficiently within the network.

  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #

STATUS

DefaultRouteReflectorStatus defines the observed state of DefaultRouteReflector

  • #
  • #
  • #
  • #
  • #
  • #
  • #