November 2015 - Routecloud Indonesia

[Junos Routing] Cara Konfigurasi Routing RIP

November 27, 2015January 20, 2016 arisyi 2 Comments

Post Views: 3,106

Yeahhh…udah lama gk nulis, hehe…ini ane baru nulis lagi di blog routecloud,. oke kali ini mau ngebahas cara konekin router juniper menggunakan routing protokol rip, nah mari kita lihat gambar berikut ini supaya lebih jelas 🙂

Siippp..gambar sudah ada,,jadi tinggal config dah..

#01 Config IP di R1, R2, R3

R1:

set interfaces ge-0/0/0 unit 12 vlan-id 12
set interfaces ge-0/0/0 unit 12 family inet address 10.0.0.1/30
set interfaces ge-0/0/1 unit 0 vlan-id 1
set interfaces ge-0/0/1 unit 0 family inet address 172.16.0.1/32
set interfaces lo0 unit 1 family inet address 192.168.1.1/32

set interfaces ge-0/0/0 unit 12 vlan-id 12

set interfaces ge-0/0/0 unit 12 family inet address 10.0.0.1/30

set interfaces ge-0/0/1 unit 0 vlan-id 1

set interfaces ge-0/0/1 unit 0 family inet address 172.16.0.1/32

set interfaces lo0 unit 1 family inet address 192.168.1.1/32

R2:

set interfaces ge-0/0/1 unit 2 vlan-id 2
set interfaces ge-0/0/1 unit 2 family inet address 172.16.2.2/32
set interfaces ge-0/0/2 unit 12 vlan-id 12
set interfaces ge-0/0/2 unit 12 family inet address 10.0.0.2/30
set interfaces ge-0/0/2 unit 23 vlan-id 23
set interfaces ge-0/0/2 unit 23 family inet address 10.0.0.5/30
set interfaces lo0 unit 2 family inet address 192.168.2.2/32

set interfaces ge-0/0/1 unit 2 vlan-id 2

set interfaces ge-0/0/1 unit 2 family inet address 172.16.2.2/32

set interfaces ge-0/0/2 unit 12 vlan-id 12

set interfaces ge-0/0/2 unit 12 family inet address 10.0.0.2/30

set interfaces ge-0/0/2 unit 23 vlan-id 23

set interfaces ge-0/0/2 unit 23 family inet address 10.0.0.5/30

set interfaces lo0 unit 2 family inet address 192.168.2.2/32

R3:

set interfaces ge-0/0/0 unit 23 vlan-id 23
set interfaces ge-0/0/0 unit 23 family inet address 10.0.0.6/30
set interfaces ge-0/0/1 unit 3 vlan-id 3
set interfaces ge-0/0/1 unit 3 family inet address 192.168.3.3/32
set interfaces lo0 unit 3 family inet address 172.16.3.3/32

set interfaces ge-0/0/0 unit 23 vlan-id 23

set interfaces ge-0/0/0 unit 23 family inet address 10.0.0.6/30

set interfaces ge-0/0/1 unit 3 vlan-id 3

set interfaces ge-0/0/1 unit 3 family inet address 192.168.3.3/32

set interfaces lo0 unit 3 family inet address 172.16.3.3/32

#02 Setting Routing RIP

R1:

set protocols rip import rip-import
set protocols rip group rip-group export advertise-rip
set protocols rip group rip-group neighbor ge-0/0/0.12

set protocols rip import rip-import

set protocols rip group rip-group export advertise-rip

set protocols rip group rip-group neighbor ge-0/0/0.12

R2:

set protocols rip group rip-group export advertise-rip
set protocols rip group rip-group neighbor ge-0/0/2.12
set protocols rip group rip-group neighbor ge-0/0/2.23

set protocols rip group rip-group export advertise-rip

set protocols rip group rip-group neighbor ge-0/0/2.12

set protocols rip group rip-group neighbor ge-0/0/2.23

R3:

set protocols rip group rip-group export advertise-rip
set protocols rip group rip-group neighbor ge-0/0/0.23

1 2	set protocols rip group rip-group export advertise-rip set protocols rip group rip-group neighbor ge-0/0/0.23

#03 Konfigurasi Policy untuk meng-advertise protocol direct dan rip,

R1:

set policy-options policy-statement advertise-rip term 1 from protocol direct
set policy-options policy-statement advertise-rip term 1 from protocol rip
set policy-options policy-statement advertise-rip term 1 then accept

