Alright, let's identify these blocks.
And if you haven't yet done so, be sure to just pause the video and even if you
don't
have a pencil and paper available, just sort of mentally check off which of
these blocks
would serve which functions.
But either way, let's go ahead and dive into this.
Probably is best to start in the middle.
If we have a true core layer, then we can expect to see this block in the
middle that connects
to many other blocks.
And we can move over to this site over here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we can move over to this site over here.
And if we have a dedicated site with users connecting in, we're probably going
to see
a distribution and access block.
And because we don't see any users coming into the distribution, it's not
collapsed in
any way.
We're not collapsing the core into the distribution or the access into the
distribution.
This is a true three-tier design for Site 1.
Meanwhile, we have this other small site.
And we see that we've got kind of interestingly here.
We've got users connecting in to a block that directly connects to the core. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We've got users connecting in to a block that directly connects to the core.
Well, at this point, we know we don't have a three-tier model.
This is a two-tier model.
And that second tier is going to consist of both distribution and access
functionality.
So it's a collapsed distribution access block.
Now moving over to the data center.
Again, the data center is going to parallel a campus architecture or a campus
site.
It's just instead of a distribution block, we're going to have an aggregation
block.
Aggregation has roughly the same role as distribution. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Aggregation has roughly the same role as distribution.
We're just going to see different protocols that play, especially as we've
talked about
virtual port channeling.
It's something we can expect in the aggregation block.
Now outside of that, we're just going to have a standard access layer that
connects our
data center appliances, servers, storage, whatever is there.
And we can refer to this as the data center access block if we so desired to
try to distinguish
from a campus site access block.
Now the other blocks are going to be based on what connects on the other side.
We see remote sites are coming in to this block in the upper right. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We see remote sites are coming in to this block in the upper right.
Those would probably be wide area network connected.
Anytime we see these lighting bolt zigzag connections in a network diagram, we
're usually
looking at some kind of circuit to connect out to remote locations where we
just can't
connect in via the local area network.
So that would be wide area network connectivity.
And then we also have this block here, which is our internet block.
As indicated by the fact that the internet is coming in here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
As indicated by the fact that the internet is coming in here.
So the internet block is probably going to consist of firewalls.
And depending on our architecture, and maybe if we have multiple internet
circuits coming
in, we might also see some routers in here as well.
And then we could run BGP to participate in the internet routing or maybe we
just receive
a default route.
Again, it depends on the scope and scale of our internet architecture.
But this is how we would build out this model.
And again, we want to make sure we understand the functionality that each block WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And again, we want to make sure we understand the functionality that each block
brings to
the table.