Hi…
Kita nge-lab lagi ya… kali ini mencoba untuk RIP route pada Juniper. Topologi nya seperti gambar dibawah, dimana interface em0 pada router terhubung dengan router sebelahnya, dan interface em4 terhubung dengan client/PC
Pertama, kita set dulu ip pada masing masing interface
Juniper1
set interfaces em0 unit 0 family inet address 10.0.0.1/24 set interfaces em4 unit 0 family inet address 192.168.1.1/24
Juniper2set interfaces em0 unit 0 family inet address 10.0.0.1/24
set interfaces em0 unit 0 family inet address 10.0.0.2/24 set interfaces em4 unit 0 family inet address 192.168.2.1/24
Kemudian, kita enable RIP protokolnya dengan command set protocols rip group NAME export policy1, dimana pada lab ini menggunakan NAME = konfigurasi dan policy = konf-policy. Kemudian mengenalkan neighbor RIP melalui interface em0
Juniper1
set protocols rip group konfigurasi export konf-policy set protocols rip group konfigurasi neighbor em0
Juniper2
set protocols rip group konfigurasi export konf-policy set protocols rip group konfigurasi neighbor em0
Selanjutnya, kita mendefinisikan policy yang dibuat
Juniper1
set policy-options policy-statement konf-policy from protocol direct set policy-options policy-statement konf-policy then accept
Juniper2
set policy-options policy-statement konf-policy from protocol direct set policy-options policy-statement konf-policy then accept
Setelah itu, jangan lupa di commit agar konfigurasi yang di set bisa jalan.
Nah, sekarang lakukan verifikasi di masing masing router
Juniper1
root> show route inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.0/24 *[Direct/0] 00:26:32 > via em0.0 10.0.0.1/32 *[Local/0] 00:26:32 Local via em0.0 192.168.1.0/24 *[Direct/0] 00:26:32 > via em4.0 192.168.1.1/32 *[Local/0] 00:26:32 Local via em4.0 192.168.2.0/24 *[RIP/100] 00:25:58, metric 2, tag 0 > to 10.0.0.2 via em0.0 224.0.0.9/32 *[RIP/100] 00:26:32, metric 1 MultiRecv root> show route protocol rip inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.168.2.0/24 *[RIP/100] 00:26:07, metric 2, tag 0 > to 10.0.0.2 via em0.0 224.0.0.9/32 *[RIP/100] 00:26:41, metric 1 MultiRecv
Juniper2
root> show route inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.0/24 *[Direct/0] 00:27:00 > via em0.0 10.0.0.2/32 *[Local/0] 00:27:00 Local via em0.0 192.168.1.0/24 *[RIP/100] 00:27:00, metric 2, tag 0 > to 10.0.0.1 via em0.0 192.168.2.0/24 *[Direct/0] 00:27:00 > via em4.0 192.168.2.1/32 *[Local/0] 00:27:00 Local via em4.0 224.0.0.9/32 *[RIP/100] 00:27:00, metric 1 MultiRecv root> show route protocol rip inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.168.1.0/24 *[RIP/100] 00:27:07, metric 2, tag 0 > to 10.0.0.1 via em0.0 224.0.0.9/32 *[RIP/100] 00:27:07, metric 1 MultiRecv
Sekarang, kita coba ping dari PC1 ke PC2 dan sebaliknya
PC1> ping 192.168.2.254 84 bytes from 192.168.2.254 icmp_seq=1 ttl=62 time=4.506 ms 84 bytes from 192.168.2.254 icmp_seq=2 ttl=62 time=3.299 ms 84 bytes from 192.168.2.254 icmp_seq=3 ttl=62 time=2.968 ms 84 bytes from 192.168.2.254 icmp_seq=4 ttl=62 time=3.359 ms 84 bytes from 192.168.2.254 icmp_seq=5 ttl=62 time=3.047 ms
PC2> ping 192.168.1.254 84 bytes from 192.168.1.254 icmp_seq=1 ttl=62 time=2.147 ms 84 bytes from 192.168.1.254 icmp_seq=2 ttl=62 time=1.505 ms 84 bytes from 192.168.1.254 icmp_seq=3 ttl=62 time=2.940 ms 84 bytes from 192.168.1.254 icmp_seq=4 ttl=62 time=2.279 ms 84 bytes from 192.168.1.254 icmp_seq=5 ttl=62 time=1.502 ms