All right, let's do a quick review here of what we've learned.
We're just going to go through a quiz here as our challenge.
And I encourage you to pause the video to make sure you can answer these
questions yourself
before we answer them.
So first up, which of the following is a Cisco term?
So recall that we just spent a little bit of time on names.
We might say this isn't a technical part of the conversation, but it is
important to
know what terms mean what in this industry.
There's certainly plenty of them to go around.
We're talking about a Cisco term.
The answer is Ether channel. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The answer is Ether channel.
Even though we use this all the time, at least those of us who work on Cisco
equipment,
we might not expect that it actually is a term created by Cisco for Cisco
products.
Everybody else uses the term port channel, and while we might use them
interchangeably,
we're not going to find Ether channels outside of the Cisco world.
Lag and Nick teaming, Nick teaming being a server concept, but both of those
are used
outside of the Cisco world as well as inside the Cisco world with lag, but that
is not
a Cisco term. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
a Cisco term.
Question two, which type of Ether channel involves stackable switches and stack
wise virtual
peers?
So this is a little bit more technical, and now we're talking about different
Ether channel
types.
And so we've got the standard Ether channels that would just be between two
devices.
The MEC or the MCEC sometimes said, the multi-chassis Ether channel, this would
be if I have
stackable switches or maybe like a chassis switch, but either way, I'm going to
take
different physical switches and I'm going to create a bundle between them. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
different physical switches and I'm going to create a bundle between them.
However, it's one logical switch on each side.
The virtual port channels where things get really crazy because we have one
physical
and one logical on this side, and then we've got another device down here.
So we create that peer link, and then we can establish a VPC, and we can even
go so
far as to create another VPC peer and pairing down here, and then we create
that bow tie
VPCs, which can be done here with the MEC as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
VPCs, which can be done here with the MEC as well.
It just looks a little different because we typically are still drawing these
out as single
logical devices.
And lastly, Nick teaming.
Yeah, that's not quite the right answer here, but all that to say when we're
talking about
switches, stackable switches and stackwise virtual, naturally we see that B
here is the
answer based on the drawings that we sketched out.
Alright, last question.
What is the maximum bandwidth a traffic flow can use on an ether channel WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
What is the maximum bandwidth a traffic flow can use on an ether channel
consisting of
8 10 gig links?
Well, the answer, not to give it away too fast here, it's not Nick teaming.
I don't know why.
I couldn't resist putting Nick teaming on here a third time.
Sometimes it seems like quizzes have a throwaway answer in here.
But as far as the ether channel concept is concerned, always remember the
analogy with
the highway and the cars and the speed and the reality is that one traffic flow
is going
to be placed onto a single member interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to be placed onto a single member interface.
So if this is eight separate 10 gig connections, we have 80 gig in total here
and yet a single
flow must be less than or equal to, that's coding, I suppose less than or equal
to 10
gigabits per second.
Now remember that flows are identified based on all of their properties, source
and destination
max, source and destination IP and a few others in there.
And then we run it through a hash and that hash gives us a numerical output WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we run it through a hash and that hash gives us a numerical output
between zero
and seven.
And so all of the packets within a flow will get that same number through the
hash.
And based on the hash output is how we select which one of these links to be
put onto.
And so that's why we always want to make sure we have links of two, four, eight
.
So long as it's up to us, because that will keep the links the most balanced.
So if any of these questions, you know, so shown some light, I suppose on a
topic that
we're not super comfortable with, then be sure to go back and watch the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we're not super comfortable with, then be sure to go back and watch the
appropriate
video in order to fill up those knowledge gaps.
And before we move on, I hope this has been informative for you and I'd like to
thank you