Scribd
Upload
167 views

BGP Basics PDF

BGP is a path vector routing protocol that runs over TCP. It is used to exchange routing and reachability information between autonomous systems (AS). BGP uses TCP to establish connections between BGP peers before exchanging routing updates. BGP speakers use internal BGP (iBGP) to share routes within an AS and external BGP (eBGP) to share routes between ASes. BGP messages include Open, Update, Notification and Keepalive messages to establish and maintain BGP sessions.

Uploaded by

kyawzinmon
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
167 views

BGP Basics PDF

BGP is a path vector routing protocol that runs over TCP. It is used to exchange routing and reachability information between autonomous systems (AS). BGP uses TCP to establish connections between BGP peers before exchanging routing updates. BGP speakers use internal BGP (iBGP) to share routes within an AS and external BGP (eBGP) to share routes between ASes. BGP messages include Open, Update, Notification and Keepalive messages to establish and maintain BGP sessions.

Uploaded by

kyawzinmon
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

BGP Fundamentals

Border Gateway Protocol - BGP


• Runs over TCP (port 179)
– TCP connection required before BGP session
– Need to be reachable!

• Path vector routing protocol


– Best path selection based on path attributes
– Route: destination and the attributes of the path to reach
the destination

• Incremental BGP updates

2
Internal & External BGP
• eBGP used to:
– Exchange networks/routes between ASes
• Aggregates and sub-aggregates

– Implement routing policies


• To manipulate inbound and outbound traffic

• iBGP is used to:


– Carry customer networks/prefixes
– Internet routes (some or all) across the AS backbone

3
BGP Message Types
• Open:
– After a TCP connection has been established between two
BGP routers, an Open message is sent
• Once the open message is confirmed (keepalive), the BGP session is
established – become BGP peers/neighbors!

– Contains:
• Sender’s ASN
• BGP version
• BGP router ID
• Hold-time (3 x keepalive interval)

4
BGP Message Types
• Keepalive:
– Exchanged initially to acknowledge Open messages
– Exchanged periodically (60 secs) to maintain BGP session
• Dataless packet

• Update:
– BGP peers exchange network information through Update
messages
• One update for each path!

– Contains:
• Withdrawn routes – no more reachable
• Path attributes – attributes for this path to reach the destinations
specified by the NLRI
• NLRI – list of networks reachable through this path <prefix, length>

5
BGP Message Types
• Notification:
– Sent when an error condition is detected
– The BGP session is torn down immediately!
– Contains:
• Error code
• Error sub-code
• Data related to error

6
BGP Neighbor States
• A BGP router goes through six different states
– Idle
• The router is looking for a route to its neighbor

– Connect
• BGP router moves from Idle to Connect state if it has found a route to its
neighbor, and has started the 3-way TCP handshake
• If the 3-way handshake is complete, sends an Open message

– Active
• A router transitions to Active state if the initial 3-way handshake was not
successful
• Initiates a new 3-way handshake
• If the 3-way handshake is complete, sends an Open message
• Else, falls back to Idle

7
BGP Neighbor States
• A BGP router goes through six different states
– Open Sent
• An Open message has been sent to the neighbor
• If it receives a keepalive, moves to Open Confirm, else back to Active

– Open Confirm
• Has received an acknowledgment for its Open message, and is waiting
for the initial keepalive
• If it receives the intial keepalive, transitions to Established

– Established
• The BGP neighbor relationship (session) is established!
• Routing information can now be exchanged

8
BGP Neighbor Relationship
• eBGP neighbors/peers
– BGP session established between routers in different ASes
– Generally directly connected!
• Session established using directly connected intf IP
• Peering address must match the TCP session!

– Else, we need a static route to reach the neighbor and


change the eBGP TTL value (default 1)

router bgp 17821


neighbor 172.16.12.2 remote-as 65000
1 7 2 .1 6 .1 2 .0 / 3 0
!
AS AS address-family ipv4
.1
17821 65000 neighbor 172.16.12.2 activate
.2
!

9
BGP Neighbor Relationship
• iBGP neighbors/peers
– BGP session established between routers within the same AS

– Does not need to be directly connected


• IGP ensure reachability (TCP connection)
– Generally using loopback addresses

AS 17821 router bgp 17821


neighbor 10.10.10.2 remote-as 17821
!

10
iBGP Operation
• iBGP routers must:
– Originate directly connected routes

– Carry routes learned from outside the AS to all routers


within the AS
• Fully-meshed instead of redistributing!
• Advertise routes learned from eBGP peers to all iBGP peers!

– To prevent routing loops (in a fully-meshed network)


• iBGP routers are not allowed to advertise iBGP learned routes to other
iBGP peers!

11
iBGP full-mesh

AS R4 router bgp 17821


17821 neighbor 10.10.10.2 remote-as 17821
neighbor 10.10.10.3 remote-as 17821
R1 R3 neighbor 10.10.10.4 remote-as 17821
!

R2

12
Sourcing iBGP from Loopback
• By default, routers use the exit-interface address as
the source address for locally originated packets
(updates)
– If the BGP TCP session was established using any other
interface (loopbacks) addresses, the source address for BGP
updates must match!

• The update-source loopback command achieves this

router bgp 17821


neighbor 10.10.10.1 remote-as 17821
neighbor 10.10.10.1 update-source loopback 0
!

13
Advertising Networks in BGP
• The network statement
– allows BGP to inject routes into BGP table and advertise to
neighbors only if it already exists in the routing table!
router bgp 17821
address-family ipv4 unicast
network <prefix> mask <subnet-mask>
address-family ipv6 unicast
network <prefix/length>

• BGP “Synchronization Rule”:


– iBGP learned routes should not be installed in the routing
table nor advertised to eBGP peers unless the route was
learned through an IGP first!
• Prevents black-hole routes!

14
How it all works?

eBGP eBGP

iBGP iBGP iBGP

IGP IGP IGP

AS 111 AS 222 AS 333

Barry Greene & Philip Smith “Cisco ISP Essentials”

15
Acknowledgement:
• Philip Smith
• Cisco Systems

16
17

You might also like