EIGRP CCNP Route

59 Chapter 1: Basic Network and Routing Concepts
Chapter 2
EIGRP Implementation
Thischaptercoversthefollowingtopics:
EstablishingEIGRPNeighborRelationships
BuildingtheEIGRPTopologyTable
Optimizing EIGRPBehavior
ConfiguringEIGRPforIPv6
NamedEIGRPConfiguration
EnhancedInteriorGatewayRoutingProtocol(EIGRP)isanadvanceddistancevector
routingprotocoldesignedbyCisco.Thebasiccongurationissimpleandeasyto
understand,soitiscommonlyusedinsmallernetworks.Itsadvancedfeatures,which
providerapidconvergence,higherscalability,andsupportformultipleroutedprotocols,
fulllrequirementsincomplexnetworkenvironments.
EIGRPsupportsbothIPv4andIPv6.AlthoughstandardEIGRPconguration
betweenIPv4andIPv6differs,itcanbeuniedusingnewlyintroducednamedEIGRP
congurationmode.
Uponcompletingthischapter,youwillbeabletodothefollowing:
ExplainEIGRPneighborrelationships
ExplainhowEIGRPchoosesthebestpaththroughthenetwork
Configurestubrouting,routesummarization,andloadbalancingwithEIGRP
ConfigurebasicEIGRPforIPv6andoptimizeitwithroutesummarization
ConfigureEIGRPthroughnamedconfiguration
60 Chapter 2: EIGRP Implementation
Establishing EIGRP Neighbor Relationships

EIGRPwasdevelopedasanenhancedversionoftheolderInteriorGatewayRouting
Protocol(IGRP)protocolandhasmanyofthesamecharacteristicsofanadvanced
Interior GatewayProtocol,suchashighspeedconvergence,partialupdates,andthepos
sibilitytosupportmultiplenetworklayerprotocols.ThefirststepinconfiguringEIGRP
istoestablishEIGRPneighborrelationshipsoverthevariousinterfacetypes.Itisimpor
tanttoknowhowtoverifythesehavebeenproperlyformedandhowparameterslike
helloandholdtimersanddifferentWANtechnologiesinfluencesessionestablishment.
Uponcompletionofthissection,youwillbeabletodothefollowing:
DescribeEIGRPcharacteristics
DescribehowEIGRPensuresreliabletransport
DescribethestepsthatEIGRPfollowstoaddroutestotheroutingtable
ChangeEIGRPtimers
DescribewhereEIGRPadjacenciesareformedinaFrameRelaynetwork
DescribewhereEIGRPadjacenciesareformedinaLayer3MPLSVPNnetwork
DescribewhereEIGRPadjacenciesareformedinaLayer2MPLSVPN Ethernet
network
EIGRP Features
KeycapabilitiesthatdistinguishEIGRPfromotherroutingprotocolsinclude fastcon
vergence,supportforvariablelengthsubnetmasking(VLSM),partialupdates,and
supportformultiplenetworklayerprotocols.Basicdescriptionofprotocoldesignand
architecturehasbeenpublishedasanInformationalRFCthatallowsCiscotoretaincon
trolofEIGRPandcustomerexperiencewhileopeningittoothervendorsto promote
interoperability.
EIGRPisaCiscoproprietaryprotocolthatcombinestheadvantagesoflinkstateand
distancevectorroutingprotocols.However,EIGRPisadistancevectorroutingprotocol.
EIGRPincludesadvancedfeaturesnotfoundinotherdistancevectorprotocols,like
RIP,whichiswhyitisreferredtoasanadvanceddistancevectorroutingprotocol.
LikeitspredecessorIGRP,EIGRPiseasytoconfigureandisadaptabletoawidevariety
ofnetworktopologies.WhatmakesEIGRPanadvanced distancevectorprotocolisthe
additionofseveralfeaturesfoundinlinkstateprotocols,suchasdynamicneighbordis
covery.EIGRPisanenhanced IGRPbecauseofitsrapidconvergenceandtheguarantee
ofaloopfreetopologyatalltimes.Featuresofthisprotocolincludethefollowing:
Fastconvergence:EIGRPusesthediffusingupdatealgorithm(DUAL)toachieve
rapidconvergence.ArouterrunningEIGRPstoresitsneighborsroutingtablesso
thatitcanquicklyadapttochangesinthenetwork.Ifnoappropriaterouteexistsin
Establishing EIGRP Neighbor Relationships 61
thelocalroutingtableandnoappropriatebackuprouteexistsinthetopologytable,
EIGRPqueriesitsneighborstodiscoveranalternativeroute.Thesequeriesareprop
agateduntilanalternativerouteisfoundoruntilitisdeterminedthatnoalternative
routeexists.
Partialupdates:EIGRPsendspartialtriggeredupdatesratherthanperiodic updates.
Theseupdatesaresentonlywhenthepathorthemetricforaroutechanges.They
containinformationaboutonlythatchangedlinkratherthantheentirerouting
table.Propagationofthesepartialupdatesisautomaticallyboundedsothatonly
thoseroutersthatrequiretheinformationareupdated.Asaresult,EIGRPconsumes
significantlylessbandwidththanIGRP.Thisbehavioralsodiffersfromlinkstate
protocoloperation,whichsendsachangeupdatetoallrouterswithinanarea.
Multiplenetworklayersupport:EIGRPsupportsIPVersion4(IPv4)andIP
Version6(IPv6)usingprotocoldependentmodulesthatareresponsibleforpro
tocolrequirementsspecifictothenetworklayer.EIGRPsrapidconvergenceand
sophisticatedmetricoffersuperiorperformanceandstabilitywhenimplementedin
IPv4andIPv6networks.
Useofmulticastandunicast:Forcommunicationbetweenrouters,EIGRPuses
multicastandunicastratherthanbroadcast.Asaresult,endstationsareunaffected
byroutingupdatesorqueries.ThemulticastaddressusedforEIGRPforIPv4is
224.0.0.10,andthemulticastaddressforEIGRPforIPv6isFF00::A.
Note EIGRPpreviouslywascalledahybridprotocol,whichisnotaccurateandsoitis
nolongerused.EIGRPisnotacombinationofadistancevectorandlinkstaterouting
protocol,but adistancevectorroutingprotocolwithfeaturesfoundinalinkstate
protocol. Therefore, currently the term advanced distance vector is typically used to
describe EIGRP.

OtherEIGRPfeaturesincludethefollowing:
VLSMsupport:EIGRPisaclasslessroutingprotocol,whichmeansthatitadvertises
asubnetmaskforeachdestinationnetwork.ThisenablesEIGRPtosupportdiscon
tinuous subnetworksandVLSM.
Seamlessconnectivityacrossalldatalinklayerprotocolsandtopologies:EIGRP
doesnotrequirespecialconfigurationtoworkacrossanyLayer2protocols.Other
routingprotocols,suchasOpenShortestPathFirst(OSPF)Protocol,requiredif
ferentconfigurationsfordifferentLayer2protocols,suchasEthernetandFrame
Relay.EIGRPwasdesignedtooperateeffectivelyinbothLANandWANenviron
ments.WANsupportfordedicatedpointtopointlinksandnonbroadcastmulti
access(NBMA)topologiesisstandardforEIGRP.EIGRPaccommodatesdifferences
inmediatypesandspeedswhenneighboradjacenciesformacrossWANlinksand
canbeconfiguredtolimittheamountofbandwidththattheprotocoluses on
WANlinks.
Sophisticatedmetric:EIGRPrepresentsmetricvaluesina32bitformattoprovide
enough granularity.EIGRPsupportsunequalmetricloadbalancing,whichallows
administratorstodistributetrafficflowmoreefficientlyintheirnetworks.
Note ThetermIP isusedforgenericIPandappliestobothIPv4andIPv6.Otherwise,

thetermsIPv4 andIPv6 areusedforthespecificprotocols.

Note Althoughthereissomereview,thischapterassumesthereader hasbasicCCNA

knowledgeofEIGRP.IfyouneedamorethoroughreviewofEIGRPorotherrouting
protocols,seeRouting Protocols Companion Guide (CiscoPress,2014).

EIGRP Features
OneofthekeytechnologiesusedinEIGRPisRTP(ReliableTransportProtocol),which
isusedforthereliableexchangeofinformation.
AsshowninFigure21,EIGRPrunsdirectlyabovetheIPlayerasitsownprotocol,
numbered88.RTPisthecomponentoftheEIGRPresponsibleforguaranteed,ordered
deliveryofEIGRPpacketstoallneighbors.Itsupportsintermixedtransmissionof
multicastorunicastpackets.Whenusingmulticastonthesegment,packetsaresentto
EIGRPs reservedmulticastaddress224.0.0.10forIPv4andFF00::AforIPv6.
88 - EIGRP
6 - TCP
17 - UDP

Frame Payload
Frame IP C
Header Header Packet Payload R
Protocol C
Number
Figure 2-1 EIGRP Encapsulation

Forefficiencyreasons,RTPsendsonlycertainEIGRPpacketsreliably,whichmeansthe
recipientisrequiredtosendanEIGRPacknowledgment.Forexample,onamultiaccess
networkthathasmulticastcapabilities,suchasEthernet,itisnotnecessarytosendhello
packetsreliablytoallneighborsindividually.Inthiscase,EIGRPsendsasinglemulticast
hellopacketcontaininganindicatorthatinformsthereceiversthatthepacketdoesnot
needtobeacknowledged.Othertypesofpackets,suchasupdates,containanindicator
inthepacketthatanacknowledgmentisrequired.Reliabletransportprotocolcansend
multicastpacketsquickly,evenwhenunacknowledgedpacketsarepending.Thischar
acteristicof theprotocolhelpstoensurethatconvergencetimeremainslowinthepres
enceofvaryinglinkspeeds.
EIGRP Operation Overview

OperationoftheEIGRPprotocolisbasedontheinformationstoredinthreetables:
neighbortable,topologytable,andtheroutingtable.
Themaininformationstoredintheneighbortableisasetofneighborswithwhich
EIGRProuterhasestablishedadjacencies.Neighborsarecharacterizedbytheirprimary
IPaddressandthedirectlyconnectedinterfacethatleadstothem.
Thetopologytablecontainsalldestinationroutesadvertisedbytheneighborrout
ers.Eachentryinthetopologytableisassociatedwithalistofneighborsthathave
advertised thedestination.Foreachneighbor,anadvertisedmetricisrecorded.Thisis
themetricthat aneighborstoresinitsroutingtabletoreachaparticular destination.
Anotherimportantinformationisthemetricthatarouterusestoreachthesamedesti
nation.Thisisthesumoftheadvertisedmetricfromtheneighborpluslinkcostto the
neighbor.Theroutewiththebestmetrictothedestinationiscalledthesuccessorandis
placedintheroutingtableandadvertisedtotheotherneighbors.
Theprocesstoestablishanddiscoverneighborroutesoccurssimultaneouslywith
EIGRP.Ahighleveldescriptionoftheprocessfollows,usingthetopologyinFigure22
asanexample.
R1 R2
I am router R1.

1 Hello
Hello, I am router R2.
Neighbor Neighbor
Table Here is my complete routing Hello 2 Table
information.

Update
4 Thanks for the information!
Topology Topology
Table 3 ACK Here is my complete routing Table
information.

Update

5
Thanks for the information!
Routing Converged Routing
Table ACK
6 Table
Figure 2-2 EIGRP Operation Overview

1. Anewrouter(routerR1inthisexample)comesuponthelinkandsendsahello
packetthroughallitsEIGRPconfiguredinterfaces.
2. Routersthatarereceivingthehellopacket(R2)ononeinterfacereplywithupdate
packetsthatcontainalltheroutesthattheyhaveintheirroutingtables,except
those thatarelearnedthroughthatinterface(splithorizon).R2sendsanupdate
packettoR1,butaneighborrelationshipisnotestablisheduntilR2sendsahello
packettoR1.TheupdatepacketfromR2hastheinitializationbitset,indicating
thatthisistheinitializationprocess.Theupdatepacketincludesinformationabout
theroutesthattheneighbor(R2)isawareof,includingthemetricthattheneighbor
isadvertisingforeachdestination.
3. Afterbothroutershaveexchangedhellosandtheneighboradjacencyisestablished,R1
repliestoR2withanACKpacket,indicatingthatitreceivedtheupdateinformation.
4. R1assimilatesalltheupdatepacketsinitstopologytable.Thetopologytable
includesalldestinationsthatareadvertisedbyneighboringadjacentrouters.Itlists
eachdestination,alltheneighborsthatcanreachthedestination,andtheirassoci
atedmetric.
5. R1sendsanupdatepackettoR2.
6. Uponreceivingtheupdatepacket,R2sendsanACKpackettoR1.
AfterR1andR2successfullyexchangeupdatepackets,theyarereadytoupdatetheir
routingtableswiththesuccessorroutesfromthetopologytable.
Configuring and Verifying Basic EIGRP for IPv4

UsingthetopologyinFigure23,thissectiondiscussesbasicEIGRPconfiguration,
includinghowtoconfiguretheEIGRPprocess,analyzeneighboradjacency,andcon
figuredifferenthelloandholdtimers.Thissectionalsodemonstrateshowtooptimize
EIGRPbehaviorbyconfiguringpassiveinterfaces.
Lo0
BR1
192.168.1.0/24
172.16.1.0/30
172.16.2.0/30
Lo0 Eth0/0 Eth0/0 Lo0
HQ WAN
192.168.0.0/24 BR2
172.16.3.0/30 192.168.2.0/24
Frame Relay
Lo0
BR3
192.168.3.0/24
Figure 2-3 Basic EIGRP Topology
Example21showsEIGRPenabledonbothinterfacesusingthenetworkcommandand
autonomoussystemnumber100.
Example 2-1 Configuration of EIGRP on BR1

BR1> enable
BR1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
BR1(config)# router eigrp 100
BR1(config-router)# network 172.16.1.0
BR1(config-router)# network 192.168.1.0
ToestablishEIGRPneighborrelationshipbetweenthetworouters,bothroutersmust
belongtothesameautonomoussystem.Theautonomoussystemnumberuniquelyiden
tifiestheEIGRPprocessontherouterandisusedtodefinetheEIGRProutingdomain.
RoutersfromthesameroutingdomainwillexchangeEIGRProutesandthoserouteswill
bemarkedasEIGRPinternalroutes.Routerswithdifferentautonomoussystemnumbers
willnotexchangeroutinginformation.RoutersintwoseparateEIGRPdomains,having
differentautonomoussystemnumbers,musthaveredistributionconfiguredtoshare
routing information.
Tostart theEIGRProutingprocessontherouter,configureitusingtheroutereigrp
autonomous-system-number command.
ToincludeoneormorelocalinterfacesintheEIGRPprocessusethenetwork
ip-address [wildcard-mask] command. Interfaces matched bythe network command
willbeenabledwithEIGRPandwillstarttosendandreceiveEIGRPpackets.
The wildcardmaskisoptionalandifomittedtheEIGRPprocessassumesthatalldirectly
connectednetworksthatarepartofthemajorclassnetworkwillparticipateintherout
ingprocess.EIGRPwillattempttoestablishneighborrelationships fromeachinterface
thatispartofthatClassA,B,orCmajornetwork.Forexample,iftherearetwoClass
Bsubnets 172.16.1.0/30 and172.16.2.0/30 on interfacesandthe network 172.16.0.0
isconfiguredwithoutthewildcardmask,youwillincludebothinterfacesinthe
EIGRPprocess.EIGRPwillassumethedefaultwildcardmaskfortheClass Bnetwork
(0.0.255.255)whendeterminingwhichinterfacestoincludeinEIGRP.
Next,EIGRPonBR2isconfigured,showninExample22.Thewildcardmaskparameter
isusedtolimitwhichinterfaceswillbeincludedintheEIGRPprocess.Ifyouwantto
includeonlythe172.16.2.0/30subnetintheEIGRPprocess,youmustissuethenetwork
172.16.2.00.0.0.3command.Withall0sinthethirdwildcardmaskoctet,youstatethat
thethirdoctetofthenetworkIPv4addressmustmatchvalueof2.Withthelastoctet
setto3,thelast3bitsarenotverified,andotherbitsmustmatchvaluesdefinedinthe
networkIPaddress.
Note Thewildcardmaskcanalsobethoughtofastheinverseofasubnetmask.Ina
wildcardmask,thenetworkbitsarerepresentedby0s,andthehostbitsarerepresented
by1s.Theinverseofsubnetmask255.255.255.252is0.0.0.3.


BR2(config-router)# network 172.16.2.0 0.0.0.3
Toenableonlyaspecificinterfaceontherouter,thewildcardmask0.0.0.0canbeused
tospecificallymatchallfouroctetsoftheinterfaceaddress.Toenableallinterfaces on
therouter forroutingprotocol,theaddressandwildcardmaskcombinationof0.0.0.0
255.255.255.255isusedtomatchallinterfaces.
Next,theBR3routerisenabledforEIGRPinautonomoussystem100onallinterfaces
inExample23.EachrouterinanEIGRProutingdomainisidentifiedbyitsrouterID.It
isusedby aroutereachtimeitiscommunicatingwithitsEIGRPneighbors.EIGRProut
erIDisalsousedforvalidatingoriginofexternalroutes.Ifanexternalrouteisreceived
withalocalrouterID,therouteisdiscarded.Youcansettherouter IDmanuallyusing
theeigrprouteridrouter-id command.TherouterIDisa32bitvalueandisconfigured
asanyIPv4addressexcept0.0.0.0and255.255.255.255.Aunique32bitvalueshouldbe
configuredforeachrouter.IftherouterIDisnotexplicitlyconfigured,therouterwill
selectthehighestaddressofitsloopbackinterfaces.Ifthereisnoloopbackinterfaceon
therouter,itwillselectthehighestIPv4addressofanyotheractivelocalinterface.The
routerIDis notchangedunlesstheEIGRPprocessisclearedoriftherouterIDismanu
ally configured.

BR3(config-router)# eigrp router-id 192.168.3.255
OnBR1,verifyEIGRPneighborrelationshipsusingtheshowipeigrpneighborscom
mandwiththeoptionaldetailkeywordattheend,asshowninExample24.
Example 2-4 Verifying EIGRP Neighbor Relationships on BR1
BR1# show ip eigrp neighbors

EIGRP-IPv4 Neighbors for AS(100)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num

0 172.16.1.1 Se0/0 13 01:29:20 17 102 0 11
BR1# show ip eigrp neighbors detail


(sec) (ms) Cnt Num

0 172.16.1.1 Se0/0 14 01:40:47 17 102 0 11
Version 7.0/3.0, Retrans: 0, Retries: 0, Prefixes: 5
Topology-ids from peer - 0
Thecommandoutputshowsyouneighborrelationshipsestablishedwithinanautono
mous system:
Hcolumnshowsyoutheorderinwhichpeeringsessionswereformed.
AddresscolumnshowsyoutheIPaddressoftheEIGRPpeer.
Interfacecolumnshowsyoutheinterfacetowhichthepeerisconnected.
Holdand Uptimecolumnsshowyoutheamountoftime,inseconds,thatthe
routerwillwaittohearfromitsEIGRPpeerbeforedeclaringitunreachableandthe
amounttimesincetheneighborrelationshipformed,respectively.
SRTTcolumnshowstheamountoftime,inmilliseconds,requiredfor therouterto
sendanEIGPpackettoitsneighborandreceiveanacknowledgmentforthatpacket.
RTOorRetransmissiontimeoutcolumnshowsyoutheamountoftimetherouter
waitsbeforesendingapacketfromtheretransmissionqueue.
QorQueuecountcolumnshowsyouthenumberofpacketsthatthesoftwareis
waitingtosend.Incaseofnetworkcongestion,thisnumberbecomesgreaterthan
zero.
Additionalinformationisdisplayedifyouusethedetailkeyword:
Retransshowsyouthenumberoftimesthatapackethasbeenretransmitted.
Retriesshowsyouthenumberoftimesanattemptwasmadetoretransmitthe
packet.
Prefixesisthenumberofprefixesreceivedfromthepeer.
InExample 25,theactiveEIGRPinterfacesaredisplayedonBR1usingtheshowip
eigrpinterfacescommand.
Example 2-5 Verifying the EIGRP Interfaces on BR1
BR1# show ip eigrp interfaces

EIGRP-IPv4 Interfaces for AS(100)
Xmit Queue PeerQ Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable Un/Reliable SRTT Un/Reliable Flow Timer Routes
Se0/0 1 0/0 0/0 17 0/16 88 0
Lo0 0 0/0 0/0 0 0/0 0 0
The InterfacecolumnintheoutputdescribeswhichinterfacesareincludedintheEIGRP
process,andthePeerscolumnindicatesthenumberofdirectlyconnectedEIGRPneigh
borsoveraspecifiedinterface.Formoredetails,usetheshowipeigrpinterfacesdetail
commandinExample26,whichshowsadditionalinformationlikenumberofsentpack
ets,numberofretransmits,andthevaluesofhellointervalandholdtimetimers.
Example 2-6 Verifying the EIGRP Interfaces Details on BR1
BR1# show ip eigrp interfaces detail

Se0/0 1 0/0 0/0 17 0/16 88 0
Hello-interval is 5, Hold-time is 15
Split-horizon is enabled
Next xmit serial <none>
Packetized sent/expedited: 5/1
Hello's sent/expedited: 16200/2
Un/reliable mcasts: 0/0 Un/reliable ucasts: 4/5
Mcast exceptions: 0 CR packets: 0 ACKs suppressed: 0
Retransmissions sent: 0 Out-of-sequence rcvd: 0
<Output omitted>
The EIGRPconfigurationonthepreconfiguredHQrouterisexaminednextusingthe
showipprotocolsandshowipeigrpinterfacescommands.
OutputoftheshowipprotocolscommandinExample27showswhich networkswere
includedintheEIGRPprocessandwhichroutinginformationsourcesexistinthis
case,those sourcescorrespondingtoWANIPaddressesbelongingtoBR1,BR2, and
BR3.
Example 2-7 Verifying the EIGRP Networks on HQ
HQ# show ip protocols

*** IP Routing is NSF aware ***
Routing Protocol is "eigrp 100"

<Output omitted>
Routing for Networks:
0.0.0.0
Routing Information Sources:
Gateway Distance Last Update
172.16.2.2 90 23:04:13
172.16.3.2 90 23:04:13
172.16.1.2 90 23:04:13
Distance: internal 90 external 170
TheoutputoftheshowipeigrpinterfacescommandinExample28showstheworking
interfacesonwhichEIGRPisenabled.NoticethatLoopback0doesnotpeerwithany
router.Inotherwords,ontheLoopback0interface,EIGRPpacketswillnotbereceived.
ThesamewouldbetrueforLANinterfacewheretherearenoadditionalroutersattach.
Topreservesomeresourcesandinstructrouterstostopsendingandreceivingpacketson
thespecificinterface,youcanconfiguresuchinterfacesaspassive.
Example 2-8 Verifying the EIGRP Interfaces Details on HQ

