BGP

BGP
© 2012 Juniper Networks, Inc. All rights reserved. | www.juniper.net

BGP Review
 BGP is the core routing protocol within the Internet
BGP is a path-vector BGP views the Internet as a
protocol used for collection of autonomous
interdomain routing. systems.
AS 65502
BG
P P
BG
AS 65501 BGP AS 65504
BG
P P
BG
AS 65503
Note: BGP Is an Internet Engineering Task Force standard defined in RFC 4271
(supersedes RFC 1771).
© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 2
BGP Usage
 BGP is typically used in large enterprise environments
where multiple ISP connections exist, and in all service
provider environments
ISP A
AS 65502
Customer A
BG
P Single-homed customers
typically use a default route
AS 65501 BGP to the Internet.
Customer B
BG
P
Static Routing
AS 65503
Multihomed customers use
BGP to control inbound and ISP B
outbound traffic.
BGP Peers
 BGP peers can reside in different ASs or the same AS

• Peers in different ASs use the external session type (EBGP)
• Peers in the same AS use the internal session type (IBGP)
AS 65502
IBGP is not used
because a single BGP IBGP is used because
speaker exists. IGP
multiple BGP speakers
IBGP exist.
EB
P G
B G P
E
IGP EBGP IGP
EB
G
P BGP
AS 65501 E AS 65504
IGP
IBGP
AS 65503
BGP Peering Sessions
 BGP peering sessions are manually defined and rely on
TCP connections
• No automatic neighbor discovery
BGP Neighbor States

TCP Connectivity BGP Connectivity
Idle OpenSent
Connect OpenConfirm
Active Established
R1 R2
TCP Connectivity
BGP Connectivity
Established Neighbors

BGP Message Types
 BGP messages are used to establish and maintain BGP
peering sessions
• All BGP messages use a common header
BGP Message Types

Open Keepalive
Update Notification
Refresh
R1 R2
TCP Connectivity
BGP Connectivity
Established Neighbors

BGP Update Messages
 BGP update messages include path advertisements and
their associated attributes
• Can also list withdrawn routes that are no longer reachable
Router compares attributes

associated with update messages to
select the best path
R1 Route X R2 Route X R3
Established Neighbors Established Neighbors

BGP Attributes
 BGP attributes are included in the update messages and
describe the BGP prefixes received from a peer
• Attributes are used to select the best path
Route X Route X
R1 R2 R3
Established Neighbors Established Neighbors
• Some common examples include:
Common BGP Attributes

Next
Local Preference AS Path Origin MED Community
Hop

High-Level BGP Operation
ISP B
(AS 65002)
ISP A ISP C
(AS 65001) (AS 65003)
Static default
route to ISP A
Static route to Customer A
Customer A is single-homed to ISP A and uses Customer B

Customer A 172.20.21.0/24 subnet, which was assigned by (AS 65501)
ISP A

ISP A’s Network
I can reach
172.20.0.0/16
R3
ISP A R2 R4
(AS 65001)
R1
Customer A I can reach

Static route for 172.20.21.0/24 172.20.21.0/24
to Customer A
Note: All BGP routes start as something other than BGP routes.

ISP A’s Aggregate
172.20.0.0/16 is reachable through AS
65002 and AS 65001
172.20.0.0/16 is reachable
172.20.0.0/16 is reachable through AS 65003, AS 65002
ISP B and AS 65001
through AS 65001
(AS 65002)
ISP A ISP C
(AS 65001) (AS 65003)
ISP A advertises an aggregate

of 172.20.0.0/16 through BGP
to ISP B
Customer B
Customer A (AS 65501)

Customer B’s Aggregate
172.31.128.0/20 is reachable through
AS 65002, AS 65003 and AS 65501
172.31.128.0/20 is reachable
ISP B through AS 65003 and
(AS 65002) AS 65501
ISP A ISP C
(AS 65001) (AS 65003)
172.31.128.0/20 is
reachable through
Default Static Route AS 65501
Customer B advertises its Customer B

Customer A 172.31.128.0/20 network (AS 65501)
through BGP to ISP C

Customer B Connects to ISP B
ISP B chooses the best path and
advertises only that path
172.31.128.0/20 is reachable through 172.31.128.0/20 is reachable through

AS 65002 and AS 65501 ISP B AS 65003 and AS 65501
(AS 65002)
ISP A ISP C
(AS 65001) (AS 65003)
172.31.128.0/20 is
reachable through
AS 65501
Default Static Route
Customer B advertises its Customer B

