KONFIGURASI ROUTING DINAMIK RIPV2 DI CISCO

Assalamu'alaikum sobat IT semua,gimana kabar kalian ?? Jika sebelumnya saya telah membahass routing statik di cisco maka kali ini kita akan membahas materi RIPv2 nah sebelum ke config ada baiknya teman pahami dulu apa itu RIP.

Kemudian sebelum keconfig ,kita ketahui dulu Konsep dasar kemudain apa saja kelebihan dan kekurangan dari Routing RIPv2 ini berikut penjelasananya.

Konsep Dasar

Keuntungan menggunakan dynamic routing dibandingkan static routing:

• Tidak perlu tahu network destination
• Perlu melakukan advertise network yang terhubung langsung
• Update perubahan topologi secara dinamis
• Pekerjaan network admin jadi berkurang
• Digunakan di industri besar
• Neighbor router melakukan pertukaran informasi routing dan membangun routing table secara otomatis
• Lebih mudah dibandingkan menggunakan static routing

RIPv2

Berikut catatan untuk RIPv2

• Open standar protocol (Cisco atau non-Cisco)
• Classless routing protocol (support default atau sub-networks)
• Mendukung VLSM
• Mendukung Autentikasi
• Menggunakan multicast address 224.0.0.9
• Administrative distance: 120
• Metric: hop count (terbaik = yang paling kecil)
• Hop ke-16 unreachable
• Load balancing 4 equal path
• Digunakan untuk organisasi kecil
• Update secara periodic dan pertukaran keseleruhan informasi routing tabel setiap 30 second

Dua langkah mudah setting routing protocol dinamis secara umum:

1. Pilih routing protocol

2. Advertise directly connected network (jaringan yang terhubung langsung dengan router)

Router(config)# router Router(config-router)#rip version 2 Router(config-router)#network <Network ID> Router(config-router)#network <Network ID> Router(config-router)#no auto-summary

network <Network-ID> : untuk advertise network yang terhubung langsung dengan router

(directly connected network).

Keuntungan RIPv2

• Mudah dikonfigurasi
• Tidak memerlukan design seperti OSPF
• Tidak kompleks
• Less overhead

Kerugian RIPv2

• Utilisasi bandwidth sangat tinggi karena diperlukan untuk broadcast setiap 30 second (RIPv1)
• Terbatas pada jumlah hop (bukan bandwidth)
• Tidak scalable, hop count hanya 15
• Konvergensi rendah

Waktu konvergensi: waktu yang dibutuhkan oleh router untuk menggunakan route alternative ketika best route down.

Topologi:

device	Interface	IP address
RT-0	Fa0/0	192.168.1.254/24
	Fa1/0	12.12.12.1/24
RT-1	Fa0/0	192.168.2.254/24
	Fa1/0	12.12.12.2/24
PC0	Fa0	192.168.1.1/24
PC1	Fa0	192.168.2.1/24

Tampilkan routing table sebelum disetting RIPv2 di R1

R1#sh 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 12.0.0.0/24 is subnetted, 1 subnets C 12.12.12.0 is directly connected, FastEthernet1/0 172.16.0.0/24 is subnetted, 2 subnets C 172.16.1.0 is directly connected, Loopback1 C 172.16.2.0 is directly connected, Loopback2 C 192.168.1.0/24 is directly connected, FastEthernet0/0 R1#

Tampilkan routing table sebelum disetting RIPv2 di R2

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 12.0.0.0/24 is subnetted, 1 subnets C 12.12.12.0 is directly connected, FastEthernet1/0 172.16.0.0/24 is subnetted, 2 subnets C 172.16.3.0 is directly connected, Loopback0 C 172.16.4.0 is directly connected, Loopback1 C 192.168.2.0/24 is directly connected, FastEthernet0/0 R2#

Setting RIPv2 di R1

Command untuk mensetting RIPv2.

R1(config)#router rip R1(config-router)#version 2 R1(config-router)#network 12.12.12.0 R1(config-router)#network 192.168.1.0 R1(config-router)#no auto-summary R1(config-router)#

Setting RIPv2 di R2

Command untuk mensetting RIPv2.

R2(config)#router rip R2(config-router)#version 2 R2(config-router)#network 12.12.12.0 R2(config-router)#network 192.168.2.0 R2(config-router)#no auto-summary R2(config-router)#

Verifikasi

Tampilkan routing table setelah disetting RIPv2 di R1

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 12.0.0.0/24 is subnetted, 1 subnets C 12.12.12.0 is directly connected, FastEthernet1/0 172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks R 172.16.0.0/16 [120/1] via 12.12.12.2, 00:00:55, FastEthernet1/0 C 172.16.1.0/24 is directly connected, Loopback1 C 172.16.2.0/24 is directly connected, Loopback2 R 172.16.3.0/24 [120/1] via 12.12.12.2, 00:00:02, FastEthernet1/0 R 172.16.4.0/24 [120/1] via 12.12.12.2, 00:00:02, FastEthernet1/0 C 192.168.1.0/24 is directly connected, FastEthernet0/0 R 192.168.2.0/24 [120/1] via 12.12.12.2, 00:00:02, FastEthernet1/0 R1#

Tes Ping dari PC0 ke PC1

PC0>ping 192.168.2.1 Pinging 192.168.2.1 with 32 bytes of data: Reply 192.168.2.1: bytes=32 time=1ms TTL=126 Reply 192.168.2.1: bytes=32 time=1ms TTL=126 Reply 192.168.2.1: bytes=32 time=1ms TTL=126 Reply 192.168.2.1: bytes=32 time=1ms TTL=126 Ping statistics for 192.168.2.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms

Ping dari PC0 ke PC1 berhasil.

Traceroute dari PC0 ke PC1

