1
00:00:00,840 --> 00:00:09,140
So in apology let's determine why certain ports are set to forwarding and why certain ports are blocking.

2
00:00:09,330 --> 00:00:12,010
So we'll work through the spending tree process.

3
00:00:12,120 --> 00:00:16,740
The first decision that needs to be made is election of a root bridge.

4
00:00:17,040 --> 00:00:22,440
So one of the switches in the typology needs to become the root of the spending tree.

5
00:00:23,230 --> 00:00:33,440
So on switch one as we saw previously show spending tree shows us that the switch or bridge is the root

6
00:00:33,440 --> 00:00:34,480
of the spending tree.

7
00:00:35,390 --> 00:00:36,420
Switch to the

8
00:00:39,700 --> 00:00:42,440
is not the root of the spending tree.

9
00:00:43,460 --> 00:00:49,740
So the outputs here we can see that it has a path cost to get to the root switch.

10
00:00:49,790 --> 00:00:55,520
It seems that the route bridge or route switch has a route ID with a party of this and MAC address of

11
00:00:55,520 --> 00:00:59,350
this which is different to the local switch MAC address.

12
00:01:00,160 --> 00:01:03,780
So first decision how is the route determined.

13
00:01:03,940 --> 00:01:11,470
It's based on lowest bridge ID which consists of the property and MAC address so which one has the same

14
00:01:11,470 --> 00:01:15,370
priority as switch 2 3 2 7 6 9.

15
00:01:15,370 --> 00:01:19,310
So that cant be used to determine the spanning tree route.

16
00:01:19,330 --> 00:01:24,950
So the tie breaker is based on the MAC address so lowest MAC address will one switch.

17
00:01:24,960 --> 00:01:28,940
One has a lower MAC address when compared to switch to.

18
00:01:29,200 --> 00:01:34,390
Once again 0 0 1 1 is the same on both switches.

19
00:01:34,570 --> 00:01:40,540
But notice C-6 e a is greater than C-Six a C in hexadecimal.

20
00:01:40,570 --> 00:01:43,600
So switch one becomes the root of the spanning tree.

21
00:01:44,250 --> 00:01:46,060
So that's the first decision.

22
00:01:46,170 --> 00:01:48,270
Determine the route bridges.

23
00:01:48,750 --> 00:01:52,080
Once again Protea 6:57 6:08 is the default.

24
00:01:52,080 --> 00:01:55,660
So we've now determined to route bridges or route switches.

25
00:01:55,920 --> 00:02:03,240
The next decision is that every non routes switch needs to determine its route port the route port is

26
00:02:03,240 --> 00:02:06,180
its best port to get to the root bridge.

27
00:02:06,570 --> 00:02:10,840
The route to Port is chosen based on lowest Poth cost.

28
00:02:11,010 --> 00:02:15,580
If there's a tie breaker on that then it's based on lowest neighbor bridge ID.

29
00:02:15,870 --> 00:02:22,810
If Poth costs are the same if that can be used to determine the route port then the lowest port priority

30
00:02:22,810 --> 00:02:23,630
is used.

31
00:02:23,820 --> 00:02:26,310
The poor priority is 128 by default.

32
00:02:26,580 --> 00:02:32,610
And if that can't be used then the lowest port IDs used as a tiebreaker.

33
00:02:32,640 --> 00:02:35,920
So first decision is based on lowest possed cost.

34
00:02:36,210 --> 00:02:40,500
Here's a table showing you the path costs of Siska switches.

35
00:02:40,680 --> 00:02:52,080
They are either based on a 1998 triple E cost or 2004 I triple E cost in the 1998 cost values a 10 meg

36
00:02:52,080 --> 00:03:02,660
link has a cost of 100 hundred make 19 1 gig 4 and 10 gig to in the triple E cost in 2004 and later

37
00:03:03,090 --> 00:03:05,700
the costs change to the following.

38
00:03:06,180 --> 00:03:14,040
So in our typology we have gig interfaces on the switches and if we look at the path cost of various

39
00:03:14,040 --> 00:03:18,260
ports notice the value associated is full.

40
00:03:18,570 --> 00:03:26,160
So these gigabit links have a pot cost a value of four which means that the switches are using the old

41
00:03:26,430 --> 00:03:31,420
Poth cost method to determine the best path to a destination.

42
00:03:32,400 --> 00:03:40,290
The first decision is to determine the route port based on the path cost in this typology we have gigabit

43
00:03:40,290 --> 00:03:44,680
to 00 connected directly to switch 1 gigabit.

44
00:03:44,680 --> 00:03:48,480
0 1 is also directly connected to switch 1 gigabit.

45
00:03:48,480 --> 00:03:56,550
0 3 is connected to a hub which in turn is connected to switch one.

46
00:03:56,650 --> 00:04:03,480
So the path cost of gigabit in 0 3 would be 8 if there was a switch connected to here.

47
00:04:03,640 --> 00:04:10,210
But at the moment the power cost is four because we have a hub instead of a switch.