Customer A
172.31.128.0/20 network (AS 65501)
through BGP to ISP B and ISP C

Loopback and Interface Peering
 IBGP sessions are usually established between loopback
addresses
• Uses IGP to maintain sessions regardless of physical topology
 EBGP sessions are usually established using the IP
addresses of the physically connected interfaces
AS 65503
R1
AS 65502 ge-0/0/1.0 ge-0/0/1.0
R2
(.1) 172.24.1.0/30 (.2)
IGP
IBGP
If failure occurs, loopback-

R3 based IBGP sessions stay up
over working links

Configuring BGP
[edit]
user@router# show routing-options
router-id 192.168.100.1;
autonomous-system 65503; Device’s assigned AS number
[edit]
user@router# show protocols bgp
group int-65503 { BGP group names are user-defined
type internal;
local-address 192.168.100.1;
neighbor 192.168.100.2;
} BGP session type determines whether
group ext-65501 { the peering session is IBGP or EBGP
type external;
peer-as 65501; EBGP peer’s assigned AS number
neighbor 172.30.1.2;
}

Configuring BGP Authentication
 BGP protocol exchanges can be MD5 authenticated
 Hitless key rollover is an option
[edit]
user@router# show protocols bgp
authentication-key juniper; Global Level
group int-65503 {
authentication-key juniper;
type internal; Group Level
neighbor 192.168.100.2;
}
group ext-65501 {
type external;
peer-as 65501;
neighbor 172.30.1.2 {
authentication-key juniper; Neighbor Level
}
}

BGP Operation
 BGP stores routes in three main routing information base
memory tables
• Adjacency-RIB-IN: Contains all received routes from each peer
• RIB-LOCAL: Contains routes the local router uses to forward
traffic
• Adjacency-RIB-OUT: Contains all advertised routes sent to
each peer
 Only active BGP routes in the local routing table can be
advertised to peers
• Single, best BGP path is advertised
• Can use advertise-inactive when BGP route is not
active, but only the single, best, inactive BGP path is advertised

Default BGP Advertisement Rules
1. IBGP advertises routes 2. EBGP advertises routes
learned from EBGP, learned from IBGP or EBGP,
and… AS 65510
AS 65501 but…
Route X
prefix X
EBGP IGP
IBGP
GP
EB
GP
EB
IGP IGP
IBGP IBGP
AS 65502 AS 65503
3. IBGP does not advertise

any routes learned from IBGP
IBGP Route Propagation
 To avoid loops, BGP speakers do not propagate IBGP-
received routes to other IBGP peers
• A full mesh is required to ensure all IBGP speakers have
consistent BGP routing information
Rule prohibits R2
from advertising
AS 65503 Route X to R3
Route X Route X
R1 R2 R3
AS 65502
IBGP Neighbors IBGP Neighbors
Solution is to have R1 and R3

become IBGP neighbors
Hidden BGP Routes
 Reasons routes might not be installed in the
RIB-LOCAL:
• Martian
• Import policy
• Unresolvable next-hop
 Number one reason: Unresolvable next hop
user@router> show route hidden extensive
inet.0: 24 destinations, 24 routes (23 active, 0 holddown, 1 hidden)
172.19.20.0/24 (1 entry, 0 announced)
BGP Preference: 170/-101
Next hop type: Unusable
State: <Hidden Int Ext>
Local AS: 1 Peer AS: 1
Age: 13:53 Metric2: 0
Task: BGP_1.192.168.10.1+179
AS path: 2 I
BGP next hop: 10.10.1.2
Localpref: 100
Router ID: 192.168.10.1

IBGP Next-Hop Propagation
 By default, IBGP peers do not change the next hop for
routes received from EBGP peers
By default, the next-hop value for the
Route X advertisement remains 172.24.1.1
How do I get to
AS 65503 172.24.1.1?
Route X Route X
AS 65502 R1 R2
(.1) 172.24.1.0/30 (.2)

IBGP Neighbors

BGP Next-Hop Resolution
 BGP next-hop solutions:
• Next-hop self
• Use a policy to alter the next-hop value
• Change the BGP next hop to be the address of the IBGP peer
• Export direct routes into the IGP
• Use a policy to advertise external interface prefixes to IBGP peers
• Adds external interface prefixes to the IGP routing tables
• IGP passive interface
• IGP advertises external interface prefixes to IBGP peers,
no adjacency formed
• Adds external interface prefixes to the IGP routing tables
• Static routes
• IGP adjacency formed on inter-AS links to EBGP peers

