WEBVTT

1
00:00.000 --> 00:04.920
Alright, hopefully you had some fun configuring MST in the lab. If you had any

2
00:04.920 --> 00:05.320
problems,

3
00:05.320 --> 00:08.560
we're just going to go through all of the questions and make sure we have

4
00:08.560 --> 00:09.060
solutions

5
00:09.060 --> 00:13.280
for everything together here. So I'm going to start by configuring MST, so

6
00:13.280 --> 00:13.600
spanning

7
00:13.600 --> 00:17.950
tree mode MST on switch three, and I'll go ahead and configure those VLANs

8
00:17.950 --> 00:18.540
because

9
00:18.540 --> 00:21.740
that is what task one wants us to do. So we're going to go ahead and just do

10
00:21.740 --> 00:22.700
that configuration

11
00:22.700 --> 00:30.350
on all three switches, spanning tree mode MST, and then VLAN two through ten,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:22.700 --> 00:30.350
on all three switches, spanning tree mode MST, and then VLAN two through ten,

12
00:30.350 --> 00:31.340
spanning

13
00:31.340 --> 00:36.780
tree mode MST, VLAN two through ten. I'd like to verify, so if I do a do show

14
00:36.780 --> 00:36.960
spanning

15
00:36.960 --> 00:41.640
tree here, we'll see that we are indeed running MSTP. And if I do that show

16
00:41.640 --> 00:42.740
spanning tree

17
00:42.740 --> 00:47.030
MST config, we should see that all of the VLANs are mapped to instance zero,

18
00:47.030 --> 00:47.820
and that would

19
00:47.820 --> 00:52.330
be the default configuration. So task two asks us to configure some of these

20
00:52.330 --> 00:53.580
other parameters.

21
00:53.580 --> 00:57.920
So we're going to into spanning tree MST configuration mode here, and we want

22
00:57.920 --> 00:59.220
to configure a region

23
00:59.220 --> 01:07.120
name of CBTN. We want to configure a revision ID of one, and then we want to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.220 --> 01:07.120
name of CBTN. We want to configure a revision ID of one, and then we want to

24
01:07.120 --> 01:08.220
map VLANs one

25
01:08.220 --> 01:14.670
through five to instance five. So instance five, VLANs one through five, and

26
01:14.670 --> 01:15.820
then instance

27
01:15.820 --> 01:20.410
ten, we want the rest of the VLANs, VLANs six through ten. So notice we don't

28
01:20.410 --> 01:20.940
have to use

29
01:20.940 --> 01:25.250
instances one and two, for example, we can just use whatever instance IDs make

30
01:25.250 --> 01:25.660
sense

31
01:25.660 --> 01:30.600
that helps us to remember which VLANs are in which which instance. So I can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:25.660 --> 01:30.600
that helps us to remember which VLANs are in which which instance. So I can

32
01:30.600 --> 01:31.340
grab that

33
01:31.340 --> 01:36.570
configuration and copy that to make sure that we get it everywhere. So spanning

34
01:36.570 --> 01:37.420
tree MST

35
01:37.420 --> 01:43.820
config pasted in to switch four, and spanning tree MST config on switch five,

36
01:43.820 --> 01:45.060
and we'll paste

37
01:45.060 --> 01:49.130
it in. So that should give us our configuration. Again, I can do a show

38
01:49.130 --> 01:51.220
spanning tree MST config,

39
01:51.220 --> 01:56.120
make sure that the VLANs, oh, we haven't exited. So that is a nuance, and you

40
01:56.120 --> 01:56.740
may have noticed

41
01:56.740 --> 02:00.700
that in the lab yourself, that until we exit out of the config mode, it doesn't
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:56.740 --> 02:00.700
that in the lab yourself, that until we exit out of the config mode, it doesn't

42
02:00.700 --> 02:01.220
actually

43
02:01.220 --> 02:05.600
save. So let's go ahead and run that same command and confirm that now our

44
02:05.600 --> 02:06.260
instances

45
02:06.260 --> 02:10.530
are properly mapped. So we should be good to go there. Now task number three,

46
02:10.530 --> 02:10.900
configure

47
02:10.900 --> 02:14.550
switch three to be the root, and switch four to be the backup route for

48
02:14.550 --> 02:16.340
specific VLANs. So if I go

49
02:16.340 --> 02:20.590
to switch three, again, I can't do this on a per VLAN basis. So if I'm told to

50
02:20.590 --> 02:21.220
make this the

51
02:21.220 --> 02:25.090
root bridge for VLANs one through five, we're good, because that maps to an

52
02:25.090 --> 02:26.580
instance. If I were told

53
02:26.580 --> 02:29.830
to make it the root for VLANs three, four, and five, but not for one and two,

54
02:29.830 --> 02:31.220
that would be impossible
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:29.830 --> 02:31.220
that would be impossible

55
02:31.220 --> 02:36.130
with MST. It's all or nothing. So I'm going to go ahead and do the spanning

56
02:36.130 --> 02:37.540
tree MST five priority

57
02:37.540 --> 02:42.420
command. And I'll just configure that for 4096. And then likewise, spanning

58
02:42.420 --> 02:43.700
tree MST 10,

59
02:43.700 --> 02:48.020
with a priority of 81 92. Now you could have chosen different values for that.

60
02:48.020 --> 02:48.900
So whatever makes

61
02:48.900 --> 02:54.570
sense from your perspective to make sure that we're the primary for MST five

62
02:54.570 --> 02:55.540
and the backup for

63
02:55.540 --> 02:59.990
MST 10 for switch three, switch four is the opposite of that. We're going to do

64
02:59.990 --> 03:02.820
spanning tree MST of five
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:59.990 --> 03:02.820
spanning tree MST of five

