The next attribute is the aggregator attribute. And as we already mentioned when we talked about how to generate an aggregate in BGP, the aggregator attribute is set really to indicate the IP address of the router or the BGP speaker which generates the aggregate route. This attribute is optional but when it is set, it's transitive. As I was saying before, not so many operators these days will actually use the aggregator attribute, as they will generate aggregates in many parts of their network using some of the alternative methods that I mentioned. It has been and is useful for debugging purposes, and that's really it's only use, for doing debugging. It doesn't influence the best path selection and it's generally otherwise not used by BGP itself. So when we generate the aggregate using the `aggregate-address` command in Cisco IOS, this will set the aggregator attribute to the IP address of the router generating the aggregate.
© Produced by Philip Smith and the Network Startup Resource Center, through the University of Oregon.
Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
This is a human-readable summary of (and not a substitute for) the license. Disclaimer. You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. NonCommercial — You may not use the material for commercial purposes. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.