Selecting the Active BGP Route
 Once BGP verifies next-hop reachability and that no
loops exist, it selects the active route as follows:
BGP Route Selection Summary
1. Prefer the path with the higher local- 6. Prefer path whose next-hop is resolved by
preference IGP route with lowest IGP metric
2. Prefer the route with the shortest AS-path 7. For EBGP-received routes, prefer the
length current active route; otherwise, prefer
routes from the peer with lowest RID
3. Prefer the route with the lower origin code 8. Prefer routes with the shortest cluster list
length
4. Prefer the path with the lowest MED 9. Prefer routes from the peer with the
metric lowest peer IP address
5. Prefer routes learned from an EBGP peer
over an IBGP peer
BGP Multipath (1 of 3)
 BGP can ignore both RID and peer ID comparisons when
multipath is configured within BGP
• Can use:
• Two peering sessions to the same router
• Two peering sessions to different routers in the same AS
R2
10.222.28.1/24 10.222.28.2/24
R1 (AS 2)
(AS 1) R3
10.222.29.1/24
10.222.29.2/24 (AS 2)
[edit protocols bgp group ext-peers]

type external;
peer-as 2;
neighbor 10.222.28.2;
neighbor 10.222.29.2;
}
user@R1> show bgp summary
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Rec
10.222.28.2 2 7 7 0 0 00:00:02 4/4/0
10.222.29.2 2 8 10 0 0 00:00:06 0/4/0

 Routes from each peer contain a single next hop
user@R1> show route protocol bgp terse
+ = Active Route, - = Last Active, * = Both
A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 172.16.20.4/30 B 170 100 >10.222.28.2 2 I
B 170 100 >10.222.29.2 2 I
* 172.16.20.8/30 B 170 100 >10.222.28.2 2 I
B 170 100 >10.222.29.2 2 I
* 172.16.20.12/30 B 170 100 >10.222.28.2 2 I
B 170 100 >10.222.29.2 2 I
* 172.16.20.16/30 B 170 100 >10.222.28.2 2 I
B 170 100 >10.222.29.2 2 I

 Peer group on R1 configured with multipath
• Active route receives two next hops
• Forwarding table still maintains a single next hop per route
user@R1> show route protocol bgp terse


* 172.16.20.4/30 B 170 100 >10.222.28.2 2 I
10.222.29.2
B 170 100 >10.222.29.2 2 I
* 172.16.20.8/30 B 170 100 >10.222.28.2 2 I
10.222.29.2
B 170 100 >10.222.29.2 2 I
* 172.16.20.12/30 B 170 100 >10.222.28.2 2 I
10.222.29.2
B 170 100 >10.222.29.2 2 I
* 172.16.20.16/30 B 170 100 10.222.28.2 2 I
>10.222.29.2
B 170 100 >10.222.29.2 2 I

Multihop Peering
 EBGP sessions can peer with nonphysical addresses
lo0: 192.168.3.4 lo0: 172.16.128.1
R1 10.10.1.2/24 10.10.1.1/24 R2
(AS 1) (AS 2)
10.10.2.2/24 10.10.2.1/24
[edit protocols bgp group ext-peers]

type external; A TTL value of 1 accommodates
local-address 192.168.3.4; Step 1 peering to a loopback address on a
directly connected peer—higher
neighbor 172.16.128.1 {
Step 2 values are needed for peers that are
multihop ttl 1; not directly connected
}
[edit routing-options]
static {
route 172.16.128.1 next-hop [ 10.10.1.1 10.10.2.1 ]; Step 3
}

Multiple Next Hops
 Both multihop and multipath create routes with multiple
next hops in the routing table
• Use a routing policy to forward traffic on both next hops
user@router> show route 172.16.20.4/30 terse


* 172.16.20.4/30 B 170 100 >10.10.1.1 2 I
10.10.2.1
B 170 100 >10.10.2.1 2 I
user@router> show route forwarding-table matching 172.16.20.4/30

Routing table: inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
172.16.20.4/30 user 0 indr 106 4
10.10.1.1 ucst 47 4 fe-0/0/0.0

Load Balancing
user@router> show configuration policy-options policy-statement load-balance
then {
load-balance per-packet;
}
user@router> show configuration routing-options forwarding-table
export load-balance;
user@router> show route 172.16.20.4/30 terse


