Bgp Routing Protocol Diagram Notation: a Visual Guide

When you're staring at a network diagram filled with AS numbers, peering lines, and route advertisements, the symbols can feel like a foreign language. BGP routing protocol diagram notation is the visual shorthand network engineers use to map out how autonomous systems exchange routing information across the internet. Understanding this notation isn't just academic it's the difference between confidently reading a network topology and guessing what each line and label means during troubleshooting or design reviews.

What Does BGP Diagram Notation Actually Represent?

BGP (Border Gateway Protocol) is the protocol that makes internet routing possible. It manages how data packets travel between autonomous systems (AS) large networks operated by ISPs, enterprises, or cloud providers. When engineers draw BGP diagrams, they use specific symbols and conventions to show these relationships.

A typical BGP diagram includes these core elements:

Autonomous System (AS) – Represented as a cloud or rounded rectangle, labeled with a unique AS number (ASN) like AS64512 or AS3356.
BGP routers/peers – Shown as circles or rectangles inside or at the border of an AS. These represent the devices running BGP sessions.
eBGP peering links – Lines connecting routers in different autonomous systems. These are typically drawn as solid lines with arrows indicating the direction of route advertisement.
iBGP peering links – Lines connecting routers within the same AS. Often shown as dashed lines or a different color to distinguish them from external peers.
Route advertisements – Indicated by arrows with labels showing the prefix being advertised (e.g., 192.0.2.0/24) or AS_PATH attributes.
AS_PATH notation – A sequence of AS numbers shown in curly braces or parentheses along a link, like {AS64512, AS64513}, representing the path a route has traversed.

Why Do Engineers Need to Read BGP Diagrams?

Network engineers encounter BGP diagrams during capacity planning, troubleshooting routing loops, designing multi-homed connections, and during security audits. If you've ever worked with a provider asking for a "network diagram with AS numbers" before provisioning a circuit, you already know why this notation matters.

BGP diagrams help answer questions like: Which upstream providers does this network use? Where does traffic from AS X reach AS Y? Are there redundant paths for failover? Without understanding the notation, you're working blind.

This is similar to how understanding TCP/IP protocol diagram codes gives you a foundation for reading other types of network diagrams. BGP notation builds on those basics but adds the AS-level perspective.

How Are eBGP and iBGP Sessions Shown in Diagrams?

One of the most common points of confusion is how diagrams distinguish between external BGP (eBGP) and internal BGP (iBGP) sessions. Here's how they typically differ:

External BGP (eBGP) Sessions

Shown as lines crossing the AS boundary
Usually a solid, thicker line
Labeled with the AS numbers on each end
Arrows indicate route advertisements between autonomous systems
The typical TTL for eBGP is 1, so peers are usually directly connected (one hop away)

Internal BGP (iBGP) Sessions

Shown as lines inside a single AS boundary
Often a dashed or dotted line
May show a full mesh, route reflector hierarchy, or confederation structure
Labels may include router IDs (e.g., RID 10.0.0.1) rather than AS numbers
iBGP peers do not need to be directly connected

Understanding this distinction matters because eBGP and iBGP behave very differently eBGP modifies NEXT_HOP and prepends AS_PATH, while iBGP does not re-advertise routes learned from one iBGP peer to another (unless using route reflectors).

What Do the Common Symbols and Labels Mean?

Here's a quick reference for the notation you'll see most often:

AS Number in a circle/cloud – Identifies the autonomous system. Public ASNs range from 1 to 64511 (16-bit) and 131072 to 4199999999 (32-bit). Private ASNs range from 64512 to 65534.
Arrow direction – Indicates the direction of route advertisement. A bidirectional arrow means both peers exchange routes. A single arrow shows that one side advertises to the other.
Prefix labels – CIDR notation (e.g., 10.0.0.0/8) along a link showing what network is being advertised.
Weight/Local Preference values – Sometimes annotated near peering links to show administrative preference for path selection.
MED (Multi-Exit Discriminator) – A numeric value shown near an eBGP link indicating the preferred entry point into an AS.
Community strings – Shown as tags or labels like "65000:100" near route advertisements.
Route reflector symbol – A router marked with "RR" inside the symbol, with client connections shown as lines with a specific marker.

These notations overlap with concepts used in OSPF and EIGRP network diagram comparisons, but BGP adds the AS-level view that those IGPs don't have.

