Posted by: Barly Wicaksono | 17 April, 2012

Redistribute Routing RIP – OSPF di Juniper

Judul dari tulisan ini adalah redistribute routing, berarti pertukaran 2 routing protokol atau lebih yang memiliki perbedaan baik dari sisi metric, administrative distance, classful, classless dan karakter pengiriman paket data. Berikut ini kutipan yang saya ambil dari cisco tentang redistribution routing protocol.

The use of a routing protocol to advertise routes that are learned by some other means, such as by another routing protocol, static routes, or directly connected routes, is called redistribution. While running a single routing protocol throughout your entire IP internetwork is desirable, multi-protocol routing is common for a number of reasons, such as company mergers, multiple departments managed by multiple network administrators, and multi-vendor environments. Running different routing protocols is often part of a network design. In any case, having a multiple protocol environment makes redistribution a necessity.

Differences in routing protocol characteristics, such as metrics, administrative distance, classful and classless capabilities can effect redistribution. Consideration must be given to these differences for redistribution to succeed.

Redistribution RIP-OSPF

Redistribution RIP-OSPF

.

Basic Knowledge

Pada router mana harus dipertukarkan 2 routing yang berbeda.
– Jawab : Pertemuan 2 routing protokol terjadi pada Router r3, maka konfigurasi pertukaran akan diletakkan di Router r3.

Konfigurasi policy yang harus dituliskan agar masing-masing routing protocol dapat menerima network yang diakomodir oleh routing protokol lawan.
*Pada cisco tidak mengunakan policy sehingga tabel routing otomatis dishare, karena aturan “Default Export& Import Policy” yang diterapkan oleh junos menyebabkan suatu tbel routing protokol tertentu tidak dapat secara default dishare*.

Default export policy RIP adalah “Reject everything. To export RIP routes, you must configure an export policy for RIP”. Jadi kita harus mengkonfigurasi export policy untuk menerima tabel routing baik dari RIP maupun OSPF. Untuk melihat Default Export & Import Policy, klik link disamping ini : Default Export & Import Policy.