* 172.16.20.4/30 B 170 100 >10.10.1.1 2 I
10.10.2.1
B 170 100 >10.10.2.1 2 I
user@router> show route forwarding-table matching 172.16.20.4/30

Routing table: inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
172.16.20.4/30 user 0 ulst 108 4
indr 106 2
10.10.1.1 ucst 47 4 fe-0/0/0.0
indr 107 2
10.10.2.1 ucst 99 4 ge-0/1/0.0

Peer Configuration Options (1 of 3)
 passive keeps BGP from sending an open message
[edit protocols bgp]
group ext-peers {
type external;
peer-as 2;
neighbor 10.10.10.1 {
passive;
}
}
 allow accepts open messages from any peer within the

configured IP address range
group ext-peers {
type external;
peer-as 65000;
allow 10.10/16;
}

 prefix-limit allows a specified amount of prefixes to be received

group ext-peers {
type external;
peer-as 2;
family inet {
unicast {
prefix-limit {
maximum 25000;
teardown 80 idle-timeout 10;
}
}
}
}
 hold-time alters the value used in the session

negotiation process
group ext-peers {
type external;
hold-time 45;
peer-as 2;
}

 advertise-peer-as disables suppression of route
advertisements
• Routes learned from an EBGP peer are advertised back to the
same EBGP peer
• Routes learned from an EBGP peer are advertised to EBGP
peers in the same AS as the originating peer

group ext-peers {
advertise-peer-as;
peer-as 2;
}

Graceful Restart
 GR allows a router undergoing a restart event to inform its
neighbors and request a grace period during which it can
recover from that restart event
• Forwarding through existing paths can continue during restart
R1 informs all neighbors of a restart
event. R1 is known as the restarting router
in GR terminology.
R3 and R6 are not aware a

restart event occurred.
R1’s neighbors hide the failure from

other routers in the network. R2, R4,
and R5 are known as helper routers in Once R1 recovers from the restart event, R1 synchronizes with its neighbors
GR terminology. without disrupting packet forwarding.

GR Support and Requirements
 Routers (restarting and helper routers) must have GR
enabled and be able to support nonstop forwarding
 End-of-RIB markers sent for each NLRI
• Notifies the neighbor that all current routing information was
sent
• Local router defers path selection algorithm until the marker is
received
 Configured globally within the [edit routing-
options] hierarchy During a restart event, forwarding continues
Control Plane Routing Engine based on existing forwarding table entries.
Forwarding Plane
FT
Packets In Packets Out
Packet Forwarding Engine
Configuring GR (1 of 2)
 GR helper mode is enabled by default
• You can disable GR helper mode globally at
the [edit routing-options] hierarchy or on a
per-protocol, per-group, or per-neighbor basis
(depending on the protocol)
[edit]
user@R1# show routing-options
graceful-restart {
disable; Disables helper mode globally for all
} protocols that support GR
[edit]
user@R1# show protocols bgp
graceful-restart; Enables helper mode for BGP
group my-group {
type internal;
Note: The most specific application is preferred.
neighbor 192.168.1.2;
neighbor 192.168.2.2 {
graceful-restart {
disable; Disables GR for BGP peer
}
}
}
Configuring GR (2 of 2)
 GR restarting router mode is not enabled by default
• You can enable this mode at the [edit routing-
options] hierarchy and disable it on a per-protocol, per-
group, or per-neighbor basis (depending on the protocol)
• Configuration options vary between
the supported protocols [edit]
user@R1# show routing-options
graceful-restart;
[edit]
user@R1# show protocols bgp
Enables restarting router mode for all graceful-restart;
protocols that support GR group my-group {
type internal;
neighbor 192.168.1.2;
neighbor 192.168.2.2 {
graceful-restart {
Disables GR for BGP peer disable;
}
}
}
Modifying Local Preference
AS 65002 AS 65003
192.168.19.0/24
R1 R2
lo0=192.168.40.1 Local preference
user@R2> show route advertising-protocol bgp 192.168.40.1

Restart Complete
Prefix Nexthop MED Lclpref AS path
* 192.168.19.0/24 Self 0 100 65003 I
[edit]
user@R2# set protocols bgp group int-peers local-preference 300
user@R2> show route advertising-protocol bgp 192.168.40.1

Restart Complete
* 192.168.19.0/24 Self 0 300 65003 I

