Escolar Documentos
Profissional Documentos
Cultura Documentos
Free Resources
View Archives
CCIE Bloggers
15 HowbasicareRIPtimers?Testyourknowledgenow.
PostedbyINEInstructorinCCIE4.0,CCIEGeneral,CCIER&S,CCIER&SWritten,CCIESP
10Comments
Apr
Search
Search
Submit
Sometimesitsthesimplethingsthatarestruggledwith.RIPisoneofthose.MostCCIEcandidates
understandthatwecanchangetheinterfaceorglobalparametersforupdates,unicast,multicast,etc.
Whatdoestakesometime,isfiguringouttheglobaltimers,especiallyifapersonisnotsurehowthey
interact.
Categories
SelectCategory
Inthispost,wewilladdresstheRIPprocessleveltimersforupdate,invalid,holddownandflush.Idontwantyou
tosleep duringthis, so we will save that one for later.
TimersBasic,allinseconds:
Update:howoftentosendupdatesinseconds
Invalid:howmanyseconds,sinceseeingavalidupdate,toconsidertherouteinvalid,andplacingtherouteinto
holddown
Hold Down:Onceinholddown,howlong(inseconds)tonotbelieveanyequalorlessimpressive(worse)route
updatesforroutesthatareinholddown
Flush:howmanyseconds,sincethelastvalidupdate,untilwethrowthatrouteinthetrash(garbagecollectionfor
unlovednonupdatedroutes)
Hereisourtopology.KeepyourattentiononR2,andthatwillbethefocalpointforthislesson.
Letssetupsomeuniquevalues,sowecanseetheresults.
Defaultsare:
Update:30
Invalid:180
HoldDown:180
Flush:240
Wewilluse30,40,10and90respectively.
R2(config)#routerrip
R2(config-router)#timersbasic30401090
Wecanseetheresultsofourchangeswithshowipprotocols.
R2#showipprotocols
RoutingProtocolis"rip"
Outgoingupdatefilterlistforallinterfacesisnotset
Incomingupdatefilterlistforallinterfacesisnotset
Sendingupdatesevery30seconds,nextduein23seconds
Invalidafter40seconds,holddown10,flushedafter90
Redistributing:rip
Defaultversioncontrol:sendversion2,receiveversion2
CCIE Bloggers
InterfaceSendRecvTriggeredRIPKey-chain
FastEthernet0/022
BrianDennisCCIE#2210
FastEthernet0/122
Routing&Sw itching
ISPDial
Security
ServiceProvider
Voice
Automaticnetworksummarizationisnotineffect
Maximumpath:4
RoutingforNetworks:
10.0.0.0
BrianMcGahanCCIE#8593
RoutingInformationSources:
Routing&Sw itching
Security
ServiceProvider
GatewayDistanceLastUpdate
10.23.0.312000:00:03
Distance:(defaultis120)
PetrLapukhovCCIE#16379
WecanseethatR2islearning2routesfromR3,the10.33.0.0/24and10.77.0.0/24R2receivedthelastupdate7
secondsago,basedontheoutput.
Routing&Sw itching
Security
ServiceProvider
Voice
MarkSnow CCIE#14073
R2#showiproute
Voice
Security
Codes:C-connected,S-static,R-RIP,M-mobile,B-BGP
D-EIGRP,EX-EIGRPexternal,O-OSPF,IA-OSPFinterarea
N1-OSPFNSSAexternaltype1,N2-OSPFNSSAexternaltype2
Popular Posts
E1-OSPFexternaltype1,E2-OSPFexternaltype2
i-IS-IS,su-IS-ISsummary,L1-IS-ISlevel-1,L2-IS-ISlevel-2
New CCIESecurity5Day
ia-IS-ISinterarea,*-candidatedefault,U-per-userstaticroute
BootcampandATCSamples
o-ODR,P-periodicdownloadedstaticroute
222HoursofVoiceContentNow
AvailableinCDNStreamingand
Gatewayoflastresortisnotset
Dow nloadableFormat
10.0.0.0/24issubnetted,4subnets
New CCIESecurityATCNow
C10.12.0.0isdirectlyconnected,FastEthernet0/1
AvailableinStreamingand
C10.23.0.0isdirectlyconnected,FastEthernet0/0
Dow nloadFormats
R10.34.0.0[120/1]via10.23.0.3,00:00:07,FastEthernet0/0
R10.77.0.0[120/8]via10.23.0.3,00:00:07,FastEthernet0/0
Letsenabledebuggingsowecanseetheplaybyplay.
R2#debugiprouting
IProutingdebuggingison
R2#debugiprip
RIPprotocoldebuggingison
R2#
01:24:23:RIP:receivedv2updatefrom10.23.0.3onFastEthernet0/0
01:24:23:10.34.0.0/24via0.0.0.0in1hops
01:24:23:10.77.0.0/24via0.0.0.0in8hops
R2#
01:24:24:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/1(10.12.0.2)
01:24:24:RIP:buildupdateentries
01:24:24:10.23.0.0/24via0.0.0.0,metric1,tag0
01:24:24:10.34.0.0/24via0.0.0.0,metric2,tag0
01:24:24:10.77.0.0/24via0.0.0.0,metric9,tag0
R2#
01:24:27:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/0(10.23.0.2)
01:24:27:RIP:buildupdateentries
01:24:27:10.12.0.0/24via0.0.0.0,metric1,tag0
AftertheupdatefromR3,learnedonFa0/0,IusedthepassiveinterfacedefaultcommandonR3insideofthe
routerripprocess.Whilewewaitfortheinvalidtimetooccur,duetothemissingroutes,wecanentertain
ourselvesbyseeingupdatesbeingsentfromR2,at30secondintervals.
R2#
01:24:53:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/1(10.12.0.2)
01:24:53:RIP:buildupdateentries
01:24:53:10.23.0.0/24via0.0.0.0,metric1,tag0
01:24:53:10.34.0.0/24via0.0.0.0,metric2,tag0
01:24:53:10.77.0.0/24via0.0.0.0,metric9,tag0
R2#
01:24:56:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/0(10.23.0.2)
01:24:56:RIP:buildupdateentries
01:24:56:10.12.0.0/24via0.0.0.0,metric1,tag0
Ithasbeen40secondssincethelastupdatesfromR3,and40secondswasourinvalidtimersetting.(Ourlast
updatewas1:24:23,andnowitis1:25:03).Theroutesenterholddown,whichmeansthe router will not
believe any newupdatesregardingtheseroutes.Holddownisintendedtoassistinavoidinginaccuraterouting
byrumorinformationwhilethenetworkconverges.Theexceptionwouldbeifaroutewithabetter(lower)metric
wasreceivedbyR2forthe10.77.0.0,R2woulduseit.(Inourexample,10.77.0.0hadametricof8.IfR2
learnedaboutthe10.77.0.0withametricof7orlowerfromaneighbor,itwoulduseitiflearnedduringthehold
down.)
R2#
01:25:03:RT:deleterouteto10.34.0.0via10.23.0.3,ripmetric[120/1]
01:25:03:RT:noroutesto10.34.0.0,enteringholddown
01:25:03:RT:NET-RED10.34.0.0/24
01:25:03:RT:deleterouteto10.77.0.0via10.23.0.3,ripmetric[120/8]
01:25:03:RT:noroutesto10.77.0.0,enteringholddown
01:25:03:RT:NET-RED10.77.0.0/24
R2advertisesapoisonedrouteforthenetworksinholddown.Thisisatriggeredupdate,andnotbasedonthe
normal30secondupdatetimer.
R2#
01:25:05:RIP:sendingv2flashupdateto224.0.0.9viaFastEthernet0/0(10.23.0.2)
01:25:05:RIP:buildflashupdateentries
01:25:05:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:05:10.77.0.0/24via0.0.0.0,metric16,tag0
01:25:05:RIP:sendingv2flashupdateto224.0.0.9viaFastEthernet0/1(10.12.0.2)
01:25:05:RIP:buildflashupdateentries
01:25:05:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:06:10.77.0.0/24via0.0.0.0,metric16,tag0
R1,sendsusapoisonreverseupdate,regardingthesamenetworks.Thisintentionallyoverridesthesplithorizon
rulewhichisinplaceonEthernetinterfacesbydefault.
R2#
01:25:08:RIP:receivedv2updatefrom10.12.0.1onFastEthernet0/1
01:25:08:10.34.0.0/24via0.0.0.0in16hops(inaccessible)
01:25:08:10.77.0.0/24via0.0.0.0in16hops(inaccessible)
R2#
01:25:10:RIP:receivedv2updatefrom10.12.0.1onFastEthernet0/1
01:25:10:10.34.0.0/24via0.0.0.0in16hops(inaccessible)
01:25:10:10.77.0.0/24via0.0.0.0in16hops(inaccessible)
Anothernormalupdate,beingsentbyR2,includingthepoisonedroutes.
R2#
01:25:22:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/1(10.12.0.2)
01:25:22:RIP:buildupdateentries
01:25:22:10.23.0.0/24via0.0.0.0,metric1,tag0
01:25:22:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:22:10.77.0.0/24via0.0.0.0,metric16,tag0
01:25:22:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/0(10.23.0.2)
01:25:22:RIP:buildupdateentries
01:25:22:10.12.0.0/24via0.0.0.0,metric1,tag0
01:25:22:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:22:10.77.0.0/24via0.0.0.0,metric16,tag0
Whiletheroutesareinholddown,therouterstillforwardspacketstothosenetworks,basedonthelast
informationthatitlastlearnedabouthowtoreachthosenetworks.Therouteswillshowupaspossiblydown
.
R2#showiproute
Codes:C-connected,S-static,R-RIP,M-mobile,B-BGP
D-EIGRP,EX-EIGRPexternal,O-OSPF,IA-OSPFinterarea
N1-OSPFNSSAexternaltype1,N2-OSPFNSSAexternaltype2
E1-OSPFexternaltype1,E2-OSPFexternaltype2
i-IS-IS,su-IS-ISsummary,L1-IS-ISlevel-1,L2-IS-ISlevel-2
ia-IS-ISinterarea,*-candidatedefault,U-per-userstaticroute
o-ODR,P-periodicdownloadedstaticroute
Gatewayoflastresortisnotset
10.0.0.0/24issubnetted,4subnets
C10.12.0.0isdirectlyconnected,FastEthernet0/1
C10.23.0.0isdirectlyconnected,FastEthernet0/0
R10.34.0.0/24ispossiblydown,
routingvia10.23.0.3,FastEthernet0/0
R10.77.0.0/24ispossiblydown,
routingvia10.23.0.3,FastEthernet0/0
Sowereistheremovaloftheholddown.Thetimerwasonly10seconds?Betterlatethannever.Eventhoughthe
holddowntimerwassetto10seconds,theholddowntimerhastoexpireandthenthenextpoisonedroute
receivedcausestheroutestoberemovedfromholddown.Ourrouteswentintoholddownat25:03,itisnow
25:36.Regardlessoftheholddowntimersetting,ifwedidntreceiveanypoisonedupdatesfromneighbors,
theholddownwouldstayuntiltheflushtimerremovestheroutecompletely.
R2#
01:25:36:RIP:receivedv2updatefrom10.12.0.1onFastEthernet0/1
01:25:36:10.34.0.0/24via0.0.0.0in16hops(inaccessible)
01:25:36:RT:10.34.0.0cameoutofholddown
01:25:36:10.77.0.0/24via0.0.0.0in16hops(inaccessible)
01:25:36:RT:10.77.0.0cameoutofholddown
Eventhoughtheroutesaredonewiththeirholddown,R2stillwillshowtherouteaspossiblydown,andwill
continuetodosountiltheflushtimerexpires.
R2#showiproute
Codes:C-connected,S-static,R-RIP,M-mobile,B-BGP
D-EIGRP,EX-EIGRPexternal,O-OSPF,IA-OSPFinterarea
N1-OSPFNSSAexternaltype1,N2-OSPFNSSAexternaltype2
E1-OSPFexternaltype1,E2-OSPFexternaltype2
i-IS-IS,su-IS-ISsummary,L1-IS-ISlevel-1,L2-IS-ISlevel-2
ia-IS-ISinterarea,*-candidatedefault,U-per-userstaticroute
o-ODR,P-periodicdownloadedstaticroute
Gatewayoflastresortisnotset
10.0.0.0/24issubnetted,4subnets
C10.12.0.0isdirectlyconnected,FastEthernet0/1
C10.23.0.0isdirectlyconnected,FastEthernet0/0
R10.34.0.0/24ispossiblydown,
routingvia10.23.0.3,FastEthernet0/0
R10.77.0.0/24ispossiblydown,
routingvia10.23.0.3,FastEthernet0/0
Anotherupdateclicksoff,andthenweapproachthe90secondflushtimer
R2#
01:25:49:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/1(10.12.0.2)
01:25:49:RIP:buildupdateentries
01:25:49:10.23.0.0/24via0.0.0.0,metric1,tag0
01:25:49:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:49:10.77.0.0/24via0.0.0.0,metric16,tag0
01:25:49:RIP:sendingv2updateto224.0.0.9viaFastEthernet0/0(10.23.0.2)
01:25:49:RIP:buildupdateentries
01:25:49:10.12.0.0/24via0.0.0.0,metric1,tag0
01:25:49:10.34.0.0/24via0.0.0.0,metric16,tag0
01:25:49:10.77.0.0/24via0.0.0.0,metric16,tag0
Basedonthelastvalidupdateof1:24:23,andnowthatitis1:25:53,90secondsareup(flushtimer)andthe
routesaredeleted.
R2#
01:25:53:RT:deletesubnetrouteto10.34.0.0/24
01:25:53:RT:NET-RED10.34.0.0/24
01:25:53:RT:deletesubnetrouteto10.77.0.0/24
01:25:53:RT:NET-RED10.77.0.0/24
Nowtheroutesdontshowupintheroutingtableeither.
R2#showiproute
Codes:C-connected,S-static,R-RIP,M-mobile,B-BGP
D-EIGRP,EX-EIGRPexternal,O-OSPF,IA-OSPFinterarea
N1-OSPFNSSAexternaltype1,N2-OSPFNSSAexternaltype2
E1-OSPFexternaltype1,E2-OSPFexternaltype2
i-IS-IS,su-IS-ISsummary,L1-IS-ISlevel-1,L2-IS-ISlevel-2
ia-IS-ISinterarea,*-candidatedefault,U-per-userstaticroute
o-ODR,P-periodicdownloadedstaticroute
Gatewayoflastresortisnotset
10.0.0.0/24issubnetted,2subnets
C10.12.0.0isdirectlyconnected,FastEthernet0/1
C10.23.0.0isdirectlyconnected,FastEthernet0/0
Ifweusecontextsensitivehelp,wefindonemoreparameterforthetimers:
R2(config-router)#timersbasic30401090?
<1-4294967295>Sleeptime,inmilliseconds
Andwellsavethatoneforanotherblog.
Bestwishes,
Keith
Tags:ccie,CCNA,CCNP,cisco,lab
DownloadthispageasaPDF
About INE Instructor:
Find all posts by INE Instructor|Visit Website
Youcanleavearesponse,ortrackbackfromyourownsite.
10ResponsestoHowbasicareRIPtimers?Testyourknowledgenow.
April16,2010at1:17am
Ian Finlayson
ExcellentBlogKeith.Thanksforthat!!!
ReallycoverstheRIPtimersinthedetailwewouldwant
Cheers,
Ian.
Reply
April18,2010at11:23am
Michal
thanksKeithforcoveringthatinalabformandwaitingforthesleeptimewalkthrough.
salutations,
michal
Reply
April18,2010at8:18pm
Rob Fleury
GreatpostKeith!Howaboutdoingthedetailonwhenaninterface
actuallyfails?Sinceaflashupdateandthenregularupdateswouldbesent,howdothetimersrespond/act?
Keepuptheexcellentwork!
Rob.
Reply
April20,2010at3:43am
Ronnie_hitman
GreatpostThumb;suptoAnthony
Reply
April20,2010at3:44am
Ronnie_hitman
SorryihadAnthonyonmymind.AnywaysthanksKEITH..
Reply
April20,2010at8:22am
ARaaz
Veryinformative,youvedoneitagainKeith.
YouwokemeupfromsleepLoL.
Reply
June26,2010at11:53pm
Somit Maloo
Superbexplanation.Keithatitsbestasalways
Reply
November29,2010at7:13am
Raj
Hi,
RouterR2enteredinHolddownstateat
01:25:03:RT:noroutesto10.34.0.0,enteringholddown
01:25:03:RT:NETRED10.34.0.0/24,
HerewesettedHolddowntimeras10secfromInvaid.Thenwhyitsnotcomeoutfromholdownat01:25:13,
Hereitscameoutaround
01:25:36:10.34.0.0/24via0.0.0.0in16hops(inaccessible)
01:25:36:RT:10.34.0.0cameout.
Plsclarify.
Reply
December31,2010at8:26pm
AlexF
>Plsclarify.
OPsays,Regardlessoftheholddowntimersetting,ifwedidntreceiveanypoisonedupdatesfromneighbors,theholddown
wouldstay(untiltheflushtimerremovestheroutecompletely).
OPimpliesthatexpiryofholddowntimeronitsownisnotsufficientfortheroutestoberemovedfromholddownan
updateisrequired.
Reply
February11,2011at12:04pm
vgm
Resultsweredifferentfromwhatwasexplained.Iexpectedtheflushtimertobeginuponreceiptofvalidupdate.Instead,theflush
timer,liketheholddowntimer,starteduponexpirationoftheinvalidtimer.Iconnectedfourrouters,configuringeachwithrip
version2,andtrieddifferentvaluesforthetimers.Specifictimervaluesusedwere,306090120,204060100,andthedefaulttimer
values,30180180240.IdeletedthelinkbetweenRouter1andRouter2andobservedthedebugoutputfromRouter3.
Reply
LeaveaReply
Name(required)
Mail(willnotbepublished)(required)
Website
Submit Comment
CiscobuysComptelforabout$31
millionhttp://t.co/EgPg5u3
Homedow nloadsareontherise,
Ciscosurveysays
http://t.co/03bUVqx
Xeroxw illmanageCisco'sglobal
printoperationshttp://t.co/5fU54HZ
twitter.com/inetraining
2010InternetworkExpert,Inc.,AllRightsReserved
pdfcrowd.com