Skip to content

Default BGP Peer#

Underlay Routing → DBDefault BGP Peers

The DefaultBGPPeer resource is in many ways similar to the BGPPeer 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. This resource is used when setting up a BGP session between two IP addresses in the default VRF. It represents a single participant in the BGP session, so if both sides of the BGP session are managed by EDA, two of these resources will need to be created.

Explicit vs implicit target IP

The source IP address of the default BGP peer is always inferred from the SystemInterface or DefaultInterface it is linked to. The target IP address can either be explicitely configured, or implicitely inferred from the neighboring SystemInterface or DefaultInterface.

If the BGP neighbor is managed by EDA and also in the default VRF, you should avoid using explicit IPs.

To set up BGP peers in Router services, use BGPPeer instead.

Dependencies#

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

Referenced resources#

DefaultBGPGroup#

A DefaultBGPPeer is always linked to a single DefaultBGPGroup. In real-world networks, multiple BGP peers share common parameters, such as BGP import and export policies, local and peer autonomous system numbers, and BGP timers. These parameters can be specified in the group instead, allowing the operator to change these settings in a single location for all linked default BGP peers. All settings in the group can optionally be overridden in the individual peer resources. Configuration inheritance works as follows:

graph LR
    A[DefaultBGPPeer] -->|overrides| B
    B[DefaultBGPGroup] -->|overrides| C
    C[DefaultRouter]

    B[DefaultBGPGroup resource]
    C[DefaultRouter resource]

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 DefaultBGPPeer.

This resource type can also be configured as the target of a DefaultBGPPeer, meaning the BGP session will be reconfigured with the new neighbor IP address if the target SystemInterface is changed.

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 DefaultBGPPeer.

This resource type can also be configured as the target of a DefaultBGPPeer, meaning the BGP session will be reconfigured with the new neighbor IP address if the target DefaultInterface is changed.

Policy#

Routing policies can be specified in various locations of the DefaultBGPPeer resource. These policies are used to filter or modify BGP routes sent/received by this DefaultBGPPeer. If no policies are configured, the default behavior for the router on which the DefaultBGPPeer is configured is followed, which may be different depending on the operating system.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: DefaultBGPPeer
metadata:
  name: example-bgp-peer-leaf1-spine1
  namespace: eda
spec:
  dynamicNeighbor: false
  group: example-default-group
  interface: leaf-1-loopback
  interfaceKind: DefaultInterface
  peerInterface: spine-1-loopback
  peerInterfaceKind: DefaultInterface
cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: DefaultBGPPeer
metadata:
  name: example-bgp-peer-leaf1-spine1
  namespace: eda
spec:
  dynamicNeighbor: false
  group: example-default-group
  interface: leaf-1-loopback
  interfaceKind: DefaultInterface
  peerInterface: spine-1-loopback
  peerInterfaceKind: DefaultInterface
EOF

Custom Resource Definition#

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

DefaultBGPPeer

protocols.eda.nokia.com / v2

SPEC

DefaultBGPPeer enables the configuration of BGP sessions within a DefaultRouter. It allows specifying a description, a DefaultInterface reference, and the peer IP address. The resource also supports dynamic neighbors, common BGP settings, and peer-specific configurations.

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

STATUS

DefaultBGPPeerStatus defines the observed state of DefaultBGPPeer

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