ccnp route lab

8/10/2019 Ccnp Route lab

1/197

Copyrights Netscope FZ LLC 2007-2015

Website: http://[email protected]

Page 1of 197

Comprehensive Coverage of the CCNP Route Blueprint

Authored By:

Khawar ButtPenta CCIE # 12353(R/S,Security,SP,Voice,Storage)

Cisco Certified Network Professional

(CCNP) Route Lab Manual


2/197



Page 2of 197

Module 1 VLSM and RouteSummarization

Authored By:





3/197



Page 3of 197

Definition

Variable-Length Subnet Mask(VLSM):provides the ability to have more thanone subnet mask within your major network. It also allows you to furthersubnet your already subnetted networks. Requires Classless RoutingProtocols.

Advantages

Efficient Use of IP addresses: Without VLSMs, networks would have to use

the same subnet mask throughout the network. But all your networks donthave the same number of hosts.

For example: You have 2 LAN connected via a Serial Point-to-point connection.Each LAN has 50 Hosts on it. When you assign the subnet mask, it has to beconsistent across your network. So you end up assign a sub-network addressto the WAN connection with 62 hosts, whereas you only need 2.

Greater Capability for Route Summarization: Route Summarization iscovered in detail, later on in this module.

Variable-Length Subnet Mask


4/197



Page 4of 197

Calculating VLSMs

In this example, we want to connect the Main Site to the Branch Offices. If weused a fixed length subnet mask, we would need 4 networks for the LANs and

3 Networks for WANs, a total of 7 networks. Let us say we have a Class Caddress of 200.200.200.0 assigned to us. If we need 7 networks, we have toborrow 4 bits, giving us 14 networks. But it will only give us 14 hosts pernetwork. In order to get around this problem, we will use VLSMs.

In VLSMs, we can get away with borrowing only 3 bits. 3 bits give us 6 usable

networks with 30 hosts per network. We will use the first 4 networks for ourLAN based networks, and subnet the fifth one further to give us additionalnetworks with less hosts on each for our WAN connections. Our WAN

connections only require 2 hosts per network and we need 3 Networks.

Subnetting the 200.200.200.0 network into 6 subnets

We borrow 3 bits, giving us a new mask of 255.255.255.224 or 27 bitSubnet Mask.

Our new networks are as follows:

200.200.200.32/27

200.200.200.64/27

200.200.200.96/27

200.200.200.128/27

25 Hosts

25 Hosts

25 Hosts

25 Hosts


5/197



Page 5of 197

200.200.200.160/27

200.200.200.192/27

We will assign the first 4 networks to our LAN-Based Networks. We can take either the 5thor 6thnetwork and further subnet it. Let use

the 5thnetwork and further subnet it.

Decimal BinarySubnet :200.200.200.10100000 (200.200.200.160)Mask : 255.255.255.11100000 (255.255.255.224)

We only need 2 hosts per WAN connection. We will borrow a further 3bits from this network, leaving only 2 bits for hosts on each network.

The network numbers are as follows:

200.200.200.10100100 (200.200.200.164) Valid Host Range: 165-166200.200.200.10101000(200.200.200.168) Valid Host Range: 169-170200.200.200.10101100 (200.200.200.172) Valid Host Range: 173-174200.200.200.10110000 (200.200.200.176) Valid Host Range: 177-178200.200.200.10110100(200.200.200.180) Valid Host Range: 181-182200.200.200.10111000(200.200.200.184) Valid Host Range: 185-186

So you can choose any 3 of the above network addresses for the WANconnections.

25 Hosts

25 Hosts

25 Hosts

25 Hosts

200.200.200.32/27

200.200.200.64/27

200.200.200.96/27

200.200.200.128/27

200.200.200.164/30

200.200.200.168/30

200.200.200.172/30


6/197



Page 6of 197

Written Exercise for Calculating VLSMs

Exercise 1

Objective: Given an IP address of 200.1.1.0, use VLSMs to assign IP addressesin a efficient manner by minimizing loss of host addresses.

Write the Network Addresses for all the networks including the WANconnections. Make sure to write the Subnet Mask in the bit format (/24).

25 Hosts

25 Hosts

5 Hosts

5 Hosts

5 Hosts


7/197



Page 7of 197

Definition

Route Summarization:reduces the number of routes that a router mustmaintain because it represents a series of network numbers in a singlesummary address.

Advantages

Reduces the size of Routing Tables

Isolates Topology changes from other routes in a Large Network

Route Summarization

A B

150.50.33.0/24

150.50.34.0/24

150.50.35.0/24

Routing Table

150.50.33.0/24

150.50.34.0/24

150.50.35.0/24

Routing Table

150.50.0.0/16


8/197



Page 8of 197

Summarizing within an Octet

Let us say that we the following networks connected to a Router named LA:

150.50.64.0/24150.50.65.0/24150.50.66.0/24150.50.67.0/24150.50.68.0/24150.50.69.0/24150.50.70.0/24

150.50.71.0/24

LA is connected to another router SD. LA wants to minimize the number ofentries it sends to SD.

Write the network in Binary Format.

150.50.01000000.00000000 (150.50.64.0)150.50.01000001.00000000 (150.50.65.0)150.50.01000010.00000000 (150.50.66.0)

150.50.01000011.00000000 (150.50.67.0)150.50.01000100.00000000 (150.50.68.0)150.50.01000101.00000000 (150.50.69.0)150.50.01000110.00000000 (150.50.70.0)150.50.01000111.00000000 (150.50.71.0)

Starting from High order bits towards low order bits (Left to Right), look at thebits that are common and draw a line.

150.50.01000000.00000000 (150.50.64.0)

150.50.01000001.00000000 (150.50.65.0)150.50.01000010.00000000 (150.50.66.0)150.50.01000011.00000000 (150.50.67.0)150.50.01000100.00000000 (150.50.68.0)150.50.01000101.00000000 (150.50.69.0)150.50.01000110.00000000 (150.50.70.0)150.50.01000111.00000000 (150.50.71.0)

The summarized address will be address you get from the common high order

bits.


9/197



Page 9of 197

150.50.01000000.00000000 (150.50.64.0).Your Subnet mask will the number of common bits, which is 16 + 16 + 5 = 21The Route that will be sent is 150.50.64.0/21.


10/197



Page 10of 197

Written Exercise for Route Summarization

Exercise 1

Where would you do Route Summarization?

What would the Summarized addresses be?

LA SF

OC

SD

131.107.1.128/28

131.107.1.144/28

131.107.1.160/28

131.107.1.176/28

131.107.1.112/28

131.107.1.80/28

131.107.1.192/28 131.107.1.208/28

131.107.1.64/28

131.107.1.96/28


11/197



Page 11of 197

Written Exercise for Route Summarization

Exercise 2

Where would you do Route Summarization?

What would the Summarized addresses be?

LA SF

OC

SD

131.107.1.64/28

131.107.1.80/28

131.107.1.96/28

131.107.1.112/28

131.107.1.192/28

131.107.1.208/28

131.107.1.48/28

131.107.1.160/28

131.107.1.128/28 131.107.1.144/28

131.107.1.176/28


12/197



Page 12of 197

Module 2 RIP v1 Labs

Authored By:





13/197



Page 13of 197

R1 Configuration

Interface IP Address Subnet Mask

Loopback 0 1.1.1.1 255.0.0.0

S 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0S 0/0 192.1.12.2 255.255.255.0

Objective: Configuring RIP v1 on the routers to exchange routes between therouters.

On R1

router#conf trouter(config)#hostname R1R1(config)#Router RIPR1(config-router)#no auto-summaryR1 (config-router)#net 1.0.0.0R1 (config-router)#net 192.1.12.0

On R2

Router#conf trouter(config)#hostname R2R2(config)#Router RIP

Lab 1 Basic RIP Configuration

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8


14/197



Page 14of 197

R2(config-router)#no auto-summaryR2 (config-router)#net 2.0.0.0R2 (config-router)#net 192.1.12.0

On Both Routers

Type Show ip route

What networks do you see listed?

Ping your partners Loopback Interface address. Are you successful?


15/197



Page 15of 197

(Note: This lab builds on the configuration of Lab 1)

Objective: Looking at the operation of RIP v1. You will take a look at theBroadcast classfull updates. You will also take a look at the effect of Passive-Interface command and the effect of turning off Split Horizon.

On Both Routers

Rx#debug ip rip (Where x is your Router number)

Interesting Facts

Does not include the directly connected network (192.1.12.0) in itsupdate towards R2.

Does not include 2.0.0.0 network although it does exist in its routingtable back towards R2.

The destination address is a Broadcast

It does not send periodic updates at constant intervals (Time Jitters)

On R1

R1(config)#int loopback 0R1(config-if)#shut

Lab 2 RIP Operation

RIP: Sending V1 update to 255.255.255.255 via Serial 0/0 (192.1.12.1)