.

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 192.168.10.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 rip export Accept_RIP
set logical-routers r1 protocols rip group rip neighbor em0.0
set logical-routers r1 protocols rip group rip neighbor lo0.0
set logical-routers r1 policy-options policy-statement Accept_RIP term Routing_RIP from protocol rip
set logical-routers r1 policy-options policy-statement Accept_RIP term Routing_RIP from protocol direct
set logical-routers r1 policy-options policy-statement Accept_RIP term Routing_RIP then accept
.
- Logical Router R2 -
set logical-routers r2 interfaces em1 unit 0 vlan-id 10
set logical-routers r2 interfaces em1 unit 0 family inet address 192.168.10.2/30
set logical-routers r2 interfaces em1 unit 1 vlan-id 20
set logical-routers r2 interfaces em1 unit 1 family inet address 192.168.20.1/30
set logical-routers r2 interfaces lo0 unit 1 family inet address 2.2.2.2/32
set logical-routers r2 protocols rip group rip export Accept_RIP
set logical-routers r2 protocols rip group rip neighbor em1.0
set logical-routers r2 protocols rip group rip neighbor em1.1
set logical-routers r2 protocols rip group rip neighbor lo0.1
set logical-routers r2 policy-options policy-statement Accept_RIP term Routing_RIP from protocol rip
set logical-routers r2 policy-options policy-statement Accept_RIP term Routing_RIP from protocol direct
set logical-routers r2 policy-options policy-statement Accept_RIP term Routing_RIP then accept
.
- Logical Router R3 -
<strong>Konfigurasi Interface</strong>
set logical-routers r3 interfaces em2 unit 0 vlan-id 20
set logical-routers r3 interfaces em2 unit 0 family inet address 192.168.20.2/30
set logical-routers r3 interfaces em2 unit 1 vlan-id 30
set logical-routers r3 interfaces em2 unit 1 family inet address 192.168.30.1/30
set logical-routers r3 interfaces lo0 unit 2 family inet address 3.3.3.3/32
set logical-routers r3 protocols ospf export Advertise_Routing
set logical-routers r3 protocols ospf area 0.0.0.0 interface em2.1
set logical-routers r3 protocols ospf area 0.0.0.0 interface lo0.2
set logical-routers r3 protocols rip group rip export Advertise_Routing
set logical-routers r3 protocols rip group rip neighbor lo0.2
set logical-routers r3 protocols rip group rip neighbor em2.0
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_OSPF from protocol ospf
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_OSPF from protocol direct
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_OSPF then accept
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_RIP from protocol rip
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_RIP from protocol direct
set logical-routers r3 policy-options policy-statement Advertise_Routing term Routing_RIP then accept
.
- Logical Router R4 -
set logical-routers r4 interfaces em3 unit 0 vlan-id 30
set logical-routers r4 interfaces em3 unit 0 family inet address 192.168.30.2/30
set logical-routers r4 interfaces em3 unit 1 vlan-id 40
set logical-routers r4 interfaces em3 unit 1 family inet address 192.168.40.1/30
set logical-routers r4 interfaces lo0 unit 3 family inet address 4.4.4.4/32
set logical-routers r4 protocols ospf export Accept_OSPF
set logical-routers r4 protocols ospf area 0.0.0.0 interface em3.0
set logical-routers r4 protocols ospf area 0.0.0.0 interface em3.1
set logical-routers r4 protocols ospf area 0.0.0.0 interface lo0.3
set logical-routers r4 policy-options policy-statement Accept_OSPF term Routing_OSPF from protocol ospf
set logical-routers r4 policy-options policy-statement Accept_OSPF term Routing_OSPF from protocol direct
set logical-routers r4 policy-options policy-statement Accept_OSPF term Routing_OSPF then accept
.
- Logical Router R5 -
set logical-routers r5 interfaces em4 unit 0 vlan-id 40
set logical-routers r5 interfaces em4 unit 0 family inet address 192.168.40.2/30
set logical-routers r5 interfaces lo0 unit 4 family inet address 5.5.5.5/32
set logical-routers r5 protocols ospf export Accept_OSPF
set logical-routers r5 protocols ospf area 0.0.0.0 interface em4.0
set logical-routers r5 protocols ospf area 0.0.0.0 interface lo0.4
set logical-routers r5 policy-options policy-statement Accept_OSPF term Routing_OSPF from protocol ospf
set logical-routers r5 policy-options policy-statement Accept_OSPF term Routing_OSPF from protocol direct
set logical-routers r5 policy-options policy-statement Accept_OSPF term Routing_OSPF 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 -
barly# run show route logical-router all

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

1.1.1.1/32         *[RIP/100] 03:37:59, metric 2, tag 0
> to 192.168.10.1 via em1.0
2.2.2.2/32         *[Direct/0] 04:01:39
> via lo0.1
3.3.3.3/32         *[RIP/100] 03:41:44, metric 2, tag 0
> to 192.168.20.2 via em1.1
4.4.4.4/32         *[RIP/100] 03:51:51, metric 2, tag 0
> to 192.168.20.2 via em1.1
5.5.5.5/32         *[RIP/100] 03:51:51, metric 2, tag 0
> to 192.168.20.2 via em1.1
192.168.10.0/30    *[Direct/0] 04:01:39
> via em1.0
192.168.10.2/32    *[Local/0] 04:01:39
Local via em1.0
192.168.20.0/30    *[Direct/0] 04:01:39
> via em1.1
192.168.20.1/32    *[Local/0] 04:01:39
Local via em1.1
192.168.30.0/30    *[RIP/100] 03:41:44, metric 2, tag 0
> to 192.168.20.2 via em1.1
192.168.40.0/30    *[RIP/100] 03:51:51, metric 2, tag 0
> to 192.168.20.2 via em1.1
224.0.0.9/32       *[RIP/100] 03:38:04, metric 1
MultiRecv
-----

logical-router: r3

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

