Alright, this challenge is meant to walk us through the concepts of the border
nodes,
as well as our fabric access points and fabric wirelessly in controllers.
So let's just make sure that we know how these all attach to one another, and
also just sort
of solidify our concepts around how an SDA fabric operates.
So point number one here, or challenge number one, a new endpoint, endpoint one
here, has
just come online via switch one.
How does the fabric become aware of the endpoint?
So remember this concept of onboarding. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So remember this concept of onboarding.
When a new host shows up, the fabric edge node here, so edge node is switch one
in this
case, is going to perform a registration to the control plane node.
So we're going to use that map register message, but ultimately we're just
simply registering
this via LISP.
So LISP is the control plane, the protocol that we're using here, and then when
we get
into fabric operation, we know that, like let's say here, n.5 cents a packet
towards WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
towards
n.1, switch five can go out to find out where n.1 is.
But in order for us to go out and ask where it is, we need that EID to our lock
mapping.
So that's the endpoint identifier, that slash 32 route to the host.
And then the our lock would be essentially saying switch one here.
And now we have mapped our endpoint to a particular fabric edge node.
Number two, what type of border node is switch two and for that matter, which
one is switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
one is switch
three.
So when we're looking at what's connected behind the border nodes here, we see
that
we've got in both cases external networks, networks that are not part of the S
DA fabric.
So since we are connecting to our other internal routes off of switch two, that
makes this
an internal border node and switch three is connecting out to the internet,
that makes
this an external border node.
And question number three is going to drill into the differences, where asks, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And question number three is going to drill into the differences, where asks,
do the border
nodes register any endpoint identifiers with the control plane node in the same
way that
we do over here?
And the answer is the internal one does.
We are going to register all of the routes that we're learning here.
Remember, we're sharing routes back and forth with the rest of the network, and
we're going
to register those with the fabric.
The external does no such registration.
We are not registering anything because we are being treated by like a default
route.
And so if we don't know where to send something, we're just going to send it to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so if we don't know where to send something, we're just going to send it to
the nearest
external border node.
Question number four, where would a fabric access point and for that matter, a
fabric
wireless LAN controller be physically connected?
Well, fabric access points are going to connect to fabric edge nodes.
And so we could see access points connecting to both of these.
But then our fabric wireless LAN controller is also going to be connected here
off of
a fabric edge node.
And so remember, a wireless LAN controller in a fabric integrated environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so remember, a wireless LAN controller in a fabric integrated environment
is going
to be connected via fabric edge node.
What tunnel type is being used between the two, we are going to see that we're
still forming
capwap tunnels for the sake of the control plane.
Just remember that data plane does not use capwap.
It's going to form a separate VX LAN tunnel to the upstream fabric edge node.
And lastly, if we're using wireless over the top, where does the wireless LAN
controller
attach?
In this case, over the top, wireless LAN controller would be connected here on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In this case, over the top, wireless LAN controller would be connected here on
the other side
of the internal border node.
So let's make sure that we have down this whole process of what gets registered
when
things get registered.
And from a wireless perspective, where are access points and wireless LAN
controllers
attached depending on the architecture type?
I hope this has been informative for you, and I'd like to thank you for viewing
.