RIP: Build update entriesNetwork 10.0.0.0 metric 1

RIP: Sending V1 update to 255.255.255.255 via Loopback 0 (1.1.1.1)RIP: Build update entries

Network 2.0.0.0

Network 192.1.12.0RIP: received V1 update from 192.1.12.2 on serial 0/0

2.0.0.0 in 1 hop

RIP: build flash update entriesnetwork 1.0.0.0 metric 16

RIP: sending v1 update to 255.255.255.255 via Serial0/0 (192.1.12.1)


16/197



Page 16of 197

Interesting Facts

When a route goes down, the router does not wait for Periodic Update. Itsends a Triggered update with a Poisoned route with a metric of 16 Notice R2 also sends an immediate Triggered Update back, indicating

that you cant reach 10.0.0.0 cannot be reached through it.

On R1

R1(config)#int loopback 0R1(config-if)#no shut

Turning Split Horizon Off

On Both Routers

Rx(Config)#int s 0/0Rx(Config-if)#no ip split-horizon

Interesting Facts

The router is advertising all routes. Even the ones that it learned fromthe same router. The reason it does make it to the routing table isbecause the Router has a better metric to the route.

Passive Interfaces

On Both RoutersRx(config)#router ripRx(config-router)#passive interface Loopback 0

Interesting FactsThe router stops advertising from the Loopback interface. The command

is useful for cutting down unnecessary broadcast over an interface thatonly has hosts on it and no router.

RIP: Sending v1 update to 255.255.255.255 via Serial0/0 (192.1.12.1)RIP: build update entries

network 1.0.0.0 metric 1




17/197



Page 17of 197


Objective:Turn Spilt-Horizon back on. You would like to send Unicast updatesbetween R1 and R2 instead of Broadcast updates.

Turning Split Horizon Back on

On Both Routers

Rx(Config)#int s 0/0Rx(Config-if)#ip split-horizon

Sending Unicast Updates on S 0/0 interface

On R1

R1(config)#Router rip

R1(config-router)#passive interface S 0/0R1(config-router)#neighbor 192.1.12.2

On R2

R2(config)#Router ripR2(config-router)#passive interface S 0/0R2(config-router)#neighbor 192.1.12.1

Passive interface command disables RIP from sending broadcasts over aspecific interface. The neighbor allows updates to go to specific IP

addresses. So It will disables all RIP broadcasts and only send unicastupdates to each other.

Lab 3 RIP using UNICAST


18/197



Page 18of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

E 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0

E 0/0 192.1.12.2 255.255.255.0

S 0/0 192.1.23.1 255.255.255.0

R3 Configuration


Loopback 0 3.3.3.3 255.0.0.0

S 0/0 192.1.23.3 255.255.255.0

Lab 4 Injection of Default Route

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/24

R4

S 0/0 (.3)L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/24


19/197



Page 19of 197

E 0/0 191.1.34.3 255.255.255.0

R4 Configuration


Loopback 0 4.4.4.4 255.0.0.0

S 0/0 192.1.34.4 255.255.255.0

Objective: R1 is acting as the ISP and R2 is the Edge Router for a companythat is running RIP internally between R2, R3 and R4. R1 will have staticroutes towards all the company networks. R2 will have a default route pointingtowards R1.

On R1

R1#conf tR1(config)#ip route 2.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 3.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 4.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 192.1.23.0 255.255.255.0 192.1.12.2R1(config)#ip route 192.1.34.0 255.255.255.0 192.1.12.2

On R2

R2#conf tR2(config)#ip route 0.0.0.0 0.0.0.0 192.1.12.1R2(config)#Router RIPR2(config-router)#no auto-summaryR2(config-router)#net 2.0.0.0R2(config-router)#net 192.1.12.0R2(config-router)#net 192.1.23.0

On R3

R3#conf tR3(config)#Router RIPR3(config-router)#no auto-summaryR3(config-router)#net 3.0.0.0R3(config-router)#net 192.1.23.0R3(config-router)#net 192.1.34.0

On R4

R4#conf t


20/197



Page 20of 197

R4(config)#Router RIPR4(config-router)#no auto-summaryR4(config-router)#net 4.0.0.0R4(config-router)#net 192.1.34.0

On R3 and R4

Type Show IP route. Do you see an entry learned through RIP that hasa *?

By default, RIP will advertise the default route to other RIP enabledrouters.

Enter Debug IP RIP and view the routing table entries going from R2 toR3 and R4.


21/197



Page 21of 197

(Builds on Lab 4)

Objecctive: Use the default-information originate instead of the default-routeon R2 to inject the default route into R3 and R4. You will no longer be usingthe default route towards R1. Configure a static route to provide reachabilitytowards 1.0.0.0 network.

On R2

R2(config)#no ip route 0.0.0.0 0.0.0.0 192.1.12.1R2(config)#clear ip route *R2(config)#ip route 1.0.0.0 255.0.0.0 192.1.12.1

On R3 and R4

Type Show IP route. Do you see an entry learned through RIP that has a*?

This is done by using the Default-information originate on R2

Enter Debug IP RIP and view the routing table entries going from R2 to R3and R4.

Lab 5 Default Network usingDefault Information Originate


22/197



Page 22of 197

Module 3 RIP v2 Labs

Authored By:





23/197



Page 23of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

S 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0

S 0/0 192.1.12.2 255.255.255.0

Objective: Configuring RIP v1 on the routers to exchange routes between therouters.

On R1

router#conf t

router(config)#hostname R1R1(config)#Router RIPR1(config-router)#no auto-summaryR1(config-router)#version 2R1 (config-router)#net 1.0.0.0R1 (config-router)#net 192.1.12.0

On R2

Router#conf t

Lab 1 Basic RIP v2 Configuration

S 0/0(.1) R2192.1.12.0/2R1S 0/0 (.2)

L0 1.1.1.1/8 L0 2.2.2.2/8


24/197



Page 24of 197

router(config)#hostname R2R2(config)#Router RIPR2(config-router)#no auto-summaryR2(config-router)#version 2R2 (config-router)#net 2.0.0.0R2 (config-router)#net 192.1.12.0

On Both Routers

Type Show ip route

What networks do you see listed?

Ping your partners Loopback Interface address. Are you successful?


25/197



Page 25of 197


Objective: Looking at the operation of RIP v2. You will take a look at theMulticast classless updates.

On Both Routers

Rx#debug ip rip (Where x is your Router number)

Interesting Facts

Update is a V2 Update

Includes the Subnet Mask

The destination address.

Lab 2 RIP 2 Operation

RIP: Sending V2 update to 224.0.0.9 via Serial 0/0 (192.1.12.1)RIP: Build update entries

Network 1.0.0.0/8 metric 1, External Tag 0

RIP: Sending V2 update to 224.0.0.9 via Loopback 0 (1.1.1.1)RIP: Build update entries

Network 2.0.0.0/8 metric 2, External Tag 0Network 192.1.12.0/8 metric 1, External Tag 0

RIP: received V2 update from 192.1.12.2 on serial 0/0

2.0.0.0/8 in 2 hop metric 1, External Tag 0


26/197



Page 26of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

E 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0

E 0/0 192.1.12.2 255.255.255.0S 0/0 192.1.23.1 255.255.255.0

R3 Configuration


Loopback 0 3.3.3.3 255.0.0.0

S 0/0 192.1.23.3 255.255.255.0

E 0/0 191.1.34.3 255.255.255.0

Lab 3 Compatibility with RIPVersion 1

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1) R2192.1.12.0/2R1S 0/0 (.2)

L0 1.1.1.1/8 L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/2

R4

S 0/0 (.3)L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/2


27/197



Page 27of 197

R4 Configuration


Loopback 0 4.4.4.4 255.0.0.0

S 0/0 192.1.34.4 255.255.255.0

Objective: R3 does not support RIP v2. Configure R1, R2 and R4 with RIP v2.Configure R3 with RIP V1. Allow R2 and R4 to exchange routes with R3.

On R1

R1#conf t

R1(config)#Router RIPR1(config-router)#no auto-summaryR1(config-router)#version 2R1(config-router)#net 192.1.12.0R1(config-router)#net 1.0.0.0

On R2

R2#conf tR2(config)#Router RIPR2(config-router)#no auto-summary

R2(config-router)#version 2R2(config-router)#net 192.1.12.0R2(config-router)#net 192.1.23.0R2(config-router)#net 2.0.0.0R2(config-router)#Interface E 0/0R2(config-if)#ip rip send v1R2(config-if)#ip rip receive v1

On R3

R3#conf t

R3(config)#Router RIPR3(config-router)#no auto-summaryR3(config-router)#version 1R3(config-router)#net 192.1.23.0R3(config-router)#net 192.1.34.0R3(config-router)#net 3.0.0.0

On R4


28/197



Page 28of 197

