Now we're going to talk about separation of iBGP versus eBGP. Many ISPs do not understand the importance of separating iBGP and eBGP. Remember that iBGP is where all customer prefixes are carried. eBGP is used for announcing aggregates to the internet and for traffic engineering. Do not do traffic engineering with customer originated iBGP prefixes, as this leads to instability to that mentioned in the earlier bad example. Even though the aggregate is announced, a flapping subprefix will lead to instability for the customer concerned. Traffic engineering prefixes should always be generated on the border routers.

© 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.