Posted by: Barly Wicaksono | 17 February, 2012

Routing RIPv2 di Juniper

RIP termasuk protokol distance vector, yang berarti ia menentukan jalur terbaik berdasarkan hop count. Mesin-mesin yang ikut berpartisipasi dalam RIP bisa termasuk aktif atau pasif RIP. Active RIP berupa router-router yang berpartisipasi dalam proses pertukaran data distance vector. Mesin-mesin Active RIP mengirimkan tabel routingnya kepada router lain dan memantau update dari router lain. Mesin passive RIP hanya memantau update tapi tidak ikut menyebarkan tabel routingnya. Mesin ini biasanya berupa komputer klien.

Jika ada dua jalur dengan network tujuan yang sama dan hop count yang sama maka router akan memilih jalur yang terlebih dahulu ada didalam tabel routing. Router RIP membroadcast pesan update setiap 30 detik. Jika jumlah router-router terlalu banyak akan timbul masalah karena akan memperlambat waktu convergence. Untuk itu, RIP membatasi angka maximum hop count sebesar 15. (sumber)

RIPv2

RIPv2

Konfigurasi Router

- Logical Router R1 -
set logical-routers R1 interfaces em0 unit 0 vlan-id 10
set logical-routers R1 interfaces em0 unit 0 family inet address 10.0.0.1/30
set logical-routers R1 interfaces lo0 unit 0 family inet address 1.1.1.1/32
set logical-routers R1 protocols rip group Neighbour_Router export Loopback
set logical-routers R1 protocols rip group Neighbour_Router export Direct
set logical-routers R1 protocols rip group Neighbour_Router neighbor em0.0
set logical-routers R1 policy-options policy-statement Direct term Directly_Connected from protocol direct
set logical-routers R1 policy-options policy-statement Direct term Directly_Connected then accept
set logical-routers R1 policy-options policy-statement Loopback term Loopback1 from route-filter 1.1.1.1/32 exact
set logical-routers R1 policy-options policy-statement Loopback term Loopback1 then accept

- Logical Router R2 -
set logical-routers R2 interfaces em2 unit 0 vlan-id 20
set logical-routers R2 interfaces em2 unit 0 family inet address 10.0.0.6/30
set logical-routers R2 interfaces lo0 unit 2 family inet address 3.3.3.3/32
set logical-routers R2 protocols rip group Neighbour_Router export Loopback
set logical-routers R2 protocols rip group Neighbour_Router export Direct
set logical-routers R2 protocols rip group Neighbour_Router neighbor em2.0
set logical-routers R2 policy-options policy-statement Direct term Directly_Connected from protocol direct
set logical-routers R2 policy-options policy-statement Direct term Directly_Connected then accept
set logical-routers R2 policy-options policy-statement Loopback term loopback1 from route-filter 3.3.3.3/32 exact
set logical-routers R2 policy-options policy-statement Loopback term loopback1 then accept

- Logical Router R3 -
set logical-routers R3 interfaces em3 unit 0 vlan-id 30
set logical-routers R3 interfaces em3 unit 0 family inet address 10.0.0.10/30
set logical-routers R3 interfaces lo0 unit 3 family inet address 4.4.4.4/32
set logical-routers R3 protocols rip group Neighbour_Router export Loopback
set logical-routers R3 protocols rip group Neighbour_Router export Direct
set logical-routers R3 protocols rip group Neighbour_Router neighbor em3.0
set logical-routers R3 policy-options policy-statement Direct term Directly_Connected from protocol direct
set logical-routers R3 policy-options policy-statement Direct term Directly_Connected then accept
set logical-routers R3 policy-options policy-statement Loopback term loopback1 from route-filter 4.4.4.4/32 exact
set logical-routers R3 policy-options policy-statement Loopback term loopback1 then accept

- Logical Router RIP -
set logical-routers RIP interfaces em1 unit 0 description To_R1
set logical-routers RIP interfaces em1 unit 0 vlan-id 10
set logical-routers RIP interfaces em1 unit 0 family inet address 10.0.0.2/30
set logical-routers RIP interfaces em1 unit 1 description To_R2
set logical-routers RIP interfaces em1 unit 1 vlan-id 20
set logical-routers RIP interfaces em1 unit 1 family inet address 10.0.0.5/30
set logical-routers RIP interfaces em1 unit 2 description To_R3
set logical-routers RIP interfaces em1 unit 2 vlan-id 30
set logical-routers RIP interfaces em1 unit 2 family inet address 10.0.0.9/30
set logical-routers RIP interfaces lo0 unit 1 family inet address 2.2.2.2/32

