Well, that brings us to the end of our conversation on rapid spanning tree.
It feels fast because we didn't spend a lot of time doing it, but at the same
time, when
we think about it, it's really a lot of the same concepts.
We just need to understand what's different.
And primarily what's different is that if we can validate that there's not
going to
be a hub somewhere on the network and we can reach out to the other switch and
negotiate,
we can immediately bring ports online.
And then from there, just recognizing what else needs to change, whether it's
the way
our halo is propagate or the way our topology changes propagate, as well as the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
our halo is propagate or the way our topology changes propagate, as well as the
different
states and port roles.
But once we get all of that down, we understand how rapid works because outside
of that, it
operates the same as traditional spanning tree.
Now as far as the lab is concerned, everything in the lab challenge is really
just what we
did in the demonstration videos.
If you had any problems, be sure to go and reference that video in order to
make sure
we've got the process down for enabling rapid spanning tree, as well as running
some commands
to see some of the mechanisms in action. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to see some of the mechanisms in action.
I hope this has been informative for you and I'd like to thank you for viewing.