Advanced Routing EIGRP

EIGRP Objectives
Describe the key capabilities that distinguish EIGRP from other routing protocols Identify the four key technologies employed by EIGRP Describe how EIGRP operates Describe the five components of the metric used by EIGRP Calculate the EIGRP metric for a range of pathways between routers Explain how IGRP routes are integrated into EIGRP routes and vice-versa Describe the commands used in a basic EIGRP configuration task Verify EIGRP operation Describe and configure MD5 router authentication Explain how to mark the spokes of large network as stubs to reduce EIGRP queries and thus improve network scaling Explain how to minimise active routes Describe how graceful shut down prevents loss of packets when routers go down

Routing Protocols
In the first lecture we said that there two kinds of routing protocol Distance Vector Link State To add to this list EIGRP is a hybrid protocol Taking features from both Distance Vector and Link State EIGRP is designed to improve upon the scaling limits of IGRP IGRP only operates as distance vector protocol EIGRP is backwardly compatible with IGRP if that is still used in a company the routing tables will converge EIGRP is proprietary to Cisco

EIGRP Features
EIGRP is an advanced distance vector routing protocol but also acts as a link-state protocol in the way that it updates neighbors and maintains routing information. The following are advantages of EIGRP over simple distance vector protocols: Rapid convergence Efficient use of bandwidth Uses both Unicast and Multicast (224.0.0.10) communications Support for VLSM and CIDR Multiple network layer support Independence from routed protocols IPv4, IPv6, IPX appletalk Routing update Authentication

EIGRP Features
Neighbor discovery and recovery Reliable Transport Protocol ( RTP ) DUAL finite-state machine algorithm Protocol-dependent modules ( PDM )

