BGP Aggregate AS-SET

Hello David

Yes, this is to be expected as you suggest.

In this case it is retained, because you are using the as-set keyword. And since the route contained within the summary comes from a single eBGP peer, it has a single AS path and not multiple ones as shown in the lesson with the curly brackets or braces “{ }”.

I’m not quite sure where your concern is. The only thing that I find strange in the output of your BGP table is the existence of AS number 8, which I don’t see in the topology.

In the first example, the as-set keyword was not used, and that is why the AS path information was removed.

If I have misunderstood your query, please clarify and let me know.

I hope this has been helpful!