00:00:00
foreign
00:00:04
[Music]
00:00:09
welcome everybody to the season premiere
00:00:11
of Key points it's a networking show yes
00:00:15
it's a show where we're going to be
00:00:17
discussing final Concepts about
00:00:20
networking career routing switching
00:00:23
firewalling data center ACI sdy and SD
00:00:26
access name it anything that can cross
00:00:29
your mind when it comes to network
00:00:30
engineering I am Ahmed mufta a technical
00:00:33
training and design manager here in
00:00:35
Cisco and this is the first episode well
00:00:39
what do we have here we are going to
00:00:41
talk about sdn software defined
00:00:44
networking first of all let's welcome
00:00:46
this guy with us this is Give It Up to
00:00:51
Mr key yeah we're gonna call this guy Mr
00:00:53
key and he's going to be with us
00:00:55
throughout the series throughout the
00:00:57
episodes and he's going to be our
00:00:59
network engineer where we're expecting
00:01:02
things to be done by this engineer okay
00:01:05
so in terms of sdn what is Mr King gonna
00:01:08
do well before diving into sdn I would
00:01:12
just like to demonstrate how Mr key is
00:01:16
not having a pleasant time dealing with
00:01:19
tens or even hundreds or maybe even
00:01:22
thousands of network devices in a
00:01:24
traditional Network field you know he's
00:01:27
got to just manage all those devices by
00:01:29
himself maybe he has a team maybe he's
00:01:31
just you know alone who knows but the
00:01:34
bottom line is you trying to earn his
00:01:38
living by managing those devices when I
00:01:40
say manage the devices I mean configure
00:01:42
them one by one of course and then also
00:01:45
Monitor and troubleshoot anything that
00:01:47
might happen with those devices it's
00:01:48
complex it's not easy I know this is our
00:01:52
job and this is what he also does but
00:01:54
it's kind of complicated which is
00:01:56
difficult to configure difficult to
00:01:58
maintain who knows what kind of
00:02:00
configuration you're dealing with who
00:02:02
knows how many sites you're dealing with
00:02:04
or when it comes to configuration yes
00:02:08
you might be a ccae double C say e
00:02:10
triple it doesn't matter but end of the
00:02:12
day this is going to be difficult and
00:02:14
that's going to give you a poor user
00:02:17
experience and guess what Mr key is not
00:02:18
very happy and he might start looking
00:02:20
for another job we want to maintain this
00:02:22
guy so what do you want to do well
00:02:25
technically
00:02:26
let's talk about the device let's talk
00:02:28
about any network device devices in the
00:02:32
networking field let's say routers
00:02:34
switches any kind of network devices
00:02:36
we're talking we're looking at some uh
00:02:39
Catalyst uh 8000 switches right here and
00:02:42
uh whether this is a catalyst whether
00:02:44
this is a router it doesn't really
00:02:46
matter because they are made of three
00:02:48
major planes can you pause for a second
00:02:51
do you remember the planes any device
00:02:53
has three planes yeah remember well yeah
00:02:55
you got it the management plane when you
00:02:59
manage or when Mr key decides to manage
00:03:02
those devices by sshing or telnetting or
00:03:05
even using a GUI to access those routers
00:03:07
and switches and push the configuration
00:03:09
this is going to be handled by the
00:03:11
management plane let's not forget that
00:03:13
the second plane is your control plane
00:03:16
which enables those devices to send
00:03:19
control plane messages through uh you
00:03:22
know to each other so let's say for
00:03:24
example these are routers that try to
00:03:25
establish some kind of usbf neighborhood
00:03:27
that's going to happen through the
00:03:29
control plane and then when when they
00:03:31
become neighbors they need to make sure
00:03:34
that they do their job and every single
00:03:38
Network device where anywhere is
00:03:41
responsible for forwarding the data
00:03:44
traffic so that's where we call this the
00:03:46
data or forwarding plane why do we need
00:03:48
to even think about this we need to
00:03:50
remember these three planes because hey
00:03:52
in traditional networking every single
00:03:56
plane is independent which makes it
00:03:59
difficult again on each network engineer
00:04:01
including Mr T to manage those devices
00:04:04
configure them monitor them and in the
00:04:06
end this is going to be complicated a
00:04:09
complicated job we want to make our life
00:04:11
easier so what happened well what
00:04:15
happened is sdn was created what we're
00:04:18
not just talking about now we're just
00:04:20
talking about way back let's say
00:04:22
2010 2011 way back okay this is where
00:04:28
the fundamentals and concept the concept
00:04:31
of sdn yes sdn is a concept it's an
00:04:34
ocean where you're trying to deal with
00:04:37
those planes separately oh well tell me
00:04:40
more about that let's look at this
00:04:42
diagram look at this this is a bunch of
00:04:44
infrastructure infrastructure devices
00:04:46
and yes we're looking at a bunch of
00:04:47
Cubes I know but I'm just trying to
00:04:51
um deal with those cubes as if they are
00:04:54
any kind of network device doesn't
00:04:55
matter whether it's a router switch
00:04:56
server firewall doesn't matter what kind
00:04:58
of device because end of the day every
00:05:00
single Network device is made of three
00:05:02
planes yes management playing control
00:05:05
plane and data plane so what do you want
00:05:06
to do
00:05:07
you want to make your life easier you
00:05:08
want to make Mr T's job easier yeah who
00:05:11
cares what he does but anyways you need
00:05:13
a central management unit you need a
00:05:16
device which is gonna abstract the
00:05:20
control plane from each and every device
00:05:22
and be able to manage those devices no
00:05:25
matter how many devices you have
00:05:27
centrally so you're gonna have that
00:05:30
layer which represents a controller you
00:05:33
need a controller which is going to be
00:05:34
able to manage who knows how many
00:05:36
devices you have
00:05:37
don't forget we want to make our job
00:05:39
easier but let me ask you a question
00:05:41
what's easier dealing with those devices
00:05:44
using GUI graphical user interface let's
00:05:47
just write it down okay well I do have a
00:05:49
pen though so I want to use it uh so
00:05:52
yeah is it easier to use the GUI
00:05:55
or is it easier to use the CLI what do
00:05:59
you think I mean I'm not talking about
00:06:01
which is accurate and which is more
00:06:02
geeky okay I'm talking about the easiest
00:06:05
boss for a second yeah you got it with a
00:06:07
G GUI so you want to make sure that you
00:06:10
have the easiest possible experience so
00:06:13
let's put on top of this applications
00:06:16
which are going to be facing from on one
00:06:19
end the user which is you the network
00:06:20
engineer and from the other end it's
00:06:22
going to be facing the controller so
00:06:23
that you're going to be dealing with
00:06:24
that GUI to be able to push as many
00:06:27
configuration options to those tens or
00:06:30
hundreds of devices without even
00:06:32
thinking about suffering and these are
00:06:34
going to be considered policies but you
00:06:37
will need to just geek out sometimes and
00:06:40
you want to be like how will the
00:06:42
application deal with the controller
00:06:43
layer and how will the controller layer
00:06:45
translate your intent into whatever CLI
00:06:48
commands that the routers or switches
00:06:51
understand and the answer is three words
00:06:53
or three letters
00:06:56
apis application programmable interface
00:06:59
and this is the interface between the
00:07:02
controller layer and the application
00:07:04
layer from the Northbound or the
00:07:06
interface between the controllers and
00:07:09
the infrastructure devices from the
00:07:11
southbound so if I were to Define sdn
00:07:15
what would it be I mean yeah you don't
00:07:17
need to have a specific definition but
00:07:19
you can think about it but I might just
00:07:22
give you a solid answer here it is
00:07:24
software-defined networking what it is
00:07:26
in a nutshell
00:07:28
centralizes it centralizes management
00:07:31
Yeah by abstracting watch that word
00:07:33
abstracting the control plane from the
00:07:37
data plane yes and then be able to
00:07:40
manage that infrastructure centrally
00:07:44
from that controller all right well
00:07:46
that's good that makes our life easier
00:07:48
but guess what that's only about
00:07:51
managing and configuring what if I told
00:07:53
you that we need to utilize AI yes
00:07:57
artificial intelligence to be able to
00:08:01
collect information about your
00:08:03
infrastructure and draw some Trends yes
00:08:07
to be able to Monitor and troubleshoot
00:08:10
your network automatically not just push
00:08:12
configuration but Monitor and
00:08:14
troubleshoot the network automatically
00:08:16
and this is the
00:08:19
introduction to what Cisco calls Network
00:08:23
Assurance using AI well to to be able to
00:08:28
Monitor and assure
00:08:30
easy management and easy
00:08:33
troubleshooting and monitoring without
00:08:35
even having to interfere this is what we
00:08:38
decide to Define as
00:08:40
IBN and den based networking is sdn plus
00:08:45
Assurance so if I were to Define it what
00:08:48
it is well you can see it right here it
00:08:51
uses AI to add Assurance to the network
00:08:54
so it can automate a complete life cycle
00:08:57
and continuously align with the network
00:08:59
to business needs not just to be
00:09:02
fulfilling your job but you want to make
00:09:03
sure that your job fulfills the needs of
00:09:06
the business so I want to be clear here
00:09:08
about something sdn is an open standard
00:09:10
yes this is a concept which is used by
00:09:13
lots of vendors in this it world and
00:09:16
this is the foundational architecture
00:09:18
for decoupling again as I said the data
00:09:20
plane and the control plane well what
00:09:22
did Cisco do to contribute in this field
00:09:26
well Cisco has sdn as well and IBN and
00:09:30
this is the arc architecture for the sdn
00:09:33
implementation it's the intent based
00:09:36
networking where we have products
00:09:38
several products three major products to
00:09:41
be accurate and they're very famous uh
00:09:44
it all started way back in 2013 when
00:09:48
they first introduced ACI for the data
00:09:50
center this is Cisco's sdn for the data
00:09:54
center using Nexus 9k switches also they
00:09:58
kept going forward and they introduced
00:10:01
SD access for for the Enterprise land
00:10:03
they did not give up and they kept on
00:10:07
pushing and they also introduced sd-wan
00:10:10
for of course the Enterprise one keep
00:10:13
few words in mind when it comes to
00:10:15
controllers because that's the most
00:10:16
important word controllers that's the
00:10:17
central device that manages any network
00:10:19
when it comes to ACI the
00:10:21
application-centric infrastructure the
00:10:24
controller is the apic when it comes to
00:10:27
SD access your controller is the DNA
00:10:30
sent or the digital Network architecture
00:10:32
Center and sd-wan has the V manage
00:10:37
hey that being said let's hit the key
00:10:41
points for today oh first of all sdn is
00:10:45
the abstraction of control plane from
00:10:48
the data plane this is going to
00:10:50
centrally manage your network which is
00:10:53
gonna automate your network and make it
00:10:55
easier on you network Engineers whereas
00:10:58
IBN uses AI artificial artificial
00:11:01
intelligence to add Assurance Telemetry
00:11:04
monitoring and troubleshooting to your
00:11:06
network which is again as I said it's
00:11:08
gonna fully automate the network and
00:11:10
this is going to reduce the network
00:11:12
complexity
00:11:14
which is eventually going to make Mr key
00:11:18
happier I'm gonna wait for you again
00:11:20
here at Cisco U and we're going to
00:11:24
always experience new key points about
00:11:27
networking
00:11:28
thanks for watching
00:11:31
[Music]
