0 évaluation0% ont trouvé ce document utile (0 vote)
49 vues8 pages
The document describes 7 different Border Gateway Protocol (BGP) configuration options for dual box multi-homed networks: 1) no high availability (HA) cluster, 2) no HA cluster with full mesh, 3) HA cluster with active/passive failover and no iBGP, 4) HA cluster with active/passive failover and full mesh, 5) HA cluster with active/active failover, 6) HA cluster with active/active failover and full mesh, 7) HA cluster with active/active failover, full mesh and option to use iBGP. The 4th, 6th and 7th configurations are recommended as they support features like asymmetric routing and load sharing.
The document describes 7 different Border Gateway Protocol (BGP) configuration options for dual box multi-homed networks: 1) no high availability (HA) cluster, 2) no HA cluster with full mesh, 3) HA cluster with active/passive failover and no iBGP, 4) HA cluster with active/passive failover and full mesh, 5) HA cluster with active/active failover, 6) HA cluster with active/active failover and full mesh, 7) HA cluster with active/active failover, full mesh and option to use iBGP. The 4th, 6th and 7th configurations are recommended as they support features like asymmetric routing and load sharing.
The document describes 7 different Border Gateway Protocol (BGP) configuration options for dual box multi-homed networks: 1) no high availability (HA) cluster, 2) no HA cluster with full mesh, 3) HA cluster with active/passive failover and no iBGP, 4) HA cluster with active/passive failover and full mesh, 5) HA cluster with active/active failover, 6) HA cluster with active/active failover and full mesh, 7) HA cluster with active/active failover, full mesh and option to use iBGP. The 4th, 6th and 7th configurations are recommended as they support features like asymmetric routing and load sharing.
Dual box multi-homed no HA cluster Dual box multi-homed full mesh, no HA cluster Dual box multi-homed HA cluster (Active/Passive) Dual box multi-homed full mesh, HA cluster (Active/Passive)* Dual box multi-homed HA cluster (Active/Active)* Dual box multi-homed full mesh, HA cluster (Active/Active)*
*Recommended
Congura0on
Single box multi-homed bgp config (recommended)
ISP
A
ISP
B
asymmetric
rou3ng
supported
cold
spare
for
hw
redundancy
load
sharing
possible
(if
announcing
>
/24)
Dual box multi-homed bgp config no HA cluster
ISP
A
ISP
B
no
asymmetric
rou3ng
(use
as-path
prepend
and
local-pref)
ibgp
unique
eBGP
peer
on
each
rewall
Dual box multi-homed bgp config full mesh, no HA cluster
ISP
A
ISP
B
limited
asymmetric
rou3ng
(use
as-path
prepend
and
local-pref)
ibgp
unique
eBGP
peers
on
each
rewall
Dual box multi-homed bgp config HA cluster (Active/Passive)
ISP
A
ISP
B
no
asymmetric
rou3ng
only
single
peer
up
at
a
3me
both
boxes
iden3cal
congs
but
one
interface
unused
on
each
no
iBGP
iden3cal
eBGP
peers
on
each
rewall
but
only
opposite
one
used
on
each
*one
eBGP
peer
always
down
ISP
may
not
allow
5
Dual box multi-homed bgp config full mesh, HA cluster (Active/Passive)
(recommended)
ISP
A
ISP
B
asymmetric
rou3ng
supported
must
connect
through
switch
on
ISP
side
of
FW
for
iden3cal
addressing/cong
use
GRES
for
BGP
failover
no
ibgp
iden3cal
eBGP
peers
on
each
rewall
load
sharing
possible
(if
announcing
>
/24)
6
Dual box multi-homed bgp config HA cluster (Active/Active) (recommended)
ISP
A
ISP
B
asymmetric
rou3ng
supported
but
can
s3ll
simulate
ac3ve/passive
use
iBGP
for
best
path
unique
eBGP
peer
on
each
rewall
load
sharing
possible
(if
announcing
>
/24)
Dual box multi-homed bgp config full mesh, HA cluster (Active/Active)
(recommended)
ISP
A
ISP
B
asymmetric
rou3ng
supported
but
can
s3ll
simulate
ac3ve/passive
op3on
to
use
iBGP
unique
eBGP
peers
on
each
rewall
load
sharing
possible
(if
announcing
>
/24)