Aggregate Route#

Virtual Networks → ARAggregate 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.

To set up aggregate routes in the default VRF, use DefaultAggregateRoute instead.

Dependencies#

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

• The Router in which the static route will be configured

Referenced resources#

Router#

Aggregate route prefixes configured in the AggregateRoute resource are only configured in the VRF of the linked Router resource. Note that the aggregate route is only installed and becomes active if at least one more specific route installed in the VRF 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 Router is configured on.

Examples#

apiVersion: protocols.eda.nokia.com/v2
kind: AggregateRoute
metadata:
  name: ospf-hierarchy-aggregate-route
  namespace: eda
spec:
  nodes:
    - leaf-1
  prefixes:
    - 10.0.0.0/22
  router: ospf-hierarchy-router

cat << 'EOF' | kubectl apply -f -
apiVersion: protocols.eda.nokia.com/v2
kind: AggregateRoute
metadata:
  name: ospf-hierarchy-aggregate-route
  namespace: eda
spec:
  nodes:
    - leaf-1
  prefixes:
    - 10.0.0.0/22
  router: ospf-hierarchy-router
EOF

Custom Resource Definition#

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