Load Sharing With BGP in Single and Multihomed Environments - Sample Configurations - Cisco

14/08/2015
LoadSharingwithBGPinSingleandMultihomedEnvironments:SampleConfigurationsCisco
IPRouting
LoadSharingwithBGPinSingleandMultihomedEnvironments:Sample
Configurations
HOME
Contents
SUPPORT
TECHNOLOGYSUPPORT
IP
LoadSharingwithBGPin
SingleandMultihomed
Environments:Sample
Configurations
Introduction
Prerequisites
Requirements
ComponentsUsed
Conventions
LoadSharingwiththeLoopbackAddressasaBGPNeighbor
NetworkDiagram
Configurations
Verify
Troubleshoot
LoadSharingWhenDualHomedtoOneInternetServiceProvider(ISP)
ThroughaSingleLocalRouter
NetworkDiagram
Configurations
Verify
Troubleshoot
LoadSharingWhenDualHomedtoOneISPThroughMultipleLocal
Routers
NetworkDiagram
Configurations
Verify
Troubleshoot
LoadSharingWhenMultihomedtoTwoISPsThroughaSingleLocal
Router
NetworkDiagram
Configurations
Verify
Troubleshoot
LoadSharingWhenMultihomedtoTwoISPsThroughMultipleLocal
Routers
NetworkDiagram
Configurations
Verify
Troubleshoot
RelatedInformation
RelatedCiscoSupportCommunityDiscussions
Introduction
Loadsharingallowsaroutertodistributetheoutgoingandincomingtrafficamongmultiplepaths.Thepaths
arederivedeitherstaticallyorwithdynamicprotocols,suchas:
RoutingInformationProtocol(RIP)
EnhancedInteriorGatewayRoutingProtocol(EIGRP)
OpenShortestPathFirst(OSPF)Protocol
InteriorGatewayRoutingProtocol(IGRP)
Bydefault,BorderGatewayProtocol(BGP)selectsonlyasinglebestpathanddoesnotperformload
balancing.ThisdocumentshowshowtoperformloadsharingindifferentscenarioswiththeuseofBGP.For
additionalinformationaboutloadbalancing,refertoHowDoesLoadBalancingWork?.
Prerequisites
Requirements
Ensurethatyoumeettheserequirementsbeforeyouattemptthisconfiguration:
KnowledgeofBGPBestPathSelectionAlgorithm
KnowledgeofConfiguringBGP
http://www.cisco.com/c/en/us/support/docs/ip/bordergatewayprotocolbgp/1376240.html
1/18
14/08/2015
ComponentsUsed
Thisdocumentisnotrestrictedtospecificsoftwareandhardwareversions.
Theinformationinthisdocumentwascreatedfromthedevicesinaspecificlabenvironment.Allofthe
devicesusedinthisdocumentstartedwithacleared(default)configuration.Ifyournetworkislive,makesure
thatyouunderstandthepotentialimpactofanycommand.
Conventions
RefertoCiscoTechnicalTipsConventionsformoreinformationondocumentconventions.
LoadSharingwiththeLoopbackAddressasaBGPNeighbor
Thisscenarioshowshowtoachieveloadsharingwhentherearemultiple(uptoamaximumofsix),equal
costlinks.Thelinksareterminatedinonerouteratalocalautonomoussystem(AS)andinanotherrouterat
aremoteASinasinglehomedBGPenvironment.TheNetworkDiagramservesasanexample.
Note:UsetheCommandLookupTool(registeredcustomersonly)tofindmoreinformationonthecommands
usedinthisdocument.
NetworkDiagram
Thissectionusesthisnetworksetup:
Configurations
Thissectionusestheseconfigurations:
RouterA
RouterB
RouterA
interfaceloopback0
ipaddress1.1.1.1255.255.255.0
interfaceserial0
ipaddress160.20.20.1255.255.255.0
noiproutecache
interfaceserial1
ipaddress150.10.10.1255.255.255.0
noiproutecache
routerbgp11
neighbor2.2.2.2remoteas10
neighbor2.2.2.2updatesourceloopback0
!UsetheIPaddressoftheloopbackinterfaceforTCPconnections.
neighbor2.2.2.2ebgpmultihop
!YoumustconfigureebgpmultihopwhenevertheexternalBGP(eBGP)
!connectionsarenotonthesamenetworkaddress.
routereigrp12
network1.0.0.0
network150.10.0.0
network160.20.0.0
noautosummary
RouterB
interfaceloopback0
ipaddress2.2.2.2255.255.255.0
interfaceserial0
ipaddress160.20.20.2255.255.255.0
noiproutecache
interfaceserial1
ipaddress150.10.10.2255.255.255.0
noiproutecache
routerbgp10
2/18
14/08/2015
neighbor1.1.1.1updatesourceloopback0
!UsetheIPaddressoftheloopbackinterfaceforTCPconnections.
neighbor1.1.1.1ebgpmultihop
!YoumustconfigureebgpmultihopwhenevertheeBGPconnections
!arenotonthesamenetworkaddress.
routereigrp12
network2.0.0.0
network150.10.0.0
network160.20.0.0
noautosummary
Note:Youcanusestaticroutesintheplaceofaroutingprotocolinordertointroducetwoequalcostpaths
toreachthedestination.Inthiscase,theroutingprotocolisEIGRP.
Verify
Usethissectiontoconfirmthatyourconfigurationworksproperly.
TheOutputInterpreterTool(registeredcustomersonly)(OIT)supportscertainshowcommands.Usethe
OITtoviewananalysisofshowcommandoutput.
Theoutputoftheshowiproutecommandshowsthatbothofthepathstothe2.2.2.0networkarelearned
viaEIGRP.Theoutputofthetraceroutecommandindicatesthattheloadisdistributedbetweentwoserial
links.Inthisscenario,loadsharingoccursonaperpacketbasis.Youcanissuetheiproutecache
commandontheserialinterfacestodoloadsharingonaperdestinationbasis.Youcanalsoconfigureper
packetandperdestinationloadbalancingwithCiscoExpressForwarding.Formoreinformationonhowto
configureCiscoExpressForwarding,refertoConfiguringCiscoExpressForwarding.
RouterA#showiproute
!Outputsuppressed.
Gatewayoflastresortisnotset
1.0.0.0/24issubnetted,1subnets
C1.1.1.0isdirectlyconnected,Loopback0
D2.2.2.0[90/2297856]via150.10.10.2,00:00:45,Serial1
[90/2297856]via160.20.20.2,00:00:45,Serial0
C160.20.20.0isdirectlyconnected,Serial0
RouterA#traceroute2.2.2.2
Typeescapesequencetoabort.
Tracingtherouteto2.2.2.2
1160.20.20.216msec
150.10.10.28msec*
Troubleshoot
Thereiscurrentlynospecifictroubleshootinginformationavailableforthisconfiguration.
LoadSharingWhenDualHomedtoOneInternetServiceProvider
(ISP)ThroughaSingleLocalRouter
ThisscenarioshowshowtoachieveloadsharingwhenmultiplelinksexistbetweenaremoteASandalocal
AS.TheselinksareterminatedinonerouteratthelocalASandonmultipleroutersatremoteASsina
singlehomedBGPenvironment.TheNetworkDiagramisanexampleofsuchanetwork.
Thissampleconfigurationusesthemaximumpathscommand.Bydefault,BGPchoosesonebestpath
amongthepossibleequalcostpathsthatarelearnedfromoneAS.However,youcanchangethemaximum
numberofparallelequalcostpathsthatareallowed.Inordertomakethischange,includethemaximum
pathspathscommandundertheBGPconfiguration.Useanumberbetween1and6forthepathsargument.
NetworkDiagram
3/18
14/08/2015
Configurations
RouterA
RouterB
RouterC
RouterA
interfaceLoopback0
ipaddress1.1.1.1255.255.255.0
!
interfaceSerial0
ipaddress160.20.20.1255.255.255.0
!
!
interfaceSerial1
ipaddress150.10.10.1255.255.255.0
!
!
routerbgp11
network1.0.0.0
maximumpaths2
!Thiscommandspecifiesthemaximumnumberofpaths
!toinstallintheroutingtableforthespecificdestination.
RouterB
interfaceEthernet0
ipaddress2.2.2.1255.255.255.0
!
interfaceSerial0
ipaddress160.20.20.2255.255.255.0
!
!
routerbgp10
network2.0.0.0
autosummary
RouterC
interfaceEthernet0
ipaddress2.2.2.2255.255.255.0
!
interfaceSerial1
ipaddress150.10.10.2255.255.255.0
!
!
routerbgp10
network2.0.0.0
autosummary
Verify
Theoutputoftheshowiproutecommandshowsthatbothofthepathstothe2.2.2.0networkarelearned
viaBGP.Theoutputofthetraceroutecommandindicatesthattheloadisdistributedbetweentwoserial
links.Inthisscenario,loadsharingoccursonaperdestinationbasis.Theshowipbgpcommandgivesthe
validentriesforthe2.0.0.0network.
4/18
14/08/2015
RouterA#showiproute
!Outputsuppressed.
C1.1.1.0isdirectlyconnected,Loopback0
B2.0.0.0/8[20/0]via150.10.10.2,00:04:23
[20/0]via160.20.20.2,00:04:01
1160.20.20.216msec
150.10.10.28msec*
RouterA#showipbgp
BGPtableversionis3,localrouterIDis1.1.1.1
Statuscodes:ssuppressed,ddamped,hhistory,*valid,>best,iinternal
Origincodes:iIGP,eEGP,?incomplete
Network
NextHop
MetricLocPrfWeightPath
*>1.0.0.0
0.0.0.0
0
32768i
*>2.0.0.0
160.20.20.20
0
10i
*150.10.10.20
0
10i
Troubleshoot
LoadSharingWhenDualHomedtoOneISPThroughMultipleLocal
Routers
ThisscenarioshowshowtoachieveloadsharingwhentherearemultipleconnectionstothesameISP
throughmultiplelocalrouters.ThetwoeBGPpeersareterminatedontwoseparatelocalrouters.Load
balancingonthetwolinksisnotpossiblebecauseBGPchoosesthesinglebestpathamongthenetworks
thatislearnedfromeBGPandinternalBGP(iBGP).LoadsharingamongthemultiplepathstoAS10isthe
nextbestoption.Withthistypeofloadsharing,traffictospecificnetworks,onthebasisofpredefined
policies,travelsthroughbothlinks.Additionally,eachlinkactsasabackuptotheotherlink,incaseonelink
fails.
Forsimplicity,assumethattheBGProutingpolicyforAS11is:
AS11acceptsthelocalroutesfromAS10,alongwithadefaultfortherestoftheInternetroutes.
Theoutboundtrafficpolicyis:
AlltrafficthatisdestinedtotheInternetfromR101goesoutthroughtheR101R103link.
IftheR101R103linkfails,thenalltraffictotheInternetfromR101goesthroughR102toAS
10.
Similarly,alltrafficthatisdestinedtotheInternetfromR102goesthroughtheR102R104link.
IftheR102R104linkfails,thenalltraffictotheInternetfromR102goesthroughR101toAS
10.
Theinboundtrafficpolicyis:
Trafficthatisdestinedfornetwork192.168.11.0/24fromtheInternetshouldcomefromthe
R103R101link.
R104R102link.
IfonelinktoAS10fails,thentheotherlinkshouldroutethetrafficthatisdestinedforall
networksbacktoAS11fromtheInternet.
Inordertoachievethis,192.168.11.0isannouncedfromR101toR103withashorterAS_PATHthanis
announcedfromR102toR104.AS10findsthebestpaththroughtheR103R101link.Similarly,
192.168.12.0isannouncedwithashorterpaththroughtheR102R104link.AS10preferstheR104R102
linkfortrafficthatisboundto192.168.12.0inAS11.
Foroutboundtraffic,BGPdeterminesthebestpathonthebasisofroutesthatarelearnedthrougheBGP.
TheseroutesarepreferabletorouteslearnedthroughiBGP.SoR101learns10.10.34.0fromR103through
eBGPandfromR102throughiBGP.Theexternalpathisselectedovertheinternalpath.So,ifyoulookat
theBGPtableintheR101configuration,theroutetoward10.10.34.0wouldbethroughtheR101R103link,
withnexthop10.10.13.3.OnR102,theroutetoward10.10.34.0wouldbethroughtheR102R104link,with
nexthop10.10.24.4.Thisachievesloadsharingfortrafficthatisdestinedto10.10.34.0.Similarreasoning
appliestothedefaultroutesonR101andR102.FormoreinformationonBGPpathselectioncriteria,refer
toBGPBestPathSelectionAlgorithm.
5/18
14/08/2015
NetworkDiagram
Configurations
R101
R102
R103
R104
R101
hostnameR101
!
interfaceEthernet0/0
ipaddress192.168.11.1255.255.255.0secondary
ipaddress192.168.12.1255.255.255.0
!
interfaceSerial8/0
ipaddress10.10.13.1255.255.255.0
!
routerbgp11
nosynchronization
bgplogneighborchanges
network192.168.11.0
network192.168.12.0
neighbor10.10.13.3routemapR101103MAPout
!TheAS_PATHisincreasedfor192.168.12.0.
neighbor192.168.12.2nexthopself
maximumpaths2
noautosummary
!
accesslist1permit192.168.12.0
routemapR101103MAPpermit10
matchipaddress1
setaspathprepend111111
!
matchipaddress2
R102
hostnameR102
!
ipaddress192.168.11.2255.255.255.0secondary
ipaddress192.168.12.2255.255.255.0
6/18
14/08/2015
!
interfaceSerial8/0
ipaddress10.10.24.2255.255.255.0
!
routerbgp11
nosynchronization
network192.168.11.0
network192.168.12.0
neighbor10.10.24.4routemapR102104MAPout
!TheAS_PATHisincreasedfor192.168.11.0.
noautosummary
!
matchipaddress1
setaspathprepend111111
!
matchipaddress2
!
R103
hostnameR103
!
ipaddress10.10.34.3255.255.255.0
!
interfaceSerial8/0
ipaddress10.10.13.3255.255.255.0
!
routerbgp10
nosynchronization
network10.10.34.0mask255.255.255.0
neighbor10.10.13.1defaultoriginate
noautosummary
!
R104
hostnameR104
!
ipaddress10.10.34.4255.255.255.0
!
interfaceSerial8/0
ipaddress10.10.24.4255.255.255.0
!
routerbgp10
nosynchronization
neighbor10.10.24.2defaultoriginate
noautosummary
!
Verify
Thissectionprovidesinformationyoucanusetoconfirmyourconfigurationisworkingproperly.
CertainshowcommandsaresupportedbytheOutputInterpreterTool(registeredcustomersonly),which
allowsyoutoviewananalysisofshowcommandoutput.
VerificationWhenBothLinksBetweenAS11andAS10AreUp
VerificationofOutboundTraffic
Note:Thegreaterthansign(>)intheshowipbgpcommandoutputrepresentsthebestpathtouseforthat
networkamongthepossiblepaths.RefertoBGPBestPathSelectionAlgorithmformoreinformation.
TheBGPtableinR101showsthatthebestpathforalloutgoingtraffictotheInternetisthroughtheR101
R103link.Theshowiproutecommandoutputconfirmstheroutesintheroutingtable.
R101#showipbgp
7/18
14/08/2015
NetworkNextHopMetricLocPrfWeightPath
*i0.0.0.0192.168.12.2100010i
*>10.10.13.3010i
!ThisisthenexthopofR103.
*i10.10.34.0/24192.168.12.2100010i
*>10.10.13.30010i
*i192.168.11.0192.168.12.201000i
*>0.0.0.0032768i
*i192.168.12.0192.168.12.201000i
*>0.0.0.0032768i
R101#showiproute
!Outputsuppressed.
Gatewayoflastresortis10.10.13.3tonetwork0.0.0.0
C192.168.12.0/24isdirectlyconnected,Ethernet0/0
C10.10.13.0isdirectlyconnected,Serial8/0
B10.10.34.0[20/0]via10.10.13.3,00:08:53
B*0.0.0.0/0[20/0]via10.10.13.3,00:08:53
HerearetheBGPandroutingtablesforR102.Accordingtothepolicy,R102shouldrouteallthetrafficto
AS10throughtheR102R104link:
R102#showipbgp
*>0.0.0.010.10.24.4010i
*i192.168.12.1100010i
*>10.10.34.0/2410.10.24.4010i
*i192.168.12.10100010i
*i192.168.11.0192.168.12.101000i
*>0.0.0.0032768i
*i192.168.12.0192.168.12.101000i
*>0.0.0.0032768i
R102#showiproute
!Outputsuppressed.
B10.10.34.0[20/0]via10.10.24.4,00:11:21
B*0.0.0.0/0[20/0]via10.10.24.4,00:11:21
VerificationofInboundTrafficfromAS10toAS11
Thenetworks192.168.11.0and192.168.12.0belongtoAS11.Accordingtothepolicy,AS11shouldprefer
theR103R101linkfortrafficthatisdestinedtonetwork192.168.11.0andtheR104R102linkfortrafficthat
isdestinedtonetwork192.168.12.0.
R103#showipbgp
*>10.10.34.0/240.0.0.0032768i
*>192.168.11.010.10.13.10011i
!ThenexthopisR101.
*192.168.12.010.10.13.10011111111i
*>i10.10.34.40100011i
!ThenexthopisR104.
8/18
14/08/2015
R103#showiproute
!Outputsuppressed.
B192.168.12.0/24[200/0]via10.10.34.4,00:04:46
!ThenexthopisR104.
B192.168.11.0/24[20/0]via10.10.13.1,00:04:46
!ThenexthopisR101.
C10.10.34.0isdirectlyconnected,Ethernet0/0
Thebestpathfornetwork192.168.11.0onR103isthroughtheR103R101link,andthebestpathfor
network192.168.12.0isthroughR104toAS11.Inthiscase,theshortestpathlengthdeterminesthebest
path.
Similarly,onR104,theBGPandroutingtableresemblesthis:
R104#showipbgp
*>i10.10.34.0/2410.10.34.301000i
*>i192.168.11.010.10.34.30100011i
*10.10.24.20011111111i
*>192.168.12.010.10.24.20011i
R104#showiproute
!Outputsuppressed.
B192.168.12.0/24[20/0]via10.10.24.2,00:49:06
!ThenexthopisR102.
B192.168.11.0/24[200/0]via10.10.34.3,00:07:36
!ThenexthopisR103.
VerificationWhentheR101R103LinkFails
WhentheR101R103linkfails,alltrafficshouldreroutethroughR102.Thisdiagramillustratesthischange:
ShutdowntheR103R101linkonR103inordertosimulatethissituation.
R103(config)#interfaceserial8/0
R103(configif)#shutdown
*May100:52:33.379:%BGP5ADJCHANGE:neighbor10.10.13.1DownInterfaceflap
*May100:52:35.311:%LINK5CHANGED:InterfaceSerial8/0,changedstateto
administrativelydown
9/18
14/08/2015
*May100:52:36.127:%LINEPROTO5UPDOWN:LineprotocolonInterfaceSerial8/0,changed
statetodown
VerifytheoutboundroutetoAS10.
R101#showipbgp
*>i0.0.0.0192.168.12.2100010i
*>i10.10.34.0/24192.168.12.2100010i
*i192.168.11.0192.168.12.201000i
*>0.0.0.0032768i
*i192.168.12.0192.168.12.201000i
*>0.0.0.0032768i
R101#showiproute
!Outputsuppressed.
B10.10.34.0[200/0]via192.168.12.2,00:01:34
B*0.0.0.0/0[200/0]via192.168.12.2,00:01:34
!AlloutboundtrafficgoesthroughR102.
R102#showiproute
!Outputsuppressed.
B10.10.34.0[20/0]via10.10.24.4,00:13:22
B*0.0.0.0/0[20/0]via10.10.24.4,00:55:22
!AlloutboundtrafficonR102goesthroughR104.
VerifytheinboundtrafficroutewhenR101R103isdown.
R103#showipbgp
*>10.10.34.0/240.0.0.0032768i
*>i192.168.11.010.10.34.40100011111111i
*>i192.168.12.010.10.34.40100011i
R103#showiproute
!Outputsuppressed.
B192.168.12.0/24[200/0]via10.10.34.4,00:14:55
!ThenexthopisR104.
B192.168.11.0/24[200/0]via10.10.34.4,00:05:46
!ThenexthopisR104.
OnR104,thetrafficfor192.168.11.0and192.168.12.0goesthroughtheR104R102link.
R104#showiproute
!Outputsuppressed.
B192.168.12.0/24[20/0]via10.10.24.2,00:58:35
!ThenexthopisR102.
B192.168.11.0/24[20/0]via10.10.24.2,00:07:57
!ThenexthopisR102.
10/18
14/08/2015
Troubleshoot
LoadSharingWhenMultihomedtoTwoISPsThroughaSingle
LocalRouter
Inthisscenario,loadbalancingisnotanoptioninamultihomedenvironment,soyoucanonlydoload
sharing.YoucannotdoloadbalancingbecauseBGPselectsonlyasinglebestpathtoadestinationamong
theBGProutesthatarelearnedfromthedifferentASs.Theideaistosetabettermetricfortheroutesin
therange1.0.0.0to128.0.0.0thatarelearnedfromISP(A)andabettermetricfortherestoftheroutesthat
arelearnedfromISP(B).TheNetworkDiagramisanexample.
RefertoSampleConfigurationforBGPwithTwoDifferentServiceProviders(Multihoming)foradditional
information.
NetworkDiagram
Configurations
RouterA
RouterB
RouterC
RouterA
interfaceSerial0
ipaddress160.20.20.1255.255.255.0
noiproutecache
interfaceSerial1
ipaddress150.10.10.1255.255.255.0
noiproutecache
routerbgp11
neighbor160.20.20.2routemapUPDATES1in
!Thisallowsonlythenetworksupto128.0.0.0.
neighbor150.10.10.2routemapUPDATES2in
!Thisallowsanythingabovethe128.0.0.0network.
autosummary
routemapUPDATES1permit10
matchipaddress1
setweight100
matchipaddress2
matchipaddress1
matchipaddress2
setweight100
accesslist1permit0.0.0.0127.255.255.255
accesslist2deny0.0.0.0127.255.255.255
accesslist2permitany
11/18
14/08/2015
RouterB
interfaceLoopback0
ipaddress2.2.2.2255.255.255.0
intloopback1
ipaddress170.16.6.5255.255.255.0
interfaceSerial0
ipaddress160.20.20.2255.255.255.0
noiproutecache
routerbgp10
network2.0.0.0
network170.16.0.0
autosummary
RouterC
interfaceLoopback0
ipaddress170.16.6.6255.255.255.0
interfaceLoopback1
ipaddress2.2.2.1255.255.255.0
interfaceSerial1
ipaddress150.10.10.2255.255.255.0
noiproutecache
routerbgp12
network2.0.0.0
network170.16.0.0
autosummary
Verify
Theoutputfromtheshowiproutecommandandtheoutputfromthetraceroutecommandshowthatany
networklowerthan128.0.0.0exitsRouterAthrough160.20.20.2.Thisrouteisthenexthopoutoftheserial
0interface.Therestofthenetworksexitthrough150.10.10.2,whichisthenexthopoutoftheserial1
interface.
RouterA#showiproute
!Outputsuppressed.
B
170.16.0.0/16[20/0]via150.10.10.2,00:43:43
!Thisisthenexthopoutthroughserial1.
B
2.0.0.0/8[20/0]via160.20.20.2,00:43:43
!Thisisthenexthopoutthroughserial0.
C
160.20.20.0isdirectlyconnected,Serial0
C
150.10.10.0isdirectlyconnected,Serial1
RouterA#showipbgp
*2.0.0.0150.10.10.20012i
*>160.20.20.2010010i
*170.16.0.0160.20.20.20010i
*>150.10.10.2010012i
1160.20.20.216msec*16msec
1150.10.10.24msec*4msec
Troubleshoot
12/18
14/08/2015
LoadSharingWhenMultihomedtoTwoISPsThroughMultiple
LocalRouters
LoadbalancingisnotpossibleinamultihomedenvironmentwithtwoISPs.BGPselectsonlythesinglebest
pathtoadestinationamongtheBGPpathsthatarelearnedfromdifferentASs,whichmakesloadbalancing
impossible.But,loadsharingispossibleinsuchmultihomedBGPnetworks.Onthebasisofpredetermined
policies,trafficflowiscontrolledwithdifferentBGPattributes.
Thissectiondiscussesthemultihomingconfigurationthathasthemostfrequentuse.Theconfiguration
showshowtoachieveloadsharing.SeetheNetworkDiagram,inwhichthemultihomeofAS100achieves
reliabilityandloadsharing.
Note:TheIPaddressesinthisexamplefollowRFC1918
notroutableontheInternet.
standardsforPrivateAddressSpaceandare
Forsimplicity,assumethattheBGProutingpolicyforAS100is:
AS100acceptsthelocalroutesfrombothproviders,alongwithadefaultfortherestoftheInternet
routes.
Theoutboundtrafficpolicyis:
TrafficthatisdestinedtoAS300goesthroughtheR1ISP(A)link.
TrafficthatisdestinedtoAS400goesthroughtheR2ISP(B)link.
Allothertrafficshouldpreferdefaultroute0.0.0.0throughtheR1ISP(A)link.
IftheR1ISP(A)linkfails,alltrafficshouldgothroughtheR2ISP(B)link.
Theinboundtrafficpolicyis:
ISP(A)R1link.
ISP(B)R2link.
IfoneISPfails,theotherISPshouldroutetrafficbacktoAS100fromtheInternetforallthe
networks.
NetworkDiagram
Configurations
R2
R1
R2
interfaceEthernet0
ipaddress192.168.21.2255.255.255.0
!
interfaceSerial0
ipaddress192.168.42.2255.255.255.0
routerbgp100
nosynchronization
13/18
14/08/2015
!ThenexttwolinesannouncethenetworkstoBGPpeers.
network10.10.10.0mask255.255.255.0
network10.10.20.0mask255.255.255.0
!ThenextlineconfiguresiBGPonR1.
!ThenextlineconfigureseBGPwithISP(B).
!Thisistheincomingpolicyroutemapfortheapplication
!ofattributestospecificroutes.
neighbor192.168.42.4routemapAS400INCOMINGin
!Thisistheoutgoingpolicyroutemapfortheapplication
neighbor192.168.42.4routemapAS400OUTGOINGout
noautosummary
!
!
!ThislinesetstheASpathaccesslist.
!Thelinepermitsallrouteswithintheroutingdomainoftheprovider.
ipaspathaccesslist1permit^400$
!
!Thesetwolinessettheaccesslist.
!ThenextthreelinesconfigureLOCAL_PREFforroutes
!thatmatchASpathaccesslist1.
routemapAS400INCOMINGpermit10
matchaspath1
setlocalpreference150
!Here,theroutemapprependsAS100toBGPupdatesfornetworks
!thatarepermittedbyaccesslist10.
routemapAS400OUTGOINGpermit10
matchipaddress10
setaspathprepend100
!Thislineannouncesthenetworkthatispermittedby
!accesslist20withoutanychangesinBGPattributes.
matchipaddress20
R1
interfaceSerial0/0
ipaddress192.168.31.1255.255.255.0
!
ipaddress192.168.21.1255.255.255.0
!
routerbgp100
nosynchronization
network10.10.10.0mask255.255.255.0
network10.10.20.0mask255.255.255.0
!IBGPpeeringwithR2
!
!ThislinesetseBGPpeeringwithISP(A).
!
!Thisistheincomingpolicyroutemapfortheapplication
neighbor192.168.31.3routemapAS300INCOMINGin
!
!Thisistheoutgoingpolicyroutemapfortheapplication
neighbor192.168.31.3routemapAS300OUTGOINGout
noautosummary
!ThislinesetstheASpathaccesslist.
14/18
14/08/2015
!Thelinepermitsallrouteswithintheroutingdomainoftheprovider.
ipaspathaccesslist1permit^300$
!
!ThesetwolinessettheIPaccesslist.
!ThenextthreelinesconfigureLOCAL_PREFforroutesthatmatch
!ASpathaccesslist1.
routemapAS300INCOMINGpermit10
matchaspath1
setlocalpreference200
!
!Here,theroutemapprependsAS100toBGPupdatesfornetworks
!thatarepermittedbyaccesslist10.
matchipaddress10
setaspathprepend100
!
!Thislineannouncesthenetworkthatispermitted
!byaccesslist20withoutanychangesinBGPattributes.
matchipaddress20
!
Verify
Issuetheshowipbgpcommandinordertoverifythattheoutbound/inboundpolicyworks.
Note:Thegreaterthansign(>)intheshowipbgpoutputrepresentsthebestpathtouseforthatnetwork
amongthepossiblepaths.RefertoBGPBestPathSelectionAlgorithmformoreinformation.
R1#showipbgp
*>0.0.0.0192.168.31.32000300i
!Thislineshowsthatthedefaultroute0.0.0.0/0ispreferred
!throughAS300,ISP(A).
*i10.10.10.0/24192.168.21.201000i
*>0.0.0.0032768i
*i10.10.20.0/24192.168.21.201000i
*>0.0.0.0032768i
*>30.30.30.0/24192.168.31.302000300i
*>i40.40.40.0/24192.168.21.201500400i
!Theroutetonetwork30.30.30.0/24(AS300)ispreferred
!throughtheR1ISP(A)link.
!throughtheR2ISP(B)link.
Now,lookattheshowipbgpoutputonR2:
R2#showipbgp
*0.0.0.0192.168.42.41500400i
*>i192.168.21.12000300i
!Thislineshowsthatthedefaultroute0.0.0.0/0ispreferred
!throughAS300,throughtheR2ISP(B)link.
*>10.10.10.0/240.0.0.0032768i
*i192.168.21.101000i
*>10.10.20.0/240.0.0.0032768i
*i192.168.21.101000i
*>i30.30.30.0/24192.168.21.102000300i
15/18
14/08/2015
*>40.40.40.0/24192.168.42.401500400i
!throughtheR1ISP(A)link.
!throughtheR2ISP(B)link.
IssuetheshowipbgpcommandonRouter6inordertoobservetheinboundpolicyfornetworks
10.10.10.0/24and10.10.20.0/24:
R6#showipbgp
*>10.10.10.0/24192.168.63.30300100100i
!Thislineshowsthatnetwork10.10.10.0/24isroutedthroughAS300
!withtheISP(A)R1link.
*192.168.64.40400100100100i
*10.10.20.0/24192.168.63.30300100100i
*>192.168.64.40400100i
!Thislineshowsthatnetwork10.10.20.0/24isroutedthroughAS400
!withtheISP(B)R2link.
*>30.30.30.0/24192.168.63.300300i
*>40.40.40.0/24192.168.64.400400i
ShutdowntheR1ISP(A)linkonR1andobservetheBGPtable.ExpectalltraffictotheInternettobe
routedthroughtheR2ISP(B)link:
R1(config)#interfaceserial0/0
R1(configif)#shutdown
*May219:00:47.377:%BGP5ADJCHANGE:neighbor192.168.31.3DownInterfaceflap
*May219:00:48.277:%LINK5CHANGED:InterfaceSerial0/0,changedstateto
administrativelydown
*May2312:00:51.255:%LINEPROTO5UPDOWN:LineprotocolonInterfaceSerial0,changed
statetodown
R1#showipbgp
*>i0.0.0.0192.168.21.21500400i
!ThebestdefaultpathisnowthroughtheR2ISP(B)link.
*i10.10.10.0/24192.168.21.201000i
*>0.0.0.0032768i
*i10.10.20.0/24192.168.21.201000i
*>0.0.0.0032768i
*>i40.40.40.0/24192.168.21.201500400i
R2#showipbgp
*>0.0.0.0192.168.42.41500400i
!ThebestdefaultrouteisnowthroughISP(B)witha
!localpreferenceof150.
*i10.10.10.0/24192.168.21.101000i
*>0.0.0.0032768i
*i10.10.20.0/24192.168.21.101000i
*>0.0.0.0032768i
*>40.40.40.0/24192.168.42.401500400i
Lookattheroutefornetwork10.10.10.0/24inRouter6:
R6#showipbgp
*>10.10.10.0/24192.168.64.40400100100i
!Network10.10.10.0isreachablethroughISP(B),whichannounced
!thenetworkwithASpathprepend.
*>10.10.20.0/24192.168.64.40400100i
*>30.30.30.0/24192.168.63.300300i
*>40.40.40.0/24192.168.64.400400i
16/18
14/08/2015
Troubleshoot
RelatedInformation
BGPMultihoming:DesignandTroubleshootingVideofromliveWebcast
BGPMultihoming:DesignandTroubleshootingQuestionsandAnswersfromliveWebcast
HowDoesLoadBalancingWork?
SampleConfigurationforBGPwithTwoDifferentServiceProviders(Multihoming)
HowBGPRoutersUsetheMultiExitDiscriminatorforBestPathSelection
BGPTechnologySupportPage
IPRoutingTechnologySupportPage
TechnicalSupport&DocumentationCiscoSystems
Wasthisdocumenthelpful?
OpenaSupportCase
Yes
No
(RequiresaCiscoServiceContract.)
RelatedCiscoSupportCommunityDiscussions
AsktheExpert:ConfiguringandTroubleshootingBorderGatewayPro...
expertVinitJain.AskquestionsfromMondayAugust10thtoFridayAugust21,2015BorderGateway...Protocol(BGP)
isoneofthemostwidelydeployedpr...
inWAN,RoutingandSwitching by ciscomoderator 5daysago LastReply 5daysago
BorderGatewayProtocol(BGP):Fundamentos,ConfiguraoeTrouble...
comMarcioFerreiraBemvindodiscussonaCSCemPortugus.Estasuaoportunidadedeaprenderefazer
todasasperguntasquequeirasobreBorderG...
inRouting&Switching by CiscoModerador 2yearsand1monthago LastReply 2yearsand1monthago
AsktheExpert:ConfiguringandTroubleshootingBorderGatewayPro...
WithSandeepSharmaWelcometotheCiscoSupportCommunityAsktheExpertconversation.Thisisanopportunityto
learnandaskquestionsaboutissuesenc...
inWAN,RoutingandSwitching by ciscomoderator 1yearand10monthsago LastReply 1yearand6monthsago
DoestheCisco3600SeriesRouterSupportFullBGP?
IfitsupportsafullBorderGatewayProtocol(BGP)routetableandmultipleneighbors,whatistherecommendedamountof
memory?OtherNetworkInfrastructu...
inOtherNetworkInfrastructureSubjects by admin 13yearsand1monthago LastReply 13yearsand1monthago
OIRonCatalyst6500
GatewayProtocol(BGP),orMultiprotocolLabelSwitching(MPLS)LabelDistributionProtocol(LDP)...3seconds.This
candisrupttheadjacenciesinprotoc...
inLAN,SwitchingandRouting by ssieger 22daysago LastReply 22daysago
TheCiscoSupportCommunityisaforumforyoutoaskandanswerquestions,sharesuggestions,and
collaboratewithyourpeers.
RefertoCiscoTechnicalTipsConventionsforinformationonconventionsusedinthisdocument.
Updated:Aug23,2005
DocumentID:13762
InformationFor
News&Alerts
Support
AboutCisco
SmallBusiness
Newsroom
Downloads
InvestorRelations
MidsizeBusiness
Blogs
Documentation
CorporateSocialResponsibility
ServiceProvider
FieldNotices
Executives
SecurityAdvisories
Industries
TechnologyTrends
LearningNetwork
Cloud
SupportCommunity
Marketplace
InternetofThings(IoT)
Contacts
Mobility
ContactCisco
SoftwareDefinedNetworking(SDN)
Communities
DevNet
VideoPortal
FindaPartner
EnvironmentalSustainability
TomorrowStartsHere
OurPeople
Careers
SearchJobs
LifeatCisco
Programs
CiscoDesignatedVIPProgram
CiscoPowered
17/18
14/08/2015
FinancingOptions
Contacts |
Feedback | Help | SiteMap | Terms&Conditions | PrivacyStatement | CookiePolicy | Trademarks
18/18

Load Sharing With BGP in Single and Multihomed Environments - Sample Configurations - Cisco

Uploaded by

Document Information

Original Title

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

Load Sharing With BGP in Single and Multihomed Environments - Sample Configurations - Cisco

Uploaded by

Copyright:

Available Formats

14/08/2015

Feedback | Help | SiteMap | Terms&Conditions | PrivacyStatement | CookiePolicy | Trademarks

You might also like