Presentation on how to chat with PDF using ChatGPT code interpreter
SDN Onboarding: Open vSwitch CLIs, OpenDaylight
1. SDN Onboarding: Spine Leaf Topology,
OVS CLIs and OpenDaylight
Telematika Open Session #10
Rabu, 11 April 2018
Lab Telematika
Sekolah Teknik Elektro dan Informatika
Institut Teknologi Bandung
Labtek 8 Lantai 4
3. “
Software Defined Network is emerging architecture that is
dynamic, manageable, cost-effective, and adaptable, making it
ideal for the high-bandwidth, dynamic nature of today’s
applications.
-Open Networking
Foundation
4. Mengapa SDN bisa tercipta?
• Companies like IBM, Burroughs, Honeywell - they
all made a killing doing everything for the
customer in mutually-exclusive, proprietary ways.
• Today we have open source, and Linux. People
buy or build their own systems (often now
virtual) and do their own thing.
5. Mengapa SDN bisa tercipta?
• Innovation is huge in compute.Today we have
open source, and Linux. People buy or build their
own systems (often now virtual) and do their
own thing.
• Contrast this with networking
6. Mengapa SDN bisa tercipta?
• for many years, people running data centers
wanted solutions that just work, were plug n' go,
and they were wiling to pay for that. And
innovation in networking was slow
• Today, data centers are exploding.
7. Mengapa SDN bisa tercipta?
• First, look at the generic architecture of a switch.
Switch consists of two main components -- the
control plane, and the forwarding plane.
• The forwarding plane is the hardware other than
CPU that makes sure packets are routed. And this
level of a switch is *fast*.
8. Mengapa SDN bisa tercipta?
• The control plane is the component where things
are configured, routing protocols live and do
their work, and the results find their way down
into the forwarding plane tables to control how
packets are routed.
9. Mengapa SDN bisa tercipta?
• Software defined networking (SDN) is a way to
exert control on the forwarding plane by writing
software to augment or replace portions of the
control plane on the switch. The SDN system
most associated with SDN is OpenFlow
10. Mengapa SDN bisa tercipta?
• OpenFlow allows the control plane to be co-
located on a compute node in a data center, as
well as an agent running on the switch.
• In simple terms, the compute node half of
OpenFlow can read stats from the switch, and
change the forwarding plane in response by
sending commands to the OpenFlow agent on
the switch.
31. Rest API dan OpenDaylight
Bagaimana Cara Mengatur Kontroller Menggunakan Rest API
32.
33. Persiapan
1. Siapkan Opendaylight, Switch OpenFlow, dan
Aplikasi Komunikasi Rest Api, misal Postman
2. Koneksikan Switch dengan Opendaylight
34. Persiapan
1. Siapkan Opendaylight, Switch OpenFlow, dan Aplikasi Komunikasi
Rest Api, misal Postman
2. Koneksikan Switch dengan Opendaylight
35. Akses Opendaylight Inventory
1. Akses untuk konfigurasi
switch berada di
opendaylight-inventory.
2. Terdapat dua pilihan,
operational untuk melihat
konfigurasi, dan config
untuk mengubah
konfigurasi
36. Contoh GET Informasi Node Openflow:1
http://[ipcontroller]:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:1
37. GET Menggunakan Postman
1. Masukan Auth Username: admin Password: admin
2. Masukkan Header Accept: application/xml dan Content-Type:
application/xml
38. GET Menggunakan Postman
1. Kirimkan Perintah GET ke URL
http://[IP_Controller]:8181/restconf/operational/opendaylight-
inventory:nodes/node/openflow:[ID_Node]
39. PUT Flow Menggunakan Postman
Terlebih dahulu, siapkan Flow dalam XML yang akan dikirimkan,
dokumentasinya ada di:
https://wiki.opendaylight.org/view/Editing_OpenDaylight_OpenFlow_
Plugin:End_to_End_Flows:Example_Flows
40. PUT Flow Menggunakan Postman
Kemudian, edit xml tersebut dan masukkan pada tab body
41. PUT Flow Menggunakan Postman
Kirimkan ke URL (dengan method PUT)
http://[IP_controller]:8181/restconf/config/opendaylight-
inventory:nodes/node/openflow:[ID_Node]/table/[ID_Table]/flow/[ID
_Flow]
Pastikan bahwa Table ID dan Flow ID URL sama dengan yang ada di
XML
42. PUT Flow Menggunakan Postman
Apabila keluar status 200 OK atau 201 Created, maka Flow sudah
berhasil dimasukkan ke switch.
root@mininet-vm:/home/mininet# ovs-ofctl dump-flows s1
NXST_FLOW reply (xid=0x4):
cookie=0x3, duration=7.149s, table=0, n_packets=0, n_bytes=0,
idle_age=7, priority=2,dl_src=00:00:00:00:00:01 actions=drop
50. Huh ?
◉ leaf terdiri dari access switch yang
umumnya digunakan untuk
menghubungkan server, firewall,
load balancer, dan edge router.
◉ spine terdiri dari switch yang
difungsikan untuk routing dan
menjadi backbone dari network
51. Why?
◉ +Masalah pada Spanning Tree Protocol,
mengeliminasi rute yang bukan rute utama
◉ + Skalabilitas
52. The ideas?
◉ menentukan switch mana yang berfungsi sebagai “spine” dan
sebagai “leaf” pada jaringan.
◉ Tiap “leaf” berfungsi seperti layaknya switch/L2, dan “spine”
berfungsi seperti layaknya router/L3
◉ Secara default, akan ada 2 mekanisme pengiriman flow dari
controller, active forwarding dan reactive forwarding.
◉ Active forwarding dilakukan saat awal sebelum jaringan siap
dengan memberikan set flow pada tiap device untuk kondisi
jaringan yang telah di prediksi.
53. The ideas?(2)
◉ Bila ada perubahan pada jaringan, akan terjadi
perubahan flow table dengan meminta flow pada
controller dengan meneruskan paket ke
controller. Disini terjadi proses reactive
forwarding
◉ Kontroller akan merespon dengan memberikan
set flow baru ke seluruh perangkat pada jaringan