65
03:02.820 --> 03:09.920
priority of 81 92 and spanning tree MST 10 priority of 4096. Now that does

66
03:09.920 --> 03:11.300
actually combine

67
03:11.300 --> 03:16.320
tasks three and four together, because three was asked to go to do one of those

68
03:16.320 --> 03:17.540
instances task

69
03:17.540 --> 03:22.110
forwards to do the other instance. So at this point, if I go to switch five, we

70
03:22.110 --> 03:23.780
should see if I do a

71
03:23.780 --> 03:28.450
show spanning tree root another great command that we use with rapid pvst plus

72
03:28.450 --> 03:30.020
and pvst plus alone.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:28.450 --> 03:30.020
and pvst plus alone.

73
03:30.020 --> 03:36.130
We see that MST five has a root port towards switch three and MST 10 has a root

74
03:36.130 --> 03:36.980
port towards

75
03:36.980 --> 03:41.870
switch four. So everything has configured appropriately here. The last couple

76
03:41.870 --> 03:42.980
tasks just for fun.

77
03:42.980 --> 03:48.100
Said go ahead and configure a hello timer for VLANs one through five. Well, as

78
03:48.100 --> 03:49.140
we might recall,

79
03:49.140 --> 03:53.390
we can't actually do just one through five, but we can accomplish the task by

80
03:53.390 --> 03:54.500
still setting a global

81
03:54.500 --> 03:59.540
hello time for MST to one. So that will set the hello timer to one second for V

82
03:59.540 --> 04:00.900
LANs one through five,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:59.540 --> 04:00.900
LANs one through five,

83
04:00.900 --> 04:04.030
but it will also do it for all the other VLANs as well. Technically, that's

84
04:04.030 --> 04:05.780
still a win. And we

85
04:05.780 --> 04:09.480
want to go ahead and copy this and paste it onto the other switches in case

86
04:09.480 --> 04:11.060
they become the root.

87
04:11.060 --> 04:15.890
Switch four is the root for some of those VLANs, but keep in mind, whoops,

88
04:15.890 --> 04:17.220
config T and then that.

89
04:17.860 --> 04:23.860
But since we were only told to ensure that it's happening on on on MST five, it

90
04:23.860 --> 04:24.660
really could just

91
04:24.660 --> 04:28.020
go on switch three and then we're really accomplishing what we set out to do

92
04:28.020 --> 04:29.780
until switch three goes

93
04:29.780 --> 04:34.100
down and switch four takes over because remember timers only matter on the root
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:29.780 --> 04:34.100
down and switch four takes over because remember timers only matter on the root

94
04:34.100 --> 04:35.780
bridge for that

95
04:35.780 --> 04:40.370
instance in this case. Last task switch five should be blocking on one of the

96
04:40.370 --> 04:41.540
ports for all of the

97
04:41.540 --> 04:47.430
VLANs. If we look back at our topology, we show that that would be blocking

98
04:47.430 --> 04:49.220
this link here to

99
04:49.220 --> 04:54.960
switch three for all of the all of the VLANs, all the instances. And we're told

100
04:54.960 --> 04:56.020
to only configure

101
04:56.020 --> 05:01.540
switch five for this task. Well, switch five is that would make it an inbound
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:56.020 --> 05:01.540
switch five for this task. Well, switch five is that would make it an inbound

102
05:01.540 --> 05:02.260
conversation.

103
05:02.260 --> 05:07.130
We want to adjust cost. So I can just really raise the cost on gig two slash

104
05:07.130 --> 05:08.100
one to make this

105
05:08.100 --> 05:12.790
happen. And I'd want to do it on all instances. So let's just go back to switch

106
05:12.790 --> 05:14.820
five interface.

107
05:14.820 --> 05:20.660
Gig two slash one, and we'll just do a spanning tree. And we could do this on

108
05:20.660 --> 05:22.980
just the instance

109
05:22.980 --> 05:26.570
where it's not blocking, which should be MST five. But I'm just going to go

110
05:26.570 --> 05:27.860
ahead and increase the

111
05:27.860 --> 05:32.150
cost for all of the instances. And we'll just increase this looks like we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:27.860 --> 05:32.150
cost for all of the instances. And we'll just increase this looks like we're

112
05:32.150 --> 05:33.300
dealing with 20

113
05:33.300 --> 05:37.450
K on all of these links. So I'll just increase it by 100,000. And that should

114
05:37.450 --> 05:38.740
do the trick. So if I

115
05:38.740 --> 05:43.740
do a show spanning tree blocked ports, we should now see that we're blocking to

116
05:43.740 --> 05:45.060
slash one for all

117
05:45.060 --> 05:49.150
of the instances. So this is a great opportunity for us to get comfortable with

118
05:49.150 --> 05:50.900
MST again, MST is

119
05:50.900 --> 05:54.650
is not starting from scratch. It's really all of the exact same concepts. We

120
05:54.650 --> 05:55.380
just have to start

121
05:55.380 --> 05:59.200
off by making sure our configurations are synced. It's those three parameters

122
05:59.200 --> 06:00.420
or really three
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:59.200 --> 06:00.420
or really three

123
06:00.420 --> 06:04.100
configurations, because two of them are parameters. One of them is a mapping

124
06:04.100 --> 06:05.460
system. But either way,

125
06:05.460 --> 06:09.060
as long as those three things are synchronized, then we're good to go. And we

126
06:09.060 --> 06:10.020
can use all of the

127
06:10.020 --> 06:14.030
same configuration commands we've been doing, and just swapping out VLAN IDs

128
06:14.030 --> 06:15.140
for instance IDs,

129
06:15.140 --> 06:18.740
because that's how MST operates. I hope this has been informative for you. And

130
06:18.740 --> 06:19.140
I'd like to

131
06:19.140 --> 06:20.100
thank you for viewing.