The primary takeaway from this conversation is going to be making sure we can
identify
which features belong at which layer.
For example, I would never expect to deploy power over ethernet or QOS tagging
into the
core or distribution layers, and that's going to apply to a lot of the other
conversations
that we had here as well.
So let's start with one of these matches.
Match the feature to its corresponding network layer.
For fast layer three switching, that belongs at the core layer every single
time.
That is our primary care about at the core layer. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That is our primary care about at the core layer.
In fact, FHRP is these belong at the distribution layer.
This would be for redundant gateway access.
Ultimately, it's going to allow us to survive a failure of one distribution
switch from
a gateway perspective.
And then QOS and VLAN marking process of elimination would be access layer, but
again, it makes
sense to have these happening at the edge of our network.
Next, we've got power over ethernet.
And where do I connect my access points and my phones?
They go at the access layer. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
They go at the access layer.
My spanning tree root, that is going to be a layer two concept.
Spanning tree does not belong in the network core.
And we certainly don't want the root in the access layer.
So that means it goes in the distribution layer.
And then fully featured routing protocols, that would go into the core layer
because we're
not going to be running stub, for example, stub areas inside of the network
core.
And lastly, match the feature, the same question, I suppose.
So high bandwidth links and overall throughput, the highest links and the most WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So high bandwidth links and overall throughput, the highest links and the most
overall throughput
is going to go into the core layer, that QOS trust boundary that we mentioned.
Remember, we have to decide which devices we trust and which we don't.
That is an access layer feature and summary route advertisements.
So once more, if we have a bunch of routes at the distribution layer, ideally,
we summarize
that, we perform summarization at the distribution layer, sending only summar
ized routes to the
core layer, which will reduce the routing table size of our core and ultimately WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
core layer, which will reduce the routing table size of our core and ultimately
of the entire
rest of the network.
So those are the features and where they belong.
Again, we need to make sure that if we are looking at a layer that we can
identify the
needs of that layer and especially compare that to the needs of the other
layers, make sure
we understand why does QOS tagging exist at the access layer and why does
summarization
exist to distribution.
The more we understand about the architecture, the more it's going to be very
logical where
these features belong and that's going to help us to be able to properly WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
these features belong and that's going to help us to be able to properly
identify them
when we need to do so.
I hope there's been informative for you and I'd like to thank you for viewing.