lab 4.2 EBGP Implementation

melanjutkan topology yang sebelumnya kalau sebelumnya kita sudah membuat area backbone BGP sebagai internal, kali ini kita akan membuat type External BGP dengan menambahkan  router C1 dan C2 sebagai EBGP.

Konfigurasi EBGP router C1

set logical-systems C1 interfaces ge-0/0/4 unit 0 family inet address 172.16.1.2/30
set logical-systems C1 interfaces lo0 unit 11 family inet address 172.16.100.1/32
set logical-systems C1 protocols bgp group EBGP family inet unicast
set logical-systems C1 protocols bgp group EBGP export export
set logical-systems C1 protocols bgp group EBGP neighbor 172.16.1.1 peer-as 487654321
set logical-systems C1 policy-options policy-statement export term 1 from protocol direct
set logical-systems C1 policy-options policy-statement export term 1 then accept
set logical-systems C1 routing-options autonomous-system 100

Konfigurasi EBGP router C2

set logical-systems C2 interfaces ge-0/0/6 unit 0 family inet address 172.16.2.2/30
set logical-systems C2 interfaces lo0 unit 12 family inet address 172.16.200.1/32
set logical-systems C2 protocols bgp group EBGP export export
set logical-systems C2 protocols bgp group EBGP neighbor 172.16.2.1 peer-as 487654321
set logical-systems C2 policy-options policy-statement export term 1 from protocol direct
set logical-systems C2 policy-options policy-statement export term 1 then accept
set logical-systems C2 routing-options autonomous-system 200

Konfigurasi EBGP router HONGKONG

set logical-systems HONGKONG interfaces ge-0/0/3 unit 0 family inet address 172.16.1.1/30
set logical-systems HONGKONG protocols bgp family inet unicast
set logical-systems HONGKONG protocols bgp group C1 neighbor 172.16.1.2 peer-as 100
set logical-systems HONGKONG protocols bgp group IBGP export nhs
set logical-systems HONGKONG policy-options policy-statement nhs term 1 from protocol bgp
set logical-systems HONGKONG policy-options policy-statement nhs term 1 then next-hop self

Konfigurasi EBGP router AMSTERDAM

set logical-systems AMSTERDAM interfaces ge-0/0/5 unit 0 family inet address 172.16.2.1/30
set logical-systems AMSTERDAM protocols bgp group IBGP family inet unicast
set logical-systems AMSTERDAM protocols bgp group C2 neighbor 172.16.2.2 peer-as 200
set logical-systems AMSTERDAM protocols bgp group IBGP export nhs
set logical-systems AMSTERDAM policy-options policy-statement nhs term 1 from protocol bgp
set logical-systems AMSTERDAM policy-options policy-statement nhs term 1 then next-hop self

EBGP Verification
Lakukan perintah berikut untuk memverifikasi EBGP pada router C1

Verifikasi EBGP router C1

lakukan tes ping ke IP Loopback router C2 dengan source 172.16.100.1

[edit]
root# run ping logical-system C1 172.16.200.1 source 172.16.100.1 count 5
PING 172.16.200.1 (172.16.200.1): 56 data bytes
64 bytes from 172.16.200.1: icmp_seq=0 ttl=60 time=270.302 ms
64 bytes from 172.16.200.1: icmp_seq=1 ttl=60 time=4.521 ms
64 bytes from 172.16.200.1: icmp_seq=2 ttl=60 time=5.844 ms
64 bytes from 172.16.200.1: icmp_seq=3 ttl=60 time=5.923 ms
64 bytes from 172.16.200.1: icmp_seq=4 ttl=60 time=4.112 ms

--- 172.16.200.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 4.112/58.140/270.302/106.083 ms

lakukan perintah berikut untuk memverifikasi EBGP pada router C2

Verifikasi EBGP router C2

lakukan tes ping ke IP Loopback router C1 dengan source 172.16.200.1

[edit]
root# run ping logical-system C2 172.16.100.1 source 172.16.200.1 count 5
PING 172.16.100.1 (172.16.100.1): 56 data bytes
64 bytes from 172.16.100.1: icmp_seq=0 ttl=60 time=7.121 ms
64 bytes from 172.16.100.1: icmp_seq=1 ttl=60 time=6.448 ms
64 bytes from 172.16.100.1: icmp_seq=2 ttl=60 time=4.137 ms
64 bytes from 172.16.100.1: icmp_seq=3 ttl=60 time=4.847 ms
64 bytes from 172.16.100.1: icmp_seq=4 ttl=60 time=65.124 ms

--- 172.16.100.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 4.137/17.535/65.124/23.818 ms

lakukan perintah berikut untuk meverifikasi EBGP pada router HONGKONG dan AMSTERDAM.

Verifikasi EBGP router HONGKONG dan AMSTERDAM