Topologi
R1 - IP ADDRESS
===============
admin@MikroTik] > sy ide se na IDN_R1 [admin@IDN_R1] > int br ad na loopback [admin@IDN_R1] > ip ad ad ad 12.12.12.1/24 int ether2 [admin@IDN_R1] > ip ad ad ad 1.1.1.1 int loopback [admin@IDN_R1] > ip ad pr Flags: X - disabled, I - invalid, D - dynamic # ADDRESS NETWORK INTERFACE 0 12.12.12.1/24 12.12.12.0 ether2 1 1.1.1.1/32 1.1.1.1 loopback [admin@IDN_R1] >
R2 - IP ADDRESS
===============
[admin@MikroTik] > sy ide se na=IDN_R2 [admin@IDN_R2] > int br ad na loopback [admin@IDN_R2] > ip ad ad ad 12.12.12.2/24 int ether1 [admin@IDN_R2] > ip ad ad ad 2.2.2.2 int loopback [admin@IDN_R2] > ip ad ad ad 23.23.23.2/24 int ether3 [admin@IDN_R2] > ip ad pr Flags: X - disabled, I - invalid, D - dynamic # ADDRESS NETWORK INTERFACE 0 12.12.12.2/24 12.12.12.0 ether1 1 2.2.2.2/32 2.2.2.2 loopback 2 23.23.23.2/24 23.23.23.0 ether3 [admin@IDN_R2] >
R3 - IP ADDRESS
===============
TAMBAHKAN KONFIGURASI ROUTING R1[admin@MikroTik] > sy ide se na IDN_R3 [admin@IDN_R3] > int br ad na loopback [admin@IDN_R3] > ip ad ad ad 23.23.23.2/24 int ether2 [admin@IDN_R3] > ip ad ad add 3.3.3.3 int loopback [admin@IDN_R3] > ip ad pr Flags: X - disabled, I - invalid, D - dynamic # ADDRESS NETWORK INTERFACE 0 23.23.23.2/24 23.23.23.0 ether2 1 3.3.3.3/32 3.3.3.3 loopback [admin@IDN_R3] >
===========================
[admin@IDN_R1] > ip ro add dst-address=23.23.23.0/24 gateway=12.12.12.2
TAMBAHKAN KONFIGURASI ROUTING R3
===========================
[admin@IDN_R3] > ip ro add dst-address=12.12.12.0/24 gateway=23.23.23.2
PEERING ANTAR ROUTER BGP
=======================
Set AS R1
=========
Set AS R2[admin@IDN_R1] > ro bgp ins se as=100 0
=========
Set AS R3[admin@IDN_R2] > ro bgp ins se as=100 0
=========
Set BGP PEER R1[admin@IDN_R3] > ro bgp ins se as=100 0
===============
Set BGP PEER R2[admin@IDN_R1] > rou bgp peer ad na peer_R2 remote-address=12.12.12.2 remote-as=100
===============
Set BGP PEER R3[admin@IDN_R2] > rou bgp peer ad na peer_R1 remote-address=12.12.12.1 remote-as=100 [admin@IDN_R2] > rou bgp peer ad na peer_R3 remote-address=23.23.23.3 remote-as=100
===============
[admin@IDN_R3] > ro bg peer ad na peer_R2 remote-address=23.23.23.2 remote-as=100
CEK STATUS BGP PEER R1
======================
[admin@IDN_R1] > ro bg peer pr stat
Flags: X - disabled, E - established
0 E name="peer_R2" instance=default remote-address=12.12.12.2 remote-as=100 tcp-md5-key=""
nexthop-choice=default multihop=no route-reflect=no hold-time=3m ttl=255 in-filter=""
out-filter="" address-families=ip default-originate=never remove-private-as=no
as-override=no passive=no use-bfd=no remote-id=2.2.2.2 local-address=12.12.12.1
uptime=1s prefix-count=0 updates-sent=0 updates-received=0 withdrawn-sent=0
withdrawn-received=0 remote-hold-time=3m used-hold-time=3m used-keepalive-time=1m
refresh-capability=yes as4-capability=yes state=established
Statusnya sudah Established.. berarti.. OKEE Lanjutkan.CEK STATUS BGP PEER R2
======================
[admin@IDN_R2] > rou bgp peer pr stat
Flags: X - disabled, E - established
0 E name="peer_R1" instance=default remote-address=12.12.12.1 remote-as=100 tcp-md5-key=""
nexthop-choice=default multihop=no route-reflect=no hold-time=3m ttl=255 in-filter=""
out-filter="" address-families=ip default-originate=never remove-private-as=no
as-override=no passive=no use-bfd=no remote-id=1.1.1.1 local-address=12.12.12.2
uptime=4m26s prefix-count=0 updates-sent=0 updates-received=0 withdrawn-sent=0
withdrawn-received=0 remote-hold-time=3m used-hold-time=3m used-keepalive-time=1m
refresh-capability=yes as4-capability=yes state=established
1 E name="peer_R3" instance=default remote-address=23.23.23.3 remote-as=100 tcp-md5-key=""
nexthop-choice=default multihop=no route-reflect=no hold-time=3m ttl=255 in-filter=""
out-filter="" address-families=ip default-originate=never remove-private-as=no
as-override=no passive=no use-bfd=no remote-id=3.3.3.3 local-address=23.23.23.2
uptime=1m18s prefix-count=0 updates-sent=0 updates-received=0 withdrawn-sent=0
withdrawn-received=0 remote-hold-time=3m used-hold-time=3m used-keepalive-time=1m
refresh-capability=yes as4-capability=yes state=established
[admin@IDN_R2] >
R2 juga Statusnya sudah Established.. berarti.. OKEE Lanjutkan.CEK STATUS BGP PEER R3
======================
[admin@IDN_R3] > ro bgp peer pr sta
Flags: X - disabled, E - established
0 E name="peer_R2" instance=default remote-address=23.23.23.2 remote-as=100 tcp-md5-key=""
nexthop-choice=default multihop=no route-reflect=no hold-time=3m ttl=255 in-filter=""
out-filter="" address-families=ip default-originate=never remove-private-as=no
as-override=no passive=no use-bfd=no remote-id=2.2.2.2 local-address=23.23.23.3
uptime=9s prefix-count=0 updates-sent=0 updates-received=0 withdrawn-sent=0
withdrawn-received=0 remote-hold-time=3m used-hold-time=3m used-keepalive-time=1m
refresh-capability=yes as4-capability=yes state=established
R3 juga Statusnya sudah Established.. berarti.. OKEE Lanjutkan. PING KE 2.2.2.2 (LOOPBACK R2)
==============================
[admin@IDN_R1] > ping 2.2.2.2
SEQ HOST SIZE TTL TIME STATUS
0 no route to host
1 no route to host
2 no route to host
sent=3 received=0 packet-loss=100%
Dari test PING tersebut masih gagal, eh bukan gagal tapi beluk berhasil.. maka selanjutnya kita ADVERTISE NETWORK IP LOOPBACK R1===========================================
ADVERTISE NETWORK IP LOOPBACK R2 ================================[admin@IDN_R1] > rou bgp net ad net 1.1.1.1/32
PING ULANG KE 2.2.2.2 (LOOPBACK R2) ===================================[admin@IDN_R2] > rou bgp net add net 2.2.2.2/32
[admin@IDN_R1] > ping 2.2.2.2
SEQ HOST SIZE TTL TIME STATUS
0 2.2.2.2 56 64 7ms
1 2.2.2.2 56 64 1ms
sent=2 received=2 packet-loss=0% min-rtt=1ms avg-rtt=4ms max-rtt=7ms
[admin@IDN_R1] >
Maka agar R2 juga bisa PING Ke 3.3.3.3 (LOOPBACK R3), advertise network ip loopback tersebut di routing BGP.
ADVERTISE NETWORK IP LOOPBACK R2
================================
[admin@IDN_R3] > rou bgp net ad net 3.3.3.3/32
Namun kendala saat ini adalah router R1 belum mengetahui rute untuk menuju ke 1.1.1.1 (IP LOOPBACK R1) dan sebaliknya karena routing tabelnya belum lengkap. Semua router BGP Speaker harus peering dengan router lainnya. Maka lakukan peering antar kedua router tersebut.
BGP PEERING R1 TO R3
=============================================================
BGP PEERING R3 TO R1 =============================================================[admin@IDN_R1] /routing bgp peer> add remote-address=23.23.23.3 remote-as=100
TEST PING DARI R1 =============================================================[admin@IDN_R3] > rou bgp peer add remote-address=12.12.12.1 remote-as=100
[admin@IDN_R1] > ping 1.1.1.1
SEQ HOST SIZE TTL TIME STATUS
0 1.1.1.1 56 64 1ms
1 1.1.1.1 56 64 2ms
2 1.1.1.1 56 64 0ms
sent=3 received=3 packet-loss=0% min-rtt=0ms avg-rtt=1ms max-rtt=2ms
[admin@IDN_R1] > ping 2.2.2.2
SEQ HOST SIZE TTL TIME STATUS
0 2.2.2.2 56 64 12ms
1 2.2.2.2 56 64 2ms
2 2.2.2.2 56 64 2ms
sent=3 received=3 packet-loss=0% min-rtt=2ms avg-rtt=5ms max-rtt=12ms
[admin@IDN_R1] > ping 3.3.3.3
SEQ HOST SIZE TTL TIME STATUS
0 3.3.3.3 56 63 9ms
1 3.3.3.3 56 63 3ms
2 3.3.3.3 56 63 7ms
sent=3 received=3 packet-loss=0% min-rtt=3ms avg-rtt=6ms max-rtt=9ms
[admin@IDN_R1] > ping 23.23.23.3
SEQ HOST SIZE TTL TIME STATUS
0 23.23.23.3 56 63 7ms
1 23.23.23.3 56 63 2ms
2 23.23.23.3 56 63 2ms
sent=3 received=3 packet-loss=0% min-rtt=2ms avg-rtt=3ms max-rtt=7ms
[admin@IDN_R1] >
No comments:
Post a Comment
Tak ada gading yang tak retak!!
Komentar dan masukan yang bersifat membangun selalu kami harapkan, demi kebaikan bersama.