.. _example_protocols_bgp_address-family_ipv6-unicast_aggregate-address_aggregate-address:

#################
Aggregate-Address
#################


.. sidebar:: Contents

  .. contents::
    :depth: 2
    :local:

Scenario to verify BGP **address-family ipv6-unicast aggregate-address** configuration
with different options: **basic**, **summary-only**, **route-map**, and **origin**
(igp/egp/incomplete).

Route aggregation allows a router to advertise a single summary IPv6 route (e.g., /32)
that covers multiple more-specific routes (e.g., /64s). The behavior varies based
on the configured options:

- **Basic** (no options): Both the aggregate route and the specific routes are
  advertised to neighbors. The aggregate has origin **incomplete** (?) by default.

- **summary-only**: Only the aggregate route is advertised; the more-specific
  routes are suppressed and NOT sent to neighbors.

- **route-map**: Applies a route-map to the aggregate route to modify its
  attributes (e.g., setting MED/metric). The specific routes are unaffected.

- **origin igp/egp/incomplete**: Sets the BGP origin code for the aggregate route.
  By default it is **incomplete** (?). Setting it to **igp** (i) or **egp** (e)
  changes the origin attribute, which influences BGP path selection (igp > egp >
  incomplete).

Each option is tested with both iBGP (same AS) and eBGP (different AS) sessions.
The topology uses DUT0 with three dummy interfaces (dum0, dum1, dum2) providing
/64 routes that are aggregated into a /32 summary.

*******************************
Test BGP IPv6 Aggregate Address
*******************************

Description
===========

Test aggregate-address options across iBGP and eBGP: basic (aggregate + specifics),
summary-only (aggregate only), route-map (attribute modification on aggregate),
and origin variants (igp, egp, incomplete).

Scenario
========

.. include:: aggregate-address/testbgpipv6aggregateaddress

.. raw:: html

  <hr>