Reliable
Reliable in terms of what we want simply indicates that data is acknowledged using Reliable Transport Protocol ( RTP )
This is not the Real-Time Protocol used in the IPTelephony course RTP in this case will provide a sequence number and to inform if an acknowledgement is required As an example update packets require an acknowledgement but hello packets do not This gives the reliability of TCP without all of the overhead that is involved with that protocol Acknowledgment do not need to be sent as an independent packet if other traffic is being sent to that router the ack will be sent with the other data In the IP stack all EIGRP data marks the protocol as 88, TCP is 6 (http://tools.ietf.org/html/rfc790)

Default Hello Intervals and Hold Times for EIGRP

Before any exchange of data can take place routers need to know the neighbours To do this a hello is sent out on 224.0.0.10 In addition this is also used as a part of the reliable transport, knowing how many acknowledgements should be received Hello?
R1
S0/0/0 S0/0/0

Hello?
R2

Hellos at a fixed (default 5 seconds), but is configurable with the hello interval. The default hello interval depends on the bandwidth of the interface. Default hold time = 3 x hello interval after this the router is declared as dead

Establishing Adjacencies with Neighbors

An EIGRP router assumes that, as long as it is receiving hello packets from known neighbors, those neighbors (and their routes) remain viable. Hold time tells the router how long it should consider the neighbor alive if it has not received any EIGRP packets (Hello, EIGRP updates, etc.). EIGRP routers exchange routing information the same way as other distance vector routing protocols, but do not send periodic updates. EIGRP updates are only sent when a network is added or removed from the topology database, when the successor for a given network changes, or when the locally used metric is updated. EIGRP, like any other distance-vector routing protocol uses splithorizon.

Split Horizon
Split Horizon
The concept of this is to prevent a route from being advertised back on the interface that it was learnt C learns about B via A If the link between And B is removed C still has an entry for router B so A would send the traffic to C At which point it would be returned to router A Split horizon prevents this as router C will not update A about router B as it was learnt through router A

Router A

Router C

Router B

Partial Bounded Updates

Unlike RIP, EIGRP does not send periodic updates. Instead, EIGRP sends its updates only when the metric for a route changes. Instead of sending the entire contents of the routing table, EIGRP sends only information about the route change partial updates. The partial update is automatically "bounded" so that only those routers that need the information are updated. Those within the same Automoonous Systems number By sending only the routing information that is needed and only to those routers that need it, EIGRP minimises the bandwidth required to send EIGRP packets.

EIGRP Terms
Successor Route
This is a router which has the best path to a particular network This is a backup route to the particular network This is the distance which is advertised by the adjacent router to the location A to C would be 15 This is the total metric from your router to the destination network A to C would be 35 All other routes which can not be used and are simply stored

Feasible Successor Route Advertised Distance Feasible Distance

Possibility route

show ip eigrp topology all-links

20 B

15 C

The Diffusing Update Algorithm (DUAL)

The feasibility condition (FC) is met when a neighbor's reported distance (RD) to a network (192.168.10.0/24) is less than the local router's feasible distance to the same destination network. Router R2 R3 R4 RD/AD FD

10 10 30

20 25 45

10 15

R2

10 10

FC = RD<FD R5
192.168.10.0/24

R1

R3

15

R4

30

Successor = R2 (FD=20) Feasible Successor = R3 (10<20)

The Diffusing Update Algorithm (DUAL)

If the Successor route fails, R1 will immediately enter the feasible successor into the routing table. R1 will update its neighbours about the topology change. Router R2 R3 R4 RD/AD FD

10 10 30

20 25 45

Update

R2
ACK

10 10

R1
Update

15

FC = RD<FD R5
192.168.10.0/24

R3

15

ACK

R4

30

Successor = R3 (FD=25) No Feasible Successor = R3 (30>25)

The Diffusing Update Algorithm (DUAL)

If the new successor route fails, R1 no longer has a feasible successor, so it enters the Active state. R1 will now query its neighbours for a route to network 192.168.10.0/24. Router R2 R3 R4 RD/AD FD

10 10 30

20 25 45

R2 15

10

FC = RD<FD R3 30 R5
192.168.10.0/24

R1
Query

15

Successor = R4 (FD=45) No Feasible Successor

Reply

R4

Packet Types
The five EIGRP packet types are as follows: 1. Hello - used to discover, verify, and rediscover neighbor routers. Multicast 224.0.0.10 2. Acknowledgment - Ack updates, queries and replies 3. Update send out routing updates 4. Query - try and discover new routes from other routers 5. Reply respond to a query

EIGRP Metrics
Metrics that can be used for EIGRP are
Bandwidth Lowest bandwidth between source and destination Delay Total delay along the path Reliability Worst reliability along the path based on lost keep alives Loading Worst load on a link between source and destination based on packet rate and the configured bandwidth of the link

EIGRP Routing Information

The result of
Show ip eigrp topology Hop count and Minimum MTU are stored but not used in the decision process

EIGRP Metric calculation

Metric = 256 *[K1 x Bandwidth+(K2 x Bandwidth)+(K3 x Delay)] x ( K5 )

(256 x Load)

(Reliability + K4)

Default constant values:- K1=1, K2=0, K3=1, K4=0, K5=0

Default settings indicate that only delay and bandwidth are used

Metric = [K1 x bandwidth (min) + K3 x delay (cumulative)] The default K values can be changed with the EIGRP router command: R2(config-router)# metric weights tos k1 k2 k3 k4 k5
Although the K values can be changed to routers will only exchange information if the K values are the SAME, which is a very good reason not to adjust the default values

EIGRP Metric calculation

The show ip protocols command is used to verify the K values. Notice that the K values on R1 are set to the default. Changing these values to other than the default is not recommended unless the network administrator has a very good reason to do so

EIGRP Metric calculation

Use the show interfaces command to view metrics Bandwidth EIGRP uses a static bandwidth to calculate metric.Most serial interfaces use a default bandwidth value of 1.544Mbps (T1)

Modifying the bandwidth value does not change the actual bandwidth of the link. If actual bandwidth of the link differs from the default bandwidth value, then the default should be changed to reflect the actual.

EIGRP Metric calculation

Delay is a measure of the time it takes for a packet to traverse a route. The delay (DLY) metric is a static value based on the type of link to which the interface is connected and is expressed in microseconds. Delay is not measured dynamically i.e. the router does not actually track how long packets are taking to reach the destination. The delay value, much like the bandwidth value, is a default value that can be changed by the network administrator.

Bandwidth Metric Calculation

172.16.2.0/24

ISP
172.16.3.0/24
S0/0/0 DCE .1

Loopback 10.1.1.1/30
S0/0/0 .2 64 kbps S0/0/1 .5

.1

R2

.9

S0/0/1 DCE

192.168.10.8/30
S0/0/1 .10 S0/0/0 DCE .6

Fa0/0

1024 kbps 1544 kbps

Fa0/0

172.16.1.0/24

.1

R1

192.168.10.4/30

R3

.1

192.168.1.0/24

Bandwidth = (10,000,000 / BW in kbps) x 256 R2 Slowest Interface = S0/0/1 link at 1024kbps 10,000,000 / 1024 = 9765.625 Round Down = 9765 9765 x 256 =2,499,840

Delay Metric Calculation

172.16.2.0/24

ISP
172.16.3.0/24
S0/0/0 DCE .1

Loopback 10.1.1.1/30
S0/0/0 .2 64 kbps S0/0/1 .5

.1

R2

.9

S0/0/1 DCE

192.168.10.8/30
S0/0/1 .10 S0/0/0 DCE .6

Fa0/0

1024 kbps 1544 kbps

Fa0/0

172.16.1.0/24

.1

R1

192.168.10.4/30

R3

.1

192.168.1.0/24

Delay = (Sum of delay / 10) x 256 Sum = 100 + 20,000 = 20,100uS Sum /10 = 20,100 / 10 = 2,010 23 2,010 x 256 = 514,560

Composite Metric Calculation

172.16.2.0/24

ISP
172.16.3.0/24
S0/0/0 DCE .1

Loopback 10.1.1.1/30
S0/0/0 .2 64 kbps S0/0/1 .5

.1

R2

.9

S0/0/1 DCE

192.168.10.8/30
S0/0/1 .10 S0/0/0 DCE .6

Fa0/0

1024 kbps 1544 kbps

Fa0/0

172.16.1.0/24

.1

R1

192.168.10.4/30

R3

.1

192.168.1.0/24

Metric = [K1 x bandwidth (min) + K3 x delay (cumulative)] Metric = [2,499,840 + 514,560] Metric = 3,014,400

EIGRP Metrics Are BackwardCompatible with IGRP

EIGRP Tables
Router Cs tables:

Topology

EIGRP Neighbor Table

Adjacency information is stored within a neighbour table. The router must have an entry for each neighbouring router in order to function.

EIGRP States
There are two states for EIGRP routing entries Passive Active Passive indicates that there are no routing updates being received or sent for that particular route the table on that route is stable Active Indicates that the successor route is no longer valid and there is no feasible successor a new route is being searched for that route via computation or being queried If there is always a feasible successor then there is no need to enter the active state As one route fails then another is added to the table

EIGRP Topology Table

When the router dynamically discovers a new neighbour, it sends an update about the routes that it knows to its new neighbour. These updates populate the topology table, which contains all the destinations advertised by neighbouring routers.
R1#show ip eigrp topology IP-EIGRP Topology Table for AS(100)/ID(192.168.1.101) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 192.168.1.96/27, 1 successors, FD is 40512000 via Connected, Serial0/0/1 P 192.168.1.0/24, 1 successors, FD is 40512000 via Summary (40512000/0), Null0 P 172.16.0.0/16, 1 successors, FD is 28160 via Summary (28160/0), Null0 P 172.16.1.0/24, 1 successors, FD is 28160 via Connected, FastEthernet0/0 P 172.17.0.0/16, 1 successors, FD is 40514560 via 192.168.1.102 (40514560/28160), Serial0/0/1

The topology table is updated when a directly connected route or interface changes or when a neighbouring router reports a change to a route.

Topology Table
To view detailed information about the metrics of a specific entry in the topology table, add the optional parameter [network] to the show ip eigrp topology command:

EIGRP Routing Table

R1#show ip route eigrp D 172.17.0.0/16 [90/40514560] via 192.168.1.102, 00:07:01, Serial0/0/1 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks D 172.16.0.0/16 is a summary, 00:05:13, Null0 192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks D 192.168.1.0/24 is a summary, 00:05:13, Null0 R1#show ip route <output omitted> Gateway of last resort is not set D 172.17.0.0/16 [90/40514560] via 192.168.1.102, 00:06:55, Serial0/0/1 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks D 172.16.0.0/16 is a summary, 00:05:07, Null0 C 172.16.1.0/24 is directly connected, FastEthernet0/0 192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks C 192.168.1.96/27 is directly connected, Serial0/0/1 D 192.168.1.0/24 is a summary, 00:05:07, Null0

Configuring EIGRP with IP

Classful configuration example: routerA(config)#router eigrp 109 routerA(config-router)#network 10.1.0.0 routerA(config-router)#network 10.4.0.0 routerA(config-router)#network 172.16.7.0 routerA(config-router)#network 172.16.2.0 routerA(config-router)#no auto-summary Classless configuration example: routerA(config)#router eigrp 109 routerA(config-router)#network 10.1.0.0 0.0.255.255 routerA(config-router)#network 10.4.0.0 0.0.255.255 routerA(config-router)#network 172.16.2.1 0.0.0.0 routerA(config-router)#network 172.16.7.2 0 0.0.0.0 routerA(config-router)#no auto-summary

Automatic Summarisation
Update: C- 2.0.0.0/8

C 2.0.0.0/8 Subnet 2.1.1.0/24

C 2.0.0.0/8 Subnet 2.2.2.0/24

EIGRP automatically summarises routes at the classful boundarythe boundary where the network address ends as defined by class-based addressing. In most cases, auto summarisation is beneficial, because it keeps the routing tables as compact as possible. Auto summarisation causes problems when two subnets are discontiguous This is shown in the diagram above where auto summary means that RTC will ignore updates from RTD

Null0 Summary Route

EIGRP automatically includes a null0 summary route as a child route whenever both of following conditions exist: 1. There is at least one subnet that was learned via EIGRP. 2. Automatic summarisation is enabled. The NULL0 interface is also known as a bit bucket, any traffic which is received at a router based on the summary that does not actually have a interface will be sent to null0 Nice way to say deleted

EIGRP Manual Summarisation

172.16.2.0/24

ISP
172.16.3.0/24
S0/0/0 DCE .1

Loopback 10.1.1.1/30
S0/0/0 .2 64 kbps S0/0/1 .5

.1

R2

.9

S0/0/1 DCE

192.168.10.8/30
S0/0/1 .10 S0/0/0 DCE .6 192.168.1.0/24
Fa0/0

Fa0/0

1024 kbps 1544 kbps

172.16.1.0/24

.1

R1

192.168.10.4/30

R3

.1 Lo2 192.168.2.1/24

Lo2 192.168.3.1/24

EIGRP Default-Network command

Verifying EIGRP
R1#show ip protocols Routing Protocol is "eigrp 100" 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 metric weight K1=1, K2=0, K3=1, K4=0, K5=0 EIGRP maximum hopcount 100 EIGRP maximum metric variance 1 Redistributing: eigrp 100 EIGRP NSF-aware route hold timer is 240s <output omitted> Maximum path: 4 Routing for Networks: 172.16.1.0/24 192.168.1.0 Routing Information Sources: Gateway Distance Last Update (this router) 90 00:09:38 Gateway Distance Last Update 192.168.1.102 90 00:09:40 Distance: internal 90 external 170

Equal Cost Load Balancing

Equal-cost load balancing is the ability of a router to distribute traffic over all its network ports that are the same metric from the destination address. EIGRP automatically load balances across equal cost paths. Load balancing increases the use of network segments and increases effective network bandwidth. Cisco IOS software by default will install up to four equal-cost paths in the routing table for most routing protocols. The maximum-paths command in can be used to allow up to six equal-cost paths.

Equal Cost Load Balancing

EIGRP can also balance traffic across multiple routes that have different metrics, which is called unequal-cost load balancing. The degree to which EIGRP performs load balancing is controlled with the variance command Router R2 R3 R4 RD/AD FD

10 10 30

20 25 45

10 15

R2

10 10

FC = RD<FD R5
192.168.10.0/24

R1

R3

15

R4

30

R1(config)#router eigrp 1 R1(config-router)#variance 2

This commands needs careful usage as traffic will be sent across links which are not equal Consider something like IPTelephony where multiple links are used

Configuring WAN Links

By default, EIGRP may use up to 50 % of the bandwidth of an interface or sub-interface for routing traffic.
This can be too much preventing data traffic going across a link especially if the bandwidth is not high on that link

EIGRP uses the bandwidth specified with the bandwidth command, or the default bandwidth of the link if none is configured, when calculating how much bandwidth to use.
Percentage can be set to a value greater than 100% which will be useful if you set the bandwidth command low for routing purposes i.e. an expensive 128kbps link you advertised as 64 kbps to prevent usage

EIGRP bandwidth usage can be adjusted as follows:

R1(config)#interface s0/0/0 R1(config-if)#bandwidth 128 R1(config-if)#ip bandwidth-percentage eigrp 1 25 AS %

Simple Password vs. MD5 Authentication

Simple password authentication:
Router sends packet and key. Neighbor checks if received key matches its key. Not secure.

MD5 authentication
Configure a key (password) and key-id; router generates a message digest, or hash, of the key, key-id and message. Message digest is sent with packet; key is not sent. Secure.

EIGRP MD5 Authentication Configuration

R1(config)#interface Serial0/0/1 R1(config-if)#bandwidth 64 R1(config-if)# ip address 192.168.1.101 255.255.255.224 R1(config-if)# ip authentication mode eigrp 100 md5 R1(config-if)# ip authentication key-chain eigrp 100 R1chain R1(config)# key chain R1chain R1(config-keychain)#key 1 R1(config-keychain-key)#key-string firstkey R1(config-keychain-key)# accept-lifetime 04:00:00 Jan 1 2006 infinite R1(config-keychain-key)# send-lifetime 04:00:00 Jan 1 2006 04:30:00 Jan 1 2006 R1(config-keychain)# key 2 R1(config-keychain-key)#key-string secondkey R1(config-keychain-key)#accept-lifetime 04:00:00 Jan 1 2006 infinite R1(config-keychain-key)#send-lifetime 04:29:00 Jan 1 2006 infinite

Factors That Influence EIGRP Scalability

Quantity of routing information exchanged between peers: without proper route summarization, this can be excessive. Number of routers that must be involved when a topology change occurs. Depth of topology: the number of hops that information must travel to reach all routers. Number of alternate paths through the network.

EIGRP Query Process

10

R6

192.168.10.0/24

10

R2 Query Reply

100

Query
10

Reply
100

R1 Query

R3
20 200

R5 Reply

R1 loses its link to R6, and sends query packets to all neighbors on interfaces other than the one used to reach the previous successor (split horizon), inquiring whether they have a route to the given destination. If a router has an alternate route, it answers the query and does not propagate it further. If a neighbor does not have an alternate route, it queries each of its own neighbors for an alternate path. The queries then propagate through the network, creating an expanding tree of queries.

R4 Query Reply

Stuck in Active (SIA)

10

R6

192.168.10.0/24

10

R2 Query

100

Query
10

100

R1 Query

3 Mins Reset
20

R3
200

R5 Reply

Once a route goes active and the query sequence is initiated, the route can only come out of the active state and move to passive state when it receives a reply for every generated query. If the router does not receive a reply to all the outstanding queries within 3 minutes (the default time), the route goes to the SIA state.

R4 Query Reply

When a route is SIA, the querying router resets the neighbor relationship to the neighbor that fails to reply.

Stuck in Active (SIA)

10

R6

192.168.10.0/24

10

R2 Query R3

100

Query R1 Query

SIA-Q SIA-R
20

SIA-Q

R1 queries R3 downstream (with an SIA-Query) at the midway point of the active timer (1.5 minutes by default) about the status of the route.

R5 Reply
200

R3 responds (with an SIAReply) that it is searching for a replacement route. R3 sends up to three SIAQueries to R5. If they go unanswered, R3 terminates the neighbor relationship with R5. R3 then updates R1 with an SIA-Reply indicating that the network is unreachable.

R4 Query Reply

Hub & Spoke Network

The spoke routers are remotes sites, and they have two connections for redundancy, not so they can transit traffic between Router A and Router B. Router A should never use the spokes as a path to anything reachable through Router B, so theres no reason to learn about, or query for, routes through these spokes.
10.1.1.0/24

Hub Network
A
Router A

B
Router B

Spoke 4 Spoke 3 Spoke 2 Spoke 1

Not Designed to Transit Traffic

EIGRP Stub Routing

The EIGRP Stub Routing feature:
Improves network stability Reduces resource utilization and Simplifies remote router (spoke) configuration

Stub routing is commonly used in hub-and-spoke topology. Stub router sends a special peer information packet to all neighboring routers to report its status as a stub router. Any neighbor that receives a packet informing it of the stub status does not query the stub router for any routes.

EIGRP Stub Routing

To inform Routers A & B B that the paths through the spokes should not be used for transit traffic, the spoke routers can be configured as stubs:
Hub Network
Reply
Router A

10.1.1.0/24

Query B
Router B

Spoke 4 Spoke 3 Spoke 2 Spoke 1

Spoke1(config)router eigrp 100 Spoke1(config-router)#eigrp stub

Configuring EIGRP Stub

Router(config-router)#eigrp stub [receive-only|connected|static|summary] receive-only: Prevents the stub from sending any type of route. connected: Permits stub to send connected routes (may still need to redistribute). static: Permits stub to send static routes (must still redistribute). summary: Permits stub to send summary routes. Default is connected and summary.

EIGRP Objectives
Describe the key capabilities that distinguish EIGRP from other routing protocols Identify the four key technologies employed by EIGRP Describe how EIGRP operates Describe the five components of the metric used by EIGRP Calculate the EIGRP metric for a range of pathways between routers Explain how IGRP routes are integrated into EIGRP routes and vice-versa Describe the commands used in a basic EIGRP configuration task Verify EIGRP operation Describe and configure MD5 router authentication Explain how to mark the spokes of large network as stubs to reduce EIGRP queries and thus improve network scaling Explain how to minimise active routes Describe how graceful shut down prevents loss of packets when routers go down

EIGRP Additional Reading

Additional useful information can be found at the following URL

http://www.cisco.com/en/US /tech/tk365/technologies_w hite_paper09186a0080094cb 7.shtml

Any Questions?