Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:15,890 --> 00:00:21,950
So let's look at optimizing spending three Packet Tracer once again makes this easy.
2
00:00:21,950 --> 00:00:30,560
We can see that these ports are blocking in spanning tree and so is this port to confirm that On Call
3
00:00:30,560 --> 00:00:42,500
1 we can use the command shows spanning tree various v lines will be shown with this command he has
4
00:00:42,500 --> 00:00:55,610
VLAN one we can see that port gigabit 1 0 23 is forwarding 24 blocking 1 0 1 is forwarding but 2 and
5
00:00:55,610 --> 00:01:09,420
3 are blocking for VLAN 1 for VLAN 10 The result is the same VLAN 20 result is the same.
6
00:01:09,490 --> 00:01:15,460
Same is true for violent 30 and a villain 100 again.
7
00:01:15,580 --> 00:01:23,380
The problem is if lots of pieces in the access layer want to send traffic to lots of servers over here
8
00:01:23,470 --> 00:01:31,600
in the network all of their traffic has to go via court too and then it's going to be sent across the
9
00:01:31,600 --> 00:01:41,790
single gigabit 1 0 23 link to the servers that's not an optimal way of doing it now and a lot of cases
10
00:01:42,210 --> 00:01:49,110
access switches have multiple villains and you can improve the performance by sending some traffic using
11
00:01:49,110 --> 00:01:57,240
this uplink and some traffic using this uplink after the moment no user traffic uses this uplink at
12
00:01:57,240 --> 00:02:04,680
all because of this port of blocking no traffic uses this uplink because of this port is blocking no
13
00:02:04,680 --> 00:02:12,180
traffic uses this uplink because this port is blocking and the same is true about gigabit 1 0 24 the
14
00:02:12,180 --> 00:02:19,980
only traffic that is permitted out of a spanning tree port and accepted in on a spending tree port are
15
00:02:20,250 --> 00:02:30,680
network protocols such as CBP Alo DP spanning tree and a few others normal user traffic cannot use any
16
00:02:30,680 --> 00:02:38,450
of these links effectively and logically those ports have been disconnected from the network so those
17
00:02:38,450 --> 00:02:45,980
links are therefore redundancy but we are wasting the bandwidth on those links so let's optimize these
18
00:02:45,980 --> 00:02:53,760
spanning three network we've been told that call 1 should be the route for Ord v lands and co 2 the
19
00:02:53,760 --> 00:03:02,630
route for even v lands now in the exam it will be more clear than that but let's assume that our order
20
00:03:02,640 --> 00:03:10,730
v lands or VLAN 1 10 and 30 and or even v lands are 20 and 100.
21
00:03:11,250 --> 00:03:27,030
So on call 1 spanning tree v land 1 route primary you can do it that way or you can specify priority
22
00:03:27,780 --> 00:03:29,560
and specify a priority.
23
00:03:29,900 --> 00:03:36,870
I'd like to use the property of zero event lowers the spending tree property to the lowest possible
24
00:03:36,870 --> 00:03:44,640
number in the exam it'll be more clear about which option you should use.
25
00:03:44,640 --> 00:03:50,970
So for VLAN 1 tenant 30 I'm gonna make this switch the route.
26
00:03:50,970 --> 00:03:58,530
Notice how the colors have changed all ports are now forwarding they green ways before they went to
27
00:03:58,530 --> 00:04:09,570
Green on court to for those v lands we want to have that switch as the backup route you want to keep
28
00:04:09,570 --> 00:04:21,940
your core switches as routes so spanning tree V Line 1 priority notice it needs to be in multiples of
29
00:04:21,940 --> 00:04:33,910
four thousand and ninety six so for V Line one V Line Chen and a villain 30 we going to make that switch
30
00:04:34,270 --> 00:04:44,420
the backup route so now when we look at call 1 show spending treat villain one.
31
00:04:44,480 --> 00:04:50,030
Notice the switch is the root to switch for villain one.
32
00:04:50,090 --> 00:04:51,840
It has a property of one.
33
00:04:52,040 --> 00:04:59,420
The reason why it's a property of one is that the property is determined by the actual property plus
34
00:04:59,480 --> 00:05:00,210
the V land.
35
00:05:00,210 --> 00:05:08,240
No notice properties 0 plus extended system my D so 0 plus 1 is 1 giving the local switch a property
36
00:05:08,240 --> 00:05:10,720
of 1 and the switch is the root.
37
00:05:10,790 --> 00:05:14,480
So that's the property of the root switch.
38
00:05:14,480 --> 00:05:15,890
When we look at the ports.
39
00:05:15,890 --> 00:05:18,170
Notice all ports of forwarding.
40
00:05:18,170 --> 00:05:29,110
What about the second switch core to show spanning tree VLAN 1 what you'll notice is all ports of forwarding
41
00:05:29,620 --> 00:05:30,920
except for gigabit.
42
00:05:30,950 --> 00:05:32,810
1 0 24.
43
00:05:33,010 --> 00:05:40,250
Now the indicators in packet tracer are green because it's not showing us the output for all v lands
44
00:05:41,020 --> 00:05:43,540
the V lands do differ.
45
00:05:43,540 --> 00:05:48,580
So as an example back on call 1 show spanning tree VLAN 20.
46
00:05:48,700 --> 00:05:53,550
Notice a lot of ports are still blocking on the switch.
47
00:05:53,680 --> 00:05:58,960
So call 1 is not the route for VLAN 20.
48
00:05:59,170 --> 00:06:09,080
Another switch is the route for VLAN 20 if we have a look on code to show spanning tree v land 20 the
49
00:06:09,170 --> 00:06:18,250
switches the router for or backed a villain a villain 20 and it has all ports forwarding so packet tracer
50
00:06:18,430 --> 00:06:22,620
and a real switch will not show Amber or orange.
51
00:06:22,780 --> 00:06:30,070
If you're using pervy land spanning tree and a trunk port is blocking on some v lands and not on other
52
00:06:30,070 --> 00:06:31,480
v lands.
53
00:06:31,480 --> 00:06:40,480
Okay sir show run pipe include spending tree events the configuration of thus far under the switch show
54
00:06:40,480 --> 00:06:50,200
run pipe include spending tree that's our configuration notice we can specify all the V lands in one
55
00:06:50,200 --> 00:07:01,680
go my doing the following so we want the switch to be the route for v lands twenty and V lands one hundred
56
00:07:02,790 --> 00:07:12,460
suspending TV Land twenty and one hundred property zero on the side spanning tree v land twenty one
57
00:07:12,460 --> 00:07:16,840
hundred property four thousand and ninety six.
58
00:07:16,840 --> 00:07:24,610
It's good practice to have your core switches being root switches and backup routes for other v lands
59
00:07:26,550 --> 00:07:35,550
so show spanning tree v land twenty notice it's still going through different states previously however
60
00:07:35,580 --> 00:07:45,300
we had a lot of blocking ports for VLAN 20 on call one that will hopefully now improve and there you
61
00:07:45,300 --> 00:07:46,080
go.
62
00:07:46,080 --> 00:07:53,140
The only port that's blocking is gigabit 1 0 24 for that villain.
63
00:07:53,370 --> 00:07:57,870
All other ports are forwarding so that's much better.
64
00:07:57,870 --> 00:08:07,640
We've been able to optimize spanning tree by making call one the route for some v lands and court to
65
00:08:07,640 --> 00:08:10,200
the route for other v lands.
66
00:08:10,260 --> 00:08:19,260
That means that if we had v VLAN 10 and 20 connected to the switch V Line 10 traffic would take this
67
00:08:19,260 --> 00:08:27,740
uplink a v land 20 traffic would take this uplink and on the switch the land 10 would go to call 1 v
68
00:08:27,750 --> 00:08:38,460
land 20 would go to court 2 and on the switch v land 30 would go to call 1 v land 20 would go to court
69
00:08:38,460 --> 00:08:46,540
2 we still have a problem however because the links between the two switches are still blocking.
70
00:08:46,570 --> 00:08:59,080
So again show spanning tree v land twenty notice on call 1 this port is blocking for veal and 20 and
71
00:08:59,080 --> 00:09:10,530
it's blocking for v land 100 hundred on the side show spending tree v land 1 port 24 is blocking for
72
00:09:10,530 --> 00:09:23,130
v land 1 for v land 10 and for v land 30 we want to combine or join these two links in an ether channel
73
00:09:23,370 --> 00:09:25,510
to get better throughput.
74
00:09:25,890 --> 00:09:28,310
So that's what we're gonna do in the next video.
8594
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.