R4#conf tR4(config)#Router RIPR4(config-router)#no auto-summaryR4(config-router)#version 2R4(config-router)#net 192.1.34.0R4(config-router)#net 4.0.0.0R4(config-router)#Interface S 0/0R4(config-if)#ip rip send version 1R4(config-if)#ip rip receive version 1

On R2

Type Debug ip rip

When R2 sends an update to R1, what address does it use?

When R2 sends an update to R3, what address does it use?

When R4 sends an update to R3, what version does it use?

When R3 sends an update to R2 and R4, what version does it use?


29/197



Page 29of 197


Objective: Configure Plain Text Authentication on all routers. Enable RIP v2on R3. Disable sending of v1 updates on R2 and R4 before enablingauthentication on all the routers.

Enable RIP V2 on all routers and Disable IP RIP Send and

Receive Version 1 commands

R1

(Requires no change)

R2

R2(config)#interface E 0/0R2(config-if)#noip rip send version 1R2(config-if)#noip rip receive version 1

R3

R3(config)#Router RIPR3(config-router)#version 2

R4

R4(config)#interface S 0/0R4(config-if)#noip rip send version 1

R4(config-if)#noip rip receive version 1

Enable Plain-text Authentication of all the Routers

R1

R1(config)#key chain KC-1R1(config-keychain)#key 1R1(config-keychain-key)#key-string CISCOR1(config-keychain-key)#exit

Lab 4 RIP V2 Plain Text

Authentication


30/197



Page 30of 197

R1(config)#int S 0/0R1(config-if)#ip rip authentication key-chain KC-1

R2

R2(config)#key chain KC-1R2(config-keychain)#key 1R2(config-keychain-key)#key-string CISCOR2(config-keychain-key)#exitR2(config)#int S 0/0R2(config-if)#ip rip authentication key-chain KC-1R2(config-if)#int E0/0R2(config-if)#ip rip authentication key-chain KC-1

R3

R3(config)#key chain KC-1R3(config-keychain)#key 1R3(config-keychain-key)#key-string CISCOR3(config-keychain-key)#exitR3(config)#int S 0/0R3(config-if)#ip rip authentication key-chain KC-1R3(config-if)#int E0/0R3(config-if)#ip rip authentication key-chain KC-1

R4

R4(config)#key chain KC-1R4(config-keychain)#key 1R4(config-keychain-key)#key-string CISCOR4(config-keychain-key)#exitR4(config)#int S 0/0R4(config-if)#ip rip authentication key-chain KC-1

Checking the Authentication On all Routers

Type Debug ip rip

Can you see the authentication happening?

Can you see the password in the debug information?

What is the password that is being passed between the routers?


31/197



Page 31of 197


Objective: Configure MD5 Authentication on all routers.

Enable RIP V2 MD 5 Authentication on all routers

R1

R1#config tR1(config)#int S 0/0R1(config-if)#ip rip authentication mode md5

R2

R2#config tR2(config)#int S 0/0R2(config-if)#ip rip authentication mode md5R2(config-if)#int E 0/0R2(config-if)#ip rip authentication mode md5

R3

R3#config tR3(config)#int E 0/0R3(config-if)#ip rip authentication mode md5R3(config)#int S 0/0R3(config-if)#ip rip authentication mode md5

R4

R4#config tR4(config)#int S 0/0R4(config-if)#ip rip authentication mode md5

Checking the Authentication On all Routers

Type Debug ip rip

Can you see the authentication happening and if so, can you see theactual password?

Lab 5 RIP V2 MD5 Authentication


32/197



Page 32of 197

Module 4 EIGRP

Authored By:





33/197


34/197



Page 34of 197

EIGRP can only be used within CISCO routers, and all Cisco routerssupport MD5 authentication. But the routes are not encrypted, so asniffer can easily see the password/s.

Multiple Network Layer Protocol Support:EIGRP can support IP, IPX,and AppleTalk, whereas the other routing protocols support only onerouted protocol. EIGRP will also perform auto-redistribution with NLSP,IPXRIP, RTMP. EIGRP supports incremental SAP and RIP updates, 224HOPS, and it uses bandwidth + delay which is far more better than justTicks and Hops used by IPXRIP. For RTMP it supports event drivenupdates, but it must run in a clientless networks(WAN), and also a bettermetric calculation.

Use Of Multicast Instead Of Broadcast:EIGRP uses multicast addressof 224.0.0.10 instead of broadcast.

Unequal and Equal Cost Path Load-Balancing:This feature will enablethe administrators to distribute traffic flow in the network. By defaultEIGRP will use up to 4 paths and this can be increased to 6.

OSI and EIGRP:Like all TCP/IP routing protocols EIGRP relies in IP todeliver the packets, EIGRP maps to the transport layer of OSI and usesprotocol number 88.

Support Of Different Topology: EIGRP can support broadcast multi-access topologies such as Token-Ring, and Ethernet. Point to pointtopology such as HDLC. NBMA topology such as Frame-Relay.

Easy configuration:The configuration of EIGRP is very similar to IGRPwhich is very simple.

Support of hierarchical addressing scheme: Eigrp supports FLSM,VLSM, CIDR/Supernetting.

100% Loop Free: EIGRP uses DUAL to attain fast convergence whilemaintaining a totally loop free topology at every instance.

Metrics: EIGRP uses 2 step metric: 1. VECTOR 2. COMPOSITE Vector metric is: Min MTU, MAX Load, Min Reliability, Total delay,

Min Bandwidth and Hop count.

The vector metric of a route received from a neighbor is computedfrom the received vector metric and the metric of the interfacethrough which the route was received.


35/197



Page 35of 197

After the vector is received and calculated it is stored in thetopology table.

The vector metric is never adjusted in the outgoing updates, therouter always reports the values it has in its topology table and

relies on the receiving router to adjust the values.

In the above diagram, the minute the Ethernet port on R-A comesactive, it notifies R-B, and R-D with its own vector metric, R-D, and

R-B will adjust these values based on the parameters of theirinterface to R-A, and then they will advertise that cost to R-C.

EIGRP uses the same formula as IGRP to calculate its compositemetric, with one difference and that is EIGRP scales the metriccomponent by 256 to achieve a finer metric granularity. This

metric is calculated using Bandwidth, Delay, Reliability, Load, andMTU. The formula that it uses is as follows:

You can view the detailed vector and composite metric of a singleEIGRP route from the topology table with the following command:

sh ip eigrp top

EIGRP Metric Calculation uses the following formula:

Metric = [107/Bandwidth(min))+(Delay(Sum)]/10)]*256

R-B

R-A

R-D

R-C

S 0/1 10.4.1.1/30

S 0/0 10.1.1.1/30

S 0/1 10.2.1.1/30S 0/0 10.1.1.2/30

S 0/0 10.2.1.2/30

S 0/1 10.3.1.2/30

S 0/0 10.3.1.1/30S 0/1 10.4.1.2/30


36/197



Page 36of 197

Bandwidth = the smallest of all bandwidths in the path to agiven destination divided by 10,000,000.

Delay = the sum of all the delay values assigned to theinterfaces along the path to a given destination divided by 10.

To find out the value of bandwidth and the delay associated to a giveninterface, sh interface < the interface type > x where x is theinterface number.

These values can be changed with the following interface modecommands:

bandwidth < bandwidth in Kbps>

delay < delay in tens of microseconds >


37/197



Page 37of 197

Feasible Distance: FD is equal to advertised distance of a neighbor plusthe cost of the link to that neighbor. In some cases we may have multipleroutes to the same destination, in situation like that FD will be based onthe lowest metric.

Feasibility Condition: It is a condition that is met if a neighborsadvertised distance to a destination is lower than the routers FD to thatsame destination.

o FC states, that the route must be advertised by a downstreamneighbor (with respect to the destination), and the cost of the

advertising routes to the destination must be less than or equal tothe cost of the route that is currently being used by the routerreceiving the advertisement.

Successor: A directly connected neighboring router that has the bestroute to a given destination. These routers are always downstreamrouters.

o In order for a neighbor to become the successor, that neighbormust firstmeet the FC. Successors are entries that are kept in therouting table.

Feasible Successor: FS are downstream neighboring router/s throughwhich a destination can be reached. FS are nothing but backup routes toa given destination, or second best route to a given destination.

o FS s are kept in the topology table, and there may be more thanone FS per destination.

o If a neighbors advertising distance to a destination meets the FC,the neighbor becomes a FS for that destination.

Active State: When a router loses its route to a destination and no FS isavailable in the topology table, the router goes into active state, in thisstate the router sends out queries to all neighbors in order to find a route

to that destination. It is possible for the routers that are receiving thequeries to send queries to their neighbor, this can create a ripple effect.

Passive State: When there is no change in the internetwork, there is noneed to do a computation or convergence, so the routers are all inpassive state. Even when a router loses its successor, as long as thatrouter has a FS in the topology table, the router will remain in the

