{"id":1968,"date":"2015-09-07T18:01:25","date_gmt":"2015-09-07T18:01:25","guid":{"rendered":"http:\/\/rachmadona.net\/?p=1968"},"modified":"2015-09-07T18:01:25","modified_gmt":"2015-09-07T18:01:25","slug":"belajar-mikrotik-di-vmware-workstation-konfigurasi-ospf","status":"publish","type":"post","link":"https:\/\/rachmadona.net\/?p=1968","title":{"rendered":"Belajar MikroTik di VMware Workstation – Konfigurasi OSPF"},"content":{"rendered":"

Setelah sebelumnya kita udah melakukan konfigurasi dasar MikroTik pada WS 10<\/a>, sekarang waktunya melakukan konfigurasi yang agak advance, yaitu routing OSPF. Buat yang baru belajar mengenai konsep routing sebaiknya baca-baca dulu di sini. Sedangkan untuk studi kasus OSPF mengunakan MikroTik bisa mampir ke sini<\/a>.<\/p>\n

Lanjut ke praktek.<\/p>\n

Kali ini kita punya topologi seperti gambar di bawah. Konfigurasi OSPF yang akan kita lakukan masih menggunakan single area, yaitu area backbone.<\/p>\n

\"config<\/a><\/p>\n

Seperti biasa petunjuk awal yang harus dilakukan adalah pengaturan VMnet terhadap masing-masing interface MikroTik. Jangan sampai tertukar atau bahkan tidak di-assign. Salah sedikit fatal akibatnya sehingga berakibat interkoneksi antar MikroTik jadi kacau. Buat tabel bila perlu.<\/p>\n

R1<\/strong><\/p>\n

Eth1: NAT<\/p>\n

Eth2: VMnet2<\/p>\n

Eth3: VMnet3<\/p>\n

R2<\/strong><\/p>\n

Eth1: VMnet5<\/p>\n

Eth2: VMnet2<\/p>\n

R3<\/strong><\/p>\n

Eth1: VMnet3<\/p>\n

Eth2: VMnet4<\/p>\n

R4<\/strong><\/p>\n

Eth1: VMnet4<\/p>\n

Eth2: VMnet5<\/p>\n

Eth3: VMnet6<\/p>\n

Apabila semua sudah sesuai maka sekarang waktunya memberikan IP Address pada setiap interface. Lihat topologi di atas apabila masih bingung.<\/p>\n

R1<\/strong><\/p>\n

\/ip address
\nadd address=192.168.2.1\/24 disabled=no interface=ether2 network=192.168.2.0
\nadd address=192.168.3.1\/24 disabled=no interface=ether3 network=192.168.3.0<\/p>\n

R1 melakukan NAT<\/p>\n

\/ip firewall nat
\nadd action=masquerade chain=srcnat out-interface=ether1<\/p>\n

Aktifkan DNS<\/p>\n

\/ip dns
\nset allow-remote-requests=yes cache-max-ttl=1w cache-size=2048KiB \\
\nmax-udp-packet-size=4096 query-server-timeout=2s query-total-timeout=10s \\
\nservers=192.168.225.2<\/p>\n

Note: IP DNS server adalah IP host dari VMnet8 (NAT)<\/p>\n

R2<\/strong><\/p>\n

\/ip address
\nadd address=192.168.2.2\/24 disabled=no interface=ether2 network=192.168.2.0
\nadd address=192.168.5.2\/24 disabled=no interface=ether1 network=192.168.5.0<\/p>\n

R3<\/p>\n

\/ip address
\nadd address=192.168.3.3\/24 disabled=no interface=ether1 network=192.168.3.0
\nadd address=192.168.4.3\/24 disabled=no interface=ether2 network=192.168.4.0<\/p>\n

R4<\/p>\n

add address=192.168.4.4\/24 disabled=no interface=ether1 network=192.168.4.0
\nadd address=192.168.5.4\/24 disabled=no interface=ether2 network=192.168.5.0
\nadd address=192.168.6.1\/24 disabled=no interface=ether3 network=192.168.6.0<\/p>\n

Setelah selesai memasukkan IP Address, sekarang waktunya kita melakukan konfigurasi OSPF. Secara sederhana yang perlu kita lakukan hanya memasukkan subnet network yang ingin di-advertise ke neighbour (router tetangga).<\/p>\n

Kita verifikasi routing table R1 terlebih dahulu:<\/p>\n

[admin@R1] > ip ro pr
\nFlags: X – disabled, A – active, D – dynamic,
\nC – connect, S – static, r – rip, b – bgp, o – ospf, m – mme,
\nB – blackhole, U – unreachable, P – prohibit
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 DST-ADDRESS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PREF-SRC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GATEWAY\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DISTANCE
\n0 ADS\u00a0 0.0.0.0\/0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.225.2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n1 ADC\u00a0 192.168.2.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.2.1\u00a0\u00a0\u00a0\u00a0 ether2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n2 ADC\u00a0 192.168.3.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.3.1\u00a0\u00a0\u00a0\u00a0 ether3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n3 ADC\u00a0 192.168.225.0\/24\u00a0\u00a0 192.168.225.143 ether1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/p>\n

Seperti yang kita lihat bahwa belum ada routing OSPF yang ditandai dengan huruf ‘o’. Router R1 belum bisa reach ke R4 (network .4, .5) dan juga PC A (192.168.6.0).<\/p>\n

Mari kita aktifkan routing OSPF pada R1 terlebih dahulu. Masukkan semua network yang directly connected (terhubung langsung) dengan interface R1.<\/p>\n

\/routing ospf network
\nadd area=backbone network=192.168.2.0\/24
\nadd area=backbone network=192.168.3.0\/24<\/p>\n

Kemudian lakukan hal yang sama pada R2.<\/p>\n

\/routing ospf network
\nadd area=backbone disabled=no network=192.168.2.0\/24
\nadd area=backbone disabled=no network=192.168.5.0\/24<\/p>\n

Sisanya, R3 & R4 juga lakukan hal yang sama pula.<\/p>\n

Apabila benar seharusnya sekarang pada setiap router sudah terdapat routing OSPF dengan nilai administrative distance\u00a0 110.<\/p>\n

Contoh yang nampak pada R3.<\/p>\n

[admin@R3] > ip ro pr
\nFlags: X – disabled, A – active, D – dynamic,
\nC – connect, S – static, r – rip, b – bgp, o – ospf, m – mme,
\nB – blackhole, U – unreachable, P – prohibit
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 DST-ADDRESS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PREF-SRC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GATEWAY\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DISTANCE
\n0 ADo<\/strong>\u00a0 192.168.2.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.3.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110
\n1 ADC\u00a0 192.168.3.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.3.3\u00a0\u00a0\u00a0\u00a0 ether1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n2 ADC\u00a0 192.168.4.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.4.3\u00a0\u00a0\u00a0\u00a0 ether2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n3 ADo\u00a0<\/strong> 192.168.5.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.4.4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110<\/strong>
\n4 ADo<\/strong>\u00a0 192.168.6.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.4.4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110<\/strong><\/p>\n

Muncul simbol ‘o’ yang menandakan routing protocol OSPF sudah berjalan dengan baik.<\/p>\n

Nah, kemudian masalah baru muncul. PC A yang terhubung dengan R4 tidak dapat melakukan koneksi ke internet. Mengapa hal itu bisa terjadi? Padahal semua router sudah bisa saling komunikasi dan konek ke internet. Apa iya? mari kita periksa lagi routing table di atas. Jika Anda teliti maka dapat ditemukan bahwa tidak ada default gateway dalam routing table R2, R3 & R4 sehingga apabila ada klien di belakang mereka yang ingin melakukan koneksi internet maka akan keluar error ‘no route to host’ karena router tidak tahu akan dikemanakan paket tersebut.<\/p>\n

Lalu bagaimana solusinya? Mudah saja, kita hanya perlu mengaktifkan fitur redistribute default pada R1 supaya default\u00a0 gateway bisa di-advertise ke R2, R3 & R4.<\/p>\n

\/routing ospf instance
\nset [ find default=yes ] disabled=no distribute-default=always-as-type-1 \\<\/p>\n

Mari kita lihat sekarang routing table pada R3.<\/p>\n

[admin@R3] > ip ro pr
\nFlags: X – disabled, A – active, D – dynamic,
\nC – connect, S – static, r – rip, b – bgp, o – ospf, m – mme,
\nB – blackhole, U – unreachable, P – prohibit
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 DST-ADDRESS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PREF-SRC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GATEWAY\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DISTANCE
\n0 ADo\u00a0 0.0.0.0\/0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.3.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110
\n1 ADo\u00a0 192.168.2.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.3.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110
\n2 ADC\u00a0 192.168.3.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.3.3\u00a0\u00a0\u00a0\u00a0 ether1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n3 ADC\u00a0 192.168.4.0\/24\u00a0\u00a0\u00a0\u00a0 192.168.4.3\u00a0\u00a0\u00a0\u00a0 ether2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0
\n4 ADo\u00a0 192.168.5.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.4.4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110
\n5 ADo\u00a0 192.168.6.0\/24\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.4.4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 110<\/p>\n

Yup, sudah ada default gateway 0.0.0.0\/0 via R1 melalui protokol OSPF. Waktunya kita coba konek internet dari PC A.<\/p>\n

\"config<\/a>Hore.. sudah berhasil.<\/p>\n

Kita akan lihat flow paket dari PC A menuju ke ISP. Apakah via R2 atau R3.<\/p>\n

\"config<\/a><\/p>\n

Ternyata flow paketnya adalah via R3<\/p>\n

\"config<\/a>Jadi seperti ini PC A -> R4 -> R3 -> R1 -> Internet<\/p>\n

Apakah selalu seperti itu flow paketnya? tidak juga. Mari kita lihat routing table pada R4.<\/p>\n

[admin@R4] > ip route pr
\nFlags: X – disabled, A – active, D – dynamic,
\nC – connect, S – static, r – rip, b – bgp, o – ospf, m – mme,
\nB – blackhole, U – unreachable, P – prohibit
\n# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
\n0 ADo 0.0.0.0\/0 192.168.4.3 110<\/strong>
\n 192.168.5.2<\/strong>
\n1 ADo 192.168.2.0\/24 192.168.5.2 110
\n2 ADo 192.168.3.0\/24 192.168.4.3 110
\n3 ADC 192.168.4.0\/24 192.168.4.4 ether1 0
\n4 ADC 192.168.5.0\/24 192.168.5.4 ether2 0
\n5 ADC 192.168.6.0\/24 192.168.6.1 ether3 0<\/p>\n

Lihat pada baris 1 yang berisi default gateway. Terlihat ada dua exit interface yang ditawarkan oleh protokol OSPF untuk menuju ke internet. Ini artinya protokol OSPF menawarkan fitur yang sangat penting, yaitu load balancing dan fail over. Beban keluar akan dibagi secara seimbang dan apabila ada link yang down makan link lainnya dapat menjadi link cadangan. Enak, tho?<\/p>\n

Oke sekian dulu mater tentang MikroTik menggunakan OSPF. Artikel selanjutnya kita kan bahas mengenai VRRP sebagai solusi FHRP. Nah, makin bingung toh? Hehe<\/p>\n

So, stay tuned ya guys \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Setelah sebelumnya kita udah melakukan konfigurasi dasar MikroTik pada WS 10, sekarang waktunya melakukan konfigurasi yang agak advance, yaitu routing OSPF. Buat yang baru belajar mengenai konsep routing sebaiknya baca-baca dulu di sini. Sedangkan untuk studi kasus OSPF mengunakan MikroTik bisa mampir ke sini. Lanjut ke praktek. Kali ini kita punya topologi seperti gambar di…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40,11,24,25],"tags":[89,276,299,371,472,474,476],"class_list":["post-1968","post","type-post","status-publish","format-standard","hentry","category-mikrotik","category-network","category-virtualization","category-vmware","tag-belajar-jaringan","tag-mikrotik-2","tag-ospf","tag-routeros","tag-vmnet","tag-vmware","tag-vmware-workstation"],"_links":{"self":[{"href":"https:\/\/rachmadona.net\/index.php?rest_route=\/wp\/v2\/posts\/1968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rachmadona.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rachmadona.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rachmadona.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/rachmadona.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1968"}],"version-history":[{"count":0,"href":"https:\/\/rachmadona.net\/index.php?rest_route=\/wp\/v2\/posts\/1968\/revisions"}],"wp:attachment":[{"href":"https:\/\/rachmadona.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rachmadona.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rachmadona.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}