Dynamic Routing Protocols – Lab Exercise
Dynamic Routing Protocols – Lab Exercise
Pada lab ini anda akan meneliti fitur dimana ini adalah umum untuk semua Interior Gateway Protocols. Termasuk konfigurasi dasar dari variasi IGP tetapi tidak menjadi focus pada lab exercise ini. Konfigurasi untuk setiap IGP akan dilakukan secara detail nantinya.
Lab Topology
Routing Protocol Updates
1) Enter the commands below on each router to provision a basic RIPv1 configuration and enable RIP on every interface.
router rip
network 10.0.0.0
no auto-summary
R1(config)#router rip
R1(config-router)#network 10.0.0.0
R1(config-router)#no auto-summary
R2(config)#router rip
R2(config-router)#network 10.0.0.0
R2(config-router)#no auto-summary
R3(config)#router rip
R3(config-router)#network 10.0.0.0
R3(config-router)#no auto-summary
R4(config)#router rip
R4(config-router)#network 10.0.0.0
R4(config-router)#no auto-summary
R5(config)#router rip
R5(config-router)#network 10.0.0.0
R5(config-router)#no auto-summary
2) Debug the routing protocol updates on R1 with the ‘debug ip rip’ command. Observe the updates being sent and received. What kind of traffic is used (unicast, broadcast or multicast)?
R1#debug ip rip
RIP: sending v1 update to 255.255.255.255 via FastEthernet1/0 (10.0.2.1)
RIP: build update entries
network 10.0.0.0 metric 1
network 10.0.1.0 metric 1
network 10.0.3.0 metric 1
network 10.1.0.0 metric 2
network 10.1.1.0 metric 3
network 10.1.2.0 metric 3
network 10.1.3.0 metric 2
Update routing dikirimkan menggunakan broadcast address 255.255.255.255. Seluruh host pada subnet harus memproses packet.
3) Enter the commands below to enable RIPv2 on every router.
router rip
version 2
R1(config)#router rip
R1(config-router)#version 2
R2(config)#router rip
R2(config-router)#version 2
R3(config)#router rip
R3(config-router)#version 2
R4(config)#router rip
R4(config-router)#version 2
R5(config)#router rip
R5(config-router)#version 2
4) What kind of traffic is used for the updates now?
RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.3.2)
RIP: build update entries
10.0.0.0/24 via 0.0.0.0, metric 2, tag 0
10.0.1.0/24 via 0.0.0.0, metric 2, tag 0
10.0.2.0/24 via 0.0.0.0, metric 2, tag 0
10.0.3.0/24 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (10.0.3.2)
RIP: build update entries
10.1.1.0/24 via 0.0.0.0, metric 2, tag 0
10.1.2.0/24 via 0.0.0.0, metric 2, tag 0
10.1.3.0/24 via 0.0.0.0, metric 1, tag 0
Dengan RIP versi 2, update routing dilakukan dengan menggunakan multicast address 224.0.0.9.
5) Turn off all debugging on R1.
R1(config)#no debug ip rip
6) Check that RIP routes have been added to R1 and it has a route to every subnet in the lab.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
R 10.1.0.0/24 [120/1] via 10.0.0.2, 00:00:30, FastEthernet0/0
R 10.1.1.0/24 [120/2] via 10.0.0.2, 00:00:30, FastEthernet0/0
[120/2] via 10.0.3.2, 00:00:08, FastEthernet1/1
R 10.1.2.0/24 [120/2] via 10.0.3.2, 00:00:08, FastEthernet1/1
R 10.1.3.0/24 [120/1] via 10.0.3.2, 00:00:08, FastEthernet1/1
7) Why are there two routes to the 10.1.1.0/24 network in the routing table?
Karena jarak R1 menuju subnet 10.1.1.0 dengan via 10.0.0.2 dan 10.0.3.2 sama-sama melewati 2 hop.
Comparing Routing Protocols
8) View the RIP database on R1.
R1#show ip rip database
10.0.0.0/24 auto-summary
10.0.0.0/24 directly connected, FastEthernet0/0
10.0.1.0/24 auto-summary
10.0.1.0/24 directly connected, FastEthernet0/1
10.0.2.0/24 auto-summary
10.0.2.0/24 directly connected, FastEthernet1/0
10.0.3.0/24 auto-summary
10.0.3.0/24 directly connected, FastEthernet1/1
10.1.0.0/24 auto-summary
10.1.0.0/24
[1] via 10.0.0.2, 00:00:03, FastEthernet0/0
10.1.1.0/24 auto-summary
10.1.1.0/24
[2] via 10.0.0.2, 00:00:03, FastEthernet0/0 [2] via 10.0.3.2, 00:00:09, FastEthernet1/1
10.1.2.0/24 auto-summary
10.1.2.0/24
[2] via 10.0.3.2, 00:00:09, FastEthernet1/1
10.1.3.0/24 auto-summary
10.1.3.0/24
[1] via 10.0.3.2, 00:00:09, FastEthernet1/1
9) Enter the commands below on each router to provision a basic OSPF configuration and enable OSPF on every interface.
router ospf 1
network 10.0.0.0 0.255.255.255 area 0
R1(config)#router ospf 1
R1(config-router)#network 10.0.0.0 0.255.255.255 area 0
R2(config)#router ospf 1
R2(config-router)#network 10.0.0.0 0.255.255.255 area 0
R3(config)#router ospf 1
R3(config-router)#network 10.0.0.0 0.255.255.255 area 0
R4(config)#router ospf 1
R4(config-router)#network 10.0.0.0 0.255.255.255 area 0
R5(config)#router ospf 1
R5(config-router)#network 10.0.0.0 0.255.255.255 area 0
10) Give OSPF time to converge. Are RIP routes included in the routing table on R1 now? Why or why not?
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
O 10.1.0.0/24 [110/2] via 10.0.0.2, 00:01:27, FastEthernet0/0
O 10.1.1.0/24 [110/3] via 10.0.0.2, 00:01:10, FastEthernet0/0
O 10.1.2.0/24 [110/4] via 10.0.0.2, 00:01:10, FastEthernet0/0
O 10.1.3.0/24 [110/13] via 10.0.0.2, 00:01:10, FastEthernet0/0
Routing tabel yang semula protocolnya RIP tergantikan oleh OSPF. Karena Administrative Distance OSPF (110) lebih baik dibandingkan RIP (120). Maka secara otomatis, router akan memprioritaskan routing protocol OSPF sebagai routing utamanya.
11) Why is there now only one route to the 10.1.1.0/24 network?
Karena OSPF menggunakan cost sebagai metric-nya. Interface R5 yaitu jalur yang ada di bawah terkonfigurasi dengan bandwidth 10Mbps. Semua interface router pada jalur atas pada topologi adalah default bandwidth 100Mbps. Maka jalur inilah yang diprioritaskan untuk menjadi jalur OSPF dan seluruh trafficnya melalui via 10.0.0.2.
R5#show run | section interface
interface FastEthernet0/0
bandwidth 10000
ip address 10.1.3.2 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
bandwidth 10000
ip address 10.0.3.2 255.255.255.0
duplex auto
speed auto
R2#show run | section interface
interface FastEthernet0/0
ip address 10.0.0.2 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 10.1.0.2 255.255.255.0
duplex auto
speed auto
12) Disable interface FastEthernet 0/0 on R2. What do you expect to happen to R1’s routing table?
R2(config)#int f0/0
R2(config-if)#shut
Jalur routing yang seluruhnya melalui hop via 10.0.0.2 berubah menjadi 10.0.3.2. Karena jalur bagian atas terputus di bagian interface dari R2. Dikarenakan jalur di bawah masih ada konfigurasi dari OSPF. Maka secara otomatis rute akan dialihkan melalui jalur bawah.
13) Verify your expected changes to R1’s routing table.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 10 subnets, 2 masks
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
O 10.1.0.0/24 [110/22] via 10.0.3.2, 00:00:35, FastEthernet1/1
O 10.1.1.0/24 [110/21] via 10.0.3.2, 00:00:35, FastEthernet1/1
O 10.1.2.0/24 [110/21] via 10.0.3.2, 00:00:35, FastEthernet1/1
O 10.1.3.0/24 [110/20] via 10.0.3.2, 00:00:35, FastEthernet1/1
14) Aside from the next hop address, what else has changed on the routing table?
Rute yang baru memiliki metric lebih tinggi. Inilah mengapa rute ini sebelumnya tidak muncul disaat jalur via R2 masih bekerja.
15) View the OSPF database on R1 with the ‘show ip ospf database’ command. What is different between it and the RIP database? Why?
RIP adalah routing protocol dengan Distance Vector. Maka dia hanya tahu neighbors dengan directly connected dan daftar network tetangga yang sudah advertised.
Sementara OSPF adalah routing protocol dengan Link State. Maka dia bisa tahu status dari seluruh link pada router-router yang ada di areanya
R1#show ip ospf database
OSPF Router with ID (10.0.3.1) (Process ID 1)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
10.0.3.1 10.0.3.1 628 0x80000007 0x00775c 3
10.1.0.2 10.1.0.2 628 0x80000005 0x00c15c 1
10.1.1.2 10.1.1.2 299 0x80000005 0x003ab7 2
203.0.113.1 203.0.113.1 296 0x80000006 0x00dd86 3
10.1.3.2 10.1.3.2 294 0x80000005 0x00824f 2
Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
10.1.0.1 10.1.1.2 307 0x80000002 0x00f4d8
10.1.1.1 203.0.113.1 301 0x80000003 0x00207c
10.1.3.1 203.0.113.1 296 0x80000004 0x0055ff
10.0.3.2 10.1.3.2 296 0x80000002 0x00b93e
Routing Protocol Metrics and Administrative Distance
16) Enter the command below to remove OSPF on every router
no router ospf 1
R1(config)#no router ospf 1
R2(config)#no router ospf 1
R3(config)#no router ospf 1
R4(config)#no router ospf 1
R5(config)#no router ospf 1
17) Will R1 still have connectivity to R4?
R1 masih bisa terhubung karena masih ada jalur bawah atau R5 yang terkonfigurasi dengan protocol routing RIP.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 10 subnets, 2 masks
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
R 10.1.0.0/24 [120/3] via 10.0.3.2, 00:00:13, FastEthernet1/1
R 10.1.1.0/24 [120/2] via 10.0.3.2, 00:00:13, FastEthernet1/1
R 10.1.2.0/24 [120/2] via 10.0.3.2, 00:00:13, FastEthernet1/1
R 10.1.3.0/24 [120/1] via 10.0.3.2, 00:00:13, FastEthernet1/1
18) What is the metric to the 10.1.1.0/24 network on R1?
Metric dengan 2 hop
19) Why is there only one route on R1 to the 10.1.1.0/24 network now?
Karena link R1 menuju R2 masih terputus
20) Make the required change so that there are two routes to the 10.1.1.0/24 network in the routing table on R1.
R2(config)#int f0/0
R2(config-if)#no shut
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
R 10.1.0.0/24 [120/1] via 10.0.0.2, 00:00:24, FastEthernet0/0
R 10.1.1.0/24 [120/2] via 10.0.3.2, 00:00:04, FastEthernet1/1
[120/2] via 10.0.0.2, 00:00:24, FastEthernet0/0
R 10.1.2.0/24 [120/2] via 10.0.3.2, 00:00:04, FastEthernet1/1
R 10.1.3.0/24 [120/1] via 10.0.3.2, 00:00:04, FastEthernet1/1
21) Enter the commands below on each router to provision a basic EIGRP configuration and enable EIGRP on every interface.
router eigrp 100
no auto-summary
network 10.0.0.0 0.255.255.255
R1(config)#router eigrp 100
R1(config-router)#no auto-summary
R1(config-router)#network 10.0.0.0 0.255.255.255
R2(config)#router eigrp 100
R2(config-router)#no auto-summary
R2(config-router)#network 10.0.0.0 0.255.255.255
R3(config)#router eigrp 100
R3(config-router)#no auto-summary
R3(config-router)#network 10.0.0.0 0.255.255.255
R4(config)#router eigrp 100
R4(config-router)#no auto-summary
R4(config-router)#network 10.0.0.0 0.255.255.255
R5(config)#router eigrp 100
R5(config-router)#no auto-summary
R5(config-router)#network 10.0.0.0 0.255.255.255
22) What changes do you expect to see in the routing tables? Why?
Protocol routing RIP seluruhnya akan digantikan dengan EIGRP. Karena Administrative Distance EIGRP (90) lebih baik dibandingkan dengan RIP (120). Maka secara otomatis protocol routing EIGRP menjadi yang lebih diutamakan.
23) Verify the changes to the routing table on R1.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
D 10.1.0.0/24 [90/30720] via 10.0.0.2, 00:01:18, FastEthernet0/0
D 10.1.1.0/24 [90/33280] via 10.0.0.2, 00:01:08, FastEthernet0/0
D 10.1.2.0/24 [90/35840] via 10.0.0.2, 00:01:00, FastEthernet0/0
D 10.1.3.0/24 [90/261120] via 10.0.3.2, 00:00:54, FastEthernet1/1
24) What is the metric to the 10.1.1.0/24 network on R1?
Metricnya adalah 33280. Perhitungannya adalah metric = [K1 * bandwidth + (K2 * bandwidth) / (256 - load) + K3 * delay] * [K5 / (reliability + K4)].
25) Why is there only one route to the 10.1.1.0/24 network on R1?
Perhitungan metric diambil salah satunya dari total bandwidth. Dikarenakan network 10.1.1.0 pada jalur atas nilainya lebih baik dibandingkan dengan jalur bawah, maka jalur yang digunakan hanya jalur atas saja.
26) Disable RIP and EIGRP on R5 with the commands below.
R5(config)#no router rip
R5(config)#no router eigrp 100
R5(config)#no router rip
R5(config)#no router eigrp 100
27) Configure the network so that there is still connectivity between all subnets if the link between R1 and R2 goes down. Accomplish this with six commands. Do not enable EIGRP on R5 but note that the routing protocol is expected to be enabled there in the future.
Floating static routes perlu ditambahkan sebagai backup dari rute EIGRP. Kita butuh memastikan rute EIGRP sebagai yang utama saat bersedia. Maka kita set AD static route menjadi 95 lebih tinggi daripada AD EIGRP 90.
R1(config)#ip route 10.1.0.0 255.255.0.0 10.0.3.2 95
R2(config)#ip route 10.0.0.0 255.255.0.0 10.1.0.1 95
R3(config)#ip route 10.0.0.0 255.255.0.0 10.1.1.1 95
R4(config)#ip route 10.0.0.0 255.255.0.0 10.1.3.2 95
R5(config)#ip route 10.0.0.0 255.255.0.0 10.0.3.1 95
R5(config)#ip route 10.1.0.0 255.255.0.0 10.1.3.1 95
R5 tidak menjalankan EIGRP sehingga saat ini tidak perlu mengatur Administrative Distance untuk rutenya ke 95. Namun AD tetap diperlukan karena untuk mencegah rute static float menjadi prioritas saat EIGRP diaktifkan nanti.
Summary route perlu digunakan untuk menyelesaikan tugas dalam enam perintah.
28) What changes do you expect to see to the routing table on R1?
Summary route akan ditambahkan ke tabel routing namun tidak akan digunakan karena panjang prefixnya /16 yang dibandingkan dengan EIGRP dengan prefix /24.
Jika floating static route individual ditambahkan ke setiap network tujuan dengan prefix /24. Maka kemudian tidak akan muncul pada routing table karena EIGRP memiliki AD yang lebih baik.
29) Verify the changes to the routing table on R1.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 13 subnets, 3 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
S 10.1.0.0/16 [95/0] via 10.0.3.2
D 10.1.0.0/24 [90/30720] via 10.0.0.2, 05:16:22, FastEthernet0/0
D 10.1.1.0/24 [90/33280] via 10.0.0.2, 05:16:22, FastEthernet0/0
D 10.1.2.0/24 [90/35840] via 10.0.0.2, 05:16:22, FastEthernet0/0
D 10.1.3.0/24 [90/266240] via 10.0.0.2, 05:16:22, FastEthernet0/0
30) Verify that traffic from PC1 to PC3 still goes via R2.
31) Shut down interface FastEthernet 0/0 on R2.
R2(config)#int f0/0
R2(config-if)#shutdown
32) What changes do you expect to see on R1’s routing table?
Rute EIGRP akan dihilangkan
33) Verify the changes to the routing table on R1.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 7 subnets, 3 masks
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
S 10.1.0.0/16 [95/0] via 10.0.3.2
34) Verify connectivity between PC1 and PC3.
35) Verify the traffic goes via R5.
36) Bring interface FastEthernet 0/0 on R2 back up.
R2(config)#int f0/0
R2(config-if)#no shutdown
37) Enter the commands below on R5 to provision a basic EIGRP configuration and enable EIGRP on every interface.
R5(config)#router eigrp 100
R5(config-router)#no auto-summary
R5(config-router)#network 10.0.0.0 0.255.255.255
R5(config)#router eigrp 100
R5(config-router)#no auto-summary
R5(config-router)#network 10.0.0.0 0.255.255.255
Loopback Interfaces
38) Configure loopback interface 0 on each router. Assign the IP address 192.168.0.x/32, where ‘x’ is the router number (for example 192.168.0.3/32 on R3.)
R1(config)#int lo0
R1(config-if)#ip address 192.168.0.1 255.255.255.255
R2(config)#int lo0
R2(config-if)#ip address 192.168.0.2 255.255.255.255
R3(config)#int lo0
R3(config-if)#ip address 192.168.0.3 255.255.255.255
R4(config)#int lo0
R4(config-if)#ip address 192.168.0.4 255.255.255.255
R5(config)#int lo0
R5(config-if)#ip address 192.168.0.5 255.255.255.255
39) Is there connectivity to the loopback interfaces from the PCs? Why or why not?
PC tidak dapat terkoneksi ke semua interface loopback karena tidak ada pada routing table. Tidak ada pada routing table dikarenakan IP address interface loopback diluar dari network yang sudah dikonfigurasi sebelumnya.
PC hanya dapat terkoneksi dengan interface loopback pada router yang berada pada satu subnet.
40) Enter the commands below on each router to include the loopback interfaces in EIGRP.
R1(config)#router eigrp 100
R1(config-router)#network 192.168.0.0 0.0.0.255
R1(config)#router eigrp 100
R1(config-router)#network 192.168.0.0 0.0.0.255
R2(config)#router eigrp 100
R2(config-router)#network 192.168.0.0 0.0.0.255
R3(config)#router eigrp 100
R3(config-router)#network 192.168.0.0 0.0.0.255
R4(config)#router eigrp 100
R4(config-router)#network 192.168.0.0 0.0.0.255
R5(config)#router eigrp 100
R5(config-router)#network 192.168.0.0 0.0.0.255
41) Verify the loopback interfaces are in the routing table on R1.
R1#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 13 subnets, 3 masks
C 10.0.0.0/24 is directly connected, FastEthernet0/0
L 10.0.0.1/32 is directly connected, FastEthernet0/0
C 10.0.1.0/24 is directly connected, FastEthernet0/1
L 10.0.1.1/32 is directly connected, FastEthernet0/1
C 10.0.2.0/24 is directly connected, FastEthernet1/0
L 10.0.2.1/32 is directly connected, FastEthernet1/0
C 10.0.3.0/24 is directly connected, FastEthernet1/1
L 10.0.3.1/32 is directly connected, FastEthernet1/1
S 10.1.0.0/16 [95/0] via 10.0.3.2
D 10.1.0.0/24 [90/30720] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 10.1.1.0/24 [90/33280] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 10.1.2.0/24 [90/35840] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 10.1.3.0/24 [90/261120] via 10.0.3.2, 00:01:36, FastEthernet1/1
192.168.0.0/32 is subnetted, 5 subnets
C 192.168.0.1/32 is directly connected, Loopback0
D 192.168.0.2/32 [90/156160] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 192.168.0.3/32 [90/158720] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 192.168.0.4/32 [90/161280] via 10.0.0.2, 00:13:00, FastEthernet0/0
D 192.168.0.5/32 [90/386560] via 10.0.3.2, 00:01:36, FastEthernet1/1
42) Verify connectivity from PC1 to the loopback interface on R5.
Adjacencies and Passive Interfaces
43) Enter the command below to verify that R1 has established EIGRP adjacencies with R2 and R5.
R1#show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(100)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.0.3.2 Fa1/1 14 00:17:21 33 198 0 16
0 10.0.0.2 Fa0/0 11 00:19:21 36 216 0 32
R1#show ip eigrp neighbors
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.0.0.2 Fa0/0 11 00:21:42 40 1000 0 22
1 10.0.3.2 Fa1/1 10 00:10:17 40 1000 0 29
44) Verify that traffic from R5 to the directly connected interfaces on R1 goes via the FastEthernet 0/1 interface.
R5#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 3 masks
S 10.0.0.0/16 [95/0] via 10.0.3.1
D 10.0.0.0/24 [90/261120] via 10.0.3.1, 00:12:21, FastEthernet0/1
D 10.0.1.0/24 [90/261120] via 10.0.3.1, 00:12:21, FastEthernet0/1
D 10.0.2.0/24 [90/261120] via 10.0.3.1, 00:12:21, FastEthernet0/1
C 10.0.3.0/24 is directly connected, FastEthernet0/1
L 10.0.3.2/32 is directly connected, FastEthernet0/1
S 10.1.0.0/16 [95/0] via 10.1.3.1
D 10.1.0.0/24 [90/263680] via 10.0.3.1, 00:12:21, FastEthernet0/1
[90/263680] via 10.1.3.1, 00:12:21, FastEthernet0/0
D 10.1.1.0/24 [90/261120] via 10.1.3.1, 00:12:21, FastEthernet0/0
D 10.1.2.0/24 [90/261120] via 10.1.3.1, 00:12:21, FastEthernet0/0
C 10.1.3.0/24 is directly connected, FastEthernet0/0
L 10.1.3.2/32 is directly connected, FastEthernet0/0
192.168.0.0/32 is subnetted, 5 subnets
D 192.168.0.1/32 [90/386560] via 10.0.3.1, 00:12:21, FastEthernet0/1
D 192.168.0.2/32 [90/389120] via 10.0.3.1, 00:12:21, FastEthernet0/1
D 192.168.0.3/32 [90/389120] via 10.1.3.1, 00:12:21, FastEthernet0/0
D 192.168.0.4/32 [90/386560] via 10.1.3.1, 00:12:21, FastEthernet0/0
C 192.168.0.5/32 is directly connected, Loopback0
45) Enter the commands below to configure the loopback interface and the link to R5 as passive interfaces on R1.
R1(config-if)#router eigrp 100
R1(config-router)#passive-interface loopback0
R1(config-router)#passive-interface fastethernet1/1
R1(config)#router eigrp 100
R1(config-router)#passive-interface loopback0
R1(config-router)#passive-interface fastEthernet1/1
46) What changes do you expect to see in the routing table on R5 and why?
Adjajency EIGRP antara R1 dan R5 akan down. Semua rute EIGRP via R1 akan dihilangkan dari routing table dan digantikan dengan rute via R4. Mengkonfigurasi interface loopback sebagai passive interface di R1 tidak akan mempengaruhi routing table.
R1(config-router)#
%DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 10.0.3.2 (FastEthernet1/1) is down: holding time expired
47) Verify the expected changes to the routing table on R5.
R5#show ip route | begin Gate
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 12 subnets, 3 masks
S 10.0.0.0/16 [95/0] via 10.0.3.1
D 10.0.0.0/24 [90/266240] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 10.0.1.0/24 [90/268800] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 10.0.2.0/24 [90/268800] via 10.1.3.1, 01:11:44, FastEthernet0/0
C 10.0.3.0/24 is directly connected, FastEthernet0/1
L 10.0.3.2/32 is directly connected, FastEthernet0/1
S 10.1.0.0/16 [95/0] via 10.1.3.1
D 10.1.0.0/24 [90/263680] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 10.1.1.0/24 [90/261120] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 10.1.2.0/24 [90/261120] via 10.1.3.1, 01:11:44, FastEthernet0/0
C 10.1.3.0/24 is directly connected, FastEthernet0/0
L 10.1.3.2/32 is directly connected, FastEthernet0/0
192.168.0.0/32 is subnetted, 5 subnets
D 192.168.0.1/32 [90/394240] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 192.168.0.2/32 [90/391680] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 192.168.0.3/32 [90/389120] via 10.1.3.1, 01:11:44, FastEthernet0/0
D 192.168.0.4/32 [90/386560] via 10.1.3.1, 01:11:44, FastEthernet0/0
C 192.168.0.5/32 is directly connected, Loopback0
Comments
Post a Comment