passive state (normal state), and it will place the FS in the routing table,and no computation will be performed.

Terminology


38/197



Page 38of 197

Topology Table: This includes route entries for all the destinations thatthe router has learned. FS are kept in this table for rapid convergence.

Neighbor table: Each Eigrp router has a neighbor table that has a list ofadjacent routers. Neighbor relationships ensure a bi-directionalcommunication between each of the directly connected neighbor.

Routing Table: Eigrp uses the best path to a given destination (theSuccessor/s) from the topology table and places it into the routing table.

Downstream: A router which is closer to the destination than the localrouter.

Upstream: This router is further away from the destination than thelocal router. This router will use the local router to get to the destination.

Advertised Distance: Is a distance reported to the current router, by aneighbor. Sometimes its referred to as Reported Distance.


39/197



Page 39of 197

Hello:Used for neighbor discovery process. Hello packets are sent asmulticasts, and they use unreliable delivery meaning that they do notneed an ACK, as long as these packets are received the routers candetermine that the neighbor is up.

Update:Update packets convey route information, these are transferredwhen necessary, and are sent only to the routers that require theinformation. When updates are requested by a single router, the sendingrouter will use unicast to convey the route informations, but if an up

date is requested by more than one router, then the updates aremulticast out to 224.0.0.10 address. The updates require ACK s. Thesepackets are used when a router comes up for the first time, or when

there is a topology change, or the metric of a route is changed for betteror worst.

Acknowledgements or ACK s:These packets are sent by the routers toacknowledge the receipt of an update. Acknowledgement packets useunicast and use unreliable delivery method.

Queries:When a router looses its successor and has no feasible

successor in the topology table, it will send a query to all neighbors inthe neighbor table. Queries will always use multicast and requires anACK.

Replies:These packets are sent in response to queries, these packetswill always use unicast and require an ACK.

Packet Types


40/197



Page 40of 197

Purpose:Smaller routing table, smaller updates, and query boundary.

Auto-summarization:Auto-summarization is turned on by default, andit is done on the major network boundary, subnets are summarized to asingle classfull networks.

Manual Summarization:Auto-summarization can be turned off, unlikeOSPF manual summarization can be done on any router in any location.

EIGRP Summarization


41/197



Page 41of 197

Module 4 EIGRP Labs

Authored By:





42/197



Page 42of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

S 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0

S 0/0 192.1.12.2 255.255.255.0

Objective: Configuring EIGRP to look at the basic configuration on EIGRP.

On R1

R1(config)#Router eigrp 12R1 (config-router)#net 1.0.0.0R1 (config-router)#net 192.1.12.0

On R2

R2(config)#Router eigrp 12R2 (config-router)#net 2.0.0.0R2 (config-router)#net 192.1.12.0

Lab 1 Configuring Basic EIGRP

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8


43/197



Page 43of 197

Test the Configuration

Type SH IP ROUTE

What routes do you see?

Are the metrics advertised correct?

Breakdown the Calculation for the Metric.

Metric = Bandwidth (min)+ Delay(sum)

Type SH IP OSPF NEIGHBOR

What is the Hello Time?

Type SH IP EIGRP TOPOLOGY. This shows the Topology table.

Type SH IP EIGRP TOPOLOGY 2.0.0.0.

Notice the Vector and Composite Metric

Type SH IP EIGRP TRAFFIC

See how the Hello # are changing and updates are not.

Bring the loopback interface down

Note the Values in the output. See how the queries number increased

Bring the loopback interface back up

Note how the update # changes

H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num

0 192.1.12.2 Se0/0 10 00:06:21 12 200 0


44/197



Page 44of 197

Changing the Hello-interval and Hold-time timers

On Both Routers

R1(config)#int S 0/0R1(config-if)#ip hello-interval eigrp 12 20R1(config-if)#ip hold-time eigrp 12 60

Type SH IP EIGRP NEIGHBOR

What and whose time do you see?


45/197



Page 45of 197

Objective: Verifying the EIGRP Metric calculations.

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

E 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0E 0/0 192.1.12.2 255.255.255.0

S 0/0 192.1.23.1 255.255.255.0

R3 Configuration


Loopback 0 3.3.3.3 255.0.0.0

S 0/0 192.1.23.3 255.255.255.0

Lab 2 - Basic Metric Calculation

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/24

R4

S 0/0 (.3)L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/24


46/197



Page 46of 197

E 0/0 191.1.34.3 255.255.255.0

R4 Configuration


Loopback 0 4.4.4.4 255.0.0.0

S 0/0 192.1.34.4 255.255.255.0

On R1

R1(config)#Router eigrp 1R1(config-router)#net 1.0.0.0R1(config-router)#net 192.1.12.0

On R2

R2(config)#Router eigrp 1R2(config-router)#net 2.0.0.0R2(config-router)#net 192.1.12.0R2(config-router)#net 192.1.23.0

On R3

R3(config)#Router eigrp 1R3(config-router)#net 3.0.0.0R3(config-router)#net 192.1.23.0R3(config-router)#net 192.1.34.0

On R4

R4(config)#Router eigrp 1R4(config-router)#net 4.0.0.0R4(config-router)#net 192.1.34.0

Type SH IP ROUTE

Do you see all the routes?

Type SH IP EIGRP NEIGHBOR.

Who are your neighbors?


47/197



Page 47of 197

Verify that the Metric Calculations are done based on the EIGRP Metriccalculation formula:Metric = [ 107/BW(min) + Delay(sum) / 10] * 256


Objective: Configuring Passive Interfaces on EIGRP to disable sending ofMulticast Updates on an Interface. Use Unicast updates to set up the neighborrelationship.

On R1 and R2

Type SH IP ROUTE



Do you see your Neighboring router?

Configure Passive-Interface on R1 and R2 towards each other

Rx(config)#Router eigrp 1Rx(config-router)#Passive-interface S 0/0

With RIP, the passive-interface command RIP doesnt send updates butcontinue to receive routes.


Do R1 and R2 see each other as neighbors?

Configure Neighbor Statements on R1 and R2 to establish therelationship

On R1

R1(config)#Router eigrp 1R1(config-router)#Neighbor 192.1.12.2 S 0/0

On R2

Lab 3 Neighbor command withEIGRP


48/197



Page 48of 197

R2(config)#Router eigrp 1R2(config-router)#Neighbor 192.1.12.1 S 0/0

On R1 and R2

Type SH IP ROUTE




In EIGRP, the Neighbor command requires the interface. By specifyingthe interface, you tell it to suppress the Multicast update on the interfaceand instead, send Unicast Updates. But because of the passive-interfacecommand, it also suppressing the Unicast updates.

Conclusion :The passive interface command under EIGRP blocks bothUnicast and Multicast updates. If you want to send Unicast updates only,use the Neighbor command along with the interface.

On R1

R1(config)#Router eigrp 1R1(config-router)#No passive-interface S 0/0

On R2

R2(config)#Router eigrp 1R2(config-router)#No passive-interface S 0/0

On R1 and R2

Type SH IP ROUTE





49/197



Page 49of 197


Objective: Configure the Ethernet link between R1 and R4. Configure theVariance command to support unequal cost load balancing. This lab shows youthe Feasible Condition come into play.

R1 Configuration


E 0/0 192.1.14.1 255.255.255.0

R4 Configuration


E 0/0 192.1.14.4 255.255.255.0

Lab 4 Unequal-Cost Load Balancing

S 0/0 (.3)

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/24

R4

L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/24

E 0/0 (.4)

E 0/0 (.1)

192.1.14.0/24


50/197



Page 50of 197

Configuring the extra link between R1 and R4 and enablingEIGRP on the new link

On R1

R1(config)#Router eigrp 1R1(config-router)#net 192.1.14.0

On R4

R4(config)#Router eigrp 1R4(config-router)#net 192.1.14.0

Changing the Bandwidth and Delay to simulate certain Linkspeeds between the Routers. Set the Delay on all the Interfacesto 2000 to simulate a WAN setup between R1, R2, R3 and R4

Router Interface Bandwidth

R1 E 0/0 64

R1 S 0/0 128

R2 S 0/0 128

R2 E 0/0 512

R3 E 0/0 512

R3 S 0/0 256

R4 S 0/0 256

R4 E 0/0 64

On R1

R1(config)#Interface S 0/0R1(config-if)#bandwidth 128R1(config-if)#Interface E 0/0R1(config-if)#bandwidth 64

R1(config-if)#delay 2000

On R2

R2(config)#Interface E 0/0R2(config-if)#bandwidth 512R2(config-if)#delay 2000R2(config-if)#Interface S 0/0R2(config-if)#bandwidth 128


51/197



Page 51of 197

On R3

R3(config)#Interface E 0/0R3(config-if)#bandwidth 512R3(config-if)#delay 2000R3(config-if)#Interface S 0/0R3(config-if)#bandwidth 256