48
00:04:10,390 --> 00:04:18,020
So we have three ports with the same path cost to get to switch one on switch two we can top show spending

49
00:04:18,010 --> 00:04:26,680
tree root as an example and we can see that gigabit 00 was chosen as the root port to get to switch

50
00:04:26,680 --> 00:04:33,340
one but that couldn't have been determined based on the path cost it would need to be determined based

51
00:04:33,340 --> 00:04:34,410
on something else.

52
00:04:36,170 --> 00:04:47,570
So once again shows spending tree so on switched to its chosen gigabit 00 as its root port can path

53
00:04:47,570 --> 00:04:53,240
cost be used to determine the best path to the route bridge based on its port numbers.

54
00:04:53,550 --> 00:05:00,170
And the answer is no the path of this link is for the path cost of the Slinky's for the path cost of

55
00:05:00,170 --> 00:05:02,270
this link is for.

56
00:05:02,770 --> 00:05:05,910
But that cant be used as the determining factor.

57
00:05:06,020 --> 00:05:12,320
So the next choice is neighbor bridge ID now and this example switch to is connected to switch one on

58
00:05:12,320 --> 00:05:15,920
two ports that are directly connected to switch one.

59
00:05:16,010 --> 00:05:19,440
So the neighboring bridge ID on both these ports is the same.

60
00:05:19,580 --> 00:05:22,790
So that cannot be used as the tiebreaker.

61
00:05:22,790 --> 00:05:28,600
The next decision criteria is based on priority but the priority of the ports are the same.

62
00:05:28,640 --> 00:05:31,250
So that can be used as a tiebreaker.

63
00:05:31,340 --> 00:05:35,500
So the port number is used as the tiebreaker.

64
00:05:35,840 --> 00:05:38,280
One is a lower number than 2.

65
00:05:38,540 --> 00:05:44,250
So hence kickabout is 0 0 is chosen as the route port in this topology.

66
00:05:44,450 --> 00:05:51,290
Now once the route ports are chosen on a per segment basis a designated port needs to be chosen.

67
00:05:51,620 --> 00:06:01,160
The easiest way to work this out is imagine that you have a PC in the middle of the cable and it needs

68
00:06:01,160 --> 00:06:06,440
to get to the root bridge using either the port on the left or the port on the right.

69
00:06:06,440 --> 00:06:12,680
So if I had a PC in this apology which port would use to get to the root bridge and hopefully it's fairly

70
00:06:12,680 --> 00:06:20,240
obvious that this port is closer to the root bridge than this port and hence on the segment gigabit

71
00:06:20,330 --> 00:06:30,680
00 to Gigabit 00 this port Port is 00 on switch one is the designated port a designated port is the

72
00:06:30,680 --> 00:06:36,540
best port to use on a per segment basis to get to the root bridge.

73
00:06:36,560 --> 00:06:42,620
So this port is the base port to use on the top segment to get to the root bridge.

74
00:06:42,620 --> 00:06:45,500
What about the segment on this segment.

75
00:06:45,530 --> 00:06:48,470
Imagine once again that you had a PC here.

76
00:06:48,470 --> 00:06:52,090
What's its best port to use to get to the root bridge.

77
00:06:52,750 --> 00:06:55,780
Well it would be this port here on switch one.

78
00:06:56,230 --> 00:07:03,190
And once again on switch one we can see that by typing show spanning tree nodes gigabit zero one on

79
00:07:03,230 --> 00:07:08,320
switch one is the designated port for this segment.

80
00:07:08,350 --> 00:07:13,690
The same is true for the segment which is the base port to use to get to the root bridge.

81
00:07:13,720 --> 00:07:23,940
It's going to be gigabit 0 3 on switch 1 and on the segment looking at least two switches running spending

82
00:07:23,940 --> 00:07:24,600
three.

83
00:07:24,740 --> 00:07:28,930
This port is the base port to use to get to the root bridge.

84
00:07:29,000 --> 00:07:32,190
So if not chosen a designated port for this top link.

85
00:07:32,480 --> 00:07:40,990
The second link these links through the hub as well as the link the last remaining link is this link.

86
00:07:41,120 --> 00:07:48,320
And the best port to use to get to the root bridge is this port on switch to any other ports on the

87
00:07:48,320 --> 00:07:50,010
network will go blocking.

88
00:07:50,030 --> 00:07:57,370
So this port gigabit 0 1 is put in the blocking state and so is gigabit.

89
00:07:57,380 --> 00:07:58,440
0 3.

90
00:07:58,470 --> 00:08:03,980
Also put in the blocking state and Reppert spending tree or Reppert Peavey's T.

91
00:08:04,070 --> 00:08:07,220
These are known as alternate ports.

92
00:08:07,220 --> 00:08:14,210
In other words on this hub as an example if we had a PC connected to it if this link went down PCs could

93
00:08:14,210 --> 00:08:21,080
send traffic into the network using this alternate port because it would not transition to the forwarding

94
00:08:21,080 --> 00:08:23,700
state when this link goes down.