HQ# show ip eigrp interfaces
Et0/0 1 0/0 0/0 1 0/2 50 0
Se1/0 1 0/0 0/0 19 0/16 96 0
Se2/0 1 0/0 0/0 24 0/16 120 0
Lo0 0 0/0 0/0 0 0/0 0 0
Example29showsconfigureinterfacesaspassiveusingthepassiveinterfacedefault
command.
Example 2-9 Configuring Passive Interfaces as the Default

HQ(config)# router eigrp 100
HQ(config-router)# passive-interface default
*Sep 24 03:27:31.719: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.3.2
(Serial2/0) is down: interface passive
(Serial1/0) is down: interface passive
(Ethernet0/0) is down: interface passive
WhenthepassiveinterfacedefaultcommandisusedundertheEIGRPprocess,the
routerimmediatelystopssendingandreceivinghellopacketsandroutingupdatesonall
interfaces.Whenconfigured,allexistingneighborrelationshipsareterminated.
TodisablepassiveinterfaceforselectedinterfacesconnectingHQtoBRrouters,usethe
nopassiveinterfaceinterface-name command,asshowninExample 210.
Example 2-10 Disabling Passive Interfaces on HQ

HQ(config-router)# no passive-interface ethernet 0/0
(Ethernet0/0) is up: new adjacency
HQ(config-router)# no passive-interface serial 1/0
(Serial1/0) is up: new adjacency
HQ(config-router)# no passive-interface serial 2/0
(Serial2/0) is up: new adjacency
Afteryouconfigurethenopassiveinterfaceinterface-name onallinterfacesleading
totheBRrouters,therouterstartssendingEIGRPhellosandupdates,andthe EIGRP
neighborrelationshipsgetreestablished.
TheshowipprotocolscommandinExample211verifiestheconfiguration ofpassive
interfacesonHQ.Asindicatedintheoutput,onlyinterfaceLoopback0remainedcon
figuredaspassive.
Example 2-11 Verifying the Passive Interface on HQ

<Output omitted>
0.0.0.0
Passive Interface(s):
Passive Interface(s):
Loopback0
172.16.2.2 90 00:29:44
172.16.3.2 90 00:29:44
172.16.1.2 90 00:29:44
Todynamicallyobservethesendingandreceivingofhellopacketsinrealtime,youcan
enabledebuggingofEIGRPhellopacketswiththedebugeigrppacketshellocommand.
InExample212,debuggingofEIGRPhellopacketsusingthedebug eigrppacketshello
commandisenabledonBR1.After20seconds,debuggingisdisabledby issuingtheno
debugallcommand.
Example 2-12 Observing EIGRP Hello Packets on BR1
BR1# debug eigrp packets hello

(HELLO)
EIGRP Packet debugging is on
BR1#
*Sep 24 04:19:50.535: EIGRP: Sending HELLO on Serial0/0
*Sep 24 04:19:50.535: AS 100, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/
rely 0/0
*Sep 24 04:19:50.877: EIGRP: Received HELLO on Serial0/0 nbr 172.16.1.1
rely 0/0 peerQ un/rely 0/0
BR1#
*Sep 24 04:19:55.232: EIGRP: Sending HELLO on Serial0/0
rely 0/0
*Sep 24 04:19:55.264: EIGRP: Received HELLO on Serial0/0 nbr 172.16.1.1

BR1# no debug all
All possible debugging has been turned off
Todynamicallylearnaboutotherdevicesonthedirectlyattachednetworksandthus
establishandmaintainEIGRPneighborrelationships,EIGRPusessmallhellopackets.
Thesearesentperiodicallyapproximatelyevery5secondsonallkindofinterfaces
exceptlowspeed(T1orslower)NBMAnetworks,wheretheyaresentbydefaultevery
60seconds.Thetimeintervaliscalledahellotimer.
HellopacketsareusedbyEIGRPtodeterminewhethertheneighborisaliveandfunc
tioning.Thesepacketsalsocontaintheholdtimeparameter,whichisusedbyEIGRP
enabledrouterstodeterminethelengthoftimeafterwhichtheneighborrelationship
becomesdeclareddeadiftheneighborstopssendinghellopackets.Shouldthishappen,
EIGRPwillstartlookingforalterativeroutingpaths.Holdtimedefaultstothreetimes
thehellointerval(15or180seconds,dependingontheunderlyingnetwork).
Example213showstheverificationofhelloandholdtimersonHQusingtheshowip
eigrpinterfacesdetailcommand.

Example 2-13 Verifying Hello and Hold Timers on HQ
HQ# show ip eigrp interfaces detail


Et0/0 1 0/0 0/0 5 0/2 50 0
Se1/0 1 0/0 0/0 13 0/15 71 0
Se2/0 1 0/0 0/0 1008 10/400 4432 0
<Output omitted>
Hellointervaldefaultsto5secondsonallinterfacesexceptonthelowspeedNBMA
links.BecauseSerial2/0usesFrameRelaywithadefaultspeedof1544Kbps,whichis
notgreaterthanT1speed,thehellotimerdefaultsto60seconds.OnNBMAlinksthat
arefasterthanT1,thehellotimerdefaultsto5seconds.
Notethattheloopbackinterfaceisnotincludedintheoutput,becauseitisstillconfig
uredasapassiveinterface.
Helloand holdtimerscanbeobservedusingthedebugeigrppacketshellocommandon
BR1,asshowninExample214.AfterdebuggingisenabledonBR1,theSerial1/0inter
faceonHQisdisabled,andresultsofthedebugareshownonBR1.

WhentheSerial1/0interfaceisshutdownonHQ,itwillstopsendingEIGRPhello
packetstoBR1andimmediatelydeclaretheEIGRPneighborrelationshipdowndueto
factthattheinterfaceisdown.However,BR1willstillbelievethattheEIGRPneighbor
relationshipisupuntiltheholddowntimeronBR1expires.After15secondswithout
receivinghellopackets,BR1willterminatetheEIGRPneighborrelationship.
Example 2-14 Observing EIGRP Hello Packets When an Interface Is Disabled
BR1# debug eigrp packets hello

(HELLO)
--------------------------------------------------------------------------------
HQ(config)# interface Serial 2/0
HQ(config-if)# shutdown
HQ(config-if)#
*Apr 9 12:09:53.485: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.3.2
(Serial2/0) is down: interface down
HQ(config-if)#
*Apr 9 12:09:55.483: %LINK-5-CHANGED: Interface Serial2/0, changed state to admin-
istratively down
*Apr 9 12:09:56.483: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0,
changed state to down
BR1#
*Oct 10 13:47:03.981: EIGRP: Received HELLO on Serial0/0 nbr 172.16.1.1
*Oct 10 13:47:03.981: AS 100, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/
*Oct 10 13:47:08.953: EIGRP: Sending HELLO on Serial0/0
rely 0/0
rely 0/0
rely 0/0
*Oct 10 13:47:18.982: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.1
(Serial0/0) is down: holding time expired
BR1# no debug all
BesuretodisabledebuggingonBR1usingthenodebugallcommandafter theneighbor
relationshipgoesdown.
NotethatEIGRPwoulddetectneighborfailurequickeriftheLayer2statusofthe
WANlinkimmediatelyreflectedthefailureofendtoendconnectivity.
Manipulating EIGRP Timers

EIGRPdeterminesdefaulttimervaluesbasedonlinktype.Ifdefaultvaluesarenotsuitable
foraspecificnetworktopology,youcanmanipulatevaluesofhelloandholdtimers.
Themainreasonforconsideringthechangingofhelloandholdtimersistoimprove
convergencetime.ThismayappearparticularlyattractiveonthelowspeedNBMAlinks
wheredefaulthelloandholdtimersdefaulttoarelativelylong60and180seconds,
respectively.However,youneedtoconsiderafewcaveatsbeforeyoudecidetochange
defaulttimervalues.
IncomparisonwithotherIGPs,suchasOSPF,EIGRPhelloandholdtimersbetween
neighborsdonotneedtobeidenticaltosuccessfullyestablishEIGRPneighborrelation
ship;however,asymmetricaltimersmayleadtoflappingEIGRPneighborrelationships
andnetworkinstability.
Forexample,ifonesideofthelinkhashellointervalsetto5secondswithdefaulthold
timesetto15secondsandtheothersidehashellointervalsetto30seconds,therouters
willestablishneighborrelationshipfor15seconds,andthenitwillbedown forthenext
15seconds.
Ifyouincreasethehellointervalonthelink,itmayleadtoasituationwherethenet
workneedsmoretimetodetectpotentialfailurewithlongerconvergencetime.Incon
trast,decreasingthehellotimertoextremelysmallvaluesmayleadtohigh utilizationof
thelinkwithroutingtraffic.
TochangetheEIGRPtimers,youcanusetheinterfaceconfigurationcommandsip
hellointerval eigrp as-number hello-time-interval and ip holdtime eigrp as-number
hold-time-interval.Theautonomoussystemnumberusedinthesecommandsmust
matchtheautonomoussystemnumberoftheEIGRPprocess.Thevalueoftheintervalis
specifiedinseconds.Example215showsanexampleofmodifyingthesetimersonBR3.
Example 2-15 Modifying and Verifying EIGRP Hello and Hold Time Timers on BR3
BR3(config)# interface serial 0/0

BR3(config-if)# ip hello-interval eigrp 100 10
BR3(config-if)# ip hold-time eigrp 100 30
BR3# show ip eigrp interface detail serial 0/0

Se0/0 1 0/0 0/0 1268 0/16 6340 0

<Output omitted>
EIGRP Neighbor Relationship over Frame Relay

FrameRelaysupportstwodifferentinterfacetypes:
Multipointlogicalinterfacesemulatingamultiaccessnetwork
Pointtopointphysicalinterfacesorlogicalpointtopointsubinterfaces
WhenconfiguringEIGRPoverpointtomultipointsubinterfaces,asingleIPsubnetis
used.ToemulatebroadcastmultiaccessnetworkandenableEIGRPtosendmulticast
packetsoverFrameRelayvirtualcircuits(VCs),youmustaddthebroadcastkeywordin
theFrameRelaystaticmappingstatementusingtheframerelaymapipip-address dlci
broadcastinterfaceconfigurationcommand.
FrameRelaymultipointsubinterfacesareapplicabletopartialmeshandfullmesh
topologies.PartialmeshFrameRelaynetworksmustdealwiththepossibilityofthesplit
horizon,whichpreventsroutingupdatesfrombeingretransmittedonthesameinterface
onwhichtheywerereceived.
WhenconfiguringEIGRPoverpointtopointsubinterfaces,adifferentIPsubnetisused
foreachsubinterface.Severalpointtopointsubinterfacescanbecreatedoverasingle
FrameRelayphysicalinterface.Thesearelogicalinterfacesthatareemulatingaleased
linenetworkandarearoutingequivalenttopointtopointphysicalinterfaces.Because
thereisasingledatalinkconnectionidentifier(DLCI)attachedtothepointtopoint
subinterface,thereisnoneedforstaticmappingshere.Multicasttrafficwillbetransmit
tedwithoutneedforanyadditionalconfiguration.Inaddition,EIGRPconsiderspoint
topointsubinterfacesfromthetopologyperspectiveasseparatephysicalinterfaces,and
thereisnopossibilityofthesplithorizonissues.FrameRelaypointtopointsubinter
facesareapplicabletohubandspoketopologies.
Note FormoreinformationaboutconfiguringFrameRelay,seeConnecting Networks

(CiscoPress,2014).

Establishing EIGRP over Layer 3 MPLS VPN

WhenyouconnectbranchofficesoverLayer3MultiprotocolLabelSwitching(MPLS)
virtualprivatenetwork(VPN),youcanestablishEIGRProutingprotocoldirectlywith
theserviceprovider.
ShowninFigure24,Layer3MPLSVPNprovidestheInternetserviceproviders(ISPs)
withapeertopeerVPNarchitecturethefollowingcharacteristics:
Provideredge(PE)routersparticipateincustomerrouting,guaranteeingoptimum
routingbetweencustomersites.
PErouterscarryaseparatesetofroutesforeachcustomer,resultinginperfectiso
lationbetweenthecustomers.
Layer 3 MPLS VPN Backbone
PE PE
CE CE CE CE

Figure 2-4 Layer 3 MPLS VPN
TheLayer3MPLSVPNterminologydividestheoverallnetworkintothecustomer
controlledpart(customernetwork,orCnetwork)andtheprovidercontrolledpart(pro
vidernetwork,orPnetwork).ContiguousportionsoftheCnetworkarecalled sitesand
arelinkedwiththePnetworkviacustomeredge(CE)routers.TheCEroutersarecon
nectedtothePErouters,whichserveastheedgedevicesoftheprovidernetwork.The
coredevicesintheprovidernetwork(providerrouters,orProuters)providethetransit
transportacrosstheproviderbackboneanddonotcarrycustomerroutes.
TheLayer3MPLSVPNbackboneprovidesaLayer3backboneinwhichtheCErouters
seePEroutersasadditionalcustomerroutersinthepath.ThePEroutersmaintainsepa
rateroutingtablesforeachcustomer,tokeepcustomerinformationisolated.
TheLayer3MPLSVPNbackbonelookslikeastandardcorporatebackbonetotheCE
routers.TheCEroutersrunstandardIProutingsoftwareandexchangeroutingupdates
withthePEroutersthatappeartothemasnormalroutersinthecustomernetwork.
ThebackboneroutersinSPnetworkarehiddenfromtheviewofthecustomer,andCE
routersareunawareoftheLayer3MPLSVPN.Therefore,theinternaltopologyofthe
MPLSbackboneistransparenttothecustomer.
Establishing EIGRP over Layer 2 MPLS VPN

Ingeneral,therearethreedifferenttypesofLayer2MPLSVPNsolutionfromthecus
tomerperspective:
Customerroutersarelocatedwithinsinglemetropolitanareaandtheymaybecon
nectedoverthelocalLayer2MPLSVPNswitchnetwork.Customertrafficnever
passesthroughtheSPbackbone.
Customerroutersarelocatedbetweenseveralgeographicallydistantareasthatneed
tobeconnectedoverL2MPLSVPNwithpointtopointlinksthroughtheSPback
bone.
Customerroutersarelocatedbetweenseveralgeographicallydistantareasthatneed
tobeconnectedoverL2MPLSVPNwithmultipointlinksthrough theSPcore.
FromthecustomerperspectiveSPnetworklookslikeaLANswitch.
ApointtopointMPLSL2VPNsolutioniswhereanMPLSbackboneprovidesaLayer
2Ethernetpointtopointconnectionbetweenthecustomerrouters.Whenestablishing
EIGRPneighborrelationshipsoverpointtopointWANEthernetlinks,everypoint
topointconnectionwillbeinitsownIPsubnet.Thissolutionisnotveryscalableas
thenumberofyourbranchofficesrisesandyouwanttoensuredirectcommunication
betweenbranches.
InthecaseofthemultipointMPLSL2VPNsolution,allroutersbelongtothesame
sharedL2broadcastdomain.Figure25showsalogicalnetworkscheme.
HQ Branch1
Branch2 Branch3

Figure 2-5 Layer 2 MPLS VPN
WhenyouestablishEIGRPneighborrelationshipsonthesharedsegment,everyrouter
onthesegmentwillbeneighborwithallotherrouters.Inthistopology,youwilltypical
lywanttoconfigureEIGRPauthenticationbetweenneighborstopreventunauthorized
personstoaddrouterstoyourWANnetwork.
Building the EIGRP Topology Table

OnceEIGRPneighborrelationshipsareestablished,theexchangeofroutinginformation
begins.EIGRPusesupdatepacketstoexchangethisinformation.Alltheroutinginfor
mationreceivedfromneighborsisstoredinanEIGRPtopologytable.
EIGRPusesDUALtocalculatebestroutestoremotenetworks.Foraroutetobe
insertedintotheroutingtable,itmustsatisfythefeasibilitycondition,whichisusedto
preventloopsintheEIGRPnetworks.Theroutewiththelowestmetrictothedestina
tionbecomesacandidatetobeinsertedintotheroutingtable.Ifany routes remain,they
mustsatisfythefeasibilityconditiontobecomeabackuproutetothedestinationnet
work,shouldtheprimaryroutebecomeunavailable.
Tocalculatethecostforeachdestinationnetwork,EIGRPusesasophisticatedmetric,
whichisbydefaultcomposedofbandwidthanddelay.
Uponcompletingthislesson,youwillbeabletodothefollowing:
DescribehowEIGRPneighborsexchangeroutinginformation
DescribehowEIGRPchoosesthebestpaththroughthenetwork
Building the EIGRP Topology Table 77
DescribehowEIGRPmetricgetscalculated
CalculateEIGRPmetric
DescribehowthefeasibilityconditionpreventsloopsinEIGRPnetworks
UnderstandEIGRPpathselectionprocess
Building and Examining the EIGRP Topology Table

ThissectionexaminesdifferentEIGRPpackettypes,explorestheEIGRPtopologytable,
andexamineshowEIGRPelectsthebestpathtothedestination.
ThissectionbeginswithadiscussionofEIGRPpackettypeasweconfigureEIGRPin
thetopologyshowninFigure26.
BeforeconfiguringEIGRPontheBRrouter,EIGRPdebuggingisenabledusingthe
debugeigrppacketscommandshowninExample216.
209.165.201.0/27
External
Network WAN Link
#1

172.16.1.0/30
Lo1
Eth0/1 WAN Link Eth0/1 Lo0
HQ #2 BR
Lo0 192.168.0.0/24
172.16.2.0/30
192.168.0.0/24
WAN Link
#3
172.16.3.0/30
Figure 2-6 EIGRP Topology
Example 2-16 Observing EIGRP on BR

BR# debug eigrp packet
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY,
SIAREPLY)
Next,inExample217,EIGRPisenabledonBRwithanautonomoussystemof100but
onlyonLoopback0andEthernet0/0interfaces.Afterobservingthehellopacketinthe
debugprocess,debuggingisdisabled.
Example 2-17 Observing EIGRP Hello Packets on BR
BR(config)# router eigrp 100

BR(config-router)# network 192.168.1.0 0.0.0.255
*Oct 8 15:20:19.227: EIGRP: Sending HELLO on Ethernet0/0
rely 0/0
*Oct 8 15:20:19.235: EIGRP: Received HELLO on Ethernet0/0 nbr 172.16.1.1
*Oct 8 15:20:19.235: AS 100, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0
*Oct 8 15:20:19.261: EIGRP: Enqueueing UPDATE on Ethernet0/0 tid 0 iidbQ un/rely

0/1 serno 1-2
*Oct 8 15:20:19.266: EIGRP: Sending UPDATE on Ethernet0/0 tid 0
rely 0/0 serno 1-2
*Oct 8 15:20:19.274: EIGRP: Received ACK on Ethernet0/0 nbr 172.16.1.1
<Output omitted>
*Oct 8 15:20:19.253: EIGRP: Received UPDATE on Ethernet0/0 nbr 172.16.1.1
*Oct 8 15:20:19.360: EIGRP: Enqueueing ACK on Ethernet0/0 nbr 172.16.1.1 tid 0
*Oct 8 15:20:19.360: Ack seq 2 iidbQ un/rely 0/0 peerQ un/rely 1/0
*Oct 8 15:20:19.364: EIGRP: Sending ACK on Ethernet0/0 nbr 172.16.1.1 tid 0
Branch# no debug all
ImmediatelyaftertheEIGRPprocessisenabledontheWANlink172.16.1.0/30,EIGRP
beginssendingandreceivinghellopackets.Theprocessofsendingandreceivinghello
packetsisunidirectional,meaningthattheroutersendsthehellopacketsunreliablyusing
multicastand expectsnoacknowledgmentfromtheotherside.WhentheBRrouter
receivesahellopacketfromtheHQneighbor,itdynamicallyformsanewEIGRPadja
cency.Hellopacketsaresentoutperiodicallytochecktheneighboravailability.
Incontrasttotheprocessofsendingandreceivinghellopackets,routingupdatesare
sentandreceivedbidirectionally.Updatepacketscontainroutinginformationandare
alwayssentreliably,meaningthatanacknowledgmentpacketisexpectedforeverysent
updatepacket.Viceversa,everyupdatepacketreceivedmustbeacknowledged.The
processoftransmittingreliablepacketsiscomposedoftwosteps:enqueuingandbun
dlingroutingupdatesontheinterfaceandsendingthereliablepackettotheneighbor.
Outputofthedebugcommandshowsthetwoseparateprocessesofsendingand receiv
ingupdate andacknowledgepacketpairs.
ThenumbersaftertheSeq...partofthedebugoutputrepresentsequenceand
acknowledgmentnumbers.Lookingatthedebugoutputcarefully,noticethateach
packetthatissentoutreliablyhasasequencenumber.Acknowledgmentthatconfirmsa
successfulreceiptofthepacketmustcarrythesamenumberasthereceivedpacket.
Next,usingtheshowipeigrptrafficcommand,EIGRPpackettrafficstatisticsareveri
fied,asshowninExample218.
Example 2-18 Verifying EIGRP Packet Traffic on BR
BR# show ip eigrp traffic

EIGRP-IPv4 Traffic Statistics for AS(100)
Hellos sent/received: 65/67

Updates sent/received: 9/7
Queries sent/received: 0/0
Replies sent/received: 0/0
Acks sent/received: 5/5

SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 101
PDM Process ID: 63
Socket Queue: 0/10000/2/0 (current/max/highest/drops)
Input Queue: 0/2000/2/0 (current/max/highest/drops)
TheshowipeigrptrafficcommanddisplaysinformationaboutwhichtypeofEIGRP
packetswere sentandreceived.Thiscommandmayproveextremelyusefulwhentrou
bleshooting,especiallyincombinationwithotherEIGRPshowanddebugcommands.
Thecommandoutputdisplaysstatisticsforhellos,updatesandacknowledgmentpack
ets,aswellasforqueriesandreplies.
Querypacketsaresentoutwhenarouterperformsaroutecomputationanddoesnot
haveanalternativepathtothedestinationnetwork.Thepacketissentreliablyasmulti
cast tothe neighborstodeterminewhethertheyhaveanalternativepathforthedestina
tion.
Replypacketsaresentinresponsetoaquerypacket.Theyaresentreliablyasunicasts.
EIGRProutesontheBRrouterareverifiedusingtheshowiprouteeigrpcommand,as
demonstratedinExample219.
Example 2-19 Verifying the EIGRP Routes on BR
BR# show ip route eigrp

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route

