Configuring BGP4+ Route Aggregation

By configuring route aggregation, you can reduce the size of the routing table of a peer. BGP4+ supports automatic aggregation and manual aggregation. Procedure

Procedure

Access the system view.
system-view
Access the BGP view.
bgp { as-number-plain | as-number-dot }
Access the BGP IPv6 unicast address family view.
ipv6-family [ unicast ]
Configure manual route aggregation.
aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy route-policy-name3 ] ^*

Manual aggregation is valid for the routing entries in the local BGP4+ routing table. For example, if 9:3::1/64 does not exist in the BGP routing table, BGP4+ does not advertise the aggregated route even after the aggregate 9:3::1 64 command is run to aggregate this route.

When configuring manual aggregation of routes, you can apply various routing policies and set the route attributes.