1.1.1.1/32         *[RIP/100] 03:37:56, metric 3, tag 0
> to 192.168.20.1 via em2.0
2.2.2.2/32         *[RIP/100] 03:37:59, metric 2, tag 0
> to 192.168.20.1 via em2.0
3.3.3.3/32         *[Direct/0] 04:01:39
> via lo0.2
4.4.4.4/32         *[OSPF/10] 04:00:50, metric 1
> to 192.168.30.2 via em2.1
5.5.5.5/32         *[OSPF/10] 04:00:45, metric 2
> to 192.168.30.2 via em2.1
192.168.10.0/30    *[RIP/100] 03:37:59, metric 2, tag 0
> to 192.168.20.1 via em2.0
192.168.20.0/30    *[Direct/0] 04:01:39
> via em2.0
192.168.20.2/32    *[Local/0] 04:01:39
Local via em2.0
192.168.30.0/30    *[Direct/0] 04:01:39
> via em2.1
192.168.30.1/32    *[Local/0] 04:01:39
Local via em2.1
192.168.40.0/30    *[OSPF/10] 04:00:45, metric 2
> to 192.168.30.2 via em2.1
224.0.0.5/32       *[OSPF/10] 04:01:43, metric 1
MultiRecv
224.0.0.9/32       *[RIP/100] 03:38:04, metric 1
MultiRecv
-----

logical-router: r1

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

1.1.1.1/32         *[Direct/0] 04:01:40
> via lo0.0
2.2.2.2/32         *[RIP/100] 03:38:00, metric 2, tag 0
> to 192.168.10.2 via em0.0
3.3.3.3/32         *[RIP/100] 03:41:41, metric 3, tag 0
> to 192.168.10.2 via em0.0
4.4.4.4/32         *[RIP/100] 03:51:48, metric 3, tag 0
> to 192.168.10.2 via em0.0
5.5.5.5/32         *[RIP/100] 03:51:48, metric 3, tag 0
> to 192.168.10.2 via em0.0
192.168.10.0/30    *[Direct/0] 04:01:40
> via em0.0
192.168.10.1/32    *[Local/0] 04:01:40
Local via em0.0
192.168.20.0/30    *[RIP/100] 03:38:00, metric 2, tag 0
> to 192.168.10.2 via em0.0
192.168.30.0/30    *[RIP/100] 03:41:41, metric 3, tag 0
> to 192.168.10.2 via em0.0
192.168.40.0/30    *[RIP/100] 03:51:48, metric 3, tag 0
> to 192.168.10.2 via em0.0
224.0.0.9/32       *[RIP/100] 03:38:05, metric 1
MultiRecv
-----

logical-router: r4

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

1.1.1.1/32         *[OSPF/150] 03:37:56, metric 3, tag 0
> to 192.168.30.1 via em3.0
2.2.2.2/32         *[OSPF/150] 03:38:00, metric 2, tag 0
> to 192.168.30.1 via em3.0
3.3.3.3/32         *[OSPF/10] 04:00:50, metric 1
> to 192.168.30.1 via em3.0
4.4.4.4/32         *[Direct/0] 04:01:41
> via lo0.3
5.5.5.5/32         *[OSPF/10] 04:00:50, metric 1
> to 192.168.40.2 via em3.1
192.168.10.0/30    *[OSPF/150] 03:38:00, metric 2, tag 0
> to 192.168.30.1 via em3.0
192.168.20.0/30    *[OSPF/150] 03:41:49, metric 0, tag 0
> to 192.168.30.1 via em3.0
192.168.30.0/30    *[Direct/0] 04:01:41
> via em3.0
192.168.30.2/32    *[Local/0] 04:01:41
Local via em3.0
192.168.40.0/30    *[Direct/0] 04:01:41
> via em3.1
192.168.40.1/32    *[Local/0] 04:01:41
Local via em3.1
224.0.0.5/32       *[OSPF/10] 04:01:44, metric 1
MultiRecv
-----

logical-router: r5

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

1.1.1.1/32         *[OSPF/150] 03:37:56, metric 3, tag 0
> to 192.168.40.1 via em4.0
2.2.2.2/32         *[OSPF/150] 03:38:00, metric 2, tag 0
> to 192.168.40.1 via em4.0
3.3.3.3/32         *[OSPF/10] 04:00:50, metric 2
> to 192.168.40.1 via em4.0
4.4.4.4/32         *[OSPF/10] 04:00:50, metric 1
> to 192.168.40.1 via em4.0
5.5.5.5/32         *[Direct/0] 04:01:40
> via lo0.4
192.168.10.0/30    *[OSPF/150] 03:38:00, metric 2, tag 0
> to 192.168.40.1 via em4.0
192.168.20.0/30    *[OSPF/150] 03:41:49, metric 0, tag 0
> to 192.168.40.1 via em4.0
192.168.30.0/30    *[OSPF/10] 04:00:50, metric 2
> to 192.168.40.1 via em4.0
192.168.40.0/30    *[Direct/0] 04:01:40
> via em4.0
192.168.40.2/32    *[Local/0] 04:01:40
Local via em4.0
224.0.0.5/32       *[OSPF/10] 04:01:43, 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=0.666 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.105 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.098 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.137 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.098/0.252/0.666/0.240 ms

