|
0:00:13
|
Now, the next thing we need to know here is...
|
|
0:00:15
|
what are some of the other minor features that we can
|
|
0:00:21
|
And it mainly relates to how the synchronization
|
|
0:00:26
|
So, when we are running either Multiple Spanning
|
|
0:00:34
|
the switches are using that synchronization process
|
|
0:00:40
|
and what should be the root ports versus
|
|
0:00:46
|
Now, essentially, the way
|
|
0:00:51
|
some device is first elected
|
|
0:00:57
|
The root bridge then tells
|
|
0:01:00
|
let's say, switch 1.
|
|
0:01:03
|
The root bridge basically
|
|
0:01:06
|
Okay, this is inside the
|
|
0:01:10
|
If switch 1 agrees on this,
|
|
0:01:12
|
it transitions this interface immediately
|
|
0:01:18
|
which means that it is forwarding.
|
|
0:01:21
|
Once it has done this,
|
|
0:01:23
|
every other downstream facing interface
|
|
0:01:31
|
Once these are transitioned to blocking,
|
|
0:01:35
|
switch 1 then sends its own proposals
|
|
0:01:39
|
downstream to the other neighbors.
|
|
0:01:42
|
So, if we have three other
|
|
0:01:45
|
switch 1 is gonna say, "I know about this
|
|
0:01:51
|
you're gonna transition your port to root.
|
|
0:01:54
|
Then, send me the acknowledgment."
|
|
0:01:56
|
Okay, which is the proposal response.
|
|
0:01:59
|
Then, you in turn will block your downstream ports,
|
|
0:02:07
|
So, the key here is that we're
|
|
0:02:11
|
moving towards the leaves in this
|
|
0:02:18
|
And it makes them quickly
|
|
0:02:22
|
Now, the reason that I'm mentioning
|
|
0:02:26
|
will only happen if these links are
|
|
0:02:37
|
Where a point-to-point link
|
|
0:02:44
|
So, if the link for some reason
|
|
0:02:48
|
or it's actually plugged into a hub,
|
|
0:02:50
|
then, the proposal process
|
|
0:02:55
|
Okay, for links that are not point-to-point,
|
|
0:02:57
|
the normal legacy Spanning
|
|
0:03:02
|
Which means that we have to go through
|
|
0:03:07
|
Then, if we're moving from blocking to forwarding,
|
|
0:03:11
|
before we go to listening and learning.
|
|
0:03:15
|
Now, the second point is that
|
|
0:03:20
|
An edge-port in Rapid Spanning Tree
|
|
0:03:23
|
is the equivalent of a port fast enabled
|
|
0:03:28
|
The reason that this is significant
|
|
0:03:31
|
is that if one of these interfaces on
|
|
0:03:38
|
Host 1.
|
|
0:03:41
|
If this link is full-duplex,
|
|
0:03:44
|
it means that the proposal
|
|
0:03:47
|
if it is configured as "Not Edge".
|
|
0:03:53
|
So if switch 1 is not configured,
|
|
0:03:57
|
Switch 1 is gonna send the proposal.
|
|
0:04:02
|
And we're assuming that host 1 is
|
|
0:04:06
|
So, it means that it's not gonna
|
|
0:04:11
|
Which in turn would then force switch 1 to revert
|
|
0:04:19
|
So, it means that on the
|
|
0:04:22
|
if we don't configure these interfaces
|
|
0:04:26
|
we're not gonna have rapid convergence.
|
|
0:04:30
|
So, when you look at the overall network design,
|
|
0:04:32
|
we need to make sure that
|
|
0:04:35
|
are point-to-point non-edge ports,
|
|
0:04:39
|
and all other interfaces that go to end hosts or phones,
|
|
0:04:46
|
those need to be edge ports as defined
|
|
0:04:54
|
So, event though the
|
|
0:04:58
|
technically says that every port that is non
|
|
0:05:05
|
Cisco's implementation doesn't do that.
|
|
0:05:09
|
the Spanning Tree Port Fast command
|
|
0:05:12
|
to allow for backwards compatability.
|
|
0:05:16
|
So, they're assuming that if you're implementing Multiple
|
|
0:05:20
|
you're already coming from
|
|
0:05:24
|
So, whatever your previous
|
|
0:05:29
|
will then now become Rapid
|
|
0:05:35
|
Now, we can see this when we look at...
|
|
0:05:38
|
the particular topology we have now.
|
|
0:05:42
|
On
|
|
0:05:45
|
switch 4, we were looking at the...
|
|
0:05:48
|
the Show Spanning Tree MST
|
|
0:05:53
|
Show...
|
|
0:05:58
|
Show Spanning Tree MST 1.
|
|
0:06:05
|
Okay, MST 1 is for VLANs 10, 40, and 50.
|
|
0:06:10
|
If we look at the topology,
|
|
0:06:19
|
VLAN 10 is on switch 1.
|
|
0:06:22
|
And it's on switch 2.
|
|
0:06:25
|
So, right now, the traffic for that
|
|
0:06:29
|
this direction, because we modified
|
|
0:06:34
|
On switch 2,
|
|
0:06:37
|
if we look at the same output,
|
|
0:06:40
|
Okay, we can that this link
|
|
0:06:46
|
Okay it says it's designated blocking.
|
|
0:06:49
|
Okay now, it says it's designated forwarding.
|
|
0:06:51
|
Okay this port should be
|
|
0:06:56
|
If we look at the configuration
|
|
0:06:58
|
of that port, there's nothing there
|
|
0:07:02
|
If I were to go to router 2,
|
|
0:07:04
|
and test my reachability to router 1,
|
|
0:07:09
|
okay, right now, I can reach that device.
|
|
0:07:13
|
If I were to shut the link down,
|
|
0:07:19
|
then bring the link back,
|
|
0:07:21
|
since I'm causing a topology change now,
|
|
0:07:30
|
switch 2 who is connected to router 2
|
|
0:07:33
|
is gonna send the Rapid
|
|
0:07:37
|
But since this is...
|
|
0:07:40
|
Not running Rapid Spanning
|
|
0:07:43
|
it's not gonna get a response.
|
|
0:07:46
|
Okay, we can see this on switch 2
|
|
0:07:53
|
MSTP...
|
|
0:07:56
|
proposals.
|
|
0:08:00
|
Then, on router 2, let's shut
|
|
0:08:09
|
The interface goes down.
|
|
0:08:12
|
Now, the interface comes back up.
|
|
0:08:17
|
Switch 2 is sending the proposal.
|
|
0:08:20
|
It's not getting a response back in.
|
|
0:08:23
|
If we were to look at the time stamps,
|
|
0:08:26
|
we would see now that this interface...
|
|
0:08:29
|
is going through the normal
|
|
0:08:32
|
So, if we Show Spanning Tree MST 1,
|
|
0:08:36
|
we can see we're in learning.
|
|
0:08:45
|
Still on learning.
|
|
0:08:48
|
Now, we're on forwarding.
|
|
0:08:50
|
Now, router 2 can send the traffic.
|
|
0:08:51
|
But if you look, we can see
|
|
0:08:54
|
These dots are where router 2 was waiting for
|
|
0:09:01
|
So, what we would want to do instead here
|
|
0:09:06
|
is on switch 2,
|
|
0:09:08
|
either say at the interface level,
|
|
0:09:15
|
Or in global config, Spanning
|
|
0:09:23
|
Now, when we look at the change
|
|
0:09:30
|
switch 1 knows that router
|
|
0:09:36
|
And likewise, it should know...
|
|
0:09:39
|
if we...
|
|
0:09:42
|
Show Spanning Tree MST 1,
|
|
0:09:46
|
it knows that router 2's link is an edge port.
|
|
0:09:50
|
Because we're not receiving
|
|
0:09:55
|
This would then imply...
|
|
0:09:57
|
that is router 2's link goes down,
|
|
0:10:05
|
and comes back up,
|
|
0:10:07
|
we should not have to wait
|
|
0:10:10
|
for listening and learning in
|
|
0:10:13
|
So, there's gonna be some basic delay here as we
|
|
0:10:19
|
But when we look at how many packets
|
|
0:10:25
|
So, it took about 6 seconds for the
|
|
0:10:29
|
And then for Spanning Tree to promote
|
|
0:10:39
|
Now, the same would be true
|
|
0:10:43
|
If for some reason, the link type
|
|
0:10:49
|
or if for some reason, maybe we're
|
|
0:10:52
|
and the links are only working in half duplex.
|
|
0:10:56
|
If we know that there's only
|
|
0:10:59
|
but the link is still running
|
|
0:11:02
|
we can say the Spanning Tree
|
|
0:11:05
|
which means that the proposal
|
|
0:11:12
|
So, both of these points,
|
|
0:11:14
|
with this command, the Link
|
|
0:11:17
|
this is whether you're running Multiple Spanning
|
|
0:11:23
|
So, this one is really, really straightforward.
|
|
0:11:25
|
If your switches support it,
|
|
0:11:29
|
and you don't wanna do a full
|
|
0:11:32
|
this is really the easiest way to go
|
|
0:11:34
|
Because the only thing you need to do
|
|
0:11:40
|
Spanning Tree Mode Rapid PVST.
|
|
0:11:54
|
So, we'll put it on all four of the switches.
|
|
0:12:00
|
Then, we'll say, Show
|
|
0:12:07
|
We are now running Per-VLAN
|
|
0:12:11
|
but the algorithm for the convergence
|
|
0:12:18
|
So, this is having still one instance of
|
|
0:12:23
|
but we're using the proposal process
|
|
0:12:27
|
in order to do the fast convergence
|
|
0:12:31
|
Still at the link levels going to the access
|
|
0:12:36
|
Spanning Tree Port Fast,
|
|
0:12:38
|
because this then is
|
|
0:12:45
|
Now, if we were to... Let's say we
|
|
0:12:52
|
And let's do a ping between...
|
|
0:12:54
|
router 2 and router 1.
|
|
0:12:56
|
We'll see that if this link goes
|
|
0:13:01
|
it's almost immediate that we
|
|
0:13:13
|
1, 2, 3, 4, 5...
|
|
0:13:18
|
1, 2, 3, 4, 5, 6. So that was 12 seconds.
|
|
0:13:23
|
Probably they didn't fully negotiate everything
|
|
0:13:34
|
So, if we Show Spanning Tree...
|
|
0:13:37
|
VLAN 10,
|
|
0:13:43
|
it says, "Fast Ethernet 13 is a point-to-point peer."
|
|
0:13:50
|
And let's see... What does switch 2 say?"
|
|
0:14:06
|
"Fast Ethernet 13 is a point-to-point peer."
|
|
0:14:08
|
I wonder if...
|
|
0:14:10
|
these switches in their different platforms.
|
|
0:14:14
|
I wonder if they're running
|
|
0:14:20
|
Because the convergence should be...
|
|
0:14:24
|
almost immediate.
|
|
0:14:28
|
But in this case, when you have
|
|
0:14:31
|
you don't need to configure
|
|
0:14:38
|
Okay, there's a question. So for...
|
|
0:14:44
|
Rapid Spanning Tree protocol, you have to enable
|
|
0:14:49
|
To configure them as edge ports correct.
|
|
0:14:51
|
So, on switch 1, when we look at
|
|
0:14:57
|
it says that, "The link to Fast Ethernet
|
|
0:15:01
|
This means that if the link goes
|
|
0:15:06
|
we don't need to send a proposal out there.
|
|
0:15:09
|
We immediately go from the down state
|
|
0:15:14
|
But for these interfaces,
|
|
0:15:19
|
we do need to go to the proposal process,
|
|
0:15:22
|
because these are point-to-point links
|
|
0:15:25
|
So, let's try this one more time.
|
|
0:15:30
|
And then on switch 1, I'm gonna
|
|
0:15:36
|
which is my root port.
|
|
0:15:39
|
And in this case...
|
|
0:15:45
|
Actually, router 2 didn't drop any packets
|
|
0:15:48
|
Probably what happened before
|
|
0:15:52
|
the network wasn't properly
|
|
0:15:56
|
So, it means now, when switch 1 is changing
|
|
0:16:02
|
so from Fast Ethernet 16 is switching to 13,
|
|
0:16:05
|
it's taking less than 2 seconds to do that,
|
|
0:16:08
|
and I can tell that because my
|
|
0:16:15
|
Now, if we wanted to get a little more accurate
|
|
0:16:29
|
So, Fast Ethernet 16 now,
|
|
0:16:38
|
So, I'm forwarding this way.
|
|
0:16:41
|
The network should be re-converged.
|
|
0:16:44
|
Let's do the ping on router 2 again.
|
|
0:16:50
|
We'll say, Send...
|
|
0:16:54
|
Let's say 5000 packets
|
|
0:16:56
|
with the time out of 1 second.
|
|
0:16:59
|
So, once... As soon as I do this, I'm
|
|
0:17:05
|
So, let's start the ping on router 2.
|
|
0:17:07
|
And then, shut the link down on switch 1.
|
|
0:17:21
|
So, it didn't drop a single packet. So it means
|
|
0:17:25
|
is less than 1 second.
|
|
0:17:28
|
So, the only thing that you need to do on all
|
|
0:17:31
|
Spanning Tree Mode Rapid PVST.
|
|
0:17:35
|
And all the path selection in root bridge
|
|
0:17:41
|
with Per-VLAN Spanning Tree,
|
|
0:17:43
|
all of that is gonna stay the same.
|
|
0:17:46
|
The only difference is that
|
|
0:17:49
|
we're using the Rapid Spanning
|
|
0:17:52
|
as opposed to the legacy 802.D algorithm.
|