PART 1 · BASIC BGP THEORY · MODULE A
Module A – BGP Fundamentals
Lesson content presented from the approved Part 1 master documentation.
Module A – BGP Fundamentals
Border Gateway Protocol (BGP) is the inter-domain routing protocol used to exchange reachability information between Autonomous Systems (ASes). BGP-4 is specified in RFC 4271 and uses TCP port 179. BGP is a path-vector protocol: routes carry attributes, including AS_PATH, that support policy decisions and loop prevention.
Why BGP is used
Interconnect separate autonomous systems across service-provider and enterprise networks.
Support multihoming and redundant Internet or WAN connectivity.
Apply routing policy and influence inbound/outbound traffic paths.
Scale inter-domain routing without relying on a single interior gateway protocol.
Control plane and data plane
The BGP control plane exchanges reachability and path attributes and selects routes.
The routing information base (RIB) contains routes selected by routing processes.
The forwarding plane uses installed forwarding information to move packets. A BGP session being Established does not guarantee a prefix is installed or traffic is forwarding.
BGP compared with an IGP
BGP runs over TCP port 179; OSPF uses IP protocol number 89.
BGP is policy-oriented and designed for inter-AS routing; IGPs are commonly used for routing within an AS.
BGP peers are explicitly configured; it does not discover neighbours using OSPF-style Hello packets.
BGP message types and states
Four principal message types: OPEN, UPDATE, NOTIFICATION and KEEPALIVE.
Six FSM states: Idle, Connect, Active, OpenSent, OpenConfirm and Established.
Route and path concepts
A prefix identifies a destination network.
A BGP route includes path attributes such as AS_PATH, NEXT_HOP and ORIGIN.
AS_PATH records AS traversal and is used for loop prevention; policy attributes influence route selection.
Core verification commands
show ip bgp summary
show ip bgp
show ip route bgp
show ip bgp neighbors
show running-config | section router bgp
show tcp brief
Senior Network QA test ideas
Verify TCP/179 reachability and neighbour configuration.
Introduce an incorrect remote-AS value and verify the session does not establish.
Withdraw an advertised prefix and verify route removal propagates.
Flap a peering interface and observe session recovery and route convergence.
Confirm that BGP session establishment and route installation are tested separately.
| Key takeaway BGP exchanges and evaluates reachability information; an Established session alone does not prove that a route is selected, installed or forwarding. |
|---|
Source and assessment noteTechnical explanations, tables, examples, QA scenarios and assessments are presented from the approved Part 1 master documentation. Verify illustrative CLI syntax against the target router platform and software release before lab or production use.