On R4

R4(config)#Interface E 0/0R4(config-if)#bandwidth 64R4(config-if)#delay 2000

R4(config-if)#Interface S 0/0R4(config-if)#bandwidth 256

Configure the Variance Command on the routers to supportunequal Load balancing

Note you have 2 ways to get to the diagonally opposite loopback networks

Calculate the metric to get to the diagonally opposite loopbacknetworks for both Paths

Metric = [ 107/BW(min) + Delay(sum) / 10] * 256

Input the appropriate Variance for the EIGRP 1 process. Variance isbased on your composite metric. (Variance = Best Path/Worst Best)Rounded up

On All Routers

Rx(config)#Router EIGRP 1Rx(config-router)#Variance xx

On All Routers

Type Clear ip route *

Type SH IP ROUTE.

Do all the routers show dual paths to get the diagonally oppositeloopback networks.


52/197



Page 52of 197

If not, Why?


53/197



Page 53of 197

Group A

Group B

Objective: Configure EIGRP Route Summarization on individual routers andthe Backbone routers connecting the two groups to each other.

R2 from each group will have E 0/1 connected to the backboneusing the 10.5.1.0 /24 network.

Use the following for x (A=1,B=2)

R1 Configuration


Loopback 0 10.x.4.1 255.255.255.0

Loopback 1 10.x.5.1 255.255.255.0

Loopback 2 10.x.6.1 255.255.255.0

Loopback 3 10.x.7.1 255.255.255.0

E 0/0 10.x.1.1 255.255.255.0

Lab 5 Route Summarization

L0 10.1.12.0

L3 10.1.15.0/24

L0 10.1.8.0

L3 10.1.11.0/24L0 10.1.4.0

L3 10.1.7.0/24

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)

S 0/0(.4)

R3

192.1.34.0/24

R4

S 0/0 (.3)L0 10.1.16.0

L3 10.1.19.0/24

192.1.23.0/24


54/197



Page 54of 197

R2 Configuration


Loopback 0 10.x.8.1 255.255.255.0

Loopback 1 10.x.9.1 255.255.255.0

Loopback 2 10.x.10.1 255.255.255.0

Loopback 3 10.x.11.1 255.255.255.0

E 0/0 10.x.1.2 255.255.255.0

S 0/0 10.x.2.1 255.255.255.0

E 0/1 10.5.1.y 255.255.255.0

R3 Configuration


Loopback 0 10.x.12.1 255.255.255.0

Loopback 1 10.x.13.1 255.255.255.0

Loopback 2 10.x.14.1 255.255.255.0

Loopback 3 10.x.15.1 255.255.255.0

E 0/0 10.x.3.1 255.255.255.0

S 0/0 10.x.2.2 255.255.255.0

R4 Configuration


Loopback 0 10.x.16.1 255.255.255.0

Loopback 1 10.x.17.1 255.255.255.0

Loopback 2 10.x.18.1 255.255.255.0

Loopback 3 10.x.19.1 255.255.255.0

E 0/0 10.x.3.1 255.255.255.0

R1 on Both Groups

R1(config)#Router eigrp 1

R1(config-router)#net 10.0.0.0R1(config-router)#net 192.X.12.0R1(config-router)#no auto-summary

R2 on Both Groups

R2(config)#Router eigrp 1R2(config-router)#net 10.0.0.0R2(config-router)#net 192.X.12.0R2(config-router)#net 192.X.23.0


55/197



Page 55of 197

R2(config-router)#no auto-summary

R3 on Both GroupsR3(config)#Router eigrp 1R3(config-router)#net 10.0.0.0R3(config-router)#net 192.X.23.0R3(config-router)#net 192.X.34.0R3(config-router)#no auto-summary

R4 on Both Groups

R4(config)#Router eigrp 1

R4(config-router)#net 10.0.0.0R4(config-router)#net 192.X.34.0R4(config-router)#no auto-summary

Objective: Configure EIGRP Route Summarization on individual routers andthe Backbone routers connecting the two groups to each other.

Type SH IP ROUTE. Do you see all the loopback networks?

Lets do summarization on each router.

On each router, calculate the summary address and enter it on theappropriate interfaces.

Write down your summary address and mask.

Apply it to your appropriate interfaces using the following command:

IP summary-address eigrp 1 [summary-address] [mask]

Type SH IP ROUTE. Do you see less routes now?

Get together with your group and figure out a summarization for theBorder router (Router connecting to the backbone).

Write it down

On the Border Routers type the following commands:

Router(config)#int E 0/1


56/197



Page 56of 197

Router(config-if)#ip summary-address eigrp 1 [address] [Mask]

Type SH IP ROUTE

Is the routing table the same? If not, what is the change?


57/197



Page 57of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

E 0/0 192.1.12.1 255.255.255.0

R2 Configuration


Loopback 0 2.2.2.2 255.0.0.0

E 0/0 192.1.12.2 255.255.255.0

S 0/0 192.1.23.1 255.255.255.0

R3 Configuration


Loopback 0 3.3.3.3 255.0.0.0

S 0/0 192.1.23.3 255.255.255.0

E 0/0 191.1.34.3 255.255.255.0

Lab 6 Injecting Default Route with

Route Redistribution

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8 L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/24

R4

S 0/0 (.3)L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/24


58/197



Page 58of 197

R4 Configuration


Loopback 0 4.4.4.4 255.0.0.0

S 0/0 192.1.34.4 255.255.255.0

Objective: R1 is acting as the ISP and R2 is the Edge Router for a companythat is running EIGRP internally between R2, R3 and R4. R1 will have static

routes towards all the company networks. R2 will have a default route pointingtowards R1.R2 should inject the default route into R3 and R4.

On R1

R1(config)#ip route 2.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 3.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 4.0.0.0 255.0.0.0 192.1.12.2R1(config)#ip route 192.1.23.0.0.0 255.255.255.0 192.1.12.2R1(config)#ip route 192.1.34.0.0.0 255.255.255.0 192.1.12.2

On R2

R2(config)#ip route 0.0.0.0 0.0.0.0 192.1.12.1R2(config)#Router EIGRP 1

R2(config-router)#no auto-summaryR2(config-router)#net 2.0.0.0R2(config-router)#net 192.1.12.0R2(config-router)#net 192.1.23.0

On R3

R3(config)#Router EIGRP 1R3(config-router)#no auto-summaryR3(config-router)#net 3.0.0.0R3(config-router)#

net 192.1.23.0R3(config-router)#net 192.1.34.0

On R4

R4(config)#Router EIGRP 1R4(config-router)#no auto-summaryR4(config-router)#net 4.0.0.0R4(config-router)#net 192.1.34.0


59/197



Page 59of 197

On R3 and R4

Type Show IP route. Do you have reachability towards the 1.0.0.0network?

On R2

Type Ping 1.1.1.1

Does it work?

On R3 and R4

Type Ping 1.1.1.1

Does it work?

Type SH IP ROUTE

Do you have any routes to the 1.1.1.1 or any Default gateway set?

Use the Redistribute command on R2 to redistribute theDefault Route into EIGRP

On R2

R2(config)#router eigrp 1R2(config-router)#redistribute static metric 10000 1000 255 1 1500

On R3 and R4

Type SH IP ROUTE

Do you see a Default Route? If so, who is advertising it?

Type Ping 1.1.1.1

Were you successful?


60/197



Page 60of 197

(Based on Lab 6 Configuration)

Objective:This lab is based on the previous lab. R2 will have a default routepointing towards R1.R2 should inject the default route into R3 and R4 usingthe Summary address command instead of Route Redistribution.

Remove the redistribute static and ip route statements fromR2

On R2

R1(config)#router eigrp 1R1(config-router)#no redistribute static metric 10000 1000 255 1 1500

Test the connection from R3 & R4 towards the 1.0.0.0 network

On R3 and R4

Type Ping 1.1.1.1

Does it work?

Type SH IP ROUTE

Any route to 1.0.0.0 network or a Default-gateway?

Add the summary routes on R2 E 0/0 Interfaces towards R3

On R2R2(config)#int E 0/0R2(config-if)#ip summary-address eigrp 1 0.0.0.0 0.0.0.0

Test the new configuration

On R3 and R4 Type Ping 4.4.4.4

Does it work? Why or Why Not?

Lab 7 Injecting Default Route with

Summary-Address Command


61/197



Page 61of 197

R1 Configuration


Loopback 0 1.1.1.1 255.0.0.0

Loopback 1 11.11.11.11 255.0.0.0

E 0/0 192.1.12.1 255.255.255.0

R2 Configuration

Interface IP Address Subnet MaskLoopback 0 2.2.2.2 255.0.0.0

E 0/0 192.1.12.2 255.255.255.0

S 0/0 192.1.23.1 255.255.255.0

R3 Configuration


Loopback 0 3.3.3.3 255.0.0.0