set policy-options policy-statement advertise-rip term 1 from protocol direct

set policy-options policy-statement advertise-rip term 1 from protocol rip

set policy-options policy-statement advertise-rip term 1 then accept

R2:

set policy-options policy-statement advertise-rip term 1 from protocol direct
set policy-options policy-statement advertise-rip term 1 from protocol rip
set policy-options policy-statement advertise-rip term 1 then accept

set policy-options policy-statement advertise-rip term 1 from protocol direct

set policy-options policy-statement advertise-rip term 1 from protocol rip

set policy-options policy-statement advertise-rip term 1 then accept

R3:

set policy-options policy-statement advertise-rip term 1 from protocol direct
set policy-options policy-statement advertise-rip term 1 from protocol rip
set policy-options policy-statement advertise-rip term 1 then accept

set policy-options policy-statement advertise-rip term 1 from protocol direct

set policy-options policy-statement advertise-rip term 1 from protocol rip

set policy-options policy-statement advertise-rip term 1 then accept

#04 Klo sudah selsai jangan lupa di commit, saatnya anda melakukan test, apakah R1, R2, R3 sudah saling tukar routing information? mari kita cek dengan show route.

root@R3# run show route protocol rip

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

10.0.0.0/30        *[RIP/100] 01:09:22, metric 2, tag 0
> to 10.0.0.5 via ge-0/0/0.23
172.16.0.1/32      *[RIP/100] 01:09:22, metric 3, tag 0
> to 10.0.0.5 via ge-0/0/0.23
172.16.2.2/32      *[RIP/100] 01:09:22, metric 2, tag 0
> to 10.0.0.5 via ge-0/0/0.23
192.168.1.1/32     *[RIP/100] 01:09:22, metric 3, tag 0
> to 10.0.0.5 via ge-0/0/0.23
192.168.2.2/32     *[RIP/100] 01:09:22, metric 2, tag 0
> to 10.0.0.5 via ge-0/0/0.23
224.0.0.9/32       *[RIP/100] 01:09:22, metric 1
MultiRecv

root@R3# run show route protocol rip

