In the world of enterprise networking, Border Gateway Protocol (BGP) plays a critical role in ensuring scalable and reliable routing between autonomous systems. Whether you’re building a lab, preparing for certifications, or deploying BGP in a production environment, understanding how to configure and optimize BGP is essential.
In this post, we’ll walk through a simple yet insightful Cisco BGP configuration example. We’ll explore how to advertise networks, use loopback interfaces, and implement route summarization using the aggregate-address command. This hands-on example will help demystify BGP behavior and give you a solid foundation for more advanced scenarios.
Interface
Configuration
- This sets up a loopback interface with a
/32 address (host route). - Commonly used as a router ID or for stable
BGP peering.
- This is a physical interface with a /24
subnet, likely used for external connectivity.
🌐 BGP Configuration
Key Points:
- AS Number: 65001 (Private ASN)
- network statements: These advertise the specified networks
into BGP only if they exist in the routing table. - aggregate-address:
- This creates a summarized route: 10.1.0.0/16.
- The summary-only keyword suppresses the
more specific routes (10.1.1.0/24 and 10.1.2.0/24) from being
advertised. - Only the aggregate route will be
advertised to BGP peers.
✅ Validation
For the aggregate-address to
be advertised:
- At least one of the more specific routes
(e.g., 10.1.1.0/24, 10.1.2.0/24) must exist in
the routing table. - The summary-only ensures that
only the summarized route (10.1.0.0/16) is sent to peers, not the
individual /24s.