All right, let's have a little bit of an interactive quiz session.
So I'm going to ask a question, be sure to pause the video, make sure you can
answer this
question before we get right into the answer.
So to start with, how does SD-WAN deliver a consistent, controllable
architecture over
a diversity of WAN circuit types?
So the whole premise of SD-WAN is I can have all kinds of complexity, again,
diverse WAN
circuit types, MPLS, Internet, LitFiber services, all kinds of things.
And I'm going to create my own architecture. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'm going to create my own architecture.
So anytime we're talking about software-defined networking, we have the overlay
concept,
which is the network I want, and we have the underlay, which is the network
that I have.
This is the way that we can kind of keep track of which one is which.
And so if I have a bunch of diverse circuit types, what I want is something a
little bit
more consistent and controllable.
And more often than not, I'm going to build that overlay using some form of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And more often than not, I'm going to build that overlay using some form of
tunneling mechanism.
Now we've got a lot of tunnels out there.
And the way that SD-WAN delivers it is C via IPsec tunnels.
A lot of data center deployments will use VXLAN.
We'll see that software-defined access uses VXLAN as well.
GRE and DMVPN are traditional ways that we can build tunnels in the network as
well.
But what we're going to find is even if we have something like DMVPN, we're
going to
want to build IPsec tunnels over the top of that, because this will be part of
the underlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the underlay
and we're still going to build our own overlay over the top of that.
So C IPsec tunnels, that is how we build out an SD-WAN architecture.
Question two, and there are four questions by the way.
What Cisco SD-WAN device is responsible for route distribution?
The answer here has to do with, well, it's route distribution, it's probably
our control
plane device, and our control plane device would be the VSmart.
Certainly one of the key takeaways from the skills is going to be making sure
we know
what all of these different devices are doing and which plane that they belong WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
what all of these different devices are doing and which plane that they belong
to.
In our case, VSmart belongs to control plane.
It's going to run that overlay management protocol or OMP routing protocol,
which is
very BGP-like in the way it behaves.
And we're going to push routes down to all of our WAN edge devices, informing
them of which
tunnels should be used for which types of traffic.
So right back to it with another SD-WAN device, which one has to have a public
IP address?
It's very important for us to understand this because it does speak to the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's very important for us to understand this because it does speak to the
responsibilities
of this particular device.
For example, we look at the planes of operation, we're going to look at that
orchestration plane,
and part of the responsibility of the orchestration plane is to do onboarding.
If we are going to onboard devices and form tunnels to one another, we might
have to perform
NAT traversal, and NAT traversal is going to require us to have that public IP
address,
which is one of the reasons why we're calling this out. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is one of the reasons why we're calling this out.
Ultimately, the orchestration plane device is indeed the VBond, so D would be
the answer
here.
It's going to have to sit somewhere with a public IP address.
We often do see them deployed into public clouds, and it's going to help our
devices get
onboarded and to be able to find one another.
And last question here, which SD-WAN device uses programmatic interfaces for
northbound,
which is using rest, and southbound, which is using net-conf communication.
So this gets into the fact that this is a software defined architecture, and as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this gets into the fact that this is a software defined architecture, and as
part of software
defined architectures, we expect controllers to be involved.
Well our controller is going to be part of the management plane, and as we said
earlier,
the name management, it's right there, it's our V-manage.
The V-manage is how we as admins log in and perform configuration via the
graphical
user interface, but I can also use some kind of API access, whether that's
using it manually
myself, maybe writing some Python scripts, or having an automation software WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
myself, maybe writing some Python scripts, or having an automation software
package out
there that does this for me.
And so this is what we call the northbound side of things.
And then the southbound side, we are pushing configuration out to the different
devices
out here, and this is going to use net-conf.
This is an architecture that's pretty common in SD, or SD, I'll just say
software defined
networking infrastructures, whether that's SD-WAN or SD-Ns, but either way, we
're often going
to find that on the user side of things that we like to use rest for API access WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to find that on the user side of things that we like to use rest for API access
, and net-conf
was built specifically to control networking devices, so it's not at all
uncommon to see
our admins using rest in our network devices relying on net-conf.
So this brings us to the end of this skill.
If we've this quiz identified any areas of weakness, it's a great opportunity
to go back
and maybe watch parts of the video again, or maybe take the quiz questions
again, just
to make sure that we've got it all down before moving on.
Either way, we're going to continue to dive into more details around how SD-WAN WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Either way, we're going to continue to dive into more details around how SD-WAN
comes
together.
At a foundational level, again, we do need to understand these four different
devices
and the four different planes in which they operate.
I hope there's been informative for you, and I'd like to thank you for viewing.