This table is used to control how DC-BGP aggregates addresses. Each entry in the table results in one aggregate address being created. This will result in an aggregate entry in the routing table when at least one more specific route matching the address specified is learnt. If the aggregate is marked as 'permanent', then an aggregate entry is created in the routing table even if no more specific matching routes are known. The options allow configuration as to whether the AS_PATH attribute keeps full information or not, and whether the more specfic route is also entered in the routing table (the summary only option). These options can also be chosen on a per route basis by matching on the advertise and suppress route maps. The attribute route map is used to set attributes of the aggregated route if required. It is possible to create overlapping entries in the table. This can result in routes that match more than one table entry. - If a route matches multiple aggregate addresses, then it is suppressed any of the matching aggregates would cause the route to be suppressed. - If a route matches the advertise map of an aggregate address, then it is not aggregated by that aggregate address. However, it may still be aggregated by other overlapping aggregate addresses.