How Do You Read a Multi-Homed BGP Diagram?

A multi-homed setup means a single AS connects to two or more upstream providers. In the diagram, you'll see one AS at the center with separate links to different ISP AS clouds. Here's how to read it step by step:

Identify the customer AS – Usually a smaller cloud or rectangle with a private or public ASN.
Find the upstream AS connections – Two or more lines leaving the customer AS to different ISP AS numbers.
Check the prefix advertisements – The customer AS typically advertises its own prefixes to both providers. Look for labels like "advertising 203.0.113.0/24."
Note path preferences – Some links may show "AS_PATH prepend x3" or "LP=200" indicating traffic engineering.
Look for backup links – A dashed secondary link often represents a failover path with a less preferred metric.

This is where understanding network protocol flow diagram codes becomes useful, since BGP multi-homed designs use similar directional and redundancy conventions.

What Mistakes Do People Make When Reading BGP Diagrams?

Confusing iBGP and eBGP lines – Assuming every line between routers is an eBGP session. If both routers are in the same AS, it's iBGP, and the behavior is very different.
Ignoring AS_PATH direction – AS_PATH is read from right (most recent AS) to left (origin AS). A path shown as "65000 65001 65002" means the route originated in AS65002 and passed through AS65001 before reaching AS65000.
Assuming all advertised routes are accepted – Diagrams don't always show import/export policies. Just because a prefix is advertised doesn't mean the receiving router installs it in its RIB.
Overlooking route reflectors – In larger iBGP topologies, the full mesh of sessions may not be drawn. Instead, route reflector relationships are shown. Missing this gives you a wrong picture of how routes propagate.
Mixing up NEXT_HOP with peering address – The NEXT_HOP attribute shown on a diagram may differ from the actual BGP peer address, especially in eBGP multihop or third-party NEXT_HOP scenarios.

What Does a Real BGP Diagram Look Like in Practice?

Consider a typical enterprise with dual ISP connectivity:

Enterprise AS 65200 connects to ISP-A AS 174 (Cogent) and ISP-B AS 3356 (Lumen).
The enterprise advertises 198.51.100.0/24 to both providers.
Primary traffic flows through ISP-A (shown with a thicker line or "LP=200" label).
ISP-B is the backup (shown with a dashed line or "LP=100" label).
AS_PATH prepending is applied on the ISP-B link to make it less preferred for inbound traffic.
Both ISPs receive the prefix but traffic engineering determines which path external networks use to reach the enterprise.

This kind of diagram tells you at a glance: the AS owns the prefix, it has two exit points, and it prefers one over the other.

How Can You Draw Your Own BGP Diagrams?

When creating BGP diagrams for documentation, change requests, or provider submissions, keep these tips in mind:

Always label AS numbers – Don't leave clouds or boxes blank. Include both the ASN and a description (e.g., "AS 65200 – Corp HQ").
Use different line styles – Solid for eBGP, dashed for iBGP. This prevents confusion at a glance.
Show route advertisements with arrows – Don't assume readers know which direction prefixes flow.
Include prefix information – Label the advertised networks on the relevant links.
Note traffic engineering details – AS_PATH prepends, local preference, MED, and community tags should appear as annotations.
Mark route reflectors clearly – Use "RR" labels and show the client-RR relationship.
Keep it consistent – Use the same symbol style throughout your diagram for routers, AS clouds, and link types.

Tools like draw.io (now diagrams.net), Visio, Lucidchart, and even simple ASCII diagrams work well. The key is consistency and completeness.

Useful Checklist for Reading Any BGP Diagram

✅ Identify all autonomous systems and their AS numbers
✅ Distinguish eBGP links (crossing AS boundaries) from iBGP links (within one AS)
✅ Check arrow directions to understand route advertisement flow
✅ Look for AS_PATH, MED, local preference, and community annotations
✅ Identify route reflectors and their client relationships
✅ Note any traffic engineering hints (prepends, weight, filtering)
✅ Verify which prefixes are being advertised and to whom
✅ Look for redundant/backup paths and how failover is indicated

Start by drawing your own network's BGP topology from scratch using your router configurations. Check your running config for show bgp summary and show ip bgp neighbors output, and map what you see onto a diagram. The hands-on practice of connecting config output to diagram notation is the fastest way to build real fluency with BGP diagrams.