Previously, we set up a simple two-router lab using both iBGP and eBGP, and we also demonstrated how to verify them. Now, we'll explore how eBGP and iBGP work together to exchange routes between different Autonomous Systems (ASes), highlighting their combined role in interconnecting more complex networks.
This three-router topology connects three ASes:
Configured Router0 to run BGP in AS 5110, establish an external BGP peering with neighbor 192.168.158.51 (AS 2640), and advertise two networks—50.50.50.0/24 and 80.80.0.0/16—into the BGP domain.
Router1 is running BGP in AS 2640. It peers externally with Router0 in AS 5110 at 192.168.158.49, and internally with another router in the same AS (192.168.74.14).
Router2 is running BGP in AS 2640 and is set up for an iBGP peering with the neighbor at 192.168.74.43.
Note:
This configuration assumes that synchronization and auto-summary are disabled.
If the BGP session is established but routes are not behaving as expected, add the following commands under the BGP configuration on each router:
After configuration, verify BGP peering, advertised routes, and routing table entries.
Expected output should show neighbors as Established.
Check if Router0 is advertising 50.50.50.0/24 and 80.80.0.0/16.
Router1 should learn 50.50.50.0/24 and 80.80.0.0/16 via Router0.
Ensure BGP routes are installed.
Try advertising Loopback1 from Router2 and ensure it is received by Router0 via eBGP.
Verify your configuration using: