All language subtitles for Software Defined Networking - CompTIA A+ 220-1101 - 2

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:02,035 --> 00:00:03,169 The advent of cloud 2 00:00:03,169 --> 00:00:06,306 computing has changed networking in many ways, 3 00:00:06,306 --> 00:00:09,776 and if you're a network administrator, you know that in the cloud, we don't 4 00:00:09,776 --> 00:00:14,247 usually have physical routers, switches, and other infrastructure devices. 5 00:00:14,514 --> 00:00:18,451 Instead, we need to take these networking platforms we use in the real world 6 00:00:18,551 --> 00:00:22,355 and move them into the virtualized cloud based world. 7 00:00:22,622 --> 00:00:26,326 One way that we're able to do this is through the advent of software 8 00:00:26,326 --> 00:00:30,797 defined networking, or in with software defined networking, 9 00:00:30,797 --> 00:00:33,033 we take those devices like switches, 10 00:00:33,033 --> 00:00:36,803 routers, firewalls, and other networking infrastructure devices, 11 00:00:37,070 --> 00:00:42,809 and we change them to be a software based platform that we could use in the cloud. 12 00:00:43,043 --> 00:00:46,413 This means that we might take something like a switch and separate 13 00:00:46,413 --> 00:00:49,983 all of the functions of the switch into individual pieces. 14 00:00:50,150 --> 00:00:51,751 We can then take these pieces 15 00:00:51,751 --> 00:00:55,321 and then create software versions that we can then run in the cloud. 16 00:00:56,056 --> 00:01:01,094 There are commonly three layers or three ways to separate these devices, 17 00:01:01,094 --> 00:01:05,832 so that we can create some consistency across all of these networking components. 18 00:01:06,099 --> 00:01:08,735 The first layer would be the infrastructure layer. 19 00:01:08,735 --> 00:01:12,906 Sometimes we hear this referred to as the data plane of that device. 20 00:01:13,139 --> 00:01:16,242 So it's common that this data plane would do the forwarding, 21 00:01:16,242 --> 00:01:19,412 the trunking, the encrypting, the network address translation 22 00:01:19,412 --> 00:01:22,682 or anything else that needs to occur at that packet level. 23 00:01:23,183 --> 00:01:26,853 When our routers and switches need to for this traffic in the data plane, 24 00:01:26,986 --> 00:01:30,723 they need some type of reference to know where this traffic will be going. 25 00:01:30,924 --> 00:01:32,292 Most of those references 26 00:01:32,292 --> 00:01:36,196 will be in the control layer or control plane of that device. 27 00:01:36,362 --> 00:01:40,567 So if you have dynamic routing protocols, a forwarding table in a switch, 28 00:01:40,567 --> 00:01:43,369 a network address translation table, and a router, 29 00:01:43,369 --> 00:01:46,206 all of those are contained in the control plane. 30 00:01:46,206 --> 00:01:50,910 And of course, you or some other process is in charge of managing that device 31 00:01:51,077 --> 00:01:52,145 to be able to manage it. 32 00:01:52,145 --> 00:01:54,080 We need to log in or access 33 00:01:54,080 --> 00:01:57,684 the device via an API or application programing interface. 34 00:01:57,917 --> 00:01:59,719 And all of that access is provided 35 00:01:59,719 --> 00:02:03,423 at the application layer or management plane of that device. 36 00:02:03,623 --> 00:02:07,460 So when you SSH into a router, when you bring up a graphical 37 00:02:07,594 --> 00:02:12,465 front end of a firewall, you're managing that device from the management plane. 38 00:02:13,433 --> 00:02:16,503 Let's see how this software defined networking 39 00:02:16,503 --> 00:02:18,805 would apply to a physical device. 40 00:02:18,805 --> 00:02:21,508 And in this case, this physical device appears to be a switch. 41 00:02:21,508 --> 00:02:26,379 But this could be a router or firewall or any other infrastructure device. 42 00:02:26,579 --> 00:02:30,550 Let's start first with that infrastructure layer or the data plane. 43 00:02:30,750 --> 00:02:33,586 If you're connecting to a switch or you need traffic forwarded 44 00:02:33,586 --> 00:02:38,124 between different interfaces on a switch, that all occurs in that data plane. 45 00:02:38,324 --> 00:02:41,661 This means will take anything that may be forwarding this traffic on 46 00:02:41,661 --> 00:02:46,065 that device, and create a software version of that that we call the data plane. 47 00:02:46,533 --> 00:02:50,470 These devices also need the tables and forwarding structure to be able 48 00:02:50,470 --> 00:02:54,240 to understand where traffic is coming from and where you'll be forwarding it to, 49 00:02:54,474 --> 00:02:57,810 and all that occurs in the control layer or the control plane. 50 00:02:58,178 --> 00:03:01,848 And lastly, you'll be managing this device probably through a console port 51 00:03:01,848 --> 00:03:03,917 or management interface to the device. 52 00:03:03,917 --> 00:03:08,021 And that section of the device can be created as the management plane. 53 00:03:08,555 --> 00:03:11,991 Obviously with software defined networking, there is no physical device, 54 00:03:11,991 --> 00:03:15,795 but you can see where the data plane, control plane and management plane 55 00:03:15,962 --> 00:03:19,999 are pulled from our physical devices to create this software 56 00:03:19,999 --> 00:03:21,668 based networking infrastructure. 57 00:03:22,769 --> 00:03:23,136 This now 58 00:03:23,136 --> 00:03:27,840 creates modular layers that you can extend between devices or create 59 00:03:27,840 --> 00:03:31,377 new devices, all based on this software defined networking. 60 00:03:31,611 --> 00:03:34,681 If we start, for instance, at the bottom, we know that network traffic 61 00:03:34,681 --> 00:03:37,984 will be traversing different devices all at the data plane. 62 00:03:37,984 --> 00:03:42,789 So communication between those can occur solely between those particular layers. 63 00:03:43,056 --> 00:03:44,791 A device may need to send 64 00:03:44,791 --> 00:03:48,595 or receive dynamic routing protocols or create tables for forwarding. 65 00:03:48,795 --> 00:03:50,029 And all of those can be done 66 00:03:50,029 --> 00:03:54,167 at the control layer or the control plane of software defined networking. 67 00:03:54,334 --> 00:03:57,270 And the layer that you're going to manage these devices from 68 00:03:57,270 --> 00:03:59,205 will be the management plane. 69 00:03:59,205 --> 00:04:03,476 We usually access the management plane through Secure Shell Simple Network 70 00:04:03,476 --> 00:04:06,913 Management protocol or an application programing interface. 71 00:04:07,480 --> 00:04:10,016 You can see that the software defined networking takes these 72 00:04:10,016 --> 00:04:13,453 very standard categorizations and extends them across 73 00:04:13,453 --> 00:04:17,490 multiple networking devices to create a very modular architecture. 74 00:04:17,757 --> 00:04:21,628 This allows you to have a software based version of these network devices 75 00:04:21,628 --> 00:04:23,529 that we use on our physical networks, 76 00:04:23,529 --> 00:04:27,433 and be able to deploy them and use them in a cloud based infrastructure. 7479

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.