WEBVTT

1
00:00.000 --> 00:03.560
All right, let's do a quick review here of what we've learned.

2
00:03.560 --> 00:06.720
We're just going to go through a quiz here as our challenge.

3
00:06.720 --> 00:09.590
And I encourage you to pause the video to make sure you can answer these

4
00:09.590 --> 00:10.320
questions yourself

5
00:10.320 --> 00:11.760
before we answer them.

6
00:11.760 --> 00:16.160
So first up, which of the following is a Cisco term?

7
00:16.160 --> 00:19.480
So recall that we just spent a little bit of time on names.

8
00:19.480 --> 00:22.600
We might say this isn't a technical part of the conversation, but it is

9
00:22.600 --> 00:23.280
important to

10
00:23.280 --> 00:26.320
know what terms mean what in this industry.

11
00:26.320 --> 00:28.360
There's certainly plenty of them to go around.

12
00:28.360 --> 00:29.880
We're talking about a Cisco term.

13
00:29.880 --> 00:32.040
The answer is Ether channel.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.880 --> 00:32.040
The answer is Ether channel.

14
00:32.040 --> 00:36.150
Even though we use this all the time, at least those of us who work on Cisco

15
00:36.150 --> 00:36.680
equipment,

16
00:36.680 --> 00:41.570
we might not expect that it actually is a term created by Cisco for Cisco

17
00:41.570 --> 00:42.560
products.

18
00:42.560 --> 00:45.940
Everybody else uses the term port channel, and while we might use them

19
00:45.940 --> 00:46.880
interchangeably,

20
00:46.880 --> 00:50.400
we're not going to find Ether channels outside of the Cisco world.

21
00:50.400 --> 00:53.930
Lag and Nick teaming, Nick teaming being a server concept, but both of those

22
00:53.930 --> 00:54.400
are used

23
00:54.400 --> 00:58.570
outside of the Cisco world as well as inside the Cisco world with lag, but that

24
00:58.570 --> 00:58.960
is not

25
00:58.960 --> 01:01.280
a Cisco term.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:58.960 --> 01:01.280
a Cisco term.

26
01:01.280 --> 01:05.240
Question two, which type of Ether channel involves stackable switches and stack

27
01:05.240 --> 01:06.000
wise virtual

28
01:06.000 --> 01:07.840
peers?

29
01:07.840 --> 01:11.170
So this is a little bit more technical, and now we're talking about different

30
01:11.170 --> 01:12.160
Ether channel

31
01:12.160 --> 01:13.160
types.

32
01:13.160 --> 01:16.880
And so we've got the standard Ether channels that would just be between two

33
01:16.880 --> 01:17.560
devices.

34
01:17.560 --> 01:23.430
The MEC or the MCEC sometimes said, the multi-chassis Ether channel, this would

35
01:23.430 --> 01:24.320
be if I have

36
01:24.320 --> 01:29.340
stackable switches or maybe like a chassis switch, but either way, I'm going to

37
01:29.340 --> 01:29.480
take

38
01:29.480 --> 01:34.040
different physical switches and I'm going to create a bundle between them.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:29.480 --> 01:34.040
different physical switches and I'm going to create a bundle between them.

39
01:34.040 --> 01:37.600
However, it's one logical switch on each side.

40
01:37.600 --> 01:41.660
The virtual port channels where things get really crazy because we have one

41
01:41.660 --> 01:42.240
physical

42
01:42.240 --> 01:47.160
and one logical on this side, and then we've got another device down here.

43
01:47.160 --> 01:52.340
So we create that peer link, and then we can establish a VPC, and we can even

44
01:52.340 --> 01:52.880
go so

45
01:52.880 --> 01:58.630
far as to create another VPC peer and pairing down here, and then we create

46
01:58.630 --> 01:59.680
that bow tie

47
01:59.680 --> 02:04.120
VPCs, which can be done here with the MEC as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:59.680 --> 02:04.120
VPCs, which can be done here with the MEC as well.