Lab 8 Redistributing Directly

Connected Networks

E 0/0 (.3)

E 0/0 (.2)

S 0/0(.1)R2192.1.12.0/24R1

S 0/0 (.2)L0 1.1.1.1/8

L0 2.2.2.2/8

S 0/0(.4)

R3

192.1.34.0/24

R4

S 0/0 (.3)L0 4.4.4.4/8 L0 3.3.3.3/8

192.1.23.0/24

L1 11.11.11.11/8


62/197



Page 62of 197

S 0/0 192.1.23.3 255.255.255.0

E 0/0 191.1.34.3 255.255.255.0

R4 Configuration


Loopback 0 4.4.4.4 255.0.0.0

S 0/0 192.1.34.4 255.255.255.0

Objective: Inject the 1.0.0.0 and 11.0.0.0 networks into EIGRP without usingthe Network command.

Configuring EIGRP on R1 R4. Dont advertise the Loopbacks

in EIGRP on R1 yet.

On R1

R1(config)#Router EIGRP 1R1(config-router)#no auto-summaryR1(config-router)#network 192.1.12.0

On R2

R2(config)#Router EIGRP 1R2(config-router)#no auto-summaryR2(config-router)#net 2.0.0.0R2(config-router)#net 192.1.12.0R2(config-router)#net 192.1.23.0

On R3

R3(config)#Router EIGRP 1R3(config-router)#no auto-summaryR3(config-router)#net 3.0.0.0

R3(config-router)#net 192.1.23.0R3(config-router)#net 192.1.34.0

On R4

R4#conf tR4(config)#Router EIGRP 1R4(config-router)#no auto-summaryR4(config-router)#net 4.0.0.0R4(config-router)#net 192.1.34.0


63/197



Page 63of 197

Redistribute all your directly connected networks on R1

On R1R1(config)#router eigrp 1R1(config-router)#redistribute connected

On R2, R3 and R4

Type SH IP ROUTE

Do you see the 1.0.0.0 and 11.0.0.0 networks?

What type of entry is it?


64/197



Page 64of 197

(Uses the same topology as Lab 8)

Objective: Redistributing EIGRP from one AS to another. Run EIGRP in AS 11between R1 and R2. Run EIGRP in AS 1 between R2, R3 and R4.

Remove eigrp 1 from R1. Remove network 192.1.12.0 and 2.0.0.0 fromEIGRP 1 on R2. Run EIGRP 11 between R1 and R2. Advertise theLoopbacks on both the Routers in EIGRP 11.

On R1

R1(config)#no router eigrp 1R1(config)#router eigrp 11R1(config-router)#no auto-summaryR1(config-router)#net 192.1.12.0R1(config-router)#net 1.0.0.0R1(config-router)#net 11.0.0.0

On R2

R2(config)#router eigrp 1R2(config-router)#no net 2.0.0.0R2(config-router)#no net 192.1.12.0R2(config-router)#Router eigrp 11R2(config-router)#net 192.1.12.0R2(config-router)#net 2.0.0.0

On R1, R3 and R4

Type SH IP ROUTE


Mutually Redistribute between EIGRP 1 and EIGRP 11 on R2.

On R2

R2(config)#router eigrp 1R2(config-router)#redistribute eigrp 11

Lab 9 Redistributing EIGRP into

EIGRP with different AS #


65/197



Page 65of 197

R2(config-router)#router eigrp 11R2(config-router)#redistribute eigrp 1

On R1, R2 and R4

Type SH IP ROUTE


Are the metrics the correct metrics?


66/197



Page 66of 197


Objective: Performing Redistribution between RIP and EIGRP Run RIP betweenR1 and R2. Run EIGRP in AS 1 between R2, R3 and R4.

Remove EIGRP 11 from R1 and R2. Run RIP v2 between R1 andR2. Advertise all the loopbacks on these 2 routers in RIP

On R1

R1(config)#no router eigrp 11R1(config)#router ripR1(config-router)#version 2R1(config-router)#net 192.1.12.0R1(config-router)#net 1.0.0.0

On R2

R2(config)#no router eigrp 11R2(config)#router ripR2(config-router)#version 2R2(config-router)#net 2.0.0.0R2(config-router)#net 192.1.12.0

On R1, R3 and R4

Type SH IP ROUTE


Perform mutual Route redistribution between RIP and EIGRPon R2

On R3

R3(config)#router eigrp 1R3(config-router)#redistribute rip metric 10000 1000 255 1 1500R3(config-router)#router rip

Lab 10 Redistributing EIGRP into RIP


67/197



Page 67of 197

R3(config-router)#redistribute eigrp 1 metric 3

On R1, R3 and R4

Type SH IP ROUTE


Ping 1.1.1.1 from R4 and Ping 4.4.4.4 from R1.

Are you successful?


68/197



Page 68of 197


Objective:This lab builds on the configuration of the previous labs. We willadd some new routes on R1 and R4 and inject them into the appropriateprotocols. We will filter certain routes from getting redistributed into the otherrouting protocol

Add the following Loopbacks on R1 and R4 and advertise theminto RIP on R1 and EIGRP 1 on R4

R1


Loopback 11 11.0.0.1 255.0.0.0

Loopback 12 12.0.0.1 255.0.0.0

Loopback 13 13.0.0.1 255.0.0.0

Loopback 14 14.0.0.1 255.0.0.0

R4


Loopback 15 15.0.0.1 255.0.0.0

Loopback 16 16.0.0.1 255.0.0.0

Loopback 17 17.0.0.1 255.0.0.0

Loopback 18 18.0.0.1 255.0.0.0

On R1

R1(config)#interface Loopback 11R1(config-if)#ip address 11.0.0.1 255.0.0.0

R1(config-if)#interface Loopback 12R1(config-if)#ip address 12.0.0.1 255.0.0.0R1(config)#interface Loopback 13R1(config-if)#ip address 13.0.0.1 255.0.0.0R1(config)#interface Loopback 14R1(config-if)#ip address 14.0.0.1 255.0.0.0R1(config-if)#router ripR1(config-router)#net 11.0.0.0R1(config-router)#net 12.0.0.0R1(config-router)#net 13.0.0.0

Lab 11 Redistributing EIGRP into RIPusing Route Filtering


69/197



Page 69of 197

R1(config-router)#net 14.0.0.0

On R4R4(config)#interface Loopback 15R4(config-if)#ip address 15.0.0.1 255.0.0.0R4(config-if)#interface Loopback 16R4(config-if)#ip address 16.0.0.1 255.0.0.0R4(config)#interface Loopback 17R4(config-if)#ip address 17.0.0.1 255.0.0.0R4(config)#interface Loopback 18R4(config-if)#ip address 18.0.0.1 255.0.0.0R4(config-if)#Router eigrp 1

R4(config-router)#net 15.0.0.0R4(config-router)#net 16.0.0.0R4(config-router)#net 17.0.0.0R4(config-router)#net 18.0.0.0

On R1, R3 and R4

Type SH IP ROUTE


Deny 11.0.0.0 & 12.0.0.0 RIP routes to be redistributed intoEIGRP

On R2

R2(config)#access-list 1 deny 11.0.0.0 0.255.255.255R2(config)#access-list 1 deny 12.0.0.0 0.255.255.255R2(config)#access-list 1 permit anyR2(config)#Route-map R-2-E permit 10R2(config-route-map)#match ip address 1

R2(config-route-map)#router eigrp 1R2(config-router)#redistribute rip route-map R-2-E

On R3 and R4

Type SH IP ROUTE

Do you see all the 11.0.0.0 and 12.0.0.0 routes?


70/197



Page 70of 197

Do you see all the other RIP routes?

Deny 15.0.0.0 & 16.0.0.0 EIGRP routes to be redistributed intoRIP

R2(config)#access-list 2 deny 15.0.0.0 0.255.255.255R2(config)#access-list 2 deny 16.0.0.0 0.255.255.255R2(config)#access-list 2 permit anyR2(config)#route-map E-2-R permit 10R2(config-route-map)#match ip address 2R2(config-route-map)#router ripR2(config-router)#redistribute eigrp 1 route-map E-2-R

On R1

Type SH IP ROUTE

Do you see all the 15.0.0.0 and 16.0.0.0 routes?

Do you see all the other EIGRP routes?


71/197



Page 71of 197


Objective: R1 and R2 will not be running any routing protocol between them.R1 will use a default route pointing towards R2. R2 will create static routes forthe R1 networks. You would like to inject some of these static routes into thealready running EIGRP instance between R2, R3 and R4.

Disabling RIP between R1 and R2. Configuring a Default Routeon R1 pointing towards R2. Configure Static routes on R2 for

all the R1 networks

On R1

R1(config)#ip route 0.0.0.0 0.0.0.0 192.1.12.2R1(config)#no Router RIP

On R2

