Not sure if you are allowed to aggregation a prefix generated from another AS out of your AS!!!. If yes then the received routes you can aggregated on the router as long as the route is the in the BGP table. By aggregating a prefix without the as-set, the prefix will appear as generated locally without AS attribute in the aggregated routes advertised out to other peers.
What we suggested will work "BUT BE VERY CAREFUL". If the prefixes belongs to the local AS you are aggregating from, then no problem. When the summarise prefixes learned from other ASes, information hiding may result in a routing loops. By removing AS_PATH attibute and replacing with empty list will prevent BGP loop-detection mechanism from working properly.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...