Modifying AS Path: remove-private
192.168.17.0/24: 1000
192.168.18.0/24: 1000
192.168.19.0/24: 1000
Internet
R1 remove-private
R2
AS 1000 R3
192.168.17.0/24: 65001 192.168.18.0/24: 65002 192.168.19.0/24: 65003
AS 65001 AS 65002 AS 65003

192.168.17.0/24 192.168.18.0/24 192.168.19.0/24

Modifying AS Path: local-as (1 of 3)
Internet
172.16.10.0/24: 1 222
172.16.12.0/24: 1 333
AS 1
172.16.10.0/24: 222
172.16.12.0/24: 333
AS 222 AS 333
172.16.10.0/24 172.16.12.0/24

AS 777
172.16.10.0/24: 1 222
172.16.12.0/24: 1 333
172.16.10.0/24: 777 1 222
172.16.12.0/24: 777 1 333
local-as 1
Internet
172.16.10.0/24: 222
172.16.12.0/24: 333
AS 222 AS 333
172.16.10.0/24 172.16.12.0/24

AS 777
172.16.10.0/24: 222
172.16.12.0/24: 333
172.16.10.0/24: 777 222
172.16.12.0/24: 777 333
local-as 1 private
Internet
172.16.10.0/24: 222
172.16.12.0/24: 333
AS 222 AS 333
172.16.10.0/24 172.16.12.0/24

Modifying AS Path: as-override
172.16.10.0/24: 65022 172.16.10.0/24: 65432 65432
10.222.4.2
AS 65022
10.222.4.1
172.16.10.0/24
AS 65432 AS 65022
as-override
user@AS65432> show route advertising-protocol bgp 10.222.4.2
* 172.16.10.0/24 Self 65022 I
user@AS65022> show route receive-protocol bgp 10.222.4.1
[edit]
user@AS65432# set protocols bgp group AS-65022 as-override
user@AS65432> show route advertising-protocol bgp 10.222.4.2
* 172.16.10.0/24 Self 65022 I
* 172.16.10.0/24 10.222.4.1 65432 65432 I

Modifying AS Path: loops
172.16.10.0/24: 65022 172.16.10.0/24: 65432 65022
AS 65022
AS 65432
172.16.10.0/24
AS 65022
[edit]
user@AS65022# set routing-options autonomous-system 65022 loops 2

* 172.16.10.0/24 10.222.4.1 65432 65022 I

BGP

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BGP

Uploaded by

Copyright:

Available Formats

BGP

© 2012 Juniper Networks, Inc. All rights reserved. | www.juniper.net

AS 65501 BGP AS 65504

 BGP peers can reside in different ASs or the same AS

IGP EBGP IGP

BGP Neighbor States

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 5

BGP Message Types

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 7

Router compares attributes

Established Neighbors Established Neighbors

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 9

Established Neighbors Established Neighbors

• Some common examples include:

Common BGP Attributes

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 10

Customer A is single-homed to ISP A and uses Customer B

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 11

Customer A I can reach

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 12

ISP A advertises an aggregate

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 13

Customer B advertises its Customer B

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 14

172.31.128.0/20 is reachable through 172.31.128.0/20 is reachable through

Customer B advertises its Customer B

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 15

If failure occurs, loopback-

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 16

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 17

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 19

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 21

3. IBGP does not advertise

IBGP Neighbors IBGP Neighbors

Solution is to have R1 and R3

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 24

(.1) 172.24.1.0/30 (.2)

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 25

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 26

[edit protocols bgp group ext-peers]

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 30

A Destination P Prf Metric 1 Metric 2 Next hop AS path

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 32

user@R1> show route protocol bgp terse

A Destination P Prf Metric 1 Metric 2 Next hop AS path

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 33

[edit protocols bgp group ext-peers]

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 34

user@router> show route 172.16.20.4/30 terse

A Destination P Prf Metric 1 Metric 2 Next hop AS path

user@router> show route forwarding-table matching 172.16.20.4/30

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 35

user@router> show route 172.16.20.4/30 terse

A Destination P Prf Metric 1 Metric 2 Next hop AS path

user@router> show route forwarding-table matching 172.16.20.4/30

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 36

 allow accepts open messages from any peer within the

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 37

[edit protocols bgp]

 hold-time alters the value used in the session

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 38

[edit protocols bgp]

© 2012 Juniper Networks, Inc. All rights reserved. www.juniper.net | 39

R3 and R6 are not aware a