R2(config)#ip route 1.0.0.0 255.0.0.0 192.1.12.1

R2(config)#ip route 11.0.0.0 255.0.0.0 192.1.12.1R2(config)#ip route 12.0.0.0 255.0.0.0 192.1.12.1R2(config)#ip route 13.0.0.0 255.0.0.0 192.1.12.1R2(config)#ip route 14.0.0.0 255.0.0.0 192.1.12.1R2(config)#no Router RIP

Redistribute all the Static routes on R2 into EIGRP except the11.0.0.0 and 14.0.0.0 networks

On R2

R2(config)#access-list 3 deny 11.0.0.0 0.255.255.255R2(config)#access-list 3 deny 14.0.0.0 0.255.255.255R2(config)#access-list 3 permit anyR2(config)#route-map S-2-E permit 10R2(config-route-map)#match ip address 3R2(config-route-map)#router eigrp 1R2(config-router)#redistribute static route-map S-2-E

Lab 12 Redistributing Static usingRoute Filtering


72/197



Page 72of 197

On R3 and R4

Type SH IP ROUTE

Verify that you see all the static routes except the 11.0.0.0 and 14.0.0.0networks

Can you Ping 11.0.0.1?

Can you Ping 12.0.0.1?


73/197



Page 73of 197


Objective: Use MD5 to authenticate the Routers that are running EIGRP

Setting up the Key for the Passwords

On R2

R2(config)#key chain KC-1R2(config-keychain)#key 1

R2(config-keychain-key)#key-string cisco

On R3

R3(config)#key chain KC-1R3(config-keychain)#key 1R3(config-keychain-key)#key-string cisco

On R4

R4(config)#key chain KC-1R4(config-keychain)#key 1R4(config-keychain-key)#key-string cisco

Applying the Key to theInterface

On R2

R2(config)#int E 0/0R2(config-if)#ip authentication key-chain eigrp 1 KC-1R2(config-if)#ip authentication mode eigrp 1 md5

On R3

R3(config)#int E 0/0R3(config-if)#ip authentication key-chain eigrp 1 trinetR3(config-if)#ip authentication mode eigrp 1 md5R3(config-if)#int S 0/0R3(config-if)#ip authentication key-chain eigrp 1 trinetR3(config-if)#ip authentication mode eigrp 1 md5

Lab 13 EIGRP Authentication


74/197



Page 74of 197

On R4

R4(config)#int S 0/0R4(config-if)#ip authentication key-chain eigrp 1 trinetR4(config-if)#ip authentication mode eigrp 1 md5

On R2, R3 and R4

oType Debug eigrp packet

oNotice the authentication is md5


75/197



Page 75of 197

Module 5 OSPF

Authored By:





76/197



Page 76of 197

History

OSPF Version 1 was specified in RFC 1131 in 1988. This protocol wasfinalized in 1989.

OSPF Version 2 (Current version). The most recent specifications arespecified in RFC 2328.

OSPF Features

Scales better than Distance Vector Routing protocols. It virtually has nopractical Hop Count Limit.

Provides Load Balancing

Introduces the concept of Areas to ease management and control traffic.

Provides Authentication.

Uses Multicast versus Broadcasts.

Convergence is Faster than in Distance Vector Routing protocols. Thereason for that is it floods the changes to all neighboring routers

simultaneously rather than in a chain.

Supports Variable Length Subnet Masking (VLSM), FLSM andSupernetting.

Provides bit-based Route summarization.

There are no periodic updates. Updates are only sent when there arechanges.

Router only send changes in updates and not the entire full tables.

OSPF uses a Cost Value, instead of hop count. Cost is based on the

speed of the link. Cost = 108/Bandwidth.

Classless Routing Protocol.

It relies on IP to deliver the Packets. Use port 89.

Open Shortest Path First (OSPF)


77/197



Page 77of 197

Areas

Area is a logical grouping of OSPF routers.

Areas divide an OSPF domain into sub-domains.

Areas allow OSPF to be extremely scalable.

Areas reduce the Memory, CPU utilization and amount of traffic in anetwork.

Most of the traffic can be restricted to within the area.

Routers within an area will have no detailed knowledge of the topologyoutside of their area.

Reduced size of the Database reduces Memory requirements for therouters.

Areas identified by a 32-bit Area ID. Can be denoted in Decimalformat(0) or Dotted format (0.0.0.0)

OSPF requires one area to be Area 0, known as the backbone area.

Backbone area or Area 0, connects all the other area to each other.

Three types of Traffic may be defined in relation to areas: Intra-area traffic consists of packets that are passed between

routers within a single area.

Inter-area traffic consists of packets that are passed between

routers in different areas. External traffic consists of packets that are passed between a

router within the OSPF domain and a router within anotherAutonomous systems.

Router Types

Routers, like Traffic, can be categorized in relation to areas.

The different Router Types are as follows: Internal Routers are routers whose interfaces all belong to the

same area. These routers have a single Link State Database.

Area Border Routers (ABR) connect one or more areas to thebackbone area and has at least one interface that belongs to thebackbone, and must maintain as separate Link State Database foreach of its connected areas. Must be a more resourceful routerthan a Internal Router.

Backbone Routers are routers with at least one interface attachedto the backbone. Although this requirement means that ABRs arealso backbone routers, but not all Backbone routers are ABRs. An

Areas and Router Types


78/197



Page 78of 197

Internal Router having all its interfaces in Area 0 is also aBackbone router.

Autonomous System Boundary Router (ASBR) are gateways forexternal traffic, injecting routes into the OSPF domain that were

learned from other protocols, such as BGP or EIGRP or RIP orIGRP. An ASBR can be located anywhere within the OSPFautonomous system. It may be an Internal, Backbone or ABR

router.


79/197



Page 79of 197

Interface:A Connection between the router and one of its attached Networks

Link State:The status of a link between two routers, that is, a routersinterface and its relationship to its neighboring routers. The link states are

advertised to other routers in a special packet called link-state advertisements(LSA).

Link State Advertisement(LSA):

Is the packet that is used by the routers to tell each other about the stateof a Link.

Certain types LSAs are flooded throughout the network and certain onesonly within the area.

The ones that are flooded within the area, are used to create a topologydatabase, also known as the Link State Database.

Router ID:

A 32-bit number assigned to each OSPF enabled router.

Its used to uniquely identify a router within an Autonomous System.

Its calculated at boot time

Its the highest Loopback address on a Router. If there is no loopbackconfigured, it will be the highest configured address on the router.

Neighbors: Two routers that have interfaces on a common network. Aneighbor relationship is usually discovered and maintained by the HelloProtocol.

Adjacent:OSPF routers form adjacency with neighboring routers in order toexchange routing information.

Flooding:A technique used to distribute LSAs between routers.

Databases or Tables:There are 3 OSPF Database or Tables:

Neighbor Database: Contains the information about Directly connectedneighbors

Link-State Database: Link States of all the routers in an Area. All routersin the same area will have an identical Link State Database.

Routing Table: Derived from the Link State Database by running theSPF(also known as the Dijkstra Algorithms).

OSPF Terminology


80/197



Page 80of 197

OSPF Defines Three Main Network Types:

Broadcast Multi-access Networks

Point-to-point Networks

Non-broadcast Multi-access (NBMA) Networks

Broadcast Networks

Networks like Ethernet, Token-Ring and FDDI are examples of BroadcastMulti-access Networks

For OSPF to exchange routes, they must establish a Neighbor Adjacencythis is done by Hello Protocol.

Hello Protocol is responsible fro establishing and maintaining neighborrelationships.

Hello packets are multicast packets

OSPF routers on broadcast networks will elect a Designated Router(DR)and Backup Designated Router(BDR).

All the other routers will establish the adjacency with the DR and BDRrather than with all the other routers on a Multi-access networks.

All routers communicate to the DR using a Multicast address of

224.0.0.6. The DR communicates with all the routers using a Multicast address of

224.0.0.5.

The Hello Packet contains the Following fields: Router ID:Routers Identification. Each router has to have a

unique ID. Hello Interval: It specifies the frequency in seconds that a router

sends hellos. In order to form a neighbor relationship, the HelloInterval on the routers has to match.

Dead Interval:It specifies the time in seconds that a router waitsto hear from a neighbor before declaring the neighbor router down.

By default, it is 4 times the hello interval. In order to form aneighbor relationship, the Dead Interval on the routers has tomatch.

Neighbors:The list of neighbors with which a bi-directionalcommunication has been established. Bi-directionalcommunication is indicated when the router sees itself listed in theneighbor hello packet.

Area ID:The ID of an area that the router belongs to. In order toform a neighbor relationship, the routers have to belong to the

same Area.

OSPF Network Types


81/197



Page 81of 197

Router Priority:An 8-bit number that indicates the priority of thisrouter when selecting a DR/BDR.

DR and BDR IP: If it is known, the IP address of the DR and BDR. Authentication Password:If authentication is enabled, two

