Configuring route summarization can reduce the size of a routing table on a peer.
On a large-scale BGP4+ network, configuring route summarization can reduce the number of advertised route prefixes and improve BGP4+ stability.
The system view is displayed.
The BGP view is displayed.
The IPv6 unicast address family view is displayed.
To advertise all summary routes and specific routes, run the aggregate ipv6-address { mask | mask-length } command.
To advertise only summary routes, run the aggregate ipv6-address { mask | mask-length } detail-suppressed command.
To advertise some of the specific routes, run the aggregate ipv6-address { mask | mask-length } suppress-policy route-policy-name command.
Using the peer route-policy command can also advertise some of the specific routes.
To generate a summary route used for loop detection, run the aggregate ipv6-address { mask | mask-length } as-set command.
To configure the attributes of summary routes, run the aggregate ipv6-address { mask | mask-length } attribute-policy route-policy-name command.
Using the peer route-policy command can also configure the attributes of summarized routes.
If as-set is configured in the aggregate command, the AS_Path attribute configured in the apply as-path command does not take effect.
To generate summary routes based on some of the specific routes, run the aggregate ipv6-address { mask | mask-length } origin-policy route-policy-name command.
Manual route summarization is valid for the routing entries that exist in the local BGP4+ routing table. For example, if the aggregate 2001:db8::1 64 command is run to summarize routes, but no route with a mask length greater than 64 (for example, 2001:db8::1/128) exists in the BGP4+ routing table, BGP4+ does not advertise the summary route.
The configuration is committed.