inet.0: 10 destinations, 11 routes (10 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.0/30 *[RIP/100] 01:09:22, metric 2, tag 0

> to 10.0.0.5 via ge-0/0/0.23

172.16.0.1/32 *[RIP/100] 01:09:22, metric 3, tag 0

> to 10.0.0.5 via ge-0/0/0.23

172.16.2.2/32 *[RIP/100] 01:09:22, metric 2, tag 0

> to 10.0.0.5 via ge-0/0/0.23

192.168.1.1/32 *[RIP/100] 01:09:22, metric 3, tag 0

> to 10.0.0.5 via ge-0/0/0.23

192.168.2.2/32 *[RIP/100] 01:09:22, metric 2, tag 0

> to 10.0.0.5 via ge-0/0/0.23

224.0.0.9/32 *[RIP/100] 01:09:22, metric 1

MultiRecv

nahh,,di R3 sudah dapat route ke 172.16.0.1 yang mana itu adalah ip R1, sory ye klo di gambar ip nya 172.16.1.1 hehe.. selanjutnya mari kita coba test ping

root@vMX-1# run ping 172.16.0.1 logical-system R3 rapid
PING 172.16.0.1 (172.16.0.1): 56 data bytes
!!!!!
--- 172.16.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.808/2.516/3.537/0.645 ms

[edit logical-systems R1]
root@vMX-1# run ping 172.16.0.1 logical-system R2 rapid
PING 172.16.0.1 (172.16.0.1): 56 data bytes
!!!!!
--- 172.16.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.307/1.414/1.606/0.112 ms

[edit logical-systems R1]
root@vMX-1# run ping 172.16.0.1 logical-system R1 rapid
PING 172.16.0.1 (172.16.0.1): 56 data bytes
!!!!!
--- 172.16.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.014/0.022/0.038/0.008 ms

root@vMX-1# run ping 172.16.0.1 logical-system R3 rapid

PING 172.16.0.1 (172.16.0.1): 56 data bytes

!!!!!

--- 172.16.0.1 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max/stddev = 1.808/2.516/3.537/0.645 ms

[edit logical-systems R1]

root@vMX-1# run ping 172.16.0.1 logical-system R2 rapid

PING 172.16.0.1 (172.16.0.1): 56 data bytes

!!!!!

--- 172.16.0.1 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max/stddev = 1.307/1.414/1.606/0.112 ms

[edit logical-systems R1]

root@vMX-1# run ping 172.16.0.1 logical-system R1 rapid

PING 172.16.0.1 (172.16.0.1): 56 data bytes

!!!!!

--- 172.16.0.1 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.014/0.022/0.038/0.008 ms

Sekian ya,, semoga membantu 🙂

arisyi

arisyi.net

Perintah Dasar Mininet dan OpenDaylight

November 19, 2015May 1, 2016 Alan Adi Prastyo 1 Comment

Post Views: 5,747

Sebelum mempelajari materi ini anda harus memahami terlebih dahulu materi Install Opendaylight Helium di Mininet 2.2.0

Aktifkan OpenDaylight

mininet@mininet-vm:~/opendaylight$ ./run.sh

1	mininet@mininet-vm:~/opendaylight$ ./run.sh

Sebelumnya anda harus install OpenDaylight dulu lihat pada materi sebelumnya “install Opendaylight Helium di mininet”

Mininet (default)

Username : mininet

Password : mininet

Buat Topologi Tree

mininet@mininet-vm:~$ sudo mn --controller=remote,ip=172.16.20.130 --topo tree,3
 
*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2 h3 h4 h5 h6 h7 h8
*** Adding switches:
s1 s2 s3 s4 s5 s6 s7
*** Adding links:
(s1, s2) (s1, s5) (s2, s3) (s2, s4) (s3, h1) (s3, h2) (s4, h3) (s4, h4) (s5, s6) (s5, s7) (s6, h5) (s6, h6) (s7, h7) (s7, h8)
*** Configuring hosts
h1 h2 h3 h4 h5 h6 h7 h8
*** Starting controller
c0
*** Starting 7 switches
s1 s2 s3 s4 s5 s6 s7
*** Starting CLI:
mininet>

mininet@mininet-vm:~$ sudo mn --controller=remote,ip=172.16.20.130 --topo tree,3

*** Creating network

*** Adding controller

*** Adding hosts:

h1 h2 h3 h4 h5 h6 h7 h8

*** Adding switches:

s1 s2 s3 s4 s5 s6 s7

*** Adding links:

(s1, s2) (s1, s5) (s2, s3) (s2, s4) (s3, h1) (s3, h2) (s4, h3) (s4, h4) (s5, s6) (s5, s7) (s6, h5) (s6, h6) (s7, h7) (s7, h8)

*** Configuring hosts

h1 h2 h3 h4 h5 h6 h7 h8

*** Starting controller

*** Starting 7 switches

s1 s2 s3 s4 s5 s6 s7

*** Starting CLI:

mininet>

Test Koneksi ke semua virtual host dengan pingall

mininet> pingall
*** Ping: testing ping reachability
h1 -> h2 h3 h4 h5 h6 h7 h8
h2 -> h1 h3 h4 h5 h6 h7 h8
h3 -> h1 h2 h4 h5 h6 h7 h8
h4 -> h1 h2 h3 h5 h6 h7 h8
h5 -> h1 h2 h3 h4 h6 h7 h8
h6 -> h1 h2 h3 h4 h5 h7 h8
h7 -> h1 h2 h3 h4 h5 h6 h8
h8 -> h1 h2 h3 h4 h5 h6 h7
*** Results: 0% dropped (56/56 received)

mininet> pingall

*** Ping: testing ping reachability

h1 -> h2 h3 h4 h5 h6 h7 h8

h2 -> h1 h3 h4 h5 h6 h7 h8

h3 -> h1 h2 h4 h5 h6 h7 h8

h4 -> h1 h2 h3 h5 h6 h7 h8

h5 -> h1 h2 h3 h4 h6 h7 h8

h6 -> h1 h2 h3 h4 h5 h7 h8

h7 -> h1 h2 h3 h4 h5 h6 h8

h8 -> h1 h2 h3 h4 h5 h6 h7

*** Results: 0% dropped (56/56 received)

Kalau outputnya seperti diatas berarti semua telah terkoneksi

Lihat pada OpenDaylight di Web Browser, http://<ip_address_opendaylight>:8080 (http://172.16.20.130:8080)

Penampilan topologi ketika di buat di mininet

Perintah Dasar Mininet

Reset Mininet

$sudo mn -c

1	$sudo mn -c

Ping h1 dengan h6

mininet> h1 ping h6
PING 10.0.0.6 (10.0.0.6) 56(84) bytes of data.
64 bytes from 10.0.0.6: icmp_seq=1 ttl=64 time=0.673 ms
64 bytes from 10.0.0.6: icmp_seq=2 ttl=64 time=0.110 ms
64 bytes from 10.0.0.6: icmp_seq=3 ttl=64 time=0.110 ms
64 bytes from 10.0.0.6: icmp_seq=4 ttl=64 time=0.134 ms

mininet> h1 ping h6

PING 10.0.0.6 (10.0.0.6) 56(84) bytes of data.

64 bytes from 10.0.0.6: icmp_seq=1 ttl=64 time=0.673 ms

64 bytes from 10.0.0.6: icmp_seq=2 ttl=64 time=0.110 ms

64 bytes from 10.0.0.6: icmp_seq=3 ttl=64 time=0.110 ms

64 bytes from 10.0.0.6: icmp_seq=4 ttl=64 time=0.134 ms

Test TCP Bandwth antara h2 dengan h5

mininet> iperf h2 h5
*** Iperf: testing TCP bandwidth between h2 and h5
*** Results: ['6.47 Gbits/sec', '6.48 Gbits/sec']

mininet> iperf h2 h5

*** Iperf: testing TCP bandwidth between h2 and h5

*** Results: ['6.47 Gbits/sec', '6.48 Gbits/sec']

cukup sekian dulu tutorial perintah dasar mininetnya, semoga bermanfaat.

Alan Adi Prastyo

System Engineer

www.routecloud.net

Install OpenDaylight Helium di Mininet 2.2.0

November 13, 2015May 1, 2016 Alan Adi Prastyo Leave a comment

Post Views: 3,287

OpenDaylight merupakan proyek opensource yang termasuk Sofware Defined Networking (SDN) yang di gunakan untuk controller.

Untuk menginstall OpenDaylight pada mininet, hal yang harus di perhatikan adalah

Download Mininet

ketika mininet running secara default open vswitch akan langsung aktif, untuk jaga” kita matikan dulu supaya tidak ada masalah saat kita install OpenDaylight

/etc/init.d/openvswitch-controller stop

1	/etc/init.d/openvswitch-controller stop

nanti kalo installasi selesai aktifkan lagi openvswitchnya

Update Package & install java untuk support OpenDaylight

apt-get update

apt-get install maven git openjdk-7-jre openjdk-7-jdk unzip

apt-get update

apt-get install maven git openjdk-7-jre openjdk-7-jdk unzip

Download OpenDaylight Helium ( Udah Stable nih)

wget https://jenkins.opendaylight.org/releng/view/controller/job/controller-merge-stable-helium/lastStableBuild/org.opendaylight.controller$distribution.opendaylight/artifact/org.opendaylight.controller/distribution.opendaylight/0.1.6-SNAPSHOT/distribution.opendaylight-0.1.6-SNAPSHOT-osgipackage.zip

unzip distribution.opendaylight-0.1.6-SNAPSHOT-osgipackage.zip

cd opendaylight/

export JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64

./run.sh

wget https://jenkins.opendaylight.org/releng/view/controller/job/controller-merge-stable-helium/lastStableBuild/org.opendaylight.controller$distribution.opendaylight/artifact/org.opendaylight.controller/distribution.opendaylight/0.1.6-SNAPSHOT/distribution.opendaylight-0.1.6-SNAPSHOT-osgipackage.zip

unzip distribution.opendaylight-0.1.6-SNAPSHOT-osgipackage.zip

cd opendaylight/

export JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64

./run.sh

Jalankan OpenDaylight di Web Browser

http://<ip_mininet_anda>:8080/

contoh : http://172.16.20.130:8080/
username dan passwordnya (admin & admin) Default

http://<ip_mininet_anda>:8080/

contoh : http://172.16.20.130:8080/

username dan passwordnya (admin & admin) Default

Tampilannya Gini ya

Akhirnya bisa juga install OpenDaylight, selamat mencoba

Kalo Gagal, coba terus sampe berhasil 🙂

Alan Adi Prastyo

System Engineer

Month: November 2015

[Junos Routing] Cara Konfigurasi Routing RIP

Perintah Dasar Mininet dan OpenDaylight

Install OpenDaylight Helium di Mininet 2.2.0

Tag Cloud

Posting Terbaru

Komentar