Skip to content

Default Aggregate Route#

Underlay Routing → DADefault Aggregate Routes

Aggregate routes are - as the name implies - routes that aggregate one or more active routes into an encompassing prefix. They are used to reduce the number of routes advertised to BGP peers. The following diagram illustrates the concept of aggregate routes:

graph LR
    A[10.0.1.0/24
    Static route]       --> C

    B[10.0.2.0/24
    BGP route]          --> C
    A                   -->|installed in| D

    C[10.0.0.0/22
    Aggregate route]    -->|installed in| D
    B                   -->|installed in| D

    D[Routing Table]

In the example above 10.0.1.0/24 is a static route, and 10.0.2.0/24 is received via the BGP protocol. Both routes are valid and installed in the same routing table. The aggregate route is also installed in the routing table, as at least one route in subnet 10.0.0.0/22 is installed in the routing table.

All three routes are advertised to other BGP peers, unless the property summaryOnly property is set to true: in this case only the aggregate route 10.0.0.0/22 is advertised.

Non-matching traffic

Traffic towards an IP that matches the aggregate route, but not a more specific route, is blackholed. In our example, the node would attract traffic for destination IP 10.0.3.123, but would discard the packet when it arrives.

To set up aggregate routes in the overlay, use AggregateRoute instead.

Dependencies#

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

Referenced resources#

DefaultRouter#

Aggregate route prefixes configured in the DefaultAggregateRoute resource are only configured in the VRF of the linked DefaultRouter resource. Note that the aggregate route is only installed and becomes active if at least one more specific route is installed in the default routing table.

TopoNode#

Optionally, a list of nodes can be provided on which the aggregate route is configured. If no nodes are specified, EDA will deploy the aggregate route on ALL nodes that the DefaultRouter is configured on.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: DefaultAggregateRoute
metadata:
  namespace: eda
  name: my-aggregate-route
spec:
  prefixes:
    - 10.0.0.0/24
  defaultRouter: router-leaf-1
  summaryOnly: true
cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: DefaultAggregateRoute
metadata:
  namespace: eda
  name: my-aggregate-route
spec:
  prefixes:
    - 10.0.0.0/24
  defaultRouter: router-leaf-1
  summaryOnly: true
EOF

Custom Resource Definition#

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

DefaultAggregateRoute

protocols.eda.nokia.com / v2

SPEC

DefaultAggregateRoute allows the configuration of aggregate routes on a DefaultRouter. It includes specifying destination prefixes, the DefaultRouter, and settings for generating ICMP unreachable messages or blocking route advertisement. Additionally, it configures the aggregator’s IP address and ASN for efficient route management.

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

STATUS

DefaultAggregateRouteStatus defines the observed state of DefaultAggregateRoute