routers must use the same password. Although OSPF routers,support authentication, the routes are still send acrossunencrypted.

Stub Area Flag:Specifies the Type of area the router is in. Theflag has to match for the routers to establish adjacency. Differenttypes of areas are discussed later.

DR and BDR election Process

For the Election process to function properly, the following conditions mustexist:

Each multi-access interface of each router has a Router Priority value,which is an 8-bit integer ranging from 0 255. The default priority onCisco Routers is 1 and can be changed on a per multi-access interfacebasis with the command IP OSPF Priority. Routers with a Priority of 0are ineligible to become a DR or BDR.

Hello packets include fields for the originating router to specify its RouterPriority and for the IP addresses of the connected interfaces of therouters it considers the DR and BDR.

When an interface first becomes active on a multi-access network, it setsthe DR and BDR fields to 0.0.0.0 in the Hello Packet.

The election process takes place after the 2-way communication hastaken place.

The Router with the Highest Priority becomes the DR and next highestpriority becomes the BDR.

In case of a tie, for either the DR or BDR, the Highest Router ID ( IPAddress) is used to break the tie.

Once a DR or BDR is chosen, even if a new router with a higher prioritycomes up, it will not become a DR or BDR.

Point-to-point Networks

Networks like T1 or a Fractional T1, that connect a pair of Routers toeach other are examples of Point-to-point networks.

Neighbors on a Point-to-point network form adjacency with each other.The destination address on Point-to-point networks is always 224.0.0.5,known as AllSPFRouters.

There are no DR or BDR router types on a Point-to-point network.


82/197



Page 82of 197

NBMA Networks

Networks like Frame Relay,X.25 or ATM, are examples of NBMAnetworks.

These type of networks do have the capability to connect more than tworouters but have no capability of broadcasts. A packet sent by one of theattached routers would not be received by all other attached routers.

OSPF routers on NBMA elect a DR and BDR and all OSPF packets areunicast.

All routers form an adjacency with the DR and BDR.

Careful selection of DR and BDR has to be done in the Hub-and-Spokeconfiguration of NBMA networks.


83/197



Page 83of 197

OSPF consists of a set of individual protocols all working together tobuild a fast and scalable interior routing protocol.

OSPF protocols are:

Hello Protocol

Exchange Protocol

Flooding Protocol

These protocols are used in different packet types. The different packettypes, their descriptions are listed in the following Table.

PacketType

Name Description ProtocolUsed

1 Hello Used to build Adjacenciesor Neighbor Relations.Carries Parameters onwhich neighbors mustagree in order to form anadjacency

Hello

2 DatabaseDescription

Used to checkSynchronization betweenrouters

Exchange

3 Link StateRequest

Used to request specificLink State records from aNeighbor Router

Exchange

4 Link StateUpdate

Used to send specific LinkState records from router torouter

Flooding

5 Link StateAdvertisements

Used to Acknowledge theabove Packet to provideReliability

All

OSPF Protocols and Packets


84/197



Page 84of 197

Frequent SPF algorithm calculation: In large networks, network changesare inevitable, so the routers would have to spend more CPU cycles forrecalculating SPF.

Large Routing Table: Each router would need to maintain at least oneentry per network, and if we have provided redundancy to some of thelinks, then more entries will be found in the routing table.

Huge Link-State Database: Remember each point-to-point link will have2 entries and so on, so one can imagine the number of entries in thatdatabase.

Solution in Hierarchical routing (multiple Areas)

In OSPF we can divide a large Area into smaller areas.

Routing still occurs between the areas called inter-area routing.

If one of the areas is having a flapping link, it will not have an effect onthe other areas, because the traffic will always be restricted to that areaIf you summarization is performed on the ABR.

Benefits

Reduced Frequency of SPF calculation: detailed routing information iskept within each area so its not necessary to flood all Link-State changesto all other areas, thus not all routers need to run the SPF calculations.

Smaller Routing Table: Because detailed routing information is keptwithin an area, the routers within an area will have smaller routing table.

Reduced Link-State Updates: LSU s can contain a variety of LSA types,instead of sending an LSU about each network within an area, you can

advertise a single or fewer summarized routes between areas to reduceoverhead associated with LSU s.

Problems with a large OSPF single

area


85/197



Page 85of 197

Routers

LSAs

Areas

Virtual-Links

Note. Hierarchical routing enables routing efficiency because it allows you to

control the type of routing information that you allow in and out of an area.

Routers In an OSPF Multi-Area

1. Internal Routers (IR):

All interfaces are in the same area.

All routers have an identical Link-State database.

2. Back Bone Routers (BBR):

All the IR s in area 0 are called the backbone routers.

They must have at least one interface in Area 0.

3. Area Border Routers (ABR):

Routers that have interfaces to multiple areas.

These routers will maintain a separate Link-State Database foreach area to which they are connected.

An exit point for an area.

ABR s can summarize the routes from one area and advertise asummarized route/s to the other areas.

4. Autonomous System Boundary Routers (ASBR):

Routers that have at least one interface into an externalnetwork such as Non-OSPF network.

These routers can redistribute Non-OSPF routes into OSPFnetworks.

Multi-Area Components


86/197



Page 86of 197

Link-State Types

1.LSA Type 1: Router Link Entry.2. LSA Type 2: Network Link Entry.

3. LSA Type 3: Summary Link Entry.4. LSA Type 4: Summary Link Entry.5. LSA Type 5: Autonomous System External Link Entry.6. LSA Type 6: MOSPF.7. LSA Type 7: NSSA.

1.LSA Type 1:

Router Link Entry. Identified by the letter O in the routing table.

Generated by all routers.

Describes the states of the routers link to the area.

Flooded within any area.

2.LSA Type 2:

Network Link Entry.

Identified by the letter O in the routing table.

Generated by DR/BDR in multi-access networks. Describes the set of routers attached to that multi-access

networks.

Flooded within any area that has DR/BDR s.

3.LSA Type 3:

Summary Link Entry

Identified by the letter IA in the routing table.

Generated by ABR.

Describes the networks in a given area to the backbone area andvise versa.

Flooded throughout the backbone area or from backbone area toother areas.

4.LSA Type 4:

Summary Network Link Entry.


87/197



Page 87of 197

LSA Type 4s are not seen in the routing table, LSA Type 4 is onlyseen in the Link-State Database.

Generated by the ASBR. In a multi-area it will be given to the ABRof the same area , and the ABR will flood the LSAs to the otherareas.

Describes reachibility to ASBR.

Flooded throughout an OSPF autonomous area except in TotallyStubby areas.

When LSA Type 4s are flooded, LSA Type 5s are seen as well.

5.LSA Type 5:

Autonomous System External Link Entry. Identified by the letter E1 or E2 in the routing table.

Generated by the ASBR.

Describes the routes to destination/s external to the OSPFautonomous system.

Flooded throughout an OSPF autonomous system except STUB,TOTALLY STUBBY, and NSSA areas.

When LSA Type 5s are flooded, LSA Type 4s are seen as well.

6.LSA Type 6:

Group Membership Link Entry.

Flooded by a Multicast OSPF Router (MOR).

Distributes group-membership location information throughoutthe routing domain.

7.LSA Type 7:

Not-So-Stubby Autonomous System External Link Entry.

Generated by ASBR in a NSSA.

These LSAs are then translated to LSA Type 5 and flooded into the

Backbone Area.

Identified by the letter N1 or N2 in the routing tables of the routersin that particular NSSA.

Describes the routes to destination/s external to the OSPFautonomous system.


88/197



Page 88of 197

E1, E2, N1, and N2 entries in the routing table:

The cost of an external route differs depending on the external typeconfiguration on the ASBR. The external-types are as follows:

E1: If a packet is E1 then the metric is calculated by adding the externalcost to the internal cost of each link the packet crosses, used only when

there are multiple ASBRs advertising a route to the same AS.

E2 (default): If a packet is E2 it will only have the external cost assigned,meaning ASBRs cost to get to an external route, used only when there isone ASBR advertising an external route/s.


89/197



Page 89of 197

Types Of Areas

1.Standard or Normal Area:

This could be any area that is not configured as Stub, TotallyStubby, or NSSA.

Can accept any LSA Types 1,2,3,4,5 .

2.Back Bone Area (transit area):

This is Area 0, area 0 must exist.

All the other areas must have a Physical or Logical connectivity to

the backbone area.

If a new area is added and it does not have direct connection to thebackbone area, a virtual link must be configured to provide theneeded connectivity to the backbone area.

The virtual Link provides the disconnected area with a logical pathto the backbone so the disconnected area can communicate withother areas.

3.Stub Area:

Does not accept information about routes external to the AS. If routers need to route to networks outside an AS, they will use a

default route (0.0.0.0).

This kind of area reduces the size of the Link-State Data

ccnp route lab

Documents