PC0>tracert 192.168.2.1 Tracing route to 192.168.2.1 over a maximum of 30 hops: 1 1 ms 0 ms 0 ms 192.168.1.254 2 0 ms 0 ms 0 ms 12.12.12.2 3 0 ms 0 ms 0 ms 192.168.2.1

Untuk menuju PC1 dari PC0 membutuhkan 3 hop.

PC1>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=0ms TTL=126 Reply from 192.168.1.1: bytes=32 time=0ms TTL=126 Reply from 192.168.1.1: bytes=32 time=0ms TTL=126 Reply from 192.168.1.1: bytes=32 time=0ms TTL=126 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms

Ping dari PC1 ke PC0 berhasil.

Traceroute dari PC1 ke PC0

PC1>tracert 192.168.1.1 Tracing route to 192.168.1.1 over a maximum of 30 hops: 1 1 ms 0 ms 0 ms 192.168.2.254 2 0 ms 0 ms 0 ms 12.12.12.1 3 1 ms 11 ms 11 ms 192.168.1.1 Trace complete.

Tampilkan informasi routing protocol yang digunakan di R1

R1#show ip protocols Routing Protocol is "rip" Sending updates every 30 seconds, next due in 12 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 2, receive 2 Interface Send Recv Triggered RIP Key-chain FastEthernet1/0 2 2 Loopback1 2 2 Loopback2 2 2 FastEthernet0/0 2 2 Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 12.0.0.0 172.16.0.0 192.168.1.0 Passive Interface(s): Routing Information Sources: Gateway Distance Last Update 12.12.12.2 120 00:00:15 Distance: (default is 120)

Debug RIP di R1

Dengan mengaktifkan fitur debug, kita bisa tahu apakah RIP sudah berjalan atau belum.

R1#debug ip rip RIP protocol debugging is on R1# RIP: received v2 update from 12.12.12.2 on FastEthernet1/0 172.16.3.0/24 via 0.0.0.0 in 1 hops 172.16.4.0/24 via 0.0.0.0 in 1 hops 192.168.2.0/24 via 0.0.0.0 in 1 hops RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (12.12.12.1) RIP: build update entries 172.16.1.0/24 via 0.0.0.0, metric 1, tag 0 172.16.2.0/24 via 0.0.0.0, metric 1, tag 0 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0 RIP: sending v2 update to 224.0.0.9 via Loopback1 (172.16.1.1) RIP: build update entries 12.12.12.0/24 via 0.0.0.0, metric 1, tag 0 172.16.2.0/24 via 0.0.0.0, metric 1, tag 0 172.16.3.0/24 via 0.0.0.0, metric 2, tag 0 172.16.4.0/24 via 0.0.0.0, metric 2, tag 0 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0 192.168.2.0/24 via 0.0.0.0, metric 2, tag 0 RIP: sending v2 update to 224.0.0.9 via Loopback2 (172.16.2.2) RIP: build update entries 12.12.12.0/24 via 0.0.0.0, metric 1, tag 0 172.16.1.0/24 via 0.0.0.0, metric 1, tag 0 172.16.3.0/24 via 0.0.0.0, metric 2, tag 0 172.16.4.0/24 via 0.0.0.0, metric 2, tag 0 192.168.1.0/24 via 0.0.0.0, metric 1, tag 0 192.168.2.0/24 via 0.0.0.0, metric 2, tag 0 RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (192.168.1.254) RIP: build update entries 12.12.12.0/24 via 0.0.0.0, metric 1, tag 0 172.16.1.0/24 via 0.0.0.0, metric 1, tag 0 172.16.2.0/24 via 0.0.0.0, metric 1, tag 0 172.16.3.0/24 via 0.0.0.0, metric 2, tag 0 172.16.4.0/24 via 0.0.0.0, metric 2, tag 0 192.168.2.0/24 via 0.0.0.0, metric 2, tag 0

Dari output debug RIP, kita bisa lihat bahwa RIP sudah running di router R1. Untuk menghentikan output debug, gunakan command undebug ip rip atau undebug all.

Setting passive-interface di R1

Untuk menghentikan routing updates yang dikirimkan ke Network A, maka aktifkan command passive-interface di interface fa0/0 R1 yang menuju Network A. Hal ini tidak mempengaruhi advertise Network A. Jadi, Network A masih tetap dikenali oleh R2 dan masih tampil di routing table R2. Di routing protocol RIPv2, mengaktifkan passive-interface mencegah multicast update melalui interface spesifik dan masih bisa mendapatkan update dari RIP neighbor yang lain.

R1(config)#router rip R1(config-router)#passive-interface fa0/0 R1(config-router)#

Tampilkan routing information di R1

show ip protocols Routing Protocol is "rip" Sending updates every 30 seconds, next due in 3 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 2, receive 2 Interface Send Recv Triggered RIP Key-chain FastEthernet1/0 2 2 Loopback1 2 2 Loopback2 2 2 Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 12.0.0.0 172.16.0.0 192.168.1.0 Passive Interface(s): FastEthernet0/0 Routing Information Sources: Gateway Distance Last Update 12.12.12.2 120 00:00:08 Distance: (default is 120) R1#

Passive-interface fa0/0 R1 sudah berhasil kita setting.

Nah jadi begitulah pembahasan dari routing RIPv2 ini, sedikit info lagi, bahwasanya RIP lebih cocok diimplementasikan pada jaringan yang sekiranya tidak akan ada lagi pertambahan device atau skala pada jaringan.

Sekian yang dapat saya bagikan pada kali ini,mohon ma'af apabila ada kesalahan dan semoga bermanfa'at bagi kita semua.Saya akhiri wabillahi taufiq wal hidayah.

Wassalamu'alaikum wr.wb

Share this post