set logical-routers RIP protocols rip group Neighbour_Router export Routing_protocol
set logical-routers RIP protocols rip group Neighbour_Router export Loopback
set logical-routers RIP protocols rip group Neighbour_Router export Direct
set logical-routers RIP protocols rip group Neighbour_Router neighbor em1.2
set logical-routers RIP protocols rip group Neighbour_Router neighbor em1.0
set logical-routers RIP protocols rip group Neighbour_Router neighbor em1.1

set logical-routers RIP policy-options policy-statement Direct term Directly_Connected from protocol direct
set logical-routers RIP policy-options policy-statement Direct term Directly_Connected then accept
set logical-routers RIP policy-options policy-statement Loopback term loopback1 from route-filter 2.2.2.2/32 exact
set logical-routers RIP policy-options policy-statement Loopback term loopback1 then accept
set logical-routers RIP policy-options policy-statement Routing_protocol term RIP from protocol rip
set logical-routers RIP policy-options policy-statement Routing_protocol term RIP then accept

- Interface Vlan Tagging -
set interfaces em0 vlan-tagging
set interfaces em1 vlan-tagging
set interfaces em2 vlan-tagging
set interfaces em3 vlan-tagging

.
Verifikasi

- Show Route Protocol RIP -</pre>
barly# run show route protocol rip logical-router all
logical-router: R1
inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2.2.2.2/32 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.2 via em0.0
3.3.3.3/32 *[RIP/100] 00:24:20, metric 3, tag 0
> to 10.0.0.2 via em0.0
4.4.4.4/32 *[RIP/100] 00:24:25, metric 3, tag 0
> to 10.0.0.2 via em0.0
10.0.0.4/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.2 via em0.0
10.0.0.8/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.2 via em0.0
224.0.0.9/32 *[RIP/100] 00:24:30, metric 1
MultiRecv
-----

logical-router: R3

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.1/32 *[RIP/100] 00:24:25, metric 3, tag 0
> to 10.0.0.9 via em3.0
2.2.2.2/32 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.9 via em3.0
3.3.3.3/32 *[RIP/100] 00:24:20, metric 3, tag 0
> to 10.0.0.9 via em3.0
10.0.0.0/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.9 via em3.0
10.0.0.4/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.9 via em3.0
224.0.0.9/32 *[RIP/100] 00:24:30, metric 1
MultiRecv
-----

logical-router: R2

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.1/32 *[RIP/100] 00:24:25, metric 3, tag 0
> to 10.0.0.5 via em2.0
2.2.2.2/32 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.5 via em2.0
4.4.4.4/32 *[RIP/100] 00:24:25, metric 3, tag 0
> to 10.0.0.5 via em2.0
10.0.0.0/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.5 via em2.0
10.0.0.8/30 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.5 via em2.0
224.0.0.9/32 *[RIP/100] 00:24:30, metric 1
MultiRecv
-----

logical-router: RIP

inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.1/32 *[RIP/100] 00:24:28, metric 2, tag 0
> to 10.0.0.1 via em1.0
3.3.3.3/32 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.6 via em1.1
4.4.4.4/32 *[RIP/100] 00:24:25, metric 2, tag 0
> to 10.0.0.10 via em1.2
224.0.0.9/32 *[RIP/100] 00:24:30, metric 1
MultiRecv
-----

- Ping Test -
barly# run ping 1.1.1.1 logical-router R1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=4.419 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.354 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.150 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.153 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.150/1.269/4.419/1.821 ms

[edit]
barly# run ping 1.1.1.1 logical-router R2
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=63 time=2.761 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=63 time=0.981 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=63 time=1.253 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=63 time=1.088 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.981/1.521/2.761/0.723 ms

[edit]
barly# run ping 1.1.1.1 logical-router R3
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=63 time=1.565 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=63 time=0.988 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=63 time=0.995 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=63 time=0.966 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.966/1.129/1.565/0.252 ms

[edit]
barly# run ping 1.1.1.1 logical-router RIP
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=1.710 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.730 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.544 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.942 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.544/0.982/1.710/0.444 ms

.

Running Configuration
RIPv2


Responses

  1. Mas kenapa ya harus pake VLAN?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: