Pesantren Mengajar – SMK 4 Kendal

Bismillah

Setelah selesai  Pesantren Mengajar – SMK 6 Balikpapan selanjutnya saya ngisi training pesantren mengajar di SMK 4 Kendal. Oke, Gimana ngajar disana? ini training seperti biasa

whatsapp-image-2016-12-14-at-10-17-17-am

Kalau ditanya saya yang mana, itu loh saya yaang depan.

whatsapp-image-2016-12-13-at-9-33-49-am

whatsapp-image-2016-12-15-at-9-18-44-am

Karena perbedaan kelas, jadi yang duduk disebelah kiri ini adalah anak kelas 1 dan kelas 2, jadi terkadang harus fokus ke kelas 1 dan 2 karena dasar masih belum kuat. hehehe

whatsapp-image-2016-12-14-at-1-56-36-pm

hmm, jangan salah paham ya. wkwkwk

oke, itu suasana kelas nya.

ini foto hari pertama,

kenapa hari pertama gak di depan postingan?-__-

karena sudah terlalu maenstrim :v

day1day12

Yah, sedikit motivasi dan dorongan untuk lebih giat. ini hari pertama loh

oke, saya mau kasih tau sedikit gimana suasana sekolah nya

yang pertama ini sedikit ruangan depan lab komputer

img_20161212_080132_hdrimg_20161212_080135_hdr

IMG_20161212_153306.jpg

oke, fokus sama yang dibelakang saya, bukan saya ya. hehehe

yang keren itu sekolah nya besar dan juga dekat sama sawah. kiri sama kanan sekolahnya itu ada sawah dan tentu bisa ngurangin stres saat ngelab. hehehe

oke, sekarang ini foto kelas malam nya

img_20161212_190551_hdrimg_20161215_221229_hdr

Siang dan malam, tetap semangat nge-lab. joss

 

ini sedikit foto foto tambahan

photo725445772324218863photo725445772324218856photo725445772324218855

 

Oke terakhir sebagai penutup yaitu foto-foto bareng

photo725445772324218858photo725445772324218861

photo725445772324218864img_20161217_154537_hdrimg_20161217_154601_hdrimg_20161217_140142

 

Oke, selesai dengan pesantren mengajar di SMK4 Kendal

 

CCIE Bootcamp IDN

Assalamu’alaikum saudaraku. Dalam blog post ini, saya ingin sharing cerita CCIE Bootcamp IDN. Well, IDN punya hajat akbar yang diadakan tiap 6 bulan sekali yaitu bootcamp. Nah untuk bulan Desember ini, IDN punya bootcamp MTCINE, JNCIE, dan CCIE-RS. MTCINE = MikroTik Certified Internetworking Engineer JNCIE = Juniper Networks Certified Internet Expert CCIE = Cisco Certified […]

Pesantren Mengajar – SMK 6 Balikpapan

Bismillah

kali ini saya nggak bahas tentang lab mikrotik, tapi saya mau sharing pengalaman menjadi trainer pesantren mengajar. oke, yang pertama tempat saya menjadi trainer adalah SMK 6 balikpapan.

IMG_20161101_102915_HDR.jpg

Oke, sedikit cerita bahwa saya sebenarnya berasal dari samarinda. jadi untuk pesantren mengajar pertama saya ngambil di Balikpapan, selain karena pengen pulang ke samarinda hehehe (samarinda dan balikpapan ada di kalimantan timur).

selain karena pengen pulang alasan lainnya adalah karena materi yang diminta sekolah tersebut adalah MTCNA + MTCRE. artinya apa yang saya pelajari, apa yang saya fokuskan itu berguna untuk orang lain.

Oh ya saya ke balikpapannya naik pesawat loh :v, gak percaya? nih buktinya. hehehe

img_20161031_102945_hdrimg_20161031_102954_hdr

Ini bukti kalau disana ngadain training. hehehe

IMG_20161102_162035_HDR.jpg