[edit]
barly# run ping 2.2.2.2 logical-router r1
PING 2.2.2.2 (2.2.2.2): 56 data bytes
64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=0.433 ms
64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=0.334 ms
64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=0.563 ms
64 bytes from 2.2.2.2: icmp_seq=3 ttl=64 time=0.411 ms
^C
--- 2.2.2.2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.334/0.435/0.563/0.082 ms

[edit]
barly# run ping 3.3.3.3 logical-router r1
PING 3.3.3.3 (3.3.3.3): 56 data bytes
64 bytes from 3.3.3.3: icmp_seq=0 ttl=63 time=0.963 ms
64 bytes from 3.3.3.3: icmp_seq=1 ttl=63 time=0.455 ms
64 bytes from 3.3.3.3: icmp_seq=2 ttl=63 time=0.509 ms
64 bytes from 3.3.3.3: icmp_seq=3 ttl=63 time=0.505 ms
^C
--- 3.3.3.3 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.455/0.608/0.963/0.206 ms

[edit]
barly# run ping 4.4.4.4 logical-router r1
PING 4.4.4.4 (4.4.4.4): 56 data bytes
64 bytes from 4.4.4.4: icmp_seq=0 ttl=62 time=1.097 ms
64 bytes from 4.4.4.4: icmp_seq=1 ttl=62 time=0.693 ms
64 bytes from 4.4.4.4: icmp_seq=2 ttl=62 time=0.662 ms
64 bytes from 4.4.4.4: icmp_seq=3 ttl=62 time=0.655 ms
^C
--- 4.4.4.4 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.655/0.777/1.097/0.185 ms

[edit]
barly# run ping 5.5.5.5 logical-router r1
PING 5.5.5.5 (5.5.5.5): 56 data bytes
64 bytes from 5.5.5.5: icmp_seq=0 ttl=61 time=1.047 ms
64 bytes from 5.5.5.5: icmp_seq=1 ttl=61 time=1.600 ms
64 bytes from 5.5.5.5: icmp_seq=2 ttl=61 time=0.890 ms
64 bytes from 5.5.5.5: icmp_seq=3 ttl=61 time=1.001 ms
^C
--- 5.5.5.5 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.890/1.135/1.600/0.275 ms

.

Running Configuration
RIP-OSPF

.


Responses

  1. Bos Barly,

    saya Bambang EP Alumni UII Juga 2004
    saya mau tanya neh karena saya belum begitu paham juniper, Mohon pencerahan nya

    Jadi Firewal Juniper saya IP nya 192.168.60.1 /24 ( segment kita 192.168.1.0/24)

    Dibawah Firewall ada Cisco 3560X Masih LAN Base,

    Sekarang ini kami ada router WAN dimana IP Lan nya 192.168.60.240
    dimana connect ke Japan, dan terconnect ke switch 3560

    Pertanyaan nya
    dari Japan sudah bisa connect ke jaringan kami 192.168.60.0/24
    Tapi dari local kami tidak bisa ping ke mereka. hanya bisa dari swith ping ke mereka, IP Japan 192.168.1.1 192.168.1.5 dsb( 192.168.1.0)

    Kalo IP PC saya saya rubah gateway ke 192.168.60.240 saya baru bisa connect ke Japan,

    Saya sudah coba add static rute di Juniper
    route : 192.168.1.0 /24 Next Hop 192.168.60.240

    Kok masih tidak bisa yah.

    Mohon advice nya

    salam Alumni

  2. sorry salah ketik.. Network segment kami 192.168.60.0 /24
    Yang di Japan 192.168.1.0

    • 1. Di firewall itu harus dikonfigurasi zone-nya.
      2. Di switch 3560 itu harus dikonfigurasi statik route kearah router Firewall.

      • lah itu masalahnya mas…3560 ga bisa routing,,, karena masih LAN BASE..😦

        • LAN Base bukannya bisa statik route ya basicnya?


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: