BGP Multihoming Examples

Two links to the same ISP
One link primary, the other link

backup only
47
(one as backup only)
• Applies when end-site has bought a large
primary WAN link to their upstream a small
secondary WAN link as the backup
– For example, primary path might be an E1, backup
might be 64kbps
48
primary
C
A
AS 100 AS 65534
E B
D
backup
• AS100 removes private AS and any customer

subprefixes from Internet announcement
49
• Announce /19 aggregate on each link
– primary link:
• Outbound – announce /19 unaltered
• Inbound – receive default route
– backup link:
• Outbound – announce /19 with increased metric
• Inbound – received default, and reduce local preference
• When one link fails, the announcement of the /19
aggregate via the other link ensures continued
connectivity
50
• Router A Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
neighbor 122.102.10.2 remote-as 100
neighbor 122.102.10.2 description RouterC
neighbor 122.102.10.2 prefix-list aggregate out
neighbor 122.102.10.2 prefix-list default in
!
ip prefix-list aggregate permit 121.10.0.0/19
ip prefix-list default permit 0.0.0.0/0
!
ip route 121.10.0.0 255.255.224.0 null0
51
• Router B Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
neighbor 122.102.10.6 description RouterD
neighbor 122.102.10.6 prefix-list aggregate out
neighbor 122.102.10.6 route-map routerD-out out
neighbor 122.102.10.6 route-map routerD-in in
!
..next slide
52
ip prefix-list aggregate permit 121.10.0.0/19
!
ip route 121.10.0.0 255.255.224.0 null0
!
route-map routerD-out permit 10
set metric 10
!
route-map routerD-in permit 10
set local-preference 90
!
53
• Router C Configuration (main link)
router bgp 100
neighbor 122.102.10.1 default-originate
neighbor 122.102.10.1 prefix-list Customer in
neighbor 122.102.10.1 prefix-list default out
!
ip prefix-list Customer permit 121.10.0.0/19
54
• Router D Configuration (backup link)
router bgp 100
!
55
• Router E Configuration
router bgp 100
neighbor 122.102.10.17 remove-private-AS
neighbor 122.102.10.17 prefix-list Customer out
!
• Router E removes the private AS and customer s subprefixes
from external announcements
• Private AS still visible inside AS100
56
With Loadsharing
57
Loadsharing to the same ISP
• More common case
• End sites tend not to buy circuits and leave
them idle, only used for backup as in previous
example
• This example assumes equal capacity circuits
– Unequal capacity circuits requires more
refinement – see later
58
Link one
C
A
AS 100 AS 65534
E B
D
Link two
• Border router E in AS100 removes private AS and any customer

subprefixes from Internet announcement
59
(with redundancy)
• Announce /19 aggregate on each link
• Split /19 and announce as two /20s, one on each link
– basic inbound loadsharing
– assumes equal circuit capacity and even spread of traffic across
address block
• Vary the split until perfect loadsharing achieved
• Accept the default from upstream
– basic outbound loadsharing by nearest exit
– okay in first approx as most ISP and end-site traffic is inbound
60
(with redundancy)
• Router A Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
network 121.10.0.0 mask 255.255.240.0
neighbor 122.102.10.2 prefix-list routerC out
!
ip prefix-list routerC permit 121.10.0.0/20
!
ip route 121.10.0.0 255.255.240.0 null0
ip route 121.10.0.0 255.255.224.0 null0
61
(with redundancy)
• Router B Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
network 121.10.16.0 mask 255.255.240.0
neighbor 122.102.10.6 prefix-list routerD out
!
ip prefix-list routerD permit 121.10.16.0/20
!
ip route 121.10.16.0 255.255.240.0 null0
ip route 121.10.0.0 255.255.224.0 null0
62
(with redundancy)
• Router C Configuration
router bgp 100
!
ip prefix-list Customer permit 121.10.0.0/19 le 20
• Router C only allows in /19 and /20 prefixes from customer
block
• Router D configuration is identical
63
(with redundancy)
router bgp 100
neighbor 122.102.10.17 prefix-list Customer out
!
64
(with redundancy)
• Default route for outbound traffic?
– Use default-information originate for the IGP and
rely on IGP metrics for nearest exit
– e.g. on router A:
router ospf 65534