Trainingnya disana selama 5 hari jadi dari senin sampai hari jum’at kalau gak salah itu.

ini salah satu gedung di SMK6 balikpapan

img_20161105_173822_hdr

berikut suasana kelas pada saat training

img_20161101_101137_hdrimg_20161103_081953_hdrimg-20161102-wa0001img-20161102-wa0000img-20161102-wa0002

Salut buat guru guru SMK 6 Balikpapan yang masih semangat untuk belajar Mikrotik.

Meski jurusan berbeda-beda dan juga beda umur tapi tetap dipersatukan dengan ikatan persaudaraan islam.

img_20161101_111822_hdr

Setiap event diakhiri dengan foto bareng

img_20161105_151244_hdrimg_20161105_151220_hdr

oke, selesai training di SMK 6 Balipapan.

Bootcamp MTCINE – Sharing pengalaman

Bismillah

Bootcamp MTCINE tanggal 5 sampai 10 desember. Sebelumnya saya mau berterima kasih kepada Pak Dedi yang mengijinkan saya dan teman teman untuk mengikuti Bootcamp MTCINE 2016 ini.

Oke, Bootcamp MTCINE kali ini diadakan di Dago Highland tepatnya di bandung.

Ni foto pembukaan MTCINE bootcamp di IDN.

img_20161205_100502_hdr

Mungkin anda berfikir suasanya tegang karena tempatnya formal gitu. tapi tenang, disini tempat rapat nya cuman khusus untuk pembahasan materi, untuk lab nya bebas mau dimana.

 

 

gak percaya kalau tempatnya dibandung? ni saya kasih bukti foto yang diambil dari dago Highland. hehehe

IMG_20161205_120519_HDR.jpg

img_20161209_064601_hdr

img_20161209_064608_hdr

kalau masih gak percaya, ni foto yang ada saya nya

IMG_20161206_062852_HDR.jpg

percaya kan. hehehe

oke, itu suasana di dago highland bandung, dan tentu sangat nyaman untuk suasana belajar apalagi untuk bootcamp. joss lah.

ini sedikit suasana ruangan rapat, walau sebenarnya disini cuman bahas materi aja baru nanti lab nya sesuai enaknya dimana

IMG_20161205_100242_HDR.jpg

Oh ya, pada saat bootcamp jika juga kedantangan trainer asal malaysia namanya Pak Khomeini ( yang pakai baju biru dan juga pakai peci) beliau satu-satunya trainer dari malaysia. hehehe

IMG_20161208_082045_HDR.jpg

Oke, seperti biasa foto-foto bareng sama peserta bootcamp sebelum ujian

DSC_8539.JPG

dsc_8516dsc_8526

Yang kerennya itu disana saya ketemu banyak orang-orang yang sudah punya banyak pengalaman di bidang Network Enggineer

 

 

 

LAB BGP : eBGP Topologi Mesh

LAB BGP :  eBGP Topologi Mesh
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 rou ad ds 23.23.23.0/24 gat 12.12.12.2

R2 – IP ADDRESS
===========================================================================