48
02:04.120 --> 02:08.300
It just looks a little different because we typically are still drawing these

49
02:08.300 --> 02:09.280
out as single

50
02:09.280 --> 02:11.160
logical devices.

51
02:11.160 --> 02:12.520
And lastly, Nick teaming.

52
02:12.520 --> 02:16.170
Yeah, that's not quite the right answer here, but all that to say when we're

53
02:16.170 --> 02:17.280
talking about

54
02:17.280 --> 02:21.330
switches, stackable switches and stackwise virtual, naturally we see that B

55
02:21.330 --> 02:21.840
here is the

56
02:21.840 --> 02:25.720
answer based on the drawings that we sketched out.

57
02:25.720 --> 02:27.080
Alright, last question.

58
02:27.080 --> 02:30.670
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

58
02:27.080 --> 02:30.670
What is the maximum bandwidth a traffic flow can use on an ether channel

59
02:30.670 --> 02:31.520
consisting of

60
02:31.520 --> 02:33.840
8 10 gig links?

61
02:33.840 --> 02:37.840
Well, the answer, not to give it away too fast here, it's not Nick teaming.

62
02:37.840 --> 02:38.840
I don't know why.

63
02:38.840 --> 02:41.880
I couldn't resist putting Nick teaming on here a third time.

64
02:41.880 --> 02:45.440
Sometimes it seems like quizzes have a throwaway answer in here.

65
02:45.440 --> 02:50.100
But as far as the ether channel concept is concerned, always remember the

66
02:50.100 --> 02:50.880
analogy with

67
02:50.880 --> 02:56.110
the highway and the cars and the speed and the reality is that one traffic flow

68
02:56.110 --> 02:56.440
is going

69
02:56.440 --> 03:01.280
to be placed onto a single member interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:56.440 --> 03:01.280
to be placed onto a single member interface.

70
03:01.280 --> 03:08.810
So if this is eight separate 10 gig connections, we have 80 gig in total here

71
03:08.810 --> 03:10.160
and yet a single

72
03:10.160 --> 03:15.580
flow must be less than or equal to, that's coding, I suppose less than or equal

73
03:15.580 --> 03:16.480
to 10

74
03:16.480 --> 03:18.600
gigabits per second.

75
03:18.600 --> 03:21.500
Now remember that flows are identified based on all of their properties, source

76
03:21.500 --> 03:22.200
and destination

77
03:22.200 --> 03:26.040
max, source and destination IP and a few others in there.

78
03:26.040 --> 03:30.890
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

78
03:26.040 --> 03:30.890
And then we run it through a hash and that hash gives us a numerical output

79
03:30.890 --> 03:31.840
between zero

80
03:31.840 --> 03:33.040
and seven.

81
03:33.040 --> 03:37.920
And so all of the packets within a flow will get that same number through the

82
03:37.920 --> 03:38.360
hash.

83
03:38.360 --> 03:43.520
And based on the hash output is how we select which one of these links to be

84
03:43.520 --> 03:44.440
put onto.

85
03:44.440 --> 03:47.070
And so that's why we always want to make sure we have links of two, four, eight

86
03:47.070 --> 03:47.320
.

87
03:47.320 --> 03:52.840
So long as it's up to us, because that will keep the links the most balanced.

88
03:52.840 --> 03:58.120
So if any of these questions, you know, so shown some light, I suppose on a

89
03:58.120 --> 03:58.960
topic that

90
03:58.960 --> 04:01.530
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

90
03:58.960 --> 04:01.530
we're not super comfortable with, then be sure to go back and watch the

91
04:01.530 --> 04:02.000
appropriate

92
04:02.000 --> 04:05.240
video in order to fill up those knowledge gaps.

93
04:05.240 --> 04:07.890
And before we move on, I hope this has been informative for you and I'd like to

94
04:07.890 --> 04:08.280
thank you