default-information originate metric 2 metric-type 1
65
(with redundancy)
• Loadsharing configuration is only on customer
router
• Upstream ISP has to
– remove customer subprefixes from external
announcements
– remove private AS from external announcements
• Could also use BGP communities
66
Multiple Dualhomed Customers

(RFC2270)
67
(RFC2270)
• Unusual for an ISP just to have one
dualhomed customer
– Valid/valuable service offering for an ISP with
multiple PoPs
– Better for ISP than having customer multihome
with another provider!
• Look at scaling the configuration
–  Simplifying the configuration
– Using templates, peer-groups, etc
– Every customer has the same configuration
(basically)
68
(RFC2270)
C
A1
AS 65534
AS 100 B1
E D A2
AS 65534
B2
A3
AS 65534
• Border router E in AS100 removes private AS
and any customer subprefixes from Internet B3
announcement
69
(RFC2270)
• Customer announcements as per previous
example
• Use the same private AS for each customer
– documented in RFC2270
– address space is not overlapping
– each customer hears default only
• Router An and Bn configuration same as
Router A and B previously
70
(RFC2270)
• Router A1 Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
network 121.10.0.0 mask 255.255.240.0
neighbor 122.102.10.2 prefix-list routerC out
!
!
ip route 121.10.0.0 255.255.240.0 null0
ip route 121.10.0.0 255.255.224.0 null0
71
(RFC2270)
• Router B1 Configuration
router bgp 65534
network 121.10.0.0 mask 255.255.224.0
network 121.10.16.0 mask 255.255.240.0
neighbor 122.102.10.6 prefix-list routerD out
!
!
ip route 121.10.0.0 255.255.224.0 null0
ip route 121.10.16.0 255.255.240.0 null0
72
(RFC2270)
• Router C Configuration
router bgp 100
neighbor bgp-customers peer-group
neighbor bgp-customers remote-as 65534
neighbor bgp-customers default-originate
neighbor bgp-customers prefix-list default out
neighbor 122.102.10.1 peer-group bgp-customers
neighbor 122.102.10.1 description Customer One
neighbor 122.102.10.1 prefix-list Customer1 in
neighbor 122.102.10.9 description Customer Two
73
(RFC2270)
neighbor 122.102.10.17 description Customer Three
!
ip prefix-list Customer1 permit 121.10.0.0/19 le 20
• Router C only allows in /19 and /20 prefixes from customer

block
74
(RFC2270)
• Router D Configuration
router bgp 100
neighbor bgp-customers peer-group
neighbor bgp-customers remote-as 65534
neighbor bgp-customers default-originate
neighbor bgp-customers prefix-list default out
neighbor 122.102.10.5 description Customer One
neighbor 122.102.10.13 description Customer Two
75
(RFC2270)
neighbor 122.102.10.21 description Customer Three
!
• Router D only allows in /19 and /20 prefixes from customer

block
76
(RFC2270)
– assumes customer address space is not part of upstream s address
block
router bgp 100
neighbor 122.102.10.17 prefix-list Customers out
!
ip prefix-list Customers permit 121.10.0.0/19

77
(RFC2270)
• If customers prefixes come from ISP s address block
– do NOT announce them to the Internet
– announce ISP aggregate only
• Router E configuration:
router bgp 100

neighbor 122.102.10.17 prefix-list my-aggregate out
!
ip prefix-list my-aggregate permit 121.8.0.0/13
78
Multihoming Summary
• Use private AS for multihoming to the same
upstream
• Leak subprefixes to upstream only to aid
loadsharing
• Upstream router E configuration is identical
across all situations
79

BGP Multihoming Examples

Uploaded by

BGP Multihoming Examples

Uploaded by

Two links to the same ISP

One link primary, the other link

• AS100 removes private AS and any customer

• Border router E in AS100 removes private AS and any customer

router ospf 65534

Multiple Dualhomed Customers

• Router C only allows in /19 and /20 prefixes from customer

• Router D only allows in /19 and /20 prefixes from customer

• Private AS still visible inside AS100

router bgp 100

You might also like