o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
D 192.168.0.0/24 [90/409600] via 172.16.1.1 , 18:20:16, Ethernet0/0

D EX 209.165.201.0/27 [170/537600] via 172.16.1.1 , 18:20:16, Ethernet0/0
OutputoftheshowiprouteeigrpcommandshowstheEIGRProutespresentinthe
routingtable.Intheoutput,youcanseetwoEIGRProutes,onemarkedwiththecodeD
andtheotherwiththecodeDEX.CodeDrepresentsEIGRPinternalroutes.
AninternalrouteoriginatedwithinanEIGRPautonomoussystem,meaningthatadirect
lyattachednetworkthatisconfiguredinEIGRPisconsideredinternalandispropagated
throughtheEIGRPautonomoussystem.Externalroutes,however,werelearnedby
anotherroutingprotocolandredistributedtoEIGRP.Theyarerepresentedwithcode
DEX.
The numbersinsquarebracketsrepresentADandtheEIGRPmetric,respectively.IPv4
addressesafterviarepresentthenexthopIPv4addresses(inthiscase,172.16.1.1),and
attheendyoucanseetheexitinterfaceforthatroute.
TocompletetheconfigurationonBR,thetworemaininginterfacesEthernet0/1and0/2
areconfiguredtobeapartoftheEIGRPprocess,asshowninExample220.
Example 2-20 Configuring networkCommands on BR
BR(config)# router eigrp 100

The configurationandverificationofEIGRPinthistopologywillbecontinuedinthe
nextsection.
Choosing the Best Path

EIGRPuses DUALtocalculatethebestpathtoadestinationnetwork.Itusesthedistance
information,alsoknownasacompositemetricstoselectefficient,loopfreepaths.
DUALcalculatesthiscompositemetricbyaddingtwovalues.Thefirstvalueisthe met
ricfromneighboringroutertothedestinationnetwork.Thisvalueisreportedtothe
routerandiscalledthereporteddistance(RD).Inmanybooks,youwillalsofindthe
termadvertised distance.Thesecondvalueisthemetricfromthelocalroutertothe
routerthatreportedthefirstvalue.Amongallmetricsfromthelocalrouter tothedes
tinationnetwork,therouterwillchoosetheonewiththesmallestcompositemetricand
consideritthebestpathtothegivendestination.Theselectedvalueiscalledfeasible
distance(FD).

Theroutewiththesmallestmetriciscalledthesuccessorrouteandthenexthoprouter
iscalledthesuccessor.Multiplesuccessorsmayexistiftheyhavethe sameFDtothe
destinationnetwork.Inthiscase,EIGRPtriestoinsertallthesuccessorroutesintothe
routingtable.Uptofoursuccessorroutesmaybeaddedtotheroutingtablebydefault.
Afeasible successorisanexthoprouterwithaloopfreepaththathasalargercostto
thedestinationthanthesuccessor.Whenmorethanonerouteexistsforthegivenprefix
inthetopologytable,therouterverifieswhethertherouteisapartofaloopfreetopol
ogy.Todothis,therouterusesasimplerulethatrequiresthattheRDofanalternative
backuprouteisalwayssmallerthantheFDofthebestpath.Thisiscalledthefeasibility
condition.Routesthatsatisfythisconditionareconsideredasbackuproutesandare
calledfeasiblesuccessorroutes.Nexthoproutersarecalledfeasiblesuccessors.
Continuingwiththeconfigurationfromtheprevioussection,thecontentofBRs EIGRP
topologytableusingtheshowipeigrptopologycommandisdisplayedinExample2
21.ObservetheinformationaboutHQLAN192.168.0.0/24.

Example 2-21 Verifying the EIGRP Topology Table on BR
BR# show ip eigrp topology

