Scenario A 5.6.1: Running RIPv1 on Classful Networks
Scenario A 5.6.1: Running RIPv1 on Classful Networks
Muhammad Bagus Bintang Timur
12 615 010
II A
Jaringan Komputer
Politeknik Negeri Samarinda
mc.bintang@gmail.com
Muhammad Bagus Bintang Timur
12 615 010
II A
Jaringan Komputer
Politeknik Negeri Samarinda
mc.bintang@gmail.com
Tujuan Praktikum
1.
Mahasiswa dapat
mengetahui bagaimana caranya Verify RIP routing
using show and debug
commands
2.
Mahasiswa melakukan Observe automatic summarization at boundary
router
and Gather information about RIP processing using
the debug ip rip command.
Pendahuluan
Karakteristik RIPv1:
- merupakan distance vector routing
protocol
- classful routing protocol
- max hop count:15. 16 ->
unreachable
- periodic update: 30s
- update dikirim secara
broadcast(255.255.255.255)
- mendukung equal cost load
balancing. Secara default adalah 4 path, sedang max path: 6
- menjalankan auto-summary secara
default
- paket yang dikirim berjenis UDP
dengan nomor port 520
- bisa mengirimkan paket update
RIPv1 dan menerima paket update RIPv1 & v2
Pada saat instalasi, router-router
yang menjalankan RIP akan membroadcast paket request kepada router lain yang
isinya adalah meminta network-network yang dimiliki router lain. Router lain
yang menerima paket request akan mengirimkan respon. Setelah itu mereka baru
bertukar-tukaran info network yang dimiliki.
untuk mengaktifkan RIP:
config# router rip
untuk menyertakan directly connected
network mana saja yang akan disebar:
config-router# network {classful-network-address
| network-address}
Comman “network” punya dua fungsi
yaitu:
1. mengaktifkan RIP di interface
router yang ip-nya berada pada range classful network yang diinput
2. network yang diinput akan
disertakan pada update packet sehingga akan tersebar
Masukkan saja classful network dibandingkan
dengan network address karena RIP secara otomatis akan mengclassfulkan network
address
Passive interface adalah interface
yang hanya akan menerima update dari router lain, tetapi interface ini takkan
pernah mengirimkan update. Sehingga, interface ini bisa ditujukan agar tidak
menyebarkan update.
untuk mengaktifkan passive
interface:
config-router# passive-interface
interface-id
untuk menyebarkan static route:
config-router# redistribute
static
config-router# default-information
originate
Router akan secara otomatis
menjalankan route summarization pada boundary router.
Boundary router adalah router yang
interfacenya memiliki ip address yang berbeda secara classful network
Auto-summary berjalan secara default
dan tidak dapat di non-aktifkan
Langkah Praktikum
Scenario
A: Running RIPv1 on Classful Networks
Gambar 6.1
Addresing
Table
Device
|
Interface
|
IP Address
|
Subnet Mask
|
Default Gateway
|
R1
|
Fa0/0
|
192.168.1.1
|
255.255.255.0
|
N/A
|
S0/0/0
|
192.168.2.1
|
255.255.255.0
|
N/A
|
|
R2
|
Fa0/0
|
192.168.3.1
|
255.255.255.0
|
N/A
|
S0/0/0
|
192.168.2.2
|
255.255.255.0
|
N/A
|
|
S0/0/1
|
192.168.4.2
|
255.255.255.0
|
N/A
|
|
R3
|
Fa0/0
|
192.168.5.1
|
255.255.255.0
|
N/A
|
S0/0/1
|
192.168.4.1
|
255.255.255.0
|
N/A
|
|
PC1
|
NIC
|
192.168.1.10
|
255.255.255.0
|
192.168.1.1
|
PC2
|
NIC
|
192.168.3.10
|
255.255.255.0
|
192.168.3.1
|
PC3
|
NIC
|
192.168.5.10
|
255.255.255.0
|
192.168.5.1
|
Pertama menkonfigurasi
semua router dan kemudian memberi IP address yang sudah ada ke setiap PC, pada
saat menkonfigurasi router pada configurasi routing menggunakan dynamic routing
dan menggunakan classfull network address.
Kedua melakukan test
apakah semua sudah terhubung dalam satu jaringan perhatikan gambar berikut :
1. melakukan test pada ketiga router apakah sudah terhubung
dengan baik atau tidak
R1#ping 192.168.2.2 (R2)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.2, timeout is
2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max
= 31/31/32 ms
R1#ping 192.168.4.2 (R2)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.4.2, timeout is
2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max
= 31/34/47 ms
R1#ping 192.168.4.1 (R3)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.4.1, timeout is
2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max
= 49/59/63 ms
2.
melakukan tes pada setiap PC yang ada
PC1 ke PC2
PC1 ke PC3
Catatan : untuk ping ke PC lain saya tidak
masukkan agar mengurangi besarnya ukuran memori file pada saat di upload di
blog, gambar di atas sudah mewakili bahwa semua PC sudah terhubung.
Setelah melakukan test ternyata semua item
sudah terhubung dalam satu jaringan.
Hasil Praktikum
Setelah semua sudah dilakukan seperti inilah hasilnya :
1.
menverifikasi semua routing sudah masuk dan mengetahui
informasi pada router dengan menggunakan command "show ip route",
"show ip protocols", "debug ip rip".
R1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M -
mobile, B - BGP
D - EIGRP,
EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF
NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF
external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS,
L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* -
candidate default, U - per-user static route, o - ODR
P - periodic
downloaded static route
Gateway of last resort is not set
C 192.168.1.0/24
is directly connected, FastEthernet0/0
C 192.168.2.0/24
is directly connected, Serial0/0/0
R
192.168.3.0/24 [120/1] via 192.168.2.2, 00:00:23, Serial0/0/0
R
192.168.4.0/24 [120/1] via 192.168.2.2, 00:00:23, Serial0/0/0
R
192.168.5.0/24 [120/2] via 192.168.2.2, 00:00:23, Serial0/0/0
R2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M -
mobile, B - BGP
D - EIGRP,
EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF
NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF
external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS,
L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* -
candidate default, U - per-user static route, o - ODR
P - periodic
downloaded static route
Gateway of last resort is not set
R
192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:04, Serial0/0/0
C 192.168.2.0/24
is directly connected, Serial0/0/0
C 192.168.3.0/24
is directly connected, FastEthernet0/0
C 192.168.4.0/24
is directly connected, Serial0/0/1
R
192.168.5.0/24 [120/1] via 192.168.4.1, 00:00:23, Serial0/0/1
R3#show ip route
Codes: C - connected, S - static, I - IGRP, R -
RIP, M - mobile, B - BGP
D
- EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1
- OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1
- OSPF external type 1, E2 - OSPF external type 2, E - EGP
i
- IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
*
- candidate default, U - per-user static route, o - ODR
P
- periodic downloaded static route
Gateway of last resort is not set
R
192.168.1.0/24 [120/2] via 192.168.4.2, 00:00:13, Serial0/0/1
R
192.168.2.0/24 [120/1] via 192.168.4.2, 00:00:13, Serial0/0/1
R
192.168.3.0/24 [120/1] via 192.168.4.2, 00:00:13, Serial0/0/1
C
192.168.4.0/24 is directly connected, Serial0/0/1
C
192.168.5.0/24 is directly connected, FastEthernet0/0
R1#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in
15 seconds
Invalid after 180 seconds, hold down 180,
flushed after 240
Outgoing update filter list for all interfaces
is not set
Incoming update filter list for all interfaces
is not set
Redistributing: rip
Default version control: send version 1,
receive any version
Interface Send Recv
Triggered RIP Key-chain
FastEthernet0/0 1 2 1
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
192.168.1.0
192.168.2.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
192.168.2.2
120 00:00:07
R2#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 0
seconds
Invalid after 180 seconds, hold down 180,
flushed after 240
Outgoing update filter list for all interfaces
is not set
Incoming update filter list for all interfaces
is not set
Redistributing: rip
Default version control: send version 1,
receive any version
Interface Send Recv
Triggered RIP Key-chain
FastEthernet0/0
1 2 1
Serial0/0/1 1
2 1
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
192.168.2.0
192.168.3.0
192.168.4.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
192.168.2.1 120 00:00:05
192.168.4.1
120 00:00:11
R3#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 2
seconds
Invalid after 180 seconds, hold down 180, flushed
after 240
Outgoing update filter list for all interfaces
is not set
Incoming update filter list for all interfaces
is not set
Redistributing: rip
Default version control: send version 1,
receive any version
Interface Send Recv
Triggered RIP Key-chain
FastEthernet0/0 1 2 1
Serial0/0/1 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
192.168.4.0
192.168.5.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
192.168.4.2
120 00:00:01
R1#debug ip rip
RIP protocol debugging is on
R1#RIP: sending
v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1)
RIP: build update entries
network 192.168.2.0 metric 1
network 192.168.3.0 metric 2
network 192.168.4.0 metric 2
network 192.168.5.0 metric 3
RIP: sending
v1 update to 255.255.255.255 via Serial0/0/0 (192.168.2.1)
RIP: build update entries
network 192.168.1.0 metric 1
RIP: received v1 update from 192.168.2.2 on
Serial0/0/0
192.168.3.0 in 1 hops
192.168.4.0 in 1 hops
192.168.5.0 in 2 hops
R2#debug ip rip
RIP protocol debugging is on
R2#RIP: received v1 update from 192.168.2.1 on
Serial0/0/0
192.168.1.0 in 1 hops
RIP: sending
v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.3.1)
RIP: build update entries
network 192.168.1.0 metric 2
network 192.168.2.0 metric 1
network 192.168.4.0 metric 1
network 192.168.5.0 metric 2
RIP: sending
v1 update to 255.255.255.255 via Serial0/0/1 (192.168.4.2)
RIP: build update entries
network 192.168.1.0 metric 2
network 192.168.2.0 metric 1
network 192.168.3.0 metric 1
RIP: sending
v1 update to 255.255.255.255 via Serial0/0/0 (192.168.2.2)
RIP: build update entries
network 192.168.3.0 metric 1
network 192.168.4.0 metric 1
network 192.168.5.0 metric 2
RIP: received v1 update from 192.168.4.1 on
Serial0/0/1
192.168.5.0 in 1 hops
RIP: received v1 update from 192.168.2.1 on
Serial0/0/0
192.168.1.0 in 1 hops
R3#debug ip rip
RIP protocol debugging is on
R3#RIP: received v1 update from 192.168.4.2 on
Serial0/0/1
192.168.1.0 in 2 hops
192.168.2.0 in 1 hops
192.168.3.0 in 1 hops
RIP: sending
v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.5.1)
RIP: build update entries
network 192.168.1.0 metric 3
network 192.168.2.0 metric 2
network 192.168.3.0 metric 2
network 192.168.4.0 metric 1
RIP: sending
v1 update to 255.255.255.255 via Serial0/0/1 (192.168.4.1)
RIP: build update entries
Comments
Post a Comment