admin@MikroTik] > sy ide se na IDN_R2
[admin@IDN_R2] > int br ad na IDN_R2
[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

R1 – IP ADDRESS
===========================================================================

[admin@MikroTik] > sy ide s na IDN_R3
[admin@IDN_R3] > int br ad na loopback
[admin@IDN_R3] > ip ad ad ad 23.23.23.3/24 int ether2
[admin@IDN_R3] > ip ad ad ad 3.3.3.3 int loopback

Set AS R1
===========================================================

[admin@IDN_R1] > rou bg ins set as=100
numbers: 0

Set AS R2
===========================================================

[admin@IDN_R2] > rou bg ins set as=200 
numbers: 0

Set AS R3
===========================================================

[admin@IDN_R3] > rou bg ins set as=300 0

R1 BGP Peeering
===========================================================

[admin@IDN_R1] > rou bg peer ad nam peer1 remote-address=12.12.12.2 remote-as=200

R2 BGP Peeering
===========================================================

[admin@IDN_R2] > rou bg pee ad na peer1 remote-address=12.12.12.1 remote-as=100 
[admin@IDN_R2] > rou bg pee add nam peer_R3 remote-address=23.23.23.3 remote-as=300

R3 BGP Peeering
===========================================================

[admin@IDN_R3] > rou bg pee ad nam peer_R2 remote-address=23.23.23.2 remote-as=200

CEK STATUS PEERING
===========================================================
R1
====

[admin@IDN_R1] > rou bg peer prin sta
Flags: X - disabled, E - established
0 E name="peer1" instance=default remote-address=12.12.12.2 remote-as=200 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=0s prefix-count=0 updates-sent=1 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

R2
====

[admin@IDN_R2] > rou bg pee pr sta
Flags: X - disabled, E - established
0 E name="peer1" 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=4h14m29s prefix-count=1 updates-sent=0 updates-received=1 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=300 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=1h4m7s prefix-count=0 updates-sent=1 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
===

[admin@IDN_R3] > rou bg pee pr sta    
Flags: X - disabled, E - established
0 E name="peer_R2" instance=default remote-address=23.23.23.2 remote-as=200 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=3s prefix-count=1 updates-sent=0 updates-received=1 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

TAMBAHKAN KONFIGURASI ROUTING
=============================
R1
======

[admin@IDN_R1] > ip rou ad ds 23.23.23.0/24 gat 12.12.12.2

R3
======

[admin@IDN_R3] > ip ro ad ds 12.12.12.0/24 gat 23.23.23.2

R1 CEK TABEL ROUTING
=============================

[admin@IDN_R1] > ip ro pr 
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADC 1.1.1.1/32 1.1.1.1 loopback 0
1 ADb 2.2.2.2/32 12.12.12.2 20
2 ADb 3.3.3.3/32 12.12.12.2 20
3 ADC 12.12.12.0/24 12.12.12.1 ether2 0
4 A S 23.23.23.0/24 12.12.12.2 1
[admin@IDN_R1] >

R2 CEK TABEL ROUTING
=============================

[admin@IDN_R2] > ip ro pr
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADb 1.1.1.1/32 12.12.12.1 20
1 ADC 2.2.2.2/32 2.2.2.2 loopback 0
2 ADb 3.3.3.3/32 23.23.23.3 20
3 ADC 12.12.12.0/24 12.12.12.2 ether1 0
4 ADC 23.23.23.0/24 23.23.23.2 ether3 0
[admin@IDN_R2] >

R3 CEK TABEL ROUTING
=============================

[admin@IDN_R3] > ip ro pr
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADb 1.1.1.1/32 23.23.23.2 20
1 ADb 2.2.2.2/32 23.23.23.2 20
2 ADC 3.3.3.3/32 3.3.3.3 loopback 0
3 A S 12.12.12.0/24 23.23.23.2 1
4 ADC 23.23.23.0/24 23.23.23.3 ether2 0
[admin@IDN_R3] >

TEST PING DARI R1 Ke semua IP Loopback

TEST PING 
================================
[admin@IDN_R1] > ping 1.1.1.1
SEQ HOST SIZE TTL TIME STATUS
0 1.1.1.1 56 64 2ms
1 1.1.1.1 56 64 1ms
sent=2 received=2 packet-loss=0% min-rtt=1ms 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 1ms
1 2.2.2.2 56 64 2ms
2 2.2.2.2 56 64 1ms
sent=3 received=3 packet-loss=0% min-rtt=1ms avg-rtt=1ms max-rtt=2ms

[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 2ms
2 3.3.3.3 56 63 2ms
sent=3 received=3 packet-loss=0% min-rtt=2ms avg-rtt=4ms max-rtt=9ms

[admin@IDN_R1] > ping 23.23.23.3
SEQ HOST SIZE TTL TIME STATUS
0 23.23.23.3 56 63 4ms
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=2ms max-rtt=4ms

[admin@IDN_R1] >

LAB BGP : eBGP Topologi Mesh

LAB BGP :  eBGP Topologi Mesh
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 rou ad ds 23.23.23.0/24 gat 12.12.12.2

R2 – IP ADDRESS
===========================================================================

admin@MikroTik] > sy ide se na IDN_R2
[admin@IDN_R2] > int br ad na IDN_R2
[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

R1 – IP ADDRESS
===========================================================================

[admin@MikroTik] > sy ide s na IDN_R3
[admin@IDN_R3] > int br ad na loopback
[admin@IDN_R3] > ip ad ad ad 23.23.23.3/24 int ether2
[admin@IDN_R3] > ip ad ad ad 3.3.3.3 int loopback

Set AS R1
===========================================================

[admin@IDN_R1] > rou bg ins set as=100
numbers: 0

Set AS R2
===========================================================

[admin@IDN_R2] > rou bg ins set as=200 
numbers: 0

Set AS R3
===========================================================

[admin@IDN_R3] > rou bg ins set as=300 0

R1 BGP Peeering
===========================================================

[admin@IDN_R1] > rou bg peer ad nam peer1 remote-address=12.12.12.2 remote-as=200

R2 BGP Peeering
===========================================================

[admin@IDN_R2] > rou bg pee ad na peer1 remote-address=12.12.12.1 remote-as=100 
[admin@IDN_R2] > rou bg pee add nam peer_R3 remote-address=23.23.23.3 remote-as=300

R3 BGP Peeering
===========================================================

[admin@IDN_R3] > rou bg pee ad nam peer_R2 remote-address=23.23.23.2 remote-as=200

CEK STATUS PEERING
===========================================================
R1
====

[admin@IDN_R1] > rou bg peer prin sta
Flags: X - disabled, E - established
0 E name="peer1" instance=default remote-address=12.12.12.2 remote-as=200 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=0s prefix-count=0 updates-sent=1 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

R2
====

[admin@IDN_R2] > rou bg pee pr sta
Flags: X - disabled, E - established
0 E name="peer1" 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=4h14m29s prefix-count=1 updates-sent=0 updates-received=1 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=300 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=1h4m7s prefix-count=0 updates-sent=1 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
===

[admin@IDN_R3] > rou bg pee pr sta    
Flags: X - disabled, E - established
0 E name="peer_R2" instance=default remote-address=23.23.23.2 remote-as=200 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=3s prefix-count=1 updates-sent=0 updates-received=1 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

TAMBAHKAN KONFIGURASI ROUTING
=============================
R1
======

[admin@IDN_R1] > ip rou ad ds 23.23.23.0/24 gat 12.12.12.2

R3
======

[admin@IDN_R3] > ip ro ad ds 12.12.12.0/24 gat 23.23.23.2

R1 CEK TABEL ROUTING
=============================

[admin@IDN_R1] > ip ro pr 
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADC 1.1.1.1/32 1.1.1.1 loopback 0
1 ADb 2.2.2.2/32 12.12.12.2 20
2 ADb 3.3.3.3/32 12.12.12.2 20
3 ADC 12.12.12.0/24 12.12.12.1 ether2 0
4 A S 23.23.23.0/24 12.12.12.2 1
[admin@IDN_R1] >

R2 CEK TABEL ROUTING
=============================

[admin@IDN_R2] > ip ro pr
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADb 1.1.1.1/32 12.12.12.1 20
1 ADC 2.2.2.2/32 2.2.2.2 loopback 0
2 ADb 3.3.3.3/32 23.23.23.3 20
3 ADC 12.12.12.0/24 12.12.12.2 ether1 0
4 ADC 23.23.23.0/24 23.23.23.2 ether3 0
[admin@IDN_R2] >

R3 CEK TABEL ROUTING
=============================

[admin@IDN_R3] > ip ro pr
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADb 1.1.1.1/32 23.23.23.2 20
1 ADb 2.2.2.2/32 23.23.23.2 20
2 ADC 3.3.3.3/32 3.3.3.3 loopback 0
3 A S 12.12.12.0/24 23.23.23.2 1
4 ADC 23.23.23.0/24 23.23.23.3 ether2 0
[admin@IDN_R3] >

TEST PING DARI R1 Ke semua IP Loopback

TEST PING 
================================
[admin@IDN_R1] > ping 1.1.1.1
SEQ HOST SIZE TTL TIME STATUS
0 1.1.1.1 56 64 2ms
1 1.1.1.1 56 64 1ms
sent=2 received=2 packet-loss=0% min-rtt=1ms 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 1ms
1 2.2.2.2 56 64 2ms
2 2.2.2.2 56 64 1ms
sent=3 received=3 packet-loss=0% min-rtt=1ms avg-rtt=1ms max-rtt=2ms

[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 2ms
2 3.3.3.3 56 63 2ms
sent=3 received=3 packet-loss=0% min-rtt=2ms avg-rtt=4ms max-rtt=9ms

[admin@IDN_R1] > ping 23.23.23.3
SEQ HOST SIZE TTL TIME STATUS
0 23.23.23.3 56 63 4ms
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=2ms max-rtt=4ms

[admin@IDN_R1] >

LAB BGP : iBGP Topologi Mesh

LAB BGP : iBGP Topologi Mesh
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
===============

[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] >

TAMBAHKAN KONFIGURASI ROUTING R1
===========================

[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
=========

[admin@IDN_R1] > ro bgp ins se as=100 0

Set AS R2
=========

[admin@IDN_R2] > ro bgp ins se as=100 0

Set AS R3
=========

[admin@IDN_R3] > ro bgp ins se as=100 0

Set BGP PEER R1
===============

[admin@IDN_R1] > rou bgp peer ad na peer_R2 remote-address=12.12.12.2 remote-as=100

Set BGP PEER R2
===============

[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

Set BGP PEER R3
===============

[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
===========================================

[admin@IDN_R1] > rou bgp net ad net 1.1.1.1/32

ADVERTISE NETWORK IP LOOPBACK R2 ================================

[admin@IDN_R2] > rou bgp net add net 2.2.2.2/32

PING ULANG KE 2.2.2.2 (LOOPBACK R2) ===================================

[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 =============================================================
[admin@IDN_R1] /routing bgp peer> add remote-address=23.23.23.3 remote-as=100

BGP PEERING R3 TO R1 =============================================================

[admin@IDN_R3] > rou bgp peer add remote-address=12.12.12.1 remote-as=100

TEST PING DARI R1 =============================================================

[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] >

LAB BGP : iBGP Topologi Mesh

LAB BGP : iBGP Topologi Mesh
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
===============

[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] >

TAMBAHKAN KONFIGURASI ROUTING R1
===========================

[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
=========

[admin@IDN_R1] > ro bgp ins se as=100 0

Set AS R2
=========

[admin@IDN_R2] > ro bgp ins se as=100 0

Set AS R3
=========

[admin@IDN_R3] > ro bgp ins se as=100 0

Set BGP PEER R1
===============

[admin@IDN_R1] > rou bgp peer ad na peer_R2 remote-address=12.12.12.2 remote-as=100

Set BGP PEER R2
===============

[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

Set BGP PEER R3
===============

[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
===========================================

[admin@IDN_R1] > rou bgp net ad net 1.1.1.1/32

ADVERTISE NETWORK IP LOOPBACK R2 ================================

[admin@IDN_R2] > rou bgp net add net 2.2.2.2/32

PING ULANG KE 2.2.2.2 (LOOPBACK R2) ===================================

[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 =============================================================
[admin@IDN_R1] /routing bgp peer> add remote-address=23.23.23.3 remote-as=100

BGP PEERING R3 TO R1 =============================================================

[admin@IDN_R3] > rou bgp peer add remote-address=12.12.12.1 remote-as=100

TEST PING DARI R1 =============================================================

[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] >