EIGRP-IPv4 Topology Table for AS(100)/ID(192.168.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 172.16.2.0/30, 1 successors, FD is 1536000

via Connected, Ethernet0/1
via 172.16.1.1 (409600/128256), Ethernet0/0
via 172.16.2.1 (1664000/128256), Ethernet0/1
via Connected, Loopback0
via Connected, Serial2/0
via 172.16.1.1 (537600/426496), Ethernet0/0
via 172.16.2.1 (1792000/426496), Ethernet0/1
EIGRPtopologytableisadatastructurethatcontainsalltheprefixeslearnedfromall
EIGRPneighbors.CodePinfrontoftheprefixmeansthattheprefixisinpassivestate.
ArouteisconsideredpassivewhenDUALisnotexecutinganycomputationtodis
coverthepossiblealternativepaths.Passivestateisthenormalanddesirablestateforall
routes.Whenallroutesareinapassivestate,thenetworkisfullyconverged.
Theroutewillstayinthepassivestateaslongasthereisatleastonevalidpathtothedes
tinationthatsatisfiesFC.ThefeasibilityconditionisafundamentalwayofhowEIGRP

internallyresolvestheproblemofroutingloops.To fully understandFC you must first

understand two other important concepts: reported distance and feasible distance.
The distance or composite metric in EIGRP is an integer number used to compare dif-
ferent paths toward the same destination network.Eachreceivedrouteincludesreport
eddistanceandisstoredintheEIGRPtopologytable.Youcanfinditintheoutputin
theparenthesesasthesecondnumber.Forpathtothenetwork192.168.0.0/24,ithas a
valueof128256forbothpathoptions.
Thetotalcosttothedestinationisthefirstnumberintheparenthesesandreflects
thereporteddistanceplusthecosttogettotheneighbor.Totalcostforthenetwork
192.168.0.0/24is409600viainterfaceEthernet0/0and1664000viainterfaceEthernet0/1.
The bestpathtothedestinationisbasedonthelowesttotalcosttothedestination.The
bestpathisselectedasthesuccessorroute,andthevalueoftotalcostforthesuccessor
path isselectedasFD.
The remainingpathsbecomecandidatesforfeasiblesuccessorroutes.Forapathto
becomeafeasiblesuccessor,itmustsatisfythefeasibilitycondition.Pathsreporteddis
tancemustbelowerthatthevalueoffeasibledistance.
Note ForathoroughreviewofDUAL,seeRouting Protocols Companion Guide (Cisco

Press,2014).

Continuingwithpreviousscenario,Example222showstheEIGRProutesintherouting
tableofBRusingtheshowiprouteeigrpcommand.
Example 2-22 Verifying the EIGRP Routes on BR

D 192.168.0.0/24 [90/409600] via 172.16.1.1, 02:32:24, Ethernet0/0

D EX 209.165.201.0/27 [170/537600] via 172.16.1.1, 02:32:24, Ethernet0/0
Examiningalltheroutespresentinthetopologytable,EIGRPwilltrytoinsertonlythe
successorroutesintotheroutingtable.Iftherouterlearnsthesamedestinationnetworks
fromothermoretrustedroutingsources,EIGRPsuccessorrouteswillnotbeinserted
intotheroutingtable.Feasiblesuccessorroutesstayinthetopologytableincasethe
successorroutefails.
All thereceivedroutesintheBRtopologytablearedisplayedusingtheshowipeigrp
topologyalllinkscommand,showninExample223.
Example 2-23 Verifying All Networks in the EIGRP Topology Table on BR
BR# show ip eigrp topology all-links

P 172.16.2.0/30, 1 successors, FD is 1536000, serno 4

via 172.16.3.1 (3449856/1536000), Serial2/0
via 172.16.1.1 (1561600/1536000), Ethernet0/0
via 172.16.1.1 (409600/128256), Ethernet0/0
via 172.16.3.1 (256512000/256000000), Serial2/0
via 172.16.2.1 (1664000/128256), Ethernet0/1
via 172.16.1.1 (2195456/2169856), Ethernet0/0
via 172.16.2.1 (3449856/2169856), Ethernet0/1
via 172.16.3.1 (2195456/281600), Serial2/0
via 172.16.2.1 (1561600/281600), Ethernet0/1
via 172.16.1.1 (537600/426496), Ethernet0/0
via 172.16.3.1 (256512000/256000000), Serial2/0
via 172.16.2.1 (1792000/426496), Ethernet0/1
The showipeigrptopologyalllinkscommanddisplaysallpossiblepathstothedestina
tion.Inadditiontothesuccessorandfeasiblesuccessorroutes,thetopologytablemay
alsocontainnonsuccessorroutes.Anonsuccessorrouteisaroutethatdoesnotsatisfy
thefeasibilitycondition.Theoutputshowstheroutetothenetwork192.168.0.0/24
nowwiththreepossiblepaths.Pathvianexthop172.16.3.1hasareporteddistanceof
256000000,whichisgreaterthanthefeasibledistancefortheroute409600.Becausethe
feasibility conditionisnotsatisfied,thepathvia172.16.3.1willnotbeacandidatefor
thesuccessorrole.WhentherouterstayswithoutroutesthatsatisfytheFC,andanew
path calculationfortheprefixmustbeperformed;theroutewilltransitintotheactive
state,andtherouterwillstartqueryingneighborsforalternativeroutes.
Next,Example224showsacontinuouspingfromtheBRroutertotheIPaddress
192.168.0.1 on HQ.
Example 2-24 Continuous Ping from BR to 192.168.0.1

BR# ping 192.168.0.1 repeat 100000 size 1000
Type escape sequence to abort.
Sending 100000, 1000-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
Becausethereisonlyonesuccessorrouteintheroutingtableandtworoutesthatsatisfy
feasibility conditioninthetopologytable,InternetControlMessageProtocol(ICMP)
trafficwillusethepathoverthe172.16.1.0/24link.
InExample225,HQsEthernet0/0interfaceisdisabled,andtheongoingpingprocess
behavioronBRisobserved.
Example 2-25 HQ Ethernet 0/0 Interface Shutdown and Results Observed on BR
HQ(config)# interface Ethernet 0/0

(Ethernet0/0) is down: interface down
*Oct 10 18:47:11.313: %LINK-5-CHANGED: Interface Ethernet0/0, changed state to
administratively down
*Oct 10 18:47:12.313: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
BR#
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!.....
(Ethernet0/0) is down: holding time expired.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
AftertheshutdownoftheEthernet0/0interfaceonHQ,thelineprotocolontheinter
faceinstantlychangesthestatetodown,andEIGRPonHQcancelsitsneighborrela
tionshipoverthisinterface.However,thestatusoftheinterfaceontheHQsideisnot
signalizedtothecorrespondingBRinterface.Therefore,theEIGRPprocessontheBR
routerwillnotimmediatelydeclaretheEIGRPneighborrelationshipoverEthernet0/0
dead.BRrealizesthatthereisnolivepeerontheothersideofthelinkafterthehold
timerexpiresduetonohellopacketsbeingreceived.
Bydefault,ittakes15secondsontheEthernetinterfacesforEIGRPtoconverge.
Duringthistimeframe,ICMPpacketsaredropped.WhenBRrealizesthattheneighbor
isdown,itstartsforwardingICMPpacketsusingthefeasiblesuccessorrouteoverthe
172.16.2.0/30 link.
SituationswhenLayer2statusofthelinkdoesnotreflecttheoperationstatusofthe
neighboringdevicesarecommoninrealworldsituations.Ifyouneedtospeed upthe
convergence,theEIGRPtimercanbeadjusted,orotherstatusdetectionmechanismscan
bedeployed.
Ifthecontinuouspinghasnotyetcompleted,enditbypressingCtrl+Shift+6.
Example226showstheroutingtableonBR.
Example 2-26 EIGRP Routes on BR
D 192.168.0.0/24 [90/1664000] via 172.16.2.1, 00:33:49, Ethernet0/1

D EX 209.165.201.0/27 [170/1792000] via 172.16.2.1, 00:33:49, Ethernet0/1

Theformerfeasiblesuccessorroutethatpointsoverthe172.16.2.0/30linkhasnow
becomethesuccessorrouteandisinstalledintheroutingtable.
ThetopologytableontheBRisverifiedusingtheshowipeigrptopologycommandin
Example227.
Example 2-27 EIGRP Topology Table on BR with New Successor
BR# show ip eigrp topology



via 172.16.2.1 (1664000/128256), Ethernet0/1
via 172.16.2.1 (1792000/426496), Ethernet0/1
Afterthefailureofthesuccessorroute,onlytherouteovertheEthernet0/1interface
satisfiesthefeasibilitycondition.Thisformerfeasiblesuccessorroutehasnowbecome a
successorandispresentinboththetopologyandtheroutingtable.Thethirdrouteover
172.16.3.0/24doesnotsatisfythefeasibilityconditionandisnotdisplayedintheout
putoftheshowipeigrptopologycommand.
InExample228,acontinuouspingisdoneonBRtowardHQandduringtheping,HQs
Ethernet0/1interfaceisdisabled.
Example 2-28 Continuous Ping on BR with HQ Interface Disabled
BR# ping 192.168.0.1 repeat 100000 size 1000

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<Output omitted>
-------------------------------------------------------------------
HQ(config)# interface ethernet 0/1
(Ethernet0/1) is down: interface down
*Oct 10 20:42:47.543: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to
*Oct 10 20:42:48.543: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1,
-------------------------------------------------------------------
BR#
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!......!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!
(Ethernet0/1) is down: holding time expired
!!!!!!!!!!!
<Output omitted>
AftertheshutdownoftheEthernet0/1interfaceontheHQrouter,theEIGRPneigh
borrelationshipusingthecurrentsuccessorrouteiscanceled.Thelastremainingroute
thatsatisfiesthefeasibleconditionisfromthetopologyandroutingtable.TheDUAL
calculationstarts,anddestination192.168.0.0/24goesintotheactivestate.TheBR
routersendsaspecialpacketcalledaquery,whichisusedtoaskneighboringroutersif
theyhaveanyalternativepathsforthelostprefix.ThepacketreachesrouterHQover
theonlyremainingactivepath,172.16.3.0/30.HQrespondstothequerywiththereply
packet,whichconfirmsthatithasnoalternativepathtoreachthelostnetwork.When
BRreceivesthereplypacket,theprocessofthenewpathcalculationends.
DuringtheDUALcalculation,192.168.0.0/24willbeintheactivestate.Droppedpack
etsduringtheconvergencephaseresultbecausetheholdtimerontheBRmustexpire
fortheEIGRPneighboroverthe172.16.2.0/30linkandthentheDUALcalculationmust
be executed.
ICMPpacketsaredroppedbeforeBRdetectstheunreachableneighboroverthesucces
sor pathandwhileEIGRPdeterminesanewvalidpathtowardthedestinationnetwork.
Althoughtheselectedrouteinthetopologytableinpreviousexamplesdidnotsatisfy
thefeasibilitycondition,intheabsenceoftheothertworoutesfromthetopologytable,
thisrouteisnowtheonlyrouteavailable.Itischosenasthesuccessorandinstalledin
theroutingtable.
Ifacontinuouspinghasnotcompleted,youcancancelitbypressingCtrl+Shift+6.
Example229showstheexaminationofthecontentoftheroutingtableonBRusingthe
showiprouteeigrpcommand.
Example 2-29 BR Routing Table with New Successor

D 192.168.0.0/24 [90/256512000] via 172.16.3.1 , 00:32:19, Serial2/0

D EX 209.165.201.0/27 [170/256512000] via 172.16.3.1 , 00:32:19, Serial2/0

TheonlyremainingavailablepathtowardbetweenHQandBRisnowactiveandpresent
inbothtopologyandroutingtables.
Exchange of Routing Knowledge in EIGRP

Beforeroutersexchangetheirroutinginformation,theymustestablishtheEIGRPneigh
borrelationship.Sessionestablishmentisfollowedbyanimmediateexchangeofupdate
packets,whichadvertisetheroutinginformationfromtheEIGRPtopologytable.Keep
inmindthatonlythebestroutesareadvertisedtotheneighbors.So,onlytheroutesthat
areusedby EIGRP,thesuccessorroutes,getadvertised.
Inadditiontothereceivedroutinginformation,thetopologytablehastwootherlocal
sources:
SubnetsofdirectlyconnectedinterfacesonwhichEIGRPhasbeenenabledusing
thenetworkcommand
SubnetslearnedbyredistributionofroutesintoEIGRPfromotherroutingproto
colsorroutinginformationsources
Redistributionisamethodoftakingroutinginformationfromonesourceandadvertising
itintoanotherroutingprotocol.Redistributionisusedinsituationswhenmultiplerouting
protocolsareusedinthesameautonomoussystem.Anothercommoncaseiswhenyou
wanttoincludealreadydefinedstaticroutesintotheselectedroutingprotocol.
EIGRP Metric
EIGRPusesacompositemetrictodeterminethebestpathtothedestination.Themet
ricsvaluederivesfromaformulathatcanusethefollowingparameters:
Bandwidth:Leastvalueofthebandwidthforalllinksbetweenthelocalrouterand
thedestination.
Delay: Cumulativedelayobtainedassumofvaluesofalldelaysforalllinks
betweenthesourceanddestination.
Reliability:Thisvaluerepresentstheworstreliabilitybetweensourceanddestina
tion(basedonkeepalives).
Load:Thisvaluerepresentstheworstloadonthelinkbetweenthesourceandthe
destination(basedonthepacketrateandtheconfiguredbandwidthoftheinterface).
Youmightfinditinmanybooksoronlinearticlesthatmaximumtransmissionunit
(MTU)isalsousedinEIGRPmetriccalculations.AlthoughitistruethatMTUvalueis
exchangedintheroutingupdatestogetherwithothermetriccomponents,itisnever
usedforthemetriccalculation.Itisonlyusedasatiebreaker,whentherouterneedsto
ignoresomeequalcostpathstothesamedestination,becauseoftoomanyequalcost
paths.Insuchcases,theroutewiththehighestminimumMTUispreferred.
Bydefault,EIGRPusesonlybandwidthanddelaytocalculatethemetric.Optionally,
thecomputationmayincludeinterfaceloadandreliability,althoughCiscodoesnotrec
ommendusingthem.Allroutersinroutingdomainmustusethesamecomponentsfor
metriccalculation,andchangingthemetriccalculationononlyoneroutercanintroduce
connectivityissuesininconsistentenvironments.
Thecomponentsusedforthemetriccalculationaredeterminedbythemetricweights,
orKvalues.DefaultKvaluesare:K1=1,K2=0,K3=1,K4=0,K5=0.IftheKvaluesareset
todefault,themetricisbasedononlybandwidthanddelayvalues.
Use theshowipprotocolscommandtoverifyKvalues.
EIGRP Metric Calculation

Tocalculatecompositemetrictothegivendestination,EIGRPusesthefollowingformula:
Metric=[(K1*Bandwidth+[(K2*Bandwidth)/(256Load)]+K3*Delay)*K5/
(K4+Reliability)]*256
IfK4andK5valuesaresettodefaultvalues,whichare0,thequotientK5/(K4+
Reliability)isnotused;thatis,itissetto1.Theformulathuseffectivelyreducestothe
following:
Metric=(K1*Bandwidth+[(K2*Bandwidth)/(256Load)]+K3*Delay)*256
IfyoutakeintoaccountdefaultK1K3values,K1=K3=1,andK2=0,theformulareduc
esEIGRPmetriccomputationtothefollowing:
Metric=(Bandwidth+Delay)*256
NotethatchangingtheKvaluesisnotrecommended.
TheformatofthedelayandbandwidthvaluesthatareusedforEIGRPmetriccalcula
tionsisdifferentfromthosethataredisplayedbytheshowinterfacecommand.The
EIGRPdelayvalueisthesumofthedelaysinthepath,intensofmicroseconds,whereas
theshowinterfaceoutputdisplaysthedelayinmicroseconds.TheEIGRPbandwidthis
calculatedusingtheminimumbandwidthlinkalongthepath,inkilobitspersecond.The
7
value10 isdividedbythisvalue.Sumofbandwidthanddelayismultipliedby256 to
ensurebackwardcompatibilitywiththeEIGRPpredecessorIGRP.
Note Valuesofdelaydisplayedintheshowinterfaceoutputarenotmeasuredbut
calculated.CiscoIOScalculatesthembasedonthenegotiatedorconfiguredinterface
bandwidth.

Note For athoroughreviewoftheEIGRPmetriccalculation,seeRouting Protocols

Companion Guide (Cisco Press,2014).

EIGRP Wide Metrics

The EIGRPcompositecostmetricdoesnotscalecorrectlyforhighbandwidthinterfaces
orEthernetchannels,resultinginincorrectorinconsistentroutingbehavior.Thelowest
delaythatcanbeconfiguredforaninterfaceis10microseconds.Asaresult,highspeed
interfaces,suchas10GigabitEthernet(GE)interfaces,orhighspeedinterfaceschan
neledtogether (GEetherchannel)willappeartoEIGRPasasingleGEinterface.This
maycauseundesirableequalcostloadbalancing.
Toresolvethisissue,theEIGRPWideMetricsfeaturesupports64bitmetriccalcu
lationsandRoutingInformationBase(RIB)scalingthatprovidestheabilitytosup
portinterfaces(eitherdirectlyorviachannelingtechniqueslikeportchannelsor
EtherChannels)uptoapproximately4.2terabits.
The 64bitmetriccalculationsworkonlyinEIGRPnamedmodeconfigurations.EIGRP
classicmodeuses32bitmetriccalculations.EIGPRnamedmodeconfigurationisdis
cussedlaterinthischapter.
The EIGRPWideMetricisbeyondthescopeofthisbook.Formoreinformation,see
the Cisco.com document EIGRP Wide Metrics,athttp://www.cisco.com/c/en/us/td/
docs/iosxml/ios/iproute_eigrp/configuration/15mt/ire15mtbook/irewidmet.pdf.
EIGRP Metric Calculation Example

InFigure27,R1hastwopathstoreachnetworksbehindR4.Thebandwidths(Mbps)
andthedelays(inmilliseconds)ofthevariouslinksareshowninthefigure.Letsdeter
mineEIGRPmetricforbothpaths.
100 Mbps
Delay 10 ms
R3 10 Mbps
100 Mbps R2
Delay 50 ms
Delay 40 ms
R1 R4
100 Mbps 100 Mbps
Delay 10 ms Delay 10 ms
R5 100 Mbps R7
50 Mbps R6 Delay 10 ms
Delay 30 ms
Figure 2-7 R1 Has Two Paths to Networks Behind R4
The calculationofthetoppathisasfollows:
1. The lowestbandwidthalongthetoppath(R1R2R3R4)is10Mbps(10000
Kbps).TheEIGRPbandwidthcalculationforthispathisasfollows:
7
Bandwidth=(10 /Leastbandwidthinkilobitspersecond)
Bandwidth=(10,000,000/10,000)=1,000

2. Thedelaythroughthetoppathisasfollows:
Delay=[(DelayR1 R2)+(DelayR2 R3)+(DelayR3 R4)]
Delay=[4000+1000+5000]=10000[tensofmicroseconds]
3. Therefore,theEIGRPmetriccalculationforthetoppathisasfollows:
Metric=(1000+11,000)*256=2,816,000
The calculationofthebottompathisasfollows.
1. Thelowestbandwidthalongthelowerpath(R1R5R6R7R4)is50000kbps.
The EIGRPbandwidthcalculationforthispathisasfollows:
7
Bandwidth=(10 /Leastbandwidthinkilobitspersecond)
Bandwidth=(10,000,000/50,000)=200
2. The delaythroughthebottompathisasfollows:
Delay=[(DelayR1 R5)+(DelayR5 R6)+(DelayR6 R7)+
(DelayR7 R4)]
Delay=[1000+3000+1000+2000]=7000[tensofmicroseconds]
3. Therefore,theEIGRPmetriccalculationforthebottompathisasfollows:
Metric=(200+7000)*256=1,843,200
Therefore,R1 choosesthebottompath,withalowermetricof1,843,200, overthetop
path,withahighermetricof2,816,000.R1installsthelowerpath,withR5asthenext
hoprouter,andametricof1,843,200intheIProutingtable.Thebottlenecksalong
thetoppathare10Mbpslinks,andthatexplainswhytheroutertakesthelowerpath.
ThislinkmeansthattherateoftransfertoR4canbeatamaximum10Mbps.Alongthe
lowerpath, thelowestspeedis50Mbps,meaningthatthethroughputratecanbeas
high asthatspeed.Therefore,thelowerpathrepresentsabetterchoiceforexample,
formovinglargefilesatgreaterspeeds.

EIGRP Metric Calculation Example
FeasibilityconditionensuresEIGRPdomainremainsloopfree.Tobeconsideredasa
feasible successorroute,theprefixmustsatisfythefeasibilitycondition,anditsreported
distancemustbelowerthanthefeasibledistanceofthesuccessorroute.Thisisthepri
marywayhowEIGRPensuresloopfreetopologythroughthenetwork.
Toillustratetheimportanceofthefeasibilitycondition,seeFigure28.RouterDadver
tisesitsLAN networktoroutersBandCwiththemetricof5.RoutersBandCaddtheir
respectivemetricsof5and10tocalculatetheirdistancestotherouterDLANnetwork
andthenadvertisethesedistancestorouterA.RouterAaddsalinkmetricof3tothe

advertisement fromBandalinkmetricof2totheadvertisementfromC.Therefore,the
bestpathfromAtoDgoesoverBbecausethemetricoftheABDpathis13andthe
metricoftheACDpathis17.
13 10
3 3 3
A B A B
A B
2 5 13 2 5
2 5 15
2
5 5 5
C 10 D C 10 D
15
C 10 D
Figure 2-8 R1 Has Two Paths to Networks Behind R4
AssumeforamomentthatthesplithorizonhasbeendisabledonrouterConthelink
betweenrouterAandC.WhenrouterAadvertisesabestpathmetricof13 fromrouter
AtoC,router CmayadvertisethesameroutebacktorouterAwithanincreasedmetric
of15.Inthiscase,routerAwillnotknowwhetherrouterChasanalternatepathtothe
LANnetworkofrouterDorwhetheritisadvertisingtherouteforthebestpathjust
backtorouterA.BecauseRDoverrouterCisgreaterthanFDofthebestpath,router
Awillnotrely ontheRDfromrouterC.ThisishowrouterAensuresthattheEIGRP
domainstaysloopfree.
EIGRP Path Calculation Example

Figure29showsanexampleofhowtheRDiscalculated.R1hasseveraloptionsthatare
availabletoreachnetwork10.0.0.0/8.R2,R4,andR8eachsendanupdatetoR1.Each
updatecontainsaRD,whichisthecostdeterminedbytheneighboringroutertoward
theannouncednetwork10.0.0.0/8.
(20) (10)
10.0.0.0/8
R7
R8
(10)
(10) (1) R3
R1 (10) R2
(10)
(100)
R6
R4 R5 (10)
Reported distance = distance to a destination as advertised by an
upstream neighbor
Destination RD Neighbor
10.0.0.0/8 2010=30 R8
10.0.0.0/8 11010=21 R2
10.0.0.0/8 100101010=130 R4
Figure 2-9 Reported Distance Calculations for R1
Figure210showsanexampleofhowtheFDiscalculated.R1hasseveraloptionsthatare
availabletoreachnetwork10.0.0.0/8.Eachupdatefromthethreeneighborshasadiffer
ent RD.ByaddingthecostofthelocallinktoR2,R4,andR8totheRDofeachpath,R1
calculatesthedistancesforeachpathtothenetwork10.0.0.0/8.Thelowestmetric tothe
destinationisoverR2.TheFDforthe10.0.0.0/8networkthereforeequals31.
(10) 10.0.0.0/8
R8 (20)
(10) R7
(10)
R1 (10) R2
(1)
R3 (10)
R4 (100)
(10)
R5 R6
Lowest metric = Feasible distance
Destination RD Metric Neighbor
10.0.0.0/8 30 3010=40 R8
10.0.0.0/8 21 2110=31 (FD) R2
10.0.0.0/8 130 13010=140 R4
Figure 2-10 Feasible Distance Calculations for R1

Figure211showsthesuccessorandfeasiblesuccessoronR1tonetwork10.0.0.0/8.
Threepathsexistfornetwork10.0.0.0/8.Thedistances(metrics)andRDvaluesarecal
culatedforallthreepathsthethreecandidatesfortheroutingtable.Thecandidate
withthelowestdistance(metric)valueoverR2becomesthesuccessorroute.Theroute
withthesecondbestmetric(andiftheRDforthisrouteislowerthantheFDonthe
successorroute)becomesafeasiblesuccessorroute.TherouteviaR8fulfills thiscriteria
and becomesthefeasiblesuccessorroute.TherouteviaR4doesnotsatisfythefeasibil
ityconditionandisthereforeconsideredasanonsuccessorroute.Onlythesuccessor
routeisacandidatetobeplacedintotheroutingtable.
(10) 10.0.0.0/8
R8 (20)
(10) R7
(10)
R1 (10) R2
(1)
R3 (10)
R4 (100)
(10)
R5 R6
Route over R2 becomes successor.
Alternative route over R8 becomes feasible successor.
Destination RD Metric Neighbor Status
10.0.0.0/8 30 40 R8 FS
10.0.0.0/8 21 31 (FD) R2 S
10.0.0.0/8 130 140 R4 Non-S
Figure 2-11 Successor and Feasible Successor for R1
Note ForathoroughreviewoftheEIGRPmetriccalculationandexamples,seethe
Routing Protocols Companion Guide (Cisco Press, 2014).
Optimizing EIGRP Behavior

WhenEIGRPisdeployedinlargernetworks,youneedtooptimizethedefaultEIGRP
behaviortoachievethedesiredscalability.ByimplementingEIGRPstubconfiguration,
youcanlimittheEIGRPqueryrange,makingEIGRPmorescalablewithfewercomplica
tions.Byusingsummarization,youcanreducethesizeoftheroutingtablesandoptimize
theexchangeofroutinginformationbetweentherouters.
Toutilizeavailableredundantlinks,EIGRPbydefaultsupportsloadbalancingacross
multiplelinks.Toimprovenetworkutilization,youcanalsoconfigureEIGRPtoutilize
unequalcost loadbalancing.
UnderstandEIGRPqueries
Describehowstubroutingcanbeusedtoreducetheamountofquerieswhen
EIGRPgoesactive
DescribetheEIGRPstuckinactiveissue
ExplainhowusingsummaryrouteslessentheimpactofqueryscopewhenEIGRP
goesactive
Describe loadbalancingoptionswithEIGRP
Optimizing EIGRP Behavior 95
EIGRP Queries
EIGRPreliesonneighboringrouterstoprovideroutinginformation.Whenarouterloses
arouteanddoesnothaveafeasiblesuccessorinitstopologytable,itlooksforanalter
nativepath tothedestination.Thisisknownasgoing active onaroute.
Whentherouteislost,theroutersendsquerypacketstoallneighborsoninterfaces
otherthantheonethatisusedtoreachtheprevioussuccessor(splithorizonbehavior).
Thesepacketsquerywhethereachoftheneighborshasaroutetothegivendestination.
Ifaneighborrouterhasanalternateroute,itanswersthequeryanddoesnotpropagate
itfurther.Ifaneighbordoesnothaveanalternateroute,itquerieseachofitsownneigh
borsforan alternatepath.Thequeriesthenpropagatethroughthenetwork,creating
anexpandingtreeofqueries.Whenarouteranswersaquery,itstopsthespreadofthe
querythroughthatbranchofthenetwork.
IntheFigure212,youcanseeanetworkexampleinwhichasinglelostroutemight
resultinanenormousnumberofqueriesthataresentthroughouttheEIGRPdomain.
Whentheroutetonetwork192.168.14.0onrouterR1islost,R1sends aquery toall
neighboringroutersandtoallinterfacesexcepttheinterfaceofthesuccessor(splithori
zon).ThequeryispropagatedtoR2.Becauseithasnoinformationaboutthelostroute,
R2cascadesthequerytoitsneighbors,whichcascadeittotheirneighbors,andsoon.
Eachqueryrequiresareplyfromtheneighbor,andtheamountoftrafficincreases.The
networktopologyinthefigureshowsthatthereisnoavailableredundantpathtonet
work192.168.14.0.
Active
R1
Active
192.168.14.0/24 R5
R3
R6
Queries
Replies R2
R7
Active
R4
Active R8
Figure 2-12 EIGRP Queries and Replies

The routein theactivestatecanbeobservedusingtheshowipeigrptopologycom
mandinExample230.TheyaremarkedwiththeletterA,andP indicatesnormalpas
sivestate.
Example 2-30 Observing the Active Route on R1

R1# show ip eigrp topology

via Connected, GigabitEthernet0/1
A 192.168.14.0/24, 0 successors, FD is 409600, Q
1 replies, active 00:00:02, query-origin: Local origin
Remaining replies:
via 172.16.1.1, r, GigabitEthernet0/0
via Connected, GigabitEthernet0/0
The EIGRPquerypropagationprocessisfarfromefficient.Manyqueriesaresent,and
each queryisfollowedbyareply.Twomajorsolutionsexisttooptimize thequeryprop
agationprocessandtolimittheamountofunnecessaryEIGRPload onthelinks.You
caneitheruseroutesummarizationortheEIGRPstubroutingfeaturetooptimizehow
queriesareexchanged.
Note ForathoroughreviewoftheEIGRPDUALandexamples,seetheRouting
Protocols Companion Guide (Cisco Press, 2014).

EIGRP Stub Routers

The stabilityoflargescaleEIGRPnetworksoftendependsonthescopeof queries
throughthenetwork.OnewayyoucanreducethenumberofEIGRPqueriesand
improvenetworkscalingistomarkthespokesofalargenetworkasstubs.
The EIGRPstubroutingfeatureenablesyoutolimitquerymessagescopeinthenet
work.RoutersconfiguredasstubsdonotforwardEIGRPlearnedroutestoother neigh
bors,andmoreimportantly,nonstubroutersdonotsendquerymessagestostubrouters.
ThissavesCPUcyclesandbandwidthandspeedsupconvergence.
Figure213showstheedgeroutersR5throughR8configuredasstubs,soR3andR4
willnotsendqueriesforthenetwork192.168.14.0/24tothem.Thisreducesthetotal
numberofqueriesandbandwidthused.Configuringtheremoteroutersasstubsalso
reducesthecomplexityofthetopologyandsimplifiestheconfiguration,especiallyin
hubandspoketopologies,wherestubroutingisenabledondualhomedremoterouters
orspokes.Thismeansthatyoudonothavetoconfigureroutefilteringonremoterout
ersto preventthemfromappearingastransitpathstohubrouters.
Active
R1
192.168.14.0/24 R5
R3
Configure
Queries R6 as
Replies R2 EIGRP
Active R7 stub
R4
R8
Figure 2-13 EIGRP Stub Routers
Configuring EIGRP Stub Routing

TheEIGRPquerypropagationprocessisnotveryefficient.Manyqueriesaresent,and
eachqueryisfollowedbyareply.TheEIGRPstubconfigurationoptionenablesyouto
marktheroutersasstubsandthusreducethenumberofexchangedEIGRPqueries.This
sectionillustratesthecommandstoconfigureandverifyEIGRPstubs.
UsingthetopologyinFigure214,noticethattherearethreerouters:HQ,BR1A,
andBR1B.AllroutersarealreadypreconfiguredwithEIGRP.BR1BannouncestoHQ
summarynetwork192.168.16.0/23,whichsummarizesprefixes192.168.16.0/24and
192.168.17.0/24. BR1B, in contrast, announces its loopback with prefix 192.168.18.0/24
asanexternalEIGRProute.
BR1B
Lo0
192.168.17.0/24
Lo1 192.168.18.0/24
Eth0/1
192.168.16.0/24
Eth0/1
Eth0/0 Eth0/0
HQ Lo0 WAN Lo0
192.168.0.0/24
networks
HQ BR1A
172.16.0.0/24
10.1.0.0/16
Figure 2-14 EIGRP Topology for Configuring Stub Routers
Example231showstheexaminationoftheroutingtablesonroutersHQandBR1A
withspecificrouteshighlighted,whichwillbediscussed.
Example 2-31 R1 and BR Routing Tables
HQ# show ip route

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 10.1.0.0/16 is directly connected, Loopback0
L 10.1.0.1/32 is directly connected, Loopback0
C 172.16.1.0/30 is directly connected, Ethernet0/0
L 172.16.1.1/32 is directly connected, Ethernet0/0
D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:12:07, Ethernet0/0
D 192.168.16.0/23 [90/307200] via 172.16.1.2, 00:12:07, Ethernet0/0
D EX 192.168.18.0/24 [170/307200] via 172.16.1.2, 00:12:07, Ethernet0/0
BR1A# show ip route

10.0.0.0/16 is subnetted, 1 subnets

D 10.1.0.0 [90/409600] via 172.16.1.1, 00:34:56, Ethernet0/0
D 192.168.16.0/23 is a summary, 03:05:24, Null0

C
192.168.16.0/24 is directly connected, Ethernet0/1
L
192.168.16.1/32 is directly connected, Ethernet0/1
S
192.168.17.0/24 [1/0] via 192.168.16.2
S 192.168.18.0/24 [1/0] via 192.168.16.2
Notice that HQ learns about networks 192.168.0.0/24, 192.168.16.0/23, and

192.168.18.0/24viaEIGRP.ThefirstrouterepresentstheLANonBR1A,thesecondisa
summaryroute,andthelastoneisaredistributedstaticroute.
The showipeigrpneighborsdetailscommandisusedtoverifyHQsneighbors,as
showninExample232.
Example 2-32 Verifying HQs neighbors

HQ# show ip eigrp neighbors detail

(sec) (ms) Cnt Num

0 172.16.1.2 Et0/0 13 02:14:33 12 100 0 20

BFD sessions
NeighAddr Interface
NoticethatBR1AistheonlyneighborvisibletoHQ.AlllearnedEIGRProuteswere
receivedfromit.NotealsothatBR1AandHQareconfiguredinEIGRPautonomous
system1.
Next,inExample233,EIGRPpacketdebuggingisenabledonHQwiththedebugeigrp
packettersecommand,andtheLoopback0interfaceisshutdown.
Example 2-33 Debugging EIGRP Query and Reply Packets on HQ
HQ# debug eigrp packets terse

(UPDATE, REQUEST, QUERY, REPLY, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)
HQ# configure terminal

HQ(config)# interface Loopback 0
*Oct 8 13:11:18.173: EIGRP: Enqueueing QUERY on Ethernet0/0 tid 0 iidbQ un/rely 0/1
serno 21-21
*Oct 8 13:11:18.177: EIGRP: Sending QUERY on Ethernet0/0 tid 0
rely 0/0 serno 21-21
*Oct 8 13:11:18.178: EIGRP: Received ACK on Ethernet0/0 nbr 172.16.1.2

*Oct 8 13:11:18.178: EIGRP: Ethernet0/0 multicast flow blocking cleared
*Oct 8 13:11:18.207: EIGRP: Received REPLY on Ethernet0/0 nbr 172.16.1.2
*Oct 8 13:11:18.207: EIGRP: Enqueueing ACK on Ethernet0/0 nbr 172.16.1.2 tid 0
*Oct 8 13:11:18.207: Ack seq 21 iidbQ un/rely 0/0 peerQ un/rely 1/0
*Oct 8 13:11:18.207: Handling TLV: 242 41 for 0 route: 10.1.0.0/16
*Oct 8 13:11:18.215: EIGRP: Sending ACK on Ethernet0/0 nbr 172.16.1.2 tid 0
HQ(config-if)#
*Oct 8 13:11:20.155: %LINK-5-CHANGED: Interface Loopback0, changed state to
*Oct 8 13:11:21.159: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0,
NoticethatHQsendsaquerymessagetoneighborBR1AovertheEthernet0/0inter
face. EIGRProutersusequerypacketstoaskneighborsaboutthepath totherecently
lostroutes.BR1Afirstconfirmsthereceiptofthequerymessagewithanackmessage,
followedbyareplypacketthatrespondstothereceivedquery.Thereplypacketcon
tainsinformationthatBR1Ahasnoalternativeroutetowardlostnetwork10.1.0.0/16.
HQrespondstoareplypacketbysendingacknowledgment.
WhenrouterHQlosesthepathtothenetwork10.1.0.0/16,EIGRPgoesintotheactive
stateforthelostroute.Theroutingprocessstaysintheactivestateuntilitfindsanalter
nativepathorreceivesresponsestoallsentqueriesfromitsneighbors.
EIGRP Stub Options

SeveraldifferentEIGRPstuboptionsallowyoutopreciselyspecifywhichroutesthe
EIGRPstubshouldadvertise,asshowninTable21.
ToconfigurearouterasastubusingEnhancedInteriorGatewayRoutingProtocol
(EIGRP),usetheeigrpstubcommandinrouterconfigurationmodeoraddressfamily
configurationmode.TodisabletheEIGRPstubroutingfeature,usethenoformofthis
command.
Table 2-1 Parameters for the eigrpstubGlobal Configuration Command

Parameter Description
receiveonly (Optional)Setstherouterasareceiveonlyneighbor
leakmap name (Optional)Allowsdynamicprefixesbasedonaleakmap
connected (Optional)Advertisesconnectedroutes

static (Optional)Advertisesstaticroutes

summary (Optional)Advertisessummaryroutes

redistributed (Optional)Advertisesredistributedroutesfromotherprotocolsand

autonomoussystems

Arouterthatisconfiguredasastubsharesinformationaboutconnectedandsummary
routeswithallneighboringroutersbydefault.Youcancombineallstuboptionsexcept
forreceiveonlytoachievedesiredcombinationofadvertisedroutes.
TheconnectedoptionpermitstheEIGRPstubroutertoadvertiseallconnectedroutes
forinterfacesthatarematchedwithanEIGRPnetworkcommand.Thisoptionisenabled
bydefaultandisthemostwidelypracticalstuboption.
ThesummaryoptionpermitstheEIGRPstubroutertosendsummaryroutes.Youcan
createsummaryroutesmanually,oryoucancreatethemautomaticallyby enablingauto
summaryatamajornetworkboundaryrouter.Thesummaryoptionisenabledbydefault.
The staticoptionpermitstheEIGRPstubroutertoadvertisestaticroutes.Youstillneed
toredistributestaticroutesintoEIGRPusingtheredistributestaticcommand.
TheredistributeoptionpermitstheEIGRPstubroutertoadvertiseall redistributedroutes,
aslong asredistributionisconfiguredonthestubrouterusingtheredistributecommand.
The receiveonlyoptionrestrictsthestubrouterfromsharinganyofitsrouteswith
anyotherrouterwithinanEIGRPautonomoussystem.Thisoption doesnotpermit
anyotheroptiontobespecifiedbecauseitpreventsanytypeofroutefrombeingsent.
Thisoptionisrarelyused.Twoexamplesarewhenarouterhasasingleinterfaceorif
NetworkAddressTranslation(NAT)withPortAddressTranslation (PAT)isconfigured,
soallhostsarehiddenbehindasingleWANinterface.
InExample234,HQsLoopback0interfaceisreenabled.InExample235,BR1Ais
configuredasanEIGRPstubusingtheeigrpstubcommand,andtheoutputonHQindi
catesthattheadjacencyisreestablished.

Example 2-34 Reenabling the HQs Loopback 0 Interface
HQ(config)# interface loopback 0
HQ(config-if)# no shutdown
Example 2-35 BR1A Configured as an EIGRP Stub Router

BR1A(config)# router eigrp 1
BR1A(config-router)# eigrp stub
(Ethernet0/0) is down: peer info changed
BR1A(config-router)#


-----------------------------------------------------------------
(Ethernet0/0) is down: Interface PEER-TERMINATION received
HQ#
*Oct 18 11:51:20.503: EIGRP: Adding stub (1 Peers, 1 Stubs)
*Oct 18 11:51:20.503: EIGRP: Enqueueing UPDATE on Ethernet0/0 nbr 172.16.1.2 tid 0
iidbQ un/rely 0/1 peerQ un/rely 0/0
*Oct 18 11:51:20.508: EIGRP: Received UPDATE on Ethernet0/0 nbr 172.16.1.2
<Output omitted>
WhentheBR1Arouterisconfiguredasastub,theEIGRPadjacency needstoberees
tablished.
EIGRPstubroutersannouncetheirnewstatusinEIGRPhellopackets.Thisinformsneigh
borsthatthe routerontheotherendofthelinkisastubrouterandthattheymuststop
sendingquerypacketstothatrouter.Thisresultsinimprovedconvergencetimebecause
thecentralroutersdonothavetowaitforqueryresponsesfromtheremoteoffices.
Next,wewillverifyhowHQdetectsthatBR1Aisnowconfiguredasastubrouter.All
debuggingis disabledonHQusingtheundebugallcommand,shownin Example236.
Example 2-36 Disabling Debug on HQ

HQ# undebug all
InExample237,EIGRPneighborsonHQareverifiedusingtheshowipeigrpneigh
borsdetailscommand.
Example 2-37 Neighbor BR1A Verified as an EIGRP Stub on HQ

(sec) (ms) Cnt Num
0 172.16.1.2 Et0/0 11 00:39:00 7 100 0 13
Stub Peer Advertising (CONNECTED SUMMARY ) Routes
Suppressing queries
BFD sessions
NeighAddr Interface
NoticeinExample237thatrouterHQseesrouterBR1Aastubrouter.Bydefault,stub
routersadvertiseonlyconnectedandsummaryroutestotheirneighbors;allotherroutes
arefiltered.Alsonoticetheinformationaboutthequeries.HQisnowsuppressingthem
becauseBR1Aisconfiguredasstub.
InExample238,theroutingtableonBR1Aisverifiedusingtheshowiproutecommand.
Example 2-38 Verifying the Routing Table on BR1A
BR1A# show ip route


D 10.1.0.0 [90/409600] via 172.16.1.1, 00:18:52, Ethernet0/0
S 192.168.17.0/24 [1/0] via 192.168.16.2
S 192.168.18.0/24 [1/0] via 192.168.16.2
NoticehowtheroutingtableonBR1Adidnotchangeafteritwasconfiguredasastub.
Configuringarouterasastubdoesnotchangeorlimittheinformationthatitreceives
fromitsneighbors,butratherlimitswhatinformationitshareswithitsneighbors.
Now,examinetheroutingtableonHQusingtheshowiproutecommandinExample239.
Bydefault,EIGRPstubrouterannouncesonlyconnectedandsummary routes.Notice
intheoutputhowtheexternalEIGRProute192.168.18.0/24isnolongerpresentinthe
routingtableonHQ.
Example 2-39 Verifying the Routing Table on HQ with BR1A as a Stub

HQ# show ip route

D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:09:07, Ethernet0/0
D 192.168.16.0/23 [90/307200] via 172.16.1.2, 00:09:07, Ethernet0/0
InExample240,BR1AisconfiguredasanEIGRPstubadvertisingonlyconnectedrout
ersusingtheeigrpstubconnectedcommand.
Example 2-40 BR1A Configured as a EIGRP Connected Stub

BR1A(config-router)# eigrp stub connected

WhenyouchangetheEIGRPstuboptions,anyneighboringsessionneedstobetorn
downand reestablished.
Next,theEIGRPneighborstubsettingonHQisverifiedusingtheshowipeigrpneigh
borsdetailcommandinExample241.
Example 2-41 Neighbor BR1A Verified as an EIGRP Connected Stub on HQ

(sec) (ms) Cnt Num
0 172.16.1.2 Et0/0 14 00:10:25 12 100 0 8

Stub Peer Advertising (CONNECTED ) Routes
Suppressing queries
BFD sessions
NeighAddr Interface
OntheHQrouter,theroutingtableisverifiedusingtheshowiproutecommandin
Example242.
Example 2-42 Verifying the Routing Table HQ

HQ# show ip route

D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:14:52, Ethernet0/0
D 192.168.16.0/24 [90/307200] via 172.16.1.2, 00:14:52, Ethernet0/0
NoticethatBR1Anowadvertisesonlyconnectednetworks192.168.0.0/24and
192.168.16.0/24.Thesummaryroute192.168.16.0/23andtheredistributedstaticroute
pointingtonetwork192.168.18.0/24arenolongerreceivedbyHQ.
Next,Example243showstheBR1ArouterconfiguredasanEIGRPreceiveonlystub
usingtheeigrpstubreceiveonlycommand.
Example 2-43 BR1A Configured as an EIGRP Receive-Only Stub

BR1A(config-router)# eigrp stub receive-only
BR1A(config-router)#
WitheachchangeofEIGRPstubsettings,reestablishmentoftheEIGRPneighboring
sessionis required.
The EIGRPneighborstubsettingonHQisverifiedusingtheshowipeigrpneighbors
detailcommandinExample244.
Example 2-44 Neighbor BR1A Verified as an EIGRP Receive-Only Stub on HQ

(sec) (ms) Cnt Num
0 172.16.1.2 Et0/0 10 00:03:03 1999 5000 0 10
Version 7.0/3.0, Retrans: 1, Retries: 0
Receive-Only Peer Advertising (No) Routes
Suppressing queries
BFD sessions
NeighAddr Interface
NeighboringrouterBR1Aisnowconfiguredasareceiveonlystub.HQ willstillsup
pressquerypackets,butrouterBR1Aisnotannouncinganyroutes,eventhoughthe
EIGRPsessionisestablished.
ThisisverifiedinHQsroutingtableusingtheshowiproutecommandinExample245.
Example 2-45 Verifying the Routing Table on HQ
HQ# show ip route



C 172.16.1.1 /30 is directly connected, Ethernet0/0
L 172.16.1.2 /32 is directly connected, Ethernet0/0
NoticethatalldynamicEIGRProuteshavedisappearedfromtheHQsrouting table.
RouterBR1Aisconfiguredasreceiveonlystubandisnotadvertisinganyroutesto
HQ.ThisstuboptioncanbeusefulincaseswhenallhostsbehindrouterBR1Awould
betranslatedusingNATwithPAT.Inascenariolikethis,HQhasnoneedtobeaware
ofnetworksbehindrouterBR1Abecausealloutgoingtrafficwouldbedestinedforthe
BR1AWANinterface,whereNATwouldbeperformed.
InExample 246,BR1Asroutingtableisshownusingtheshowiproutecommand.
Example 2-46 Routing Table of BR1A Configured as a Receive-Only Stub
BR1A# show ip route


D 10.1.0.0 [90/409600] via 172.16.1.1, 00:05:57, Ethernet0/0
S 192.168.17.0/24 [1/0] via 192.168.16.2
S 192.168.18.0/24 [1/0] via 192.168.16.2
Noticethateventhereceiveonlystuboptiondoesnotinfluencewhichroutesare
receivedbythestubrouter.TheroutingtableonBR1Aremainsthesameregardless of
EIGRPstubconfigurationontheBR1Arouter.
Stuck in Active
Whenarouterlosesarouteandsendsaquerymessagetoitsneighbors,itisexpectinga
responsetothatquerymessageinaformofareplypacket.Failuretoreceivearesponse
toaquerymessagecanleadtosessiontermination.
EIGRPusesareliablemulticastapproachtosearchforanalternative route.Therefore,it
isimperativethatEIGRPreceivesareplyforeachquerythatitgeneratesinthenetwork.
Oncearoutegoesactiveandthequerysequenceisinitiated,itcanonlycomeoutofthe
activestateandtransitiontothepassivestatewhenitreceivesareplyforeverygener
atedquery.Iftherouterdoesnotreceiveareplytoalltheoutstandingquerieswithin3
minutes(thedefaulttime),theroutegoesintothestuckinactive(SIA)state.Thistimer
iscalledtheactivetimer.Oncetheactivetimerexpires,theneighborrelationshipis
reset.Thissettingcausestheroutertogoactiveonallroutesthatwereknownthrough
thelostneighborandtoreadvertisealltheroutesthatitknowstothelostneighbor.
ShowninFigure215,themostcommonreasonforlostreplymessagesisanunreliable
linkbetween thetworouters,onwhichsomepacketsmightgetlost.Althoughtherout
ersreceiveenoughpacketstomaintaintheneighborrelationship,therouterdoesnot
receiveallthequeriesorreplies.Whenthisconditionoccurs,theeffecteddeviceswill
generateEIGRPDUAL3SIAerrormessages.
Active
R1 Reply is lost
Active R5
192.168.14.0/24
R3 R6
Queries
Replies
R2 R7
Active
R4
R8
Figure 2-15 EIGRP Lost Reply

Resettinganeighborrelationshipduetoalostreplymessageisveryaggressivebehavior.
Inlargeenvironmentswithslowerlinks,itcancauselongconvergencetimesandnetwork
instability.
TwonewadditionalEIGRPpacketswereintroducedtoovercomethedescribedlimita
tion.Whennoreplytoaqueryisreceived,EIGRPsendsanSIAquerypacketwhenthe
activetimerishalfwaythrough(after90seconds).Thisenablestheneighboringrouterto
respondwithaSIAreplyandconfirmtotheupstreamrouterthatitisstillsearchingfor
areplacementroute.
SIA-Reply
SIA Query Lost reply
R1 R2 R3
192.168.14.0/24 Query Query
Figure 2-16 EIGRP Stuck in Active

PacketsillustratedintheFigure216areexchangedinthefollowingorder:
R1queriesdownstreamR2(withanSIAquery)atthemidwaypointoftheactive
timer(oneandahalfminutesbydefault)aboutthestatusoftheroute.
R2responds(withanSIAreply)thatitstillissearchingforareplacementroute.
UponreceivingthisSIAreplyresponsepacket,R1validatesthestatusofR2and
doesnot terminatetheneighborrelationship.
Meanwhile,R2willsenduptothreeSIAqueriestoR3.Iftheygounanswered,R2
willterminatetheneighborrelationshipwithR3.R2willthenupdateR1withan SIA
replyindicatingthatthenetwork192.168.14.0/24isunreachable.
R1andR2willremovetheactiveroutefromtheirtopologytables.Theneighbor
relationshipbetweenR1andR2remainsintact.
Reducing Query Scope by Using Summary Routes

Anotherwayyoucanreducethenumberofquerymessagesistoimplementroutesum
marization.WhenarouterreceivesanEIGRPqueryforaspecificnetwork,whichis
includedinasummaryroutepresentintheroutersroutingtable,itimmediatelysends a
replymessagewithoutfurtherforwardingthequerypacket.Thisreducesthenumberof
queriessentandimprovesconvergencetime.
IntheFigure217scenarioexample,routerHQperformssummarizationforallremote
networks.Asummaryrouteisannouncedtootherrouters,likerouterGW.Whencon
nectivitytotheremotelocationfailsandHQisleftwithoutanyfeasiblesuccessorsto
reachthe lostnetwork,itsendsaquerytoitsneighbors.WhenrouterGWreceivesa
queryforanetwork192.168.12.0/24,itimmediatelyrespondswithareplymessage
withoutfurtherforwardingthequerybecauseithasasummaryroute192.168.0.0/16,
whichalsodescribes192.168.12.0/24prefix.However,becausethisroutewaslearned
fromrouterHQ,routerGWwillrespondthatitdoesnothaveanalternativepath for
192.168.12.0/24.
Repl 192.168.12.0/24
BR
Query WAN
GW HQ
WAN
Summary route
192.168.18.0/24
192.168.0.0/16
BR
Figure 2-17 Reducing Queries Using a Summary Route
Configuring EIGRP Summarization

ImplementingEIGRPsummarizationprovidesseveralbenefits.Notonlydoesitreduce
thesizeofroutingtablesontherouters,butitalsolimitsthequeryscope.Inthissec
tion,wewillconfigureEIGRPsummarizationusingthetopologyinFigure218.
Lo0: 10.10.0.0/16
Lo1: 10.11.0.0/16
Lo2: 10.12.0.0/16
BR Lo3: 10.13.0.0/16
WAN
Internet
HQ
WAN
Lo0: 10.64.0.0/16
Lo1: 10.65.0.0/16
BR Lo2: 10.66.0.0/16
2
Figure 2-18 EIGRP Topology for Summarization
Priortoanysummarization,Example247showstheroutingtableonHQusingthe
showiproutecommand.
Example 2-47 Verifying HQs Routing Table Prior to Summarization

HQ# show ip route
Gateway of last resort is 209.165.200.226 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.10.0.0 [90/409600] via 172.16.1.2, 00:18:16, Ethernet0/1
D 10.11.0.0 [90/409600] via 172.16.1.2, 00:18:16, Ethernet0/1
D 10.12.0.0 [90/409600] via 172.16.1.2, 00:18:16, Ethernet0/1
D 10.13.0.0 [90/409600] via 172.16.1.2, 00:18:16, Ethernet0/1
D 10.64.0.0 [90/409600] via 172.16.2.2, 00:16:55, Ethernet0/2
D 10.65.0.0 [90/409600] via 172.16.2.2, 00:16:55, Ethernet0/2
D 10.66.0.0 [90/409600] via 172.16.2.2, 00:16:55, Ethernet0/2
NoticeintheoutputthatHQreceivedsevendifferentinternalnetworksfromrouters
BR1andBR2.Reducingthenumberofroutesintheroutingtablebyusingsummariza
tionimprovesnetworkconvergenceandalsoreducesthenumberofqueries. EIGRPsup
portsbothautomaticandmanualsummarization.
InExample248,automaticEIGRPsummarizationisconfiguredonBR1usingtheauto
summaryEIGRPconfigurationcommand.

Example 2-48 Configuring Automatic Summarization on BR1

BR1(config-router)# auto-summary
(Ethernet0/0) is resync: summary configured
(Ethernet0/0) is resync: summary up, remove components
Whenautomaticsummarizationisenabled,theneighboringadjacencydoesnotterminate;
onlyroutinginformationissynchronized.TheautosummaryEIGRPcommandenables
automaticsummarizationofroutestoclassfulnetworkboundaries.ThisEIGRPbehavior
wasenabledbydefaultondevicesrunningoldersoftware,beforeCiscoIOS15.
InExample 249,thesummarizedrouteonHQisverifiedusingtheshowiproute
command.

Example 2-49 Verifying BR1s Summarized Routes on HQ
HQ# show ip route

S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.0.0.0/8 [90/409600] via 172.16.1.2, 00:17:23, Ethernet0/1
D 10.64.0.0/16 [90/409600] via 172.16.2.2, 00:32:36, Ethernet0/2
D 10.65.0.0/16 [90/409600] via 172.16.2.2, 00:32:36, Ethernet0/2
D 10.66.0.0/16 [90/409600] via 172.16.2.2, 00:32:36, Ethernet0/2
The routes10.10.0.0/16to10.13.0.0/16arenolongerintheHQroutingtable.Instead,
theyarereplacedbytheautosummaryroute10.0.0.0/8.
Next,inExample250,viewtheroutingtableonBR1usingtheshowiproutecommand.
Example 2-50 Null0 Summary Route on BR1

BR1# show ip route

D 10.64.0.0/16 [90/435200] via 172.16.1.1, 00:31:01, Ethernet0/0
D 10.65.0.0/16 [90/435200] via 172.16.1.1, 00:31:01, Ethernet0/0
D 10.66.0.0/16 [90/435200] via 172.16.1.1, 00:31:01, Ethernet0/0
D 172.16.2.0/30 [90/307200] via 172.16.1.1, 00:31:06, Ethernet0/0
D 209.165.200.224 [90/307200] via 172.16.1.1, 00:31:06, Ethernet0/0
NotetheadditionalrouteinBR1sroutingtabledescribingnetwork10.0.0.0/8and
pointingtotheNull0interface.Thisrouteisinstalledautomaticallywhenroutesumma
rizationis configured,topreventroutingloops.ImaginethatBR1receivesapacketfora
networkthatisdescribedwiththesummaryroute10.0.0.0/8andisnotpresentinBR1s
routingtable.IfBR1hadadefaultroutepointingtoHQ,itwouldsendthispacketback
toHQ,andHQwouldbounceitbacktoBR1.Thispacketwouldbe stuckinarouting
loopuntiltheTimeToLive(TTL)fieldexpired.AsummaryroutepointingtotheNull0
interfaceonarouterthatannouncesthesummaryroutetootherneighborstherefore
preventspotentialroutingloops.
InExample251,automaticEIGRPsummarizationisalsoenabledonBR2usingtheauto
summaryEIGRPconfigurationcommandonBR2.
Example 2-51 Configuring Automatic Summarization on BR2

BR2(config-router)# auto-summary
BR2(config-router)#
(Ethernet0/0) is resync: summary up, remove components
The summaryrouteonHQisverifiedbyviewingHQsroutingtableonHQusingthe
showiproutecommand,asshowninExample252.
Example 2-52 Verifying BR2s Summarized Routes on HQ
HQ# show ip route

S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.0.0.0/8 [90/409600] via 172.16.2.2, 00:51:02, Ethernet0/2
[90/409600] via 172.16.1.2, 00:51:02, Ethernet0/1
NoticethatHQreceivedthesamesummaryroutefromBR2asitdidfromBR1.This
isbecausebothBR1andBR2sitonamajornetworkboundaryandthereforeadvertise
thesamesummaryroute.Becausebothrouteshavethesamecost,HQwillloadbalance
betweenthesetworoutes.
ConnectivityistestedusingthepingcommandfromHQtoIPaddress10.10.0.1,which
belongstothesummarizednetworkonrouterBR1.Example253showsthe resultsof
theping.
Example 2-53 Testing Connectivity from HQ to the Summarized Network

HQ# ping 10.10.0.1
U.U.U
Success rate is 0 percent (0/5)
Thereisagoodchancethatthisconnectivitytestwillfail.Ifyoureceivedsuccessful
ICMPreplies,trytotestconnectivitytoIPsfromothersummarizednetworks,suchas
10.11.0.1,10.12.0.1,or10.13.0.1.
The outputU.U.UindicatesthatHQreceivedICMPdestinationunreachablereplies.
BecauseHQthinksthatbothroutershaveaccesstoallnetworkswithin10.0.0.0/8prefix,
itcaneasilyforwardtraffictotheincorrectneighbor.
Automatic summarizationcausesconnectivityissuesinnetworkswhereclasslessnet
worksarediscontiguous.Network10.0.0.0/8representsonelargeclassfulnetwork,but
inourscenario,portionsofthisnetworkareusedindifferentlocations.Becauseavast
majorityofnetworkstodayusesmallsubnetsofclasslessaddresses,automaticsumma
rizationbecomesusefulonlyinrarecasesandthereforeisnotarecommendedwayto
optimizeEIGRP.
TodisableEIGRPautomaticsummarizationonbothBR1andBR2thenoautosummary
commandisusedonbothrouters,asshowninExample254.
Example 2-54 Disabling Automatic Summarization on BR1 and BR2

BR1(config-router)# no auto-summary
---------------------------------------------------------------------------
BR2(config-router)# no auto-summary
TheoutputinExample255verifiesthatautomaticsummarizationhasbeendisabledon
bothrouters,byusingtheshowiproutecommandonHQ.
Example 2-55 HQs Routing Table Verifying Automatic Summarization Has Been
Disabled
HQ# show ip route
S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.10.0.0 [90/409600] via 172.16.1.2, 00:23:26, Ethernet0/1
D 10.11.0.0 [90/409600] via 172.16.1.2, 00:23:26, Ethernet0/1
D 10.12.0.0 [90/409600] via 172.16.1.2, 00:23:26, Ethernet0/1
D 10.13.0.0 [90/409600] via 172.16.1.2, 00:23:26, Ethernet0/1
D 10.64.0.0 [90/409600] via 172.16.2.2, 00:22:05, Ethernet0/2
D 10.65.0.0 [90/409600] via 172.16.2.2, 00:22:05, Ethernet0/2
D 10.66.0.0 [90/409600] via 172.16.2.2, 00:22:05, Ethernet0/2
The HQrouternowhasallannouncedEIGRPnetworks.
Determining the Summary Route

Todeterminethesummaryroute,youneedtoanalyzethesubnetsyouwanttosum
marize.Youneedtodeterminethehighestorderbitsthatmatchinalloftheaddresses.
ByconvertingtheIPaddressestothebinaryformat,youcanidentifythecommonbits
sharedamongthesubnets.
IntheexampleinTable22,thefirst13bitsarecommonamongthesubnets.Therefore,
thebestsummaryrouteis10.8.0.0/13.
Table 2-2 Calculating an IPv4 Summary Route
Prefix Binary Format

10.10.0.0/16 00001010 . 00001010 . 00000000 . 00000000
10.11.0.0/16 00001010 . 00001011 . 00000000 . 00000000
10.12.0.0/16 00001010 . 00001110 . 00000000 . 00000000
10.13.0.0/16 00001010 . 00001111 . 00000000 . 00000000
Summaryroute
10.8.0.0/16 00001010 . 00001000 . 00000000 . 00000000
Keepinmindthatthesummaryroute10.8.0.0/13alsodescribessomeunlistednetworks
besidethefoursubnetsinthetable.Twosuchexamplesarenetwork10.9.0.0/16and
10.14.0.0/16.Ifthesesubnetsareusedinadifferentpartofthenetwork,thedetermined
summaryroutewouldcauseconnectivityissues.Inthisexample,twoseparatesummary
routeswouldneedtobedefined.Summaryroute10.10.0.0/15woulddescribeonlynet
works10.10.0.0/16and10.11.0.0/16,andsummaryroute10.12.0.0/15woulddescribe
only the 10.12.0.0/16 and 10.13.0.0/16 subnets.
Ifarouterhastworoutestothesamedestination(forexample,asummaryrouteanda
morespecificroutewithalongermatchingprefixlength),theroutingtableprocesswill
choose themorespecificmatch.
Continuingwiththepriortopology,Example256showsBR1configuredformanual
summarizationoninterfaceEthernet0/0usingtheipsummaryaddresseigrp1
10.8.0.0/13 interface command.
Example 2-56 Configuring Manual Summarization on BR1

BR1(config)# interface Ethernet 0/0
BR1(config-if)# ip summary-address eigrp 1 10.8.0.0/13
*Dec 3 13:22:53.406: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.16.1.1
Toconfiguremanualroutesummarization,itisnecessarytoselectthecorrectinterface
topropagatethesummaryroute,thecorrectautonomoussystemnumber,thesummary
address, anditsmask.BeginningwithCiscoIOS15,theipsummaryaddresscommand
canuseeither thesubnetmaskindotteddecimalformatorusetheprefixlength,asindi
cated intheexample.
Youcandeterminewhatkindofsummaryrouteyouneedtospecifybyanalyzingcom
monbitsinIPaddressofallsubnetsthatyouwanttosummarizetoonenetwork.All bits
thatarecommonbetweenaddressesdefinethesummaryaddressanditsmask.
Notethatthesummaryrouteisadvertisedonlyifamorespecificcomponent(amore
specificentry)ofthesummaryrouteispresentintheroutingtable.
ExamineBR1s routingtableusingtheshowiproutecommand,asshowninExample257.
Example 2-57 Null0 Route in BR1s Routing Table
BR1# show ip route


D 10.64.0.0/14 [90/435200] via 172.16.1.1, 00:24:06, Ethernet0/0
D 172.16.2.0/30 [90/307200] via 172.16.1.1, 05:09:11, Ethernet0/0
D 209.165.200.224 [90/307200] via 172.16.1.1, 05:09:11, Ethernet0/0
Whenconfiguringaroutertoannounceasummaryroute,italsoaddsthisroute toits
routingtableandpointsitattheNullinterfacetopreventroutingloops.Apacketfor
wardedtotheNullinterfaceissimplydropped,whichpreventstherouterfromforward
ingthepackettoadefaultrouteandpossiblycreatingaroutingloop.
Forexample,ifBR1receivesapacketdestinedfornetwork10.8.0.0/24,theroute
10.8.0.0/13pointingtotheNullinterfaceisidentifiedasthebestmatch.Thispacketgets
discardedbecauseamorespecificrouteisnotknowntotherouter.
AsshowninExample258,BR2isalsoconfiguredwithmanualsummarizationoninterface
Ethernet 0/0usingtheipsummaryaddresseigrp110.64.0.0/14interfacecommand.
Example 2-58 Configuring Manual Summarization on BR2

BR2(config)# interface Ethernet 0/0
BR2(config-if)# ip summary-address eigrp 1 10.64.0.0/14
The summaryaddress10.64.0.0/14isdeterminedbyanalyzingthecommonbitsamong
thesubnetsthatarepresentonrouterBR2.
VerifythatthesummaryroutesareadvertisedbyexaminingtheroutingtableonHQ
usingtheshowiproutecommand,showninExample259.
Example 2-59 Verifying Summary Routes Received on HQ

HQ# show ip route

S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.8.0.0/13 [90/409600] via 172.16.1.2, 01:30:05, Ethernet0/1
D 10.64.0.0/14 [90/409600] via 172.16.2.2, 01:10:46, Ethernet0/2
All branchsubnetsarenowsummarizedbytwosummaryroutes.Themetricofthesum
maryrouteequalstotheminimummetricofmorespecificroutes,whichareaggregated
inthesummaryroute.
Noticealsothedefaultroute,pointingtothenexthopIPaddress209.165.200.226,
whichis reachableovertheEthernet0/0interface.
TestwhetherHQhasconnectivitytoexternalnetworkreachableovertheInternetby
using theping 209.165.202.129 command, shown in Example 260.
Example 2-60 Testing Connectivity to the External Network on HQ

HQ# ping 209.165.202.129
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Connectivity totheexternalIPaddressissuccessfulbecauseHQhasadefaultroute
pointingtowardtheInternetnetwork.
Next,inExample261,testtodeterminewhetherBR1hasconnectivitytotheexternal
networkbyusingtheping209.165.202.129command.Verifyalsotheroutingtable
using the show ip route 209.165.202.129 command.
Example 2-61 Testing Connectivity to the External Network on BR1

BR1# ping 209.165.202.129
.....
Success rate is 0 percent (0/5)
BR1# show ip route 209.165.202.129
% Network not in table
ConnectivitytoexternalIPaddress209.165.202.129failsbecauseBR1hasnoinforma
tiononhowtoreach209.165.202.129IPaddress.
Connectivitytoexternalnetworksisnormallyprovidedbytheuse ofthedefaultroute,
becausedescribingallindividualexternalnetworks,likethosepresentontheInternet,
wouldbetimeandresourceconsuming.
Obtaining Default Route

Aroutercanobtainadefaultrouteinseveraldifferentways.
The mainpurposeofusingadefaultrouteistodecreasethesizeoftheroutingtable.
Thisespeciallyappliestothestubnetworks,whereitispreferredtooptimizethenum
berofroutes.
Beforearouterinstallsthedefaultroute,itexaminesdefaultroutecandidates:
Thecandidatecanbeastaticallyconfigureddefaultroutedefinedlocallywiththe
command ip route 0.0.0.0 0.0.0.0 next-hop | interface. In this command, interface
istheoutgoinginterfacethroughwhichallpacketswithunknowndestinationswill
beforwarded,andnext-hop istheIPaddresstowhichpacketswith unknowndesti
nationswillbeforwarded.
Thecandidateisalsoadefaultrouteannouncedbythedynamicroutingprotocol.
EIGRPcanredistributestaticallydefineddefaultroutesbyusingtheredistribute
staticconfigurationcommand.
In addition,anyclassfulnetworkresidinginthelocalroutingtablecanbecomea
defaultcandidatewhenusedwiththeipdefaultnetworkconfigurationcommand.
The commandattachesanexteriorflagtoanyclassfulEIGRProute,thusmakingita
candidate foradefaultroute.
Note InEIGRP,defaultroutescannotbedirectlyinjectedasinOSPF,forexample,
whereyoucanusethedefaultinformationoriginatecommand;however,youcan
summarizeto0.0.0.0/0onaninterface.

The routerexaminesalldefaultcandidatesandselectsthebestonebasedontheADand
routemetric.

Whenselected,theroutersetsthegatewayoflastresorttothenexthopof theselected
candidate.Thisdoesnotapplywhenthebestcandidatehappenstobeoneofthedirect
lyconnectedroutes.
InExample262,theroutingtableisverified,andastaticdefaultrouteisredistributed
onHQintoEIGRPusingtheredistributestaticEIGRPconfigurationcommand.

Example 2-62 Verifying HQs Routing Table and Redistributing a Static Default Route
HQ# show ip route

S* 0.0.0.0/0 [1/0] via 209.165.200.226

D 10.8.0.0/13 [90/409600] via 172.16.1.2, 23:00:26, Ethernet0/1
D 10.64.0.0/14 [90/409600] via 172.16.2.2, 22:41:07, Ethernet0/2
HQ# configure terminal
HQ(config-router)# redistribute static
NoticethestaticdefaultroutepresentinHQsroutingtable.Theredistributestatic
commandredistributesallstaticallydefinedroutesonHQintotheEIGRPprocess.
BecausethedefaultrouteistheonlystaticroutedefinedonHQ,onlythisroutewill be
redistributed.
InExample263,theroutingtableonBR1isverifiedusingtheshowiproutecommand.

Example 2-63 Verifying the Redistributed Static Default Route Is Received on BR1
BR1# show ip route

D*EX 0.0.0.0/0 [170/307200] via 172.16.1.1, 00:17:06, Ethernet0/0

D 10.64.0.0/14 [90/435200] via 172.16.1.1, 22:51:03, Ethernet0/0
D 172.16.2.0/30 [90/307200] via 172.16.1.1, 1d03h, Ethernet0/0
D 209.165.200.224 [90/307200] via 172.16.1.1, 1d03h, Ethernet0/0
YoucanseethatBR1receivedadefaultrouteoverEIGRP.Theneighboringrouter,HQ,
whichannouncedthedefaultroute,wasselectedasagatewayoflastresort.BR1will
nowsendallpacketswithunknowndestinationstowardHQ.
Route0.0.0.0ismarkedwithanasterisk(*),whichindicatesthatitisa candidatedefault
route.ItisalsolabeledwithDEX,whichindicatesthatrouteisanexternalEIGRProute.
EIGRPmarksallroutesthathavebeenlearnedbyanotherroutingprotocolor thatreside
intheroutingtableasstaticroutesasexternalroutes.
ConnectivityonBR1toexternalnetworkisverifiedusingtheping209.165.202.129
command,asshowninExample264.
Example 2-64 Verifying Connectivity from BR1 to an External Network

BR1# ping 209.165.202.129
!!!!!
Connectivity fromBR1toexternalnetworkisnowsuccessful.BecauseBR1hasnospe
cificinformationaboutthedestinationIPaddress209.165.202.129,ituses thereceived
defaultnetworktoforwardpacketstowardtheHQrouter.
Load Balancing with EIGRP

EIGRPcandistributetrafficovermultiplelinksleadingtothesamedestinationto
increasetheeffectivenetworkbandwidth.Itsupportsloadbalancingoverequalmetric
pathsandalsooverunequalmetricpaths.
EIGRPenablesloadbalancingbetweenamaximumoffourequalmetricpathsby
default.YoucanconfigurethemaximumnumberofparallelroutesthatanIProuting
protocolcansupportusingthemaximumpathsrouterconfigurationcommand.Upto
sixequallygoodroutescanbekeptintheroutingtable.
Whena packetisprocessswitched,loadbalancingoverequalmetricpathsoccursona
perpacketbasis.Whenpacketsarefastswitched,loadbalancingoverequalmetricpaths
occursonaperdestinationbasis.CiscoExpressForwarding(CEF)switching,enabledby
default,supportsbothperpacketandperdestinationloadbalancing.
Loadbalancingoverunequalmetriclinksisdisabledbydefault.Onlyfeasiblesuccessor
pathscanbeincludedintheEIGRPloadbalancing,toensurethetopologystaysloop
free.
Configuring EIGRP Load Balancing

Inthissection,wewillconfigureEIGRPunequalcostloadbalancing.Thetopologyin
Figure219includestworouters,whichareinterconnectedwiththreelinks.Thefirst
two Ethernetlinksareequal,butthethirdseriallinkisslower.EIGRPhasalreadybeen
configuredonbothrouters.
4Mbps
WAN link
172.16.1.0/30
.1
Eth0/1 4Mbps Eth0/1 192.168.0.0/24

HQ WAN link B
R
172.16.2.0/30
1Mbps
WAN link
172.16.3.0/30
Figure 2-19 EIGRP Topology for Load Balancing
EIGRP Load Balancing

First,inExample265,weverifyconnectivityfromHQtoIPaddress192.168.0.1onthe
BRrouter.
Example 2-65 Verifying Connectivity from HQ to BR
HQ# ping 192.168.0.1

!!!!!
The routingtableonHQisverifiedinExample266.
Example 2-66 Verifying the Routing Table on HQ
HQ# show ip route


C 172.16.3.0/30 is directly connected, Serial1/0
L 172.16.3.1/32 is directly connected, Serial1/0
D 192.168.0.0/24 [90/409600] via 172.16.2.2, 00:26:18, Ethernet0/1

[90/409600] via 172.16.1.2, 00:26:18, Ethernet0/0

Eventhoughthreelinksareestablishedbetweentherouters,HQhasinsertedonlytwo
equalcostEIGRProutesintotheroutetableforthedestinationnetwork192.168.0.0/24.
TrafficforthisdestinationwillbeloadbalancedacrossinterfacesEthernet0/0and
Ethernet 0/1.
HQsroutingtablehastwopathsforthe192.168.0.0/24network,butitishelpfultosee
whatisstoredinHQsEIGRPtopologytable.InExample267,weexaminetheEIGRP
topologytableonHQ.
Example 2-67 Viewing HQs Topology Table with Equal-Cost Routes
HQ# show ip eigrp topology


via 172.16.1.2 (409600/128256), Ethernet0/0
via 172.16.2.2 (409600/128256), Ethernet0/1
via 172.16.3.2 (2297856/128256), Serial1/0
TheEIGRPtopologytablerevealsthatHQreceivedinformationaboutthedestination
network192.168.0.0/24overallthreeinterfaces.BothroutesoverEthernetinterfaces
havethelowestcostandarebothselectedassuccessorroutes.Thethirdroutereceived
overtheserialinterfacehasahighercostbecauseofthelowerbandwidthontheserial
link.
Bydefault,onlyequalcostloadbalancingisenabled.Forutilizationofunequalcost
links,additionalconfigurationisrequired.
EIGRP Load Balancing Across Unequal-Metric Paths

EIGRPcanbalancetrafficacrossmultipleroutesthathavedifferentmetrics,whichis
calledunequalmetricloadbalancing.ThedegreetowhichEIGRPperformsloadbalanc
ingis controlledbythevarianceparameter.SettingavariancevalueenablesEIGRPto
installmultipleloopfreerouteswithunequalmetricinalocalroutingtable.EIGRPwill
alwaysinstall asuccessorintothelocalroutingtable.Additionalfeasiblesuccessorsare
candidatesforthelocalroutingtable.AdditionalentriesthroughEIGRPmustmeettwo
criteriatobeinstalledinthelocalroutingtable:
Theroutemustbeloopfree.Thisconditionissatisfiedwhentheadvertiseddistance
islessthanthetotaldistance,orwhentherouteisafeasiblesuccessor.
Themetricoftheroutemustbelowerthanthemetricofthebestroute(thesucces
sor)multipliedbythevariancethatisconfiguredontherouter.
The defaultvalueforthevariancecommandis1,whichindicatesequalcostloadbalanc
ing;onlyrouteswiththesamemetricasthesuccessorareinstalledinthelocalrouting
table.Thevariancecommandisnotlimitingthemaximumnumberofpaths;itisthe
multiplierthatdefinestherangeofmetricvaluesthatareacceptedforloadbalancingby
theEIGRPprocess.Ifthevarianceissetto2,anyEIGRPlearnedroutewithametricthat
islessthantwotimesthesuccessormetricwillbeinstalledinthelocalroutingtable.The
EIGRPvariancecommandhasasingleparameter,multiplier,whichisthemetricvalue
usedforloadbalancing.Itcanbeavaluefrom1to128.Thedefaultis1,whichmeans
equalcostloadbalancing.
Note EIGRPdoesnotloadsharebetweenmultipleroutes;itonlyinstallstheroutes
inthelocalroutingtable.Thelocalroutingtablethenenablesswitchinghardware or
softwaretoloadsharebetweenthemultiplepaths.

OnHQ,modifyingthevariancemultiplier,asshowninExample268,enablesEIGRP
unequalloadbalancing.
Example 2-68 Verifying Connectivity from BR1 to an External Network

HQ(config-router)# variance 6
The costofthepathovertheseriallinkequals2297856,andthebestpathhasacost
of409600.Youneedtodefinethevariancevalueasatleast6orhigherifyouwantto
includethepathovertheseriallinkintotheroutingtable.Whenvarianceissetto6or
higher,thecostofthepathovertheseriallink(2297856)islowerthanthebestpathcost
multipliedbythevariancemultiplier.
Example269showsthechangeinHQsroutingtable.
Example 2-69 Verifying Connectivity from HQ to an External Network

HQ# show ip route

C 172.16.3.0/30 is directly connected, Serial1/0
L 172.16.3.1/32 is directly connected, Serial1/0
D 192.168.0.0/24 [90/2297856] via 172.16.3.2, 00:02:03, Serial1/0

[90/409600] via 172.16.2.2, 00:02:03, Ethernet0/1

[90/409600] via 172.16.1.2, 00:02:03, Ethernet0/0
Afterconfiguringthevariancemultiplier,routerHQinstallsallthreeroutesfordestina
tion 192.168.0.0/24 into the routing table.
ThevariancevaluecanbeverifiedbydisplayingtheIPprotocolssettings shownin
Example270.
Example 2-70 Verifying Variance Setting on HQ

Routing Protocol is "eigrp 1"

Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP-IPv4 Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 172.16.3.1
Topology : 0 (base)
Active Timer: 3 min

Maximum path: 4
Maximum hopcount 100
Maximum metric variance 6
Automatic Summarization: disabled

Maximum path: 4
0.0.0.0
172.16.2.2 90 00:02:21
172.16.3.2 90 00:02:21
172.16.1.2 90 00:02:21
The commandoutputshowsyouthecurrentvariancesettingsontherouter,inaddition
tothemaximumnumberofpathsthatcanbeusedforloadbalancing.Youcanchange
thelatterbyusingthemaximumpathEIGRPconfigurationcommand.Bysettingthis
valueto1,youeffectivelydisableEIGRPloadbalancing.
Configuring EIGRP for IPv6

OriginallycreatedtorouteforIPv4,IPX,andAppleTalk,EIGRPwaseasilyextendedto
advertiseIPv6routes.AlthoughEIGRPforIPv6sharesmuchofthecharacteristicsofthe
EIGRPforIPv4,italsohassomeuniquespecifics.
OneofthemajordifferencesbetweenIPv4andIPv6EIGRPversionsisthefactthatyou
mustexplicitlyenableEIGRPforIPv6oneachIPv6enabledinterface.
Uponcompletingthissection,youwillbeabletodothefollowing:
DescribedifferencesandsimilaritiesofEIGRPforIPv4andIPv6
ConfigurebasicEIGRPforIPv6settings
ConfigureandverifyEIGRPforIPv6summarization
VerifybasicEIGRPforIPv6settings
Overview of EIGRP for IPv6

EIGRPforIPv6isaversionofEIGRPintendedtosendIPv6prefixes/lengthsrather than
IPv4subnet/maskvalues.ItissometimereferredintheCiscodocumentationasEIGRPv6
toemphasizethatitisusedwiththeIPv6.EIGRPforIPv6hasmuchin commonwith
EIGRPforIPv4,butthefollowingdifferencesbetweenthetwoexist:

EIGRPforIPv6usesIPv6prefixesandlengthsratherthanIPv4subnetsandmasks.
ToestablishEIGRPforIPv6neighborrelationship,itusesIPv6linklocaladdresses.
EIGRPforIPv4doesnothavetheconceptoflinklocaladdress.
EIGRPusesbuiltinauthenticationfeaturesoftheIPv6protocolratherthanprotocol
specificauthenticationimplementedwithIPv4toguaranteemessageauthentication.
Totransportroutinginformation,EIGRPforIPv6encapsulatesIPv6prefixesinthe
IPv6messages,notintheIPv4packets.
IPv6hasnoconceptoftheclassfulnetwork;sowhenyouuseEIGRPforIPv6,there
isnoautomaticsummarizationattheclassboundaries.Theonlywaytosummarize
IPv6advertisedprefixesisthroughmanualsummarization.
IfIPv4addressisnotconfiguredontherouter,EIGRPforIPv6requiresanEIGRP
routerIDbeforeitcanstartrunning.InIPv4,ifyoudonotconfiguretheEIGRP
routerID,therouterwillautomaticallyassignitusingthehighestloopbackorthe
highestactiveinterfaceIPv4address.
YouconfigureEIGRPforIPv6underaspecificinterfaceintendedtosendand
receiveroutingprotocolmessages.InEIGRPforIPv4,youconfigureinterfaces
undertheroutingprotocolconfigurationmode.
EIGRP forIPv6usesassigneddedicatedmulticastaddressFF02::A,whereasEIGRP
forIPv4usesdedicatedmulticastaddress224.0.0.10.

Configuring and Verifying EIGRP for IPv6
Inthissection,weconfigure,establish,andverifyEIGRPforIPv6.Thetopologyin
Figure220hasthreerouter:HQ,BR1,andBR2.Thebranchroutersareconnectedto
theheadquartersusingEthernetlinks.HQandBR1havealreadybeenconfiguredfor
EIGRPforIPv6,butBR2hasnotbeen.IPv6addressesonallroutershavealsoalready
beenconfigured.
BesidestheIPv6globalunicastaddressesshownFigure220,eachrouterhasbeenmanu
allyconfiguredwiththefollowingIPv6linklocaladdresses:

HQEthernet0/0:FE80:100::1
HQEthernet0/1:FE80:200::1
BR1Ethernet0/0:FE80:100::2
BR1Ethernet0/0:FE80:200::2

Configuring EIGRP for IPv6 129
2001:DB8:0:0::/64
Lo0
Lo1
2001:DB8:0:1::/64
BR1 Lo2
WAN Lo3
2001:DB8:0:2::/64
2001:DB8:0:3::/64
2001:DB8:0:100::/64
HQ
WAN
2001:DB8:0:200::/64 Lo0
2001:DB8:0:16::/64
BR2
Figure 2-20 EIGRP for IPv6 Topology
EIGRP for IPv6 Configuration

BeforeconfiguringEIGRPforIPv6,IPv6unicastroutingmustbeenabledontherouter.
Example271showsIPv6routingenabledontheBR2routerusingtheipv6unicast
routingglobalconfigurationcommand.
Example 2-71 Enabling IPv6 Routing on BR2

BR2(config)# ipv6 unicast-routing
The essentialcommandtoenableroutingoftheIPv6datagramsisipv6unicastrouting
inglobalconfigurationmode.Intheabsenceofthiscommand,theroutercanstillbe
configuredwithIPv6addressesonitsinterfacesbutwillnotbeanIPv6router.
The ipv6unicastroutingcommandenablestherouter:
TobeconfiguredforstaticanddynamicIPv6routing
ToforwardIPv6packets
TosendICMPv6routeradvertisementmessages
IfyouhaveconfiguredIPv6routingprotocolsontherouter,thecommandnoipv6
unicastroutingwillremoveallIPv6routingprotocolentriesfromtheIPv6routingtable.
Example272showstheconfigurationofEIGRPforIPv6onBR2usingautonomous
system100andIPaddress192.168.2.1fortherouterID.
Example 2-72 Configuring the EIGRP Router ID on BR2

BR2(config)# ipv6 router eigrp 100
BR2(config-rtr)# eigrp router-id 192.168.2.1
Note EIGRP for IPv6 has a shutdown feature. The routing process must be in no
shutdown modeforEIGRPforIPv6processing.Noshutdownisthedefaultonlater
IOSs.Ifnecessary,youmighthavetoissuethenoshutdowncommandinEIGRPforIPv6
configurationmode.
ConfiguringEIGRPforIPv6consistsoftwosteps.TheinitialstepistoconfigureEIGRP
fortheIPv6routingprocessusingtheipv6routereigrpcommand.Whenenteringthe
command,youmustspecifytheautonomoussystemnumber,whichhasthesamemean
ingasitdoesinEIGRPforIPv4.Itdefinesautonomoussystemsunderthecontrolofa
singleadministrator,anditmustmatchbetweenallneighboringroutersthatintendto
establishanEIGRPadjacency.
Another importantparameteristheEIGRProuterID.LikeEIGRPforIPv4,EIGRPfor
IPv6usesa32bitrouterID.IfnoIPv4activeaddressisconfiguredontherouter,the
routerwillnotbeabletochoosetheEIGRProuterID.Inthiscase,you mustconfigure
therouterIDmanuallyundertheEIGRProutingprocess.
EachrouterparticipatinginEIGRPforIPv4andIPv6isidentifiedbya32bitrouter
ID.Routers willtrytodeterminetherouterIDbasedonthehighestconfiguredIPv4
addressonaloopbackinterfaceor,ifnoloopbackisconfigured,basedonthehighest
configuredIPv4addressonaphysicalinterface.IfnoIPv4interfaceisconfiguredonthe
router,therouterIDmustbemanuallydefinedtomakeEIGRPforIPv6operational.
Example273showstheconfigurationofEIGRPforIPv6onEthernet0/0andLoopback
0interfacesonBR2.

Example 2-73 Configuring EIGRP for IPv6 on BR2 Interfaces
BR2(config)# interface ethernet 0/0

BR2(config-if)# ipv6 eigrp 100
*Oct 23 19:57:55.933: %DUAL-5-NBRCHANGE: EIGRP-IPv6 100: Neighbor
FE80:200::1 (Ethernet0/0) is up: new adjacency
BR2(config-if)# exit
BR2(config)# interface loopback 0
BR2(config-if)# ipv6 eigrp 100
ThesecondstepintheEIGRPforIPv6configurationprocessistoenabletheprotocol
ontheinterface.BeforeyouenableEIGRPforIPv6ontheinterface,itmusthaveavalid
IPv6linklocaladdress.ThisisbecauseEIGRPforIPv6useslinklocal addressestoform
EIGRPneighborrelationships.
Thelinklocaladdressisautomaticallycreatedonaninterfacewhen theinterfaceobtains
aglobalIPv6address,eithermanuallyordynamically.CiscoIOSusesEUI64tocreate
thelinklocaladdresssinterfaceID.
IPv6canalsobeenabledonaninterfacewithoutassigningaglobalunicastaddressusing
theinterfacemodecommandipv6enable.Inthiscase,IPv6linklocaladdress willbe
assignedautomaticallytotheinterface,againusingEUI64fortheinterface ID.

However,automaticallycreatedEUI64linklocaladdressesaredifficulttoremember
orrecognizebecauseorthenondescriptive64bitinterfaceID.Itiscommonpractice
tomanuallyassigneasilyrecognizableIPv6linklocaladdressesontherouterusingthe
commandipv6addresslink-local-address linklocal.Aroutercanbeconfiguredwith
thesamelinklocaladdressonallofitslinksaslongasthelinklocaladdressisuniqueon
each ofitslinks.
Example274verifiesthattheEIGRPforIPv6neighboradjacencyisestablishedwith
routerHQ.
Example 2-74 Verifying EIGRP for IPv6 Neighbor Adjacency on BR2

BR2# show ipv6 eigrp neighbors
(sec) (ms) Cnt Num
0 Link-local address: Et0/0 13 08:25:34 9 100 0 16

FE80:200::1

Outputoftheshowipv6eigrpneighborscommandissimilartotheoutputoftheshow
ipeigrpneighborscommand.YoucannoticethedifferenceintheAddressFormatfield,
becauselinklocalIPv6addressesareusedtoestablishEIGRPneighborrelationship.The
meaningofotherfieldsareidenticaltotheIPv4verificationcommand.
Example275showstheEIGRPforIPv6topologytableonBR2.
Example 2-75 Verifying the EIGRP for IPV6 Topology Table on BR2
BR2# show ipv6 eigrp topology

P 2001:DB8:0:2::/64, 1 successors, FD is 435200

via FE80:200::1 (435200/409600), Ethernet0/0
P 2001:DB8::/64, 1 successors, FD is 435200
via FE80:200::1 (435200/409600), Ethernet0/0
via FE80:200::1 (435200/409600), Ethernet0/0
via FE80:200::1 (435200/409600), Ethernet0/0
via FE80:200::1 (307200/281600), Ethernet0/0
Outputoftheshowipv6eigrptopologycommandagainshowsthesimilaritiesbetween
EIGRPforIPv4andIPv6.Bothprotocolsuseacompositemetric,whichisaninteger
numbercalculatedbyusingdefaultinterfacebandwidthanddelayparameters.Tosend
packetstothedestination,therouterchoosestheroutewiththesmallest(best)metric.
Thisroute,calledthesuccessorroute,willbeplacedintheroutingtable.Otherroutes
thatsatisfythefeasibilityconditionwillbecandidatesforthefeasiblesuccessorroutes.
EIGRPforIPv6useslinklocaladdressestoestablishneighborrelationship,andthese
addresses arealsoshowninthetopologytableassourcesoflearnedroutes.
Example276displaystheIPv6routingtableforEIGRProutesonBR2.
Example 2-76 Displaying the IPv6 Routing Table on BR2

BR2# show ipv6 route eigrp
IPv6 Routing Table - default - 10 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D 2001:DB8::/64 [90/435200]
via FE80:200::1, Ethernet0/0
D 2001:DB8:0:1::/64 [90/435200]
D 2001:DB8:0:2::/64 [90/435200]
D 2001:DB8:0:3::/64 [90/435200]
D 2001:DB8:0:100::/64 [90/307200]
Thesuccessorroutesfromthetopologytablearecandidatestobeinserted intherout
ingtable.Administrativedistance,shownasthefirstnumberinsquaredparentheses,is
bydefaultthesameasitisforIPv4EIGRP.ForinternalEIGRProutes,itissetto90.The
secondnumberinthebracketsrepresentsthefeasibledistance,whichisanEIGRPcom
positemetricofthebestpath.
Example277showsapingfromtheBR2LANinterfacetotheBR1LANaddress.
Example 2-77 Verifying Connectivity to BR1 LAN

BR2# ping 2001:DB8:0:1::1 source loopback 0
Sending 5, 100-byte ICMP Echos to 2001:DB8:0:1::1, timeout is 2 seconds:
Packet sent with a source address of 2001:DB8:0:16::1
!!!!!
IfyouhaveconfiguredLANandWANinterfacesontheBR2routertobeadvertised
usingEIGRPforIPv6,thestreamofICMPechoandreplypacketsbetweenLANinter
faceswillbe sentandreceivedsuccessfully.
Determining the IPv6 Summary Route

TodeterminetheIPv6summaryroute,youneedtoanalyzethesubnetsyouwant
tosummarize.Youneedtodeterminethehighestorderbitsthatmatchinallofthe
addresses.ByconvertingtheIPaddressestothepartialbinaryformat,youcanidentify
thecommonbitssharedamongthesubnets.
InTable23,thefirst62bitsarecommonamongallthreesubnets.Therefore,thebest
summaryrouteis2001:DB8:0:0::/62.
Table 2-3 Calculating an IPv6 Summary Route

Prefix Binary Format
2001:DB8:0:0::64 2001:DB8:0:0000000000000000
2001:DB8:0:1::64 2001:DB8:0:0000000000000001
2001:DB8:0:2::64 2001:DB8:0:0000000000000010
Summaryroute
2001:DB8:0:0::62 2001:DB8:0:0000000000000000
Example278showsrouterBR1summarizingalllocalprefixesbyusingtheipv6sum
maryaddresseigrpconfigurationcommand.
Example 2-78 Configuring EIGRP for IPv6 Summary Route

BR1(config)# interface Ethernet0/0
BR1(config-if)# ipv6 summary-address eigrp 100 2001:DB8:0:0::/62
*Oct 24 18:14:31.222: %DUAL-5-NBRCHANGE: EIGRP-IPv6 100: Neighbor
FE80:100::1 (Ethernet0/0) is resync: summary configured

Summarizationisamethodofreplacingseverallongerprefixeswithoneshorterpre
fix.YouronlyoptiontosummarizeroutesinEIGRPforIPv6ismanualsummarization.
EIGRPforIPv6doesnotsupportautomaticsummarization.SimilartoEIGRPforIPv4,
manualsummarizationcanbeconfiguredintheinterfaceconfigurationmodeusing
theipv6summaryaddresseigrpcommand.Whenasummaryrouteisconfiguredfor
EIGRPforIPv6,therouterwillresynchronizeitsneighborrelationshipontheinterface
wheresummarizationwasconfigured.TheBR1routerwillsendonlyoneaggregated
routetotheHQrouterinsteadofsendingseveralprefixes.
Summarizationreducesthenumberofroutingtableentriesandimprovesnetworksta
bilitybyeliminatingunnecessaryroutingupdatesafterthepartofnetworkfails.Italso
reducesprocessorworkloadandmemoryrequirements.
Example279displaysBR2sIPv6routingtable.
Example 2-79 Verifying Summary Route Received on BR2

B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D 2001:DB8::/62 [90/435200]
D 2001:DB8:0:100::/64 [90/307200]
ThecontentoftheIPv6routingtableontherouterBR2showsthatinsteadoffourLAN
prefixesthereisonlyoneaggregatedprefixwiththeshorterprefixlengthof/62.
AnotherveryusefulcommandfortheEIGRPforIPv6verificationisshowipv6proto
cols, showninExample280.Includedintheoutputfromthiscommandaretheinter
facesthatparticipateintheEIGRPforIPv6routing,theKvalues,andtherouterID.The
defaultADsfortheIPv6EIGRPinternalandexternalroutesarethesameasfortheIPv4
EIGRP:90and170.ThiscommandalsorevealsthedistancevectorsideoftheEIGRPfor
IPv6;ithasarelativelylargemaximumhopcountof100.
Example 2-80 Verifying EIGRP for IPv6 on BR1

BR2# show ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "ND"
IPv6 Routing Protocol is "eigrp 100"
EIGRP-IPv6 Protocol for AS(100)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 K6=0
Router-ID: 192.168.2.1
Topology : 0 (base)
Active Timer: 3 min
Maximum path: 16
Total Prefix Count: 0
Total Redist Count: 0
Interfaces:
Ethernet0/0
Loopback0
Redistribution:
None
Named EIGRP Configuration

EventhoughbasicEIGRPconfigurationisprettysimple,configuringadditionalparam
eterscanincreaseconfigurationcomplexity.Someparametersareconfiguredinglobal
configurationmode,othersunderspecificinterfaces.WhenyouenableEIGRPconfigu
rationforIPv6,thingscanbecomeoverwhelming.Youmustusesimilar,slightlydiffer
entcommandsandconfigurationprocedurestoenableEIGRPforIPv6.
CiscointroducedanewwayofconfiguringEIGRP,whichiscallednamedEIGRP.It
enablesyoutogatherallEIGRPconfigurationsinoneplace,usingunifiedconfiguration
commandsforallunderlyingnetworkprotocols.
DescribehowEIGRPnamedconfigurationisdifferentfromtheclassicEIGRPcon
figuration
Explainwhatisconfiguredunderdifferentaddressfamilyconfigurationmodes
CompareexamplesofclassicandnamedEIGRPconfiguration
ConfiguringandverifyingEIGRPforIPv6
Introduction to Named EIGRP Configuration

ConfiguringEIGRPforbothIPv4andIPv6onthesameroutercanbecomeacomplex
taskbecauseconfigurationtakesplaceusingdifferentrouterconfigurationmodes: rout
ereigrpandipv6routereigrp.Anewerconfigurationoptionisavailablethatenables
theconfigurationofEIGRPforbothIPv4andIPv6underasingleconfigurationmode.
EIGRPnamedconfigurationhelpseliminateconfigurationcomplexitythatoccurswhen
configuringEIGRPforbothIPv4andIPv6.Forexample,enablinginterfacesforEIGRP
forIPv4isdoneinEIGRProuterconfigurationmode.However,inEIGRPforIPv6,
interfacesareenabledonthespecificinterface.Thisdiscrepancyleadstoconfusion,and
itisthisreasonthatEIGRPnamedconfigurationtriestounifyEIGRPconfigurationand
simplify configurationtasks,reducingthechancesofconfigurationmistakes.
EIGRPnamedconfigurationisavailableinCiscoIOSRelease15.0(1)Mandlaterreleases.
Named EIGRP Configuration 137
Configuring Named EIGRP

Figure221showsthetopologyusedinthissectionforconfiguringnamedEIGRP.
NoticethattheallthreeroutershavebeenconfiguredwithbothIPv4andIPv6address
es.BasicEIGRPforIPv4andIPv6hasalsobeenconfiguredonHQ,BR1,andBR2.
Lo0 192.168.1.0/24
BR1 2001:DB8:0:1::/64
WAN
10.0.0.0/24 Lo0
2001:DB8:0:0::/64 HQ
WAN
Lo0 192.168.2.0/24
2001:DB8:0:2::/64
192.168.3.0/24
BR2
Lo1 2001:DB8:0:3::/64
Figure 2-21 Named EIGRP Topology
Toverify completeIPv4andIPv6connectivityinthetopology,pingsaresentfromBR2
toBR1,asshowninExample281.
Example 2-81 Verifying IPv4 and IPv6 Connectivity

BR2# ping 192.168.1.1 source Loopback0
Packet sent with a source address of 192.168.2.1
!!!!!
BR2# ping 2001:DB8:0:1::1 source Loopback0
Sending 5, 100-byte ICMP Echos to 2001:DB8:0:1::1, timeout is 2 seconds:
Packet sent with a source address of 2001:DB8:0:2::1
!!!!!
BecauseallthreeroutersinthetopologyarepreconfiguredwithEIGRPforIPv4and
IPv6,connectivitytestsshouldbesuccessful.
The existingEIGRPconfigurationonBR2isshowninExample282.
Example 2-82 Current EIGRP for IPv4 and IPv6 Configuration
BR2# show running-config

<Output omitted>
interface Loopback0
ip address 192.168.2.1 255.255.255.0
ipv6 address 2001:DB8:0:2::1/64
ipv6 enable
ipv6 eigrp 1
!
interface Loopback1
ip address 192.168.3.1 255.255.255.0
ipv6 address 2001:DB8:0:3::1/64
ipv6 enable
ipv6 eigrp 1
!
interface Ethernet0/0
ip address 172.16.1.6 255.255.255.252
ipv6 address 2001:DB8:0:101::2/64
ipv6 enable
ipv6 eigrp 1
<Output omitted>
router eigrp 1
network 0.0.0.0
<Output omitted>
ipv6 router eigrp 1
<Output omitted>
NoticethatEIGRPisconfiguredwithanautonomoussystemof1forbothIPv4andIPv6.
Allpresent IPv4configurationisgatheredunderrouterconfiguration mode,andIPv6
EIGRPconfigurationispresentinrouterconfigurationmodeandwitheachinterface.
BeforeconfiguringnamedEIGRPforIPv4andIPv6onBR2,thebasicEIGRPconfigura
tionsareremoved,asshowninExample283.
Example 2-83 Removing EIGRP for IPv4 and IPv6 Configuration on BR2
BR2(config)# no router eigrp 1
BR2(config)# no ipv6 router eigrp 1
BR2(config)#
*Dec 27 09:50:05.585: %DUAL-5-NBRCHANGE: EIGRP-IPv6 1: Neighbor
FE80::A8BB:CCFF:FE00:3310 (Ethernet0/0) is down: procinfo free
BR2(config)# interface Ethernet0/0
BR2(config-if)# no ipv6 eigrp 1
BR2(config-if)# interface Loopback0

BR2(config-if)# interface Loopback1
BasicEIGRPmustberemovedfrominterfaceconfigurationmodeforIPv4andfrom
globalconfigurationmodefrombothIPv4andIPv6.
Address Families
ClassicorbasicEIGRPusestheglobalconfigurationcommandroutereigrpas-number
forIPv4andipv6routereigrpas-number forIPv6.Inbothcases,theautonomoussys
tem numberisusedtoidentifytheindividualEIGRPprocess.
EIGRPnamedconfigurationmodeusestheglobalconfigurationcommandroutereigrp
virtual-instance-name.BothEIGRPforIPv4andIPv6canbeconfiguredwithinthis
samemode.
EIGRPsupportsmultipleprotocolsandcancarryinformationaboutmanydifferent
routetypes.NamedEIGRPconfigurationisorganizedinahierarchical manner,where
configurationforspecificroutetypeisgroupedunderthesameaddressfamily.
IPv4unicastandIPv6unicastaretwoofthemostcommonlyusedaddressfamilies.
EIGRP for IPv4 Address Family

UsingthesametopologyinFigure221,Example284showstheconfigurationofBR2s
namedEIGRPvirtualinstancecalledLAB.NamedEIGRPisconfiguredinglobalcon
figurationmodeusingtheroutereigrpcommandfollowedbythenameoftheEIGRP
virtualinstance.Thenamehaslocalsignificanceanddoesnotneedtomatchbetween
neighboringrouters.Theroutereigrpvirtual-instance-name commanddefinesasingle
EIGRPinstancethatcanbeusedforalladdressfamilies.Atthispoint,theroutingproto
colisnotyetenabled.Atleastoneaddressfamilymustbedefinedfirst.
Example284showsBR2enteringtheIPv4addressfamilyconfigurationmodeusingthe
existingautonomoussystemnumber1.Theautonomoussystemnumbermustbethe
samein allroutersintheEIGRProutingdomain.
Example 2-84 IPv4 Address Family Added to the EIGRP Named Configuration on BR2
BR2(config)# router eigrp LAB

BR2(config-router)# address-family ipv4 autonomous-system 1
BR2(config-router-af)#
TheEIGRPipv4addressfamilycommandisconfiguredinEIGRPnamemodeusingthe
syntaxandtheparametersinTable24:
address-family ipv4 [multicast] [unicast] [vrf vrf-name] autonomous-system

autonomous-system-number
Table 2-4 Parameters for the EIGRP addressfamilyipv4Command

ipv4 SelectstheIPV4protocoladdressfamily.
multicast (Optional)Specifiesthemulticastaddressfamily.Thiskeywordis
availableonlyinEIGRPnamedIPv4configurations.

unicast (Optional)Specifiestheunicastaddressfamily.Thisisthedefault.
vrf vrf-name (Optional)SpecifiesthenameoftheVRF.

autonomoussystem Specifiestheautonomoussystemnumber.
autonomous-system-
number
The addressfamilycommandenablestheIPv4addressfamilyandstartsEIGRPforthe
definedautonomoussystem.Thecommandputsyouintheaddressfamilyconfiguration
mode,whichisalsoreflectedbythechangeoftheprompt.
InIPv4addressfamilyconfigurationmode,youcanenableEIGRPforspecificinterfaces
byusingthenetworkcommand,andyoucandefinesomeothergeneralparameterssuch
asrouteridoreigrpstub.
Unlessspecifiedotherwise,addressfamilyisbydefaultdefinedasunicastaddressfam
ily.Unicastaddressfamiliesareusedforexchangeofunicastroutes.
Note TheEIGRPaddressfamilycommandisalsoavailableunderclassicorbasicEIGRP
forbothIPv4andIPv6.ConfigurationissimilartonamedEIGRP.

Next,inaddressfamilyconfigurationmode,EIGRPisenabledonBR2allIPv4inter
faces,asshowninExample285.
Example 2-85 Enabling All Interfaces in IPv4 Address Family Configuration Mode
BR2(config-router-af)# network 0.0.0.0

YoucanenableEIGRPforIPv4oninterfacesinnamedconfigurationwiththenetwork
command,thesamewayaswithnormalEIGRPconfiguration.Youcanbe specificand
useawildcardmasktoselectonlyindividualinterfaces,oryoucanuse0.0.0.0,which
enablesEIGRPonallIPv4enabledinterfaces.
Toverify thenamedconfigurationofEIGRPforIPv4,EIGRPneighbors,theEIGRP
topologytable,andtheroutingtableforEIGRProutesareverifiedonBR2,asshownin
Example286.

Example 2-86 Verifying Named Configuration of EIGRP for IPv4 BR2
BR2# show ip eigrp neighbors

EIGRP-IPv4 VR(LAB) Address-Family Neighbors for AS(1)
(sec) (ms) Cnt Num

0 172.16.1.5 Et0/0 14 00:21:56 10 100 0 12
BR2# show ip eigrp topology

EIGRP-IPv4 VR(LAB) Topology Table for AS(1)/ID(192.168.3.1)

via 172.16.1.5 (458752000/327761920), Ethernet0/0
via 172.16.1.5 (524288000/458752000), Ethernet0/0
via 172.16.1.5 (196608000/131072000), Ethernet0/0
BR2# show ip route eigrp


D 10.0.0.0 [90/3584000] via 172.16.1.5, 00:36:57, Ethernet0/0
172.16.1.1 /16 is variably subnetted, 3 subnets, 2 masks
D 172.16.1.0/30 [90/1536000] via 172.16.1.5, 00:36:57, Ethernet0/0
D 192.168.1.0/24 [90/4096000] via 172.16.1.5, 00:36:57, Ethernet0/0

EventhoughyouhaveconfiguredEIGRPinnamedconfigurationmode,howEIGRP
operatesandinteractswithneighborsdoesnotreallychange.Youcanusethesame veri
ficationcommandstoanalyzeandverifyEIGRPstatus.
Individual interfacescanbeconfiguredorremovedfromtheEIGRPforIPv4andIPv6
process using the afinterface interface-type interface number command in address
familyconfigurationmode.ThiscommandisusedtoconfigureEIGRPparameterson
theinterfacessuchasmanualsummarizationandauthentication.Anexampleofthis
commandis discussedinthenext,usingtheEIGRPforIPv6addressfamily.
EIGRP for IPv6 Address Family

Example287showstheIPv6addressfamilyforautonomoussystem1addedtothe
EIGRPnamedconfigurationonBR2.
Example 2-87 IPv6 Address Family Added to the Named EIGRP Configuration on BR2

FE80::A8BB:CCFF:FE00:3310 (Ethernet0/0) is up: new adjacency
The EIGRPaddressfamilyipv6commandisconfiguredinrouterconfigurationmode
usingthesyntaxandtheparametersinTable25:
address-family ipv6 [unicast] [vrf vrf-name] autonomous-system autonomous-system-

number
Table 2-5 Parameters for the EIGRP addressfamilyipv6Command

Ipv6 SelectstheIPv6protocoladdressfamily.
unicast (Optional)Specifiestheunicastaddressfamily.
Thisisthedefault.
vrf vrf-name (Optional)SpecifiesthenameoftheVRF.
autonomoussystem Specifiestheautonomoussystemnumber.
autonomous-systemnumber
WhendefiningtheIPv6addressfamily,itisimportanttousethecorrectautonomous
systemnumber.AllthreeroutersinthetopologywereconfiguredwithIPv6autono
moussystem1inthebeginning,soitisnecessarythatyouusethesameautonomous
systemifyoudonotwanttoreconfigureHQandBR1aswell.Keepinmindthatthere
isnorequirementforanautonomoussystemnumbertomatchbetween IPv4andIPv6
addressfamilies;itmustonlymatchbetweenneighborswithinthesameaddressfamily.
Note TheEIGRPautonomoussystemnumbersfortheIPv4andIPv6addressfamilies
donothavetobethesame.Theonlyrequirementisthatthesameautonomoussystem
numberforIPv4andthesameautonomoussystemnumberforIPv6beusedby all routers
inthesameEIGRProutingdomain.

NoticehowanIPv6EIGRPneighborrelationshipgetsestablishedassoonasyoudefine
theIPv6addressfamily.EIGRPforIPv6doesnotneedtobeenabledontheinterface.
All IPv6enabledinterfacesareautomaticallyincludedintheEIGRPforIPv6process.
TheIPv6addressfamilyconfigurationwillshowupintherunningconfigurationasauni
cast addressfamilybydefault.
YoucanconfigureorremoveindividualinterfacesfromtheEIGRPforIPv6processby
using the afinterface interface-type interface number command in address family con
figurationmode,asdescribedinTable26:
af-interface {default | interface-type interface number}
Table 2-6 Parameters for the afinterfaceAddress Family Configuration Mode Command
default Specifiesthedefaultaddressfamilyinterfaceconfigura
tionmode.Commandsappliedunderthismodeaffectall
interfacesusedbythisaddressfamilyinstance.
interface-type interface number Interfacetypeandnumberoftheinterfacethatthe
addressfamilysubmodecommands willaffect.

UsinganinterfacenotactuallyonBR2,Ethernet0/1(sowedonotaffectourconfigu
ration),isshowninExample288.Theshutdowncommandisusedinaddressfamily
interfaceconfigurationmodetoremovethisinterfacefromEIGRPforIPv6,which was
includedbydefault.However,forallotherIPv6purposes,theinterfaceisstillintheup/
upstate.Theinterfacecanstillbepingedfromanotherdeviceonthenetwork.
TheafinterfacecommandisalsousedtoconfigureotherspecificEIGRPinterface
optionssuchasauthentication,bandwidthpercent,andmanualsummarization.Acom
pletelistingoftheseoptionsisshownlaterinthischapter,inExample295.
Example 2-88 Disabling EIGRP for IPv6 on an Interface

BR2(config-router-af)# af-interface ethernet 0/1
BR2(config-router-af-interface)# shutdown
Example289verifiestheEIGRPneighbors,IPv6EIGRPtopologytable,andIPv6rout
ingtableforEIGRProutesonBR2.ThesamecommandsareusedtoverifyEIGRPfor
IPv6inbasicandnamedconfigurationmodes.
Example 2-89 Verifying EIGRP for IPv6 on BR2
BR2# show ipv6 eigrp neighbors

EIGRP-IPv6 VR(LAB) Address-Family Neighbors for AS(1)
(sec) (ms) Cnt Num
0 Link-local address: Et0/0 10 02:03:36 1594 5000 0 11
FE80::A8BB:CCFF:FE00:3310
BR2# show ipv6 eigrp topology

EIGRP-IPv6 VR(LAB) Topology Table for AS(1)/ID(192.168.3.1)

P 2001:DB8::/64, 1 successors, FD is 458752000
via FE80::A8BB:CCFF:FE00:3310 (458752000/327761920), Ethernet0/0

B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP
H - NHRP, I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
IS - ISIS summary, D - EIGRP, EX - EIGRP external, NM - NEMO
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP
D 2001:DB8::/64 [90/3584000]
via FE80::A8BB:CCFF:FE00:3310, Ethernet0/0
D 2001:DB8:0:1::/64 [90/4096000]
D 2001:DB8:0:100::/64 [90/1536000]
Example290showstherunningconfiguration,whichillustratesthestructureofnamed
EIGRPonBR2.
Example 2-90 Displaying BR2s Running Configuration
BR2# show running configuration | section router eigrp

router eigrp LAB
!
address-family ipv4 unicast autonomous-system 1
!
topology base
exit-af-topology
network 0.0.0.0
exit-address-family
!
!
topology base
exit-af-topology
exit-address-family
Noticethattheconfigurationisstructuredaroundaddressfamiliesinahierarchical
format.Configurationisalsounifiedamongaddressfamilies,meaningthatadditional
parameterssuchasauthenticationandsummarizationareconfiguredinthesamemanner.
TheTopologyBasesectionoftheconfigurationreferstothetopologybase configura
tionmode.WithinthetopologybaseiswheregeneralEIGRPsettingsareconfigured
thatrelatetothetopologytable.Forexample,youcandefinevarianceandmaximum
pathsparametersforloadbalancingorredistributeroutesfromotherroutingsources
withinthetopologybase.Thisisdiscussedlaterinthischapter,inExample297.
Example291showshowmanualsummarizationisconfiguredinnamedEIGRPconfigu
rationmode.WithintheEIGRPIPv4addressfamily,theaddressfamilyinterfacecon
figurationmodeisentered,andBR2sloopbackprefixesaresummarized.
Example 2-91 EIGRP Summarization in Named Configuration Mode

BR2(config-router-af-interface)# summary-address 192.168.2.0/23
BR2(config-router-af-interface)#
172.16.1.5 (Ethernet0/0) is resync: summary configured
Toentertheaddressfamilyinterfaceconfigurationmode,usetheafinterfacecom
mand.AllinterfacespecificEIGRPcommandsareconfiguredwithintheaddressfamily
interfaceconfigurationmode.Summarization,helloanddeadtimers,andpassiveinter
facesettingsareafewexamplesofavailableoptions.
WhenintheIPv4addressfamilyinterfaceconfigurationmode,you cansummarizeIPv4
prefixesusingthesummaryaddresscommand.Youcanspecifysubnetmaskeitherin
decimalformatorprefixlengthformat,asshownintheexample.
The summaryrouteisverifiedbyexaminingtheroutingtableonBR1,asshownin
Example292.
Example 2-92 Displaying BR1s Routing Table with the Summary Route
BR1# show ip route

D 10.0.0.0 [90/409600] via 172.16.1.1, 3d05h, Ethernet0/0
D 172.16.1.4/30 [90/307200] via 172.16.1.1, 3d05h, Ethernet0/0
D 192.168.2.0/23 [90/307200] via 172.16.1.1, 00:34:21, Ethernet0/0
NoticeBR1nowreceivesonlysummarizedroutedescribingbothloopbackson BR2.
Example293showsallofBR2sIPv6interfacesconfiguredaspassiveexceptfor
Ethernet 0/0.
Example 2-93 Configuring All IPv6 Interfaces as Passive Except for Ethernet 0/0

BR2(config-router-af)# af-interface default
BR2(config-router-af-interface)# passive-interface

FE80::A8BB:CCFF: FE00:F010 (Ethernet0/0) is down: interface passive
BR2(config-router-af-interface)# exit
BR2(config-router-af)# af-interface ethernet0/0
BR2(config-router-af-interface)# no passive-interface
*Dec 31 08:42:57.111: % DUAL-5-NBRCHANGE: EIGRP-IPv6 1: Neighbor

FE80::A8BB:CCFF: FE00:F010 (Ethernet0/0) is up: new adjacency

Theafinterfacedefaultcommandisusefulfordefininguserdefaultsto applytoEIGRP
interfacesthatbelongtoanaddressfamilywhenEIGRPisconfiguredusingthenamed
method.Forexample,authenticationmodeisdisabledbydefault,andyoucanenable
messagedigest5(MD5)authenticationforallEIGRPinterfacesintheaddress familyby
usingaddressfamilyinterfaceconfigurationmodeandthenselectivelyoverridingthe
newdefaultsettingusingdifferentaddressfamilyinterfaceconfigurationcommands.
The outputinExample293showshowusingthepassiveinterfacecommandappliesto
allinterfaces,includingEthernet0/0,thatconnectBR2totherestofthenetwork.
Toeditasingleinterface,enterafinterfaceconfigurationmodeandspecify theappro
priateinterface.OnceEthernet0/0interfaceisconfiguredwiththenopassiveinterface
command,EIGRPneighboradjacencygetsreestablished.
Usetheafinterfacedefaultcommandwithcautionbecausesomedefaultsettingscanbe
differentdependingontheinterfacetype.Forexample,thedefaulthello intervalis5sec
ondsformostinterfaces,butis60secondsforslowNBMAinterfaces,andchangingthe
hellointervalinaddressfamilyinterfaceconfigurationmodewillaffectall interfaces.
UsingtheshowipprotocolscommandinExample294,wecanverifywhichinterfaces
aremarkedaspassive.
Example 2-94 Verifying Passive Interfaces on BR2

BR2# show ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "ND"
IPv6 Routing Protocol is "eigrp 1"
EIGRP-IPv6 VR(lab) Address-Family Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 K6=0
Metric rib-scale 128
Metric version 64bit
Router-ID: 192.168.3.1
Topology : 0 (base)
Active Timer: 3 min
Maximum path: 16
Total Prefix Count: 6

Total Redist Count: 0
Interfaces:
Ethernet0/0
Loopback1 (passive)
Loopback0 (passive)
Redistribution:
None
Named EIGRP Configuration Modes

NamedEIGRPconfigurationmodegathersallEIGRPconfigurationsinoneplace.Ituses
threedifferentconfigurationmodestostructuredifferentconfigurationoptions.
Addressfamilyconfigurationmode:GeneralEIGRPconfigurationcommandsfor
selectedaddressfamilyareenteredunderaddressfamilyconfigurationmode.Here
youcanconfiguretherouterIDanddefinenetworkstatements,whicharerequired
forIPv4EIGRPconfiguration.Youcanalsoconfigurerouteras anEIGRPstub.
Addressfamilyconfigurationmodegivesyouaccesstotwoadditionalconfigura
tionmodes:addressfamilyinterfaceconfigurationmodeandaddressfamilytopol
ogyconfigurationmode.
Example295showsthecommandsonBR1availableinaddressfamilyinterface
configurationmode:Youshoulduseaddressfamilyinterfaceconfigurationmode
forallthosecommandsthatyouhavepreviouslyconfigureddirectlyunderinter
faces.Mostcommonoptionsaresettingsummarizationwiththesummaryaddress
commandormarkinginterfacesaspassiveusingpassiveinterfacecommand.You
canalsomodifydefaulthelloandholdtimetimers.
Example296showsthecommandsonBR1availableinaddressfamilyinterface
configurationmode.
Addressfamilytopologyconfigurationmode:Addressfamilytopologyconfigura
tionmodegathersallconfigurationoptionsthatdirectlyimpactthe EIGRPtopology
table.Hereyoucansetloadbalancingparameterssuchasvarianceandmaximum
paths, oryoucanredistributestaticroutesusingtheredistributecommand.
Example297showsthecommandsonBR1availableinaddressfamilytopology
configurationmode.
Example 2-95 Address Family Configuration Mode

BR1(config-router)# address-family ipv6 unicast autonomous-system 1
BR1(config-router-af)# ?
Address Family configuration commands:
af-interface Enter Address Family interface configuration

default Set a command to its defaults
eigrp EIGRP Address Family specific commands
exit-address-family Exit Address Family configuration mode
help Description of the interactive help system
maximum-prefix Maximum number of prefixes acceptable in aggregate
metric Modify metrics and parameters for address advertisement
neighbor Specify an IPv6 neighbor router
no Negate a command or set its defaults
shutdown Shutdown address family
timers Adjust peering based timers
topology Topology configuration mode
Example 2-96 Address Family Interface Configuration Mode

BR1(config-router-af-interface)# ?
Address Family Interfaces configuration commands:
authentication authentication subcommands
bandwidth-percent Set percentage of bandwidth percentage limit
bfd Enable Bidirectional Forwarding Detection
dampening-change Percent interface metric must change to cause update
dampening-interval Time in seconds to check interface metrics
exit-af-interface Exit from Address Family Interface configuration mode
hello-interval Configures hello interval
hold-time Configures hold time
next-hop-self Configures EIGRP next-hop-self
passive-interface Suppress address updates on an interface
shutdown Disable Address-Family on interface
split-horizon Perform split horizon
summary-address Perform address summarization
BR1(config-router-af-interface)#
Example 2-97 Address Family Topology Configuration Mode

BR1(config-router-af)# topology base
Summary 151
BR1(config-router-af-topology)# ?
Address Family Topology configuration commands:
default-information Control distribution of default information
default-metric Set metric of redistributed routes
distance Define an administrative distance
distribute-list Filter entries in eigrp updates
eigrp EIGRP specific commands
exit-af-topology Exit from Address Family Topology configuration mode
maximum-paths Forward packets over multiple paths
metric Modify metrics and parameters for advertisement
redistribute Redistribute IPv6 prefixes from another routing protocol
summary-metric Specify summary to apply metric/filtering
timers Adjust topology specific timers
traffic-share How to compute traffic share over alternate paths
variance Control load balancing variance
BR1(config-router-af-topology)#
Classic Versus Named EIGRP Configuration

The easiestwaytocompareclassicEIGRPconfigurationtonamedEIGRPconfiguration
modeistoshowconfigurationexamplessidebyside.
AsyoucanseeinExample298,namedEIGRPputsallconfigurations inoneplace.IPv4
andIPv6EIGRPconfigurationcommandsarestructuredwithincorrespondingaddress
families.AllcommandspreviouslyconfiguredunderinterfacesarenowsetwithinEIGRP
addressfamilyinterfaceconfigurationmode.Notonlyisconfigurationeasier,clear hier
archicalstructurealsosimplifiesanalysisandtroubleshootingprocess.
Example 2-98 Classic Versus Named EIGRP Configuration
interface Loopback1
ip address 192.168.3.1 255.255.255.0
ipv6 address 2001:DB8:0:3::1/64
ipv6 eigrp 1
!
interface Ethernet0/0
ip address 172.16.1.6 255.255.255.252
ip summary-address eigrp 1 192.168.2.0 255.255.254.0
ipv6 address 2001:DB8:0:101::2/64
ipv6 eigrp 1
!
router eigrp 1
network 0.0.0.0
passive-interface default
no passive-interface Ethernet0/0
!
ipv6 router eigrp 1
!
router eigrp LAB
!
!
af-interface default
passive-interface
exit-af-interface
!
af-interface Ethernet0/0
summary address 192.168.2.0/23
no passive-interface
exit-af-interface
!
topology base
exit-af-topology
network 0.0.0.0
exit-address-family
!
!
topology base
exit-af-topology
exit-address-family
Summary
Inthischapter,youlearnedaboutestablishingEIGPRneighborrelationships,building
theEIGRPtopologytable,optimizingEIGRPbehavior,configuringEIGRPforIPv6, and
implementingnameEIGRPconfiguration.Keypointsinthischapterincludethefollowing:
EIGRPisanadvanceddistancevectorprotocol.
EIGRPusesRTPforreliable,guaranteeddeliveryofpackets.
Helloandholdtimerscanbeadaptedtoinfluencenetworkconvergence.
EIGRPadaptswelltovarioustechnologiessuchasFrameRelay,Layer3MPLS
VPN,andLayer2MPLSVPN.
EIGRP useshello,update,query,reply,andacknowledgmentpackets.
EIGRPusesacompositemetricthatisbydefaultbasedonbandwidthanddelay.
Reporteddistanceisthemetricvaluereportedbytheneighboringrouter.

Feasibledistanceisthelowestdistancetoadestinationfromtheperspectiveofthe
localrouter.
Alternativepathmustsatisfythefeasibilityconditiontobecomeafeasiblesuccessor.
Thereporteddistanceofanalternatepathmustbelessthanthefeasibledistance.
Whenarouteislostandnofeasiblesuccessorisavailable,queriesaresenttoall
neighboringroutersonallinterfaces.
EIGRPstubconfigurationimprovesnetworkstabilityandreducesresourceutilization.
SummarizationdecreasesthesizeoftheIProutingtableandoptimizesexchangeof
routing information.
EIGRPperformsequalcostloadbalancing.
Tosupportunequalcostloadbalancing,avarianceparametermustbeconfigured.
EIGRPforIPv6usesIPv6linklocaladdressestoformneighborrelationships.
EIGRPforIPv6supportsonlymanualprefixsummarization.
ToconfigureEIGRPforIPv6,youmustdefinetheroutingprocessandconfigure
interfacesparticipatinginEIGRProuting.
EIGRPforIPv6verificationcommandshavesimilarsyntaxtoEIGRPforIPv4
commands.
ClassicEIGRPconfigurationisdividedoverdifferentconfigurationmodes.
NamedEIGRPconfigurationgathersEIGRPconfigurationinone place.
NamedEIGRPconfigurationunifiesconfigurationcommandsfordifferentaddress
families.
NamedEIGRPconfigurationishierarchicallyorganizedusingthreeaddressfamily
configurationmodes.
ThesameverificationcommandsforclassicEIGRPareusedtoverifynamedEIGRP
configuration.
Review Questions
Answerthefollowingquestions,andthenseeAppendixA,AnswerstoReview
Questions,fortheanswers.
1. WhichtransportlayerprotocolisusedforexchangeofEIGRPmessages?
a. TCP
b. UDP
c. RSVP
d. RTP
e. EIGRPrunsdirectlyabovethenetworklayeranddoesnotuseadditional
transportprotocols.
Review Questions 153
2. Whichpackettypeestablishesneighborrelationships?
a. Ack
b. Hello
c. Query
d. Reply
e. Update
3. Whatis usedinEIGRPmetriccalculationsbydefault?(Choosetwo.)
a. Bandwidth
b. MTU
c. Reliability
d. Load
e. Delay
f. Hopcount
4. Whatistheformulaforselectingafeasiblesuccessor?
a. TheADofthecurrentsuccessorrouteislessthantheFDofthefeasiblesucces
sorroute.
b. TheFDofthecurrentsuccessorrouteislessthantheADofthefeasiblesucces
sorroute.
c. TheFDofthefeasiblesuccessorrouteislessthantheADofthecurrentsucces
sorroute.
d. TheADofthefeasiblesuccessorrouteislessthantheFDofthecurrentsucces
sorroute.
5. WhatdoesthepassivestateintheEIGRPtopologytablesignify?
a. Thereareoutstandingqueriesforthisnetwork.
b. Thenetworkisunreachable.
c. Thenetworkisupandoperational,andthisstatesigniesnormalconditions.
d. Afeasiblesuccessorhasbeenselected.
6. EIGRPforIPv6useswhichmulticastaddress?
a. FF01::2
b. FF01::10
c. FF02::5
d. FF02::A
e. EIGRPforIPv6doesnotusemulticastaddressing
7. WhichverificationcommandshowsyouadvertiseddistanceofreceivedEIGRP
IPv6routes?
a. showipv6route
b. showipv6routeeigrp
c. showipv6eigrp
d. showipeigrpneighbors
e. showipv6eigrptopology
f. showipprotocols
8. Whatare twobenefitsofusingnamedEIGRPconfiguration?
a. Improved scalability
b. Fasterconvergence
c. UnifyingIPv4andIPv6congurationcommands
d. Supportformultipleareas
e. GatheringallEIGRPcongurationinonceplace
9. IsEIGRPoperationaltrafficmulticastorbroadcast?
10. WhatarethefourkeytechnologiesemployedbyEIGRP?
11. WhichofthefollowingbestdescribestheEIGRPtopologytable?
a. Itispopulatedasaresultofreceivinghellopackets.
b. Itcontainsalllearnedroutestoadestination.
c. Itcontainsonlythebestroutestoadestination.
12. DescribethefivetypesofEIGRPpackets.
13. HowoftenareEIGRPhellopacketssentonLANlinks?
14. Whatisthedifferencebetweentheholdtimeandthehellointerval?
15. Whichof thefollowingstatementsaretrue?(Choosethree.)
a. Arouteisconsideredpassivewhentherouterisnotperformingrecomputation on
thatroute.
b. Arouteispassivewhenitisundergoingrecomputation.
c. Arouteisactivewhenitisundergoingrecomputation.
d. Arouteisconsideredactivewhentherouterisnotperformingrecomputationon
thatroute.
e. Passiveistheoperationalstateforaroute.
f. Activeistheoperationalstateforaroute.
16. Whichofthefollowingstatementsaretrueaboutreporteddistance(RD)andfea
sibledistance(FD)?(Choosetwo.)
a. TheRDistheEIGRPmetricforaneighborroutertoreachaparticularnetwork.
b. TheRDistheEIGRPmetricforthisroutertoreachaparticularnetwork.
c. TheFDistheEIGRPmetricforthisroutertoreachaparticularnetwork.
d. TheFDistheEIGRPmetricfortheneighborroutertoreachaparticularnet
work.
17. Router AhasthreeinterfaceswithIPaddresses172.16.1.1/24,172.16.2.3/24,
and172.16.5.1/24.WhatcommandsenableyoutoconfigureEIGRPtorunin
autonomoussystem100ononlytheinterfaceswithaddresses172.16.2.3/24and
172.16.5.1/24?
18. WhatdoesthepassiveinterfacecommanddowhenconfiguredwithEIGRP?
19. HowdoestheEIGRPstubfeaturelimitthequeryrange?
20. Whatdoestheeigrpstubreceiveonlycommanddo?

EIGRP CCNP Route

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

EIGRP CCNP Route

Transféré par

Droits d'auteur :

Formats disponibles

59 Chapter 1: Basic Network and Routing Concepts

60 Chapter 2: EIGRP Implementation

Establishing EIGRP Neighbor Relationships

Establishing EIGRP Neighbor Relationships 61

62 Chapter 2: EIGRP Implementation

Note ThetermIP isusedforgenericIPandappliestobothIPv4andIPv6.Otherwise,

Note Althoughthereissomereview,thischapterassumesthereader hasbasicCCNA

Figure 2-1 EIGRP Encapsulation

Establishing EIGRP Neighbor Relationships 63

EIGRP Operation Overview

Figure 2-2 EIGRP Operation Overview

64 Chapter 2: EIGRP Implementation

Configuring and Verifying Basic EIGRP for IPv4

Figure 2-3 Basic EIGRP Topology

Establishing EIGRP Neighbor Relationships 65

Example 2-1 Configuration of EIGRP on BR1

66 Chapter 2: EIGRP Implementation

Example 2-2 Configuration of EIGRP on BR2

BR2(config)# router eigrp 100

Example 2-3 Configuration of EIGRP on BR3

BR3(config)# router eigrp 100

Example 2-4 Verifying EIGRP Neighbor Relationships on BR1

BR1# show ip eigrp neighbors

BR1# show ip eigrp neighbors detail

Establishing EIGRP Neighbor Relationships 67

H Address Interface Hold Uptime SRTT RTO Q Seq

Example 2-5 Verifying the EIGRP Interfaces on BR1

BR1# show ip eigrp interfaces

68 Chapter 2: EIGRP Implementation

Example 2-6 Verifying the EIGRP Interfaces Details on BR1

BR1# show ip eigrp interfaces detail

Example 2-7 Verifying the EIGRP Networks on HQ

HQ# show ip protocols

Routing Protocol is "eigrp 100"

Establishing EIGRP Neighbor Relationships 69

Example 2-8 Verifying the EIGRP Interfaces Details on HQ

Example 2-9 Configuring Passive Interfaces as the Default

Example 2-10 Disabling Passive Interfaces on HQ

Establishing EIGRP Neighbor Relationships 71

Example 2-11 Verifying the Passive Interface on HQ

HQ# show ip protocols

Example 2-12 Observing EIGRP Hello Packets on BR1

BR1# debug eigrp packets hello

70 Chapter 2: EIGRP Implementation

*Sep 24 04:19:55.264: EIGRP: Received HELLO on Serial0/0 nbr 172.16.1.1

HQ# show ip eigrp interfaces detail

Example 2-14 Observing EIGRP Hello Packets When an Interface Is Disabled

BR1# debug eigrp packets hello

Establishing EIGRP Neighbor Relationships 73

Manipulating EIGRP Timers

BR3(config)# interface serial 0/0

Hello-interval is 10, Hold-time is 30

74 Chapter 2: EIGRP Implementation

EIGRP Neighbor Relationship over Frame Relay

Note FormoreinformationaboutconfiguringFrameRelay,seeConnecting Networks

Establishing EIGRP over Layer 3 MPLS VPN

Establishing EIGRP Neighbor Relationships 75

Layer 3 MPLS VPN Backbone

Establishing EIGRP over Layer 2 MPLS VPN

76 Chapter 2: EIGRP Implementation

Building the EIGRP Topology Table

Building the EIGRP Topology Table 77

Building and Examining the EIGRP Topology Table