Alright, let's go ahead and review these questions together.
We have this scenario where we've got to put together some information on SDA,
which means
we better know a little bit of how this architecture comes together.
So the first question is simply what type of architecture is Cisco SDA, and the
answer
here is going to be that it's an access layer fabric.
It's not layer two or layer three, it's actually kind of both.
Now we're definitely not just organically connecting one switch to another, and
so it
is definitely a fabric.
Which two controllers are used in SDA. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Which two controllers are used in SDA.
All of these are valid Cisco products, but we're going to use Catalyst Center,
which
yeah, used to be known as DNA Center, and the Identity Services Engine, which
is ICE.
ICE is going to provide the security framework, leveraging Cisco TrustSec for
the enforcement
of that policy.
DNA Center is going to give us the automation and the management over the
fabric.
These other products, VManage, SD-WAN related, APIC is ACI related, both SD-N
products by
Cisco, but not SDA related and prime infrastructure at this point is a pretty WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Cisco, but not SDA related and prime infrastructure at this point is a pretty
legacy product.
Access layer switches will be deployed as which type of SDA node.
So remember we've got these three different types.
We do have wireless integration, but keep in mind we're talking about fabric
borders,
fabric control plane nodes, and fabric edge nodes.
And we're talking about the access layer switches themselves.
They will be fabric edge nodes.
They exist at the edge of the network and they're going to be forming VXLan
tunnels with
one another and sending traffic across the underlay, which is the layer three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
one another and sending traffic across the underlay, which is the layer three
network that
we build for our fabric.
So lastly, which plane of operation will each of these protocols be used in?
So we're talking about finding out, okay, so as CTS is, this is Cisco TrustSec
at which
plane of operation is this operating.
We are going to run CTS at the policy plane.
This is probably the most unique element of this conversation because the
policy plane
is not something we're used to talking about. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is not something we're used to talking about.
From SDA perspective, it's a very important part of it because Cisco wants
security to
be foundational to this product and this platform.
We talked about that earlier.
Security can't just be layered on anymore in modern network.
Everything has to be built with security in mind.
So that's why we have a policy plane to begin with to enforce our security
policies.
We also have a data plane in mind.
Whoops, let's click down here for a VXLan. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Whoops, let's click down here for a VXLan.
So we have a data plane that would be VXLan.
We're going to send our traffic through VXLan tunnels at the data plane if I
receive a packet
that is destined for a remote something in the network, probably a remote host
connected
to a different fabric edge node, then I'm going to insert it into a VXLan
tunnel and
forward it as part of the data plane.
And the control plane is how I find out where I'm sending it.
And we do use Lisp at the control plane in order to find out where I should be
sending
that traffic.
So all of these questions are intended to make sure that we understand the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So all of these questions are intended to make sure that we understand the
fabric, how
the fabric comes together, and a little bit about the architecture that Cisco
uses to
build their SDA product, which is going to give us that fabric and SDA based
network that
goes out to our access layer.
I hope there's been informative for you and I'd like to thank you for viewing.